Unable to return to stock - One (M8) Q&A, Help & Troubleshooting

Hi,
I tried to update the phone to 5.0 and failed. My device was rooted / unlocked / S-On. I also had CWm Philz installed. After running lots of tutorials, current state is: no OS on it, I have also lost Philz, and device is RELOCKED. I can enter fastboot mode.
I have downloaded the correct (at least I think) version for my phone from htcdev (One M8, H3G, UK, v4.4.4, 3.32.771.10.). There is only one file that can be downloaded with same version (3.32.771.10). I have followed the instructions from htcdev site (manual mode), but it fails on signature checking:
fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.011s]
finished. total time: 0.011s
fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.075s]
finished. total time: 0.075s
fastboot flash zip
m8ul-3.4.0-ga90a790.zip
target reported max download size of 1826418688 bytes
sending 'zip' (450344 KB)...
OKAY [ 15.170s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 32.435s
fastboot getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.22.21331147A1.29G
(bootloader) version-main: 3.32.771.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: H3G__106
(bootloader) security: on
(bootloader) build-mode: SHIP
How can I flash this firmware, or how can I install OS to my m8? I also have an OTA v5 file which was downloded on my system through OTA updates, but it failed to install due to phone being rooted / CWM installed. Although my device was sim network locked, when I bought the phone I have received a code to unlock sim from my carrier, and the phone was running without problems, and I have received OTA updates without problems (up to v5).

Did you run the zip twice?
After it fails the first time just run the flash zip command again (back to back),more times than none you have to run it twice

The ZIP you're trying to flash isn't an RUU, it's the kernel source file from HTC Dev...you'll need to restore a back up for your version (3.32.771.10) and then restore the stock recovery

AFAIK htcdev does not release any firmware.
What you downloaded is kernel source.

@jball
I have run it more than once, and nothing...
@EddyOS @ckpv5
Thanks guys, you are correct, I have just checked the zip fle. What are my options then, I cannot find a backup version anywhere for my phone (H3G__006, .3.32.771.10).

Goran_ said:
Thanks guys, you are correct, I have just checked the zip fle. What are my options then, I cannot find a backup version anywhere for my phone (H3G__006, .3.32.771.10).
Click to expand...
Click to collapse
These are that I can suggest :
1. Re-Unlock your device (try the unlock_code.bin that you have before)
2. Install latest TWRP recovery (you can enable MTP in recovery to transfer the extracted nandroid)
3. Download nandroid backup 2.22.771.5 and its stock recovery from my post here :
http://forum.xda-developers.com/showpost.php?p=55322461&postcount=1897
4. Restore 2.22.771.5 and flash stock recovery afterward
5. Reboot, run setup as this nandroid will put your device as new
6. Check software update - do OTA
7. Download-Install-reboot
8. Repeat step 6 & 7 until the last OTA

ckpv5 said:
These are that I can suggest :
1. Re-Unlock your device (try the unlock_code.bin that you have before)
2. Install latest TWRP recovery (you can enable MTP in recovery to transfer the extracted nandroid)
3. Download nandroid backup 2.22.771.5 and its stock recovery from my post here :
http://forum.xda-developers.com/showpost.php?p=55322461&postcount=1897
4. Restore 2.22.771.5 and flash stock recovery afterward
5. Reboot, run setup as this nandroid will put your device as new
6. Check software update - do OTA
7. Download-Install-reboot
8. Repeat step 6 & 7 until the last OTA
Click to expand...
Click to collapse
I have unlocked the phone again, which restored the Philz also. I could not find a way to restore 2.22.771.5 using twrp, it just did not see it, I tried putting the extracted folder in twrp/backups, but no success, probably I was missing something. However, I have found some backup that i forgot i made, which restored 1.54.771.5. I was able to download stock recovery for the same version, and from that point the phone started updating OTAs.
When I upgrade my phone to 5.01, I would like to backup stock recovery at that point. This will allow me to be bale to quickly restore v5 in the future. So this are the steps I intend to perform:
1) backup stock recovery
2) install Philz
3) backup the system using Philz
I know how to do step 2) and 3), but I do not know how to do step 1). Any help on that one?

Goran_ said:
I know how to do step 2) and 3), but I do not know how to do step 1). Any help on that one?
Click to expand...
Click to collapse
I'm not familiar with Philz recovery but I know it can restore TWRP backup .. someone managed to do that before.
I'm not sure whether you can restore from 1.54 up to v5 when your current hboot is 3.19 because it will be two jumps from 3.16 to 3.19. Anyway just try first, hopefully there will be no problem.
To backup recovery .. the easiest way for me is after download the OTA, select install later, copy the OTA zip from Internal Storage\Download folder to PC.
Open the OTA zip with 7-zip, you'll see firmware.zip. Open firmware.zip, you'll see recovery.img - extract this recovery.img out.

You don't need stock recovery it is posted in the backup thread or as said pull from the ota.
If you Insist on backing up easiest way is to >> fastboot boot recovery.img<< This works with twrp, then root then backup recovery with flashify.

Problem solved! Thanks

Goran_ said:
Problem solved! Thanks
Click to expand...
Click to collapse
Great :good::good:
Next time you need backup of 4.20.771.2, let me know (I have that now).
Anyway I believe you've made yours

Related

[Q] Bricked phone?

