Database Develop

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.

help about my p9

can anyone help me. my p9 stuck on Your Device Has been unlocked and can't be trusted.
cant go in twrp and won't power off only i can do is going in fastboot. but every time flash on fastboot it always failed (remote unknown command)
my phone status when fastboot is PHONE Unlocked FRP Lock. help me pls... thanks and sorry for my bad english

how to re-lock bootloader and unlock sir? and the problem is every time i flash stock recovery in fastboot FAILED (remote: command not allowed)

it always getting FAILED (remote: command not allowed)

Moto X4 (XT1900-1) Unlock Bootloader Issue

I'm new to this all so before giving up I wanted to ask around.
I've went through the steps and got my unlock data, when I enter it. It says that that the bootloader is unlockable. But every where I've read says the XT1900-1 is definitely unlockable but none of them seem to post their methods in doing so. I wanted to see if i'm doing something wrong or if anyone has any information.
I've got USB Debugging turned on as well as OEM unlocking in the Developers options.
The only thing I could think that might be useful info is when i'm trying to get the unlock data in cmd I have to use the command "fastboot oem get_unlock_data" a few times because it gives me error messages each time.
Here is a list of messages right before it gives me the bootloader data and thanks for your time in advance.
"C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem get_unlock_data
...
FAILED (remote: unknown command)
finished. total time: 0.002s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem get_unlock_data
(bootloader) slot-countta: not found
(bootloader) slot-suffi: not found
...
(bootloader) 'get_unlock_datas' is not a supported oem command
(bootloader) See 'fastboot oem help'
FAILED (remote failure)
finished. total time: 0.004s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem get_unlock_data
(bootloader) slot-counttas: not found
(bootloader) slot-suffixe: not found
(bootloader) slot-suffi: not found
...
FAILED (remote: unknown command)
finished. total time: 0.002s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem get_unlock_data
(bootloader) slot-counttas: not found
...
(bootloader) Unlock data:"

Follow Motorola's steps: https://support.motorola.com/ca/en/bootloader/unlockyourdeviceb

Forgot to add, ensure you have latest drivers and adb/fastboot packages. Also, try a different USB slot.

gourry30 said:
I'm new to this all so before giving up I wanted to ask around.
I've went through the steps and got my unlock data, when I enter it. It says that that the bootloader is unlockable. But every where I've read says the XT1900-1 is definitely unlockable but none of them seem to post their methods in doing so. I wanted to see if i'm doing something wrong or if anyone has any information.
I've got USB Debugging turned on as well as OEM unlocking in the Developers options.
The only thing I could think that might be useful info is when i'm trying to get the unlock data in cmd I have to use the command "fastboot oem get_unlock_data" a few times because it gives me error messages each time.
Here is a list of messages right before it gives me the bootloader data and thanks for your time in advance.
"C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem get_unlock_data
...
FAILED (remote: unknown command)
finished. total time: 0.002s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem get_unlock_data
(bootloader) slot-countta: not found
(bootloader) slot-suffi: not found
...
(bootloader) 'get_unlock_datas' is not a supported oem command
(bootloader) See 'fastboot oem help'
FAILED (remote failure)
finished. total time: 0.004s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem get_unlock_data
(bootloader) slot-counttas: not found
(bootloader) slot-suffixe: not found
....
Click to expand...
Click to collapse
Yep. Same thing happened to me.
I think its something to do with the usb controller. fwiw i have an Intel eXtensible host controller. I had tried both the 2.0 and 3.0 slots, and another OS. didnt matter, same result. see this link, and this one. No fix. ended up using another computer. worked fine.

Neffy27 said:
Forgot to add, ensure you have latest drivers and adb/fastboot packages. Also, try a different USB slot.
Click to expand...
Click to collapse
Already followed the sites steps, that's the way I found out that it said it was not unlockable.
As well as I got the latest USB drivers for my phone and the abd fastboot program.

mchamb said:
Yep. Same thing happened to me.
I think its something to do with the usb controller. fwiw i have an Intel eXtensible host controller. I had tried both the 2.0 and 3.0 slots, and another OS. didnt matter, same result. see this link, and this one. No fix. ended up using another computer. worked fine.
Click to expand...
Click to collapse
I have a spare laptop I can give it an attempt from that, I'll update you and thanks for the idea.

