Flashing OTA - AT&T, Rogers HTC One X, Telstra One XL

I have a Telus evita phone on 4.1.1. I was wondering if I could flash the German O2 or T-Mobile OTA to receive 4.2.2. My phone is SuperCID and S-OFF. Phone is currently stock because I ran a RUU then updated to 4.1.1. Will I lose my data if I flash the OTA?
Thanks

dx99 said:
I have a Telus evita phone on 4.1.1. I was wondering if I could flash the German O2 or T-Mobile OTA to receive 4.2.2. My phone is SuperCID and S-OFF. Phone is currently stock because I ran a RUU then updated to 4.1.1. Will I lose my data if I flash the OTA?
Thanks
Click to expand...
Click to collapse
I would just flash TWRP back onto the phone, then flash Turge's stock T-Mobile Sense 5 ROM posted in Development. Install the 2.15 firmware if you experience signal drops or random reboots.
My typical recommendation is to stay away from official OTAs if you are modded.

I just don't want to flash anything on my phone that's not official. That's why I'm asking, I want to keep my phone stock and just get an official update not a rom from another source.

Your phone is already far from stock, with SuperCID and S-off. You're already down the rabbit hole. And putting an OTA for another version is also not going to be "stock" or "official" for your phone.
The stock ROM is just from the OTA dump, completely unmodified (not even rooted, in fact). Its what is on my phone, and is running great.
Running the OTA might be risky. OTA does not necessarily have all the components. For instance, the T-Mobile 5.05 OTA does not have all the hboot modules. It assumes you are coming for the most recent T-Mobile RUU or OTA. So depending on what is currently on your phone, you can brick.
In theory, I think what you are proposing will work if you RUU to the most recent T-Mobile Germany RUU, than T-Mobile Germany Sense 5 OTA.
But again, you're making it more complicated than need be. What is exactly the issue with "unofficial" ROMs? If you don't trust the devs here, you would not have done SuperCID and s-off to begin with.

It's not that I don't trust the devs I just want to use official carrier updates. I know my phone isn't stock what I meant is using stock/original files from carriers. So even though my phone is from Telus and I used a RUU from them to get back to stock firmware I can flash a T-Mobile RUU over top of it then use their OTA afterwards?

dx99 said:
So even though my phone is from Telus and I used a RUU from them to get back to stock firmware I can flash a T-Mobile RUU over top of it then use their OTA afterwards?
Click to expand...
Click to collapse
Yes, the only thing stopping the RUU from running would be the carrier ID check and hboot version check (might be some other checks). But since you have s-off, all security checks are bypassed by definition.

Alright, would there be any issues with the fact that I'm on 4.1.1 and going backwards in firmware first? Since most RUU are 4.0.

dx99 said:
Alright, would there be any issues with the fact that I'm on 4.1.1 and going backwards in firmware first? Since most RUU are 4.0.
Click to expand...
Click to collapse
Now that you mention it, it looks like you would have to run the most recent RUU from T-Mobile Germany (3.17.111.1) then run two OTAs (3.17.111.2, and then finally 5.08.111.2). Run them out of sequence, and you risk a brick.
RUUs can be installed out of sequence, but there isn't one for 5.08.
I retract my former idea to RUU then OTA. I can't personally recommend such action upon further consideration. Its more complicated than I originally thought. I go back to my former statement, in that you are making this much more complicated than it should be. You are actually creating a higher risk of bricking your phone due to some imagined fear of "unofficial software".

redpoint73 said:
Now that you mention it, it looks like you would have to run the most recent RUU from T-Mobile Germany (3.17.111.1) then run two OTAs (3.17.111.2, and then finally 5.08.111.2). Run them out of sequence, and you risk a brick.
RUUs can be installed out of sequence, but there isn't one for 5.08.
I retract my former idea to RUU then OTA. I can't personally recommend such action upon further consideration. Its more complicated than I originally thought. I go back to my former statement, in that you are making this much more complicated than it should be. You are actually creating a higher risk of bricking your phone due to some imagined fear of "unofficial software".
Click to expand...
Click to collapse
So then its not possible to use the T-Mobile RUU and OTA on my Telus phone?

