my htcone is soff(by revone) and unlock(by htcdev)
now I have some questions:
1.if I update firmware to 2.24.401.1(hboot1.54),can I Reverting to S-ON and Lock the device use revone?
2.if I update firmware to 2.24.401.1(hboot1.54),can I downgrade Hboot by flashing a 4.1.2 RUU?
3.is there any change/deferent between 2.24.401.1 and 1.29 firmware when I use a 4.2.2 rom?
With the s-off you can do all what do you want
even with S-off after I updated hboot to 1.54 I couldn't flash an RUU with a 1.44 hboot. I got mainver error.
The way to get around this is to manually flash the downgraded Hboot then run the RUU.
You can also it seem flash the 2.17 firmware zip found here http://forum.xda-developers.com/showthread.php?t=2183023&page=500
and that will allow you to flash a downgraded RUU.
Related question, when browsing the different threads in the One Android Development forums I've come across the specific instructions to install the latest 2.24.709.1 ver firmware multiple times but never thought about doing the upgrade at the time. Now that I want to do it, I've been scouring the threads for those instructions and cannot find them, go figure. Can anyone point me out to one of those helpful links? Thanks
I just switched my phone to S-OFF, that's a requirement, right?
Related
Is there anyway to downgrade to older version of hboot?
Now, i am on hboot 1.25.My phone is thailand region.
I cant install stock ruu.i have 140 error all the time.
I think RUU is too old but i dont know where to find a newer version.
I download ruu from stickied topic in development forum.
http://forum.xda-developers.com/showthread.php?t=1317895
I think that is the only ruu for thailand region. Anyone can help?
Many thanks.
Btw, my phone is still s-on and i think i cant s-off because i still want a warranty(that is why i am trying to go back to stock rom). Please help.
Sorry for my English. I am not good at English(I am Thai).
KazumaSaruwatari said:
Is there anyway to downgrade to older version of hboot?
Now, i am on hboot 1.25.My phone is thailand region.
I cant install stock ruu.i have 140 error all the time.
I think RUU is too old but i dont know where to find a newer version.
I download ruu from stickied topic in development forum.
http://forum.xda-developers.com/showthread.php?t=1317895
I think that is the only ruu for thailand region. Anyone can help?
Many thanks.
Btw, my phone is still s-on and i think i cant s-off because i still want a warranty(that is why i am trying to go back to stock rom). Please help.
Sorry for my English. I am not good at English(I am Thai).
Click to expand...
Click to collapse
There are only 2 versions of Hboot -> 1.25 and 1.28, there are no official older versions, maybe beta or engineering ones that were not released publicly.
You can S-OFF with unprotected Hboot, but this is not needed for you, check your CID from your phone and flash the according RUU for it, if not, take this tool and flash the S-OFF for 1.25 and after that you can flash any RUU you want as it bypasses that (as far as i know), after the RUU flashing, the HBOOT will be overwrited as well, so you will end up with a stock, locked, S-ON device with the region-stock ROM of your choice, hope this helps
Lexmazter said:
There are only 2 versions of Hboot -> 1.25 and 1.28, there are no official older versions, maybe beta or engineering ones that were not released publicly.
You can S-OFF with unprotected Hboot, but this is not needed for you, check your CID from your phone and flash the according RUU for it, if not, take this tool and flash the S-OFF for 1.25 and after that you can flash any RUU you want as it bypasses that (as far as i know), after the RUU flashing, the HBOOT will be overwrited as well, so you will end up with a stock, locked, S-ON device with the region-stock ROM of your choice, hope this helps
Click to expand...
Click to collapse
I just did what you say.
I S-OFF my phone.
I relock bootloader.
Then, I install RUU. It seems to run smoothly but in the end error 140 came up and my phone is S-ON again with still old custom rom.
What should I do?
KazumaSaruwatari said:
I just did what you say.
I S-OFF my phone.
I relock bootloader.
Then, I install RUU. It seems to run smoothly but in the end error 140 came up and my phone is S-ON again with still old custom rom.
What should I do?
Click to expand...
Click to collapse
Well, as far as i know, you unlock the bootloader again, S-OFF, and after that you flash the RUU, i didn't install any RUU's until now, you should check the guide from stona15 that can be found here, There are more details about what to do and what you want.
Hope this helps
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
I was just going to flash ARHD 3.1 GE which is 4.3 based.
Currently i'm unlocked/s-off (thanks to revone) with hboot 1.44 and RUU 1.29.401.16.
Do I even have to update firmware or does 1.29 based fw work with 4.3 correctly?
Basically i'm confused with these firmware packages: http://forum.xda-developers.com/showthread.php?t=2182823
Is flashing a 2.24.401.12 based firmware going to update hboot too? Does this one break touch in recoveries too?
Why the custom firmwares based on 2.17.401.1 RUU and why aren't there 2.24.401.12 based custom firmwares?
Hopefully someone can answer at least some of my questions :angel:
Thanks
_saiko said:
I was just going to flash ARHD 3.1 GE which is 4.3 based.
Currently i'm unlocked/s-off (thanks to revone) with hboot 1.44 and RUU 1.29.401.16.
Do I even have to update firmware or does 1.29 based fw work with 4.3 correctly?
Basically i'm confused with these firmware packages: http://forum.xda-developers.com/showthread.php?t=2182823
Is flashing a 2.24.401.12 based firmware going to update hboot too? Does this one break touch in recoveries too?
Why the custom firmwares based on 2.17.401.1 RUU and why aren't there 2.24.401.12 based custom firmwares?
Hopefully someone can answer at least some of my questions :angel:
Thanks
Click to expand...
Click to collapse
Sounds like your a noob, so don't upgrade your hboot.
Sent from my One using xda app-developers app
gee thanks, you answered everything
I want to keep hboot 1.44, so it's fairly a simple question whether the 2.24 based firmware updates hboot as well or not.
That is my main question.
Tw1tchy said:
Sounds like your a noob, so don't upgrade your hboot.
Sent from my One using xda app-developers app
Click to expand...
Click to collapse
That was so rude, even if he is a noob, I think he has the right to find information and in this case, ask for it.
To be honest, I would like the answer to this too.
_saiko said:
gee thanks, you answered everything
I want to keep hboot 1.44, so it's fairly a simple question whether the 2.24 based firmware updates hboot as well or not.
That is my main question.
Click to expand...
Click to collapse
Yes the firmware will update the hboot. It may also update your radio and other hidden partitions.
I would recommend having s-off if your looking to upgrade your firmware. If you don't s-off you have to find the firmware corresponding with your CID. Most of it the time you have to run a RUU to upgrade so back up. Lastly S-OFF only works on hboot 1.44 so if your looking to s-off in the past (assuming you haven't already) don't upgrade because there is no downgrade method yet.
Sent from my One using xda app-developers app
Guys,
Go here: http://forum.xda-developers.com/showthread.php?t=2316726
Read the guide, and flash the 3.06/2.17 combo file if you can (S-off helps). Will give you the great updated touch drivers, and the GE 3.06 firmware. Sneakyghost did an excellent job with this guide, it will really help you out!
And if i'm S-OFF and on 1.44 HBOOT. Does it worth me upgrading ? What will be the benefits of new firmware / hbott ?
Im already s-off on 1.44 using revone, so what would happen with s-off status if I were to flash the 3.06/2.17 firmware from snakyghost?
Would it remain s-off?
Also something caught my eye, is the hboot from snakyghost a modified version and would reverting to s-on while having it brick the device?
r3v0Lut10n said:
And if i'm S-OFF and on 1.44 HBOOT. Does it worth me upgrading ? What will be the benefits of new firmware / hbott ?
Click to expand...
Click to collapse
Sirs please if you could give an answer Id be grateful
_saiko said:
Im already s-off on 1.44 using revone, so what would happen with s-off status if I were to flash the 3.06/2.17 firmware from snakyghost?
Would it remain s-off?
Also something caught my eye, is the hboot from snakyghost a modified version and would reverting to s-on while having it brick the device?
Click to expand...
Click to collapse
You will not lose s-off if you flash it just don't s-on with that firmware
Flashing firmware need not be a harrowing experience. As long as you read the guides carefully and follow the instructions to the letter, you will be fine. I have probably flashed at least 5-6 firmware packages on my One since getting it.
In general, once you're s-off, it's good to be on the most recent firmware because of various bug fixes like touch sensitivity. And, it would seem to be best to be on a matching firmware/rom base.
Once you start doing this stuff, however, forget about going back to s-on. You can do it if you're careful, but it's a bad idea. One mistake could leave you with a brick or crippled phone.
Again, to emphasize: Read very carefully, follow the instructions exactly, and you'll be safe.
Thank you Sirs
Usually i'd go and test things myself before asking, but in this case a wrong choice is not an option
All,
I have the Dev Edition with S-OFF and CID111111 running ARHD 13.3. With the latest update to the Dev Edition to 4.3, can I just flash the RUU for the latest of the Dev Edition? Will it work with TWRP custom recovery?
Thanks for any info.
Emh, the RUU isn't a zip, but an exe that you have to flash with the pc...
However, you can flash it
You can flash an RUU when S-OFF with Super CID, I've done it a number of times
The RUU is a complete update so it will overwrite the custom recovery anyway
Awesome guys....with that being said, I have a few more question. Since I'm S-Off and Super CID, you said I can flash any RUU, but it will wipe the custom recovery. That is fine, but when I want to flash a ROM in the future, I will have to reflash a new recovery correct? Will this mess with my HBOOT? I'm on 1.55 right now.
Also, I'm on the http://forum.xda-developers.com/showthread.php?p=39588860 looking at the collecdtion of RUU's...do I flash the ZIP, EXE or the Decrypted RUU's?
Again, thanks for your replies!
Download the RUU from HTCDev directly so you know you've got the right file, then flash it with the phone connected in fastboot. It will downgrade the HBOOT and put the phone back to 1.29.1540.16 and be just like it was out the box (except you'll still be S-OFF with Super CID). You can then get the OTA to .17 and then the OTA to Android 4.3...after that, you can flash a custom recovery and do what you want (but I'd take a nandorid first of course)
EDDYOS,
Thanks for all your info!! I will do exactly that!
One last question, I promise...since I am on S-OFF I should not be worried that flashing the RUU and downgrading to HBOOT 1.54 and not be able to achieve SOFF again? Cause isn't 1.54 having issues with SOFF? Or does that not matter to me since I have the Dev Editoin?
Again, thanks for all your advice.
You'll stay S-OFF so it's irrelevant...the only way you'll go S-ON is if YOU make it. RUUs/OTAs don't touch it
Example:
I'm currently on 2.24.401.8, HBOOT 1.54 and have S-OFF (as I did it when I could ages ago). I recently went back to 1.28.401.7 using the RUU and was still S-OFF. I then got the 4 OTAs to get back to 2.24.401.8 and I'm still S-OFF
EddyOS said:
You'll stay S-OFF so it's irrelevant...the only way you'll go S-ON is if YOU make it. RUUs/OTAs don't touch it
Example:
I'm currently on 2.24.401.8, HBOOT 1.54 and have S-OFF (as I did it when I could ages ago). I recently went back to 1.28.401.7 using the RUU and was still S-OFF. I then got the 4 OTAs to get back to 2.24.401.8 and I'm still S-OFF
Click to expand...
Click to collapse
EddyOS...
Thanks alot! Gotcha!
Anyone know where I can find a stock Lollipop Sense ruu that I can flash to restore an M7 back to stock?
Previously I have been using a euro JB based ruu from htc1guru, but it's a pain starting out on Jellybean, and upgrading from there but that website only goes up to a Kitkat radio for a euro base ruu, and even then I ran into issue flashing kitkat ruu.
I am super CID and s-off of course. I always flash 1.44 hboot prior to doing the above.
I need the zip by the way, not an exe as I am running linux on my laptop.
Thanks.
maritimesbob said:
Anyone know where I can find a stock Lollipop Sense ruu that I can flash to restore an M7 back to stock?
Previously I have been using a euro JB based ruu from htc1guru, but it's a pain starting out on Jellybean, and upgrading from there but that website only goes up to a Kitkat radio for a euro base ruu, and even then I ran into issue flashing kitkat ruu.
I am super CID and s-off of course. I always flash 1.44 hboot prior to doing the above.
I need the zip by the way, not an exe as I am running linux on my laptop.
Thanks.
Click to expand...
Click to collapse
HI bob, look at the sticky threads in the general section. Don't forget that you need at least hboot 1.57 and a 6.xx.xxx.x firmware (version-main) to flash a Lollipop RUU.