mchamb said:
Yep. Same thing happened to me.
I think its something to do with the usb controller. fwiw i have an Intel eXtensible host controller. I had tried both the 2.0 and 3.0 slots, and another OS. didnt matter, same result. see this link, and this one. No fix. ended up using another computer. worked fine.
Click to expand...
Click to collapse
Just attempted it on my laptop I only had to enter it once into abd fastboot this time but it still came up with the "Your device does not qualify for bootloader unlocking. I'm starting to think it's not a possibility for the XT1900-1

Try mfastboot instead fastboot.
https://androidfilehost.com/?fid=95916177934532795
Copy mfastboot.exe to fastboot folder and run mfastboot.exe.

gourry30 said:
Just attempted it on my laptop I only had to enter it once into abd fastboot this time but it still came up with the "Your device does not qualify for bootloader unlocking. I'm starting to think it's not a possibility for the XT1900-1
Click to expand...
Click to collapse
Do you have the Amazon version? Project fi (A1) and us retail are unlockable, but I think Amazon is not.
It also sounds like you have USB issues so keep trying different drivers/computers. Older hardware might be better.

gourry30 said:
Just attempted it on my laptop I only had to enter it once into abd fastboot this time but it still came up with the "Your device does not qualify for bootloader unlocking. I'm starting to think it's not a possibility for the XT1900-1
Click to expand...
Click to collapse
I was able to unlock the project fi version of the 1900-1, Sounds like you have the Amazon version. which is not unlockable.

Comby_sk said:
Try mfastboot instead fastboot.
https://androidfilehost.com/?fid=95916177934532795
Copy mfastboot.exe to fastboot folder and run mfastboot.exe.
Click to expand...
Click to collapse
I'll give that a shot, thanks for the info.

mchamb said:
I was able to unlock the project fi version of the 1900-1, Sounds like you have the Amazon version. which is not unlockable.
Click to expand...
Click to collapse
From the research I did on the phone, the XT1900-1 is the Project-fi version and the XT1900-7 is the amazon version.

gourry30 said:
From the research I did on the phone, the XT1900-1 is the Project-fi version and the XT1900-7 is the amazon version.
Click to expand...
Click to collapse
No, XT1900-7 is EMEA version (Europe, Middle East, Africa).

I also just got the androidone moto x4 and am trying to get the one button nav to work but I am stuck unlocking the bootloader. When i type fastboot oem get_unlock_data it returns one line that looks like this INFO4c5647006 and it keeps going. It does not return anything like this (bootloader) 0A40040192024205#4C4D3556313230
(bootloader) 30373731363031303332323239#BD00
(bootloader) 8A672BA4746C2CE02328A2AC0C39F95
(bootloader) 1A3E5#1F53280002000000000000000
(bootloader) 0000000
how do i get this?

Again, I haven't done this yet but based on my current phone, you need to use the oem unlocking option under developer options first.
Which, is supposedly messing up another person since they broke their device, ended with a locked bootloader and couldn't boot to the system to flip that switch.
Point in short, be careful and make sure you read all of the instructions first.
Also, if that doesn't work, there are some YouTube videos for the X4 that might help.

I bought a 1900-1 from Amazon (the Amazon Prime version). It is not unlockable. Confirmed that with Motorola and Amazon after not being able to get an unlock code from the Motorola site
I then bought a 1900-1 Android One version from Best Buy. It is unlockable and I've already rooted it.

Cannot Boot into EDL mode on Mi A2

I tried countless methods like using toolkit, adb reboot edl (this just simply reboots the phone), fastboot boot edl (here it says press any key to shutdown) but i cannot boot into edl. MY bootloader is unlocked using both fastboot oem unlock and unlock_critical. How do i do it? on fastboot mi flash says lenght cannot be zero and i cannot convert it to 6x and hence cannot try one custom roms
Any advice is appreciated, thanks

Try to flash on another pc , same thing happened to me

fastboot oem edl

twentyfourinc said:
fastboot oem edl
Click to expand...
Click to collapse
FAILED (remote: Device is already locked!)
finished. total time: 0.000s
I always get this. please help

Sagar Sritighor said:
FAILED (remote: Device is already locked!)
finished. total time: 0.000s
I always get this. please help
Click to expand...
Click to collapse
did you got the solution?

