[Q] HTC One S Root OTA Update Questions - HTC One S

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

Related

[Q] Returning to stock [i9020a]

I just wanted to make sure that I understood the process of returning my phone to stock before I make a mistake.
All I've done since I purchased the phone was root it and unlock the bootloader. I have not loaded any custom roms.
So If I understand this correctly I need to:
1) Flash the Stock Image (which should include the stock recovery?)
2) Use fastboot to lock the bootloader
The reason I'm wanting to return the phone to stock is to receive OTA updates. I never use any apps requiring root, and don't plan on loading any custom roms.
I never did find a 2.3.4 stock image for the I9020A..
you should actually be able to get ota updates no problem. it'll just remove root every time you update.
it's probably not a good idea to lock the bootloader though cause if you ever want to unlock it again in the future you'll have to wipe everything from your phone. your best bet is to just flash stock recovery so you can install the update
i'm pretty sure that works, but hopefully someone else can verify just so you don't get some bad information lol
I heard the same thing about OTA updates. If you're phone is rooted and you're using the original rom, you'll get the update but you'll have to root your phone once again.
I haven't tried this myself so I cannot verify it.
It's just the word on the street, you know!
EraqEE said:
I heard the same thing about OTA updates. If you're phone is rooted and you're using the original rom, you'll get the update but you'll have to root your phone once again.
I haven't tried this myself so I cannot verify it.
It's just the word on the street, you know!
Click to expand...
Click to collapse
you need stock everything, so stock kernel, rom, radio, etc... the op should be fine to update if they flash stock recovery though. rooting is simple from there
dmuntean said:
I just wanted to make sure that I understood the process of returning my phone to stock before I make a mistake.
All I've done since I purchased the phone was root it and unlock the bootloader. I have not loaded any custom roms.
So If I understand this correctly I need to:
1) Flash the Stock Image (which should include the stock recovery?)
2) Use fastboot to lock the bootloader
The reason I'm wanting to return the phone to stock is to receive OTA updates. I never use any apps requiring root, and don't plan on loading any custom roms.
I never did find a 2.3.4 stock image for the I9020A..
Click to expand...
Click to collapse
where can i find a method to return a phone thats unlocked and rooted? any help would be appreciated.
Sent from my Inspire 3G.
bdpyo said:
where can i find a method to return a phone thats unlocked and rooted? any help would be appreciated.
Sent from my Inspire 3G.
Click to expand...
Click to collapse
I would like to do the same, I have a Fido/ATT I9020A and I'm having a hard time finding a stock nandroid backup to restore my phone with...
Anyone?>
bump
Sent from my Inspire 3G.
Here is stock 2.3.4 (GRJ22) with UCKD1 Radio & KA3 Bootloader.. http://dl.dropbox.com/u/7812800/Stock-GRJ22-i9020A-unsigned.zip Flash via ClockworkMod Recovery (due to it being unsigned zip)
I extracted and packaged it from my i9020a (and tested it on there).
how do you recomend flashing?
Sent from my Inspire 3G.
bdpyo said:
how do you recomend flashing?
Sent from my Inspire 3G.
Click to expand...
Click to collapse
Sorry forgot to add that to post... since its unsigned you need to flash via ClockworkMod Recovery.
kibmcz said:
Sorry forgot to add that to post... since its unsigned you need to flash via ClockworkMod Recovery.
Click to expand...
Click to collapse
Thanks kibmcz ! I'm a n00b when it comes to this but when you say flash via ClockworkMod you mean get into clockwork recovery mount the usb, transfer the zip onto the SD card and then <<Install from zip>> ?
Is that the method?
davis2k said:
Thanks kibmcz ! I'm a n00b when it comes to this but when you say flash via ClockworkMod you mean get into clockwork recovery mount the usb, transfer the zip onto the SD card and then <<Install from zip>> ?
Is that the method?
Click to expand...
Click to collapse
Yep that method works
kibmcz said:
Yep that method works
Click to expand...
Click to collapse
Thanks again kibmcz, so I just completed the flash, then did a fastbook oem lock.
Seems to be working fine except for one thing...
When I go into settings and hit Sound I get a Force close when I try and select a new ringtone...
Should I try reflashing again?
davis2k said:
Thanks again kibmcz, so I just completed the flash, then did a fastbook oem lock.
Seems to be working fine except for one thing...
When I go into settings and hit Sound I get a Force close when I try and select a new ringtone...
Should I try reflashing again?
Click to expand...
Click to collapse
Didn't happen on mine (In fact im using a self rooted rom based on that exact stock zip) try doing a wipe in stock recovery.
after flashing that does it take it back to out of box condition?
reason i ask is because i bought a already rooted and unlocked one here from market place and i want to return it to stock firmware, radio, kernel and such to recieve OTA updates and what not.
your info is greatly appreciated
Sent from my Inspire 3G.
bdpyo said:
after flashing that does it take it back to out of box condition?
reason i ask is because i bought a already rooted and unlocked one here from market place and i want to return it to stock firmware, radio, kernel and such to recieve OTA updates and what not.
your info is greatly appreciated
Sent from my Inspire 3G.
Click to expand...
Click to collapse
Using my zip yes... it flashes Bootloader, Radio, Boot, System and on first boot (and any other time recovery changes) Recovery is flashed. All you got to to is lock the bootloader and that wipes user data and usb storage.
hey man i appreciate you coming forward with a solution, ive yet to recieve the phone but wanted to prepare.
my goal is to flash everything back to stock and start completly over whereas i have no clue what method was originally used to root and unlock the bootloader.
when the time comes hope you dont mind a PM if i have any extra questions.
Sent from my Inspire 3G.
Just did the method using the stock ROM provided by kibmcz "thanks BTW!"
Phone is back to stock, working like it did when I first bought it. Had a little trouble with some Force Close issues but did a factory reset/data clear of the cache and all that before re-flashing, and it seems to be working Vanilla!
bdpyo said:
hey man i appreciate you coming forward with a solution, ive yet to recieve the phone but wanted to prepare.
my goal is to flash everything back to stock and start completly over whereas i have no clue what method was originally used to root and unlock the bootloader.
when the time comes hope you dont mind a PM if i have any extra questions.
Sent from my Inspire 3G.
Click to expand...
Click to collapse
Great and thanks DM all you want i don't mind. Oh and i now got stock 2.3.6 (GRK39F) uploaded.
Code:
[B][URL="http://dl.dropbox.com/u/7812800/Stock-GRK39F-I9020a-unsigned.zip"][B]Android 2.3.6/GRK39F/UCKF1 Radio/KA3 Bootloader[/B][/URL][/B]
Works on: I9020A
Unofficial, unsigned, must flash through ClockworkMod Recovery. Contains recovery, radio and bootloader.
kibmcz said:
Great and thanks DM all you want i don't mind. Oh and i now got stock 2.3.6 (GRK39F) uploaded.
Code:
[B][URL="http://dl.dropbox.com/u/7812800/Stock-GRK39F-I9020a-unsigned.zip"][B]Android 2.3.6/GRK39F/UCKF1 Radio/KA3 Bootloader[/B][/URL][/B]
Works on: I9020A
Unofficial, unsigned, must flash through ClockworkMod Recovery. Contains recovery, radio and bootloader.
Click to expand...
Click to collapse
So all I have done to my nexus s is root and cwm and kernel. I can do the ota to 2.3.6 or flash your package?
Running build GTJ61 and I9020AUCKE1 2.3.4 stock.
Sent from my Nexus S using xda premium

