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.
Related
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
Hello.
I am currently running ParanoidAndroid 4.6Beta5. Since PA's developement for M8 seems to be dead, I wanted to try CM12.
When I tried to install latest nightly build of CM12 I got a message that my bootloader (3.16) is not supported, and that I need to update it to 3.18 or 3.19.
I googled a bit and found out that in order to update it, I need to restore latest official ROM.
I managed to restore official ROM (3.28.401.6, based on android 4.4.4) but the WiFi wasn't working, so I couldn't do much there. I relocked bootloader and flashed official recovery, and then tried to run RUU.
RUU failed with code [315]. I ran out of ideas and google results to browse.
I unlocked my bootloader again, flashed clockworkmod recovery back, and restored my backup of ParanoidAndroid.
Right now the phone is in the same state as when I was starting.
Here is some basic info about my phone:
Model: HTC ONE M8 16GB Unlocked (purchased on amazon; network free)
CID: HTC_001
Bootloader: Unlocked
Recovery: Clockworkmod Touch v6.0.4.8
S status: S-ON
Click to expand...
Click to collapse
So the basic question is: how to flash CM12 on HTC One M8? I spent so many hours on it without any result, so this thread is my last chance.
Edit: SOLVED!
See http://forum.xda-developers.com/showpost.php?p=58859881&postcount=13 for solution.
ProTofik said:
Hello.
I am currently running ParanoidAndroid 4.6Beta5. Since PA's developement for M8 seems to be dead, I wanted to try CM12.
When I tried to install latest nightly build of CM12 I got a message that my bootloader (3.16) is not supported, and that I need to update it to 3.18 or 3.19.
I googled a bit and found out that in order to update it, I need to restore latest official ROM.
I managed to restore official ROM (3.28.401.6, based on android 4.4.4) but the WiFi wasn't working, so I couldn't do much there. I relocked bootloader and flashed official recovery, and then tried to run RUU.
RUU failed with code [315]. I ran out of ideas and google results to browse.
I unlocked my bootloader again, flashed clockworkmod recovery back, and restored my backup of ParanoidAndroid.
Right now the phone is in the same state as when I was starting.
Here is some basic info about my phone:
So the basic question is: how to flash CM12 on HTC One M8? I spent so many hours on it without any result, so this thread is my last chance.
Click to expand...
Click to collapse
Since you are S-On, you can't just flash the firmware, which is the easiest way. But you can use this method.
I'll give you an RUU to flash. But before you flash it, backup everything that is important to you, because this will wipe your phone.
Download this.
Rename it to 0P6BIMG.zip (that's a zero not the letter)
Put it onto the root of your extSD (By root of I mean just on the card and not a folder)
Boot into bootloader and choose hboot.
Follow the prompts (vol up to flash, power button to reboot when done)
Congratulations! You now have the latest lollipop firmware.
Make sure you delete the renamed zip from your extSD when you are done. If you don't delete it, it will try to update again every time you go back to hboot.
Since you are S-On, you can't just flash the firmware
Click to expand...
Click to collapse
What do you mean by firmware. Bootloader or ROM? I did 'just' flash PA without a problem.
I guess the ROM you liked is the latest official one. By installing it I will get my bootloader updated and then I will be able to flash CM12. Do I get this right? or will I get stuck on stock forever?
Edit: I just tried to flash your image using hboot but it didn't work. Check file attached.
I checked MD5 checksum just to make sure that it did download correctly and it does match with the one on the download page. However, I did notice that when I'm trying to open that zip file on my PC I'm getting an error saying that the archive is corrupted.
ProTofik said:
What do you mean by firmware. Bootloader or ROM? I did 'just' flash PA without a problem.
I guess the ROM you liked is the latest official one. By installing it I will get my bootloader updated and then I will be able to flash CM12. Do I get this right? or will I get stuck on stock forever?
Edit: I just tried to flash your image using hboot but it didn't work. Check file attached.
I checked MD5 checksum just to make sure that it did download correctly and it does match with the one on the download page. However, I did notice that when I'm trying to open that zip file on my PC I'm getting an error saying that the archive is corrupted.
Click to expand...
Click to collapse
It probably didn't work because you are S-On. The method I gave you is generally used by S-Off users to flash firmware, but since it was a signed zip, I thought it might work.
Rename the download I gave you to ROM.zip at put it into your fastboot/platform-tools folder on your PC. Then hook your phone up to your PC and fastbooot.
fastboot devices to make sure your phone and PC are properly connected. (letters and numbers/ser. #)
fastboot oem rebootRUU
fastboot flash zip ROM.zip
EDIT: If you respond here, please use the reply button, I will get a notification that way. I just stumbled back to this thread by chance.
xunholyx said:
It probably didn't work because you are S-On. The method I gave you is generally used by S-Off users to flash firmware, but since it was a signed zip, I thought it might work.
Rename the download I gave you to ROM.zip at put it into your fastboot/platform-tools folder on your PC. Then hook your phone up to your PC and fastbooot.
fastboot devices to make sure your phone and PC are properly connected. (letters and numbers/ser. #)
fastboot oem rebootRUU
fastboot flash zip ROM.zip
EDIT: If you respond here, please use the reply button, I will get a notification that way. I just stumbled back to this thread by chance.
Click to expand...
Click to collapse
Sorry, doesn't work either. I'm getting this error on 3rd command:
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash zip ROM.zip
target reported max download size of 1830711296 bytes
error: cannot load 'ROM.zip'
Click to expand...
Click to collapse
ProTofik said:
Sorry, doesn't work either. I'm getting this error on 3rd command:
Click to expand...
Click to collapse
Okay. There must be something I am not aware of.
In fastboot: fastboot getvar all and post the readout here. But delete the serial number and IMEI for your own safety. Never post those on a public forum.
xunholyx said:
Okay. There must be something I am not aware of.
In fastboot: fastboot getvar all and post the readout here. But delete the serial number and IMEI for your own safety. Never post those on a public forum.
Click to expand...
Click to collapse
There you go:
C:\Program Files (x86)\Android\android-sdk\platform-tools>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: 1.54.401.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: TOP SECRET
(bootloader) imei: TOP SECRET
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__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: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.063s
Click to expand...
Click to collapse
ProTofik said:
There you go:
Click to expand...
Click to collapse
It should work. Try this download instead. https://drive.google.com/file/d/0B17smFr95pleU2NqcVB3NWxoNnM/view
It's pretty much the same one. Maybe the other one is screwed somehow? Try with this one instead and hopefully you can get updated.
xunholyx said:
It should work. Try this download instead. https://drive.google.com/file/d/0B17smFr95pleU2NqcVB3NWxoNnM/view
It's pretty much the same one. Maybe the other one is screwed somehow? Try with this one instead and hopefully you can get updated.
Click to expand...
Click to collapse
Didn't work but I got a different error this time
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash zip ROM
.zip
target reported max download size of 1830711296 bytes
sending 'zip' (1536838 KB)...
OKAY [ 43.198s]
writing 'zip'...
(bootloader) zip header checking...
FAILED (remote: 32 header error)
finished. total time: 43.510s
Click to expand...
Click to collapse
Is it not possible to just restore whatever ROM my phone came with and then just do the OTA update?
ProTofik said:
Didn't work but I got a different error this time
Is it not possible to just restore whatever ROM my phone came with and then just do the OTA update?
Click to expand...
Click to collapse
LOL!
Yes. I got caught up in this method. You will also need the stock recovery (more important than the ROM) to use the OTAs. Plus your system partition has to be unmodified. That means no Xposed modules. If you have them, delete them using Xposed framework, then uninstall that as well.
xunholyx said:
LOL!
Yes. I got caught up in this method. You will also need the stock recovery (more important than the ROM) to use the OTAs. Plus your system partition has to be unmodified. That means no Xposed modules. If you have them, delete them using Xposed framework, then uninstall that as well.
Click to expand...
Click to collapse
So if I get this right, I just need to restore my factory ROM and Recovery image, then update it through OTA to lollipop. After that I will be able to flash my custom recovery and ROMs once again, right?
Do you have any links to the ROM and Recovery to my phone?
ProTofik said:
So if I get this right, I just need to restore my factory ROM and Recovery image, then update it through OTA to kitkat. After that I will be able to flash my custom recovery and ROMs once again, right?
Do you have any links to the ROM and Recovery to my phone?
Click to expand...
Click to collapse
Yes. Sorry for the confusion I have caused.
xunholyx said:
LOL!
Yes. I got caught up in this method. You will also need the stock recovery (more important than the ROM) to use the OTAs. Plus your system partition has to be unmodified. That means no Xposed modules. If you have them, delete them using Xposed framework, then uninstall that as well.
Click to expand...
Click to collapse
Success. For future generations, here is what I did:
Using fastboot getvar all command I found out that my phone was still mentally stuck on stock rom 1.54.401.5. Using this info, I downloaded matching nandroid backup of that ROM from here and restored it using my custom recovery.
Then, downloading from the same thread, I flashed back stock recovery image using HTC One 2014 (M8) All-In-One Toolkit V2.0.
I was back on my original ROM with original recovery, so I started doing OTA updates until I got to the official android 5.0.1. These updates updated my bootloader to version 3.19.
Having the bootloader that I needed, I flashed custom recovery and installed CM12 without any problem.
Thanks for help!
Hey, I just found this as I am having the same problem. I am trying to follow your solution, but hit a road block and was wondering if you could help. I ran the command "fastboot getvar all" in fastboot and got output similar to yours. Following your advice I looked at the line (bootloader) version-main: 1.55.605.2 which is different than yours, but okay I just need to find a matching one. But when I go to the link that you had provided I can't find a backup that matches mine (or at least I think I can't). What does it mean for it to match anyway? I'm getting so close! I want cm12!!
I did it over like 6 months ago. I can't remember any more. Sorry.
Anyway, CM12 has way too many problem on HTC ONE M8 to be used as a daily driver. I am using GPE Rom now, which I can recommend.
I just need to find some way to update my bootloader so I can get lollipop up and running. Thanks tho
noo_too_droid said:
Following your advice I looked at the line (bootloader) version-main: 1.55.605.2 which is different than yours, but okay I just need to find a matching one. But when I go to the link that you had provided I can't find a backup that matches mine (or at least I think I can't). What does it mean for it to match anyway?
Click to expand...
Click to collapse
The number needs to match exactly to restore to stock and OTA update the software/firmware (and therefore update hboot).
You can try to post on the following thread, and ask if someone can post the stock nandroid for 1.55.605.2 :http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Otherwise (if you can't get a stock nandroid) you may need to resort to getting s-off in order to update hboot (actually I recommend updating all firmware, not just hboot).
ProTofik said:
Success. For future generations, here is what I did:
Using fastboot getvar all command I found out that my phone was still mentally stuck on stock rom 1.54.401.5.
Click to expand...
Click to collapse
Hi there! I have a problem with my One M8 (S-OFF) - I cant flash any ROM on it. I can restore backups from a CM11 4.4.4 and an ARHD 41.0 but can't upgrade from either. I was looking at your solution and noticed that my ROM number is blank when I run fastboot getvar all. Is this a matter of concern? How can I flash a ROM again?
raghuchary said:
Hi there! I have a problem with my One M8 (S-OFF) - I cant flash any ROM on it. I can restore backups from a CM11 4.4.4 and an ARHD 41.0 but can't upgrade from either. I was looking at your solution and noticed that my ROM number is blank when I run fastboot getvar all. Is this a matter of concern? How can I flash a ROM again?
Click to expand...
Click to collapse
Your version-main is blank because of a bug in some older TWRPs. Update to 2.8.7.0. Flashing the new recovery won't fix version-main being blank until you flash new firmware though.
Also, you probably do have to update your firmware. You say you can't flash any ROMs, but you give no details.
xunholyx said:
Your version-main is blank because of a bug in some older TWRPs. Update to 2.8.7.0. Flashing the new recovery won't fix version-main being blank until you flash new firmware though.
Also, you probably do have to update your firmware. You say you can't flash any ROMs, but you give no details.
Click to expand...
Click to collapse
Apologies, newbie here. I was looking for the correct place to place my request for help, when I found this thread and asked. I will put it up in the Q&A section.
Hi,
I have a big problem with my HTC one M8.
I was tring to back sense from GPE conversion, and now I do not know how to proceed. Maybe bricked my phone.
My situation is as follows:
Relocked. Adb can't find my device so I can not unlock again.
No recovery, no ROM installed. So, I can not flag USB debug. Can't proceed since relocked. Any suggestion?
Matteo
mtt_73 said:
Hi,
I have a big problem with my HTC one M8.
I was tring to back sense from GPE conversion, and now I do not know how to proceed. Maybe bricked my phone.
My situation is as follows:
Relocked. Adb can't find my device so I can not unlock again.
No recovery, no ROM installed. So, I can not flag USB debug. Can't proceed since relocked. Any suggestion?
Matteo
Click to expand...
Click to collapse
im going to assume your phones is s-off?
Yes s-off. Not sure how, but I am in recovery. Something looks like stock, I think. What can I do from here? Should I install twrp recovery? Or what else?
Thank you.
Sent from my Nexus 4 using XDA Free mobile app
mtt_73 said:
Yes s-off. Not sure how, but I am in recovery. Something looks like stock, I think. What can I do from here? Should I install twrp recovery? Or what else?
Click to expand...
Click to collapse
You can't install custom recovery with a (re)locked bootloader.
With s-off, you shouldn't ever relock the bootloader, as its no longer a requirement to RUU once s-off. But that's neither here nor there at this point, just info for future reference.
Any response to: fastboot devices
Make sure the phone is in fastboot mode.
Try to run the GPE RUU with phone in fastboot mode, to get the phone back up and running at least. Assuming you are still on the GPE CID and MID.
How can I flash ruu gpe with boot loader relocked? Is it possible? It gives me error.
Sent from my Nexus 4 using XDA Free mobile app
mtt_73 said:
How can I flash ruu gpe with boot loader relocked? Is it possible? It gives me error.
Click to expand...
Click to collapse
I think you've got it backwards. With s-on the bootloader actually needs to be relocked (or locked) in order to RUU.
With s-off, RUU will run whether the bootloader is unlocked, relocked, or locked.
In other words, the bootloader being relocked is not the problem.
What is the error message?
Did you change the CID/MID yet (what are they currently)? The CID and MID need to match the RUU.
Hi guys,
I have a problem with my one m8 at&t, unlocked, and i can only navigate in hboot in hboot & fastboot modes. no htc logo screens or sth like this.
when i try to go to recovery or do factory reset i get three android skaters on the screen for cca 0.2 sec and it returns to fastboot usb mode.
Its friends phone so i dont know what he had done to it, but i just want to make it work again, wiping data is not the problem.. can you tell me what should i do to get recovery( TWRP/ CWM) working, thats all i need for now because im going to s-off later. i tried to do something but it didnt work.
some things i have tried in that order:
1)flashing twrp via fastboot:
C:\adb>fastboot flash recovery C:\adb\openrecovery-twrp-2.8.5.0-m8.img
target reported max download size of 1830727680 bytes
sending 'recovery' (16086 KB)...
OKAY [ 1.438s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 1.500s
2) flashing stock recovery via fastboot( i dont know if i had the right one):
C:\adb>fastboot flash recovery C:\adb\recovery.img
target reported max download size of 1830727680 bytes
sending 'recovery' (14109 KB)...
OKAY [ 1.262s]
writing 'recovery'...
FAILED (remote: image error! (BootMagic check fail))
finished. total time: 1.277s
3) 'booting' same stock recovery- what changed now are 3 android skaters for cca 0.2 sec when i try to enter recovery or start factory reset from bootloader, before it just went to fastboot usb mode.
C:\adb>fastboot boot recovery.img
creating boot image...
creating boot image - 14450688 bytes
downloading 'boot.img'...
OKAY [ 1.273s]
booting...
OKAY [ -0.000s]
finished. total time: 1.273s
Can please anyone help me? Thanks in advance
Here is data about the phone:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: INVALID_VER_INFO
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT.............8
(bootloader) imei: 35...........30
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(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
redpoint73 said:
I think you've got it backwards. With s-on the bootloader actually needs to be relocked (or locked) in order to RUU.
With s-off, RUU will run whether the bootloader is unlocked, relocked, or locked.
In other words, the bootloader being relocked is not the problem.
What is the error message?
Did you change the CID/MID yet (what are they currently)? The CID and MID need to match the RUU.
Click to expand...
Click to collapse
I will try again later. If I am not wrong the error is about partition problem. It does not recognize the zip.
Sent from my Nexus 4 using XDA Free mobile app
mtt_73 said:
I will try again later. If I am not wrong the error is about partition problem. It does not recognize the zip.
Click to expand...
Click to collapse
When you get a chance, you should list exactly (in detail, and in order) what you have done to the phone to get to this point.
I can't tell how far you go in the conversion (GPE>Sense) but it seems you at least got partway (if you indeed got a partition size error).
Also need to know current CID and MID.
---------- Post added at 12:35 PM ---------- Previous post was at 12:31 PM ----------
mato123 said:
I have a problem with my one m8 at&t, unlocked, and i can only navigate in hboot in hboot & fastboot modes. no htc logo screens or sth like this.
when i try to go to recovery or do factory reset i get three android skaters on the screen for cca 0.2 sec and it returns to fastboot usb mode.
Its friends phone so i dont know what he had done to it, but i just want to make it work again, wiping data is not the problem.. can you tell me what should i do to get recovery( TWRP/ CWM) working, thats all i need for now because im going to s-off later. i tried to do something but it didnt work.
some things i have tried in that order:
Click to expand...
Click to collapse
I would highly suggest not to post to another user's troubleshooting thread like this, as it doesn't look like the same problem at all (and in my experience rarely is, even when folks will post "I have the same issue"). You really should have just started your own thread, and would have been justified doing so IMO. Posting here just confuses matters for you, the OP and those trying to help.
But DON'T start another thread now (and add even more confusion). I'll ask the mods if they can move this post to its own thread.
ok, sorry
redpoint73 said:
When you get a chance, you should list exactly (in detail, and in order) what you have done to the phone to get to this point.
I can't tell how far you go in the conversion (GPE>Sense) but it seems you at least got partway (if you indeed got a partition size error).
Also need to know current CID and MID.
Click to expand...
Click to collapse
Thanks for reply.
I went now in fastoob mode and tried to flash the RUU GPE again.
The error is:
macbooks-MacBook-Proownloads macbook$ ./fastboot-mac flash RUU-HTC_One_M8_GPE_5.1-4.04.1700.4.zip
unknown partition 'RUU-HTC_One_M8_GPE_5.1-4.04.1700.4.zip'
error: cannot determine image filename for 'RUU-HTC_One_M8_GPE_5.1-4.04.1700.4.zip'
Just to clarify. I successfully when in GPE (with conversation). The problem was when going back to Sense. I do not know exactly what I did wrong.
My CID is 11111111
My MID is 0P6B10000
Really do not know how to proceed.
M
I unfortunately don't know jack about how to use fastboot and other actions on a Mac. I'm also not that familiar with running the RUU as a zip (I always do it on a PC with the RUU .exe).
But it looks like you just have the command syntax wrong. I think it should be:
fastboot oem rebootRUU
fastboot flash zip filename.zip
But it also look to me like nothing is actually "wrong" (aside from adb not working?). The phone not booting after relocking the bootloader is normal and intentional. You should just be able to run the desired Sense RUU, provided you have the right MID.
I am back to GPE!
Stupid me! I missed a "zip" in the fastboot command...
Thank you for support!
I will try again to go back to Sense.
M
mtt_73 said:
I am back to GPE!
Stupid me! I missed a "zip" in the fastboot command...
Thank you for support!
I will try again to go back to Sense.
M
Click to expand...
Click to collapse
hehe try watch this movie: https://www.youtube.com/watch?v=CCGj0rOuiR4
Most important is the firmware flash... so partition layout etc is changed to sense like after that you can flash sense roms etc. (for example viper rom as in video)
0kk0 said:
Most important is the firmware flash... so partition layout etc is changed to sense
Click to expand...
Click to collapse
Some folks have had to do this, some haven't. But yes, if the RUU fails and gives a image size error, flashing the Sense firmware manually (then RUU) is the right thing to do.
This part has never made sense to me, since the RUU flashes firmware anyway, by definition. All I can guess, is that it has to do with the sequence in which the firmware is flashed (versus other partitions) in the RUU.
redpoint73 said:
Some folks have had to do this, some haven't. But yes, if the RUU fails and gives a image size error, flashing the Sense firmware manually (then RUU) is the right thing to do.
This part has never made sense to me, since the RUU flashes firmware anyway, by definition. All I can guess, is that it has to do with the sequence in which the firmware is flashed (versus other partitions) in the RUU.
Click to expand...
Click to collapse
So, even if the sense RUU is available, to go back to sense I need to flash the firmware before to flash the RUU. Right?
Sent from my HTC One_M8 using xda Forum
mtt_73 said:
So, even if the sense RUU is available, to go back to sense I need to flash the firmware before to flash the RUU. Right?
Click to expand...
Click to collapse
I just said in the post you quoted: some folks are fine just running the RUU (to convert from GPE to Sense); but when the RUU alone doesn't work, run the firmware manually first, then the RUU.
Running the firmware manually first (then RUU) has a higher chance of working, I'd say.
redpoint73 said:
I just said in the post you quoted: some folks are fine just running the RUU (to convert from GPE to Sense); but when the RUU alone doesn't work, run the firmware manually first, then the RUU.
Running the firmware manually first (then RUU) has a higher chance of working, I'd say.
Click to expand...
Click to collapse
I did it. I am back to Sense now.
Any advice to remove tell HTC problem? I mean it says that I have a testing device. Is it because I am s-off? Should I go for s-on again? And how?
TY!
Hi,
Well, as the title said i'm stuck in bootloop after re-locking the bootloader.
Here is the history of what happened:
Unlocked the bootloader
flashed TWERP recovery and rooted.
I saw I can't install OTA updates so I unrooted the phone and flashed back to stock recovery. Still couldn't install OTA updates.
Unlocked the bootloader again and restored system partition back to original "untouched" status (from this thread: http://forum.xda-developers.com/tmobile-one-m9/general/please-read-rooting-using-twrp-t3069022). Only to realize i'm not on t-mobile, but the phone worked anyway .
Flashed back to stock recovery but still couldn't install the updates (If I remember correctly I got a massage that my software was tampered).
I'm S-on so I thought before trying the sunshine app I'll relock the bootloader. So I did that and that's it.
Here's were I'm now:
software status: modified
RELOCKED
S-ON
I can access stock recovery and download mode.
ADB devices doesn't recognize the phone (all drivers are ok and up to date and I've tried different cables and usb ports)
On the other hand, fasboot devices does work and recognize my phone.
So I come to you with help after going though tons of pages, guides and what not. I'm at it for a week now and no luck.
Help me XDA-Kanobi, you're my only hope
Thanks
Yotam
unlock with fastboot
Sorry to bump but is there any way to unlock it with fastboot maybe since it's the only way I can connect?
any suggestion or idea will be helpful
Thanks
Yotam
yotamh said:
Sorry to bump but is there any way to unlock it with fastboot maybe since it's the only way I can connect?
any suggestion or idea will be helpful
Thanks
Yotam
Click to expand...
Click to collapse
What's your current firmware? Is the allow OEM unlock option (or how ever it was called in English) activated in the developer options (only important for firmware versions with a 2 or higher at the beginning)? If yes you can re-unlock with the unlock_token you got from HTCdev.
Flippy498 said:
What's your current firmware? Is the allow OEM unlock option (or how ever it was called in English) activated in the developer options (only important for firmware versions with a 2 or higher at the beginning)? If yes you can re-unlock with the unlock_token you got from HTCdev.
Click to expand...
Click to collapse
My current firmware is 5.0.something. To be honest I don't remember and can't check.
I've tired to re-unlock with the unlock_token you got from HTCdev but it didn't work. I've got the token with fastboot but only in download mode an then when I tried to unlock with the file they send you to the mail It gives an error that I can check later when I'm home.
Yotam
yotamh said:
My current firmware is 5.0.something. To be honest I don't remember and can't check.
I've tired to re-unlock with the unlock_token you got from HTCdev but it didn't work. I've got the token with fastboot but only in download mode an then when I tried to unlock with the file they send you to the mail It gives an error that I can check later when I'm home.
Yotam
Click to expand...
Click to collapse
It seems like you're talking about the android version not the firmware version since there is no 5.0.XXX.X firmware for the M9. For now it might be the best solution to wait until you're home.
yotamh said:
Hi,
Well, as the title said i'm stuck in bootloop after re-locking the bootloader.
Here is the history of what happened:
Unlocked the bootloader
flashed TWERP recovery and rooted.
I saw I can't install OTA updates so I unrooted the phone and flashed back to stock recovery. Still couldn't install OTA updates.
Unlocked the bootloader again and restored system partition back to original "untouched" status (from this thread: http://forum.xda-developers.com/tmobile-one-m9/general/please-read-rooting-using-twrp-t3069022). Only to realize i'm not on t-mobile, but the phone worked anyway .
Flashed back to stock recovery but still couldn't install the updates (If I remember correctly I got a massage that my software was tampered).
I'm S-on so I thought before trying the sunshine app I'll relock the bootloader. So I did that and that's it.
Here's were I'm now:
software status: modified
RELOCKED
S-ON
I can access stock recovery and download mode.
ADB devices doesn't recognize the phone (all drivers are ok and up to date and I've tried different cables and usb ports)
On the other hand, fasboot devices does work and recognize my phone.
So I come to you with help after going though tons of pages, guides and what not. I'm at it for a week now and no luck.
Help me XDA-Kanobi, you're my only hope
Thanks
Yotam
Click to expand...
Click to collapse
OK OK dont get frenetic...DO AS EXACTLY AS I SAY OK?.................boot into download MODE Only and follow SAKITECH video on how to root M9, then flash a custom rom or SD Zip-Ruu to allow phone to boot again. =D hope this helps!
LLegion said:
OK OK dont get frenetic...DO AS EXACTLY AS I SAY OK?.................boot into download MODE Only and follow SAKITECH video on how to root M9, then flash a custom rom or SD Zip-Ruu to allow phone to boot again. =D hope this helps!
Click to expand...
Click to collapse
the problem is I can't unlock the bootloader. ADB devices doesn't work
Flippy498 said:
What's your current firmware? Is the allow OEM unlock option (or how ever it was called in English) activated in the developer options (only important for firmware versions with a 2 or higher at the beginning)? If yes you can re-unlock with the unlock_token you got from HTCdev.
Click to expand...
Click to collapse
how can I check the firmware version from the bootloader?
(under os in download mode I see - 1.32.401.15. is that the firmware?
yotamh said:
how can I check the firmware version from the bootloader?
(under os in download mode I see - 1.32.401.15. is that the firmware?
Click to expand...
Click to collapse
Yes, that's correct. And with that firmware your problems can be solved without much hassle. Just download either the 1.32.401.15 or the 1.40.401.8 RUU which are both linked in my google sheet (link can be found in my signature). Follow the instructions and your phone should be usable again in no time. If you choose the 1.40.401.8 RUU there's one OTA less you need to install after you recovered your phone.
And a little advice for the future: If you want to install future OTAs then you don't need to relock your bootloader. If your phone isn't completely stock this will always result in a bootloop.
Flippy498 said:
Yes, that's correct. And with that firmware your problems can be solved without much hassle. Just download either the 1.32.401.15 or the 1.40.401.8 RUU which are both linked in the google sheet in my signature. Follow the instructions and your phone should be usable again in no time. If you choose the 1.40.401.8 RUU there's one OTA less you need to install after you recovered your phone.
And a little advice for the future: If you want to install future OTAs then you don't need to relock your bootloader. If your phone isn't completely stock this will always result in a bootloop.
Click to expand...
Click to collapse
Thanks a lot for the answer. Is it possible to flash the RUU if I'm S-ON??
yotamh said:
Thanks a lot for the answer. Is it possible to flash the RUU if I'm S-ON??
Click to expand...
Click to collapse
Of course. The only things you cannot do is downgrading or flashing RUUs that have a different SKU (=the three numbers behind the second dot in the firmware version). RUUs with the same version as your phone or higher versions are fine, though.
Flippy498 said:
Of course. The only things you cannot do is downgrading or flashing RUUs that have a different SKU (=the three numbers behind the second dot in the firmware version). RUUs with the same version as your phone or higher versions are fine, though.
Click to expand...
Click to collapse
HI
So i'm trying to flash the RUU and I'm getting this:
C:\Users\Yotam\Desktop\Phone files>fastboot flash zip M9_1.32.401.15_FullStock_rename_to_ROM.zip <----I've tried to change it to ROM.zip as well but I get the same error
target reported max download size of 800000000 bytes
sending 'zip' (111548 KB)...
OKAY [ 7.869s]
writing 'zip'...
(bootloader) HOSD CL#506785
(bootloader) GPT is up-to-dated. [17408]
(bootloader) Perform pre-update
(bootloader) ERR ZIP signature checking failed...
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 8
(bootloader) ERR Update zip file failed.
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 8
(bootloader) [email protected]
FAILED (remote: 8: fail to flash via downloadzip)
finished. total time: 12.962s
The ZIP file is fine (i've downloaded it twice just to be sure), phone is with the sd card in it (I though it's worth mentioning), S-ON.
Not sure what else...what seems to be the issue here?
some more info
fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei:
(bootloader) version-main: 1.32.401.15
(bootloader) boot-mode: RUU
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: HTC__016
all:
finished. total time: 0.014s
yotamh said:
HI
So i'm trying to flash the RUU and I'm getting this:
C:\Users\Yotam\Desktop\Phone files>fastboot flash zip M9_1.32.401.15_FullStock_rename_to_ROM.zip <----I've tried to change it to ROM.zip as well but I get the same error
target reported max download size of 800000000 bytes
sending 'zip' (111548 KB)...
OKAY [ 7.869s]
writing 'zip'...
(bootloader) HOSD CL#506785
(bootloader) GPT is up-to-dated. [17408]
(bootloader) Perform pre-update
(bootloader) ERR ZIP signature checking failed...
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 8
(bootloader) ERR Update zip file failed.
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 8
(bootloader) [email protected]
FAILED (remote: 8: fail to flash via downloadzip)
finished. total time: 12.962s
The ZIP file is fine (i've downloaded it twice just to be sure), phone is with the sd card in it (I though it's worth mentioning), S-ON.
Not sure what else...what seems to be the issue here?
Click to expand...
Click to collapse
yotamh said:
some more info
fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei:
(bootloader) version-main: 1.32.401.15
(bootloader) boot-mode: RUU
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: HTC__016
all:
finished. total time: 0.014s
Click to expand...
Click to collapse
For your own safety you should delete your IMEI as it can be used for phone scam by others.
Why are you trying to flash one of Sneakyghosts' firmware packs? They can only be used with S-OFF and do not contain a rom. I've already explained earlier that you can find the needed RUUs and instructions in the google sheet in my signature.
Flippy498 said:
For your own safety you should delete your IMEI as it can be used for phone scam by others.
Why are you trying to flash one of Sneakyghosts' firmware packs? They can only be used with S-OFF and do not contain a rom. I've already explained earlier that you can find the needed RUUs and instructions in the google sheet in my signature.
Click to expand...
Click to collapse
Hi thanks for the top about the IMEI I've changed it.
and sorry, I didn't understood the the original comment and got in to the a wrong line in the comment. I'll try again with the correct file (2gb will take some to download). Again, thank you for your answer and patient. It's nice to see people try to help. :good:
THANK YOU so much! everything is working and even updated! thanks!
it seems i have a strange issue after all.
my phone doesn't detect my htc headphones. It recognize other headphone and the HTC headphones works with other devices.
it looks like a software issue.
Flippy498 said:
For your own safety you should delete your IMEI as it can be used for phone scam by others.
Why are you trying to flash one of Sneakyghosts' firmware packs? They can only be used with S-OFF and do not contain a rom. [REMOVED BECAUSE I'M A NEWBIE]I've already explained earlier that you can find the needed RUUs and instructions in the google sheet in my signature[/URL].
Click to expand...
Click to collapse
Hi I know this is probably old but I was in this exact same predicament and I had "tried everything" and your instructions brought my phone back to life!! I am so grateful after almost a week of adb commands and zip files that got me nowhere! THANK YOU SO MUCH!!!:good:
I seem to have soft bricked my m9 hima while trying to go back to stock in order to update the firmware to the latest rev. (Yes, I have read the other threads, but I Think this might be a little more unique to my situation? )
I cannot get into my stock recovery, or my TWRP(which is what I used before).
Download mode appears to work.
I can't install TWRP with fastboot/adb, might be because device is S-on.
Tried running RUU, but says my device isn't compatible.
I would really appreciate anyones' input!
Nanometer45 said:
I seem to have soft bricked my m9 hima while trying to go back to stock in order to update the firmware to the latest rev. (Yes, I have read the other threads, but I Think this might be a little more unique to my situation? )
I cannot get into my stock recovery, or my TWRP(which is what I used before).
Download mode appears to work.
I can't install TWRP with fastboot/adb, might be because device is S-on.
Tried running RUU, but says my device isn't compatible.
I would really appreciate anyones' input!
Click to expand...
Click to collapse
Useful information that will help us help you:
CID (Carrier ID)
MID (Model ID)
Firmware version that you're currently on
Steps you took that led to your current situation
Like you said, this is a soft brick. Odds are good we can help.
---------- Post added at 04:39 PM ---------- Previous post was at 04:32 PM ----------
If you're new to ADB & fastboot, check out this thread
Once you've installed those:
- plug your phone into your computer while it is in download mode
- open a command prompt
- run the command "fastboot getvar all"
Phone is:
MID 0PJA11000
CID CWS__001
Firmware I tried to flash was this:
RUU_HIMA_UL_L51_SENSE70_ATT_MR_Cingular_US_2.11.502.18
It looks like the firmware update failed, but when the RUU program tries to read the firmware it now shows as the new one listed above.
I got to this point by trying to update the firmware. I had problems getting the new TWRP working, and I got impatient :-\
Make sure you double check the md5 hash and filesize of twrp before you flash it.
Sent from my HTC One M9 using Tapatalk
I tried flashing TWRP, and it seems to have taken it, but phone says it cannot boot intothe boot loader, it said that before I started running into soft brick issues i believe.
Try my copy https://drive.google.com/folderview?id=0B4vTiHTBB629QmxGTkpyZWlCR28
Sent from my HTC One M9 using Tapatalk
Which do you recommend, your twrp?
I know mine works..
Sent from my HTC One M9 using Tapatalk
Can't get it to flash:
C:\Program Files (x86)\ClockworkMod\Universal Adb Driver>fastboot flash recovery T1F.img
target reported max download size of 800000000 bytes
sending 'recovery' (30912 KB)...
OKAY [ 2.444s]
writing 'recovery'...
(bootloader) HOSD CL#591203
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 2.651s]
finished. total time: 5.096s
Says:
Failed to boot to recovery mode
Flash the twrp 2.9.0.1 in the link i gave. See what that does.
Sent from my HTC One M9 using Tapatalk
Nanometer45 said:
Can't get it to flash:
C:\Program Files (x86)\ClockworkMod\Universal Adb Driver>fastboot flash recovery T1F.img
target reported max download size of 800000000 bytes
sending 'recovery' (30912 KB)...
OKAY [ 2.444s]
writing 'recovery'...
(bootloader) HOSD CL#591203
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 2.651s]
finished. total time: 5.096s
Says:
Failed to boot to recovery mode
Click to expand...
Click to collapse
I'm pretty sure 2.9.x and later versions only work on MM, and you're on LP firmware. Try one of the 2.8.x versions from here: https://dl.twrp.me/hima/
Doesn't boot into TWRP. Maybe S-off is a problem.
Missed your post, I'll try an older build. Though I was running Cyanogenmod 13, so I don't see how that invited the problem. Doesn't hurt to try.
Older TWRP worked. Now I just need to get the latest firmware on it without android installed. Any tips?
Was able to finally get the RUU to take. Thanks for helping out. Is there no MM update for the ATT M9? That would explain some of the issues I was having. Only custom roms for options then.