2 Sensation Resurr. Completed but does not turn on - GSM-Forum

scorcci · 10-10-2012, 07:24

Hi Folks,
Here I am again.
I just completed the resurrection with 2 HTC Senstation, everything went just fine on the Riff Box but I still can not turn them on or enter on the Bootloader, any help will be very appreciated.

Here is the reports from riff box.

Device One: Sensation 4G Tmobile:

Open serial port...OK
Connecting to the RIFF Box...OK
Firmware Version: 1.33, JTAG Manager Version: 1.44
Selected Resurrector: [HTC Sensation4G (PG5810000) V1.0.4557.1904]

Connecting to the dead body...OK
Detected dead body ID: 0x104210E1 - CORRECT!
Set I/O Voltage reads as 1.80V, 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: 0x0015/0x0000 (MLL00M, 0x000090000000 Bytes = 2.25 GB)
Detected an Initialized FLASH2 Chip, ID: 0x0015/0x0000 (MLL00M, 0x000000080000 Bytes = 0.50 MB)

Flashing the dead body...OK
ERROR: Timeout while waiting for DCC Loader response. Trying to recover...OK
Resurrection complete!

---

Device Two: Just Sensation, I guess, XE model:

Open serial port...OK
Connecting to the RIFF Box...OK
Firmware Version: 1.33, JTAG Manager Version: 1.44
Selected Resurrector: [HTC Sensation (PG5813000) V1.0.4557.1879]

Connecting to the dead body...OK
Detected dead body ID: 0x104210E1 - CORRECT!
Set I/O Voltage reads as 1.80V, 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: 0x0015/0x0000 (MLL00M, 0x000090000000 Bytes = 2.25 GB)
Detected an Initialized FLASH2 Chip, ID: 0x0015/0x0000 (MLL00M, 0x000000080000 Bytes = 0.50 MB)

Flashing the dead body...OK
Resurrection complete!

---
At this moment I am writing the full 2.5gb senstation flash file bin on the XE Model to see what happen next, if it will get back to work.
But anyway, I want to hear from you guys what is going on, if you can help me again.
Thank you very much again.

Faheem Anjum · 10-10-2012, 07:29

what the status of phone before repair boot ?

scorcci · 10-10-2012, 15:33

Hi Dear,
THanks for your help.
Both turned off from nothing and did not back to turn on again...
It seens to be something hard to fix, but we never know.
By the way, here is the report from write flashing, I tried to turn on and it did not work.
Since both uses the same type of front painel, I tested on both painels and did not turn on.
regards.

---

Firmware Version: 1.33, JTAG Manager Version: 1.44
Selected Resurrector: [HTC Sensation (PG5813000) V1.0.4557.1879]

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

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: 0x0015/0x0000 (MLL00M, 0x000090000000 Bytes = 2.25 GB)
Detected an Initialized FLASH2 Chip, ID: 0x0015/0x0000 (MLL00M, 0x000000080000 Bytes = 0.50 MB)

Writting FLASH1 memory from 0x000000000000 to 0x00008FFFFFFF
ERROR: Timeout while waiting for DCC Loader response. Trying to recover...OK
ERROR: DCC Loader has reported Error Code = 0x35 (0x000000). Trying to recover...OK
ERROR: DCC Loader has reported Error Code = 0x35 (0x000000). Trying to recover...OK
ERROR: Timeout while waiting for DCC Loader response. Trying to recover...OK
ERROR: DCC Loader has reported Error Code = 0x35 (0x000000). Trying to recover...OK
ERROR: DCC Loader has reported Error Code = 0x22 (0x000000). Trying to recover...OK
ERROR: Timeout while waiting for DCC Loader response. Trying to recover...OK
ERROR: DCC Loader has reported Error Code = 0x22 (0x000000). Trying to recover...OK
Completed in 07:06:42.744 (Average Transfer Rate: 92.15 kB/s)

Faheem Anjum · 10-11-2012, 08:46

contact me on sonork if you have some time

**legija** · 10-11-2012, 11:17

That is well known fault with HTC new phones. Few users reported that reballing CPU and RAm helped.

scorcci · 10-11-2012, 14:11

Thanks Mr. Faheem, I will search for you on sonork, thanks Mr. Legija, but what means reballing? That would be ressolder with hot air?
Regards.

BABAK NURI · 10-11-2012, 23:57

Yes,Reball or Resolder
--
But Both (CPU+eMMC) Haved Glue...So You Need Carful when use hot air
--
I haved few phone(sensation_Normall-XE and XL)...Same as your phone
This is HW Fault(99.9%)

scorcci · 10-18-2012, 08:34

Thanks again folks.
My friend applied flux to ressold eMMC on both logic boards.
I made the ressurrection process again and one logic is back to working state after installing a RUU.
The second logic board did not work, in fact is getting very very hot, I guess something is causing short curcuit, but I was thinking about HW problems on this one.
Thanks again everybody for your great support, regards.

