Hi all I have recently got a Z4 Tablet and I am trying to root it to put a custom rom on. I have got the TA partition backed up, but when I'm trying to unlock the bootloader I get the same error on 2 computers, this is what i get:
C:\platform-tools>fastboot oem unlock 0x<mycode>
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
Thanks
Do you have a custom boot.img flashed? You may try to flash Stock rom first via Sony Companion.
Or try another version of fastboot tool.
Related
Hi guys!
Today, i decided to unlock bootloader to root my moto e. I did not want to download the 1.1 GB android sdk file so i used another option.
I just had to download a small file <500kb. I cannot post links right now cuz i haven't posted much.I followed the instructions correctly but when unlocking i get error:
<bootloader> Failed to erase partition
<bootloader> General Unlock Failure!
<bootloader> OEM unlock failure!
FAILED <remote failure>
However, i still got the bootloader unlocked warning on my phone. So i am in doubt: Is the bootloader unlocked correctly in my phone or not? Should I proceed to root it?
MrKarma4ya said:
Hi guys!
Today, i decided to unlock bootloader to root my moto e. I did not want to download the 1.1 GB android sdk file so i used another option.
I just had to download a small file <500kb. I cannot post links right now cuz i haven't posted much.I followed the instructions correctly but when unlocking i get error:
<bootloader> Failed to erase partition
<bootloader> General Unlock Failure!
<bootloader> OEM unlock failure!
FAILED <remote failure>
However, i still got the bootloader unlocked warning on my phone. So i am in doubt: Is the bootloader unlocked correctly in my phone or not? Should I proceed to root it?
Click to expand...
Click to collapse
Just go to fastboot (pressing power and volume down keys) and check bootloader status!
I'm trying to flash system.img using fastboot. However it says "FAILED (remote: Command not allowed)"
I can access fastboot and Recovery.
I'm doing this because I have no OS due to accidental wipe.
I'm using Huawei Mediapad M2 801L
Caelestiel said:
I'm trying to flash system.img using fastboot. However it says "FAILED (remote: Command not allowed)"
I can access fastboot and Recovery.
I'm doing this because I have no OS due to accidental wipe.
I'm using Huawei Mediapad M2 801L
Click to expand...
Click to collapse
Already another thread here. http://forum.xda-developers.com/android/help/help-please-help-to-unlock-bootloader-t3514419/page1
Please use search and read before posting. It keeps the forums clean . Copy and paste the adb/fastboot log you got here so that we can help you better. Also you can flash a custom rom and get things straight if you have a custom recovery like TWRP or CWM installed.
So I bought a son new phone.
As he told he installed magisk first, flashing "magisk_patched.img" through windows shell, everything was fine. Then He flashed twrp and magisk, everything was almost fine, he noticed that he cant play audio. He was trying to fix it first through installing magisk audio mods like viper and sauron. It didn't fixed anything, he unistalled it, everything was still in the same state, so he decided to flash stock frimware. He flashed through mi flashing tool, unfortunetaly It was image for "global xiaomi version" I mean "PFQMIXM" when as far as I know It should be "PFQEUXM". It didn't work and he was stuck in a bootloop. He found "MiUi 11 " image and for still unknown to me reason thought that it is going to fix everything. He flashed It again through mi flashing tool. It didn't work. He did that second time but at last he just closed the flashing tool while it was doing its thing.
At last he found eu firmware but now after all of that when i try to flash it or single files like crc list i get this:
flash crclist "E:\ModCR\adb\images\crclist.txt"
Sending 'crclist' (0 KB) FAILED (Write to device failed (Unknown error))
fastboot: error: Command failed
Device only boots to fastboot (no recovery/twrp either).
I tried erasing cache:
./fastboot erase cache
Erasing 'cache' FAILED (Write to device failed (Unknown error))
fastboot: error: Command failed
I tried to check slots:
./fastboot getvar active-slot
getvar:active-slot FAILED (Write to device failed (Unknown error))
Finished. Total time: 5.003s
I tried to change slot:
./fastboot set_active b
fastboot: error: Device does not support slots
When i typed "fastboot devices" It appeared as "??????"
./fastboot devices
???????????? fastboot
I don't know how to fix it, If anyone knows or has any kind of even small idea please write it down. I would be very greatfull.
Install custom recovery twrp
Install custom rom
Reboot
Download firmware EU
Install a firmware witch miflash
Restore Factory
Walaaaaa
xt610 said:
Install custom recovery twrp
Install custom rom
Reboot
Download firmware EU
Install a firmware witch miflash
Restore Factory
Walaaaaa
Click to expand...
Click to collapse
What i understand from op post is that fastboot commands are not working. So how will he flash twrp?
The firmware version doesn't matter at all you can flash EU on global and vice versa it doesn't matter.
What I think happened was your son never switched to slot 'a' before using mi flash.
Xiaomi's install script for miflash requires you to be on slot 'a' before flashing.
The only way to recover from this is edl mode which requires a xiaomi verified account to fix.
MOD EDIT: Part removed
Please do not advertise/recommend remote unlock services on XDA. Please read the FORUM RULES especially those:
i tried to install twrp in my Xiaomi mi a3 but the command not worked, i tried to change the slot to b, so i execute the command, but still nothing. I use mi flash Tool to redo a clean install of the system without first replacing the slot equal to b, also the procedure locked the bootloader. Now I don't know what to do anymore, I ask you for help!
RattlyFern41846 said:
i tried to install twrp in my Xiaomi mi a3 but the command not worked, i tried to change the slot to b, so i execute the command, but still nothing. I use mi flash Tool to redo a clean install of the system without first replacing the slot equal to, also the procedure locked the bootloader. Now I don't know what to do anymore, I ask you for help!
Click to expand...
Click to collapse
Does this command work for you ?
fastboot flashing unlock
fastboot flashing unlock_critical
RizwanH20 said:
Does this command work for you ?
fastboot flashing unlock
fastboot flashing unlock_critical
Click to expand...
Click to collapse
response of the first command:
fastboot flashing unlock
FAILED (remote: 'Flashing Unlock is not allowed
')
fastboot: error: Command failed
response of the second command:
FAILED (remote: ' Device already : unlocked!')
fastboot: error: Command failed
Hi everyone!
I want to install TWRP on a P20 Lite with the main goal to install LOS16 and possible other custom ROMs. Therefore I was following the official guide on LOS.
However when I try to boot/flash the TWRP image-file with fastboot i receive the following error:
Problem
Code:
$>fastboot flash recovery twrp.img
Sending 'recovery' (14946 KB) OKAY [ 0.396s]
Writing 'recovery' FAILED (remote: 'partition length get error')
fastboot: error: Command failed
$>fastboot boot twrp.img
Sending 'boot.img' (14946 KB) OKAY [ 0.376s]
Booting FAILED (remote: 'invalid command')
fastboot: error: Command failed
Error is shown in admin command line as well.
Furthermore I get the following error which let me think that it is more of a fastboot problem.
Code:
$>fastboot getvar version
getvar:version FAILED (remote: 'invalid command')
$>fastboot oem device-info
FAILED (remote: 'invalid command')
fastboot: error: Command failed
Specs
Phone: Huawei P20 Lite ANE-LX1
Build:9.1.0.377(C432E7R1P7)
EMUI-Version 9.1.0
Bootloader unlocked - PHONE Unlocked, FRP unlocked (via PotatoNV method with same adb/fastboot installation).
Adb:
Android Debug Bridge version 1.0.41
Version 30.0.5-6877874
Info
Same error with adb/fastboot from two different PCs (Win10). Adb and fastboot seem to work in general. For example both show the device in List of devices attached and i can reboot and boot via adb and fastboot.
As I understand this post it is not possible to flash twrp directly on android 9.
However I tried the twrp file linked in the mentioned post and several images linked in this forum (this, this) + the one from twrp-anne and got the same error fastboot: error: Command failed on all.
Does anybody know or has a hint what might be the problem? Any help appreciated.
Best regards
I had the same issue.
You have to use the command: fastboot flash recovery_ramdisk twrp.img
yellowzebra said:
As I understand this post it is not possible to flash twrp directly on android 9.
Click to expand...
Click to collapse
Hello, please read carefully :
-Alf- said:
flash TWRP , run command
fastboot flash recovery_ramdisk (TWRP's_name).img
Click to expand...
Click to collapse
-Alf- said:
Since A8 and above you can not install TWRP over eRecovery from fastboot, only from TWRP:
Click to expand...
Click to collapse
- eRecovery and Recovery are two different things .
That worked!
Thank you very much. Both of you for the fast answer
I am currently researching before asking more noob questions. Have some thoughts. Especially on difference between eRecovery and Recovery and why commands as fastboot oem device info where not working before the recovery_ramdisk. Might return later.
Thx!