So has anyone managed to use the changed cid after updating to the new 1.85 to re unlock the downloader?
I'm still showing 1111111 cid, but neither the old unlock token, or even new ones will unlock the darn downloader.
I think I saw someone say they managed it, but cant find the post.
Sent from my HTC One X using xda premium
I have root and unlock bl on 1.85.
I finally got it to work! I had to manually RELOCK the 1.85 bootloader (even though it said it was relocked already). Then hit the unlock again. Bam. Thank goodness!
So you re-locked, flashed 1.85, manually re-locked again, and then unlocked?
How did you achieve root? Just by flashing the recovery and SuperSU?
Yes to all. Now im trying to find the right supersu zip to use in rec.
gtkansan said:
Yes to all. Now im trying to find the right supersu zip to use in rec.
Click to expand...
Click to collapse
it's in the thread on the development forum. its the root 1.85 one that only has like 3 posts
http://forum.xda-developers.com/showthread.php?t=1673935
Fantastic. Thank you! Worked and Im finally back up!
After doing the following steps, I had to manually install Busybox from the market.
so if im on rooted 1.73, i can run supercid, run thru htcdev to unlock, manually relock, ruu 1.85, manually relock, unlock thru htcdev, and then can flash CWM & install SuperSU for root?
malox23 said:
so if im on rooted 1.73, i can run supercid, run thru htcdev to unlock, manually relock, ruu 1.85, manually relock, unlock thru htcdev, and then can flash CWM & install SuperSU for root?
Click to expand...
Click to collapse
seems to be correct. Thats exactly what I'm doing/about to do
SkizzMcNizz said:
seems to be correct. Thats exactly what I'm doing/about to do
Click to expand...
Click to collapse
cool, let me know how it goes...i just reg'd at htcdev.
gtkansan said:
Fantastic. Thank you! Worked and Im finally back up!
Click to expand...
Click to collapse
when you say you manually re-locked what do you mean? When I try to re-lock it says already relocked.
---------- Post added at 03:32 AM ---------- Previous post was at 03:28 AM ----------
I can't get it to take. It always still says relocked.
SkizzMcNizz said:
when you say you manually re-locked what do you mean? When I try to re-lock it says already relocked.
---------- Post added at 03:32 AM ---------- Previous post was at 03:28 AM ----------
I can't get it to take. It always still says relocked.
Click to expand...
Click to collapse
Just keep on trying, it took me at least 50 tries to get mine unlocked again.
Sent from my HTC One X using xda premium
Related
So my ATT One X is soft bricked and when I run RUU_Evita_UL_Cingular_US-1.82.502 It gives me the customer ID error.
I rooted, unlocked bootloader, and flashed CMR, but it is now no longer rooted and the bootloader is relocked.
I did modify the CID to "11111111" to unlock the bootloader, but without me being rooted I am unable to put the original "mmcblk0p4" back on (idk if that even matters.) I have no backups and absolutely everything is erased.
I did flash the stock recovery img file, but I don't know if it was relevant to international One X or if there is one specifically for ATT One X.
I guess a fix would be making a goldcard, without an sd card somehow....
Thanks for the Help.
Never seen that error before. Have you tried running the 1.85 RUU? I have RUU'd multiple times while still having the SuperCID so I don't think that's the issue.
Sent from my HTC One X using xda premium
_MetalHead_ said:
Never seen that error before. Have you tried running the 1.85 RUU? I have RUU'd multiple times while still having the SuperCID so I don't think that's the issue.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
I was actually using the 1.7 RUU
I'll try 1.82 then 1.85. Hopefully that will work.
Thanks for the quick reply! :good:
Have you tried to relocking the boot loader?
fastboot oem lock
Then run ruu.
The ruu will flash the stock recovery.
Sent from my HTC One X using xda premium
Still not going through and getting same error....
Any ideas?
Thanks.
Are in Canada? That would mean u need to use the rogers ruu, not the evita. Or, are u positive u changed your cid to 11111111 and not ROGER001. There were tutorials in the beginning doing this before supercid 11111111 was found. But customer I'd means either, rogers or evita typically. Evita ruu won't work on rogers and vice versa:thumbup:
Sent from my HTC One X using xda premium
18th.abn said:
Are in Canada? That would mean u need to use the rogers ruu, not the evita. Or, are u positive u changed your cid to 11111111 and not ROGER001. There were tutorials in the beginning doing this before supercid 11111111 was found. But customer I'd means either, rogers or evita typically. Evita ruu won't work on rogers and vice versa:thumbup:
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
No. I'm in US on ATT network. And yes I did change the CID to 11111111 because I used that method to unlock my bootloader.
I've tried several RUUs for my phone and still get same error. If I were to verify I had changed the CID I would have to be rooted.
Is it possible to root a soft-bricked device????
What's the error number?
Depending on what it is, there are different fixes.
if you can still do fastboot commands I'd unlock the bootloader again then push the twrp with USB support.
Once you do that you can flash the rom of your choice by copying it to your phone from TWRP.
---------- Post added at 08:51 PM ---------- Previous post was at 08:44 PM ----------
I was stuck with a soft brick when I interrupted the installation of a ROM that was a bad download.
I was able to do what I said in my previous post and it fixed me right up
gunnyman said:
What's the error number?
Depending on what it is, there are different fixes.
if you can still do fastboot commands I'd unlock the bootloader again then push the twrp with USB support.
Once you do that you can flash the rom of your choice by copying it to your phone from TWRP.
Click to expand...
Click to collapse
It's error #131.
Can I unlock bootloader without root? I have tried running the adb shell in cmd, but the device cannot be found.
I was able to check if I had the SuperCID, and unfortunately it has changed back to stock.
ArcriusOneX said:
It's error #131.
Can I unlock bootloader without root? I have tried running the adb shell in cmd, but the device cannot be found.
I was able to check if I had the SuperCID, and unfortunately it has changed back to stock.[/QUOTEhmm I've never switched my CID back so I am not sure if it will work, but try this
get to the bootloader (power volume down)
from bootloader select fastboot
once in fastboot mode
with phone plugged into usb type
fastboot flash unlocktoken Unlock_code.bin just like you did to unlock the bootloader in the first place just make sure that adb, fastboot, and the unlock.bin file are all in the same directory on your computer
once you are unlocked you should be able to do the rest
Error 131 is related to using the wrong RUU for your CID SuperCID will override this error. If you flashed your CID back to the AT&T one the only RUU you can flash (I think) is the 1.85 one
Click to expand...
Click to collapse
gunnyman said:
ArcriusOneX said:
It's error #131.
Can I unlock bootloader without root? I have tried running the adb shell in cmd, but the device cannot be found.
I was able to check if I had the SuperCID, and unfortunately it has changed back to stock.[/QUOTEhmm I've never switched my CID back so I am not sure if it will work, but try this
get to the bootloader (power volume down)
from bootloader select fastboot
once in fastboot mode
with phone plugged into usb type
fastboot flash unlocktoken Unlock_code.bin just like you did to unlock the bootloader in the first place just make sure that adb, fastboot, and the unlock.bin file are all in the same directory on your computer
once you are unlocked you should be able to do the rest
Error 131 is related to using the wrong RUU for your CID SuperCID will override this error. If you flashed your CID back to the AT&T one the only RUU you can flash (I think) is the 1.85 one
Click to expand...
Click to collapse
Yeah I actually was able to unlock the bootloader already. Sorry I spoke too soon!
How do I go about pushing the twrp?
Click to expand...
Click to collapse
ArcriusOneX said:
gunnyman said:
Yeah I actually was able to unlock the bootloader already. Sorry I spoke too soon!
How do I go about pushing the twrp?
Click to expand...
Click to collapse
download it from and follow the directions here http://forum.xda-developers.com/showthread.php?t=1703626
very simple and straightforward
Click to expand...
Click to collapse
gunnyman said:
ArcriusOneX said:
download it from and follow the directions here http://forum.xda-developers.com/showthread.php?t=1703626
very simple and straightforward
Click to expand...
Click to collapse
SUCCESS!!!! :laugh::laugh::laugh:
Thank you so much! You resurrected my phone!
I'm guessing this is similar to CMR?? Looks a lot nicer.
Click to expand...
Click to collapse
ArcriusOneX said:
gunnyman said:
SUCCESS!!!! :laugh::laugh::laugh:
Thank you so much! You resurrected my phone!
I'm guessing this is similar to CMR?? Looks a lot nicer.
Click to expand...
Click to collapse
yeah I like it better myself it's faster.
glad you're all fixed
Click to expand...
Click to collapse
Hi all, I'm new here, but I have a major problem. I had rooted my phone with the ViperXL rom, and the all-in-one tool kit. Recently I was planning on returning to stock, so I attempted to unroot the phone. I'm not very savvy when it comes to rooting, so the first thing I did was stupidly relock the bootloader.. big mistake, because now I'm stuck on the bootloader screen and NOTHING is working, not recovery, not factory reset. Please, I need some serious help, I have no phone.
Download the ruu for your phone they are in the general section hook your phone to your computer and run the ruu if you want complete stock if not just reunlock your bootloader
Sent from my HTC One X using Tapatalk 2
Download appropriate ruu from this thread
http://forum.xda-developers.com/showthread.php?p=37227608
Sent from my Nexus 4 using xda premium
I think once you relock, its expecting you to RUU, and everything is wiped. Just get the correct RUU and run it, as suggested above.
urbanismm said:
Recently I was planning on returning to stock, so I attempted to unroot the phone. I'm not very savvy when it comes to rooting, so the first thing I did was stupidly relock the bootloader.
Click to expand...
Click to collapse
Actually, that's exactly what you do when you're returning to stock. Relock, run RUU, done.
---------- Post added at 08:15 AM ---------- Previous post was at 08:14 AM ----------
redpoint73 said:
I think once you relock, its expecting you to RUU, and everything is wiped.
Click to expand...
Click to collapse
I think things on your sdcard are only wiped when you unlock. The last time I relocked, everything was still there until I unlocked again.
Hi all,
I am having one issue with my AT&T HTC One X. I had my HOX rooted with CM10 installed. I unrooted it flashed at&t rom through RUU. After that (without reading enough about it) I updated my phone to JB update and got bricked. I sent out my phone to mobiletechvideos and they did an awesome job in JTAGing my phone and its running fine now with official At&t ROM ( and all its bloat) and its running on JB 4.1.1.
Now as my phone is still under warranty I wanna try taking it to the at&t device support center and get it replaced (I know its void already but I still wanna try it) The question is that I still have Superuser installed in there and I dont see any options in it to uninstall it. I also download root checker app which says that I still have root. I went into bootloader and it says LOCKED hboot 2.14. Now how can I turn it to complete stock (out of the box) without SU and root so that i can TRY to get it replaced under the warranty. Thanks!!
Isn't SU simply an application that's installed?
Not sure what they check for at the service center (probably varies depending on the person), but unrooting (possible?), locking the bootloader, and making sure that 'TAMPERED' doesn't show when booting into the bootloader is probably a good idea. Pretty sure that once they see 'TAMPERED', they'll say your warranty is hosed, and you're stuck with your current device.
Just my thoughts. I would search XDA for threads that have similar experiences and see what they have to say before attempting that, of course.
You can use ES file explorer or Root explorer to delete super user.
Sent from my HTC One X using xda premium
so did you request for them to put jellybean back on it? i just sent my phone in but i requested for s-off while they are fixing it. i wonder if they are goin to put jellybean on mine and whether or not ill still be able to root afterwards
jrlatta said:
so did you request for them to put jellybean back on it? i just sent my phone in but i requested for s-off while they are fixing it. i wonder if they are goin to put jellybean on mine and whether or not ill still be able to root afterwards
Click to expand...
Click to collapse
Yes I asked them to update ROM to 4.1.1 and thats what they did.
My phone is on JB 4.1.1 with software version 3.18
I just rebooted to bootloader and saw that its locked but its S-OFF, can I install a custom ROM? Attached is the screen shot from the bootloader
uzair_rock said:
My phone is on JB 4.1.1 with software version 3.18
I just rebooted to bootloader and saw that its locked but its S-OFF, can I install a custom ROM? Attached is the screen shot from the bootloader
Click to expand...
Click to collapse
If i an reading this correctly, you have s off and supe cid. You need to unlock the boot loader but i dont know if that is possible. It is just werid they kept it locked, but it is s off. I am sure htc will see that
Sent from my Carbon-ize Evita using xda-developers app
I believe there is a way to trick htc dev If it will allow you to change cid. I have seen where people would change it to a rogers cid and use dev to unlock since there are no restrictions like at&t has. But I would research this carefully before any attemp is made to do it. Forget where I read it. But it might be worth looking into.
Sent from my HTC One X using xda premium
Venomtester said:
I believe there is a way to trick htc dev If it will allow you to change cid. I have seen where people would change it to a rogers cid and use dev to unlock since there are no restrictions like at&t has. But I would research this carefully before any attemp is made to do it. Forget where I read it. But it might be worth looking into.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Oh wow, that seems sweet. Since Rogers uses the "evita" code name. I wonder if it would also work for Telstra as well. Gonna google see. If that is the case you (or where ever you read it from) just solve a handful of mysteries for us AT&T folks.
EDIT: It's by our very own redpoint73. Amazing what a quick google can do http://forum.xda-developers.com/showthread.php?t=1671237
By now I have realized that I have root, SUID and S-OFF. But the question is how do I get my boot loader unlocked?? I need that unlocked to flash custom ROMs and radios....help needed guys.
Thanks
uzair_rock said:
By now I have realized that I have root, SUID and S-OFF. But the question is how do I get my boot loader unlocked?? I need that unlocked to flash custom ROMs and radios....help needed guys.
Thanks
Click to expand...
Click to collapse
thats what i said, i was trying to understand how you have s-off, but the bootloader is locked (not re-locked)
do you have the unlock_code.bin that you first used?
uzair_rock said:
By now I have realized that I have root, SUID and S-OFF. But the question is how do I get my boot loader unlocked?? I need that unlocked to flash custom ROMs and radios....help needed guys.
Click to expand...
Click to collapse
Just to to HTCDev.com and follow the bootloader unlock process. Since you have SuperCID, it will work.
uzair_rock said:
By now I have realized that I have root, SUID and S-OFF. But the question is how do I get my boot loader unlocked?? I need that unlocked to flash custom ROMs and radios....help needed guys.
Thanks
Click to expand...
Click to collapse
Fastboot oem writecid 22222222
Then unlock with htcdev
If that Fastboot command doesn't work, (not sure the the bootloader needs to be unlocked for it to work) then hex edit your Cid. And then unlock with htcdev
Sent from my HTC One X using xda app-developers app
---------- Post added at 02:38 PM ---------- Previous post was at 02:37 PM ----------
redpoint73 said:
Just to to HTCDev.com and follow the bootloader unlock process. Since you have SuperCID, it will work.
Click to expand...
Click to collapse
I thought it didn't accept 1s anymore?
Sent from my HTC One X using xda app-developers app
Herc08 said:
thats what i said, i was trying to understand how you have s-off, but the bootloader is locked (not re-locked)
do you have the unlock_code.bin that you first used?
Click to expand...
Click to collapse
No idea bro! I bricked my phone, then sent it to get JTAGed, I asked them to update my phone to 4.1.1 and this is what I got.
exad said:
I thought it didn't accept 1s anymore?
Click to expand...
Click to collapse
Folks have been reporting still being able to use 11111111 (even after it was reported that HTC was blocking it), while others have had to change to 22222222. There doesn't seem to be any rhyme or reason. But you're right, if 11111111 doesn't work for the OP, they should try 22222222.
So I successfully unlocked my boot loader. So now I have root, S-OFF and unlocked bootloader. The question is now I want to flash a custom ROM i.e. ViperXL. Do I need to flash boot.img first like it is with 1.14 hboot?
Not if you are s-off.
Sent from my HTC One X using xda premium
---------- Post added at 08:20 PM ---------- Previous post was at 08:17 PM ----------
What recovery are you using?
Sent from my HTC One X using xda premium
Venomtester said:
Not if you are s-off.
Sent from my HTC One X using xda premium
---------- Post added at 08:20 PM ---------- Previous post was at 08:17 PM ----------
What recovery are you using?
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
But I am on the 3.18 firmware with JB 4.1.1. I just need to flash the ROM in TWRP?
uzair_rock said:
But I am on the 3.18 firmware with JB 4.1.1. I just need to flash the ROM in TWRP?
Click to expand...
Click to collapse
Since you are s-off, you can just flash in twrp as normal. You can fastboot the boot.img if you want, but it isnt necessary. So if you want to download the zip straight from your phone, you can...no pc needed. S-off is almost like a super phone...
Yes. S-Off makes its possible to flash roms without flashing boot image separately. Just flash the zip from twrp.
Sent from my HTC One X using xda premium
I want to be able to flash the latest CM10.1 for my AT&T HTC One X. Details about the phone-
Unlocked with HTCDev. Hboot 1.14.0002. Have latest TWRP flashed. Says TAMPERED, UNLOCKED, and S-ON.
I tried a RUU to update the Hboot, but that didn't work.
How can I update the firmware so I can run latest ROMs like CM10.1? I've looked at similar questions, but the answers were for the International Version of the HTC One X.
Any help or suggestions are appreciated.
seth50k said:
I want to be able to flash the latest CM10.1 for my AT&T HTC One X. Details about the phone-
Unlocked with HTCDev. Hboot 1.14.0002. Have latest TWRP flashed. Says TAMPERED, UNLOCKED, and S-ON.
I tried a RUU to update the Hboot, but that didn't work.
How can I update the firmware so I can run latest ROMs like CM10.1? I've looked at similar questions, but the answers were for the International Version of the HTC One X.
Any help or suggestions are appreciated.
Click to expand...
Click to collapse
S-off
Run 3.18 ruu (no need to relock with s-off)
Relash recovery
Flash cm10
Sent from my HTC One XL using xda premium
31ken31 said:
S-off
Run 3.18 ruu (no need to relock with s-off)
Relash recovery
Flash cm10
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Ok, so here's the 2nd question. Somehow I managed to wipe whatever ROM I had on here (CleanROM I think), so it doesn't boot to anything. I've tried flashing CleanROM 6 and 3.20.401.1 Odexed, both error out in TWRP.
I'm assuming I've managed to softbrick it?
seth50k said:
Ok, so here's the 2nd question. Somehow I managed to wipe whatever ROM I had on here (CleanROM I think), so it doesn't boot to anything. I've tried flashing CleanROM 6 and 3.20.401.1 Odexed, both error out in TWRP.
I'm assuming I've managed to softbrick it?
Click to expand...
Click to collapse
Not sure 3.20.401.1 is but what did you do? You didn't do factory reset from bootloader did you?
RollTribe said:
Not sure 3.20.401.1 is but what did you do? You didn't do factory reset from bootloader did you?
Click to expand...
Click to collapse
I might have. What I was trying to do is clean out the phone to sell it, then get it updated, etc. I know in TWRP I ran probably every type of wipe, and I may have run Factory reset from the bootloader. It was a while ago and I set it aside, and now i've come back to it trying to get this phone sorted out.
seth50k said:
I might have. What I was trying to do is clean out the phone to sell it, then get it updated, etc. I know in TWRP I ran probably every type of wipe, and I may have run Factory reset from the bootloader. It was a while ago and I set it aside, and now i've come back to it trying to get this phone sorted out.
Click to expand...
Click to collapse
If you did, then you're not gonna be able to so anything with ROMs. Run an ruu, reunlock, and report back.
RollTribe said:
If you did, then you're not gonna be able to so anything with ROMs. Run an ruu, reunlock, and report back.
Click to expand...
Click to collapse
I've tried running RUU, it gets about halfway and fails. Do I need to flash the stock recovery and relock first, then run a RUU?
U need to relock the bootloader
Use command prompt
"Fastboot oem lock" from fastboot then run the ruu.... I recommend getting s-off as well is very easy and fast and it will save u a lot of troubles in the future plus u will not have to lock the bootloader to flash an ruu
Sent from my HTC One X using xda premium
If you ruu with s-on and supercid you brick.
Be careful with your advice breeze. You'll cause him a brick.
Sent from my One X using xda app-developers app
breezedragon said:
U need to relock the bootloader
Use command prompt
"Fastboot oem lock" from fastboot then run the ruu.... I recommend getting s-off as well is very easy and fast and it will save u a lot of troubles in the future plus u will not have to lock the bootloader to flash an ruu
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Yeah, but you need a ROM working to even do the s-off process. So getting a ROM loaded is my main priority at this point. I can get into Bootloader/Fastboot, and I can still get to TWRP. Flashing a ROM from TWRP isn't working, and neither is running the latest RUU from fastboot. I get ERROR 159 when I try to run the latest RUU. So do I need to fastboot oemlock, then try again?
Perhaps running the RUU that was previously on it would work? 2.20, is what firmware was on it last.
seth50k said:
Yeah, but you need a ROM working to even do the s-off process. So getting a ROM loaded is my main priority at this point. I can get into Bootloader/Fastboot, and I can still get to TWRP. Flashing a ROM from TWRP isn't working, and neither is running the latest RUU from fastboot. I get ERROR 159 when I try to run the latest RUU. So do I need to fastboot oemlock, then try again?
Perhaps running the RUU that was previously on it would work? 2.20, is what firmware was on it last.
Click to expand...
Click to collapse
Yeah, you have to run the same/later ruu if you're not S-Off. And you'll have to relock and you can flash stock recovery to be safe (but I think it flashes for you).
---------- Post added at 02:12 PM ---------- Previous post was at 02:11 PM ----------
exad said:
If you ruu with s-on and supercid you brick.
Be careful with your advice breeze. You'll cause him a brick.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
That's not necessarily true, I've ruu'ed with s-on and SuperCID and was fine. It is risky, though.
Unlock, flash a sense rooted rom, soff and then ruu up to 3.18
Sent from my One X using xda app-developers app
RollTribe said:
Yeah, you have to run the same/later ruu if you're not S-Off. And you'll have to relock and you can flash stock recovery to be safe (but I think it flashes for you).
---------- Post added at 02:12 PM ---------- Previous post was at 02:11 PM ----------
That's not necessarily true, I've ruu'ed with s-on and SuperCID and was fine. It is risky, though.
Click to expand...
Click to collapse
I'm able to run the 2.20 RUU so far after relocking, it's about 3/4 of the way done. After this i'll try the latest RUU, then go from there to re-unlock, then S-OFF, THEN reflash TWRP?
seth50k said:
I'm able to run the 2.20 RUU so far after relocking, it's about 3/4 of the way done. After this i'll try the latest RUU, then go from there to re-unlock, then S-OFF, THEN reflash TWRP?
Click to expand...
Click to collapse
Yup, you can swap the last two if you want
RollTribe said:
Yup, you can swap the last two if you want
Click to expand...
Click to collapse
Well shoot...got so close. 2.20 RUU worked, then I did the latest RUU, which completed fine, but now the phone won't turn on, and won't even show a red LED charging indicator. WTF...
seth50k said:
Well shoot...got so close. 2.20 RUU worked, then I did the latest RUU, which completed fine, but now the phone won't turn on, and won't even show a red LED charging indicator. WTF...
Click to expand...
Click to collapse
Yep, looks like it's bricked. http://forum.xda-developers.com/showthread.php?t=2181929
seth50k said:
Well shoot...got so close. 2.20 RUU worked, then I did the latest RUU, which completed fine, but now the phone won't turn on, and won't even show a red LED charging indicator. WTF...
Click to expand...
Click to collapse
Yeah, you have to s-off before running latest ruu. Damn sorry if I was unclear man.
RollTribe said:
Yeah, you have to s-off before running latest ruu. Damn sorry if I was unclear man.
Click to expand...
Click to collapse
It's alright, just a little surprised given the fact that HTC allows you to unlock and such, but their own RUU bricks the phone if in such a state.
I think it might be under warranty still, might try that route. Thanks for the help.
Sorry about your phone. It's Jtagg or new phone.
---------- Post added at 02:34 PM ---------- Previous post was at 02:34 PM ----------
seth50k said:
It's alright, just a little surprised given the fact that HTC allows you to unlock and such, but their own RUU bricks the phone if in such a state.
I think it might be under warranty still, might try that route. Thanks for the help.
Click to expand...
Click to collapse
They state on their site that after unlocking the bootloader, RUU/OTA could brick you.
If you plan to try warranty with HTC, do not mention that you unlocked. They will charge you 200 straight up no matter what you say.
RollTribe said:
That's not necessarily true, I've ruu'ed with s-on and SuperCID and was fine. It is risky, though.
Click to expand...
Click to collapse
But was it the 3.18? It applies specifically for the AT&T 3.18 (and for some 3.17 JB RUUs on other carriers, and reported by some folks on this forum).
If you were able to run the 3.18 RUU successfully with SuperCID and S-on, I believe this is the first I've heard of it.
---------- Post added at 12:37 PM ---------- Previous post was at 12:33 PM ----------
seth50k said:
It's alright, just a little surprised given the fact that HTC allows you to unlock and such, but their own RUU bricks the phone if in such a state.
Click to expand...
Click to collapse
SuperCID as implemented on the AT&T One X is a mod/hack, and therefore not explicitly "allowed" by HTC. They can't really be held responsible for the effects of it.
SuperCID shouldn't be "expected" to brick under these conditions (worked fine with pre-JB RUUs), and nobody here has really been able to explain exactly why the phone bricks from SuperCID. But unfortunately, it does.
My bootloader is tampered but locked and i desperatly need to unlock it , i have temp root from weaksause app and that it. i tryed hexing and tryed programs from before 4.2.2. i was wondering if i do a factory reset on the phone will it turn back to 4.1.2 since i ruu'ed it to 4.2.2 ?
Don't reset in boot loader. Adds probs
---------- Post added at 01:05 AM ---------- Previous post was at 01:03 AM ----------
Um. Tampered does mean unlocked
marknoll said:
Don't reset in boot loader. Adds probs
---------- Post added at 01:05 AM ---------- Previous post was at 01:03 AM ----------
Um. Tampered does mean unlocked
Click to expand...
Click to collapse
Tampered doesn't mean unlocked.
thatkidzac said:
My bootloader is tampered but locked and i desperatly need to unlock it , i have temp root from weaksause app and that it. i tryed hexing and tryed programs from before 4.2.2. i was wondering if i do a factory reset on the phone will it turn back to 4.1.2 since i ruu'ed it to 4.2.2 ?
Click to expand...
Click to collapse
Do you have the at&t model? Factory resetting won't roll back the RUU, it'll only wipe user data.
Sent from my Evita
timmaaa said:
Tampered doesn't mean unlocked.
Do you have the at&t model? Factory resetting won't roll back the RUU, it'll only wipe user data.
Sent from my Evita
Click to expand...
Click to collapse
Yes it ATT and ok but is there another way im already root all i need is recovery which need unlock bootloader
even if there is an downgrade would be helpful i had 4.1.2 before but no root programs worked then i just ruu'ed to see if it would work nd didnt
There's no way for you to unlock your bootloader, because there's no exploit for you to get SuperCID on the latest at&t update. You should have unlocked before you took the update. All it would have taken while you were on 4.1.2 was some research to find the exploit for that specific firmware, which does exist and does work, but now that you've taken the update there's no way for you to roll back. Sorry, but you're stuck.
Sent from my Evita
timmaaa said:
Tampered doesn't mean unlocked.
Do you have the at&t model? Factory resetting won't roll back the RUU, it'll only wipe user data.
Sent from my Evita
Click to expand...
Click to collapse
Oops..my bad. I thought it did. [emoji336]
marknoll said:
Oops..my bad. I thought it did. [emoji336]
Click to expand...
Click to collapse
Unlocked = unlocked
Tampered = non-official software (root)
Sent from my Evita
OK. Thanks. I thought it meant unlocked. ?