Database Info

Quick Qestion About Relocking The Bootloader

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.

[Q] Need info about bootloader mode and other stuff

Hi im new to htc and bootloader and all this stuff.
when i had galaxy s2 i knew everything about it. (download, recovery)
so here is what i need to know:
1.can i create a NAND backup of a stock rom and restore to it if i have s-on?
2.what doe's ***tampered*** in bootloader mode means?
3.when i flash a custom rom and i extract the boot.img do i have to remove it from the zip file itself?
Thanks for any HELP!!!!

LSGio said:
Hi im new to htc and bootloader and all this stuff.
when i had galaxy s2 i knew everything about it. (download, recovery)
so here is what i need to know:
1.can i create a NAND backup of a stock rom and restore to it if i have s-on?
2.what doe's ***tampered*** in bootloader mode means?
3.when i flash a custom rom and i extract the boot.img do i have to remove it from the zip file itself?
Thanks for any HELP!!!!
Click to expand...
Click to collapse
1. No, if you have S-ON you can't create a NAND backup as you don't have a custom recovery.
2. ***TAMPERED*** means that an app or apps have gone into your /system/ partition, thereby triggering the tampered flag. You can remove this message by running a HTC RUU.
3. No, you first flash the zip file with the boot.img inside, then flash the boot.img in the bootloader. fastboot flash boot boot.img

1.i do have a custom recovery which i flashed with all in one kit. (i was able to flash it because i unlocked the bootloader but i dont know what s-off means and also supercid)
so can i do a nand backup of a stock rom and restore to it?
and i also wanted to know how to s-off and what are the differences between s-off and supercid?

LSGio said:
1.i do have a custom recovery which i flashed with all in one kit. (i was able to flash it because i unlocked the bootloader but i dont know what s-off means and also supercid)
so can i do a nand backup of a stock rom and restore to it?
and i also wanted to know how to s-off and what are the differences between s-off and supercid?
Click to expand...
Click to collapse
Then yes you can make a backup and restore later. Just always full wipe, cache and dalvik cache wipe.
As far as flashing kernels/boot.img, if you are < hboot 1.13 then just flash via recovery. If your hboot is > or = to hboot 1.13tjen flash via fastboot or flash img GUI (available in the play store and in various threads).
And as of right now there is no s-off for the one s.
Sent from a baked One S
If I've helped hit the thanks button

LSGio said:
1.i do have a custom recovery which i flashed with all in one kit. (i was able to flash it because i unlocked the bootloader but i dont know what s-off means and also supercid)
so can i do a nand backup of a stock rom and restore to it?
and i also wanted to know how to s-off and what are the differences between s-off and supercid?
Click to expand...
Click to collapse
S-Off means you have full access to all firmware partitions of the phone (I think, correct me if Im wrong). You can unlock the boot loader to gain access to the relevant partitions to flash a custom ROM even with S-ON.
The phone CID just represents the region it is from. For example HTC_TMOUS is for the One S used on the US T-Mobile network. When the phone checks for updates, it only downloads the one's relevant to the CID. SuperCID is 111111111 and represents the "developer" region you can download or run any update on a One S with super CID.

KACE321 said:
S-Off means you have full access to all firmware partitions of the phone (I think, correct me if Im wrong). You can unlock the boot loader to gain access to the relevant partitions to flash a custom ROM even with S-ON.
The phone CID just represents the region it is from. For example HTC_TMOUS is for the One S used on the US T-Mobile network. When the phone checks for updates, it only downloads the one's relevant to the CID. SuperCID is 111111111 and represents the "developer" region you can download or run any update on a One S with super CID.
Click to expand...
Click to collapse
Is that means that if i have supercid i can run any ruu?
if this is the meaning so how do i supercid my one s?

LSGio said:
Is that means that if i have supercid i can run any ruu?
if this is the meaning so how do i supercid my one s?
Click to expand...
Click to collapse
fastboot oem writecid 11111111

usaff22 said:
fastboot oem writecid 11111111
i have 2 questions:
1.how many 1's do i have to write
2.can i get back to my cid and how?
Click to expand...
Click to collapse

