Develop Bugs

Confirm this?? If S-off, I can flash recovery with bootloader locked?

It is so hard to re-locate threads between this general HTC One M8 and the variant for the carriers....so I hate adding to repetitive questions in threads....
BUT... I was certain that I read countless times that you could flash recoveries from ADB with bootloader locked provided you had S-off.
And now I am getting this error:
FAILED (remote: not allowed)
I had two updates and wanted to flash stock recovery then reflash TWRP.... I thought it would take 20 minutes tops....

syntropic said:
It is so hard to re-locate threads between this general HTC One M8 and the variant for the carriers....so I hate adding to repetitive questions in threads....
BUT... I was certain that I read countless times that you could flash recoveries from ADB with bootloader locked provided you had S-off.
And now I am getting this error:
FAILED (remote: not allowed)
I had two updates and wanted to flash stock recovery then reflash TWRP.... I thought it would take 20 minutes tops....
Click to expand...
Click to collapse
SO I said f*ck it... no big deal, and I unlocked the bootloader and flashed the stock recovery (btw, I flashed a stock recovery I found in the TMO forums that had a version number identical to the software version I had installed, this is correct right????). I had no problems flashing the stock recovery....so apparently, you need to unlock the bootloader whenever you are flashing recoveries irrespective of whether you have S-off.
But then, I tried to run the OTA, and got the red triangle error.... — Is this because my bootloader is now unlocked?
This seems to be going against everything I have read numerous times (namely that if you are S-off, the bootloader is not that big of an issue). I am assuming this is because my bootloader is now unlocked... so I will unlock it.

IGNORE

Just adding my experiences as I don't want to start another thread with new information...
I have unlocked bootloader
flashed stock recovery
relocked bootloader
went into setting==>apps and enabled the 10 or so apps that I had previously disabled...
I even deleted all downloaded OTA updates and had the phone re-download them again.
However, I still cannot install OTA updates. I know that the standard instructions are to flash a stock rom or restore a nandroid that is stock, but my phone is stock!!! Nothing has touched any of the original software on it other than the stock recovery, which I flashed back on it...
I think my phone is techincally still rooted because it has the SuperSu binary installed... But (again) from everything I read, the way I understood it was that in order to get OTA updates you needed to have stock (or pretty close with no uninstalled/frozen/disabled system apps), and the stock recovery.... AND that is it....
Anyway, I did a fastboot getvar all if that is helpful.... I have pasted it below:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.19.213311491.03G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.22.531.5
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA44VWM00543
(bootloader) imei: ★★★★★★★★★★★★★
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B13000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 5e4b24e4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.059s

syntropic said:
Just adding my experiences as I don't want to start another thread with new information...
I have unlocked bootloader
flashed stock recovery
relocked bootloader
went into setting==>apps and enabled the 10 or so apps that I had previously disabled...
I even deleted all downloaded OTA updates and had the phone re-download them again.
However, I still cannot install OTA updates. I know that the standard instructions are to flash a stock rom or restore a nandroid that is stock, but my phone is stock!!! Nothing has touched any of the original software on it other than the stock recovery, which I flashed back on it...
I think my phone is techincally still rooted because it has the SuperSu binary installed... But (again) from everything I read, the way I understood it was that in order to get OTA updates you needed to have stock (or pretty close with no uninstalled/frozen/disabled system apps), and the stock recovery.... AND that is it....
Anyway, I did a fastboot getvar all if that is helpful.... I have pasted it below:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.19.213311491.03G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.22.531.5
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA44VWM00543
(bootloader) imei: DO NOT POST IMEI NUMBER
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B13000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 5e4b24e4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.059s
Click to expand...
Click to collapse
What OTA update are you trying to install?
version-bootloader: 3.18.0.0000 - latest
version-main: 2.22.531.5 - latest
Remove your IMEI from your post.

BerndM14 said:
What OTA update are you trying to install?
version-bootloader: 3.18.0.0000 - latest
version-main: 2.22.531.5 - latest
Remove your IMEI from your post.
Click to expand...
Click to collapse
I removed it just before I saw your post... but thanks! And thanks for replying.
I am trying to install the 2.22.531.6 OTA software.
I don't know if the bootloader/hboot version has any correlation to the software, but I have not touched anything... I did two updates, then a three days later did HTCDev unlock of bootloader, I flashed TWRP, flashed SuperSU, got Sunshine S-Off, then relocked bootloader. As mentioned I also disabled a bunch of apps. But as of now, I have re-enabled them.
The only variable that wasn't precisely in my control was the stock recovery. I didn't know which one to flash, but made the common sense decision to flash the 2.22.531.5-TMO-Recovery.img since the version number of the recovery matched exactly the version number of the software that is showing on my hboot screen. I thought that was a educated guess that wouldn't be too risky.
I haven't flashed or changed the hboot, or flashed any RUUs....nothing else.
really confused....because aside from the recovery, I didn't touch any of the firmware.
NB: I do have a nandroid that I made that is entitled: 2014-09-24-14-06{whatever) release keys I don't know what release keys means.... I have made a lot of nandroids in my time... 95% of them on HTC devices using TWRP (at least since its inception), and I have never seen a "release keys" appended to the name of an nandroid like that.
I could restore this nandroid... but then I would have to unlock the BL, fastboot flash TWRP, flash SuperSU (although I know TWRP now prompts you which is very cool), then restore the nandroid, fastboot flash the stock recovery, then (apparently) re-lock the bootloader, and get the OTAs.... if the OTAs even work...

