I can't get the bootloader unlocked on a phone I just purchased with a relocked bootloader. I am on firmware 2.20 and my CID reads 11111111. I enter the unlock code and it says successful and I get the warning message on my phone about unlocking the bootloader and I hit yes to unlock. After the phone reboots all my data is wiped but when I reboot back into bootloader it still says relocked. I have tried multiple times with multiple unlock codes but no dice. I cannot get into stock recovery either after running the stock RUU. Anyone have any ideas? Thanks.
bsharp8 said:
I can't get the bootloader unlocked on a phone I just purchased with a relocked bootloader. I am on firmware 2.20 and my CID reads 11111111. I enter the unlock code and it says successful and I get the warning message on my phone about unlocking the bootloader and I hit yes to unlock. After the phone reboots all my data is wiped but when I reboot back into bootloader it still says relocked. I have tried multiple times with multiple unlock codes but no dice. I cannot get into stock recovery either after running the stock RUU. Anyone have any ideas? Thanks.
Click to expand...
Click to collapse
boot into the ROM and make sure USB debugging is enabled.. Reboot to fastboot and type "fastboot erase cache" and then try to unlock again
absolutelygrim said:
boot into the ROM and make sure USB debugging is enabled.. Reboot to fastboot and type "fastboot erase cache" and then try to unlock again
Click to expand...
Click to collapse
Bingo! That did the trick. Thank you very much. Man I do miss my old s-off phones.
Related
I have use [XOOM][Wingray][STOCK]An easy way to return your XOOM to its *original* state but, at least step, i had push down bottom.. so i dont know if my wingray has bootloader locked or unlocked... can anybody help me??
thanks!
edudu1414 said:
I have use [XOOM][Wingray][STOCK]An easy way to return your XOOM to its *original* state but, at least step, i had push down bottom.. so i dont know if my wingray has bootloader locked or unlocked... can anybody help me??
thanks!
Click to expand...
Click to collapse
LOCKING BOOT LOADER
You need ADB so follow these steps.
To lock your boot loader you definitely need to have a proper connection between your device and computer.
To re lock your boot loader you need to:
1. Turn off your device
2. Hold your volume down button and press the power button. (KEEP HOLDING YOUR VOLUME DOWN BUTTON) You will see a white screen with fastboot written on it.
3. Navigate with your volume up or down to fastboot and press the power button to select it.
4. Connect your device with your computer,
5. Open the terminal in your computer and type in 'adb devices',
6. Type in 'fastboot oem lock' without quotes and your device is locked again, you will see relocked.
but i don't know the status of my bootloader.. if i have bootloader unlocked, i can re-use the zip to back to stock, that it includes relock bootloader
and if i have bootloader locked, i will unlock it
how i can know if it is unlocked or locked? thanks!
edudu1414 said:
but i don't know the status of my bootloader.. if i have bootloader unlocked, i can re-use the zip to back to stock, that it includes relock bootloader
and if i have bootloader locked, i will unlock it
how i can know if it is unlocked or locked? thanks!
Click to expand...
Click to collapse
You could try flashing a custom recovery to it. If it works, then your bootloader is unlocked.
edudu1414 said:
but i don't know the status of my bootloader.. if i have bootloader unlocked, i can re-use the zip to back to stock, that it includes relock bootloader
and if i have bootloader locked, i will unlock it
how i can know if it is unlocked or locked? thanks!
Click to expand...
Click to collapse
Only try to flash a custom recovery. If it works, you have unlocked bootloader.
Remember that locking back your bootloader can brick your tablet, and that locked bootloader is not needed for the updates.
I unlocked twice my unlocked bootloader and notting happened, it said "it's already unlocked" or something similar, but do at your own risk.
i dont flash a recovery yet but.. i can enter to android system recovery <3e>
does this mean that i have bootloader unlocked?
thanks!
EDIT. i flash twp2 and it works.. so i hadn't have my bootloader locked..
sure, i'm gonna flash ICS.. no more JB now
I was installed with Twrp and had rooted my oneplus 3.
I unticked root access in supersu.
Booted to bootloader and typed on my pc in command prompt ,"Fastboot oem lock"
This gave a confirmation on my device,I confirmed locking.
And after that my device did not booted up.I managed to get in bootloader again as I was not even able to open the recovery and unlocked the bootloader once again by this my device booted up.
I flashed stock recovery and repeated the relocking process,this time I was able to open recovery also but no able to boot up.
I again unlocked the bootloader and installed twrp back turned my device up.
Then I unchecked oem unlocking under developer options.
Relocked the bootloader once again.
And now I am stuck at bootloader,not able to unlock it even this time as I turned off oem unlocking.
Now I can only open bootloader.
Please help!
hchawla98 said:
I was installed with Twrp and had rooted my oneplus 3.
I unticked root access in supersu.
Booted to bootloader and typed on my pc in command prompt ,"Fastboot oem lock"
This gave a confirmation on my device,I confirmed locking.
And after that my device did not booted up.I managed to get in bootloader again as I was not even able to open the recovery and unlocked the bootloader once again by this my device booted up.
I flashed stock recovery and repeated the relocking process,this time I was able to open recovery also but no able to boot up.
I again unlocked the bootloader and installed twrp back turned my device up.
Then I unchecked oem unlocking under developer options.
Relocked the bootloader once again.
And now I am stuck at bootloader,not able to unlock it even this time as I turned off oem unlocking.
Now I can only open bootloader.
Please help!
Click to expand...
Click to collapse
OEM locking a bootloader on a phone that was rooted is a big mistake.
You'll need to flash stock recovery, then flash the stock ROM via adb sideload.
Can be done with this tool http://forum.xda-developers.com/oneplus-3/development/toolkit-oneplus-3-toolkit-unlock-t3398799
Thanks for reply
Newyork! said:
OEM locking a bootloader on a phone that was rooted is a big mistake.
You'll need to flash stock recovery, then flash the stock ROM via adb sideload.
Can be done with this tool http://forum.xda-developers.com/oneplus-3/development/toolkit-oneplus-3-toolkit-unlock-t3398799
Click to expand...
Click to collapse
with that tool I was only able to wipe cache.
Nothing else is working
It says failed
hchawla98 said:
with that tool I was only able to wipe cache.
Nothing else is working
It says failed
Click to expand...
Click to collapse
Can you access stock recovery?
NO
Newyork! said:
Can you access stock recovery?
Click to expand...
Click to collapse
I can't access it as I am installed with TWRP Recovery as it is also not starting.
Hello guys, I dont know whats happening with my Nexus 5 right now. Its stuck on Google logo which appears during restarting of the phone.
I have tried everything. I try to go into recovery it dosent work. I tried changing it to CWM from TWRP still it stays TWRP i get errors while flashing .bat files like (error: failure to write). Please help been stuck on this since past 72hours. Any help to resolve this issue is appreciated. Thanks :crying::crying::crying:
If the bootloader is unlocked, relock the bootloader and reboot into fastboot mode. If the bootloader unlocks itself, the internal memory is probably damaged. If the bootloader remains locked, unlock it and flash 4.4 using fastboot commands.
audit13 said:
If the bootloader is unlocked, relock the bootloader and reboot into fastboot mode. If the bootloader unlocks itself, the internal memory is probably damaged. If the bootloader remains locked, unlock it and flash 4.4 using fastboot commands.
Click to expand...
Click to collapse
OEM can be locked and unlocked. But the only problem now is i cannot override the previous partitions as there is an error "failed to write" i dont understand why is this happening this is also the reason i cannot get into my recovery as when i enter recovery it gets stuck for some reason.
audit13 said:
If the bootloader is unlocked, relock the bootloader and reboot into fastboot mode. If the bootloader unlocks itself, the internal memory is probably damaged. If the bootloader remains locked, unlock it and flash 4.4 using fastboot commands.
Click to expand...
Click to collapse
Also what does flash 4.4 mean? Sorry new to this!
audit13 said:
If the bootloader is unlocked, relock the bootloader and reboot into fastboot mode. If the bootloader unlocks itself, the internal memory is probably damaged. If the bootloader remains locked, unlock it and flash 4.4 using fastboot commands.
Click to expand...
Click to collapse
Also i tried to erase partitions manually but i always got an error as (remote: failed to erase partition)
Let's start with the bootloader.
Boot into fastboot mode, lock the bootloader, reboot into fastboot mode. Does the bootloader stay "locked" or does it go back to say "unlocked"?
audit13 said:
Let's start with the bootloader.
Boot into fastboot mode, lock the bootloader, reboot into fastboot mode. Does the bootloader stay "locked" or does it go back to say "unlocked"?
Click to expand...
Click to collapse
It goes back to unlocked
audit13 said:
Let's start with the bootloader.
Boot into fastboot mode, lock the bootloader, reboot into fastboot mode. Does the bootloader stay "locked" or does it go back to say "unlocked"?
Click to expand...
Click to collapse
Do you have discord or teamspeak or any other apps to chat directly?
NeXussssssssss said:
It goes back to unlocked
Click to expand...
Click to collapse
The internal memory may be damaged.
You might want to try this: https://forum.xda-developers.com/google-nexus-5/general/how-fixed-bricked-nexus-5-corrupted-t2903593
audit13 said:
The internal memory may be damaged.
You might want to try this: https://forum.xda-developers.com/google-nexus-5/general/how-fixed-bricked-nexus-5-corrupted-t2903593
Click to expand...
Click to collapse
I tried the 1st step by overwriting twrp with cwm dint work. Also ADB isnt connected. I tried to but just fastboot works.
I recommend flashing stock 4.4 using fastboot commands.
Stock ROMs are here: https://developers.google.com/android/images
audit13 said:
I recommend flashing stock 4.4 using fastboot commands.
Stock ROMs are here: https://developers.google.com/android/images
Click to expand...
Click to collapse
I tried flashing new roms it says failure to write to cache,boot,recovery everything fails!
There is no way to erase partitions as it fails!
I would say the internal memory is damaged and will require a motherboard change.
So I got my new U12+, bought the unlocked version, I'm pretty sure when it updated it became locked??
Anyway, went to HTCdev to unlock and I get this message when I try
Security checking failed DENY
Shows it as locked S-ON
Should I reset it then get S-Off?
Sounds like you might be confusing a few things.
The Unlocked version is the sim-unlocked. The boot loader will be Locked S-ON. Two different things.
Now to unlock your boot loader to run custom software make sure you follow the steps exactly on HTCdev website.
Get your token key while in Download Mode, copy and paste the correct parts. Then unlock once you have the correct unlock token bin from HTC.
Unlocking your boot loader is all down while in Download Mode. Make sure your have OEM boot loader unlock enabled in Developer Settings.
What a dummy....
OK, de-bugging on and OEM unlocking is enabled.
Tried the steps at HTC and got no response from the phone after typing the get identifier command
I'll try again
BTW, is it just me or is it a pain to get the button sequence just right?
geoffwoerner said:
What a dummy....
OK, de-bugging on and OEM unlocking is enabled.
Tried the steps at HTC and got no response from the phone after typing the get identifier command
I'll try again
BTW, is it just me or is it a pain to get the button sequence just right?
Click to expand...
Click to collapse
It's annoying. But if you have adb on your computer with Debugging enabled within Developer Settings.
adb reboot bootloader
Thatll save you a few a minute or two
OK, so now I'm stumped again,
adb reboot bootloader
phone reboots as it should
fastboot oem get_identifier_token and nothing
<waiting for any device>
Never Mind, took a few tries and new drivers, we're good to go!
How were you able to resolve it? what drivers should i download? I tried twice and i am getting the same message:
Error Code: Invalid Bootloader Token Length.
Error Reason: The submitted Token appears to be the wrong length and won't work.
HTC u 12 Plus . android 9. adb and fastboot installed on a mac os mojave
Hey guys,
I am trying to unlock my bootloader but it doesnt work, everytime I do the "Fastboot oem get_unlock_data" command, it says it failed to get unlock data.
I have unlock bootloader option in dev settings enabled and all drivers properly installed along with fully working sdk and fastboot tools etc. I have a couple xiaomi devices with different custom roms.
Previously I installed RETLA using tiny fastboot script cus i bought the phone in latin america but software channel says RETAR... Is this discrepancy the problem?
If not, anyone know why even though bootloader unlock option is on, the fastboot command to get the data fails?
Using getvar all i see the cid is 0x0000, i've read that having cid: 0x0000 is the problem, might installing the proper firmware: RETAR change this?
Ty
Hpotersept2 said:
cid is 0x0000
Click to expand...
Click to collapse
Most likely you will have to forget about unlocking the bootloader.
Reflashing will not help you in any way.
ilia3367 said:
Most likely you will have to forget about unlocking the bootloader.
Reflashing will not help you in any way.
Click to expand...
Click to collapse
Do you know why the cid is like that? Idk what has been done to it cus I bought it used. Any ideas?
Ty
The boot loader on your phone was blocked incorrectly and the system stopped starting.
cid: 0x0000 is a consequence of the boot loader working state recovery software.
It is now in a state oem-locked" as it was originally from the factory. But you cannot unlock the bootloader now. But, if I'm not mistaken, you can install firmware for any update region without having to unlock the bootloader.