Develop Bugs

[Q] Broken recovery HTC M8 (Devil's Loop)

Hei guys I managed to **** up my HTC M8 pretty bad (I think..)
I had a rooted M8 with 4.4.4 so 5.0.2 came out a few days ago and I tried to update my phone today. To do so I wanted to unroot my phone so I did the following things:
1. I did a factory reset using the option in Clockworkmod
2. I flashed the stock recovery to my phone
3. I (re)locked my bootloader
The problem is something seems to be wrong with the flashed recovery, Factory Resetting or booting into recovery just restarts the phone and the OTA also just reboots the phone. Unlocking the bootloader and CHECK SMARTSD also won't work anymore..
I really don't know what to do now/where to ask for help..
Here is some information I can provide:
Bootloader looks like this:
*** Software status: Modified ***
*** Relocked ***
M8_UL PVT SHIP S-ON
HBOOT-3.19.0.000
RADIO-1.22.21331147A1.29G
OpenDSP-v46.2.2-00564-M8974_F0.0811
OS-3.28.401.9
eMMC-boot 2048MB
Getvar All (Toolkit) gives me this:
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.22.21331147A1.2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.28.401.9
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT46PWM01039
(bootloader) imei: 357871053519784
(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: df77f8b7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.010s
I really don't know hat to do now..
Hope you can help me, thanks for reading.

Unrooting and relocking the bootloader was a useless move. OTA accepts rooted phones and with bootloader unlocked. OTA needs a stock recovery and a clean system.
What you can do is flash via adb TWRP and restore a working backup of your firmware.
P.S. Delete your IMEI and SERIAL NUMBER from your post.

Bricked to the Max... (Maybe)

Prologue:
So there I was, caressing my shiny and smooth M8.
At the beginning of the year I S-Offed, and added DigitalHigh's awesome Beyond Stock...
Later on, I used a standard RUU GPE Rom.
After repeated Wi-Fi password amnesia, I wanted Beyond Stock Back.
Flashing "GPE_5.1_M8_DH_080215.zip" gives me an "Error 7" even with repeated wipes... hehe... wipes
Searching didn't give me a coherent answer.
So I though, let's update TWRP... and...
Now
The thing's only usable in Bootloader.
If I go to recovery or ANYTHING, the "Google" logo stares at me in disgust.
Odd detail: I'm using fastboot and when it's stuck on the "Google" logo, entering "adb devices" detects the phone in recovery mode.
I flashed TWRP 2.8.7.0, but all I see is the "Google" logo. (I can still feel vibrations on the screen as if I'm hitting a menu button)
I also tried to "fastboot -w" and it gave me the "remote: not allowed" result.
Actually, I tried to fastboot a lot of things and the result came the same.
Anyways, I'll give a detailed log as soon as I remember how, but the reason I post this is 'cause searching for this doesn't give an understandable or reliable result.
Thanks
C:\WINDOWS\system32>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.14.21331931.LA02_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.11.1700.5
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(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: 6e0f5a3d
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.057s

Give the output of :
Fastboot getvar all
But delete the serial and imei before posting ! If you have an old bootloader you have to use the 2.7 series of TWRP. if you have the latest bootloader (3.18-3.19) you have to use 2.8 series of TWRP !

OOOOOOOOOHHHH, Where I get new M8 bootloader?
Hold Up, going to work, will post 'getvar' later today.

It's there, brah.
Take a look if you can.

It's an AT&T device, you are using it with AT&T ? And you fully converted it from sense to GPE ? You could also :
1: run the GPE ruu again. It will get you on GPE stock again and since you are s-off that should not be a problem of any kind.
2: convert back to sense (original AT&T with software number x.xx.502.x)
i am not sure if the AT&T RUU will cover the "back to sense conversion" so this might be interesting too as it involves the standalone flashing of the firmware first (you need a AT&T firmware, NOT the one posted there !!!)
here is more conversion info :http://forum.xda-developers.com/showthread.php?t=2733523
and here you can get firmwares : http://forum.xda-developers.com/showthread.php?t=2701376
if you want number 2 here is more info with a download link to the latest android L RUU : http://www.theandroidsoul.com/download-att-htc-one-m8-lollipop-ruu-4-28-502-1-75822/

Didnt want to start my own thread due to the shame..
Hi,,
I have managed to remove my OS, without making a backup. All i have running is TWRP. Was going to install CM12.1, but didnt update the M8 to the latest software that contains relevant bootloader. From here it went downhill - fast.
Ended up with no OS, no backkups, and no ability to flash other ROMS i think.
If someone could give me a few ideas, i would really appreciate it.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.15.2133156.UA13G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: XXXXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXX
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__203
(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: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Mike

Sheriff1972 said:
Hi,,
I have managed to remove my OS, without making a backup. All i have running is TWRP. Was going to install CM12.1, but didnt update the M8 to the latest software that contains relevant bootloader. From here it went downhill - fast.
Ended up with no OS, no backkups, and no ability to flash other ROMS i think.
If someone could give me a few ideas, i would really appreciate it.
Click to expand...
Click to collapse
Your case is different and you should start your own thread but there are many same case as yours.
Here is one and the solution is in there.. run RUU - http://forum.xda-developers.com/htc-one-m8/help/os-sos-t3192177
Anything you're not sure, ask there. Don't hijack this thread.

UPDATE: Thanks to ckpv5 and the links that were provided i was able to complete the reinstall - thank you so much!!
Opps - sorry - didnt mean to offend!
Will take a look.
Thanks
Mike

The RUU got me an OS and, right now, that is all I need.
Thank you!!

Bootloop on stock!

I have no idea what's happened but all of a sudden my phone stopped booting up, from having looked around the relevant information seems to be the bootloader screen and "fastboot getvar all" so I've included those below. Does anyone know what's going on?
Bootloader Screen:
***Software status: Official***
***Locked***
M8_UL_CA PVT SHIP S-ON
HBOOT-3.19.0.0000
RADIO-1.25.214500021.06G
OpenDSP-v48.2.2-00564-M8974_F0.1211
OS-4.16.401.13
eMMC-boot 2048MB
Aug 4 2015, 19:21:49.3
fastboot getvar all:
(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_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: 11111111
(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.055s
I removed the IMEI but nnot he MEID because the fact that it's all zero's may be relevant.
Another thing was from what I read the model ID seems to be European but the bootloader model seems to be telling me that it's a US phone. I bought the phone online so that may be relevant. I could be entirely wrong though! I'm from the UK if that's relevant?

kelechi96 said:
I removed the IMEI but nnot he MEID because the fact that it's all zero's may be relevant.
Click to expand...
Click to collapse
You should also remove the serial number.
kelechi96 said:
Another thing was from what I read the model ID seems to be European but the bootloader model seems to be telling me that it's a US phone. I bought the phone online so that may be relevant. I could be entirely wrong though! I'm from the UK if that's relevant?
Click to expand...
Click to collapse
I agree, it looks like AT&T or Dev Edition that was "converted" by previous owner to be Euro (401).
I'd suggest finding the signed 4.16.401 RUU and try running it, to see if if fixes your bootloop. Any user data will be lost when you RUU.

[Help] My HTC one M8 has no OS.

I may have been an idiot and managed to remove the OS from my phone, and cannot for the life of me figure out how to get it back to working order.
The bootloader screen displays the following
*** Software status: Modified ***
*** UNLOCKED ***
M8_UL_CA PVT SHIP S-ON
HBOOT-3.19.0.0000
RADIO-1.29.214500021.24_2G
OpenDSP-v51.2.2-00593-M8974_FO.1015
OS-
eMMC-boot 2048MB
Nov 27 2015,01:21:29.0
fastboot getval all returns
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.24_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: REDACTED
(bootloader) imei: REDACTED
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: BS_US001
(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: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
And I have TWRP v2.7.0.2 on recovery.
I am at my wits end on this, so any help would be greatly appreciated.

Since it appears you are using the US unlocked version, why not use the Windows RUU to restore it? I don't have the link handy, but you can download it from HTC. Just put your device into download mode and go. It will blow away your recovery, but that's easy enough to restore.

jshamlet said:
Since it appears you are using the US unlocked version, why not use the Windows RUU to restore it? I don't have the link handy, but you can download it from HTC. Just put your device into download mode and go. It will blow away your recovery, but that's easy enough to restore.
Click to expand...
Click to collapse
I forgot to mention I tried that, and it errored out near the end. I think I may have managed to fix it by loading the rom from Insert-coin onto an SD card, and mounted it and installed through TWRP.
Its currently optimizing apps, so I think I should be home free at this point.
I feel kinda dumb by asking for help then figuring it out myself not long after, but it happens sometimes.

Voidablemelon said:
I may have been an idiot and managed to remove the OS from my phone, and cannot for the life of me figure out how to get it back to working order.
The bootloader screen displays the following
*** Software status: Modified ***
*** UNLOCKED ***
M8_UL_CA PVT SHIP S-ON
HBOOT-3.19.0.0000
RADIO-1.29.214500021.24_2G
OpenDSP-v51.2.2-00593-M8974_FO.1015
OS-
eMMC-boot 2048MB
Nov 27 2015,01:21:29.0
fastboot getval all returns
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.24_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: REDACTED
(bootloader) imei: REDACTED
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: BS_US001
(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: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
And I have TWRP v2.7.0.2 on recovery.
I am at my wits end on this, so any help would be greatly appreciated.
Click to expand...
Click to collapse
Your "OS" and version-main are blank because there was a bug in the TWRP version you are using.
Update to TWRP v2.8.7.0 or newer, reflash your current firmware or update it if you haven't already, and your OS and version-main will show the version of firmware you are running again.

Voidablemelon said:
I forgot to mention I tried that, and it errored out near the end. I think I may have managed to fix it by loading the rom from Insert-coin onto an SD card, and mounted it and installed through TWRP.
Its currently optimizing apps, so I think I should be home free at this point.
I feel kinda dumb by asking for help then figuring it out myself not long after, but it happens sometimes.
Click to expand...
Click to collapse
Figuring out yourself is always better than anything else,don't you felt like Einstein or something when you did it yourself w/o any help?

Voidablemelon said:
I forgot to mention I tried that, and it errored out near the end.
Click to expand...
Click to collapse
If you tell us what RUU (exact file name) and the specific error number and error message, we can probably tell you why the RUU failed.
---------- Post added at 10:39 AM ---------- Previous post was at 10:25 AM ----------
Voidablemelon said:
I may have been an idiot and managed to remove the OS from my phone, and cannot for the life of me figure out how to get it back to working order.
Click to expand...
Click to collapse
Good job figuring it out yourself.
You're not an idiot (common mistake) but here are a few good rules to live by, when modding Android devices:
1) Always make a TWRP backup of your current ROM (and user data, if desired - but that's always a good idea too) and have it handy, so you can recover from such situations (no OS). That is one of the main functions an benefits of having TWRP, the ability to make backups and use them to recover.
If you have a TWRP backup, recovering from "no OS" is simply as booting into TWRP, and restoring the backup.
My typical recommendation, is to make a TWRP backup before root (so you have a backup of the "stock" unrooted ROM) and prior to every time you flash a new ROM, or flash other mods. That way, if any of those mods go wrong, you can still revert back to a "known good" configuration.
2) If you don't have a TWRP backup on hand, know how to flash a ROM to recover from "no OS" (now you know how!)
3) I'm guessing you wiped "system" in TWRP to cause no OS (this the most usual cause)? If so, be careful what you choose to wipe in the "Advanced" wipe options of TWRP. Don't wipe anything, if you don't know what it is, or what the result will be. You've probably already learned this lesson, to some extent.

Update Fails

Hi guys.
I need your help please!
I have read every page on this forum and still no further with the Stock update for HTC One M8s.
As far as i know, my modelid: 0PKV10000 and cidnum: ORANG001.
Therefore, i chose to download: 0PKVIMG_M8_QL_UL_L50_SENSE60_Orange_UK_1.11.61.2_R [email protected]_15.00_016_F_release_431629 _signed
Please correct me if the Stock/CID/MID is incorrect.
1. I downloaded the zip file according to my CID/MID from the following location:
> ruu.lalleman.net > HTC_M8S(QL_UL) > Firmware (Expert) > Firmware Crypted (Original HTC)
0PKVIMG_M8_QL_UL_L50_SENSE60_Orange_UK_1.11.61.2_R [email protected]_15.00_016_F_release_431629 _signed
2. I renamed the file name to 0PKVIMG.zip and then copied on to my formatted (FAT32 & exFAT) SD card.
3. I powered off my phone and inserted the SD card.
4. I then booted into Bootloader.
5. Fastboot AC was showing and HBOOT highlighted, I pressed Power button and it started reading the SD card.
I selected Vol Up for Yes to start Update process, and then everything on the screen was automatic.
I have taken 4 photos (attached) of the automatic update process. (excuse the poor quality photos due to light).
At the very end of the update process, you can see that the update has completely failed.
I read somewhere on the forum that within the zip file there is a rom file. Unfortunately the zip file does NOT contain the rom file. It only contains the following files:
android-info.txt
boot_signed.img
cache.img
dzdata_16g.hdr
dzdata_16g.img
dzdata_32g.hdr
dzdata_32g.img
Listed below is my Bootloader & getvar info:
*** Software status: Official ***
*** LOCKED ***
M8QL_UL PVT SHIP S-ON
HBOOT-3.19.0.000
RADIO-INVALID_VER_INFO
OS
eMMC-boot 2048MB
Aug 13 2015,21:18:08.0
(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:
(bootloader) version-misc: XA SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid:
(bootloader) product: m8ql_ul
(bootloader) platform: hTCBmsm8939
(bootloader) modelid: 0PKV1****
(bootloader) cidnum: ORANG001
(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: 42756eb7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
(bootloader) mfg-name:
all: Done!
finished. total time: 15.964s
Please let me know if i have done something incorrectly.
Where do i go from here?
Your help is greatly appreciated.

Any Progress?
Hey, I've come across the same issue.
I've got an HTC One M8s from the UK (Orange/EE).
My phone (out of the blue stopped) booting into the OS and just sits on a blank screen.
Did you find a fix for this problem?
If so, would you mind sharing the solution, please?
bashme said:
Hi guys.
I need your help please!
I have read every page on this forum and still no further with the Stock update for HTC One M8s.
As far as i know, my modelid: 0PKV10000 and cidnum: ORANG001.
Therefore, i chose to download: 0PKVIMG_M8_QL_UL_L50_SENSE60_Orange_UK_1.11.61.2_R [email protected]_15.00_016_F_release_431629 _signed
Please correct me if the Stock/CID/MID is incorrect.
1. I downloaded the zip file according to my CID/MID from the following location:
> ruu.lalleman.net > HTC_M8S(QL_UL) > Firmware (Expert) > Firmware Crypted (Original HTC)
0PKVIMG_M8_QL_UL_L50_SENSE60_Orange_UK_1.11.61.2_R [email protected]_15.00_016_F_release_431629 _signed
2. I renamed the file name to 0PKVIMG.zip and then copied on to my formatted (FAT32 & exFAT) SD card.
3. I powered off my phone and inserted the SD card.
4. I then booted into Bootloader.
5. Fastboot AC was showing and HBOOT highlighted, I pressed Power button and it started reading the SD card.
I selected Vol Up for Yes to start Update process, and then everything on the screen was automatic.
I have taken 4 photos (attached) of the automatic update process. (excuse the poor quality photos due to light).
At the very end of the update process, you can see that the update has completely failed.
I read somewhere on the forum that within the zip file there is a rom file. Unfortunately the zip file does NOT contain the rom file. It only contains the following files:
android-info.txt
boot_signed.img
cache.img
dzdata_16g.hdr
dzdata_16g.img
dzdata_32g.hdr
dzdata_32g.img
Listed below is my Bootloader & getvar info:
*** Software status: Official ***
*** LOCKED ***
M8QL_UL PVT SHIP S-ON
HBOOT-3.19.0.000
RADIO-INVALID_VER_INFO
OS
eMMC-boot 2048MB
Aug 13 2015,21:18:08.0
(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:
(bootloader) version-misc: XA SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid:
(bootloader) product: m8ql_ul
(bootloader) platform: hTCBmsm8939
(bootloader) modelid: 0PKV1****
(bootloader) cidnum: ORANG001
(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: 42756eb7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
(bootloader) mfg-name:
all: Done!
finished. total time: 15.964s
Please let me know if i have done something incorrectly.
Where do i go from here?
Your help is greatly appreciated.
Click to expand...
Click to collapse

thedjsean said:
Hey, I've come across the same issue.
I've got an HTC One M8s from the UK (Orange/EE).
My phone (out of the blue stopped) booting into the OS and just sits on a blank screen.
Click to expand...
Click to collapse
The OP tried to manually flash a zip that they downloaded themselves. Did you do that?
Also, you don't have the same version (region/carrier). So again, another difference, so it's not the "same" issue.
You should describe specifically what happened, not just say it's the "same issue". Since in every case (downs, maybe hundreds) I've seen folks say it's the "same issue", it never is exactly the same. Did it happen "out of the blue" or did it happen when trying to update (topic of the thread)? Conflicting info, makes it hard for anyone to help.
Also, please don't quote a whole wall of text, just to post a few sentences; which clutters up the thread. I know quting the previous post is default when responding. But simply delete what isn't directly relevant to your issue, before posting.