Database Info

[Q] How root RUU 1.85

Im update to 1.85 and now i can't root my phone, help me please...

Currently there is no 1.85 root method..
I'm stuck in the same boat [and theres NO big flags saying "Upgrading to 1.85 means no root unless you do this first!"] and modified my CID from 11111111 [superCID] to the stock one so yeah. We'll either have to wait for the bootloader unlock // A force CID Method // and-or a root method to bypass the 1.85 issue or until a new update comes out with its own method(s).
Some people have had luck doing this though;
http://forum.xda-developers.com/showthread.php?t=1671396
By following the 12th step and attempting to use HTCDev.com.

I've tried everything to no avail on 1.85. Other ICS exploits such as Mempodroid have also been patched.
HELP!

TKTAB911 said:
Currently there is no 1.85 root method..
I'm stuck in the same boat [and theres NO big flags saying "Upgrading to 1.85 means no root unless you do this first!"] and modified my CID from 11111111 [superCID] to the stock one so yeah. We'll either have to wait for the bootloader unlock // A force CID Method // and-or a root method to bypass the 1.85 issue or until a new update comes out with its own method(s).
Some people have had luck doing this though;
http://forum.xda-developers.com/showthread.php?t=1671396
By following the 12th step and attempting to use HTCDev.com.
Click to expand...
Click to collapse
...

TKTAB911 said:
...
Click to expand...
Click to collapse
I was agreeing with you... I was also just saying that instead of waiting around, I've tried all of the other ICS exploits to see if anything was overlooked.

TKTAB911 said:
theres NO big flags saying "Upgrading to 1.85 means no root unless you do this first!"
Click to expand...
Click to collapse
True, the thread in which the RUU is posted has no such warning. But my index thread (sticky at the top of Development) is your friend. I even put it in boldface:
[STOCK] AT&T RUU_Evita_UL_Cingular_US-1.85.502 Warning: Can only be rooted if SuperCID before running this RUU. Details here
Also, as a rule, never update to a new official firmware, until you have done thorough research on whether a root method exists or still works. Its fairly common for new official ROMs to break existing root methods.

Root 1.85
crazydai said:
Im update to 1.85 and now i can't root my phone, help me please...
Click to expand...
Click to collapse
Could we try to reinstall RUU 1.73... or 1.82...? I have not attempted this but wondering if we could do that then root and so on?
Thanks,
David

djcortes said:
Could we try to reinstall RUU 1.73... or 1.82...? I have not attempted this but wondering if we could do that then root and so on?
Thanks,
David
Click to expand...
Click to collapse
I've tried doing this to no avail. I've tried both. I've even extracted the rom.zip and tried to replace it but I still the get the 140 bootloader error.

robertatl said:
I've tried doing this to no avail. I've tried both. I've even extracted the rom.zip and tried to replace it but I still the get the 140 bootloader error.
Click to expand...
Click to collapse
Well that blows!
thanks for answering the question though

robertatl said:
I've tried doing this to no avail. I've tried both. I've even extracted the rom.zip and tried to replace it but I still the get the 140 bootloader error.
Click to expand...
Click to collapse
What about replacing System.IMG inside of the %temp% folder with System.IMG from 1.82 with the /data/local/tmp exploit?

mbaran said:
What about replacing System.IMG inside of the %temp% folder with System.IMG from 1.82 with the /data/local/tmp exploit?
Click to expand...
Click to collapse
hmm.. I would be willing to try this but would need some guidance with the exploit.
meaning how to do it!
-David

djcortes said:
hmm.. I would be willing to try this but would need some guidance with the exploit.
meaning how to do it!
-David
Click to expand...
Click to collapse
I don't even know if it's possible, but when you start the RUU in windows it extracts it's whole working set of data to %temp% on Windows.
No idea if one System.IMG could be substitutes for the other, since it's all signed.

djcortes said:
hmm.. I would be willing to try this but would need some guidance with the exploit.
meaning how to do it!
-David
Click to expand...
Click to collapse
I just tried that exploit as well but it fails due to permission denied error

