HTC phones with eMMC chip with ID: M4G2DE problems - GSM-Forum

MichieMax · 09-07-2011, 11:44

Any solution on Desire S S510e unlocking with Riff Box
BR

smartecs · 09-11-2011, 13:41

Open serial port...OK
Connecting to the RIFF Box...OK
Firmware Version: 1.26, JTAG Manager Version: 1.35
Selected Resurrector: [HTC Desire S]

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

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: 0x002E/0x0066 (0x0086800000 Bytes)

Flashing the dead body...
ERROR: DCC Loader has reported Error Code = 0x35 (0x000000). Trying to recover...FAILED
ERROR: Failed due to multiple communication errors. Terminating at 0x000008D200

domestik · 09-12-2011, 16:34

same problem for me. Need help, riff team

**legija** · 09-12-2011, 17:18

1. Make sure to have all pins soldered properly,
2. Make sure to have stable power source for phone

Most of errors with Desire S come out off bad soldering, or even some people don't solder GND.

domestik · 09-12-2011, 18:23

I've tried on 4 or 5 pieces, it is not bad soldering. All of my Saga with the problem described here:
[solved]BRICKed: inside eMMC's dead, with E:Can't open /cache/recovery/log - xda-developers

main question is: can we repair it? or there is hardware malfunction of eMMC chip

**legija** · 09-12-2011, 21:36

eMMC doesn't support bad blocks handling, hence once it gets partially damaged, it has to be replaced.

Problem is, even if You replace it with blank chip, it would be impossible to boot it via JTAG since JTAG is enabled by FSBL. Blank eMMC - no FSBL, no JTAG.
Dead loop.

There is, though, some possibility to be explored, but not before two weeks from today.
Our coder is on holidays now.

BesTCooL · 09-14-2011, 12:26

desire S all ok but not make repair

Open serial port...OK
Connecting to the RIFF Box...OK
Firmware Version: 1.26, JTAG Manager Version: 1.35
Selected Resurrector: [HTC Desire S]

Resetting target...OK
STATUS: Target is halted.

R0 = 0xFFFFFFFF R6 = 0x00000000 R12 = 0x00000000
R1 = 0xFFFFFFFC R7 = 0x00000000 R13 = 0x00000000
R2 = 0x00000000 R8 = 0x00000000 R14 = 0x00000000
R3 = 0x00000000 R9 = 0x00000000 R15 = 0xFFFFFFF8
R4 = 0x00000000 R10 = 0x00000000 CPSR = 0x00000000
R5 = 0x00000000 R11 = 0x00000000

Open serial port...OK
Connecting to the RIFF Box...OK
Firmware Version: 1.26, JTAG Manager Version: 1.35
Selected Resurrector: [HTC Desire S]

Connecting to the dead body...OK
Set I/O Voltage reads as 2.59V, TCK Frequency is RTCK
Model selected: HTC - HTC Desire S

Detected dead body ID: 0x17B360E1

Open serial port...OK
Connecting to the RIFF Box...OK
Firmware Version: 1.26, JTAG Manager Version: 1.35
Selected Resurrector: [HTC Desire S]

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

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

wait always no make any operation

BesTCooL · 09-14-2011, 16:10

Flashing the dead body...
ERROR: DCC Loader has reported Error Code = 0x35 (0x000000). Trying to recover...FAILED
ERROR: Failed due to multiple communication errors. Terminating at 0x000008D200

welking · 09-16-2011, 13:33

Quote:

Originally Posted by BesTCooL

Flashing the dead body...
ERROR: DCC Loader has reported Error Code = 0x35 (0x000000). Trying to recover...FAILED
ERROR: Failed due to multiple communication errors. Terminating at 0x000008D200

ME TOO !

hellp！！！！

remark · 09-17-2011, 08:17

Quote:

Originally Posted by BesTCooL

Flashing the dead body...
ERROR: DCC Loader has reported Error Code = 0x35 (0x000000). Trying to recover...FAILED
ERROR: Failed due to multiple communication errors. Terminating at 0x000008D200

The same problem ...

MPhoneClinic · 09-22-2011, 07:10

For me is can't even communicate ......

please check the picture and help me!!

what did i do wrong

Thanks

**legija** · 09-22-2011, 13:15

Quote:

Originally Posted by MPhoneClinic

For me is can't even communicate ......

please check the picture and help me!!

what did i do wrong

Thanks

You did nothing wrong, it's just FSBL erased from phone, hence no JTAG is enabled.
So, for now You can't do much about it.

..::Thanh_gsm::.. · 09-23-2011, 10:55

