HTC Desire V successfully resurrected but not working properly

[slim.legend]

Hi,
I received a htc desire v in fastboot mode which would't go into RUU mode or recovery. I tried to unlock it's bootloader but the id token was corrupted. I connected it to riffbox and resurrect it and set the super cid. Now im enable to flash a stock rom on it and unlock it's bootloader. I flashed it with a stock rom and after it restarts, it stayed on logo and shutdown! I unlocked it and write a custom recovery... but still it wont boot into recovery. Can anyone help me out? Mr babak nuri please tell me what is your opinion about this? Will writing a full dump be helpful? Thanks in advance

[BABAK NURI]

Hi
Yes,Dump file is good idea...But You Know all suddenly error or dead is HW for 99%

So,Just try write 256mb via dcc loader,Then Try set only superCID and Flash With Latest RUU

[slim.legend]

Originally Posted by BABAK NURI

Hi
Yes,Dump file is good idea...But You Know all suddenly error or dead is HW for 99%

So,Just try write 256mb via dcc loader,Then Try set only superCID and Flash With Latest RUU

I did as you said but the problem exist... what do you recommend sir?

[slim.legend]

Open serial port...OK
Connecting to the RIFF Box...OK
Firmware Version: 1.37, JTAG Manager Version: 1.55
Selected Resurrector: [HTC DesireV (PL1110000) V1.0.4800.54829]

Connecting to the dead body...OK
Detected dead body ID: 0x106220E1 - IGNORED!
Set I/O Voltage reads as 2.60V, TCK Frequency is RTCK
Adaptive Clocking RTCK Sampling is: [Sample at MAX]
Settings Code: 0x20010000000000000000000010000000

Resurrection sequence started.
Establish communication with the phone...OK
Initializing internal hardware configuration...OK
Uploading resurrector data into memory...OK
Starting communication with resurrector...OK

Detected an Initialized FLASH1 Chip, ID: 0x0090/0x014A (XINYH, 0x00008F800000 Bytes = 2.24 GB)
Detected an Initialized FLASH2 Chip, ID: 0x0090/0x014A (XINYH, 0x000000200000 Bytes =2 .00 MB)

Writting FLASH1 memory from 0x000000000000 to 0x00000FFFFFFF
Completed in 00:50:17.433 (Average Transfer Rate: 86.88 kB/s)

I tried it one more time and here is the log...

[BABAK NURI]

So,I Think if you have "hang on Logo" Problem,,,Usually is eMMC fault But I haved this phone with exact your problem...Only solve when i did replace CPU
-
Thx

[slim.legend]

Originally Posted by BABAK NURI

So,I Think if you have "hang on Logo" Problem,,,Usually is eMMC fault But I haved this phone with exact your problem...Only solve when i did replace CPU
-
Thx

Thank you sir for all you help. I will try changing CPU and report if it worked.

[slim.legend]

Unfortunately it didnt worked Mr Nuri. Anyway thank you for all your helpfull advices...