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
Related
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.
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:
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.
Hello i tried to unlock the Bootloader but i get an error every Time
C:\Users\kilia>adb reboot bootloader
C:\Users\kilia>cd C:\adb
C:\adb>fastboot flash unlock unlock.bin
sending 'unlock' (1 KB)...
FAILED (remote: unknown command)
finished. total time: -0.000s
Kilian122 said:
Hello i tried to unlock the Bootloader but i get an error every Time
C:\Users\kilia>adb reboot bootloader
C:\Users\kilia>cd C:\adb
C:\adb>fastboot flash unlock unlock.bin
sending 'unlock' (1 KB)...
FAILED (remote: unknown command)
finished. total time: -0.000s
Click to expand...
Click to collapse
What model are you using as of right now only the European model and TIM Mobile (Italian Carrier) can be officially unlocked other than that you're SOL
Joe199799 said:
What model are you using as of right now only the European model and TIM Mobile (Italian Carrier) can be officially unlocked other than that you're SOL
Click to expand...
Click to collapse
I am using the LG G7: LMG710EM and i have my offical unlock.bin but its not working :/
Kilian122 said:
I am using the LG G7: LMG710EM and i have my offical unlock.bin but its not working :/
Click to expand...
Click to collapse
Interesting, I'm sorry I've helped all i can I have a G710TM I don't have an unlockable bootloader, I suggest going over to the root instructions thread and posting there you might have better luck or wait it out. I'm sorry I couldn't help you
Joe199799 said:
Interesting, I'm sorry I've helped all i can I have a G710TM I don't have an unlockable bootloader, I suggest going over to the root instructions thread and posting there you might have better luck or wait it out. I'm sorry I couldn't help you
Click to expand...
Click to collapse
at least you tried thank you
Kilian122 said:
at least you tried thank you
Click to expand...
Click to collapse
No problem, anytime
Are u connected?
Have u enabeld oem unlock in settings and activated usb debuging
Run command :Adb devices
Yes i have enabled the 2 things and when i tipe that in it shows me a number
Kilian122 said:
Yes i have enabled the 2 things and when i tipe that in it shows me a number
Click to expand...
Click to collapse
It should be "fastboot oem unlcok unlock.bin"
LameMonster82 said:
It should be "fastboot oem unlcok unlock.bin"
Click to expand...
Click to collapse
you mean "fastboot oem unlock unlock.bin"
yes and thats not working
Did u follow the guide on lg page when u register to obtain your unlock file? Did u enter correvt ime and everything?
maydayind said:
Did u follow the guide on lg page when u register to obtain your unlock file? Did u enter correvt ime and everything?
Click to expand...
Click to collapse
Yes i did and i got the file via email
Kilian122 said:
you mean "fastboot oem unlock unlock.bin"
yes and thats not working
Click to expand...
Click to collapse
What does it say?
LameMonster82 said:
What does it say?
Click to expand...
Click to collapse
C:\adb>fastboot flash unlock unlock.bin
sending 'unlock' (1 KB)...
FAILED (remote: unknown command)
finished. total time: -0.000s
Kilian122 said:
C:\adb>fastboot flash unlock unlock.bin
sending 'unlock' (1 KB)...
FAILED (remote: unknown command)
finished. total time: -0.000s
Click to expand...
Click to collapse
From your post you are running "fastboot flash unlock unlock.bin", while the correct command, as others already mentioned, is "fastboot oem unlock unlock.bin".
dbolivar said:
From your post you are running "fastboot flash unlock unlock.bin", while the correct command, as others already mentioned, is "fastboot oem unlock unlock.bin".
Click to expand...
Click to collapse
Thats still not Working :/
C:\adb>fastboot oem unlock unlock.bin
...
FAILED (remote: unknown command)
finished. total time: 0.000s
dbolivar said:
From your post you are running "fastboot flash unlock unlock.bin", while the correct command, as others already mentioned, is "fastboot oem unlock unlock.bin".
Click to expand...
Click to collapse
And the LG Developer Site says "fastboot flash unlock unlock.bin"
From what i can se your phone isnt unockebl.
Or u Dident enable oem unlock in developer settings
maydayind said:
From what i can se your phone isnt unockebl.
Or u Dident enable oem unlock in developer settings
Click to expand...
Click to collapse
Yes i enabled it and it is unlockable
That's weird. What I'd suggest is for you to try a different (newer?) version of fastboot. Try downloading straight from Google:
https://developer.android.com/studio/releases/platform-tools
I have enabled oem unlock and usb debug from settings. I am using vivo fastboot tool. And after entering fastboot menu, I tried the code fastboot bbk unlock_vivo.
C:\Users\dell\Desktop\vivo_fastboot_for_windows>fastboot devices
MNFM7PSSGM75SKBY fastboot
C:\Users\dell\Desktop\vivo_fastboot_for_windows>fastboot bbk unlock_vivo
...
FAILED (remote: unclock fail.)
finished. total time: 0.004s
Please someone help me. I tried various solutions from the internet but could'nt find one.
How to unblock bootloader unlock please.
Vivo y12 bootloader unlock kase kare
How to unblock bootloader vivo y12 video make please xda deploper
bickey.jaiswal said:
I have enabled oem unlock and usb debug from settings. I am using vivo fastboot tool. And after entering fastboot menu, I tried the code fastboot bbk unlock_vivo.
C:\Users\dell\Desktop\vivo_fastboot_for_windows>fastboot devices
MNFM7PSSGM75SKBY fastboot
C:\Users\dell\Desktop\vivo_fastboot_for_windows>fastboot bbk unlock_vivo
...
FAILED (remote: unclock fail.)
finished. total time: 0.004s
Please someone help me. I tried various solutions from the internet but could'nt find one.
Click to expand...
Click to collapse
Same goes to my vivo y11