10-10-2012, 07:24	#1 (permalink)
scorcci Crazy Poster Join Date: Oct 2011 Posts: 56 Member: 1670612 Status: Offline Thanks Meter: 5	2 Sensation Resurr. Completed but does not turn on Hi Folks, Here I am again. I just completed the resurrection with 2 HTC Senstation, everything went just fine on the Riff Box but I still can not turn them on or enter on the Bootloader, any help will be very appreciated. Here is the reports from riff box. Device One: Sensation 4G Tmobile: Open serial port...OK Connecting to the RIFF Box...OK Firmware Version: 1.33, JTAG Manager Version: 1.44 Selected Resurrector: [HTC Sensation4G (PG5810000) V1.0.4557.1904] Connecting to the dead body...OK Detected dead body ID: 0x104210E1 - CORRECT! Set I/O Voltage reads as 1.80V, 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: 0x0015/0x0000 (MLL00M, 0x000090000000 Bytes = 2.25 GB) Detected an Initialized FLASH2 Chip, ID: 0x0015/0x0000 (MLL00M, 0x000000080000 Bytes = 0.50 MB) Flashing the dead body...OK ERROR: Timeout while waiting for DCC Loader response. Trying to recover...OK Resurrection complete! --- Device Two: Just Sensation, I guess, XE model: Open serial port...OK Connecting to the RIFF Box...OK Firmware Version: 1.33, JTAG Manager Version: 1.44 Selected Resurrector: [HTC Sensation (PG5813000) V1.0.4557.1879] Connecting to the dead body...OK Detected dead body ID: 0x104210E1 - CORRECT! Set I/O Voltage reads as 1.80V, 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: 0x0015/0x0000 (MLL00M, 0x000090000000 Bytes = 2.25 GB) Detected an Initialized FLASH2 Chip, ID: 0x0015/0x0000 (MLL00M, 0x000000080000 Bytes = 0.50 MB) Flashing the dead body...OK Resurrection complete! --- At this moment I am writing the full 2.5gb senstation flash file bin on the XE Model to see what happen next, if it will get back to work. But anyway, I want to hear from you guys what is going on, if you can help me again. Thank you very much again.

10-10-2012, 07:29	#2 (permalink)
Faheem Anjum No Life Poster Join Date: Nov 2006 Location: (United States Of Islam) Age: 37 Posts: 24,984 Member: 399832 Status: Offline Sonork: Faheem Anjum Thanks Meter: 24,310	what the status of phone before repair boot ?

10-10-2012, 15:33	#3 (permalink)
scorcci Crazy Poster Join Date: Oct 2011 Posts: 56 Member: 1670612 Status: Offline Thanks Meter: 5	Hi Dear, THanks for your help. Both turned off from nothing and did not back to turn on again... It seens to be something hard to fix, but we never know. By the way, here is the report from write flashing, I tried to turn on and it did not work. Since both uses the same type of front painel, I tested on both painels and did not turn on. regards. --- Firmware Version: 1.33, JTAG Manager Version: 1.44 Selected Resurrector: [HTC Sensation (PG5813000) V1.0.4557.1879] Connecting to the dead body...OK Detected dead body ID: 0x104210E1 - CORRECT! Set I/O Voltage reads as 1.80V, TCK Frequency is RTCK Adaptive Clocking RTCK Sampling is: [Sample at MAX] Settings Code: 0x24010000000000000000000090000000 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: 0x0015/0x0000 (MLL00M, 0x000090000000 Bytes = 2.25 GB) Detected an Initialized FLASH2 Chip, ID: 0x0015/0x0000 (MLL00M, 0x000000080000 Bytes = 0.50 MB) Writting FLASH1 memory from 0x000000000000 to 0x00008FFFFFFF ERROR: Timeout while waiting for DCC Loader response. Trying to recover...OK ERROR: DCC Loader has reported Error Code = 0x35 (0x000000). Trying to recover...OK ERROR: DCC Loader has reported Error Code = 0x35 (0x000000). Trying to recover...OK ERROR: Timeout while waiting for DCC Loader response. Trying to recover...OK ERROR: DCC Loader has reported Error Code = 0x35 (0x000000). Trying to recover...OK ERROR: DCC Loader has reported Error Code = 0x22 (0x000000). Trying to recover...OK ERROR: Timeout while waiting for DCC Loader response. Trying to recover...OK ERROR: DCC Loader has reported Error Code = 0x22 (0x000000). Trying to recover...OK Completed in 07:06:42.744 (Average Transfer Rate: 92.15 kB/s)

10-11-2012, 08:46	#4 (permalink)
Faheem Anjum No Life Poster Join Date: Nov 2006 Location: (United States Of Islam) Age: 37 Posts: 24,984 Member: 399832 Status: Offline Sonork: Faheem Anjum Thanks Meter: 24,310	contact me on sonork if you have some time

10-11-2012, 11:17	#5 (permalink)
legija Product Manager Join Date: Apr 2006 Age: 55 Posts: 5,746 Member: 256342 Status: Offline Sonork: None Thanks Meter: 28,276	That is well known fault with HTC new phones. Few users reported that reballing CPU and RAm helped.

10-11-2012, 14:11	#6 (permalink)
scorcci Crazy Poster Join Date: Oct 2011 Posts: 56 Member: 1670612 Status: Offline Thanks Meter: 5	Thanks Mr. Faheem, I will search for you on sonork, thanks Mr. Legija, but what means reballing? That would be ressolder with hot air? Regards.

10-11-2012, 23:57	#7 (permalink)
BABAK NURI Product Supporter Join Date: Mar 2005 Location: Tehran.IR Age: 43 Posts: 7,259 Member: 131131 Status: Offline Sonork: 100.1606847 Thanks Meter: 4,475	Yes,Reball or Resolder -- But Both (CPU+eMMC) Haved Glue...So You Need Carful when use hot air -- I haved few phone(sensation_Normall-XE and XL)...Same as your phone This is HW Fault(99.9%)

10-18-2012, 08:34	#8 (permalink)
scorcci Crazy Poster Join Date: Oct 2011 Posts: 56 Member: 1670612 Status: Offline Thanks Meter: 5	Thanks again folks. My friend applied flux to ressold eMMC on both logic boards. I made the ressurrection process again and one logic is back to working state after installing a RUU. The second logic board did not work, in fact is getting very very hot, I guess something is causing short curcuit, but I was thinking about HW problems on this one. Thanks again everybody for your great support, regards.