dx99 said:
So then its not possible to use the T-Mobile RUU and OTA on my Telus phone?
Click to expand...
Click to collapse
I think its possible, but its needlessly complicated and possibly risky. If you do it wrong, you might brick.
I don't personally recommend it, and its my personal opinion that you don't have a particularly valid reason for going that route when simpler methods exist. So if you proceed, its at your own judgement and you take all responsibility if something goes wrong.

If it does manage to work so you think there might be compatability issues with the play store or region specific things?

Related

sprint RUU

can i take a CDMA hero for GCI Wireless / Alaska Digitel and use the RUU to make it work on sprint? i just want to make sure before i get it that it works
i think the bootloader is different. pretty sure you will get an error running the ruu
thedudejdog said:
i think the bootloader is different. pretty sure you will get an error running the ruu
Click to expand...
Click to collapse
is there a way to reprovision to make it work?
thedudejdog said:
i think the bootloader is different. pretty sure you will get an error running the ruu
Click to expand...
Click to collapse
You could have them check the bootloader version from fastboot (hold vol down when turning the phone on).
Version 1.41.0000 is the one that works with the 1.56 RUU.
afaik this is the reason they don't have root yet.
all they would have to do is flash a sprint ruu, root, flash recovery, and then flash whatever rom they wanted. but the Alaskan Digital guys got root-patched. the bootloader is newer than ours. a few months ago they were trying to root and most all of the non-sprint hero's are rooted. all but alaskan digital.
Thread
read this... it says on the first post it will mess with the pri i think it may turn it into a sprint phone. (the 2.1 ruu)
Sprint 2.1 RUU - Supposedly a Sprint 2.1 RUU has been floating around. Until we hear otherwise, DO NOT APPLY IT. Specifically, problems have been reported with GCI Wireless / Alaska DigiTel: "it can break roaming, possibly cause data connection issues, and of course it could adversely affect the bill." and "If someone updates with an RUU we currently have no way to fix their phone." Even if you're with Cellular South or someone else, I suggest not applying it.
Click to expand...
Click to collapse
i have found that and looked it over. i just dont want to make it a paper weight and not have a phone
then your best bet will be to get it and run the 2.1 ruu and hope for the best.. lol.
(almost) anything that you do can be recovered. except a gsm radio flash. so don't flash any of those and you'll be fine.
You need to have a goldcard setup but flashing Sprint's 2.1 RUU over any other carriers Hero will work so long as the bootloader is not newer. Currently, the Sprint 2.1 RUU that's floating around has the newest bootloader I know of so it will flash over anything at this point.
Just a warning though, you can't go back to another RUU after because everything else has an older bootloader. Which doesn't matter so much because the Sprint 2.1 RUU floating around is a dev rom and rooted so you can flash the custom recovery and go to whatever ROM you want.
EDIT: If you are not on Sprint and you use a Sprint RUU you DO have to program your carriers PRL after using QPST or CDMA Workshop
@curtis8523 I know I sent this to you via email already but I wanted to make sure it's searchable on XDA.
navalynt said:
Just a warning though, you can't go back to another RUU after because everything else has an older bootloader. Which doesn't matter so much because the Sprint 2.1 RUU floating around is a dev rom and rooted so you can flash the custom recovery and go to whatever ROM you want.
Click to expand...
Click to collapse
This is a good point. You could flash the 2.1 test RUU to get it to Sprint. If you want to run the 1.56 ruu you can flash everything 1.5 except the hboot by following the instructions here >> http://forum.xda-developers.com/showthread.php?t=657086

[Q] HTC One X (AT&T) manual update

