Database Info

[Q] Returning to stock [i9020a]

I just wanted to make sure that I understood the process of returning my phone to stock before I make a mistake.
All I've done since I purchased the phone was root it and unlock the bootloader. I have not loaded any custom roms.
So If I understand this correctly I need to:
1) Flash the Stock Image (which should include the stock recovery?)
2) Use fastboot to lock the bootloader
The reason I'm wanting to return the phone to stock is to receive OTA updates. I never use any apps requiring root, and don't plan on loading any custom roms.
I never did find a 2.3.4 stock image for the I9020A..

you should actually be able to get ota updates no problem. it'll just remove root every time you update.
it's probably not a good idea to lock the bootloader though cause if you ever want to unlock it again in the future you'll have to wipe everything from your phone. your best bet is to just flash stock recovery so you can install the update
i'm pretty sure that works, but hopefully someone else can verify just so you don't get some bad information lol

I heard the same thing about OTA updates. If you're phone is rooted and you're using the original rom, you'll get the update but you'll have to root your phone once again.
I haven't tried this myself so I cannot verify it.
It's just the word on the street, you know!

EraqEE said:
I heard the same thing about OTA updates. If you're phone is rooted and you're using the original rom, you'll get the update but you'll have to root your phone once again.
I haven't tried this myself so I cannot verify it.
It's just the word on the street, you know!
Click to expand...
Click to collapse
you need stock everything, so stock kernel, rom, radio, etc... the op should be fine to update if they flash stock recovery though. rooting is simple from there

dmuntean said:
I just wanted to make sure that I understood the process of returning my phone to stock before I make a mistake.
All I've done since I purchased the phone was root it and unlock the bootloader. I have not loaded any custom roms.
So If I understand this correctly I need to:
1) Flash the Stock Image (which should include the stock recovery?)
2) Use fastboot to lock the bootloader
The reason I'm wanting to return the phone to stock is to receive OTA updates. I never use any apps requiring root, and don't plan on loading any custom roms.
I never did find a 2.3.4 stock image for the I9020A..
Click to expand...
Click to collapse
where can i find a method to return a phone thats unlocked and rooted? any help would be appreciated.
Sent from my Inspire 3G.

bdpyo said:
where can i find a method to return a phone thats unlocked and rooted? any help would be appreciated.
Sent from my Inspire 3G.
Click to expand...
Click to collapse
I would like to do the same, I have a Fido/ATT I9020A and I'm having a hard time finding a stock nandroid backup to restore my phone with...
Anyone?>

bump
Sent from my Inspire 3G.

Here is stock 2.3.4 (GRJ22) with UCKD1 Radio & KA3 Bootloader.. http://dl.dropbox.com/u/7812800/Stock-GRJ22-i9020A-unsigned.zip Flash via ClockworkMod Recovery (due to it being unsigned zip)
I extracted and packaged it from my i9020a (and tested it on there).

how do you recomend flashing?
Sent from my Inspire 3G.

bdpyo said:
how do you recomend flashing?
Sent from my Inspire 3G.
Click to expand...
Click to collapse
Sorry forgot to add that to post... since its unsigned you need to flash via ClockworkMod Recovery.

kibmcz said:
Sorry forgot to add that to post... since its unsigned you need to flash via ClockworkMod Recovery.
Click to expand...
Click to collapse
Thanks kibmcz ! I'm a n00b when it comes to this but when you say flash via ClockworkMod you mean get into clockwork recovery mount the usb, transfer the zip onto the SD card and then <<Install from zip>> ?
Is that the method?

davis2k said:
Thanks kibmcz ! I'm a n00b when it comes to this but when you say flash via ClockworkMod you mean get into clockwork recovery mount the usb, transfer the zip onto the SD card and then <<Install from zip>> ?
Is that the method?
Click to expand...
Click to collapse
Yep that method works

kibmcz said:
Yep that method works
Click to expand...
Click to collapse
Thanks again kibmcz, so I just completed the flash, then did a fastbook oem lock.
Seems to be working fine except for one thing...
When I go into settings and hit Sound I get a Force close when I try and select a new ringtone...
Should I try reflashing again?

davis2k said:
Thanks again kibmcz, so I just completed the flash, then did a fastbook oem lock.
Seems to be working fine except for one thing...
When I go into settings and hit Sound I get a Force close when I try and select a new ringtone...
Should I try reflashing again?
Click to expand...
Click to collapse
Didn't happen on mine (In fact im using a self rooted rom based on that exact stock zip) try doing a wipe in stock recovery.

after flashing that does it take it back to out of box condition?
reason i ask is because i bought a already rooted and unlocked one here from market place and i want to return it to stock firmware, radio, kernel and such to recieve OTA updates and what not.
your info is greatly appreciated
Sent from my Inspire 3G.

bdpyo said:
after flashing that does it take it back to out of box condition?
reason i ask is because i bought a already rooted and unlocked one here from market place and i want to return it to stock firmware, radio, kernel and such to recieve OTA updates and what not.
your info is greatly appreciated
Sent from my Inspire 3G.
Click to expand...
Click to collapse
Using my zip yes... it flashes Bootloader, Radio, Boot, System and on first boot (and any other time recovery changes) Recovery is flashed. All you got to to is lock the bootloader and that wipes user data and usb storage.

