• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Help HTC One M8 stuck in recovery mode

Yep it does, that's why I linked you to post #36. Just follow the steps, and you should be sorted.
 
Okay. I've been looking at this post for about 4 hours now, trying to fix my HTC that's stuck in a bootloop. After getting to the whole adb steps, I get a message in the CMD window saying"< waiting for device >", and I don't know what to do. I've tried updating my HTC Sync drivers, uninstalling them, removing my SD card any my SIM, and clearing /cache and /data over and over and over. It WAS working with abd, and I got it to reboot to RUU with "fastboot oem rebootRUU", and I realised that I needed some other files (the RUU.zip thing), so I held the power off button. I accidentally downloaded HTC's .exe program (It's called RUU_M8_UL_M60_SENSE70_ATT_MR_Cingular_US_6.20.502.5_combined.exe) and now NOTHING will work. I don't know what to do, and I'm having a small heart attack right now (yay me). Anyone know what I can do?
 
NeoHD said:
Okay. I've been looking at this post for about 4 hours now, trying to fix my HTC that's stuck in a bootloop. After getting to the whole adb steps, I get a message in the CMD window saying"< waiting for device >", and I don't know what to do. I've tried updating my HTC Sync drivers, uninstalling them, removing my SD card any my SIM, and clearing /cache and /data over and over and over. It WAS working with abd, and I got it to reboot to RUU with "fastboot oem rebootRUU", and I realised that I needed some other files (the RUU.zip thing), so I held the power off button. I accidentally downloaded HTC's .exe program (It's called RUU_M8_UL_M60_SENSE70_ATT_MR_Cingular_US_6.20.502.5_combined.exe) and now NOTHING will work. I don't know what to do, and I'm having a small heart attack right now (yay me). Anyone know what I can do?
Click to expand...


Fixed it, just gotta update my PC's drivers.
 
@saltire

hey, thanks for all your help on this forum. my htc is in the same place as these other guys, I tried your instructions on post 36 and got this back after writing "htc_fastboot flash zip ruu.zip"