redpoint73 said:
True, the thread in which the RUU is posted has no such warning. But my index thread (sticky at the top of Development) is your friend. I even put it in boldface:
[STOCK] AT&T RUU_Evita_UL_Cingular_US-1.85.502 Warning: Can only be rooted if SuperCID before running this RUU. Details here
Also, as a rule, never update to a new official firmware, until you have done thorough research on whether a root method exists or still works. Its fairly common for new official ROMs to break existing root methods.
Click to expand...
Click to collapse
You did put a warning in the thread, but it's misleading and lead me to be stuck in stock 1.85. May I suggest that you re-word it "Can only be rooted if SuperCID -> Unlocked -> Relocked" so other people don't get confused. I set up SuperCID but did not unlock, and that's what screwed me.

red3gunner said:
You did put a warning in the thread, but it's misleading and lead me to be stuck in stock 1.85. May I suggest that you re-word it "Can only be rooted if SuperCID -> Unlocked -> Relocked" so other people don't get confused. I set up SuperCID but did not unlock, and that's what screwed me.
Click to expand...
Click to collapse
Can't you just unlock the bootloader now, since you already have SuperCID?
If not, that's news to me, and the reason my index thread is worded the way it is.

Yes, that worked! Thanks, sorry for the noobism.

red3gunner said:
Yes, that worked! Thanks, sorry for the noobism.
Click to expand...
Click to collapse
Ha, no worries! I was confused there for a second.

Need help with att one x rooted

I just rooted my htc one x att model and after rooting it, it rebooted. The phone couldnt get passed the one and beats audio startup screen !
I also didnt get to get my bootloader unlocked because of this, and i also dont have a backup. I need help just getting it back to the factory default. Go easy on my im a newbie Thanks!

Lilsir64 said:
I just rooted my htc one x att model and after rooting it, it rebooted. The phone couldnt get passed the one and beats audio startup screen !
I also didnt get to get my bootloader unlocked because of this, and i also dont have a backup. I need help just getting it back to the factory default. Go easy on my im a newbie Thanks!
Click to expand...
Click to collapse
Download and flash the 1.85 RUU from here:
http://www.filefactory.com/file/2oy....09.12_10.86.32.08L_release_262092_signed.exe
(its an exe...run it and it will give you instructions on what to do)

aooga said:
Download and flash the 1.85 RUU from here:
(its an exe...run it and it will give you instructions on what to do)
Click to expand...
Click to collapse
it says i have to upgrade to premium to download

Lilsir64 said:
it says i have to upgrade to premium to download
Click to expand...
Click to collapse
Oh SORRY!!! let me get you another one
HERE: http://d-h.st/bS4

ok well i can try to unlock the bootloader could that help me any? PLEASE HELP MEEEEEE!

Lilsir64 said:
ok well i can try to unlock the bootloader could that help me any? PLEASE HELP MEEEEEE!
Click to expand...
Click to collapse
no no no...dont do that. Just run the RUU that i gave you for 1.85. That will get you a working non rooted phone. Then you can follow the root instructions for 1.85 that are posted here, then you can use superCID to unlock the bootloader.
EDIT: Sent you a PM too

Lilsir64 said:
ok well i can try to unlock the bootloader could that help me any? PLEASE HELP MEEEEEE!
Click to expand...
Click to collapse
RUU can only be run with bootloader locked or relocked. So do not unlock it.

thanks guys but can you give me the step by step on what to do i have the ruu file. tell me what to download and what to do, much appreciated can this brick my phone?

Lilsir64 said:
thanks guys but can you give me the step by step on what to do i have the ruu file. tell me what to download and what to do, much appreciated can this brick my phone?
Click to expand...
Click to collapse
Honestly its really simple. Download the file in the link i gave you. Run it in windows. Let it install. Connect your phone and follow the on screen instructions. This wont brick your phone if you follow the directions given to you when you run the exe file.

Can't Get Back To Unrooted Stock No Matter What I Try

