Just got Nexus 4 and trying to unlock the bootloader.
Follow the instructions and Fastboot detetcts the Nexus ok using command "fastboot devices"
But when I then type "fastboot oem unlock" I get "command write failed unknown error"
Any ideas please?
robolots said:
Just got Nexus 4 and trying to unlock the bootloader.
Follow the instructions and Fastboot detetcts the Nexus ok using command "fastboot devices"
But when I then type "fastboot oem unlock" I get "command write failed unknown error"
Any ideas please?
Click to expand...
Click to collapse
Off the top of my head: try another port, another cable reinstall drivers.
Any ideas what causes bootloader (fastboot oem get-bootinfo) to always give "unlocked" status and then behaves like locked on some commands? Even when I relock bootloader, status after that is still "unlocked."
And then on some commands, like "fastboot continue" I get "command not allowed" error.
Any ideas what could cause that?
Huawei is unresponsive, but before that, OEM unlock and USB debugging were turned on.
Hey guys! I just got and HTC U Ultra, and I'm trying to unlock the bootloader the same way I always have with any HTC. fastboot oem get_identifier_token. I'm using a command prompt from a Linux build OS, but the command keeps failing. FAILED (remote: unknown command). Any ideas?
EDIT: Never mind. There was a glitch that I worked out. Thanks anyways!
Hello there,this probably has been questioned a lot of times but I will ask it anyway.
I'm new to this so I researched a bit about the subject,already downloadead the files and everything is pretty much ready. The only thing that I can't do right now is the bootloader part,basically I put this code on the prompt "fastboot oem get_unlock_data" and all I get is this message "FAILED (remote: unknown command)".
So what should I do ? Is there an alternate command that I can try ?
My phone i a MediaTek and it's model is XT1763
I don't have much else to say so thank you for reading.
Are you in fastboot (bootloader mode) when you issue the command? Here's the procedure I followed.
Thanks that guide worked,apparently I didn't need the code from lenovo and could already unlock it
question:
today I locked the booloader,but my PH-1 can't boot,it siad"Your devices is corrput,It can't be trusted and will not boot."
I use adb cant find devices.But it can use"fastboot decives".
"fastboot -w"is failed,the remote is "remote: Erase is not allowed in Lock State."
"fastboot flash boot.img" or "fastboot flash recovery twrp.img" also failed. the remote is "remote: Erase is not allowed in Lock State"
can anyone tell me how to get devices?
[IMG="https://drive.google.com/open?id=1cAIFNdksNV9-yUEQQBzwz7S1uDxgNhGp"]
[email protected] said:
question:
today I locked the booloader,but my PH-1 can't boot,it siad"Your devices is corrput,It can't be trusted and will not boot."
I use adb cant find devices.But it can use"fastboot decives".
"fastboot -w"is failed,the remote is "remote: Erase is not allowed in Lock State."
"fastboot flash boot.img" or "fastboot flash recovery twrp.img" also failed. the remote is "remote: Erase is not allowed in Lock State"
can anyone tell me how to get devices?
[IMG="https://drive.google.com/open?id=1cAIFNdksNV9-yUEQQBzwz7S1uDxgNhGp"]
Click to expand...
Click to collapse
Can you boot to recovery and factory reset?
ktmom said:
Can you boot to recovery and factory reset?
Click to expand...
Click to collapse
no,the phone can't do this
[email protected] said:
no,the phone can't do this
Click to expand...
Click to collapse
Have you tried unlocking again in fastboot?
ktmom said:
Have you tried unlocking again in fastboot?
Click to expand...
Click to collapse
Yes,but it failed. remote is Flashing Unlock is not allowed .
[email protected] said:
Yes,but it failed. remote is Flashing Unlock is not allowed .
Click to expand...
Click to collapse
It sounds like the OEM unlock was turned off in developer settings.
If you can't get to recovery and you can't boot to be able to unlock again, you're stuck [emoji17]
This is a warning to others. Don't lock bootloader. You can leave phone unrooted, no TWRP, and bootloader unlocked. It has the annoying warning splash screen with every reboot, but a lot safer than locking bootloader
HueyT said:
This is a warning to others. Don't lock bootloader. You can leave phone unrooted, no TWRP, and bootloader unlocked. It has the annoying warning splash screen with every reboot, but a lot safer than locking bootloader
Click to expand...
Click to collapse
Exactly. This has been highlighted many times - relocking the BL after unlocking it once is a bad idea...
Shoot me a msg I May Be of help
question:
today I locked the booloader,but my PH-1 can't boot,it siad"Your devices is corrput,It can't be trusted and will not boot."
I use adb cant find devices.But it can use"fastboot decives".
"fastboot -w"is failed,the remote is "remote: Erase is not allowed in Lock State."
"fastboot flash boot.img" or "fastboot flash recovery twrp.img" also failed. the remote is "remote: Erase is not allowed in Lock State"
can anyone tell me how to get devices?
Click to expand...
Click to collapse
For "Your devices is corrput,It can't be trusted and will not boot." Press power button?
Try
fastboot oem disable_dm_verity
Then
If able boot into recovery (hard reset button combination)
adb reboot "dm-verity enforcing"
Worth a shot ...
Aimless Rambler said:
For "Your devices is corrput,It can't be trusted and will not boot." Press power button?
Try
fastboot oem disable_dm_verity
Then
If able boot into recovery (hard reset button combination)
adb reboot "dm-verity enforcing"
Worth a shot ...
Click to expand...
Click to collapse
also failed……