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.

Problem to install TWRP to the Huawei P8 with Mac OS X.

I am quite new to the android rooting & custom recovery and having a problem with my Huawei P8 GRA-UL00 flashing (purchased from China), when I try the procedure with MAC OS X. My step by step actions and result was as follows:
1. I installed "SDK Tools Only" for Mac. Connected the device via USB, launched terminal and successfully see the device with the "adb devices" command.
2. Vol +, Vol- and Power didn't work to enter to the fastboot&rescure mode. However, Vol- and Power worked. (Also, Vol+ and Power enters to the Huawei eRecovery mode, which shows EMUI logo, Reboot, Download new version and recovery and Shutdown buttons. I guess this is stock recovery???)
3. In the fastboot mode, I have successfully seen the device with "fastboot devices". Then I unlocked the bootloader with the code. The first problem was here, there were no auto-reboots and I entered "fastboot reboot" command, and stuck in seeing "reboooting..." in terminal. Nothing happened after this command. After 10 minutes I manually rebooted the phone by pressing power and entered into the fastboot mode. I was written as "Phone Unlocked". (Do u think it was really successful?)
4. I tried to flash the TWRP file which was uploaded by @jniklast (openrecovery-twrp-2.8.7.0-p8-ul10-r4.img). The result was like that:
MacBook-Airlatform-tools go$ ./fastboot flash recovery openrecovery-twrp-2.8.7.0-p8-ul10-r4.img
target reported max download size of 471859200 bytes
sending 'recovery' (25566 KB)...
OKAY [ 0.703s]
writing 'recovery'...
OKAY [ 0.353s]
finished. total time: 1.056s
MacBook-Airlatform-tools go$
5. Tried fastboot reboot, but I wasn't successful:
MacBook-Airlatform-tools go$ ./fastboot reboot-bootloader
rebooting into bootloader...
ERROR: usb_read failed with status e00002ed
FAILED (status read failed (No such file or directory))
finished. total time: 0.121s
MacBook-Airlatform-tools go$
I am not sure if I have correctly defined my problem. I guess I wasn't successful to install TWRP even it says so. What should I do after finishing the flash recovery command?
Can anyone help me with this error?

@landros57 That recovery is only for Android 5.1.1 beta version. You should flash the @jniklast 's GRA-L09 version of TWRP which is for Android 5.0.

I'm not quite sure what the problem is? You enter rescue mode via power + vol- so that's correct. You enter recovery via power + vol- and vol+ so what happens if you do that after flashing TWRP? And better not use the adb command go voot into recovery as that will lead to a bootloop to recovery which has to be broken by manually booting into it once.

samusalo said:
@landros57 That recovery is only for Android 5.1.1 beta version. You should flash the @jniklast 's GRA-L09 version of TWRP which is for Android 5.0.
Click to expand...
Click to collapse
Thank you samusalo.. Then I understand that TWRP for GRA-L09 can work on a GRA-UL00. I will try.
jniklast said:
I'm not quite sure what the problem is? You enter rescue mode via power + vol- so that's correct. You enter recovery via power + vol- and vol+ so what happens if you do that after flashing TWRP? And better not use the adb command go voot into recovery as that will lead to a bootloop to recovery which has to be broken by manually booting into it once.
Click to expand...
Click to collapse
I don't use adb reboot, I manually press Vol - and Power. Then, the Fastboot & Rescue mode opens, and I enter to the terminal "fastboot flash recovery openrecovery-twrp-2.8.7.0-p8-ul10-r4.img". It quickly shows that the installation is successful. Then I enter fastboot reboot-bootloader (I guess this is required to launch TWRP) but it shows that usb read error.

@jniklast and @samusalo thank you for your explanations. They both worked.
I flashed the GRA-L09 version of the TWRP to my GRA-UL00 and it worked! Now I have a backup...
I also realized that I am doing something wrong.. After installing TWRP, I was trying to fastbot reboot-boatloader in order to get TWRP launched automatically. However, the only thing I need to do is to follow jniklast's instructions and after the phone shut down, press Vol+ Vol- and Power together to get the TWRP launch.
Now I will try to flash an official International ROM, instead of my Chinese ROM.
Is the following command correct for this?
fastboot flash system "HUAWEI P8 Firmware(GRA-UL00&UL10,Android5.0,Emtion UI 3.1,V100R001C900B141,General Version).zip"