writing 'ZIP'...(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
FAIL12 Signature verify fail
FAILED (remote: 12 signature verify fail)
Execution time is 8(s)

Im not sure what to do :S


and just so you know, might getvar all is:

(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.0.u20410.1@50408
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.12.401.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8q_ul
(bootloader) platform: hTCBmsm8939
(bootloader) modelid: 0PKV10000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 7900fbfd
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0


Any help you could give me would be massively appreciated.

edit: hi i've been looking around and the problem might be the fact that i have a htc m8s not a htc m8. Do you know what to do differently? I've tried looking through some forums but couldnt find anything i could understand :/ any guidance would be really appreciated.
 
Last edited:
saltire said:
I have an HTC desire eye and was downloading the latest android update(not sure which one) then all of a sudden an inverted triangle with a red exclamation mark popped up on the screen. Now the phone is stuck in a bit of a boot loop fluctuating between the exclamation and the HTC powered by android screen. The bootloader shows this :

**software status: official**
**Locked **
EYE_TUHL XC SHIP S-OFF
CID-11111111
HBOOT-3.19.0.000
RADIO-1.23.213311711.05G
OpenDSP-v46.2.2-00564-M8974.0811
Os-1.17.707.9
eMMC-boot 2048MB
Nov 6 2014,18:27:44.0

I've tried clearing the partition cache, restoring to factory settings, ramdump, basically everything and my phone still hasn't been able to escape the bootloop.
The recovery screen shows this(right at the bottom):

Device_CW_Install : No CW files. Skip CW Installation.
Write host_mode : 0 done
Click to expand...
 
I am having very similar problem. I am in no rush though as I was due for an upgrade, so just got myself a new HTC 10 and left this one sitting till now.

After my failed OTA update, it seems even my bootloader got trashed. I have only these options (reboot, reboot to bootloader, boot to download mode, boot to recovery mode, power down)
  • 'Reboot' and 'Reboot to bootloader' seem to do the same thing, just bring me back to bootloader
  • 'Boot to download mode' fails and takes me back to bootloader
  • 'Boot to Recovery mode' also fails and takes me back to bootloader
  • I don't have any fastboot option available
running a 'fastboot getvar all' only returns me this:
(bootloader) version:0.5
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x14000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5e0000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x118000000
(bootloader) serialno:HT566SV01766
all:
finished. total time: 0.142s

my software status: Official
LOCKED
S-ON

I don't mind at all though wiping everything, just want to get this phone working as toy for the kids to play on.

Any help is greatly appreciated.
 
Last edited:
Zelp said:
I am having very similar problem. I am in no rush though as I was due for an upgrade, so just got myself a new M9 and left this one sitting till now.

After my failed OTA update, it seems even my bootloader got trashed. I have only these options (reboot, reboot to bootloader, boot to download mode, boot to recovery mode, power down)
  • 'Reboot' and 'Reboot to bootloader' seem to do the same thing, just bring me back to bootloader
  • 'Boot to download mode' fails and takes me back to bootloader
  • 'Boot to Recovery mode' also fails and takes me back to bootloader
  • I don't have any fastboot option available
running a 'fastboot getvar all' only returns me this:
(bootloader) version:0.5
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x14000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5e0000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x118000000
(bootloader) serialno:HT566SV01766
all:
finished. total time: 0.142s

my software status: Official
LOCKED
S-ON

I don't mind at all though wiping everything, just want to get this phone working as toy for the kids to play on.

Any help is greatly appreciated.
Click to expand...

sorry, just realized this is actually happening on my htc one m9, not m8
 
Did you not get "cidnum" from the getvar all?

If it still responds to fastboot it may be possible to reflash it, but we'll need to know your cidnum, or else what country and whether unlocked or sold through a carrier (and if so, which), and some idea of the software version, in order to find an RUU that will work for your phone.
 
I'm running into a bootloop as well. It's my daughter's phone. It happened overnight. She's not interested in ROMs or anything, I don't think it's been messed with
Carrier is Sprint.
Is this right for the RUU linked in this thread?


(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: INVALID_VER_INFO
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.20.654.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:*************
(bootloader) imei: **************
(bootloader) imei2: Not Support
(bootloader) meid: **************
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B70000
(bootloader) cidnum: SPCS_004
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 205bdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.022s


EDIT: I see that my phone is m8_whl so this ruu will not work, but with the right ruu i'm assuming the method stays the same. correct?
 
Last edited:
Yes, method is same with right RUU. In your case that means a Sprint RUU with at least as recent a software version as the phone currently has.
 
I've tried this a few times without success.
Could it be that I'm having trouble because of " (bootloader) version-misc: PVT SHIP S-ON"?

When I try to use the fastboot method the oem rebootRUU command returns this error

C:\Android\platform-tools>fastboot oem rebootRUU
...
(bootloader) Error: Command never completed
(bootloader) Error: Command timeout error
(bootloader) Error: Command completed with errors
(bootloader) Failed Reading block @ 786432
(bootloader) [SD_ERR] sd_read_sector: read sector failed (786432 256)
(bootloader) [ERR] partition_read_emmc(589): error -1
(bootloader) Start Verify: 3
(bootloader) Error: Command never completed
(bootloader) Error: Command timeout error
(bootloader) Error: Command completed with errors
(bootloader) Failed Writing block @ 786432
(bootloader) [SD_ERR] sd_write_sector: write sector failed (786432 256)
OKAY [ 10.079s]
finished. total time: 10.081s


When I try the SDcard method the device returns a quick error message on the screen that says something like
No Gift File
No Image

Any insight here?
 
Hello,

This thread seems to be what I am looking for. A co-worker gave me an HTC One M8 and asked if I could fix it, everyone told him it was FUBAR. The phone is stuck on the HTC start up screen which started to happen after the phone did not take a full update, pooped the bed half way through. Here is my data after the "getvar all":

(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.23.213311491.A13G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.04.1700.10
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: **************
(bootloader) imei: *****************
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: eee2521c
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

Looking to see what RUU or what not I need to install. Not sure what ones are correct for this phone, not worried about any data either.

On a side note, could I put the Google Play Edition software on the phone.

Thanks a ton for any info.
 
Last edited:
Chainout said:
I've tried this a few times without success.
Could it be that I'm having trouble because of " (bootloader) version-misc: PVT SHIP S-ON"?
Click to expand...
No, that is completely normal.
When I try to use the fastboot method the oem rebootRUU command returns this error

C:\Android\platform-tools>fastboot oem rebootRUU
...
(bootloader) Error: Command never completed
(bootloader) Error: Command timeout error
(bootloader) Error: Command completed with errors
(bootloader) Failed Reading block @ 786432
(bootloader) [SD_ERR] sd_read_sector: read sector failed (786432 256)
(bootloader) [ERR] partition_read_emmc(589): error -1
(bootloader) Start Verify: 3
(bootloader) Error: Command never completed
(bootloader) Error: Command timeout error
(bootloader) Error: Command completed with errors
(bootloader) Failed Writing block @ 786432
(bootloader) [SD_ERR] sd_write_sector: write sector failed (786432 256)
OKAY [ 10.079s]
finished. total time: 10.081s
Click to expand...
You are getting errors like that just from rebootRUU, not even flashing anything? That doesn't sound good to me. I fear you may have memory errors.

You could try "fastboot oem task 28", which will reformat the user data partition. If the problem is in system then you would need to be S-Off for the corresponding command to work.

When I try the SDcard method the device returns a quick error message on the screen that says something like
No Gift File
No Image
Click to expand...
Can you give the exact output, rather than "something like"? It sounds like it's not finding the file, but hard to be certain with partial information.
 
Fakker said:
Hello,

This thread seems to be what I am looking for. A co-worker gave me an HTC One M8 and asked if I could fix it, everyone told him it was FUBAR. The phone is stuck on the HTC start up screen which started to happen after the phone did not take a full update, pooped the bed half way through. Here is my data after the "getvar all":

(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.23.213311491.A13G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.04.1700.10
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: **************
(bootloader) imei: *****************
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: eee2521c
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

Looking to see what RUU or what not I need to install. Not sure what ones are correct for this phone, not worried about any data either.

On a side note, could I put the Google Play Edition software on the phone.

Thanks a ton for any info.
Click to expand...
That seems to be an AT&T M8. It has been modified by the owner (it's S-Off and has had the cidnum altered), whether anything they did is the reason the update failed I could only speculate. Funny that someone who makes such modification should not know what to do.

Good that you are not worried about the data, because they are probably gone ;).

I think someone probably has already tried putting GPE firmware on this. It would be very helpful to know the history of this device, e.g. whether they had successfully run GPE firmware on it, and how exactly it got into this state.

Assuming that it was running GPE firmware before this happened, then you could try a GPE RUU. I think that this one, in zip format, corresponds to the software you have one it currently: https://www.androidfilehost.com/?w=files&flid=41674. I found that by following links in the first post of this XDA thread, which describes converting a phone to GPE: https://forum.xda-developers.com/showthread.php?t=2708589.

If you wanted to try a stock M8 Sense ROM then this is the most recent ATT RUU I can see on AndroidRUU.com: RUU_M8_UL_L50_SENSE60_ATT_MR_Cingular_US_4.28.502.1_Radio_4.0.U605611_50319A_40.45.C33065.00_F_release_426617_signed_2.exe
 
You must log in or register to reply here.
Back
Top Bottom