Database Info

Unable to re-unlock bootloader--HELP!

So I am ATT One X and was on Magnolia rom 1.82. I tried to upgrade to the latest RUU by re-locking the bootloader. Because I used the Rogers CID before to Unlock, I had to change the CID to SuperCID before upgrading.
After I changed from Rogers CID to SuperCID, relocked, upgraded to 1.85 RUU, I attempted to re-unlock via HTC-DEV. I went through all the steps and successfully received and unlock code and successfully flashed it.
HOWEVER!!!! The bootloader still says RELOCKED and I can't flash stuff.
I tried changing the CID back to ROGER001 and running the original unlock key but that failed to i went through HTCDEV with that CID and got the unlock code, successfully flashed it, but still had the RELOCKED bootloader.
Did I mess something up???? Please tell me i didn't....Any help is appreciated

b3nman said:
So I am ATT One X and was on Magnolia rom 1.82. I tried to upgrade to the latest RUU by re-locking the bootloader. Because I used the Rogers CID before to Unlock, I had to change the CID to SuperCID before upgrading.
After I changed from Rogers CID to SuperCID, relocked, upgraded to 1.85 RUU, I attempted to re-unlock via HTC-DEV. I went through all the steps and successfully received and unlock code and successfully flashed it.
HOWEVER!!!! The bootloader still says RELOCKED and I can't flash stuff.
I tried changing the CID back to ROGER001 and running the original unlock key but that failed to i went through HTCDEV with that CID and got the unlock code, successfully flashed it, but still had the RELOCKED bootloader.
Did I mess something up???? Please tell me i didn't....Any help is appreciated
Click to expand...
Click to collapse
Check for errors in the command prompt when you try to unlock. What does it say?

dimgl said:
Check for errors in the command prompt when you try to unlock. What does it say?
Click to expand...
Click to collapse
none whatsoever everything goes flawlessly. just when i reboot into the bootloader it says RELOCKED at the top.

Do you think its because i unlocked with the Rogers CID and then Re-unlocked with the Super CID?

