Related
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
Hey all,
I rooted my HOX (1.73, 4.0.3) with the kpenn ne-Click a few days after I got it for the Tether and to de-bloat. Since then I haven't read anything on the One X till I heard Jelly Bean coming along. Anyhoo my question is what the upside of getting the new OTA (4.0.4) would be and how I would go about it if I wanted to (I've never updated before and ATT has stopped asking me to update, also I get nothing when I try to check for an update).
I've been reading around and it seems like most people are on to 1.85 and are flashing 4.1/2.2. My primary uses of my phone are for the media applications/web browsing and I haven't noticed any real drop in performance but I have heard the new updates have sped up the HOX considerably which is something I'm always interested in.
Thanks!
DON'T flash any OTA you will lose your root and will lose your ability to re root because there is no boot loader unlock for the new base. If you want to update and flash a new ROM and want to stick to sense, look at clean rom or xi40. Both are updated on the new base and are heaps and bounds better than the original ATT software :thumbup:
Shaddy-Z. said:
DON'T flash any OTA you will lose your root and will lose your ability to re root because there is no boot loader unlock for the new base. If you want to update and flash a new ROM and want to stick to sense, look at clean rom or xi40. Both are updated on the new base and are heaps and bounds better than the original ATT software :thumbup:
Click to expand...
Click to collapse
i one-clicked unrooted my phone earlier and freaked out (and the new updates didn't work out on my phone anyway). i ended up getting kpenn's one click again and putting SU back into my phone. Do you have any links that can take me on a step by step process of unlocking my phone and flashing those roms on it? I just love being able to control my phone and pushing it to its absolute limits.
Sigh. I followed the tutorial but I made a few mistakes...
1) I unlocked my phone way earlier than I should have so I wiped everything before I could make a back-up..
2) Re-locked accordingly to see if I could keep updating. I did manage to get to 1.85 like the tutorial said but.....
3) Since I didn't have a custom recovery I wasn't sure how to proceed. I couldn't get the root to flash so I tried using the 1-click 1.85 root since my phone was running 1.85.
....This ended up updating to 2.2 so now I have an unlocked HOX 2.2/4.0.4. With all the bloat.
Dumb dumb dumb. Ugh.
Pbdeng said:
Sigh. I followed the tutorial but I made a few mistakes...
1) I unlocked my phone way earlier than I should have so I wiped everything before I could make a back-up..
2) Re-locked accordingly to see if I could keep updating. I did manage to get to 1.85 like the tutorial said but.....
3) Since I didn't have a custom recovery I wasn't sure how to proceed. I couldn't get the root to flash so I tried using the 1-click 1.85 root since my phone was running 1.85.
....This ended up updating to 2.2 so now I have an unlocked HOX 2.2/4.0.4. With all the bloat.
Dumb dumb dumb. Ugh.
Click to expand...
Click to collapse
it's UNLOCKED?
you're lucky then.
just push a recovery like twrp then push root. Then you can debloat.
Yep, it's still unlocked. That was around the 4-7th reset I did (I messed up a lot). Do you have a link that shows me how to do that? I'm actually not as bummed about going to 2.2 since it runs so much faster than 1.73 did.
Pbdeng said:
Yep, it's still unlocked. That was around the 4-7th reset I did (I messed up a lot). Do you have a link that shows me how to do that? I'm actually not as bummed about going to 2.2 since it runs so much faster than 1.73 did.
Click to expand...
Click to collapse
make sure you have your unlock token and then go to http://www.htcdev.com/bootloader/unlock-instructions/page-4/
and follow the directions.
after that look at this thread to install twrp http://forum.xda-developers.com/showthread.php?t=1777773
then this one to re-root
http://forum.xda-developers.com/showthread.php?t=1673935
I notice one of the links is for 1.85. Does that mean that I'll go from 2.2 back to 1.85? I just wanted to make sure since my impression from the forums is that there is no 2.2 root yet unless it was flashed.
Pbdeng said:
I notice one of the links is for 1.85. Does that mean that I'll go from 2.2 back to 1.85? I just wanted to make sure since my impression from the forums is that there is no 2.2 root yet unless it was flashed.
Click to expand...
Click to collapse
no those pages just tell you how to manually install root and recovery.
your bootloader is still unlockable
unlock it
then install a recovery
then install root via that recovery
Ahh, thanks a bunch man.
Sorry if this is repetitive....
So I've checked my phone and currently it states that it is
"Re-locked"
I downloaded a recovery so it's currently on my phone. Furthermore I all ready had a copy of SU sitting in my phone's download folder.
Does this mean that I'm going to...
- Unlock bootloader (that is currently relocked) and have everything erased again.
- Reboot from recovery (of the evita 2.2.img I just downloaded with TWRP)
- Then flash the SU root I all ready have on my phone?
Pbdeng said:
Sorry if this is repetitive....
So I've checked my phone and currently it states that it is
"Re-locked"
I downloaded a recovery so it's currently on my phone. Furthermore I all ready had a copy of SU sitting in my phone's download folder.
Does this mean that I'm going to...
- Unlock bootloader (that is currently relocked) and have everything erased again.
- Reboot from recovery (of the evita 2.2.img I just downloaded with TWRP)
- Then flash the SU root I all ready have on my phone?
Click to expand...
Click to collapse
yeah unlock the boot loader. set up the phone again
then install the recovery then root.
to make your unlock stick, turn off fastboot in power options, then power down phone completely then restart it to the bootloader.
Hmm, so my phone is definitely unlocked now. I installed the recovery and I manually flashedthe new SuperSU in that link you posted for me. As far as I can tell nothing is happening.
Note: It says that it installs the recovery but there is no reboot that occurs. I've done this both with the android app and manually and nothing is happening.
I don't see SuperSU and rootchecker is confirming that my phone isn't rooted yet.
so you reboot to recovery, choose the superSU package to install then what happens?
I know this works I've done it quite a few times myself.
Presently I installed the latest img file with TWRP with the app. There is not reboot that occurs (unless I'm suppose to reboot on my own?). If that's the case then I've been a total idiot.
I've just been installing the openrecovery and then I press "Flash Roms" to flash the supersu. I get a little notification that says "Preparing to Flash" and then nada.
After you install twrp recovery you reboot. Then you boot to recovery and flash the super su zip manually
Wooh! I got it to work! Thank you so much!
Pbdeng said:
Wooh! I got it to work! Thank you so much!
Click to expand...
Click to collapse
No problemmo.
Does this also mean that I can flash any ROMs I want on my phone now?
Yes. But you will have to flash kernels aka boot.img separately using fast boot.
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
Basically I'm asking before I apply the ORA whether or not it will be a harder, easier, or exactly the same process to get root and unlock the bootloader.
Any extra steps to flash or incompatible roms afterwards?
Just curious. I am not rooted but have studied the process to where I know I could if I wanted to. Wondering if applying the OTA will change what I already know and/or make it harder to get root.
Sent from my SCH-I535 using xda app-developers app
GoodVibrant-ions said:
Basically I'm asking before I apply the ORA whether or not it will be a harder, easier, or exactly the same process to get root and unlock the bootloader.
Any extra steps to flash or incompatible roms afterwards?
Just curious. I am not rooted but have studied the process to where I know I could if I wanted to. Wondering if applying the OTA will change what I already know and/or make it harder to get root.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Check out this thread over in the dev section.
http://forum.xda-developers.com/showthread.php?t=2046439
GoodVibrant-ions said:
Basically I'm asking before I apply the ORA whether or not it will be a harder, easier, or exactly the same process to get root and unlock the bootloader.
Any extra steps to flash or incompatible roms afterwards?
Just curious. I am not rooted but have studied the process to where I know I could if I wanted to. Wondering if applying the OTA will change what I already know and/or make it harder to get root.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I re rooted after going back to stock ICS. Verified root, then upgraded to OTA Jellybean. Root stayed via OTA Rootkeeper.
GoodVibrant-ions said:
Basically I'm asking before I apply the ORA whether or not it will be a harder, easier, or exactly the same process to get root and unlock the bootloader.
Any extra steps to flash or incompatible roms afterwards?
Just curious. I am not rooted but have studied the process to where I know I could if I wanted to. Wondering if applying the OTA will change what I already know and/or make it harder to get root.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
If you use cwm6 you won't lose anything. Accept the update, after booting into recovery cwm will ask if you want to install un trusted . zip. Say yes. It installs, just before reboot it will ask if you want to keep root, then ask if you want to keep custom recovery. Answer yes and you're good. It will reboot and say update failed but that's just because you kept the recovery. If you go to check for update it will say you are up to date.
Frunple said:
If you use cwm6 you won't lose anything. Accept the update, after booting into recovery cwm will ask if you want to install un trusted . zip. Say yes. It installs, just before reboot it will ask if you want to keep root, then ask if you want to keep custom recovery. Answer yes and you're good. It will reboot and say update failed but that's just because you kept the recovery. If you go to check for update it will say you are up to date.
Click to expand...
Click to collapse
This is correct. Same thing happened on my rooted GS 3. The update menu said "failed" but the update did actually take.
But don't do what I just did: try to back up the ROM Manager. It will not make the phone happy. Now stuck at the soft brick screen. Argh
Knightvision said:
This is correct. Same thing happened on my rooted GS 3. The update menu said "failed" but the update did actually take.
But don't do what I just did: try to back up the ROM Manager. It will not make the phone happy. Now stuck at the soft brick screen. Argh
Click to expand...
Click to collapse
If you haven't already fixed it, this happened to me upgrading to the various JB leaks once when I forgot to re-unlock the bootloader and tried to boot into CWM recovery. It gave me the Verizon warning screen, but I was able to use the Vol. Down + Home method to get into download mode and then just had the phone reboot. It booted normally and then you can use EZ-unlock to unlock the bootloader again. It might tell you that it is already unlocked, which isn't right so lock it and then unlock it.
BigErnM said:
If you haven't already fixed it, this happened to me upgrading to the various JB leaks once when I forgot to re-unlock the bootloader and tried to boot into CWM recovery. It gave me the Verizon warning screen, but I was able to use the Vol. Down + Home method to get into download mode and then just had the phone reboot. It booted normally and then you can use EZ-unlock to unlock the bootloader again. It might tell you that it is already unlocked, which isn't right so lock it and then unlock it.
Click to expand...
Click to collapse
I can confirm that this method works. I used Voodoo to keep my root and then answered yes to allowing CWM to install the unsigned .zip and answered yes to keeping root. I then got the dreaded Verizon warning triangle and was prepared to Odin back to Stock and start over. Just by chance I went into download mode and it allowed me boot my Rom. Once in, I checked EZ-unlock and it said I was unlocked, so I went ahead and locked and then unlocked and all was good! Hope this helps saves someone else some hassle.
Real_JESRadio said:
I re rooted after going back to stock ICS. Verified root, then upgraded to OTA Jellybean. Root stayed via OTA Rootkeeper.
Click to expand...
Click to collapse
man I tried this but it didnt work rootkeeper says its rooted but no root access the super user app is there...could i have done something wrong?? do i have do something after i upgrade to get to work?? thanx
BigErnM said:
If you haven't already fixed it, this happened to me upgrading to the various JB leaks once when I forgot to re-unlock the bootloader and tried to boot into CWM recovery. It gave me the Verizon warning screen, but I was able to use the Vol. Down + Home method to get into download mode and then just had the phone reboot. It booted normally and then you can use EZ-unlock to unlock the bootloader again. It might tell you that it is already unlocked, which isn't right so lock it and then unlock it.
Click to expand...
Click to collapse
It's fixed now. The CMW recovery mode wasn't working for some reason. Whatever broke ROM Manager did so by breaking CMW Recovery. I blame myself for stupidly trying to run a backup like that. Anyway, all I could get was the triangle screen and it would only reboot to that or the CMW that wasn't working. Ended up putting it in Odin mode and reflashing with one of the no-wipe leaks. Works fine now. And VZW says I am up to date.
Will get around to rerooting/unlocking again later today. And smacking myself for getting into this mess.
Good to learn from mistakes that are not fatal. Good to have LOTS of resources to figure out how to bail it out too!
Hey all,
Ok, so I rooted my Razr HD, unlocked the boot loader, and now would like to take the latest OTA update. It is failing right now. I tried a factory reset before doing it, and saved root with voodoo and all that. I am assuming though, that it is failing because the recovery is not stock? It's TWRP.
What do I need to do to get the damned OTA update installed, and then have the custom recovery with root intact?
Thanks!
-------------------------
Resolved:
Used clockwork mod instead, downloaded stock image, flashed using RSD Lite 6.1.4.
Sad Panda said:
Hey all,
Ok, so I rooted my Razr HD, unlocked the boot loader, and now would like to take the latest OTA update. It is failing right now. I tried a factory reset before doing it, and saved root with voodoo and all that. I am assuming though, that it is failing because the recovery is not stock? It's TWRP.
What do I need to do to get the damned OTA update installed, and then have the custom recovery with root intact?
Thanks!
Click to expand...
Click to collapse
You can go the hard route and re-load the stock recovery, re-load all of the stock apps, and take the OTA. You can also fastboot to the latest OTA and just re-root. It's easy to re-root with an unlocked BL, you just need to flash SU in recovery. The easiest option is to find a stock ROM on here and just flash it. I believe there are a couple in dev section. Also, there is one on Batakang that's based off of the latest DST ROM.
RikRong said:
You can go the hard route and re-load the stock recovery, re-load all of the stock apps, and take the OTA. You can also fastboot to the latest OTA and just re-root. It's easy to re-root with an unlocked BL, you just need to flash SU in recovery. The easiest option is to find a stock ROM on here and just flash it. I believe there are a couple in dev section. Also, there is one on Batakang that's based off of the latest DST ROM.
Click to expand...
Click to collapse
Oh ok, so the stock roms are using the updated kernel/baseband/etc ?
Sad Panda said:
Hey all,
Ok, so I rooted my Razr HD, unlocked the boot loader, and now would like to take the latest OTA update. It is failing right now. I tried a factory reset before doing it, and saved root with voodoo and all that. I am assuming though, that it is failing because the recovery is not stock? It's TWRP.
What do I need to do to get the damned OTA update installed, and then have the custom recovery with root intact?
Thanks!
Click to expand...
Click to collapse
as long as you didnt delete or freeze any stock apps put stock recovery back on using this tool. http://www.mediafire.com/download/tt7cwwua49n24uv/Razr_HD_Recovery_Flasher_V7.rar then take the update. make a note of your baseband before you start because the update is going to fail at the end even if it installs. the bb will let you know if you got all you could or if there are issues. afterwards, restore root and use the tool to put cwm or twrp back on.
Hi guys,
So i had my phone rooted with an unlocked bootloader running CM for quite some time. I decided yesterday to go back to stock (factory reset via matts utility). Its been hitting me with an OTA update since then, and i kept hitting install later...install later....
and today i accidentally hit install now. So it tried to do it via CWM recovery, and obviously failed. and when it fails, no matter what i do, it reboots back to the system (which is good), but then immediately tries to run the update again.
Is there any way for me to get this to stop happening? I turned off my phone in case i have to do something via fastboot (save the battery). but can i maybe flash the stock recovery through the utility? would that do it?
Thanks for any help!
msassounian said:
Hi guys,
So i had my phone rooted with an unlocked bootloader running CM for quite some time. I decided yesterday to go back to stock (factory reset via matts utility). Its been hitting me with an OTA update since then, and i kept hitting install later...install later....
and today i accidentally hit install now. So it tried to do it via CWM recovery, and obviously failed. and when it fails, no matter what i do, it reboots back to the system (which is good), but then immediately tries to run the update again.
Is there any way for me to get this to stop happening? I turned off my phone in case i have to do something via fastboot (save the battery). but can i maybe flash the stock recovery through the utility? would that do it?
Thanks for any help!
Click to expand...
Click to collapse
Hold all 3 keys till black, toggle pwr: off on off.
Scroll vol dn to recovery. Vol up to select.
Wipe cache. Done
Thanks it worked for me! Thanks!
Enviado desde mi XT1053 mediante Tapatalk
Hello Professor, maybe this question is out of date or frequently asked questions. do the update ota 4.1.2 can downgrade to 4.0.4 to Unlock BootLoader?? I feel free with the Droid Razr maxx HD Locked. Please explanation. Thanks
Xt926 maxx Verizon US
prabu33 said:
Hello Professor, maybe this question is out of date or frequently asked questions. do the update ota 4.1.2 can downgrade to 4.0.4 to Unlock BootLoader?? I feel free with the Droid Razr maxx HD Locked. Please explanation. Thanks
Xt926 maxx Verizon US
Click to expand...
Click to collapse
This is for the 907 but same steps as for the 926, just get the 404 xml for the 926 & mod the xml as I did for/in the xml file.
There are several steps to delete.
http://forum.xda-developers.com/showthread.php?t=2391641
aviwdoowks said:
This is for the 907 but same steps as for the 926, just get the 404 xml for the 926 & mod the xml as I did for/in the xml file.
There are several steps to delete.
http://forum.xda-developers.com/showthread.php?t=2391641
Click to expand...
Click to collapse
you make 100% without any constraints on mobile downgrade to 4.0.4 and do unlock bootloader the step by step? Please explain you did remove the part where the xml so that it runs correctly on you and me. Thank you for the progress
prabu33 said:
you make 100% without any constraints on mobile downgrade to 4.0.4 and do unlock bootloader the step by step? Please explain you did remove the part where the xml so that it runs correctly on you and me. Thank you for the progress
Click to expand...
Click to collapse
Just compare the stock & mod9 xmls, no secrets.
Just be warned that downgrading to 4.0.4 will NOT allow you to unlock the bootloader.