Develop Bugs

[Q] HOX stuck in bootloop and cannot restore stock ROM

Hi,
I've using CM 11 for a while on my HOX. I didn't have the backup of my original ROM. I didn't think I'd need to sell the phone but I wanted to and I was told to restore the stock ROM back. I thought I got the correct RUU and when I tried to flash (after relocking bootloader and erasing cache), I was told by RUU GUI that there was a bootloader version problem. Reading about it, I found that my HBOOT version is 1.72.0000 and the RUU showed something like 1.29.
After reading further I found that I was downgrading the HBOOT and for that I need to have S-OFF (I have S-ON).
I then extracted the ROM.zip file from the RUU and tried to flash the system.img and boot_signed.img files and found myself in a situation where the phone goes into a boot loader loop.
The battery has been dead and I'm also plagued by the power management bug in HOX ( doesn't charge at all and had to leave it on for days). Luckily it started charging again but since the phone goes into a bootloader loop, the battery is dying.
I found the fastboot-battery-recharge on this forum where I'm trickle charging it.
Can you help me flash the original ROM back by identifying the correct RUU (android files. org)?
My phone details:
F:\HOX>fastboot getvar all
(bootloader) version: 0.5a
(bootloader) version-bootloader: 1.72.0000
(bootloader) version-baseband: 5.1204.164D3.31
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.17.161.3
(bootloader) serialno: XXXX
(bootloader) imei: XXXX
(bootloader) product: endeavoru
(bootloader) platform: HBOOT-T30S
(bootloader) modelid: PJ4610000
(bootloader) cidnum: VODAP001
(bootloader) battery-status: low
(bootloader) battery-voltage: 3547mV
(bootloader) devpower: 0
(bootloader) partition-layout: None
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: None
(bootloader) hbootpreupdate: 2
(bootloader) gencheckpt: 0
I downloaded this RUU: RUU_ENDEAVOR_U_JB_45_S_HTC_Europe_3.14.401.31_R_Radio_5.1204.162.29_release_302015_signed.exe
Would this work when the phone is charged?
Please assist as I want to sell the phone.
Thanks in advance guys.

The battery seems to have charged a little bit and I tried the RUU mentioned above, but it doesn't run fully. I get the initial messages to accept about battery being 30% etc, and then I'm shown the current image versoin 4.17.xxx and then the "Update" button. When I click it, the RUU just closes. I'm trying to download another RUU: RUU_ENDEAVOR_U_JB_45_S_HTC_Europe_3.14.401.27_Radio_5.1204.162.29_release_298897_signed.exe
In case there was something wrong with the ROM..

The flashing of the second RUU failed this time with error 158. Incorrect RUU. So I went ahead and unlocked bootloader again and CM is back working now thankfully. I still don't know how to flash it with stock ROM correctly. I'm reading about downloading some Nandroid backups 3.20.x versions and restoring it.
I don't want to risk anymore, so please let me know.
Standing by.........

corpuscallosum said:
The flashing of the second RUU failed this time with error 158. Incorrect RUU. So I went ahead and unlocked bootloader again and CM is back working now thankfully. I still don't know how to flash it with stock ROM correctly. I'm reading about downloading some Nandroid backups 3.20.x versions and restoring it.
I don't want to risk anymore, so please let me know.
Standing by.........
Click to expand...
Click to collapse
You will never succsses to flash RUU no RUU for this high main version restore nandroid or install custom rom on it

Ok thank you. That clarifies about RUU flashing. I have downloaded 3.14 (VODAP0001) Nandroid from one of pages of this site and follow the instructions to flash. Hopefully I'll get stock ROM back then.
Do I need to have the stock recovery also? Is stock recovery required for OTA and when factory reset on the stock ROM it would revert back to factory state (going through setup process again)?

corpuscallosum said:
Ok thank you. That clarifies about RUU flashing. I have downloaded 3.14 (VODAP0001) Nandroid from one of pages of this site and follow the instructions to flash. Hopefully I'll get stock ROM back then.
Do I need to have the stock recovery also? Is stock recovery required for OTA and when factory reset on the stock ROM it would revert back to factory state (going through setup process again)?
Click to expand...
Click to collapse
3.14 will not work you will have problem with the tuch will not work you need nandroid with your numbers. Yes stock recovery is need for OTA but you are with latest base I think

