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

Help M8 Stuck in a Bootloop

EarlyMon said:
Please cite cases where you've personally seen that work on any HTCs.


I'm not as much in the mood to argue as I am looking forward to a private message explaining why you have two accounts here - we can merge those for you.
Click to expand...

I have tried to send a pm. I'm not sure how as i have posted very little on this forum. I clicked on your forum name and the best i see is start a conversation. If i have two accounts please merge them. One may have been from way back when, not sure.
 
EarlyMon said:
:(

Well, charge as is then.

:(
Click to expand...
EarlyMon said:
Welcome, sorry for woes.

First step - remove the sim and sd cards - hold volume up and power - it will force a power reset. Try to boot up after that.

I'm already 99% sure that won't work but let's hope for that 1%.

Failing that, power off, go ahead and put your sim and sd card back in.

Get the Mini-SDK if you don't already have fastboot on your pc -

http://androidforums.com/threads/adb-guide-updated-2014-11-11.443072/#post-5389081

Ignore the part about needing drivers for now.

Unzip the sdk-tools.zip file to get the sdk-tools folder. Windows Explorer, shift + right click the sdk-tools folder, choose Open command window here.

Power off phone. Hold volume down while powering on, follow on screen prompts so it says FASTBOOT at the top, FASTBOOT USB mode when plugged in to the pc.

In command window say -

fastboot getvar all

Alt+space to get command window menu, E for edit, select all, copy and paste into your reply here.

Be sure to remove the meid and serial numbers, those are private.
Click to expand...


Hey EarlyMon, I'm in a near identical situation as mkgino, I've gotten to this point with the sdk-tools, any help? I'm also going to take this in to Tmobile for a replacement but I'm hoping to save the 4k+ photos off the device.

C:\Users\\Desktop\sdk-tools\sdk-tools>fastboot getvar all
(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: 4.20.531.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid:
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B13000
(bootloader) cidnum: T-MOB010
(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: 06f11f5b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.525s

Any help?
 
mollycameron said:
Hey EarlyMon, I'm in a near identical situation as mkgino, I've gotten to this point with the sdk-tools, any help? I'm also going to take this in to Tmobile for a replacement but I'm hoping to save the 4k+ photos off the device.

C:\Users\\Desktop\sdk-tools\sdk-tools>fastboot getvar all
(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: 4.20.531.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid:
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B13000
(bootloader) cidnum: T-MOB010
(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: 06f11f5b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.525s

Any help?
Click to expand...
This is not good.

The fact that the radio firmware can't be identified means that the storage partition information is very likely corrupt.

You can probably fix that by flashing the right RUU but that's going to erase the entire phone and start over.

It looks like you never unlocked it or tinkered with it.

Is that correct or am I not reading that right? (It's been one of those days for me sorry.)
 
EarlyMon said:
This is not good.

The fact that the radio firmware can't be identified means that the storage partition information is very likely corrupt.

You can probably fix that by flashing the right RUU but that's going to erase the entire phone and start over.

It looks like you never unlocked it or tinkered with it.

Is that correct or am I not reading that right? (It's been one of those days for me sorry.)
Click to expand...

You are right. Stock from tmobile. I've never modified it.
 
mollycameron said:
You are right. Stock from tmobile. I've never modified it.
Click to expand...
My advice is that you're stuck losing the pictures. :(

You can flail around, try to unlock it and install recovery and try to get to the internal storage.

I never advise that.

With a corrupted partition table, you have far, far less than a 1% chance for success and nearly 100% chance that you'll never have any sympathy from your local service again - they'll be convinced that you broke it if you leave any tamper markers - and it's designed so you will get those markers if you try anything.

Sorry. :(
 
Hey EarlyMon,

I'm hoping you can help me but I'm assuming I too am a lost cause. My phone, similar to mkgino, was sitting beside me and restarted on its own and then became stuck on the same screen with the exceptions noted in bold below:

***Software Status Official***
***LOCKED***
M8_WLV PVT SHIP S-ON
HBOOT-3.19.0.0000
RADIO-INVALID_VER_INFO
OpenDSP-INVALID_VER_INFO
OS-4.17.605.9
eMMC-boot 2048MB
Aug 11 2015, 22:31:04.0

FASTBOOT
<VOL UP> to previous item
<VOL DOWN> to next item
<POWER> to select item

HBOOT
RAMDUMP
REBOOT
REBOOT FASTBOOT
POWER DOWN

When I try to reboot or hardboot, this screen returns. I initially took mine to Verizon and they informed me it was because the power button was stuck but I am still able to press it so I am not sure that is the case. My phone is a Verizon stock phone and has not been unlocked or manipulated in any form.

I was debating trying the sdk tools and have downloaded but because I am not phone/technologically savvy, I questioned whether the "RADIO-INVALID_VER_INFO" in addition to the "OpenDSP-INVALID_VER_INFO" made my situation different. My ultimate goal would be to recover pictures.

Hope you can help!
 
Mornin' EarlyMon,

Just stumbled onto this site. Yesterday I encountered the same problem. As with others, my device was laying on my desk and it happened. I have the same screen information as PaulaM. I took it back to my carrier (Verizon) yesterday. They had no clue; to resolve, they are sending me a replacement. Looking at your earlier responses, I'm resigned to the fact that all is lost. So my questions is: What caused this and are there any preventative measures I can take?
Thanks
The II
 
EarlyMon said:
This is not good.

The fact that the radio firmware can't be identified means that the storage partition information is very likely corrupt.

You can probably fix that by flashing the right RUU but that's going to erase the entire phone and start over.

It looks like you never unlocked it or tinkered with it.

Is that correct or am I not reading that right? (It's been one of those days for me sorry.)
Click to expand...
 
Hey EarlyMon, I got the same problem as mkgino in the first post, I've gotten to this point with the sdk-tools, any help? I'm in Germany and i have no idea how to save this Phone of mine.

C:\Users\PappyLuv>fastboot getvar all
< waiting for any device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.214500021.06G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.16.401.13
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(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: f063fb42
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.186s
C:\Users\PappyLuv>
 
@PappyLuv Do you mean you're stuck in a bootloop? Any idea what happened to put the phone in this state? What have you tried to do so far eg vol up + power to force a re-start?

If all else fails then you're in luck as you have a WWE CID number so I can point you to a signed RUU zip file that should get you sorted. Be warned though that if you resort to this it will wipe your phone including the internal storage.
 
saltire said:
If all else fails link to a previous post of mine with what you need to download and steps to do it:

HTC One M8 stuck in recovery mode

Note that this will also upgrade the phone's firmware and OS to Android 6.0 (Marshmallow).
Click to expand...

heyy thnx a lot @saltire so far, i think i messed up a bit... i have installed all tho adb and sdk drivers...i thought when i factory reset in bootload it will restore to factory but i guess i erased everything and it can't even even restore... i tried using some customed ruu from xda developers but my phone can just not flash, i have no idea why...maybe i'm using the wrong ruu for my phone or i got a wrong firware version,, and i keep getting this error: adb server is out of date ***killing*** anytime i try to flash it just can't find a bootable image and keep failing, i hope you still can help out.
 
Last edited:
Are you trying to use the RUU from the download link on the xda site that my post above links to? If so you don't do anything with the zip, either flash it via htc_fastboot with the phone in 'oem rebootRUU' mode, or use the sd card method. Both will work successfully, and will work for your phone - you have the correct modelid and the CID is for WWE firmware.

Since your phone is S-ON you can't just run any RUU, you need a signed (completely unmodified) RUU that matches your phone modelid and CID exactly.

Edit: If the adb server doesn't stop and re-start itself when trying fastboot commands, then try:

adb kill-server

then try the fastboot commands again.
 
@saltire Well I followed your post on the thread you sent me and did the following: First I downloaded the htc_fastboot.exe and placed it in the platform-tools folder and also did the same to the ruu I downloaded from the link you sent me. Then I started cmd from the same folder and activated my phone into fastboot mode by pressing the power and volume down button. Connected to the PC and in cmd "fastboot oem rebootRUU" sent the phone to the state where the htc icon comes with the black background without any green bar below. I already renamed the ruu file I downloaded to RUU, I entered in cmd "fastboot flash zip RUU.zip" but I got the error "cannot load RUU.zip". I don't know if you get the steps I used in flashing but if you do, you think I'm doing something wrong? Also, when I enter adb kill-server, I get the message "server not running".
 
Ok, did you downlaod and save the RUU file in the same folder where you have the fastboot tools? When you renamed the RUU file, in Windows Explorer do you have the option to "hide know file extensions" switched off? You need to check you haven't renamed the file as RUU.zip.zip as that won't work.

You may also need to use the htc_fastboot tool to do the flash zip command.

As noted if the fastboot method isn't working you can use the sd card method instead. Just remember to delete the zip file off the card once the phone has updated and booted successfully - otherwise the next time you go in to HBOOT mode it will go through the whole wipe/install process again.
 
You must log in or register to reply here.
Back
Top Bottom