My device is a OnePlus 8T originally purchased from T-Mobile. I unlocked the bootloader to flash OxygenOS 12 in the open beta. Everything is working splendidly, but I can't seem to relock the bootloader. Using fastboot flashing lock, I get an error message asking me to flash the unlock token first. When attempting fastboot flash cust-unlock unlock_token.bin, I get an error asking to turn on OEM unlocking. OEM unlocking is greyed out because the bootloader is unlocked. Can you help? Thanks!
scothouse said:
My device is a OnePlus 8T originally purchased from T-Mobile. I unlocked the bootloader to flash OxygenOS 12 in the open beta. Everything is working splendidly, but I can't seem to relock the bootloader. Using fastboot flashing lock, I get an error message asking me to flash the unlock token first. When attempting fastboot flash cust-unlock unlock_token.bin, I get an error asking to turn on OEM unlocking. OEM unlocking is greyed out because the bootloader is unlocked. Can you help? Thanks!
Click to expand...
Click to collapse
here brother:
Thanks, but my phone asks for an unlock token when I execute fastboot oem lock or fastboot flashing lock I get the error message: FAILED (remote: 'Please flash unlock token first.') When attemptIng to flash the token, I get the error message: FAILED (remote: 'Please turn on OEM unlocking in Settings - Developer option'). I heard back from OnePlus Support, and it sounds like I would need to perform a factory reset in order to lock the bootloader. That would revert the phone to the T-Mobile OxygenOS 11 image. I unlocked the bootloader so that I could flash the global OxygenOS 12 image. Also, I'm hearing from other folks in the OnePlus Community that the bootloader should remain unlocked if I'm in the beta. I'm not sure about that, but, for now, I haven't found a way to lock the bootloader and retain the beta image. Thanks, tho, I appreciate the link.
scothouse said:
Thanks, but my phone asks for an unlock token when I execute fastboot oem lock or fastboot flashing lock I get the error message: FAILED (remote: 'Please flash unlock token first.') When attemptIng to flash the token, I get the error message: FAILED (remote: 'Please turn on OEM unlocking in Settings - Developer option'). I heard back from OnePlus Support, and it sounds like I would need to perform a factory reset in order to lock the bootloader. That would revert the phone to the T-Mobile OxygenOS 11 image. I unlocked the bootloader so that I could flash the global OxygenOS 12 image. Also, I'm hearing from other folks in the OnePlus Community that the bootloader should remain unlocked if I'm in the beta. I'm not sure about that, but, for now, I haven't found a way to lock the bootloader and retain the beta image. Thanks, tho, I appreciate the link.
Click to expand...
Click to collapse
Yeah, there is no way to retain the beta image until OnePlus Gives an official update of OxygenOS 12 for your phone. and if you want to lock bootloader, u have to be on the official version.
BUT THERE IS NO WAY TO LOCK BOOTLOADER AND USE OxygenOS 12 FOR NOW. SO STOP SEARCHING
Gotcha - makes sense and will do. Thanks again!
Spuffyffet said:
BUT THERE IS NO WAY TO LOCK BOOTLOADER AND USE OxygenOS 12 FOR NOW. SO STOP SEARCHING
Click to expand...
Click to collapse
There is no mentioning of unlocking bootloader for OB1 OOS12 in official thread.
@scothouse I ran into a smiliar situation with the OnePlus 8 5g tmobile. After installing the global Rom and upgrading to android 12 i couldnt relock it.
so what i did was downgrade my phone to android 11. the OEM unlocking was still greyed out but i was able to execute the fastboot flash cust-unlock unlock_token.bin command. then voila i locked it.
once you do that then update your phone then you are down.
Just use MSM tools. Of course everything will be factory reset
samdaman91 said:
@scothouse I ran into a smiliar situation with the OnePlus 8 5g tmobile. After installing the global Rom and upgrading to android 12 i couldnt relock it.
so what i did was downgrade my phone to android 11. the OEM unlocking was still greyed out but i was able to execute the fastboot flash cust-unlock unlock_token.bin command. then voila i locked it.
once you do that then update your phone then you are down.
Click to expand...
Click to collapse
Were you able to re-upgrade to Android 12 once the bootloader was locked again?
jefffeely said:
Were you able to re-upgrade to Android 12 once the bootloader was locked again?
Click to expand...
Click to collapse
Yes with OTA
In case anyone is on Android 13, I was able to re-lock the bootloader without issue.
I didn't need the unlock_token back when I flashed the global ROM to replace the Tmo one. I do need the token for the re-lock purpose though
Related
I have a SIM unlocked Oneplus 7 pro T-Mobile version that had gone through the process of unlocking boot loader with adb and fastboot.
But when I try the command "fastboot oem unlock". I get an error code with "Remote: Please flash unlock code".
I was able to get the unlock code using another fastboot command, but I haven't been able to find out how to either apply it, flash it, or maybe I missed something?
Nitruckz said:
I have a SIM unlocked Oneplus 7 pro T-Mobile version that had gone through the process of unlocking boot loader with adb and fastboot.
But when I try the command "fastboot oem unlock". I get an error code with "Remote: Please flash unlock code".
I was able to get the unlock code using another fastboot command, but I haven't been able to find out how to either apply it, flash it, or maybe I missed something?
Click to expand...
Click to collapse
You must get the BL unlock token from OnePlus.
https://www.oneplus.com/account/sign-in?return_to=https://www.oneplus.com/unlock_token
https://www.getdroidtips.com/how-to-unlock-t-mobile-oneplus-7-pro-bootloader/
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.
I have already unlocked the sim on my phone and enabled oem unlocking and USB debugging and when I reboot to the bootloader then type in "fastboot oem get_unlock_code" it just sits on a message "< waiting for device >" Does anyone know what im doing wrong or how to fix this
stez827 said:
I have already unlocked the sim on my phone and enabled oem unlocking and USB debugging and when I reboot to the bootloader then type in "fastboot oem get_unlock_code" it just sits on a message "< waiting for device >" Does anyone know what im doing wrong or how to fix this
Click to expand...
Click to collapse
I have a global op9 and the command is "fastboot oem unlock" not sure if it's different with your device but that command allows me to unlock my bl.
mattie_49 said:
I have a global op9 and the command is "fastboot oem unlock" not sure if it's different with your device but that command allows me to unlock my bl.
Click to expand...
Click to collapse
Yeah that would work if I had a global one not a TMobile one but since it's TMobile I have to get an unlock code send that to TMobile wait a week or 2 and then I can unlock it
stez827 said:
Yeah that would work if I had a global one not a TMobile one but since it's TMobile I have to get an unlock code send that to TMobile wait a week or 2 and then I can unlock it
Click to expand...
Click to collapse
You can use an MSM tool to flash the global rom for 11 bypassing the need for the unlock token. However, if you decide to go to OOS 12, you'll need the unlock token once more. Source: Spent the past two weeks fiddling with my T-Mo OP9
posar said:
You can use an MSM tool to flash the global rom for 11 bypassing the need for the unlock token. However, if you decide to go to OOS 12, you'll need the unlock token once more. Source: Spent the past two weeks fiddling with my T-Mo OP9
Click to expand...
Click to collapse
I'm trying to flash another rom so I need to token anyway thanks for the help though
stez827 said:
I'm trying to flash another rom so I need to token anyway thanks for the help though
Click to expand...
Click to collapse
You can flash another rom after flashing global 11 and unlocking the bootloader. I was just warning you that you would still need the token if for some reason you decided to flash OOS 12.
posar said:
You can flash another rom after flashing global 11 and unlocking the bootloader. I was just warning you that you would still need the token if for some reason you decided to flash OOS 12.
Click to expand...
Click to collapse
Really ok I'll look more into that then thank you
"waiting for device" means its not seeing your device.. probably need the driver installed.
Idk why but for me, I had to disable windows driver verification for it to work
So, i recently flashed arrow os 12.1 on my poco x4 pro (veux) using twrp. Flashing the rom removed twrp and now i cant flash it back because fastboot says that my bootloader is locked...
Of course, it isn't and the problem is that allow oem unlocking isn't on... I really would appreciate some help because i've been stuck on this rom for a day.
Gonna wait for some answers, thank you.
In the first place, flashing the rom shouldn't relock your bootloader. Can you please reboot to fastboot mode and use mi unlock tool with the same account you used to unlock bootloader first time.
Soma Das said:
In the first place, flashing the rom shouldn't relock your bootloader. Can you please reboot to fastboot mode and use mi unlock tool with the same account you used to unlock bootloader first time.
Click to expand...
Click to collapse
Thank you for your response. Sadly i already tried that and the tool says that the phone is unlocked.
I'm trying to reflash stock rom via EDL mode, but i always get some error.
By the way, when using fastboot getvar command, it says that my bootloader is locked.
So, i recently bought a poco x4 pro (veux) and flashed a custom rom using twrp. Sadly, the rom's recovery managed to overwrite twrp and when i tried to flash twrp back, i could not flash it because fastboot said my bootloader wasn't unlocked. When i tried to unlock the phone again the xiaomi tool said that the bootloader was already unlocked. So, i used the getvar command which said that my bootloader was locked. So, i remembered that i didnt turn on allow oem unlocking in developer options. Sadly, when i looked for it the setting wasn't there. I tried using Edl mode to go back to stock but with no success. I always get some failed to read hello packet error. Can someone give me any help? Im kinda getting desperate...
WhyisAethertaken said:
So, i recently bought a poco x4 pro (veux) and flashed a custom rom using twrp. Sadly, the rom's recovery managed to overwrite twrp and when i tried to flash twrp back, i could not flash it because fastboot said my bootloader wasn't unlocked. When i tried to unlock the phone again the xiaomi tool said that the bootloader was already unlocked. So, i used the getvar command which said that my bootloader was locked. So, i remembered that i didnt turn on allow oem unlocking in developer options. Sadly, when i looked for it the setting wasn't there. I tried using Edl mode to go back to stock but with no success. I always get some failed to read hello packet error. Can someone give me any help? Im kinda getting desperate...
Click to expand...
Click to collapse
Go to service centre if it is critical. I have never seen such case so i couldn't help. I am afraid that you would have to pay the service centre people money for reflashing your device.
Also have you tried flashing fastboot ROM (MIUI) through fastboot? Also try to flash stock recovery rom via the recovery you have now currently.
Another thing you could try is using the Xiaomi official flashing utility (which is not unlock tool) to flash stock rom which does not require OEM unlock.
Soma Das said:
Go to service centre if it is critical. I have never seen such case so i couldn't help. I am afraid that you would have to pay the service centre people money for reflashing your device.
Also have you tried flashing fastboot ROM (MIUI) through fastboot? Also try to flash stock recovery rom via the recovery you have now currently.
Another thing you could try is using the Xiaomi official flashing utility (which is not unlock tool) to flash stock rom which does not require OEM unlock.
Click to expand...
Click to collapse
Thanks for the reply, i will try what you said.
Used MSMDT to reset to TMO firmware on KB2007 (OnePlus 8T) and now bootloader is locked and unlock token doesn't work again "FAILED (remote: 'Error - Verify Failed ! (4:-2)')" and my bootloader is permanently locked. Any help would be appreciated.
The MSM Tool returns the device to the way it was when you took it out of the box and booted it for the first time. Do you have USB Debugging enabled in Developer Options? You only need the token once. Have you tried using ADB to unlock the bootloader?
I checked oem unlock in the settings, and then tried to flash twrp and got an error saying the device was locked, tried fastboot oem unlock, and it told me to flash the unlock token, but it won't accept the token.
Try requesting another through OnePlus Support then.