Ok. I think I'm having trouble identifying the correct versions then. I thought 3.14 is the bootloader version. Is that the baseband version then?
Since I have 5.1204, do I need to download a Nandroid 5.1204 version?

Can i get some help please unbricking mine i cant seem to find the correct ruu any where ive already relocked the bootloader and now ive been stuck with out a phone for 2 weeks
X:\Fastboot>fastboot getvar all
(bootloader) version: 0.5a
(bootloader) version-bootloader: 1.72.0000
(bootloader) version-baseband: 5.1204.164D3.31
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.17.161.3
(bootloader) serialno: SH25AW109670
(bootloader) imei: 354461055970384
(bootloader) product: endeavoru
(bootloader) platform: HBOOT-T30S
(bootloader) modelid: PJ4610000
(bootloader) cidnum: VODAP001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3793mV
(bootloader) devpower: 71
(bootloader) partition-layout: None
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: None
(bootloader) hbootpreupdate: 2
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 1.050s
this is all ive got id really apreciate any help

corpuscallosum said:
Ok. I think I'm having trouble identifying the correct versions then. I thought 3.14 is the bootloader version. Is that the baseband version then?
Since I have 5.1204, do I need to download a Nandroid 5.1204 version?
Click to expand...
Click to collapse
you need nand backup with this numbers 4.17.161.3 this with the red is important dont look your CID if you find nand with this numbers is the prfect like 4.18.401.4 this with the red is WWE region, in your case is 161 maybe this is Vodafone I don't know Germany or UK
---------- Post added at 11:34 PM ---------- Previous post was at 11:33 PM ----------
RayOneX said:
Can i get some help please unbricking mine i cant seem to find the correct ruu any where ive already relocked the bootloader and now ive been stuck with out a phone for 2 weeks
X:\Fastboot>fastboot getvar all
(bootloader) version: 0.5a
(bootloader) version-bootloader: 1.72.0000
(bootloader) version-baseband: 5.1204.164D3.31
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.17.161.3
(bootloader) serialno: SH25AW109670
(bootloader) imei: 354461055970384
(bootloader) product: endeavoru
(bootloader) platform: HBOOT-T30S
(bootloader) modelid: PJ4610000
(bootloader) cidnum: VODAP001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3793mV
(bootloader) devpower: 71
(bootloader) partition-layout: None
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: None
(bootloader) hbootpreupdate: 2
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 1.050s
this is all ive got id really apreciate any help
Click to expand...
Click to collapse
If you read the hole thread you will see no RUU for this main version and unlock your bootloader and flash recovery and then custom rom or nand backup with this numbers 4.17.161.3

Thant said:
you need nand backup with this numbers 4.17.161.3 this with the red is important dont look your CID if you find nand with this numbers is the prfect like 4.18.401.4 this with the red is WWE region, in your case is 161 maybe this is Vodafone I don't know Germany or UK
---------- Post added at 11:34 PM ---------- Previous post was at 11:33 PM ----------
If you read the hole thread you will see no RUU for this main version and unlock your bootloader and flash recovery and then custom rom or nand backup with this numbers 4.17.161.3
Click to expand...
Click to collapse
Can i please get help doing this with a step by step instruction list or even links please
---------- Post added at 05:38 PM ---------- Previous post was at 05:29 PM ----------
RayOneX said:
Can i please get help doing this with a step by step instruction list or even links please
Click to expand...
Click to collapse
Nandroid Backup 4.17.161.2 CID VODAP001 thanks to alextheg will this be okay its from this page http://forum.xda-developers.com/showthread.php?t=1975140

Thant, thanks. I guess 4.17.161.3 is for me. I'll see if there's a uk based VODAP001.
I will use this: 4.17.161.2 CID VODAP001. Will follow the steps mentioned where I got the Nand backup itself.

wohoo!! I got the 'stock' ROM back!! Thanks Thant! You're brilliant! I also copied the recovery.img from the Nand backup. Can I flash that with cmd: "fastboot flash recovery recovery.img"? Can I erase cache and relock bootloader to see if I get OTA? Is that the correct way forward?

corpuscallosum said:
wohoo!! I got the 'stock' ROM back!! Thanks Thant! You're brilliant! I also copied the recovery.img from the Nand backup. Can I flash that with cmd: "fastboot flash recovery recovery.img"? Can I erase cache and relock bootloader to see if I get OTA? Is that the correct way forward?
Click to expand...
Click to collapse
you need stock recovery not this in the backup search for stok recovery for your base or download OTA and choice install later then take the recovery from OTA and flash it

