Htc thunderbolt stuck on 53%

[CHAGUA]

HEY THERE, I HAVE THIS HTC THUNDERBOLT (MECHA) ADR6400LVZW THAT I REPIAR BOOT , AFTER RAPAIR PHONE ENTER IN FASTBOOT VOL- + POWER

WHEN I TRY TO LOAD THE RUU PHONE STUCK ON 54%

WHITH OTHER RUU STUCK ON 12%

MECHA XD SHIP S-OFF
HBOOT-1.04.000
MICROP-/
RADIO-1.48.00.0930W_3
eMMC-BOOT
FEB 23 2011,20:42:55




AND ALSO DO I HAVE TO REPAIR ALSO THE CP AREA?
IF THAT THE CASE WHAT PARAMETERS DO I NEED

CID 11111111 OR VZW_0001
DOES MAKE ANY DEFRENCE IF I PUT A DEFERENT IMEI ON CP PART AND OTHER O AP PART?

AFTER I DO UNLOCK PROCEDURE I MEAN UNLOCK THE PHONE, THE BOOT LOADER ALSO UNLOCKS, SO WHY I CANT LOAD ANY RUU SINCE I USE UNLOCK BOOT LOADER AND CID 11111111

[BABAK NURI]

Hi
Mybe You have a bad sector on flash chip.....

[CHAGUA]

Originally Posted by BABAK NURI

Hi
Mybe You have a bad sector on flash chip.....

THE PHONE WAS IN A GOOD CONDITION, MY OTHER PARTNER KILLIT WHILE ROOTING IT

HERES THE AP PART

Open serial port...OK
Connecting to the RIFF Box...OK
Firmware Version: 1.32, JTAG Manager Version: 1.43
Selected Resurrector: [HTC Thunderbolt AP V1.0.0.0]

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

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: 0x0045/0x0000 (SEM08G, 0x00010B800000 Bytes = 4.18 GB)
Detected an Initialized FLASH2 Chip, ID: 0x0045/0x0000 (SEM08G, 0x000000100000 Bytes = 1.00 MB)

Flashing the dead body...OK
Resurrection complete!

HERES THE CP PART




Open serial port...OK
Connecting to the RIFF Box...OK
Firmware Version: 1.32, JTAG Manager Version: 1.43
Selected Resurrector: [HTC Thunderbolt CP V1.0.0.0]

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

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: 0x00AD/0x15A1 (128MB)
Selected Resurrection Data for the NAND Chip with Page size = 2KB

Flashing the dead body...OK
WARNING: Programming Error (0x24) at 0x0000002C0000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x0000002C8000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x0000002D0000 is handled as Cut Excess.
Resurrection complete!

BRINGS TO MY ATTENTION THIS 3 ERROS DIGGIN AND LOOKING ON XDA, THE PROBLEM IS ON MDM PARTITION THERES SOMETHING THAT ACROSS TO YOUR MIND

[CHAGUA]

Originally Posted by chagua

the phone was in a good condition, my other partner killit while rooting it

heres the ap part

open serial port...ok
connecting to the riff box...ok
firmware version: 1.32, jtag manager version: 1.43
selected resurrector: [htc thunderbolt ap v1.0.0.0]

connecting to the dead body...ok
detected dead body id: 0x17b360e1 - ignored!
Set i/o voltage reads as 2.01v, tck frequency is rtck
adaptive clocking rtck sampling is: [sample at max]

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: 0x0045/0x0000 (sem08g, 0x00010b800000 bytes = 4.18 gb)
detected an initialized flash2 chip, id: 0x0045/0x0000 (sem08g, 0x000000100000 bytes = 1.00 mb)

flashing the dead body...ok
resurrection complete!

heres the cp part




open serial port...ok
connecting to the riff box...ok
firmware version: 1.32, jtag manager version: 1.43
selected resurrector: [htc thunderbolt cp v1.0.0.0]

connecting to the dead body...ok
detected dead body id: 0x204600e1 - ignored!
Set i/o voltage reads as 1.81v, tck frequency is rtck
adaptive clocking rtck sampling is: [sample at max]

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: 0x00ad/0x15a1 (128mb)
selected resurrection data for the nand chip with page size = 2kb

flashing the dead body...ok
warning: Programming error (0x24) at 0x0000002c0000 is handled as cut excess.
Warning: Programming error (0x25) at 0x0000002c8000 is handled as cut excess.
Warning: Programming error (0x25) at 0x0000002d0000 is handled as cut excess.
Resurrection complete!

brings to my attention this 3 erros diggin and looking on xda, the problem is on mdm partition theres something that across to your mind

doing more research the phone gets stuck on mdm9k= lte radio, cdma radio flash ok, but somehow it does not flash lte radio and i think it has to do with warning errors on resurector

[CHAGUA]

Astillero any answer frontera support?
Br
CHAGUACEDA

Enviado desde mi LG-P930 usando Tapatalk 2