Entering recovery - One (M8) Q&A, Help & Troubleshooting

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

Related

Unable to return to stock

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

[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.

[Q] Upgrading To 2.10.709.1 Help

Greetings to all of you
i need little help since i'm a new HTC User
first of all , my phone is :
S-On , Rooted , Unlocked Bootloader , TWRP & finally on stock base 1.40.709.8
CID : HTC_621
MID : 0PJA10000
now i need to update to latest base " 2.10.709.1 "
how to do so step by step ??
EDIT :
i read here on XDA " If your device is S-ON , then you cannot flash an RUU with version less than your phone's current version . The same applies for hboot version "
Amr Nasser said:
Greetings to all of you
i need little help
i'm a new HTC User , I've HTC M9
first of all , my phone is :
S-On , Rooted , Unlocked Bootloader , TWRP & finally on Lee Droid Rom base 1.40.401.8
CID : HTC_621
MID : 0PJA10000
now i need to update to latest 2.10.401.1
how to do so step by step ??
Click to expand...
Click to collapse
Either you S-OFF with sunshine (costs 25 USD) so you can flash the leaked firmware or you wait untill the official OTA gets distributed by HTC. If you choose to do the latter you need to restore your system to stock, unrooted, read-only state by flashing a RUU or restoring a stock backup and reflashing the stock recovery.
Important
Flippy498 said:
Either you S-OFF with sunshine (costs 25 USD) so you can flash the leaked firmware or you wait untill the official OTA gets distributed by HTC. If you choose to do the latter you need to restore your system to stock, unrooted, read-only state by flashing a RUU or restoring a stock backup and reflashing the stock recovery.
Click to expand...
Click to collapse
this posted yesterday :
http://forum.xda-developers.com/showpost.php?p=61995182&postcount=373
i have the same MID & CID
does it mean if i get back to stock 1.40.401.8 , i can use that OTA To get 2.10.401.1 ??
Amr Nasser said:
this posted yesterday :
http://forum.xda-developers.com/showpost.php?p=61995182&postcount=373
i have the same MID & CID
does it mean if i get back to stock 1.40.401.8 , i can use that OTA To get 2.10.401.1 ??
Click to expand...
Click to collapse
The update from the link is for the Asian SKU 709. If you go back to a stock version with the SKU 401 you can only use updates with the same SKU and the update for firmware 2.10.401.1 has not been realesed officially untill now.
Edit: Maybe I understood you wrong. What is your actual firmware version? I mean the one that is stated in the download mode in the line with "OS" at the beginning. That is the firmware you need to look for if you want to get back to stock. The one in settings>about only tells you the base of the rom you are using.
Important
Flippy498 said:
The update from the link is for the Asian SKU 709. If you go back to a stock version with the SKU 401 you can only use updates with the same SKU and the update for firmware 2.10.401.1 has not been realesed officially untill now.
Edit: Maybe I understood you wrong. What is your actual firmware version? I mean the one that is stated in the download mode in the line with "OS" at the beginning. That is the firmware you need to look for if you want to get back to stock. The one in settings>about only tells you the base of the rom you are using.
Click to expand...
Click to collapse
i will go back to stock 1.40.709.8 ?? then update to 2.10.709.1 ?? both are Asian
will this work , i think they are same SKU now ??
Amr Nasser said:
i will go back to stock 1.40.709.8 ?? then update to 2.10.709.1 ?? both are Asian
will this work , i think they are same SKU now ??
Click to expand...
Click to collapse
Your phone is S-ON so you can only go back to the stock firmware that belongs to your phones SKU. You need to look at the "OS" line in download mode if you want to know which SKU versions you can use.
Amr Nasser said:
Greetings to all of you
i need little help
i'm a new HTC User , I've HTC M9
first of all , my phone is :
S-On , Rooted , Unlocked Bootloader , TWRP & finally on Lee Droid Rom base 1.40.401.8
CID : HTC_621
MID : 0PJA10000
now i need to update to latest 2.10.401.1
how to do so step by step ??
Click to expand...
Click to collapse
Since you're s-on, you're already on .709 firmware. There is no way you could be on anything else because it would not flash. Still, you should reboot to download mode and see what it says. If it's 1.32.709 as I expect, proceed.
1. Use Titanium Backup to back up all your user data and apps to your external sdcard; remove it.
2. Relock and run the existing RUU for your phone (this will wipe everything). Link is in this thread; follow instructions in the OP.
3. Wait until the OTA shows up and install.
4. Unlock and reroot, then restore your backed up data and apps.
Important
iElvis said:
Since you're s-on, you're already on .709 firmware. There is no way you could be on anything else because it would not flash. Still, you should reboot to download mode and see what it says. If it's 1.32.709 as I expect, proceed.
1. Use Titanium Backup to back up all your user data and apps to your external sdcard; remove it.
2. Relock and run the existing RUU for your phone (this will wipe everything). Link is in this thread; follow instructions in the OP.
3. Wait until the OTA shows up and install.
4. Unlock and reroot, then restore your backed up data and apps.
Click to expand...
Click to collapse
when i entered download mode , my OS showed me 1.40.709.8
so i assume now ,
relock my bootloader , run RUU 1.32.709 then OTA from my phone till i reach 1.40.709.8 and then i use the OTA in this thread to upgrade to 2.10.709.1 :
http://forum.xda-developers.com/showpost.php?p=61995182&postcount=373
then i can Unlock again and install TWRP and so on ,, am i right ??
Amr Nasser said:
when i entered download mode , my OS showed me 1.40.709.8
so i assume now ,
relock my bootloader , run RUU 1.32.709 then OTA from my phone till i reach 1.40.709.8 and then i use the OTA in this thread to upgrade to 2.10.709.1 :
http://forum.xda-developers.com/showpost.php?p=61995182&postcount=373
then i can Unlock again and install TWRP and so on ,, am i right ??
Click to expand...
Click to collapse
Correct. Although I think there is no need to flash the last OTA manually. You can update via the OTA function until you reach 2.10.709.1 since it's been released officially.
Amr Nasser said:
when i entered download mode , my OS showed me 1.40.709.8
so i assume now ,
relock my bootloader , run RUU 1.32.709 then OTA from my phone till i reach 1.40.709.8 and then i use the OTA in this thread to upgrade to 2.10.709.1 :
http://forum.xda-developers.com/showpost.php?p=61995182&postcount=373
then i can Unlock again and install TWRP and so on ,, am i right ??
Click to expand...
Click to collapse
No. If you're on 1.40, the 1.32 RUU will not flash because you're s-on—you can't downgrade. You need to find the 1.40.709 RUU. Let me look around.
Edit: It doesn't seem to be posted anywhere I can find. You need to get back to stock to flash an OTA. I think your only option unless HTC releases a RUU for 2.10.709 may be to s-off and update manually.
iElvis said:
No. If you're on 1.40, the 1.32 RUU will not flash because you're s-on—you can't downgrade. You need to find the 1.40.709 RUU. Let me look around.
Edit: It doesn't seem to be posted anywhere I can find. You need to get back to stock to flash an OTA. I think your only option unless HTC releases a RUU for 2.10.709 may be to s-off and update manually.
Click to expand...
Click to collapse
Actually downgrading with S-ON is possible as long as the bootloader version doesn't need to be downgraded, too (source). Just checked on my phone that the aboot is even with the 2.7.401.1 firmware still on version 1.0.0.0000. So there should be no problem.
Flippy498 said:
Actually downgrading with S-ON is possible as long as the bootloader version doesn't need to be downgraded, too (source). Just checked on my phone that the aboot is even with the 2.7.401.1 firmware still on version 1.0.0.0000. So there should be no problem.
Click to expand...
Click to collapse
That's interesting, thanks. Didn't use to be that way.
Important
Flippy498 said:
Actually downgrading with S-ON is possible as long as the bootloader version doesn't need to be downgraded, too (source). Just checked on my phone that the aboot is even with the 2.7.401.1 firmware still on version 1.0.0.0000. So there should be no problem.
Click to expand...
Click to collapse
i relocked my bootloader then tried to flash RUU with these orders :
fastboot oem rebootRUU
fastboot flash zip 0PJAIMG.zip
i got this error every time :
target reported max download size of 800000000 bytes
Invalid sparse file format at header magi
and i can't flash RUU
any ideas ??
Amr Nasser said:
i relocked my bootloader then tried to flash RUU with these orders :
fastboot oem rebootRUU
fastboot flash zip 0PJAIMG.zip
i got this error every time :
target reported max download size of 800000000 bytes
Invalid sparse file format at header magi
and i can't flash RUU
any ideas ??
Click to expand...
Click to collapse
Download and use HTC_fast boot.exe instead of facebook.exe. you can find HTC_fastboot by searching the forum. Just place it on the same folder as your current fastboot.exe file.
Command are the same except instead of typing "fastboot flash..." It's "HTC_fastboot flash..."
Edit: this is because regular fastboot can't handle files over 2GB.
Important
Flippy498 said:
Actually downgrading with S-ON is possible as long as the bootloader version doesn't need to be downgraded, too (source). Just checked on my phone that the aboot is even with the 2.7.401.1 firmware still on version 1.0.0.0000. So there should be no problem.
Click to expand...
Click to collapse
jollywhitefoot said:
Download and use HTC_fast boot.exe instead of facebook.exe. you can find HTC_fastboot by searching the forum. Just place it on the same folder as your current fastboot.exe file.
Command are the same except instead of typing "fastboot flash..." It's "HTC_fastboot flash..."
Edit: this is because regular fastboot can't handle files over 2GB.
Click to expand...
Click to collapse
that's worked , but now i got this error :
C:\Users\Amr\Desktop\Squabbi's Toolkit\adb>htc_fastboot oem rebootRUU
... OKAY
Execution time is 206(ms)
C:\Users\Amr\Desktop\Squabbi's Toolkit\adb>htc_fastboot flash zip 0PJAIMG.zip
< waiting for device >
sending 'zip'... (250395 KB) OKAY
sending time = 10.592 secs
writing 'zip'... (bootloader) HOSD CL#553039
(bootloader) ERR [SD_UPDATE_ERR] Main version NOT ALLOWED
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 19
(bootloader) ERR Update zip file failed.
(bootloader) ERR ZIP ERROR, exit read zip loop
(bootloader) ERR ZIP signature checking failed...
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 19
(bootloader) [email protected]
FAIL19: fail to flash via downloadzip
FAILED (remote: 19: fail to flash via downloadzip)
Execution time is 19(s)
i've S-On , and my bootloader is " RELOCKED " >> if this can help
Edit :
i've " Relocked " My bootloader through
reboot bootloader
then download mode
fastboot oem lock
any ideas ??
Amr Nasser said:
that's worked , but now i got this error :
C:\Users\Amr\Desktop\Squabbi's Toolkit\adb>htc_fastboot oem rebootRUU
... OKAY
Execution time is 206(ms)
C:\Users\Amr\Desktop\Squabbi's Toolkit\adb>htc_fastboot flash zip 0PJAIMG.zip
< waiting for device >
sending 'zip'... (250395 KB) OKAY
sending time = 10.592 secs
writing 'zip'... (bootloader) HOSD CL#553039
(bootloader) ERR [SD_UPDATE_ERR] Main version NOT ALLOWED
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 19
(bootloader) ERR Update zip file failed.
(bootloader) ERR ZIP ERROR, exit read zip loop
(bootloader) ERR ZIP signature checking failed...
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 19
(bootloader) [email protected]
FAIL19: fail to flash via downloadzip
FAILED (remote: 19: fail to flash via downloadzip)
Execution time is 19(s)
i've S-On , and my bootloader is " RELOCKED " >> if this can help
Edit :
i've " Relocked " My bootloader through
reboot bootloader
then download mode
fastboot oem lock
any ideas ??
Click to expand...
Click to collapse
Main version not allowed looks like its saying you can't downgrade. Maybe the bootloader version changed.
Amr Nasser said:
that's worked , but now i got this error :
C:\Users\Amr\Desktop\Squabbi's Toolkit\adb>htc_fastboot oem rebootRUU
... OKAY
Execution time is 206(ms)
C:\Users\Amr\Desktop\Squabbi's Toolkit\adb>htc_fastboot flash zip 0PJAIMG.zip
< waiting for device >
sending 'zip'... (250395 KB) OKAY
sending time = 10.592 secs
writing 'zip'... (bootloader) HOSD CL#553039
(bootloader) ERR [SD_UPDATE_ERR] Main version NOT ALLOWED
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 19
(bootloader) ERR Update zip file failed.
(bootloader) ERR ZIP ERROR, exit read zip loop
(bootloader) ERR ZIP signature checking failed...
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 19
(bootloader) [email protected]
FAIL19: fail to flash via downloadzip
FAILED (remote: 19: fail to flash via downloadzip)
Execution time is 19(s)
i've S-On , and my bootloader is " RELOCKED " >> if this can help
Edit :
i've " Relocked " My bootloader through
reboot bootloader
then download mode
fastboot oem lock
any ideas ??
Click to expand...
Click to collapse
Which RUU did you try to flash? As far as I know there is one for 1.32.709.6 and one for 1.36.709.3. Best case scenario would be you downloaded a wrong RUU. Worst case scenario would be that downgrading is (in contrast to the post I linked earlier) not aboot dependent and not possible if the software numbers (in your case the 40 you want to downgrade to 32 or 36) differ.
iElvis said:
No. If you're on 1.40, the 1.32 RUU will not flash because you're s-on—you can't downgrade. You need to find the 1.40.709 RUU. Let me look around.
Edit: It doesn't seem to be posted anywhere I can find. You need to get back to stock to flash an OTA. I think your only option unless HTC releases a RUU for 2.10.709 may be to s-off and update manually.
Click to expand...
Click to collapse
mY RECOMMENDATION IS TO WAIT UNTIL DE 2.10 RUU ZIP AND DO THE SCARD METHOD, IS SAFE FAST AND THEN YOU GOT A FULL STOCK CLEAN OF BLOATWARE, ALSO IYOU WILL BECOME OFFICIAL STOCK, YOU WOULD HAVE TO ROOT AGAIN AND FLASH TWRP. NO S-OFF REQUIERED.
Important
jollywhitefoot said:
Main version not allowed looks like its saying you can't downgrade. Maybe the bootloader version changed.
Click to expand...
Click to collapse
i searched the internet and found a nandroid backup which was the same stock rom my device was running
now i restored it via TWRP , everything is perfect now
so now , i've stock 1.40.709.8 base
Unlocked , TWRP Recovery , Rooted , S-On
And i got OTA Notification to update to 2.10.709.1 >> downloaded it >> but it doesn't install >> i know that i must flash stock recovery and " RELOCK " bootloader
can anyone provide me stock recovery for 1.40.709.8 ??
what is the next steps i have to do , because when i " RELOCK " my bootloader >> device start in bootloader mode and don't boot and i have to unlock it again so it can boot , what causes this ??
EDIT :
can i just flash OTA zip file via TWRP or i can't ??
Amr Nasser said:
i searched the internet and found a nandroid backup which was the same stock rom my device was running
now i restored it via TWRP , everything is perfect now
so now , i've stock 1.40.709.8 base
Unlocked , TWRP Recovery , Rooted , S-On
And i got OTA Notification to update to 2.10.709.1 >> downloaded it >> but it doesn't install >> i know that i must flash stock recovery and " RELOCK " bootloader
can anyone provide me stock recovery for 1.40.709.8 ??
what is the next steps i have to do , because when i " RELOCK " my bootloader >> device start in bootloader mode and don't boot and i have to unlock it again so it can boot , what causes this ??
EDIT :
can i just flash OTA zip file via TWRP or i can't ??
Click to expand...
Click to collapse
Flashing OTAs with TWRP isn't possible but you can use the recovery that is placed in the OTA. The OTA can be found in
Code:
/data/data/com.htc.updater/files/
Just copy it to your pc and open the zip file. The recovery can be found in one of the subfolders. Next step would be making a TWRP backup with only recovery checked. After the backup has finished you need to copy it to your pc, too. Now you need to rename the stock recovery you grabbed from the OTA to
Code:
recovery.emmc.win
and replace the recovery in the backup with the renamed file. Next you need to copy the backup back to your phone and restore it with TWRP. When you reboot now TWRP will be replaced by the stock recovery and you should be able to install the OTA. I'm not sure whether it is necessary to relock for the update with S-ON. With S-OFF it is actually not needed.
Edit: I missed the part where you stated that you're still rooted and assumed that you restored a "read-only backup". My instructions won't work until you restored a stock, unrooted and read-only system beforehand.

(solved)Help with update To android M

Today I received the android m update I download it and install stock recovery so I can install the update But every Time I do it gets to the half of the bar and then says install aborted I have tried factory reset and wipe cache nothing worked
I had twrp recovery before And every time I get any update I replace the twrp with stock recovery and it always worked for me until today
Any solution please?????
What did you use TWRP for, or better asked what did you change on your system? Has your system been rooted or the system.img been manipulated in any kind?
Send by the swarm intelligence of my coffee machine (AKA HTC One M9).
HTCNerdYoda said:
What did you use TWRP for, or better asked what did you change on your system? Has your system been rooted or the system.img been manipulated in any kind?
Send by the swarm intelligence of my coffee machine (AKA HTC One M9).
Click to expand...
Click to collapse
I used TWRP for root access and yes my system Is rooted but and boot loader unlocked for reinstalling stock recovery was working before and the updates were installed successfully
OTA failure
My device is not rooted and today I tried to upgrade to marshmallow (ota) but it failed to do so after 80% it aborted the installation and now I'm stuck with a dump phone please help I'm not familiar with this kind of situation. I tried to wipe cache partition and wipe data/factory reset but nothing works. IT says on the screen:
Android Recovery
HTC/htc_m8/htc_m8
6.0/MRA58K/buildteam12171409
user/release-keys
Use volume up/down and power.
-----------------------------------------
Reboot system now
Reboot to bootloader
Apply update from ADB
Apply update from SD card
Wipe data/factory reset
Wipe cache partition
Power off
-----------------------------------------
Supported API: 3
handle_cota_install: install cwpkg to/c
ache/data/cwtemp/cwpkg.zip
handle_cota_install: install cwprop to /
cache/data/cwtemp/cw.prop
Write host_mode success
handle_cota_install: No CW files. Skip c
w installation.
ecmelg said:
My device is not rooted and today I tried to upgrade to marshmallow (ota) but it failed to do so after 80% it aborted the installation and now I'm stuck with a dump phone please help I'm not familiar with this kind of situation. I tried to wipe cache partition and wipe data/factory reset but nothing works. IT says on the screen:
Android Recovery
HTC/htc_m8/htc_m8
6.0/MRA58K/buildteam12171409
user/release-keys
Use volume up/down and power.
-----------------------------------------
Reboot system now
Reboot to bootloader
Apply update from ADB
Apply update from SD card
Wipe data/factory reset
Wipe cache partition
Power off
-----------------------------------------
Supported API: 3
handle_cota_install: install cwpkg to/c
ache/data/cwtemp/cwpkg.zip
handle_cota_install: install cwprop to /
cache/data/cwtemp/cw.prop
Write host_mode success
handle_cota_install: No CW files. Skip c
w installation.
Click to expand...
Click to collapse
Try flashing RUU for ur model id.
Alxens said:
I used TWRP for root access and yes my system Is rooted but and boot loader unlocked for reinstalling stock recovery was working before and the updates were installed successfully
Click to expand...
Click to collapse
If it is rooted the OTA won't be installed as the system partition and thus it's md5 has been changed by mounting it r/w and flashing SuperSU. This is as google and HTC following this guidelines changed the OTA delivery to a block based system where the routine checks if the system has been untouched prior to installing it. You got to restore the untouched image of the system partition for your device. After this you could flash the stock recovery and install the OTA.
Send by the swarm intelligence of my coffee machine (AKA HTC One M9).
HTCNerdYoda said:
If it is rooted the OTA won't be installed as the system partition and thus it's md5 has been changed by mounting it r/w and flashing SuperSU. This is as google and HTC following this guidelines changed the OTA delivery to a block based system where the routine checks if the system has been untouched prior to installing it. You got to restore the untouched image of the system partition for your device. After this you could flash the stock recovery and install the OTA.
Send by the swarm intelligence of my coffee machine (AKA HTC One M9).
Click to expand...
Click to collapse
I have twrp backup system
would this work??
Alxens said:
Today I received the android m update I download it and install stock recovery so I can install the update But every Time I do it gets to the half of the bar and then says install aborted I have tried factory reset and wipe cache nothing worked
I had twrp recovery before And every time I get any update I replace the twrp with stock recovery and it always worked for me until today
Any solution please?????
Click to expand...
Click to collapse
Esta solución me sirvió a mi. www . htc.com/us/support/rom- downloads . html (saca los espacios) en tú caso descarga la versión desbloqueada
Yes would work
Send by the swarm intelligence of my coffee machine (AKA HTC One M9).
I'm having the same problem. I don't have a ROOT and already talked to the HTC help desk and didn't find any solution. With this TWRP can I fix this problem?
sonoman87 said:
I'm having the same problem. I don't have a ROOT and already talked to the HTC help desk and didn't find any solution. With this TWRP can I fix this problem?
Click to expand...
Click to collapse
Most likely NO.
The above user(s) used TWRP backups to remove changes that were done by root.
Since you never rooted (from the sounds of it) you don't have the same problem.
redpoint73 said:
Most likely NO.
The above user(s) used TWRP backups to remove changes that were done by root.
Since you never rooted (from the sounds of it) you don't have the same problem.
Click to expand...
Click to collapse
Thanks redpoint73. So, what do you recommend me to do now? Because, the problem started with the android notification of the update and then the system crashed. Search for a ROM and try to install it?
Thanks again!
sonoman87 said:
Thanks redpoint73. So, what do you recommend me to do now? Because, the problem started with the android notification of the update and then the system crashed. Search for a ROM and try to install it?
Click to expand...
Click to collapse
If there is a MM RUU for your version, download and run it.
redpoint73 said:
If there is a MM RUU for your version, download and run it.
Click to expand...
Click to collapse
I've fixed it! Thanks so much again!
sonoman87 said:
I've fixed it! Thanks so much again!
Click to expand...
Click to collapse
Which country are you from? And which ROM did you use? I'm from Spain and I'm afraid if I install the ROM it wouldn't work again in my country
oscar1355 said:
Which country are you from? And which ROM did you use? I'm from Spain and I'm afraid if I install the ROM it wouldn't work again in my country
Click to expand...
Click to collapse
First of all, you need to understand that ROM and RUU are two very different things.
Also, nobody can advise you the proper RUU is, without knowing some basic information. Namely, do fastboot getvar all, and post the output (delete IMEI and serial number before posting).
Hey everyone,
I am trying to get my M8 to stock (been stuck at this for about 10 days now, tried everything). I am from India. There was some problem and I accidentally have a phone now with no OS and TWRP. I have installed stock recovery and plan to flash the ROM/RUU. Some details of my device:
Software status: Modified
Unlocked S-ON
C:\Android>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:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: <serial number>
(bootloader) imei: <imei number>
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B65000
(bootloader) cidnum: HTC__038
(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: 205bdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I would really appreciate it if you could guide me how to get my phone to stock OS. The ROM that I should prefer etc. I have been going through a lot of forums and ended up being utterly confused.
Thanks in advance for the help!
skull_143 said:
been stuck at this for about 10 days now, tried everything
There was some problem and I accidentally have a phone now with no OS and TWRP.
Click to expand...
Click to collapse
Sorry, this is a pet peeve of mine, but I really wish folks would stop posting they "tried everything". This literally tells us nothing, and you should list specifically one-by-one (and in detail) what things you tried, and the results (again in detail) of each.
"Accidentally" appears to mean you unlocked the bootloader, then flashed an very old, obsolete version TWRP (which causes the main version to be blank) then decided it was a good idea to wipe the OS (system)? Again, you need to tell us exactly what steps you took to get to this point.
My next advice to you, is to only do things that are specifically instructed for you to do in your situation. Don't guess or do things without fully understanding them. As your present situation seems to indicate you don't have a very good understanding of what you are doing, and only making matter worse by proceeding with insufficient knowledge.
skull_143 said:
I have installed stock recovery and plan to flash the ROM/RUU. Some details of my device
Click to expand...
Click to collapse
RUU will only work if its version 6.15.720.2
Your version (CID and MID) is rather obscure, so I'm not sure whether such RUU exists or not. If not, your best bet is to get TWRP back on the phone, and restore the stock nandroid 6.15.720.2 using the files and instructions on the following thread: http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Also, flashing stock recovery is not needed to RUU; and not helpful in your current situation (you'll probably need to go back to custom recovery TWRP).
redpoint73 said:
Sorry, this is a pet peeve of mine, but I really wish folks would stop posting they "tried everything". This literally tells us nothing, and you should list specifically one-by-one (and in detail) what things you tried, and the results (again in detail) of each.
"Accidentally" appears to mean you unlocked the bootloader, then flashed an very old, obsolete version TWRP (which causes the main version to be blank) then decided it was a good idea to wipe the OS (system)? Again, you need to tell us exactly what steps you took to get to this point.
My next advice to you, is to only do things that are specifically instructed for you to do in your situation. Don't guess or do things without fully understanding them. As your present situation seems to indicate you don't have a very good understanding of what you are doing, and only making matter worse by proceeding with insufficient knowledge.
RUU will only work if its version 6.15.720.2
Your version (CID and MID) is rather obscure, so I'm not sure whether such RUU exists or not. If not, your best bet is to get TWRP back on the phone, and restore the stock nandroid 6.15.720.2 using the files and instructions on the following thread: http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Also, flashing stock recovery is not needed to RUU; and not helpful in your current situation (you'll probably need to go back to custom recovery TWRP).
Click to expand...
Click to collapse
Sorry about the shortened version, just though it might be too big and unnecessary. Okay here goes what happened. I moved the whatsapp media to my laptop (at this time the device was unrooted and running stock android M updated over OTA). After the move, the device was stuck at the splash screen with HTC logo. After this I gave the phone to a service centre (not official HTC) and asked them to NOT root and put stock OS and get the phone working. What they did was, rooted it and installed a custom ROM with TWRM recovery (which was very screwed up, as in the camera kept crashing and I couldn't even use that). So, I decided to get it back to stock ROM and sense UI.
So what I did was looked up some thread (not sure which one) and went ahead to do a wipe through recovery. Here I did the mistake of wiping everything and so the device doesn't have any OS at the moment. The phone is still getting stuck in HTC logo now (obviously as it doesn't have an OS). I have tried to do the following:
1. To flash the boot only using fastboot flash boot and fastboot flash zip commands. The version I tried was stock 3.35.720.1_recovery.img. This didnt seem to work.
2. Next tried to go to usb fastboot mode and tried to run the RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4.exe official one from the laptop. But it showed some mismatch of versions and aborted.
3. Then I read that stock could only be flashed on S-ON devices if we relock the bootloader. So used the fastboot oem relock command to relock bootloader and then tried both the above but didn't work.
4. Next saw somewhere that it is pretty impossible to flash on a locked S-ON device. So went to htcdev and got the bootloader unlocked again.
5. Downloaded a stock image 3.35.720.1 Stock Unrooted. Read that we need lower or same stock recovery to flash the same and so flashed the stock recovery of the same version. Next extracted the .win001 and .win002 files using the tar command and finally put them along with META_INF folder and boot.img files into a zip file. The image had the contents of the system folder and tried to flash this using fastboot and also through the stock option "Update from SD card". Got error "E: footer is wrong. E: update signature verification failed".
This is the status so far. I am not sure what I should be doing anymore. Hope this helps in understanding the situation. Sorry it's so long.
Please advice what I should do now. Currently, I have stock recovery installed and no OS. I just want to have the stock sense OS on the device.
Thanks for all your time.
skull_143 said:
Please advice what I should do now. Currently, I have stock recovery installed and no OS. I just want to have the stock sense OS on the device.
Thanks for all your time.
Click to expand...
Click to collapse
1. Download the 6.15.720.2 RUU.zip : http://forum.xda-developers.com/showpost.php?p=66309774&postcount=20
2. relock the bootloader with command - fastboot oem lock
option 1 - if you have a microsd
1. rename the downloaded RUU.zip as to 0P6BIMG.zip
2. put it on root of your microsd not in any folder
3. on bootloader select hboot - it will scan the zip and ask you to update.
4. select volume up to update
5. once completed, delete the zip from microsd
option 2
1. Download htc_fastboot.exe : https://drive.google.com/file/d/0B8L4pkbzdlR3eTlJSjdKVEdHX1U/view
2. put both htc_fastboot.exe and the 0P6BIMG.zip in your fastboot folder
3. run below commands :
fastboot reboot-bootloader (reboot to bootloader to ensure the connection is good)
fastboot oem rebootRUU (put the device in RUU mode)
htc_fastboot flash zip 0P6BIMG.zip (to install RUU - read it is htc_fastboot not fastboot)
Once complete - fastboot reboot
run setup .. done