I think some users reported having to attempt BL unlock multiple times on 1.85 before it worked. Pretty sure I read that on one of the bootloader unlock threads in Development (can't remember if it was the one-click SuperCID thread, or the "original" hex editor method thread).
Mine worked the first try on 1.85. I used the same bin file that unlocked 1.73.

redpoint73 said:
I think some users reported having to attempt BL unlock multiple times on 1.85 before it worked. Pretty sure I read that on one of the bootloader unlock threads in Development (can't remember if it was the one-click SuperCID thread, or the "original" hex editor method thread).
Mine worked the first try on 1.85. I used the same bin file that unlocked 1.73.
Click to expand...
Click to collapse
Thats the thing. I changed the CID from when i originally Unlocked it. Has anyone successfully done this?

SOLVED
I figured it out.
When you select power off or reset from the Power Menu, OR use the adb reboot command from command line, it doesn't really completely power off. So you have to actually hold the power button until it completely powers down and THEN start the bootloader for the the unlocked change to take effect. At least thats what happened with me. Your mileage may vary....

Make sure when you boot up to turn on usb debugging you also turn off fast boot (settings/power) its not the fast boot we're used to but its HTCs way of not completely powering off the phone to give a faster boot time. I personally had to run the unlock twice to get the bootloader to say unlocked instead of relocked.
Hope this helps.
Sent from my HTC One X using xda premium

Dear god, this thread should be a sticky. After 30 tries, I disable fastboot, power off completely using the power button and when I booted to the bootloader, it was unlocked.

[SOLVED!!] Customer ID Error on RUU

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

Urgent please. How do i return my phone to stock RUU from customer rom?

Hello,
I need to return my phone to stock really fast. Can anyone quickly tell me how to go from the leaked Cleanrom 3.1 to the 1.85 ruu that was released? Do i need to relock the bootloader? If so, how? Anything i need to do with CID?

Relock bootloader, then run the RUU.
Sent from my HTC One X using xda premium

Ok just did the fastboot oem lock, tried to reboot but it wouldnt. So now im running the RUU while still at the bootloader screen. The RUU seems to be running...

jason.hamilton said:
Ok just did the fastboot oem lock, tried to reboot but it wouldnt. So now im running the RUU while still at the bootloader screen. The RUU seems to be running...
Click to expand...
Click to collapse
That's all you need to do. Note that the RUU install will take a LONG time, longer than the 10 minutes it says it will take. This seems to be due to superCID

Worked like a charm. Thank you very much =). It did take a while.

Bootloader will not unlock

Good evening,
I completed the HBOOT downgrade found in the developer forum with no issues. Once on 1.06, I attempted to unlock the bootloader and it did not work. The bootloader unlock screen appears but once the phone reboots the bootloader remains relocked. I ran two RUUs (1.09 and 1.14 respectively) but I am still plagued by the relocked bootloader. I noticed my device ID changes with each attempt. I read the entire downgrade forum but none of the solutions helped me. Please assist.
Thank you

chanoelmano said:
Good evening,
I completed the HBOOT downgrade found in the developer forum with no issues. Once on 1.06, I attempted to unlock the bootloader and it did not work. The bootloader unlock screen appears but once the phone reboots the bootloader remains relocked. I ran two RUUs (1.09 and 1.14 respectively) but I am still plagued by the relocked bootloader. I noticed my device ID changes with each attempt. I read the entire downgrade forum but none of the solutions helped me. Please assist.
Thank you
Click to expand...
Click to collapse
Em I'm sure you can't downgrade with a locked bootloader. The only thing that comes to mind is to keep trying, I had to do it a few times myself.

I completed the downgrade. I wish to unlock the bootloader. I flashed the RUUs to see if they would allow me to do so on a different HBOOT

chanoelmano said:
I completed the downgrade. I wish to unlock the bootloader. I flashed the RUUs to see if they would allow me to do so on a different HBOOT
Click to expand...
Click to collapse
I still don't see this is even possible without the bootloader being already unlocked.

My bootloader was unlocked before I downgraded. I had to lock it so that I could flash RUU. I am now having trouble unlocking it again.

chanoelmano said:
My bootloader was unlocked before I downgraded. I had to lock it so that I could flash RUU. I am now having trouble unlocking it again.
Click to expand...
Click to collapse
Why did you flash the RUU? there was no need for that. All I can say is keep trying. What was you Hboot before downgrading?

good luck mate i have the same problem and i can't do anything

My hboot was 1.14 I was having radio issues so I downgraded. Once on 1.06 I could not get my bootloader unlocked so I flashed RUUs to see if I could work from there.

Even now nothing has helped you?

I think you messed it up with running the RUU when there was no need too. Maybe try getting the JB OTA update and try again after.

Very well. Do you know where I can obtain the JB update? I

chanoelmano said:
Very well. Do you know where I can obtain the JB update? I
Click to expand...
Click to collapse
By running a RUU and just wait in till you get the update.

alexskin said:
good luck mate i have the same problem and i can't do anything
Click to expand...
Click to collapse
I continually flashed the unlock code and eventually I was able to unlock the bootloader.

my problem is that i can't get the token from htcdevs, i all ways get an error. i'll try with an old token and see if it works

[Q] Did something really stupid, Please help.

Ok, so I installed Cleanrom 6 and flashed Elemental 6.0(I know it's experimental, I should have been prepared for something like this). I went into recovery(CWM) for something and instead of getting into recovery it just showed cwm logo and immediately rebooted to the splash screen and stayed there. I then tried to reboot several times into recovery and the rom, only resulting in the same thing. SOO while in bootloader I decide "hey I'll just run the 2.20 ruu and everything will be ok.". Well, I ran fastboot oem lock and it said it failed but now the bootloader says RELOCKED. Now, having relocked, the RUU program STILL can't detect my phone. Then I realize, I don't have the Unlock_code.bin anymore. So now I'm stuck in bootloader, (somewhat)relocked, and have absolutely no idea what to do next. Oh and I have S-OFF if that helps.
Thanks for taking the time to read that wall of text(hopefully), Does ANYONE have an idea of what I can do next? I sincerely appreciate any help I can get.
Thanks

Ouch. I've done stuff like this, so I'll be nice. This is what happens when something goes wrong and you panic and start trying a lot of stuff without thinking it through.
Does adb devices detect the phone? You should be able to get another unlock token by going back to htcdev, assuming you're still supercid. Try that before running the RUU.

iElvis said:
Ouch. I've done stuff like this, so I'll be nice. This is what happens when something goes wrong and you panic and start trying a lot of stuff without thinking it through.
Does adb devices detect the phone? You should be able to get another unlock token by going back to htcdev, assuming you're still supercid. Try that before running the RUU.
Click to expand...
Click to collapse
Thanks so much for the reply, Yeah I'm still SuperCID and I'll try that. I am supposed to be in bootloader for the RUU to detect my phone, right? and when it "relocked" it said
Code:
C:\ADB>fastboot oem lock
...
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = -2228225 (0xFFDDFFFF)
FAILED (status read failed (Too many links))
finished. total time: 0.938s
Again, sorry. I know this was REALLY dumb. I just panicked. Thanks for taking the time to help.

Are you s-off or not? You can run a ruu not being in bootloader, but once you relock, you can't boot up without running the ruu unless you're s-off.
If you're s-on, proceed very carefully. People with s-on and supercid have bricked running the latest ruu.

iElvis said:
Are you s-off or not? You can run a ruu not being in bootloader, but once you relock, you can't boot up without running the ruu unless you're s-off.
if you're s-on, proceed very carefully. People with s-on and supercid have bricked running the latest ruu.
Click to expand...
Click to collapse
I'm S-OFF. I guess I just got cocky and figured WELL I'M S-OFF SO I'LL JUST TRY EVERYTHING HURR DURR lol. But yeah I'm s-off.

He said he's s-off. So just get a new unlock code from HTC dev and reunlock and reinstall cwm or twrp and flash cleanrom again
Sent from my VENOMized HoxL

jacobas92 said:
I'm S-OFF. I guess I just got cocky and figured WELL I'M S-OFF SO I'LL JUST TRY EVERYTHING HURR DURR lol. But yeah I'm s-off.
Click to expand...
Click to collapse
If you're s-off, you're fine. Just get a new unlock code and you can flash what you want.

iElvis said:
If you're s-off, you're fine. Just get a new unlock code and you can flash what you want.
Click to expand...
Click to collapse
Ok, thanks guys. I REALLY appreciate the help. It's booting fine now. I guess the only problem now is why it won't get past the first 3 seconds into booting to recovery or the rom. I had also flashed multiple versions of TWRP but still had the same problems. I'll just shut it down for an hour or 2 and try again later.

fastboot erase cache
You switched from CWM to TWRP and need to clear the cache.

iElvis said:
fastboot erase cache
You switched from CWM to TWRP and need to clear the cache.
Click to expand...
Click to collapse
AH. Wow. I would hit thanks again but it seems I've hit my limit. I guess the rom wouldn't boot cause I had been undervolting. It's strange, I only undervolted to 825 and it usually only gets unstable around 800. Plus, I was at stock clock speeds. Oh well. Guess I'll be trying flars bulletproof kernel. lol I NEED s2w.
Thanks again for all the help. You guys are awesome.:good:

jacobas92 said:
AH. Wow. I would hit thanks again but it seems I've hit my limit. I guess the rom wouldn't boot cause I had been undervolting. It's strange, I only undervolted to 825 and it usually only gets unstable around 800. Plus, I was at stock clock speeds. Oh well. Guess I'll be trying flars bulletproof kernel. lol I NEED s2w.
Thanks again for all the help. You guys are awesome.:good:
Click to expand...
Click to collapse
My phone doesn't like undervolting at all. Bulletproof is a great way to go.
Sent from my HTC One XL

area51avenger said:
He said he's s-off. So just get a new unlock code from HTC dev and reunlock and reinstall cwm or twrp and flash cleanrom again
Sent from my VENOMized HoxL
Click to expand...
Click to collapse
If he's s-off he doesn't need to relock or unlock bootloader right? At least I didn't when I ruu'd back to stock while s-off.
Sent from my Elemental Venomized S-off HTC One XL

majortaylor said:
If he's s-off he doesn't need to relock or unlock bootloader right? At least I didn't when I ruu'd back to stock while s-off.
Sent from my Elemental Venomized S-off HTC One XL
Click to expand...
Click to collapse
Its all good now they helped me. But to answer your question, I do know that even with s-off there are a few if not all fastboot commands that write to certain partitions that require an unlocked bootloader (at least from my experience).