remote: oem unlocked is not allowed [Mi A1]

nicobelic · May 26, 2018

Hello everyone.

I got this problem today. My Mi A1 doesn't want to unlock the bootloader, and I follow all the instructions. In the cmd, when I type "fastboot oem unlock", this error appears "remote: unlock is not allowed".

Besides, the smartphone is frozen on the screen of initialization of Mi, making it impossible for me to go in the administrator options of the device.

_mysiak_ · May 26, 2018 at 7:04 PM

Please describe what you did to the phone before it got to this state.

nicobelic · May 26, 2018 17 1 0

_mysiak_ said:
Please describe what you did to the phone before it got to this state.

I tried to install the gcam on the device and had to unlock the bootloader. At first work, I unlock it, and went to install gcam but it did not work so well. After that my device had some performance problems and I decided to reinstall the ROM using MiFlash.

As I was giving errors and I could not install by MiFlash, I searched for tutorials on Youtube, trying to install without MiFlash, I found some but did not work again. So, I decided to type in the cmd "flashboot oem lock" because I thought this would be the problem that I could not install the ROM by MiFlash and again, it worked, I managed to block it.

However, after searching again, I discovered that I had to unlock it, so I typed the "flashboot oem unlock" command and gave this error, and when I turn on the phone, just appear a white screen with Mi logo.

_mysiak_ · May 26, 2018 at 7:30 PM

Are you sure that you have Mi A1 phone? What was the system version before you tried to install Gcam?

nicobelic · May 26, 2018 17 1 0

_mysiak_ said:
Are you sure that you have Mi A1 phone? What was the system version before you tried to install Gcam?

I sure, the system was Android 8.0. Android One.

Chiggie14899 · Oct 9, 2014 32 13 0

Did you enable OEM unlocking from the Developer Options? Probably not. Enable it first and try again.

nicobelic · May 26, 2018 17 1 0

Chiggie14899 said:
Did you enable OEM unlocking from the Developer Options? Probably not. Enable it first and try again.

Like I said, I can't. My smartphone is in mode bootloop.

_mysiak_ · May 26, 2018 at 8:42 PM

Connect your phone in fastboot mode and type in "fastboot getvar all" and share the output please.

mardrest · May 26, 2018 at 8:47 PM

nicobelic said:
Like I said, I can't. My smartphone is in mode bootloop.

Try flashing in edl mode, in fastboot type in cmd: fastboot oem edl, it will give you a fail. It's normal, you should have a black screen and the led blinking. Look if the drivers are installed and after install with MiFlash.

nicobelic · May 26, 2018 17 1 0

_mysiak_ said:
Connect your phone in fastboot mode and type in "fastboot getvar all" and share the output please.

fastboot getvar all
(bootloader) version:0.5
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:3828000
(bootloader) variant:QRD eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:MSM8953_TISSOT2.0_20180504180424
(bootloader) display-panel:
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) max-download-size: 0x1fe00000
(bootloader) slot-count:2
(bootloader) current-slot:_a
(bootloader) slot-retry-count:_b:7
(bootloader) slot-success:_b:No
(bootloader) slot-active:_b:No
(bootloader) slot-unbootable:_b:No
(bootloader) slot-retry-count:_a:7
(bootloader) slot-success:_a:Yes
(bootloader) slot-active:_a:Yes
(bootloader) slot-unbootable:_a:No
(bootloader) has-slot:userdata: No
(bootloader) has-slot:logdump: No
(bootloader) has-slot:dpo: No
(bootloader) has-slot:msadp: No
(bootloader) has-slot:apdp: No
(bootloader) has-slot:keymasterbak: No
(bootloader) has-slot:keymaster: No
(bootloader) has-slot:cmnlib64bak: No
(bootloader) has-slot:cmnlib64: No
(bootloader) has-slot:cmnlibbak: No
(bootloader) has-slot:cmnlib: No
(bootloader) has-slot:lksecappbak: No
(bootloader) has-slot:lksecapp: No
(bootloader) has-slot:mcfg: No
(bootloader) has-slot:syscfg: No
(bootloader) has-slot:mdtp: No
(bootloader) has-slot:dip: No
(bootloader) has-slot:mota: No
(bootloader) has-slot:limits: No
(bootloader) has-slot:config: No
(bootloader) has-slot:keystore: No
(bootloader) has-slot:misc: No
(bootloader) has-slot

ersist: No
(bootloader) has-slot:system: Yes
(bootloader) has-slot:devinfo: No
(bootloader) has-slot:boot: Yes
(bootloader) has-slot:abootbak: No
(bootloader) has-slot:aboot: No
(bootloader) has-slot:splash: No
(bootloader) has-slot:sec: No
(bootloader) has-slot:fsg: No
(bootloader) has-slot