hey man i appreciate you coming forward with a solution, ive yet to recieve the phone but wanted to prepare.
my goal is to flash everything back to stock and start completly over whereas i have no clue what method was originally used to root and unlock the bootloader.
when the time comes hope you dont mind a PM if i have any extra questions.
Sent from my Inspire 3G.

Just did the method using the stock ROM provided by kibmcz "thanks BTW!"
Phone is back to stock, working like it did when I first bought it. Had a little trouble with some Force Close issues but did a factory reset/data clear of the cache and all that before re-flashing, and it seems to be working Vanilla!

bdpyo said:
hey man i appreciate you coming forward with a solution, ive yet to recieve the phone but wanted to prepare.
my goal is to flash everything back to stock and start completly over whereas i have no clue what method was originally used to root and unlock the bootloader.
when the time comes hope you dont mind a PM if i have any extra questions.
Sent from my Inspire 3G.
Click to expand...
Click to collapse
Great and thanks DM all you want i don't mind. Oh and i now got stock 2.3.6 (GRK39F) uploaded.
Code:
[B][URL="http://dl.dropbox.com/u/7812800/Stock-GRK39F-I9020a-unsigned.zip"][B]Android 2.3.6/GRK39F/UCKF1 Radio/KA3 Bootloader[/B][/URL][/B]
Works on: I9020A
Unofficial, unsigned, must flash through ClockworkMod Recovery. Contains recovery, radio and bootloader.

kibmcz said:
Great and thanks DM all you want i don't mind. Oh and i now got stock 2.3.6 (GRK39F) uploaded.
Code:
[B][URL="http://dl.dropbox.com/u/7812800/Stock-GRK39F-I9020a-unsigned.zip"][B]Android 2.3.6/GRK39F/UCKF1 Radio/KA3 Bootloader[/B][/URL][/B]
Works on: I9020A
Unofficial, unsigned, must flash through ClockworkMod Recovery. Contains recovery, radio and bootloader.
Click to expand...
Click to collapse
So all I have done to my nexus s is root and cwm and kernel. I can do the ota to 2.3.6 or flash your package?
Running build GTJ61 and I9020AUCKE1 2.3.4 stock.
Sent from my Nexus S using xda premium

Gain root access on the latest 1.55.531.3 update, ONLY IF you are S-OFF