No, you need to extract the img files to be able to flash it via fastboot. Look for huawei image extractor

jniklast said:
No, you need to extract the img files to be able to flash it via fastboot. Look for huawei image extractor
Click to expand...
Click to collapse
Many .img files exists in the update.app file. I guess I need to flash only the system.img?
If I flash the recovery.img or boot.img inside the update.app, will I lose the custom recovery and my backup?

I'd first try to only flash system.img. If that doesn't work also flash boot.img. it might be though that you have to flash another cust.img as well and I'm not quite sure if that's possible via fastboot. In that case you'd have to do it via TWRP which is a bit tricky

Partially Successful
jniklast said:
I'd first try to only flash system.img. If that doesn't work also flash boot.img. it might be though that you have to flash another cust.img as well and I'm not quite sure if that's possible via fastboot. In that case you'd have to do it via TWRP which is a bit tricky
Click to expand...
Click to collapse
Flashing boot and system was successful! Then, again, my "fastboot reboot-bootloader" didn't work and retured me my initial error. But I rebooted manually and successfully launched my phone OS.
I now have a slow-operating new Android firmware, which is a little weird )) I think it is now a international&chinese hybrid version. Some apps disappeared and I have a complete new page for google services and apps. However, my chinese stuff (baidu spotlight search, notifications, etc.) remains The EMUI Build is: GRA-UL00V100R001C00B120, which should be V100R001C900B141 as I have flashed the img files of this update.
I tried "fastboot erase userdata", "fastboot erase cache" and "fastboot erase system" but they both returned with "FAILED (remote: Command not allowed)".
The following were my successful fastboot flash commands:
MacBook-Airlatform-tools go$ ./fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (23256 KB)...
OKAY [ 0.653s]
writing 'boot'...
OKAY [ 0.569s]
finished. total time: 1.222s
MacBook-Airlatform-tools go$ sudo ./fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' (459646 KB)...
OKAY [ 20.184s]
writing 'system'...
OKAY [ 6.149s]
sending sparse 'system' (450260 KB)...
OKAY [ 22.868s]
writing 'system'...
OKAY [ 6.051s]
sending sparse 'system' (437337 KB)...
OKAY [ 18.146s]
writing 'system'...
OKAY [ 5.952s]
sending sparse 'system' (460637 KB)...
OKAY [ 19.570s]
writing 'system'...
OKAY [ 6.267s]
sending sparse 'system' (448019 KB)...
OKAY [ 18.582s]
writing 'system'...
OKAY [ 5.982s]
sending sparse 'system' (165186 KB)...
OKAY [ 6.853s]
writing 'system'...
OKAY [ 2.206s]
finished. total time: 138.824s
MacBook-Airlatform-tools go$

jniklast said:
it might be though that you have to flash another cust.img as well and I'm not quite sure if that's possible via fastboot. In that case you'd have to do it via TWRP which is a bit tricky
Click to expand...
Click to collapse
I was finally successful to flash cust.img with fastboot and now I have B141 and all Chinese apps are removed. All Chinese ROM specific apps are disappeared and the only remaining Chinese stuff is the text in the Magazine Unlock, accessible when swiped up from the bottom of the screen at the lock screen.
The remaining problem for now is; when I press the Dialer, Contacts and Messages apps at the bottom, they crash.
Do I need to flash any other from the following extracted img files?
3RDMODEM.img
CACHE.img
CRC.img
CURVER.img
DTIMAGE.img
EFI.img
FASTBOOT.img
HIFI.img
MCUIMAGE.img
MODEM.img
MODEM_DSP.img
MODEMNVM_UPDATE.img
RECOVERY.img
RECOVERY2.img
SENSORHUB.img
SHA256RSA.img
TEEOS.img
TRUSTFIRMWARE.img
USERDATA.img
VERLIST.img
XLOADER.img