how to upadate hboot from 3.16 to 3.19 ?

I tried rooting my device and at last I was succesfull but now I want to install the latest ROM but to install that I need to upgrade my hboot and I am not getting how to do that please somebody help me my phone is in S-ON mode and it's an At&t international version phone
sheikharfaz said:
I tried rooting my device and at last I was succesfull but now I want to install the latest ROM but to install that I need to upgrade my hboot and I am not getting how to do that please somebody help me my phone is in S-ON mode and it's an At&t international version phone
Click to expand...
Click to collapse
post the result of fastboot getvar all ( after removing serialno and mei )
sheikharfaz said:
I tried rooting my device and at last I was succesfull but now I want to install the latest ROM but to install that I need to upgrade my hboot and I am not getting how to do that please somebody help me my phone is in S-ON mode and it's an At&t international version phone
Click to expand...
Click to collapse
Your sequence is a bit mixed up. You should have updated firmware (hboot, radio, etc.) before unlocking bootloader. As you'll now have to relock the bootloader in order to update firmware. Then unlock it again, and TWRP again, to install custom ROM.
You also do not need root to flash custom ROMs (just need unlocked bootloader, custom recovery, and right firmware); unless you had another specific reason to root first?
Also, you will want all the updated firmware, not just hboot. As firmware contains a bunch of modules besides hboot, which will not play well with current ROMs (especially WiFi, Bluetooth, as well as radio and others). All the firmware installs in one zip, so it's not hard to do.
However, I agree with the previous post that we need more info on the phone. Fastboot getvar all, and post the results (delete IMEI and serial number before posting).
"At&t international version" is a contradiction. It's either one or the other, it can't be both.
redpoint73 said:
You should have updated firmware (hboot, radio, etc.) before unlocking bootloader. As you'll now have to relock the bootloader in order to update firmware.
Click to expand...
Click to collapse
Here's something I just learned recently (2 or 3 mos ago), although I haven't been able to test it myself since my M8 is S-Off.
When flashing an RUU.zip or signed firmware.zip from extSD instead of from your PC, relocking your bootloader isn't necessary.
Like I said, I haven't confirmed it myself, but the person who told me that I consider a reliable source. He was positive about it with M9, and quite sure it was the same with the M8.
redpoint73 said:
Your sequence is a bit mixed up. You should have updated firmware (hboot, radio, etc.) before unlocking bootloader. As you'll now have to relock the bootloader in order to update firmware. Then unlock it again, and TWRP again, to install custom ROM.
You also do not need root to flash custom ROMs (just need unlocked bootloader, custom recovery, and right firmware); unless you had another specific reason to root first?
Also, you will want all the updated firmware, not just hboot. As firmware contains a bunch of modules besides hboot, which will not play well with current ROMs (especially WiFi, Bluetooth, as well as radio and others). All the firmware installs in one zip, so it's not hard to do.
However, I agree with the previous post that we need more info on the phone. Fastboot getvar all, and post the results (delete IMEI and serial number before posting).
"At&t international version" is a contradiction. It's either one or the other, it can't be both.
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.21331931.LA11G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.58.502.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
(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: c3d94491
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.037s
redpoint73 said:
Your sequence is a bit mixed up. You should have updated firmware (hboot, radio, etc.) before unlocking bootloader. As you'll now have to relock the bootloader in order to update firmware. Then unlock it again, and TWRP again, to install custom ROM.
You also do not need root to flash custom ROMs (just need unlocked bootloader, custom recovery, and right firmware); unless you had another specific reason to root first?
Also, you will want all the updated firmware, not just hboot. As firmware contains a bunch of modules besides hboot, which will not play well with current ROMs (especially WiFi, Bluetooth, as well as radio and others). All the firmware installs in one zip, so it's not hard to do.
However, I agree with the previous post that we need more info on the phone. Fastboot getvar all, and post the results (delete IMEI and serial number before posting).
"At&t international version" is a contradiction. It's either one or the other, it can't be both.
Click to expand...
Click to collapse
Can i get what next i can do?
because i am not able to find the right firmware.Can you help me with that?
sheikharfaz said:
Can i get what next i can do?
because i am not able to find the right firmware.Can you help me with that?
Click to expand...
Click to collapse
remove serialno from the getvar result in your post above
i don't know what you want
you need the latest firmware to flash a custom rom or you need to flash the latest stock rom ( by using RUU ) ???
in all cases you need to flash the latest firmware first 6.20.502.5 ( it's the latest firmware for your AT&T device variant )
6.20.502.5 is marshmallow and it's the latest official OS for this device
note :- flashing the signed firmware will wipe your internal storage so make sure to backup your files
flash firmware
1-download this signed firmware https://mega.nz/#!XV5EjYhS!gNN_rAYovaMQpaeP2OSdkfYAIEAmv6VnB-QlZ1VadMU ( rename it to something short and easy if you like )
2- open a cmd window in the folder where the firmware located
3- relock the bootloader ( if it's unlocked ) by this commands
fastboot oem lock
fastboot reboot-bootloader
3- now start flashing the firmware using this commands and replace firmwarename with the actual firmware name
fastboot oem rebootRUU
fastboot flash zip firmwarename.zip
if you see FAILED (remote: 90 hboot pre-update! please flush image again immediately)
then repeat the flashing command again
fastboot flash zip firmwarename.zip
after it complete type
fastboot reboot-bootloader
flash custom rom
now you have the latest firmware if you want to flash a custom rom unlock the bootloader and flash twrp then flash the desired rom
flash stock rom using RUU.exe
if you want the latest stock rom RUU.exe it's available on htc website here http://www.htc.com/us/support/htc-one-m8-att/news/
direst link for the RUU http://dl3.htc.com.s3.amazonaws.com...70_ATT_MR_Cingular_US_6.20.502.5_combined.exe
after flash the firmware and do all the above commands run the RUU as a normal application and follow the setup wizard
sheikharfaz said:
(bootloader) version-main: 1.58.502.1
Click to expand...
Click to collapse
As suspected, you need to update all the firmware, not just hboot. Your firmware is still on the original 2014 release of Kitkat. This will cause many issues, even if you updated hboot. For instance, you would find WiFi would be broken on just about every current custom ROM around; due to the WiFi firmware partition on the phone being outdated, and not compatible with the current ROMs.
ahmed has the process outlined well. I would recommend to follow his instructions above.
ahmed.ismael said:
remove serialno from the getvar result in your post above
i don't know what you want
you need the latest firmware to flash a custom rom or you need to flash the latest stock rom ( by using RUU ) ???
in all cases you need to flash the latest firmware first 6.20.502.5 ( it's the latest firmware for your AT&T device variant )
6.20.502.5 is marshmallow and it's the latest official OS for this device
note :- flashing the signed firmware will wipe your internal storage so make sure to backup your files
flash firmware
1-download this signed firmware https://mega.nz/#!XV5EjYhS!gNN_rAYovaMQpaeP2OSdkfYAIEAmv6VnB-QlZ1VadMU ( rename it to something short and easy if you like )
2- open a cmd window in the folder where the firmware located
3- relock the bootloader ( if it's unlocked ) by this commands
fastboot oem lock
fastboot reboot-bootloader
3- now start flashing the firmware using this commands and replace firmwarename with the actual firmware name
fastboot oem rebootRUU
fastboot flash zip firmwarename.zip
if you see FAILED (remote: 90 hboot pre-update! please flush image again immediately)
then repeat the flashing command again
fastboot flash zip firmwarename.zip
after it complete type
fastboot reboot-bootloader
flash custom rom
now you have the latest firmware if you want to flash a custom rom unlock the bootloader and flash twrp then flash the desired rom
flash stock rom using RUU.exe
if you want the latest stock rom RUU.exe it's available on htc website here http://www.htc.com/us/support/htc-one-m8-att/news/
direst link for the RUU http://dl3.htc.com.s3.amazonaws.com...70_ATT_MR_Cingular_US_6.20.502.5_combined.exe
after flash the firmware and do all the above commands run the RUU as a normal application and follow the setup wizard
Click to expand...
Click to collapse
if you see FAILED (remote: 90 hboot pre-update! please flush image again immediately)
what does this mean ? which image should i flash?
sheikharfaz said:
if you see FAILED (remote: 90 hboot pre-update! please flush image again immediately)
what does this mean ? which image should i flash?
Click to expand...
Click to collapse
just do "fastboot flash zip *whatever you renamed it to*.zip" a second time without rebooting
ahmed.ismael said:
remove serialno from the getvar result in your post above
i don't know what you want
you need the latest firmware to flash a custom rom or you need to flash the latest stock rom ( by using RUU ) ???
in all cases you need to flash the latest firmware first 6.20.502.5 ( it's the latest firmware for your AT&T device variant )
6.20.502.5 is marshmallow and it's the latest official OS for this device
note :- flashing the signed firmware will wipe your internal storage so make sure to backup your files
flash firmware
1-download this signed firmware https://mega.nz/#!XV5EjYhS!gNN_rAYovaMQpaeP2OSdkfYAIEAmv6VnB-QlZ1VadMU ( rename it to something short and easy if you like )
2- open a cmd window in the folder where the firmware located
3- relock the bootloader ( if it's unlocked ) by this commands
fastboot oem lock
fastboot reboot-bootloader
3- now start flashing the firmware using this commands and replace firmwarename with the actual firmware name
fastboot oem rebootRUU
fastboot flash zip firmwarename.zip
if you see FAILED (remote: 90 hboot pre-update! please flush image again immediately)
then repeat the flashing command again
fastboot flash zip firmwarename.zip
after it complete type
fastboot reboot-bootloader
flash custom rom
now you have the latest firmware if you want to flash a custom rom unlock the bootloader and flash twrp then flash the desired rom
flash stock rom using RUU.exe
if you want the latest stock rom RUU.exe it's available on htc website here http://www.htc.com/us/support/htc-one-m8-att/news/
direst link for the RUU http://dl3.htc.com.s3.amazonaws.com...70_ATT_MR_Cingular_US_6.20.502.5_combined.exe
after flash the firmware and do all the above commands run the RUU as a normal application and follow the setup wizard
Click to expand...
Click to collapse
i am not able to unlock my device back
E:\new\android-sdk-windows\platform-tools>fastboot flash unlocktoken Unlock_code.bin
target reported max download size of 1826418688 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 0.133s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.144s
ahmed.ismael said:
remove serialno from the getvar result in your post above
i don't know what you want
you need the latest firmware to flash a custom rom or you need to flash the latest stock rom ( by using RUU ) ???
in all cases you need to flash the latest firmware first 6.20.502.5 ( it's the latest firmware for your AT&T device variant )
6.20.502.5 is marshmallow and it's the latest official OS for this device
note :- flashing the signed firmware will wipe your internal storage so make sure to backup your files
flash firmware
1-download this signed firmware https://mega.nz/#!XV5EjYhS!gNN_rAYovaMQpaeP2OSdkfYAIEAmv6VnB-QlZ1VadMU ( rename it to something short and easy if you like )
2- open a cmd window in the folder where the firmware located
3- relock the bootloader ( if it's unlocked ) by this commands
fastboot oem lock
fastboot reboot-bootloader
3- now start flashing the firmware using this commands and replace firmwarename with the actual firmware name
fastboot oem rebootRUU
fastboot flash zip firmwarename.zip
if you see FAILED (remote: 90 hboot pre-update! please flush image again immediately)
then repeat the flashing command again
fastboot flash zip firmwarename.zip
after it complete type
fastboot reboot-bootloader
flash custom rom
now you have the latest firmware if you want to flash a custom rom unlock the bootloader and flash twrp then flash the desired rom
flash stock rom using RUU.exe
if you want the latest stock rom RUU.exe it's available on htc website here http://www.htc.com/us/support/htc-one-m8-att/news/
direst link for the RUU http://dl3.htc.com.s3.amazonaws.com...70_ATT_MR_Cingular_US_6.20.502.5_combined.exe
after flash the firmware and do all the above commands run the RUU as a normal application and follow the setup wizard
Click to expand...
Click to collapse
stuck in bootloop after locking the device
i accidently mistyped fastboot reboot instead of fastboot reboot-bootloader
what shall i do now
xunholyx said:
just do "fastboot flash zip *whatever you renamed it to*.zip" a second time without rebooting
Click to expand...
Click to collapse
stuck in bootloop
what can i do?please help
ahmed.ismael said:
remove serialno from the getvar result in your post above
i don't know what you want
you need the latest firmware to flash a custom rom or you need to flash the latest stock rom ( by using RUU ) ???
in all cases you need to flash the latest firmware first 6.20.502.5 ( it's the latest firmware for your AT&T device variant )
6.20.502.5 is marshmallow and it's the latest official OS for this device
note :- flashing the signed firmware will wipe your internal storage so make sure to backup your files
flash firmware
1-download this signed firmware https://mega.nz/#!XV5EjYhS!gNN_rAYovaMQpaeP2OSdkfYAIEAmv6VnB-QlZ1VadMU ( rename it to something short and easy if you like )
2- open a cmd window in the folder where the firmware located
3- relock the bootloader ( if it's unlocked ) by this commands
fastboot oem lock
fastboot reboot-bootloader
3- now start flashing the firmware using this commands and replace firmwarename with the actual firmware name
fastboot oem rebootRUU
fastboot flash zip firmwarename.zip
if you see FAILED (remote: 90 hboot pre-update! please flush image again immediately)
then repeat the flashing command again
fastboot flash zip firmwarename.zip
after it complete type
fastboot reboot-bootloader
flash custom rom
now you have the latest firmware if you want to flash a custom rom unlock the bootloader and flash twrp then flash the desired rom
flash stock rom using RUU.exe
if you want the latest stock rom RUU.exe it's available on htc website here http://www.htc.com/us/support/htc-one-m8-att/news/
direst link for the RUU http://dl3.htc.com.s3.amazonaws.com...70_ATT_MR_Cingular_US_6.20.502.5_combined.exe
after flash the firmware and do all the above commands run the RUU as a normal application and follow the setup wizard
Click to expand...
Click to collapse
please send me next steps too.
sheikharfaz said:
stuck in bootloop
what can i do?please help
Click to expand...
Click to collapse
You flashed firmware first?
xunholyx said:
You flashed firmware first?
Click to expand...
Click to collapse
yes,now how do i come out of this bootloop ,there is nothing on screen except that htc logo
Okay. How long did you wait for it to boot up? I can take up to 20 mins sometimes. crazy I know
xunholyx said:
Okay. How long did you wait for it to boot up? I can take up to 20 mins sometimes. crazy I know
Click to expand...
Click to collapse
the battery got drained .so now i am able to get into bootloader .can i please get how to unloack bootloader .i have tried fastboot oem unlock and even
fastboot flash unlocktoken Unlock_code.bin
please help
sheikharfaz said:
the battery got drained .so now i am able to get into bootloader .can i please get how to unloack bootloader .i have tried fastboot oem unlock and even
fastboot flash unlocktoken Unlock_code.bin
please help
Click to expand...
Click to collapse
request another unlock_code
follow the steps to unlock the bootloader again on the hcdev website http://www.htcdev.com/bootloader/
sheikharfaz said:
can i please get how to unloack bootloader .i have tried fastboot oem unlock please help
Click to expand...
Click to collapse
This command doesn't work on the M8, it's not even worth trying. The whole point of the HTCDev.com bootloader unlock process, is due to the fact that HTC forbids unlocking the bootloader with that command. It only applies to certain devices.
You need to use the bin code command. If it doesn't work, just request a new bin code, like ahmed suggested.

Categories

Resources