Related
Hi,
I'm very familiar with flashing ROMs on phones and have flashed a fair few in my time. I flashed my sisters Desire S a while ago but recently the phone has stopped detecting the SIM card and subsequently has to go back for warranty.
I've flashed a Stock rom over it - trouble is, I now have the locked HBOOT v 2.00.0002 with S-OFF!
Could someone verify if these steps are correct? I'm not too familiar with the Desire S.
1. Downgrade HBOOT to earlier version - 0.98 i think it is.... or 0.68
2. Turn S-ON
3. Flash RUU Stock ROM
I cannot for the life of me downgrade the HBOOT version - I've tried every method out there!
I am very familiar with working in command line on Windows and Linux so don't be afraid to get technical!
Any help is very much appreciated!
Daft question, but have you tried a different Sim?
Does she still have the box?
Swyped from my Desire S using XDA Premium
Haha I spent hours debugging the sim card issue and finally came to the conclusion it's a hardware fault!
Yes - tried several different sim cards from two different carriers (this household only uses 2 carriers!)
Also tried several different ROMs/Radios - she was happily using MIUI for months then she just told me it stopped detecting her SIM card - she certainly hasn't been playing with ROMs so I know it's nothing she has done.
Update: Box is long gone
I've flashed a Stock rom over it - trouble is, I now have the locked bootloader v 2.00.0002 with S-OFF!
Could someone verify if these steps are correct? I'm not too familiar with the Desire S.
1. Downgrade bootloader to earlier version - 0.98 i think it is.... or 0.68
2. Turn S-ON
3. Flash RUU Stock ROM
Can I skip the first step? I guess not.
What has me confused is that you flashed the 0.98 hboot and you said it was s on, now you ran the RUU, and its s off....
Did you use revolutionary to get s off or was it s off to start with?
The correct steps would be.. (if you use revolutionary)
1. Use fastboot to flash 0.98.2000 over the revolutionary one.
2. Run correct RUU.
Problem you could run into are cid's of the RUU (make a goldcard to avoid error) and two misc version being higher than RUU.
Thanks for the reply. I never said it was S-on, the phone was running a custom MIUI ROM with S-Off, I flashed a stock rom straight over the top of it by running the RUU (pretty sure I shouldn't have done!) now I have stock ROM with S-Off and locked HBOOT v2.00.0002
I cannot remember if I used revolutionary to get s off originally - it was many months ago, more than likely though. I remember the phone came with S-On and I had to make it S-Off.
I just want to get S-On again with stock rom but it's proving impossible!
So just to clarify, it is currently running stock rom with LOCKED HBOOT v2.00.0002 and S-Off.
I've tried manually overwriting the version with miscinfo, I've also tried the zerg method - all to no avail.
I have NEVER heard of a stock hboot that is s-off, only when the phone was s-off to start with (early models), or if you used a clip.
Flashing the RUU would bring the phone back to completely stock. (if it flashed correctly)
foX2delta said:
I have NEVER heard of a stock hboot that is s-off, only when the phone was s-off to start with (early models), or if you used a clip.
Flashing the RUU would bring the phone back to completely stock. (if it flashed correctly)
Click to expand...
Click to collapse
Haha want screenshots? I assure you that's what I've got.
Ran an older RUU which has downgraded my HBOOT to 0.98 or 0.68 (can't remember off top of my head) and am running stock rom, HBOOT says ***locked*** at top and also says S-OFF.
I think I'm getting there now.
.. for now Sensation is rooted (GB, s-off, stock) but I guess s-off will be gone after recovery, so is there a chance to root it again, but this time (after) OTA ICS?
thanks!
S-OFF isn't touched, so you can reflash CWM/4EXT via HBOOT once the update is done. You need to be 100% stock otherwise to get the official update, though
EddyOS said:
S-OFF isn't touched, so you can reflash CWM/4EXT via HBOOT once the update is done. You need to be 100% stock otherwise to get the official update, though
Click to expand...
Click to collapse
.. I see, as I understand s-off wont be gone after recovery (with original RUU) and then I'll run OTA ICS, should I be able to root again when on ICS?
thanks!
I have a couple questions.
I am on the 1.16 hboot with cid111111 and s-off unlocked tampered. twrp and maximus rom.
I finally did super cid and s-off on my one-s. Shortly after I recieved a notification that ota update 3.16.401.8 (612.27 mb) was available.
I was wondering if it would even work if i attempted to update. or would i have to update manually. Or would it brick it.
The main reason i would want to update is because the JB Sense roms just dont seem to run smoothly on my phone.
I was thinking this would update everything so the custom roms run smoother.
And Should i even update my hboot. does it make a difference.
I would usually be against it(ive had to downgrade other phones before).
Never take an OTA if you are on a custom rom with a custom recovery. Especially if you have SuperCID, unless you want a paperweight. If you want that OTA, you need to get you original CID, flash stock recovery, relock bootloader, then flash an RUU for your carrier.
impostle said:
Never take an OTA if you are on a custom rom with a custom recovery. Especially if you have SuperCID, unless you want a paperweight. If you want that OTA, you need to get you original CID, flash stock recovery, relock bootloader, then flash an RUU for your carrier.
Click to expand...
Click to collapse
Ok. ill look into that. sounds easy enough. last time i tried to update, i couldnt because of my cid. now i guess since there is an official t-mob i can do it?
You cant flash an ruu with super cid?
Oh and also, Once i update my hboot am i able to install the older ICS roms like maximus. thats just the most stable one i have found for my particular phone.
One more. Will i be able to restore my cid with s-off
ruu update
i relocked, then changed my cid to HTC__001
I triedto update via ruu exe file. but i got an error 155.
Im not sure how to update via the zip of the ruu. if its possible.
Also cant find any instruction or files for the original recovery.
I will try to install ota. hopefully i dont end up with a new frisbee.
If i were to extract the framwork.zip frim the ruu zip then install it via fastboot. would that give me the latest hboot. then maybe i could install the updates.
myphonesbetter said:
i relocked, then changed my cid to HTC__001
I triedto update via ruu exe file. but i got an error 155.
Im not sure how to update via the zip of the ruu. if its possible.
Also cant find any instruction or files for the original recovery.
I will try to install ota. hopefully i dont end up with a new frisbee.
If i were to extract the framwork.zip frim the ruu zip then install it via fastboot. would that give me the latest hboot. then maybe i could install the updates.
Click to expand...
Click to collapse
If you update your Hboot that kind makes it more difficult to flash custom roms. You should just find a nice custom jellybean rom, there are some good ones out there.
impostle said:
If you update your Hboot that kind makes it more difficult to flash custom roms. You should just find a nice custom jellybean rom, there are some good ones out there.
Click to expand...
Click to collapse
updating your hboot makes no significant difference (its a myth that its more difficult to flash custom roms on a later hboot).
im on latest hboot and can flash all things i want.
and if your device is S-off dont bother to relock your device/reinstall stock recovery. It will get overwritten anyways.
only thing important is to change the cid. you can always install a older hboot if s-off
have you tried the ruu.exe while in fastboot-usb?
real187 said:
updating your hboot makes no significant difference (its a myth that its more difficult to flash custom roms on a later hboot).
im on latest hboot and can flash all things i want.
and if your device is S-off dont bother to relock your device/reinstall stock recovery. It will get overwritten anyways.
only thing important is to change the cid. you can always install a older hboot if s-off
have you tried the ruu.exe while in fastboot-usb?
Click to expand...
Click to collapse
When I said it was more difficult I meant it was more work, having to flash the boot.img separately. If you are on a lower Hboot you don't have to do that. Also if you are going to suggest he do S-Off you should at least give him a warning about some of the issues people have ran into after doing it.
EDIT: Thats what I get for watching too many threads, I miss stuff.
impostle said:
When I said it was more difficult I meant it was more work, having to flash the boot.img separately. If you are on a lower Hboot you don't have to do that. Also if you are going to suggest he do S-Off you should at least give him a warning about some of the issues people have ran into after doing it.
Click to expand...
Click to collapse
he is already S-off. (see first post)
but anyways, if you dont do research before you do something, and it fuks up your device, its still gonna be your own fault.
what issues your talking about?
real187 said:
he is already S-off. (see first post)
but anyways, if you dont do research before you do something, and it fuks up your device, its still gonna be your own fault.
what issues your talking about?
Click to expand...
Click to collapse
I saw a thread about people losing 3g/4g data after an S-Off.
With S-Off you are made in the shade, you can downgrade your Hboot just by running the appropriate RUU. But you have to change your CID back to what is was before you try to flash the RUU.
impostle said:
I saw a thread about people losing 3g/4g data after an S-Off.
With S-Off you are made in the shade, you can downgrade your Hboot just by running the appropriate RUU. But you have to change your CID back to what is was before you try to flash the RUU.
Click to expand...
Click to collapse
I have seen the tread. But im scepitical, because if it really was only because of the s-off more people should have it. Might be hardware related.
Eh you do not have tot change back your Cid to original (if its a branded Cid the ruu still wont run), just a valid HTC Cid.
Verstuurd van mijn One S met Tapatalk
He could flash from recovery or fastboot flash any hboot he wants with s-off. No RUU needed for downgrade or upgrade. That's only needed to go back to stock for warranty purposes.
@myphonesbetter
If you want the red warning text overlay to be gone as well choose any of the files here and flash it within recovery. S-Off needed to do so!
To remove ***Tampered*** as well download hboot 1.140004. You will need to come from a lower hboot version so if you're already on >1.140004 flash one <1.140004 first.
--- edit ---
You can lock/unlock your phone as well by flashing. Read more in [how to] reset your lock status flag. Also it's in the Droid DNA forums it's valid for One S. Remember: You need s-off for this to work.
--- and one more ---
You can change your CID pretty simple on rootet devices. Just enter fastboot mode and type:
'fastboot oem writecid HTC__001'
Reboot bootloader then. You can find a collection of HTC ONE S CID's here
^^^^^Very helpful post. thank you. I wouldve never found that.
When you run the ruu .exe, do you have to be in fastboot or in android? The install app told me just to turn the phone on so i figured it would automatically go into bootloader. but it did nothing at all to my phone and gave me an error 115.
When i tried the ota it tells me that I am runnning an altrered OS and i will have to install it a different way.
Sorry for the easy questions. but i just cant seem to find any threads that say how to. I found the ruu and a zip of the ruu. but not how to install it.
The best sense rom has instructions on flashing a newer hboot. .but i want to install a completely stock rom.
myphonesbetter said:
^^^^^Very helpful post. thank you. I wouldve never found that.
.
Click to expand...
Click to collapse
guess you run out of thanks, no?
Never even noticed the thanks meter. I have more of a direct thank you approach.
I tried to flash the ruu .exe in fastboot. and it actually rebooted into the black htc screen, so i figure thats the way to do it.
Unfortunately I got another error. image error (159) use the correct rom and flash again.
I am attempting to flash 3.16.401.8 onto hboot 1.16 (relocked) i am s-off and i changed my cid to HTC__001 via fastboot.
Is there another way. or can i flash the zip in twrp or cwm? Again i just want an oem jelly bean with the proper hboot and radio and everything that the OTA would change. so i can be up to date before i move on to the JB roms.
Ive tried all of the custom ones, and the wifi cuts in and out. i used the wifi partition fix. and i flashed the latest radio. nothing helped for more than a few hours.
don't know what to say; normally you can flash whatever rom you want without problems;
guess 99% of users here did it.
however I can not understand what do you want to be full stock? warranty problems?
ultimul said:
don't know what to say; normally you can flash whatever rom you want without problems;
guess 99% of users here did it.
however I can not understand what do you want to be full stock? warranty problems?
Click to expand...
Click to collapse
Yah thats usually how it works for me. if it works for 99% of people with one step. ill have to do it manually with 20 steps. I guess its made me learn alot about adb and fastboot. I could never get adb to work untill i upgraded to windows 7 recently. until then i had to exract everything to my sdcard via terminal emulator and then drag it to my computer form the card and modify things. but ive been forced to learn quite a bit.
Its weird. I bought my phone off of craigslist from someone who had no idea how to root. But when i opened it into hboot it said Tampered and locked. with no signs of ever being unlocked. completely stock rom and no red warning text on the splash screen.
The reason i want to be stock it so i know all the correct partitions and everything are set up right. (that part i dont understand yet).
I know that a normal system wipe in twrp or cwm doesnt wipe everything. If i wipe and install the same rom i am using(just to clear it up and start over) it doesnt even wipe the app data. (at least on my phone)
Im thinking that its because i am installing a euro rom with a HTC__001 cid and mine was originally TMUS T-MOB010 .
one thing i noticed also is that windows could not verify either of the ruus i downloaded from shppied roms
How do i flash the ruu.zip that i downloaded? Do i need to rename it update.zip like the older phones? Its been a while.
Ok so i know im pretty much helping myself here but i hate when i come across threads with no conclusion.
I was able to succesfully update with the t-mob 2.35 ruu .exe thats on shipped roms .com so i know its not a problem with my computer.
still on hboot1.14 (thought i was on 1.16).
I changed my cid back to t-mob010.
Im just not sure why i cant update with the htc__001 with the 3.16 update.
Any help would be appreciated.
Ahh, things go on here! Nice! :laugh:
It's not quite clear if the RUU is the right one on this phone as many people report problems... So let's go OTA.
To flash the 3.16 OTA update your hboot needs to be < 2.15, your recovery needs to be the HTC stock one , your device needs to be relocked (not totally shure as mine wasn't at that time and it worked, but please remember that) and you need to have HTC stock system/ and stock data/ (ICS) files on your phone (you'll have to unroot as well, if rootet), as the OTA seems to check if certain files are present before working.
All that is quite a pain in the ass, isn't it?! So do one the following:
- Just make shure your bootloader version is lower 2.15, else flash a lower one.
- Click here and you'll have access to one of my google drive folders.
- Download the 2.31 zip. Unpack and copy these nandroid backup files into the appropriate TWRP folder on your phone, reboot into recovery and restore. Once done, you'll be able to flash the 3.16 OTA update after reboot. Remember to change CID before if you're on 11111111.
- Or download the 3.16 zip, unpack and restore. You'll have stock htc sense JB without the OTA. You don't even need to downgrade your bootloader in case. CID doesn't matter here.
- To root simply download SU_Bbox file and flash in recovery.
Important: With the JB update HTC invented disk write protection by default. This simply means that files deleted within stock sense JB will be back after rebooting the phone, also root was granted and working (still grats to htc for this one!!!). Check out for elemental x kernel at this point, as flar2 is the one offering additional modules for the stock kernel working around this. So you can be on stock JB as close as possible with write protection disabled.
--- edit ---
I nearly forgot: If you're experiencing WiFi troubles afterwards search for flashing wifi partitions.
--- and one more ---
myphonesbetter said:
I was able to succesfully update with the t-mob 2.35 ruu .exe thats on shipped roms .com so i know its not a problem with my computer.
still on hboot1.14 (thought i was on 1.16).
I changed my cid back to t-mob010.
Im just not sure why i cant update with the htc__001 with the 3.16 update.
Click to expand...
Click to collapse
Cause you're on 2.35 US. You need to be on 2.31 EU before, because 3.16 is EU and there is still no JB update to 2.35 US. 3.16 OTA will work with htc__001 (htc worldwide).
The OTA determined my OS was modified.
I could not restore the folder i took directly out of the zip.
There was a folder inside the folder that contained the same files. I was able to flash this.
My hboot is still at 1.14 my cid is not htc--001 relocked. the update was 650 mb of which i could not use wifi for becauese it just said error.
so 650 mb through tmobile. only took a few minutes but used almoast half of my months dl limit.
IDK. i found instructions on how to update the hboot in best sense roms thread. i will try that.
Edit: the restore for 3.16 worked in twrp. shouldve tried that first.
I may still update my hboot. I cant really find any instructions. Apparently the search just finds every thread and lists it.
If you are on the latest TWRP 2.4.3.0 go back to 2.4.1.0 (the latest one seems to have restore problems).
The folder contained in the zip needs to be copied to /TWRP/BACKUPS/HT23whatever/
You should be able to restore then.
--- edit
hehe, ok then.
You can flash any of these hboots from within TWRP. Up or down, it doesn't matter - you're s-off.
---------- Post added at 10:43 AM ---------- Previous post was at 10:32 AM ----------
CID should be HTC__001 not htc--001. Maybe a typo.
Hi, I really f up.
I can't install roms, and I got TMOB-101.
I tried recently flash a new rom. and didn't backed it up.
please someone send me TMOB-101 backup ot RUU.
HELP!
if you've unlocked your hboot, you need to relock it and then you can install a RUU.
http://www.htconeforum.com/forum/ht...unbrick-restore-htc-one-s-stock-relocked.html
Good luck
No ruu for me there
Sent from my HTC One S using Tapatalk 2
Do you have the TMo USA?
No. I've got t-mob101 (t-mobile Germany)
Sent from my HTC One S using Tapatalk 2
try this:
http://androidfiles.org/ruu/?dir=Ville
Tried this already...
No ruu
Sent from my HTC One S using Tapatalk 2
RUU_Ville_U_TMO_DE_1.77.111.5_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_259421_signed.exe
Really not?
It's a early ruu. I need the 3.16 one
Sent from my HTC One S using Tapatalk 2
lol. There isn't one from TMOB_101 and I really doubt that there ever will be one...
If you want to stick to your CID you should flash this one above and check the OTA updates. Things can be soooo easy...
If you want to go for JB you'll have to change CID to HTC__001 and flash the appropriate RUU. 3.16 will come in by OTA update.
Isn't it will brick my device? (flashing a earlier version then I got)
Sent from my HTC One S using Tapatalk 2
No, it will simply not flash (= exit with an error).
Each RUU/OTA update comes with a certain new bootloader version. Dependant on this version you can upgrade to the next higher hboot but usually not downgrade to a lower hboot. E.g. if youre on 2.15 JB you can't downgrade to 1.14 ICS by RUU anymore. But you are still able to flash custom roms based on whatever android version. The only thing here is with bootloaders > 1.09 the kernel needs to be flashed separately in fastboot mode.
That's where s-off / downgrading bootloader comes into game. As downgrading bootloader is a pain, s-off would be the way to go. For warranty purposes you will be able to restore a stock phone (locked, tampered warning removed, s-on). And if your screen is blank, it will also be blank for TMOB, so there is no need to restore stock.
Look here: http://forum.xda-developers.com/showthread.php?t=2200930
There is the "RUU_Ville_U_ICS_40_S_TMO_DE_2.38.111.10_Radio_1.09 es.50.02.07_2_10.09d.50.04L_ver2_release_287723_signed.exe"
(Android 4.04 version)
rootrider said:
No, it will simply not flash (= exit with an error).
Each RUU/OTA update comes with a certain new bootloader version. Dependant on this version you can upgrade to the next higher hboot but usually not downgrade to a lower hboot. E.g. if youre on 2.15 JB you can't downgrade to 1.14 ICS by RUU anymore. But you are still able to flash custom roms based on whatever android version. The only thing here is with bootloaders > 1.09 the kernel needs to be flashed separately in fastboot mode.
That's where s-off / downgrading bootloader comes into game. As downgrading bootloader is a pain, s-off would be the way to go. For warranty purposes you will be able to restore a stock phone (locked, tampered warning removed, s-on). And if your screen is blank, it will also be blank for TMOB, so there is no need to restore stock.
Click to expand...
Click to collapse
I've got the same Problem.
But I can't SuperCID / S-Off my Phone like here: http://forum.xda-developers.com/showthread.php?t=1671396
It just doesn't work!!!
How could I go back to a Stock ROM ??
I have really no idea
TMOB-101 ?
Which bootloader version?
rootrider said:
TMOB-101 ?
Which bootloader version?
Click to expand...
Click to collapse
hboot-2.15.0000
Golden-One said:
I've got the same Problem.
But I can't SuperCID / S-Off my Phone like here: http://forum.xda-developers.com/showthread.php?t=1671396
It just doesn't work!!!
How could I go back to a Stock ROM ??
I have really no idea
Click to expand...
Click to collapse
I can sent you a twrp nandroid backup from my phone (s4-tmobile germany)
I have backups from the 3.16.111.5.and from the latest 3.16.111.7. They are the stock roms with the supersu added.
If you recover the 3.16.111.5 nandroid backup you will take a OTA update to clean 3.16.111.7 (without supersu).
hi
Can you send me the backups too?
thank you so much!
kevin3688 said:
hi
Can you send me the backups too?
thank you so much!
Click to expand...
Click to collapse
You can find it/them here.
It's just plain stock nandroids. No root - nothing.
rootrider said:
You can find it/them here.
It's just plain stock nandroids. No root - nothing.
Click to expand...
Click to collapse
Thanks a lot!
Well the update that hit tmous today have any effect on One S user who are already rooted and using a 4.2.2 Rom?
Sent from my One S using xda app-developers app
mrminor13 said:
Well the update that hit tmous today have any effect on One S user who are already rooted and using a 4.2.2 Rom?
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
No. You must me on the stock rom to get notification. You must then have a locked bootloader and stock recovery to actually run the update.
fbihawk said:
No. You must me on the stock rom to get notification. You must then have a locked bootloader and stock recovery to actually run the update.
Click to expand...
Click to collapse
That's what I thought. I'm excited that I get to see it on my wife's phone.
Sent from my One S using xda app-developers app
fbihawk said:
No. You must me on the stock rom to get notification. You must then have a locked bootloader and stock recovery to actually run the update.
Click to expand...
Click to collapse
Locked bootloader? I have done an update before with an unlocked boot loader. Just curious. Plan to try this afternoon.
Sent from my HTC One S using Tapatalk 2
SoTacMatt said:
Locked bootloader? I have done an update before with an unlocked boot loader. Just curious. Plan to try this afternoon.
Sent from my HTC One S using Tapatalk 2
Click to expand...
Click to collapse
That's been my experience. Try it without if you would like. Can't hurt anything.
i am currently S-off and running viper rom. If I change my cid back to the TMo version and reflash the ruu so I return to stock, would I get the update? DO i need to lock the bootloader and S-ON?
I hav relocked the bootloader bt cn some one provide me stock recovery for cid 044 jelly bean
Sent from my HTC One S using xda app-developers app
Just so you guys know...i dont condone everyone to do this but it worked for me...
Was: SuperCid 111111 , Rooted, and S-Off running latest(before today) Tmo Us rom .
Flashed stock recovery, locked bootloader, ran ota update, unlocked bootloader, flashed twrp, flashed Supersu in said recovery.
Now rooted/supercid/soff on Tmo us jelly bean 4.1.1 ...
aegentirony said:
Just so you guys know...i dont condone everyone to do this but it worked for me...
Was: SuperCid 111111 , Rooted, and S-Off running latest(before today) Tmo Us rom .
Flashed stock recovery, locked bootloader, ran ota update, unlocked bootloader, flashed twrp, flashed Supersu in said recovery.
Now rooted/supercid/soff on Tmo us jelly bean 4.1.1 ...
Click to expand...
Click to collapse
You should not use supercid for an ota there are many reports of bricked phones that way! change your cid to original also stock recovery is a must!
fbihawk said:
That's been my experience. Try it without if you would like. Can't hurt anything.
Click to expand...
Click to collapse
Re-locked bootloader and the RUU is working. Thanks!!!
Have you guys updated your phone yet, and if so were you able to unlock and root again? I just finished restoring the gf's phone back to stock but all her apps were backed up via Titanium and from Viper 2.0, which is JB based. I can't restore her apps and data unless she's on a JB rom, if I remember correctly.
Sent from the other One.
Could someone please point me in the right direction to where I can get my wife's T-MobileUS One S (S4) back to where she can OTA update it to JB? I've been around quite awhile, but am personally a Nexus user and am not very familiar with Sense roms yet. I've done a lot of reading up on it but am getting a little confused. I keep reading about the HBOOT version possibly causing problems? Here is her setup.
Stock 4.0.4/rooted
CWM recovery
CID-T-MOB010
***TAMPERED ***
***UNLOCKED***
VLE PVT SHIP S-ON RL
HBOOT-1.14.0004
RADIO-1.08ts.50.02.16
OpenDSP-v29.1.0.45.0622
eMMC-boot
Aug 14 2012,18:01:48
I'm not sure what ROM my gf was on. First I backed up with Titanium Backup. I flashed the stock recovery with fastboot, locked the bootloader, ran the 2.35 Tmobile RUU (to get her to completely stock), ran the Software Update from the About Menu to get JB, unlocked the bootloader, flashed TWRP recovery with fastboot, and flashed the supersu.zip in TWRP. All is good, I have working root and was able to restore using Titanium. She'll be happy when she wakes up.
Is a locked bootloader necessary?
SoTacMatt said:
Re-locked bootloader and the RUU is working. Thanks!!!
Click to expand...
Click to collapse
Did you try updating without re-locking the bootloader? I was able to update the last time (the security fix they pushed out) without re-locking the bootloader. I'd like to avoid re-locking if possible. I know I need to revert to the stock recovery (that's fine).
--------------
ROM: T-Mobile Stock 4.0.4
HBOOT: 1.14.0005
Recovery: CWM 5.8.3.1
Rooted: Yes
I did try to use the RUU without locking the bootloader. It failed. That is when I did 'fastboot oem lock' and everything else went smoothly!!!
Not necessary to re-lock bootloader for OTA
I can confirm that it is not necessary to re-lock the bootloader to receive the OTA update to JB. I am on Stock TMOUS, rooted and with an unlocked bootloader. I suspect that one needs to re-lock the bootloader only if one is restoring the device to factory settings using an RUU. It certainly isn't required for a successful OTA update.
Here are the steps I followed (assuming you have the android SDK configured and the phone plugged in via USB into a PC):
1. Installed the stock recovery (fastboot flash recovery <name_of_recovery_file.img>)
2. Un-installed Superuser.apk to remove root. ( rm /system/app/Superuser.apk )
3. Rebooted the phone.
4. Checked for system update (Settings - About - Software updates - Check now...)
5. Chose to download the update. It took a while to download even on WiFi.
6. Chose to install the update.
7. Let the phone settle for about 30 minutes. It will not be as responsive during this time.
8. Re-install custom recovery (I use ClockworkMod).
9. Re-install root.
Once the update was complete (step 6 above), I did have a minor issue where the keypad was not showing up for me to enter the PIN to unlock the phone. I rebooted (hold down the Power button for about 10 seconds) and then I was able to get past that just fine.
------------
ROM: T-Mobile US Stock 4.1.1
HBOOT: 2.15.0000
Radio: 1.13.50.05.31
Recovery: CWM 5.8.3.1
Rooted: Yes