When I try to unlock the bootloader the message "remote: oem unlock is not allowed" is shown and YES, I've allowed OEM unlocking in developer options. The device is also authorized in adb. So does anyone know how to fix this?
Related
Can anyone confirm that the bootloader is unlocked? or can be unlocked by the option in dev options, i believe it says OEM unlock or something to that effect.
Yes, OEM Unlock is there
Excellent! Thank you.
I have the US version the 690Y and get the remote failed unknown command error when I do the command fastboot oem unlock.I even tried the newer fastboot oem flashing unlock.Do you have any idea how to work this out?My device is recognized in fastboot,all drivers correct but I keep getting errors.Any ideas?I haven't seen anyone post they've successfully unlocked the bootloader yet so I assume it's not possible as of yet?I appreciate any suggestions.
bob24260 said:
I have the US version the 690Y and get the remote failed unknown command error when I do the command fastboot oem unlock.I even tried the newer fastboot oem flashing unlock.Do you have any idea how to work this out?My device is recognized in fastboot,all drivers correct but I keep getting errors.Any ideas?I haven't seen anyone post they've successfully unlocked the bootloader yet so I assume it's not possible as of yet?I appreciate any suggestions.
Click to expand...
Click to collapse
So far it doesn't seem possible on the 690Y but works on the 690M. The lack of development for this phone is sad. I would gladly pay for a root option.
There must be some way to easily unlock the bootloader since the option "OEM unlocking - Allow the bootloader to be unlockled" exists in the developer settings. What are we missing?
I have the 690M and same, I check allow OEM unlock in developer settings but then the command is not recognized.
Ideas?
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?
What could be reason behind "oem unlock failed" if your device bootloader is already unblocked?
You said its "unblocked" which pretty much means its already unlocked or something.
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?