Hello folks, sorry for the dumb questions but this is new for me. I have HTC One X (AT&T) phone, bought in USA. This is my first android phone and I barely know android as a software. I unlocked the phone buying an unlock code from ebay and I am using the phone on another carrier. My question is, how can i manually update my phone (what is the newest update?) since AT&T is not a carrier in my country and I cannot update automatically.
At the moment my software information are:
Android version 4.0.3
HTC Sense version 4.0
Software number 1.85.502.3 710RD
Kernel version 3.0.8-01155-gca24d1eroo[email protected] # SMP PREEMPT (why is there root in the kernel version, my phone has never been rooted?)
Build number 1.85.502.3_R2 CL63811 release-keys
Doing this manual update if possible will the phone be locked to AT&T again, or my phone will remain unlocked?
I'm sorry for my bad english and sorry if there is already a question like this (I watched the noob video and did use the search button)
Thank you in advance
If you ever want to root or flash custom ROMs or other mods, I would advise not installing the latest (2.20) version AT&T firmware. Installing the official 2.20 firmware updates the bootloader, which plugs the holes by which kernels and radios can be flashed from recovery.
If you want root, I would root on 1.85, SuperCID, and unlock bootloader. Then you can install any firmware you want, including stock rooted versions that are more up to date than 2.20.
If you still want to install the 2.20 firmware, you can download the RUU (ROM updated utility) from HTC and run it on a PC, with the phone connected via USB. The phone should remain SIM unlocked after running the RUU. But RUU will wipe your data partition (but not the internal SD).
A lot of this may be over your head, so this may help: http://forum.xda-developers.com/showthread.php?t=1784459
redpoint73 said:
If you ever want to root or flash custom ROMs or other mods, I would advise not installing the latest (2.20) version AT&T firmware. Installing the official 2.20 firmware updates the bootloader, which plugs the holes by which kernels and radios can be flashed from recovery.
If you want root, I would root on 1.85, SuperCID, and unlock bootloader. Then you can install any firmware you want, including stock rooted versions that are more up to date than 2.20.
If you still want to install the 2.20 firmware, you can download the RUU (ROM updated utility) from HTC and run it on a PC, with the phone connected via USB. The phone should remain SIM unlocked after running the RUU. But RUU will wipe your data partition (but not the internal SD).
A lot of this may be over your head, so this may help: http://forum.xda-developers.com/showthread.php?t=1784459
Click to expand...
Click to collapse
Thank you redpoint73 for your answer, I will follow your advice and will root it on 1.85.
I suppose what I should do first is rooting my phone following this guide: http://forum.xda-developers.com/showthread.php?t=1644167.
Than I should do this: http://forum.xda-developers.com/showthread.php?t=1672284
Please correct me if I am mistaken
After doing all of that which firmware do you suggest or stock rooted version, or its just matter of taste? Now again the same question will I lose my SIM-unlock after rooting mt phone?
StoleMacuk said:
Thank you redpoint73 for your answer, I will follow your advice and will root it on 1.85.
I suppose what I should do first is rooting my phone following this guide: http://forum.xda-developers.com/showthread.php?t=1644167.
Than I should do this: http://forum.xda-developers.com/showthread.php?t=1672284
Please correct me if I am mistaken
After doing all of that which firmware do you suggest or stock rooted version, or its just matter of taste? Now again the same question will I lose my SIM-unlock after rooting mt phone?
Click to expand...
Click to collapse
The root method you linked is actually for 1.73. You want to use this one for 1.85: http://forum.xda-developers.com/showthread.php?t=1709296
The SuperCID method you linked is correct.
ROM/firmware is very much a matter of taste, and what features you are looking for. If you want stock, you can install the stock rooted 2.20 AT&T firmware in the Development forum (after unlocking the bootloader and installing TWRP). If you want something based on stock, but with cool added features and customizations, look at ViperXL, CleanROM, or Nocturnal LE. But that doesn't mean that any of the other ROMs are not also great. And that doesn't even mention the more "vanilla" (no HTC Sense) Android experience you can get from AOSP based ROMs, and their variants.
The differences and benefits of each are simply too extensive to discuss here. Just start looking at the ROMs and see what looks interesting to you.
Take a look at my index to see all the resources in an organized list:
http://forum.xda-developers.com/showthread.php?t=1671237
redpoint73 said:
The root method you linked is actually for 1.73. You want to use this one for 1.85: http://forum.xda-developers.com/showthread.php?t=1709296
The SuperCID method you linked is correct.
ROM/firmware is very much a matter of taste, and what features you are looking for. If you want stock, you can install the stock rooted 2.20 AT&T firmware in the Development forum (after unlocking the bootloader and installing TWRP). If you want something based on stock, but with cool added features and customizations, look at ViperXL, CleanROM, or Nocturnal LE. But that doesn't mean that any of the other ROMs are not also great. And that doesn't even mention the more "vanilla" (no HTC Sense) Android experience you can get from AOSP based ROMs, and their variants.
The differences and benefits of each are simply too extensive to discuss here. Just start looking at the ROMs and see what looks interesting to you.
Take a look at my index to see all the resources in an organized list:
http://forum.xda-developers.com/showthread.php?t=1671237
Click to expand...
Click to collapse
I have a doubt. As I'm no from USA, I'll have no option to update the firmware over the air. How must I proceed in this part of the manual method?
Won't I have any issues with this?
Thank you guys in advance...
galitore said:
How must I proceed in this part of the manual method?
Click to expand...
Click to collapse
My advice? Stop now. If, in fact, "This is my first android phone and I barely know android as a software," you're not ready to root.
You need to spend the next week (at least) reading and searching and reading some more. Don't come back until you can answer the following questions:
1. What does "rooting" mean, what exactly does it do to your phone?
2. What are you doing when you unlock the bootloader?
3. What's the difference between stock and custom recovery, and stock and custom ROMs?
Once you feel like you understand all this, you're ready to proceed. If you push forward now, you'll almost certain to get into trouble that you won't be able to get out of without extensive help.
iElvis said:
My advice? Stop now. If, in fact, "This is my first android phone and I barely know android as a software," you're not ready to root.
You need to spend the next week (at least) reading and searching and reading some more. Don't come back until you can answer the following questions:
1. What does "rooting" mean, what exactly does it do to your phone?
2. What are you doing when you unlock the bootloader?
3. What's the difference between stock and custom recovery, and stock and custom ROMs?
Once you feel like you understand all this, you're ready to proceed. If you push forward now, you'll almost certain to get into trouble that you won't be able to get out of without extensive help.
Click to expand...
Click to collapse
Hi iElvis,
actually it wasn`t me who said "This is my first android phone and I barely know android as a software"... it was another member.
I had an Motorola Atrix 4G which I rooted a coupe of times, but this one was made for my country market, differently than my HOX, that is at&t. But in one thing you`re right. I have not much experience with HOX. That`s true...
My question was regarding the part of the manual process which needs a communication between at&t and my cellphone. In this case I wouldn`t find any upgrade option to accept or deny. So i don`t know what would happen in this case... does anyone know?!?!
galitore said:
Hi iElvis,
actually it wasn`t me who said "This is my first android phone and I barely know android as a software"... it was another member.
I had an Motorola Atrix 4G which I rooted a coupe of times, but this one was made for my country market, differently than my HOX, that is at&t. But in one thing you`re right. I have not much experience with HOX. That`s true...
My question was regarding the part of the manual process which needs a communication between at&t and my cellphone. In this case I wouldn`t find any upgrade option to accept or deny. So i don`t know what would happen in this case... does anyone know?!?!
Click to expand...
Click to collapse
Whoops! Sorry about that.
As far as I know, the only way is to flash a custom rom with the base you want, or to run the RUU for that base, which will leave you relocked and unrooted.