Yes, you can make nand backups and restore them if you have a custom recovery. You don't need to have s-off for that but you do need to have your bootloader unlocked. Depending on your hboot version, restoring a nand backup will not restore your boot image. (1.09 and below will, 1.13 and up won't.) We do now have the means to downgrade hboot tho.
You get the *tampered* line if your recovery is unsigned. When you use a custom rom, you will most likely also get a red warning text over your boot splash. It's normal.
You have to extract the boot image from the rom zip and flash it in fastboot before you boot the new rom. This may even be before you flash the new rom. You can leave the rom zip unchanged and flash it in recovery.
-Jobo

if ill do a nand it will back up the boot img but wont restore it because of my hboot version?
Oh and one more thing when i rooted my htc with the supersu zip than after 2 days it asked for mksh premissions and than when i rebootedy phone it was stuck in recovery and then i fixed it with a wipe but how can i prevent this from hapenning and why does it hapenned?
Sent from my HTC One S using xda app-developers app

LSGio said:
if ill do a nand it will back up the boot img but wont restore it because of my hboot version?
Click to expand...
Click to collapse
Correct. On old hboots, pretty much everything except sbl and hboot is writable in recovery or even while fully booted. On newer hboots, most is read-only. Boot image can be flashed in fastboot but radio and other stuff can not.
LSGio said:
Oh and one more thing when i rooted my htc with the supersu zip than after 2 days it asked for mksh premissions and than when i rebootedy phone it was stuck in recovery and then i fixed it with a wipe but how can i prevent this from hapenning and why does it hapenned?
Click to expand...
Click to collapse
The mksh root request is a known thing. You can search the forums for it to read some opinions. As far as I know not yet properly explained why it happens but harmless. It is not related to getting stuck in recovery, altho I have no idea what caused that for you.

touch of jobo said:
Correct. On old hboots, pretty much everything except sbl and hboot is writable in recovery or even while fully booted. On newer hboots, most is read-only. Boot image can be flashed in fastboot but radio and other stuff can not.
The mksh root request is a known thing. You can search the forums for it to read some opinions. As far as I know not yet properly explained why it happens but harmless. It is not related to getting stuck in recovery, altho I have no idea what caused that for you.
Click to expand...
Click to collapse
can you please tell me how can i download an ruu that matches my stock rom. cause when i get to the filefactory server it tells me that i need to buy premium because the file is larger than 500MB.
and the link to the ruu downloads is from this thread:
http://forum.xda-developers.com/showthread.php?t=1543588
if youll go to the first page and click the (ville S4) link you will see a list of ruu's but i can't download them because the size of them is larger han 500mb and i need premium.

back to stock firmware onex at&t

As the title says. I just bought a hox at&t version and did a root metod and it failed. The phone is still save and I can normally use it. Now I want to re-flash the stock firmware that the phone was runing the first time I used it. I am scared with the fact about I wouldn't update to Jelly Bean beacuse it might contains any corrupt file due the failed root.
Is there a detailed how to'' guide? I only see guys in here says about flash RUU.
please help!

If you are going to give up that easily, than maybe root is not for you.
What firmware number (1.85, 2.20, etc.) is the phone now? What root method did you try? Root method varies by firmware version, so its a common mistake to use the wrong one. Also, even with the correct method, you may need multiple attempts before its successful (not necessarily due to anything you are doing wrong).
If you truly want to return to stock, just find the RUU for your version number. Download to your computer. Connect the phone via USB. Then just run the RUU. Its an .exe, no guide needed.
Links to the RUUs are on my Index thread: http://forum.xda-developers.com/showthread.php?t=1671237

thanks for the reply!! now I'm downloading the RUU, but if I do Root and want to come back stock again, only flash the correct RUU file? What about bootloaders (relock)? and kernel?

jics91 said:
thanks for the reply!! now I'm downloading the RUU, but if I do Root and want to come back stock again, only flash the correct RUU file? What about bootloaders (relock)? and kernel?
Click to expand...
Click to collapse
all you need to do is "fastboot oem lock" and run the ruu at the fastboot screen.

