Related
htc one with 2.24.401.2 built and 1.54 hboot
tried flash recovery pulled out from cmw back up
tried 2.24.401.1 ota ruu wwe dint work
getting signature fail always please i wan just unroot
htc one m7 said:
htc one with 2.24.401.2 built and 1.54 hboot
tried flash recovery pulled out from cmw back up
tried 2.24.401.1 ota ruu wwe dint work
getting signature fail always please i wan just unroot
Click to expand...
Click to collapse
I am in exactly the same boat
here is my setup
HBOOT: 1.54.0000
OS: 2.24.401.1
Looking for the correct RUU to flash. any help is appreciated
winwiz said:
I am in exactly the same boat
here is my setup
HBOOT: 1.54.0000
OS: 2.24.401.1
Looking for the correct RUU to flash. any help is appreciated
Click to expand...
Click to collapse
this will be my last and first HTC to root
i had gs3 i flash a home rom any second i wanted im searching for that RUU from 1 month ago i dint find it
htc customer services and htc dev both sucks
htc one m7 said:
this will be my last and first HTC to root
i had gs3 i flash a home rom any second i wanted im searching for that RUU from 1 month ago i dint find it
htc customer services and htc dev both sucks
Click to expand...
Click to collapse
I realised that I took a nandroid backup of the original firmware, so I have been successful in returning to stock.
When I boot to the bootloader, I see TAMPERED AND UNLOCKED. I guess this is to to a custom recovery and also unlocked bootloader. Any ideas how I can get this back to normal? Am I then back to stock fully?
winwiz said:
I realised that I took a nandroid backup of the original firmware, so I have been successful in returning to stock.
When I boot to the bootloader, I see TAMPERED AND UNLOCKED. I guess this is to to a custom recovery and also unlocked bootloader. Any ideas how I can get this back to normal? Am I then back to stock fully?
Click to expand...
Click to collapse
me i have my stuck rom running also nandroid pulled by cmd
but no chance for me
There is NO way for you to remove the tampered flag or change relocked to locked if you are on Hboot 1.54, no S-Off available which is what you need. If you are on a lower Hboot then you can S-Off and remove the flag and return to 100% stock.
There are also NO 2.24 RUU's so don't bother trying to find one.
It amuses me that somebody would never buy another HTC phone because they don't know what to do. Other phones can be unlocked , rooted, flashed, by pure noobs who don't know what they're doing. The One requires you to learn a little and do some reading to know what to do, when you've done that you'll find it isn't hard at all.
Why are you so desperate to go back to stock? If you just want the stock experience, flash a stock rom.
If you're trying to hide the fact that you rooted and unlocked in order to return/sell it, you can't really complain that you're having problems trying to deceive people. Sorry.
Had either of you done any research and reading prior to rooting, your problems would have been apparent.
AllAboutTheCore said:
There is NO way for you to remove the tampered flag or change relocked to locked if you are on Hboot 1.54, no S-Off available which is what you need. If you are on a lower Hboot then you can S-Off and remove the flag and return to 100% stock.
There are also NO 2.24 RUU's so don't bother trying to find one.
It amuses me that somebody would never buy another HTC phone because they don't know what to do. Other phones can be unlocked , rooted, flashed, by pure noobs who don't know what they're doing. The One requires you to learn a little and do some reading to know what to do, when you've done that you'll find it isn't hard at all.
Click to expand...
Click to collapse
thanks next time when i need a root i will get s-off before that .now my chance is getting s-off wich is not available now
if u dint tell me dont search i would search for ever XD
iElvis said:
Why are you so desperate to go back to stock? If you just want the stock experience, flash a stock rom.
If you're trying to hide the fact that you rooted and unlocked in order to return/sell it, you can't really complain that you're having problems trying to deceive people. Sorry.
Had either of you done any research and reading prior to rooting, your problems would have been apparent.
Click to expand...
Click to collapse
i just want to get updates from htc
AllAboutTheCore said:
There is NO way for you to remove the tampered flag or change relocked to locked if you are on Hboot 1.54, no S-Off available which is what you need. If you are on a lower Hboot then you can S-Off and remove the flag and return to 100% stock.
There are also NO 2.24 RUU's so don't bother trying to find one.
It amuses me that somebody would never buy another HTC phone because they don't know what to do. Other phones can be unlocked , rooted, flashed, by pure noobs who don't know what they're doing. The One requires you to learn a little and do some reading to know what to do, when you've done that you'll find it isn't hard at all.
Click to expand...
Click to collapse
Noobs are what this thread is for. Why are you flaming and complaining in a Q&A thread anyway? If you're not going to help, get out of the way and flame on elsewhere.
htc one m7 said:
i just want to get updates from htc
Click to expand...
Click to collapse
Then you should've left the phone stock
htc one m7 said:
htc one with 2.24.401.2 built and 1.54 hboot
tried flash recovery pulled out from cmw back up
tried 2.24.401.1 ota ruu wwe dint work
getting signature fail always please i wan just unroot
Click to expand...
Click to collapse
Try a factory reset, but don't use the backup to restore settings. It might be a hassle, but it should uninstall SU, and if you don't restore those settings, it should be unrooted. Just go to play store and reinstall the apps you had before. They should be saved under your account. I hope this helps.
Edit: Another possibility would be to install an all in one toolkit, and have that unroot the phone for you. I'm not 100% sure it would work with 1.54, though. There are two good ones here and here.
Edit: Yet another possibility would be to flash hboot 1.44 and then run the RUU again.
Edit: Finally, have you tried unrooting through the SU app itself?
kibmikey1 said:
Try a factory reset, but don't use the backup to restore settings. It might be a hassle, but it should uninstall SU, and if you don't restore those settings, it should be unrooted. Just go to play store and reinstall the apps you had before. They should be saved under your account. I hope this helps.
Edit: Another possibility would be to install an all in one toolkit, and have that unroot the phone for you. If you used the revone method to root, it should take care of it. I'm not 100% sure it would work with 1.54, though. There are two good ones here and here.
Edit: Yet another possibility would be to flash hboot 1.44 and then run the RUU again.
Click to expand...
Click to collapse
I've personally managed to get it back to stock, and even got an OTA update. The only issue I have is that in the bootloader it's saying TAMPERED and RELOCKED
I guess there is not much I can do about this,
Any above all, thank you for your help. You have been helpful unlike the others with a snobbish attitude
winwiz said:
I've personally managed to get it back to stock, and even got an OTA update. The only issue I have is that in the bootloader it's saying TAMPERED and RELOCKED
I guess there is not much I can do about this,
Any above all, thank you for your help. You have been helpful unlike the others with a snobbish attitude
Click to expand...
Click to collapse
You could run the all in one toolkit and remove the tampered and relocked flags.
---------- Post added at 02:06 AM ---------- Previous post was at 01:17 AM ----------
iElvis said:
Why are you so desperate to go back to stock? If you just want the stock experience, flash a stock rom.
If you're trying to hide the fact that you rooted and unlocked in order to return/sell it, you can't really complain that you're having problems trying to deceive people. Sorry.
Had either of you done any research and reading prior to rooting, your problems would have been apparent.
Click to expand...
Click to collapse
This thread is open for questions like these. Flame on elsewhere.
kibmikey1 said:
Try a factory reset, but don't use the backup to restore settings. It might be a hassle, but it should uninstall SU, and if you don't restore those settings, it should be unrooted. Just go to play store and reinstall the apps you had before. They should be saved under your account. I hope this helps.
Edit: Another possibility would be to install an all in one toolkit, and have that unroot the phone for you. I'm not 100% sure it would work with 1.54, though. There are two good ones here and here.
Edit: Yet another possibility would be to flash hboot 1.44 and then run the RUU again.
Edit: Finally, have you tried unrooting through the SU app itself?
Click to expand...
Click to collapse
unrooting thrrough su app dint work and that tool kit s wont work for 1.54 hboot im so unlucky
htc one m7 said:
unrooting thrrough su app dint work and that tool kit s wont work for 1.54 hboot im so unlucky
Click to expand...
Click to collapse
If your phone was 2.24 out of the box and you never went s-off, you don't need a ruu because your firmware would not have changed. So you just need to restore stock recovery and stock system files, then relock. Flash a stock rom, flash stock recovery in fastboot, and unroot through the superuser app. Then relock in fastboot.
The AIO toolkits will not help with relocked and tampered on 1.54 because they require s-off, which is not available on that hboot. Also, factory reset won't unroot you; it may remove the superuser.apk but will not remove root access.
kibmikey1 said:
Noobs are what this thread is for. Why are you flaming and complaining in a Q&A thread anyway? If you're not going to help, get out of the way and flame on elsewhere.
Click to expand...
Click to collapse
Who's flaming and complaining, and I did help ... I wouldn't help you now but that's another story. As for noobs, If you can't be bothered to read and search then that says something about you. For starters, even though you were wrong (and not the OP) I did help, I have also spent more time helping on here than I have posting anything else, so if you don't like it, you know what you can do.
You might want to give correct advice aswell, if he's on Hboot 1.54 then he'd need S-Off to flash an older Hboot, which he cannot do. Thanks
iElvis said:
If your phone was 2.24 out of the box and you never went s-off, you don't need a ruu because your firmware would not have changed. So you just need to restore stock recovery and stock system files, then relock. Flash a stock rom, flash stock recovery in fastboot, and unroot through the superuser app. Then relock in fastboot.
The AIO toolkits will not help with relocked and tampered on 1.54 because they require s-off, which is not available on that hboot. Also, factory reset won't unroot you; it may remove the superuser.apk but will not remove root access.
Click to expand...
Click to collapse
when i red your reply it seemed too easy but no
stuck recovery when you mean that ''fastboot flash recovery recovery.img'' pulled from nandroid back up ? yes ur right i manged to do that it was succesful but no change even a systim rom is not available getting signature failure 'seems promising yah
i know my thing is hard but it shouldnt be like that right im runing a rom now 4.3 im fine with it but i really want to F*** htcdev members :v
I mean stock recovery, which you can pull from the firmware file for your phone. Find the recovery.img file in the zip and use that.
Stop trying to flash ruus and firmware packages in fastboot; you may screw up your phone doing it.
Just get a stock rom that correspond to the firmware package from the development forum and flash in custom recovery. Then flash the stock recovery in fastboot. Once that's done, you should be able to get OTAs.
iElvis said:
I mean stock recovery, which you can pull from the firmware file for your phone. Find the recovery.img file in the zip and use that.
Stop trying to flash ruus and firmware packages in fastboot; you may screw up your phone doing it.
Just get a stock rom that correspond to the firmware package from the development forum and flash in custom recovery. Then flash the stock recovery in fastboot. Once that's done, you should be able to get OTAs.
Click to expand...
Click to collapse
if you want to help me help me now
i have my reovery.img and it flashes perfectly
how to get stuck rom ?
you mean the file with date it is bout 1.8GB named 2013-08-27.19.58.35 that i should put it in supfic folder do i can flash it with recovery cwm ?
since i have my back up and since it is S-on i wont mind flashing any thing
Could somebody please help with a few brief answers in case I mess something up? I'm new to HTC/S-OFF concept.
I bought a used sprint htc one that I wish to return completely to stock in fear previous owner messed something up, and to start from scratch (SU can't install busybox).
The phone has been unlocked, and rooted, no S-OFF, Hboot 1.56 OTA updated to 4.06.651.9 stock. (don't need to edit hboot, or show "locked" again through S-OFF, just normal "relocked", and stock everything else. I know I need to relock bootloader, and stock recovery anyways)
Is an official RUU for 4.06.651.9 (slash .4) the only way to return to stock completely? I don't want/need S-OFF (currently available through Firewire for Sprint on 1.56) unless necessary.
Can I S-OFF, and then S-ON afterwards?
What is the difference between an official RUU vs pushing this stock firmware (4.06.651.9) or .4 through fastboot? Do I need to S-OFF and go to an earlier firmware, and THEN, go to the newest like some people suggest because of the radio?
What has the radio to do with going back to an earlier firmware, and then upgrading?
Is there a way to "freeze" the OTA software upgrade like it's possible on other non HTC devices?
Sorry to bother guys, I have read many threads, but I'm not so clear on these questions
ianthomas said:
Could somebody please help with a few brief answers in case I mess something up? I'm new to HTC/S-OFF concept.
I bought a used sprint htc one that I wish to return completely to stock in fear previous owner messed something up, and to start from scratch (SU can't install busybox).
The phone has been unlocked, and rooted, no S-OFF, Hboot 1.56 OTA updated to 4.06.651.9 stock. (don't need to edit hboot, or show "locked" again through S-OFF, just normal "relocked", and stock everything else. I know I need to relock bootloader, and stock recovery anyways)
Is an official RUU for 4.06.651.9 (slash .4) the only way to return to stock completely? I don't want/need S-OFF (currently available through Firewire for Sprint on 1.56) unless necessary.
Can I S-OFF, and then S-ON afterwards?
What is the difference between an official RUU vs pushing this stock firmware (4.06.651.9) or .4 through fastboot? Do I need to S-OFF and go to an earlier firmware, and THEN, go to the newest like some people suggest because of the radio?
What has the radio to do with going back to an earlier firmware, and then upgrading?
Is there a way to "freeze" the OTA software upgrade like it's possible on other non HTC devices?
Sorry to bother guys, I have read many threads, but I'm not so clear on these questions
Click to expand...
Click to collapse
... oh man so many questions and believe me this is the best way to go by it
long story short you can just factory reset your device and it will be like stock out of the box.
Now though you dont need it but here is the link to RUU if you really wanna do it but it wont make a difference if you are not experiencing any hiccups. but for this RUU to run you need to relock your botloader via fastboot.
http://forum.xda-developers.com/showthread.php?t=2658910
you are in a good position to gain s-off as you are already unlocked so go get it. folow rumrunner.us
if you get s-off 1st then no need to lock your bootloader. RUU runs irrespective of bootloader status if device is s-off.
and yes you can s-on after s-off.
hope this helps ...
Devilish_Angel said:
... oh man so many questions and believe me this is the best way to go by it
long story short you can just factory reset your device and it will be like stock out of the box.
Now though you dont need it but here is the link to RUU if you really wanna do it but it wont make a difference if you are not experiencing any hiccups. but for this RUU to run you need to relock your botloader via fastboot.
http://forum.xda-developers.com/showthread.php?t=2658910
you are in a good position to gain s-off as you are already unlocked so go get it. folow rumrunner.us
if you get s-off 1st then no need to lock your bootloader. RUU runs irrespective of bootloader status if device is s-off.
and yes you can s-on after s-off.
hope this helps ...
Click to expand...
Click to collapse
I really appreciate your help . I'm still a little stuck though. When you say:
"long story short you can just factory reset your device and it will be like stock out of the box."
If by that you mean to Factory Reset through the privacy options of any Android phone, then this is a big NO-NO for me from previous expirience with many other non HTC phones that would soft brick if I did that on a rooted phone. Maybe it works on HTC's, but it seems too easy to be true So I would rather not risk it, and go the RUU way if possible,
"Now though you dont need it but here is the link to RUU if you really wanna do it but it wont make a difference if you are not experiencing any hiccups. but for this RUU to run you need to relock your botloader via fastboot.
http://forum.xda-developers.com/showthread.php?t=2658910"
I was going to try that RUU, even though it's for 4.06.651.4, and I have 4.06.651.9. I was going to assume it works on all 4.0's firmwares on S-ON, and that I need S-OFF to go back to earlier firmwares? The info out there is very vague on this, but since I'm S-ON, I will risk it, since it seems the most I would get out of that in S-ON maybe a softbrick.
"you are in a good position to gain s-off as you are already unlocked so go get it. folow rumrunner.us"
The rumrunner threads seem to say it doesn't work on Hboot 1.56. So far I only read a few threads with people saying only Firewire works on Hboot 1.56, but again, others say it doesn't, and the info it's very vague. I will try S-OFF if I have to though
"and yes you can s-on after s-off."
This one does seem dangerous. The only credible info I found on it was from a popular dev in these threads saying NOT to be quoted about using this command because he wasn't sure either:
fastboot oem writesecureflag 3
Click to expand...
Click to collapse
So the info was vague/unclear again, so I will take a leap of faith with S-OFF if I have to, and report back anything else I find
ianthomas said:
I really appreciate your help . I'm still a little stuck though. When you say:
"long story short you can just factory reset your device and it will be like stock out of the box."
If by that you mean to Factory Reset through the privacy options of any Android phone, then this is a big NO-NO for me from previous expirience with many other non HTC phones that would soft brick if I did that on a rooted phone. Maybe it works on HTC's, but it seems too easy to be true So I would rather not risk it, and go the RUU way if possible,
"Now though you dont need it but here is the link to RUU if you really wanna do it but it wont make a difference if you are not experiencing any hiccups. but for this RUU to run you need to relock your botloader via fastboot.
http://forum.xda-developers.com/showthread.php?t=2658910"
I was going to try that RUU, even though it's for 4.06.651.4, and I have 4.06.651.9. I was going to assume it works on all 4.0's firmwares on S-ON, and that I need S-OFF to go back to earlier firmwares? The info out there is very vague on this, but since I'm S-ON, I will risk it, since it seems the most I would get out of that in S-ON maybe a softbrick.
"you are in a good position to gain s-off as you are already unlocked so go get it. folow rumrunner.us"
The rumrunner threads seem to say it doesn't work on Hboot 1.56. So far I only read a few threads with people saying only Firewire works on Hboot 1.56, but again, others say it doesn't, and the info it's very vague. I will try S-OFF if I have to though
"and yes you can s-on after s-off."
This one does seem dangerous. The only credible info I found on it was from a popular dev in these threads saying NOT to be quoted about using this command because he wasn't sure either:
So the info was vague/unclear again, so I will take a leap of faith with S-OFF if I have to, and report back anything else I find
Click to expand...
Click to collapse
... well you are the 1st one to experience problems after factory reset . usually it happens other way round. i cant remember how many times i have rooted how many phones of how many makes and never ever have i encountered any problems after resets. factory resets are done to rectify any harm done to the device OS by the user, apps, kernels, mods or something else. it brings the phone back to original stock out of the box state.
by the experiences i have with the phones you just need to reset it and if you are really adamant to RUU, you can.
as for the s-off is concerned, there is no harm trying rumrunner or firewater. they do no harm even if they fail. a lot of people including me have gained s-off with hboot 1.56. if rumrunner doesnt work for you try fire water and if that too fails, flash ARHD 41 and then try rumrunner ...
S-OFF - do it!
Devilish_Angel said:
... well you are the 1st one to experience problems after factory reset . usually it happens other way round. i cant remember how many times i have rooted how many phones of how many makes and never ever have i encountered any problems after resets. factory resets are done to rectify any harm done to the device OS by the user, apps, kernels, mods or something else. it brings the phone back to original stock out of the box state.
by the experiences i have with the phones you just need to reset it and if you are really adamant to RUU, you can.
as for the s-off is concerned, there is no harm trying rumrunner or firewater. they do no harm even if they fail. a lot of people including me have gained s-off with hboot 1.56. if rumrunner doesnt work for you try fire water and if that too fails, flash ARHD 41 and then try rumrunner ...
Click to expand...
Click to collapse
Take it from me, one who has replaced his One 3 times- twice being directly my fault, get S-OFF. If I could go back in time and slap younger me in the face, I would. Instead, I will tell you this- get S-OFF. It doesn't take a ton of work, and you will never find a reason to regret it. Plus, RootLinux has an HBOOT flasher in the Development forums if you really want everything to LOOK stock. Once you're S-OFF, you don't have to relock the bootloader to flash an RUU, another perk.
slyest12 said:
Take it from me, one who has replaced his One 3 times- twice being directly my fault, get S-OFF. If I could go back in time and slap younger me in the face, I would. Instead, I will tell you this- get S-OFF. It doesn't take a ton of work, and you will never find a reason to regret it. Plus, RootLinux has an HBOOT flasher in the Development forums if you really want everything to LOOK stock. Once you're S-OFF, you don't have to relock the bootloader to flash an RUU, another perk.
Click to expand...
Click to collapse
... well buddy you quoted the wrong guy . never mind. this is exactly what i was telling him to get s-off to make things easier. appreciate your help though ...
ianthomas said:
Is there a way to "freeze" the OTA software upgrade like it's possible on other non HTC devices?
Sorry to bother guys, I have read many threads, but I'm not so clear on these questions
Click to expand...
Click to collapse
It's my understanding that the OTA only works on bone stock phones.
slyest12 said:
It's my understanding that the OTA only works on bone stock phones.
Click to expand...
Click to collapse
Edited for clarity or the lack there of.
Or bone stock rooted Roms, however you have to flash stock recovery first if s-on, how about with s-off?
Little story to tell:
A day or two ago I got a notification of an ota*.9* to be exact, I tried installing it knowing it wouldn't cause I was rooted. I like to flash back to my stock Rom and update the apps and stuff so I get get the stock feel back without losing much from my daily driver Roms.
Anyways, there is a thread in the forums about installing this update, I tried it and wiped my phone minus the stock Rom, everything was gone even backups. The thread suggested to me to download this app sort of like flashify to flash stock recovery. After flashing stock recovery, well I had or think I had stock recovery cause I had to reinstall twrp, that's when I found out I wiped the heck out of my phone.
I had to start from scratch without a stock Rom cause what ever I did, my stock Rom was borked somehow, everything was gone, I couldn't "repair" missing stuff* like the weather/widget couldn't stick on the home screen. I had to make a sense six Rom my "stock" Rom while gathering more info on RUU and being s-off.
What I thought was this, I'd have to relock boot loader to do a RUU, which I didn't want to do, cause I am thinking I will lose root and have to htcdev again. But I'm s-off'd and now knowing that I won't need to relock bootloader, I have a question.
How do I EXACTLY go about RUU with s-off if I don't have to "oem lock"?
I s-off'd mainly to change boot splash and use a modded hboot to show its "not" rooted, I knew I don't have to htcdev again while s-off, but I was hoping to not come to that point, then this ota thing happened.
Sorry for a long post and prolly going way off topic, but s-off and RUUs or having to flash stock recovery in order to install an ota is confusing to me.
1. Can I RUU without relocking bootloader with s-off?
2. Can I install an ota update without flashing stock recovery with s-off?
3. Last thing, what are the steps to update my stock Rom, while being s-off?
Lol, nice hijack buddy, but it just so happens I have the same question
I got frustrated about a continuous brick while on S-ON, so I decided to S-OFF on my Hboot 1.56, and turns out, only Firewater was able to give me S-OFF. The process was very simple!!!
http://firewater-soff.com/
But even with S-OFF, I still soft brick or get into a bootloader bootloop while trying to install any non stock ROMS:
[Q] Bootloader Bootlopp soft brick on Viper 5.8.0 and other ROMS
I stopped trying more crazy things... I learned no to use TWRP 2.7 in my case, and use older versions, or PhilzTouch, but I still can't figure out how to either OTA update to .9, or install the Viper ROM correctly.
My guess is the same as yours... I shouldn't push a Stock odex ROM through fastboot, or ADB sideload through recovery. Having S-OFF means being able to use the RUU tool WITHIN a stock ROM itself, BUT BEFORE doing so, maybe it's best to flash a stock recovery, or this firmware file:
[Guide][How-to] Run 4.06.651.4 RUU on any windows without any problem..!!
That I guess it's the same found here (MD5 match "Full Firmware from RUU (fastboot flashable)"):
[RUU][Firmware]Sprint HTC One | 4.06.651.4 | Encrypted | Decrypted | Stock Rooted ROM
Anyways, before trying to do any of that, I will try to simply run the RUU from within the stock ROM, and hope the RUU flashes a firmware that contains a stock recovery as well (and maybe more?), so that maybe that's all I need to install the .9 OTA properly through the stock ROM, and after that, try and get the Viper ROM installed properly.
Will report back whatever I can find.
More useful posts:
[Tutorial][Rescue]Sprint HTC One users that flash GSM roms on their CDMA devices.
[ROM] Bad Boyz Sprint ONE ROMz | 4.4.2 | KitKat | Deodexed | myHUB | Updated 2/23/14
[HOW TO] ADB Sideload/Push if you Wipe Internal Storage And have no ROM to Flash
[Tutorial][Resource][Root]Unlock-Recovery-SuperSU for HTC One(M7)-Sprint-m7wls The all in one folder put togheter by BD619 in this post is pretty handy.
EDIT: Actually I will report back in my other question too, since this thread was supposed to be about RUU, and S-OFF, which I resolved through Firewater under Hboot 1.56.
Sorry for the hijack mang!!
Good info here though.
I tried flashing the stock Rom that's on post #2 on the ruu thread but I still get the ota nagging, and data is slow for some reason, that Rom is really wonky for me.
At the moment I'm using a sense 6 Rom and viper Rom 5.8, and data with those are well enough to say I can browse normally on 3g.
Anyways so what is being said is that we would have to just run the ruu though desktop and it should have stock bootloader so we can take the .9 ota. And then after its done we can just flash any custom recovery after that?
Is there really no way to just bypass the its, like how we can bypass hfa?
v1ral said:
Sorry for the hijack mang!!
Good info here though.
I tried flashing the stock Rom that's on post #2 on the ruu thread but I still get the ota nagging, and data is slow for some reason, that Rom is really wonky for me.
At the moment I'm using a sense 6 Rom and viper Rom 5.8, and data with those are well enough to say I can browse normally on 3g.
Anyways so what is being said is that we would have to just run the ruu though desktop and it should have stock bootloader so we can take the .9 ota. And then after its done we can just flash any custom recovery after that?
Is there really no way to just bypass the its, like how we can bypass hfa?
Click to expand...
Click to collapse
... There is a way to bypass hfa if you don't know yet ...
Devilish_Angel said:
... There is a way to bypass hfa if you don't know yet ...
Click to expand...
Click to collapse
I only know about deleting or modifying the "xxxOmad.apks" in the /system/app/ areas. Is there another way?
v1ral said:
I only know about deleting or modifying the "xxxOmad.apks" in the /system/app/ areas. Is there another way?
Click to expand...
Click to collapse
... here you go. download the attached zip file. flash the rom, boot the rom until you see hfa then restart device in recovery and flash the below file. when its done restart the device normally and guess what ???? no hfa ...
slyest12 said:
Take it from me, one who has replaced his One 3 times- twice being directly my fault, get S-OFF. If I could go back in time and slap younger me in the face, I would. Instead, I will tell you this- get S-OFF. It doesn't take a ton of work, and you will never find a reason to regret it. Plus, RootLinux has an HBOOT flasher in the Development forums if you really want everything to LOOK stock. Once you're S-OFF, you don't have to relock the bootloader to flash an RUU, another perk.
Click to expand...
Click to collapse
I forgot to thank you for your advise, which I took, and I don't regret There is a tiny little fine print about this though: " you don't have to relock the bootloader to flash an RUU"... That is not mentioned in the guides I read, and I will try to clarify in my noob post.
v1ral said:
Edited for clarity or the lack there of.
Or bone stock rooted Roms, however you have to flash stock recovery first if s-on, how about with s-off?
Sorry for a long post and prolly going way off topic, but s-off and RUUs or having to flash stock recovery in order to install an ota is confusing to me.
1. Can I RUU without relocking bootloader with s-off?
2. Can I install an ota update without flashing stock recovery with s-off?
3. Last thing, what are the steps to update my stock Rom, while being s-off?
Click to expand...
Click to collapse
It is confusing for me too, but one of my theories was right, and I felt like a dunce once I figured it out, and I think you figured it out too...
Anyways, the HTC one will be for my brother, so I had limited access to it, and finally did more tests on it to figure things out.
I will try and answer your questions to my best of knowledge, but please keep in mind this is a noob/guinea pig point of view that is still asking questions, and I may be wrong on some things, so bear with me, but this has worked for me:
===========================================================================
Being on a Sprint HTC ONE with Hboot 1.56, originally on stock 4.06.651.4 , and S-OFF thanks to Firewater (other methods failed for me). I would recommend getting S-OFF now (to whoever else this may help).
OK v1ral, as far as I know, the ability to flash the 4.06.651.4 RUU WITHOUT having to relock the bootloader is from WITHIN the stock ROM itself, NOT from fastboot or anywhere else.
TIP: When unlocking the bootloader, simply save the .BIN file HTCDEV sends you, and save the command used to unlock for quick unlocking and relocking, just in case.
However you have to flash stock recovery first if s-on, how about with s-off?
You don't have to flash a stock recovery, because the RUU itself does that for you, regardless of S-ON or S-OFF. The only condition is having to relock the bootloader if S-ON BEFORE running the 4.06.651.4 RUU from WITHIN the stock ROM you're in, but obviously that is not necessary if S-OFF.
Can I RUU without relocking bootloader with s-off?
As far as I know, yes. that is the perk of having S-OFF.
Can I install an ota update without flashing stock recovery with s-off?
As far as I know (please correct me), the RUU itself flashes a stock recovery anyways, or at least that's one of the messages it gives while working. Keep reading for the info on how to install the OTA properly in my case.
Last thing, what are the steps to update my stock Rom, while being s-off?
OK, here we go, there is a very important, and easy missing detail nobody mentions in the guides I read, and the reason I was soft bricking with any rom.
How to OTA update from 4.06.651.4 to 4.06.651.9 properly, regardless of being S-ON, or S-OFF, and avoid bootloader bootloop for noobs
First off, If you're already in trouble, and can't install a stock rom, in a bootloop, or don't know how to adb sideload a rom into your device, etc... PM me to try and help you out of it, and start off in a stock room. That may take more time.
Moving on, assuming you're already in a stock rom, or any 'working' rom for that matter, meet these requierements first:
Make sure you never installed HTC Sync before, EVER. Have proper drivers installed, and a correct ADB online connection to your phone is important. I'm just assuming you didn't lazy out, and know how to research the drivers in here already. I just need you to run the command
ADB devices
Click to expand...
Click to collapse
and get a correct online connection between your phone, and PC. Another thing is not to use usb 3.0, or the frontal usb inputs on your PC, and use the back inputs just in case...
And even MORE important tip, is to never... EVER... use cheap low quality or damaged usb cables. I learned this the hard way hard bricking 2 phones in my old LG LGNPST days (LGNPST is another type of flashing tool for LG devices).
Having a damaged usb cable may be really dangerous, specially if your'e S-OFF
Having an al in one folder with the tools to work is pretty convenient, and user BD619 gathered one in his thread
He may not always have the latest version of the TWRP or CWM/PhilzTouch recoveries in it, but you can easily get them in this forum obviously.
TIP: TWRP is the recommended recovery on this device, version 2.7.0.3 didn't work for me, but the new 2.7.0.4 seems better for me, but I still can't mount an OTG drive to it, so you may have to learn how to push/adb sideload ROMs or files into it like this.
OK, from WITHIN your stock ROM, run this 4.06.651.4 RUU first (you only need to relock bootloader prior to running it if you're S-ON):
http://forum.xda-developers.com/showthread.php?t=2658910
It doesn't matter if you're already on firmware 4.06.651.4, run it anyways (it will flash a stock recovery, and more), reboot, and
THEN relock your bootloader, regardless of being S-ON or S-OFF
That was the little detail I was missing, and should've figured out before...
After relocking the bootloader, reboot back in, and THEN, and only then, you can download and install the 4.06.651.9 update from within the Software Update option.
After updating properly to 4.06.651.9, it is then that you can unlock the bootloader back again, flash TWRP, and root with it, or get ROMS already rooted without hiccups.
Finally, if I'm wrong on any of the small details in this, please correct me, but it was what worked for me at least.
Devilish_Angel said:
... here you go. download the attached zip file. flash the rom, boot the rom until you see hfa then restart device in recovery and flash the below file. when its done restart the device normally and guess what ???? no hfa ...
Click to expand...
Click to collapse
Lol, what I meant to put is ota not about hfa.. I have stopped hfa on all the new flashed roms I get by renaming/deleting some files in the system/app.
Does that link work for all roms?
v1ral said:
Lol, what I meant to put is ota not about hfa.. I have stopped hfa on all the new flashed roms I get by renaming/deleting some files in the system/app.
Does that link work for all roms?
Click to expand...
Click to collapse
... It should. Moreover it is far more easy to flash a simple zip than mounting the file system, finding files and then deleting some and renaming some ? ...
I have a HTC One on the EE network in the UK and I am still currently on Android 4.3 and Sense 5.5, they haven't bothered to release Android 4.4 yet and I have no hope that they will release Sense 6.
So, I would like to know how to go about changing my EE branded phone into an Unlocked International Version so that I can receive OTA updates direct from HTC.
Current CID: ORANG001
Current Hboot: 1.55
Current Software Number: 3.63.61.1
Radio: 4A.21.3263.04
Locked Bootloader with S-On
I would very much appreciate any help you can give.
Thank-You
rh92 said:
I have a HTC One on the EE network in the UK and I am still currently on Android 4.3 and Sense 5.5, they haven't bothered to release Android 4.4 yet and I have no hope that they will release Sense 6.
So, I would like to know how to go about changing my EE branded phone into an Unlocked International Version so that I can receive OTA updates direct from HTC.
Current CID: ORANG001
Current Hboot: 1.55
Current Software Number: 3.63.61.1
Radio: 4A.21.3263.04
Locked Bootloader with S-On
I would very much appreciate any help you can give.
Thank-You
Click to expand...
Click to collapse
first of all you need to unlock your bootloader and s-off your phone, debrand is not possible with s=on
the you would need to change your cid to something like HTC__001 or developer edition cid, one fastboot command required to do this.
and then run the correct RUU for those cid's and your done.
its quite easy to do, the hardest part is getting s-off, however you may be ok on 1.55 hboot, try rumrunner, read the instructions and download the required file here: http://rumrunner.us/
Seanie280672 said:
first of all you need to unlock your bootloader and s-off your phone, debrand is not possible with s=on
the you would need to change your cid to something like HTC__001 or developer edition cid, one fastboot command required to do this.
and then run the correct RUU for those cid's and your done.
its quite easy to do, the hardest part is getting s-off, however you may be ok on 1.55 hboot, try rumrunner, read the instructions and download the required file here: http://rumrunner.us/
Click to expand...
Click to collapse
Do I need custom recovery? If so which is best.
And do I need to have a custom ROM installed to gain s-off or can s-off be achieved on my current EE branded ROM?
Thanks
rh92 said:
Do I need custom recovery? If so which is best.
And do I need to have a custom ROM installed to gain s-off or can s-off be achieved on my current EE branded ROM?
Thanks
Click to expand...
Click to collapse
nope its not required for either, you should be able to s-off on stock rom, if you get an error or for some reason it fails, then you MAY have to flash a custom recovery and custom rom / kernel.
The RUU's will put you back to fully stock anyway in the end.
Seanie280672 said:
nope its not required for either, you should be able to s-off on stock rom, if you get an error or for some reason it fails, then you MAY have to flash a custom recovery and custom rom / kernel.
The RUU's will put you back to fully stock anyway in the end.
Click to expand...
Click to collapse
If the s-off does cause an error or it fails, can this cause my device to get bricked?
And by fully stock do you mean that the RUU turns s-on and locks my boot loader? (just in case I need to send my phone in for repair).
Thanks
rh92 said:
If the s-off does cause an error or it fails, can this cause my device to get bricked?
And by fully stock do you mean that the RUU turns s-on and locks my boot loader? (just in case I need to send my phone in for repair).
Thanks
Click to expand...
Click to collapse
no your phone wont brick
and no the ruu wont turn your phone s-on, you will need to lock your bootloader before running the RUU, but that's one simple command too, but only after s-off.
all you need right now is to make sure you have the drivers installed and that your device is detected in windows both when booted into a rom and on the bootloader screen.
Seanie280672 said:
no your phone wont brick
and no the ruu wont turn your phone s-on, you will need to lock your bootloader before running the RUU, but that's one simple command too, but only after s-off.
all you need right now is to make sure you have the drivers installed and that your device is detected in windows both when booted into a rom and on the bootloader screen.
Click to expand...
Click to collapse
After installing the RUU how would I get s-on?
Thanks
rh92 said:
After installing the RUU how would I get s-on?
Thanks
Click to expand...
Click to collapse
don't s-on, never s-on simple as that.
Seanie280672 said:
don't s-on, never s-on simple as that.
Click to expand...
Click to collapse
Ok, I was just asking in case I needed to send my phone in for repair in the future.
rh92 said:
Ok, I was just asking in case I needed to send my phone in for repair in the future.
Click to expand...
Click to collapse
not really something they will check to be honest, but if you s-on and you've played about with your phone down the line, like flashed a modified firmware or hboot, you will get an instant brick, if your hboot version is too high you will get the tampered flag back, or if you make a mistake along the way and the fix requires s-off, it will be very difficult to get again.
Seanie280672 said:
not really something they will check to be honest, but if you s-on and you've played about with your phone down the line, like flashed a modified firmware or hboot, you will get an instant brick, if your hboot version is too high you will get the tampered flag back, or if you make a mistake along the way and the fix requires s-off, it will be very difficult to get again.
Click to expand...
Click to collapse
So, is the following step by step list correct.
1. Unlock boot loader
2. Get s-off via rumrunner
3. Change CID
4. Lock boot loader
5. Run RUU
And, I am currently on 4.3 and Sense 5.5, so can I go straight to the sense 6 and Android 4.4 RUU, or do I have to install the sense 5.5 and Android 4.4 RUU first.
Thanks
rh92 said:
So, is the following step by step list correct.
1. Unlock boot loader
2. Get s-off via rumrunner
3. Change CID
4. Lock boot loader
5. Run RUU
And, I am currently on 4.3 and Sense 5.5, so can I go straight to the sense 6 and Android 4.4 RUU, or do I have to install the sense 5.5 and Android 4.4 RUU first.
Thanks
Click to expand...
Click to collapse
yup that's the correct order, and you will have to use this RUU as its the only full RUU available, everything else is just OTA's
http://androidruu.com/getdownload.p...10.38r.1157.04L_release_353069_signed_2-1.exe
Seanie280672 said:
yup that's the correct order, and you will have to use this RUU as its the only full RUU available, everything else is just OTA's
http://androidruu.com/getdownload.p...10.38r.1157.04L_release_353069_signed_2-1.exe
Click to expand...
Click to collapse
And after installing this RUU I can just download Sense 6 via OTA.
rh92 said:
And after installing this RUU I can just download Sense 6 via OTA.
Click to expand...
Click to collapse
yes, just accept the ota's one at a time.
Seanie280672 said:
yes, just accept the ota's one at a time.
Click to expand...
Click to collapse
Thanks for your help
I have an PN07200, how can I get sense 6, which will be the best RUU and CID?.... Thanks!
Enviado desde mi HTC One X+ mediante Tapatalk
is it possible to re-apply the branding?
i.e.
RUU
change cid
OTA with brand change
gwaitsi said:
is it possible to re-apply the branding?
i.e.
RUU
change cid
OTA with brand change
Click to expand...
Click to collapse
yup, change your cid to its original one, and find your service providers RUU and flash it.
Hi guys! I just got my brand new htc one (m7) with this stock software:
M7_UL PVT SHIP S-ON RH
HBOOT-1.55.0000
RADIO-4A.21.3263.04
OpenDSP-v32.120.274.0909
OS-3.63.708.3
eMMC-boot 2048MB
Oct 29 2013,17:34:05.0
HBOOT
Xperia's are easily rooted, deodexed, unlocked, re-locked, downgraded, etc. and if I want to revert to stock, i'll just flash stock FTF and return to warranty unlike HTC phones there's this hboot, s-off, etc. I read a lot of tutorials, noob guides, etc. but got confused on where to start. I just want root without unlocking bootloader or s-off and revert to stock when needed. Any tips guys? and how do you compare xperia development from htc's. Thanks guys.
cyrom said:
Hi guys! I just got my brand new htc one (m7) with this stock software:
M7_UL PVT SHIP S-ON RH
HBOOT-1.55.0000
RADIO-4A.21.3263.04
OpenDSP-v32.120.274.0909
OS-3.63.708.3
eMMC-boot 2048MB
Oct 29 2013,17:34:05.0
HBOOT
Xperia's are easily rooted, deodexed, unlocked, re-locked, downgraded, etc. and if I want to revert to stock, i'll just flash stock FTF and return to warranty unlike HTC phones there's this hboot, s-off, etc. I read a lot of tutorials, noob guides, etc. but got confused on where to start. I just want root without unlocking bootloader or s-off and revert to stock when needed. Any tips guys? and how do you compare xperia development from htc's. Thanks guys.
Click to expand...
Click to collapse
you can only get temproot without unlocking the bootloader
the steps for your phone are
unlock bootloader @ htcdev.com
flash custom recovery (TWRP 2.6.3.3 preferred)
Make a Nandroid Backup
Flash SuperSU
reboot and enjoy
clsA said:
you can only get temproot without unlocking the bootloader
the steps for your phone are
unlock bootloader @ htcdev.com
flash custom recovery (TWRP 2.6.3.3 preferred)
Make a Nandroid Backup
Flash SuperSU
reboot and enjoy
Click to expand...
Click to collapse
so meaning to say, unlocking bootloader is a must, right?
cyrom said:
so meaning to say, unlocking bootloader is a must, right?
Click to expand...
Click to collapse
Yes if you want perm root
hello
cyrom said:
so meaning to say, unlocking bootloader is a must, right?
Click to expand...
Click to collapse
Yes,unlocking bootloader is must if you want to get permanent root.Further, if you want to return to complete stock in future,you should think about getting S-Off too.I have had a lot of problem because i can't get S-Off .But you should study before you do anything. Unlocking bootloader will result in loss of data/preload* apps which is a serious problem if you want to get future official OTA updates.If you unlock bootloader,u have to flash data/preload apps again if an official OTA update comes in near future. The most serious part is that the OTA updates check md5 of the apps intalled,so each app of data/preload must have the same md5 as before.But, if you are planning to use custom roms and you don't want official updates, that is not going to be a problem.There are several things that should be carefully studied before you do anything.I can give you a head start on what items to study.
1.check your CID ,mid,firmware version and note it.
2.Search OTA which matches your CID,mid and firmware version, it contains the stock recovery,data/preload apps which you may need in future.
3.Try to learn about S-ON/S-OFF, their uses and implications.
4.Do study about how OTA affects your chances to get S-OFF which you may need in future during serious problems.
5. try to read more and more through the forum, this is must.
Lastly,if you need comprehensive details on unlocking bootloader,flashing recovery,rooting and more, go through the video tutorials by "Sakitech" on youtube.I found them the most useful ones.And. last but not the least, this is all my opinion.Good luck!:good:
clsA said:
Yes if you want perm root
Click to expand...
Click to collapse
oh i see. btw i'm on 4.4.3 (6.13.708.1) and i can simply unlock my BL and get permroot but if i needed to revert to stock i can just flash 4.3 (3.63.708.3) via cmd and get 100% stock?
cyrom said:
oh i see. btw i'm on 4.4.3 (6.13.708.1) and i can simply unlock my BL and get permroot but if i needed to revert to stock i can just flash 4.3 (3.63.708.3) via cmd and get 100% stock?
Click to expand...
Click to collapse
only if you get s-off ... you can not flash a RUU lower than your current software version with s-on
The post above by @sudhirtripathee explains alot
thanks for posting that
@sudhirtripathee thanks mate! i found one stock ota zip for my firmware but it's 4.3 (out-of-the-box) not sure if it's safe to downgrade since im on 4.4.3 with S-ON. So yeah, I'll keep reading before a modify my m7.
cyrom said:
@sudhirtripathee thanks mate! i found one stock ota zip for my firmware but it's 4.3 (out-of-the-box) not sure if it's safe to downgrade since im on 4.4.3 with S-ON. So yeah, I'll keep reading before a modify my m7.
Click to expand...
Click to collapse
he mentions the OTA contains files you may need in the future ... it's of no use to you now your already above that version. When you unlock the bootloader your phone gets wiped and you loose (everything) a folder called data/preload
that's needed later to take a new OTA update. That folder can sometimes be retrieved from an old OTA package.
I know it seems confusing now but it will all be simple once you start doing it.
clsA said:
he mentions the OTA contains files you may need in the future ... it's of no use to you now your already above that version. When you unlock the bootloader your phone gets wiped and you loose (everything) a folder called data/preload
that's needed later to take a new OTA update. That folder can sometimes be retrieved from an old OTA package.
I know it seems confusing now but it will all be simple once you start doing it.
Click to expand...
Click to collapse
sudhirtripathee said:
Yes,unlocking bootloader is must if you want to get permanent root.Further, if you want to return to complete stock in future,you should think about getting S-Off too.I have had a lot of problem because i can't get S-Off .But you should study before you do anything. Unlocking bootloader will result in loss of data/preload* apps which is a serious problem if you want to get future official OTA updates.If you unlock bootloader,u have to flash data/preload apps again if an official OTA update comes in near future. The most serious part is that the OTA updates check md5 of the apps intalled,so each app of data/preload must have the same md5 as before.But, if you are planning to use custom roms and you don't want official updates, that is not going to be a problem.There are several things that should be carefully studied before you do anything.I can give you a head start on what items to study.
1.check your CID ,mid,firmware version and note it.
2.Search OTA which matches your CID,mid and firmware version, it contains the stock recovery,data/preload apps which you may need in future.
3.Try to learn about S-ON/S-OFF, their uses and implications.
4.Do study about how OTA affects your chances to get S-OFF which you may need in future during serious problems.
5. try to read more and more through the forum, this is must.
Lastly,if you need comprehensive details on unlocking bootloader,flashing recovery,rooting and more, go through the video tutorials by "Sakitech" on youtube.I found them the most useful ones.And. last but not the least, this is all my opinion.Good luck!:good:
Click to expand...
Click to collapse
So can you guys elaborate the safest steps on modding htc and return to a 100% stock. Thank you guys!
Sent from my HTC One using XDA Free mobile app
cyrom said:
So can you guys elaborate the safest steps on modding htc and return to a 100% stock. Thank you guys!
Sent from my HTC One using XDA Free mobile app
Click to expand...
Click to collapse
cyrom said:
So can you guys elaborate the safest steps on modding htc and return to a 100% stock. Thank you guys!
Sent from my HTC One using XDA Free mobile app
Click to expand...
Click to collapse
In my opinion, unlock your bootloader,intall custom recovery, and root. After you do all these steps, your device's bootloader menu will show tampered and unlocked flag.So, if you want to remove those flags in future, you will strictly need S-OFF. So, you could see how important is it to get S-OFF. Getting S-OFF gets harder as the hboot version of your phone increases and hboot version normally increases after official software update. In some cases, you will need to use premium apps like Moonshine to get S-OFF.So i advice you to unlock bootloader, intall custom recovery,root and then get S-OFF. Having all of them gives you entire freedom in modding. But, after having S-OFF, you will also need to be more responsible when you flash things. That's why, i told you to read as much as possible. If you want to do what i told you, follow these steps.
1.unlock bootloader, install custom recovery, and root.Link:http://www.youtube.com/watch?v=kJYAS2KN17Y
2.to get S-OFF, try: http://firewater-soff.com/instructions/
3. During the end of second step, if you get "Whelp it sucks,no amount of re-flashing custom roms and kernel will do", you will need moonshine to S-OFF. Since it is a premium app,AFAIK, you will need to pay 25$. But, before you pay, they will make sure whether or not will it work on you device.Link: http://forum.xda-developers.com/showthread.php?t=2291087, http://moonshine.io/
4.and to return back to 100% stock in future, this tutorial might help: http://forum.xda-developers.com/showthread.php?t=2358738
sudhirtripathee said:
In my opinion, unlock your bootloader,intall custom recovery, and root. After you do all these steps, your device's bootloader menu will show tampered and unlocked flag.So, if you want to remove those flags in future, you will strictly need S-OFF. So, you could see how important is it to get S-OFF. Getting S-OFF gets harder as the hboot version of your phone increases and hboot version normally increases after official software update. In some cases, you will need to use premium apps like Moonshine to get S-OFF.So i advice you to unlock bootloader, intall custom recovery,root and then get S-OFF. Having all of them gives you entire freedom in modding. But, after having S-OFF, you will also need to be more responsible when you flash things. That's why, i told you to read as much as possible. If you want to do what i told you, follow these steps.
1.unlock bootloader, install custom recovery, and root.Link:http://www.youtube.com/watch?v=kJYAS2KN17Y
2.to get S-OFF, try: http://firewater-soff.com/instructions/
3. During the end of second step, if you get "Whelp it sucks,no amount of re-flashing custom roms and kernel will do", you will need moonshine to S-OFF. Since it is a premium app,AFAIK, you will need to pay 25$. But, before you pay, they will make sure whether or not will it work on you device.Link: http://forum.xda-developers.com/showthread.php?t=2291087, http://moonshine.io/
4.and to return back to 100% stock in future, this tutorial might help: http://forum.xda-developers.com/showthread.php?t=2358738
Click to expand...
Click to collapse
thank you sir!
sorry for bumping this thread..
I think i've done enough reading so correct me if i'm wrong, just making sure before I touch my phone.
my current stock status:
**LOCKED**
M7-UL PVT SHIP S-ON RH
HBOOT - 1.57.0000
RADIO - 4T.28.3218.04
Open DSP - v32.120.274.0909
OS - 6.13.708.1
eMMc - boot 2048MB
Jul 22 2014, 20:59:16.0
Click to expand...
Click to collapse
To gain permanent root access:
I'm gonna need to unlock bootloader first;
Make a stock nandroid (with stock recovery intact via cmd fastboot boot recovery.img);
Install custom recovery and install SuperSU.zip
To revert to 100% stock:
I'm gonna be needing S-OFF. (i'm on 1.57 so I'm gonna search for it.)
flash my stock nandroid
flash stock recovery (if fastboot boot recovery.img didnt work)
lock recovery
fix tampered/relock flag
done.
Thanks!
cyrom said:
I think i've done enough reading so correct me if i'm wrong, just making sure before I touch my phone.
my current stock status:
To gain permanent root access:
1)I'm gonna need to unlock bootloader first; + 2)flash a custom recovery like TWRP
3)Make a stock nandroid (with stock recovery intact via cmd fastboot boot recovery.img); ---> fastboot boot recovery.img command only work on hboot 1.44 so you'll need to make a nandroid backup with the recovery installed on your phone which will overwrite your stock recovery.
Install custom recovery and 3)install SuperSU.zip
To revert to 100% stock:
I'm gonna be needing S-OFF. (i'm on 1.57 so I'm gonna search for it.) --> Firewater or Sunshine if firewater doesnt work.
flash my stock nandroid + flash back /data/preload folder (wiped when unlocking bootloader)
flash stock recovery (if fastboot boot recovery.img didnt work) If you can find your stock recovery somewhere (overwritten by the custom recovery)
lock recovery
fix tampered/relock flag ---> might come back if removed on hboot 1.55 and above
Click to expand...
Click to collapse
see above quote in blue
or
to revert to stock
flash the 2.24.708.4 RUU.zip which will also flash the stock recovery
remove flags etc etc
you might want to take a look at nkk71's guide to returning 100% stock (linked in my sig)
alray said:
see above quote in blue
or
to revert to stock
flash the 2.24.708.4 RUU.zip which will also flash the stock recovery
remove flags etc etc
Click to expand...
Click to collapse
Thanks! but is is ok to downgrade? my out of the box version was 3.63.708.3 i'll download it anyway.
cyrom said:
Thanks! but is is ok to downgrade? my out of the box version was 3.63.708.3 i'll download it anyway.
Click to expand...
Click to collapse
yes but downgrade only if needed (like to return to stock) You must have s-off to downgrade and use this RUU. Once downgraded you can take ota to re-update your phone.
alray said:
yes but downgrade only if needed (like to return to stock) You must have s-off to downgrade and use this RUU. Once downgraded you can take ota to re-update your phone.
Click to expand...
Click to collapse
thanks for the heads up. i thought id never find ruu zip for my version.
cyrom said:
thanks for the heads up. i thought id never find ruu zip for my version.
Click to expand...
Click to collapse
just confirm that the ruu match your MID and CID
CID and MID of the ruu can be found in the android-info.txt file of the ruu
alray said:
see above quote in blue
or
to revert to stock
flash the 2.24.708.4 RUU.zip which will also flash the stock recovery
remove flags etc etc
you might want to take a look at nkk71's guide to returning 100% stock (linked in my sig)
Click to expand...
Click to collapse
one more thing, if i flash the RUU.zip for my version, my current hboot (1.57) will also be downgraded to that version's hboot?
and will it be back to s-on (if i succeeded s-off now) ? thanks
cyrom said:
one more thing, if i flash the RUU.zip for my version, my current hboot (1.57) will also be downgraded to that version's hboot?
and will it be back to s-on (if i succeeded s-off now) ? thanks
Click to expand...
Click to collapse
yes hboot will also be downgraded. You will not loose s-off when flashing a ruu. Only turn s-on back if you must send the phone for warranty.
Hi guys
Basically I need to send my device into HTC for repair. It is S-OFF and I have a stock HTC European _001 rom on it. I really really need to restore to the UK O2_001 stock rom and get back to S-ON to avoid any possible issues with the warranty.
The problem is I can't find any O2 UK zips or nandroid backups to flash. For some reason the RUU files do not work for me, and I really don't have the time to be troubleshooting this.
I would really appreciate it if someone could upload a nandroid backup that I can use very soon? Otherwise I'll need to stick with the unbranded HTC Europe rom and risk them knowing I've unlocked the device.
Thanks for any help.
fade2black101 said:
Hi guys
Basically I need to send my device into HTC for repair. It is S-OFF and I have a stock HTC European _001 rom on it. I really really need to restore to the UK O2_001 stock rom and get back to S-ON to avoid any possible issues with the warranty.
The problem is I can't find any O2 UK zips or nandroid backups to flash. For some reason the RUU files do not work for me, and I really don't have the time to be troubleshooting this.
I would really appreciate it if someone could upload a nandroid backup that I can use very soon? Otherwise I'll need to stick with the unbranded HTC Europe rom and risk them knowing I've unlocked the device.
Thanks for any help.
Click to expand...
Click to collapse
if you want to follow my guide http://forum.xda-developers.com/showthread.php?t=2541082
Files you'll need are in post #7 under "HTC One M7_UL - modelid=PN0710000 - cidlist=O2___001,O2___102"
EDIT: there's also this RUU http://androidruu.com/getdownload.p...8_10.38r.1157.04L_release_353143_signed_2.exe
but as mentioned in my guide, i don't encourage going s-off to s-on on newer firmware
nkk71 said:
if you want to follow my guide http://forum.xda-developers.com/showthread.php?t=2541082
Files you'll need are in post #7 under "HTC One M7_UL - modelid=PN0710000 - cidlist=O2___001,O2___102"
EDIT: there's also this RUU http://androidruu.com/getdownload.p...8_10.38r.1157.04L_release_353143_signed_2.exe
but as mentioned in my guide, i don't encourage going s-off to s-on on newer firmware
Click to expand...
Click to collapse
Hello, thanks for that
Unfortunately I can't seem to downgrade the bootloader. I'm on 1.61.
Not entirely sure what to do now.. Will it be possible to achieve S-ON again and lock the bootloader without downgrading the hboot?
I don't really have time to spend ages on this, as the phone will be getting collected on Friday and I'm busy with work. I also don't really have time to troubleshoot the 100000 reasons why RUU.exe files aren't working for me and why I can't downgrade the bootloader. May just have to send it in unlocked and hope for the best.
fade2black101 said:
Hello, thanks for that
Unfortunately I can't seem to downgrade the bootloader. I'm on 1.61.
Not entirely sure what to do now.. Will it be possible to achieve S-ON again and lock the bootloader without downgrading the hboot?
I don't really have time to spend ages on this, as the phone will be getting collected on Friday and I'm busy with work. I also don't really have time to troubleshoot the 100000 reasons why RUU.exe files aren't working for me and why I can't downgrade the bootloader. May just have to send it in unlocked and hope for the best.
Click to expand...
Click to collapse
so quick and dirty? (and hope for the best)... did you use sunshine to s-off? before i post the steps.
haha
And yes I did. And I plan to use it again when I get phone back. Let me know your suggestion and I'll give it a go when I have some time
fade2black101 said:
haha
And yes I did. And I plan to use it again when I get phone back. Let me know your suggestion and I'll give it a go when I have some time
Click to expand...
Click to collapse
okay cool, i only asked because sunshine will work again (without needing to pay again), in case that infamous "tamper detected - rebooting" happens (shouldnt in your case but just in case it does)
gimme a few minutes, and i'll post instructions with links....
Thanks
I will check this out tomorrow when I have some time
fade2black101 said:
Thanks
I will check this out tomorrow when I have some time
Click to expand...
Click to collapse
okay, should be easy enough:
1) download Guru_Bootloader_Reset_1.0.zip and put it on your virtual storage
2) download 4.19.401.9-TWRP2633_combined_nowipe.zip
if need be change cid to a compatible one:
Code:
fastboot oem writecid HTC__001
fastboot reboot-bootloader
flash firmware
Code:
fastboot oem rebootRUU
fastboot flash zip 4.19.401.9-TWRP2633_combined_nowipe.zip
fastboot flash zip 4.19.401.9-TWRP2633_combined_nowipe.zip
fastboot reboot-bootloader
set back O2 UK cid:
Code:
fastboot oem writecid O2___001
fastboot reboot-bootloader
3) go to RECOVERY (it should be TWRP 2.6.3.3 from the file above) and run the Bootloader Reset
--> remove TAMPERED
--> set LOCKED
4) go back to bootloader, and check it says LOCKED, and no more TAMPERED
5) download RUU_4.20.206.16.EXE
and run it
(if it "exits" for some unknown reason, make sure you have this installed vcredist)
6) reboot the phone to make sure it boots up fine, do not take OTA updates
7) if you really insist, go s-on
Code:
fastboot oem writesecureflag 3
8) reboot three times (do not take any OTAs, especially above 6.xx), and make sure no TAMPERED is triggered
nkk71
You're a star! Thank you so much for that. After hours spent fumbling about I spent 20 minutes following your instructions today and everything worked perfectly. The Visual C++ file you suggested did the trick too, even after I installed several other (wrong ones) yesterday. Really happy this is finally sorted
Just a quick question. I haven't gone back to S-ON yet. I think it may not be neccessary for the warranty, but maybe I shouldn't risk it as I can always just gain S-OFF again via Sunshine once I get the phone back (unless they inexplicably change the motherboard). I'm wondering if there is a high risk of bricking my device if I run that S-ON command?
Cheers once again!
fade2black101 said:
nkk71
You're a star! Thank you so much for that. After hours spent fumbling about I spent 20 minutes following your instructions today and everything worked perfectly. The Visual C++ file you suggested did the trick too, even after I installed several other (wrong ones) yesterday. Really happy this is finally sorted
Just a quick question. I haven't gone back to S-ON yet. I think it may not be neccessary for the warranty, but maybe I shouldn't risk it as I can always just gain S-OFF again via Sunshine once I get the phone back (unless they inexplicably change the motherboard). I'm wondering if there is a high risk of bricking my device if I run that S-ON command?
Cheers once again!
Click to expand...
Click to collapse
there's no risk in bricking using that "fastboot oem writesecureflag 3" command to set s-on; the RUU would have set everything back to stock; if in the unlikely event the "TAMPERED" comes back, you'll need to s-off again, and use my guide with the 1.xx RUU + nandroid method
as for sending it in S-OFF, it's really country/carrier/service centre/person specific.... from what i've seen UK is one of the most tolerant countries (some people have even sent the phone in with tamperd and running a custom rom, and still got the camera fixed)
but it's your call, i cant really say for sure how they would react.
and if all is good now, could you also edit the main thread title to include [SOLVED] (go to 1st post click EDIT, at the bottom of the edit window click GO ADVANCED, then you can edit the main title), thanks and good luck