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!
Related
Ok so I have a One X with AT&T and I am just asking for some clarifications.
1.) I am on software version 1.73, which is from what I understand to be root-able, but software version 1.85 isn't root-able?
2.) After reading around on here people keep referring to them re-locking their boot-loaders after they unlock them through htc-dev, so my question is do you need to re-lock it afterwards? Also, what is the reason why?
Any answers are appreciated, please inform me if I have blatantly missed something obvious or if i'm in the wrong place.
Can I ask Red or one of the other mods to please move this to Q&A, it seems I neglected this
And Red are you really 15?
1.85 has not yet been rooted. Correct. After gaining root, super cid and unlocking bootloader you only need to relock it when needing to use a ruu, say to upgrade to 1.88 or if you just want or need to go back to stock. After ruu you can go back and re unlock it since ruu won't affect super Cid. Hope this helps
Sent from my HTC One X using xda premium
Thanks for the answer.
One more thing, are you able to flash CWM and roms after unlocking the bootloader the first time? Or do you have to run the RUU to be able to?
Once bootloader is unlocked you can flash your recovery. The latest twrp recovery is choice since it the only one with functioning USB at the moment. If you decide to relock and run a ruu remember to unlock and reflash your recovery of choice too. The only time u need to ruu (typically) is to upgrade or downgrade firmware or fix a soft brick so you don't NEED to ruu at all but it's a good idea to upgrade for the bug fixes from 1.73.
Sent from my HTC One X using xda premium
I have read various guides, and eventually taken the plunge to downgrade my bootloader.
htcDev Unlock
Goldcard
Install oldest RUU
S-OFF using revolutionary
Flash CWM recovery
Backup Stock 2.33 ROM with Sense
Install CM9
Feeling quite pleased with myself, even though you guys have really done all the hard work, I've just followed the steps!
What I can't find is this;
If I go back to the Stock ROM and updates are offered OTA, if I accept, will this, not only bring me back to 2.3.5 with Sense 3.0, but also change my bootloader back to 2.00.0002 Locked and S-ON ?
Unfortunately it will be *RELOCKED* and S-ON
Sent from my HTC Desire S
amidabuddha said:
Unfortunately it will be *RELOCKED* and S-ON
Click to expand...
Click to collapse
What he said. If you wanted to remain "locked" and not "relocked" - you should have avoided unlocking the bootloader, and should have used temp-root for misc_version.
Ok, what are the inplications of being 'RE-LOCKED'
Like CM9, but get the feeling development stalled, also certain apps won't work Nat West being one, though I suspect that is to do with their development.
Thinking about going back to Stock. If I do this via OTA, my bootloader will be upgraded back to 2.00.0002, 'RE-LOCKED' and S-ON, then wait for official OTA upgrade to ICS, which seems not to be happening as per HTC announcements. Even then I may have issues with apps that haven't been coded to deal with it.
If I am 'RE-LOCKED' can I not use htcDev again, or am I stuck with the Official bootloader etc and unable to load other ROMS, or can I just repeat the processes I have been through already?
I have also been reading about unlocking with an XTC Clip, where would I get this done, Is this a better solution? etc etc..
No issues with RELOCKED except that your warranty is gone.
If you have no warranty you can go for XTC Clip, since permanent S-OFF will give you more freedom in terms of modifications. Personally I consider flashing boot.img separately each time as annoying.
As per the unlock again, it should be possible, but I am not sure if this can be done by a fastboot command or the unlock token has to be flashed again.
Sent from my HTC Desire S
When I unlocked mine I remember reading somewhere that the token would need to be used again if the phone was re locked. So I kept it just in case
Hey guys,
I am an amateur in all these stuff. I recently picked up at&t one x white unlocked from US running 4.0.3
I wanted to update my phone but i guess i am afraid if my phone gets locked . Moreover i cannot even update it through settings as it says not able to connect to AT&T server.
Please help me regarding custom ROMS , updates Rooting etc and steps to follow.
Links to Threads that can help will be awesome.
Hoping you guys will help a new member
Thanks
Ankit
trojan_virus said:
Hey guys,
I am an amateur in all these stuff. I recently picked up at&t one x white unlocked from US running 4.0.3
I wanted to update my phone but i guess i am afraid if my phone gets locked . Moreover i cannot even update it through settings as it says not able to connect to AT&T server.
Please help me regarding custom ROMS , updates Rooting etc and steps to follow.
Links to Threads that can help will be awesome.
Hoping you guys will help a new member
Thanks
Ankit
Click to expand...
Click to collapse
1) you mean Sim - unlocked right? In that case it won't get locked even if you update the phone software.
2)First and important step is using the search function and I known its very hard for you but once in a while try using the search function, trust me you won't get tired
Follow the instructions in this link http://forum.xda-developers.com/showthread.php?p=30741993
Sent from my HTC One X using xda premium
trojan_virus said:
Links to Threads that can help will be awesome.
Click to expand...
Click to collapse
Everything you need is here: http://forum.xda-developers.com/showthread.php?t=1671237
And don't update. The newest 2.20 version firmware is not currently rootable. And hope you don't already have 2.20 on the phone.
redpoint73 said:
Everything you need is here: http://forum.xda-developers.com/showthread.php?t=1671237
And don't update. The newest 2.20 version firmware is not currently rootable. And hope you don't already have 2.20 on the phone.
Click to expand...
Click to collapse
Thanks for correcting... I learned how to provide better reply
Sent from my HTC One X using xda premium
a little help guys...
I also have an unlocked HOX. I tried updating the software manually by downloading the AT&T ROM Update from the HTC website but got an error and now i'm stuck on a white screen that says:
**** TAMPERED ****
**** UNLOCKED ****
EVITA PVT SHIP S-ON RL
HBOOT.1.09.0000
OpenDSP-v28.1.0.32.0504
eMMC-boot
Apr 2 2012,21:08:24
RUU
Update Fail!
* I did a factory reset and now passed that white screen...does anyone know what the problem was? is my phone rooted?
y2janz said:
a little help guys...
I also have an unlocked HOX. I tried updating the software manually by downloading the AT&T ROM Update from the HTC website but got an error and now i'm stuck on a white screen that says:
**** TAMPERED ****
**** UNLOCKED ****
EVITA PVT SHIP S-ON RL
HBOOT.1.09.0000
OpenDSP-v28.1.0.32.0504
eMMC-boot
Apr 2 2012,21:08:24
RUU
Update Fail!
* I did a factory reset and now passed that white screen...does anyone know what the problem was? is my phone rooted?
Click to expand...
Click to collapse
You cannot run an RUU on a boot loader unlocked phone. relock it first.
gunnyman said:
You cannot run an RUU on a boot loader unlocked phone. relock it first.
Click to expand...
Click to collapse
Thanks. Unfortunately I don't know how to do that. I guess I'll hold off 4.0.4 for now...
You need to read some more, before running things willy-nilly without the proper research.
I would advise against running the 2.20 RUU. As I already mentioned, it updates the hboot, which robs you of the ability to flash kernels and radios. There is no upside to it, since you can flash the ROM in other ways. Your phone is bootloader unlocked, and has full ability to flash kernels and radios. These are all good things. Don't take a step backward by flashing the 2.20 RUU.
If all you want is to update the ROM to 2.20, just flash the pre-rooted ROM (which will not replace the hboot): http://forum.xda-developers.com/showthread.php?t=1812459
But in fact, these are more recent versions:
http://forum.xda-developers.com/showthread.php?t=1789059
http://forum.xda-developers.com/showthread.php?t=1838135
Ya know, you guys CAN extract the rom.zip from 2.2x ruu and pull each image and flash them individually to get the 2.2x updates and keep your unlocked 1.09 hboot intact. That way you dont have to do the kernal flashing and what not. It will be fully updated, sbl's, radio everything.:beer:
18th.abn said:
Ya know, you guys CAN extract the rom.zip from 2.2x ruu and pull each image and flash them individually to get the 2.2x updates and keep your unlocked 1.09 hboot intact. That way you dont have to do the kernal flashing and what not. It will be fully updated, sbl's, radio everything.:beer:
Click to expand...
Click to collapse
how I wish I had done this.
Thanks a lot guys. I should have done some research. I bought this phone second hand thinking "unlocked" meant I could use it on other networks --didn't know the previous owner meant he unlocked the bootloader...hahaha...I guess i'll do some research to relock it.
y2janz said:
I guess i'll do some research to relock it.
Click to expand...
Click to collapse
Didn't read a thing I typed, apparently.
No need to relock it. Just run one of the stock rooted or custom ROMs in Development. Flash a new radio if you want.
I'm sorry, i really don't know how to do any of those stuff...
I just got the phone a couple of days ago and i am still waiting on my t-mobile non-gba micro sim that i ordered online, now im really not sure anymore if its unlocked to other networks...
I won't know til that sim card gets here, but in the mean time i'll do some reading on all those stuff you mentioned =)
I went to the HTC site and did a manual update, but I dont have sense 4.1. anyone know if the ATT version will get it?
plz help
I have a at&t one x I bought last night that is unlocked and I am using on telus.
The phone isn't rooted and is running on android 4.0.3 and HTC sence 4.0
When I try to update it nothing happens. My brother has the same phone thro telus and has received updates. I have went to settings about phoneat&t updates but when I search it does not do nothing .
An AT&T phone won't get the updates unless it's on their network it seems. Just download the ruu
Sent from my VENOMized HoxL
Bump. I unlocked my Rogers One X a while back, because I am planning on selling it. Since that time though, I have run an RUU on it. I no longer have another carrier's SIM card to test, so I just want to know if the unlock is permanent , or if it gets relocked when an RUU or factory reset is run.
The SIM unlock is permanent and will survive any RUU or factory reset.
Sent from my Evita
I need some major help, good folks of XDA. I've purchased this HTC One S from a guy who got it from Fido; naturally it was locked to Fido. I was planning on giving it to my girlfriend who is with Telus. I used cellunlocker.net to unlock the phone to find out that it didnt work with Telus. It would pick up signal then lose signal, pick up signal and lose signal every 10 seconds or so. I thought if I put a custom ROM on it might get me signal so I unlocked bootloader, rooted and put Viper ROM on it but it turns out it still wouldn't pick up network on Telus. So I decided to try it on my network, Rogers, and it picks up network but only 2G!!! Now my One S has the stable CM10 on it with baseband 1.08ts.50.02.16_10.08e.50.04L, unlocked bootloader with s-on, hboot 1.06, radio - 0.16.31501s.02
Here are the solutions I have tried so far to this problem;
-Tried to install multiple RUU both with ROGER001 CID and Super CID:11111111 and I couldn't install any of the RUUs, kept getting Error 155 with Rogers RUU and Check CID errors with other RUUs.
-Used to have 1.13 hboot but downgraded to 1.06 so I could change basebands and everytime I flash a different baseband, nothing changes after reboot.
-There is a recent jellybean rogers ota update zip but I dont know how to install it
please someone help!!! Thank you in advance and even more if my problem ever gets solved
Wrong forum for this kind of question. Have you tried flashing the telus radio? Also modifying the build.prop with the telus settings might help. Odd that you're having that issue on Rogers since Fido is the same network. Sounds like someone may have sold you a dud...
Sent from my HTC One S using xda premium
alltubetone said:
Wrong forum for this kind of question. Have you tried flashing the telus radio? Also modifying the build.prop with the telus settings might help. Odd that you're having that issue on Rogers since Fido is the same network. Sounds like someone may have sold you a dud...
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
Just asking, why is this the wrong (forum) as you say cuz this forum handles all devices does it not and I don't see anything wrong with his post?
SuperCID lets you flash any RUU, that error is most likely down to the bootloader being unlocked so if you really want to run a RUU then you want SuperCID and the lock the bootloader then run the RUU and also before you start the RUU be in fastboot mode first.
Darknites said:
SuperCID lets you flash any RUU, that or is most likely down to the bootloader being unlocked so if you really want to run a RUU then you want SuperCID and the lock the bootloader then run the RUU and also before you start the RUU be in fastboot mode first.
Click to expand...
Click to collapse
I did fastboot oem lock before flashing and got the same results; rather frustrating
alltubetone said:
Wrong forum for this kind of question. Have you tried flashing the telus radio? Also modifying the build.prop with the telus settings might help. Odd that you're having that issue on Rogers since Fido is the same network. Sounds like someone may have sold you a dud...
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
is it possible for a dud phone to have only 2g working and not get 3g?
dpk0875 said:
I did fastboot oem lock before flashing and got the same results; rather frustrating
Click to expand...
Click to collapse
Try hex editing mmcblk0p23 .... There is a method here for flashing RUUs that is discussed in the development forum in the sticky for downgrading your bootloader.... Try the hex edit, and then lock and then flash.
You could also try flashing a different baseband radio. For Canada, I didnt get the best reception from 1.08. You can d/l new baseband radios either for your phones radio partition or for CM10 (which uses a different location). There is a thread with radios collected in them in the development section.
I would try flashing a different radio before the RUU... The RUUs will upgrade your bootloader and then you cant flash new radios and other partition on SENSE seperately (ie ROMS wont flash properly and you will need to fastboot the boot.img every time)...
Funny , I unlocked my Original Fido One S to use it on Wind and it works perefectly. It should work on Telus ...have you tried inputting telus apn and restarting the phone after?
Okay i just bought a brand new ATT HTC One X and out of the box it comes with 4.1.1 and is build 3.18 with the 2.14 hboot.
i have flashed htc phones before and so im not new to it.
HOWEVER! lol
I was looking over the forum (and as confusing as it is with the different versions of the htc one x/xl/s/whatever else ) i believe this is the correct forum.
I am completely stock and those are my build and hboot out of the box. I want to root/unlock BL but so far no luck with any of the exploits.
Anyone here successfully rooted a 3.18 one x? or could i flash an RUU for the 2.20 build? how would i flash without first being rooted/custom recovery?
sorry if seem noob questions, been browsing the forums and google/bing all day and can't find a straight answer.
Bubbled said:
Anyone here successfully rooted a 3.18 one x? or could i flash an RUU for the 2.20 build? how would i flash without first being rooted/custom recovery?
Click to expand...
Click to collapse
Unfortunately the answers are no and no. JB is decent even on fully stock AT&T, you will just have to look the other way when scrolling through your app tray
I don't think the current root methods allow for the 3.18 build to gain root. Might be in the 2.20 boat all over again until someone can find a definite procedure.
soooooooooooooooooooooo lame. my rezound had viper rez rom and it was based off one x jb but had all the tweaks and stuff so right now its like a major downgrade lol
guess i'll cry and wait for the HTC One to come out later this month, since i only grabbed the one x cause it was literally 11 cents at walmart with a 14 day return and my rezound is acting up and randomly restarting/tanking battery!
sigh
thanks for the info though Groovy
Bubbled said:
Okay i just bought a brand new ATT HTC One X and out of the box it comes with 4.1.1 and is build 3.18 with the 2.14 hboot.
i have flashed htc phones before and so im not new to it.
HOWEVER! lol
I was looking over the forum (and as confusing as it is with the different versions of the htc one x/xl/s/whatever else ) i believe this is the correct forum.
I am completely stock and those are my build and hboot out of the box. I want to root/unlock BL but so far no luck with any of the exploits.
Anyone here successfully rooted a 3.18 one x? or could i flash an RUU for the 2.20 build? how would i flash without first being rooted/custom recovery?
sorry if seem noob questions, been browsing the forums and google/bing all day and can't find a straight answer.
Click to expand...
Click to collapse
I had exact the same issue and trust me I tried everything I could find. Finally I used exploit v2.1.1 and then rooted with Revolution HD Root using TWRP 2.4.1.0...
lightflier said:
I had exact the same issue and trust me I tried everything I could find. Finally I used exploit v2.1.1 and then rooted with Revolution HD Root using TWRP 2.4.1.0...
Click to expand...
Click to collapse
Try that and you'll get a brick. Those are tools/roms for the Tegra 3 One X.
Sent from my HTC One X using Tapatalk 2
iElvis said:
Try that and you'll get a brick. Those are tools/roms for the Tegra 3 One X.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
OK...
I thought something like this would work:
1. HTCdev bootloader unlock
2. Flash custom recovery (TWRP)
3. Achieve SuperCID (can do this via TWRP adb?)
4. Run S-OFF procedure
juicejuice said:
I thought something like this would work:
1. HTCdev bootloader unlock
2. Flash custom recovery (TWRP)
3. Achieve SuperCID (can do this via TWRP adb?)
4. Run S-OFF procedure
Click to expand...
Click to collapse
AT&T version of the One X isn't officially supported by htcdev to unlock boot loader (which is why many needed to change cid). If people who have the AT&T version are s-on, relocked, RUUed to 2.20, and flashed ota, they cannot root/unlock boot loader unless an amazing dev creates an exploit
Sent from my Nexus 7 using xda premium
panda_mode said:
AT&T version of the One X isn't officially supported by htcdev to unlock boot loader (which is why many needed to change cid). If people who have the AT&T version are s-on, relocked, RUUed to 2.20, and flashed ota, they cannot root/unlock boot loader unless an amazing dev creates an exploit
Click to expand...
Click to collapse
Damn that's annoying! If that were me I would sell my AT&T phone and with the cash buy an overseas One XL model with 32GB
juicejuice said:
I thought something like this would work:
1. HTCdev bootloader unlock
2. Flash custom recovery (TWRP)
3. Achieve SuperCID (can do this via TWRP adb?)
4. Run S-OFF procedure
Click to expand...
Click to collapse
The AT&T CID is blocked within HTCDev.com. A unique situation, almost certainly directed by AT&T. Therefore, on AT&T version of the One X, you need at least temp root to change the CID, then you can unlock the bootloader.
No root/temp root on AT&T 3.18 = no bootloader unlock. It also means no S-off (since you need root to change the CID).
redpoint73 said:
The AT&T CID is blocked within HTCDev.com. A unique situation, almost certainly directed by AT&T. Therefore, on AT&T version of the One X, you need at least temp root to change the CID, then you can unlock the bootloader.
No root/temp root on AT&T 3.18 = no bootloader unlock. It also means no S-off (since you need root to change the CID).
Click to expand...
Click to collapse
At least 1 person had success with xfactor so he could try but if it doesn't work then he's sol
Sent from my VENOMized HoxL
area51avenger said:
At least 1 person had success with xfactor so he could try but if it doesn't work then he's sol
Click to expand...
Click to collapse
I suppose it doesn't hurt to try. Otherwise, I'd just take the phone back, if root/S-off, etc. is important to the OP. I assume 11 cents is a subsidized price. So no point in using up an upgrade on a phone that can't be modded, if he wants to get the HTC One when its released.
OP may also check to see if the store has any older stock with 2.20 firmware (or any previous firmware version except 3.18). Phones with 3.18 out of the box must be very new, so I wouldn't be surprised if they had some older stock also.
I returned the one x today. will be looking into the t-mobile version of the HTC One which they told me comes out friday the 22nd. being a new phone i know i wont be able to do any mods or anything for a while, but that won't take long with the awesome Devs we have here! All the other models of the One X were sold out, and im guessing that someone realized that the new firmware was Out of Box so picked em all up. only had 2-3 stores with one each so its possible. now all the new stores have the new firmware no big deal, i'd prefer an HTC DNA anyways, but we'll see what the One is all about.
redpoint73 said:
The AT&T CID is blocked within HTCDev.com. A unique situation, almost certainly directed by AT&T. Therefore, on AT&T version of the One X, you need at least temp root to change the CID, then you can unlock the bootloader.
No root/temp root on AT&T 3.18 = no bootloader unlock. It also means no S-off (since you need root to change the CID).
Click to expand...
Click to collapse
I tried Xfactor and it said the cid for my device out of box 3.18 firmware 2.14 hboot was CID Cws__001.
Techinstein said:
I tried Xfactor and it said the cid for my device out of box 3.18 firmware 2.14 hboot was CID Cws__001.
Click to expand...
Click to collapse
Yes, the CID for AT&T is cws_001 on all of the previous firmware versions, as well. This hasn't changed. cws__001 is blocked on HTCDev.com.
So i have the key for my past bootloader unlock can i use it?
Enviado desde mi HTC One X usando Tapatalk 2
coldrazor said:
So i have the key for my past bootloader unlock can i use it?
Click to expand...
Click to collapse
Yes.
If you were unlocked before, how did you get on the 3.18 RUU/OTA? Did you change your CID back to AT&T's CID? Or did you S-off.
If you are S-off, no need to unlock the bootloader.
redpoint73 said:
Yes.
If you were unlocked before, how did you get on the 3.18 RUU/OTA? Did you change your CID back to AT&T's CID? Or did you S-off.
If you are S-off, no need to unlock the bootloader.
Click to expand...
Click to collapse
Yes, you still need to have the bootloader unlocked to write to recovery and some other stuff. I tested this myself.
exad said:
Yes, you still need to have the bootloader unlocked to write to recovery and some other stuff. I tested this myself.
Click to expand...
Click to collapse
Really? Kinda negates part of the purpose of having S-off, doesn't it?