Database Develop

Stuck In Fastboot

I don't have a backup, I installed CM11 and then locked the bootloader but now it won't boot and is stuck in the Fastboot menu. When I type "fastboot oem unlock" it says command error!!

lewiskay13 said:
I don't have a backup, I installed CM11 and then locked the bootloader but now it won't boot and is stuck in the Fastboot menu. When I type "fastboot oem unlock" it says command error!!
Click to expand...
Click to collapse
It's because you are entering the wrong command. "fastboot oem unlock" is used on nexus devices. The command you will have to use to unlock is this, keeping the unlock token you got from HTCDev in the same directory as the fastboot binary
Code:
fastboot flash unlock token Unlock_code.bin

lewiskay13 said:
I don't have a backup, I installed CM11 and then locked the bootloader but now it won't boot and is stuck in the Fastboot menu. When I type "fastboot oem unlock" it says command error!!
Click to expand...
Click to collapse
you cannot lock bootloader after installing custom system as it wont detect the system.

Flashing bootloader unlock image gets stuck on waiting for device.

My device is plugged in with the stock cable and it is booted into bootloader via adb reload bootloader.
I've tried both fastboot -i 0x2b4c flash unlock unlock_bootloader.img and fastboot -i 0x2b4c flash unlock unlock_bootloader.img, both result in stuck on waiting.

SachK2 said:
My device is plugged in with the stock cable and it is booted into bootloader via adb reload bootloader.
I've tried both fastboot -i 0x2b4c flash unlock unlock_bootloader.img and fastboot -i 0x2b4c flash unlock unlock_bootloader.img, both result in stuck on waiting.
Click to expand...
Click to collapse
I had a similar thing happen to me when I did my unlocking, fastboot doesn't recognise your phone, what happens if you send "fastboot -i 0x2b4c devices"?
Eventually I did figure it out but I can't remember the solution, but one thing that did work all the time was mauronofrio's multi-tool. https://forum.xda-developers.com/zu...ol-tool-one-driversunlocktwrpfactory-t3432782
Have a go, see if that works.

SachK2 said:
My device is plugged in with the stock cable and it is booted into bootloader via adb reload bootloader.
I've tried both fastboot -i 0x2b4c flash unlock unlock_bootloader.img and fastboot -i 0x2b4c flash unlock unlock_bootloader.img, both result in stuck on waiting.
Click to expand...
Click to collapse
Hi, SachK2.
When I faced the same issue, installing the custom USB drivers that are usually attached to the bootloader unlock topic did the trick to me.

I tried the multi-tool but it gets stuck and crashes on the command window. I cant find the custom drivers download.

SachK2 said:
I tried the multi-tool but it gets stuck and crashes on the command window. I cant find the custom drivers download.
Click to expand...
Click to collapse
posting the links to another forum is disallowed here, though if I were in your shoes, I'd go on 4pda, search there zuk z2 pro topic and download the drivers there - wasn't able to find those drivers within xda yet
I'll also PM you the direct link so that you can check [the registration might be needed to be able to view and download the files]

TWRP Fastboot Command not allowed (P10)

Hi!
I'm trying to install TWRP on my P10. I've unlocked bootloader on Huawei website.
Whenever I'm typing in fastboot "flash recovery twrp.img" it goes through and everything says OK
But when i try to "fastboot boot twrp.img" I get FAILED (remote: command not allowed)
"fastboot oem device-info" gives me the same error too and "fastboot oem unlock" gives me already fastboot unlocked

What do you thing "fastboot boot twrp.img" should do? This command isn't allowed because it does not exist.
If you want to boot into your flashed TWRP recovery, you have to enter "fastboot reboot" and press volume up while booting - the USB cable has to be disconnected.
Instead of "fastboot oem device-info" try "fastboot Gevtvar unlocked".

or use adb when the phone is running.
"adb reboot recovery"
you can't go direct from fastboot to recovery simply by a command

Yeah, the command was wrong, sorry xD
Anyway I thinks it's fixed now and I'm able to boot manually to recovery from phone now!

jejeje i was coming here to tell you about wrong command

I have the same problem with FAILED (remote: command not allowed). When I try to install or flash anything I see the info about FAILED (remote: command not allowed). I have FRP locked and I can't enable OEM developing option (it is inactive). I can't relock bootloader, can't instal TWRP, I have only simply erocevery where I can't wipe - only reboot and shutdown device.
I tried do update via dload, hwota - all with defeat
In ADB and Fastboot I can see my device connected.
Does anyone have any idea?

do you have instaled driver for P10, does computer recognice device like P10 ?

DiMeteo24 said:
I have the same problem with FAILED (remote: command not allowed). When I try to install or flash anything I see the info about FAILED (remote: command not allowed). I have FRP locked and I can't enable OEM developing option (it is inactive). I can't relock bootloader, can't instal TWRP, I have only simply erocevery where I can't wipe - only reboot and shutdown device.
I tried do update via dload, hwota - all with defeat
In ADB and Fastboot I can see my device connected.
Does anyone have any idea?
Click to expand...
Click to collapse
Any news? My p10+ it's in the same case

same problem im already unlock but the twr not install what is propper command

Hey guys, for all of you with "command not allowed" problem, you have to check OEM unlock setting on developer options but if you have a greyed out button, you need to flash again your stock room with a tool like dc-phoenix unlocker and bypass frp lock (on YouTube you will find tons of videos regarding this matter). Also, you can check if your Fastboot is protected (frp locked) on Fastboot screen...