Last week I went back to stock to familiarize myself with the process (which unfortunately brought my HBoot to 1.14). I also decided to try out TWRP when I rooted again. But before I could finish up I hit a button in TWRP that didn't need any confirmation. I don't remember which button because it did what it did quicker than I could notice. After that I couldn't even flash a ROM because I couldn't mount the sd card and whatever happened erased everything on my phone but I ended up figuring that out.Now I'm on ViperOneS but I can't unroot. I can't flash either of the RUU (Error 155) that are for T-Mobile US I even changed my CID to 11111111 but no dice(and yes I did flash the stock recovery and boot before relocking). The only thing I can do to get close to unrooted stock is flash the nandroid of a rooted stock ROM. Now I haven't mentioned every method I've tried, so before I start getting bashed for not searching, I want to mention that I've been at this for about 4 days and I have tried EVERYTHING that I've found on XDA and other forums but nothings worked. Is it my HBoot that prevents from doing anything? Should get another One S? Or should I just be thankful that I have a functioning phone?
Sorry for the long winded post but I wanted to make sure I put in as much detail as possible.

antny said:
Last week I went back to stock to familiarize myself with the process (which unfortunately brought my HBoot to 1.14). I also decided to try out TWRP when I rooted again. But before I could finish up I hit a button in TWRP that didn't need any confirmation. I don't remember which button because it did what it did quicker than I could notice. After that I couldn't even flash a ROM because I couldn't mount the sd card and whatever happened erased everything on my phone but I ended up figuring that out.Now I'm on ViperOneS but I can't unroot. I can't flash either of the RUU (Error 155) that are for T-Mobile US I even changed my CID to 11111111 but no dice(and yes I did flash the stock recovery and boot before relocking). The only thing I can do to get close to unrooted stock is flash the nandroid of a rooted stock ROM. Now I haven't mentioned every method I've tried, so before I start getting bashed for not searching, I want to mention that I've been at this for about 4 days and I have tried EVERYTHING that I've found on XDA and other forums but nothings worked. Is it my HBoot that prevents from doing anything? Should get another One S? Or should I just be thankful that I have a functioning phone?
Sorry for the long winded post but I wanted to make sure I put in as much detail as possible.
Click to expand...
Click to collapse
It's most likely your hboot that prevents the RUU's from working. You can only use a RUU that contain a hboot of 1.14 or higher.
Since your signature says HBoot: 1.14 & Radio: 1.08ts.50.02.16_10.08e.50.04L. I assume you updated via the T-mobile US OTA, is that correct?
What's interesting is that other hboots in the 1.14 family are listed as 1.14.0002 but the T-mobile OTA the hboot is labeled 1.14.0004. I haven't seen anyone state if this is will prevent "downgrading" to 1.14.002 and don't feel like finding out myself.
What RUU are you trying?

dc211 said:
It's most likely your hboot that prevents the RUU's from working. You can only use a RUU that contain a hboot of 1.14 or higher.
Since your signature says HBoot: 1.14 & Radio: 1.08ts.50.02.16_10.08e.50.04L. I assume you updated via the T-mobile US OTA, is that correct?
What's interesting is that other hboots in the 1.14 family are listed as 1.14.0002 but the T-mobile OTA the hboot is labeled 1.14.0004. I haven't seen anyone state if this is will prevent "downgrading" to 1.14.002 and don't feel like finding out myself.
What RUU are you trying?
Click to expand...
Click to collapse
Yeah it was the T-Mobile OTA, worst decision ever... I've tried both the 1.84 and 1.53 T-Mo RRU's multiple times and since I changed my CID I've thought of trying another carriers but I don't want to possibly make things worse.
Sent from my HTC One S using xda premium

