So I wanted to flash a new firmware (from nougat to oreo xt1789-06) but i didnt even get to that part.
I mistakenly locked the oem and then couldnt continue with the flash, tried to boot and i already knew it would be hardbricked now.
I tried unlocking it again, got the unlock key and everything but somehow it just wont unlock the bootloader.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock OTJL5PQU2J22WRF7EP56
...
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.014s]
finished. total time: 0.015s
C:\Program Files (x86)\Minimal ADB and Fastboot>
is what im getting
I hope someone knows how i can unlock the oem again
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 bought a WWE HTC 10 to use in the states... I used sunshine and have s-off locked status, I changed the cid and mid to the unlocked us numbers and did a conversion using the htc ruu.exe, I have a red warning every time i start the phone about development purposes only etc... I figure this must have to do with the s-off so i want to set it back to on as though i just bought a usa unlocked model!
im in download mode
I tried the good old
Code:
fastboot oem writesecureflag 3
and i got this output
Code:
...
(bootloader) HTC KEY CARD VERSION: 7
(bootloader) VERIFY_BY_PROJECT_SIGN_KEY_FAIL hosd (-9)
FAILED (remote: Partition verify fail -9)
finished. total time: 1.024s
what am i doing wrong?
THC Butterz said:
I bought a WWE HTC 10 to use in the states... I used sunshine and have s-off locked status, I changed the cid and mid to the unlocked us numbers and did a conversion using the htc ruu.exe, I have a red warning every time i start the phone about development purposes only etc... I figure this must have to do with the s-off so i want to set it back to on as though i just bought a usa unlocked model!
im in download mode
I tried the good old
Code:
fastboot oem writesecureflag 3
and i got this output
Code:
...
(bootloader) HTC KEY CARD VERSION: 7
(bootloader) VERIFY_BY_PROJECT_SIGN_KEY_FAIL hosd (-9)
FAILED (remote: Partition verify fail -9)
finished. total time: 1.024s
what am i doing wrong?
Click to expand...
Click to collapse
Go to bootloader mode?
Sent from my SM-G935T using Tapatalk
didnt work in bootloader mode at all
Code:
...
FAILED (remote: unknown command)
finished. total time: 0.052s
didnt work in uru mode either
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem rebootRUU
...
OKAY [ 0.001s]
finished. total time: 0.002s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem writesecureflag 3
...
(bootloader) HTC KEY CARD VERSION: 7
(bootloader) VERIFY_BY_PROJECT_SIGN_KEY_FAIL hosd (-9)
FAILED (remote: Partition verify fail -9)
finished. total time: 1.042s
THC Butterz said:
didnt work in bootloader mode at all
Code:
...
FAILED (remote: unknown command)
finished. total time: 0.052s
didnt work in uru mode either
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem rebootRUU
...
OKAY [ 0.001s]
finished. total time: 0.002s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem writesecureflag 3
...
(bootloader) HTC KEY CARD VERSION: 7
(bootloader) VERIFY_BY_PROJECT_SIGN_KEY_FAIL hosd (-9)
FAILED (remote: Partition verify fail -9)
finished. total time: 1.042s
Click to expand...
Click to collapse
Actually if you still have the red warning then the Ruu likely didn't fully flash. You shouldn't have that message if it successfully flashes.
Sent from my SM-G935T using Tapatalk
dottat said:
Actually if you still have the red warning then the Ruu likely didn't fully flash. You shouldn't have that message if it successfully flashes.
Sent from my SM-G935T using Tapatalk
Click to expand...
Click to collapse
after speaking with jcase figgured out that because the ruu didnt mach the one the phone shipped with im sol for turning s-off back to s-on
THC Butterz said:
after speaking with jcase figgured out that because the ruu didnt mach the one the phone shipped with im sol for turning s-off back to s-on
Click to expand...
Click to collapse
Yeah I still believe that a fully flashed matching Ruu will clear that flag. Can you try flashing again and see if the dev flag clears?
Sent from my SM-G935T using Tapatalk
hi all ,
i have a zenfone 2 laser exactly ze550kl , i don't know how was done on it .
everything i done it appear only fastboot mode...fastboot device find the device and adb device not find it
I've tryied a lot of guide but nothing..so i want to start again
If someone can and want follow me to resolve please answer
(fastboot getvar all is empty)
sorry for my bad english , i'm italian :angel:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
G1AZCY06E666 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem device-info
...
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.000s]
finished. total time: 0.000s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
all:
finished. total time: 0.000s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.859s]
booting...
FAILED (remote: unlock device to use this command)
finished. total time: 0.859s
Hi All.
I just bought the leeco pro 3 and want to unlock the bootloader. I followed the steps outlined in "X727 (US Model) Persistent bootloader unlock from 5.8.019s". I turned on USB debugging, permanently added USB device, and turned on the "allow oem unlocking option". Then, i rebooted to fast boot and tried the following commands and received an error.
Code:
:~$[B] fastboot oem device-info[/B]
...
(bootloader) Device product name: [le_zl1_oversea]
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Serial console enabled: false
(bootloader) Serial hw output enabled: false
(bootloader) Display panel:
OKAY [ 0.083s]
finished. total time: 0.083s
:~$ [B]fastboot oem unlock-go[/B]
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.008s
:~$ [B]fastboot oem unlock[/B]
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.004s
[email protected]:~$ fastboot reboot
rebooting...
finished. total time: 0.007s
My phone came with 5.8.020S (I think) and I tried the above steps with that version. Then i updated to 5.8.021S and tried again and received the same issue. I checked for more updates but none were found.
I am sure this issue has been solved somewhere but I just want to make sure I do not brick this device. Please help.
Developer Options ---> usb debug ---> open ..
Developer Options ---> Oem unlock ---> open ..
Have you enabled them?
lazye53 said:
Developer Options ---> usb debug ---> open ..
Developer Options ---> Oem unlock ---> open ..
Have you enabled them?
Click to expand...
Click to collapse
Thanks for the reply.. Yes. Both of those options are on. I have tried multiple times to turn them off and on and redo the unlock at fast boot, but i get the same error
sagarc88 said:
Hi All.
I just bought the leeco pro 3 and want to unlock the bootloader. I followed the steps outlined in "X727 (US Model) Persistent bootloader unlock from 5.8.019s". I turned on USB debugging, permanently added USB device, and turned on the "allow oem unlocking option". Then, i rebooted to fast boot and tried the following commands and received an error.
Code:
:~$[B] fastboot oem device-info[/B]
...
(bootloader) Device product name: [le_zl1_oversea]
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Serial console enabled: false
(bootloader) Serial hw output enabled: false
(bootloader) Display panel:
OKAY [ 0.083s]
finished. total time: 0.083s
:~$ [B]fastboot oem unlock-go[/B]
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.008s
:~$ [B]fastboot oem unlock[/B]
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.004s
[email protected]:~$ fastboot reboot
rebooting...
finished. total time: 0.007s
My phone came with 5.8.020S (I think) and I tried the above steps with that version. Then i updated to 5.8.021S and tried again and received the same issue. I checked for more updates but none were found.
I am sure this issue has been solved somewhere but I just want to make sure I do not brick this device. Please help.
Click to expand...
Click to collapse
For 5.8.021S, go to page 26 ....
sagarc88 said:
Thanks for the reply.. Yes. Both of those options are on. I have tried multiple times to turn them off and on and redo the unlock at fast boot, but i get the same error
Click to expand...
Click to collapse
I had this issue also this I solved it.
Undo the OEM allow to unlock reboot then enable OEM to unlock bootloader.
Still had the problem.
I ended up flash the bootloader then then ran the bootloader unlock commander and it worked.
Sent from my LEX727 using xda premium
mchlbenner said:
I had this issue also this I solved it.
Undo the OEM allow to unlock reboot then enable OEM to unlock bootloader.
Still had the problem.
I ended up flash the bootloader then then ran the bootloader unlock commander and it worked.
Sent from my LEX727 using xda premium
Click to expand...
Click to collapse
You need to flash 2 files via adb first, then run the unlock command.
I did it successfully for 021s
Sent from my LEX727 using Tapatalk
kukuteku said:
For 5.8.021S, go to page 26 ....
Click to expand...
Click to collapse
This worked perfectly!! Thank you very much.
Flashing Critical Locked
I'm just a dabbler in this stuff, but I think I understand everything required to get LineageOS on my LEX727. The problem is, in the process of learning, I think I locked the ability to flash aboot, and now I can't get the twrp recovery onto my phone. Does anyone have any ideas or know what to do? If I can do anything from here?
Thanks for any help!
MAHawbs said:
I'm just a dabbler in this stuff, but I think I understand everything required to get LineageOS on my LEX727. The problem is, in the process of learning, I think I locked the ability to flash aboot, and now I can't get the twrp recovery onto my phone. Does anyone have any ideas or know what to do? If I can do anything from here?
Thanks for any help!
Click to expand...
Click to collapse
What did locked ability flash abootd it d relock bootloader.
What did you ?
Sent from my SM-A730F using xda premium
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.