the same problem, riff box now no solution, wait for good news from OZ.

Quote:

Open serial port...OK
Connecting to the RIFF Box...OK
Firmware Version: 1.26, JTAG Manager Version: 1.35
Selected Resurrector: [HTC Desire S]

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

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: 0x003E/0x0096 (0x0086800000 Bytes)

Flashing the dead body...
ERROR: DCC Loader has reported Error Code = 0x35 (0x000000). Trying to recover...FAILED
ERROR: Failed due to multiple communication errors. Terminating at 0x000008D200

an144 · 09-30-2011, 17:28

I have exactly the same problem.
when the solution?

demon · 10-02-2011, 08:28

I have also problem with resurrecting Desire S.

Resurrection finishes fine, but phone wont boot, cannot enter into recovery, hboot, nothing.
The phone was in boot loop after an official update, tried flashing it with an SDcard method, but the flashing froze, when it was writing the radio_v2 part. After waiting about 30min, I pulled battery, and since then I cannot make it to boot. Tried all combinations with Riff (reflash SPL, write custom CID, repair and reflash imei zone, etc...), and nothing works.

Please help...

d3m0n

PS
Here is log of operation

[10/1/2011 3:15:58 PM] [START OPERATION_ID = RESURRECT]
[10/1/2011 3:18:33 PM] Open serial port...OK
[10/1/2011 3:18:33 PM] Connecting to the RIFF Box...OK
[10/1/2011 3:18:33 PM] Firmware Version: 1.26, JTAG Manager Version: 1.35
[10/1/2011 3:18:33 PM] Selected Resurrector: [HTC Desire S]
[10/1/2011 3:18:33 PM]
[10/1/2011 3:18:33 PM] Connecting to the dead body...OK
[10/1/2011 3:18:33 PM] Detected dead body ID: 0x17B360E1 - CORRECT!
[10/1/2011 3:18:33 PM] Set I/O Voltage reads as 2.61V, TCK Frequency is RTCK
[10/1/2011 3:18:33 PM] Adaptive Clocking RTCK Sampling is: [Sample at MAX]
[10/1/2011 3:18:33 PM]
[10/1/2011 3:18:33 PM] Resurrection sequence started.
[10/1/2011 3:18:33 PM] Establish communication with the phone...OK
[10/1/2011 3:18:33 PM] Initializing internal hardware configuration...OK
[10/1/2011 3:18:33 PM] Uploading resurrector data into memory...OK
[10/1/2011 3:18:33 PM] Starting communication with resurrector...OK
[10/1/2011 3:18:33 PM]
[10/1/2011 3:18:33 PM] Detected an Initialized FLASH1 Chip, ID: 0x003E/0x0082 (0x0086800000 Bytes)
[10/1/2011 3:18:33 PM]
[10/1/2011 3:18:33 PM] Flashing the dead body...OK
[10/1/2011 3:18:33 PM] Resurrection complete!
[10/1/2011 3:18:33 PM] [FINISH OPERATION_ID = RESURRECT]

09-07-2011, 11:44	#1 (permalink)
MichieMax No Life Poster Join Date: Oct 2003 Location: Kenya,Mombasa Posts: 757 Member: 40758 Status: Offline Thanks Meter: 26	Any news on HTC desire S S510e Any solution on Desire S S510e unlocking with Riff Box BR

09-11-2011, 13:41	#2 (permalink)
smartecs Freak Poster Join Date: Oct 2003 Location: mobile world Age: 49 Posts: 395 Member: 42370 Status: Offline Thanks Meter: 32	problem with my desire s.... Open serial port...OK Connecting to the RIFF Box...OK Firmware Version: 1.26, JTAG Manager Version: 1.35 Selected Resurrector: [HTC Desire S] Connecting to the dead body...OK Detected dead body ID: 0x17B360E1 - CORRECT! Set I/O Voltage reads as 2.61V, TCK Frequency is RTCK Adaptive Clocking RTCK Sampling is: [Sample at 1 MHz] 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: 0x002E/0x0066 (0x0086800000 Bytes) Flashing the dead body... ERROR: DCC Loader has reported Error Code = 0x35 (0x000000). Trying to recover...FAILED ERROR: Failed due to multiple communication errors. Terminating at 0x000008D200