Applying RUUs on Unlocked 1.14/2.22 AT&T One X

Before anyone tries to flame me, I've read all of the recent ICS and JB rom threads, as well as most of the generic question threads. I've unlocked, rooted, and flashed several roms before settling on CleanROM so I am not a complete noob. The master q&a thread doesn't cover RUUs much, and people aren't that interested in applying non rootable RUUs, so info on going back to stock on a newer or even older RUU doesn't seem to be widely available. My biggest concern is bricking my phone or losing major functionality, as some people using asian based roms seem to be having reboot and/or wifi issues.
1. Applying a different carriers S4 JB RUU is perfectly safe as long as I relock the boot loader, even with Super-CID.
I've seen conflicting reports of issues with RUUs when you have Super-CID, even with the original shipping RUU and a relocked boot loader. Can someone confirm that using RUUs is safe as long as the boot loader is relocked? What if it isn't relocked? Just an error or a bricked phone?
2. Once you unlock your phone on 1.14, you are stuck with that radio forever unless you apply an RUU or switch to Cyanogenmod.
3. Assuming RUUs are safe, applying a different carriers' RUU on my AT&T One X won't hurt anything. There may be apn issues, but otherwise everything should work (especially the camera and wifi).
Again, I understand that without root, I may not be able to add apns anyway. AT&T at least seems to have blocked the ability on their stock rom; not sure if other carriers do the same.
I really appreciate the help. I have searched, so this is more of a confirmation than anything else. Just trying to avoid bricking my phone and learn something new at the same time.
Tim
Sent from my HTC One X using xda premium
tlazarus said:
Before anyone tries to flame me, I've read all of the recent ICS and JB rom threads, as well as most of the generic question threads. I've unlocked, rooted, and flashed several roms before settling on CleanROM so I am not a complete noob. The master q&a thread doesn't cover RUUs much, and people aren't that interested in applying non rootable RUUs, so info on going back to stock on a newer or even older RUU doesn't seem to be widely available. My biggest concern is bricking my phone or losing major functionality, as some people using asian based roms seem to be having reboot and/or wifi issues.
1. Applying a different carriers S4 JB RUU is perfectly safe as long as I relock the boot loader, even with Super-CID.
I've seen conflicting reports of issues with RUUs when you have Super-CID, even with the original shipping RUU and a relocked boot loader. Can someone confirm that using RUUs is safe as long as the boot loader is relocked? What if it isn't relocked? Just an error or a bricked phone?
2. Once you unlock your phone on 1.14, you are stuck with that radio forever unless you apply an RUU or switch to Cyanogenmod.
3. Assuming RUUs are safe, applying a different carriers' RUU on my AT&T One X won't hurt anything. There may be apn issues, but otherwise everything should work (especially the camera and wifi).
Again, I understand that without root, I may not be able to add apns anyway. AT&T at least seems to have blocked the ability on their stock rom; not sure if other carriers do the same.
I really appreciate the help. I have searched, so this is more of a confirmation than anything else. Just trying to avoid bricking my phone and learn something new at the same time.
Tim
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Im on hboot 1.14, firmware 2.20 att. Unlocked , rooted , flashed Rom. However , I had some problem then decided go back stock.
1. Downloaded ruu2.20 for att
2. Relock bootloader
3. Boot phone to bootloader mode then run ruu. Now my phone is stock
P/s :
- you don't need to root your phone to add apn . I can add T-Mobile apn just fine after I flashed ruu.
- ruu.exe can't run if you bootloader is unlocked.
Sent from my HTC One X using XDA Premium HD app
tritran18518 said:
Im on hboot 1.14, firmware 2.20 att. Unlocked , rooted , flashed Rom. However , I had some problem then decided go back stock.
1. Downloaded ruu2.20 for att
2. Relock bootloader
3. Boot phone to bootloader mode then run ruu. Now my phone is stock
P/s : you don't need to root your phone to add apn .
Sent from my HTC One X using XDA Premium HD app
Click to expand...
Click to collapse
Thanks - that answers my RUU questions as far as going back to stock using RUUs. I assume the same applies to other carrier's RUUs, i.e. Telus/Asia. What about using an OTA on a phone with Super-CID?
redpoint73 said:
A factory reset or running the RUU will not change the CID.
SuperCID doesn't prevent you from getting the AT&T OTA (although root and unlocked bootloader will).
Click to expand...
Click to collapse
^^
jiggamanjb said:
^^
Click to expand...
Click to collapse
Okay, I think that answers my questions. No problems with using a RUU, AT&T or otherwise, as long as it is for the XL. Stuck on my current radio unless I use a RUU. And I need to relock my bootloader before applying a RUU, although I can unlock it after. I will lose root, however. Thanks!