syntropic said:
I removed it just before I saw your post... but thanks! And thanks for replying.
I am trying to install the 2.22.531.6 OTA software.
I don't know if the bootloader/hboot version has any correlation to the software, but I have not touched anything... I did two updates, then a three days later did HTCDev unlock of bootloader, I flashed TWRP, flashed SuperSU, got Sunshine S-Off, then relocked bootloader. As mentioned I also disabled a bunch of apps. But I have no re-enabled them.
The only variable that wasn't precisely in my control was the stock recovery. I didn't know which one to flash, but made the common sense decision to flash the 2.22.531.5-TMO-Recovery.img since the version number matched exactly the version number of the software as shown in the hboot screen. So I assumed it was the right one. I haven't flashed or changed the hboot, or flashed any RUUs....nothing else.
really confused.
Click to expand...
Click to collapse
Ok stock recovery flashed back is good then, you need to be completely stock to do OTA's i.e If you made changes to the system even removed pre-installed apps like Facebook, Twitter etc you need to restore those back as well. As the OTA will do a verification check to see that all those things are intact before it continues the update. If it's not stock then you're not getting OTA. Bootloader status won't make a difference, you can keep it unlocked.
When you do the OTA and it fails what error does it give? When an OTA gets applied it reboots the system to the stock recovery and proceeds to apply the update, if it fails you can view the error. You can press Volume Up and then TAP the power button and it'll show you the recovery log details at the bottom, there it should tell you what errors you have during the OTA installation.
/system/app/blahblahblah has unexpected contents, or cannot find /system/app/blahblah etc
If it requires missing files etc just get them and add them back on the device. Like I said above, you need to be stock.

BerndM14 said:
{...}
When you do the OTA and it fails what error does it give? When an OTA gets applied it reboots the system to the stock recovery and proceeds to apply the update, if it fails you can view the error. You can press Volume Up and then TAP the power button and it'll show you the recovery log details at the bottom, there it should tell you what errors you have during the OTA installation.
/system/app/blahblahblah has unexpected contents, or cannot find /system/app/blahblah etc
If it requires missing files etc just get them and add them back on the device. Like I said above, you need to be stock.
Click to expand...
Click to collapse
Cool... NEAT trick I didn't know about that...!!! thank you for the tip. They should put that in the documentation with the f*ckin phone.
The recovery/installation log says (in relevant part):
Verifying current sytem. . .
"/system/build.prop" has unexpected contents
Installation aborted.
I thought about why the build.prop would have changes, and remembered that I have an app called Android Tweaker Pro (but it is being renamed since Google now prohibits apks with 'Android' in the name). It requires root to make its tweaks. Its a good app, but it does make a lot of changes to build.prop. But... am pretty sure it has a reset/restore to default option on it... I am going to check and try that.
Will let you know...
Sh*t.... still can't believe I didn't know about the installation log screen... very impressed.

syntropic said:
Cool... NEAT trick I didn't know about that...!!! thank you for the tip. They should put that in the documentation with the f*ckin phone.
The recovery/installation log says (in relevant part):
Verifying current sytem. . .
"/system/build.prop" has unexpected contents
Installation aborted.
I thought about why the build.prop would have changes, and remembered that I have an app called Android Tweaker Pro (but it is being renamed since Google now prohibits apks with 'Android' in the name). It requires root to make its tweaks. Its a good app, but it does make a lot of changes to build.prop. But... am pretty sure it has a reset/restore to default option on it... I am going to check and try that.
Will let you know...
Sh*t.... still can't believe I didn't know about the installation log screen... very impressed.
Click to expand...
Click to collapse
And so we all learn new things everyday It's great!
[Recovery] [RUU 2.22.531.6] [TWRP Nandroid Backups] [Radio IMGs][ OTA 2.22.531.6]
There's a stock backup for 2.22.531.5 in there that you can restore to go back to stock for the OTA. Changes to build.prop usually is changes to system. Perhaps you could also try and pull the build.prop from there and restore that and see if it works
---------- Post added at 01:22 AM ---------- Previous post was at 01:20 AM ----------
BerndM14 said:
And so we all learn new things everyday It's great!
[Recovery] [RUU 2.22.531.6] [TWRP Nandroid Backups] [Radio IMGs][ OTA 2.22.531.6]
There's a stock backup for 2.22.531.5 in there that you can restore to go back to stock for the OTA. Changes to build.prop usually is changes to system. Perhaps you could also try and pull the build.prop from there and restore that and see if it works
Click to expand...
Click to collapse
They also have the 2.22.531.6 stuff there so just make sure you select the correct versions, it's under the "clickable" buttons so...

OK.... I used a app called Nandroid Manager (very helpful app) which extracts anything you want from a nandroid. Since I had already disabled the Android Tweaker 2 App, and realized I had an original build.prop in that nandroid, I just extracted that and renamed the old one, and used the extracted one. I did a chmod 644, and then attempted OTA install.. And it went fine! Very nice... A bigger headache then I had anticipated... but it serves me right for forgetting that I had root apps modifying sh*t that I had not considered.
Very big thanks for the tips.
Also...lastly, since I stupidly relocked the bootloader, I am now no longer root but cannot flash TWRP because the BL is locked. I cannot use Scotty1223's method (I don't think) because it requires su permissions in adb shell.
I could probably just use the htc .bin file.... but out of curiousity, is there any easy way to get temp root in this case?
EDIT: Actually.... I would really like to avoid the htc unlock token as that erases the data partition as some kind of existential pennace ordained by HTC for unlocking your bootloader.

syntropic said:
[...] And it went fine! Very nice... A bigger headache then I had anticipated... but it serves me right for forgetting that I had root apps modifying sh*t that I had not considered.
Very big thanks for the tips.
Click to expand...
Click to collapse
Glad it worked out :good:
Also...lastly, since I stupidly relocked the bootloader, I am now no longer root but cannot flash TWRP because the BL is locked. I cannot use Scotty1223's method (I don't think) because it requires su permissions in adb shell.
I could probably just use the htc .bin file.... but out of curiousity, is there any easy way to get temp root in this case?
Click to expand...
Click to collapse
Yeah you can use the unlock binary you had if you went through htc unlock method, or you can just do it again if you want(another headache).
You'll have to read up on temp root methods, I haven't used any at all, so I'm not entirely sure, sorry.
---------- Post added at 02:01 AM ---------- Previous post was at 01:58 AM ----------
BerndM14 said:
Glad it worked out :good:
Yeah you can use the unlock binary you had if you went through htc unlock method, or you can just do it again if you want(another headache).
You'll have to read up on temp root methods, I haven't used any at all, so I'm not entirely sure, sorry.
Click to expand...
Click to collapse
Just saw your edit...you're right it'll probably wipe everything again.
Did you get S-OFF with Sunshine? I don't know if maybe there's a way to unlock the bootloader again even if you're already S-OFF If you didn't then it probably won't be feasible to pAy $25 just to unlock the bootloader, I'd rather then just back up everything and let the data get wiped doing it the HTC way.
Check the Sunshine Thread maybe, they had some discussions in there about temp roots if I recall correctly.