DR: No
(bootloader) has-slot:modemst2: No
(bootloader) has-slot:modemst1: No
(bootloader) has-slot:dsp: No
(bootloader) has-slot:devcfgbak: No
(bootloader) has-slot:devcfg: No
(bootloader) has-slot:tzbak: No
(bootloader) has-slot:tz: No
(bootloader) has-slot:rpmbak: No
(bootloader) has-slot:rpm: No
(bootloader) has-slot:sbl1bak: No
(bootloader) has-slot:sbl1: No
(bootloader) has-slot:ssd: No
(bootloader) has-slot:fsc: No
(bootloader) has-slot:modem: Yes
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache:
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0xcd3779e00
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xc0000000
(bootloader) crc:1
(bootloader) serialno:349794d29805
(bootloader) kernel:lk
(bootloader) product:tissot
all:
finished. total time: 0.776s

nicobelic · May 26, 2018 17 1 0

mardrest said:
Try flashing in edl mode, in fastboot type in cmd: fastboot oem edl, it will give you a fail. It's normal, you should have a black screen and the led blinking. Look if the drivers are installed and after install with MiFlash.

This shows up:

>fastboot oem edl
...
OKAY [ 0.016s]
finished. total time: 0.016s

nicobelic · May 26, 2018 17 1 0

mardrest said:
Try flashing in edl mode, in fastboot type in cmd: fastboot oem edl, it will give you a fail. It's normal, you should have a black screen and the led blinking. Look if the drivers are installed and after install with MiFlash.

This shows up:

PHP:

>fastboot oem edl
...
OKAY [  0.016s]
finished. total time: 0.016s

mardrest · May 27, 2018 at 8:29 AM

nicobelic said:
This shows up:

PHP:

>fastboot oem edl ... OKAY [ 0.016s] finished. total time: 0.016s

If you have a black screen and the led blinks, then you are on edl mode, you can install the rom with MiFlash

nicobelic · May 26, 2018 17 1 0

mardrest said:
If you have a black screen and the led blinks, then you are on edl mode, you can install the rom with MiFlash

To be honest, nothing happened to the device, it still continues in "fastboot" mode after typing the command and no led blinks.

mardrest · May 27, 2018 at 6:16 PM

nicobelic said:
To be honest, nothing happened to the device, it still continues in "fastboot" mode after typing the command and no led blinks.

Try updating the driver, you can get from this sit: https://www.androidbrick.com/download/qualcomm_diag_qd_loader_2016_qfil_driver/

Custom rom 243 · Jun 5, 2017 211 30 0

Is "allow OEM unlcking" enabled ?? If not you can enable from developer options .

ProchyGaming · May 27, 2018 at 6:33 PM

Custom rom 243 said:
Is "allow OEM unlcking" enabled ?? If not you can enable from developer options .

As he said he can't get into the rom

Custom rom 243 · Jun 5, 2017 211 30 0

ProchyGaming said:
As he said he can't get into the rom

Oh that's why I thought such a obvious reason was not told by anyone .

---------- Post added at 06:37 PM ---------- Previous post was at 06:35 PM ----------

nicobelic said:
I tried to install the gcam on the device and had to unlock the bootloader. At first work, I unlock it, and went to install gcam but it did not work so well. After that my device had some performance problems and I decided to reinstall the ROM using MiFlash.

As I was giving errors and I could not install by MiFlash, I searched for tutorials on Youtube, trying to install without MiFlash, I found some but did not work again. So, I decided to type in the cmd "flashboot oem lock" because I thought this would be the problem that I could not install the ROM by MiFlash and again, it worked, I managed to block it.

However, after searching again, I discovered that I had to unlock it, so I typed the "flashboot oem unlock" command and gave this error, and when I turn on the phone, just appear a white screen with Mi logo.

Could you follow that same procedure of locking OEM and then booting into the ROM ? (,Just asking,not giving a solution)

nicobelic · May 26, 2018 17 1 0

mardrest said:
Try updating the driver, you can get from this sit: https://www.androidbrick.com/download/qualcomm_diag_qd_loader_2016_qfil_driver/

I install the driver, write "fastboot oem edl" command, nothing changes.

I think I screwed up realy bad.

nicobelic · May 27, 2018

This is happening

I found a video that shows the SAME PROBLEM I'm having with my Mi A1.

Why can not I fix the problem? I can not unlock the bootloader.

https://www.youtube.com/watch?v=51LnEOrM3nQ

This shows up when I tried: https://imgur.com/uAVuFle

remote: oem unlocked is not allowed [Mi A1]

Member

Senior Member

Member

Senior Member

Member

Member

Member

Senior Member

Senior Member

Member

Member

Member

Senior Member

Member

Senior Member

Senior Member

Senior Member

Senior Member

Member

Member