[Q] Dumb Questions...

Okay, So I'm fairly new to all this. I've made several (unsuccessful) attempts at rooting my AT&T HOX, but I finally think I know where I went wrong.
In the past, I had tried unlocking the bootloader without having SuperCID access. (So yes, I currently have s-on..) Mainly due to the fact that I didn't know I needed sim access to root.
Because of these past issues, I have done the ATT OTA update.. From what I have read in other posts, correct me if I'm wrong, there is currently no way to gain SuperCID with the 5.18 update..
Other than waiting, is there any way I could go about rooting my phone? Is it possible to reset to factory settings, and go back to Original software?
Please help. Would eventually love to get rid of all the ATT and HTC crap on my phone.. (can't stand sense 5..)
Android version - 4.2.2
HTC Sense version - 5.0
Software number 5.18.502.1
Evita PUT SHIP S-ON RL
HBOOT - 2.18.0000
Radio - 1.35a.32.45.27
OpenDSP-v33.1.0.45.1128
eMMC-boot
Because you've taken the latest at&t update there is no way at all to get SuperCID so you can unlock your bootloader. You'll have to wait and see whether a dev deems it worth his time to find a crack, but I wouldn't hold your breathe if I was you. Probably should have done your research before taking the update.
Sent from my Evita
tsunami560 said:
Okay, So I'm fairly new to all this. I've made several (unsuccessful) attempts at rooting my AT&T HOX, but I finally think I know where I went wrong.
In the past, I had tried unlocking the bootloader without having SuperCID access. (So yes, I currently have s-on..) Mainly due to the fact that I didn't know I needed sim access to root.
Because of these past issues, I have done the ATT OTA update.. From what I have read in other posts, correct me if I'm wrong, there is currently no way to gain SuperCID with the 5.18 update..
Other than waiting, is there any way I could go about rooting my phone? Is it possible to reset to factory settings, and go back to Original software?
Please help. Would eventually love to get rid of all the ATT and HTC crap on my phone.. (can't stand sense 5..)
Android version - 4.2.2
HTC Sense version - 5.0
Software number 5.18.502.1
Evita PUT SHIP S-ON RL
HBOOT - 2.18.0000
Radio - 1.35a.32.45.27
OpenDSP-v33.1.0.45.1128
eMMC-boot
Click to expand...
Click to collapse
1. I'm not are of a root for this new firmware (as Timmaaa has stated).
2. I'm not sure why you chose to get the OTA update if you can't stand HTC and Sense. Any time you grab an update from A&T, you're risking not being able to root
3. I recommend you purchase a Google phone and root/mod it as much as you want. No more HTC, No More ATT, No more Sense.
DanGeorges said:
1. I'm not are of a root for this new firmware (as Timmaaa has stated).
2. I'm not sure why you chose to get the OTA update if you can't stand HTC and Sense. Any time you grab an update from A&T, you're risking not being able to root
3. I recommend you purchase a Google phone and root/mod it as much as you want. No more HTC, No More ATT, No more Sense.
Click to expand...
Click to collapse
Hey Dan,
Thanks for the reply. I got the OTA because I like new. I didn't really think about it when I did it, so yea, it was a dumb mistake on my part.
I only got HTC, because it was my introduction to Android. I now have a rooted N7, and I love it. I would also love to get an N5, however, it's a good chunk of money I don't have currently, which is why I will be rooting my HOX once a root is available.
So, is anyone aware of a way to roll back an OTA update? Or is my best bet waiting for a 5.18 exploit?
Like I said, there is absolutely no way for you to get root unless someone releases an exploit.
Sent from my Evita
tsunami560 said:
So, is anyone aware of a way to roll back an OTA update? Or is my best bet waiting for a 5.18 exploit?
Click to expand...
Click to collapse
If such a thing were possible, than a new exploit would not be necessary, and we would have told you about it already.
You can't "rollback" or revert to previous Android versions unless already rooted, s-off, etc.

Possible Root for AT&T HTC_One_X_RUU_5.18.502.1

I'm having reception issues and would like to try the 5.18 update (with its included 1.35a.32.45.27_10.144.32.34a radio) but I require root (I read the thread here that says the WeakSauce Root works on the AT&T ONE X but am not sure about using an exploit that has to reroot on every boot, albeit automatic). Searching for rooting information for the latest AT&T 5.18 update, I came across this Chinese thread: Translated Chinese forum link. The OP includes the AT&T ROM, Chinese language pack file, Chinese APN file, and a root file. I can't read Chinese and there is much lost in the Google translation but from what I can tell this is the American AT&T 5.18 ROM, and at least one poster said the rooting worked.
My current setup is:
Ver: 4.1.1
ROM: 3.18.502.6.71ORD
HBOOT-2.14.0000
RADIO-0.24p.32.09.06
Bootloader unlocked, Super CID, S-OFF, rooted
Faked locked and S-ON status
1. My first and most important question is, being S-OFF with Super CID, If I update to 5.18 and I can't root it, can I still reflash with something else?
2. The root package (which I am attaching) is a zip. I assume after flashing 5.18 I'll have to flash a custom recovery by this means, "fastboot flash recovery recoveryfilename.img," correct?
3. I also assume the bootloader will be relocked and will need to be unlocked again. Can this be done by the normal method?
4. Will I need to Super CID again?
Thanks!
You're over thinking it. Since you are s-off, you can do almost anything, and not worry about having to root, SuperCID, unlock the bootloader, etc. again.
You also have several options:
a) Yes, you can run the 5.18 RUU if you like. I don't even think you have to relock the bootloader, since you are s-off. You will still be SuperCID and S-off after RUU. Although since RUU re-installs stock recovery, you will need to install TWRP again. At that point, you can always flash SU to root, and/or install custom ROMs.
b) If its just the radio you want to try, you can just install the 2.18 firmware: http://forum.xda-developers.com/showthread.php?t=2651052
This will keep your current ROM intact, but it might be your desire to update that anyway.
c) Just because a radio is newer, does not necessarily mean it will be "better" in your particular area. The "best" radio is often a trial and error exercise. Since you are s-off, you can flash any of the radios here to see if they yield any improvement: http://forum.xda-developers.com/showthread.php?t=1694012
Also, while a different radio may give some improvement, I won't expect any miracles. Might even find reception is worse.
@redpoint73
Thanks for the response, just what I was wanting to know... and yes, I often over think things. I"ll give 5.18 a try.
Also, the answers to your questions in blue font:
1. My first and most important question is, being S-OFF with Super CID, If I update to 5.18 and I can't root it, can I still reflash with something else?
Since you are s-off, you can still flash custom recovery, install custom ROMs, run older RUUs, etc. So there would be a variety of ways to revert, if you wanted to.
2. The root package (which I am attaching) is a zip. I assume after flashing 5.18 I'll have to flash a custom recovery by this means, "fastboot flash recovery recoveryfilename.img," correct?
If the intent of the method is to root a phone that was never bootloader unlocked (which is also the only reason you would ever need a new root exploit) then NO that doesn't make any sense. If the bootloader is locked, you can't flash custom recovery.
3. I also assume the bootloader will be relocked and will need to be unlocked again. Can this be done by the normal method?
With S-off, I don't believe you need to relock the bootloader to run the RUU.
4. Will I need to Super CID again?
No, you will still have SuperCID. This only gets changed if you do so deliberately. Same with S-off.
The above options are very good, but if you are interested in the weaksauce root method I can assure you it is very simple and hassle free. You won't even know its a "temp root" because it reroots on reboot instantly. The only downside, is that no custom roms or recoverys may be flashed to my knowledge. If this is a problem then I suggest using redpoint73's answer.
Also if you have luck, please let me know I would be interested and greatly thankful.
He doesn't need to root his device, he's already rooted. Did you not read the thread?
Sent from my Evita
moved to Q&A forum.
I did indeed read the thread, he was asking about the weaksauce root method so i was explaining it to him. Also, if he updates to 5.18 he will need to root (that is of course if he chooses RUU). Bringing me to my next question, did you in fact not read the thread?
FlubbedJohn said:
I did indeed read the thread, he was asking about the weaksauce root method so i was explaining it to him. Also, if he updates to 5.18 he will need to root (that is of course if he chooses RUU). Bringing me to my next question, did you in fact not read the thread?
Click to expand...
Click to collapse
He's already S-OFF, he does not need any root exploits -_- he can just flash su.
I flashed the 5.18 RUU without issue and was still bootloarder unlocked. S-OFF, and Super CID but did lose my faked locked and S-ON status. I then flashed TWRP then booted to recovery and when I went to reboot, TWRP asked if I wanted to root so I selected, yes. Upon booting into the system it went straight to Google Play and downloaded and installed SuperSU as TWRP said it would--rooted.
I still had the same signal issue with 5.18 ROM so I tried flashing several older radios but still had the same problem. When I got the phone (used) it had 2.20 ROM. Signal was not as good as my SGS3 or Lumia 920 but at least I could get a couple of bars sitting 12' from my repeater ( 3-4 bars on the other phones, no signal in my house without the repeater). After flashing up to 3.18 ROM I could no longer get a signal in my chair, only if I set the phone inches from the repeater. Since the initial flashing to 3.18 if I step inside my local Walmart (before the registers) I will have 3 bars LTE but when I dial after a few seconds it will lose all signal and the call will fail. Outside with 3 bars it works fine. I'm at a loss.
FlubbedJohn said:
I did indeed read the thread, he was asking about the weaksauce root method so i was explaining it to him. Also, if he updates to 5.18 he will need to root (that is of course if he chooses RUU). Bringing me to my next question, did you in fact not read the thread?
Click to expand...
Click to collapse
Even if he updates to 5.18 he will not need any root exploits. He is s-off so he can run any RUU he likes without having to relock his bootloader. This means all he needs to do is flash a custom recovery afterwards, and flash SuperSU or Superuser.
If you're going to give advice here on the forums, bring your knowledge up a bit so that you are able to give advice that is accurate and relevant. Giving the wrong advice will at the very least send another user on a wild goose chase doing things that are irrelevant (like weaksauce), and worst case scenario you could end up bricking someone's phone. I doubt you want that on your conscience.
Sent from my Evita
Pop45398 said:
I flashed the 5.18 RUU without issue and was still bootloarder unlocked. S-OFF, and Super CID but did lose my faked locked and S-ON status.
Click to expand...
Click to collapse
That makes sense. I believe the spoofed BL lock and S-on are hacked hboot. The RUU replaces (overwrites) hboot.
Pop45398 said:
I still had the same signal issue with 5.18 ROM so I tried flashing several older radios but still had the same problem. When I got the phone (used) it had 2.20 ROM. Signal was not as good as my SGS3 or Lumia 920 but at least I could get a couple of bars sitting 12' from my repeater ( 3-4 bars on the other phones, no signal in my house without the repeater). After flashing up to 3.18 ROM I could no longer get a signal in my chair, only if I set the phone inches from the repeater. Since the initial flashing to 3.18 if I step inside my local Walmart (before the registers) I will have 3 bars LTE but when I dial after a few seconds it will lose all signal and the call will fail. Outside with 3 bars it works fine. I'm at a loss.
Click to expand...
Click to collapse
Keep in mind that comparing signal "bars" between different phones means nothing. There is no standard to what the bars even represent. You can read the signal strength (dBm) in Settings>About>Network.
But if I understand properly, its not just a matter of the "bars" but actual reception (dropped calls, etc.). If it worked fine on the 2.20 setup, did you try the radio associated with 2.20 (radio 0.19as.32.09.11_2_10.105.32.25)?
Also keep in mind that certain buildings do not play well with phones at all. Big box stores can be particularly notorious for this. Not sure what combination of concrete, steel, etc. interferes with cell signal, but I often get zero signal in Target, IKEA, etc. At the climbing gym where I go every week (not a huge building, but steel beams with concrete face) none of my friends get any signal regardless of phone (my HOX, iPhones, all on AT&T) when we are inside. Then we will get a flood of SMS messages the minute we walk out the building!
timmaaa said:
Even if he updates to 5.18 he will not need any root exploits. He is s-off so he can run any RUU he likes without having to relock his bootloader. This means all he needs to do is flash a custom recovery afterwards, and flash SuperSU or Superuser.
If you're going to give advice here on the forums, bring your knowledge up a bit so that you are able to give advice that is accurate and relevant. Giving the wrong advice will at the very least send another user on a wild goose chase doing things that are irrelevant (like weaksauce), and worst case scenario you could end up bricking someone's phone. I doubt you want that on your conscience.
Sent from my Evita
Click to expand...
Click to collapse
He was the one who was looking for the root method, I just delivered. He was looking for a way to root, I gave it to him. You can the rest to him.
Yes, that's correct. But as respoint had said prior to you first responding he didn't need a root method. Plus, it's our responsibility as people giving advice here to firstly know what we're talking about, and secondly to steer someone in the right direction if they're on the wrong track. Not to just provide incorrect information because that's what they think they need to do.
My statement from earlier still stands, if you want to help people on here you need to bring your knowledge up a bit first. I'm not trying to be harsh, the fact is that accuracy and relevancy are absolutely paramount on XDA, providing incorrect information is dangerous. Please don't take that the wrong way! You're new here so welcome to our forum
Sent from my Evita
FlubbedJohn said:
He was the one who was looking for the root method, I just delivered. He was looking for a way to root, I gave it to him. You can the rest to him.
Click to expand...
Click to collapse
I agree with timmaaa on this. Its just my own opinion (but many others will likely agree) that any temp root solution (even one that re-temp roots with every boot) is inferior to a true permanent root. Especially when the temp root requires an app to be installed.
For the OPs particular case, WeakSauce looks to be more complicated (or at least more contrived) and less comprehensive solution than the s-off status and unlocked bootloader he already has. It probably would have made more sense to present the issue in a way such as: Yes, WeakSauce will work for temp root, but the other provided options are probably better choices.

Categories

Resources