https://youtu.be/i3OU4DOd7aY
Odesláno z mého Mi A2 pomocí Tapatalk

Sagar Sritighor said:
FAILED (remote: Device is already locked!)
finished. total time: 0.000s
I always get this. please help
Click to expand...
Click to collapse
Try unlocking bootloader critical.
fastboot flashing unlock_critical

Here you go...
Here i have solotion for your problem.
first unlock oem 'fastboot oem unlock' then boot twrp using 'fastboot boot' give one space and drag and drop twrp image and click anywhere on cmd window and hit enter.
now copy the twrp in your phone internal storage and go to install option in twrp. select install image. select your recovery file and select recovery ramdisk. now reboot to recovery, install any custom os and reboot it. once booted enable developer option and enable usb debugging. open all in one tool. once the device is detected by the tool press on reboot to edl. now u will be booted to edl mode. now you wont be rebooted autometically.

Stuck at huawei logo, only fastboot&rescue mode and battery draining!?

Hi!
Sorry for my English at the beggining!
After a successful downgrade (camera problem) and an attempt to return to the new android version through dload, the phone did not start.
Stops on the huawei logo, does not go to bootloader at all, and what is worse, the phone does not go off because it is constantly trying to start itself and because of this the battery is discharged and I can not do anything. Anyone have any ideas?
Only fastboot is working but nothings works there and photo is in ink below how it looks.
Plz help!
imgur.com/xeAsELp

wysoczanin said:
Hi!
Sorry for my English at the beggining!
After a successful downgrade (camera problem) and an attempt to return to the new android version through dload, the phone did not start.
Stops on the huawei logo, does not go to bootloader at all, and what is worse, the phone does not go off because it is constantly trying to start itself and because of this the battery is discharged and I can not do anything. Anyone have any ideas?
Only fastboot is working but nothings works there and photo is in ink below how it looks.
Plz help!
imgur.com/xeAsELp
Click to expand...
Click to collapse
You rolled back to MM - actually, what was your stock firmware and to which (c900, by DLOAD ?) did you roll-back?
As per Fastboot screen, rolling-back (as usual) locked FRP and Bootloader, but still try to execute commands (what they return for status?) :
Code:
fastboot oem get-bootinfo
PAUSE
fastboot oem get-product-model
PAUSE
fastboot oem get-build-number
PAUSE
fastboot oem oeminforead-SYSTEM_VERSION
PAUSE
fastboot getvar vendorcountry
Your Fastboot photo says to connect to HiSuite - I don't know could you (without booting to system), did you try if it maybe offers you restoring the firmware

Hi! Thx for answering!
Below are the commands answear!
It was the newest 7.0 but my bro had problem with camera and tried to rollback to MM. He usesd DLOAD method.
PS C:\Users\Lukasz\Desktop\Marcinek\adb\platform-tools> adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
PS C:\Users\Lukasz\Desktop\Marcinek\adb\platform-tools> fastboot devices
MWS7N17118004613 fastboot
PS C:\Users\Lukasz\Desktop\Marcinek\adb\platform-tools> fastboot oem get-bootinfo
...
(bootloader) locked
OKAY [ 0.007s]
finished. total time: 0.007s
PS C:\Users\Lukasz\Desktop\Marcinek\adb\platform-tools> fastboot oem get-product-model
...
(bootloader) EVA-L09
OKAY [ 0.005s]
finished. total time: 0.006s
PS C:\Users\Lukasz\Desktop\Marcinek\adb\platform-tools> fastboot oem get-build-number
...
(bootloader) :EVA-L09C900B182
OKAY [ 0.004s]
finished. total time: 0.005s
PS C:\Users\Lukasz\Desktop\Marcinek\adb\platform-tools> fastboot oem oeminforead-SYSTEM_VERSION
...
FAILED (remote: Command not allowed)
finished. total time: 0.011s
PS C:\Users\Lukasz\Desktop\Marcinek\adb\platform-tools> fastboot getvar vendorcountry
vendorcountry: dt/pl
finished. total time: 0.005s
PS C:\Users\Lukasz\Desktop\Marcinek\adb\platform-tools>
Im downloading hisuite right now

Issue fixed!
DC Phoenix was needed to do this, and HCU!
So if someone have similar issue, u r gonna need to spend 20 euros to fix it