[Q] Can I just confirm my phone is stuffed?

col320ce · Feb 18, 2012

History:
Desire S rooted using "revolutionary-0.4pre4" but otherwise no changes (rooted many months ago).
Crashed during update of Apps (I pressed update all and it crashed it after a few minutes). Had to pull the battery out to reset. Crashed again after about 2 minutes so I pulled the battery again and now won't load past the HTC loading screen.
I assume something fried as I pulled the battery.
I have tried updating the ROM without success - just to confirm I am doing it properly I put the file onto the phone's normal SD card (eg "RunnymedeS-Saga-v6.zip"), start recovery mode, wipe data and cache and load from zip file.
It either finishes loading or says there is a problem with the zip file (I've tried 5 or so ROM files). on the times it managed to finish it resets and just gets stuck on the HTC load screen (like before).

In Recovery mode I have:
-Revolutionary-
SAGA PVT SHIP S-OFF RL
HBOOT-6.98.1002
RADIO-3805.06.02.03_M
eMMC-boot
Mar 10 2011,14:58:38

Is the phone stuffed or is there anything else I can try?

eyahl · Feb 18, 2012

col320ce said:
History:
Desire S rooted using "revolutionary-0.4pre4" but otherwise no changes (rooted many months ago).
Crashed during update of Apps (I pressed update all and it crashed it after a few minutes). Had to pull the battery out to reset. Crashed again after about 2 minutes so I pulled the battery again and now won't load past the HTC loading screen.
I assume something fried as I pulled the battery.
I have tried updating the ROM without success - just to confirm I am doing it properly I put the file onto the phone's normal SD card (eg "RunnymedeS-Saga-v6.zip"), start recovery mode, wipe data and cache and load from zip file.
It either finishes loading or says there is a problem with the zip file (I've tried 5 or so ROM files). on the times it managed to finish it resets and just gets stuck on the HTC load screen (like before).

In Recovery mode I have:
-Revolutionary-
SAGA PVT SHIP S-OFF RL
HBOOT-6.98.1002
RADIO-3805.06.02.03_M
eMMC-boot
Mar 10 2011,14:58:38

Is the phone stuffed or is there anything else I can try?

Ate you still able to boot into recovery?? Try full wiping your phone

Sent my thoughts to your head with XDA App

nenad_l · Feb 18, 2012

i'm no expert, but i'm pretty sure there is still bunch of options for you...

search trough forum, even try to install stock roms (ruu)

chin up!

col320ce · Feb 18, 2012

I have tried a full wipe but will try a .RUU file.
I can get into recovery and move about...

col320ce · Feb 19, 2012

Just tried installing from .RUU file using FASTBOOT USB and RUU from computer. And it won't get past the first screen - "Rebooting to bootloader.........."
After all I have done it still tells me I have Software version 1.47.832.1 installed.

enigmaamit · Feb 19, 2012

col320ce said:
History:
Desire S rooted using "revolutionary-0.4pre4" but otherwise no changes (rooted many months ago).
Crashed during update of Apps (I pressed update all and it crashed it after a few minutes). Had to pull the battery out to reset. Crashed again after about 2 minutes so I pulled the battery again and now won't load past the HTC loading screen.
I assume something fried as I pulled the battery.
I have tried updating the ROM without success - just to confirm I am doing it properly I put the file onto the phone's normal SD card (eg "RunnymedeS-Saga-v6.zip"), start recovery mode, wipe data and cache and load from zip file.
It either finishes loading or says there is a problem with the zip file (I've tried 5 or so ROM files). on the times it managed to finish it resets and just gets stuck on the HTC load screen (like before).

In Recovery mode I have:
-Revolutionary-
SAGA PVT SHIP S-OFF RL
HBOOT-6.98.1002
RADIO-3805.06.02.03_M
eMMC-boot
Mar 10 2011,14:58:38

Is the phone stuffed or is there anything else I can try?

Can you enter the custom recovery at all?

If so, do the following and post your result so first we can rule out an eMMC problem.

Set up adb (link in my sig) connect your device to the PC, enter recovery, open cmd (command prompt) on the PC and type:

adb shell
dmesg | grep mmc0

Source : Amidabuddha's excellent guide here : http://xdaforums.com/showthread.php?t=1284196

col320ce · Feb 19, 2012

I can enter recovery and I am on the screen with "HBOOT USB PLUG" when plugged into the PC.

I have set up the abd link but it cmd says "error: device not found"

I assume I have not installed adb correctly or am not in the correct part of the command prompt. Do I need to go to C:/android-tools/ then type adb shell or does it not matter?

When I type
adb shell
dmesg | grep mmc0
I assume I hit return after the first line?

How do I type the vertical line in the second line?

I have HTC Sync Installed
I have the folder at c drive root - c:\android-tools\
I have put a copy of the content of the folder into windows\sytem32
I can't see the phone in "my computer" when it is attached by USB.

???

col320ce · Feb 19, 2012

Just got it to work

C:\Documents and Settings\Person>adb shell
~ # dmesg | grep mmc0
dmesg | grep mmc0
<3>[ 8.471618] mmc0: No card detect facilities available
<6>[ 8.472259] mmc0: Qualcomm MSM SDCC at 0x00000000a0500000 irq 98,0 dma 7
<6>[ 8.472412] mmc0: Platform slot type: MMC
<6>[ 8.472625] mmc0: 4 bit data mode disabled
<6>[ 8.472747] mmc0: 8 bit data mode enabled
<6>[ 8.472991] mmc0: MMC clock 144000 -> 50000000 Hz, PCLK 96000000 Hz
<6>[ 8.473114] mmc0: Slot eject status = 0
<6>[ 8.473236] mmc0: Power save feature enable = 1
<6>[ 8.473480] mmc0: DM non-cached buffer at ffa0f000, dma_addr 0x0c1fa000
<6>[ 8.473602] mmc0: DM cmd busaddr 0x0c1fa000, cmdptr busaddr 0x0c1fa300
<6>[ 8.626892] mmc0: new high speed MMC card at address 0001
<6>[ 8.628082] mmcblk0: mmc0:0001 M4G2DE 2.10 GiB
<3>[ 9.837493] mmc0: Failed to get card ready i = 122109
<6>[ 9.837585] mmc0: reinit card
<4>[ 9.837707] mmc0: Starting deferred resume
<6>[ 11.879486] mmc0: Deferred resume failed
<3>[ 11.881774] mmc0: DMA channel flushed (0x80000004)
<6>[ 11.882141] mmc0: Controller has been reset
<6>[ 11.882324] mmc0: Worked around bug 1535304
<3>[ 11.883758] mmc0: DMA channel flushed (0x80000004)
<6>[ 11.884094] mmc0: Controller has been reset
<6>[ 11.884368] mmc0: Worked around bug 1535304
<6>[ 11.890960] mmc0: reinit card
<4>[ 11.891052] mmc0: Starting deferred resume
<6>[ 13.931549] mmc0: Deferred resume failed
~ #

I don't think this is a good sign.

thanks

enigmaamit · Feb 19, 2012

col320ce said:
I can enter recovery and I am on the screen with "HBOOT USB PLUG" when plugged into the PC.

???

There is a difference between being in the bootloader and Recovery.xCan you boot into recovery?

amidabuddha · Feb 19, 2012

col320ce said:
<3>[ 9.837493] mmc0: Failed to get card ready i = 122109
<6>[ 9.837585] mmc0: reinit card
<4>[ 9.837707] mmc0: Starting deferred resume
<6>[ 11.879486] mmc0: Deferred resume failed
<3>[ 11.881774] mmc0: DMA channel flushed (0x80000004)
<6>[ 11.882141] mmc0: Controller has been reset
<6>[ 11.882324] mmc0: Worked around bug 1535304
<3>[ 11.883758] mmc0: DMA channel flushed (0x80000004)
<6>[ 11.884094] mmc0: Controller has been reset
<6>[ 11.884368] mmc0: Worked around bug 1535304
<6>[ 11.890960] mmc0: reinit card
<4>[ 11.891052] mmc0: Starting deferred resume
<6>[ 13.931549] mmc0: Deferred resume failed
~ #

Sorry man.

col320ce said:
I assume something fried as I pulled the battery.

Another proof that this is a dangerous action on Desire S

enigmaamit · Feb 19, 2012

col320ce said:
Just got it to work

C:\Documents and Settings\Person>adb shell
~ # dmesg | grep mmc0
dmesg | grep mmc0
<3>[ 8.471618] mmc0: No card detect facilities available
<6>[ 8.472259] mmc0: Qualcomm MSM SDCC at 0x00000000a0500000 irq 98,0 dma 7
<6>[ 8.472412] mmc0: Platform slot type: MMC
<6>[ 8.472625] mmc0: 4 bit data mode disabled
<6>[ 8.472747] mmc0: 8 bit data mode enabled
<6>[ 8.472991] mmc0: MMC clock 144000 -> 50000000 Hz, PCLK 96000000 Hz
<6>[ 8.473114] mmc0: Slot eject status = 0
<6>[ 8.473236] mmc0: Power save feature enable = 1
<6>[ 8.473480] mmc0: DM non-cached buffer at ffa0f000, dma_addr 0x0c1fa000
<6>[ 8.473602] mmc0: DM cmd busaddr 0x0c1fa000, cmdptr busaddr 0x0c1fa300
<6>[ 8.626892] mmc0: new high speed MMC card at address 0001
<6>[ 8.628082] mmcblk0: mmc0:0001 M4G2DE 2.10 GiB
<3>[ 9.837493] mmc0: Failed to get card ready i = 122109
<6>[ 9.837585] mmc0: reinit card
<4>[ 9.837707] mmc0: Starting deferred resume
<6>[ 11.879486] mmc0: Deferred resume failed
<3>[ 11.881774] mmc0: DMA channel flushed (0x80000004)
<6>[ 11.882141] mmc0: Controller has been reset
<6>[ 11.882324] mmc0: Worked around bug 1535304
<3>[ 11.883758] mmc0: DMA channel flushed (0x80000004)
<6>[ 11.884094] mmc0: Controller has been reset
<6>[ 11.884368] mmc0: Worked around bug 1535304
<6>[ 11.890960] mmc0: reinit card
<4>[ 11.891052] mmc0: Starting deferred resume
<6>[ 13.931549] mmc0: Deferred resume failed
~ #

I don't think this is a good sign.

thanks

Ouch!

eMMC most likely dead. I'm real sorry man... wish there was anything further i could suggest....

You'll have to take it to the Service Centre, and hope for the best.

I still don't understand, that after all the warnings against pulling battery, why do so many users do it? It baffles me. Honest to God, i still have to figure that behavior out... It's like wanting to brick your phone.

gefilus · Feb 19, 2012

I usaly leave debugging on all the time. If it hangs 3 button combo or clear catches with adb and then restart it. Never pull battery out, if you don't have access to PC then leave it and do it later, better do it without risk. And you got faulty emmc before becouse it hanged on app upgrade. Sorry mate

Sent from my HTC Desire S using xda premium

incrediblealex · Feb 19, 2012

Is pulling the battery the only way to brick the m4g2de emmc chip or can it just happen on its own?

gefilus · Feb 19, 2012

incrediblealex said:
Is pulling the battery the only way to brick the m4g2de emmc chip or can it just happen on its own?

Here is a post about what can brick it. Many things can fry it. But still Never pull out battery

Sent from my HTC Desire S using xda premium

col320ce · Feb 19, 2012

I can enter bootloader but the computer can't find the phone unless I go into the RECOVERY (revolutionary CWM v4.0.1.4). I assume the text printout is still valid?
In bootloader (after vol down and on) I attach the USB and the screen says (amongst other things) HBOOT USB PLUG (from HBOOT).

C:\>adb shell
error: device not found

Unless anyone thinks the phone is not stuffed, can I brick it further to stop the HTC repair man seeing that it is S-OFF? I have tried to remove revolutionary and S-OFF but can't get anything to work.

incrediblealex · Feb 19, 2012

Not sure If you can brick it further since your emmc is where you write all of the files

Topics

Topics

[Q] Can I just confirm my phone is stuffed?

col320ce

Member

eyahl

Senior Member

nenad_l

Senior Member

col320ce

Member

col320ce

Member

enigmaamit

Senior Member

col320ce

Member

col320ce

Member

enigmaamit

Senior Member

amidabuddha

Senior Member

enigmaamit

Senior Member

gefilus

Senior Member

incrediblealex

Senior Member

gefilus

Senior Member

col320ce

Member

incrediblealex

Senior Member

Similar threads

New posts