This is now delicate stuff, you could try and flash the radio (aka modem.img) but that will probably break connectivity as that is different in hardware. Maybe you'd need to install the dialer and messaging apks from the ul00 firmware. Does an alternate dialer work so that you can actually call someone?
And I think fastboot reboot-bootloader doesn't exist. It's either fastboot reboot bootloader or maybe only fastboot reboot. Anyway, booting into bootloader or recovery is better done by pressing the keys on the P8

jniklast said:
This is now delicate stuff, you could try and flash the radio (aka modem.img) but that will probably break connectivity as that is different in hardware. Maybe you'd need to install the dialer and messaging apks from the ul00 firmware. Does an alternate dialer work so that you can actually call someone?
And I think fastboot reboot-bootloader doesn't exist. It's either fastboot reboot bootloader or maybe only fastboot reboot. Anyway, booting into bootloader or recovery is better done by pressing the keys on the P8
Click to expand...
Click to collapse
Hello again,
Actually the hardware is the same, it is GRA-UL00. The device originally had: GRA-UL00-UL10_EMUI3.1_Android5.0_C00B173
I tried to fastboot the following ROM:
HUAWEI P8 Firmware(GRA-UL00&UL10,Android5.0,Emtion UI 3.1,V100R001C900B141,General Version)
I was successful to flash Root, CUST and System but when I try to flash any Modem-related img files (Modem.img, 3RDMODEM.img, MODEM_DSP.img, MODEMNVM_UPDATE.img), I get the following error:
sending 'modem' (38865 KB)...
OKAY [ 1.038s]
writing 'modem'...
FAILED (remote: Command not allowed)
finished. total time: 1.039s
I didn't try to install APKs.
I am still having crash problems with the dialer, contacts, messages, google play, and some other google services.

Network Mode FREEZE AUTO
Hi did you try checking Mobile Networks In Settings, As i m unable to open that. As soon as i click on it the network gets released and then comes back. THATS' ALL. I have the same phone and did the same stuff. Unable to Flash Modem.IMG as well.

Finally Done!
meetkhems said:
Hi did you try checking Mobile Networks In Settings, As i m unable to open that. As soon as i click on it the network gets released and then comes back. THATS' ALL. I have the same phone and did the same stuff. Unable to Flash Modem.IMG as well.
Click to expand...
Click to collapse
I finally succeeded.
After flashing the Boot.img, system.img and cust.img and launching the phone, I flashed the stock recovery and made a wipe/reset to factory settings. First, I extracted the recovery.img from the update.app file which you can find after downloading the official firmware and running the Huawei Update Extractor script available in the forum. Then I flashed this stock recovery.img in the fastboot mode. And finally I entered in the stock recovery (Huawei eRecovery) mode by pressing the Vol+, and Power buttons. After the wipe & reset to factory settings, I launched the phone and all problems with the radio, dialer, contacts, google services, etc were solved.
Thank you @jniklast for your help.

landros57 said:
I finally succeeded.
After flashing the Boot.img, system.img and cust.img and launching the phone, I flashed the stock recovery and made a wipe/reset to factory settings. First, I extracted the recovery.img from the update.app file which you can find after downloading the official firmware and running the Huawei Update Extractor script available in the forum. Then I flashed this stock recovery.img in the fastboot mode. And finally I entered in the stock recovery (Huawei eRecovery) mode by pressing the Vol+, and Power buttons. After the wipe & reset to factory settings, I launched the phone and all problems with the radio, dialer, contacts, google services, etc were solved.
Thank you @jniklast for your help.
Click to expand...
Click to collapse
Thanks a lot but i m still facing the problem. As soon as i select Mobile networks in settings nothing opens just the network gets released "NO Service" & comes back. I m unable to open it to select Network Mode or to change apn. It is not greyed Out but still not opening rest everything is working beautifully. Please Help. @jniklast for your help.[/QUOTE]

