Related
Hi folks,
I've got a T-Mobile branded Sensation, no idea how long they will take to get the 2.3.4 update out, probably months.
I want to S-OFF, Super CID etc and flash something else or just use a Euro RUU.
Problem is, for warranty purposes, I need to back up my current rom or obtain the T-Mobile RUU.
Is there anyway I can dump this rom first?
I've checked the big list of roms for the Sensation, lots of US ones there but nothing for T-Mobile Uk.
Thanks
Backup stock ROM:
1. S-OFF
2. Install CWM
3. Backup with CWM
Job Done!
Restore stock ROM:
1. Restore backup
2. Flash stock recovery
3. Flash stock HBOOT
4. Run S-ON command via adb
Obviously the ROM you restore will have all your personal data so a hard reset after making sure it boots up would be wise to go back to a 100% 'out the box' state
i,m uploading the official TMO uk 1.34 RUU now link to follow
link
http://dl.dropbox.com/u/38694724/RU...0U_10.51.9007.27_M3_release_196473_signed.exe
Where'd you get that?
west2cool said:
i,m uploading the official TMO uk 1.34 RUU now link to follow
Click to expand...
Click to collapse
That's excellent, cheers!!! Definately UK?
It would have to be as the T-Mobile US ones are 1.27/1.29
EddyOS said:
It would have to be as the T-Mobile US ones are 1.27/1.29
Click to expand...
Click to collapse
Would make life alot easier if it is the real deal.
Very true but I'd still backup your ROM as it stands anyway before flashing anything new
EddyOS said:
Where'd you get that?
Click to expand...
Click to collapse
got it off a chinese website, i was hunting around
One i'm specifically after is 1.34.110.1
If you give me a link I can re-host it pretty quick, i've got an 8Mbit upload speed.
Arthur Hucksake said:
One i'm specifically after is 1.34.110.1
If you give me a link I can re-host it pretty quick, i've got an 8Mbit upload speed.
Click to expand...
Click to collapse
link in my first post, dont forget thank
Thanks dude.
If this is the real deal, legit one, then we're onto a winner.
I got a "communications were interrupted" error when using Revolutionary.
Rebooted with vol down, it's showing me as SHIP S-OFF
Ok to assume that it's all ok anyway?
I had this too, run it 3 times and eventually it will say it's done. I did report this on their feedback on the website as well
When I boot up with vol down, it is showing Revolutionary at the top and S-OFF.
Copied the PG58IMG 4.0.1.4 updated over, went into HBoot and it flashed.
Reboot, deleted the PG58IMG off the SD card.
Reboot, back into the bootloader screen and it's allowed me to run clockwork, so now done a full back up which has just finished.
All I want to do next is install the stock European 2.3.4 rom (RUU_Pyramid_HTC_Europe_1.45.401.2), so I assume the next step is to change CID?
Thing is, I want to be able to use future OTA updates with this rom. Am I right in saying that whatever ID I set it to is what updates I will get?
Cheers
Yeah, change CID to HTC__001 and then you're completely unbranded. OTA's should also go through without issue too
Awesome. Job done. CiD change, installed the european rom and i'm now 2.3.4
Bootloader is showing ***locked*** but I aint worried about that.
That's the new HBOOT, you can still use Revolutionary to S-OFF it again if need be (I personally re-flashed the 1.17.0011 HBOOT back as I didn't like the LOCKED message)
EddyOS said:
That's the new HBOOT, you can still use Revolutionary to S-OFF it again if need be (I personally re-flashed the 1.17.0011 HBOOT back as I didn't like the LOCKED message)
Click to expand...
Click to collapse
I don't understand why it still says S-OFF at the top. lol
Because it does, but it's not technically S-OFF - I tried to flash a different HBOOT and it didn't work until I re-ran Revo
Hey guys,
I just want to know, if my thoughts are true:
Im owning a Sensation 4G from Bell (Canada). In general it takes more time until an update will reach my phone, because it has to be adapted by the carrier.
As far as I know, if I had a rom with no branding, I mean a original stock rom of HTC, updates will be recieved earlier.
Is it possible, to change to rom from bell to an original rom of HTC without branding?
I think, it does, but would I be able to get official OTA updates, too? Do I have to change the CID for this?
Thank you in advance
@@RON
@@RON said:
Hey guys,
I just want to know, if my thoughts are true:
Im owning a Sensation 4G from Bell (Canada). In general it takes more time until an update will reach my phone, because it has to be adapted by the carrier.
As far as I know, if I had a rom with no branding, I mean a original stock rom of HTC, updates will be recieved earlier.
Is it possible, to change to rom from bell to an original rom of HTC without branding?
I think, it does, but would I be able to get official OTA updates, too? Do I have to change the CID for this?
Thank you in advance
@@RON
Click to expand...
Click to collapse
Better if you superCID to prevent headaches (I guess you are S-Off already).
Chose a RUU close to the one you have now.
You won't lose S-OFF but:
- will lose root (if you are rooted)
- will lose personal settings and apps, but you can download again from market.
Hope it helped.
Or you can just wait for a dev to release a Rom based off the new update
Sent from my insertcoined Sensation 4G with Beats Audio
kualmente said:
Better if you superCID to prevent headaches (I guess you are S-Off already).
Chose a RUU close to the one you have now.
Click to expand...
Click to collapse
Hehe, thank you, but you´re wrong, I´m still S-ON
I´m not dealing with S-OFF as long as enough. At first I want to gather information, befor I do this
Previously I had a HD2. HSPL (S-OFF) and flashing a custom rom, was very easy. I my opinion, with the Sensation it´s a bit more tricky xD
Is this correct, if I flash a stock rom, it will not change the CID?
In case of warranty, I have to set the CID to the default value?
Can anyone tell me, where I can find the stock rom from Bell, if I would go back to it?
@@RON said:
Hehe, thank you, but you´re wrong, I´m still S-ON
I´m not dealing with S-OFF as long as enough. At first I want to gather information, befor I do this
Previously I had a HD2. HSPL (S-OFF) and flashing a custom rom, was very easy. I my opinion, with the Sensation it´s a bit more tricky xD
Is this correct, if I flash a stock rom, it will not change the CID?
In case of warranty, I have to set the CID to the default value?
Can anyone tell me, where I can find the stock rom from Bell, if I would go back to it?
Click to expand...
Click to collapse
I made a search for you (but you should do that ). Found it here
Your RUU should be 1.35.666.1
So I guess that stock RUU is the first on this list HERE (check in settings - about phone if it is correct).
What is your current CID btw?
kualmente said:
I made a search for you (but you should do that ). Found it here
Your RUU should be 1.35.666.1
What is your current CID btw?
Click to expand...
Click to collapse
This first shows me just the users manual and quick start guide to download :/
And it´s not correct, my current RUU is 1.45.666.5
Some days ago, I found this list, but does not found this appropriate RUU. The search term "bell" does not found it, but "bm" xD
My current CID is BM___001
@@RON said:
This first shows me just the users manual and quick start guide to download :/
And it´s not correct, my current RUU is 1.45.666.5
Some days ago, I found this list, but does not found this appropriate RUU. The search term "bell" does not found it, but "bm" xD
My current CID is BM___001
Click to expand...
Click to collapse
Ever tought that "BM" stays for Bell Mobile (or Mobility)? Your RUU is the 2nd on the list in such case. Should be newer than the first
kualmente said:
Ever tought that "BM" stays for Bell Mobile (or Mobility)? Your RUU is the 2nd on the list in such case.
Click to expand...
Click to collapse
Afaik "BM" stands for Bell Mobility. It´s true, I have the 2nd RUU in this list
Recall my question:
Is this correct, if I flash a stock rom, it will not change the CID?
In case of warranty, I have to set the CID to the default value?
Click to expand...
Click to collapse
Flashing an RUU doesn't change the CID
Find my post in general
Sent from my HTC Sensation 4G using xda premium
Your thread is about bootloops, how will it help someone debrand their phone? Serious question
The OP just needs to Google 'debrand htc sensation' and they'll get all the info they need (or even search the same terms on here)
Just a small update; meanwhile I set my bootloader to S-Off (yay xD).
Do I have to flash a custom (non-stock) recovery?
Why respectively for what I have to flash a custom recovery. Only for backup and restore my phone?
@@RON said:
Do I have to flash a custom (non-stock) recovery?
Why respectively for what I have to flash a custom recovery. Only for backup and restore my phone?
Click to expand...
Click to collapse
I would be very happy if someone could answer my questions
@@RON said:
Just a small update; meanwhile I set my bootloader to S-Off (yay xD).
Do I have to flash a custom (non-stock) recovery?
Why respectively for what I have to flash a custom recovery. Only for backup and restore my phone?
Click to expand...
Click to collapse
you don't have to flash a custom recovery for RUU, and you only need a custom recovery if you're gonna be flashing different roms or for backup and restoring
Thanks
What kind of backup and restore can I do? backing up systemfiles or the complete phone? (to which target? sd-card?)
Sent from my HTC-Z710a using xda app-developers app
@@RON said:
Thanks
What kind of backup and restore can I do? backing up systemfiles or the complete phone? (to which target? sd-card?)
Sent from my HTC-Z710a using xda app-developers app
Click to expand...
Click to collapse
You can do the complete phone, anything that's in the Rom you're using, and yes it saves it to the sd card
Assuming I set my CID to superCID and flash an unbranded stock ROM, is it possible to get OTA updates with superCID set?
Or should I set it to a normal value e.g. HTC__001 (appropriate to the flashed ROM)
Sent from my HTC-Z710a using xda app-developers app
@@RON said:
Assuming I set my CID to superCID and flash an unbranded stock ROM, is it possible to get OTA updates with superCID set?
Or should I set it to a normal value e.g. HTC__001 (appropriate to the flashed ROM)
Sent from my HTC-Z710a using xda app-developers app
Click to expand...
Click to collapse
I honestly don't know.. never done it because i use custom roms.. but have you tried using arhd? It's like an unbranded stock Rom and it gets updated too
Enviado desde mi HTC Sensation 4G
@@RON said:
Assuming I set my CID to superCID and flash an unbranded stock ROM, is it possible to get OTA updates with superCID set?
Or should I set it to a normal value e.g. HTC__001 (appropriate to the flashed ROM)
Click to expand...
Click to collapse
For interested people, I wrote my answer down here
http://forum.xda-developers.com/showpost.php?p=32126495&postcount=142
Hi.
So I am T-Mobile US. I am running GB with ROOT.
I want to update to ICS update which just came out.
I can't do OTA since it won't let me (since i am rooted?).
I went ahead and downloaded this official one from here:
http://forum.xda-developers.com/showthread.php?t=1654347
Now here is my Q:
Should I just flash this ROM after putting it in my SD Card?
Should I wipe? Or can I keep all the data (which I prefer)?
Thanks a million!
You can't just flash that. You'll need the 3.32 firmware, preferably the T-Mobile version.
sshede said:
You can't just flash that. You'll need the 3.32 firmware, preferably the T-Mobile version.
Click to expand...
Click to collapse
Thanks so much. Will I find this here in the forums, or at T-Mobile site? Thanks
benyben123 said:
Thanks so much. Will I find this here in the forums, or at T-Mobile site? Thanks
Click to expand...
Click to collapse
IF you want to do OTA update...you need to make sure your recovery, CID, and your current software is the one that's supported by T-mobile OTA. Not sure if you are running a custom GB or a stock one. But basically, if you're on stock but you just rooted it...it's fine to have it rooted...in fact you want to have it rooted and S-off before doing the update
Read this http://www.htcsensationforum.com/ht...to-downgrade-upgrade-gb-lt-gt-ics-a-tutorial/
There are also several post about it here. But bascially you need the software version that's supported by T-mobile for the update (they list those in their update info). So either you run a RUU to bring you to the stock version of these software...including stock recovery...and also change your CID back to T-mobile one...TMOB010 I think..but just double check.
IF all you've change is root and CID...then you just flash the stock recovery that's for the version of the stock software you have now and change the CID back to t-mobile..then it should work.
I had trouble initially but turns out the recovery file I had was probably not the correct version so it kept aborting. Worked fine after I flashed the right recovery.
newr said:
IF you want to do OTA update...you need to make sure your recovery, CID, and your current software is the one that's supported by T-mobile OTA. Not sure if you are running a custom GB or a stock one. But basically, if you're on stock but you just rooted it...it's fine to have it rooted...in fact you want to have it rooted and S-off before doing the update
Read this http://www.htcsensationforum.com/ht...to-downgrade-upgrade-gb-lt-gt-ics-a-tutorial/
There are also several post about it here. But bascially you need the software version that's supported by T-mobile for the update (they list those in their update info). So either you run a RUU to bring you to the stock version of these software...including stock recovery...and also change your CID back to T-mobile one...TMOB010 I think..but just double check.
IF all you've change is root and CID...then you just flash the stock recovery that's for the version of the stock software you have now and change the CID back to t-mobile..then it should work.
I had trouble initially but turns out the recovery file I had was probably not the correct version so it kept aborting. Worked fine after I flashed the right recovery.
Click to expand...
Click to collapse
Wow thanks for your time. Too many things i here i don't even know what they mean. I guess I will just pass and stick to my GB. Safe way.
Thanks a lot
all you have to do is flash this file from recovery. it could not be any simpler. http://www.4shared.com/zip/34Y1RPQf/Sensation_33253114.html
you will lose some things like your settings but you will keep all your backed up apps and contacts.
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
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