antny said:
Yeah it was the T-Mobile OTA, worst decision ever... I've tried both the 1.84 and 1.53 T-Mo RRU's multiple times and since I changed my CID I've thought of trying another carriers but I don't want to possibly make things worse.
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
I feel your pain. I updated with the OTA that moved us to hboot 1.13 before anyone said they changed the security :crying:.
The 1.84 and 1.53 RUU's wouldn't work for sure. 1.84 has the 1.13 hboot and 1.53 has the 1.09 hboot. Your only hope of using an RUU at this time is one of the Europe RUU's. The good news is that you already moved to supercid so you got that out of the way.
The ones that might work are the ones labeled "RUU_Ville_U_ICE_40_S_Europe_2.xxxxxx"
Here you can get the 2.21 RUU I can't recall if it's the 4.0.4 based one though. Not really sure where to get the other ones as file factory changed their download rules.
http://www.mediafire.com/?xlklqrlljb2zt#r9489rkr82wh2
You might need to click the "mainver error fix" on the on the All-in-one tool kit to get them to work since you would be downgrading the rom.
And if you do use that RUU from mediafire you can go here and click the thanks button for SneakyGhost for putting up the RUU for you to download.
http://forum.xda-developers.com/showpost.php?p=32262143&postcount=153
Then go here and click the thanks button for Football since he's the only source of RUU's there is.
http://forum.xda-developers.com/showpost.php?p=23542379&postcount=1
Good luck.

I've downgraded from 2.31 to 2.21, I know both have HBOOT 1.14 but not exactly sure if they have the exact identical numbers after the 1.14.
HTC One S
---------- Post added at 08:38 AM ---------- Previous post was at 08:34 AM ----------
antny said:
Yeah it was the T-Mobile OTA, worst decision ever... I've tried both the 1.84 and 1.53 T-Mo RRU's multiple times and since I changed my CID I've thought of trying another carriers but I don't want to possibly make things worse.
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
2.21 RUU worked better for me than the T-Mobile stock Rom, it doesn't have w Wi-Fi calling do if that's a must for you only hope is to wait for the T-Mobile 2.35 RUU to be released.
HTC One S

dc211 said:
I feel your pain. I updated with the OTA that moved us to hboot 1.13 before anyone said they changed the security :crying:.
The 1.84 and 1.53 RUU's wouldn't work for sure. 1.84 has the 1.13 hboot and 1.53 has the 1.09 hboot. Your only hope of using an RUU at this time is one of the Europe RUU's. The good news is that you already moved to supercid so you got that out of the way.
The ones that might work are the ones labeled "RUU_Ville_U_ICE_40_S_Europe_2.xxxxxx"
Here you can get the 2.21 RUU I can't recall if it's the 4.0.4 based one though. Not really sure where to get the other ones as file factory changed their download rules.
http://www.mediafire.com/?xlklqrlljb2zt#r9489rkr82wh2
You might need to click the "mainver error fix" on the on the All-in-one tool kit to get them to work since you would be downgrading the rom.
And if you do use that RUU from mediafire you can go here and click the thanks button for SneakyGhost for putting up the RUU for you to download.
http://forum.xda-developers.com/showpost.php?p=32262143&postcount=153
Then go here and click the thanks button for Football since he's the only source of RUU's there is.
http://forum.xda-developers.com/showpost.php?p=23542379&postcount=1
Good luck.
Click to expand...
Click to collapse
I've thanked Football and gone to the link you provided but I don't get the whole Pt.1,2 and 3 thing. What am I supposed to do with that?
Edit: All good, just got it from the Dropbox link.... T-Mobile and Easy Tether don't mix.
fmedrano1977 said:
I've downgraded from 2.31 to 2.21, I know both have HBOOT 1.14 but not exactly sure if they have the exact identical numbers after the 1.14.
HTC One S
---------- Post added at 08:38 AM ---------- Previous post was at 08:34 AM ----------
2.21 RUU worked better for me than the T-Mobile stock Rom, it doesn't have w Wi-Fi calling do if that's a must for you only hope is to wait for the T-Mobile 2.35 RUU to be released.
HTC One S
Click to expand...
Click to collapse
I don't really care about wifi calling, cool feature but I hardly use it. Is it 4.0.4 and Sense 4.1 though? It wouldnt stop me from using it if it wasn't but I'm just curious haha.

4.0.4 and Sense 4.0
HTC One S

fmedrano1977 said:
4.0.4 and Sense 4.0
HTC One S
Click to expand...
Click to collapse
Cool Cool Cool thanks