There you go---> https://forum.xda-developers.com/hu...ution-bl-unlockedfrp-locked-fastboot-t3684302
PS READ the post to the END!! don't make mistakes it's really easy and fast. It works!

Hi guys.
I know this thread is pretty old but I'm getting the exact same problem as the OP except on my P20 Pro: I can flash a recovery but not boot one from fastboot.
The biggest difference is that my bootloader is unlocked and I have FRP Unlock, so according to every post I've seen it SHOULD be working.
My fastboot log:
PS C:\adb> fastboot devices
LCL0218415002142 fastboot
PS C:\adb> fastboot boot twrp-3.2.1-0-charlotte.img
downloading 'boot.img'...
OKAY [ 0.187s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.187s

Armand Bernard said:
Hi guys.
I know this thread is pretty old but I'm getting the exact same problem as the OP except on my P20 Pro: I can flash a recovery but not boot one from fastboot.
The biggest difference is that my bootloader is unlocked and I have FRP Unlock, so according to every post I've seen it SHOULD be working.
My fastboot log:
PS C:\adb> fastboot devices
LCL0218415002142 fastboot
PS C:\adb> fastboot boot twrp-3.2.1-0-charlotte.img
downloading 'boot.img'...
OKAY [ 0.187s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.187s
Click to expand...
Click to collapse
Have you try this command fasboot reboot recovery_ramdisk?

I get:
PS C:\adb> fastboot reboot recovery_ramdisk
fastboot: usage: unknown reboot target recovery_ramdisk
with "fastboot boot recovery_ramdisk" I get
error: cannot load 'recovery_ramdisk': No such file or directory

I sorted out my problem from a different angle so I no longer need to boot to TWRP from fastboot. Thanks for your help!

Question
Armand Bernard said:
I sorted out my problem from a different angle so I no longer need to boot to TWRP from fastboot. Thanks for your help!
Click to expand...
Click to collapse
Could you please tell me how did u solve this problem. thx

darkdante13 said:
Could you please tell me how did u solve this problem. thx
Click to expand...
Click to collapse
This was quite some time back so I don't remember all that well, but I think I just used the built in Huawei recovery, erecovery, to restore my whole phone and then I was able to reinstall my custom recovery and boot to it normally. I can't guarantee this as I don't remember the whole context of this. Using erecovery I didn't lose my locally stored files, only my apps and app data. Hope this helps.

Can't access full fastboot commands

Hi all, I was wondering if you know, after bootloader unlocking, why I can't access full fastboot commands as the one to remotely boot a recovery. "fastboot boot recovery.img" says "Failed: Command not allowed" and also does "fastboot oem ?" to list oem commands. OEM unlocking is permanently On , on the Dev Options and as I said before, bootloader is unlocked. But, I still can, I guess, flash boot, recovery etc. but I don't want to do it right now. I can tell it because so happened on my previous Huawei Phone and what's happening now on my P10 is the same thing. Thanks in advance.

Up, my ROM is VTR-L09C55B130 stock and I'm on Android 7.0

Unlock OEM via ADB

Hi, so my Xiaomi MI A2 is kinda not working and I think that wiping cache partition might help but I can't access the recovery so I wanted to install TWRP. The thing is I have the boatloader locked, I have the USB depuration activated but not the OEM, so how can I unlock boatload or unlock OEM via fastboot?
Thanks

_08_ said:
Hi, so my Xiaomi MI A2 is kinda not working and I think that wiping cache partition might help but I can't access the recovery so I wanted to install TWRP. The thing is I have the boatloader locked, I have the USB depuration activated but not the OEM, so how can I unlock boatload or unlock OEM via fastboot?
Thanks
Click to expand...
Click to collapse
run "fastboot oem unlock" and "fastboot oem unlock_critical" see if its execute without error , then run " fastboot oem device-info" , let us know what the result.

shihabrumel said:
run "fastboot oem unlock" and "fastboot oem unlock_critical" see if its execute without error , then run " fastboot oem device-info" , let us know what the result.
Click to expand...
Click to collapse
It won't let me. It says:
my command: fastboot oem unlock System: FAILED (remote "flashing unlock is not allowed")
Fastboot: error: command failed.
Same with the critical. I also had an error trying another command, it said, not allowed in lock mode.
Actually, I'm trying other commands and it's the same error with all comands.

My Mi A2 was not booting
My mi a2 last updated to 19/04/05 pie version, then i install the Google camera using below steps..
1. Turn on debugging mode/oem & turn off the phone
2. Then power button+vol dwn Fastboot mode & connect to pc (Pc already have the adb)
3. In pc>adb>folder>Cmd> type "fastboot oem unlock"
4. Then factory reset the phone and reboot again to fastboot mode
5. Then boot the patched image for phone
6. Then install the magisk and gcam work perfectly.
Simply i used these methods
the***********.com/enable-camera2-api-xiaomi-mi-a2-lite-guide/
But then I tried to relock the bootloader, using below commands on cmd
1. "adb reboot-bootloader"
2."fastboot oem lock"
I tried these 2 commands 4 or 5 times
But phone is not power on with locked bootloader. Then I unlock again oem and try again,, But not working,
Then i unlock bootloader again and try these commands to lock it again,
1. "adb reboot-bootloader"
2."fastboot flashing lock"
3. "fastboot oem lock"
Unfortunately it is not work, also i can't give command "fastboot oem unlock", also i can't turn on my phone, Please help me... I want to restore my phone to working mode... Please help me, Quick, urgent :crying::crying::crying::crying: