Couple quick question regarding locking the re-locking the bootloader.
First off I have the ATT One X rooted with TWRP Recovery. To go back to stock if I so choose, would I have to reflash the stock recovery then do fastboot oem lock before running the ruu or can i just fastboot oem lock the bootloader without flashing the stock recovery, then run the ruu?
I think I have to reflash the stock recovery first before relocking the bootloader. If that's the case, can someone link to the stock recovery img file?
I also read that if you're currently rooted and has your CID, you can update to 2.20 and root again...is that still the case?
Thanks
plmiller0905 said:
Couple quick question regarding locking the re-locking the bootloader.
First off I have the ATT One X rooted with TWRP Recovery. To go back to stock if I so choose, would I have to reflash the stock recovery then do fastboot oem lock before running the ruu or can i just fastboot oem lock the bootloader without flashing the stock recovery, then run the ruu?
I think I have to reflash the stock recovery first before relocking the bootloader. If that's the case, can someone link to the stock recovery img file?
I also read that if you're currently rooted and has your CID, you can update to 2.20 and root again...is that still the case?
Thanks
Click to expand...
Click to collapse
You can just fastboot oem lock, the RUU will take care of restoring the original ROM.
EDIT: This is my 123 post
plmiller0905 said:
Couple quick question regarding locking the re-locking the bootloader.
First off I have the ATT One X rooted with TWRP Recovery. To go back to stock if I so choose, would I have to reflash the stock recovery then do fastboot oem lock before running the ruu or can i just fastboot oem lock the bootloader without flashing the stock recovery, then run the ruu?
I think I have to reflash the stock recovery first before relocking the bootloader. If that's the case, can someone link to the stock recovery img file?
I also read that if you're currently rooted and has your CID, you can update to 2.20 and root again...is that still the case?
Thanks
Click to expand...
Click to collapse
If you want to go back to stock just fastboot oem lock then run the RUU. This is what I did. You can then re-unlock the bootloader and install SuperSU to reestablish root. It's pretty easy. Keep in mind, once you go to 2.20 you can not flash boot.img or radios from TWRP. You have to use adb to flash the boot.img, then boot into recovery and flash the ROM.
If you go into the Dev section, one of the first threads covers this and actually has a guide so you wouldn't have had to ask a question.
danny39 said:
You can just fastboot oem lock, the RUU will take care of restoring the original ROM.
EDIT: This is my 123 post
Click to expand...
Click to collapse
So even though I have a custom recovery (TWRP) I don't have to flash the stock recovery before I relock the bootloader?
plmiller0905 said:
So even though I have a custom recovery (TWRP) I don't have to flash the stock recovery before I relock the bootloader?
Click to expand...
Click to collapse
Here. You don't need the 1.85 RUU though. Just use 2.20 and skip the manual update from AT&T.
http://forum.xda-developers.com/showthread.php?t=1812039&highlight=2+20+unlock
Butters619 said:
If you want to go back to stock just fastboot oem lock then run the RUU. This is what I did. You can then re-unlock the bootloader and install SuperSU to reestablish root. It's pretty easy. Keep in mind, once you go to 2.20 you can not flash boot.img or radios from TWRP. You have to use adb to flash the boot.img, then boot into recovery and flash the ROM.
If you go into the Dev section, one of the first threads covers this and actually has a guide so you wouldn't have had to ask a question.
Click to expand...
Click to collapse
Butters619 said:
Here. You don't need the 1.85 RUU though. Just use 2.20 and skip the manual update from AT&T.
http://forum.xda-developers.com/showthread.php?t=1812039&highlight=2+20+unlock
Click to expand...
Click to collapse
Thanks...I really appreciate it
plmiller0905 said:
So even though I have a custom recovery (TWRP) I don't have to flash the stock recovery before I relock the bootloader?
Click to expand...
Click to collapse
No, it's the opposite: You can't RUU until you relock. It will fail if you try.
iElvis said:
No, it's the opposite: You can't RUU until you relock. It will fail if you try.
Click to expand...
Click to collapse
Oh ok...gotcha...so fastboot lock bootloader then run the ruu...great.
Like I mentioned before...I just got a little confused because people on YouTube is also flashing a stock recovery IMG before running the ruu.
Sent from my HTC One X using Tapatalk 2
plmiller0905 said:
So even though I have a custom recovery (TWRP) I don't have to flash the stock recovery before I relock the bootloader?
Click to expand...
Click to collapse
RUU will restore your recovery to the stock recovery.
Just keep in mind that once you lock your bootloader you won't be able to boot your phone until you run the RUU. So make sure you're ready to go with the RUU before you fastboot oem lock.
Related
So to get current I would just flash to the newest ruu, then root it (can you root 1.85?), then open the downloader, then flash cwm?
Just trying to cover my bases.
Sent from my HTC One X using XDA
Is your objective to update to 1.85 and remain rooted?
joho5 said:
So to get current I would just flash to the newest ruu, then root it (can you root 1.85?), then open the downloader, then flash cwm?
Just trying to cover my bases.
Sent from my HTC One X using XDA
Click to expand...
Click to collapse
If you are currently bootloader unlocked, then go into fastboot etc and "fastboot oem unlock" (http://forum.xda-developers.com/showthread.php?t=1675312).
If not, then flash new RUU.
Afterwards bootloader unlock.
Then flash CWM.
Finally flash Superuser through CWM.
Then you can flash custom ROMs (hopefully more are coming!!!).
ce12373 said:
If you are currently bootloader unlocked, then go into fastboot etc and "fastboot oem unlock" (http://forum.xda-developers.com/showthread.php?t=1675312).
If not, then flash new RUU.
Afterwards bootloader unlock.
Then flash CWM.
Finally flash Superuser through CWM.
Then you can flash custom ROMs (hopefully more are coming!!!).
Click to expand...
Click to collapse
I am not unlocked. I'm still on 1.72 just debloated and rooted. To unlock my bootloader, I just use htcdev right?
So I will flash current ruu, then unlock with htcdev, then flash cwm, and then flash the root and ill be ready?
I got a question, in the future will you always have to be on that certain ruu to flash that particular Rom? I come from the infuse where once you were rooted and had cwm, you could skip around rims by cwm every time, didn't have to do anything prior to each custom rom.
Sent from my HTC One X using XDA
Ok, so Ive relocked my bootloader and have no root. I didn't run RUU because I was on official rom already. Do I still need RUU? My Bootloader says relocked security warning?
Did you have a stock recovery before?
No because on one post it no need to change recovery
Just checked the bootloader and when I pressed recovery it took my to fastboot.
Did you purposely install a custom recovery? If no, you are good to go. If you have, you will need to run the RUU. OTA needs stock recovery.
yeah I installed through cmd. Do I need RUU
????
I got my HOX about 2 weeks now. I really want to flash it with a custom Rom. Tried lots of rooting instructions with no success. Phone is now back to factory reset using RRU method. I got the bootloader unlock. No success loading Clockworkmod on boatloader recovery.
sherwinator said:
I got my HOX about 2 weeks now. I really want to flash it with a custom Rom. Tried lots of rooting instructions with no success. Phone is now back to factory reset using RRU method. I got the bootloader unlock. No success loading Clockworkmod on boatloader recovery.
Click to expand...
Click to collapse
I have the same issue but it says my phone says it is tapered. I want to go back to stock at least. What instructions did you follow for that?
ironnik said:
I have the same issue but it says my phone says it is tapered. I want to go back to stock at least. What instructions did you follow for that?
Click to expand...
Click to collapse
not sure how to remove the "tampered" status but i got it back to stock using RRU method and load a stock Rogers Rom. you need to re-lock it before using RRU. my status now is Tampered and Relock.
sherwinator said:
not sure how to remove the "tampered" status but i got it back to stock using RRU method and load a stock Rogers Rom. you need to re-lock it before using RRU. my status now is Tampered and Relock.
Click to expand...
Click to collapse
Did you use the 1.94 RUU or did you try to Flash the 1.73 original?
You must root on 1.85. Scripts don't work on any other version.
XNine said:
You must root on 1.85. Scripts don't work on any other version.
Click to expand...
Click to collapse
Can I just use RRU to go back to 1.85? Please attach a link.
Thanks
ericth18 said:
Best way to root at this moment would be to unlock your bootloader using HTCDEV and flash TWRP recovery and then flash CleanRom 4.5 which will give you root as long as you kepp that rom on your phone. There could be other roms out there that will give you root access but I've flashed a few and CleanRom 4.5 was the only one that got me rooted. Until they come up with a way to perm root on 1.94 I suggest using this method.
Click to expand...
Click to collapse
If your bootloader is unlocked, you can root with any ROM.
If you unlock and flash a recovery-
fastboot flash recovery nameofrecovery.img
and you cant get it to boot the custom recovery heres the trick, after you flash the recovery type
fastboot boot nameofrecovery.img
Butters619 said:
If your bootloader is unlocked, you can root with any ROM.
Click to expand...
Click to collapse
If this is true, then why can't anyone root their 2.2x phones?
thechilipepper said:
If this is true, then why can't anyone root their 2.2x phones?
Click to expand...
Click to collapse
Cuz att doesn't let us bl unlock our phone HTC dev blocks our cid
Whyyyy is this in general? Please keep all question/help threads in the Q&A section only. Thank you.
Thread Moved.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"If you choose not to decide, you still have made a choice"
Sent from my Galaxy Note (i717), using XDA Premium.
Hey all. Im currently running 1.85 and im trying to update. I downloaded the 2.20 RUU from HTC, as well as the latest Sync Manager and Drivers. I put the phone in Fastboot USB and go to run the RUU. It starts to update but then randomly fails and I have to recover each time. Any idears?
if your bootloader was unlocked did you run "fastboot oem lock"
DvineLord said:
if your bootloader was unlocked did you run "fastboot oem lock"
Click to expand...
Click to collapse
Yes it is and no I didn't. What is it?
its the only way you will be able to ruu. so run the command then run the ruu.
DvineLord said:
its the only way you will be able to ruu. so run the command then run the ruu.
Click to expand...
Click to collapse
I'm not familiar with how to do that. Is there a tutorial?
fastboot oem lock
run the ruu exe
???
profit
synn21588 said:
I'm not familiar with how to do that. Is there a tutorial?
Click to expand...
Click to collapse
all the resources available to the hox are here http://forum.xda-developers.com/showthread.php?t=1671237
Why on earth would you want to run the 2.20 RUU? It will update the hboot, which plugs the hole by which kernels can be flashed from the recovery. You will need to push the boot.img separately via fastboot every time you flash a ROM (or other alternate methods).
If you just want the stock 2.20 firmware, install the stock pre-rooted 2.20 ROM avaiable from Development. Or a more updated on, since there are stock pre-rooted ROMs available up to 2.42 now. If you want the newer radios, those are posted in Development as well.
redpoint73 said:
Why on earth would you want to run the 2.20 RUU? It will update the hboot, which plugs the hole by which kernels can be flashed from the recovery. You will need to push the boot.img separately via fastboot every time you flash a ROM (or other alternate methods).
If you just want the stock 2.20 firmware, install the stock pre-rooted 2.20 ROM avaiable from Development. Or a more updated on, since there are stock pre-rooted ROMs available up to 2.42 now. If you want the newer radios, those are posted in Development as well.
Click to expand...
Click to collapse
So I can just flash the latest ROMs without updating to the latest firmware? I already unlocked my boot loader and have TWRP installed
synn21588 said:
So I can just flash the latest ROMs without updating to the latest firmware? I already unlocked my boot loader and have TWRP installed
Click to expand...
Click to collapse
Yes. Flash away.
redpoint73 said:
Yes. Flash away.
Click to expand...
Click to collapse
Sweet. Thanks
Help please. I am running Htc one x 2.20 rooted. I Installed a back up of the factory rom of 2.2.0 and relocked the device to use RUU to get it back to stock and i Followed the Program instructions, but it fails and I don't know if it is because I am running the same version or what I need to get it back to stock. I ended up making it say security warning but when i booted back in to the bootloader the security warning is gone.
You run the ruu in fastboot after running "fastboot oem lock"
DvineLord said:
You run the ruu in fastboot after running "fastboot oem lock"
Click to expand...
Click to collapse
Thanks a lot. Also Think fire wall and anti virus program may have had problems as I just thought of that this morning.
ok i need help,i install PA over stock rom on 2.2 firmare,before flashing i maked a nandroid backup,i wanted to sell the phone and wanted to back to stock rom,BUT im stuck at boot loop htc screen because while i flash Pa i flash a PA boot img so i cant boot now stock rom,what is to best advice to back to any rom,can i flash somehow flash boot image of stock rom and where can find that boot img,or something else i can do,when i get into twrp recovery i cant do factory reset its failed and i dont have gapps and PA rom on my sd card that files are no more on my sd card i dont know why,so i cant flash PA anymore,need any help asap
if you are selling it reboot into bootloader and run "fastboot oem lock" then run the 2.20 ruu
DvineLord said:
if you are selling it reboot into bootloader and run "fastboot oem lock" then run the 2.20 ruu
Click to expand...
Click to collapse
i will try thanks
vigorito said:
i will try thanks
Click to expand...
Click to collapse
i dont have in bootloader oem lock?
vigorito said:
i dont have in bootloader oem lock?
Click to expand...
Click to collapse
i run the ruu 2.2 (i didnt find the fastboot oem lock) and the ruu start updating the rom and sending about 5 mins and i get error 155 unknown error the rom update utillity cannot cupdate your anddorid phone please get the correct rom update utillity and try again,can i just go to recovery again and do a restore again of stock rom ( nandroid stock) and then just flash boot image from stock rom but i dont know where can find boot image from stock rom?
vigorito said:
i run the ruu 2.2 (i didnt find the fastboot oem lock) and the ruu start updating the rom and sending about 5 mins and i get error 155 unknown error the rom update utillity cannot cupdate your anddorid phone please get the correct rom update utillity and try again,can i just go to recovery again and do a restore again of stock rom ( nandroid stock) and then just flash boot image from stock rom but i dont know where can find boot image from stock rom?
Click to expand...
Click to collapse
Fastboot oem lock
Type into the fastboot cmd prompt while phone is in fastboot. Then run the ruu
Sent from my One X using xda app-developers app
Myrder said:
Fastboot oem lock
Type into the fastboot cmd prompt while phone is in fastboot. Then run the ruu
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
i did it in command promt i get bootloader lock succesfully
then bootloader tz htc svc disable ret and some numbers
and then failed (status read failed) too many links and in bootloader i see its relocked and some security warning
im running ruu now will se whats gonna happen
bro...i hit thanks!
I was actually wondering about the issue of having to flash the boot.img if restoring a TWRP backup. I assumed that it would have to be flashed via fastboot, since boot.img is obviously needed but can't be accessed by recovery on the 1.14 hboot. But haven't seen that discussed or confirmed here. Doesn't actually apply to my One X, since I'm on the old hboot. More just wondering academically.
Seems like the OP has taken the route of running the RUU. But if you ever need the boot.img for a stock ROM, many of the stock ROMs are posted in Development. So you can download the right one, and pull boot.img from it.
Yes you need to flash boot.img when restoring a backup on hboot 1.14.
Sent from my HTC One XL using xda app-developers app
Thanks for the tips guys, I also used this just now to unroot my phone and return it to bone-stock. I used the All-in-one tool to relock the bootloader and got the same error message that OP got, but after rebooting into the bootloader it said Re-Locked. Then downloaded HTC Sync and the 2.20 RUU and ran it. Took 15 minutes total and my phone looks stock, unless of course some busybody at AT&T decides to check the bootloader.
I am returning my One X and buying a One X + tomorrow morning.
EDIT: Oh and in case anyone is confused, you DO NOT need to flash boot.img in order to flash the 2.20 RUU.
i heard people say that they flashed the twrp boot backup in fastboot and it worked the same as flashing the boot from rom.zip in the ruu. i prefer the ruu method for going back to stock, just seems more official imo.