I recently switched my one over to GPE and now i want to revert to stock. I am running s-off and hboot 1.54. When I try to run the stock ruu exe for my phone i get an error 158, saying something to the effect that it is the wrong ruu. I know its the right one because ive used it before. Could my hboot version be the problem? If so would flashing 1.44 hboot fix this? Im using supercid 11111111.
As my instructions said, you have to put the 1.44 hboot back first.
DevinM7 said:
I recently switched my one over to GPE and now i want to revert to stock. I am running s-off and hboot 1.54. When I try to run the stock ruu exe for my phone i get an error 158, saying something to the effect that it is the wrong ruu. I know its the right one because ive used it before. Could my hboot version be the problem? If so would flashing 1.44 hboot fix this? Im using supercid 11111111.
Click to expand...
Click to collapse
I got into a bit of a mess myself trying to do the same thing but got it back in the end.
You need to change your mid back to your original one and, in my case, I had to flash a stock sense firmware http://forum.xda-developers.com/showthread.php?t=2182823 before I could run a sense RUU.
I figured it out. I had to flash 1.44 bootloader and when I did, the stock ruu went perfect. Thanks for the input though. Everyone on here has been a huge help.
Sent from my HTC One using xda app-developers app
Related
I'm running converted GE with 1.54 Google Hboot on my AT&T M7 (S-Off)
in order to go back to stock with the RUU I have to first load the 2.17 firmware Vomer provided in his thread.
If I don't do that I get error 155 when using the RUU.
I lock my bootloader before running it.
What am I missing. I thought S-off and SuperCID bypassed the checks and RUU's just worked.
Thanks for any advice.
Why are you locking your bootloader? You don't need to do that with s-off, I thought.
I wonder if there is some sort of check in the GE bootloader that isn't s-on/s-off dependent.
iElvis said:
Why are you locking your bootloader? You don't need to do that with s-off, I thought.
I wonder if there is some sort of check in the GE bootloader that isn't s-on/s-off dependent.
Click to expand...
Click to collapse
I found RUU failed with it unlocked.
I'm very confused at this point and just wonder if HTC changed things up on us.
gunnyman said:
I found RUU failed with it unlocked.
I'm very confused at this point and just wonder if HTC changed things up on us.
Click to expand...
Click to collapse
Well, the new 1.54 hboot thwarts the s-off exploit, as you know. It could be HTC introduced some elements with it that restore some type of security checks. It might explain the weird things going on in the s-off threads.
I know there are some substantial differences between the 2.17 hboot and 2.24 hboot even though the version number is the same.
iElvis said:
Well, the new 1.54 hboot thwarts the s-off exploit, as you know. It could be HTC introduced some elements with it that restore some type of security checks. It might explain the weird things going on in the s-off threads.
I know there are some substantial differences between the 2.17 hboot and 2.24 hboot even though the version number is the same.
Click to expand...
Click to collapse
SO maybe it isn't me.
Good to know.
Should I be able to just flash a 1.44 HBoot to get around this? Because either the one I have is corrupt, or it doesn't work thanks to the new 1.54 HBoot.
Lucky for me, the 2.17 firmwre.zip installs and things work after that.
gunnyman said:
SO maybe it isn't me.
Good to know.
Should I be able to just flash a 1.44 HBoot to get around this? Because either the one I have is corrupt, or it doesn't work thanks to the new 1.54 HBoot.
Lucky for me, the 2.17 firmwre.zip installs and things work after that.
Click to expand...
Click to collapse
You might try sticking with the 2.17 hboot and see if that helps.
iElvis said:
You might try sticking with the 2.17 hboot and see if that helps.
Click to expand...
Click to collapse
I have it on the Google Edition HBoot for OTA updates but heck that OTA might make reversal impossible.
*eek*
gunnyman said:
I have it on the Google Edition HBoot for OTA updates but heck that OTA might make reversal impossible.
*eek*
Click to expand...
Click to collapse
Must be the GE hboot or perhaps hboot 1.54 from 2.24 in general. I had a AT&T device with the new firmware and hboot 1.54 (from 2.17) I was able to run the RUU with s-off and bootloader still unlocked.
My fear is an ota for the ge would break the ability to downgrade hboot. The 2.17 works because it is the same 1.54
Okay I'm not sure about GE but when I had 2.24 and HBOOT 1.54.0000 I just ran the 1.28.401.7 RUU and it all went fine. I'm S-OFF of course.
Rex2369 said:
Okay I'm not sure about GE but when I had 2.24 and HBOOT 1.54.0000 I just ran the 1.28.401.7 RUU and it all went fine. I'm S-OFF of course.
Click to expand...
Click to collapse
weird.
I've calmed my own fears I was able to flash sneakyghost's provided 1.44Hboot. I'm safe.
gunnyman said:
weird.
I've calmed my own fears I was able to flash sneakyghost's provided 1.44Hboot. I'm safe.
Click to expand...
Click to collapse
Coming from full GE experience (1.54 hboot, GE recovery and ROM), I had to flash just the 1.44 hboot and relock my bootloader before the Dev RUU worked for me.
Sent from my HTC One using xda premium
So clearly HTC changed something about what S-off means and what you can and can't do with it.
Alright, so my friend has an AT&T One and it had 1.26.502.10 firmware (like mine), but he had some camera issues... He decided to do all the modding (root, s-off, etc...) and upgraded to 4.2.2 firmware 2.24. His camera issues continue, and he plans on returning to 4.1.2 with the available RUU that returns the phone to 1.26.502.12. He is s-off, supercid, unlocked bootloader, rooted, running twrp 2.6.0.1 and is on stock rooted 2.24.401.1 Rom. I thought of just using that RUU to return him to fully stock, but since it has all the mods I'm not really sure if I should take another approach or other steps. Please help me out here, I don't wanna brick his phone (even though he's taking it to be replaced). Thanks in advanced!
just download this and run it
https://support.htc.com/en-us/010-H..._Maintenance_Release_Instructions_|_5.30.2013
he couldnt run this with out the mods
Just run the RUU, as he's S-OFF there should be no issues
jerrycoffman45 said:
just download this and run it
https://support.htc.com/en-us/010-H..._Maintenance_Release_Instructions_|_5.30.2013
he couldnt run this with out the mods
Click to expand...
Click to collapse
Yes, that's the very file I have. Thanks! Will run it now! Thanks for the quick reply!
EddyOS said:
Just run the RUU, as he's S-OFF there should be no issues
Click to expand...
Click to collapse
Will do, thanks for ur quick reply!
There's the odd thread here and there saying if you're on the 1.54 HBOOT you need to downgrade to 1.44 before the RUU will work but try it first and see how you get on
EddyOS said:
There's the odd thread here and there saying if you're on the 1.54 HBOOT you need to downgrade to 1.44 before the RUU will work but try it first and see how you get on
Click to expand...
Click to collapse
Hmm, will I get a kind of error during the RUU process that might possibly brick the device or will it warn me before the RUU process starts? Can I and should I just flash the 1.44 RUU from fastboot before starting the RUU? The phone's on 2.24 right now with the modded 1.54 hboot (I know he first has to flash the original, but can/should he flash the 1.44 instead?).
EDIT: As far as I've read till now, the ones having errors were converted to Google Edition with GE hboot and all... I did read about 2 people (one with 2.17 and the other with 2.24 like my friend's phone) both on 1.54 hboot and it worked for both of em. I'm just gonna go ahead and flash the RUU on my friend's phone and hope for the best
So I had an issue with a HTC One, but I got a replacement! I turned S-OFF, flashed the shipped ROM, locked the bootloader and turned S-ON.
Worked perfectly and looks like new!
Anyhow, during this, I found out that revone doesn't work with newer HBOOT versions.
I have a new HTC One and it has the compatible version of HBOOT so I am in luck.
I want to flash custom ROM's such as ARHD but I don't want to update the hboot.
Does a newer version of HBOOT come with ARHD, or is that something only OTA updates include? Does ARHD stick with older HBOOT?
If it does update hboot,
If I turn S-OFF right away, will I be protected in-case a new HBOOT comes through? Will I be able to flash an older HBOOT version in case I need to turn S-ON?
Is it safe to turn S-OFF right now, and just leave it off, just in the case if my hboot gets updated or something - I can always revert to an older version.
I would also like to say thank you for all of your posts! I am an old time iPhone user for 5 years and I'm glad I switched to Android. There is just so much more you can do.
Your posts really help, contributors! It helped me return my device to new status, without 'relocked' and 'tampered' flags in the bootloader!
So thumbs up to XDA! :good:
rowebil said:
So I had an issue with a HTC One, but I got a replacement! I turned S-OFF, flashed the shipped ROM, locked the bootloader and turned S-ON.
Worked perfectly and looks like new!
Anyhow, during this, I found out that revone doesn't work with newer HBOOT versions.
I have a new HTC One and it has the compatible version of HBOOT so I am in luck.
I want to flash custom ROM's such as ARHD but I don't want to update the hboot.
Does a newer version of HBOOT come with ARHD, or is that something only OTA updates include?
If I turn S-OFF, will I be protected in-case a new HBOOT comes through? Will I be able to flash an older HBOOT version?
I would also like to say thank you for all of your posts! I am an old time iPhone user for 5 years and I'm glad I switched to Android. There is just so much more you can do.
Your posts really help, contributors! It helped me return my device to new status, without 'relocked' and 'tampered' flags in the bootloader!
So thumbs up to XDA! :good:
Click to expand...
Click to collapse
I have never update the hboot when using ARHD, I just gave it a flash.
As to updating via ota, the only thing close to that for me is when I did a gpe conversion to hboot 1.54 but I could go back.
Sent from my One using Tapatalk 4
squabbi said:
I have never update the hboot when using ARHD, I just gave it a flash.
As to updating via ota, the only thing close to that for me is when I did a gpe conversion to hboot 1.54 but I could go back.
Sent from my One using Tapatalk 4
Click to expand...
Click to collapse
It is just in the case that I need to do this replacement all over again. I don't want to update to another HBOOT accidentally through a ROM, and then find out I can't get S-OFF/S-ON and I'm stuck lol.
I can't get my words out too clear tonight! I'm not really sure as of why.
If I have S-OFF, and my HBOOT updates somehow, can I go back and flash another HBOOT?
Then another thought comes, I don't want to turn S-OFF because the thread says may not work with all ROM's, which is why I asked if ARHD will update my HBOOT.
Also, thanks for your AIO toolkit! I was looking for it earlier today. I used it when I bought my phone and worked great! Thanks for that!
rowebil said:
It is just in the case that I need to do this replacement all over again. I don't want to update to another HBOOT accidentally through a ROM, and then find out I can't get S-OFF/S-ON and I'm stuck lol.
I can't get my words out too clear tonight! I'm not really sure as of why.
If I have S-OFF, and my HBOOT updates somehow, can I go back and flash another HBOOT?
Then another thought comes, I don't want to turn S-OFF because the thread says may not work with all ROM's, which is why I asked if ARHD will update my HBOOT.
Also, thanks for your AIO toolkit! I was looking for it earlier today. I used it when I bought my phone and worked great! Thanks for that!
Click to expand...
Click to collapse
If you want to go back to S-ON you should use an ruu to go back to stock then use the S-ON command.
I'm sure you can downgrade back to hboot 1.44 but some say you can't, but it worked for the Google edition conversion and I returned to 1.44.
I'm glad the toolkit worked for you!
Sent from my One using Tapatalk 4
squabbi said:
If you want to go back to S-ON you should use an ruu to go back to stock then use the S-ON command.
I'm sure you can downgrade back to hboot 1.44 but some say you can't, but it worked for the Google edition conversion and I returned to 1.44.
I'm glad the toolkit worked for you!
Sent from my One using Tapatalk 4
Click to expand...
Click to collapse
Ah okay, I didn't think about that!
So an RUU will also downgrade hboot?
I don't want to be stuck with a junk hboot that is locked down.
It is going to work for me again, when I unlock this new phone!
It's safe to go S-Off now and leave it off. hboot updates won't cause S-On
ARHD won't update your hboot.
If your hboot is updated, you must be already S-Off to downgrade.
You are on 1.44 right now. If you go s-off now, you will remain s-off even after accepting OTAs, and you can downgrade your hboot whenever you feel like. On the other hand, if you are s-on right now, and accept an OTA, you'll be upgraded to the locked down 1.54, on which you can't get s-off, nor can you downgrade.. What I suggest is going s-off right now, and doing whatever flashing you want to do.. Beware, with s-off, you can permanently brick(hard brick) your phone. If you ever want to go back to s-on, flash an RUU of ONLY 4.1.2. All roms work with s-off, so no need to worry
Sent from my HTC One using Tapatalk 4
rowebil said:
Ah okay, I didn't think about that!
So an RUU will also downgrade hboot?
I don't want to be stuck with a junk hboot that is locked down.
It is going to work for me again, when I unlock this new phone!
Click to expand...
Click to collapse
An ruu should, but if you don't want to factory restore, you can just flash the ruu.
Sent from my One using Tapatalk 4
Hy, it´s possible downgrade hboot from 1.54 on 1.44 or older with flashing stock RUU - RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed.exe. My HTC One is on 1.54 hboot unlocked rooted but S-on and it´s my problem because I need flashing some things that needs S-off.
Not possible if s-on with hboot 1.54. To downgrade you need to be s-off! If you try running the RUU in your phones present state, the RUU will fail to install, due to the hboot being a higher version presently to the one you are trying to install.
Hope that makes sense?
Sent from my HTC One using XDA Premium 4 mobile app
Short answer: nope. Basically what spikeydoo2006 said. Once you're on hboot v1.54, you can never go back.
Hello was hoping for some advice. need to return my phone to stock as selling it to make money for the HTC one max. Currently rooted with s-off using rumrunner it all looks pretty simple. Just want to make sure I get correct ruu.zip or ruu .exe as I want to get my radio kernel and firmware etc back to current stock. I was on 2.24.401.8 when started out with 1.54 hboot. I'm on cid htc_001. Now I'm running ARHD. Custom hboot 1.56 to remove red warning text when I have hopefully found a correct ruu can I flash this over custom hboot to get back to stock or will this brick the phone? Or will I need to flash hboot 1.44 first and which 1? also on 4.06.1540.2 I think it is. Help would be very appreciated. Thanks
Sent from my C6833 using Tapatalk
nathlynn22 said:
Hello was hoping for some advice. need to return my phone to stock as selling it to make money for the HTC one max. Currently rooted with s-off using rumrunner it all looks pretty simple. Just want to make sure I get correct ruu.zip or ruu .exe as I want to get my radio kernel and firmware etc back to current stock. I was on 2.24.401.8 when started out with 1.54 hboot. I'm on cid htc_001. Now I'm running ARHD. Custom hboot 1.56 to remove red warning text when I have hopefully found a correct ruu can I flash this over custom hboot to get back to stock or will this brick the phone? Or will I need to flash hboot 1.44 first and which 1? also on 4.06.1540.2 I think it is. Help would be very appreciated. Thanks
Sent from my C6833 using Tapatalk
Click to expand...
Click to collapse
You will need to downgrade hboot to 1.44 before running the 1.28.401.7 ruu.exe
check your MID also match the ruu (PN0710000)
make sure you are not using windows 8.1
For more info follow instructions from nkk71's guide linked below.
alray said:
You will need to downgrade hboot to 1.44 before running the 1.28.401.7 ruu.exe
check your MID also match the ruu (PN0710000)
make sure you are not using windows 8.1
For more info follow instructions from nkk71's guide linked below.
Click to expand...
Click to collapse
FYI, in case you missed it , guide update 8-Feb, separate hboot downgrade no longer needed (mostly), as preferred method is ruu.zip, no longer ruu.exe
(more reliable, more OS support, more information, etc.)
nkk71 said:
FYI, in case you missed it , guide update 8-Feb, separate hboot downgrade no longer needed (mostly), as preferred method is ruu.zip, no longer ruu.exe
(more reliable, more OS support, more information, etc.)
Click to expand...
Click to collapse
It's cool I used ruu.exe and downgraded my hboot. Now I've got stock phone just can't get s -on says waiting for device
Sent from my C6833 using Tapatalk
Nevermind. Thanks guys looking good
Sent from my C6833 using Tapatalk
nkk71 said:
FYI, in case you missed it , guide update 8-Feb, separate hboot downgrade no longer needed (mostly), as preferred method is ruu.zip, no longer ruu.exe
(more reliable, more OS support, more information, etc.)
Click to expand...
Click to collapse
good, i'll go read your updated guide! thanks for the info.