jics91 said:
but if I do Root and want to come back stock again, only flash the correct RUU file? What about bootloaders (relock)? and kernel?
Click to expand...
Click to collapse
RUU flashes everything: Stock recovery, radio, kernel, and I believe hboot. It will also wipe the phone, so backup anything you want to keep. As DvineLord said, your bootloader needs to be locked. Other than that, just run the RUU, and it does the rest.
---------- Post added at 01:56 PM ---------- Previous post was at 01:54 PM ----------
jics91 said:
now I'm downloading the RUU,
Click to expand...
Click to collapse
Make sure you dowload the right RUU for your firmware version. RUU will only run if the RUU is the right CID, and same version number or a later one (older RUU will not run).

[Q] Flashing RUU on s-off?

Didn't find to much related to specifically to what I want to do.
I was tinkering with my software and messed something up and won't boot.
I can seem to find a strict stock rooted rom from t-mobile
Can I do the following without messing up my phone?
I already have s-off and twrp and a none working rom.
I want to relock bootloader, flash ruu
unlock again and flash recovery and root file.
I think this should work without messing up the phone and I should still have s-off right?

M9x3mos said:
Didn't find to much related to specifically to what I want to do.
I was tinkering with my software and messed something up and won't boot.
I can seem to find a strict stock rooted rom from t-mobile
Can I do the following without messing up my phone?
I already have s-off and twrp and a none working rom.
I want to relock bootloader, flash ruu
unlock again and flash recovery and root file.
I think this should work without messing up the phone and I should still have s-off right?
Click to expand...
Click to collapse
I've ran an RUU a couple times and still had S-off when it was done. It should not impact that at all.

Or you can skip all that and just flash the t mobile ROM in the dev section.
But, yeah, you will keep soff through the ruu
HTC_One_S | S-OFF | ViperOneS_2.2.0 | Black&Blue_Inverted_Sense | Bulletproof_1.4
Inverted Sense _4+_and_5_click me

No need to relock bootloader if s-off. You should flash stock recovery so and use a CID according to your RUU file.

Stock recovery not needed.
Just ruu away
Verstuurd van mijn HTC One S met Tapatalk

Oooh
I also thought too you needed to re lock to flash a ruu.
I guess that is only if not s off then.
Just need to match cid though still.

SCID will work with any RUU. But you shouldn't use it if you insist to upgrade by OTA... Some people reported a brick this way.

Updating EU RUU from 2.31.401.5 to 3.16.401.8 (going from a CM10.1 version)
Well here is what I've done if it can help some. No warranty that it'll work for everyone, but let's go:
First thing : I've started with CM10.1, S-OFF, SuperCID (11111111) and TWRP 2.5.0.0
I DID NOT relock the bootloader and NOT put back the original Recovery
1) I've put back my original CID (EU Bouygues eg. HTC__203. You should put your original one). Fortunately, I had the original mmcblk0p4 file backup (just copy back the original file to /dev/block. See here : http://forum.xda-developers.com/showthread.php?p=26516911#post26516911).
2) once my original CID has been put back (still S-OFF and TWRP and not relock), I've started in bootloader mode the RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5 and let things run
3) after the installation and reboot, I went to Parameters/Update/Check to force the JB update 3.16.401.8 download.
4) I've let the JB update to be performed (several reboot): all went fine. Going into fastboot, I'm still Unlocked / S-OFF / HTC__203 (original) / Radio 1.11.50 and HBOOT 2.15.000. Sounds good !
5) I went back into fastboot to re-flash the TWRP 2.5.0.0 (fastboot flash recovery openrecovery-twrp-2.5.0.0-ville.img)
6) I then reboot into Recovery : now TWRP is back ! In TWRP, try to reboot into bootloader. TWRP will warn you that you're not ROOT and suggest to install root on your phone. Hit YES.
7) Reboot normally your phone : you should have now a Super SU Installer icon in your apps. Open it, choose install via TWRP, and you're good to go! You've now the latest HTC JB sense version with root.
Optional :
-You can perform a full TWRP backup (with Sense/original CID) in case of further HTC update (?)
-You can put back your SuperCID if wanted
Now if you want to test the CM10.1-3.4 kernel here http://forum.xda-developers.com/showthread.php?t=2302248, it's booting fine (after full wipe)
Voilà !
Hope this helps