Fixed!! HOX stuck in bootloop and cannot restore ROM
Perfect! I choose install later when the OTA came up on the phone, connected it to my computer and navigated to the download folder on my phone. Found the file : "OTA_ENDEAVOR_U_JB_50_S_Vodafone_UK_4.17.161.3-4.17.161.2_release_369941".
Extracted recovery.img from the firmware.zip file within, copied to my computer, put the phone in fastboot mode and flashed the recovery using command: fastboot flash recovery recovery.img.
That was it. Rebooted the phone and installed the OTA without any issues!!
It back to factory state. Thanks a million Thant!!

corpuscallosum said:
Perfect! I choose install later when the OTA came up on the phone, connected it to my computer and navigated to the download folder on my phone. Found the file : "OTA_ENDEAVOR_U_JB_50_S_Vodafone_UK_4.17.161.3-4.17.161.2_release_369941".
Extracted recovery.img from the firmware.zip file within, copied to my computer, put the phone in fastboot mode and flashed the recovery using command: fastboot flash recovery recovery.img.
That was it. Rebooted the phone and installed the OTA without any issues!!
It back to factory state. Thanks a million Thant!!
Click to expand...
Click to collapse
Good to hear that

M8 only boots into fastboot

Hi guys, I need help bringing my phone back to life. I tried to return my phone back to stock by running a RUU. But now I've learnt (the hard way) it was the wrong RUU and now I can only boot into bootloader. There is no recovery I can boot into. This is the getvar:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.24.21331147A1.09G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT46KWM00547
(bootloader) imei: <REMOVED>
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B63000
(bootloader) cidnum: HTC__622
(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: 3aa067db
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I tried to find the correct HBOOT and CID version RUU but to no avail. I've tried another RUU for 0P6B but I think it was MID 0P6B1000 while mine is 0P6B3000. And most other solutions involve have S-OFF which mine isn't. I'm not sure what else I can do. Any help is greatly appreciated!

riceinbowl said:
I tried to find the correct HBOOT and CID version RUU but to no avail. I've tried another RUU for 0P6B but I think it was MID 0P6B1000 while mine is 0P6B3000. And most other solutions involve have S-OFF which mine isn't.
Click to expand...
Click to collapse
I think you want the RUU for 4.18.708.12, if such RUU exists. I don't know if it exists or not, but this at least give you a starting point to look (seems like you were somewhat guessing before).

redpoint73 said:
I think you want the RUU for 4.18.708.12, if such RUU exists. I don't know if it exists or not, but this at least give you a starting point to look (seems like you were somewhat guessing before).
Click to expand...
Click to collapse
Thanks for this! I will have a look around for this.

riceinbowl said:
Thanks for this! I will have a look around for this.
Click to expand...
Click to collapse
Don't think 4.18.708.12 RUU exists.
If your bootloader is unlocked ... you can install TWRP 2.8.7.0 then restore 4.18.708.12 stock non-rooted backup and install 4.18.708.12 stock recovery.img then do OTA to Marshmallow 6.16.708.1
Everything that you need and How-To : http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860

#4 is correct
boot into fastboot means that ur system got some problems
or even isnt exist
restore a TWRP backup or flash a stock rom will help

qscwdv65 said:
#4 is correct
boot into fastboot means that ur system got some problems
or even isnt exist
restore a TWRP backup or flash a stock rom will help
Click to expand...
Click to collapse
I agree, if there is no RUU for the version, than the way forward is to restore a stock TWRP backup. Unlocked bootloader is required.

M8 starting up in Fastboot, won't load installed ROM

I've stuffed something up along the way and now my M8 seems to refuse to load any ROM I've installed on it. What's the best way to go about fixing this? It's unlocked with S-Off.

Flashing an RUU is a silver bullet for starting over, as an RUU formats all your device's partitions and flashes them with stock images.
You'll need to provide CID & MID or your current firmware version (i.e. 4.16.401.10) if you need help locating a compatible RUU.
Cheers

Need some more details to see why the phone won't boot into OS after flashing a ROM.
Is an OS number indicated on the bootloader screen? If so, what is it?
What version TWRP?
What ROMs have you tried?

shirreer said:
Flashing an RUU is a silver bullet for starting over, as an RUU formats all your device's partitions and flashes them with stock images.
You'll need to provide CID & MID or your current firmware version (i.e. 4.16.401.10) if you need help locating a compatible RUU.
Cheers
Click to expand...
Click to collapse
I've tried flashing a few different RUUs and they all come out with an error 155. Googling it suggests I need to relock my bootloader but locking it and running the RUU again gives me the same error. I'm using SuperCID 11111111 and my MID is 0P6B70000. Currently on firmware 4.16.1540.8.
redpoint73 said:
Need some more details to see why the phone won't boot into OS after flashing a ROM.
Is an OS number indicated on the bootloader screen? If so, what is it?
What version TWRP?
What ROMs have you tried?
Click to expand...
Click to collapse
My OS number is 4.16.1540.8, I've tried TWRP 2.7.0.1, 2.8.7.0 and 3.0.0.0, roms I've tried include CM13, SkyDragon and a stock TWRP backup I found in another thread here.

roseyhead said:
I've tried flashing a few different RUUs and they all come out with an error 155. Googling it suggests I need to relock my bootloader but locking it and running the RUU again gives me the same error. I'm using SuperCID 11111111 and my MID is 0P6B70000. Currently on firmware 4.16.1540.8.
Click to expand...
Click to collapse
Your MID and firmware number don't jive; and it can indicate something pretty dangerous (and possibly a radio bricked phone).
Need more info on what you've done.
Do fastboot getvar all, and post the output (delete serial number and IMEI before posting).
Was the phone new and stock (unmodified) when you got it; or did it have a previous owner?
Please list all the mods you have applied (s-off, changed CID, changed MID? etc.).

Ok, here's what getvar all reports:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.24.21331147A1.09G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.16.1540.8
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: -snip-
(bootloader) imei: -snip-
(bootloader) imei2: Not Support
(bootloader) meid: 99000499014851
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B70000
(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: 3aa067db
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.035s
I bought the phone second-hand, it was running a custom ROM (SkyDragon) with cid already set to 11111111 and I wanted to return it to stock. I got the Unlocked/Developer RUU from HTC's site but that didn't start up for me so I tried a bunch of stuff, fiddling with firmwares and unlocking/relocking bootloader and so on but in the end the RUU just hadn't downloaded properly. Once I managed to get the RUUs to run they've all come up with error 155 when they start the flash and flashing the rom.zip direct gives me an error (I forget if it's the same or different)
I've also tried restoring assorted TWRP backups, installing new roms and so on, directly flashing boot.img, things seem to flash ok but the phone just boots direct into fastboot.

Update: I'm not sure what went differently this time but I've installed the latest Cyanogenmod nightly and it's starting up as expected.
I'd like to get back to stock though. What's the best way to go about doing this? The phone was already modified when I got it so I'm not sure what it would've had on it when it was purchased originally.
Edit: A bit of googling suggests this is a Sprint handset (I dismissed this to begin with since I'm in Australia and didn't think it'd be an overseas handset, but ok) so I've flashed 6.20.651.3 firmware and am waiting for a matching RUU to download. Fingers crossed!
Edit again: All sorted now, thanks for your help!

roseyhead said:
Update: I'm not sure what went differently this time but I've installed the latest Cyanogenmod nightly and it's starting up as expected.
I'd like to get back to stock though. What's the best way to go about doing this? The phone was already modified when I got it so I'm not sure what it would've had on it when it was purchased originally.
Edit: A bit of googling suggests this is a Sprint handset (I dismissed this to begin with since I'm in Australia and didn't think it'd be an overseas handset, but ok) so I've flashed 6.20.651.3 firmware and am waiting for a matching RUU to download. Fingers crossed!
Edit again: All sorted now, thanks for your help!
Click to expand...
Click to collapse
I'm glad you're all set. But for other users' benefit, here is a link to HTC's official Sprint RUU page, with instructions for flashing the RUU as well as a download link for Sprint M8 marshmallow RUU 6.20.651.3
Sprint RUU instructions page:
http://www.htc.com/us/support/htc-one-m8-sprint/news/
Sprint M8 marshmallow RUU 6.20.651.3 Direct Link:
http://dl3.htc.com/application/RUU_M8_WHL_M60_SENSE70_SPCS_MR_Sprint_WWE_6.20.651.3.exe
Cheers

i am having the same problem. i dont even know what carrier this phone was from. but the model number written on the back is OP6B110 M8x... and this is the result of getvar all..
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.08.20.0916
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.16.654.4
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) imei2: Not Support
(bootloader) meid: 99000499165808
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B70000
(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: 8a0f02ff
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

roseyhead said:
I got the Unlocked/Developer RUU from HTC's site but that didn't start up for me so I tried a bunch of stuff, fiddling with firmwares and unlocking/relocking bootloader and so on but in the end the RUU just hadn't downloaded properly. Once I managed to get the RUUs to run they've all come up with error 155 when they start the flash and flashing the rom.zip direct gives me an error (I forget if it's the same or different)
Click to expand...
Click to collapse
Happy to see your sorted it out.
I agree it appears to be the Sprint version, based on the the MID (0P6B70000) and product name (m8_whl). While the MID can be modified, the product name is typically not (never seen a mod method for that - so the product name is very reliable).
That being said, I would strongly caution you moving forward, to not flash any firmware or RUU to this device except Sprint M8 firmware/RUU. Reason being, the partitioning on the Sprint phone is different from most other versions; and flashing another version's firmware can lead to a radio brick (phone boots, but nothing requiring the radio will work).
---------- Post added at 11:38 AM ---------- Previous post was at 11:30 AM ----------
mushfiq20 said:
i am having the same problem. i dont even know what carrier this phone was from. but the model number written on the back is OP6B110 M8x... and this is the result of getvar all..
(bootloader) version-main: 2.16.654.4
(bootloader) product: m8_whl
(bootloader) modelid: 0P6B70000
Click to expand...
Click to collapse
This is Sprint version, same as OP based on the model ID and product name. Although main version would indicate the Sprint Harmon Kardon version. RUU can be found at the bottom of the following webpage: http://www.htc.com/us/support/htc-one-m8-harman-kardon-edition-sprint/news/
The M8x designation on the back cover can't be trusted in this case. The back cover has been replaced to remove the "Sprint" logo branding. We've seen several phones like this (back cover replaced to remove evidence of branding) on the forum. You have to go by the getvar data.
Also, be sure to remove your IMEI and serial number from the getvar output. These are personal data, and should never be posted online.

redpoint73 said:
That being said, I would strongly caution you moving forward, to not flash any firmware or RUU to this device except Sprint M8 firmware/RUU. Reason being, the partitioning on the Sprint phone is different from most other versions; and flashing another version's firmware can lead to a radio brick (phone boots, but nothing requiring the radio will work).
Click to expand...
Click to collapse
Thanks a lot for the tip! I'll bear that in mind going forward.

Hi there I seem to be having similar issues. I purchased a refurbished M8. The case indicates 0P6B110 M8x however fastboot getvar all gives:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.09.20.0209
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.30.651.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: [REDACTED]
(bootloader) imei: [REDACTED]
(bootloader) imei2: Not Support
(bootloader) meid: 99000499237658
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B70000
(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: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Going off the info in the thread I downloaded RUU 6.20.651.3.
While verifying I want to update the ROM version it states:
From:
Image Version: 1.54.651.8
To:
Image Version: 6.20.651.3
After clicking next and progressing I get Error 155.
On the fastboot recovery screen shows:
*** LOCKED ***
m8_whl pvt ship s-off
cid-111111111
hboot-3.16.0.0000
radio-1.09.20.0209
opendsp-v38.2.2-00542-m8974.0311
os-3.30.651.2
eMMC-boot 2048
loading zip info fail
RUU
Any help with this would be greatly appreciated.

metalbassist33 said:
On the fastboot recovery screen shows:
*** LOCKED ***
m8_whl pvt ship s-off
cid-111111111
hboot-3.16.0.0000
radio-1.09.20.0209
opendsp-v38.2.2-00542-m8974.0311
os-3.30.651.2
eMMC-boot 2048
loading zip info fail
RUU
Any help with this would be greatly appreciated.
Click to expand...
Click to collapse
To run a Marshmallow RUU, you need to fastboot flash its firmware.zip first.
1. flash 6.20.651.3 firmware.zip
2. run RUU
You should be able to find the firmware.zip in Sprint section
Or you try to find one version lower (lollipop) than 6.20.651.3 RUU, run it then do OTA to 6.20.651.3

ckpv5 said:
To run a Marshmallow RUU, you need to fastboot flash its firmware.zip first.
1. flash 6.20.651.3 firmware.zip
2. run RUU
You should be able to find the firmware.zip in Sprint section
Or you try to find one version lower (lollipop) than 6.20.651.3 RUU, run it then do OTA to 6.20.651.3
Click to expand...
Click to collapse
Just to confirm, if I get a lollipop version, do I still need to fastboot flash a firmware.zip?

metalbassist33 said:
Just to confirm, if I get a lollipop version, do I still need to fastboot flash a firmware.zip?
Click to expand...
Click to collapse
No .. not needed, run Lollipop RUU then do OTA to Marshmallow

Cant go back to Sense (from gpe)

Hello
Since i flashed the gpe ruu, i cant get back to sense.
I tried almost everything. I tried 3 different ruu.exe's, 2 different ruu.zip's and dozens of firmwares. (old and new ones, international and devEd's)
My Bootloader is unlocked, i have s-off and supercid.
(I tried everything with a relocked bootloader, too!)
I followed this guide right here. (And a good hand full of other guides, here on xda)
Currently i have cm13 installed (without gapps!! -.- because /system is too small), but i really want sense back tho
I downloaded 3 different sense based custom roms and tried them all. But twrp is unable to flash them, due to the changed /system partition size. (i tried twrp 2.8.7.0 AND 3.0.0-1)
For those of you who are able to speak or read german, I have a different thread in a german forum.
I appreciate any help!
Thanks

What specific RUUs (file name) and firmwares (version numbers) did you try?
Do fastboot getvar all, and post the results (delete IMEI and serial number before posting).

Firmware's:
1.54.401.5-W_Splash.zip
M8_4.16.401.13_WWE_TWRP2870.zip
M8_6.12.401.4_WWE_FullStock.zip
M8_6.12.401.4_WWE_TWRP2870.zip
M8_6.12.1540.4_DevEd_FullStock.zip
RUU's:
RUU_M8_UL_L50_SENSE60_MR_HTC_Europe_4.16.401.10_Radio_1.25.214500021.06G_20.68.4196t.01_F_release_417003_signed.exe
RUU_3.28.401.9_M8_WWE_Stock.exe
0P6BIMG_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4_Radio_1.29.214500021.12G_20.72.4196t.01_release_464360_signed.zip
0P6BIMG_M8_UL_L50_SENSE60_MR_HTC_Europe_4.16.401.10_Radio_1.25.214500021.06G_20.68.4196t.01_F_release_417809_signed.zip
fastboot getvar all: (i restored an old cm13 backup. i dont know why there is no version-main)
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: ----
(bootloader) imei: ----
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B17000
(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: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

crruell said:
(bootloader) modelid: 0P6B17000
Click to expand...
Click to collapse
There is your problem .. you need to change it to 0P6B10000 then flash the firmware.zip then install RUU.
See this on how to change it : http://forum.xda-developers.com/showthread.php?t=2708581

ckpv5 said:
There is your problem .. you need to change it to 0P6B10000 then flash the firmware.zip then install RUU.
See this on how to change it : http://forum.xda-developers.com/showthread.php?t=2708581
Click to expand...
Click to collapse
Oh my god..
Thank you mate! I will try this, when im back home

crruell said:
fastboot getvar all: (i restored an old cm13 backup. i dont know why there is no version-main)
Click to expand...
Click to collapse
Known TWRP bug, usually happens due to an older version TWRP being used at some point in the past.
Once you flash a firmware successfully, that firmware's version number will be properly shown as main version again.

Hm.
i still cant flash the ruu.
ruu.exe is still giving me errors and the .zip in hboot still says, that the /system partition is too small.
(i also tried the original mid [t-mobile])

solution:
ruu.exe & ruu zip wont work for me.
i tried flashing the firmware & latest twrp and then restoring 6.12.401.4-twrp backup.
and..
it actually worked.
(sorry for double post. i didnt mean to :s)

crruell said:
solution:
ruu.exe & ruu zip wont work for me.
i tried flashing the firmware & latest twrp and then restoring 6.12.401.4-twrp backup.
and..
it actually worked.
(sorry for double post. i didnt mean to :s)
Click to expand...
Click to collapse
As I said earlier.. flash firmware.zip first to change partition size then only you can install RUU.
Restoring a backup after firmware.zip is as same as install RUU after firmware.zip is flashed.
And to install RUU zip, you need to use htc_fastboot.exe

Htc one M8 Os problem

Htc one m8
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.401.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT46PWM03644
(bootloader) imei: 3578710********
(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: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.158s
Is there a solution without s-off
Tried Stock rom:
RUU_M8_UL_L50_SENSE60_MR_BrightstarUS_WWE_4.16.154 0.8_Radio_1.24.21331147A1.09G_20.68.4196.01_F_rele ase_411207_signed.exe
RUU_M8_UL_L50_SENSE60_MR_HTC_Europe_4.16.401.10_Ra dio_1.25.214500021.06G_20.68.4196t.01_F_release_41 7003_signed.exe
RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.154 0.4.exe
with bootloader locked/unlocked state;
with s-on:
Failed
Tried zip
0P6BIMG_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4 _Radio_1.29.214500021.12G_20.72.4196t.01_release_4 64360_signed.zip
Failed
Tried nandroid backup
M8_UL_TWRP_Nandroid_6.12.401.4.zip
succefully flashed backup but stuck on htc logo
Failed
Please help

What is the problem? Is it not booting into the ROM?

when there was boot.the phone at the startup gave (unfortunately------- has stopped)error and also no back key home key visible.
wiped the device. it was all same.
tried RUU it was the same
unlocked the boot loader
and flashed
stock recovery
twrp recovery
then tried nandroid backup restore
the restore was succefull but the phone wont reach startup (tried 1Hour max)
one peculiar thing i notice.earlier when it was booting to startup i was unable to copy anything to internal or external memory as it would say device not ready or disconnected.but i was able to browse the folders.
My opinion partition problem.Need others help to sort out
Note all the files i have mentioned is checked with md5

My comments below in red font:
raffazila said:
Tried Stock rom:
RUU_M8_UL_L50_SENSE60_MR_BrightstarUS_WWE_4.16.154 0.8_Radio_1.24.21331147A1.09G_20.68.4196.01_F_rele ase_411207_signed.exe
RUU_M8_UL_L50_SENSE60_MR_HTC_Europe_4.16.401.10_Ra dio_1.25.214500021.06G_20.68.4196t.01_F_release_41 7003_signed.exe
RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.154 0.4.exe
None of these will ever work on your device, in the s-on configuration. The RUUs containing "BrightstarUS" are for the US Developer's Edition. They won't run on your phone, as they will fail CID and MID checks (your device has CID and MID - can't change these with s-on).
The one labeled "Europe" is for an older version (Lollipop) than what is installed on the phone (Marshmallow). This will fail version check. By definition, you can't "downgrade" by RUU with s-on
with bootloader locked/unlocked state;
with s-on:
Failed
with s-on, its absolutely mandatory to have a locked or relocked bootloader to flash RUU. Unlocked bootloader will make it fail
Tried zip
0P6BIMG_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4 _Radio_1.29.214500021.12G_20.72.4196t.01_release_4 64360_signed.zip
Failed
This is the correct RUU for your version, and should run with s-on. Saying it "Failed" with no other info, is not enough. Were their any error messages, other outputs, etc.? What commands did you use to run it? Were you in fastbootRUU mode?
I would suggest trying to run this again, with the bootloader RELOCKED, and you also need to use htc_fastboot, as the "generic" fastboot will not work with RUU.
Click to expand...
Click to collapse

Firstly it is good someone with good knowledge is answering my doubts.
Secondly i want to tell you something which i noticed in most of the forum is irrelevant posts.I want to avoid those kind of post.
Finaly to say you have found the nearest problem which i was thinking too.
I will check and post.

@redpoint73 Problem soilved.Silly mistake.Thanks.

raffazila said:
Secondly i want to tell you something which i noticed in most of the forum is irrelevant posts.I want to avoid those kind of post.
Click to expand...
Click to collapse
I can't tell what you are referring too, as the statement is really vague. Can you give more details?
---------- Post added at 09:31 AM ---------- Previous post was at 09:28 AM ----------
raffazila said:
Problem soilved.Silly mistake.Thanks.
Click to expand...
Click to collapse
Its best if you posted the solution, and what the mistake was. Useful for those helping (to see whether we sent you on the right path), as well as anyone else reading which may have the same or similar issue.
No mistake is that silly when it comes to these devices. Its often just specific knowledge that was missing, or a detail you didn't catch before (which is an honest mistake, either way).