Develop Bugs

[Q] Cannot flash Stock RUU

When I got my M8, I achieved S-OFF using Sunshine. I have to do a warranty exchange.
I am now trying to flash stock RUU, but flashing fails with the error
Code:
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
FAILED (remote: 32 header error)
I googled around and someone said this is due to a corrupted zip, but I checked the zip's md5 and it matches with the one on this forum. Any help is appreciated.

siddardhab said:
When I got my M8, I achieved S-OFF using Sunshine. I have to do a warranty exchange.
I am now trying to flash stock RUU, but flashing fails with the error
Code:
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
FAILED (remote: 32 header error)
I googled around and someone said this is due to a corrupted zip, but I checked the zip's md5 and it matches with the one on this forum. Any help is appreciated.
Click to expand...
Click to collapse
Did you happen to run the gpe ruu?

Yes, I flashed the GPE RUU, I then followed instructions in this post
Flashed the firmware mentioned in that post
Flashed TWRP
Restored Stock Nandroid backup
Changed the Cid to Tmobile Cid
Relocked the bootloader, becasue I think flashing stock RUU requires a locked bootloader
I then flashed Stock RUU, but I can't seem to get past the above erro.

siddardhab said:
Yes, I flashed the GPE RUU, I then followed instructions in this post
Flashed the firmware mentioned in that post
Flashed TWRP
Restored Stock Nandroid backup
Changed the Cid to Tmobile Cid
Relocked the bootloader, becasue I think flashing stock RUU requires a locked bootloader
I then flashed Stock RUU, but I can't seem to get past the above erro.
Click to expand...
Click to collapse
Here's what worked for me on the same issue.
1.) Change CID to 11111111 (SuperCID)
2.) Flash firmware file from post.
3.) Flash TWRP
4.) Flash ViperRom through TWRP, and allow to boot.
5.) Run T-mobile Ruu.
I never bothered to change my CID back to T-MOB010.
This worked for me. hopefully it helps.

Hmm, well I have a question.
Since I already restored Stock Nandroid, can I just flash Stock recovery, relock the bootloader and remove the tampered flag.
Is the result going to be any different than going via RUU method?

siddardhab said:
Hmm, well I have a question.
Since I already restored Stock Nandroid, can I just flash Stock recovery, relock the bootloader and remove the tampered flag.
Is the result going to be any different than going via RUU method?
Click to expand...
Click to collapse
If you are S-Off, I don't believe that bootloader lock state matters anymore for ruu. I never relocked my bootloader. You can try flashing the stock recovery and relocking the bootloader to do the ruu. I was really just trying everything I could think of to get back to stock. I left my CID at SuperCID, never relocked my bootloader at all and everything has worked for me.

phil.culler said:
If you are S-Off, I don't believe that bootloader lock state matters anymore for ruu. I never relocked my bootloader. You can try flashing the stock recovery and relocking the bootloader to do the ruu. I was really just trying everything I could think of to get back to stock. I left my CID at SuperCID, never relocked my bootloader at all and everything has worked for me.
Click to expand...
Click to collapse
This is what I think I am going to do. Keep S-off...And everything else stock. Although I might lock the bootloader for security (plus it's so easy with Scotty1223's method).
But I'm also thinking...how do you do nandroids? Do you just run a custom recovery from ADB (without actually changing the stock recovery on the phone) and create one that way? Or do you use the HTC backup? I have never looked at the HTC backup, but I assumed was for sd data only.
Also, I know getting SuperCID essentially de-brands your phone...But what practical use does it have?

[Q] Help Flashing Stock ROM onto Developer M8

