so heres the story i bricked my one x and had to relock the bootloader and ruu back to 1.73 so currently my bootloader is tampereed relocked and im on 1.73
what do i have to do to get recovery back and get back to flashing roms from this step
also the reason it got bricked was becasue cwm delted all my data
so other recoveries might be a better option
can someone please tell me what i have to do from here to unlock again i already have all the files installed cause i unlocked the bootloader before
thanks
nman123 said:
so heres the story i bricked my one x and had to relock the bootloader and ruu back to 1.73 so currently my bootloader is tampereed relocked and im on 1.73
what do i have to do to get recovery back and get back to flashing roms from this step
also the reason it got bricked was becasue cwm delted all my data
so other recoveries might be a better option
can someone please tell me what i have to do from here to unlock again i already have all the files installed cause i unlocked the bootloader before
thanks
Click to expand...
Click to collapse
1. unlock the bootloader using 'fastboot flash unlocktoken <UNLOCK FILE>'
2. flash TWRP via fastboot
nman123 said:
so heres the story i bricked my one x and had to relock the bootloader and ruu back to 1.73 so currently my bootloader is tampereed relocked and im on 1.73
what do i have to do to get recovery back and get back to flashing roms from this step
also the reason it got bricked was becasue cwm delted all my data
so other recoveries might be a better option
can someone please tell me what i have to do from here to unlock again i already have all the files installed cause i unlocked the bootloader before
thanks
Click to expand...
Click to collapse
Use the same token., here is a thread http://forum.xda-developers.com/showthread.php?t=1675312. Or you can run fastboot flash unlocktoken Unlock_code.bin
Related
My Desire S was unlocked but still S-ON.
I want to change back to stock ROM and stock recovery.
I've try
- RUU_Saga_hTC_Asia_WWE_1.48.707.1_Radio_20.28I.30.085AU_3805.06.02.03_M_release_199476_signed
- RUU_Saga_HTC_Thailand_1.35.1113.2_Radio_20.28d.30.0805U_3805.04.02.01_M_release_183327_signed
but it doesn't work.
What method should I use to restore my phone without rooting (hboot 2.00.002).
Thank you.
P.S. Sorry for poor English.
You need to relock your bootloader before installing RUU.
Code:
fastboot oem lock
chninkel said:
You need to relock your bootloader before installing RUU.
Code:
fastboot oem lock
Click to expand...
Click to collapse
It's working but still got an error [140] bootloader version error (different from the first error before relocked).
I bought in Thailand so I think I should use this one
RUU_Saga_HTC_Thailand_1.35.1113.2_Radio_20.28d.30.0805U_3805.04.02.01_M_release_183327_signed
It has only one version of Thailand's RUU.
What should I do now?
Goldcard
Sent from my HTC Desire S
I have hboot 1.18, with bootloader unlocked using HTC Dev, and I'm running ARHD with stock kernel.
Revolutionary gives me the zerg root error, so I used HTC Dev method. But now I'm unable to use the tacoroot method because my bootloader is unlocked. I tried relocking the bootloader, but that gives me a security warning and I can't boot my phone normally without unlocking it again.
Can someone please tell me how to upgrade to ICS now?
I'm a noob and I don't want to experiment too much and brick my phone.
crimsonedge03 said:
I have hboot 1.18, with bootloader unlocked using HTC Dev, and I'm running ARHD with stock kernel.
Revolutionary gives me the zerg root error, so I used HTC Dev method. But now I'm unable to use the tacoroot method because my bootloader is unlocked. I tried relocking the bootloader, but that gives me a security warning and I can't boot my phone normally without unlocking it again.
Can someone please tell me how to upgrade to ICS now?
I'm a noob and I don't want to experiment too much and brick my phone.
Click to expand...
Click to collapse
hmm by relocking you mean fastboot oem lock ?
that should not give security warning...
also before trying tacoroot ...you should flash stock recovery first...any GB stock recovery would do...(fastboot flash recovery recovery.img)
I had a NANDROID backup which I made just after unlocking the bootloader and rooting my phone. I restored that backup before relocking (fastboot oem lock) but it gave me the security warning.
Also, what if I relock the bootloader and then run a BG RUU? Would that work?
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.
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.
Hi everyone,
I want to root my "One X 3.18 AT&T cws_001" to flash my boot.img because i have a reboot/crash problem. However, to root the device the bootloader must be unlocked, and to unlock the Bootloader it must be rooted Anyone have an idea of how i can resolve this ? Thanks.
darkdean said:
Hi everyone,
I want to root my "One X 3.18 AT&T cws_001" to flash my boot.img because i have a reboot/crash problem. However, to root the device the bootloader must be unlocked, and to unlock the Bootloader it must be rooted Anyone have an idea of how i can resolve this ? Thanks.
Click to expand...
Click to collapse
If your phone is not rooted flashing boot.img doesn't apply to you. If it's completely stock do factory reset in bootloader. If that doesn't work, download and run the 3.18 AT&T RUU EXE file not ZIP file and run it with your phone plugged in.
exad said:
If your phone is not rooted flashing boot.img doesn't apply to you. If it's completely stock do factory reset in bootloader. If that doesn't work, download and run the 3.18 AT&T RUU EXE file not ZIP file and run it with your phone plugged in.
Click to expand...
Click to collapse
I did this but the problem is still here, how can i root it with a locked bootloader please ? or how can i unlock the bootloader whithout root ?
darkdean said:
I did this but the problem is still here, how can i root it with a locked bootloader please ? or how can i unlock the bootloader whithout root ?
Click to expand...
Click to collapse
Rooting will not fix your issue if running the RUU does not. RUU is the software fix for rooted and none rooted phones. So if an RUU does not fix it. It's a hardware issue.
Your phone needs to be operational to root/unlock.