Hi,
My HTC U12+ just have a broken screen. I wanted to revert to original by flashing the RUU zip file. May I know if it is necessary to relock the bootloader before flashing the RUU?
Thanks in advance.
No, it's not necessary
MadBastard said:
No, it's not necessary
Click to expand...
Click to collapse
Thanks for replying.
Some people said it is required to ***RELOCKED** the bootloader first and some said no need. So I relock it by FASTBOOT OEM LOCK just for safe.
And I also followed the guide for U11 and it worked.
https://forum.xda-developers.com/htc-u11/how-to/how-to-flash-ruu-zip-to-factory-t3730859
Related
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.
i updated to 2.20 ruu and thank god i already had supercid set to 11111111.but now when i try to unlock bootloader from htcdev,it doesn't stick.please help
saketh91 said:
i updated to 2.20 ruu and thank god i already had supercid set to 11111111.but now when i try to unlock bootloader from htcdev,it doesn't stick.please help
Click to expand...
Click to collapse
very simple to fix. The fact that you got to the "ready to unlock?" screen means the unlock token works.
go into settings on the phone go to power. Turn OFF fastboot.
Power off the phone completely.
Boot to bootloader
send the unlock.bin again
this time it will stick.
saketh91 said:
i updated to 2.20 ruu and thank god i already had supercid set to 11111111.but now when i try to unlock bootloader from htcdev,it doesn't stick.please help
Click to expand...
Click to collapse
Sometimes the phone can get confused about its locked state.
To fix:
-Force reboot the phone. Hold the power button for 10+ seconds until bottom lights flash and then stop.
-Boot in to bootloader
Now force the phone to lock even if you think it is locked already.
-fastboot oem lock
-fastboot flash unlocktoken Unlock_code.bin
Sending "fastboot oem lock" tends to get the phone back on the right track so it doesn't just keep rebooting in to a relocked state.
get into bootloader manually volume down + power.
Wow, so I've been under the impression that if I updated to 2.20 via the RUU that I couldn't do anything. I know my supercid is definitely 11111111. I can still unlock the bootloader if this is the situation? Root wouldn't happen though right?
Ethere said:
Wow, so I've been under the impression that if I updated to 2.20 via the RUU that I couldn't do anything. I know my supercid is definitely 11111111. I can still unlock the bootloader if this is the situation? Root wouldn't happen though right?
Click to expand...
Click to collapse
yes root will happen.
unlock bootloader. Install twrp recovery. Flash the root package found here http://forum.xda-developers.com/showthread.php?t=1673935
Thanks so much gunny. One quick question. I got the bootloader unlocked without a problem. Now, twrp recovery...can I just do that through GooManager, or should I do it another way?
Ethere said:
Thanks so much gunny. One quick question. I got the bootloader unlocked without a problem. Now, twrp recovery...can I just do that through GooManager, or should I do it another way?
Click to expand...
Click to collapse
I think you may have to use fastboot flash recovery recovery.img because of the new limitations of the new HBOOT. It might be only for boot.imgs though
That worked rohan32 Thanks so much to both of you. Now I have an unlocked bootloader and TWRP installed. Going for root now. Thank you thank you thank you! You guys have saved me from wanting another phone!
[EDIT]Rooted as well. Again, thank you both so much!
thanks everyone i solved my problem.dint except quick replies from you guys.
Ethere said:
Wow, so I've been under the impression that if I updated to 2.20 via the RUU that I couldn't do anything. I know my supercid is definitely 11111111. I can still unlock the bootloader if this is the situation? Root wouldn't happen though right?
Click to expand...
Click to collapse
If you stay away from the AT&T cid you will be fine.
In theory things could change but at the moment so long as you have super cid prior to RUU flashing you will be fine.
OK I just got my AT&T HOX today and from what I've read hear there is no way to root it? Since I have 2.20.502.7 710RD but if I use super cid I can flash roms?
Without root you can't get super Cid
Please update the title and add "Resolved"
Sent from my HTC One XL using xda premium
my phone run "villec2-jb-4.1.1-deodexed" i down ruu som and run but it faill 155, phone show hboot orlder?????? ruu is ics
who can help me fixx??? thank!!! so much sorry bad english
daothuan said:
my phone run "villec2-jb-4.1.1-deodexed" i down ruu som and run but it faill 155, phone show hboot orlder?????? ruu is ics
who can help me fixx??? thank!!! so much sorry bad english
Click to expand...
Click to collapse
relock your bootloader before you run the RUU
tivofool said:
relock your bootloader before you run the RUU
Click to expand...
Click to collapse
i did, but it faillll have tips ??????
daothuan said:
i did, but it faillll have tips ??????
Click to expand...
Click to collapse
is there a newer RUU that you can run on your device?
http://forum.xda-developers.com/showthread.php?t=2094414
The only tips that I have are
put back stock recovery on your phone if you have changed it. (you will have to unlock bootloader to do this)
relock bootloader.
OH, and one time even though usb debugging was checked on the phone, I had to uncheck it and check it again before the ruu worked.
Will relocking bootloader automatically restore stock recovery? Cause I am trying to return to stock from S-off back to S-on and I am following this guide but in the HTC One S toolkit, the recovery section doesn't have a stock recovery to flash. I can use some help with this also, I want to see if returning phone to stock will fix signal drop issues and if not I will have to return it on insurance. My biggest problems are I do not have an RUU from my carrier so could use some advice as to which one to use? here is the link for RUU's but there isn't one for Cincinnati Bell wireless.
You need S-OFF
Sent from my Nexus 7 using Tapatalk HD
Anybody can help me find ROM 3.32.708.12. ? My phone is breaked and it is so important.
Thank for your help
marco1962 said:
Anybody can help me find ROM 3.32.708.12. ? My phone is breaked and it is so important.
Thank for your help
Click to expand...
Click to collapse
Do you mean stoc ROM? We need your CID to get it. to find it boot to bootloader and use the following fastboot command:
fastboot getvar cid
If you are unlocked and just want a ROM to flash, all ICS and JB ROMs are compatible.
astar26 said:
Do you mean stoc ROM? We need your CID to get it. to find it boot to bootloader and use the following fastboot command:
fastboot getvar cid
If you are unlocked and just want a ROM to flash, all ICS and JB ROMs are compatible.
Click to expand...
Click to collapse
RUU official ROM, with CID HTC_622
marco1962 said:
RUU official ROM, with CID HTC_622
Click to expand...
Click to collapse
Couldn't find exact ROM for you, but try this:
http://www.androidruu.com/getdownlo...0U_11.24A.3504.31_M_release_266490_signed.exe
astar26 said:
Couldn't find exact ROM for you, but try this:
http://www.androidruu.com/getdownlo...0U_11.24A.3504.31_M_release_266490_signed.exe
Click to expand...
Click to collapse
Dear Astra, so thanks for your help. But again I received ERROR [131]: ....
This is my boot loader screenshot. Hope this will help to solve my problem.
marco1962 said:
Dear Astra, so thanks for your help. But again I received ERROR [131]: ....
This is my boot loader screenshot. Hope this will help to solve my problem.
Click to expand...
Click to collapse
It seems that you re-locked your bootloader. Can you try to unlock it? it may help restore your phone without using an RUU. Use th following command:
fastboot oem unlock
Edit: also, how did you get to this situation? It might help solving it.
astar26 said:
It seems that you re-locked your bootloader. Can you try to unlock it? it may help restore your phone without using an RUU. Use th following command:
fastboot oem unlock
Edit: also, how did you get to this situation? It might help solving it.
Click to expand...
Click to collapse
The attached is result of command fastboot oem lock
and how was this this.
i was using Cygen ROM 4.2.2 for several months. one day stoped on boot screen. I tried to install ROM again but can not.
Final i tried to lock and use from official RUU, but all type of RUU give the erroe 131.
this is my story
To unlock ur bootloader again u will need to use the Unlock token again from htc dev.
jmcclue said:
To unlock ur bootloader again u will need to use the Unlock token again from htc dev.
Click to expand...
Click to collapse
now again Unlocked phone, even wrote CWM and installed stock ROM.
But after reboot stop on HTC logo, and don't do anything more.
i am going to became crazy.
marco1962 said:
now again Unlocked phone, even wrote CWM and installed stock ROM.
But after reboot stop on HTC logo, and don't do anything more.
i am going to became crazy.
Click to expand...
Click to collapse
Because you are on S-ON you need to flash the boot.img of the Rom via fastboot command or
flash 4ext recovery
Enable smartflash from it
Flash the Rom
Sent from my HTC Sensation Z710e using xda premium
HTC A9 s-off. after flashing RUU.exe software still modified and bootloader unlocked. WHY?????
UAALEX said:
HTC A9 s-off. after flashing RUU.exe software still modified and bootloader unlocked. WHY?????
Click to expand...
Click to collapse
RUU doesn't regain s-on and it doesn't relock bootloader. To relock bootloader you should be running a command in fastboot that's similar to
Code:
fastboot oem relock
EVOuser94 said:
RUU doesn't regain s-on and it doesn't relock bootloader. To relock bootloader you should be running a command in fastboot that's similar to
Code:
fastboot oem relock
Click to expand...
Click to collapse
but RUU.exe must set software to official, or not?
UAALEX said:
but RUU.exe must set software to official, or not?
Click to expand...
Click to collapse
To ruu you need to relock bootloader only if you are s-on, if you're s-off you don't need to worry about that.
Ruu also might not set it to official, because you would have a modified boot.img, though correct me if I'm wrong.