Hi all, long term lurker first time poster so please go easy on me.
After having many successes on rooting and flashing various device over the years thanks to this forum, I have finally completely knackered my M8 I think.
Awhile ago I rooted and flashed Venom Rom which worked perfectly. I then decided I wanted Revolution HD rom but obviously didn't follow the guide correctly as afterwards I couldn't get wifi. I still used the phone for a few months until yesterday when I finally decided to do something about it. So using Minimal ADB Fastboot I flashed a Lollipop firmware and was going to flash another ROM.
However, the phone won't boot into recovery, just the bootloader. Can anyone please tell me (in simple terms ) where I can go from here or whether I now have a brick?
If it helps the phone is "Relocked" and S-ON.
pastyal said:
Hi all, long term lurker first time poster so please go easy on me.
After having many successes on rooting and flashing various device over the years thanks to this forum, I have finally completely knackered my M8 I think.
Awhile ago I rooted and flashed Venom Rom which worked perfectly. I then decided I wanted Revolution HD rom but obviously didn't follow the guide correctly as afterwards I couldn't get wifi. I still used the phone for a few months until yesterday when I finally decided to do something about it. So using Minimal ADB Fastboot I flashed a Lollipop firmware and was going to flash another ROM.
However, the phone won't boot into recovery, just the bootloader. Can anyone please tell me (in simple terms ) where I can go from here or whether I now have a brick?
If it helps the phone is "Relocked" and S-ON.
Click to expand...
Click to collapse
post your fastboot getvar all please without imei and serial number
did the firmware flash complete successfully ?
---------- Post added at 10:40 AM ---------- Previous post was at 10:34 AM ----------
also forgot to add, if the firmware flash went through fine then you will now have stock recovery on your phone, this will just look like a big red exclamation mark on your phone.
at this point you either need to find a stock RUU for your phone and run it now or unlocked your bootloader again at HTC dev, flash a custom recovery and then flash a custom rom.
if you have anything custom / non stock on your phone right now, it wont boot or load with a relocked bootloader.
Seanie280672 said:
post your fastboot getvar all please without imei and serial number
did the firmware flash complete successfully ?
---------- Post added at 10:40 AM ---------- Previous post was at 10:34 AM ----------
also forgot to add, if the firmware flash went through fine then you will now have stock recovery on your phone, this will just look like a big red exclamation mark on your phone.
at this point you either need to find a stock RUU for your phone and run it now or unlocked your bootloader again at HTC dev, flash a custom recovery and then flash a custom rom.
if you have anything custom / non stock on your phone right now, it wont boot or load with a relocked bootloader.
Click to expand...
Click to collapse
Many thanks for the reply. I don't think the Firmware flashed succesfully, I tried three times and each time got the same response:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash zip firmware.zip
target reported max download size of 1830711296 bytes
sending 'zip' (49565 KB)...
OKAY [ 2.770s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 6.410s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash zip firmware.zip
target reported max download size of 1830711296 bytes
sending 'zip' (49565 KB)...
OKAY [ 2.787s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 6.431s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash zip firmware.zip
target reported max download size of 1830711296 bytes
sending 'zip' (49565 KB)...
OKAY [ 2.790s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 6.415s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
rebooting...
finished. total time: 0.013s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp.img
target reported max download size of 1830711296 bytes
sending 'recovery' (17034 KB)...
OKAY [ 1.706s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.455s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp.img
target reported max download size of 1830711296 bytes
sending 'recovery' (17034 KB)...
OKAY [ 1.713s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.463s
Click to expand...
Click to collapse
And heres the getvar all
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(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:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(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: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Click to expand...
Click to collapse
pastyal said:
Many thanks for the reply. I don't think the Firmware flashed succesfully, I tried three times and each time got the same response:
And heres the getvar all
Click to expand...
Click to collapse
which firmware did you download ? description or link if possible.
also you cant flash custom recovery as your bootloader is locked, and you need stock recovery and HTC dev unlock token to unlock it.
remove your imei and serial number from your getvar all, also, as you are s-on, you need to make sure that the firmware you flashed is ORANG001 firmware as per your cid, at a guess it will be something like 4.xx.61.x the 61 is the key, this will relate to region / carrier 61 is orange / EE, and the 4 is the latest android version firmware for the HTC one M8, as your version main is missing I cant fully confirm this, this is a fault from flashing earlier versions of TWRP recovery.
alternatively, you can flash a custom rom and get s-off via sunshine s-off @ $25 and convert your phone.
Seanie280672 said:
which firmware did you download ? description or link if possible.
also you cant flash custom recovery as your bootloader is locked, and you need stock recovery and HTC dev unlock token to unlock it.
remove your imei and serial number from your getvar all, also, as you are s-on, you need to make sure that the firmware you flashed is ORANG001 firmware as per your cid, at a guess it will be something like 4.xx.61.x the 61 is the key, this will relate to region / carrier 61 is orange / EE, and the 4 is the latest android version firmware for the HTC one M8, as your version main is missing I cant fully confirm this, this is a fault from flashing earlier versions of TWRP recovery.
alternatively, you can flash a custom rom and get s-off via sunshine s-off @ $25 and convert your phone.
Click to expand...
Click to collapse
Ooops thanks for the heads up on removing the info!
Aaah thats the mistake I made by using the wrong firmware. I will locate the correct firmware and try that later on today. I did look at the Sunshine option but was unsure if it would help me at this moment in time. Think i'll try the correct firmware first.
Will update here later with good news hopefully!
Seanie280672 said:
post your fastboot getvar all please without imei and serial number
did the firmware flash complete successfully ?
---------- Post added at 10:40 AM ---------- Previous post was at 10:34 AM ----------
also forgot to add, if the firmware flash went through fine then you will now have stock recovery on your phone, this will just look like a big red exclamation mark on your phone.
at this point you either need to find a stock RUU for your phone and run it now or unlocked your bootloader again at HTC dev, flash a custom recovery and then flash a custom rom.
if you have anything custom / non stock on your phone right now, it wont boot or load with a relocked bootloader.
Click to expand...
Click to collapse
Ok, I have now succesfully flashed the correct (I think ) firmware. I flashed twice to be sure. In cmd I rebooted to Fastboot but all I have now is the screen you mentioned with the red exclamation mark within a triangle. Where do I go from here as the phone won't do anything, not even turn off. It does occasionally turn off itself and I try to enter bootloader but it just loads to the red exclamation mark again.?
pastyal said:
Ok, I have now succesfully flashed the correct (I think ) firmware. I flashed twice to be sure. In cmd I rebooted to Fastboot but all I have now is the screen you mentioned with the red exclamation mark within a triangle. Where do I go from here as the phone won't do anything, not even turn off. It does occasionally turn off itself and I try to enter bootloader but it just loads to the red exclamation mark again.?
Click to expand...
Click to collapse
hold volume up, volume down and power button for about 15 to 20 seconds, phone will go off, before it comes back on quickly release all buttons and just hold volume down only, it should boot to the bootloader.
Thank you for that, that gets me into the bootloader but it won't load into fastboot now?
pastyal said:
Thank you for that, that gets me into the bootloader but it won't load into fastboot now?
Click to expand...
Click to collapse
what do you mean wont load into fastboot ? do you mean your computer just says waiting for device, which firmware did you flash ?
Seanie280672 said:
what do you mean wont load into fastboot ? do you mean your computer just says waiting for device, which firmware did you flash ?
Click to expand...
Click to collapse
Yes pc says waiting for device. I flashed a firmware from here, not sure which one it was now though http://forum.xda-developers.com/showthread.php?t=2701376
Do I need to flash a stock recovery now? If so do I need to be able to get the phone to load into fastboot?
pastyal said:
Yes pc says waiting for device. I flashed a firmware from here, not sure which one it was now though http://forum.xda-developers.com/showthread.php?t=2701376
Do I need to flash a stock recovery now? If so do I need to be able to get the phone to load into fastboot?
Click to expand...
Click to collapse
no you don't need to flash stock recovery, I don't see any firmware files for your phone in that link, and as your s-on, they shouldn't of been successful, nothing should of changed.
waiting for device is generally a driver problem, check device manager whilst your phone is plugged into your computer, should say android devices - MyHTC
Seanie280672 said:
no you don't need to flash stock recovery, I don't see any firmware files for your phone in that link, and as your s-on, they shouldn't of been successful, nothing should of changed.
waiting for device is generally a driver problem, check device manager whilst your phone is plugged into your computer, should say android devices - MyHTC
Click to expand...
Click to collapse
I can't see any android devices listed under device manager. I installed HTC Sync yesterday though which I thought loaded the drivers? What should i do now?
pastyal said:
I can't see any android devices listed under device manager. I installed HTC Sync yesterday though which I thought loaded the drivers? What should i do now?
Click to expand...
Click to collapse
Try to uninstall HTC Sync and any HTC drivers. Then see if the phone shows up in Device Manager. If so, select to manually pick drivers, and pick the generic MTP device.
Might not work for you, but this is what I had to do to get fastboot/adb working on my PC with the M8.
pastyal said:
I can't see any android devices listed under device manager. I installed HTC Sync yesterday though which I thought loaded the drivers? What should i do now?
Click to expand...
Click to collapse
Also make sure in bootloader it says FASTBOOT USB and not HBOOT
redpoint73 said:
Try to uninstall HTC Sync and any HTC drivers. Then see if the phone shows up in Device Manager. If so, select to manually pick drivers, and pick the generic MTP device.
Might not work for you, but this is what I had to do to get fastboot/adb working on my PC with the M8.
Click to expand...
Click to collapse
ssantos132 said:
Also make sure in bootloader it says FASTBOOT USB and not HBOOT
Click to expand...
Click to collapse
Sorted it, was a simple matter of swapping USB ports. I have a new laptop and forgot one of the ports was USB 3.0 which the phone was connected with. Evidently it prefers a USB 2.0 port.
So I assume now I need to find the correct firmware, of which I'm struggling with a little. Can anyone po8nt me in the right direction? I have been through a lot of threads here and can't seem to find anything.
pastyal said:
Sorted it, was a simple matter of swapping USB ports. I have a new laptop and forgot one of the ports was USB 3.0 which the phone was connected with. Evidently it prefers a USB 2.0 port.
Click to expand...
Click to collapse
That's right, USB 3.0 does not play well with this device.
pastyal said:
So I assume now I need to find the correct firmware, of which I'm struggling with a little. Can anyone po8nt me in the right direction? I have been through a lot of threads here and can't seem to find anything.
Click to expand...
Click to collapse
I can't find the firmware for your CID either. You may have better luck updating the firmware by OTA.
To do that, you will need to restore the stock ROM and stock recovery, using the files and instructions here: http://forum.xda-developers.com/showthread.php?t=2701376
After restoring stock ROM and stock recovery, you will need to update up to Lollipop, which will probably include a few (3) OTA updates.
Once you've updated to current firmware by OTA, you can install custom recovery again, and run the current custom ROMs.
redpoint73 said:
That's right, USB 3.0 does not play well with this device.
I can't find the firmware for your CID either. You may have better luck updating the firmware by OTA.
To do that, you will need to restore the stock ROM and stock recovery, using the files and instructions here: http://forum.xda-developers.com/showthread.php?t=2701376
After restoring stock ROM and stock recovery, you will need to update up to Lollipop, which will probably include a few (3) OTA updates.
Once you've updated to current firmware by OTA, you can install custom recovery again, and run the current custom ROMs.
Click to expand...
Click to collapse
I'm getting myself in a right mess I think. I've just tried installing the stock recoveries from https://www.androidfilehost.com/?w=files&flid=25064 as linked to from this thread http://forum.xda-developers.com/showthread.php?t=2694994 which I thought woud be perfect for me but I get an error of "FAILED (remote: signature verify fail)" in cmd. If I reboot the phone into recovery I get the red exclamation mark again.
Any ideas on what i'm doing wrong? Am i right in thinking I need to flash a stock recovery and THEN a stock ROM, or should it be the other way around?
pastyal said:
I'm getting myself in a right mess I think. I've just tried installing the stock recoveries from https://www.androidfilehost.com/?w=files&flid=25064 as linked to from this thread http://forum.xda-developers.com/showthread.php?t=2694994 which I thought woud be perfect for me but I get an error of "FAILED (remote: signature verify fail)" in cmd. If I reboot the phone into recovery I get the red exclamation mark again.
Any ideas on what i'm doing wrong? Am i right in thinking I need to flash a stock recovery and THEN a stock ROM, or should it be the other way around?
Click to expand...
Click to collapse
Multiple mistakes here:
1) You need the stock ROM and recovery that corresponds with your hboot (3.16) which would indicate a 1.x software and corresponding recovery. The files you linked are for software 3.x and 4.x.
2) I'm also not sure why you are stumbling around in threads that aren't even for your CID when I already gave you a link to the proper location for the stock nandroid for your CID version. You want to restore the stock nandroid for ORANG001, which is 1.54.61.5 and the stock recovery 1.54.xx
3) You need to flash the stock ROM (restore stock nandroid) before the stock recovery. Once you've restored stock recovery, you cannot flash a ROM or nandroid. You need custom recovery to do that.
3) Lollipop recoveries for other CID won't work. But a KitKat recovery for another CID will work (as mentioned in item 2 above, you want a 1.54.xx recovery to correspond to the stock ROM 1.54.61.5 since a recovery doesn't seem to be posted for your exact software 1.54.61.5
redpoint73 said:
Multiple mistakes here:
1) You need the stock ROM and recovery that corresponds with your hboot (3.16) which would indicate a 1.x software and corresponding recovery. The files you linked are for software 3.x and 4.x.
2) I'm also not sure why you are stumbling around in threads that aren't even for your CID when I already gave you a link to the proper location for the stock nandroid for your CID version. You want to restore the stock nandroid for ORANG001, which is 1.54.61.5 and the stock recovery 1.54.xx
3) You need to flash the stock ROM (restore stock nandroid) before the stock recovery. Once you've restored stock recovery, you cannot flash a ROM or nandroid. You need custom recovery to do that.
3) Lollipop recoveries for other CID won't work. But a KitKat recovery for another CID will work (as mentioned in item 2 above, you want a 1.54.xx recovery to correspond to the stock ROM 1.54.61.5 since a recovery doesn't seem to be posted for your exact software 1.54.61.5
Click to expand...
Click to collapse
Thanks very much for that, the reason why i was stumbling around is because i had already tried that Nandroid backup but i think i must have used incorrect instructions. I read I had to open the zip file and flash the boot.img, but I just get the same error as before if I do that.
Could you please tell me how to restore the stock Nandroid. i promise you I am going around in circles lol
pastyal said:
i had already tried that Nandroid backup but i think i must have used incorrect instructions. I read I had to open the zip file and flash the boot.img, but I just get the same error as before if I do that.
Click to expand...
Click to collapse
Instruction on restoring a nandroid are in post #3 of the stock nandroid collection thread I linked before. Click where it says Questions & Answers, and you will see the 2nd question is how to restore a stock nandroid: http://forum.xda-developers.com/showpost.php?p=58128936&postcount=3
I think you may have seen these instructions, but you only did one part, not the remaining parts of the process. The boot.img is essentially just the kernel; technically a few other things too, but either way its like 1% of what you need to have a working ROM. Namely, if you only flashed boot.img, you didn't do the steps I've highlighted in orange below:
- Place the nandroid backup unpacked on the sdcard of the phone in the right backup folder
* Philz touch uses - Clockworkmod\Backups\
* TWRP uses - TWRP\Backups\ or TWRP/Backups/serialnum/ (replace serialnum with your device's serial number. To have TWRP create the proper directory structure for you, just do a simple backup of just the boot partition and put the backup files in there) thanks to garyd9 for the additional info
- Flash the boot.img or boot.emmc.win file from the nandroid backup
- Make a full wipe in the recovery
- Restore the nandroid backup and reboot
You need to unzip the downloaded file, then place the entire folder contents to the proper location on the phone. Then boot recovery (probably TWRP) and use the restore function to install the nandroid. I actually do not think you need to extract and flash boot.img separately.
After that, install the stock recovery with the fastboot command: fastboot flash recovery filename.img
Where "filename.img" is the actual name of the desired stock recovery file.
---------- Post added at 11:03 AM ---------- Previous post was at 10:57 AM ----------
pastyal said:
If it helps the phone is "Relocked" and S-ON.
Click to expand...
Click to collapse
Are you currently unlocked again? The above is from your top post, but I don't know if you've changed this (unlocked again).
You can only do the above mentioned steps (restore nandroid, stock recovery, etc.) if you are bootloader unlocked.

Can't Flash TWRP Recovery

Self-admitted newb here. Been reading up on FAQs and instructions on how to Root my new device and am eager to learn more to eventually fully optimize. I was able to unlock, but when attempting to flash TWRP recovery, it'll just hang forever with this message:
"sending 'recovery' (11976 KB)...".
I confirmed checksums of files downloaded, USB Debugging is flagged, Fastboot is deselected, updated the HTC drivers on my PC, and my S/N is acknowledged with the 'fastboot devices' command. I even did a Factory Reset from bootload screen, as this is a new device with no data on it yet.
Any helpful suggestions on determining next steps would be greatly appreciated!
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.15.2133156.UA12.5mv
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.54.401.109
(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: 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: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
You need 2.7 series..
flyera343 said:
You need 2.7 series..
Click to expand...
Click to collapse
Agreed, and I was mistakenly attempting to flash twrp-2.8.6.1-m8.img initially . I'm sorry I failed to mention that in the original post and yes, I also did erase cache several times. Re-attempting to flash twrp-2.7.0.1-m8.img is when the 'sending recovery' hang issue comes up.
bump
pill_popper said:
(bootloader) version-main: 1.54.401.109
(bootloader) modelid: 0P6B12000
(bootloader) security: off
Click to expand...
Click to collapse
You have a very old software version. Since your device is S-Off, I suggest :
1. change the MID 0P6B12000 to 0P6B10000
Follow this thread : http://forum.xda-developers.com/showthread.php?t=2708581
2. run 4.16.401.10 RUU.exe - https://docs.google.com/file/d/0B17smFr95pleeTQ5U1NzNkZzM0U/edit?pli=1
RUU will flash your entire phone back to stock including recovery
(as your device is S-Off, no need to lock/relock bootloader)
3. Now you can install the latest TWRP recovery and do whatever you want to do
Thank you for your kind words. I appreciate it. Will follow up on the points covered in your post and report back.
Ahh.. you need a rooted ROM to do that change of MID.
Without a custom recovery installed, you may not have a rooted ROM.
Reading back your problem ... the error is stuck at sending recovery, not enter recovery. This is possible if you don't have a proper fastboot/adb files.
Try this : http://forum.xda-developers.com/showthread.php?t=2317790
then try to install TWRP recovery again
ckpv5 said:
Ahh.. you need a rooted ROM to do that change of MID.
Without a custom recovery installed, you may not have a rooted ROM.
Reading back your problem ... the error is stuck at sending recovery, not enter recovery.
Click to expand...
Click to collapse
Correct, sorry if I wasn't being clear about that. I've Unlocked, but not yet rooted hence, the attempt to send TWRP. I haven't yet taken next steps though.
ckpv5 said:
This is possible if you don't have a proper fastboot/adb files.
Try this : http://forum.xda-developers.com/showthread.php?t=2317790
then try to install TWRP recovery again
Click to expand...
Click to collapse
More reading! :cyclops:
**Updated**
So I've tried using Minimal ADB tool as well. Now instead of hanging, I'm eliciting errors.
target reported max download size of 1830711296 bytes
sending 'recovery' (11976 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 5.023s
I'm running as Administrator in Windows 7, I can hear the PC recognize the phone when I plug it in the USB and I've also confirmed multiple times the 'fastboot devices' command recognizes my phone.
If this might be a USB related issue, how would I go about investigating in that direction? Not sure what is preventing me from simply flashing a TWRP recovery. Any thoughts on this are welcome, thank you.
*bumpity bump*
So I can see 'FASTBOOT USB' in bootloader mode, and the fastboot devices command returns my S/N, but still the adb devices command just returns the message 'list of devices' and nothing else. Attempting to flash TWRP recovery still fails. I've uninstalled all HTC stuff and manually updated the driver to 'MTP USB Device' via Device Manager per redpoint73's advice. Before I give up on this PC, are there any additional steps I can take? Any guidance from you guys would be appreciated, thanks!
First, you don't run adb command when on fastboot mode, only fastboot command will work.
Is the USB 3.0 on PC ? You need USB 2.0
Is your device properly working ?
I like to suggest to flash Dev Edition firmware to your device or simply run the Dev Edition RUU to bring the hboot/software version to the latest version before you try TWRP again.
You have MID/CID that match/fit a Dev Edition device except the software version no.
ckpv5 said:
First, you don't run adb command when on fastboot mode, only fastboot command will work.
Is the USB 3.0 on PC ? You need USB 2.0
Is your device properly working ?
I like to suggest to flash Dev Edition firmware to your device or simply run the Dev Edition RUU to bring the hboot/software version to the latest version before you try TWRP again.
You have MID/CID that match/fit a Dev Edition device except the software version no.
Click to expand...
Click to collapse
I guess what most on here would consider to be trivial are to me revelations. Thank you for your response and now I see my device S/N is recognized after running the adb devices command when the phone is running in 'normal' mode! Yes, it is properly working but sadly, all four USB ports on the PC are USB 3.0 I'll read up on your suggestions and reply with questions at that point before taking action. Again with the reading! :cyclops: My concerns here are if stock recovery would continue to work if I go down either of those paths and how the phone is supposed to respond if it's not responding when attempting to flash TWRP. Thanks again for your inputs, I appreciate it!
First .. you need to know your reason to install a TWRP. If you plan to install a custom ROM, it won't properly work because you have a very low version hboot as most custom ROMs require a hboot 3.19.0000
then .. there are other ways to achieve this (all because you have a S-Off device)
1. You can install TWRP using the external_sd (microSD) method but you can only use a lower version TWRP 2.7.x.x or better 2.8.1.0 (because you failed in fastboot method)
2. As I said earlier - install the latest firmware.zip but using the external_sd method too ... but your device may get stuck because your ROM is too low
3. The safest/fastest is install RUU but again you need a USB 2.0 (I'm not sure whether you can install RUU zip using the external_sd method).
4. Back to no. 2 - you can install the firmware.zip using the external_sd method (need to do it twice) then install TWRP again the external_sd method then you need to install a ROM or restore a backup meant for the newer hboot 3.19
ckpv5 said:
First .. you need to know your reason to install a TWRP. If you plan to install a custom ROM, it won't properly work because you have a very low version hboot as most custom ROMs require a hboot 3.19.0000
then .. there are other ways to achieve this (all because you have a S-Off device)
1. You can install TWRP using the external_sd (microSD) method but you can only use a lower version TWRP 2.7.x.x or better 2.8.1.0 (because you failed in fastboot method)
2. As I said earlier - install the latest firmware.zip but using the external_sd method too ... but your device may get stuck because your ROM is too low
3. The safest/fastest is install RUU but again you need a USB 2.0 (I'm not sure whether you can install RUU zip using the external_sd method).
4. Back to no. 2 - you can install the firmware.zip using the external_sd method (need to do it twice) then install TWRP again the external_sd method then you need to install a ROM or restore a backup meant for the newer hboot 3.19
Click to expand...
Click to collapse
If I wanted to attempt #3, please point me to the correct version as it wasn't clear to me what file to choose here:
http://forum.xda-developers.com/showthread.php?t=2701376
Thanks!
http://dl3.htc.com/application/RUU_...G_20.68.4196.01_F_release_411207_signed_2.exe
1. put device on fastboot/bootloader mode
2. run the exe (select run as administrator in windows context menu
3. follow instruction - accept, next, next, blablabla until finish
ckpv5 said:
http://dl3.htc.com/application/RUU_...G_20.68.4196.01_F_release_411207_signed_2.exe
1. put device on fastboot/bootloader mode
2. run the exe (select run as administrator in windows context menu
3. follow instruction - accept, next, next, blablabla until finish
Click to expand...
Click to collapse
The whole point of this exercise is to gain root so that yes, I can have the option of flashing a custom ROM. I noticed in the executable's file name you referenced model M8_UL_L50, but mine is M8_UL_CA. I also noticed its radio version differs from the one listed in my getvar all file. *edit* I've now realized this file is straight from HTC.
Since my current version is so old, is it still OK to run this to update to the latest version rather than updating to an intermediate version before updating to the latest version? Just wanted to confirm before taking any unnecessary action. Thank you again for your patience and the helpful information!
M8_UL - M8 with LTE
L50 - Android L 5.0
CA - US region
Radio version different because yours is old/lower version and this is newer/latest version and you're going to update hboot, radio and many more with this RUU. You need the update in order to install custom ROM as I mentioned before most custom ROMs work only on hboot 3.19.0000
You have S-Off device, you don't need intermediate version ... and most important RUU doesn't need intermediate version because RUU will wipe clean your device and replace all images with those come with it. (So make a backup of your important files to PC)

HTC M8 stuck in fastboot only showing RUU

Ok this is what happened.
I had the rom Android Revolution installed on my HTC M8.
Today I installed the new ROM Revolution, Android 6.0, but when I could not turn on wifi.
After searching in google found that its a MUST to update your firmware, which I have subsequently done true the PC with mini-sdk. That did not work, and now I'm stuck in fastboot. He won't let me into recovery anymore, if i chose it, he trows me back to fastboot menu
SCREEN IN FASTBOOT:
Tampered *** ***
*** *** Relocked
M8_UL PVT SHIP S-ON
HBOOT-318.0.0000
RADIO 1.19.21331147A1.09G
OpenDSP-v38.2.2-00542-M8974.0311
OS 2.22.161.6
eMMC boat 2048MB
RUU
anyone have a solution?
Do i have to update firmware now, really don't now wich steps i should take right now.
Thanks for the effort
C:\mini-sdk>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.19.21331147A1.09G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.22.161.6
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: VODAPE17
(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: 5e4b24e4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
C:\mini-sdk>
Mcdrug said:
After searching in google found that its a MUST to update your firmware, which I have subsequently done true the PC with mini-sdk. That did not work, and now I'm stuck in fastboot.
Click to expand...
Click to collapse
What exactly did you try to flash (full file name) and where did you get it from?
Any error messages when you tried to flash the firmware, or other outputs?
redpoint73 said:
What exactly did you try to flash (full file name) and where did you get it from?
Any error messages when you tried to flash the firmware, or other outputs?
Click to expand...
Click to collapse
download
M8_6.12.401.4_WWE_TWRP2870.zip
hboot_signedbyaa.img
pg2fs_spcustom.img
radio.img
rcdata.img
rpm.img
sbl1-8974AA-1.img
sbl1-8974AB-1.img
sbl1-8974AB-2.img
sdi.img
sensor_hub.img
splash1.nb0
tp_SYN3508.img
tp_SYN3528.img
tz.img
wcnss.img
adsp.img
android-info.txt
error message:
i thought it was something like (FAILED (remote: 12 signature verify fail). maybe have to do it again to make sure what error message i got?
Mcdrug said:
download
M8_6.12.401.4_WWE_TWRP2870.zip
i thought it was something like (FAILED (remote: 12 signature verify fail).
Click to expand...
Click to collapse
Yes, it would be signature verify fail. Its a hacked firmware (with stock recovery replaced with TWRP). You can't flash this with s-on. You can only flash signed firmware with s-on; and once its hacked, its no longer signed.
Additionally, its not the right version number for your CID. It would need to have "161" in the place of "401".
Your best bet is probably to return to full stock nandroid 2.22.161.6 and stock recovery 2.22.161.6, than OTA up to LP or MM. Instructions and required files here:
http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
redpoint73 said:
Yes, it would be signature verify fail. Its a hacked firmware (with stock recovery replaced with TWRP). You can't flash this with s-on. You can only flash signed firmware with s-on; and once its hacked, its no longer signed.
Additionally, its not the right version number for your CID. It would need to have "161" in the place of "401".
Your best bet is probably to return to full stock nandroid 2.22.161.6 and stock recovery 2.22.161.6, than OTA up to LP or MM. Instructions and required files here:
http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Click to expand...
Click to collapse
He won't let me flash recovery twrp-2.8.1.0-m8.img
FAILsignature verify fail
FAILED (remote: signature verify fail)
Mcdrug said:
He won't let me flash recovery twrp-2.8.1.0-m8.img
FAILsignature verify fail
FAILED (remote: signature verify fail)
Click to expand...
Click to collapse
You need to unlock the bootloader again, in order to flash custom recovery.
Big relief i am in recovery again!
Actually back in my Android Revolution Rom , but without WIFI
Don't want to do anyting wrong again right now.
So next thing to do is folow the steps from your posted link #5?
Or do i have to do other things now?
Mcdrug said:
Big relief i am in recovery again!
Actually back in my Android Revolution Rom , but without WIFI
Don't want to do anyting wrong again right now.
So next thing to do is folow the steps from your posted link #5?
Or do i have to do other things now?
Click to expand...
Click to collapse
You have to follow all the steps through Step 14.
Again, the goal is to return to full stock nandroid 2.22.161.6 and stock recovery 2.22.161.6, than OTA up to LP or MM
Can't get true this step:
6(a). Reboot, connect device to PC then
open Internal Storage - TWRP/BACKUPS/SerialNo./ (if backup is set to internal storage)
open SD Card - TWRP/BACKUPS/SerialNo./ (if backup is set to MicroSD)
6(b). For those with no OS, connect device to PC. In TWRP recovery go to mount, make sure MTP is enabled.
Then you can open Internal Storage - TWRP/BACKUPS/SerialNo./ (if backup is set to internal storage)
If i make a backup from Boot he puts is in internal store TWRP/BACKUPS/SerialNo./ but when i copy the unzip files he stops, too big.
solution might be: Are you mounting the MTP in recovery mode ? It won't work this way.
You need to transfer them on a working OS (I mean you have to be on homescreen)
Try use an external sdcard.
I have put an external sdcard inside, i can put the files on the card
But then the files aren't located at the TWRP/BACKUP map.
What to do?
Mcdrug said:
If i make a backup from Boot he puts is in internal store TWRP/BACKUPS/SerialNo./ but when i copy the unzip files he stops, too big.
What to do?
Click to expand...
Click to collapse
when you select boot to backup, you can select which storage the backup goes to .. select microSD instead of internal (read all menu in the backup section on TWRP)
then you can use a card reader to mount your microsd to PC and transfer the extracted contents of the backup zip to the same folder that you made with the boot backup and replace all files when PC ask you.
All done, back in stock rom, thank you very much!!
10. In reboot menu select bootloader (when TWRP asks whether you want to root your device, select do not install)
I choose in this step do not install, but he rebooted me direct into the stock rom.
Tried some things to get into the bootloader again, volume down and power, cmd with adb fastboot, but nothing really worked.
What's the reason i can't get back to bootloader, and how do i get step 11 fixed and flash stock recovery?
To go to bootloader when on OS running ... press power button and select restart. When the screen turn black .. hold volume down button .. that will take you to hboot screen, press power once will get you to fastboot/bootloader
To go to bootloader when on OS running ... you need to enable USB debugging in settings - Developer options. To enable Developer options, go to settings - about - software information - more - click build number until the developer options is enabled.
Once usb debugging is enabled, you can run command adb reboot bootloader to get to fastboot/bootloader
It works, did the last step:
11. fastboot flash stock recovery that you downloaded - command fastboot flash recovery x.xxx.xx.x_recovery.img
but now can't entering recovery anymore, just showing a red trangle with an exclamation mark? And in some minutes he boots to OS.
Have to do step 1 again? Maybe go to a higher version? I want OTA to MM 6.0
You don't need to get into recovery after you installed stock recovery.
what you need to do ... boot to OS .. go to settings - about - software update - check for update, download and click install let the system do its stuff to update. After reboot, repeat the checking & install process.
And you need to do the checking & install, multiple times to update :
2.22.161.6 --> 4.19.161.2 --> 4.19.161.3 --> 6.12.161.4 --> done.

Entering recovery

Hello , please help , I unlock bootloader flash TWRP 2.7.0.2 , root , after update to TWRP 3.0.0.2 , and go to recovery stays on the screen , some solution
You can't use TWRP 3.x.x.x when your hboot is lower than 3.19.0000
or lower than lollipop firmware
Install TWRP 2.8.x.x
ckpv5 said:
You can't use TWRP 3.x.x.x when your hboot is lower than 3.19.0000
or lower than lollipop firmware
Install TWRP 2.8.x.x
Click to expand...
Click to collapse
The same happens when I install 2.8.4.0 , and when I install any rom does not give me the animation start , nothing but the same screen until it comes to system
TWRP 2.8.4.0 & above is meant for firmware 4.x
If your firmware is 1.x & 2.x, use 2.8.1.0
If your firmware is 3.x, use 2.8.3.0
See simple guide here : http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Can you post fastboot getvar all result (without serial & imei no.) then we'll see what is best for you.
ckpv5 said:
TWRP 2.8.4.0 & above is meant for firmware 4.x
If your firmware is 1.x & 2.x, use 2.8.1.0
If your firmware is 3.x, use 2.8.3.0
See simple guide here : http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Can you post fastboot getvar all result (without serial & imei no.) then we'll see what is best for you.
Click to expand...
Click to collapse
You can restore a backup TWRP lollipop with this firmware kitkat ?Cid HTC _332 for example el 4.32.600.2,thanks
No.. you need to restore 1.12.600.20 backup and update to 4.32.600.2 then later update to Marshmallow 6.17.600.3
Install TWRP 2.8.1.0
Restore 1.12.600.20 backup
Install stock recovery 4.32.600.2
Do OTA
Everything that you need are in my backup thread that I linked above
ckpv5 said:
No.. you need to restore 1.12.600.20 backup and update to 4.32.600.2 then later update to Marshmallow 6.17.600.3
Install TWRP 2.8.1.0
Restore 1.12.600.20 backup
Install stock recovery 4.32.600.2
Do OTA
Everything that you need are in my backup thread that I linked above
Click to expand...
Click to collapse
but I 'm s -on and here in Mexico no update to MM via Ota
vences31 said:
but I 'm s -on and here in Mexico no update to MM via Ota
Click to expand...
Click to collapse
Backup and recovery flash stock you suggested , to download the update via OTA lollipop and restarts to install and stays on the white screen with HTC logo , do I have root not know if this is the error ?
Make sure you don't accept root when asked by TWRP.
After OTA is downloaded, let the system install it, no manual install. The first boot will take time.
ckpv5 said:
Make sure you don't accept root when asked by TWRP.
After OTA is downloaded, let the system install it, no manual install. The first boot will take time.
Click to expand...
Click to collapse
but the image of the phone does not appear installing the update
After you restore 1.12.600.20 backup & install 4.32.600.2 stock recovery, the phone booted fine ?
When doing restore, you wipe all cache, dalvik-cache, data & system ? And you restore all boot, data & system ?
Let's say it booted fine, then you check OTA, download & let system install, then it should boot to recovery ... but instead of going to recovery, it get stuck on white screen.. is this what happening ?
Press both power + volume up buttons to reboot the device and try redo the process.
ckpv5 said:
After you restore 1.12.600.20 backup & install 4.32.600.2 stock recovery, the phone booted fine ?
When doing restore, you wipe all cache, dalvik-cache, data & system ? And you restore all boot, data & system ?
Let's say it booted fine, then you check OTA, download & let system install, then it should boot to recovery ... but instead of going to recovery, it get stuck on white screen.. is this what happening ?
Click to expand...
Click to collapse
Yes...try again
If this is not successful .. I'll write another method later tonight.
I have to go now ... will be around after 12 hours
ckpv5 said:
If this is not successful .. I'll write another method later tonight.
I have to go now ... will be around after 12 hours
Click to expand...
Click to collapse
and because if I install a custom rom 6.0.1 does not give me the boot animation and wifi when entering the system is switched off screen,thanks for your time
vences31 said:
and because if I install a custom rom 6.0.1 does not give me the boot animation and wifi when entering the system is switched off screen,thanks for your time
Click to expand...
Click to collapse
That's because your current firmware is too low to handle a 6.0.x custom ROM
I really don't get it why you can't update. Had the same experience before with someone else but the problem was down to not following the guide accordingly.
http://forum.xda-developers.com/showpost.php?p=64730207&postcount=683
You said before, if you install TWRP 2.8.4.0, you can boot to recovery ? If yes, I'll give you another way as your intention is to install custom ROM
ckpv5 said:
That's because your current firmware is too low to handle a 6.0.x custom ROM
I really don't get it why you can't update. Had the same experience before with someone else but the problem was down to not following the guide accordingly.
http://forum.xda-developers.com/showpost.php?p=64730207&postcount=683
You said before, if you install TWRP 2.8.4.0, you can boot to recovery ? If yes, I'll give you another way as your intention is to install custom ROM
Click to expand...
Click to collapse
I want to have Android 6.0 functional either official or custom ROM , or at least spend KitKat , if there are other ways please shares , Eh understood many things thanks to you and now I understand , with other devices I've had it was easier but this has been difficult
You're on KiKat now.. I'm preparing files for you to manually update to lollipop.
Once done, I want you to try to update to Marshmallow. If no success, I'll tell how to manually update to Marshmallow after you tried system update.
This will involve relocking bootloader assuming your device is S-On (you don't give fastboot getvar all result that I asked before)
1. Install TWRP 2.8.4.0 (as you said this is the highest TWRP version that you can install and can boot to it)
2. Download the 4.32.600.2 backup and restore - http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
(just follow the steps as in the guide 1-10 only, skip the rest)
3. Download fw_4.32.600.2.zip - https://sourceforge.net/projects/htconem8/files/fw_4.32.600.2.zip/download
4. Install the firmware
1. If the bootloader is UNLOCKED (for S-On device only), relock it with commands:
fastboot oem lock
fastboot reboot-bootloader
If the bootloader is LOCKED or RELOCKED, skip the above.
2. Put the device in bootloader/fastboot mode and connect to PC, run these commands
fastboot oem rebootRUU
fastboot flash zip fw_4.32.600.2.zip
you'll see ERROR/FAILED, repeat
fastboot flash zip fw_4.32.600.2.zip
fastboot reboot-bootloader
You should see the OS written 4.32.600.2 (in green color) on the bootloader.
Now reboot the device .. once the setup completed, check OTA. You should have 6.17.600.3 OTA, download and let system install.
Once the OTA installation is completed and phone rebooted to OS ... you now have a Marshmallow updated firmware & ROM.
You can unlock bootloader again with unlock_code.bin that you received from HTC or apply a new one.
Once unlocked, install TWRP 3.0.2-0, you can install any custom ROM that you like
ckpv5 said:
You're on KiKat now.. I'm preparing files for you to manually update to lollipop.
Once done, I want you to try to update to Marshmallow. If no success, I'll tell how to manually update to Marshmallow after you tried system update.
This will involve relocking bootloader assuming your device is S-On (you don't give fastboot getvar all result that I asked before)
1. Install TWRP 2.8.4.0 (as you said this is the highest TWRP version that you can install and can boot to it)
2. Download the 4.32.600.2 backup and restore - http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
(just follow the steps as in the guide 1-10 only, skip the rest)
3. Download fw_4.32.600.2.zip - https://sourceforge.net/projects/htconem8/files/fw_4.32.600.2.zip/download
4. Install the firmware
1. If the bootloader is UNLOCKED (for S-On device only), relock it with commands:
fastboot oem lock
fastboot reboot-bootloader
If the bootloader is LOCKED or RELOCKED, skip the above.
2. Put the device in bootloader/fastboot mode and connect to PC, run these commands
fastboot oem rebootRUU
fastboot flash zip fw_4.32.600.2.zip
you'll see ERROR/FAILED, repeat
fastboot flash zip fw_4.32.600.2.zip
fastboot reboot-bootloader
You should see the OS written 4.32.600.2 (in green color) on the bootloader.
Now reboot the device .. once the setup completed, check OTA. You should have 6.17.600.3 OTA, download and let system install.
Once the OTA installation is completed and phone rebooted to OS ... you now have a Marshmallow updated firmware & ROM.
You can unlock bootloader again with unlock_code.bin that you received from HTC or apply a new one.
Once unlocked, install TWRP 3.0.2-0, you can install any custom ROM that you like
Click to expand...
Click to collapse
I have to let you start 4.32.xxx After restoring the device. ? , He asked that the hboot 3.16.xxx I have is only for the version of KitKat?*
Don't start after restore 4.32.600.2, only boot to bootloader to install 4.32.600.2 firmware. This will get you to hboot 3.18.0000
Only after you installed firmware then only you can restart.
If this also you cannot follow the guide, I don't know how else to help you.
My first guide should be the easiest way but you keep saying it didn't boot. I believe because the guide was not followed accordingly.
@joikep - are you still around ? If yes, maybe you can help as it seems we have language barrier here.
ckpv5 said:
Don't start after restore 4.32.600.2, only boot to bootloader to install 4.32.600.2 firmware. This will get you to hboot 3.18.0000
Only after you installed firmware then only you can restart.
If this also you cannot follow the guide, I don't know how else to help you.
My first guide should be the easiest way but you keep saying it didn't boot. I believe because the guide was not followed accordingly.
@joikep - are you still around ? If yes, maybe you can help as it seems we have language barrier here.
Click to expand...
Click to collapse
if properly flash the firmware? , or failed normal? I appear in red letters 4.32.600.2 in bootloader , but start system , signal device is connected , but disconnects wifi and on every moment
(bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) Lock successfully...
(bootloader) deinit_lcd
(bootloader) mipi display off
(bootloader) mdp_clock_off
(bootloader) disable_mmss_clk done
(bootloader) pll1_disable done
(bootloader) TZ_HTC_SVC_DISABLE ret = 536739196 (0x1FFDFD7C)
(bootloader) [CRITICAL] SPMI write command failure: cmd_id =
0, error
(bootloader) = 4
(bootloader) [CRITICAL] SPMI write command failure: cmd_id =
0, error
(bootloader) = 4
(bootloader) [INFO] Rebooting device
FAILED (status read failed (No such file or directory))
finished. total time: 1.376s
C:\Users\mauricio\Downloads\One_M8_All-In-One_Kit_v\Data>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.031s]
finished. total time: 0.128s
C:\Users\mauricio\Downloads\One_M8_All-In-One_Kit_v\Data>fastboot flash fw_4.32.
600.2.zip
unknown partition 'fw_4.32.600.2.zip'
error: cannot determine image filename for 'fw_4.32.600.2.zip'
C:\Users\mauricio\Downloads\One_M8_All-In-One_Kit_v\Data>fastboot flash zip fw_4
.32.600.2.zip
target reported max download size of 1830711296 bytes
sending 'zip' (52971 KB)...
OKAY [ 2.455s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
(bootloader) checking hboot version...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) signature checking...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
finished. total time: 8.354s
C:\Users\mauricio\Downloads\One_M8_All-In-One_Kit_v\Data>fastboot reboot-bootloa
der
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.109

Getting back to stock for OTA update

Hello fellow XDA users!
I just bought my m8 and it came with Software status modified, bootloader unlocked, philz touch, S-on but Super CID.
The problem now is that i can't OTA and it is still in kitkat
So I started to work on it tonight, and I can't get it back to stock :
I have flashed TWRP, made a boot backup to create necessary folders, and downloaded a stock nandroid backup for my main version, 3.28.401.6.
Wiped the phone, restored the rom, flashed stock recovery and here in bootloader my software status is still modified, so no OTA possible.
Suppose it has something to do with superCID, but i can't modify it anymore as I'm not s-off and I don't know what is the stock CID for the phone, just bought it.
Sorry to create another boring thread about OTA updates btw, but I just can't understand what I'm doing wrong here (coming from a samsung device, but I've been reading a lot here, and still no luck about my situation.)
http://forum.xda-developers.com/showthread.php?t=2701376 this is the thread where I downloaded the Nandroid, if it has any importance... It is the one rooted but which has apparently no effect on OTA
http://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845 this seems interesting as I could maybe flash a RUU of same version to become unmodified but i'll ask you before doing anything stupid
Thank you all for your future answers
EDIT : Here are info from getvar all if you need (removed serialno and imei)
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.21.21331147A1.19_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.28.401.6
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B13000
(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: df77f8b7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.007s
WoBble12 said:
(bootloader) modelid: 0P6B13000
(bootloader) cidnum: 11111111
(bootloader) security: on
Click to expand...
Click to collapse
With the above current CID/MID ... you can only update to Marshmallow either with T-MOB US RUU or Developer Edition RUU as both work on MID 0P6B13000
You current software 3.28.401.6 won't do any good as that is workable for OTA when your MID is 0P6B10000
So if you want a EU version, you need to spend USD25 to S-Off the device, else just go for Developer Edition RUU.
Step 1 : install 6.12.1540.4 firmware
You can get the firmware and how-to : http://forum.xda-developers.com/showpost.php?p=60218734&postcount=5
Step 2 : install 6.12.1540.4 RUU
Download : http://www.htc.com/us/support/htc-one-m8/news/
Ok, thank you for the quick reply!
I was mistaken by the back plate of the device saying OP6B100, so didn't verify the mid in the adb log...
Now for a few questions, what are the differences between the dev version and the European one? Anything related to getting signal or something?
If I just update fw and rom with your two links, it will work even with my software status says "modified"? And Will it change back to official status?
Are updates going to be better if I go s-off and european again or is it the exact same version?
1. I don't see any significant difference with EU and Dev Ed except the obvious radio config.
But both worked fine for me in Asia region.
2. You should get the official status.
3. I don't see a point to S-Off as there is no more further OTA offered by HTC.
Once you updated to Marshmallow, you can always unlock the bootloader and install any custom ROM that you like. Most important is to have Marshmallow firmware (or at least Lollipop), doesn't matter whether it is EU or Dev Ed.
Ok, thanks again for the replies! Will try dev software, and if it doesn't work I'll pay for s-off
Ok so... I tried to update firmware, followed the tutorial, but i'm stuck at flashing the RUU. I went to the link you sent me, downloaded the 1.4 GB file, and now I have a zip file and a .exe file. The .exe will just start, say me it installs installshield, ask me to agree with the terms of licence, and close.
So I searched a bit, and i tried to flash the RUU as I did for the firmware, but now rebooting just leads me to a black screen, and the RUU fails.
please tell me what I did wrong so I can fix it.
Here is the ADB output :
C:\adb>fastboot flash zip RUU.zip
target reported max download size of 1826418688 bytes
sending 'zip' (1217690 KB)...
OKAY [ 34.178s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 79.165s
You can't use generic fastboot.exe to flash the RUU.zip, you need to use htc_fastboot.exe
Read this : http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
but use your RUU.zip (not the one in the guide)
sorry to bother for this but what is my RUU.zip you are talking about?
And i've tried with HTC fastboot and no luck neither...
You mentioned these above
C:\adb>fastboot flash zip RUU.zip
target reported max download size of 1826418688 bytes
sending 'zip' (1217690 KB)...
OKAY [ 34.178s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 79.165s​
So I thought that you have a RUU zip.
Since you can't run RUU.exe (due to either USB2.0 is not available or lack of HTC USB Drivers and some Microsoft files in your PC), you can do this :
Run the RUU.exe, when it opens where you can see the dialog box for you to accept agreement ..
Open your windows temp folder ( in windows run dialog, type %temp% )
You'll see two newly created folder, one of them has a file named rom.zip
Copy this rom.zip to your fastboot folder ... this is your RUU.zip
Can you post your current fastboot getvar result ? Need to see that you successfully installed the firmware.zip
ckpv5 said:
You mentioned these above
C:\adb>fastboot flash zip RUU.zip
target reported max download size of 1826418688 bytes
sending 'zip' (1217690 KB)...
OKAY [ 34.178s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 79.165s​
So I thought that you have a RUU zip.
Since you can't run RUU.exe (due to either USB2.0 is not available or lack of HTC USB Drivers and some Microsoft files in your PC), you can do this :
Run the RUU.exe, when it opens where you can see the dialog box for you to accept agreement ..
Open your windows temp folder ( in windows run dialog, type %temp% )
You'll see two newly created folder, one of them has a file named rom.zip
Copy this rom.zip to your fastboot folder ... this is your RUU.zip
Click to expand...
Click to collapse
Ok, just saw this at the moment on another thread, was going to try with the %temp% method, the command you made bold was the RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4.zip file that I renamed to be able to flash it more easily lol, what a noob I am ^^ so i'm going to extract this rom.zip and flash it, hope it works now! all fastboot commands have to be replaced with "htc fastboot" now, or only the flashing one?
Once again, thank you! (Using the thanks button at each of your posts too, don't worry )
yes, I verified in bootloader it says OS-6.12.1540.4 !!! Win! now just estracting the Rom from the temp folder!
htc_fastboot only when flashing RUU.zip
Another method to install the RUU.zip once you copied out the rom.zip from Windows Temp folder.
1. rename the rom.zip to 0P6BIMG.zip
2. place it on root of your microsd (which is formatted to fat32)
3. boot to bootloader and select hboot
4. it will scan the file and ask whether you want to update
5. volume up to update and leave it to do its stuff until it is completed and ask you to reboot
6. after reboot, remove that 0P6BIMG.zip from your microsd (so it won't ask you again to update whenever you boot to bootloader/hboot)
ckpv5 said:
htc_fastboot only when flashing RUU.zip
Another method to install the RUU.zip once you copied out the rom.zip from Windows Temp folder.
1. rename the rom.zip to 0P6BIMG.zip
2. place it on root of your microsd (which is formatted to fat32)
3. boot to bootloader and select hboot
4. it will scan the file and ask whether you want to update
5. volume up to update and leave it to do its stuff until it is completed and ask you to reboot
6. after reboot, remove that 0P6BIMG.zip from your microsd (so it won't ask you again to update whenever you boot to bootloader/hboot)
Click to expand...
Click to collapse
I've done the 1st method, and now after a flash that went well, i'm stuck in bootloader, with os version bein written in red and showing two times the version number, second one in parenthesis.
Instead of having options to power down etc, I only have a orange RUU option which is selected but I can't validate with power button, and in ADB I did command to reboot to bootloader but not doing anything now...
When in RUU mode, you don't use adb .. use fastboot
fastboot reboot-bootloader
When you have OS written in red, that's usually means the firmware is not correctly installed.
Try to get to fastboot with the above command then reinstall firmware.zip
ckpv5 said:
When in RUU mode, you don't use adb .. use fastboot
fastboot reboot-bootloader
When you have OS written in red, that's usually means the firmware is not correctly installed.
Try to get to fastboot with the above command then reinstall firmware.zip
Click to expand...
Click to collapse
C:\adb>fastboot reboot-bootloader
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 8.033s
that's what I get...
And in bootloader actually I only have the variables and the "RUU" option highlighted in orange :/
Connect to PC so you can hear the connect/disconnect sound
Press & hold both power & volume up till you hear the disconnect sound
Release both button and press & hold volume down button, this should get you to hboot
(remove the microsd first as you have the RUU zip there)
that's what I get...
And in bootloader actually I only have the variables and the "RUU" option highlighted in orange​
Can you use the power button to select it to get to RUU mode then fastboot reboot-bootloader or press & hold buttons method ?
ckpv5 said:
Connect to PC so you can hear the connect/disconnect sound
Press & hold both power & volume up till you hear the disconnect sound
Release both button and press & hold volume down button, this should get you to hboot
(remove the microsd first as you have the RUU zip there)
Click to expand...
Click to collapse
I don't have the rom on micro sd for the moment, but just disconnected and reconnected to PC, now I'm on the RUU screen with the green bar being completed but not doing anything. Should I try to re launch a command line and reflash the rom.zip?
WoBble12 said:
I don't have the rom one micro sd for the moment, but just disconnected and reconnected to PC, now I'm on the RUU screen with the green bar being completed but not doing anything. Should I try to re launch a command line and reflash the rom.zip?
Click to expand...
Click to collapse
Run command fastboot reboot-bootloader
to get to bootloader
check the OS now written in red or green
if red, reflash firmware.zip not rom/RUU.zip
if green .. just reboot and wait for awhile and see how it goes.
if it is stuck after 10 minutes .. reflash RUU/rom zip
I'm now on marshmallow! Tastes sweet lol!
Can't test the signal at the moment as I have to cut my micro SD to the right size, and I have no time for it. I will do this tomorrow , and reply back here to say if it worked. Anyway, couldn't have done this without you so big thanks for this and big thanks to all the XDA community!
WoBble12 said:
....I have to cut my micro SD to the right size....
Click to expand...
Click to collapse
Hehe .. I believe you wanted to say to cut SIM card, not microSD
Great to know you managed to update.
Yes of course, simcard ^^
So I can now say that the phone is working and I have signal through my card.
Only weird thing is that after installing a few apps, system is taking up 8+ gig's of storage, which seems really big to me. But hey, it's a 32gig's one so I'm not afraid

Categories

Resources