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
Related
I tried to re lock the boot-loader on my used ATT One X. I used a different Unlock_code than what was used to unlock it and now its bricked. Is there anyway around this? It boots straight to Fastboot no-matter what and I tried to flash a Stock RUU and after 5 minutes it said it was unsuccessful. Please help! Thanks!
What software version were you on previous to this?
gunnyman said:
What software version were you on previous to this?
Click to expand...
Click to collapse
I got it unlocked again and booted. Do you want me to screenshot the software info, because I still want to go back to stock if that is possible.
Rszafraniec93 said:
I tried to re lock the boot-loader on my used ATT One X. I used a different Unlock_code than what was used to unlock it and now its bricked. Is there anyway around this? It boots straight to Fastboot no-matter what and I tried to flash a Stock RUU and after 5 minutes it said it was unsuccessful. Please help! Thanks!
Click to expand...
Click to collapse
If you can get to the bootloader you are NOT bricked. Just relax, run the 1.85 or 2.20 RUU again and you will be fine.
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.
I lock bootloader on Verizon Google Pixel when my device have TWRP and i have brick! Device Loading up to logo Google on 1 sec and reboot. Fastboot work, but i don't unlock bootloader. In recovery is don't enter. Please help me!
https://forum.xda-developers.com/pixel/how-to/psa-read-relocking-bootloader-t3494614 ....very important advice. With my limited knowledge NEVER relock unless you have signed OEM images correctly reloaded into device before locking.
kkjb said:
https://forum.xda-developers.com/pixel/how-to/psa-read-relocking-bootloader-t3494614 ....very important advice. With my limited knowledge NEVER relock unless you have signed OEM images correctly reloaded into device before locking.
Click to expand...
Click to collapse
There is still no solution to this problem? ((
Unlock again.
lafester said:
Unlock again.
Click to expand...
Click to collapse
how can I unlock it now?
I already wrote to a man who used to be for money unlocked Verizon bootloader, but he says "No solution for this problem yet"
Groh12 said:
how can I unlock it now?
I already wrote to a man who used to be for money unlocked Verizon bootloader, but he says "No solution for this problem yet"
Click to expand...
Click to collapse
Put the phone in fastboot mode, then run `fastboot flashing unlock` from a PC. If it says unlocking not allowed, you're out of luck, it's a brick now. Never lock your phone without being 100% stock on both slots
Groh12 said:
how can I unlock it now?
I already wrote to a man who used to be for money unlocked Verizon bootloader, but he says "No solution for this problem yet"
Click to expand...
Click to collapse
No idea. I've never relocked unless I am completely stock and take at least one ota first to make sure, along with full factory resets before and after updating.
There are others here that claim they where able to unlock again and save their phones though so maybe it's possible.
lafester said:
No idea. I've never relocked unless I am completely stock and take at least one ota first to make sure, along with full factory resets before and after updating.
There are others here that claim they where able to unlock again and save their phones though so maybe it's possible.
Click to expand...
Click to collapse
In this topic https://forum.xda-developers.com/pi...bootloader-t3540772/post77016940#post77016940 man has unbrick Pixel XL, but i think that method will work on Pixel.
So today i decided to downgrade from V10.2.1.0.PEEMIXM to V10.0.11.0.PEEMIFH because i was having serious battery issues on V10.2.1.0.
I should have looked into it more carefully but nope, my dumb ass decided to install the older ROM version via the Updater in Settings and it bricked my device in the process.
Now my device is stuck on boot with the message "The system has been destroyed. Press power button to shutdown".
I have the global version with the bootloader locked. The only thing i have access to now is fastboot.
Any ways i can recover from this? Any help is greatlyyy appreciated.
You can try to unlock bootloader with fastboot mode, but i'm not sure that works because the system has been destroyed and your account has been destryed too. I think, the best for you, is to send it in warranty for repair. I have bricked a Redmi Note 4 like that and even with the test point method, he has never work again.
boxof said:
So today i decided to downgrade from V10.2.1.0.PEEMIXM to V10.0.11.0.PEEMIFH because i was having serious battery issues on V10.2.1.0.
I should have looked into it more carefully but nope, my dumb ass decided to install the older ROM version via the Updater in Settings and it bricked my device in the process.
Now my device is stuck on boot with the message "The system has been destroyed. Press power button to shutdown".
I have the global version with the bootloader locked. The only thing i have access to now is fastboot.
Any ways i can recover from this? Any help is greatlyyy appreciated.
Click to expand...
Click to collapse
If you can find the fastboot version of the ROM you were on before downgrading just flash it with miflash
Azev said:
You can try to unlock bootloader with fastboot mode, but i'm not sure that works because the system has been destroyed and your account has been destryed too. I think, the best for you, is to send it in warranty for repair. I have bricked a Redmi Note 4 like that and even with the test point method, he has never work again.
Click to expand...
Click to collapse
Fortunately for me i was able to unlock the bootloader. Likely because i registered my device since i first got it (about 1 month now), so i think i must have met the wait time requirement and it was fine that i couldn't access the system.
Mackay53 said:
If you can find the fastboot version of the ROM you were on before downgrading just flash it with miflash
Click to expand...
Click to collapse
I tried miflash the first time with my bootloader still locked but miflash refused to work with a locked bootloader.
So i tried again with my bootlocker unlocked and it worked as expected.
Lesson learnt. All is well again and i'm able to keep my bootloader locked with the "flash_all_lock" option.
Thank you so much for all the help!
boxof said:
Fortunately for me i was able to unlock the bootloader. Likely because i registered my device since i first got it (about 1 month now), so i think i must have met the wait time requirement and it was fine that i couldn't access the system.
I tried miflash the first time with my bootloader still locked but miflash refused to work with a locked bootloader.
So i tried again with my bootlocker unlocked and it worked as expected.
Lesson learnt. All is well again and i'm able to keep my bootloader locked with the "flash_all_lock" option.
Thank you so much for all the help!
Click to expand...
Click to collapse
I am very sorry for reviving this thread, but if it's possible, can I ask you how you had managed to unlock the bootloader through fastboot? Now I am facing a similar situation to the one you once did, where my phone is stuck with the error message "The system has been destroyed" with a locked bootloader, and the only thing I have access to is Fastboot. I will greatly appreciate it if you could take some time to help me out because I have tried looking everywhere on xda forums and yours seems like the only one that is very similar to what I am currently facing now. Thanks so much.
nsynsy said:
I am very sorry for reviving this thread, but if it's possible, can I ask you how you had managed to unlock the bootloader through fastboot? Now I am facing a similar situation to the one you once did, where my phone is stuck with the error message "The system has been destroyed" with a locked bootloader, and the only thing I have access to is Fastboot. I will greatly appreciate it if you could take some time to help me out because I have tried looking everywhere on xda forums and yours seems like the only one that is very similar to what I am currently facing now. Thanks so much.
Click to expand...
Click to collapse
Unless you have got unlock permission and linked phone to account you can't unlock.
Unlock like how you would normally - put the phone into fastboot, connect it to your PC, and run the mi unlock tool. For this to work, hopefully you have associated your device to a mi account and have met the unlock requirements ie. surpassed the waiting period. Otherwise you're out of luck as there is no other ways (that i know of) to register the device now as you can't get into the system.
As a last resort you can try opening up the back of the phone and flash new firmware using the test point if unlocking is not possible. I'm not sure how or where the testing point is located exactly, but it's a possible solution that i found while researching when my device was bricked. Good luck!
nsynsy said:
I am very sorry for reviving this thread, but if it's possible, can I ask you how you had managed to unlock the bootloader through fastboot? Now I am facing a similar situation to the one you once did, where my phone is stuck with the error message "The system has been destroyed" with a locked bootloader, and the only thing I have access to is Fastboot. I will greatly appreciate it if you could take some time to help me out because I have tried looking everywhere on xda forums and yours seems like the only one that is very similar to what I am currently facing now. Thanks so much.
Click to expand...
Click to collapse
u say u can only access to fastboot..
How about pressing volume up and power button? can u enter in stock mi recovery with mi assistant options?
I have a TracFone moto g pure (XT2163DL) running android 12, build number S3RHS32.20-42-13-2-1. I managed to get my oem unlock to show up and turned it on. First I tried using the Motorola unlock site to unlock my bootloader but it said it wasn't eligible. So then I tried using fastboot command "fastboot oem unlock" and a screen popped up telling me I can choose to unlock my bootloader and when I told it to unlock I received a message saying it was successful. But it isn't. It said it's unlocked but yet it is still locked anyway. I know TracFone has problems unlocking bootloader's but why would it let me get that far if it is impossible to unlock? Is there anything else I can do? If anyone knows something else I can try please point me in the right direction. I don't mind doing my homework after all that's how I learn but I'm just at a point where I need some guidance.please help me and always thank you so much for your time in advance...
If the bootloader reports unlocked, what makes you say it's still locked?
V0latyle said:
If the bootloader reports unlocked, what makes you say it's still locked?
Click to expand...
Click to collapse
Nothing is wiped and it still says OEM secured on the fastboot page. The only difference now is when I try to reboot back into system it will first boot back into the bootloader again and then it will boot into system when I reboot a second time