Database Users

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

Unable to format in TWRP

When I try to wipe internal it says
Code:
Wiping internal storage -- /data/media...
Error opening: '/data/media' (No such file or directory)
When I try to format instead - I get even more errors:
Code:
Formatting Data using make_ext4fs...
Failed to mount '/data' (Device or resource busy)
Failed to mount '/data' (Device or resource busy)
Unable to recreate /data/media folder.
You may need to reboot recovery to be able to use /data again.
Updating partition details...
Failed to mount '/data' (Device or resource busy)
...done
Is this because of encryption? And if so - this is weird because I never encrypted my device. I currently have no OS and just trying to unsoftbrick my phone.

specialk00 said:
...Is this because of encryption? And if so - this is weird because I never encrypted my device. I currently have no OS and just trying to unsoftbrick my phone.
Click to expand...
Click to collapse
Use fastboot and make sure you are using the latest binaries. Format system, userdata and cache. Upon booting for the first time, the 6P automatically defaults to encryption- unless you intervene and stop it from doing so.

v12xke said:
Use fastboot and make sure you are using the latest binaries. Format system, userdata and cache. Upon booting for the first time, the 6P automatically defaults to encryption- unless you intervene and stop it from doing so.
Click to expand...
Click to collapse
Yep, I just fixed it somehow, I think it was related to MTP in TWRP. However now I'm stuck with a different issue. No matter what I flash in fastboot - I get
Code:
C:\Users\Nexusflip\AppData\Local\Android\sdk\platform-tools>fastboot flash recovery D:\Downloads\angler\twrp-3.1.1-0-angler.img
target didn't report max-download-size
sending 'recovery' (16948 KB)...
FAILED (command write failed (No error))
finished. total time: 0.003s
I always get this weird "No error" thing.

specialk00 said:
Yep, I just fixed it somehow, I think it was related to MTP in TWRP. However now I'm stuck with a different issue. No matter what I flash in fastboot - I get
Click to expand...
Click to collapse
Are you sure you are using the latest binaries? Hash checked the TWRP file? Put TWRP img in your fastboot folder? Format/erase recovery partition?

v12xke said:
Are you sure you are using the latest binaries? Hash checked the TWRP file? Put TWRP img in your fastboot folder? Format/erase recovery partition?
Click to expand...
Click to collapse
Yes I'm using the latest binaries - I got them via Android SDK and updated everything. I checked the ones you linked and they are exactly the same.
Regarding the hash check - this has nothing to do with the file being corrupted. This happens with ANY file I try to flash.
I tried putting the TWRP img in my fastboot folder and the results are the same.
Erasing the recovery partition gives the same error.
Code:
C:\Users\username\AppData\Local\Android\sdk\platform-tools>fastboot erase recovery
erasing 'recovery'...
FAILED (command write failed (No error))
finished. total time: 0.009s

specialk00 said:
Yes I'm using the latest binaries - I got them via Android SDK and updated everything. I checked the ones you linked and they are exactly the same. Regarding the hash check - this has nothing to do with the file being corrupted. This happens with ANY file I try to flash. I tried putting the TWRP img in my fastboot folder and the results are the same. Erasing the recovery partition gives the same error.
Click to expand...
Click to collapse
Were you able to successfully fastboot format userdata, system and cache with no errors? Did you get the same error using format as you did erase recovery? Is your phone bootlooping ? If yes, then your phone may have the BLOD. There are a few instances of users still having access to recovery mode, but not being able to flash anything. If you flash a full stock image with flash-all.bat, it finishes but the phone still loops then you likely have the BLOD.