I found out that it is possible to gain root access in an 'unrootable' update, IF you are S-OFF, by flashing ClockworkMod thru the bootloader, and then flashing Superuser thru ClockworkMod. I found out that this worked on the G2, as described here by rdmerck:
http://forum.xda-developers.com/showthread.php?t=1206930
So all i did was replace the android_info.txt and the recovery.img in his zip, with the ones for our device. I just tried it, and it worked! i have Superuser access in the new 1.55.531.3 ROM.
INSTRUCTIONS:
Pretty simple...
1. Download the 2 attached files, put them both on the root of your sdcard, and rename the CWM_HBOOT.zip to PG59IMG.zip.
2. Boot into the bootloader however you prefer, let it read the PG59IMG.zip, and press volume up to update when prompted. When it finishes, it will prompt you to press Power to reboot.
3. Now boot into recovery however you prefer, and it should be ClockworkMod(I used the Modaco 4.0.0.9 version, basically because i had it conveniently lying around in .img format. I'm sure Rom Manager could now be used to flash the latest 5.0.2.7 version of CWM). Choose 'install from sdcard', then 'choose zip from sdcard', then choose the Superuser-3.0.7-efgh-signed.zip and choose 'yes'. As has happened in the past, i had to flash it 3 times until it successfully installed. But it did work.
4. Choose to reboot, and enjoy root access on the latest stock ROM!
I figure a lot of people probably won't need all that instruction, but i included it for people who are newer to flashing stuff thru the HBOOT and CWM. I also figure that the user base for this will probably be very small, as most folks who are S-OFF probably are not choosing to run the stock ROM. But anyway, if you DO have S-OFF, i wanted you to know that you can have root access on the latest update. I figure this will also enable us to make nandroid images of the new ROM, if that would help development at all.
Anyway, here are the 2 files:
ClockworkMod: http://dl.dropbox.com/u/18474790/CWM_HBOOT.zip
Superuser: http://dl.dropbox.com/u/18474790/Superuser-3.0.7-efgh-signed.zip
Note:
-This worked for me and should work for you, but use at your own risk.
-You must be S-OFF to do this.
-Hopefully this is only a temporary solution for those with S-OFF, until either Team Revolutionary cracks the update, or HTCDEV fixes whatever is preventing their bootloader unlocker tool from working on our device.

Using HTC Supertools v3 Will Temp(Prep)Root, get S-Off.
Sent from my ICS Splashed using Tapatalk

Litesorrows said:
Using HTC Supertools v3 Will Temp(Prep)Root, get S-Off.
Sent from my ICS Splashed using Tapatalk
Click to expand...
Click to collapse
is that right? is that a new development? and it works on the new update? if so, that's awesome.

yogi2010 said:
is that right? is that a new development? and it works on the new update? if so, that's awesome.
Click to expand...
Click to collapse
HTC Supertools has been out for a while. IDK, I got S-Off and Root on my Brothers DS. I got S-Off first, then ran the root exploit.
Sent from my ICS Splashed using Tapatalk

Great work, Yogi. Worked beautifully!

HebrewToYou said:
Great work, Yogi. Worked beautifully!
Click to expand...
Click to collapse
Awesome. My thanks go to rdmerck for the idea!

Nice bro! I may put this in Mr Root as another way to Root

xmc wildchild22 said:
Nice bro! I may put this in Mr Root as another way to Root
Click to expand...
Click to collapse
Yeah man, sounds good. I mean, perhaps this will be helpful to at least a few people, lol. It's an interesting and very simple idea tho... probably useful mainly on stock HBOOTs where fastboot is blocked, but S-OFF had been attained.

Litesorrows said:
HTC Supertools has been out for a while. IDK, I got S-Off and Root on my Brothers DS. I got S-Off first, then ran the root exploit.
Sent from my ICS Splashed using Tapatalk
Click to expand...
Click to collapse
Will it work on a updated mt4gs which hasnet obtained s off?
sent from my ice cream sandwhich MT4GS

Guess I will give this a shot later today.

how do i upgrade to the latest OTA if i'm already on a rooted stock ROM?

psychedel!k said:
how do i upgrade to the latest OTA if i'm already on a rooted stock ROM?
Click to expand...
Click to collapse
Well, since nobody has made a custom rom with the latest OTA bits, you will have to do what I did:
You'll need to downgrade yourself with the stock PG59IMG.zip, putting that file (found here) on the root of your sdcard and booting into the bootloader.
That will basically return your phone to stock and, IIRC, revert your status to S-OFF Locked. Then you'll need to boot up and check for system updates. You'll definitely be given the first small OTA update, but you very likely wont receive the latest OTA update via system updates.
For that you'll need to download it (from here) and flash it through the stock recovery. Once you've done that you can use the instructions in this thread to re-flash clockworkmod recovery and re-root.
Your phone will still be S-OFF but you'll have a locked bootloader.

Still can't figure out what I need to do to root my phone. That's on hboot 1.45.0013
Guess I might have to wait til Revo find a fix for it.

Hotshot205 said:
Still can't figure out what I need to do to root my phone. That's on hboot 1.45.0013
Guess I might have to wait til Revo find a fix for it.
Click to expand...
Click to collapse
Are you s-off?

No my phone is not
Sent from my myTouch_4G_Slide using Tapatalk

HebrewToYou said:
Your phone will still be S-OFF but you'll have a locked bootloader.
Click to expand...
Click to collapse
so does that mean i won't be able to restore a custom rom image?

psychedel!k said:
so does that mean i won't be able to restore a custom rom image?
Click to expand...
Click to collapse
Since you're S-OFF, you could flash ClockworkMod on the update and then flash a custom ROM, but I believe that would leave you with an old ROM and the new radio, which seems to have caused issues for people. Since there aren't yet any custom ROMs based on the latest update, you should probably stay where you are if you want a custom ROM. But if you do install the update, you would still be able to downgrade and get back to where you are now.

Wonder how long it will/could be before revo crack the current HBOOT
Sent from my myTouch_4G_Slide using Tapatalk

psychedel!k said:
how do i upgrade to the latest OTA if i'm already on a rooted stock ROM?
Click to expand...
Click to collapse
You could run this ROM, which is based on the latest OTA release from HTC, so no OTA updates are needed. It is optimized, deodexed, and tweaked just a tad. I use it as my daily driver with great success. http://rootzwiki.com/topic/12063-devrom12192011-stock-12853110-r2-deodexed-crtgpu/

Fuzi0719 said:
You could run this ROM, which is based on the latest OTA release from HTC, so no OTA updates are needed. It is optimized, deodexed, and tweaked just a tad. I use it as my daily driver with great success. http://rootzwiki.com/topic/12063-devrom12192011-stock-12853110-r2-deodexed-crtgpu/
Click to expand...
Click to collapse
I think possibly we've been thru this before, lol, but that ROM isn't the very latest... there has been a pretty big update since then that thus far is only available as an official OTA update package.

[Q] HTCdev.com Unlock - HBOOT cannot find Recovery Img.

I have tried everything under the sun, but I cannot get this thing to work. My phone will not find any recovery img I put on my SD card. No matter how new or old it may be. It is really frustrating. Can anyone help?

You're doing it wrong.
Take the recovery.img off your SD card and put it on your desktop. Then use fastboot to flash the recovery image.

Wait how do I use fastboot? I used a Mac to unlock my phone using htvdev.com's method.

My intentions are to also root my phone and install the new set Coindroid rom. Can I do that with my current setup? I couldn't use revolutionary because I own a Mac.

If you unlocked, then you know how to use fastboot!
To install the recovery you use
Code:
fastboot flash recovery recovery.img

Rusty! said:
If you unlocked, then you know how to use fastboot!
To install the recovery you use
Code:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
ok well what about install a custom ROM such as coindroid and rooting the phone? Do i follow the same steps every time?

Nope, once you've installed recovery, you just enter that and install the ROM/root files.

Ok which recovery would you recommend? I am mostly used to ClockworkMod, but does the touch interface ClockworkMod work for the Sensation 4g?

Yes it does, that's what I use. You can find it here: www.clockworkmod.com/rommanager

Rusty! said:
Yes it does, that's what I use. You can find it here: www.clockworkmod.com/rommanager
Click to expand...
Click to collapse
Ok.
And the code for that would be:
Code:
fastboot flash recovery (what I just downloaded?)

TO OP: Coindroid is an ICS ROM. All ICS roms require updated "ICS" firmware found in HTC's 3.32 software update. Here's the problem, you CAN'T update your firmware (except for stock TMobile versions) because you didn't s-off. HTC bootloader unlock does not give you s-off and only allows for flashing rom, recovery, and in a round about way kernel. You need to update your hboot and radio by updating firmware, which, as i said, you no longer can do. You are now stuck on gingerbread based ROMs until TMobile releases their version of the ICS update next month. If you flash an ICS ROM you will end up in a bootloop.

Behold_this said:
TO OP: Coindroid is an ICS ROM. All ICS roms require updated firmware. Here's the problem, you CAN'T update your firmware because you didn't s-off. HTC bootloader unlock does not give you s-off and only allows for flashing rom, recovery, and in a round about way kernel. You need to update your hboot and radio by updating firmware, which, as i said, you no longer can. You are now stuck on gingerbread until TMobile releases the ICS update next month. If you flash an ICS ROM you will end up in a bootloop.
Click to expand...
Click to collapse
hrm. Well if I root can I still get the update from T-Mobile? I want to remove the crap off of my phone. And then would it be wise to still install a recovery?

cashman0712 said:
hrm. Well if I root can I still get the update from T-Mobile? I want to remove the crap off of my phone. And then would it be wise to still install a recovery?
Click to expand...
Click to collapse
You would need full stock ROM to successfully install the update via OTA, meaning stock recovery and all system apps present.
**edit** I also added a little more info in my previous post, to give you a clearer understanding of what's happened.

Ok, So I only unlocked the bootloader via htcdev.com. Should I just leave my phone as is until the update then? And did the bootloader unlocker mess up my chances of getting the update?

I honestly don't know how HTC bootloader unlock may or may not effect OTA's, but I will say this, if you don't get the update or if you do and it causes problems with your device, you're on your own. Your warranty has been voided by the HTC unlock method and TMobile will not service the device so you will have to go through HTC which can cost $$$!

Behold_this said:
I honestly don't know how HTC bootloader unlock may or may not effect OTA's, but I will say this, if you don't get the update or if you do and it causes problems with your device, you're on your own. Your warranty has been voided by the HTC unlock method and TMobile will not service the device so you will have to go through HTC which can cost $$$!
Click to expand...
Click to collapse
Won't there be a way to update it even if I don't get updated through T-Mobile?
EDIT: Also couldn't I just relock it just in case?

There probably will be. In your case, your best hope is that the official RUU for the TMobile updated software gets leaked and posted. They usually do. Look for it in this thread. Probably won't be available until sometime after it's official release.

Behold_this said:
There probably will be. In your case, your best hope is that the official RUU for the TMobile updated software gets leaked and posted. They usually do. Look for it in this thread. Probably won't be available until sometime after it's official release.
Click to expand...
Click to collapse
Ok thanks for the help and tips!

Another quick question. Can't I just flash the GB Stock ROM and then update if I need to?

[Q] HTC One S Root OTA Update Questions

Hello Everyone,
As of today, my phone received the new OTA Update for my HTC One S. However, obviously I cannot update due to my phone being rooted. As a person who is still relatively new with rooting (about a month rooted with my phone-first time), I have a couple questions.
First and foremost, have you guys enjoyed the OTA Update so far? I have read about the list of improvements, and they look promising.
Secondly, I obviously want to stay rooted, are there any suggestions about how to update and then have my phone rooted? Preferably without losing my root, but I don't think that's possible.
Thirdly, I saw a thread about the viper (I believe that's what it's called) rom and that could be my possible solution. But, I am rooted on stock rom and have never put on another rom before. So what are your thoughts on this rom?
Thanks in advance
Sent from my HTC VLE_U using xda app-developers app

Problem Fixed
DrOfLife said:
Hello Everyone,
As of today, my phone received the new OTA Update for my HTC One S. However, obviously I cannot update due to my phone being rooted. As a person who is still relatively new with rooting (about a month rooted with my phone-first time), I have a couple questions.
First and foremost, have you guys enjoyed the OTA Update so far? I have read about the list of improvements, and they look promising.
Secondly, I obviously want to stay rooted, are there any suggestions about how to update and then have my phone rooted? Preferably without losing my root, but I don't think that's possible.
Thirdly, I saw a thread about the viper (I believe that's what it's called) rom and that could be my possible solution. But, I am rooted on stock rom and have never put on another rom before. So what are your thoughts on this rom?
Thanks in advance
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
Hey Dr.
I had the same issue and fixed it. I'm enjoying the OTA update...seems snappier and the option to change the menu button and get rid of that eyesore at the bottom of the screen is great....See this post on how to fix it:
http://forum.xda-developers.com/showthread.php?p=32069130
All you have to do is download the stock recovery (link located in the post above), rename it "Recovery.IMG" and put it in the /Data/Recoveries folder that your All In One Kit uses. Then open up the All In One root kit, flash the stock recovery, and reboot your phone. It should look the same, and give you the same notification that an update is available. Install the update, and then reflash your TWRP or CWM and reroot (the OTA unroots the device, so you need to reinstall SuperSu.
Thanks to all the people that have helped me do the same!!!

fsustrength said:
Hey Dr.
I had the same issue and fixed it. I'm enjoying the OTA update...seems snappier and the option to change the menu button and get rid of that eyesore at the bottom of the screen is great....See this post on how to fix it:
http://forum.xda-developers.com/showthread.php?p=32069130
All you have to do is download the stock recovery (link located in the post above), rename it "Recovery.IMG" and put it in the /Data/Recoveries folder that your All In One Kit uses. Then open up the All In One root kit, flash the stock recovery, and reboot your phone. It should look the same, and give you the same notification that an update is available. Install the update, and then reflash your TWRP or CWM and reroot (the OTA unroots the device, so you need to reinstall SuperSu.
Thanks to all the people that have helped me do the same!!!
Click to expand...
Click to collapse
I keep flashing the stock recovery with all-in-one and then downloading and installing the update. Everytime, about halfway it goes back to the red triangle with the exclamation point and restarts the phone five minutes later.
I check software and its still 4.0.3 and the update redownloads. I've tried several "stock recoveries" and the update afterwards... never works.

TheAdictsPunk said:
I keep flashing the stock recovery with all-in-one and then downloading and installing the update. Everytime, about halfway it goes back to the red triangle with the exclamation point and restarts the phone five minutes later.
I check software and its still 4.0.3 and the update redownloads. I've tried several "stock recoveries" and the update afterwards... never works.
Click to expand...
Click to collapse
I have also tried the steps and have run into the same problem. All is well when I flash into recovery, but when the phone starts updating about quarter or half-way through it also gives me the same red error message and the phone restarts soon after with no update. I have tried several times with the same problem.
However, thanks fsustrength for the instructions, before I was getting no where, but now I almost got it
Sent from my HTC VLE_U using xda app-developers app

ckpv5 said:
As there are many questions on how to do OTA update & to revert to stock after a device is rooted and bootloader unlocked; I made this simple guide which I hope will help the newbies especially.
NOTE : always do a backup and a nandroid backup before trying any of these.
OTA update:
A) ROM is stock, bootloader unlocked, stock recovery and not rooted.
- just run the OTA update, there is no need to relock the bootloader
B) ROM is stock, bootloader unlocked, CWM recovery and not rooted.
- flash the stock recovery that comes with your RUU, extract the RUU for the stock recovery.
* boot to bootloader
* fastboot flash recovery recovery_signed.img
* fastboot reboot-bootloader
* fastboot erase cache
* fastboot reboot
- run the OTA update
C) ROM is stock, bootloader unlocked, stock recovery and rooted
- download OTA Rootkeeper from Play Store
- run the OTA Rootkeeper and click protect root
- run the OTA update, there is no need to relock bootloader
- Once done, run OTA Rootkeeper and click restore root
D) ROM is stock, bootloader unlocked, CWM recovery and rooted
- download OTA Rootkeeper from Play Store
- run the OTA Rootkeeper and click protect root
- no need to relock bootloader
- boot to bootloader and fastboot flash the stock recovery
- run the OTA update
- Once done, run OTA Rootkeeper and click restore root
E) ROM is custom, bootloader unlocked, CWM recovery and rooted and you have a stock nandroid backup
- flash the stock boot.img if after nandroid restore, you have a bootloop
- flash the stock recovery.img
- relock the bootloader - fastboot oem lock
- boot your device and run the OTA update
F) ROM is custom, bootloader unlocked, CWM recovery and rooted and you don't have a stock nandroid backup
- if you dont have the stock nandroid backup, you need to run RUU
- before you can run the RUU you need to:
* flash the stock recovery.img
* flash the stock boot.img (maybe no need)
* relock the bootloader - fastboot oem lock
* run RUU
- run device setup
- run the OTA update
Flashing RUU to revert to stock or to update your One V after you have a custom ROM installed.
- you must have the correct RUU for your device.
- if you are not sure, download CID Getter from Play Store and run it, it will show your CID.
- with your CID, you may be able to find a correct RUU for your device
then (even though some people may not agree with this, but this will bring no harm and it is noob-proof) do this:
1- flash a stock recovery.img
fastboot flash recovery recovery_signed.img
fastboot reboot-bootloader
fastboot erase cache
2- flash a stock boot.img
fastboot flash boot boot_signed.img
fastboot reboot-bootloader
fastboot erase cache
3- re-lock bootloader
fastboot oem lock
fastboot reboot-bootloader
fastboot erase cache
4- flash RUU
Note : for people with ERROR 155 UNKNOWN ERROR they need to go into HBOOT and select FASTBOOT and run the RUU to revert to stock (thanks Lloir)
And usually:
Error 155 - usually wrong recovery.img /wrong boot.img
Error 140 - wrong bootloader / bootloader unlocked
Error 131 - wrong RUU for your device
Credit to all XDA members that posted all the guides in various forum thread and some from own experience which I compiled here for easy reference.
Click to expand...
Click to collapse
Some wonderful person wrote a guide for the One V. Every though it's not the same phone the rules are the same. If these instructions help you click the link and thank the guy for writing it.
http://forum.xda-developers.com/showpost.php?p=27288357&postcount=1