meetkhems said:
Thanks a lot but i m still facing the problem. As soon as i select Mobile networks in settings nothing opens just the network gets released "NO Service" & comes back. I m unable to open it to select Network Mode or to change apn. It is not greyed Out but still not opening rest everything is working beautifully. Please Help. @jniklast for your help.
Click to expand...
Click to collapse
Just checked and realized that I also have the same problem. THe contents of the "Mobile Networks" button doesn't show up and it works like a reset button. When I press, it disconnects me from the network and then the it reconnects to the network automatically.

Any Update on this anyone? I am unable to use the phone as it drains a lot of battery on 3G and i cant change it to 2G as due to Blank Mobile Network Settings.

Guys I have one problem I want to flash stock recovery for P8 L09 but in cmd it fails like not allowed command anybody knows why ?

landros57 said:
Just checked and realized that I also have the same problem. THe contents of the "Mobile Networks" button doesn't show up and it works like a reset button. When I press, it disconnects me from the network and then the it reconnects to the network automatically.
Click to expand...
Click to collapse
Hi landro57 have you tried to flash the update.app file of 18 Kb from local update? Some owners of the P8 gra ul09 variant are using that file to debrand their P8s. The mobile networks problem you ae experiencing is the same some other people have turnaround with that trick. You should check with it and report back to us, because if that goes ok, it means no more china firmware on our P8 gra ul00, we can simply flash the international general P8 firmware V100R001C900B141.
Inviato dal mio SGP311 utilizzando Tapatalk

GryphonA said:
flash the update.app file of 18 Kb from local update
Click to expand...
Click to collapse
Hi GryphonA, I don't get it, which 18kb update.app file do you mean?
I got the same problem (no access to mobile networks settings) and I can't remember if I never had that access or it happened due to my rooting/cusomizing activities.
I have GRA-UL00C433B180. I flashed also C470B180 but that didn't solve the problem.
BTW: There are a lot of mobile network setting apps and widgets in the Play Store but all apps I tested show the same failure as the mobile network settings: There seems to be a network reset and nothing more.

