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
Related
hi
i am trying to unlock the bootlaoder for my new htc m9
after i got the unloch_code, i receive this msg in cmd
target reported max download size of 800000000 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 0.009s]
writing 'unlocktoken'...
(bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X01, enable unlock
FAILED (remote: UnlockToken Verify Fail!!)
finished. total time: 0.038s
please help
what is missing ?
This does not belong in development.
@osamaxosama
In developer options, you have an option called OEM unlocking. This should be checked.
skodann said:
@osamaxosama
In developer options, you have an option called OEM unlocking. This should be checked.
Click to expand...
Click to collapse
i will check it and update this.
skodann said:
@osamaxosama
In developer options, you have an option called OEM unlocking. This should be checked.
Click to expand...
Click to collapse
didn't work
still the same, same msg also
i receive on my phone that download is 100%
and at the botoom of the screen " under flash "
it didn't take me to the bootloader next screen.
Pretty sure the token has to be obtained after OEM unlocking is checked, try a second token.
osamaxosama said:
didn't work
still the same, same msg also
i receive on my phone that download is 100%
and at the botoom of the screen " under flash "
it didn't take me to the bootloader next screen.
Click to expand...
Click to collapse
Activate the OEM unlock, obtain the unlock code.bin after that, make sure that you are using htc_fastboot, not other thing, and (I am not 100% sure, but other members can help) go into download mode, not into bootloader when you flash the unlock code.bin
Tirofog said:
Pretty sure the token has to be obtained after OEM unlocking is checked, try a second token.
Click to expand...
Click to collapse
i guess this might help, i am still using same token , the one i obtained before unlocking oem.
i'll try this
thanks
skodann said:
Activate the OEM unlock, obtain the unlock code.bin after that, make sure that you are using htc_fastboot, not other thing, and (I am not 100% sure, but other members can help) go into download mode, not into bootloader when you flash the unlock code.bin
Click to expand...
Click to collapse
dear
you mean i have to obtain the token when i am at fast boot not download mode ?
flashing is on downlaod mode yeah, but getting the token is from fastboot ?
Tirofog said:
Pretty sure the token has to be obtained after OEM unlocking is checked, try a second token.
Click to expand...
Click to collapse
didn't work, same msg
skodann said:
Activate the OEM unlock, obtain the unlock code.bin after that, make sure that you are using htc_fastboot, not other thing, and (I am not 100% sure, but other members can help) go into download mode, not into bootloader when you flash the unlock code.bin
Click to expand...
Click to collapse
i did this exactly. but to let you know, i couldn't get the token when on fastboot, but after entering download mode, i was able to get the token.
also, i tried to flash the token on fastboot, but didn't flash, only on download mode i was able to get the token and flash it.
on cmd i still get the same msg, but on my htc screen i see this " attached picture " " download 100% "under flash
ad everytime i press the power button, i see another " under flash " msg.
help please
osamaxosama said:
help please
Click to expand...
Click to collapse
What happens if you press the power button.. try adb to reboot recovery/bootloader??
solved
i tried on another pc.
the issue seemed to be from th sdk folder.
i tried 15 seconds installer, i knew it was the problem, because it runs from everywhere, i think it doesn't recognize flash commands or the file destination.
thank you all
Hello
Oneplus 3, France, [email protected] . Update with full OTA. It same with 3.1.2 and 3.2.0 ...
I'm blocked on this :
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.012s
and ...
Flashing Stock Recovery, press any key to start.....
target reported max download size of 536870912 bytes
sending 'recovery' (18665 KB)...
OKAY [ 0.448s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.472s
Done Flashing Stock Recovery, have fun!
Now Boot to Stock Recovery...
downloading 'boot.img'...
Nothing after ...
But i can flash ota via sideload, o don't have local flash ...
You have to go into settings -> developer options (google how to make it visible) and then check "allow oem unlock" That will do the trick
Then you can unlock bootloader via adb, just as you were trying earlier.
Thanks you.
there is no android system of any kind on my phone, and bootloader is locked, as above it does say remote bootloader unlock not allowed, as i cant go in settings and tick the allow oem unlock option is there any other way to unlock bootloader??
op3user123 said:
there is no android system of any kind on my phone, and bootloader is locked, as above it does say remote bootloader unlock not allowed, as i cant go in settings and tick the allow oem unlock option is there any other way to unlock bootloader??
Click to expand...
Click to collapse
Can you get into stock recovery?
Hw4ng3r said:
Can you get into stock recovery?
Click to expand...
Click to collapse
Yes I got in updated my advice drives of Windows and phone is working again.... Thanks anyways....
op3user123 said:
there is no android system of any kind on my phone, and bootloader is locked, as above it does say remote bootloader unlock not allowed, as i cant go in settings and tick the allow oem unlock option is there any other way to unlock bootloader??
Click to expand...
Click to collapse
hallo i got the same problem there is no android system of any kind on my phone (one plus 3), and bootloader is locked. can u tell how u get it done
Yes I got in updated my advice drives of Windows and phone is working again.... Thanks anyways....
When removing TWRP and flashing my phone back to factory images, I received a size issue on the main image. I then manually flashed each .img using fastboot. Lastly, assuming it was good, I was an idiot and locked the bootloader.
Is there any way to recover from this using adb and sideloading? I have the factory recovery image working, locked bootloader but nothing else. Any help would be greatly appreciated
nvrpunk said:
When removing TWRP and flashing my phone back to factory images, I received a size issue on the main image. I then manually flashed each .img using fastboot. Lastly, assuming it was good, I was an idiot and locked the bootloader.
Is there any way to recover from this using adb and sideloading? I have the factory recovery image working, locked bootloader but nothing else. Any help would be greatly appreciated
Click to expand...
Click to collapse
try to enter bootloader via adb reboot bootloader or key combination and issue fastboot oem unlock.
ulxerker said:
try to enter bootloader via adb reboot bootloader or key combination and issue fastboot oem unlock.
Click to expand...
Click to collapse
This does not work.
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.016s
nvrpunk said:
This does not work.
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.016s
Click to expand...
Click to collapse
try it with nexus root toolkit
or
download latest OTA image and adb sideload OTA.zip in recovery.
ulxerker said:
try it with nexus root toolkit
or
download latest OTA image and adb sideload OTA.zip in recovery.
Click to expand...
Click to collapse
Thanks, I am going to try the sideload of the OTA.zip And see if that works.
nvrpunk said:
This does not work.
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.016s
Click to expand...
Click to collapse
I'm curious if you did anything other than what you listed, because Allow OEM unlocking that was set from Developer Options should still be one given what your described actions.
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.