Related
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
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
curious if there is something i'm missing here... i've unlocked my bootloader successfully but whenever i fastboot flash a recovery or flash root files in recovery nothing seems to stick... not sure whats going on... i've heard of having to flash recovery everytime on devices with a locked bootloader but i didn't think that would apply here... any help is much appreciated... (this is also my first samsung/nexus device so i'm more familiar with methods used on the EVO line)
thispaininmyhead said:
curious if there is something i'm missing here... i've unlocked my bootloader successfully but whenever i fastboot flash a recovery or flash root files in recovery nothing seems to stick... not sure whats going on... i've heard of having to flash recovery everytime on devices with a locked bootloader but i didn't think that would apply here... any help is much appreciated... (this is also my first samsung/nexus device so i'm more familiar with methods used on the EVO line)
Click to expand...
Click to collapse
Make sure you're using a perm root method. and make sure you have the correct updated SU application. My root wouldn't come through because I didn't have the latest SU.
Hopefully I helped.
thispaininmyhead said:
curious if there is something i'm missing here... i've unlocked my bootloader successfully but whenever i fastboot flash a recovery or flash root files in recovery nothing seems to stick... not sure whats going on... i've heard of having to flash recovery everytime on devices with a locked bootloader but i didn't think that would apply here... any help is much appreciated... (this is also my first samsung/nexus device so i'm more familiar with methods used on the EVO line)
Click to expand...
Click to collapse
Hi,
What root method did u use?
What recovery are u using?
What ROM are u flashing?
The more info, the better
Vs Nexus S4G using tapatalk2
Unlocked the boot loader with fast boot commands then flashed superuser.zip with clockwork 3.x.x and twrp 2.2.0 haven't tried flashing any Roms since nothing seems to stick...
Sent from my Nexus S 4G using Tapatalk 2
And Vidal I used the toolkit you linked me to in my last q&a post...
Sent from my Nexus S 4G using Tapatalk 2
vidaljs said:
Hi,
What root method did u use?
What recovery are u using?
What ROM are u flashing?
The more info, the better
Also after looking into the scripts and files in the method with the toolkit it seems none of the files get pushed to the device to begin flashing
Sent from my Nexus S 4G using Tapatalk 2
Click to expand...
Click to collapse
By default, any recovery you flash on the system will be gone by the next reboot. This is a security measure the android os does I think.
1. You can flash a ROM. Anyone. I prefer aokp or cna. That way the recovery sticks (the recovery sticks on all the ROMs besides stock)
OR
P.S. You will need the latest cwm recovery
2. So all you need to do is to flash the recovery of your choice. I would recommend CWM for this short guide. Then once flashed go to the recovery make a backup. Then if it reboots flash the same recovery again. Boot into it and restore that backup. When you restore it and go reboot system now it should come up with a menu saying recovery flash fix (or something around those lines). Hit/navigate to yes and you should get a sticky recovery from there. BTW I have not tried this method.
You cannot blame me for bricking, damaging or done anything to your phone
Hope this helps.
Regards,
UselessSniper001
P.S. I don't know how root isn't sticking. I mean if you have flashed the su is the recovery already well then you are all set to go. Unless you haven't actually flashed the su in the recovery. Then flash the recovery from your PC boot into the recovery and flash the su files in the recovery. Reboot and enjoy. Then follow this guide above. Or follow this link:
http://forum.xda-developers.com/showthread.php?t=875875&page=2
I finally figured out the SU and CWM I was flashing was ancient so I found the newest and they stuck with help of the fix ya mentioned inside CWM... Thanks
Sent from my Nexus S 4G using Tapatalk 2
Hi everyone,
I've got a Verizon HTC One M8 that was at Android 4.4.3, and which I have used Sunshine to get s-off so that I could use SUinstaller and get a basic rooting of my phone. I run it using the Xposed Framework and Greenify, so I kinda need root to make those effective.
Anyway, I've been touching "Update Later" for a few weeks now, waiting until I had time to sit down and figure out what I had to do to keep root when I took the update to 4.4.4. Unfortunately the dialog box surprised me this morning when I was going to do something else, and I ended up accidentally hitting the "Update Now" button.
As I got s-off with Sunshine, I assume getting root back isn't gonna be that difficult, but I just don't know how to.
Is there an app to give me root again? Do I need to flash a ROM? I want to keep it pretty stock, I don't necessarily want a custom ROM, and I want to be able to use this new Eye Experience thing that they've added.
Thanks to anyone that decides to help me out,
Chris
Flash twrp then flash su through recovery and wala..and u can then flash back the stock recovery if you wanna be ready for the next ota
Sent from my One M8 using XDA Free mobile app
ChrisRevocateur said:
Hi everyone,
I've got a Verizon HTC One M8 that was at Android 4.4.3, and which I have used Sunshine to get s-off so that I could use SUinstaller and get a basic rooting of my phone. I run it using the Xposed Framework and Greenify, so I kinda need root to make those effective.
Anyway, I've been touching "Update Later" for a few weeks now, waiting until I had time to sit down and figure out what I had to do to keep root when I took the update to 4.4.4. Unfortunately the dialog box surprised me this morning when I was going to do something else, and I ended up accidentally hitting the "Update Now" button.
As I got s-off with Sunshine, I assume getting root back isn't gonna be that difficult, but I just don't know how to.
Is there an app to give me root again? Do I need to flash a ROM? I want to keep it pretty stock, I don't necessarily want a custom ROM, and I want to be able to use this new Eye Experience thing that they've added.
Thanks to anyone that decides to help me out,
Chris
Click to expand...
Click to collapse
All you to do is use ADB commands on your computer. Just unlock the bootloader. Then flash zip for twrp. Once you do that, install a rom. But u may be thinking, maybe I need root. And the answer is TWRP automatically roots your phone because it installs all the Supersu binaries to your phone. Hoped this helped. If it didn't, just ignore it.
Robby_Rimal said:
All you to do is use ADB commands on your computer. Just unlock the bootloader. Then flash zip for twrp. Once you do that, install a rom. But u may be thinking, maybe I need root. And the answer is TWRP automatically roots your phone because it installs all the Supersu binaries to your phone. Hoped this helped. If it didn't, just ignore it.
Click to expand...
Click to collapse
Totally not applicable. Guessing you aren't a vzw user? Op is s off via sunshine. Sunshine unlocks bootloader and turns s off. Op needs to simply flash twrp and latest su.zip. Also, on vzw you can't unlock bootloader unless s off. We don't get to HTC dev here... And besides, once s off, what does it matter if locked or unlocked?
Second post in this thread hit the nail on the head. @MotoTurbo
dottat said:
Totally not applicable. Guessing you aren't a vzw user? Op is s off via sunshine. Sunshine unlocks bootloader and turns s off. Op needs to simply flash twrp and latest su.zip. Also, on vzw you can't unlock bootloader unless s off. We don't get to HTC dev here... And besides, once s off, what does it matter if locked or unlocked?
Second post in this thread hit the nail on the head. @MotoTurbo
Click to expand...
Click to collapse
An unlocked bootloader will let you install different roms that are not sense. Like cyanogenmod, paranoid android, and that snazz. And yes I am on dh's android 5 lollipop ROM. I am on the vzw m8. I have the latest 4.4.4 firmware with digital Hugh's "custom firmware" flashed through fastboot. Thank you very much dottat.
Robby_Rimal said:
An unlocked bootloader will let you install different roms that are not sense. Like cyanogenmod, paranoid android, and that snazz. And yes I am on dh's android 5 lollipop ROM. I am on the vzw m8. I have the latest 4.4.4 firmware with digital Hugh's "custom firmware" flashed through fastboot. Thank you very much dottat.
Click to expand...
Click to collapse
I don't think you understood my post.
the original post stated S-OFF via sunshine. this means bootlocker unlocked and S-OFF. VRZN doesn't allow free bootloader unlock via htcdev.
if this 4.4.4 release via OTA, then firmware updated (this is good). since still S-OFF, just flash lastest TWRP img (via fastboot) and install ROM (VenomONE v3.0 -- if you have 4.4.4 firmware).
you still be good to go... -GA
Yep I had the same question.
If you're S-Off, you should have stayed S-Off. Flash a custom recovery(e.g. TWRP), download Chainfire's SuperSU, and flash it to your phone.
Q&A for [ROOT] Root for SHIELD Tablet 2.0 (Lollipop)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROOT] Root for SHIELD Tablet 2.0 (Lollipop). If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
UK Root?
Wondering if i should try root since im in UK.
Heres the boot.img from the UK update, is it any different from the NA version before i try root?
EDIT: Wont let me post outside links
Should i try it or no?
DazEB said:
Wondering if i should try root since im in UK.
Heres the boot.img from the UK update, is it any different from the NA version before i try root?
EDIT: Wont let me post outside links
Should i try it or no?
Click to expand...
Click to collapse
If it is the WiFi Only model it should work, but no promises. If it is LTE please PM the link to the boot.img
Cwm and future ota
Does CWM prevents future OTA? What if I want root but stock recovery? Thanks.
Sweet, I followed the "Locked bootloader" method step by step and it working perfectly, no problem whatsoever. Thank you very much!!
layanto said:
Does CWM prevents future OTA? What if I want root but stock recovery? Thanks.
Click to expand...
Click to collapse
Cwm had not prevented any OTAs on the shield tablet for me yet.
Sent from my SHIELD Tablet using XDA Free mobile app
Hi,
Thanks for the instructions. I followed the unlocked bootloader one, but now I cant boot. I flashed the modified LTE boot img and now everytime I boot it keeps going into fastboot mode.
Unlocked bootloader
flashed CWM
Booted into CWM and flashed SuperSU Beta
Selected Yes to fix Root
Reboot system
Boot back into fastboot and flash the modified boot.img
Reboot system...............now keeps booting into fastboot.
Please help.
EDIT: I'm an idiot. Unzip the boot.img before you flash it. Problem solved.
layanto said:
Does CWM prevents future OTA? What if I want root but stock recovery? Thanks.
Click to expand...
Click to collapse
You can also restore stock recovery afterward by flashing this
SuperPichu said:
You can also restore stock recovery afterward by flashing this
Click to expand...
Click to collapse
Possibly dumb question, but is the stock recovery on 4.4.2 KK the same as stock recovery on L? If I backup the stock recovery on KK with flashify, can I then restore once I am rooted and on L?
layanto said:
Possibly dumb question, but is the stock recovery on 4.4.2 KK the same as stock recovery on L? If I backup the stock recovery on KK with flashify, can I then restore once I am rooted and on L?
Click to expand...
Click to collapse
You can definitely restore it if you make a backup. I'm actually not sure if they are the same.
Can this be done without a computer?
Jaybenosa said:
Can this be done without a computer?
Click to expand...
Click to collapse
No
Sent from my SHIELD Tablet using XDA Free mobile app
Yah I figured. So I'm pretty much a noob and I'm trying to unlock my bootloader right now but I'm so lost lol
So I failed miserably, accidentally hit reboot system after step 4 so now I'm on lollipop not rooted and no unlocked boot loader nor have a recovery ??
Jaybenosa said:
Yah I figured. So I'm pretty much a noob and I'm trying to unlock my bootloader right now but I'm so lost lol
Click to expand...
Click to collapse
This is how to unlock the bootloader. It will erase all your userdata.
https://developer.nvidia.com/sites/...eld/SHIELD_tab/HowTo-Flash-Recovery-Image.txt
In reading through the other thread, I can't seem to definitively find what I'm looking for.
My Shield has a locked bootloader, but I've installed the OTA. Is my only option to unlock the bootloader and then follow the unlocked bootloader root method? Or is there a way to root only (I'd like to keep stock recovery) with the OTA already installed?
KentuckyHouse said:
In reading through the other thread, I can't seem to definitively find what I'm looking for.
My Shield has a locked bootloader, but I've installed the OTA. Is my only option to unlock the bootloader and then follow the unlocked bootloader root method? Or is there a way to root only (I'd like to keep stock recovery) with the OTA already installed?
Click to expand...
Click to collapse
You will have to unlock. You can restore the stock recovery afterward if you wish
Sent from my SHIELD Tablet using XDA Free mobile app
Does towelroot still work for the LTE devices when moving to lolli?
OK, so I had to unlock my bootloader since I'd already taken the OTA.
Now I'm at this point. I can't seem to get recovery to stick. I've flashed it multiple times in fastboot and it just won't stick. Now, over in the other thread, someone has asked if I've done the "fastboot flash boot boot-root.img" step yet. This confuses me, as that step comes AFTER you flash recovery, then flash SuperSU with CWM. But seeing as how I can't get recovery to stick, I can't flash SuperSU, and that means I can't move on to that step.
So I guess what I'm asking is, can I run "fastboot flash boot boot-root.img" before "fastboot flash recovery recovery.img"? Will that make a difference? Will it brick my tablet?
I'm all out of ideas here.
Locked bootloader and updated to ver 2.0 lollipop.
Hi there.
I have downloaded and installed version 2 lollipop and I would like root to store my games on SD. When checking the root guide it informed me to download update but not install. I have already installed the update and was wandering if they is a way to root my device still.
Kind regards