BerndM14 said:
Glad it worked out :good:
Yeah you can use the unlock binary you had if you went through htc unlock method, or you can just do it again if you want(another headache).
You'll have to read up on temp root methods, I haven't used any at all, so I'm not entirely sure, sorry.
---------- Post added at 02:01 AM ---------- Previous post was at 01:58 AM ----------
Just saw your edit...you're right it'll probably wipe everything again.
Did you get S-OFF with Sunshine? I don't know if maybe there's a way to unlock the bootloader again even if you're already S-OFF If you didn't then it probably won't be feasible to pAy $25 just to unlock the bootloader, I'd rather then just back up everything and let the data get wiped doing it the HTC way.
Check the Sunshine Thread maybe, they had some discussions in there about temp roots if I recall correctly.
Click to expand...
Click to collapse
I have been spending the past 2+ hours researching this. Even worse, the HTC token no longer unlocks the bootloader.... So I have this great phone with S-Off, but no way to get root. In my first attempt with chatting with HTC, they said that they "were very sorry but [they] do not support 'unlocking the bootloader' as it is against the warranty". WTF????? I am trying to get though to HTCDev... luckily I didn't change my CID. But I hate waiting for this.... I do a lot of stuff on that phone with root privileges..
I tried adb root, adb root shell, adb shell su, and a whole bunch of combination.... no dice...
There is just no way to hack a way to get temporary root at this point. I have looked... Weaksauce has long been deprecated/useless once you are past 4.4.2.
My planned 20+ minute task today is now going into its sixth hour....!!

syntropic said:
I have been spending the past 2+ hours researching this. Even worse, the HTC token no longer unlocks the bootloader.... So I have this great phone with S-Off, but no way to get root. In my first attempt with chatting with HTC, they said that they "were very sorry but [they] do not support 'unlocking the bootloader' as it is against the warranty". WTF????? I am trying to get though to HTCDev... luckily I didn't change my CID. But I hate waiting for this.... I do a lot of stuff on that phone with root privileges..
I tried adb root, adb root shell, adb shell su, and a whole bunch of combination.... no dice...
There is just no way to hack a way to get temporary root at this point. I have looked... Weaksauce has long been deprecated/useless once you are past 4.4.2.
My planned 20+ minute task today is now going into its sixth hour....!!
Click to expand...
Click to collapse
how did you get S-OFF? Firewater?

BerndM14 said:
how did you get S-OFF? Firewater?
Click to expand...
Click to collapse
He said SunShine on OP.
OP - try towelroot to gain root then use scotty's guide to unlock bootloader

If you are still S-off, just use adb to unlock the bootloader again.
http://forum.xda-developers.com/showthread.php?t=2475914
No muss, no fuss, and no lost files.

jshamlet said:
If you are still S-off, just use adb to unlock the bootloader again.
http://forum.xda-developers.com/showthread.php?t=2475914
No muss, no fuss, and no lost files.
Click to expand...
Click to collapse
Really ?
Read his problem again... His device has no root so can't do what you suggested

ckpv5 said:
Really ?
Read his problem again... His device has no root so can't do what you suggested
Click to expand...
Click to collapse
I realized that shortly after posting.
However, there is still a solution. Use Sunshine to temp-root, then use a local terminal instead of adb.

jshamlet said:
If you are still S-off, just use adb to unlock the bootloader again.
http://forum.xda-developers.com/showthread.php?t=2475914
No muss, no fuss, and no lost files.
Click to expand...
Click to collapse
When ckpv5 referred to Scotty's method in the post above yours, he is talking about the thread you linked. I am aware of that method and think it is great, but you need to get a shell... and you need root privileges in that shell in order to run the dd= command. That is just the way it works. It doesn't matter if you are S-off (this is why I have been frustrated). Until HTC replies to me, I am stuck with an unrooted phone with S-off.
I am going to try the towelroot method though... I forgot about that (thank you ckpv5).
If I can get temporary root long enough to unlock the bootloader.... then I can flash TWRP and I am good to go. We'll see.

syntropic said:
When ckpv5 referred to Scotty's method in the post above yours, he is talking about the thread you linked. I am aware of that method and think it is great, but you need to get a shell... and you need root privileges in that shell in order to run the dd= command. That is just the way it works. It doesn't matter if you are S-off (this is why I have been frustrated). Until HTC replies to me, I am stuck with an unrooted phone with S-off.
I am going to try the towelroot method though... I forgot about that (thank you ckpv5).
If I can get temporary root long enough to unlock the bootloader.... then I can flash TWRP and I am good to go. We'll see.
Click to expand...
Click to collapse
Yeah, I had a bit of a brain fart on that one. I forgot you have to be able to su to execute that dd command, even s-off. However, I do know for a fact that you don't actually have to flash TWRP to re-root. When I did the same thing you are doing, I simply booted TWRP instead of installing it to preserve the stock recovery.
TWRP did have an issue booting for a while when using the firmware that came along with 4.4.3, but they appear to have fixed it in the last two versions. I ended up using CWM instead, but the effect is the same.

jshamlet said:
I realized that shortly after posting.
However, there is still a solution. Use Sunshine to temp-root, then use a local terminal instead of adb.
Click to expand...
Click to collapse
That is another good potential solution...and I know it works.... I will try and let you know!

Please help me

