Days past I successfully unlocked the bootloader on my girlfriend's Taimen handset, flashed TWRP etc etc. No hitches whatsoever. I bought another for myself via the Google Store.
I booted it up today. As was on hers, OEM Unlock is prevented until I allow the handset to update to 8.1.
Done. OEM unlock then accessible and enabled.
I used my girlfriend's same PC with the same Minimal ADB and Fastboot, rebooted to fastboot and execute
Code:
fastboot flashing unlock_critical
Are you sure? ...volume up/down and power button to commit. Done. The unlock appeared successful as it rebooted to the out of box setup routine again.
I transferred the TWRP zip to the handset and rebooted to fastboot. Upon executing the command to temp boot TWRP from the IMG file fastboot
Code:
boot path "C:\Program Files (x86)\Minimal ADB and Fastboot\twrp-3.2.1-2-taimen.img"
I got the following response...
Code:
downloading 'boot.img'...
OKAY [ 0.870s]
booting...
FAILED (remote: Can not boot in Lock State)
finished. total time: 0.873s
Sure enough I look down at the handset and the fastboot menu reflects it's locked again. Weird.
I reboot and check OEM unlock. It reflects OEM unlock still toggled on. I go back to fastboot and again execute
Code:
fastboot flashing unlock_critical
Code:
FAILED (remote: Device already : unlocked!)
finished. total time: 0.002s
This is despite fastboot clearly showing "device state - locked"
I regress to dev options and toggle OEM unlock off. Reboot. Toggle OEM Unlock back on.
Same ill behavior.
Am I missing something??
try fastboot flashing unlock
depending on bootloader version you no longer need to fastboot flashing unlock_critical
see here.
@uicnren You a gentlemen and a scholar. Simple as that. Thanks.
Pay_It_Forward_Pete said:
@uicnren You a gentlemen and a scholar. Simple as that. Thanks.
Click to expand...
Click to collapse
:good:
Related
I'm trying to unlock the bootloader of my Nexus 5x, because I want to downgrade to 6.1 after proximity sensor issues. I tried "fastboot oem unlock" and "fastboot flashing unlock", but it looks like the bootloader auto-locks after reboot, and so I can't flash anything.
Did this happen to someone?
Do you have "Secure boot- enable (no rpmb)" on fastboot screen?
This is my fastboot screen
View attachment 3984342
You can't unlock bootloader because probably you have replacement emmc memory/motherboard without flashed rpmb partition. You can't do enything with that, but on this forum there is a topic, where someone wrote how to work around this problem.
Wuzimu said:
You can't unlock bootloader because probably you have replacement emmc memory/motherboard without flashed rpmb partition. You can't do enything with that, but on this forum there is a topic, where someone wrote how to work around this problem.
Click to expand...
Click to collapse
I sent my phone to LG support for an hardware problem, that's probably the cause. Thank you very much for your help
Here you go:http://forum.xda-developers.com/nexus-5x/help/bootloader-relocks-reboot-t3466854
unlock bootloader problem
C:\Program Files\Minimal ADB and Fastboot>fastboot oem unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.016s
mohitkhurama93 said:
C:\Program Files\Minimal ADB and Fastboot>fastboot oem unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.016s
Click to expand...
Click to collapse
Update your platform tools, make sure USB debugging is enabled, then try again.
Sent from my Nexus 5X using Tapatalk
I've got the lastest sdk tools and google usb driver installed and still get a fail when trying to run fastboot flashing unlock. I also have allow oem unlocking checked. Is there something I'm missing?
C:\Android>adb reboot bootloader
C:\Android>fastboot devices
7xxxxxxxxxxxx5 fastboot
C:\Android>fastboot flashing unlock
...
FAILED (command write failed (No error))
finished. total time: 0.003s
xxnirvana69xx said:
I've got the lastest sdk tools and google usb driver installed and still get a fail when trying to run fastboot flashing unlock. I also have allow oem unlocking checked. Is there something I'm missing?
C:\Android>adb reboot bootloader
C:\Android>fastboot devices
7xxxxxxxxxxxx5 fastboot
C:\Android>fastboot flashing unlock
...
FAILED (command write failed (No error))
finished. total time: 0.003s
Click to expand...
Click to collapse
sorry delete!!! try fastboot flashing unlock_critical
lucky_strike33 said:
did you go to developer and tick on to unlock bootloader?
Click to expand...
Click to collapse
Sure did. OEM unlocking is ticked.
lucky_strike33 said:
sorry delete!!! try fastboot flashing unlock_critical
Click to expand...
Click to collapse
Same thing.
C:\Android>fastboot devices
7xxxxxxxxxxxxxxxx5 fastboot
C:\Android>fastboot flashing unlock_critical
...
FAILED (command write failed (No error))
finished. total time: 0.003s
xxnirvana69xx said:
Same thing.
C:\Android>fastboot devices
7xxxxxxxxxxxxxxxx5 fastboot
C:\Android>fastboot flashing unlock_critical
...
FAILED (command write failed (No error))
finished. total time: 0.003s
Click to expand...
Click to collapse
Try a different cable?
Unfortunately I am at work and only have the C to C cable that was in the box.
My sdk/platform tools files are the same ones I've used with my 6P since 11-2015, and unlocking the 2 XL bl worked on the first attempt.
my process:
pow button + vol down
open cmd prompt in platform tools folder
fastboot devices (recognized my device)
fastboot flashing unlock
use vol up to select UNLOCK MY BOOTLOADER
power, to confirm
erases everything,
restarts
profit
Az Biker said:
My sdk/platform tools files are the same ones I've used with my 6P since 11-2015, and unlocking the 2 XL bl worked on the first attempt.
my process:
pow button + vol down
open cmd prompt in platform tools folder
fastboot devices (recognized my device)
fastboot flashing unlock
use vol up to select UNLOCK MY BOOTLOADER
power, to confirm
erases everything,
restarts
profit
Click to expand...
Click to collapse
Tried with a slightly older version I had for my og pixel and it worked. Wonder what was up with the other version.
xxnirvana69xx said:
Tried with a slightly older version I had for my og pixel and it worked. Wonder what was up with the other version.
Click to expand...
Click to collapse
I have the latest adb and fastboot files and can not get my device to be recognized by adb can anyone help me with this?
canemaxx said:
I have the latest adb and fastboot files and can not get my device to be recognized by adb can anyone help me with this?
Click to expand...
Click to collapse
Pm instead
xxnirvana69xx said:
Found this to possibly get you an older version of the platform tools...
"Well, you could use direct link, like
Click to expand...
Click to collapse
I started off with what I was using with my pixel XL and that didn't work and I have installed about 10 different version thus far and still nothing
I basically ended up using another cable, different version of adb, and another computer. Hard to tell what the problem exactly was since I changed 3 things at the same time between it not working and working. My guess is the cable and/or the computer.
Hey guys, i have to send my Pixel C to repair so i want to lock my bootloader. My Problem is, that i cant enable OEM unlocking in the developer options because its grayed out saying that my bootloader is already unlocked. "fastboot flashing lock" and "fastboot oem lock" both give me the error "FAILED (remote: Enable OEM unlock is not set)".
Is there a workaround for this?
Thanks for your help!
I also have this issue.
Same thing here. I loaded LineageOS and have decided to go back to factory. I can't figure it out either. Here are my results.
fastboot flashing lock
FAILED (remote: Enable OEM unlock is not set)
finished. total time: 0.022s
fastboot flashing unlock
FAILED (remote: Device already unlocked)
finished. total time: 0.003s
fastboot flashing get_unlock_ability
(bootloader) 0
OKAY [ 0.020s]
finished. total time: 0.020s
Ok all, I finally figured it out.
I had to download factory image 6.0.1 (MXB48J) go thru the instructions to flash this image.
Started up in android went thru the min setup to get into Settings and Developer Options. Turn on USB debugging and the OEM Unocking.
adb reboot bootloader
flashboot flashing lock
Prompted me about wiping the device.
Everything is good.
good friends after an update my google pixel stays in boot loop I have tried several ways to unlock the bootloader to install a stock rom from flashboot but every time i try to unlock the bootloader it tells me that i have to activate or unlock the oem option
I tried to do it with the adb flashtool but it gives me error
c:\adb>fastboot oem unlock
FAILED <remote: oem unlock is not allowed>
finished. total time: 0.044s
c:\adb>
I can not enter the Android system either from my Google Pixel since it is damaged the same to activate the option of OEM
I need someone to help me with this problem because the phone does not let me do anything for the fastboot because the bootloader and the OEM are blocked
Hello,
today i got a Moto E20 for debugging my webservices. I habe to Unlock the Bootloader for that.
I enabled the Developer-Menu in Android and the oem_unlock and usb-debugging in the settings.
When i boot the device into fastboot all seems OK... i get a connection with adb and fastboot to the device.
But all "fastboot oem XXX" commands just reply
fastboot oem device_info
...
OKAY [ 0.000s ]
finished. total time: 0.000s
Click to expand...
Click to collapse
That is the default reply for
fastboot oem get_unlock_data
fastboot oem device_info
just with different timings...
Any suggestions?
Bootloader version is aruba-1bfa2a4-2021
SW-Version: motorola/aruba_reteu/aruba:11/RON31.266-20/63893
kind regards
Sven
you are in the fastbootd mode .. the correct mode would be in the bootloader mode (adb reboot bootloader) ..
unfortunately it still does not work - the relevant command does not seem to work (fastboot oem get_unlock_data) -
motorola via support says it can not be unlocked .. but i certainly dont believe that - the e40 for example can be ..
the reteu firmware might be limited ..