Ah! Great success. I'm now running the European 2.21 RUU and it's great. Thanks again guys. Hopefully if someone's in the same position as I was they'll find this useful.
Sent from my HTC One S using xda premium

antny said:
Ah! Great success. I'm now running the European 2.21 RUU and it's great. Thanks again guys. Hopefully if someone's in the same position as I was they'll find this useful.
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
Glad it worked out for you.

antny said:
Ah! Great success. I'm now running the European 2.21 RUU and it's great. Thanks again guys. Hopefully if someone's in the same position as I was they'll find this useful.
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
One last thing I did after installing that RUU was edit the build.prop to match some lines from the T-Mobile one:
ro.ril.hsdpa.category=24
ro.ril.hsupa.category=6
ro.ril.hsxpa=4
ro.ril.fast.dormancy.rule=2
ro.ril.radio.svn=1
Make sure those match, these have given me the fastest DL speeds.
HTC One S

Yes! Thank you. This seems to be what I'm looking for. You can see the question I posted recently about this similar issue. But I also don't understand the part 1, 2, and 3 thing. Help?

DoogleDood said:
Yes! Thank you. This seems to be what I'm looking for. You can see the question I posted recently about this similar issue. But I also don't understand the part 1, 2, and 3 thing. Help?
Click to expand...
Click to collapse
What are you trying to do?
HTC One S

Nevermind I got it! I wasn't sure if the 3 "parts" of the EU RUU needed to be combined or... what. But upon extracting I found the full file.

fmedrano1977 said:
One last thing I did after installing that RUU was edit the build.prop to match some lines from the T-Mobile one:
ro.ril.hsdpa.category=24
ro.ril.hsupa.category=6
ro.ril.hsxpa=4
ro.ril.fast.dormancy.rule=2
ro.ril.radio.svn=1
Make sure those match, these have given me the fastest DL speeds.
HTC One S
Click to expand...
Click to collapse
Why thank you sir.

antny said:
Why thank you sir.
Click to expand...
Click to collapse
Please someone help me I just flashed axiom rom wifif won't work I tryd other roms too, wifi won't work how can I fix this ??
Do I need to flash a RUU I am new to this. I had th latest tmo update before I rooted the phone people says that's why wifi won't work in other thread.
Please help me fix this !!!

johnyguy said:
Please someone help me I just flashed axiom rom wifif won't work I tryd other roms too, wifi won't work how can I fix this ??
Do I need to flash a RUU I am new to this. I had th latest tmo update before I rooted the phone people says that's why wifi won't work in other thread.
Please help me fix this !!!
Click to expand...
Click to collapse
I'm honestly not to sure on how to fix this. I've searched it before I went back to stock (going back to stock is a definite fix) and couldn't find much on it. I'm sure something has developed from it by now though. Actually :: navigates to another tab:: http://forum.xda-developers.com/showthread.php?t=1900644 if it's compatible with your ROM, this kernel claims to have a fix for wifi and sound (I don't know what the sound issue is all about) but try that, it might work. But most importantly search, read, search and read some more, especially since you're new to this, I've rooted many phones and I still had problems with the One S. Good luck!

Found RUU 2.35 and finally got my phone back to stock. I posted info here:
http://forum.xda-developers.com/showthread.php?t=1941402

sylvestk said:
Found RUU 2.35 and finally got my phone back to stock. I posted info here:
http://forum.xda-developers.com/showthread.php?t=1941402
Click to expand...
Click to collapse
That release gives you the no data when screen is off issue.
HTC One S

Correct 1.85RUU / Downgrade?

Will someone post the correct 1.85 RUU for this phone, or send a link to it? Having a little trouble trying to find it. Or maybe I did?
RUU_Evita_Cingular_US_1.85.502.3_R2_Radio_0.71.32.09.12_10.86.32.08L_release_262092_signed
I'm trying to downgrade via this guide: http://forum.xda-developers.com/showpost.php?p=33914948&postcount=65
Edited the mmcblk0p23 just fine, placed it back on my phone and tried to run the RUU but it says that it wasn't able to run, which leads me to the conclusion it's the wrong RUU.
Any input would be fantastic.
Edit: just tried again and this is the error that I am getting.

