Pretty much what the title says. I'm on Android 7.1 (crDroid) with TWRP Alka installed and bootloader initially officially unlocked but now it shows that it's locked. Also, I tried unlocking with MiUnlock and it doesn't work. What do I do?
Just use MiFlash in Fastboot with Fastboot MIUI ROM. If you scared of EDL mode and/or it said your bootloader is locked then read below:
You can re-unlock it by using fastboot. You need adb, fastboot, xiaomi driver to do this. I recommend to use universal ADB & Fastboot.
Boot your phone to fastboot screen (aka bootloader mode) by using advanced reboot or adb terminal "reboot bootloader" or hardware key: Volume Down + Power
Code:
fastboot devices
fastboot oem device-info
If it show up with "Device unlocked: false" then unlock it by using:
Code:
fastboot oem unlock-go
Click to expand...
Click to collapse
If you setup MiCloud before going custom ROM, you will need to enter your MiAccount ID/E-mail and password.
Your phone will be locked again after using MiFlash, but you are at MIUI and you can use MiUnlock to unlock it anytime.
hey please help i am unable to unlock boot loader of my coolpad note 5 which has snapdragon 617 soc, no unlock code type help or instruction on official forum and no help there because all command returns as unknown command ,
i tried many command except these two command all return unknown command ,
fastboot devices works shows device no
fast getvar all works showing something
i checked all driver installed properly and pc showing it on device manager as fastboot device even fastboot recognized it as a fastboot devices, also i allow oem unlocking on developer setting and enabled usb debugging
after this all command like
fastboot oem unlock
fastboot oem unlock-go
fastboot boot
fastboot reboot
fastboot flashing unlock
fastboot oem device-info
fastboot flash
all and more i found i net returns unknown command remote
i tried with vendor id but no result
i checked fastboot getvar all returns its kernal as lk
so do little kernel has problem , i have its firmware package but not found aboot.c
please help its unrooted
attached error command screenshot in zip
I am facing same issues
Sent from my Andromax A16C3H using Tapatalk
I tryed to unlock my bootloader using "fastboot oem unlock (unlock code)" but it fails and gives the messege in the photo
https://drive.google.com/file/d/0B1SKvTTgj1mXcEdabGtPaDlnWDg/view?usp=sharing
any idea to solve this
this is the photo of my device in fastboot mode
https://drive.google.com/file/d/0B1SKvTTgj1mXcWtoT0ZWV0FTMXM/view?usp=sharing
sahlshd said:
I tryed to unlock my bootloader using "fastboot oem unlock (unlock code)" but it fails and gives the messege in the photo
https://drive.google.com/file/d/0B1SKvTTgj1mXcEdabGtPaDlnWDg/view?usp=sharing
any idea to solve this
this is the photo of my device in fastboot mode
https://drive.google.com/file/d/0B1SKvTTgj1mXcWtoT0ZWV0FTMXM/view?usp=sharing
Click to expand...
Click to collapse
You need to turn on oem unlock in developer options
Sent from my Nexus 6P using Tapatalk
Oem unlock is not shown in developer options I tryed to turn it on using "fastboot enable oem unlocking" but it seems nothing happens
Thanks in advance
Goto settings developer options and enable oem unlock
I have enabled OEM unlock in developer mode,
but fastboot oem unlock / fastboot flashing unlock does not work.
I am trying to unlock the bootloader for my device (it's a cheap Chinese phone) and then root using Magisk. The first problem is that OEM Unlock option is not available in developer options, so I got no choice other than try unlocking using fastboot. Now the second problem is that fastboot doesn't show anything at all. Normally there is a Fastboot written at the top left corner of the device but in my case there is no output but the blank screen, and I do verify that my device is in fastboot mode because when I do fastboot devices, it show's the output:
Code:
C:\Users\Mujtaba>adb devices
List of devices attached
Y3123A0310Q0100020953 device
C:\Users\Mujtaba>adb reboot bootloader
C:\Users\Mujtaba>fastboot devices
Y3123A0310Q01000209 fastboot
Since fastboot was responding (partially), I tried to unlock the bootloader using different commands but each time I get read/write failed error.
Code:
C:\Users\Mujtaba>fastboot oem unlock
...
FAILED (command write failed (Unknown error))
finished. total time: 5.011s
C:\Users\Mujtaba>fastboot oem unlock
...
FAILED (status read failed (Too many links))
finished. total time: 80.886s
Alas, I got the same results with fastboot oem unlock-go and fastboot flashing unlock as fastboot is not accepting (at least I think) any command except fastboot devices.
I read the official guide and there I found that:
Devices should deny the fastboot flashing unlock command unless the get_unlock_ability is set to 1. If set to 0, the user needs to boot to the home screen, open the Settings > System > Developer options menu and enable the OEM unlocking option (which sets the unlock_ability to 1).
Click to expand...
Click to collapse
My device supports unlocking bootloader because I've checked the build.prop file using adb shell getprop and it includes the properties stated below:
The ro.oem_unlock_supported property should be set at build time based on whether the device supports flashing unlock.
If the device suppports flashing unlock, set ro.oem_unlock_supported to 1. If the device doesn't support flashing unlock, set ro.oem_unlock_supported to 0. If the device supports flashing unlock, then the bootloader should indicate the lock status by setting the kernel command line variable androidboot.flash.locked to 1 if locked or 0 if unlocked.
For devices that support dm-verity, use ro.boot.verifiedbootstate to set the value of ro.boot.flash.locked to 0; this unlocks the bootloader if the verified boot state is orange.
Click to expand...
Click to collapse
Code:
C:\Users\Mujtaba>adb shell getprop
[ro.oem_unlock_supported]: [1]
[ro.boot.verifiedbootstate]: [green]
[ro.boot.flash.locked]: [1]
[sys.oem_unlock_allowed]: [0]
.
.
Someone on reddit did this to find the OEM unlock state, mine of course returned 0 as you can see above.
Code:
adb shell getprop sys.oem_unlock_allowed
Device Specs:
CPU: ARM Cortex-A-7 @ 1.20 Ghz
GPU: Mali-400 MP
Board: sp7731cea (Unisoc aka Spreadtrum)
Build: Q Infinity C_MP_26_01
Treble: NA
Seamless update (A/B): NA
Your phone is based on Spreadtrum chipset. Means such a device has its own mechanism to unlock the bootloader.
jwoegerbauer said:
Your phone is based on Spreadtrum chipset. Means such a device has its own mechanism to unlock the bootloader.
Click to expand...
Click to collapse
Yes I know that and I already found a method but again it uses oem get_identifier_token to get Identifier token and when I do that fastboot returns nothing.
There are other methods as well, like getting a PAC file for your device then extracting boot.img from it, patching it with magisk manager and then flashing that single partition (in this case BOOT partition) using SPD Research Tool but it gives me error as well.
Install the matching Android USB Driver if not done yet. Having installed common ADB / Fastboot drivers isn't enough.
Additional advice: Replace Help in this thread's title by QMobile QInfinity C
jwoegerbauer said:
Install the matching Android USB Driver if not done yet. Having installed common ADB / Fastboot drivers isn't enough.
Additional advice: Replace Help in this thread's title by QMobile QInfinity C
Click to expand...
Click to collapse
I have installed SPD drivers and Google USB drivers however the problem is not with drivers because I can use the following commands without an issue:
Code:
fastboot devices
fastboot reboot
fastboot reboot bootloader
The problem occurs when using:
Code:
fastboot oem unlock
fastboot flashing unlock
Google's USB driver is only suitable to Google devices like the Pixel / Nexus.
As already said: Install the Android USB Driver matching your phone!
Take note that OEM's Fastboot implementation isn't always same as AOSP 's Fastboot.
IMO before trying to unlock a device's bootloader it's always a good idea to check by means of ADB whether unlocking the bootloader is natively supported on device:
Code:
adb shell "getprop ro.oem_unlock_supported"
If returned value is 1, then it's supported otherwise it's not.
BTW: I no longer participate this thread.
jwoegerbauer said:
IMO before trying to unlock a device's bootloader it's always a good idea to check by means of ADB whether unlocking the bootloader is natively supported on device:
Code:
adb shell "getprop ro.oem_unlock_supported"
If returned value is 1, then it's supported otherwise it's not.
Click to expand...
Click to collapse
I've already included this property in the post. It returned 1