OK, tried to root my HTC One X, got the HTCDev unlock, but could never get an S-OFF on 5.18 firmware. Did have a CID unlock, so set it back to OEM Relock, and have tried to RUU the exact firmware back. It says its sucsessful but get a loop condition, White HTC, then a strange black screen, when I get back to Bootloader and tried again, same result. Any ideas, attached are pic. of strange screen and Bootloader
mbardsley said:
OK, tried to root my HTC One X, got the HTCDev unlock, but could never get an S-OFF on 5.18 firmware. Did have a CID unlock, so set it back to OEM Relock, and have tried to RUU the exact firmware back. It says its sucsessful but get a loop condition, White HTC, then a strange black screen, when I get back to Bootloader and tried again, same result. Any ideas, attached are pic. of strange screen and Bootloader
Click to expand...
Click to collapse
What were you trying to do in the first place? When you say CID unlock do you mean bootloader unlock? I think you're a bit confused about what you've been doing. Why did you relock the bootloader? What is your CID currently? Do not attempt to run the RUU again until we can confirm what your CID is, you could brick your phone.
Sent from a crappy Samsung because my Evita died
Confirmed CID is showing all 11111111, bootloader screen now says ***TAMPERED*** then ***UNLOCKED*** and still has S-ON, and this was a 5.18, which I think was my mistake for trying. Cannot run RUU utility, it wont complete, can get into TWRP recovery 2.6.0.0 but not able to flash, or anything. At this time would love to be able to just flash back to my stock.
Flash a Sense ROM, get s-off, run the RUU.
Sent from a crappy Samsung because my Evita died
THANKS! That did the trick, I knew I was close, but thought I had to get S-OFF before a flash of ROM.
Related
My problem is a little complicated.
It dates back to last night. Suddenly i just want to try ICS so i download the firmware and rom from this thread(http://forum.xda-developers.com/showthread.php?t=1408351). I met with a problem, after i flash the firmware, the system stuck but i pulled the battery out then problem solved. The next step is just as usual and nothing unusual happened. It's not so smooth and perfect as CM7, which i think it's just a problem of maturity.
After i restore the apps and finish setting the phone, i check the bootloader and find that the bootloader shows it's locked. There wouldn't be a problem if i just accept that. But i decided to do something, unfortunately, i messed up.
The bootloader shows "locked" and "Security warning" and the phone can't boot into system by any means. I tried a lot of methods and finally i unlock the bootloader by official method. Result seems to be good. The bootloader shows "unlock" but "s on" and the phone can boot into recovery. It seems i just wake up from a nightmare.
but the nightmare never ends. Although i can wipe or install any rom, but the phone just stuck at the splash screen. I tried but i faild. Is there anyone has some suggestions? And how to s off?
The hboot version is 1.23.0000 and it doesn't install any PG58IMG files no matter it is radios or else.
Thank you in advance
You need to Soff again.
Its normall for the latest firmware hboot 1.23 to show locked. Its not really locked
big_sw2000 said:
You need to Soff again.
Its normall for the latest firmware hboot 1.23 to show locked. Its not really locked
Click to expand...
Click to collapse
Could you tell me how to s off please? Or downgrade the hboot? It seems that hboot 1.23 isn't supported by revolutionary?
Have a look
http://forum.xda-developers.com/showthread.php?t=1192300
big_sw2000 said:
Have a look
http://forum.xda-developers.com/showthread.php?t=1192300
Click to expand...
Click to collapse
I have read the thread, if relotionary is the only way to s off, i don't think it help because it requires hboot is under 1.18, but the hboot of my phone is 1.23, is not in the supported list. Besides, my phone can't boot into system, the revolutionary is always waiting for device
Revert to 1.17 and S-off using revolutionary
I hope it is possible, don't know exactly what is possible to be flashed with s-on, but since your phone is unlocked you can use fastboot commands, so I think it wont be a problem.
akos.szekacs said:
Revert to 1.17 and S-off using revolutionary
I hope it is possible, don't know exactly what is possible to be flashed with s-on, but since your phone is unlocked you can use fastboot commands, so I think it wont be a problem.
Click to expand...
Click to collapse
In this thread, it mentions that how to revert to 1.17(http://forum.xda-developers.com/showpost.php?p=20681060&postcount=22), on the condition that the hboot is 1.20,but my hboot is 1.23. I'm trying the zip from the thread, hope it works
It remains usless. The bootloaders shows "PG58IMG.zip" is a wrong image.
My Sensation XE came with HBoot 1.2.000, so i installed at ROM from here with HBoot 1.18.000 and then got S-OFF.
jkolner said:
My Sensation XE came with HBoot 1.2.000, so i installed at ROM from here with HBoot 1.18.000 and then got S-OFF.
Click to expand...
Click to collapse
And which ruu? I tried ruu too, but it didn't work.
i know that 1.20 can be reverted to 1.17 and then s off. But my hboot is 1.23 rather than 1.20. And i have another problem: the bootloader can't update by PG58IMG.zip, it always shows no file or wrong image.
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.
I have an At&t HTC One X that I bought from a licensed store in Jersey.
I used a hex editior to change the CID so I could use HTCdev to unlock the bootloader (so my current CID is Roger001, which was not the original CID). Currently installed CleanROM 4.0.
Want to get back to stock to return phone...what information do I need to provide so that someone can tell me what RUU to use? In settings I see build number 1.85.502.3...hboot is 1.09.0000...radio is 0.17.32.09.12.
You can relock your bootloader then change your CID back to CWS__001 using the same hex hack method you used to make it a ROGERS CID then run the 1.85 RUU and your back to stock. One thing is your bootloader will still say relocked at the top but there is nothing you can do about that but hope they don't look at that and deny you.
Link to the 1.85 RUU: http://forum.xda-developers.com/showthread.php?t=1670238
So I hack the CID back, lock the bootloader, and run the RUU mentioned and that's it? I figured my hboot version, radio version and all the rest of it would lead me to a different RUU than the one you pointed to...
When you RUU back to 1.85 it will flash everything to the 1.85 versions.
If I lock the bootloader, how do I change the CID back? When I hacked the CID and used ADB my phone was on with the ROM loaded and plugged in...If I lock the bootloader, I can only get into the hboot screen...can I still ADB push and pull from there?
And if I'm planning on flashing the 1.85 RUU, do I need to change the CID at all? Can't I just lock the bootloader, and then run the .exe?
Locked bootloader and then ran the 1.85 RUU you pointed me to...received error 131...back to Hboot with a locked bootloader...any suggestions? Y'all made it sound so simple...
Because you didn't change Cid. Error 131
You can still unlock then push a recovery then from that recovery put a rom on the phone and flash. Use twrp.
So from here...unlock bootloader...then push twrp recovery...at what point do I change the CID and run the RUU to get back to stock?
aram12 said:
So from here...unlock bootloader...then push twrp recovery...at what point do I change the CID and run the RUU to get back to stock?
Click to expand...
Click to collapse
after you have a rooted ROM on it and can access the proper partition with a hex editor to change the CID back after that you can relock bootloader and run RUU
This is why you get nexus, just flash stock images
Sent from my Galaxy Nexus using Tapatalk 2
So I was going to buy a new phone, and trade in my sensation for it, so I reverted to stock. Except I installed the wrong RUU for my region and only noticed after re-enabling s-on, and then I was really stupid and tried to flash the right rom.zip while it was s-on and now my phone only boots into the bootloader... how can I S-off and reinstall the right RUU from only the bootloader? Revolutionary is constantly waiting for my device and htc's token id unlocker isn't recognising it either, and when it does it always comes up with an error
chocchief said:
how can I S-off and reinstall the right RUU from only the bootloader? Revolutionary is constantly waiting for my device and htc's token id unlocker isn't recognising it either, and when it does it always comes up with an error
Click to expand...
Click to collapse
do you have htc drivers installed?
if now you have 1.17-1.18 hboot version then revolutionary.io method is the only way to S-OFF
for flashing ruu from bootloader see here
http://forum.xda-developers.com/showthread.php?t=1672425 (step 4)
but first you have to be S-OFF
In trying to update the HBOOT from 2.15 to 2.18, I tried to flash ATT 3.18 RUU on an S-OFF, Bootloader unlocked ATT One X.
Everything seem to go fine until I rebooted. Now all I can do is notice is that the top line reads as "RELOCKED" and the radio and everything else updated fine, but it won't go beyond the HTC logo now.
Tried flashing a recovery via FASTBOOT which seems to send the file but do nothing, I also tried to unlock it again using the original bootloader unlock.bin from HTCDEV, but that is failing as well. I can't go into recovery at all now to flash any custom ROM as well.
Any guidance on getting around this, I have seen some "Relocking" threads but none for AT&T HTC One X. Appreciate the forum's guidance in getting through this mess up.
Did you actually relock the bootloader yourself? An RUU can't normally do that.
Transmitted via Bacon
No, For some reason, my ADB/Fastboot commands didn't get response from the Phone, and then I simply flashed the RUU. That's where it started showing as relocked. After breaking sweat over what was happening, I went ahead and flashed it again and it seems The RUU was not successful in the 1st attempt since it booted nicely after the 2nd flash.
Currently I had to request a new unlock code to unlock the bootloader again and now it is unlocked successfully and the phone is alive and getting a rest before I flash 5.0 ROMs on it. I have renamed it Phoenix due to the 2 bricks it went through and still able to function as my primary device after 30 months of purchase.