Here: http://forums.team-nocturnal.com/showthread.php/1005-RUU-One-X-XL-LTE-RUU-s
Here: http://forum.xda-developers.com/showthread.php?t=1670238
Or also here: http://forum.xda-developers.com/showthread.php?t=1671237
I believe that since you are editing the version number on your phone, it shouldn't matter what RUU version, as long as the CID is correct (which SuperCID should also render a moot point).

redpoint73 said:
Here: http://forums.team-nocturnal.com/showthread.php/1005-RUU-One-X-XL-LTE-RUU-s
Here: http://forum.xda-developers.com/showthread.php?t=1670238
Or also here: http://forum.xda-developers.com/showthread.php?t=1671237
I believe that since you are editing the version number on your phone, it shouldn't matter what RUU version, as long as the CID is correct (which SuperCID should also render a moot point).
Click to expand...
Click to collapse
Well, quick on the draw with 3 links... I have the correct one. Now it's just a matter of finding out why it's not working. I'll look at my CID and see what's going on.

Did you reboot into fast boot and relock the boot loader after applying the edit?

Im trying this right now but my hex file is all zeros? Why is this and what should I do to resolve this?

absolutelygrim said:
Did you reboot into fast boot and relock the boot loader after applying the edit?
Click to expand...
Click to collapse
Yeah. Ran the 2.20 RUU just fine

mlaws90 said:
Im trying this right now but my hex file is all zeros? Why is this and what should I do to resolve this?
Click to expand...
Click to collapse
The place you have to edit will be on the right side, You'll find the line 0x0a0 on the left.

Myrder said:
The place you have to edit will be on the right side, You'll find the line 0x0a0 on the left.
Click to expand...
Click to collapse
Screenshot:
Is this all I do?:

mlaws90 said:
Is this all I do?
Click to expand...
Click to collapse
Yeah
Wait, that's your mmcblk0p23? That's wrong, that should have your CID and Clearimage what not above the 0x0a0 line...
Grim, what do?

Myrder said:
Yeah
Wait, that's your mmcblk0p23? That's wrong, that should have your CID and Clearimage what not above the 0x0a0 line...
Grim, what do?
Click to expand...
Click to collapse
Yeah, I only have the unlocked bootloader, not SuperCID, I THINK, I did it a long time ago, I got the phone on release day. Could this be why? I am getting an RUU Error 154 or 155 I think why I do try it it will go about 2 min then fail.

mlaws90 said:
I only have the unlocked bootloader, not SuperCID, I did it a long time ago, I got the phone on release day. Could this be why? I am getting an RUU Error 154 or 155 I think why I do try it it will go about 2 min then fail.
Click to expand...
Click to collapse
Oh, that makes sense.. I got the phone two weeks after release, and finally decided to root about 3 weeks ago-ish? so me being dumb I didn't even think to look here before I did the OTA update from AT&T. So I had to do the x factor exploit to get rooted. That might be why yours isn't like mine...? I'm not 100% sure on that one.

mlaws90 said:
Yeah, I only have the unlocked bootloader, not SuperCID, I THINK, I did it a long time ago, I got the phone on release day. Could this be why? I am getting an RUU Error 154 or 155 I think why I do try it it will go about 2 min then fail.
Click to expand...
Click to collapse
That was the same way mine was. I got the 155 error. Going to run some errands after I get my phone back working again.. and give it another go later.

mlaws90 said:
Yeah, I only have the unlocked bootloader, not SuperCID, I THINK, I did it a long time ago, I got the phone on release day.
Click to expand...
Click to collapse
You can't have an unlocked bootloader without SuperCID on the AT&T branded version. Or possibly another CID besides the AT&T CID, since AT&T's CID is not allowed on HTCDev.com.

Should look like this

