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?
Related
I have a Wildfire S CDMA from Virgin, USA which I unlocked, s-off and rooted, and installed cyanogenmod recovery.
Fastboot shows MARVELC PVT SHIP S-OFF RL
HBOOT-1.06.0000
I am looking to unlock from 'RL', and reroot, but after no small amount of wading through forums, I'm here asking you all for assistance. I'm new to messing with my phone, but feel like I'm about ready for an 'Ah HA!' breakthrough.
Initially, I had deleted all system/data through Recovery, and finally found an RUU that would run and reinstalled the stock ROM.
Rerooting has been a challenge. When I follow the instructions at htcdev, I fail to execute run get_identifier_token, with "command error"
Fastboot running on my desktop does recognize the device, but have not been able to flash anything.
When I boot into recovery, the phone loads the HTC spash, but lands on a screen with a red triangle and exclamation point.
PG76IMG.zip isn't recognized by FASTBOOT on the phone, regardless of the modelid or cid in the android-info.txt
I would appreciate any suggestions to get back to root.... hard to imagine that some people use their phone with out it.
Lhooqtoo said:
I have a Wildfire S CDMA from Virgin, USA which I unlocked, s-off and rooted, and installed cyanogenmod recovery.
Fastboot shows MARVELC PVT SHIP S-OFF RL
HBOOT-1.06.0000
I am looking to unlock from 'RL', and reroot, but after no small amount of wading through forums, I'm here asking you all for assistance. I'm new to messing with my phone, but feel like I'm about ready for an 'Ah HA!' breakthrough.
Initially, I had deleted all system/data through Recovery, and finally found an RUU that would run and reinstalled the stock ROM.
Rerooting has been a challenge. When I follow the instructions at htcdev, I fail to execute run get_identifier_token, with "command error"
Fastboot running on my desktop does recognize the device, but have not been able to flash anything.
When I boot into recovery, the phone loads the HTC spash, but lands on a screen with a red triangle and exclamation point.
PG76IMG.zip isn't recognized by FASTBOOT on the phone, regardless of the modelid or cid in the android-info.txt
I would appreciate any suggestions to get back to root.... hard to imagine that some people use their phone with out it.
Click to expand...
Click to collapse
It's because your bootloader doesn't support being unlocked.............Any bootloader that has *LOCKED*(or *RELOCKED*) written can be unlocked via HTCdev
Look over for the RUUs provided before the steps and see which one's for the CDMA WFS, run it and you will be able to unlock the phone
csoulr666 said:
It's because your bootloader doesn't support being unlocked.............Any bootloader that has *LOCKED*(or *RELOCKED*) written can be unlocked via HTCdev
Look over for the RUUs provided before the steps and see which one's for the CDMA WFS, run it and you will be able to unlock the phone
Click to expand...
Click to collapse
Downloaded the WFS SprintVM RUU from htcdev. It fails with error130 model ID error.
Identical situation as shown here:
http://forum.xda-developers.com/showthread.php?t=2027649
Walkthrough for downgrade exists here: but links are missing..
http://forum.xda-developers.com/showthread.php?t=1942991
Lhooqtoo said:
Downloaded the WFS SprintVM RUU from htcdev. It fails with error130 model ID error.
Identical situation as shown here:
http://forum.xda-developers.com/showthread.php?t=2027649
Walkthrough for downgrade exists here: but links are missing..
http://forum.xda-developers.com/showthread.php?t=1942991
Click to expand...
Click to collapse
If it doesn't work look for updates on your phone, maybe your carrier released an OTA with an unlockable bootloader
csoulr666 said:
If it doesn't work look for updates on your phone, maybe your carrier released an OTA with an unlockable bootloader
Click to expand...
Click to collapse
There is an OTA system update (through Settings/About phone/Software updates), however, the update fails with a red question mark over device. Doesn't custom recovery (CWM) and a changed CID (111..1) prohibit OTA update?
Lhooqtoo said:
There is an OTA system update (through Settings/About phone/Software updates), however, the update fails with a red question mark over device. Doesn't custom recovery (CWM) and a changed CID (111..1) prohibit OTA update?
Click to expand...
Click to collapse
The custom recovery does, but the CID doesn't....... Try doing it with a custom recovery installed
csoulr666 said:
The custom recovery does, but the CID doesn't....... Try doing it with a custom recovery installed
Click to expand...
Click to collapse
I currently have CWM installed (though currently if I run recovery from the bootloader, it fails).
If the custom recovery prohibits the OTA update, shouldn't I remove CWM to allow the OTA?
Try doing it with a stock recovery installed
csoulr666 said:
Try doing it with a stock recovery installed
Click to expand...
Click to collapse
followed this:
http://forum.xda-developers.com/showthread.php?t=2025121
sending 'recovery' <3146 KB>...
OKAY [ 1.522s]
writing 'recovery'...
FAILED <remote: not allowed>
finished. total time: 1.526s
No joy?
Is there any chance that flashing the recovery would succeed if the recovery were different? (instead of a permissions issue).
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!
Phone specs:
Code:
RELOCKED
M8_UL PVT SHIP S-OFF
CID-11111111
HBOOT-3.16.0.0000
RADIO-1.23.213311491.05G
OpenDSP-v48.2.2-00564-M8974_FO.1211
OS-4.20.531.4 (1.54.401.5)
eMMC-boot 2048MB
So I'm trying to update my One M8, and I think I messed up pretty bad. I tried running the RUU updater for my T-Mobile variant (found on HTC's ROM Download page), but got the infamous "error 155." However, my bootloader is re-locked. Therefore, according to all the forum posts I could find, I shouldn't be getting that error. I've run a few commands since then, including fastboot oem writecid 11111111 and fastboot erase cache. Somehow, I've managed to get to the point where my phone won't even boot into recovery, it just gets stuck at the "Entering recovery..." screen. However, while stuck on this screen, the phone does respond to ADB commands. I can get root shell access, but I'm not sure what to do with it.
I've tried flashing TWRP 3.0.0.0 to no avail. I've tried running fastboot boot <twrp filename here>, also to no avail. I'm pretty much stuck with a phone that only boots into fastboot, and a weird purgatory-recovery where I can achieve shell access. The RUU file fails to update no matter what I do.
Is there a way I can fix this, or have I completely bricked my phone?
Thank you for your time.
RalphORama said:
Phone specs:
Code:
RELOCKED
M8_UL PVT SHIP S-OFF
CID-11111111
HBOOT-3.16.0.0000
RADIO-1.23.213311491.05G
OpenDSP-v48.2.2-00564-M8974_FO.1211
OS-4.20.531.4 (1.54.401.5)
eMMC-boot 2048MB
So I'm trying to update my One M8, and I think I messed up pretty bad. I tried running the RUU updater for my T-Mobile variant (found on HTC's ROM Download page), but got the infamous "error 155." However, my bootloader is re-locked. Therefore, according to all the forum posts I could find, I shouldn't be getting that error. I've run a few commands since then, including fastboot oem writecid 11111111 and fastboot erase cache. Somehow, I've managed to get to the point where my phone won't even boot into recovery, it just gets stuck at the "Entering recovery..." screen. However, while stuck on this screen, the phone does respond to ADB commands. I can get root shell access, but I'm not sure what to do with it.
I've tried flashing TWRP 3.0.0.0 to no avail. I've tried running fastboot boot <twrp filename here>, also to no avail. I'm pretty much stuck with a phone that only boots into fastboot, and a weird purgatory-recovery where I can achieve shell access. The RUU file fails to update no matter what I do.
Is there a way I can fix this, or have I completely bricked my phone?
Thank you for your time.
Click to expand...
Click to collapse
Have you flashed both stock recovery for the RUU in particular youre flashing and re-locked BL, and are you installing a version number that is equal to or higher than the one you already have installed.
Completely stock phone should flash RUU, as long as its not a version down from whats installed, ie, trying to flash LP when MM is already flashed on phone, UNLESS of course youre s-off and supercid, because with supercid you should be able to flash any RUU .
But i had similar issues, im s-on, so i had to revert to stock LP completely, then flashed HTC__001 Stock MM for my phone, failing all that there is always the option of copying a nandroid on here to ur sd card, boot into twrp and restore the Nandroid just to get it up and running again.
I would run the RUU, let it sit at first screen, goto start button and type in %temp%, find the folder inside temp that ruu just created, (sort by date), pull the rom.zip from that to ur desktop, Unzip it and get the files recovery and boot.img, flash them both to ur phone via fastboot, if it still works, then restart ur phone and it should load up, you could then try to install the RUU from windows again, failing that after flashing recovery and boot, goto ur stock recovery and wipe and reset then reboot phone.
It doesnt sound like hard brick, just soft brick, it should be ok.
If you try to flash a Android MM ruu i suggest to flash a lower ruu first. Usually the big jump from the 3.16 boot loader to a 3.19 boot loader is too much.
Or flash the standalone firmware first and then the full ruu.
The high version of TWRP doesn't work because your bootloader is too low (3.16) if you want a working TWRP then use a 2.7 version.
If you can get to the bootloader then it's just a softbrick. A hardbrick is only when the bootloader is not accessible anymore or when the phone doesn't boot up in any way anymore.
Cheers
Mr Hofs said:
Or flash the standalone firmware first and then the full ruu.
Click to expand...
Click to collapse
This is most likely the solution. In particular, if OP is trying to install MM RUU, there is a new peculiarity (requirement?) with all MM RUUs, where you need to have MM firmware in order to run the RUU, or else you will have Error 155.
Find the firmware.zip that matches the version number of the RUU, flash it; then try the RUU again.
---------- Post added at 09:42 AM ---------- Previous post was at 09:35 AM ----------
gazza35 said:
Have you flashed both stock recovery for the RUU
Click to expand...
Click to collapse
You don't need stock recovery to RUU. Folks keep saying this, and its not true.
You need stock recovery to OTA, but you do not need it for RUU. OTA and RUU are two very different things.
gazza35 said:
because with supercid you should be able to flash any RUU .
Click to expand...
Click to collapse
This is also not true. You need to match MID and CID (or SuperCID) in order to flash an RUU. SuperCID bypasses the CID check, but you still need to pass the MID check.
---------- Post added at 09:44 AM ---------- Previous post was at 09:42 AM ----------
gazza35 said:
But i had similar issues, im s-on, so i had to revert to stock LP
Click to expand...
Click to collapse
Same peculiarity with the MM RUU I mentioned above (need to flash the MM firmware if coming from LP) also applies if you try to downgrade back to LP. Meaning, you need to flash the LP firmware, then LP RUU.
Mr Hofs said:
If you try to flash a Android MM ruu i suggest to flash a lower ruu first. Usually the big jump from the 3.16 boot loader to a 3.19 boot loader is too much.
Or flash the standalone firmware first and then the full ruu.
The high version of TWRP doesn't work because your bootloader is too low (3.16) if you want a working TWRP then use a 2.7 version.
If you can get to the bootloader then it's just a softbrick. A hardbrick is only when the bootloader is not accessible anymore or when the phone doesn't boot up in any way anymore.
Cheers
Click to expand...
Click to collapse
Thank you (and everyone else) for your replies! Out of curiosity, where can I find a lower RUU? I can only find the most recent one from HTC's website.
EDIT: I flashed TWRP 2.7 and I was able to boot into recovery! I love progress.
RalphORama said:
Out of curiosity, where can I find a lower RUU? I can only find the most recent one from HTC's website.
Click to expand...
Click to collapse
You can find the links for older T-Mob RUUs here: http://forum.xda-developers.com/showthread.php?t=2714456
Sorry..if it's an already solved issue.
I'm using an unlocked HTC M8 which I rooted, unlocked bootloader and installed the latest Lineage OS (Android 7.1.2).
I got a good offer for the device and would like to sell it. So I want to revert it back to stock.
The device information are :
version-main: 6.12.111.4
version-misc: PVT SHIP S-ON
modelid: 0P6B10000
cidnum: T-MOB101
I could only find a Lollipop firmware for my CID which I copied into my SD card as OP6BIMG.zip
But the bootloader gives error as "Large Image Update Failed..Press power to reboot"
This goes on until I remove my SD card.
The RUU I used is "0P6BIMG_M8_UL_L50_SENSE60_MR_TMO_DE_4.19.111.3_Radio_1.25.214500021.06G_20.68.4196t.01_F_release_449335_combined_signed.zip"
Is this because I'm trying to downgrade Android version?
Also should I try after re-locking the bootloader (which is something I'm a bit worried to do because I think I will end up in an even worse condition if it doesn't work...because in my experience with an M9 it never unlocks again after relocking in a custom rom.)
Please help.
If you can't find 6.12.111.4, restore fully stock backup
https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
You don't need to relock bootloader to restore nandroid
Edit : here is RUU.zip - https://www.androidfilehost.com/?fid=24399965296001026
You need to relock bootloader to install RUU
ckpv5 said:
If you can't find 6.12.111.4, restore fully stock backup
https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
You don't need to relock bootloader to restore nandroid
Edit : here is RUU.zip - https://www.androidfilehost.com/?fid=24399965296001026
You need to relock bootloader to install RUU
Click to expand...
Click to collapse
OK..will try the RUU zip after relocking bootloader.
Hope it works.
Will update about the same after.
Downloading...
So I relocked my bootloader.. downloaded the RUU zip.. renamed it to 0P6BIMG and put in my SD card.
Booted into bootloader and voila.. it flashed right away and now am back to pure stock.
Thank you..ckpv5 for all the help.
You saved my day.
[email protected] said:
I'm using an unlocked HTC M8 which I rooted, unlocked bootloader and installed the latest Lineage OS (Android 7.1.2).
I got a good offer for the device and would like to sell it. So I want to revert it back to stock.
Click to expand...
Click to collapse
Just good practice: Always make a TWRP backup before flashing a custom ROM, root, etc.
I personally never start messing with these phones, without beforehand having some strategy to get back to stock.
[email protected] said:
The device information are :
version-main: 6.12.111.4
I could only find a Lollipop firmware for my CID which I copied into my SD card as OP6BIMG.zip
But the bootloader gives error as "Large Image Update Failed..Press power to reboot"
This goes on until I remove my SD card.
The RUU I used is "0P6BIMG_M8_UL_L50_SENSE60_MR_TMO_DE_4.19.111.3_Radio_1.25.214500021.06G_20.68.4196t.01_F_release_449335_combined_signed.zip"
Is this because I'm trying to downgrade Android version?
Click to expand...
Click to collapse
Correct. You cannot "downgrade" by RUU with s-on.
[email protected] said:
Also should I try after re-locking the bootloader (which is something I'm a bit worried to do because I think I will end up in an even worse condition if it doesn't work...because in my experience with an M9 it never unlocks again after relocking in a custom rom.)
Click to expand...
Click to collapse
Typically, no problem unlocking the bootloader on the M8 again, after relocking it.
Locked or Relocked bootloader is required to RUU with s-on.
redpoint73 said:
Just good practice: Always make a TWRP backup before flashing a custom ROM, root, etc.
I personally never start messing with these phones, without beforehand having some strategy to get back to stock.
Correct. You cannot "downgrade" by RUU with s-on.
Typically, no problem unlocking the bootloader on the M8 again, after relocking it.
Locked or Relocked bootloader is required to RUU with s-on.
Click to expand...
Click to collapse
Thanks for all the information.
Will definitely keep these in mind the next time I try to mess with software;
Hello a quick question, instead of reverting to stock by RUU, can I flash a Sense-based rom via TWRP? I am presently on Lineage 15.1 with latest TWRP and S on. Thank you.
Babakkardan said:
Hello a quick question, instead of reverting to stock by RUU, can I flash a Sense-based rom via TWRP? I am presently on Lineage 15.1 with latest TWRP and S on. Thank you.
Click to expand...
Click to collapse
If you are looking to go back to stock..you can use Stock RUU zip of your model to flash via recovery.
[email protected] said:
If you are looking to go back to stock..you can use Stock RUU zip of your model to flash via recovery.
Click to expand...
Click to collapse
You can't flash RUU.zip with recovery. It will fail if you try to do so. You need to flash RUU.zip with htc_fastboot in RUUmode. Otherwise use the SD card method (auto install in bootloader). Another alternative is to flash the RUU executable (.exe).
redpoint73 said:
You can't flash RUU.zip with recovery. It will fail if you try to do so. You need to flash RUU.zip with htc_fastboot in RUUmode. Otherwise use the SD card method (auto install in bootloader).
Click to expand...
Click to collapse
Oops my bad...I actually meant the sd card method renaming the rom to OP6BIMG.
:angel:
(Thanks for correcting)
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).