Database Users

[Q] Unknown partition error when using fastboot flash recovery.img

First of all, I would like to apologize if this question has been answered in another thread. I have searched the xda forums and others with no success.
My situation is the following:
Running on Windows 8.1
1. Rooted Nexus 4 on 4.4 (if I remember correctly)
2. OTA update to 4.4.2 (loosing root, but device remains unlocked) (I think I also tried flashing the factory image manually, but failed, I don't remember exactly)
I rooted my phone when Kitkat was fresh and found there were no custom roms on 4.4 yet so I went back to stock because it was the easiest way to get the update. Right now I can not flash a custom recovery.
fastboot oem unlock
...
FAILED (remote: Already Unlocked)
finished. total time: 0.002s
===================================================
fastboot flash recovery.img
unknown partition 'recovery.img'
error: cannot determine image filename for 'recovery.img'
This is the same for both TWRP and CWM. I am very sure I did NOT misspell the name.
Does anyone have any idea why this is happening and how to fix it?
Thank you for taking the time to read this post!

You have to use this
fastboot flash recovery recovery.img

wrong syntax, must be: fastboot flash recovery recovery.img

Wow.... I am ashamed with myself. I cannot believing I missed that.
Thank you for the quick reply guys.

I was just doing the same here thanks!

command doesnt work for me
jd1639 said:
You have to use this
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
I've tried to use that command but this is all i get after:
Sending 'recovery' (22432 KB) OKAY [ 0.579s]
Writing 'recovery' FAILED (remote: '(recovery_b) No such partition')
fastboot: error: Command failed
Is there that is wrong and that i may need to fix?

FastSl0th said:
I've tried to use that command but this is all i get after:
Sending 'recovery' (22432 KB) OKAY [ 0.579s]
Writing 'recovery' FAILED (remote: '(recovery_b) No such partition')
fastboot: error: Command failed
Is there that is wrong and that i may need to fix?
Click to expand...
Click to collapse
In the xda forum, check carefully whether you are asking a question in the appropriate Q&A section for your device, because you are certainly not writing about Nexus 4.
.

FastSl0th said:
command doesnt work for me
I've tried to use that command but this is all i get after:
Sending 'recovery' (22432 KB) OKAY [ 0.579s]
Writing 'recovery' FAILED (remote: '(recovery_b) No such partition')
fastboot: error: Command failed
Is there that is wrong and that i may need to fix?
Click to expand...
Click to collapse
Hopefully you may have already asked or solved this question. I am assuming you are issuing command from platform-tools folder. If you have a Windows 10 OS system then, I too could not found USB drivers for my system with windows 10. If 'fastboot devices' command returning some device id then maybe I have guessed wrong reason.

I entered "fastboot flash XXX.img" Too. hahaha
After i see this article, I entered "fastboot flash recovery flash XXX.img"
Thank you anyway.

unsolved

dan60 said:
unsolved
Click to expand...
Click to collapse
fastboot: error: cannot determine image filename for 'bootC:\Android Development\platform-tools\magisk_patched-24300_NP5BG.img' How To Solve This Problem Brother..Please Tell me

fastboot: error: cannot determine image filename for 'bootC:\Android Development\platform-tools\magisk_patched-24300_NP5BG.img' How to Solve This Problem Brother...Please Tell Me

d4_daman_ said:
fastboot: error: cannot determine image filename for 'bootC:\Android Development\platform-tools\magisk_patched-24300_NP5BG.img' How to Solve This Problem Brother...Please Tell Me
Click to expand...
Click to collapse
Hi there!
It didn't work for me but you can try it >>>
jd1639 said:
You have to use this
fastboot flash recovery recovery.img
Click to expand...
Click to collapse

Hi guys, I found the same error when I've tried to install TWRP on mi Xiaomi Mi A3 by FASTBOOT on Linux Terminal.
After a lot of searching, I solved my problem using the syntax below:
"fastboot flash boot XXX.img"
"boot" is the partition about FASTBOOT are asking for.
Hope to be usefull.

[GUIDE] LG G STYLO How to root the T-Mobile 6.0 update

This guide was made before Kingroot was able to root the official update. But thanks to @oskar and @TheDerekHarper on XDA and to @josephwv on Android forums it is now comfirmed that Kingroot will root the official update. But first you must still follow steps #1 through #6 so Kingroot can root your device.
Now before Kingroot was able to root the update I figured out how to root the official update and it is not all to complicated. The following guide will walk you through the root process. But I am not responsible for anything that happens to your devices by using this guide as you are responsible for your device.
What you need:
1. A computer running Linux or Windows with adb and fastboot installed. (I used Ubuntu)
2. If you are using Windows you need all the drivers for your device installed. Linux users will not have to worry about this.
3. A functioning USB cable for your device.
4. Battery charged at least 50% just for safety.
5. The TWRP revovery.img, this is the same TWRP recovery we already have for the LG G Stylo I have just renamed it to recovery.img to make it easier to type the name in while typing fastboot commands.
6. The SuperSU-v2.65-20151226141550.zip by Chainfire. (All credit to Chainfire for this awesome zip.)
How to root your device:
1. I suggest you first go to Settings/General/About Phone/Software info and tap on the "Build number" until it says"You are now a developer". Then back out of until you are in Settings/General and go to "Developer options" and turn "Enable OEM unlock" on. This is to allow TWRP recovery to be able to boot. Also turn on "USB debugging" while you are there.
2. Download the SuperSU-v2.65-20151226141550.zip to your device. You need to move the zip file from your Downloads folder to somewhere on your external SD card as it will not be deleted from there when you use the "fastboot oem unlock" command in step #6.
3. Download the recovery.img to your computer. If you do not have adb and fastboot setup globally for linux or in your path for windows you need to move the recovery.img to the directory your adb and fastboot is in and open a terminal or command line (depending on your OS) in that directory or cd to that directory. If you do have adb and fastboot globally or in your path you can just open a terminal or command line in the directory you have the recovery.img or cd to the directory you have the recovery.img.
4. Once you have the terminal or command line open run the command "adb devices" to make sure your devices is detected by adb. You may get a toast pop up on your device asking if you to "Allow usb debugging". Except this as this is the RSA key you need to allow your computer to communicate with your device via adb. You should see something like "LGH631dffacad9 device" in your terminal or command line. If you see "unauthorized" instead of "device" you have not excepted the RSA key.
5.Now type the following command in your terminal or command line. Type "adb reboot bootloader". This will reboot your device to fastboot mode. Once in fastboot mode use the "fastboot devices" to make sure your device is recognized by fastboot. You should see something like "dffacad9 fastboot". If you are in Linux and get a error message you may have to use "sudo fastboot devices" for fastboot to work. (If you are using Windows and are having trouble with fastboot recognizing your device you need to install the device drivers. If it still does not work install the drivers again with your device connected to your computer in fastboot mode.)
6. To fully unlock your bootloader you have to use the command "fastboot oem unlock". You have to do this or this root method will not work. But be warned that if you do use this command it will factory reset your device. Plus you will get a line of text saying the bootloader is unlocked on the splash screen when you boot your device.
6-1: If you are wanting to use Kingroot to root your device you can reboot your device now. Open the Kingroot app and let it root your device and then use Flashify, Rashr, or a similar app to flash the recovery. Then boot to recovery and flash the SuperSU.zip in recovery and it will remove Kingroot and have SuperSU installed on your device.
7. Now you can do this two ways if you do not want to keep the stock recovery you can use the command "fastboot flash recovery.img" to install the recovery and then use the command "fastboot reboot recovery" to boot to the TWRP recovery. (If this command gives you issue like it seems to be for many then just use the the following method and then use Flashify or Rashr app to install TWRP after you are done rooting.) If you want to keep the stock recovery you can use the command "fastboot boot recovery.img" to boot to the TWRP recovery.
8. Once you are booted to the TWRP recovery you should make a full backup first so you have a backup to restore to in case things go bad. After you make a backup then select install and then find the SuperSU-v2.65-20151226141550.zip and install it. Once it is installed reboot your device to system. If TWRP gives you a warning about the su binaries missing and asks if you want to install thee su binaries before you reboot select no or it will interfere with the rooting process of the SuperSU.zip. When your device reboots it will boot to the LG splash screen and then reboot again. But then it will boot to the OS but it will take a minute. Make sure you let your device reboot all the way to the lockscreen or home screen depending on if you have a lockscreen enabled or not. You should be fully rooted after this, enjoy.

Resserved in case needed later.

Thank you.

target reported max download size of 268435456 bytes
sending 'recovery' (11300 KB)...
OKAY [ 0.359s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.359s

ok so i know this is 100% my fault for not reading, but why would you even include step 6? it wipes everything including the supersu.zip. the files i'm pissed about, but i can get over. mostly music plus some ****ty pictures. contacts can text me. but the main thing is i had to restart my phone, get it started up and everything, then put the super su.zip back onto the phone. just a tedious task.

Can I use this guide with my G4 Stylus (H635)?

wtf... i get this same error
C:\adb>fastboot flash recovery v10.img
target reported max download size of 268435456 bytes
sending 'recovery' (11230 KB)...
OKAY [ 0.390s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.390s
I've tried multiple versions of the TWRP for the g stylo on adroidforum and none of it flashes with the fastboot flash recovery .....img option. Every single one fails. Please tell me how you flashed the recovery... Also I cant run it through Flashify because my SuperSU says no binary is installed... I'm completely lost at this point

aaron2z said:
wtf... i get this same error
C:\adb>fastboot flash recovery v10.img
target reported max download size of 268435456 bytes
sending 'recovery' (11230 KB)...
OKAY [ 0.390s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.390s
I've tried multiple versions of the TWRP for the g stylo on adroidforum and none of it flashes with the fastboot flash recovery .....img option. Every single one fails. Please tell me how you flashed the recovery... Also I cant run it through Flashify because my SuperSU says no binary is installed... I'm completely lost at this point
Click to expand...
Click to collapse
Someone mentioned using the Kingroot app and I gotta admit, I was skepticle at first but after testing. I can confirm it works.
Just go go KingRoot.net, download their apk, install and run the root program. Igll work out of the box after, sadly I couldn't get the above method to work either with super su.

aaron2z said:
wtf... i get this same error
C:\adb>fastboot flash recovery v10.img
target reported max download size of 268435456 bytes
sending 'recovery' (11230 KB)...
OKAY [ 0.390s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.390s
I've tried multiple versions of the TWRP for the g stylo on adroidforum and none of it flashes with the fastboot flash recovery .....img option. Every single one fails. Please tell me how you flashed the recovery... Also I cant run it through Flashify because my SuperSU says no binary is installed... I'm completely lost at this point
Click to expand...
Click to collapse
do the fastboot boot recovery.img so it boots up twrp then flash the supersu zip then boot your phone you should be rooted then flash twrp using flashify

I was getting the same error, ( in step 7 don't flash the recovery )
just use "fastboot boot recovery.img" and it will boot to TWRP without installing it
you can then install SU, ( note ) when you exit or re boot from TWRP it will say SU in not installed do you want to install it, I did the first time and it seemed to hose up, so I did everything over and the second time selected no to re install.
once booted I used flashify to install the TWRP img, and I am able to boot to recovery using Quickboot apk
on a side note I have SU installed, I can use root explorer and other apps that ask for SU access, but Titanium backup
doesn't seem to uninstall apps anymore, they seem to re install after a reboot
Hope this helps yall's
aaron2z said:
wtf... i get this same error
C:\adb>fastboot flash recovery v10.img
target reported max download size of 268435456 bytes
sending 'recovery' (11230 KB)...
OKAY [ 0.390s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.390s
I've tried multiple versions of the TWRP for the g stylo on adroidforum and none of it flashes with the fastboot flash recovery .....img option. Every single one fails. Please tell me how you flashed the recovery... Also I cant run it through Flashify because my SuperSU says no binary is installed... I'm completely lost at this point
Click to expand...
Click to collapse

TheDerekHarper said:
Someone mentioned using the Kingroot app and I gotta admit, I was skepticle at first but after testing. I can confirm it works.
Just go go KingRoot.net, download their apk, install and run the root program. Igll work out of the box after, sadly I couldn't get the above method to work either with super su.
Click to expand...
Click to collapse
I gotta be honest... I'm pretty skeptical to try it. I've read of everyone having either a softbrick boot loop or the root just not staying after reboot. Yours worked for H631 T-mobile 6.0 and stayed? If you confirm T-mobile variant and 6.0 I'll try it. There's a lot of headache with this method for me (not saying it doesn't work). I bricked my phone trying to get the binary files for SU by trying to reroot. But unbricked it with LG Flash Tools and a stock kdz. So I don't want to brick it again twenty minutes later lol

aaron2z said:
I gotta be honest... I'm pretty skeptical to try it. I've read of everyone having either a softbrick boot loop or the root just not staying after reboot. Yours worked for H631 T-mobile 6.0 and stayed? If you confirm T-mobile variant and 6.0 I'll try it. There's a lot of headache with this method for me (not saying it doesn't work). I bricked my phone trying to get the binary files for SU by trying to reroot. But unbricked it with LG Flash Tools and a stock kdz. So I don't want to brick it again twenty minutes later lol
Click to expand...
Click to collapse
Made a tutorial on how to get the marshmallow update (i.e. rom i've used.)
And then afterwards i downloaded Minimal ADB & Fastboot, OEM Unlocked the device (for safety) and downloaded the Kingroot Apk.
Installed it, and just allowed the program to root. It was pretty simple, haven't had any issues (i've even disabled OEM Unlock from the phone & USB Debugging.)
Hell, even adoptable storage is enabled for my phone too (but that's another tutorial from somewhere else.)
I do plan to make a root video, just so someone could see it and grab their opinion.
To be clear: I'm using a metroPCS LG Stylo. Also, only time the phone had issues was when i factory reset it to get rid of root. (didn't work)
so i had to follow the steps from the above tutorial to reflash the stock rom.

jothe1 said:
do the fastboot boot recovery.img so it boots up twrp then flash the supersu zip then boot your phone you should be rooted then flash twrp using flashify
Click to expand...
Click to collapse
well this did it, the root actually worked.

I got a permanent root from the procedure listed on page one of this thread. The only thing I did differently was, when booted into TWRP and you try to re boot the system you will get the question if you want TWRP to install root. If you do allow TWRP to install root, you wont get root. At this point select the option to just reboot the phone. The LG Logo will appear twice before it fully boots. When the device is fully up, you will have root.

Foamp said:
ok so i know this is 100% my fault for not reading, but why would you even include step 6? it wipes everything including the supersu.zip. the files i'm pissed about, but i can get over. mostly music plus some ****ty pictures. contacts can text me. but the main thing is i had to restart my phone, get it started up and everything, then put the super su.zip back onto the phone. just a tedious task.
Click to expand...
Click to collapse
My apologies as I made a typo in the guide. The correct command is "fastboot flash recovery recovery.img" to flash the recovery. I will fix this along with another rework about putting the SusperSU.zip only on your SD card.
oskar5510 said:
Can I use this guide with my G4 Stylus (H635)?
Click to expand...
Click to collapse
I do not know if you can use it or not as I do not have that device. But you can try it bit if your device does not boot to fastboot mode when you issue the adb reboot bootloader command then your device's bootloader is not unlockable and this root method will not work for you. But from the posts in this thread point out that Kingroot now works on the 6.0 update so you can also try Kingroot to see if it willroot your device.
aaron2z said:
wtf... i get this same error
C:\adb>fastboot flash recovery v10.img
target reported max download size of 268435456 bytes
sending 'recovery' (11230 KB)...
OKAY [ 0.390s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.390s
I've tried multiple versions of the TWRP for the g stylo on adroidforum and none of it flashes with the fastboot flash recovery .....img option. Every single one fails. Please tell me how you flashed the recovery... Also I cant run it through Flashify because my SuperSU says no binary is installed... I'm completely lost at this point
Click to expand...
Click to collapse
Again sorry as this is fully my fault for making the typo on the fastboot command to flash recovery. I am fixing it as soon as I am done with this post.
TheDerekHarper said:
Someone mentioned using the Kingroot app and I gotta admit, I was skepticle at first but after testing. I can confirm it works.
Just go go KingRoot.net, download their apk, install and run the root program. Igll work out of the box after, sadly I couldn't get the above method to work either with super su.
Click to expand...
Click to collapse
Thank you for posting this.
jothe1 said:
do the fastboot boot recovery.img so it boots up twrp then flash the supersu zip then boot your phone you should be rooted then flash twrp using flashify
Click to expand...
Click to collapse
Yes this is how I did it when I rooted my device. I will edit the guide some to point this out.
AgainstTheFlow said:
I got a permanent root from the procedure listed on page one of this thread. The only thing I did differently was, when booted into TWRP and you try to re boot the system you will get the question if you want TWRP to install root. If you do allow TWRP to install root, you wont get root. At this point select the option to just reboot the phone. The LG Logo will appear twice before it fully boots. When the device is fully up, you will have root.
Click to expand...
Click to collapse
Thank you for posting this so others can see this does work.
infektedpc said:
target reported max download size of 268435456 bytes
sending 'recovery' (11300 KB)...
OKAY [ 0.359s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.359s
Click to expand...
Click to collapse
I also apologize to you for my mistake. It will be corrected shortly.
TheDerekHarper said:
Made a tutorial on how to get the marshmallow update (i.e. rom i've used.)
And then afterwards i downloaded Minimal ADB & Fastboot, OEM Unlocked the device (for safety) and downloaded the Kingroot Apk.
Installed it, and just allowed the program to root. It was pretty simple, haven't had any issues (i've even disabled OEM Unlock from the phone & USB Debugging.)
Hell, even adoptable storage is enabled for my phone too (but that's another tutorial from somewhere else.)
I do plan to make a root video, just so someone could see it and grab their opinion.
To be clear: I'm using a metroPCS LG Stylo. Also, only time the phone had issues was when i factory reset it to get rid of root. (didn't work)
so i had to follow the steps from the above tutorial to reflash the stock rom.
Click to expand...
Click to collapse
Thanks for posting this I will add this to the post as another option to root seeing as it is comfirmed. I will give credit to you and @oskar for this info.

Is there anyway to do this without wiping your data from 'fastboot oem unlock'? My bootloader keeps saying locked in fastboot mode even though I checked Enable OEM Unlock in settings. It won't let me boot the recovery.img because it's locked.

supersonic125 said:
Is there anyway to do this without wiping your data from 'fastboot oem unlock'? My bootloader keeps saying locked in fastboot mode even though I checked Enable OEM Unlock in settings. It won't let me boot the recovery.img because it's locked.
Click to expand...
Click to collapse
Are you trying to use the fastboot boot recovery.img command?

Yeah, if I try to flash instead of booting I get:
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 268435456 bytes
sending 'recovery' (11300 KB)...
OKAY [ 0.380s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.401s

supersonic125 said:
Yeah, if I try to flash instead of booting I get:
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 268435456 bytes
sending 'recovery' (11300 KB)...
OKAY [ 0.380s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.401s
Click to expand...
Click to collapse
Hmmm looks like maybe fully unlocking the bootloader enables all fastboot commands. You can try downloading and installing Kingroot and root with it as the posts here comfirm it will root the update now. Or just u lock the bootloaderb but your device will be reset if you do.

T-Macgnolia said:
Hmmm looks like maybe fully unlocking the bootloader enables all fastboot commands. You can try downloading and installing Kingroot and root with it as the posts here comfirm it will root the update now. Or just u lock the bootloaderb but your device will be reset if you do.
Click to expand...
Click to collapse
What if we just enable oem unlock in both the system and the bootloader then use adb to push the recovery, superuser, and busybox to the system. King Root caused too many system instabilities, it had injected itself as a system app and after unrooting and uninstalling after a reboot I was left with a soft brick due to a secure boot error 1003. A stock 5.1.1 kdz and the lg flash tool was able to bring my Stylo back to life.
It could all be done by running a simple batch file bundled with everything we need for our device. Linux would probably be the better option but it could work the same in windows.

Please Help me! I can't flash stock rom

Hello I'm trying to flash stock ROM via adb, specifically cust.img, boot.img, system.img, Because I've bricked my phone and it stuck on huawei logo, but when i try to flash, i got the following error "FAILED (remote: Command not allowed)"
Code:
C:\adb>fastboot flash cust cust.img
target reported max download size of 471859200 bytes
sending 'cust' (304183 KB)...
OKAY [195.875s]
writing 'cust'...
FAILED (remote: Command not allowed)
finished. total time: 195.899s
c:\adb>fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (21690 KB)...
OKAY [ 13.671s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 13.694s
c:\adb>fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' (460798 KB)...
OKAY [314.622s]
writing 'system'...
FAILED (remote: Command not allowed)
finished. total time: 314.665s
Please how I can unbrick my phone and reinstall the firmware
Obs. My bootloader is unlocked and I'm using TWRP recovery

Is your phone really shows Unlocked in red color when it's in fastboot mode?
Was your phone rooted, if yes, with which method?
You should try doing:
fastboot erase cache
fastboot erase userdata
These commands perform the same thing as Factory Reset do.
If it's not working, try to do the "dload" method with your original firmware your phone was shipped with.
Create a folder, called "dload" in your sdcard root, put the UPDATE.APP file of the firmware in it, and without connecting it to PC, press Vol + and Vol - and Power button until it starts flashing the firmware, and see what happens.
In later days, we've got a lot of troubleshooting topic opened up with your problem, the users cannot flash even with unlocked bootloader, and yet, there's no real solution to them.

I suggest that you use Windows 10? If I'm right sometimes this version of Windows cannot be used to flash via adb
I recommend you to use Windows 8.1 or 7 . My best way is of course using Linux

daviddosa said:
Is your phone really shows Unlocked in red color when it's in fastboot mode?
Was your phone rooted, if yes, with which method?
You should try doing:
fastboot erase cache
fastboot erase userdata
These commands perform the same thing as Factory Reset do.
If it's not working, try to do the "dload" method with your original firmware your phone was shipped with.
Create a folder, called "dload" in your sdcard root, put the UPDATE.APP file of the firmware in it, and without connecting it to PC, press Vol + and Vol - and Power button until it starts flashing the firmware, and see what happens..
Click to expand...
Click to collapse
Yes, it shows PHONE unlocked in red name, and I've made the root using an app called kingroot
I've tried to erase cache and userdata using adb but I can't, still got the same error "FAILED (remote: Command not allowed)"
I can't make dload method because I don't have stock recovery, and I can't flash the stock recovery using adb because its keep saying "FAILED (remote: Command not allowed)".
I don't know what to do
sokkoban said:
I suggest that you use Windows 10? If I'm right sometimes this version of Windows cannot be used to flash via adb
I recommend you to use Windows 8.1 or 7 . My best way is of course using Linux
Click to expand...
Click to collapse
I'm using windows 7 is this moment, maybe I try to flash using Linux later

Seems like all the guys with the same problem used KingRoot to root...that is the common thing amongst all.
I dont't think you need the stock recovery to update via the "dload" method, but I'm not sure.
If you don't have your original firmware's UPDATE.APP yet, download it, as well as the Huawei Update Extractor.
Load your file into the program, select ONLY BOOT.IMG, CUST.IMG(if it has one), SYSTEM.IMG and RECOVERY.IMG(optional, if selected, restores original recovery) right click on one, and press Create Flashable Zip.
Copy this to your sdcard and try to flash it.
I did not thest this above method, and don't know it the created flashable zip is really flashable, but I'm running out of possible solutions slowly.
Let us know what happens.

daviddosa said:
Seems like all the guys with the same problem used KingRoot to root...that is the common thing amongst all.
I dont't think you need the stock recovery to update via the "dload" method, but I'm not sure.
If you don't have your original firmware's UPDATE.APP yet, download it, as well as the Huawei Update Extractor.
Load your file into the program, select ONLY BOOT.IMG, CUST.IMG(if it has one), SYSTEM.IMG and RECOVERY.IMG(optional, if selected, restores original recovery) right click on one, and press Create Flashable Zip.
Copy this to your sdcard and try to flash it.
I did not thest this above method, and don't know it the created flashable zip is really flashable, but I'm running out of possible solutions slowly.
Let us know what happens.
Click to expand...
Click to collapse
So I tried to create a flashable zip using the Huawei Update Extractor however, was not possible, it's showing the following message "no suitable files selected. Check profiles.xml"
I've tried also creating flashable zip manually and flash it using TWRP, but TWRP reboot every time I try to flash theses files, that's why I think dload method work only with stock recovery

Hello,
I created the script for flash via fastboot if you want try this method
Extract BOOT.img, Cust.img, Recovery.img, System.img and copy to fastboot folder.(attachment)
Enable developer options and USB debugging
Simply run file FLASH-ALL.bat file

sokkoban said:
Hello,
I created the script for flash via fastboot if you want try this method
Extract BOOT.img, Cust.img, Recovery.img, System.img and copy to fastboot folder.(attachment)
Enable developer options and USB debugging
Simply run file FLASH-ALL.bat file
Click to expand...
Click to collapse
Thanks for the help but this method didn't work, everytime I try to flash the files, I got the same error "FAILED (remote: Command not allowed)” I don't know what is happening my bootloader is unlocked, why I can't flash the files with adb
Code:
target max-download-size: 450MB
sending 'boot' (21690 KB)...
OKAY [ 13.912s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 13.919s
target max-download-size: 450MB
sending 'recovery' (34264 KB)...
OKAY [ 21.963s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 21.985s
target max-download-size: 450MB
sending 'cust' (304183 KB)...
OKAY [191.580s]
writing 'cust'...
FAILED (remote: Command not allowed)
finished. total time: 191.603s
target max-download-size: 450MB
Sparse-Flash is enabled!
sending sparse 'system' (460798 KB)...
OKAY [366.120s]
writing 'system'...
FAILED (remote: Command not allowed)
finished. total time: 366.144s
ROM flashed , if all went well
You must be restarted.
If you leave the recovery to hard reset and restart the phone
Created by sokoban. Thank you for using my release
rebooting...
finished. total time: 0.054s
Pressione qualquer tecla para continuar. . .

This is very strange. May be you really have locked bootloader
Post answer from this command in fastboot mode:
Code:
fastboot oem get-bootinfo

sokkoban said:
This is very strange. May be you really have locked bootloader
Post answer from this command in fastboot mode:
Code:
fastboot oem get-bootinfo
Click to expand...
Click to collapse
This was the result
Code:
C:\adb>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.016s]
finished. total time: 0.016s
As you can see the ADB says that the bootloader is unlocked, but I'm still having trouble

Same issue with Huawei G6-U10
I'm having the same problem with Huawei Ascend G6-U10
Currently running on ROM b146, since it has some issues I was trying to downgrade or upgrade ( there is a b330 out).
I'm not an expert.
This morning I've unlocked the boot loader and then tried to flash a couple of different ROMs and I always get the same error message:
c:\adb>fastboot flash BOOT ./G6-U10verb330/boot.img
target reported max download size of 536870912 bytes
sending 'BOOT' (9696 KB)...
OKAY [ 0.310s]
writing 'BOOT'...
FAILED (remote: Command not allowed)
finished. total time: 0.321s
c:\adb>fastboot oem get-bootinfo
(bootloader) Bootloader Lock State: UNLOCKED
(bootloader) System State: Bootloader in UNLOCKED state
(bootloader) Bootloader Version: 001.001.000
I'm guessing this is not a G6-U10 specific issue so if anyone can give any hint it'll be very appreciated.
Thanks.

I have the same problem with a honor 4x.
Rooted with kingroot. We haven't writing permission in /system. That's why we can't install the recovery. If you try to install superSU and update the binary I guess you get an error.
Now the question is: how we can do to make writeble /system with fast boot?
"mount -o rw,remount -t ext3 /dev/block/xxxxxxxxx /system" in terminal doesn't work...

Similar thing happened to me. Even if command for showing unlocked bootloader said it was unlocked that was false because I used Kingroot previously. Only thing that helped was to unlock the bootloader through fastboot again. Then it was really unlocked and I could flash recovery (in my case TWRP) which before I was unable to.

Diego Sousa said:
This was the result
Code:
C:\adb>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.016s]
finished. total time: 0.016s
As you can see the ADB says that the bootloader is unlocked, but I'm still having trouble
Click to expand...
Click to collapse
Have you tried it with linux yet?
And have you used the Update.APP and dload method?

Maybe a driver problem? Have administrator rights? And debug mode on?
Try to connect your phone (power on) to the pc and wait to be recognized. In cmd type this:
Code:
adb devices
It has to show you your serial number right? If doesn't your device is not being recognized by adb.
Next type:
Code:
adb reboot-bootloader
This will restart your phone into fastboot and now you can type "fastboot devices" like first command and it has to show you your serial number again.
Try rebooting into bl with this, not by plugin in the phone, and install the rom again

Huawei P8 Lite
Hello I have a problem with my phone. I do not know how to hell I fix it.
It says error cannot load system.img but still I can install boot.img and others.
I¨d tryed that "dload" with update.app doesnt work.
phone is Huawei P8 Lite
this is my first time here

Have you tried install it in twrp? You don't have a twrp backup of stock rom?
In this case if you go in the Huawei eRecovery you can restore stock rom and twrp will be overwrited downloading the last rom , i tried it with my p8 lite 2017 .

Tuki2 said:
Hello I have a problem with my phone. I do not know how to hell I fix it.
It says error cannot load system.img but still I can install boot.img and others.
I¨d tryed that "dload" with update.app doesnt work.
phone is Huawei P8 Lite
this is my first time here
Click to expand...
Click to collapse
What are you using to go into fastboot mode? Is it ADB from Android SDK?? It turns out that using ADB from Android SDK lets you flash small files but not large files... I suggest you try flashing the file through Minimal ADB & Fastboot

sokkoban said:
Hello,
I created the script for flash via fastboot if you want try this method
Extract BOOT.img, Cust.img, Recovery.img, System.img and copy to fastboot folder.(attachment)
Enable developer options and USB debugging
Simply run file FLASH-ALL.bat file
Click to expand...
Click to collapse
i have the same issue as well, but just with Cust.img

[GUIDE] Update with fastboot

Guide for installing new security update with fastboot and with a bootloader-unlocked Pixel XL.
This is basically the same thing as usual but with the new structure.
If you have modified a little the stock android (hosts file, root, kernel, etc.), you may experience a fail in OTA update;
If you have a bootloop/soft brick/not sure of the state of your android system;
This is the solution.
This WILL NOT delete your data and apps. This will remove your custom kernel/root/hosts/recovery through (which is a good thing because it will be clean then).
I assume you already have anything to do fastboot command. If not, see this good thread.
1) Download your system image for Marlin (Pixel XL) on google website.
For November update, there are 3 versions:
NDE63U Europe
NDE63V US, except Verizon
NDE63X Verizon
2) Unzip the file marlin-nde63v-factory-a66866ba.zip
3) Unzip inside the new directory (marlin-nde63v) the image-marlin-nde63v.zip
4) Reboot into bootloader
Code:
adb reboot bootloader
5) Execute fastboot commands (assuming the bin is on your PATH)
Code:
fastboot flash bootloader bootloader-marlin-*.img
fastboot reboot-bootloader
fastboot flash radio radio-marlin-*.img
fastboot reboot-bootloader
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash system system.img
fastboot flash system_b system_other.img
fastboot flash vendor vendor.img
fastboot flash modem modem.img
fastboot reboot
Here we go, you have a fresh unrooted vanilla android with latest security patch.
6) To add TWRP and Root:
Code:
fastboot boot /path/to/twrp.img
In TWRP, install twrp.zip
Reboot into the installed recovery
In TWRP, install supersu.zip
Root thread for more information.
TWRP thread for more information.

** Reserved **

cam30era said:
@firewave,
Thanks for posting the guide. Just like Nexus devices except for the slot files. After unzipping the factory image, I do notice 15 additional files (other than boot, system, vendor, etc) that I've never seen before on a Nexus device. Do you happen to know what those are for, and why we don't flash them if doing a manual fastboot flash?
Thanks, in advance....
Click to expand...
Click to collapse
Other files are more for complete reset. There are for example, time-zones data, default crypto key, default /sdcard, bootlocker state, etc.
Only aboot.img is obscure for me. I'm at work so I can't dig into it, but I updated my pixel xl without issue that way.
I'm also add EX kernel and root again without issue.

firewave said:
Other files are more for complete reset. There are for example, time-zones data, default crypto key, default /sdcard, bootlocker state, etc.
Only aboot.img is obscure for me. I'm at work so I can't dig into it, but I updated my pixel xl without issue that way.
I'm also add EX kernel and root again without issue.
Click to expand...
Click to collapse
aboot is actually part of the bootloader.

death2all110 said:
aboot is actually part of the bootloader.
Click to expand...
Click to collapse
yep, it's why I'm unsure what to do with. Probably nothing.
I will loopmount the file at home and see.

Will this FDR the phone or just apply the update? I am currently on a Verizon Pixel XL Rooted/Unlocked and on the P build. Thanks for any information.

wx9kvh said:
Will this FDR the phone or just apply the update? I am currently on a Verizon Pixel XL Rooted/Unlocked and on the P build. Thanks for any information.
Click to expand...
Click to collapse
In the op in bold, he said it will not erase your data or apps

C:\android>fastboot flash bootloader bootloader-marlin-*.img
error: cannot load 'bootloader-marlin-*.img'
C:\android>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.047s]
finished. total time: 0.105s
C:\android>fastboot flash radio radio-marlin-*.img
< waiting for any device >
error: cannot load 'radio-marlin-*.img'
C:\android>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.047s]
finished. total time: 0.048s
C:\android>fastboot flash boot boot.img
target didn't report max-download-size
sending 'boot' (26405 KB)...
FAILED (command write failed (No error))
finished. total time: 0.001s
C:\android>fastboot flash system system.img
< waiting for any device >
target reported max download size of 536870912 bytes
I am getting the above error but it proceeds to do all other commands. Then I get hung up at the Google screen. Any suggestions? I can get into the bootloader. I've tried the fastboot commands twice now...same result

dablitzkrieg said:
C:\android>fastboot flash bootloader bootloader-marlin-*.img
error: cannot load 'bootloader-marlin-*.img'
C:\android>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.047s]
finished. total time: 0.105s
C:\android>fastboot flash radio radio-marlin-*.img
< waiting for any device >
error: cannot load 'radio-marlin-*.img'
C:\android>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.047s]
finished. total time: 0.048s
C:\android>fastboot flash boot boot.img
target didn't report max-download-size
sending 'boot' (26405 KB)...
FAILED (command write failed (No error))
finished. total time: 0.001s
C:\android>fastboot flash system system.img
< waiting for any device >
target reported max download size of 536870912 bytes
I am getting the above error but it proceeds to do all other commands. Then I get hung up at the Google screen. Any suggestions? I can get into the bootloader. I've tried the fastboot commands twice now...same result
Click to expand...
Click to collapse
Yes! Your using an old ADB / Fastboot combo...
See my post here: http://forum.xda-developers.com/showpost.php?p=69578798&postcount=74
Post if that does not resolve.
Also stop using wildcards "*". Use absolute paths.

chapelfreak said:
In the op in bold, he said it will not erase your data or apps
Click to expand...
Click to collapse
That was not in the original post. I screenshot the OP, the part about adding a kernel or custom ROM at the bottom was also added. But thanks for the update.

wx9kvh said:
That was not in the original post. I screenshot the OP, the part about adding a kernel or custom ROM at the bottom was also added. But thanks for the update.
Click to expand...
Click to collapse
That makes sense, our posts are an hour apart or so.

Scott said:
Yes! Your using an old ADB / Fastboot combo...
See my post here: http://forum.xda-developers.com/showpost.php?p=69578798&postcount=74
Post if that does not resolve.
Also stop using wildcards "*". Use absolute paths.
Click to expand...
Click to collapse
I appreciate the help. The link you provided me, I've downloaded it, but for some reason cant launch the app after I unzip the file. I've been at this for like 4 hours. I've tried so many different things and can't get past the Google screen. Please help

I was able to utilize the old tool. I'm all set. Thanks

chapelfreak said:
That makes sense, our posts are an hour apart or so.
Click to expand...
Click to collapse
Lol. No big deal haha.

Scott said:
Yes! Your using an old ADB / Fastboot combo...
See my post here: http://forum.xda-developers.com/showpost.php?p=69578798&postcount=74
Post if that does not resolve.
Also stop using wildcards "*". Use absolute paths.
Click to expand...
Click to collapse
Scott...can I flash the radio.img from V to the Verizon X. This radio is horrible

ADB Sideload Works too
Alternatively, use the instructions found on this page followed by a re-flash of your preferred kernel and a fastboot boottoroot to regain root.
https://developers.google.com/android/nexus/ota

So i just followed all of these instructions, and when going into about phone, it shows that i am now on an N build and still with the October security patch. What did i miss?
Update :
I believe I fixed the issue. The little window with the commands in it for some reason had scrolled up and I missed the flashing the "bootloader-marlin-*" step.
Update 2 :
I am now on X with the November security update. GREAT GUIDE!

Followed it to a T and soft bricked mine so now trying to find a way to fix or toss it out the windows haha. Just a heads up guys.
Ended up using the skipsoft tool and pushing a factory update same results but lost data/apps no biggie.

This is odd i followed the instructions trying to flash X to my phone coming from NDE63P and somehow ended up on NDE63N (Ignore this i missed a command)

What steps do I need to add if I want to completely restore back to factory settings (format userdata)? Or would it be the same to just factory reset through the newly restored stock recovery?

Cannot install any custom recovery on Asus ZB601KL

Hello!
I have Asus ZB601KL with officialy unlocked bootloader
I can't install any custom recovery, this is typical situation
Code:
[[email protected]~/Downloads/X00TD]$ platform-tools/fastboot flash revovery twrp-3.3.1-0-X00T-20190525.img
Sending 'revovery' (28852 KB) FAILED (remote: 'unknown command')
fastboot: error: Command failed
other version of fastboot shows me
Code:
[[email protected]~/Downloads/X00TD]$ ./fastboot flash revovery twrp-3.3.1-0-X00T-20190525.img
target reported max download size of 536870912 bytes
sending 'revovery' (28852 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.000s
How can i install recovery, help me please!

Vitaly T. said:
Hello!
I have Asus ZB601KL with officialy unlocked bootloader
I can't install any custom recovery, this is typical situation
other version of fastboot shows me
How can i install recovery, help me please!
Click to expand...
Click to collapse
+1 facing the same problem... Recently I found out it might be a port issue or a cable issue so i tried using my old laptop. Although it showed sending ok, writing ok but when i tried to get into recovery, it was the stock recovery. Try changing cables or using usb 2.0 ports. I didn't work for me but might work for you.
If possible please let me know how it went.

I have a bit different issue here
My phone is officially unlocked and updated to stock Pie 053
When I flash twrp via fastboot, it doesn't do anything, only blinking cursor
When I press ctrl+C to cancel it and reboot, it is still stock recovery
View attachment 4783849
Here is the twrp which I'm trying to flash
https://forum.xda-developers.com/as...ent/recovery-unofficial-twrp-3-2-3-0-t3888110

willysusilo said:
I have a bit different issue here
My phone is officially unlocked and updated to stock Pie 053
When I flash twrp via fastboot, it doesn't do anything, only blinking cursor
When I press ctrl+C to cancel it and reboot, it is still stock recovery
View attachment 4783849
Here is the twrp which I'm trying to flash
https://forum.xda-developers.com/as...ent/recovery-unofficial-twrp-3-2-3-0-t3888110
Click to expand...
Click to collapse
What does fastboot devices show?

jassalmithu said:
What does fastboot devices show?
Click to expand...
Click to collapse
Showing serial number of my phone like usual
When I entered "fastboot getvar all" it showed unlocked = yes

Is your CPU ryzen? If yes try it with another Intel CPU PC,and make sure you are enabled USB debugging in developer option and use USB 2.0 cable and port.