yeah
with the tmo model I can get the JB ruu right from HTC
I have just been having issues that I want to get stock and maybe root.
Will double check CID and just flash then.
I think hboot and radio on jb equivlent already but will try that.
Thank you

I wanted to post a little warning here, and relate what happened with my RUU update. First, I'm unlocked, s-off, Hboot 1.13.0000, superCID (11111111), running TWRP 2.5.0.0.
So I read somewhere that the latest RUU may not install correctly if on an older Hboot so I fastboot flashed the latest 2.15, no problems. Then I found a decrypted ROM that Hasoon2000 had posted thinking that this would give me the firmware I wanted, I believe this was based off of RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1. 11.50.05.28_10.27.50.08L_release. I then Fastboot flashed: (I didn't relocking bootloader or changing CID but I did first flash stock recovery because I wasn't sure it I needed to or not)
1. fastboot erase cache
3. fastboot oem rebootRUU
4. fastboot flash zip "name of ROM".zip
The script ran and everything flashed successfully, so I reflashed TWRP 2.3.3.0 and the phone booted just like stock ROM. At this point I checked the Hboot and it was 2.04 something! with a 1.11?? radio. (So this told me I likely wouldn't have needed to first flash the 2.15 Hboot not sure about this tho) I then tried to restore my backed up SDcard and here is where I ran into problems. My SDcard/internal storage only had 48.6MB of space! Nothing I did would change it I worked with this for several hours last night before giving up and this morning I thought to try running a different Tmobile RUU. Found this thread http://forum.xda-developers.com/showthread.php?t=2250573 and downloaded this Firmware package: http://www.filedropper.com/firmware_1 and ran the same fastboot commands (changed recovery back to stock which I probably wouldn't have needed to do...??) and everything flashed perfectly (I needed to run the "fastboot flash zip firmware.zip" the second time, which is normal). I now have my SDcard back with Hboot 2.15, radio 1.13, superCID and s-off yet, "hopefully" am ready to flash the new 3.4 updated stuff!
I suspect the reason for my problems lay in my flashing a euro ROM/RUU, but I really don't know that for sure. This is just what happened to me. Hope this helps a bit!

i believe i have an issue that is too challenging for me. i flashed the lates trickdroid and for some reason i couldnt get my radio to show. my baseband version was unknown. i tried to flash a new radio tto no avail. finally i flashed the jb ruu and now the rom will work for a couple of minutes and then reboot still with unknow baseband radio version. im s off with super cid. any thing to help woul be appreciated.

Did you run the ruu exe or how did you flash it?
Sent from my HTC VLE_U using xda premium

Clom801 said:
i believe i have an issue that is too challenging for me. i flashed the lates trickdroid and for some reason i couldnt get my radio to show. my baseband version was unknown. i tried to flash a new radio tto no avail. finally i flashed the jb ruu and now the rom will work for a couple of minutes and then reboot still with unknow baseband radio version. im s off with super cid. any thing to help woul be appreciated.
Click to expand...
Click to collapse
Have you tried the fastboot flash zip firmware.zip method? It's working great at updating firmware for all the AOSP ROMs.

TheArtiszan said:
Did you run the ruu exe or how did you flash it?
Sent from my HTC VLE_U using xda premium
Click to expand...
Click to collapse
i ran the RUU. i tried the TMOUS ICS and EU JB
---------- Post added at 06:58 PM ---------- Previous post was at 06:57 PM ----------
el_smurfo said:
Have you tried the fastboot flash zip firmware.zip method? It's working great at updating firmware for all the AOSP ROMs.
Click to expand...
Click to collapse
is that the new method posten in the development section? i will try
ok, tried it and it didnt work. still shows no signal with an x ans reboots after a couple minutes

You can try the tmous jb one.
That might be better as not a downgrade.
Not sure about the eu one but that could be why the ics one is not working.
Sent from my HTC VLE_U using xda premium