09-14-2011, 12:26	#7 (permalink)
BesTCooL No Life Poster Join Date: Dec 2002 Location: TURKEY Age: 44 Posts: 3,285 Member: 18442 Status: Offline Sonork: 111110 Thanks Meter: 622	desire S jtag desire S all ok but not make repair Open serial port...OK Connecting to the RIFF Box...OK Firmware Version: 1.26, JTAG Manager Version: 1.35 Selected Resurrector: [HTC Desire S] Resetting target...OK STATUS: Target is halted. R0 = 0xFFFFFFFF R6 = 0x00000000 R12 = 0x00000000 R1 = 0xFFFFFFFC R7 = 0x00000000 R13 = 0x00000000 R2 = 0x00000000 R8 = 0x00000000 R14 = 0x00000000 R3 = 0x00000000 R9 = 0x00000000 R15 = 0xFFFFFFF8 R4 = 0x00000000 R10 = 0x00000000 CPSR = 0x00000000 R5 = 0x00000000 R11 = 0x00000000 Open serial port...OK Connecting to the RIFF Box...OK Firmware Version: 1.26, JTAG Manager Version: 1.35 Selected Resurrector: [HTC Desire S] Connecting to the dead body...OK Set I/O Voltage reads as 2.59V, TCK Frequency is RTCK Model selected: HTC - HTC Desire S Detected dead body ID: 0x17B360E1 Open serial port...OK Connecting to the RIFF Box...OK Firmware Version: 1.26, JTAG Manager Version: 1.35 Selected Resurrector: [HTC Desire S] Connecting to the dead body...OK Detected dead body ID: 0x17B360E1 - CORRECT! Set I/O Voltage reads as 2.59V, TCK Frequency is RTCK Adaptive Clocking RTCK Sampling is: [Sample at 8 MHz] Resurrection sequence started. Establish communication with the phone...OK Initializing internal hardware configuration...OK Uploading resurrector data into memory.. wait always no make any operation

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
news headlines to gsm phone	mos	Nokia Legacy Phones ( DCT-1 ,2 ,3 ,L )	7	05-22-2016 11:42
Help with 6110	paulomt1	Nokia Legacy Phones ( DCT-1 ,2 ,3 ,L )	2	05-25-2009 16:29
Netmonitor with FBus????	ratzfatz	Nokia Legacy Phones ( DCT-1 ,2 ,3 ,L )	4	06-09-1999 17:04

09-12-2011, 16:34	#3 (permalink)
domestik Freak Poster Join Date: Sep 2003 Location: The land of rape and honey Age: 46 Posts: 416 Member: 40118 Status: Offline Thanks Meter: 97	same problem for me. Need help, riff team

09-12-2011, 17:18	#4 (permalink)
legija Product Manager Join Date: Apr 2006 Age: 55 Posts: 5,746 Member: 256342 Status: Offline Sonork: None Thanks Meter: 28,276	1. Make sure to have all pins soldered properly, 2. Make sure to have stable power source for phone Most of errors with Desire S come out off bad soldering, or even some people don't solder GND.

09-12-2011, 18:23	#5 (permalink)
domestik Freak Poster Join Date: Sep 2003 Location: The land of rape and honey Age: 46 Posts: 416 Member: 40118 Status: Offline Thanks Meter: 97	I've tried on 4 or 5 pieces, it is not bad soldering. All of my Saga with the problem described here: [solved]BRICKed: inside eMMC's dead, with E:Can't open /cache/recovery/log - xda-developers main question is: can we repair it? or there is hardware malfunction of eMMC chip

09-12-2011, 21:36	#6 (permalink)
legija Product Manager Join Date: Apr 2006 Age: 55 Posts: 5,746 Member: 256342 Status: Offline Sonork: None Thanks Meter: 28,276	eMMC doesn't support bad blocks handling, hence once it gets partially damaged, it has to be replaced. Problem is, even if You replace it with blank chip, it would be impossible to boot it via JTAG since JTAG is enabled by FSBL. Blank eMMC - no FSBL, no JTAG. Dead loop. There is, though, some possibility to be explored, but not before two weeks from today. Our coder is on holidays now.

09-14-2011, 16:10	#8 (permalink)
BesTCooL No Life Poster Join Date: Dec 2002 Location: TURKEY Age: 44 Posts: 3,285 Member: 18442 Status: Offline Sonork: 111110 Thanks Meter: 622	Flashing the dead body... ERROR: DCC Loader has reported Error Code = 0x35 (0x000000). Trying to recover...FAILED ERROR: Failed due to multiple communication errors. Terminating at 0x000008D200

09-30-2011, 17:28	#14 (permalink)
an144 Junior Member Join Date: Mar 2005 Age: 50 Posts: 22 Member: 125913 Status: Offline Thanks Meter: 12	I have exactly the same problem. when the solution?