Related
Alright, so I got this phone a week ago. First off, I am loving it. Screw Apple.
Anyway, first thing I wanted to do was root it so I can debloat all of T-Mobile's poop applications they cram inside of it.
I've read places that HBOOT 1.45.0013 isn't rootable. I've read it IS rootable, but only with S-OFF on a previous HBOOT. And I've read that it is rootable, but you can't get S-OFF after root.
I've used HTC's unlock tool, which went successful because I flashed CWM through fastboot. I've tried HTC Supertool, MrRoot, and Revolutionary (which says it isn't compatible)
My question then is, which of the above statements is true? If it is rootable, I don't care about S-OFF too much. But I can't ever find a guide that tells me how to root it with this current HBOOT.
Halp pl0x? <3
If you download the Superuser zip (just google superuser android or something), you can flash it in recovery to get root. Alternatively, download a ROM with root preloaded (DS-mod is essentially stock with root and a few other standard root things added in) and flash it.
Limewirelord said:
If you download the Superuser zip (just google superuser android or something), you can flash it in recovery to get root. Alternatively, download a ROM with root preloaded (DS-mod is essentially stock with root and a few other standard root things added in) and flash it.
Click to expand...
Click to collapse
What's the difference in flashing Superuser, and downloading it from the Market?
Sent from my myTouch_4G_Slide using xda premium
It won't install correctly if you do it while the system is on and live (through the market) you have to do it while the operating system is not running (through clockworkmod)
Afterwards, it's fine to update through the market, but the initial install will fail if done on a running version of Android.
Blue6IX said:
It won't install correctly if you do it while the system is on and live (through the market) you have to do it while the operating system is not running (through clockworkmod)
Afterwards, it's fine to update through the market, but the initial install will fail if done on a running version of Android.
Click to expand...
Click to collapse
..Huh, just flashed Superuser. Weird that it's that easy. All the other threads were like "omg HBOOT 1.45.0013 can't be rooted hnnnnnggg"
So, now onto ROMs, are there any ICS based ones you reccomend?
Btw I see tht your question has been answered but in Mr Root's next update will include a Rooter/Unrooter for the newest H-Boot (Without S-Off)
MewTech said:
..Huh, just flashed Superuser. Weird that it's that easy. All the other threads were like "omg HBOOT 1.45.0013 can't be rooted hnnnnnggg"
So, now onto ROMs, are there any ICS based ones you reccomend?
Click to expand...
Click to collapse
For a while it was so - you couldn't do anything with 1.45.0013, HTC broke the OTA so you couldn't unlock it.
In my quest for s-on to s-off (still ongoing) I found a leaked copy of the OTA as a signed HTC package so now we can actually unlock them, and people can work with them and they are now rootable.
Still stuck with s-on though, which is unfortunate - we're working on it and hopefully can crack it soon. Got some leads we're chasing down, each layer we unravel shows us another that has to be solved below it.
ICS? Dunno - i'm not interested in ICS yet, still trying to learn gingerbread through and through (i'm an android newbie) before moving up to ICS. That's on hold right now because of the s-on issue i'm working on. tbalden has been leading the charge on ICS and I would recommend looking into his works if that is your interest.
Limewirelord said:
If you download the Superuser zip (just google superuser android or something), you can flash it in recovery to get root. Alternatively, download a ROM with root preloaded (DS-mod is essentially stock with root and a few other standard root things added in) and flash it.
Click to expand...
Click to collapse
can you explain in detail how to flash it to rom?????
Using CWM to flash it, you will need the super user ZIP file. Find it somewhere (it's everywhere, no doubt) and put it on your SD card. Reboot the phone to recovery mode, and using CWM recovery, select "flash any zip from SD card" (I'd look up the exact wording, except that my phone has been running a solid 24 days without reboot and I really wanna see how long it goes). Navigate to where your super user ZIP file is, and select it. Follow prompts, et voila, root on reboot.
Assuming all works. If something didn't work, you messed up. Try again from step 1, make sure you have a zip file and not an APK file, make sure you select the correct "flash zip" option (there are two, one specifically for update.zip and another for whatever zip you choose).
HIH
ok this is my huge problem i have the same hboot with s-on
i have the full stock stupid t-mobile mt4gs AOS 2.3.4 software# 1.55.531.3 and i DONT have CWM or any of the extras in only thing i succeeded is getting the bootloader unlocked so what should i do?
Install clockworkmod then flash either superuser pr a ROM - if staying stocl with root, be a good time to do some spring cleaning on all the junk it comes with pre-installed.
Blue6IX said:
Install clockworkmod then flash either superuser pr a ROM - if staying stocl with root, be a good time to do some spring cleaning on all the junk it comes with pre-installed.
Click to expand...
Click to collapse
ok i download this now i try flash CWM recovery and i get this
an error occurred while attempting to run privileged commands!
??????
what do i do next??
We love to title our posts here
crimedave1987 said:
ok i download this now i try flash CWM recovery and i get this
an error occurred while attempting to run privileged commands!
??????
what do i do next??
Click to expand...
Click to collapse
Well,
What exactly did you do that returned this error (mainly because I don't remember if fastboot or adb returns that)? What tutorial/guide were you following? Were you in adb trying to "dd" the CWM recovery image or were you trying to flash an img file from within fastboot? Either way, what was the exact command you typed?
Your other thread (sorry, didn't realize I had replied to you in two different places) received an answer as well. After looking around to get the info you need for this post, I see now you've posted in quite a few threads to which I'm subscribed (guess I just never noticed the name, sorry).
So I see you have an unlocked bootloader. At this point, yes, flash CWM. Blue6ix gave an excellent post on how to do this. Is this the one you are currently trying to follow in order to install CWM?
tried to use superuser
I tried to load the superuser zip file in recovery with cwm. installation aborted. any suggestions? I have mytouch4gslide with s on unlocked with HBoot 1.45.0013
wesomatic said:
I tried to load the superuser zip file in recovery with cwm. installation aborted. any suggestion? I have mytouch4g with s on unlocked with HBoot 1.45.0013
Click to expand...
Click to collapse
From my earlier post:
cj chitwood said:
Using CWM to flash it, you will need the super user ZIP file. Find it somewhere (it's everywhere, no doubt) and put it on your SD card. Reboot the phone to recovery mode, and using CWM recovery, select "flash any zip from SD Card”. Navigate to where your super user ZIP file is, and select it. Follow prompts, et voila, root on reboot.
Assuming all works. If something didn't work, you messed up. Try again from step 1, make sure you have a zip file and not an APK file, make sure you select the correct "flash zip" option (there are two, one specifically for update.zip and another for whatever zip you choose).
HIH
Click to expand...
Click to collapse
Did this help? Only things I can think of are (1) using ”flash update.zip” instead of ”flash [any] zip file” or, less likely, (2) trying to flash an apk instead of a zip.
--
Sent from my Android ”phone”:
HTC DoubleShot /T-Mobile MyTouch 4G Slide running Bulletproof
Yes, that thread did help me. I used your instructions. I even have a new sd card. I have read some threads about formating it first. I did not do that. Also where can I get a good zip file? I down loaded it from some file sharing program 2share I think... Tried again ROOTED!!!! It was so easy!!! Been doing this for a week!!! Wow!!!!!!!!!!!!!!!!!!!
bricked my phone!!!
Just want to add... Do not use ROM Manager from The Market. Bricked my phone. Just stays in start up. Had it rooted and everything!!!!
NO BRICK
Thank God For CWM!!!!!
I am stuck someplace in betweem
Hi:
I too have a MyTouch Slidwe 4G with the hboot 1.45.0013. All the contrary information I have found lead me to go to the professionals. I purchased the root-android.org software. It seemed to run fine - I got no errors and it said that the phone was rooted. I see the superuser app on the phone. However, when I try to run Titanium Backup, it says that the phone is not rooted. The people at root-android.org are not answering my emails (I did get my money back). Any ideas of where I should go from here?
Thanks!
You should never have to purchase root for any android, if it has been done once then chances are it is plastered how to all over the internet, if the phone has a thread on xda then it will be there. Being you got yourself this far I'll help you out a bit more
http://forum.xda-developers.com/showthread.php?p=29439712
Read and understand is my advice, always read until you understand, then search if you have questions, then finally ask questions here if you are still stumped.
For the most part every question you can ask is already answered by one of the super helpful xda folk here, and chances are it is the right information.
I do advice to gain radio soff with the wire trick, it will make life easier... Read up and happy flashing!
Sent from my Nexus 7 using xda premium
I have an HTC One X updated to 4.0.4, software number 2.20.502.7 710RD. I messed up my phone trying to install a cyanogenmod 10 preview but messed up flashing a recovery. Long story short, it would not boot into the regular firmware and wouldn't let me get access anything but the bootloader menu, flashboot, and cwm recovery menu. I ended up using the ruu, htc_one_x_RUU_2.20.502.7_att_us_08022012. I heard that you can't root this new firmware unless you still have you unlock token id thing which i do. I tried running the same tool I used to root my phone before and it did unlock the bootloader but it didn't root it. It installed supersu but not the su binary. If someone would be willing to walk me though rooting my phone that would be great and if someone would be willing to link me to the most up to date clockwork mod recovery page that would be great. And if I misheard and it isn't possible to root at all right now then just say so and I'll shut up. Also all I want to do is install google now for ics on my phone, not flash a rom, because I heard that it wouldn't be safe to do that right now.
pizzalover2 said:
I have an HTC One X updated to 4.0.4, software number 2.20.502.7 710RD. I messed up my phone trying to install a cyanogenmod 10 preview but messed up flashing a recovery. Long story short, it would not boot into the regular firmware and wouldn't let me get access anything but the bootloader menu, flashboot, and cwm recovery menu. I ended up using the ruu, htc_one_x_RUU_2.20.502.7_att_us_08022012. I heard that you can't root this new firmware unless you still have you unlock token id thing which i do. I tried running the same tool I used to root my phone before and it did unlock the bootloader but it didn't root it. It installed supersu but not the su binary. If someone would be willing to walk me though rooting my phone that would be great and if someone would be willing to link me to the most up to date clockwork mod recovery page that would be great. And if I misheard and it isn't possible to root at all right now then just say so and I'll shut up. Also all I want to do is install google now for ics on my phone, not flash a rom, because I heard that it wouldn't be safe to do that right now.
Click to expand...
Click to collapse
You can't. There's a dozen threads right now stating that you cannot root on 2.20.
pizzalover2 said:
I have an HTC One X updated to 4.0.4, software number 2.20.502.7 710RD. I messed up my phone trying to install a cyanogenmod 10 preview but messed up flashing a recovery. Long story short, it would not boot into the regular firmware and wouldn't let me get access anything but the bootloader menu, flashboot, and cwm recovery menu. I ended up using the ruu, htc_one_x_RUU_2.20.502.7_att_us_08022012. I heard that you can't root this new firmware unless you still have you unlock token id thing which i do. I tried running the same tool I used to root my phone before and it did unlock the bootloader but it didn't root it. It installed supersu but not the su binary. If someone would be willing to walk me though rooting my phone that would be great and if someone would be willing to link me to the most up to date clockwork mod recovery page that would be great. And if I misheard and it isn't possible to root at all right now then just say so and I'll shut up. Also all I want to do is install google now for ics on my phone, not flash a rom, because I heard that it wouldn't be safe to do that right now.
Click to expand...
Click to collapse
Not safe to flash a rom? Of course it's safe. Just flash one and you'll have root. Otherwise stay on stock with no root.
Where did you hear that it wouldn't be safe to flash a rom?
Sent from my One X using xda app-developers app
XNine said:
You can't. There's a dozen threads right now stating that you cannot root on 2.20.
Click to expand...
Click to collapse
This is true but not in his case he was unlocked prior to update so he can unlock and root again.
To the op
Don't use cwm use twrp its officilay supported for the one x download goo manager from the market and install it from the app as far the root not working try the process again because it should work.
Edit
Open Su and try to update the binary.
Sent from my Nocturnalized Beast
---------- Post added at 12:48 AM ---------- Previous post was at 12:43 AM ----------
He can't just flash a rom with the new hboot you will need to flash the boot image from fastboot unless flashing a rom that is 2.20 or 2.23 base and even then he will.lose init.d support if he skips flashing the boot from fastboot
Sent from my Nocturnalized Beast
How to Root 4.04 w/ unlock token
Ok, this is what worked for me. First, make sure you have your bootloader unlocked with your unlock token. CIDspoofer will not give you root, but it will unlock your bootloader with the unlock token.
Next, go here http://theunlockr.com/2012/06/05/how-to-install-twrp-2-1-recovery-on-att-and-rogers-htc-one-x/ and download the twrp recovery image and flash it with adb running the commands in the instructions.
Get yourself the 4.04 stock rooted zip from here in the OP of this thread. Take your pick of ODEXED or DE-ODEXED. http://forum.xda-developers.com/showthread.php?t=1812459
Put zip on sd, reboot into recovery, flash the zip and you should be good to go. Stock, rooted update.
I hope this helps.
Ok, I am really excited now. Instead of flashing just a rooted version of the stock, would it be possible to flash to a jelly bean rom. If so how would i do that and which jelly bean rom is the most stable. I am really excited to use google now. I have flashed twrp and can flash the new firmware if i need but if I can get a jelly bean rom that would be preferable.
pizzalover2 said:
Ok, I am really excited now. Instead of flashing just a rooted version of the stock, would it be possible to flash to a jelly bean rom. If so how would i do that and which jelly bean rom is the most stable. I am really excited to use google now. I have flashed twrp and can flash the new firmware if i need but if I can get a jelly bean rom that would be preferable.
Click to expand...
Click to collapse
Just check the dev section. Whatever you find for Jellybean isn't going to be 100% since it's being worked on by the devs, and it's not official. If you don't care about camera and video not working, check out cyanogenmod 10 alpha in the original dev section.
pizzalover2 said:
Ok, I am really excited now. Instead of flashing just a rooted version of the stock, would it be possible to flash to a jelly bean rom. If so how would i do that and which jelly bean rom is the most stable. I am really excited to use google now. I have flashed twrp and can flash the new firmware if i need but if I can get a jelly bean rom that would be preferable.
Click to expand...
Click to collapse
You don't need Jellybean for Google Now anymore, there's a thread in general. You can just flash a .zip and get google now, that way you can get a really stable rom like cleanrom 4.5
Ruayly said:
Can anyone send me a link to root on 1.85 please
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Dev section http://forum.xda-developers.com/showthread.php?t=1709424
SO I am sure I will get the barrage of no's but, of course I am dumb and have my HTCOX ATT stock at 2.20.502.7 never got a token at 1.85 and want to go Cyanagenmod 10 on my phone. Is there any way to revert firmware and then root using the 1.85 method? Or any other thoughts?
jackdforme said:
SO I am sure I will get the barrage of no's but, of course I am dumb and have my HTCOX ATT stock at 2.20.502.7 never got a token at 1.85 and want to go Cyanagenmod 10 on my phone. Is there any way to revert firmware and then root using the 1.85 method? Or any other thoughts?
Click to expand...
Click to collapse
Please search before posting things like this. There is at least I mean at least 10 threads about this. If you upgraded and did not change your cid or unlock your bootloader you are out of luck until a new exploit is found or s off is achieved.
Sent from my Nocturnalized Beast
Root 1.85
Ruayly said:
Can anyone send me a link to root on 1.85 please
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
http://www.xda-developers.com/xda-tv-2/how-to-root-the-htc-one-x-xda-tv/
http://forum.xda-developers.com/showthread.php?t=1577671
http://forum.xda-developers.com/showthread.php?t=1709424
Root 1.85
Ruayly said:
Can anyone send me a link to root on 1.85 please
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1678138
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
Hi,
I have this AT&T one x, (I m using on NON AT&T network), so cant have an ota update.
Looking at few forums, downloaded the OTA version on XDA (631 Mb)
Saw people writing, that just rename the file to update.zip and then go to recovery and choose install from internal memory.
That dint work for me.
Error: not able to mount sd mem
Then few people wrote to choose install from external mem.
That dint work either.
Error: not able to mount sd mem
Then saw few people saying that I need to root my device and unlock bootloader.
I dint that, and tried from bootlaoder to install from zip.
That also dint work.
Now saw, I few wrote that i need to be S - OFF.
Which I tried doing it, but i m not able to do s-off for myself.
Pls pls pls.... can any of you EXPERTs out here help me.
Waited like for AT&T to release the update, now when it is out, i m not able to make it through.
Your step by step instruction would be highly appreciable.
Be aware, that if you have the AT&T version, and you are rooted, then you probably have SuperCID (in fact, you must have SuperCID, unless it was already changed back). If you have SuperCID you must S-off (or return to the AT&T CID) before applying the OTA, or you will brick your phone!
I am not all that familiar with the process to install using OTA.zip (and haven't done it myself), but it was discussed in these threads:
http://forum.xda-developers.com/showthread.php?t=2180408
forum.xda-developers.com/showthread.php?t=1701460
redpoint73 said:
Be aware, that if you have the AT&T version, and you are rooted, then you probably have SuperCID (in fact, you must have SuperCID, unless it was already changed back). If you have SuperCID you must S-off (or return to the AT&T CID) before applying the OTA, or you will brick your phone!
I am not all that familiar with the process to install using OTA.zip (and haven't done it myself), but it was discussed in these threads:
http://forum.xda-developers.com/showthread.php?t=2180408
forum.xda-developers.com/showthread.php?t=1701460
Click to expand...
Click to collapse
How to S Off ATT HOX???
Thats the big question.
I have rooted my phone through one click TWRP Toolkit.
abhishek jain said:
How to S Off ATT HOX???
Thats the big question.
Click to expand...
Click to collapse
No, that is a very small question. Or at least a very easy one to answer.
Take 5 minutes to look around before asking "big" questions: http://forum.xda-developers.com/showthread.php?t=1671237
http://forum.xda-developers.com/showthread.php?t=2136172
If you would read my first post, I have already posted that I tried doing that was not able to do.
On the third comment that we need push in , where it given an error 92 or something like that, I dint got that.
Tried many times and then it became a "big" for me.
We all are born not experts in every field.
So before comenting pls try to know what's behind it
Sent from my HTC One X using xda app-developers app
Lol it doesn't take an expert to read and take five mins..this is probably one if the easiest s off methods you'll see for awhile... You probably didn't set up your adb fastboot environment up right
a box of kittens said:
Lol it doesn't take an expert to read and take five mins..this is probably one if the easiest s off methods you'll see for awhile... You probably didn't set up your adb fastboot environment up right
Click to expand...
Click to collapse
Changed my laptop and tried again.
Now I am S-OFF
THough I applied the same comments on three different machine.
4th Time it worked.
Now how to install this OTA updated which I have downlaoded
abhishek jain said:
Changed my laptop and tried again.
Now I am S-OFF
THough I applied the same comments on three different machine.
4th Time it worked.
Now how to install this OTA updated which I have downlaoded
Click to expand...
Click to collapse
Anyone to help me out in this case:
I am S OFF
Rooted
Unlocked bootloader
AT&T HOX on non AT&T network
631 mb update.zip
Looking top update
Rename file update.zip and copy to internal storage.
Reboot to bootloader and enter recovery.
Push power+ vol up when recovery screen appears to enter recovery dialog.
Ignore errors.
Select install from internal storage
Select update.zip
Phone will reboot a couple of times.
iElvis said:
Rename file update.zip and copy to internal storage.
Reboot to bootloader and enter recovery.
Push power+ vol up when recovery screen appears to enter recovery dialog.
Ignore errors.
Select install from internal storage
Select update.zip
Phone will reboot a couple of times.
Click to expand...
Click to collapse
I tried this method couple of time before : unlocking, rooting and S-off ing
In this case , do i need to relock my bootloader and stock recovery?
If yes, where can i find stock recovery, i have deleted it.
By "i deleted it" do you mean you installed a custom recovery? If so, yes you need to get stock recovery back on.
Only way I know of to reinstall stock recovery is to run the 2.20 ruu. Since you're s-off, you don't need to relock; just run it.
iElvis said:
By "i deleted it" do you mean you installed a custom recovery? If so, yes you need to get stock recovery back on.
Only way I know of to reinstall stock recovery is to run the 2.20 ruu. Since you're s-off, you don't need to relock; just run it.
Click to expand...
Click to collapse
I am not a techie but as far as i know, i have not installed a custom recovery.
I did TWRP tool kit, rooting and unlocking bootloader.
How can see if i am custom recovery or stock
abhishek jain said:
I am not a techie but as far as i know, i have not installed a custom recovery.
I did TWRP tool kit, rooting and unlocking bootloader.
How can see if i am custom recovery or stock
Click to expand...
Click to collapse
You probably have a custom recovery. Reboot to bootloader and select recovery and see what you get. If it's TWRP, you'll get a teamwin splash screen and then some options. Stock recovery will just show a screen with a green circle.
iElvis said:
You probably have a custom recovery. Reboot to bootloader and select recovery and see what you get. If it's TWRP, you'll get a teamwin splash screen and then some options. Stock recovery will just show a screen with a green circle.
Click to expand...
Click to collapse
Then I have custome recovery.
Could you gimme a link for stock recovery image
I do not know if one is available. I have never seen one posted. Running a ruu will put it back on.
iElvis said:
I do not know if one is available. I have never seen one posted. Running a ruu will put it back on.
Click to expand...
Click to collapse
Yes now i have got my phone updated with the OTA update
abhishek jain said:
Yes now i have got my phone updated with the OTA update
Click to expand...
Click to collapse
Please click "Thanks" if anyone in the thread helped you.
iElvis said:
Please click "Thanks" if anyone in the thread helped you.
Click to expand...
Click to collapse
I have already done that.
And now in case anyone needs help, i can help those people out.
Coz the method is simple, but it is not at all explained clearly in any of the threads.
It has come in bit and pieces.
I have noticed one thing.
That after installing the update and again unlockin the bootloader and rooting, I am not able to see "TAMPERED" being written in the boatloader.
Also, now when I am rooted and also have SU permission, I m not able to switch on my WiFi tether with the files mentioned in the thread
http://forum.xda-developers.com/showthread.php?t=1677261
The "TAMPERED" flag goes away when you're s-off and flash a new hboot.
I believe wifi tether is blocked on the new AT&T base. You can flash a custom rom on the 3.17 base and it should work.