[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?

Failed to load system.img for OS 7.1.1 on Nexus 6P

Hi,
I am currently flashing my Nexus 6P with OS 7.1.1
After executing flash-all.bat as suggested on Android factory images i get the below error:
"sending 'bootloader' (3532 KB)...
OKAY [ 0.103s]
writing 'bootloader'...
OKAY [ 0.202s]
finished. total time: 0.317s
rebooting into bootloader...
OKAY [ 0.081s]
finished. total time: 0.084s
sending 'radio' (48728 KB)...
OKAY [ 1.086s]
writing 'radio'...
OKAY [ 2.175s]
finished. total time: 3.267s
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.018s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate -1473177068 bytes
error: update package missing system.img
Press any key to exit..."
Can anyone help out in this? Not sure what does failed to allocate -1473177068 bytes means? How can I solve this.

Try flashing each IMG file manually.

Don't use the flash-all.bat program. Manually type in your fastboot commands.
Extract that big ZIP you have in the same folder with your flash-all.bat. You'll see a bunch of img files called vendor.img, system.img, etc.
Once extracted, run the following commands in order. Replace "partition" with the img file name. Example: fastboot format system
fastboot format partition (if it gives an error, try fastboot erase partition).
fastboot flash partition imgfile
fastboot format cache
fastboot reboot-bootloader
Examples of what things should look like:
fastboot format system
fastboot flash system system.img
fastboot format cache
fastboot reboot-bootloader
<once rebooted, shouldn't take more than 2 seconds>
fastboot format vendor
fastboot flash vendor vendor.img
fastboot format cache
fastboot reboot-bootloader
<again, reboot, ~2 seconds>
If at any time it says it can't format memory type or something similar, usually this is for bootloader, radio and boot partitions, use fastboot erase boot (fastboot erase bootloader, fastboot erase radio).
Do this for each of the files, except for userdata - don't even flash that, just format userdata and skip the flash userdata part.
Also, flash your recovery of TWRP, the latest, and make sure that you boot to recovery first, before you boot the phone all together.

Did you verify the checksum of the image?

DON'T DO THAT...
Wiltron said:
fastboot erase bootloader
Click to expand...
Click to collapse
This will be your last fastboot command... Phone bricked.
To the OP, you should solve your flash-all problem as this script is the recommended way to flash factory images. You need some disk space (like 4 or 5GB)

rchtk said:
DON'T DO THAT...
This will be your last fastboot command... Phone bricked.
Click to expand...
Click to collapse
As long as you flash the bootloader again prior to rebooting you're fine.
I do this weekly with new builds of various ROMs.

Wiltron said:
As long as you flash the bootloader again prior to rebooting you're fine.
I do this weekly with new builds of various ROMs.
Click to expand...
Click to collapse
I find it way too risky tbh and don't see any added value in doing this.

rchtk said:
I find it way too risky tbh and don't see any added value in doing this.
Click to expand...
Click to collapse
Yeah, no reason to advise this. Especially in a thread of someone who may or may not be comfortable using fastboot. Risk > Reward 100%
Not like any 'gremlins' get left behind when updating a bootloader.
OP, just read and follow the beginner sticky thread and you'll do just fine. This one.

RoyJ said:
Yeah, no reason to advise this. Especially in a thread of someone who may or may not be comfortable using fastboot. Risk > Reward 100%
Not like any 'gremlins' get left behind when updating a bootloader.
OP, just read and follow the beginner sticky thread and you'll do just fine. This one.
Click to expand...
Click to collapse
Thank you RoyJ.....it worked

I did the "fastboot flash system system.img" and it says "FAILED <remote: data too large>. Never have any problem with the monthly updates before.

wormbaby11 said:
I did the "fastboot flash system system.img" and it says "FAILED <remote: data too large>. Never have any problem with the monthly updates before.
Click to expand...
Click to collapse
Googling wasn't much help in this case, found threads mostly for old HTC phones around 2013. However I did find one user trying to install 7.1 on his 5X which was able to solve his own issue by updating his Android tools in the SDK.
If you don't already have it, download and install the Android SDK. Follow the link I posted above and there's a section about how to install it.
Open the SDK Manager and under the section named "Tools" you should see; "Android SDK Tools" & "Android SDK Platform-tools".
Check to see if there's an update. I just noticed there is an available update on my PC. SDK Tools & SDK Platform-tools updated versions are 25.2.3 & 25.0.1, respectively. Update and reboot your PC and that should solve your issue. Let us know if that works for you.
Edit: Also, this is more than just a monthly security update. It was a bump up from 7.0.0 to 7.1.1. In any version bump like that, it never hurts to make sure the SDK is up to date.

Thanks Roy, that did the trick.
RoyJ said:
Googling wasn't much help in this case, found threads mostly for old HTC phones around 2013. However I did find one user trying to install 7.1 on his 5X which was able to solve his own issue by updating his Android tools in the SDK.
If you don't already have it, download and install the Android SDK. Follow the link I posted above and there's a section about how to install it.
Open the SDK Manager and under the section named "Tools" you should see; "Android SDK Tools" & "Android SDK Platform-tools".
Check to see if there's an update. I just noticed there is an available update on my PC. SDK Tools & SDK Platform-tools updated versions are 25.2.3 & 25.0.1, respectively. Update and reboot your PC and that should solve your issue. Let us know if that works for you.
Edit: Also, this is more than just a monthly security update. It was a bump up from 7.0.0 to 7.1.1. In any version bump like that, it never hurts to make sure the SDK is up to date.
Click to expand...
Click to collapse

Glad to hear you got it working!

[Guide] Fool/Noob proof way to do clean installs on Nexus Devices
http://forum.xda-developers.com/nexu...talls-t3518311
try this clean install should work

brickwd nova?

i did all ok for some weeks. But one day phone was discharged and after charge i got a black screen. Sometimes it flashes a bit depending on the boot and i can get some sound if i push volume down or up.
i tried fastboot or adb but no devices. (how can i force connection?). I went to the huawei shop they somehow restarted it and i could the the different booting option but they reboot it and they told me they couldn t do anything about because of the rom. I asked to redo what they have done and leave it to the reboot option so i could probably manage it from this point, but they told me it was not possible. So back home i tried everything but no success. How do i force the reboot from my computer with which softs?
tks
update
i do
adb devices
List of devices attached
GGXDU1721001169 recovery
if i do adb reboot-bootloader
i still have black screen
and fastboot devices gives
no permissions f astboot
how can i grant permission?
what command should i use? i tried a recovery but didn t work either think i t is an permission issue
tks

update
so i did
$ sudo fastboot devices
[sudo] password for xxxx:
GGXDU1721001169 fastboot
[email protected] ~ $ cd Downloads
[email protected] ~/Downloads $ sudo fastboot devices
GGXDU17210001169 fastboot
[email protected] ~/Downloads $ sudo fastboot flash recovery recovery.img
target reported max download size of 532676608 bytes
sending 'recovery' (34228 KB)...
OKAY [ 0.848s]
writing 'recovery'...
OKAY [ 0.785s]
finished. total time
[email protected] ~/Downloads $ sudo fastboot reboot
rebooting...
finished. total time: 0.053s
and still black screen?????
is it hardware issue?
is it possible somehow to reinstall a rom but usting the computer?

yes you can like you have flashed recovery, do the same thing with boot.img and system.img
extract them with update extracter from the full rom

Same with my CAZ-AL10, I guess it's because of missing drivers(*.so)

zaabolla said:
yes you can like you have flashed recovery, do the same thing with boot.img and system.img
extract them with update extracter from the full rom
Click to expand...
Click to collapse
ｔｋｓ
sorry i m not clear about the method. do i use the same recovery img? from this image i extract the boot ant the system img? and once i use fasboot? same commands?
tks

fastboot flash (system system.img) (boot boot.img)
Yes, extract from the same file you got the recovery from.

if your Nova be supported by fast boot command so it can be fix. don't worry. just find the correct rec , boot , system ...
my Nova l11 bricked like u before , i try many many method ... and help by mod hen.... in 2 day ... done ... everything alrigth ... now i can change 2 rom stock , LOS 14 so easy ....
good luck bro .

do you use image extractor? it seems it only use update image, or do you use another soft to extract it?
tks

Is there a way to wipe or reset TWRP from fast boot. i m also trying to see where the error comes from. how can i see the logs with my computer?
tks

If you want to get rid of twrp then flash stock recovery.img in fastboot.

babysocola1x said:
if your Nova be supported by fast boot command so it can be fix. don't worry. just find the correct rec , boot , system ...
my Nova l11 bricked like u before , i try many many method ... and help by mod hen.... in 2 day ... done ... everything alrigth ... now i can change 2 rom stock , LOS 14 so easy ....
good luck bro .
Click to expand...
Click to collapse
bro my nova l11 bricked update installing stuck at 5% fastboot mode status is phone locked can you please guide me to unbrick my phone?

abuapka said:
bro my nova l11 bricked update installing stuck at 5% fastboot mode status is phone locked can you please guide me to unbrick my phone?
Click to expand...
Click to collapse
1st get unlock code from huawei site for your phone
( need serial number..., find them)
Second, find the appropriate firmware for your model
Third extract update.app with huawei update extractor
Now you will have boot.img, recovery.img and system.img
In fastboot mode unlock the bootloader with your code
Then flash each file with it's fastboot command

i
zaabolla said:
1st get unlock code from huawei site for your phone
( need serial number..., find them)
Second, find the appropriate firmware for your model
Third extract update.app with huawei update extractor
Now you will have boot.img, recovery.img and system.img
In fastboot mode unlock the bootloader with your code
Then flash each file with it's fastboot command
Click to expand...
Click to collapse
where can i use the code? because on fastboot mode there is no option except
phone locked
and second connect hisuit using usb cable etc.
but when i try to connect hisuit with usb phone didnt recognized by hisuit in laptop
one more thing when i connect my phonr with dsta cable on fastboot mode adb devices didnt show any device jyst because i didnt enable usb debugging in developer mode because my phone is new i didnt change anything just try to update using firmware finder app and stuck on 5% cant even start my phone its stuck on bootloop i can go to fastboot mode recovery mode. also try to update using sd card but didnt work kindly guide me