I have an AT&T 3.18 one x. The bootloader is showing as TAMPERED. I am able to successfully get superCID and get the unlock_code.bin from htcdev. I can successfully use that and the phone warns me, blah blah, and then resets everything and boots into a wiped android.
The problem is that when I reboot into the bootloader again it still says TAMPERED LOCKED. I am unable to load an custom recoveries.
Everything I read says I can unlock the BL without htcdev, but it requires root. But the way to acquire root is with an unlocked bootloader! rock-->me<--hard place.
Any advice on what to try next? I've never had this much trouble rooting/romming before, I've lost my touch apparently.
Sounds like its unlocked but the locked field I your bootloader is spoofed.. Did you buy this phone used?
If im wrong then it just means you need to keep trying thr unlock bin file over andover until it unlocks. Do a hard reset by holding thepower button until the phone shuts off between tries. Eventually it will unlock
Yes, bought it used.
I tried flashing recovery downloaded from cm install wiki and got "signature invalid".
The only way I can get into the BL is using adb or holding volume down while restarting from os.
I've done it twice, will try more.
The supercid is only the temp one meant for using htcdev. Do I need to redo that each time before applying the unlock code bin?
germancarsrock said:
Yes, bought it used.
I tried flashing recovery downloaded from cm install wiki and got "signature invalid".
The only way I can get into the BL is using adb or holding volume down while restarting from os.
I've done it twice, will try more.
The supercid is only the temp one meant for using htcdev. Do I need to redo that each time before applying the unlock code bin?
Click to expand...
Click to collapse
No you should not need to. Your bootloader is definitely still locked. Keep trying! It was probably relocked. It may take many tries before it unlocks. Ive relocked my bootloader a few times in the past for testing purposes
Success! Thanks for the encouragement!
Only took two more attempts. First tried turning off "reboot faster" option in the power settings menu before I did the restart-while-holding-volume-down. But that didn't work.
Then tried the hold-power-for-10-seconds like you suggested and it worked that time. Now I am TAMPERED UNLOCKED S-OFF and running cm10.
Related
So my cousin got a one x,
we followed the 36 page guide, unlocked the rogers bootloader, then flashed the AT&T firmware 1.85, and then tried unlocking the bootloader again, but not matter what happens when he confirms the unlock token, it just turns off. then he turns it back on and it sets it up, reboots to the bootloader and it still says locked...
i've tried to help him but i have no clue as far as i know...
we've gotten a new token 3 times now as well and it hasn't worked either.
does anyone else have this problem?
can he flash back to the Rogers RUU? just for stock sakes or is he stuck on AT&T 1.85 now?
thanks guys.
EDIT:
Mod's please close, figured it out, just tried using an OLD unlock code and for some reason it worked. =\
thanks anyway, sorry for the spam.
FaithCry said:
EDIT:
Mod's please close, figured it out, just tried using an OLD unlock code and for some reason it worked. =\
thanks anyway, sorry for the spam.
Click to expand...
Click to collapse
the issue is how you boot in to fastboot. If you use adb to get there sometimes the unlock wont take. i tried 10+ times with one phone. If you power off, then hold down vol- to get to fastboot, then run the unlock command it normally will work the first time. The unlock tokens are the exact same. re downloading them and using the old one probably had nothing to do with it. Glad you are unlocked now
Here's the story...
So I bought my HTC one X (AT&T) from a guy on craigslist, who claims he unlocked the bootloader, and rooted the phone.
So I get it and it has the factory 4.0.4 update on it...
Well he did indeed unlock the bootloader, it said unlocked, but the phone was not rooted, im guessing it WAS rooted on 4.0.3, then he did the OTA and it removed the root and update it to 4.0.4.
Whatever the case is I now want to do a factory reset on the phone, but either method i try the phone just reboots and never resets. Ive tried:
1.Settings > Storage > Factory Data Reset, but the phone goes to the HTC Quietly brilliant screen with some red HTC writing that says dont distribute this software, blah blah.
2. Power down + Volume Down, then doing the Data Reset in the bootloader, but I get the same HTC Quietly brilliant screen with the same red HTC writing, then it just boots back up to the phone, and nothing is reset.
What can I do to get this thing factory reset guys? Suggestions?
tdesbien31 said:
Here's the story...
So I bought my HTC one X (AT&T) from a guy on craigslist, who claims he unlocked the bootloader, and rooted the phone.
So I get it and it has the factory 4.0.4 update on it...
Well he did indeed unlock the bootloader, it said unlocked, but the phone was not rooted, im guessing it WAS rooted on 4.0.3, then he did the OTA and it removed the root and update it to 4.0.4.
Whatever the case is I now want to do a factory reset on the phone, but either method i try the phone just reboots and never resets. Ive tried:
1.Settings > Storage > Factory Data Reset, but the phone goes to the HTC Quietly brilliant screen with some red HTC writing that says dont distribute this software, blah blah.
2. Power down + Volume Down, then doing the Data Reset in the bootloader, but I get the same HTC Quietly brilliant screen with the same red HTC writing, then it just boots back up to the phone, and nothing is reset.
What can I do to get this thing factory reset guys? Suggestions?
Click to expand...
Click to collapse
What are you expecting factory reset to do?
All it does is wipe anything from /data which is where the user installed apps are. It should also go through first time setup again.
Since the bootloader is unlocked push a custom recovery, I suggest TWRP and do a factory reset from there.
gunnyman said:
What are you expecting factory reset to do?
All it does is wipe anything from /data which is where the user installed apps are. It should also go through first time setup again.
Since the bootloader is unlocked push a custom recovery, I suggest TWRP and do a factory reset from there.
Click to expand...
Click to collapse
Right, the guy I purchased the phone from has/had crap setup all over the place, long story short he butchered the files of the phone trying to delete his data, and his crap is still everywhere. So how would I go about pushing TWRP?
Go to http://forum.xda-developers.com/wiki/HTC_One_X then scroll down to Total recovery - flashing a RUU to completely restore your phone.
Follow those instructions
WARNING THIS DOES RELOCK THE BOOTLOADER AND YOU WON'T BE ABLE TO UNLOCK IT UNTIL A NEW METHOD IS DISCOVERED. But it will factory reset your phone.
Download the ruu from HTC
Sent from my HTC One XL using Tapatalk
tdesbien31 said:
Right, the guy I purchased the phone from has/had crap setup all over the place, long story short he butchered the files of the phone trying to delete his data, and his crap is still everywhere. So how would I go about pushing TWRP?
Click to expand...
Click to collapse
go here and follow the instructions http://teamw.in/project/twrp2/99
danny39 said:
Go to http://forum.xda-developers.com/wiki/HTC_One_X then scroll down to Total recovery - flashing a RUU to completely restore your phone.
Follow those instructions
WARNING THIS DOES RELOCK THE BOOTLOADER AND YOU WON'T BE ABLE TO UNLOCK IT UNTIL A NEW METHOD IS DISCOVERED. But it will factory reset your phone.
Download the ruu from HTC
Sent from my HTC One XL using Tapatalk
Click to expand...
Click to collapse
So if my bootloader is relocked im totally screwed, right?
tdesbien31 said:
So if my bootloader is relocked im totally screwed, right?
Click to expand...
Click to collapse
if it has been unlocked it can be unlocked again as long as the seller didn't change the CID back to the AT&T default
to check this from boot loader type fastboot getvar cid. if it reports back 11111111 or rogers01 you're good to unlock it again. if it does NOT say this, DO NOT relock.
tdesbien31 said:
So if my bootloader is relocked im totally screwed, right?
Click to expand...
Click to collapse
What gunnyman said. But my bootloader is locked and I'm perfectly fine.
Unless you want to flash other ROMs then having your bootloader locked is fine
Sent from my HTC One XL using Tapatalk
gunnyman said:
if it has been unlocked it can be unlocked again as long as the seller didn't change the CID back to the AT&T default
to check this from boot loader type fastboot getvar cid. if it reports back 11111111 or rogers01 you're good to unlock it again. if it does NOT say this, DO NOT relock.
Click to expand...
Click to collapse
Ok so it says "relocked"
and my cid is 11111111, whats my next step to get this thing unlocked again?
Sorry for all the questions you guys are being helpful
You can unlock again by getting a token from htcdev go to htcdev.com create an account. Then click unlock bootloader. Then choose other devices. Follow the directions from there. Or get the unlock token from the seller.
gunnyman said:
You can unlock again by getting a token from htcdev go to htcdev.com create an account. Then click unlock bootloader. Then choose other devices. Follow the directions from there. Or get the unlock token from the seller.
Click to expand...
Click to collapse
ok ill go about that method, thanks guys you were a huge help!
I tried rooting my HTC one with qbking77 video tutorial. Unlocked the bootloader but couldn't root upon many unsuccessful attempts. Eventually relocked the bootloader.now my phone is given me tampered and relocked and security warning. I can't even turn off the phone. Anytime I try to turn it off it goes to fastboot mode. Is there anyway I can have stock android back on my phone and get ota. My network is three in the UK
Plzzz help!!!!!!!!!!!!!!!!!!!!!!
you can't
K.V.K said:
Plzzz help!!!!!!!!!!!!!!!!!!!!!!
Click to expand...
Click to collapse
well my friend sry but you can't restore this code
most of devices like samsung,motorola etc they have.... lets say a key for the bootloader(is the door) and this key if you root your device
breaks and the half key stays inside the door hole to reminds you that the key is broken(the devicesis root/unlockbootloader).
so if you root any motorola device the code state goes
automatically 2 and stays like this,you can flash again the stock rom and relock the bootloader sure
but the code stays 2 for ever.
i hope to help you
moto g XT1541 stock rom 6.0.1 lockbootloader
bromoxitos said:
well my friend sry but you can't restore this code
most of devices like samsung,motorola etc they have.... lets say a key for the bootloader(is the door) and this key if you root your device
breaks and the half key stays inside the door hole to reminds you that the key is broken(the devicesis root/unlockbootloader).
so if you root any motorola device the code state goes
automatically 2 and stays like this,you can flash again the stock rom and relock the bootloader sure
but the code stays 2 for ever.
i hope to help you
moto g XT1541 stock rom 6.0.1 lockbootloader
Click to expand...
Click to collapse
I'm not exactly sure what you are saying, but I think the jist of it is how do you relock the bootloader... the answer is you cannot, once it is unlocked it will always report as unlocked, even if you reflash stock and find a way to relock the device.
When you unlocked your device, it was plainly stated in the disclosure on the website that once the bootloader is unlocked, it is irreversible.
yeap
acejavelin said:
I'm not exactly sure what you are saying, but I think the jist of it is how do you relock the bootloader... the answer is you cannot, once it is unlocked it will always report as unlocked, even if you reflash stock and find a way to relock the device.
When you unlocked your device, it was plainly stated in the disclosure on the website that once the bootloader is unlocked, it is irreversible.
Click to expand...
Click to collapse
YEAAA we say the same think,but i use an othey way to say it.
i say in the end you can relock the bootloader (more or less) when i say this i mean that you put some partitions back in boot loader
so when you flash the stock rom you can take any ota update,but the main bootloader is unlock always.
i know that form my old moto g2gen, moto x2013!!!
bromoxitos said:
YEAAA we say the same think,but i use an othey way to say it.
i say in the end you can relock the bootloader (more or less) when i say this i mean that you put some partitions back in boot loader
so when you flash the stock rom you can take any ota update,but the main bootloader is unlock always.
i know that form my old moto g2gen, moto x2013!!!
Click to expand...
Click to collapse
You could relock the bootloader on older Motos, but not anymore... Actually, it can be relocked but it will never report as locked or relocked, it will always be reported as unlocked. I don't how to be more plain in describing this.
And yes, you can take an OTA when unlocked, as long as you have a stock ROM and recovery and your bootloader is the correct version for your ROM. If your bootload and ROM are out of sync (ie. you have a Marshmallow bootloader and a Lollipop ROM), if your bootloader and ROM are out of sync, you could potentially get into a hard bricked situation.
ohh!!
acejavelin said:
You could relock the bootloader on older Motos, but not anymore... Actually, it can be relocked but it will never report as locked or relocked, it will always be reported as unlocked. I don't how to be more plain in describing this.
And yes, you can take an OTA when unlocked, as long as you have a stock ROM and recovery and your bootloader is the correct version for your ROM. If your bootload and ROM are out of sync (ie. you have a Marshmallow bootloader and a Lollipop ROM), if your bootloader and ROM are out of sync, you could potentially get into a hard bricked situation.
Click to expand...
Click to collapse
not any more? damn....yea we say the same think,sry for my english,yea i khow what you talking about i brick my moto x like this!!! any way.
ty for the new info about bootloader.
you was 100%
were you a clear,thanks a lot,and i hope to help him
Once I sent my hard bricked phone to Motorola. I had unlocked the bootloader and done the stupid mistake of sideloading an older version and upgrading to a newer, but still older version. When it came back, it said it was Status Code 0.
Wonder how they did it.
yagyaxt1068 said:
Once I sent my hard bricked phone to Motorola. I had unlocked the bootloader and done the stupid mistake of sideloading an older version and upgrading to a newer, but still older version. When it came back, it said it was Status Code 0.
Wonder how they did it.
Click to expand...
Click to collapse
They flash the eMMC chip (internal storage chip) directly... If you could get the right image you could possibly do it yourself with a few hundred to thousand dollar investment in a proper JTAG flashing unit.
Key would be getting the right Image, this would be far more than just a normal stock fastboot image, and is probably generated on the fly per device due to differences in serial number, IMEI, etc. These types of images don't get leaked out.
acejavelin said:
I'm not exactly sure what you are saying, but I think the jist of it is how do you relock the bootloader... the answer is you cannot, once it is unlocked it will always report as unlocked, even if you reflash stock and find a way to relock the device.
When you unlocked your device, it was plainly stated in the disclosure on the website that once the bootloader is unlocked, it is irreversible.
Click to expand...
Click to collapse
ok so what if you have never root unlocked, did nothing but use as intended to be.. never trying to do anything to it. wtf would i have a code 2 status then? care to sum that up for me.. cause 100% my situation.
wiytboi said:
ok so what if you have never root unlocked, did nothing but use as intended to be.. never trying to do anything to it. wtf would i have a code 2 status then? care to sum that up for me.. cause 100% my situation.
Click to expand...
Click to collapse
You unlocked the bootloader... It doesn't matter if you actually changed anything else or not. Once it's been done, this status code can never go back to 0. If the status code is 2 and you didn't unlock the bootloader, then someone else did.
acejavelin said:
You unlocked the bootloader... It doesn't matter if you actually changed anything else or not. Once it's been done, this status code can never go back to 0. If the status code is 2 and you didn't unlock the bootloader, then someone else did.
Click to expand...
Click to collapse
No I didn't.. I don't even know how to.. I just found out about recovery mode.. Wait wait before i say that.. How do you unlock boot loader? Turning developer mode on? Going to recovery menu? I've never hard reset it.. Just soft or doing new device. You said it could work fine for a while then shirt out? Like guy I bought from did and then I bought used for couple years and then went tits up?
wiytboi said:
No I didn't.. I don't even know how to.. I just found out about recovery mode.. Wait wait before i say that.. How do you unlock boot loader? Turning developer mode on? Going to recovery menu? I've never hard reset it.. Just soft or doing new device. You said it could work fine for a while then shirt out? Like guy I bought from did and then I bought used for couple years and then went tits up?
Click to expand...
Click to collapse
You unlock the bootloader with a series of steps that includes submitting a code to Motorola and getting an unlock code back... Performing it forces a factory reset as well. It's not something you can do by accident.
The issue with Status Code 2 was that an official update could have detected that and refused to update properly or done something worse... That never happened.
If everything is working fine, the status being 2 isn't important, it just means the previous owners had unlocked the bootloader and likely rooted or otherwise modified the phone.
Hello,
I messed with my Pixel phone and now I feel it bricked. It was working fine until I update it to 8.0 Oreo. Then I rooted it using magisk.
Later, I decided to re-lock my bootloader, which was really a big mistake. I did re-lock it using the following command:
fastboot oem lock
It showed me if I lock my bootloader, it would wipe everything. I hit yes.
After that, this issue started, my phone won't start, as soon as the google logo shows up, it restarts and does the same thing everytime.
I tried to install the factory image, "sailfish" for Pixel 8.1.0, using the following command:
flash-all
it gave me an error message. It said I need to unlock the bootloader.
Of course, I tried to unlock the bootloader using the following command:
fastboot flashing unlock
It also gave me an error message, it said:
FAILED (remote: oem unlock is not allowed)
I don't know what else should I do. I tried to find a solution for my problem, but there is no clear answer.
One of the common solution is to enable the USB debugging/OEM unlocking from the developer settings. But, again, I can't even turn on my phone and use it normally.
The only thing that I can access to is the bootloader screen.
There are several threads which state "hey don't try relocking your bootloader for any reason" for a reason. You CANNOT relock these phones with ANY custom firmware or modifications. Your phone is bricked. You can try talking to Google and they /may/ rma your phone but there is 0 guarantee especially given that you did something that is a known feature and is intended to brick the phone. Can't hurt to try though
KittyRgnarok said:
There are several threads which state "hey don't try relocking your bootloader for any reason" for a reason. You CANNOT relock these phones with ANY custom firmware or modifications. Your phone is bricked. You can try talking to Google and they /may/ rma your phone but there is 0 guarantee especially given that you did something that is a known feature and is intended to brick the phone. Can't hurt to try though
Click to expand...
Click to collapse
You are totally right. I'll contact them to RMA my phone.
hamooz92 said:
You are totally right. I contact them to RMA my phone.
Click to expand...
Click to collapse
Good luck. Update the thread with the results cuz I'm curious if they will rma a phone bricked like that