Clom801 said:
i ran the RUU. i tried the TMOUS ICS and EU JB
---------- Post added at 06:58 PM ---------- Previous post was at 06:57 PM ----------
is that the new method posten in the development section? i will try
ok, tried it and it didnt work. still shows no signal with an x ans reboots after a couple minutes
Click to expand...
Click to collapse
Interesting thought... Try a cm based ROM. They use a radio in a different system folder. If it still doesn't work, sounds more like a hardware failure.

[Q] Unable to get in to recovery or install CWM or TWRP

I'm trying to update a phone I haven't used for a while with a newer ROM, but I'm not able to get in to recovery to do it. It's already rooted with an old ViperOne ROM on and I thought it already had CWM on., but Flashify is telling me it has the stock recovery. I've tried installing CWM and TWRP via Flashify and Fastboot and they've completed without any errors, but I'm never able to get in to it and it boots as normal. I can't even get in to the stock recovery that's supposedly there.
Does anyone have any idea what the problem might be?
Thanks.

Well try this.
Download Rom Manager
It wil flash the CWM by itself and then reboot into the Recovery. Notice what happens.
---------- Post added at 05:08 PM ---------- Previous post was at 05:07 PM ----------
If Helped Click Thanks...

I've tried that too, still just reboots as normal.

Then it might be a Dead Recovery. Well which device are you using. And maybe Flashing your Device back to stock which would flash back the stock recovery.
Hope This Works ..!
---------- Post added at 05:14 PM ---------- Previous post was at 05:12 PM ----------
Tell me wgich device are you using.

HTC One S S4 running Android 4.0.4 ICS

mrkwtrs said:
HTC One S S4 running Android 4.0.4 ICS
Click to expand...
Click to collapse
As first step you should flash the latest JellyBean RUU which will also upgrade your bootloader to 2.15. If your phone is "S-ON" you will have to relock the bootloader before running the RUU. Once done your phone should be fully working again so you can unlock the bootloader again and flash the latest TWRP recovery.
For getting the matching RUU you need to check your CID. Connect your phone in fastboot mode, open commandline and typ:
fastboot getvar all

LS.xD said:
As first step you should flash the latest JellyBean RUU which will also upgrade your bootloader to 2.15. If your phone is "S-ON" you will have to relock the bootloader before running the RUU. Once done your phone should be fully working again so you can unlock the bootloader again and flash the latest TWRP recovery.
For getting the matching RUU you need to check your CID. Connect your phone in fastboot mode, open commandline and typ:
fastboot getvar all
Click to expand...
Click to collapse
OK, Bootloader relocked, back to S-On, CID reset to O2___001.
Would you agree that the RUU is the 7th one down in this list?

mrkwtrs said:
OK, Bootloader relocked, back to S-On, CID reset to O2___001.
Would you agree that the RUU is the 7th one down in this list?
Click to expand...
Click to collapse
NO! You were S-OFF? That made life easier. Unbranded EU firmware is fine BUT I suppose you cant flash it now, as you reverted the CID...
I said, IF you're S-ON...
Best way is get S-OFF again via rumrunner.us, change CID to HTC__001 and then flash the RUU you mentioned before

LS.xD said:
NO! You were S-OFF? That made life easier. Unbranded EU firmware is fine BUT I suppose you cant flash it now, as you reverted the CID...
I said, IF you're S-ON...
Best way is get S-OFF again via rumrunner.us, change CID to HTC__001 and then flash the RUU you mentioned before
Click to expand...
Click to collapse
Just seen an O2 UK RUU further down the list so I'll try that.

mrkwtrs said:
Just seen an O2 UK RUU further down the list so I'll try that.
Click to expand...
Click to collapse
Ok, give it a try, you should go S-OFF anyway as you need HBOOT 2.15 if you want to use roms newer than ICS.

LS.xD said:
Ok, give it a try, you should go S-OFF anyway as you need HBOOT 2.15 if you want to use roms newer than ICS.
Click to expand...
Click to collapse
Think I'm all sorted. Thanks for your help! :good: