Hi so I've been tinkering with my Mediapad M3 to get 5ghz wifi to work on it. I got it to work but then I needed to unroot my system.
I used this guide https://forum.xda-developers.com/honor-6x/how-to/how-to-to-stock-emui-5-0-flashing-twrp-t3679985 and now I'm stuck at the part where it says to flash the Vendor.img using the install tool in TWRP.
My problem is that there is no Vendor partition in TWRP to install the vendor image to. I'm using this version of twrp: twrp_BTV-W09_5_greatslon.img that I got from this forum: https://forum.xda-developers.com/mediapad-m3/development/twrp-greatslon-mod-t3489232 It's the only version of twrp that I've found that works on my device.
All the other instructions work but I think without the vendor image the rest of the system won't work properly.
I've also tried to fastboot flash the vendor image and I get the following error message:
Writing 'vendor' FAILED (remote: 'Command not allowed') fastboot: error: Command failed
This is driving me nuts so any help would be greatly appreciated, thank you in advance.
Related
Hello,
I'll start off by apologizing for being a noob. I tried to follow the instructions found here but somehow I got stuck in a state where my NP won't boot up. It is stuck at the Google black screen with an unlock icon. I tried to flash the 2.1 Lollirock rom and now i'm stuck in this state.
I have the NP plugged in and can get to the bootloader screen but I can't seem to figure out how to fix this. I downloaded the boot.img and system.img files from the Lollirock XDA page.
Steps I did:
At the bootloader page -
1) fastboot oem unlock (twice)
2) the bootloader screen then said it was unlocked
3) flashboot boot boot.img
4) flashboot flash system system.img
5) flashboot -w
Everything was successful with no errors so I put enabled Normal Boot in the bootloader and it just sits at the Google screen for about a minute and loops.
I tried to download fugu-lmy48n-factory-3b9d8638.tgz from the nexus stock image page and tried flashboot flash system fugu-lmy48n-factory-3b9d8638.tgz and got the error:
< waiting for device >
target reported max download size of 536870912 bytes
erasing 'system'...
OKAY [ 1.223s]
sending 'system' (457721 KB)...
OKAY [ 16.014s]
writing 'system'...
FAILED (remote: flash_cmds error!
)
finished. total time: 18.417s
I unzipped the TGZ file and tried with the TAR file and got the same error.
Then I flashed CM Recovery and that worked and I can get into CM Recovery thinking I can just update with the CM12.1 rom. The problem is that I don't have the zip on the device's sd card so I had to push from ADB by doing -
ADB sideload cm-12.1-20150520-UNOFFICIAL-fugu.zip
and it starts and goes for about 46% and stops with CM Recovery stating:
E: Failed to verify whole-file signature
E: signature verification failed
Installation aborted.
I googled this and people said to turn off signature verification since most roms are signed but I can't find any instructions on how to do that....
I also found an OTA zip of 6.0 and when updating from CM via ADB sideload, it gives me the error:
E: Error in /sideload/package.zip
(Status 7)
So that's where I'm at....not sure what to do next so any help you guys can provide would GREATLY be apprciated. Thanks!!!
Disregard, I think I got it figured out. I guess I was in stock recover and not in CM Recovery. Flashed CM Recovery again and I was able to flash CM12.1. RIght now it's sitting at the loading screen with the happy blue android face.
Hi @all,
i just messed something up while testing several custom roms for my Zenfone5 so actually i cant write system neither by "sideload" nor by "fastboot flash system". i always get the a mistake like:
Code:
FAILED (remote: flash_cmds error!)
Actually i cant find a mistake by myself. Is it located in my PC or in my phone? i already searched for an errorlist for fastboot but that doesn't get me any results...
and as we say in germany:
Vielen Dank im Vorraus!
Vere'Athor
You're trying to flash a wrong file.
What's the command you're running?
I get the same error running this command:
fastboot.exe flash recovery recovery.img
I cant erase this partition too. When i run this:
fastboot.exe erase recovery
I get this:
FAILED (remote: unable to format)
¨
Please Help
Waërloga666 said:
I get the same error running this command:
fastboot.exe flash recovery recovery.img
I cant erase this partition too. When i run this:
fastboot.exe erase recovery
I get this:
FAILED (remote: unable to format)
¨
Please Help
Click to expand...
Click to collapse
Can you post a link to recovery you are trying to flash? (I will test it)
Can anyone help me out? I tried to install CM 13.1 in Zenfone 5 but when it gets to "writing boot" the following message appears:
FAILED (remote: flash_cmds error!)
How could i solve this? txs everyone
(If any of you guys could text in Portuguese i would be very pleasant)
if u want to flash custom rom
all u need is to unlock bootloader
take a look on this thread using auto.bat for unlock bootloader!
https://forum.xda-developers.com/zenfone-5/general/recovery-twrp-2-8-6-0-asus-zenfone-5-t3136263
after unlocked try flash TWRP again
to confirm success unlocked not!
if fail it will show error failed
just follow step by step read thru!
hope it helps
good luck !
I am Having The Same Error (FAILED (remote: flash_cmds error!)
What To do
Hello
i have followed all the guides in order to install the latest version of TWRP in mi X Compact in order to Magisk, but im having this issue on the fastboot comand:
Sending 'recovery' (21552 KB) OKAY [ 0.724s]
Writing 'recovery' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
i have serched for solutions but nothing seems to work, its the first time i try to install TWRP on this phone so its never been rooted (Bootloader is not unlocked) and everyting has alredy been updated to the latest version, any help?
Thanks in advance!
i just unlocked the bootloader, and still gives me the "FAILED (remote: Command not allowed)" error when flashin TWRP trough fastboot HELP PLEASE
Black Swift said:
i just unlocked the bootloader, and still gives me the "FAILED (remote: Command not allowed)" error when flashin TWRP trough fastboot HELP PLEASE
Click to expand...
Click to collapse
Try fastboot boot twrp.img
just tried it, i got a message on my phone screen:
"your device has failed verification and will not work properly"
then phone restarts
in the windows power shell i get this message:
FAILED (Status read failed (Too many links))
I just seem to be unable to install TWRP on this phone :C
Help please!!!
i just tried a different cable, im still getting the "comand not allowed" message, can anyone help me please??
It is very hard to find any Information on the ASUS Zenfone Max Pro M1 X00TDB Modell, is there someone who knows more?
I cannot find a modell specific twrp recovery.img or any kind of Custom OS support
Maybe someone can show me how to compile them myself?
My Bootloader is already unlocked
When I try to install the unofficial X00TD recovery.img, I just get this error code:
PS C:\adb\unlock> fastboot flash recovery twrp-3.2.2-1-20180727-X00TD.img
Sending 'recovery' (58328 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
For some reason my stock android recovery it says:
asus/WW_X00TD/ASUS_X00T_1
Is that normal?
Any advice is helpful, thanks in advance
*UPDATE: I solved it by disconnecting the phone, exexuting the bootloader flash command and after getting "waiting for device" plug the phone back in the computer.
OT4KUBoi said:
It is very hard to find any Information on the ASUS Zenfone Max Pro M1 X00TDB Modell, is there someone who knows more?
I cannot find a modell specific twrp recovery.img or any kind of Custom OS support
Maybe someone can show me how to compile them myself?
My Bootloader is already unlocked
When I try to install the unofficial X00TD recovery.img, I just get this error code:
PS C:\adb\unlock> fastboot flash recovery twrp-3.2.2-1-20180727-X00TD.img
Sending 'recovery' (58328 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
For some reason my stock android recovery it says:
asus/WW_X00TD/ASUS_X00T_1
Is that normal?
Any advice is helpful, thanks in advance
*UPDATE: I solved it by disconnecting the phone, exexuting the bootloader flash command and after getting "waiting for device" plug the phone back in the computer.
Click to expand...
Click to collapse
I solved it by disconnecting the phone, exexuting the bootloader flash command and after getting "waiting for device" plug the phone back in the computer.
Now I have a new problem, when I try to Install the official LineageOS X00TD https://download.lineageos.org/X00TD on my X00TDB Device I get an error 7 message on TWRP, do you guys know a solution?
I'm trying to root my Huawei P8 Lite 2017 PRA-LX1 (running on EMUI 5.0.3 Android 7.0). But I'm getting stuck :
My BootLoader is unlock, but my FRP is locked when I access the fastboot mode.
The option Allow OEM unlock is turned off and greyed out in the dev settings.
It prevents me from doing any command with fastboot, except "fastboot devices" and "fastboot oem get-bootinfo". All other commands return me :
Code:
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
I'm worried cause it looks like I no longer have a recovery img : when I boot with Vol UP + Power, I got a screen with the Android guy saying :
Code:
ERROR MODE
Attention !
Please Update system again
Error
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
Each time I boot, I have a black screen with white and yellow writtings saying
"your devices has been unlocked and cannot be trusted"
From there I can boot normaly to the standard OS (EMUI 5.0.3 ; Android 7.0).
I can also enter the eRecovery mode to download latest version and recovery. But it fails and say "Getting package info failed".
When I try the factory reset from the settings, I get the same error as the one I got when trying to access the recovery more :
Code:
ERROR MODE
Attention !
Please Update system again
Error
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
To get to this situation, I tried to follow this guide :
[GUIDE] Unlock bootloader, root the device and install any custom ROM! (ALE-L23/21)
Hi all! So, you have a P8 lite in your pocket and you hate EMUI? Well, that was my case too, it's uncustomizable, ugly, and removes plenty of features from android stock. I do not like it one bit, and I like even less the fact that this phone is...
forum.xda-developers.com
I was not able to flash any OS with the dload/ procedure.
So I followed this guide :
[UPDATED GUIDE] [BOOTLOADER UNLOCK] Huawei p8 lite 2017 (pra-lx1)
This guide is the only one made and tested personally by me, I am not responsible for malfunctions or any damage to the device, carefully read every single step and everything will be successful [ATTENTION]: Before proceeding, save all your...
forum.xda-developers.com
and was able to correctly unlock my bootloader.
Then, I got back to the first guide to Install TWRP. The command fastboot flash recovery was working well :
Code:
$ fastboot flash recovery twrp-3.6.2_9-0-prague.img
Sending 'recovery' (14998 KB) OKAY [ 0.430s]
Writing 'recovery' OKAY [ 0.370s]
Finished. Total time: 0.828s
But I never managed to enter the TWRP recovery.
The Vol UP + Power reboot was getting me the eRecovery mode (to install the standard OS).
I tried to enter TWRP with fastboot :
Code:
$ fastboot boot twrp-3.6.2_9-0-prague.img
Sending 'boot.img' (14998 KB) OKAY [ 0.420s]
Booting FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
Trying to solve this situation have made the things worse and worse.
I would like to follow this tutorial
[Solution]BL unlocked&FRP Locked-Fastboot FAILED (remote: Command not allowed)
Note: THIS IS NOT A SOLUTION TO BYPASS FRP! I am not responsible if you are dumb dumb and break your phone This Solution is written in under 10 minutes AND WORKS ONLY AND ONLY FOR STOCK people with no experience stay away This is not a...
forum.xda-developers.com
but since I cannot do a factory reset (first step tutorial) and I don't have a recovery img working, I'm a bit timorous.
Do you think I can upgrade my OS (from my OS settings menu) without a recovery img ? Will that solve the issue with my recovery img ?
Any thoughts on the situation would be much appreciated.
Thanks for reading me !