Wow, that is a very useful guide right there! However, while reading the guide, Step D is exactly what both TheAdictsPunk and I seem to have done (I'm making an assumption that he did). I did in fact have and used the root keeper app, put it on temporary unroot, and flashed the stock rom and ran the update. Yet, I still run into the problem of the red error sign. I'm sure there is a factor that maybe could cause it to stop, but I cannot put a finger on it.
However, I did notice something while following the procedures of the guide on my phone. When I flash the stock rom on my phone, I have to re-download the system update. While downloading the system update I notice that some of my apps get root permissions from SuperSu in the background, even though in root keeper I temporarily took off root. Rootkeeper also states that my phone is unrooted. Could this problem cause the red error message? If so, any way to fix it?
Sent from my HTC VLE_U using xda app-developers app

DrOfLife said:
Wow, that is a very useful guide right there! However, while reading the guide, Step D is exactly what both TheAdictsPunk and I seem to have done (I'm making an assumption that he did).
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
I did! Last night I even tried flashing the recovery image through fastboot instead of the all-in-one kit. Then, even, the recovery image wouldn't flash all the way through... maybe our phones are having a problem with the recovery being reflashed and not the update at all.

I had the same exact issue. I finally got fed up and just flashed the RUU with my computer and then just used the All-in-one program to re-root. I am now enjoying 2.31 and really glad I updated. Obviously the RUU wipes everything, but I had done a full backup using Titanium Backup, and then restored all the important settings and data (like accounts, wifi list, bookmarks, dictionary, etc.) (but not the system apps themselves! ) and it worked out pretty well. Still had some things to adjust, like sounds and such. If you want to keep your SMS's use the built-in backup in the messaging app, then restore after the update.. more reliable than any other app I've tried.

mmceorange said:
I had the same exact issue. I finally got fed up and just flashed the RUU with my computer and then just used the All-in-one program to re-root. I am now enjoying 2.31 and really glad I updated. Obviously the RUU wipes everything, but I had done a full backup using Titanium Backup, and then restored all the important settings and data (like accounts, wifi list, bookmarks, dictionary, etc.) (but not the system apps themselves! ) and it worked out pretty well. Still had some things to adjust, like sounds and such. If you want to keep your SMS's use the built-in backup in the messaging app, then restore after the update.. more reliable than any other app I've tried.
Click to expand...
Click to collapse
I'm strongly considering doing that, I can back all my contacts and apps and sms messages via Mobile Go. So, wiping my phone isn't too big of an issue for me because I can restore almost everything I need back on my phone. If you don't mind me asking, where did you get the source that you got the RUU? Also, I have never flashed an ruu before so is their a guide for our phone to flash a RUU?
Sent from my HTC VLE_U using xda app-developers app

DrOfLife said:
I'm strongly considering doing that, I can back all my contacts and apps and sms messages via Mobile Go. So, wiping my phone isn't too big of an issue for me because I can restore almost everything I need back on my phone. If you don't mind me asking, where did you get the source that you got the RUU? Also, I have never flashed an ruu before so is their a guide for our phone to flash a RUU?
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
http://www.lastnite.de/RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5.exe
Links to downloads are on that page.. just copy/paste.
Basically start your phone in fastboot, connect to usb, then run the ruu with admin privileges. Make sure you are on stock recovery, and already have the USB drivers installed on your PC (unless you're on Linux.. already has them.. and maybe Mac too?)

mmceorange said:
http://www.lastnite.de/RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5.exe
Links to downloads are on that page.. just copy/paste.
Basically start your phone in fastboot, connect to usb, then run the ruu with admin privileges. Make sure you are on stock recovery, and already have the USB drivers installed on your PC (unless you're on Linux.. already has them.. and maybe Mac too?)
Click to expand...
Click to collapse
Well I followed all your steps, and all was going well until I ran across RUU error 130, which states that it was using the incorrect RUU. I looked into it and I found that it was the Europe version, and I have the T-Mobile version of my phone. I'm assuming that this is the issue, am I right? Does the RUU in Europe different than the T-Mobile USA one? If so, are there any RUU's out there that cover my phone? I have searched for them with no luck..
Sent from my HTC VLE_U using xda app-developers app

DrOfLife said:
Well I followed all your steps, and all was going well until I ran across RUU error 130, which states that it was using the incorrect RUU. I looked into it and I found that it was the Europe version, and I have the T-Mobile version of my phone. I'm assuming that this is the issue, am I right? Does the RUU in Europe different than the T-Mobile USA one? If so, are there any RUU's out there that cover my phone? I have searched for them with no luck..
Click to expand...
Click to collapse
Ok I figured out a couple answers to my questions. One, the Europe version and the T-Mobile Version are different. That explains why the RUU did not work and gave me Error 130. However, the T-Mobile RUU, RUU_Ville_U_TMOUS_1.84.531.2_R2_Radio_0.16.31501S, is the alternate version that also recieves the OTA update. The RUU is found here http://androidforums.com/one-s-all-things-root/560329-ruu-download-mirrors.html
Then, following the steps, I have successfully updated my phone to the newer softeware!
But of course, I run into another problem.... The CWM recovery does not work for my phone. I flashed the recovery via the HTC One S All-in-One Toolkit. But when getting my phone into recovery mode, it "crashes." (By crashes I mean the phone will go into the htc developmental screen, then turn to black, then reload the normal bootup screen and boot normally up) So, I don't have CWM and I'm unable to root my phone again because I don't have CWM to flash SuperSu. Any thoughts on this?

Rerooting
DrOfLife said:
So, I don't have CWM and I'm unable to root my phone again because I don't have CWM to flash SuperSu. Any thoughts on this?
Click to expand...
Click to collapse
I'm still running stock 1.84, but I'm rooted and unlocked. I do not have any kind recovery like CWM or TWRP. You may have to flash a stock recovery image in order to re-install the recovery of your choice. If you want to get rooted again try this method: http://forum.xda-developers.com/showthread.php?t=1577831 It's what I used to gain root. It's a rather easy to follow guide. I used this instead of the AIO kit.
I'm going to try and revert to locked and unroot in order to get the update. Wish me luck.

DrOfLife said:
Well I followed all your steps, and all was going well until I ran across RUU error 130, which states that it was using the incorrect RUU. I looked into it and I found that it was the Europe version, and I have the T-Mobile version of my phone. I'm assuming that this is the issue, am I right? Does the RUU in Europe different than the T-Mobile USA one? If so, are there any RUU's out there that cover my phone? I have searched for them with no luck..
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
Oh lol sorry about that.
DrOfLife said:
Ok I figured out a couple answers to my questions. One, the Europe version and the T-Mobile Version are different. That explains why the RUU did not work and gave me Error 130. However, the T-Mobile RUU, RUU_Ville_U_TMOUS_1.84.531.2_R2_Radio_0.16.31501S, is the alternate version that also recieves the OTA update. The RUU is found here http://androidforums.com/one-s-all-things-root/560329-ruu-download-mirrors.html
Then, following the steps, I have successfully updated my phone to the newer softeware!
Click to expand...
Click to collapse
Awesome!
DrOfLife said:
But of course, I run into another problem.... The CWM recovery does not work for my phone. I flashed the recovery via the HTC One S All-in-One Toolkit. But when getting my phone into recovery mode, it "crashes." (By crashes I mean the phone will go into the htc developmental screen, then turn to black, then reload the normal bootup screen and boot normally up) So, I don't have CWM and I'm unable to root my phone again because I don't have CWM to flash SuperSu. Any thoughts on this?
Click to expand...
Click to collapse
I personally have never encountered that before, so I am of little help here. The suggestion above me sounds like the right direction though.

Red triangle error
dc211 said:
Some wonderful person wrote a guide for the One V. Every though it's not the same phone the rules are the same. If these instructions help you click the link and thank the guy for writing it.
http://forum.xda-developers.com/showpost.php?p=27288357&postcount=1
Click to expand...
Click to collapse
I'm using method C, i still get that red triangle error. Also i can't get the ruu for my phone. I'm desperate can you please help me.

lonegunman0 said:
I'm using method C, i still get that red triangle error. Also i can't get the ruu for my phone. I'm desperate can you please help me.
Click to expand...
Click to collapse
Im getting the same thing. Even after flashing "stock recovery" that i got from the modaco link, I can't update or even go into the stock recovery...I would absolutely love to enjoy the update too!

skidmarc11 said:
Im getting the same thing. Even after flashing "stock recovery" that i got from the modaco link, I can't update or even go into the stock recovery...I would absolutely love to enjoy the update too!
Click to expand...
Click to collapse
If this many people are running into this problem, maybe we can get a role call of whose using what method, if not stock ROM what custom they are using, and what carrier they us?
I'm stock ROM, Stock Recovery, and Tmobile US. I used Method C.
I'm wondering if they have changed the update in a way that is preventing some people from updating. like it detects a certain file before update or something idk. I'm not any sort of advanced android user so I am probably wrong, but it's the first thing that comes to mind. Otherwise, maybe they sent out a bad update file, but I feel like that probably wouldn't be the case since it's been happening for a couple days now.
Thought's ideas anyone, or am I alone in any of these thoughts?

Stock rom
mylegiscramped said:
If this many people are running into this problem, maybe we can get a role call of whose using what method, if not stock ROM what custom they are using, and what carrier they us?
I'm stock ROM, Stock Recovery, and Tmobile US. I used Method C.
I'm wondering if they have changed the update in a way that is preventing some people from updating. like it detects a certain file before update or something idk. I'm not any sort of advanced android user so I am probably wrong, but it's the first thing that comes to mind. Otherwise, maybe they sent out a bad update file, but I feel like that probably wouldn't be the case since it's been happening for a couple days now.
Thought's ideas anyone, or am I alone in any of these thoughts?
Click to expand...
Click to collapse
skidmarc11 said:
Im getting the same thing. Even after flashing "stock recovery" that i got from the modaco link, I can't update or even go into the stock recovery...I would absolutely love to enjoy the update too!
Click to expand...
Click to collapse
Yes i agree about the file detection. I'm running stock rom but i think i've just realised my problem. Although i have a stock rom my problem is that the stock rom i'm running is deodexed. I read somewhere that if the stock rom is tweaked in any way or if any bloatware is deleted you can't get OTA updates.
Hope this helped

Wouldn't an RUU fix any of those problems?

Yes it would
Sent from my HTC One S using xda app-developers app

[Q] Help updating kernel

Hey, I am picking up a used Cincinnati Bell one s from a friend later today. I know he unlocked or did something via the htc method but other then that I think it is s-on and not super cid (however I am not completely sure. I will know for sure when I get it today) I know the phone hasn't had the official JB update yet. When I get the phone later today I was wanting to get the official update so I can install the newer roms. I do know it has a JB rom on it now but he said it is having some issues and I would rather just update it officially and go from there.
What would be the best way to do this? I know a few months ago the friend I am getting it from restored his stock rom nandroid and tried to do the ota but it kept failing, I am assuming it is because of the unlocked bootloader but I dont know for sure.
What steps can I take to get the updated 3.14 kernel?
Thanks in advance.

aadrcw said:
Hey, I am picking up a used Cincinnati Bell one s from a friend later today. I know the phone has a unlocked bootloader via the htc method but other then that I think it is s-on and not super cid (however I am not completely sure. I will know for sure when I get it today) I know the phone hasn't had the official JB update yet. When I get the phone later today I was wanting to get the official update so I can install the newer roms. I do know it has a JB rom on it now but he said it is having some issues and I would rather just update it officially and go from there.
What would be the best way to do this? I know a few months ago the friend I am getting it from restored his stock rom nandroid and tried to do the ota but it kept failing, I am assuming it is because of the unlocked bootloader but I dont know for sure.
What steps can I take to get the updated 3.14 kernel?
Thanks in advance.
Click to expand...
Click to collapse
Not getting official update even when the ROM is stock can be due to
- Custom Recovery presence
- Root
- removal of any bloatware apps
- Unlocked bootloader (not sure, but should be relocked before update )
Never update with SuperCID, Brick is the result.
Sent from my Nexus 7 using Tapatalk HD

khan.orak said:
Not getting official update even when the ROM is stock can be due to
- Custom Recovery presence
- Root
- removal of any bloatware apps
- Unlocked bootloader (not sure, but should be relocked before update )
Never update with SuperCID, Brick is the result.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Alright, I'll be getting the phone here in about 3 hours or so, What would be the best way to remove the recovery, root and then lock the bootloader back? Sorry if this is a known thing, I am nbew to htc devices so Idk if there is some special way with them

aadrcw said:
Alright, I'll be getting the phone here in about 3 hours or so, What would be the best way to remove the recovery, root and then lock the bootloader back? Sorry if this is a known thing, I am nbew to htc devices so Idk if there is some special way with them
Click to expand...
Click to collapse
- Root removal: restore stock OS (from RUU/OTA/NANDROID)
- Custom Recovery removal: flash a stock recovery. (Via RUU or fastboot)
- locking bootloader: via fastboot
You will be needing HTC drivers (standalone or HTC sync), ADB+Fastboot files and from this folder adb+fastboot commands will be given.
Sent from my Nexus 7 using Tapatalk HD

khan.orak said:
- Root removal: restore stock OS (from RUU/OTA/NANDROID)
- Custom Recovery removal: flash a stock recovery. (Via RUU or fastboot)
- locking bootloader: via fastboot
You will be needing HTC drivers (standalone or HTC sync), ADB+Fastboot files and from this folder adb+fastboot commands will be given.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Alright, One more question, Will any stock recovery work or are they rom specific?

aadrcw said:
Alright, One more question, Will any stock recovery work or are they rom specific?
Click to expand...
Click to collapse
Stock/custom Recoveries are actually variant specific. If you have S4 version, download this.
And if you have S3 version, I don't have a recovery at hand but you can extract it from RUU/OTA files or simply ask for it in respective sections.
Sent from my Nexus 7 using Tapatalk HD