OEM Unlocking toggled.
Unlock data submitted to Motorola.
Email received with unlock code.
Running unlock code on fastboot gives me "by unlocking the bootloader, you will..." screen with "DO NOT UNLOCK THE BOOTLOADER" and "UNLOCK THE BOOTLOADER" options.
When I select "UNLOCK THE BOOTLOADER" and click start, the bootloader still shows as oem_locked after.
I've rooted a number of Moto phones before. Never seen this bug before. Is it a known bug?
Bump. Anyone know how to resolve this?
Related
So I went through steps to "un-grey" the OEM unlocking in dev settings, and success! I got it to work and immediately booped the option and restarted. But when I typed "fastboot flashing unlock", I still get "Flashing unlock is not allowed". Any idea what I'm doing wrong? Afaik, the phone was only ever used on ATT, not the cursed Verizon.
engineer_james said:
So I went through steps to "un-grey" the OEM unlocking in dev settings, and success! I got it to work and immediately booped the option and restarted. But when I typed "fastboot flashing unlock", I still get "Flashing unlock is not allowed". Any idea what I'm doing wrong? Afaik, the phone was only ever used on ATT, not the cursed Verizon.
Click to expand...
Click to collapse
I think there is currently no solution to unlock bootloader yet for greyed out OEM option.
even if you got the un-grey OEM option as Pixel 2 has a security chip that blocks the unlocking ( unlike OG Pixel that doesn't have )
I'm in the same boat as the OP. I have the option to turn on 'OEM unlocking' so when I attempted to unlock my bootloader last night I received FAILED (remote: 'Flashing Unlock is not allowed') in the command prompt. Now 'OEM unlocking has been greyed out after the failed attempt. What's going on here?
Currently trying to root my google pixel 2. The guy who sold me this phone said it was unlocked but I guess that was a LIE. When it arived, It had a verizon SIM card and the OEM unlockd button was grayed out. Surprisingly, this method actually managed to get the grayed out OEM unlock button to turn blue:
Here’s an easy method to bootloader unlock a Verizon Pixel or Pixel XL
There's now a simple method to unlock the bootloader of your Verizon-branded Google Pixel or Pixel XL. Give your phone new life!
www.androidauthority.com
However, after I ran "adb reboot bootloader" the command "fastboot oem unlock" still failed. And after the OS booted, the button was grayed out again.
1. What is actually going on here? Why does this method seem to work for some people?
2. Is there any way to get around this?
anon_lastname said:
Currently trying to root my google pixel 2. The guy who sold me this phone said it was unlocked but I guess that was a LIE. When it arived, It had a verizon SIM card and the OEM unlockd button was grayed out. Surprisingly, this method actually managed to get the grayed out OEM unlock button to turn blue:
Here’s an easy method to bootloader unlock a Verizon Pixel or Pixel XL
There's now a simple method to unlock the bootloader of your Verizon-branded Google Pixel or Pixel XL. Give your phone new life!
www.androidauthority.com
However, after I ran "adb reboot bootloader" the command "fastboot oem unlock" still failed. And after the OS booted, the button was grayed out again.
1. What is actually going on here? Why does this method seem to work for some people?
2. Is there any way to get around this?
Click to expand...
Click to collapse
I just tried my AT&T SIM card in the phone and it worked... So the phone is not even carrier locked, but the bootloader is locked.
If you can reactivate the OEM unlock button try using 'fastboot flashing unlock' rather than the OEM unlock command. Mine wasn't carrier locked but fastboot flashing unlock unlocked my bootloader.
Had the same drama unlocking a pixel I had and fastboot flashing unlocked sorted the bootloader once I'd activated the OEM unlock button.
Junglism93 said:
If you can reactivate the OEM unlock button try using 'fastboot flashing unlock' rather than the OEM unlock command. Mine wasn't carrier locked but fastboot flashing unlock unlocked my bootloader.
Had the same drama unlocking a pixel I had and fastboot flashing unlocked sorted the bootloader once I'd activated the OEM unlock button.
Click to expand...
Click to collapse
I tried that after using the exploit in the OP to get the unlock OEM button. Didn't work.
I'm pretty much done with this POS phone.
anon_lastname said:
I tried that after using the exploit in the OP to get the unlock OEM button. Didn't work.
I'm pretty much done with this POS phone.
Click to expand...
Click to collapse
Fair enough mate, worth a try but definitely sounds like it's the end of the road for unlocking it sadly. Might be time to sell it on mad move on to something else.
I'm not asking how, I already know that part. I have an unlocked TMobile/Sprint phone, but from reading TMobile roms are a bit different as they do thier own or modified oos.
I have checked and I can toggle the oem locking in settings. I own the phone outright but I don't have an unlocked sim. I've heard with TMobile you have to call and have the sim unlocked , which in turn let's you then toggle the oem unlock so you can unlock the bootloader.
So my question is, since I bought the phone unlocked, and I can toggle the oem unlock feature, can I just unlock the bootloader now and proceed with root or does it sim need to be unlocked too??
You have to go into fastboot to check if you have it toggled on in dev options go into bootloader and do fastboot oem unlock from command prompt it will unlock or it won't you may have to get an unlock token from one plus also TMobile locks bootloader you need an unlock token file
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
Question - is anyone having issues unlocking the boot loader of Motorola devices, from old to new?
I have a few old devices that I need to unlock the boot loader to test some ROM's, TWRP etc. and I go through the Motorola site as you have to. After I enter the unlock code (removing all the (bootloader) and spaces), I always now get "The device is not eligible for bootloader unlocking". I have had this issue before and assumed it was a vendor locked device, but now with more than five devices having the same message, surely they all cannot be ineligible for bootloader unlocking. The CSN code with getvar indicates the bootloader is able to be unlocked.
Is any else experiencing this?
Is it logging in with the same account?