Hello there,
I have the htc one m8. tried to install custom rom while i did followed carefully all steps beside the annoying thing - s-off.
It hasnt says anything about it and i just did those steps:
Open bootloader
install TWRP recovery
flash the rom
Then my m8 reboot but stock on the htc green logo, tried almost everything i had in mind including use my dad GS4 to transfer stock rom into my SD card and then try to install it throw recovery mod which of course, failed.
dont know what alse to do i've been like this for 4-5 hours, please help me!! :crying::crying:

ben33891471 said:
Hello there,
I have the htc one m8. tried to install custom rom while i did followed carefully all steps beside the annoying thing - s-off.
It hasnt says anything about it and i just did those steps:
Open bootloader
install TWRP recovery
flash the rom
Then my m8 reboot but stock on the htc green logo, tried almost everything i had in mind including use my dad GS4 to transfer stock rom into my SD card and then try to install it throw recovery mod which of course, failed.
dont know what alse to do i've been like this for 4-5 hours, please help me!! :crying::crying:
Click to expand...
Click to collapse
Hold down the power button + vol up till your phone reboots (it'll take a bit, 20 seconds or so). AS SOON AS THE SCREEN GOES BLACK slide your finger from vol up to vol down. That will take you to your bootloader.
Hook up to your PC and get into ADB. Enter the command fastboot getvar all and post the readout here. Delete your serial no and IMEI from the readout before posting it for your own security.

xunholyx said:
Hold down the power button + vol up till your phone reboots (it'll take a bit, 20 seconds or so). AS SOON AS THE SCREEN GOES BLACK slide your finger from vol up to vol down. That will take you to your bootloader.
Hook up to your PC and get into ADB. Enter the command fastboot getvar all and post the readout here. Delete your serial no and IMEI from the readout before posting it for your own security.
Click to expand...
Click to collapse
Ok there:
version: 0.5
version-bootloader: 3.16.0.0000
version-baseband: 1.14.21331931.LA21G
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno:
imei:
imei2: Not Support
meid: 00000000000000
product: m8_ul_ca
platform: hTCBmsm8974
modelid: 0P6B12000
cidnum: CWS__001
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 0a41237a
hbootpreupdate: 11
gencheckpt: 0

ben33891471 said:
Ok there:
version: 0.5
version-bootloader: 3.16.0.0000
version-baseband: 1.14.21331931.LA21G
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno:
imei:
imei2: Not Support
meid: 00000000000000
product: m8_ul_ca
platform: hTCBmsm8974
modelid: 0P6B12000
cidnum: CWS__001
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 0a41237a
hbootpreupdate: 11
gencheckpt: 0
Click to expand...
Click to collapse
You have old firmware and probably tried flashing a 4.4.4 ROM. I would suggest getting S-Off to update your firmware. Also your version main is blank. That would give your actual firmware version, but I can tell it is 4.4.2 based from your hboot number. It is blank because the TWRP version you are using is either old or 2.8.1.0. Both will cause that. Update your recovery as well.
In the meantime, flash this in recovery. It is a stock ROM backup that should fix your issue.
If you are going to try to run newer versions of ROMs, you'll need to have newer firmware. You can either get S-Off to do that, or convert back to stock (stock ROM and recovery, unmodified system partition) and take the OTAs.

xunholyx said:
You have old firmware and probably tried flashing a 4.4.4 ROM. I would suggest getting S-Off to update your firmware. Also your version main is blank. That would give your actual firmware version, but I can tell it is 4.4.2 based from your hboot number. It is blank because the TWRP version you are using is either old or 2.8.1.0. Both will cause that. Update your recovery as well.
In the meantime,flash this in recovery[/URL]. It is a stock ROM backup that should fix your issue.
If you are going to try to run newer versions of ROMs, you'll need to have newer firmware. You can either get S-Off to do that, or convert back to stock (stock ROM and recovery, unmodified system partition) and take the OTAs.
Click to expand...
Click to collapse
Yes, my phone is a at&t one, 4.4.2. tried to install the new version of android revolution hd with the lolipop 5.0.
I'm downloading the stock rom you gave me, but how do i install it? via cmd? becuase i cant transfer it to my htc..

ben33891471 said:
Yes, my phone is a at&t one, 4.4.2. tried to install the new version of android revolution hd with the lolipop 5.0.
I'm downloading the stock rom you gave me, but how do i install it? via cmd? becuase i cant transfer it to my htc..
Click to expand...
Click to collapse
You can't put it onto your extSD? In the bootloader menu, pick hboot (vol keys to navigate, power button to select) and it will give you the option for booting into recovery.
Or in ADB/fastboot issue the command fastboot reboot-recovery

xunholyx said:
You can't put it onto your extSD? In the bootloader menu, pick hboot (vol keys to navigate, power button to select) and it will give you the option for booting into recovery.
Or in ADB/fastboot issue the command fastboot reboot-recovery
Click to expand...
Click to collapse
I'll use my sister gs4 to copy the rom to the SD card. Back to you soon with answer

xunholyx said:
You can't put it onto your extSD? In the bootloader menu, pick hboot (vol keys to navigate, power button to select) and it will give you the option for booting into recovery.
Or in ADB/fastboot issue the command fastboot reboot-recovery
Click to expand...
Click to collapse
omg its says failed right away when i do "swipe to confirm flash".. what should i do?

ben33891471 said:
omg its says failed after 2 sec.. what should i do?
Click to expand...
Click to collapse
Okay. I didn't explain the process thinking you would realize that it is a nandroid backup and not a ROM.
You have to place it into your TWRP backup folder.
Here are the instructions:
Q : How do i restore the stock nandroid backup
A : In general :
- Place the nandroid backup unpacked on the sdcard of the phone in the right backup folder
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
If your backups are saved to your SD card, that's where to put it. It's always best to save nandroids to external.
---------- Post added at 01:16 PM ---------- Previous post was at 12:49 PM ----------
ben33891471 said:
omg its says failed right away when i do "swipe to confirm flash".. what should i do?
Click to expand...
Click to collapse
This will probably be easier for you. Download this ROM. It is 4.4.2 based and should work for you. It's not a backup, so no messing around putting it into a folder. Place it onto your extSD and flash it in recovery.

xunholyx said:
Okay. I didn't explain the process thinking you would realize that it is a nandroid backup and not a ROM.
You have to place it into your TWRP backup folder.
Here are the instructions:
Q : How do i restore the stock nandroid backup
A : In general :
- Place the nandroid backup unpacked on the sdcard of the phone in the right backup folder
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
If your backups are saved to your SD card, that's where to put it. It's always best to save nandroids to external.
---------- Post added at 01:16 PM ---------- Previous post was at 12:49 PM ----------
This will probably be easier for you. Download this ROM. It is 4.4.2 based and should work for you. It's not a backup, so no messing around putting it into a folder. Place it onto your extSD and flash it in recovery.
Click to expand...
Click to collapse
I cant to full wipe, only System and cache. Dalvik cache and Data says Failed right away.
I couldn't restore from the backup its says failed as well.
I'm downloading this rom now, hopefully it will work.
Just to be sure, after the download done, i move the zip to my SD card then go to recovery and flash? no other things to do? commands?

ben33891471 said:
I cant to full wipe, only System and cache. Dalvik cache and Data says Failed right away.
I couldn't restore from the backup its says failed as well.
I'm downloading this rom now, hopefully it will work.
Just to be sure, after the download done, i move the zip to my SD card then go to recovery and flash? no other things to do? commands?
Click to expand...
Click to collapse
Yes, just flash it. If you have issues after the flash, retry the wipes and flash it again. Not being able to wipe dalvik and data is strange. What version of TWRP are you using? The newest is 2.8.4.0. I'm using 2.8.3.0 and don't have these problems. You should probably update your recovery. The system, cache, and dalvik get wiped automatically during the ROM install as the devs have that put into the install script.

xunholyx said:
Yes, just flash it. If you have issues after the flash, retry the wipes and flash it again. Not being able to wipe dalvik and data is strange. What version of TWRP are you using? The newest is 2.8.4.0. I'm using 2.8.3.0 and don't have these problems. You should probably update your recovery. The system, cache, and dalvik get wiped automatically during the ROM install as the devs have that put into the install script.
Click to expand...
Click to collapse
This is the name of file Official-TWRP-m8wlv
maybe you could give me the TWRP you have?

ben33891471 said:
This is the name of file Official-TWRP-m8wlv
maybe you could give me the TWRP you have?
Click to expand...
Click to collapse
That's the version for Verizon. Are you on Verizon? If so, you can find all the Verizon TWRP downloads here: http://techerrata.com/browse/twrp2/m8_wlv
If you aren't on Verizon, then that will be what is causing your issues.

xunholyx said:
That's the version for Verizon. Are you on Verizon? If so, you can find all the Verizon TWRP downloads here: http://techerrata.com/browse/twrp2/m8_wlv
If you aren't on Verizon, then that will be what is causing your issues.
Click to expand...
Click to collapse
Oh crap
I'm on AT&T
Just download this one http://www.handy-faq.de/forum/htc_o..._0_touch_recovery_2015_01_01_twrp_themes.html
is it ok?

ben33891471 said:
Oh crap
I'm on AT&T
Just download this one http://www.handy-faq.de/forum/htc_o..._0_touch_recovery_2015_01_01_twrp_themes.html
is it ok?
Click to expand...
Click to collapse
Maybe. The link I gave you is from the official TWRP website, just like this next link is. Flashing a recovery not meant for your device can really screw stuff up and possibly hard brick your phone. Be more careful.
You will want to use one of these recovery versions. I'm using 2.8.3.0, but I have heard good things about the newest 2.8.4.0.
http://techerrata.com/browse/twrp2/m8

ben33891471 said:
Oh crap
I'm on AT&T
Just download this one http://www.handy-faq.de/forum/htc_o..._0_touch_recovery_2015_01_01_twrp_themes.html
is it ok?
Click to expand...
Click to collapse
At&t and GSM variants use same recovery so flash 2.8.4.0 provided in the link above BY xunholyx.
Also i recommend to upgrade the rom by running stock backup and then update through official OTA ..

xunholyx said:
Maybe. The link I gave you is from the official TWRP website, just like this next link is. Flashing a recovery not meant for your device can really screw stuff up and possibly hard brick your phone. Be more careful.
You will want to use one of these recovery versions. I'm using 2.8.3.0, but I have heard good things about the newest 2.8.4.0.
http://techerrata.com/browse/twrp2/m8
Click to expand...
Click to collapse
Allright thanx, this one is for AT&T, right?
Listen the download of the viperone rom just stop in 695 MB
I really dont know what to do, you think after ill put this TWRP recovery you just bring me, and try to flash revolution rom or used the backup it will work?
Even if i dont have s-off ?

xunholyx said:
Maybe. The link I gave you is from the official TWRP website, just like this next link is. Flashing a recovery not meant for your device can really screw stuff up and possibly hard brick your phone. Be more careful.
You will want to use one of these recovery versions. I'm using 2.8.3.0, but I have heard good things about the newest 2.8.4.0.
http://techerrata.com/browse/twrp2/m8
Click to expand...
Click to collapse
ahsan64 said:
At&t and GSM variants use same recovery so flash 2.8.4.0 provided in the link above BY xunholyx.
Also i recommend to upgrade the rom by running stock backup and then update through official OTA ..
Click to expand...
Click to collapse
damm its not working not the TWRP 2.8.4.0 and not the 2.8.3.0
i just ****ing want my phone to get work again why im ****ing stupid i screw my phone
i dont care dont have root and the other **** things just want my phone to work again dont care even on stock
please help me i get nervous its almost 12 hours im try to solve this

ben33891471 said:
damm its not working not the TWRP 2.8.4.0 and not the 2.8.3.0
i just ****ing want my phone to get work again why im ****ing stupid i screw my phone
i dont care dont have root and the other **** things just want my phone to work again dont care even on stock
please help me i get nervous its almost 12 hours im try to solve this
Click to expand...
Click to collapse
what's not working.. ?
Or any error while installing rom .
Can you please show the commands how you are flashing recovery .

ahsan64 said:
what's not working.. "
Or error while installing rom .
Can you please show the commands how you are flashing recovery .
Click to expand...
Click to collapse
I type fastboot boot and then paste the file its done and restart but stock on the logo with the red words and when i tap on the screen there is vibrate but thats all
please help me bro i dont know what to do

[Solved] Cannot install CM12 due to outdated bootloader

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.

htc one m8 twrp won't boot

Hello,
i have a problem with my htc one m8 any help will be appreciate.
i wan't to install the new rom viperone m8 but when i try to flash twrp latest version the recovery don't load it's reboot the bootloader only and don't get access to twrp to install rom
i'm able to flash philz_touch_6.26.6-m8.img and install skydragon latest rom
i'm also able to flash twrp-2.7.0.2-m8.img
here is my getvar all
c:\>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.21331147A1.06
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: <----------- i have doubt on this why it's empty
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__247
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: eb00c9d0
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.016s
there is any solution for my problem?
can i install viperone 4.6.0 with wrp-2.7.0.2-m8.img
bootloader is unlocked and phone is s-off
Thank you in advance for your help.

First, remove Serial & Imei no from your post.
Can you remember whether your stock ROM is 4.21.1020.1 or 3.31.1020.9 ? Because both have hboot 3.19.0000
Don't use TWRP 2.7.0.2, use at least 2.8.4.0 or newer or latest.
Run these command
fastboot flash recovery NameofRecovery.img
fastboot erase cache
fastboot reboot-bootloader
now you should be able to enter recovery.
Advisable to reboot your device after doing fastboot erase cache and then boot to recovery

Hello,
thank you very much for your help.
i was on 4.21.1020.1
yes i have tried to use twrp-2.8.4.0-m8.img but not working
i also did what you said
fastboot flash recovery NameofRecovery.img
fastboot erase cache
fastboot reboot-bootloader
it's boot to bootloader it don't show twrp recovery.
very strange
thank you for your assistance
ckpv5 said:
First, remove Serial & Imei no from your post.
Can you remember whether your stock ROM is 4.21.1020.1 or 3.31.1020.9 ? Because both have hboot 3.19.0000
Don't use TWRP 2.7.0.2, use at least 2.8.4.0 or newer or latest.
Run these command
fastboot flash recovery NameofRecovery.img
fastboot erase cache
fastboot reboot-bootloader
now you should be able to enter recovery.
Advisable to reboot your device after doing fastboot erase cache and then boot to recovery
Click to expand...
Click to collapse

Yeah .. that's strange because your device on latest hboot.
Since your device is S-Off .. may I know why did you S-Off it ?
Seeing your device has stock CID/MID .. I'm scare that you jump from a lower 3.16.0000 hboot straight to 3.19.0000
Some people face problem too when they jump hboot.

i had to S-Off because in skydragon installation guides requirements
s-off is more easy
there is any solution to back and redo everything.
Thank you
ckpv5 said:
Yeah .. that's strange because your device on latest hboot.
Since your device is S-Off .. may I know why did you S-Off it ?
Seeing your device has stock CID/MID .. I'm scare that you jump from a lower 3.16.0000 hboot straight to 3.19.0000
Some people face problem too when they jump hboot.
Click to expand...
Click to collapse

Hello
Anyone got this type of problems?
There is any solution ?
Thank you

novalayer said:
yes i have tried to use twrp-2.8.4.0-m8.img but not working
i also did what you said
fastboot flash recovery NameofRecovery.img
Click to expand...
Click to collapse
You understand "NameofRecovery.img" needs to be the actual file name (such as: twrp-2.8.4.0-m8.img)?

redpoint73 said:
You understand "NameofRecovery.img" needs to be the actual file name (such as: twrp-2.8.4.0-m8.img)?
Click to expand...
Click to collapse
@redpoint73, I think that is refering to an issue that occured with the new update from HTC. I have it too and another users the same. The recovery TWRP higher than twrp-2.8.1.0-m8.img does not boot and enter back to bootloader. We discused this in another thread and we don't have an resolution until now. Is not manifesting on all the phones and is not region and provider dependent. In this thread you can see more details. http://forum.xda-developers.com/htc-one-m8/help/htc-one-m8-stuck-boot-screen-t3186424

whiperhack said:
@redpoint73, I think that is refering to an issue that occured with the new update from HTC. I have it too and another users the same. The recovery TWRP higher than twrp-2.8.1.0-m8.img does not boot and enter back to bootloader. We discused this in another thread and we don't have an resolution until now. Is not manifesting on all the phones and is not region and provider dependent. In this thread you can see more details. http://forum.xda-developers.com/htc-one-m8/help/htc-one-m8-stuck-boot-screen-t3186424
Click to expand...
Click to collapse
Good info. Makes sense since he was able to flash TWRP 2.7.something.
But it would be useful for folks when they seek help to actually give the exact fastboot commands used, and not just cut and paste from somebody else's post (so we can't even be sure if he is using the right commands to install TWRP).

For some reason I only can use twrp-2.7.0.2. All the others get back to bootloader immediately. Is there a solution? It happens after going back to sense from GPE. I followed this thread: http://forum.xda-developers.com/showthread.php?t=2733523
Edit: Maybe is has somrthing to do with hboot? I have 3 .19.0.000

Petert87 said:
For some reason I only can use twrp-2.7.0.2. All the others get back to bootloader immediately. Is there a solution? It happens after going back to sense from GPE. I followed this thread: http://forum.xda-developers.com/showthread.php?t=2733523
Edit: Maybe is has somrthing to do with hboot? I have 3 .19.0.000
Click to expand...
Click to collapse
Something isn't right here. If you actually followed the thread you linked, you would not be on hboot 3.19.
The thread is also incredibly obsolete, as in 3 software/firmware generations old (the current is 4.16.xxx).
You most likely can't use the current TWRP due to outdated firmware. But you haven't provided enough info to tell for sure. Do fastboot getvar all and post the output (be sure to delete IMEI and serial numbers before posting the getvar data, as these are personal info).

redpoint73 said:
Something isn't right here. If you actually followed the thread you linked, you would not be on hboot 3.19.
The thread is also incredibly obsolete, as in 3 software/firmware generations old (the current is 4.16.xxx).
You most likely can't use the current TWRP due to outdated firmware. But you haven't provided enough info to tell for sure. Do fastboot getvar all and post the output (be sure to delete IMEI and serial numbers before posting the getvar data, as these are personal info).
Click to expand...
Click to collapse
I'm at work so atm cant provide a getvar all. What I did:
write cid 11111111, flashed 1.54.401.5-W_Splash.zip, reboot stock recovery, factory reset, installed TWRP. Again factory reset in TWRP. Then installed MaximusHD. Then I installed the first Nandroid I had from my software x.xx.161.x. Then did all OTA's. I think my hboot never updated during OTA.s

Petert87 said:
Then did all OTA's. I think my hboot never updated during OTA.s
Click to expand...
Click to collapse
And why do you think that? If that were the case, you would not be on hboot 3.19. Flashing 1.54 firmware would put you on hboot 3.16.

redpoint73 said:
And why do you think that? If that were the case, you would not be on hboot 3.19. Flashing 1.54 firmware would put you on hboot 3.16.
Click to expand...
Click to collapse
I thought that OTA updates the firmware automatically

Petert87 said:
I thought that OTA updates the firmware automatically
Click to expand...
Click to collapse
Yes, it does.
But why do you think it failed to do so?

redpoint73 said:
Yes, it does.
But why do you think it failed to do so?
Click to expand...
Click to collapse
Because I'm on old hboot and latest lollipop.

Petert87 said:
Because I'm on old hboot and latest lollipop.
Click to expand...
Click to collapse
You stated your were on hboot 3.19; which is the latest hboot there is.

redpoint73 said:
You stated your were on hboot 3.19; which is the latest hboot there is.
Click to expand...
Click to collapse
Sorry, there was a misunderstanding. I thought you said the latest was 4.16.xxx but that was the software not hboot. Software is 4.19.161.3

Petert87 said:
Sorry, there was a misunderstanding. I thought you said the latest was 4.16.xxx but that was the software not hboot. Software is 4.19.161.3
Click to expand...
Click to collapse
I see.
Well, it would seem that your firmware is up to date. So I see no reason why TWRP 2.8 would cause any trouble.
What versions of TWRP did you try exactly? I would focus on the current/latest which is 2.8.7.

redpoint73 said:
I see.
Well, it would seem that your firmware is up to date. So I see no reason why TWRP 2.8 would cause any trouble.
What versions of TWRP did you try exactly? I would focus on the current/latest which is 2.8.7.
Click to expand...
Click to collapse
I tried every version until one works and stopped at that one.

Unable to install/enter twrp recovery

I purchased a HTC M8 dual sim phone. I unlocked the bootloader and flashed the latest twrp on it, all seemed fine. However when rebooting to recovery it's stuck at "entering recovery...". There's tons of threads about that suggesting various version of twrp, so far I have tried (erasing cache in between):
twrp-2.7.1.0-m8.img
twrp-2.8.0.0-m8.img
twrp-2.8.1.0-m8.img
twrp-2.8.3.0-m8.img
twrp-2.8.7.0-m8.img
twrp-3.0.0-1-m8.img
twrp-3.1.1-0-m8.img
twrp-3.2.3-1-m8.img
twrp-3.3.0-0-m8.img
twrp-3.3.1-0-m8.img
However I always get either stuck at entering recovery or go directly back to bootloader.
So I wanted to do OTA updates first, but HTC doesn't allow me to anymore. So I installed stock recovery from here: https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860 Still couldn't install the OTA. So i (probably stupidly followed these instructions to get S-ON: https://forum.xda-developers.com/ve...w-to-to-stock-unroot-lock-bootloader-t3505783
The getvar all reports:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.22.30306251.27G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.33.401.6
(bootloader) version-misc: PVT SHIP S-ON
[...]
(bootloader) meid: A1000037D21505
(bootloader) product: m8_dugl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B41000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 6b903f73
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
In some old threads about dual sim "special" twrp imgs like TWRP_Recovery_2.8.0.5_M8_CPTB.img are recommended, but the download links are broken.
So in the end I'd just like to get twrp installed, from there I know my way around (I'd have tried lineage first). Any pointers/ideas what to try next to achieve that?

imsodin said:
Still couldn't install the OTA. So i (probably stupidly followed these instructions to get S-ON: https://forum.xda-developers.com/ve...w-to-to-stock-unroot-lock-bootloader-t3505783
Click to expand...
Click to collapse
S-off does not limit OTA. So maybe not the best idea to make it s-on again. On the other hand, s-on will not limit installation of TWRP, custom ROMs, etc.
Also, if the device was made s-off by sunshine, you should be able to install the sunshine app, and just s-off it again with no fee. The sunshine license is forever associated with the device, and if it was purchased once, you can s-off that device again and again.
imsodin said:
In some old threads about dual sim "special" twrp imgs like TWRP_Recovery_2.8.0.5_M8_CPTB.img are recommended, but the download links are broken.
Click to expand...
Click to collapse
Far as I can recall, the dual SIM M8 did require it's own version of TWRP. Keep trying to find a working link, is all you can do.

redpoint73 said:
S-off does not limit OTA. So maybe not the best idea to make it s-on again. On the other hand, s-on will not limit installation of TWRP, custom ROMs, etc.
Also, if the device was made s-off by sunshine, you should be able to install the sunshine app, and just s-off it again with no fee. The sunshine license is forever associated with the device, and if it was purchased once, you can s-off that device again and again.
Far as I can recall, the dual SIM M8 did require it's own version of TWRP. Keep trying to find a working link, is all you can do.
Click to expand...
Click to collapse
Good to know about s-on, then it won't bother me.
As to a working link: They all go to yandex/mega/..., i.e. no luck with any archives. I scoured xda and google, and all broken links or pointers to the "normal" m8 twrp (often explicitly stating that it's the same for dual sim, e.g. https://forum.xda-developers.com/htc-one-m8/help/twrp-recovert-htc-one-m8-dual-sim-t3384609). I really don't want to write this phone off, well mostly I don't want to look for an alternative, but I am at my wits end and wasting too much time

imsodin said:
I scoured xda and google, and all broken links or pointers to the "normal" m8 twrp (often explicitly stating that it's the same for dual sim, e.g. https://forum.xda-developers.com/htc-one-m8/help/twrp-recovert-htc-one-m8-dual-sim-t3384609).
Click to expand...
Click to collapse
It is confusing to determine whether the dual SIM requires its own recovery or not, as I looked at some threads myself. But the thread you linked in particular, the guy that says it is the same recovery (as the single SIM M8) ckpv5, I don't think I've ever seen him wrong about anything. So I would take his word for it.
Based on his thread here: https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
the proper TWRP version for OS version 3.xx should be TWRP 2.8.3.0, so you should focus there. I know you tried it already, but it doesn't hurt to try it again.

TLDR:
This device isn't unproblematic to handle - don't just assume anything from previous experience as I did. I manages to create a paperweight (technically maybe recoverable, but I don't have the patience anymore to try).
Thanks for keeping me on the right track, I managed to get twrp 2.8.1.0 (sic!) to work. I doubt the following will be helpful to anyone, but who knows:
fastboot getvar all showed the above output, i.e. version 3.33.401.6. However when I tried to get the downloaded OTA (for the firmware) I noticed it says it will upgrade to 3.33.401.6. So checking the settings in Android I find that my actual version is 1.45.401.12. Which according to https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860 means you should use twrp 2.8.1.0.
I was pretty sure I already tried that, but I probably didn't. I did find a dubious claim that you need to flash the recovery twice immediately and then erase cache and did that for good measure (I know I am not supposed to, but when it comes to all things android/phone I do believe in "weird s**t").
Now after that I installed LOS 16 - well I tried. TWRP fails to report the model which aborts the installation. So I removed the asserts from LOS' install script. Stupid move: It doesn't only check the model but also the bootlocker - and that was actually incompatible. Obviously as I have no reason to go back to some ancient HTC OS I didn't do a backup. So now I can't boot a system to get to s-off and can't install an RUU - which for all I read is the only way to get back on track to update the firmware. Just for funsies I also tried to flash a newer boot.img in hopes to get to bootloader 0.19, but that didn't have any effect.
The only way out would be to install some ROM that runs on bootloader 0.18 - I didn't find any. Then get to s-off using sunshine, then go through the entire back-to-stock dance and finally use OTAs to update firmware and once done go back to custom. Well, actually that would have been the intuitive and logical thing to do in the first place: Exhaust all official upgrades, backup, go custom. But inpatient me wanted to take the shortcut to custom and now I spent hours for nothing.
Sorry for the lengthy rant

See my comments below in red font:
imsodin said:
TLDR:
fastboot getvar all showed the above output, i.e. version 3.33.401.6. However when I tried to get the downloaded OTA (for the firmware) I noticed it says it will upgrade to 3.33.401.6. So checking the settings in Android I find that my actual version is 1.45.401.12. Which according to https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860 means you should use twrp 2.8.1.0.
The OS number reported by getvar is the correct (current) firmware. The OS number shown in settings is not to be trusted. At some point, it looks like somebody flashed a 1.45.xxx based ROM, but the phone still has 3.33.xx firmware. You want the ROM to correspond with the firmware.
Now after that I installed LOS 16 - well I tried. TWRP fails to report the model which aborts the installation. So I removed the asserts from LOS' install script. Stupid move: It doesn't only check the model but also the bootlocker - and that was actually incompatible. Obviously as I have no reason to go back to some ancient HTC OS I didn't do a backup. So now I can't boot a system to get to s-off and can't install an RUU - which for all I read is the only way to get back on track to update the firmware.
You don't need s-off to flash an RUU intended for your version M8 (dual SIM). If the RUU is not for the dual SIM, it will probably brick your phone if you flashed it. So those safeguards exist for a reason.
If you can find RUUs for your dual SIM M8, that would be an easy way out. But I don't think I've seen such an animal.
Other options might be:
- (if you can find them) flash 3.33.401.6 stock backup and stock recovery. Then OTA update.
- (if you can find it) flash 4.30.401.16 signed firmware, and restore stock TWRP backup 4.30.401.16 that ckpv5 posted in his collection.
- (if you can find it) flash 4.30.401.16 signed firmware and flash LOS16, as that firmware might put you on the right bootloader and firmware to work with that ROM.
I know these unfortunately are all high bars to meet, as the dual SIM doesn't have a lot of resources posted.
Just for funsies I also tried to flash a newer boot.img in hopes to get to bootloader 0.19, but that didn't have any effect.
boot.img is a completely separate partition from bootloader. They sound the same, but not the same. boot.img is essentially the kernel. You can't flash bootloader by itself with s-on. But you can flash bootloader with the correct RUU or signed firmware for your version M8 (CID, MID).
Click to expand...
Click to collapse

The problem is my CID has been changed to 111111 (which I read is some kind of magical super-power CID, don't know why though ), thus I can't flash any RUUs. I tried flashing a few x.x.401.x firmwares without success.
Anyway thanks again for helping me - in the meantime I lost the phone I wanted to replace, which was the final trigger to abandon this project and just get a cheap new phone that I'll hopefully not butcher (for now (still gets security updates) it'll get Magisk Root only - after upgrading and backing up).