I have a rooted AT&T One X+ that I unlocked via HTCDev when I first got it and now run Elegencia. I'd like to update to the newest RUU (to get the radio/hboot/all the new stuff) before updating my phone again (running an older Elegencia version currently). I understand that running the RUU will wipe the SD card/phone/recovery/everything and bring me back entirely to stock and will relock the bootloader. My problem is that I don't have the unlock token from HTCDev anymore for the bootloader. Does anyone know if it's still possible to unlock the bootloader for an AT&T One x+ via HTCDev or did they close that loophole??? Or is there a way for me to recover the unlock token?
Thanks!
I want to do the same and from what I have read you can still unlock from HTCDev after updating.
The only thing I don't know is do you need to relock the bootloader before running the RUU?
I don't think you need to relock before running the RUU, it should do it itself I would think.
I've also done some more reading and I'm also wondering if it's really worth it....looks like you can flash the radio. May just pass on having to deal with unlocking/that whole thing again.
gewbert3 said:
I don't think you need to relock before running the RUU, it should do it itself I would think.
I've also done some more reading and I'm also wondering if it's really worth it....looks like you can flash the radio. May just pass on having to deal with unlocking/that whole thing again.
Click to expand...
Click to collapse
You have to relock bootloader and then you are able to run the ruu. If bootloader is unlocked and you try to run the ruu the setup will not complete and fail.
Have you tried to obtain the unlock.bin from the HTC website again since it was deleted?
xxxrichievxxx said:
You have to relock bootloader and then you are able to run the ruu. If bootloader is unlocked and you try to run the ruu the setup will not complete and fail.
Have you tried to obtain the unlock.bin from the HTC website again since it was deleted?
Click to expand...
Click to collapse
Thanks for the tip on the bootloader, didn't know that.
How would I get the unlock.bin from the website again? I looked around HTCDev and couldn't find it anywhere.
gewbert3 said:
Thanks for the tip on the bootloader, didn't know that.
How would I get the unlock.bin from the website again? I looked around HTCDev and couldn't find it anywhere.
Click to expand...
Click to collapse
No problem
This is where I got my unlock.bin to unlock my bootloader. The steps are very easy, Go here http://www.htcdev.com/bootloader and where it says "Select device" select 'Other supported models' and follow the on screen steps. Then they will email you your unlock.bin to unlock your bootloader
OK so I need to go through the process again, I thought there'd just be a way to get the bin file again without having to do it again, oh well.
Guess question becomes whether it's really worth it or not....
You can update the radio without having to lock your bootloader and be able to update roms
Sent from my HTC One X+
If you have the email from when you originally unlocked your phone you get it there.
Sent from my HTC One X+ using xda app-developers app
I'm having an issue with the HTC dev unlock it says my token is too short but I cookies from
<<<<<<<<<start>>>>>> to
<<<<<<<<<end>>>>>>> several times I'm trying to use hysoon2000's all I. One tool kit is there a block since the ota? It auto downloaded so idk if it can be unlocked anymore anyone want to help me take a crack at it?
Sent from my HTC One X+ using xda app-developers app
I GOT it the root kit needs to be updated to the newer sdk files other than that it's good
Sent from my HTC One X+ using xda app-developers app
gewbert3 said:
OK so I need to go through the process again, I thought there'd just be a way to get the bin file again without having to do it again, oh well.
Guess question becomes whether it's really worth it or not....
Click to expand...
Click to collapse
they sent you the unlock.bin via email just search your emails for it it should still be there unless you deleted the email after you downloaded it
Yea I did delete the email, that's the problem. Oh well, decided to not worry about it.
Related
Future of this rom and me - https://plus.google.com/u/0/100983447046094793882/posts/7YtTFWWgT1C
Hope this helps people others comming sooon i have slow internet
Let's hope that nobody will be needing these with the exception of obtaining S-OFF and ROM production.
I added some tags for you too.
All ruus released enjoy
md5's for the ruu's added so enjoy but remeber you need to htc relock your boot loader before you can restore
Have you are anyone tested the relock? Frrom what I remember on previous ones I thought you could not relock like the nexus one.
But basically relock then flash these thru bootloader and you are back to the way has came out the box?
M9x3mos said:
Have you are anyone tested the relock? Frrom what I remember on previous ones I thought you could not relock like the nexus one.
But basically relock then flash these thru bootloader and you are back to the way has came out the box?
Click to expand...
Click to collapse
yep you got it and me and binary both tested the relock scripts they are good to go
xboarder56 said:
yep you got it and me and binary both tested the relock scripts they are good to go
Click to expand...
Click to collapse
I tested that script on an unbiased Windows 7 machine.
Unbiased means that it had nothing but the drivers installed. No adb or fastboot files.
I wanted to clean it up and make it look better but x was in a hurry to release it for whatever reason.
Well clean up and I will reupdate it
Sent from my HTC Amaze 4G using xda premium
xboarder56 said:
Well clean up and I will reupdate it
Sent from my HTC Amaze 4G using xda premium
Click to expand...
Click to collapse
Nah. It's it's not broke, don't fix it.
Lol ok
Sent from my HTC Amaze 4G using xda premium
more various roms/ruus coming wendsday
more ruu's released
Sorry for sounding like a n00b and redundancy but just wanted to make sure I understand this right before I make any changes on device.
The relocker posted by xboarder and binary, does that completely reverse the HTC bootloader unlock done the HTC dev site?
Assuming it does, that does mean we can get the regular updates to device again?
Sorry again if is redundant but just want to make sure there is a 100% way of returning to stock software very much like my vibrant / g2 / hd2
TheArtiszan said:
Sorry for sounding like a n00b and redundancy but just wanted to make sure I understand this right before I make any changes on device.
The relocker posted by xboarder and binary, does that completely reverse the HTC bootloader unlock done the HTC dev site?
Assuming it does, that does mean we can get the regular updates to device again?
Sorry again if is redundant but just want to make sure there is a 100% way of returning to stock software very much like my vibrant / g2 / hd2
Click to expand...
Click to collapse
yes it will let you do updates again if you follow the guide
I've tried installing this via hboot both unlocked and relocked and it doesn't actually do anything. it checks the image then just goes back to hboot. Any Idea what I'm doing wrong?
I am trying to get my Telus Amaze back to stock. I have re locked the phone it says so in the hboot menu. I have downloaded the RRU for Telus and it is on the root of my SD card. When I boot into hboot I see the progress bar in blue on the right hand side, then it goes into yellow verifiying, then it just stops no option to install the update.... It just isn't working.. any thoughts?
gmarcoux said:
I've tried installing this via hboot both unlocked and relocked and it doesn't actually do anything. it checks the image then just goes back to hboot. Any Idea what I'm doing wrong?
Click to expand...
Click to collapse
I am in the same boat. Let me if you figure it out.
hello to every one, can anyone help me with installing the stock rom?
the problem is that after i relock my phone & put the RUU file in the root folder ( with root explorer), i turn of, got in to the bootloder and nothing happened.
what do i need to do from here?
Sent from my HTC_Amaze_4G using XDA App
So, if I were to flash the 1.26 or 1.35, I wonder if I'd get working WiFi calling? Anyone that is still on 1.36.531.4, does your WiFi calling still work?
Curious, as I have seen conflicting points-Can the update from verizon be installed to a rooted phone or not? How about from the stock Verizon rom (de-bloated) on a rooted phone, or relocking the phone/back to stock and getting it? I thought I read that if you get the update on a stock DNA you can no longer unlock it with the present methods, is that true or false? Anyone know for sure? Lastly what does the update get you?
You need to have stock Rom and recovery to update.
And if you update a DNA that has never been unlocked before then you won't be able to unlock your DNA. But if you've unlocked before then your fine.
Sent from my HTC6435LVW using xda app-developers app
rootntootn said:
Curious, as I have seen conflicting points-Can the update from verizon be installed to a rooted phone or not? How about from the stock Verizon rom (de-bloated) on a rooted phone, or relocking the phone/back to stock and getting it? I thought I read that if you get the update on a stock DNA you can no longer unlock it with the present methods, is that true or false? Anyone know for sure? Lastly what does the update get you?
Click to expand...
Click to collapse
As long as you have unlocked your bootloader before the ota visit this http://forum.xda-developers.com/showthread.php?t=2152993 and it will tell you how to re-unlock and update the firmware and unlock, but make sure you have your original Unlock_code.bin file before you proceed because if you take the ota and you havent unlocked your bootloader before you will be stuck for a long time
.torrented said:
As long as you have unlocked your bootloader before the ota visit this http://forum.xda-developers.com/showthread.php?t=2152993 and it will tell you how to re-unlock and update the firmware and unlock, but make sure you have your original Unlock_code.bin file before you proceed because if you take the ota and you havent unlocked your bootloader before you will be stuck for a long time
Click to expand...
Click to collapse
Of all the times I don't spend hours researching, this is one of them where I screwed myself. I had my bootloader unlocked before the OTA and I am going to be "stuck for a long time". LOL I read several articles (not here - my own idiocy) on the OTA update and the "how tos" on going back to stock to get it, etc etc... Not one mentioned to reunlock after performing the RUU, then doing the OTA..... didn't find out I was screwed until the CID couldn't be read and the my Unlock_bin failed. So this is what it feels like again to be on a bloated phone, full of VZW crap..lol
cstmeyers said:
Of all the times I don't spend hours researching, this is one of them where I screwed myself. I had my bootloader unlocked before the OTA and I am going to be "stuck for a long time". LOL I read several articles (not here - my own idiocy) on the OTA update and the "how tos" on going back to stock to get it, etc etc... Not one mentioned to reunlock after performing the RUU, then doing the OTA..... didn't find out I was screwed until the CID couldn't be read and the my Unlock_bin failed. So this is what it feels like again to be on a bloated phone, full of VZW crap..lol
Click to expand...
Click to collapse
You should still be able to flash your token and re unlock your bootloader even after the OTA
Sent from my HTC6435LVW using XDA Premium HD app
.torrented said:
You should still be able to flash your token and re unlock your bootloader even after the OTA
Sent from my HTC6435LVW using XDA Premium HD app
Click to expand...
Click to collapse
I tried a couple of times but it kept failing. I'm not sure if I am missing a step but I think I was doing it correctly. I will try it again when I get home from work.
So, I received my HTC One today, and quickly fired it up and tried to unlock the bootloader. I downloaded the All-In-One-Toolkit from the international HTC One forum (which many said would work for the AT&T One). I was able to copy and paste my Token ID, but every time I try to submit it, I keep getting an error. I'm assuming HTC laid the kibosh on unlocking the AT&T bootloader So, I was wondering if anyone received their One today, were you able to unlock your bootloader? Thanks so much.
Roricken said:
So, I received my HTC One today, and quickly fired it up and tried to unlock the bootloader. I downloaded the All-In-One-Toolkit from the international HTC One forum (which many said would work for the AT&T One). I was able to copy and paste my Token ID, but every time I try to submit it, I keep getting an error. I'm assuming HTC laid the kibosh on unlocking the AT&T bootloader So, I was wondering if anyone received their One today, were you able to unlock your bootloader? Thanks so much.
Click to expand...
Click to collapse
I just unlocked less than an hour ago
jmztaylor said:
I just unlocked less than an hour ago
Click to expand...
Click to collapse
Hmmmm..Strange. Did you unlock it via HTC dev site or another method?
Thanks
Roricken said:
Hmmmm..Strange. Did you unlock it via HTC dev site or another method?
Thanks
Click to expand...
Click to collapse
I don't use all in one scripts so I HTC unlocked manually and flashed manually.
jmztaylor said:
I don't use all in one scripts so I HTC unlocked manually and flashed manually.
Click to expand...
Click to collapse
after hearing reports that sounds like the best way to go for now
Just got my 64gb and unlocked via instructions on the HTC dev site, no issues at all...
Roricken said:
Hmmmm..Strange. Did you unlock it via HTC dev site or another method?
Thanks
Click to expand...
Click to collapse
I followed the HTC Dev Site and got my Unlock_code.bin seconds later.
I'll just hold onto it for now
clsA said:
I followed the HTC Dev Site and got my Unlock_code.bin seconds later.
I'll just hold onto it for now
Click to expand...
Click to collapse
Yeah, I went that route as well and was able to unlock it. Now, I need to try to figure out why my CWM won't work. I pushed via cmd and it shows as being installed, but every time I boot in recovery, it just boots back in to the main screen. Have yall had success in installing a custom recovery?
Dudes,
Too many dead pixels dying on my phone and ATT is sending me another replacement device through warranty. I RUU'd and brought everything back to normal from the CID, hboot, radio, and back to s-on but I cannot get my bootloader to show "Locked". It just shows relocked. Im certain I cannot send it back to them saying relocked. Ive searched and maybe im not searching good enough. Care to share some commands?
"fastboot oem lock" only relocks it.
I restored the phone to 3.17 firmware and RUU but before I update it to the 4.3 id like it to show locked. Any help is appreciated.
Edit: Nevermind I found my answer. Read that this was not possible.
kennypow3rs said:
Dudes,
Too many dead pixels dying on my phone and ATT is sending me another replacement device through warranty. I RUU'd and brought everything back to normal from the CID, hboot, radio, and back to s-on but I cannot get my bootloader to show "Locked". It just shows relocked. Im certain I cannot send it back to them saying relocked. Ive searched and maybe im not searching good enough. Care to share some commands?
"fastboot oem lock" only relocks it.
I restored the phone to 3.17 firmware and RUU but before I update it to the 4.3 id like it to show locked. Any help is appreciated.
Edit: Nevermind I found my answer. Read that this was not possible.
Click to expand...
Click to collapse
If you're s-off it is totally possible there's a command for it built right in to revone.
Sent from my HTC One using Tapatalk
to my knowledge any htc device no longer show "locked" after you unlocked it the first time..it will always show relocked when locked again..
Nick281051 said:
If you're s-off it is totally possible there's a command for it built right in to revone.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Too bad i found this out after i s-on'd the phone again lol. So now im in the process of unlocking with rumrunner, then re s-off, then try to "lock" it again. Thanks for the replies guys
kennypow3rs said:
Too bad i found this out after i s-on'd the phone again lol. So now im in the process of unlocking with rumrunner, then re s-off, then try to "lock" it again. Thanks for the replies guys
Click to expand...
Click to collapse
No problem lol good luck
Sent from my HTC One using Tapatalk
Nick281051 said:
No problem lol good luck
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
ok now I have some problems. I unlocked again, s-off'd and then tried to "lock" and s-on again. Something went wrong and now I have a message in hboot that says "security warning" and tampared over the words "locked". I doesnt boot to the rom again just goes to recovery im guessing with the phone and the red triangle. lol Pain in the butt.
To be honest I have no clue how to fix that lol I haven't tried to lock it yet
Sent from my HTC One using Tapatalk
Nick281051 said:
To be honest I have no clue how to fix that lol I haven't tried to lock it yet
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Theres no rom on the phone now lol.Gotta figure this out! Thanks for your help dude!
Run a ruu that will fix it tampered will be gone too
Sent from my HTC One using Tapatalk
So right now it's unlocked with tampered above an s-off. Is it wise to lock bootloader first before I run ruu? Which order should I go? I know s-on is last for sure...
Sent from my HTC One using Tapatalk
For anyone that's searching for this exact issue ill share what i did to get my phone completely back to stock. I did search the forum but the info was all over the place and in my opinion it was as clear as "I" needed it to be hence me creating a thread for something so simple. Ok as follows here is what I did step by step.
First I had to make sure I installed HTC sync of course. At the moment my firmware was 3.57 and I downloaded the 3.17 RUU.exe from HTC.com
Your firmware *HBOOT* and the RUU you download have to match or you will get errors. Well, least I did.
Make sure you download some type of toolkit it would make life a lot easier. I used this one it worked like a charm!
At the moment, my phone is bootloader unlocked and s-off fyi.
Next, Use the tool to "lock" your bootloader first not "re-lock" just "lock". If you're having issues push revone again and follow commands on toolbox.
Now, check hboot to see if it shows "locked" if it has tampered above locked that's ok the RUU will take care of that.
Run, the RUU, make sure usb debugging on and htc sync already installed. Let it run.
After its done, start up phone again, turn off fastboot under "power" and turn usb debugging on again.
Start up toolkit, look to the right and it will say "s-on" device. You can only s-on after you've ran the RUU and are on stock hboot and rom.
Check Hboot again and it should read "Locked" and now "s-on".
Phone now ready to send back for warranty or etc.
Hope this helps anyone that searches. I found a few thread via google and they helped out a bunch.
Just my luck that Verizon puts this new OTA out the day before I was going to root this thing! It looks to me like we have no option now to root these updated devices. Anyone have any ideas?
therreid said:
Just my luck that Verizon puts this new OTA out the day before I was going to root this thing! It looks to me like we have no option now to root these updated devices. Anyone have any ideas?
Click to expand...
Click to collapse
You either need to wait, or try search how to revert the update.
dafuzzbudd said:
You either need to wait, or try search how to revert the update.
Click to expand...
Click to collapse
I tried to wipe/factory reset then install stock 2.17.605.2 RUU last night from .exe file. Wouldn't let it load due to updated bootloader. I also tried flashing unlock_code.bin from previous unlock experience with Hasoon2000's toolkit without luck as well as running through mdmower's unlock script with attempt to change CID. Also HTCdev just gives me an error now when trying to get a new unlock token... ugh. I'm guessing I probably need root to modify bootloader to revert to old to unlock it... so probably just screwed until someone smarter figures out a way to unlock the new bootloader...
dkkunkel said:
Also HTCdev just gives me an error now when trying to get a new unlock token... ugh. ..
Click to expand...
Click to collapse
Did you make sure your copy and paste to HTC was correct? That was my problem a couple of weeks ago. A single <space> was the culprit for me.
pmcall said:
Did you make sure your copy and paste to HTC was correct? That was my problem a couple of weeks ago. A single <space> was the culprit for me.
Click to expand...
Click to collapse
Yes, it was correct; just like other successful times... Did yours unlock after the latest OTA or was it prior to the update?
dkkunkel said:
I tried to wipe/factory reset then install stock 2.17.605.2 RUU last night from .exe file. Wouldn't let it load due to updated bootloader. I also tried flashing unlock_code.bin from previous unlock experience with Hasoon2000's toolkit without luck as well as running through mdmower's unlock script with attempt to change CID. Also HTCdev just gives me an error now when trying to get a new unlock token... ugh. I'm guessing I probably need root to modify bootloader to revert to old to unlock it... so probably just screwed until someone smarter figures out a way to unlock the new bootloader...
Click to expand...
Click to collapse
Were you rooted with s-off, or s-on?
dkkunkel said:
I tried to wipe/factory reset then install stock 2.17.605.2 RUU last night from .exe file. Wouldn't let it load due to updated bootloader. I also tried flashing unlock_code.bin from previous unlock experience with Hasoon2000's toolkit without luck as well as running through mdmower's unlock script with attempt to change CID. Also HTCdev just gives me an error now when trying to get a new unlock token... ugh. I'm guessing I probably need root to modify bootloader to revert to old to unlock it... so probably just screwed until someone smarter figures out a way to unlock the new bootloader...
Click to expand...
Click to collapse
dkkunkel said:
Yes, it was correct; just like other successful times... Did yours unlock after the latest OTA or was it prior to the update?
Click to expand...
Click to collapse
Prior to update coming out, I have not installed the OTA.
junkmail9 said:
Were you rooted with s-off, or s-on?
Click to expand...
Click to collapse
Rooted, s-on. had avatar nightly installed//had issues with no data service and eventually re-loaded stock RUU with hopes to find a fix (after wiping, clean install, flash/re-flash firmware multiple times) and put avatar back on.... but then the OTA hit and here I am... unable to unlock bootloader.
dkkunkel said:
Rooted, s-on. had avatar nightly installed//had issues with no data service and eventually re-loaded stock RUU with hopes to find a fix (after wiping, clean install, flash/re-flash firmware multiple times) and put avatar back on.... but then the OTA hit and here I am... unable to unlock bootloader.
Click to expand...
Click to collapse
Hopefully you at least have data service now. Unless you can manage SuperCID, you might be out of luck for a while. I hope I'm wrong about that.
I am now curious if anyone who is s-off installed the OTA (either accidentally or intentionally) and retained s-off. In theory, if you're s-off you can recover from nearly anything. (I will admit that I have absolutely no desire to try it for myself)
junkmail9 said:
Hopefully you at least have data service now. Unless you can manage SuperCID, you might be out of luck for a while. I hope I'm wrong about that.
I am now curious if anyone who is s-off installed the OTA (either accidentally or intentionally) and retained s-off. In theory, if you're s-off you can recover from nearly anything. (I will admit that I have absolutely no desire to try it for myself)
Click to expand...
Click to collapse
How were you able to get the CID to change? I followed the CID change script manually using temp-root and DD commands through shell with a hex editor and it would NOT change the CID although I was given no errors. Crazy.
stevey500 said:
How were you able to get the CID to change? I followed the CID change script manually using temp-root and DD commands through shell with a hex editor and it would NOT change the CID although I was given no errors. Crazy.
Click to expand...
Click to collapse
I used DirtyRacun back on the 2nd OTA to obtain s-off, and DirtyRacun does not require the SuperCID method. I have not done anything with the latest OTA, as it isn't worth the risk to me... I somehow doubt that the DirtyRacun will work with the latest OTA, but I do not recall seeing anyone post that they have tried it, either.
junkmail9 said:
I used DirtyRacun back on the 2nd OTA to obtain s-off, and DirtyRacun does not require the SuperCID method. I have not done anything with the latest OTA, as it isn't worth the risk to me... I somehow doubt that the DirtyRacun will work with the latest OTA, but I do not recall seeing anyone post that they have tried it, either.
Click to expand...
Click to collapse
Ah... I'll go ahead and give it a try. This phone bone-stock is nearly unbearably slow. HTC bloating the hell out of these phone and then locking the bootloaders is a sad marketing scheme.
stevey500 said:
Ah... I'll go ahead and give it a try. This phone bone-stock is nearly unbearably slow. HTC bloating the hell out of these phone and then locking the bootloaders is a sad marketing scheme.
Click to expand...
Click to collapse
Anyone figure out if this works?? DirtyRacun after OTA I mean. thanks
join in for the unbelievable ... post2014-OTA [S-OFF] has been achieved
http://forum.xda-developers.com/showthread.php?t=2664460