Hey guys,
So I have a Developer Edition M8 (HBOOT- 3.19), and I went through multiple steps trying to get GPE onto it. Since I'm posting here, I screwed up along the way, and Google hasn't been to helpful. To put it simply, I do not have an OS on the phone right now, and need to flash stock back onto it, and am having trouble because TWRP recovery no longer wishes to run.
Here's what happened:
I was following an outdated guide to getting GPE (I didn't know it was outdated at the time) and it said to flash insertcoin in order to be able to use firewater to get S-Off. I flashed insertcoin, realized firewater was no longer supporeted, and felt like I had wasted a few hours. I then found sunshine and tried to use it, but insertcoin was not close enough to stock to be compatible, so I tried to flash a stock ROM I found on this thread here onto the phone. I am fairly certain I downloaded the correct file, as the HBOOT 3.19 leads to the 3.xx file, and my CIS is BS_US002, so I downloaded the 3.28 file available. I took the zip, placed it onto the phone, and wiped insertcoin, and tried to install the stock ROM. Well, it failed.
I went back to the drawing board, actually read the instructions, and did this: I placed the unpacked zip into the TWRP/Backups folder on the phone. I then used fastboot flash recovery FILE.IMG to flash boot.emmc.win from my computer to the phone. Now, when I try to go into recovery to wipe and recover, it no longer enters TWRP. It is stuck on the HTC screen.
What do I do from here? My main goal is just to get stock back onto the phone, and I hope I did not mess up the phone.
To put all phone info in one place:
HTC One M8 Developer Edition
HBOOT- 3.19
CID- BS_US002
Thank you!

rbalutiu said:
Hey guys,
So I have a Developer Edition M8 (HBOOT- 3.19), and I went through multiple steps trying to get GPE onto it. Since I'm posting here, I screwed up along the way, and Google hasn't been to helpful. To put it simply, I do not have an OS on the phone right now, and need to flash stock back onto it, and am having trouble because TWRP recovery no longer wishes to run.
Here's what happened:
I was following an outdated guide to getting GPE (I didn't know it was outdated at the time) and it said to flash insertcoin in order to be able to use firewater to get S-Off. I flashed insertcoin, realized firewater was no longer supporeted, and felt like I had wasted a few hours. I then found sunshine and tried to use it, but insertcoin was not close enough to stock to be compatible, so I tried to flash a stock ROM I found on this thread here onto the phone. I am fairly certain I downloaded the correct file, as the HBOOT 3.19 leads to the 3.xx file, and my CIS is BS_US002, so I downloaded the 3.28 file available. I took the zip, placed it onto the phone, and wiped insertcoin, and tried to install the stock ROM. Well, it failed.
I went back to the drawing board, actually read the instructions, and did this: I placed the unpacked zip into the TWRP/Backups folder on the phone. I then used fastboot flash recovery FILE.IMG to flash boot.emmc.win from my computer to the phone. Now, when I try to go into recovery to wipe and recover, it no longer enters TWRP. It is stuck on the HTC screen.
What do I do from here? My main goal is just to get stock back onto the phone, and I hope I did not mess up the phone.
To put all phone info in one place:
HTC One M8 Developer Edition
HBOOT- 3.19
CID- BS_US002
Thank you!
Click to expand...
Click to collapse
use this
http://dl3.htc.com/application/RUU_..._2G_20.63.4196.01_release_394319_signed_2.exe

clsA said:
use this
Click to expand...
Click to collapse
Just flash the exe onto the phone using the fastboot command? or is there something more to it?

rbalutiu said:
Just flash the exe onto the phone using the fastboot command? or is there something more to it?
Click to expand...
Click to collapse
it's a RUU just click it in windows
no flashing just put the phone in bootloader fastboot usb

clsA said:
it's a RUU just click it in windows
no flashing just put the phone in bootloader fastboot usb
Click to expand...
Click to collapse
I downloaded the RUU and tried running it: it gave me error code 155 and said that it cannot update the phone. Right below it also states to get the correct RUU and try again, although I think this is the right one.
Is there any way to troubleshoot this/fix this?

rbalutiu said:
I downloaded the RUU and tried running it: it gave me error code 155 and said that it cannot update the phone. Right below it also states to get the correct RUU and try again, although I think this is the right one.
Is there any way to troubleshoot this/fix this?
Click to expand...
Click to collapse
Flash this first
https://www.androidfilehost.com/?fid=95784891001612796
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot-bootloader
Then flash the RUU ...

clsA said:
Flash this first
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot-bootloader
Then flash the RUU ...
Click to expand...
Click to collapse
I put in both flash zip commands and both resulted in failures, stating "remote: 99 unknown fail". Was this intended or something went wrong?

rbalutiu said:
I put in both flash zip commands and both resulted in failures, stating "remote: 99 unknown fail". Was this intended or something went wrong?
Click to expand...
Click to collapse
I figured out the problem but still no solution: both of these require s-off. The bootloader is unlocked, but I currently have S-On. What can we do to either make it S-Off or put the stock ROM on the phone?

The ruu and Firmware works fine with s-on
post the command window output ..your doing something wrong

rbalutiu said:
I figured out the problem but still no solution: both of these require s-off. The bootloader is unlocked, but I currently have S-On. What can we do to either make it S-Off or put the stock ROM on the phone?
Click to expand...
Click to collapse
bootloader needs to be relocked when you are s-on, for ruu mode flashing (firmware.zip or full ruu)

nkk71 said:
bootloader needs to be relocked when you are s-on, for ruu mode flashing (firmware.zip or full ruu)
Click to expand...
Click to collapse
Thanks nkk71, but the Developer edition he has comes with the bootloader unlocked .. i never locked mine to flash the RUU ( I did s-off the phone so I'm not sure if it's needed or not)
OP: use fastboot oem lock to relock your bootloader and try the RUU again

clsA said:
Thanks nkk71, but the Developer edition he has comes with the bootloader unlocked .. i never locked mine to flash the RUU ( I did s-off the phone so I'm not sure if it's needed or not)
OP: use fastboot oem lock to relock your bootloader and try the RUU again
Click to expand...
Click to collapse
Yep, I know it's silly that the US Dev edition (bootloader unlocked by default), has to be relocked for RUU mode flash with S-ON... same thing on the M7

nkk71 said:
Yep, I know it's silly that the US Dev edition (bootloader unlocked by default), has to be relocked for RUU mode flash with S-ON... same thing on the M7
Click to expand...
Click to collapse
Progress made.
I locked bootloader, ran the RUU, got stock back onto there. Then unlocked again, rerooted, and got s-off. Now I'm trying to install the GE RUU as said by this site and its giving me something that says "FAILED <remote: 42 custom id check fail>" .
Just this one last step, what can I do to go around this and fix this?
Thank you both for your help so far!

rbalutiu said:
Progress made.
I locked bootloader, ran the RUU, got stock back onto there. Then unlocked again, rerooted, and got s-off. Now I'm trying to install the GE RUU as said by this site and its giving me something that says "FAILED <remote: 42 custom id check fail>" .
Just this one last step, what can I do to go around this and fix this?
Thank you both for your help so far!
Click to expand...
Click to collapse
you'll need to edit the android_info.txt to include your MID and CID
Should look like this
modelid: 0P6B12000
modelid: 0P6B17000
modelid: 0P6B1****
cidnum: 11111111
cidnum: T-MOB010
cidnum: CWS__001
cidnum: BS_US001
cidnum: BS_US002
cidnum: GOOGL001
mainver: 3.11.1700.5
btype:0
aareport:1
hbootpreupdate:3
Click to expand...
Click to collapse
And you'll want these new files, not the old one's on that site
Lollipop > http://forum.xda-developers.com/showthread.php?t=2708589
and the older Build: 4.4.4 - 2.12.1700.1 about half way down the page here >> http://www.graffixnyc.com/m8.php

clsA said:
you'll need to edit the android_info.txt to include your MID and CID
Should look like this
And you'll want these new files, not the old one's on that site
Lollipop > http://forum.xda-developers.com/showthread.php?t=2708589
and the older Build: 4.4.4 - 2.12.1700.1 about half way down the page here >> http://www.graffixnyc.com/m8.php
Click to expand...
Click to collapse
Thanks so much! Got 5.0.1 running on the phone, thanks for all the help!

M9 soft bricked after 7.0 update

Hi guys,
I've updated my M9 to 7.0 through OTA update. After installing my phone boots directly in to the bootloader. I can enter download and recovery mode without any trouble but that's about it. When i try to boot in to the phone it boots back to the bootloader. My phone is S-ON so i can't flash a RUU through ADB, however the phone is unlocked.
I tried to flash a RUU through the external micro SD card method but that failed because the firmware is lower than my firmware.
Current M9 Status:
*Unlocked*
S-On
Firmware 4.14.401.7
Stuck in bootloader/recovery/downloadmode
I tried everything to my knowledge. Is there someone who encountered the same problems as i do? Or is there someone who knows a solution to all of this?

ruubs said:
Hi guys,
I've updated my M9 to 7.0 through OTA update. After installing my phone boots directly in to the bootloader. I can enter download and recovery mode without any trouble but that's about it. When i try to boot in to the phone it boots back to the bootloader. My phone is S-ON so i can't flash a RUU through ADB, however the phone is unlocked.
I tried to flash a RUU through the external micro SD card method but that failed because the firmware is lower than my firmware.
Current M9 Status:
*Unlocked*
S-On
Firmware 4.14.401.7
Stuck in bootloader/recovery/downloadmode
I tried everything to my knowledge. Is there someone who encountered the same problems as i do? Or is there someone who knows a solution to all of this?
Click to expand...
Click to collapse
Some questions:
Did you have a completely stock device when you applied the OTA?
Did it ever successfully boot into Nougat, or did the OTA immediately result in the current condition?
I wonder if you could either flash TWRP or use it via your computer (there's a way to run it in your phone without installing it) so that you could apply the OTA again. I'm not sure if it would fix whatever went wrong, though.
Alternatively, you could flash a ROM (again, via TWRP), obtain S-OFF, change your MID & CID to the developer version and apply that RUU.

computerslayer said:
Some questions:
Did you have a completely stock device when you applied the OTA?
Did it ever successfully boot into Nougat, or did the OTA immediately result in the current condition?
I wonder if you could either flash TWRP or use it via your computer (there's a way to run it in your phone without installing it) so that you could apply the OTA again. I'm not sure if it would fix whatever went wrong, though.
Alternatively, you could flash a ROM (again, via TWRP), obtain S-OFF, change your MID & CID to the developer version and apply that RUU.
Click to expand...
Click to collapse
I did have a completely stock device before i installed the OTA.
It did never successvully booted into nougat. Right after the install it booted in to the bootloader.
How can i flash TWRP or another ROM while im S-ON? Or am i wrong in this? Please help me out

ruubs said:
I did have a completely stock device before i installed the OTA.
It did never successvully booted into nougat. Right after the install it booted in to the bootloader.
How can i flash TWRP or another ROM while im S-ON? Or am i wrong in this? Please help me out
Click to expand...
Click to collapse
S-ON is no obstacle to flashing TWRP or another ROM. You will need to unlock your bootloader in order to do either but I assumed that you had already done this since you posted that your status is unlocked.

computerslayer said:
S-ON is no obstacle to flashing TWRP or another ROM. You will need to unlock your bootloader in order to do either but I assumed that you had already done this since you posted that your status is unlocked.
Click to expand...
Click to collapse
The phone status is indeed unlocked.
I didn't know I could flash TWRP or a ROM. I thought I needed S-OFF for that.
I want my phone to be as stock as possible. Can I flash a stock ROM or does it have to be a custom one.
And do i need to flash TWRP in order to flash a ROM?

So i've searched around and came to the conclusion to fix my phone is to flash TWRP first. After that FLASH a custom ROM, if that goes as planned S-OFF my phone with the SunShine method. After that go back to stock and hope everything goes well.

ruubs said:
So i've searched around and came to the conclusion to fix my phone is to flash TWRP first. After that FLASH a custom ROM, if that goes as planned S-OFF my phone with the SunShine method. After that go back to stock and hope everything goes well.
Click to expand...
Click to collapse
That's the route I would take too. The readme thread has a section dedicated to changing your SKU in order to use other RUUs.

How to preserve stock ROM

So, I picked up a used HTC 10 yesterday, stock Nougat kinda sucks in terms of battery life and I want to switch to RR, however, my previous 2 HTC's had been S-OFF'd by me to switch them to the .401 WWE firmware, however this one is already on .401 so I don't want to get S-OFF since I don't really need it.
If I was to unlock the bootloader and flash RR, and then, want to go back to stock, how would I go about it?
As far as I know, there aren't any RUUs available for 2.41.401.41, so would flashing an older RUU work, and then taking an OTA to the newer firmware?
This is what download mode says:
*** LOCKED ***
htc_pmeuhl PVT S-ON
LK-1.0.0.0000
[email protected]
OpenDSP-v20.0.8996.00007_0809
OS-2.41.401.41
Aug 2 2017, 12:18:15 (857212)

murtaza02 said:
So, I picked up a used HTC 10 yesterday, stock Nougat kinda sucks in terms of battery life and I want to switch to RR, however, my previous 2 HTC's had been S-OFF'd by me to switch them to the .401 WWE firmware, however this one is already on .401 so I don't want to get S-OFF since I don't really need it.
If I was to unlock the bootloader and flash RR, and then, want to go back to stock, how would I go about it?
As far as I know, there aren't any RUUs available for 2.41.401.41, so would flashing an older RUU work, and then taking an OTA to the newer firmware?
This is what download mode says:
*** LOCKED ***
htc_pmeuhl PVT S-ON
LK-1.0.0.0000
[email protected]
OpenDSP-v20.0.8996.00007_0809
OS-2.41.401.41
Aug 2 2017, 12:18:15 (857212)
Click to expand...
Click to collapse
You can't flash an older RUU while S-On.
First off, unlocking the bootloader will wipe your phone, so there is that.
To backup the stock ROM: After unlocking the bootloader and flashing TWRP, do a backup in recovery before flashing SuperSU. Then to take the OTAs, you will only need to restore that backup and then flash the stock recovery.
To get the stock recovery you could do a search for it.
Or you could download the OTA,
Transfer that to your PC,
Open it with 7zip,
Search for the recovery.zip in it,
Then flash that.
Chances are that an RUU.zip for x.xx.401.x will be posted here on XDA soon after it is released, so that is probably the best way to go.
Do a backup in TWRP,
Flash the RUU.zip,
Restore your backup. That way you'll have the new firmware.

xunholyx said:
You can't flash an older RUU while S-On.
First off, unlocking the bootloader will wipe your phone, so there is that.
To backup the stock ROM: After unlocking the bootloader and flashing TWRP, do a backup in recovery before flashing SuperSU. Then to take the OTAs, you will only need to restore that backup and then flash the stock recovery.
To get the stock recovery you could do a search for it.
Or you could download the OTA,
Transfer that to your PC,
Open it with 7zip,
Search for the recovery.zip in it,
Then flash that.
Chances are that an RUU.zip for x.xx.401.x will be posted here on XDA soon after it is released, so that is probably the best way to go.
Do a backup in TWRP,
Flash the RUU.zip,
Restore your backup. That way you'll have the new firmware.
Click to expand...
Click to collapse
So, I kinda crapped myself since I jumped the gun and flashed RR without making a TWRP backup and in the RUU collection thread, the latest one in the first post is older than the one I have, however a few pages down, someone was kind enough to post the RUU, OTA and TWRP backup for the exact 401 build that I was running.
Going back to stock is going to be a piece of cake now.
Cheers.

Request at&t 6.20.502.5 stock recovery.img

Hi i have s-on with unlocked bootloader iam trying to restore back to stock using this guide here https://forum.xda-developers.com/htc-one-m8/general/guide-restore-european-htc-one-m8-to-t3072235
But iam unable to find stock recovery.img for at&t in order to proceed, Can anyone help out?

To return to "full" stock, just relock the bootloader and flash the 6.20.502.5 RUU (will wipe all user data on the phone). I don't know why that guide is advising to flash the boot.img and recovery.img before flashing the RUU. It isn't necessary.

redpoint73 said:
To return to "full" stock, just relock the bootloader and flash the 6.20.502.5 RUU (will wipe all user data on the phone). I don't know why that guide is advising to flash the boot.img and recovery.img before flashing the RUU. It isn't necessary.
Click to expand...
Click to collapse
Will this work even though the device is s-on?

David_UK said:
Will this work even though the device is s-on?
Click to expand...
Click to collapse
Yes. RUU that is intended for your specific device version (AT&T) will work just fine with s-on. As long as it's equal or greater to version number on the phone (no "downgrading" by RUU is allowed with s-on).
S-off is only needed to run RUU for another version (need s-off to change CID, MID), or to run an older version RUU (downgrade).