Can you restore a nexus s to "factory" settings to receive OTA updates?

Hi Guys, as subject really! Is it possible to get the phone in a "Google" state to pull down updates, obviously meaning the impending ICS one!
B
I'm implying that you're on a custom ROM at the moment. You'll have to flash one of the stock ROM images, then you can get OTA's again.
It doesn't matter if you're rooted or have an unlocked bootloader.
Greetz
frutelaken said:
I'm implying that you're on a custom ROM at the moment. You'll have to flash one of the stock ROM images, then you can get OTA's again.
It doesn't matter if you're rooted or have an unlocked bootloader.
Greetz
Click to expand...
Click to collapse
Hey mate, thankyou for helping. I've not actually received it yet, bought one off ebay and I am just pre-empting - If you flash stock does the root and unlocked bootloader become standard again??
(I'm upgrading from an old Galaxy 3, so am reasonably familiar with flashing, but want a simple life now and am going stock Google )
B
Nope, flashing a stock image will not affect your bootloader being unlocked. You'll have to run the "fastboot oem lock" command to lock the bootloader again. Check one of the turorials here
Greetz
//edit: Actually, I'm suddenly not sure of this. Sunday evenings' got me confused. Please wait for someone else to verify.
Thankyou I'll have a look round
I have been flashing several ROMs using ROM Manager and the bootloader wasn't affected by this. The stock OTAs kept unrooting the phone though.
n00bfuscator said:
I have been flashing several ROMs using ROM Manager and the bootloader wasn't affected by this. The stock OTAs kept unrooting the phone though.
Click to expand...
Click to collapse
That's normal, the OTA's reset the permissions on key folders, effectively SU looses it's execute permissions, removing root. What i do now is download the OTA to the SD card, apply it, re-apply the SU.zip to keep root, modify the restore-recovery script so i can keep CWM, then reboot.
I'm not sure how it's going to go with ICS, but we shall see.

Recommendations on OTA (ATT 4.0.3/4.0/1.73)

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.

How to apply OTA update on Rooted At&t One X

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.

Soft Bricked! (Need help finding RUU)

Hey Everyone!
I've been trying to fix this problem for hours with no luck, and while I've found solutions that have worked for others I can't find one that is specific enough to my situation.
So I just got an HTC One X that is locked to Rogers today from Kijiji, and I love it - great phone. The thing I didn't like was the hoard of stock apps that took up about four pages on the app drawer, so I thought hey, I'll root it and delete them. I didn't have any intention of using any custom ROMs, just wanted superuser permission to delete stock apps. Unlocking went fine (finding the token and what not using the app I found on here), and the rooting seemed to go alright until it turned off and didn't start again. I pulled out the cable from the computer and now things are weird..
I can sometimes get into the hboot, but when I try to just start the phone normally it goes to the HTC splash screen and has red writing telling me "this build is for development purposes only", etc etc. I really wanted to get rid of those stock apps but at this point I just want my phone working again. Am I screwed?
I CANNOT find the RUU that I need ANYWHERE. I've tried flashing both Clockwork Recovery and TWRP, and both are apparently successfully installed, but neither will open for me. This is seriously pushing me towards an iPhone
Thanks in advance.
oot-n-aboot said:
Hey Everyone!
I've been trying to fix this problem for hours with no luck, and while I've found solutions that have worked for others I can't find one that is specific enough to my situation.
So I just got an HTC One X that is locked to Rogers today from Kijiji, and I love it - great phone. The thing I didn't like was the hoard of stock apps that took up about four pages on the app drawer, so I thought hey, I'll root it and delete them. I didn't have any intention of using any custom ROMs, just wanted superuser permission to delete stock apps. Unlocking went fine (finding the token and what not using the app I found on here), and the rooting seemed to go alright until it turned off and didn't start again. I pulled out the cable from the computer and now things are weird..
I can sometimes get into the hboot, but when I try to just start the phone normally it goes to the HTC splash screen and has red writing telling me "this build is for development purposes only", etc etc. I really wanted to get rid of those stock apps but at this point I just want my phone working again. Am I screwed?
I CANNOT find the RUU that I need ANYWHERE. I've tried flashing both Clockwork Recovery and TWRP, and both are apparently successfully installed, but neither will open for me. This is seriously pushing me towards an iPhone
Thanks in advance.
Click to expand...
Click to collapse
Yes, please get an iphone! Redpoint73 resource compilation thread, linked in my signature, has all the RUUs and OTAs you would ever need. Good luck.
Sweet, I found the right RUU but it's a zip file and I'm not able to get into recovery mode on my phone. I can get into hboot but rebooting to recovery from there just shows the HTC splash screen with the "developer only" message" then shuts off again. I've tried installing both Clockwork and TWRP with no luck. Any ideas?
exad said:
Yes, please get an iphone! Redpoint73 resource compilation thread, linked in my signature, has all the RUUs and OTAs you would ever need. Good luck.
Click to expand...
Click to collapse
oot-n-aboot said:
Sweet, I found the right RUU but it's a zip file and I'm not able to get into recovery mode on my phone. I can get into hboot but rebooting to recovery from there just shows the HTC splash screen with the "developer only" message" then shuts off again. I've tried installing both Clockwork and TWRP with no luck. Any ideas?
Click to expand...
Click to collapse
The zip file is an OTA and not an RUU. You would need to extract the recovery from that zip file (may be burried deep). Will be called recovery.img or recovery_signed.img or something to that effect. Fastboot flash recovery recoveryfilename.img then boot to that recovery then install the zip through the phone's stock recovery.
I really appreciate the help but I still can't seem to find the proper RUU. I've tried a few and they all fail. If it helps, the number I get when I typed getvar version-main is: 3.17.631.2
Would someone be able to link me to a download for this particular RUU? Thanks
Edit: Thought I'd update a bit of what I've done. Ive found the one I should need in the list you've provided, but there is no link for download. There is the OTA file but not the RUU. I've been using ARUWizard to try to install the RUU, but any one I've tried so far just says it's not the right one. No other error messages, it just tells me to find the appropriate ROM. I can't understand why this is so difficult to find the right one! It seems like all the other models are readily available. Thanks again!
(This looks like the one, but no download link:
3.17.631.2
File Timestamp: 04/12/12
Publically Seen: 08/01/13
Android: 4.1.1
Kernel: 3.4.10-g240d4d5
hboot: 2.14.0000
radio: 0.23a.32.09.29_10.128.32.34
adsp: 31.1.0.45.0815
wcnss: 1031145
tp_syn3202: 3.2_PR1293981
tz: 001.138.010
sbl1: 001.138.003
sbl2: 001.138.004
sbl3: 001.138.005
OTA: OTA_EVITA_UL_JB_45_S_Rogers_WWE_3.17.631.2_0.23a.3 2.09.29_10.128.32.34a_release_299850qstr7rxdbfuofl 6j.zip (full)
RUU: N/A
Source: evitaul-jb-crc-3.4.10-240d4d5.zip
exad said:
The zip file is an OTA and not an RUU. You would need to extract the recovery from that zip file (may be burried deep). Will be called recovery.img or recovery_signed.img or something to that effect. Fastboot flash recovery recoveryfilename.img then boot to that recovery then install the zip through the phone's stock recovery.
Click to expand...
Click to collapse
Rogers did not release an ruu for that software version. Proceed with the ota the way I explained in my last post or s-off if you want to run the ruu for the older software version.
Sent from my One X using xda app-developers app
For some reason flashing stock recovery doesn't work for me. It says it is successful but when I try to boot to recovery it just goes right back to hboot or sits on the HTC splash screen. I can install TWRP though. Do you know of a nandroid backup for my phone? cid is Roger001
exad said:
Rogers did not release an ruu for that software version. Proceed with the ota the way I explained in my last post or s-off if you want to run the ruu for the older software version.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
oot-n-aboot said:
For some reason flashing stock recovery doesn't work for me. It says it is successful but when I try to boot to recovery it just goes right back to hboot or sits on the HTC splash screen. I can install TWRP though. Do you know of a nandroid backup for my phone? cid is Roger001
Click to expand...
Click to collapse
Fastboot erase cache
Sent from my HTC One X using xda premium
31ken31 said:
Fastboot erase cache
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Try that. Nandroid will not restore your recovery. Only the ROM/kernel/radio files and settings.
I have tried that but unfortunately still can't get into stock recovery. It just goes to the HTC splash and shuts off after a couple of seconds. I know I have the right OTA so if I can get into stock recovery I shouldn't have a problem. Any other suggestions? Am I downloading the wrong version of the recovery?
exad said:
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Try that. Nandroid will not restore your recovery. Only the ROM/kernel/radio files and settings.
Click to expand...
Click to collapse
oot-n-aboot said:
I have tried that but unfortunately still can't get into stock recovery. It just goes to the HTC splash and shuts off after a couple of seconds. I know I have the right OTA so if I can get into stock recovery I shouldn't have a problem. Any other suggestions? Am I downloading the wrong version of the recovery?
Click to expand...
Click to collapse
Extract the recovery from the OTA Zip file. It will be in there somewhere. I have done this myself so I know it works.
exad said:
Extract the recovery from the OTA Zip file. It will be in there somewhere. I have done this myself so I know it works.
Click to expand...
Click to collapse
I have as well and worked like a charm
Sent from my HTC One X using xda premium
Sorry, I forgot to mention, if you are not S-OFF, you need to relock after flashing stock recovery and doing fastboot erase cache.
Hey guys, sorry for the late reply, it was a busy long weekend. Here's where I'm at now. I've managed to install cyanogenmod, which booted up fine and everything looked great, but the touch screen didn't work. After some searching I found it it is because the firmware is too new or something, and to downgrade the touch firmware I would have to S-OFF, which would require me to superCID... and I don't know what any of that is and I'd really just like to get back to stock anyway, so..
I've done what you said. Taken the "recovery.img" out of the OTA file for my phone. I've flashed the recovery, relocked the bootloader and erased the cache. Upon booting to recovery it will either splash the HTC screen then go to a black screen (I used to think it was powering off but it looks like it is on but just not displaying anything). Sometimes it will show a image of a phone with a red exclamation mark with a triangle around it.
I feel like I've royally screwed up this phone and I'd just like to get it back to stock.
Thanks!
Edit: The internet is telling me hold volume up + power to get to recovery from the red triangle, but it just reboots me into the bootloader.
exad said:
Sorry, I forgot to mention, if you are not S-OFF, you need to relock after flashing stock recovery and doing fastboot erase cache.
Click to expand...
Click to collapse
You just need to get into stock recovery. Then you can install that ota zip file. I remember having a hard time getting into it too. I would reflash stock recovery to try to remember how I got to the flash screen but my motherboard is out on rma.
Sent from my Sony Tablet S using xda app-developers app
Just posting in case other people have my problem:
I didn't fix it myself, but a friend did for me. He said it wasn't rooted properly so he basically started from scratch and redid that part of it. There is no RUU file for my phone, but he used to AT&T version and it seems to have worked perfectly. Nothing I've noticed so far has any problems.
Anyway, thanks for all the help guys!
exad said:
You just need to get into stock recovery. Then you can install that ota zip file. I remember having a hard time getting into it too. I would reflash stock recovery to try to remember how I got to the flash screen but my motherboard is out on rma.
Sent from my Sony Tablet S using xda app-developers app
Click to expand...
Click to collapse
oot-n-aboot said:
Just posting in case other people have my problem:
I didn't fix it myself, but a friend did for me. He said it wasn't rooted properly so he basically started from scratch and redid that part of it. There is no RUU file for my phone, but he used to AT&T version and it seems to have worked perfectly. Nothing I've noticed so far has any problems.
Anyway, thanks for all the help guys!
Click to expand...
Click to collapse
Since your friend fixed the issue for you what firmware are you now now. Is it still rooted?
Looks like I have Android version 4.1.1, HTC Sense 4+, and using CleanROM 6.5.0. Is that what you were wondering?
Also, SuperUser is enabled in SuperSU, so that means I'm rooted right?
takylo said:
Since your friend fixed the issue for you what firmware are you now now. Is it still rooted?
Click to expand...
Click to collapse

Categories

Resources