1. Are you ready for the Galaxy S20? Here is everything we know so far!

M8 Stuck in a Bootloop

Discussion in 'Android Devices' started by mkgino, Jun 4, 2015.

  1. EarlyMon

    EarlyMon The PearlyMon
    VIP Member

    They'll be attempting to format everything - basically no.
     

    Advertisement

  2. James L

    James L Android Expert

    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 likes this.
  3. mollycameron

    mollycameron Lurker


    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?
     
  4. EarlyMon

    EarlyMon The PearlyMon
    VIP Member

    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.)
     
  5. mollycameron

    mollycameron Lurker

    You are right. Stock from tmobile. I've never modified it.
     
  6. EarlyMon

    EarlyMon The PearlyMon
    VIP Member

    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. :(
     
  7. PaulaM

    PaulaM Lurker

    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!
     
  8. BanunDuce

    BanunDuce Lurker

    Hey EarlyMon, How can I get my picture out of the phone before I reinstall the RUU
     
  9. I'm afraid I don't think you can. What would help next time, is that you could backup pictures onto a micro-sd card, or on your computer.
     
  10. The II

    The II Lurker

    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
     
  11. PappyLuv

    PappyLuv Lurker

     
  12. PappyLuv

    PappyLuv Lurker

    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>
     
  13. saltire

    saltire Android Expert

    @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.
     
  14. saltire

    saltire Android Expert

    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).
     
  15. PappyLuv

    PappyLuv Lurker

    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.
     
    #40 PappyLuv, Apr 25, 2016
    Last edited: Apr 25, 2016
  16. saltire

    saltire Android Expert

    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.
     
  17. PappyLuv

    PappyLuv Lurker

    @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".
     
  18. saltire

    saltire Android Expert

    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.
     

HTC One M8 Forum

The HTC One M8 release date was March 2014. Features and Specs include a 5.0" inch screen, 4MP camera, 2GB RAM, Snapdragon 801 processor, and 2600mAh battery.

March 2014
Release Date
0
Reviews
Loading...
Tags:

Share This Page

Loading...