v12xke said:
Were you able to successfully fastboot format userdata, system and cache with no errors? Did you get the same error using format as you did erase recovery? Is your phone bootlooping ? If yes, then your phone may have the BLOD. There are a few instances of users still having access to recovery mode, but not being able to flash anything. If you flash a full stock image with flash-all.bat, it finishes but the phone still loops then you likely have the BLOD.
Click to expand...
Click to collapse
I tried minimal adb & fastboot (bit older version) and got this.
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp-3.1.1-0-angler.img
target didn't report max-download-size
sending 'recovery' (16948 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 0.007s
Then I tried another old version of fastboot - got one from july 2016 (23.0.1) and nothing happened when executing flash or format commands.
Then I tried normal, latest fastboot and both (new & old) versions of fastboot gave me this error.
Code:
C:\Users\Nexusflip\AppData\Local\Android\sdk\platform-tools>fastboot erase userdata
erasing 'userdata'...
FAILED (command write failed (No error))
finished. total time: 0.023s
Then I tried to format (instead of erase)
Code:
C:\Users\Nexusflip\AppData\Local\Android\sdk\platform-tools>fastboot format userdata
FAILED (command write failed (No error))
I don't know if my phone is bootlooping because I don't have OS installed and my internal storage is squeaky clean. All this crap didn't just start out of nowhere - I flashed 8.0.0 dev preview 2 images through TWRP. I know I'm not the brightest. When I launch flash-all.bat it's just blank and does nothing at all.

specialk00 said:
I don't know if my phone is bootlooping because I don't have OS installed and my internal storage is squeaky clean. All this crap didn't just start out of nowhere - I flashed 8.0.0 dev preview 2 images through TWRP. I know I'm not the brightest. When I launch flash-all.bat it's just blank and does nothing at all.
Click to expand...
Click to collapse
It sounds to me like your internal storage (memory) is bad. Bottom line is that if you can't format your basic partitions successfully, you will not be able to flash a full ROM. If you don't believe your memory is bad, you can search the 6P forums for the Qualcomm Flash Image Loader (QFIL) & EDL mode. There is a rescue binary for the 6P floating around that some people have been successful in using restoring corrupt partitions, presumably because it works at the hardware level.

v12xke said:
It sounds to me like your internal storage (memory) is bad. Bottom line is that if you can't format your basic partitions successfully, you will not be able to flash a full ROM. If you don't believe your memory is bad, you can search the 6P forums for the Qualcomm Flash Image Loader (QFIL) & EDL mode. There is a rescue binary for the 6P floating around that some people have been successful in using restoring corrupt partitions, presumably because it works at the hardware level.
Click to expand...
Click to collapse
What should I do from now on? I have no idea what to do. The device has been bricked for 24 hours now.
This is the closest I've found to my problem. Also on a Nexus 6P. https://forum.xda-developers.com/nexus-6p/help/zip-file-signature-verification-error-t3561054
I tried adb reboot edl and it says error: closed. So not even that works.

specialk00 said:
What should I do from now on? I have no idea what to do. The device has been bricked for 24 hours now. This is the closest I've found to my problem. Also on a Nexus 6P. https://forum.xda-developers.com/nexus-6p/help/zip-file-signature-verification-error-t3561054
I tried adb reboot edl and it says error: closed. So not even that works.
Click to expand...
Click to collapse
Stock fastboot does not support boot to EDL. You need a modified fastboot, BUT getting to EDL mode won't help you until you have all the proper tools and 6P specific files. I don't want to get your hopes up. I think your device is not recoverable due to a hardware issue (bad memory). If you are looking for a learning project to keep you busy with very little hope of success, keep digging. If you need a working phone, you need to buy another one, or a 6P replacement motherboard from a screen damaged parts phone. Unfortunately, there have been many onboard memory failures on the 6P.

I fixed the problem. It turned out to be a faulty USB-C to USB-A cable. The only problems were with file transfer-related commands. I then tried transferring a 1 kb file, then 1 mb (failed) then 200kb, then 300kb (failed). So it turns out the cable is ****ty. Wow. And nothing is corrupted. I'm typing this from my phone now.

Did I just lose all my data?

Today after a successful OTA manual upgrade(downloaded latest zip and flashed) I decided to reinstall TWRP in order to reroot. However, after running first "fastboot flash recovery twrp.zip" then "fastboot boot twrp.zip", I am no longer prompted to enter my passcode(which I know) to decrypt the device, and the /system partition is empty in the TWRP file manager. The sdcard partition is filled with my encrypted files(assuming by their base64 names).
I dont think any of my actions in TWRP were significant, except possibly when I flashed the twrp.zip to have the recovery be persistent. (When I launched TWRP for the first time, I wasn't prompted for my password to decrypt then either, so I assume the damage was already done)
I have tried "twrp decrypt [password]" in the twrp terminal but I get "Failed to decrypt data"
A. Is there a way to reflash my system(e.g Can I just flash the same update.zip) and be back to normal
Or B. Can I retrieve and decrypt my data, given that I know my lockscreen passcode which is normally used to decrypt it.
Here is everything I wrote in my command prompt(Can't post links):
E:\Coding\OnePlus>fastboot
-snip fastboot help-
E:\Coding\OnePlus>fastboot flash recovery twrp-installer-fajita-3.2.3-2.zip
target reported max download size of 536870912 bytes
sending 'recovery' (16693 KB)...
OKAY [ 0.359s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 0.364s
E:\Coding\OnePlus>fastboot boot twrp-installer-fajita-3.2.3-2.zip
creating boot image...
creating boot image - 17096704 bytes
downloading 'boot.img'...
OKAY [ 0.361s]
booting...
OKAY [ 0.092s]
finished. total time: 0.455s
E:\Coding\OnePlus>fastboot devices
d535eae7 fastboot
E:\Coding\OnePlus>fastboot boot twrp-installer-fajita-3.2.3-2.zip
creating boot image...
creating boot image - 17096704 bytes
downloading 'boot.img'...
OKAY [ 0.361s]
booting...
FAILED (status read failed (Too many links))
finished. total time: 0.456s
E:\Coding\OnePlus>fastboot flash recovery twrp-installer-fajita-3.2.3-2.zip
< waiting for device >
^C
E:\Coding\OnePlus>fastboot devices
E:\Coding\OnePlus>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
d535eae7 recovery
E:\Coding\OnePlus>adb flash
-snip adb help-
E:\Coding\OnePlus>adb push twrp-installer-fajita-3.2.3-2.zip /data
7500 KB/s (17094317 bytes in 2.225s)
E:\Coding\OnePlus>
Click to expand...
Click to collapse

As you learned from the first command there is no recovery partition, you can't flash like that. Your data is on a different partition, so it should be ok (pictures and such, I'm assuming that's what you are worried about)
Next I don't know what ROM or OS you are using, but if it's a current one, you will need a newer version of TWRP. Download 3.3.1-6 or 3.3.1-7 from this thread (link) You need the IMG file first. Run:
fastboot boot twrp-3.3.1-6-fajita.img (Or -7 if you download -7)
Hopefully that will ask you for your password and decrypt all your data. At this point backup your data. Then I would dirty flash your ROM as it's hard to say what you did with all that flashing up above. Then run the TWRP installer. Then Reboot to recovery, flash magisk (If this was a custom ROM, remeber to also re-flash Gapps). Just like you were doing a regular update. Hopefully that fixes everything.

jonesbeverly44 said:
Today after a successful OTA manual upgrade(downloaded latest zip and flashed) I decided to reinstall TWRP in order to reroot. However, after running first "fastboot flash recovery twrp.zip" then "fastboot boot twrp.zip", I am no longer prompted to enter my passcode(which I know) to decrypt the device, and the /system partition is empty in the TWRP file manager. The sdcard partition is filled with my encrypted files(assuming by their base64 names).
I dont think any of my actions in TWRP were significant, except possibly when I flashed the twrp.zip to have the recovery be persistent. (When I launched TWRP for the first time, I wasn't prompted for my password to decrypt then either, so I assume the damage was already done)
I have tried "twrp decrypt [password]" in the twrp terminal but I get "Failed to decrypt data"
A. Is there a way to reflash my system(e.g Can I just flash the same update.zip) and be back to normal
Or B. Can I retrieve and decrypt my data, given that I know my lockscreen passcode which is normally used to decrypt it.
Here is everything I wrote in my command prompt(Can't post links):
Click to expand...
Click to collapse
Hello my friend. Did you ever find a solution to get your directory back? Mine looks like you explained now in TWRP and in a file manager. Like it was encrypted or something.

boobteg2 said:
Hello my friend. Did you ever find a solution to get your directory back? Mine looks like you explained now in TWRP and in a file manager. Like it was encrypted or something.
Click to expand...
Click to collapse
Fastboot the .IMG file not the .zip file, if it is encrypted then adb sideload or boot to system then fastboot again.

I am no longer prompted to enter my passcode(which I know) to decrypt the device, and the /system partition is empty in the TWRP file manager. The sdcard partition is filled with my encrypted files(assuming by their base64 names).
Click to expand...
Click to collapse
OnePlus uses FBE (File Based Encryption) which is why it looks like this. Just booting TWRP doesn't affect your data. As long as you're able to restore a working system partition and let phone boot your data should be accessible, but _only_ once phone fully boots.

having some trouble flashing the magisk patched image

(edit: is my device bricked? it won't load Android now, but is in fastboot
also should i have updated Android first?
i'm thinking of keeping it stock at this point, or maybe finish rooting if possible.)
copied below is what i put in Command Prompt
and then tried downloading adb and fastboot again
i downloaded a fresh factory image for my version
and followed these instructions
How to root the Google Pixel 4 or Pixel 4 XL with Magisk
Looking to root your Google Pixel 4 or Pixel 4 XL? Here's how to unlock the bootloader and root the latest 2019 Pixel smartphones!
www.xda-developers.com
here's what i did:
fastboot flash boot "C:\path\magisk_patched-25200_NVE3j.img"
target reported max download size of 268435456 bytes
sending 'boot' (65536 KB)...
OKAY [ 2.199s]
writing 'boot'...
FAILED (remote: Failed to write to partition Not Found)
finished. total time: 2.348s
adb reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device '(null)' not found
C:\adb>
C:\adb>fastboot reboot fastboot
usage: fastboot [ <option> ] <command>
commands:
then i got the latest platform-tools, because i had installed some other ADB and Fastboot from XDA in an installer with some Google Drivers.
fastboot flash boot "C:\path\magisk_patched-25200_NVE3j.img"
Sending 'boot_a' (65536 KB) OKAY [ 2.355s]
Writing 'boot_a' (bootloader) Image missing OS version
OKAY [ 0.424s]
Finished. Total time: 3.129s
I also downloaded drivers from Google but i'm not sure how to install the DLL file until the device is out of Fastboot?
I tried using the menu to boot to Recovery. Didn't work.
In Device Manager, should i select Android Bootloader Interface to update to this driver?
Or wait until i can select it as a normal Android device after if it's possible to boot it normally?
And what about the website Flash.Android.com? could that get me to stock safely? but not rooted.

Sanman99 said:
copied below is what i put in Command Prompt
and then tried downloading adb and fastboot again
i downloaded a fresh factory image for my version
and followed these instructions
How to root the Google Pixel 4 or Pixel 4 XL with Magisk
Looking to root your Google Pixel 4 or Pixel 4 XL? Here's how to unlock the bootloader and root the latest 2019 Pixel smartphones!
www.xda-developers.com
here's what i did:
fastboot flash boot "C:\path\magisk_patched-25200_NVE3j.img"
target reported max download size of 268435456 bytes
sending 'boot' (65536 KB)...
OKAY [ 2.199s]
writing 'boot'...
FAILED (remote: Failed to write to partition Not Found)
finished. total time: 2.348s
Click to expand...
Click to collapse
If the next thing you did was
Sanman99 said:
adb reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device '(null)' not found
Click to expand...
Click to collapse
then ADB wasn't running. Use fastboot devices to ensure your PC sees your phone before flashing
Sanman99 said:
C:\adb>
C:\adb>fastboot reboot fastboot
usage: fastboot [ <option> ] <command>
commands:
Click to expand...
Click to collapse
Correct syntax is adb reboot fastboot/bootloader/recovery
The way it works is like this:
Code:
<tool> <command> <instruction> <options>
where:
<tool> is what you are instructing to send the command to the device: ADB for Android system or recovery, fastboot for bootloader or fastbootd
<command> is what you want the device to do, i.e.: devices / reboot / flash / boot / erase / etc:
devices tells the tool to display connected ADB devices
reboot tells the device to reboot, can provide instruction for what mode you want it to reboot into, example: adb [B]reboot [/B]bootloader
flash can only be used in fastboot, tells the bootloader to flash the specified partition with the specified image, example: fastboot [B]flash [/B]boot <path to boot image
boot tells bootloader to immediately load the specified image without flashing, example: fastboot [B]boot [/B]TWRP.img
erase tells the bootloader to wipe the device; if no partition is specified, this will wipe user data. Use with extreme caution. Example: fastboot [B]erase [/B]data
<instruction> is the details for the command you're giving: adb reboot bootloader, fastboot flash boot <path to image>, fastboot boot <path to image>
<options> include details that may be necessary for various operations, example: fastboot update image-redfin-buildnumber.zip -w --skip-reboot --slot=all --force (this tells the bootloader to update using the specified update package, to wipe data, to not automatically reboot when done flashing, to flash both slots, and to ignore any baseband/bootloader requirements
<option> and <command> can be switched, for example: fastboot --skip-reboot --slot=all --force -w update image-redfin-buildnumber.zip
Sanman99 said:
then i got the latest platform-tools, because i had installed some other ADB and Fastboot from XDA in an installer with some Google Drivers.
fastboot flash boot "C:\path\magisk_patched-25200_NVE3j.img"
Sending 'boot_a' (65536 KB) OKAY [ 2.355s]
Writing 'boot_a' (bootloader) Image missing OS version
OKAY [ 0.424s]
Finished. Total time: 3.129s
Click to expand...
Click to collapse
It's always important to make sure you're using the latest ADB platform tools.
What happened after you successfully flashed the patched image?

V0latyle said:
If the next thing you did was
then ADB wasn't running. Use fastboot devices to ensure your PC sees your phone before flashing
Correct syntax is adb reboot fastboot/bootloader/recovery
The way it works is like this:
Code:
<tool> <command> <instruction> <options>
where:
<tool> is what you are instructing to send the command to the device: ADB for Android system or recovery, fastboot for bootloader or fastbootd
<command> is what you want the device to do, i.e.: devices / reboot / flash / boot / erase / etc:
devices tells the tool to display connected ADB devices
reboot tells the device to reboot, can provide instruction for what mode you want it to reboot into, example: adb [B]reboot [/B]bootloader
flash can only be used in fastboot, tells the bootloader to flash the specified partition with the specified image, example: fastboot [B]flash [/B]boot <path to boot image
boot tells bootloader to immediately load the specified image without flashing, example: fastboot [B]boot [/B]TWRP.img
erase tells the bootloader to wipe the device; if no partition is specified, this will wipe user data. Use with extreme caution. Example: fastboot [B]erase [/B]data
<instruction> is the details for the command you're giving: adb reboot bootloader, fastboot flash boot <path to image>, fastboot boot <path to image>
<options> include details that may be necessary for various operations, example: fastboot update image-redfin-buildnumber.zip -w --skip-reboot --slot=all --force (this tells the bootloader to update using the specified update package, to wipe data, to not automatically reboot when done flashing, to flash both slots, and to ignore any baseband/bootloader requirements
<option> and <command> can be switched, for example: fastboot --skip-reboot --slot=all --force -w update image-redfin-buildnumber.zip
It's always important to make sure you're using the latest ADB platform tools.
What happened after you successfully flashed the patched image?
Click to expand...
Click to collapse
thanks for the quick reply
and extensive yet clear
Yes i did: Fastboot Devices
and it shows the serial number
So when i tried flashing
It didn't flash though, did it? Does that look like it flashed?
When it took 2 or 3 seconds for a 64megabyte file from my computer, isn't on the phone itself.
And said: Image missing OS version
I checked online and other users have the same problem.
I'm stuck in Fastboot. I'm downloading Android SDK Studio and updated the USB Driver again.
I can't get into Recovery or the OS.
Enter reason: error boot prepare
when trying Recovery
I'm wondering if I should get GrapheneOS or if LineageOS is up to date on Pixel 4. I might not want to tinker as much anymore. I still might use the usual apps, but at least utilize root.
Should i be using a different USB cable/cord maybe?
I don't know if I have an OEM USB-c.

Sanman99 said:
thanks for the quick reply
and extensive yet clear
Yes i did: Fastboot Devices
and it shows the serial number
So when i tried flashing
It didn't flash though, did it? Does that look like it flashed?
Click to expand...
Click to collapse
When it says OKAY, that means it successfully flashed.
Sanman99 said:
When it took 2 or 3 seconds for a 64megabyte file from my computer, isn't on the phone itself.
And said: Image missing OS version
I checked online and other users have the same problem.
Click to expand...
Click to collapse
What version of Magisk are you using and where did you download it from?
You are using boot.img, not bootloader.img, right?
You're using the correct firmware for your phone (flame)?
Sanman99 said:
I'm stuck in Fastboot. I'm downloading Android SDK Studio and updated the USB Driver again.
I can't get into Recovery or the OS.
Enter reason: error boot prepare
when trying Recovery
Click to expand...
Click to collapse
It's starting to sound like you might be using the wrong image. Try reflashing the stock boot image (unpatched).
Sanman99 said:
I'm wondering if I should get GrapheneOS or if LineageOS is up to date on Pixel 4. I might not want to tinker as much anymore. I still might use the usual apps, but at least utilize root.
Click to expand...
Click to collapse
One step at a time, I think fixing this should be pretty easy.
Sanman99 said:
Should i be using a different USB cable/cord maybe?
I don't know if I have an OEM USB-c.
Click to expand...
Click to collapse
It's worth a try. Are you using a USB A to C cable, or just C to C? If you're using a C to C cable, try using A to C.
Also, I don't know if you've noticed, but I do have a guide for rooting your device here. Check out the "Initial Root" section to make sure you're doing everything right.

V0latyle said:
When it says OKAY, that means it successfully flashed.
What version of Magisk are you using and where did you download it from?
You are using boot.img, not bootloader.img, right?
You're using the correct firmware for your phone (flame)?
It's starting to sound like you might be using the wrong image. Try reflashing the stock boot image (unpatched).
One step at a time, I think fixing this should be pretty easy.
It's worth a try. Are you using a USB A to C cable, or just C to C? If you're using a C to C cable, try using A to C.
Also, I don't know if you've noticed, but I do have a guide for rooting your device here. Check out the "Initial Root" section to make sure you're doing everything right.
Click to expand...
Click to collapse
tried the (unpatched) factory boot image now
with a different USB cable (both are USB-A to USB-C)
C:\path>fastboot flash boot "C:\path\oriole-tp1a.221005.002-factory-f28b656e\oriole-tp1a.221005.002\image-oriole-tp1a.221005.002\boot.img"
Sending 'boot_a' (65536 KB) OKAY [ 1.627s]
Writing 'boot_a' (bootloader) Image missing OS version
OKAY [ 0.506s]
Finished. Total time: 2.465s
Yes i followed the steps
Here is what i originally did
Yes i downloaded a Magisk apk from the guide I mentioned which links to Github
and i updated the app after opening it
then patched the Boot.img and copied to my computer
I'm reading your thread now, which directed to this
[GUIDE] Pixel 4 "flame": Unlock Bootloader, Update, Root, Pass SafetyNet
If you are looking for my guide on a different Pixel, find it here: Pixel 3 Pixel 3XL Pixel 3a Pixel 3aXL Pixel 4XL Pixel 4a Pixel 4a (5G) Pixel 5 Pixel 5a Pixel 6 Pixel 6 Pro For best results, use the latest stable Magisk release. Discussion...
forum.xda-developers.com
Yes i downloaded the correct Factory image
I had enabled USB Debugging
and
yep i did the
fastboot flashing unlock
and this is where the problem happened
(well unrelated, i didn't rename the patched-boot.img)
fastboot flash boot <drag and drop master root.img here>
as i copied the output...it took like 2 seconds and gave that message saying something about the OS version
and i can't get ADB working...
Should I have used the PixelFlasher tool?
I don't know what went wrong or what to do now. As I said, some others have had this same error.
i just tried again with fastboot from the SDK directory
C:\Users\path\AppData\Local\Android\Sdk\platform-tools>fastboot flash boot "C:\Users\path\Downloads\oriole-tp1a.221005.002-factory-f28b656e\oriole-tp1a.221005.002\image-oriole-tp1a.221005.002\boot.img"
Sending 'boot_a' (65536 KB) OKAY [ 1.617s]
Writing 'boot_a' (bootloader) Image missing OS version
OKAY [ 0.491s]
Finished. Total time: 2.457s

It's hard to say exactly where you're going wrong. Did you mess with vbmeta at all? You should get no error messages when flashing the original boot image.
Have you tried to boot even after getting the error message?
Pixel Flasher is useful, but it's very important that you understand how everything works under the hood, because the tool just automates what we'd otherwise have to manually do, and the tool can't necessary fix problems.

V0latyle said:
It's hard to say exactly where you're going wrong. Did you mess with vbmeta at all? You should get no error messages when flashing the original boot image.
Have you tried to boot even after getting the error message?
Pixel Flasher is useful, but it's very important that you understand how everything works under the hood, because the tool just automates what we'd otherwise have to manually do, and the tool can't necessary fix problems.
Click to expand...
Click to collapse
(edit: you were right. it wasn't the right Flame image at all. it was Oriole.)
i don't know what vbmeta is.
I can't boot into anything but fastboot.
If I go on the Flash.Android.com website, should i flash to Android 12?
wait...what if it wasn't a Pixel 4 image
is there another that has tp1a.221005.002 ?
how can i check which one this is?
i know you said check if it says Flame
i know i was in the list for Pixel 4 flame when i was about to download
but i typed Ctrl+F and to search the right code
this is what i downloaded
https://dl.google.com/dl/android/aosp/oriole-tp1a.221005.002-factory-f28b656e.zip
---
ok.... here's Flame
https://dl.google.com/dl/android/aosp/flame-tp1a.221005.002-factory-f91d46b5.zip
so i just have to flash the Boot.img from this
and then patch it again, right?

Sanman99 said:
(edit: you were right. it wasn't the right Flame image at all. it was Oriole.)
Click to expand...
Click to collapse
Yeah, that's a pretty common problem.
Sanman99 said:
i don't know what vbmeta is.
Click to expand...
Click to collapse
Don't worry about it
Sanman99 said:
I can't boot into anything but fastboot.
Click to expand...
Click to collapse
Do you mean bootloader? What do you see on the screen? Any error message at the bottom?
Sanman99 said:
If I go on the Flash.Android.com website, should i flash to Android 12?
Click to expand...
Click to collapse
Just update to the latest version, if you haven't already.
Sanman99 said:
wait...what if it wasn't a Pixel 4 image
is there another that has tp1a.221005.002 ?
Click to expand...
Click to collapse
Yes - since the Pixel 3, Google has started using what are called common system images, where the core system build is exactly the same across the entire range of phones. That makes updates much easier, because instead of having to rebuild firmware every month with the source Android update, they can just update the system image, while device specific partitions such as /product, /system_ext, /vendor_boot etc can be updated periodically.
The downside to this is that the updates can be confusing...because the build number is almost exactly the same for every phone, from the Pixel 7 all the way down through the Pixel 4a (since the 4 / 4XL are no longer supported)
As an example, the latest 4a build number is TQ1A.230105.001, and it's exactly the same for the 4a 5g, 5, 5a, and 6a. The Pixel 6, and 6 Pro are TQ1A.230105.002, and the 7 / 7 Pro are TQ1A.230105.001.A2. So there's minor differences there but for the most part the system images are very similar.
Sanman99 said:
how can i check which one this is?
i know you said check if it says Flame
Click to expand...
Click to collapse
As long as it's for the Pixel 4 (flame) it should be OK. The factory images are named in this fashion: device-buildnumber-factory-hash.zip, so yours should be flame-TP1A.221005.002-factory-f91d46b5.zip
Sanman99 said:
i know i was in the list for Pixel 4 flame when i was about to download
but i typed Ctrl+F and to search the right code
this is what i downloaded
https://dl.google.com/dl/android/aosp/oriole-tp1a.221005.002-factory-f28b656e.zip
Click to expand...
Click to collapse
Yeah that's the wrong one
Sanman99 said:
ok.... here's Flame
https://dl.google.com/dl/android/aosp/flame-tp1a.221005.002-factory-f91d46b5.zip
Click to expand...
Click to collapse
Yep
Sanman99 said:
so i just have to flash the Boot.img from this
Click to expand...
Click to collapse
Yes. Just to make absolutely sure we are on the same page, when you download the file, you'll have the original zip (using barbet for my wife's phone as an example)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Extract this to its own folder, which will have another folder inside it with the bootloader image, radio image, scripts, and the system update:
Extract the "image-sunfish.tp1a.221005.002.zip" to its own folder:
In this folder will be the various images for the system update; the one you need is boot.img:
To get running again without root, just flash this:
fastboot flash boot <drag and drop the boot.img here>
Sanman99 said:
and then patch it again, right?
Click to expand...
Click to collapse
Yep...once you're booted into Android, copy the same boot.img to your phone, making sure to delete any old ones, then patch it in Magisk, copy the magisk-patched_25200-xxxxx.img back to your PC, then flash it the same way you did the boot image.

V0latyle said:
Yeah, that's a pretty common problem.
Don't worry about it
Do you mean bootloader? What do you see on the screen? Any error message at the bottom?
Just update to the latest version, if you haven't already.
Yes - since the Pixel 3, Google has started using what are called common system images, where the core system build is exactly the same across the entire range of phones. That makes updates much easier, because instead of having to rebuild firmware every month with the source Android update, they can just update the system image, while device specific partitions such as /product, /system_ext, /vendor_boot etc can be updated periodically.
The downside to this is that the updates can be confusing...because the build number is almost exactly the same for every phone, from the Pixel 7 all the way down through the Pixel 4a (since the 4 / 4XL are no longer supported)
As an example, the latest 4a build number is TQ1A.230105.001, and it's exactly the same for the 4a 5g, 5, 5a, and 6a. The Pixel 6, and 6 Pro are TQ1A.230105.002, and the 7 / 7 Pro are TQ1A.230105.001.A2. So there's minor differences there but for the most part the system images are very similar.
As long as it's for the Pixel 4 (flame) it should be OK. The factory images are named in this fashion: device-buildnumber-factory-hash.zip, so yours should be flame-TP1A.221005.002-factory-f91d46b5.zip
Yeah that's the wrong one
Yep
Yes. Just to make absolutely sure we are on the same page, when you download the file, you'll have the original zip (using barbet for my wife's phone as an example)
View attachment 5812273
Extract this to its own folder, which will have another folder inside it with the bootloader image, radio image, scripts, and the system update:
View attachment 5812283
Extract the "image-sunfish.tp1a.221005.002.zip" to its own folder:
View attachment 5812285
In this folder will be the various images for the system update; the one you need is boot.img:
View attachment 5812289
To get running again without root, just flash this:
fastboot flash boot <drag and drop the boot.img here>
Yep...once you're booted into Android, copy the same boot.img to your phone, making sure to delete any old ones, then patch it in Magisk, copy the magisk-patched_25200-xxxxx.img back to your PC, then flash it the same way you did the boot image.
Click to expand...
Click to collapse
yeah yeah sorry i didn't reply
and thanks so much for the explanation
i was busy setting up my phone
but realized GrapheneOS isn't supposed to have root anyways
so now i have to decide if I want a custom ROM or just Stock with root, or maybe GrapheneOS and whether to put Google services on it and a bunch of apps defeating its purpose in some ways
flashing the phone went very smoothly. Then i put GrapheneOS on it.
if you have any advice about which ROM to do, i'd appreciate it
lots of features are built into Stock now anyways
in that case, i'd just reflash the Magisk patched boot image and then lock the bootloader in settings again?
or i have to reinstall Stock entirely
maybe Android Flash Tool and not that Flash.Android.com
i've done this for multiple phones over the years but i guess i've never understood it thoroughly
i can check for a guide....(and follow it carefully lol)
awesome help. this saved me a bit of stress today.

Never ever lock the bootloader unless everything is 100% bone stock. Not even a patched image. If anything is modified, locking the bootloader will prevent the device from booting Android, and it may not be possible to unlock it again. I'll have more for you on ROMs in the morning, specifically GSIs.

V0latyle said:
Never ever lock the bootloader unless everything is 100% bone stock. Not even a patched image. If anything is modified, locking the bootloader will prevent the device from booting Android, and it may not be possible to unlock it again. I'll have more for you on ROMs in the morning, specifically GSIs.
Click to expand...
Click to collapse
Or I think I got that confused with the Settings menu OEM Unlock
Not the fastboot command.
I just did whatever the GrapheneOS instructions said.

Sanman99 said:
Or I think I got that confused with the Settings menu OEM Unlock
Not the fastboot command.
I just did whatever the GrapheneOS instructions said.
Click to expand...
Click to collapse
Well, GrapheneOS sets a custom root of trust, so as long as nothing is modified, you can relock the bootloader. You won't be able to have root, though. I generally advise against locking the bootloader unless you're on bone stock firmware.
As for ROMs, I don't have a lot of experience with custom ROMs, especially not in the past 6 years or so. My daily is a Pixel 5, and I'm pretty happy with the OEM firmware. I do have a Samsung tablet that I'm running an AOSP Developer Preview GSI on; I had tried LineageOS first, didn't like it that much, then figured out how to install a GSI. The Pixel 3 and newer should be Project Treble compliant, so you could potentially use a GSI if you wanted.
By the way, GSI = Generic System Image. The idea is that it can run on almost any device, utilizing the stock kernel, and does not require porting or any other customizations to get it to run on other devices.

[HELP] Z00TD/ZE551KL soft-bricked? No recovery mode, no OS, locked bootloader.

Hey guys, I need help with this Asus Zenfone 2 Laser that:
Cannot boot to any OS (asus logo pops up, freezes, and then a blue screen flashes for a really short period, before it powers off, see video here.)
Can't download the unlock app to unlock bootloader
Can't access ADB
Cannot access Recovery mode
Can't "factory reset", apply update over ADB, etc.
Bootloader is locked
Can't flash custom recovery, boot TWRP, or really anything...
See fastboot reference below for more info
Code:
$ fastboot boot twrp-3.7.0_9-0-Z00T.img
Sending 'boot.img' (31066 KB) OKAY [ 0.987s]
Booting FAILED (remote: 'unlock device to use this command')
fastboot: error: Command failed
$ fastboot flash recovery twrp-3.7.0_9-0-Z00T.img
Sending 'recovery' (31066 KB) OKAY [ 0.987s]
Writing 'recovery' FAILED (remote: 'Permission denied, phone is protected')
fastboot: error: Command failed
$ fastboot flash boot boot.img # (Original boot.img from factory image)
Warning: skip copying boot image avb footer (boot partition size: 0, boot image size: 17980722).
Sending 'boot' (17559 KB) OKAY [ 1.478s]
Writing 'boot' FAILED (remote: 'Permission denied, phone is protected')
fastboot: error: Command failed
$ fastboot flashing unlock
FAILED (remote: 'unknown command')
fastboot: error: Command failed
$ fastboot oem device-info
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.003s]
Finished. Total time: 0.003s
As someone who has only worked with Google Pixel phones in the past, I'm very frustrated for a few reasons.
Firstly, why the hell is the ONLY WAY to unlock a bootloader through an app that was released in such a clandestine, under-the-table way?
Second, why is the manufacturer gatekeeping the recovery files? The only way I was able to find the stock recovery.img is through a comment on a Reddit post (ironically posted by an ASUS Employee).
Third, I've been scouring the internet for many, many days trying to find any kind of emergency recovery method, but every single tutorial acts on the assumption that the bootloader is unlocked, and that boot.img, recovery.img, etc. can be flashed.
Enough about the frustration. Now let's talk about what I've tried so far.
I tried ASUS Flash Tool (Finding ADB drivers was a whole different fiasco for this device), and came up empty handed, as it doesn't detect the device when in fastboot mode.
I tried using fastboot to flash boot, recovery, system, fastboot, and dnx/ifwi, to no avail.
I tried booting into recovery via `fastboot reboot recovery`, `fastboot reboot-recovery`, `fastboot oem reboot-recovery`, and by holding Vol Down while booting up. They all give the same result, which is just an instant (<1 second) reboot. My best guess is that recovery.img is either missing or badly corrupt, so the bootloader just gives up and exits immediately.
Please help. I don't want an expensive paperweight sitting in my drawer just because of a bootloop that wasn't my fault (seriously this device just bootlooped itself one day, I didn't flash a custom rom, root or anything like that).
Any help is appreciated,
Thanks in advance

you can flash on locked bootloader in EDL mode. search in the forum, don't hesitate to ask for clarity on search results. I give you a starting point.
(don't read the whole thread, it will only confuse you)
https://forum.xda-developers.com/t/...image-dump-file-raw-bin.4543217/post-88139417

alecxs said:
you can flash on locked bootloader in EDL mode. search in the forum, don't hesitate to ask for clarity on search results. I give you a starting point.
(don't read the whole thread, it will only confuse you)
https://forum.xda-developers.com/t/...image-dump-file-raw-bin.4543217/post-88139417
Click to expand...
Click to collapse
Probably a dumb question, but how can I put my device into EDL mode?
I've tried many key combinations in conjunction with plugging it into the computer, and I've tried connecting it without a battery.

if nothing else works you need to figure out test points
https://forum.xda-developers.com/t/...ed-to-unlock-bootloader.4531349/post-87944673

you still have fastboot? try this for EDL mode.
Code:
fastboot oem enter-dload

Good news and bad news. Good news is: I was able to enter EDL mode.
Bad news is, apparently my entire partition scheme was messed up, and upon running "edl w gpt gptboth0.bin", fastboot no longer works.
I have tried flashing aboot using edl ("edl w aboot emmc_appsboot.mbn") and it's not working.
Not to mention that it is almost impossible to find the firmware file with all the factory files such as "emmc_appsboot.mbn". The place where I got my file seemed very sketchy and I'm not surprised if the reason it's not working is because it's the wrong file.
Once again, this is a result of ASUS gatekeeping their recovery files to service centers to drive up repair sales.
If anyone has a link, or would like to provide a donor file, it would be VERY much appreciated.

what is inside official download?
https://www.asus.com/supportonly/asus zenfone 2 laser (ze551kl)/helpdesk_bios

alecxs said:
what is inside official download?
https://www.asus.com/supportonly/asus zenfone 2 laser (ze551kl)/helpdesk_bios
Click to expand...
Click to collapse
So yes, I was able to get fastboot back. However, I am now facing another issue.
In order to get fastboot back, I had to run this command
Bash:
edl qfil rawprogram0.xml patch0.xml image_dir
This seemed fine at first, but now, running "edl printgpt" returns nothing. Somehow, the phone is able to boot to fastboot without any GPT partitions visible.
However, when I try to flash gpt_main0, or gpt_both0, the phone now becomes unbootable.
This means, if I try to create a partition table to flash recovery onto, appsboot (and by extension, fastboot) no longer works.
Code:
$ fastboot flash recovery recovery.img
Sending 'recovery' (18115 KB) OKAY [ 0.581s]
Writing 'recovery' FAILED (remote: 'partition table doesn't exist')
fastboot: error: Command failed
"partition table doesn't exist"
If I try to create the partition table, the phone refuses to boot...

OS were
sj-dan said:
So yes, I was able to get fastboot back. However, I am now facing another issue.
In order to get fastboot back, I had to run this command
Bash:
edl qfil rawprogram0.xml patch0.xml image_dir
This seemed fine at first, but now, running "edl printgpt" returns nothing. Somehow, the phone is able to boot to fastboot without any GPT partitions visible.
However, when I try to flash gpt_main0, or gpt_both0, the phone now becomes unbootable.
This means, if I try to create a partition table to flash recovery onto, appsboot (and by extension, fastboot) no longer works.
Code:
$ fastboot flash recovery recovery.img
Sending 'recovery' (18115 KB) OKAY [ 0.581s]
Writing 'recovery' FAILED (remote: 'partition table doesn't exist')
fastboot: error: Command failed
"partition table doesn't exist"
If I try to create the partition table, the phone refuses to boot...
Click to expand...
Click to collapse
So we're you able to find a fix in any way? I find myself in just about the same situation tho for different reasons. I have a radiant max 5g att device i moronicaly tried to download a gsi using the dsu updater, but forgot to unlock bootloader or even enable USB debugging before attempt. So OS system is crashing an saying 'device corrupted' on boot attempt. Recovery mode gets the same result. Was able to use the bugjaegar app to connect ad run the bootloader but every repair attempt is blocked by the fact the USB debugging isn't on. To make matters worse I accidentky hit boot fastbootd command instead of normal and whatever that did wiped out my ability to even connect with bootloader so I'm kind of stuck.

faisaliteb said:
Mod. edit: spammer gone. alecxs
I found many tutorials about fixing bootloops on the Nexus but they all seem to require an unlocked bootloader.
The bootloader on the device is locked. I can see the device in fastboot devices but I can't unlock it.
Any idea how to repair this? Can I somehow flash a factory image onto the device even though OEM unlock is disabled? There is no data on the device that would need to be preserved. I'm ideally looking for a Linux-based solution. more info... ***
Click to expand...
Click to collapse
Yeah man I've been looking at this problem for over a week now and can't find much online at all to help. Except for this EDLmode some devices can boot into, and apparently you can flash a locked system using this emergency download mode. I dunno still researching.