absolutelygrim said:
Should look like this
Click to expand...
Click to collapse
But why doesnt mine look like that , can someone upload a mmcblk0p23 for me to use, if that is possible. Mine is all Zeros and I get the 154 or 155 error on RUU.

mlaws90 said:
But why doesnt mine look like that , can someone upload a mmcblk0p23 for me to use, if that is possible. Mine is all Zeros and I get the 154 or 155 error on RUU.
Click to expand...
Click to collapse
Try extracting p23 with your phone plugged into a computer and USB debugging on

I'll give this another go later tonight, If it doesn't work I'll just downgrade my hboot and leave it alone. lol.

Myrder said:
I'll give this another go later tonight, If it doesn't work I'll just downgrade my hboot and leave it alone. lol.
Click to expand...
Click to collapse
I drowngraded hboot, changed main version and then ran the RUU just now with no problems. Weird that it isn't working for you.

mbh87 said:
I drowngraded hboot, changed main version and then ran the RUU just now with no problems. Weird that it isn't working for you.
Click to expand...
Click to collapse
First time I got ahead of myself and didn't save the mmcblk0p23... The next time, idk wtf happened. I'll downgrade hboot in a bit and then try again to see what that will do.

Myrder said:
First time I got ahead of myself and didn't save the mmcblk0p23... The next time, idk wtf happened. I'll downgrade hboot in a bit and then try again to see what that will do.
Click to expand...
Click to collapse
If you tried running it over the top of 2.20 without downgrading hboot then that would be a problem too.

Need help finding correct RUU to return to stock

I'd like to return to stock JB for moonshine S-OFF, and the software version that was last installed before I rooted was 3.14.531.17 710RD. This was the small update that was released to fix the battery drain after the release of JB for the One S. It was released right after 3.14.531.11, which I see an RUU for. My question is: Can I use the 3.14.531.11 RUU (detailed RUU name: RUU_Ville_U_JB_45_S_TMOUS_3.14.531.11_Radio_1.13.50.05.31_10.30.50.08L_release_309489_signed_ICS_2) even though I upgraded, before rooting and installing CM10.1, to 3.14.531.17? All other relevant information matches.
Thanks.
EDIT: Nevermind, stupid question. Of course that number denotes the software version so I'll be fine for S-OFF as long as I don't OTA upgrade to 3.14.531.17.

can someone confirm this? been trying to find info on this, having no luck.

I don't know if you need them to match but I do know here is the link for the last updates RUU

noknife said:
can someone confirm this? been trying to find info on this, having no luck.
Click to expand...
Click to collapse
Yes, this is correct. Use that RUU.exe to return to stock, and it will also work when using Moonshine.
That RUU.exe is for U.S. tmobile users.

tivofool said:
Yes, this is correct. Use that RUU.exe to return to stock, and it will also work when using Moonshine.
That RUU.exe is for U.S. tmobile users.
Click to expand...
Click to collapse
Thanks for the info. Would have responded sooner but didn't notice your response till now. still quite knew to android (haven't even owned mine a month) , so have been reading A LOT.. You knew exactly what I was trying to achieve there. Success!! Got s-off, and supercid. Running MaximusHD 10.0.0 right now. One more quick question though if you don't mind. Can there be issues switching between mods, as long as I don't go ruu obviously. Thanks for your time.

noknife said:
snipped.... Can there be issues switching between mods, as long as I don't go ruu obviously. Thanks for your time.
Click to expand...
Click to collapse
Mods? I don't use any mods on Maximus, so I don't know about that.
If you mean switching between ROMs when you have Maximus installed, then yes, you need to downgrade your firmware to try any other rom after Maximus is installed.

tivofool said:
Mods? I don't use any mods on Maximus, so I don't know about that.
If you mean switching between ROMs when you have Maximus installed, then yes, you need to downgrade your firmware to try any other rom after Maximus is installed.
Click to expand...
Click to collapse
ha, yeah meant roms, still getting used to the auto correct. not only first android, first smart phone.ha. that's the answer i was looking for. thanks for reading between my clumsiness, think i'll leave her alone for now then. it's easy enough so far, but all it takes is once. thanks for the info