Develop Bugs

[Q] Writing 'system' FAILED, any ideas?

This is my third Nexus to play with and this is the first time I encountered this problem on flashing.
Using fastboot commands seems to flash the other imgs, but specifically on the system.img and radio.img it says
writing 'system.img' . . . FAILED (remote: Write Fail)
I tried searching on different forums even Nexus One's and Nexus S', but still to no avail.
Any ideas? It will be greatly appreciated!
Mico

Corrupt system partitions? Bad cable? These are some possibilities does this process work on other Nexus's ?
Sent from my Galaxy Nexus using xda premium

I don't think a bad cable is the case, this is the original cable and I have used it to flash a yakju build a week earlier.
But on the corrupt partitions, how can I fix it?

Mickosis said:
I don't think a bad cable is the case, this is the original cable and I have used it to flash a yakju build a week earlier.
But on the corrupt partitions, how can I fix it?
Click to expand...
Click to collapse
You don't. And I could never trust Samsung stock cables... very thin and long. That's a lot of room for error. I'm just spitting out possibilities. In hope to narrow itndown
Sent from my Galaxy Nexus using xda premium

So if in case I got a corrupted partition problem, I should bring this to a Samsung repair store?
Damn Samsung corrupted already in a week @[email protected]
Update : I tried adb-ing in CWM a nandroid and restore, it didn't spit out an error, but it seems it goes on a boot loop when I boot it up.

Mickosis said:
So if in case I got a corrupted partition problem, I should bring this to a Samsung repair store?
Damn Samsung corrupted already in a week @[email protected]
Click to expand...
Click to collapse
Are you trying to flash Google's stock images? Have you tried redownloading them just incase the download was corrupt or something?

anton2009 said:
Are you trying to flash Google's stock images? Have you tried redownloading them just incase the download was corrupt or something?
Click to expand...
Click to collapse
Yes, I tried yakju and takju. The system.img always give that error. Everything else can be pushed and written.

Try 'fastboot erase system', then flash system.
Trying this on windows or Linux?
Which adb version are you using?
Sent from my i9250

I got it fixed, weird, I tried fastboot flashing on a different PC and it worked.
Thanks to all who replied, you may close this now

same problem! can´t format nor flash system.img
I have a stock firmware GSM version 4.04, and suddenly from one day to the other it doesn't boot anymore and I'm stuck in Goggle logo.
Trying to do a factory reset (from recovery) it gives:
--Wiping data...
Formatting /data...
Error mounting/data!
Skipping format.....
Formatting /cache...
E:format_volume: make_extf4fs failed on /dev/block/platform/omap/omap_hsmmc.0/by-name/cache
formatting /sd-ext...
formatting /sdcard/.android_secure...
Error mounting mounting /sdcard/.android_secure!
skipping format...
Data wipe complete...
E:Can't mount /cache/recovery/log
E:Can´t open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can´t open /cache/recovery/last_log
E:failed closing /dev/block/platform/omap/omap_hsmmc.0/by-names/misc
(I/O error)
Also trying to mount /system ->
Error mounting /system!
from fastboot if I try to reflash System and userdata ->
C:\galaxy>fastboot flash system system.img
sending 'system' (321251 KB)...
OKAY [ 29.667s]
writing 'system'...
FAILED (remote: Write Fail)
finished. total time: 47.294s
C:\galaxy>fastboot flash userdata userdata.img
sending 'userdata' (137554 KB)...
OKAY [ 12.642s]
writing 'userdata'...
FAILED (remote: Write Fail)
finished. total time: 20.180s
Is it a hardware problem?

Like the post above yours, have you tried another PC?
Sent from my i9250

bk201doesntexist said:
Like the post above yours, have you tried another PC?
Sent from my i9250
Click to expand...
Click to collapse
+1. This.
It is probably a driver or cable issue.

Writing 'system failed'
efrant said:
+1. This.
It is probably a driver or cable issue.
Click to expand...
Click to collapse
Yes, already tried in other pc without luck.
Also from recovery menu, using wipe data/reset to factory default fails, as it cannot format the respective partitions.
Any ideas?

nictew said:
Is it a hardware problem?
Click to expand...
Click to collapse
Per the I/O error, I would say yes, there's a hardware problem.

nictew said:
Yes, already tried in other pc without luck.
Also from recovery menu, using wipe data/reset to factory default fails, as it cannot format the respective partitions.
Any ideas?
Click to expand...
Click to collapse
have you tried erasing first, then flash? in fastboot?

Hi,
i have a similar problem, can't format/erase/write on userdata partition.
i tried with odin, several pda (all fails when trying to write userdata)
and
Code:
fastboot erase userdata
fails too (just hangs forever, when other partitions are erase in tenth of second), tried from windows and linux, with different cables...
so, hardware issue ? anything i can try to fix it (soft/hard)? replacing the motherboard would work ?
thanks in advance !

julienvt said:
Hi,
i have a similar problem, can't format/erase/write on userdata partition.
i tried with odin, several pda (all fails when trying to write userdata)
and
Code:
fastboot erase userdata
fails too (just hangs forever, when other partitions are erase in tenth of second), tried from windows and linux, with different cables...
I am having the same issue
Click to expand...
Click to collapse

Hi,
you can see the full discussion about my issue here:
http://forum.xda-developers.com/showthread.php?t=2309568
the phone's been sold for pieces...
let me know if you managed to solve this !

Stuck in bootloop, can't flash

Posted in the general thread, but no replies.
I seem to have softbricked my phone by rooting then applying the OTA update. I've tried re-rooting, wiping cache, factory resetting, etc., and nothing seems to work. Following the steps in http://forum.xda-developers.com/zenf...d-zf2-t3127835 I can get to step 7, but when I submit any of the commands I get this:
Code:
C:\Users\Elliott\Downloads\CWM_Zenfone_2_Intel>fastboot flash fastboot droidboot.img
target reported max download size of 536870912 bytes
sending 'fastboot' (14822 KB)...
OKAY [ 0.666s]
writing 'fastboot'...
FAILED (remote: Permission denied
)
finished. total time: 0.839s
C:\Users\Elliott\Downloads\CWM_Zenfone_2_Intel>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (11882 KB)...
OKAY [ 0.545s]
writing 'recovery'...
FAILED (remote: Permission denied
)
finished. total time: 0.716s
C:\Users\Elliott\Downloads\CWM_Zenfone_2_Intel>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (11868 KB)...
OKAY [ 0.522s]
writing 'boot'...
FAILED (remote: Permission denied
)
finished. total time: 0.694s
C:\Users\Elliott\Downloads\CWM_Zenfone_2_Intel>fastboot flash system system.img
target reported max download size of 536870912 bytes
erasing 'system'...
FAILED (remote: Permission denied)
finished. total time: 125.564s
It wasn't clear if it was a windows permission error or an android permission error, so I tried an admin command prompt but that didn't change anything.
Any suggestions? Thanks in advance

Bump in hopes of a solution

And another bump, any help would be greatly appreciated

I'm wondering if it has to do with having a bootloader installed being over a certain version. I had 2 Asus Zenfone 2s and I get the same error messages. I can't remember what my first ZF2 had for firmware to start, but I was a dummy and updated it all the way to 2.20.40.90 stock. Everytime I tried to write via fastboot, Permission Denied. My new ZF2 on 2.20.40.59 also has the same problem. I feel like Asus patched the ability to fastboot these files or something. Running CMD as Administrator doesn't help the situation.

bumping because I'm having the same issue, coming back to stock after having CM12.1

As easy as it sounds, the solution was just flashing the newest software from the ASUS website, using adb sideload UL-Z00A-WW-2.20.40.97-user.zip
I can't imagine why I wouldn't have done that sooner, but it fixed it. Whether that worked due to something else I did, i have no idea, but my phone is now working

I had that before but fortunately I was able to fix it.
Get a microsd, but a firmware from Asus website, make sure that it is the correct one if you have WW then download WW, download it from Asus website or it will not work.
Then put the micro sd on the phone., rename the file MOFD_UPDATE don't put zip cause it will be doubled.
Boot to bootloader then boot to recovery. Automatically the phone will restore itself.

Hi I'm currently facing a similar problem. Connected the phone via USB to a laptop and it rebooted all of a sudden and is in bootloop. It was not rooted and it was on 2.19.40.23, the phone is ZE550ML or Z008. There are 6 gigs of photos on internal memory which I want to recover.
I tried fastboot flashing preroot images and recovery boot and bootdroid images. Didn't work
I tried sideloading stock image from the Asus website. Didn't work
When I go into recovery the message - failed to map file /sdcard/MOFD_SDUPDATE comes up, last post said MOFD_UPDATE on my phone comes up different.
I also tried "adb pull / " - started pulling stuff but stops at some point.
I also tried flashing CWM and trying to mounts the internal storage as external device, didn't work.
I was also unable to mount the SD card, might have something to do with MOFD not being mapped.
Don't know if TWRP has any similar functionality but when I tried flashing any other recovery, after the process when I go into recovery itself the stock one takes over...
Any help would be greatly appreciated.

KylarBStern said:
Hi I'm currently facing a similar problem. Connected the phone via USB to a laptop and it rebooted all of a sudden and is in bootloop. It was not rooted and it was on 2.19.40.23, the phone is ZE550ML or Z008. There are 6 gigs of photos on internal memory which I want to recover.
I tried fastboot flashing preroot images and recovery boot and bootdroid images. Didn't work
I tried sideloading stock image from the Asus website. Didn't work
When I go into recovery the message - failed to map file /sdcard/MOFD_SDUPDATE comes up, last post said MOFD_UPDATE on my phone comes up different.
I also tried "adb pull / " - started pulling stuff but stops at some point.
I also tried flashing CWM and trying to mounts the internal storage as external device, didn't work.
Don't know if TWRP has any similar functionality but when I tried flashing any other recovery, after the process when I go into recovery itself the stock one takes over...
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Do what i have posted above
Sent from my ONE A2001 using Tapatalk

ebanreb37 said:
Do what i have posted above
Sent from my ONE A2001 using Tapatalk
Click to expand...
Click to collapse
I already tried it, I wrote in my post that I tried it. And it didn't work.

KylarBStern said:
I already tried it, I wrote in my post that I tried it. And it didn't work.
Click to expand...
Click to collapse
SD card MUST be FAT32 or 32gb or less. If you are using anything else it won't detect the sd card.
Cheers...

Ok it's been a while since I've tried anything with this phone and just now I did what you said, copied the firmware file which I downloaded from ASUS to a 2GB sd card formatted in fat32, rebooted to recovery phone applied the update sucessfully and restarted but I am still stuck in bootloop ? I tried every method so I asume the phone is ****ed and I should send it back for RMA ?

Nexus 7 flo stuck in bootloop

Hi all,
My nexus 7 2013 wifi edition got stuck in bootloop. The tablet just crashed when I went in the apps section in the settings menu. Since then it is stuck in a bootloop and can't boot anymore. The tablet was running a kitkat version of android and was rooted.
I tried wiping cache/dalvik/data, nothing works and nothing is able to mount. It also shows the 0mb internal memory. Wiping doesn't work so I can't get rid of the 0mb. With the nexus toolkit it doesn't let me flash anything or return it to stock
I had TWRP 2.6.3 installed and tried updating it to 2.8.4 but the flashing failed.
It was able to send the recovery file to the tablet but then I got a "remote: flash write failure".
I am running out of options here. What can I do. TWRP flash seems to have failed and if I try to enter recovery now it also gets stuck in the bootlogo.
I hope someone can help me further.

Hello, and thanks for using XDA Assist.
There is a one click factory restore tool that you can find here, that has helped me in the past when I hard bricked my Nexus 7 a couple of years ago. It should work for you too.
Good luck!

Thank you for your reply. I tried the tool.
What I get, when using the bricked NEXUS.bat:
Code:
08e80e7d fastboot
sending 'bootloader' <3911 KB>...
OKAY [ 0.202s ]
writing 'bootloader'...
FAILED <remote: flash write failure>
finished. total time: 90.748s
rebootin into bootloader...
OKAY [ 0.009s ]
finished. Total time: 0.011s
erasing 'system'...
It will stick on erasing system.

Also after performing these steps, I can not boot into recovery anymore. TWRP does not start and there is also no android puppet on its back

Wrong advice. Emmc problem for which there is no remedy yet.

Th same issue happened to me tonight using my 7. I'm getting the same message when I try to flash the stock image isingbthe "flash-all" command.
Rick

Memke said:
Thank you for your reply. I tried the tool.
What I get, when using the bricked NEXUS.bat:
Code:
08e80e7d fastboot
sending 'bootloader' <3911 KB>...
OKAY [ 0.202s ]
writing 'bootloader'...
FAILED <remote: flash write failure>
finished. total time: 90.748s
rebootin into bootloader...
OKAY [ 0.009s ]
finished. Total time: 0.011s
erasing 'system'...
It will stick on erasing system.
Click to expand...
Click to collapse
I copied your log to my thread as an example of symptoms of failed, unwritable eMMC flash memory.

Today I contacted Asus and was given an RMA #. I believe this to be a hardware failure also because it happened out of no where on me. I was watching a video fine, went to reboot the tablet and it went to bootloader loop.

C5Longhorn said:
Today I contacted Asus and was given an RMA #. I believe this to be a hardware failure also because it happened out of no where on me. I was watching a video fine, went to reboot the tablet and it went to bootloader loop.
Click to expand...
Click to collapse
May I ask you to post eMMC brand when you get a replacement from ASUS?

Yes, I will if I go through with it and get it back.
Sent from my Nexus 6P using Tapatalk

k23m said:
May I ask you to post eMMC brand when you get a replacement from ASUS?
Click to expand...
Click to collapse
I posted in the other thread, but I got a tablet back from ASUS this week. I got the following chip info from SD Insight.
Hynix
HBG4e
31 GB
Jun 2013

Finally Found a Fix
So Basically below are the steps that I have followed to fix this issue on my TAB.
**NOTE: Replace ****?? with www
Hardware fix (In case due to internal wire contact issues .. this may happen due to drops )
Fix 1: (Temp)
- Follow the instructions provided by ****??.youtube.com/watch?v=0C5tpeNA4xg
Fix 2: ( Depend on analysis from Fix1.. this could be a more permanent fix)
- Is Fix 1 works then there is a high probability that you had dropped the device @ least once. I guess build quality by ASUS is kind of dodgy for Nexus 7 2013 Model.
For me this was caused due to Touchscreen Digitizer Cable, this could be due to frequent drops of Tab (Refer: ****??.ifixit.com/Store/Parts/Nexus-7-2nd-Gen-Wi-Fi-LCD-Screen-and-Digitizer-Assembly-/IF235-039-1 The Cable is Silver Color)
Power off the TAB, Disconnect and reconnect the cable (this also fixed other issue for me... gyro was not working properly in my device) . Now power ON the device.
Software Fix
Fix 3( If the issue is not related to HW, Note, Following below instruction will wipe your device Data)
- Download the latest Rom image from ****??developers.google.com/android/images#razor (for Wifi Version)
- Follow the Steps ****??developers.google.com/android/images#instructions
PS: There are many tutorials in youtube for flashing ROM/Recovering Data from TAB. Please search and Refer . Please add Https for all the link as I can post full link here.
HOPE This works for you

January OTA won't Sideload--Strange Error

I have my Pixel 2 XL currently running on the December update (8.1) and Magisk installed, stock recovery. Downloaded the January OTA file (multiple times, actually) and when I run the command to Sideload the OTA zip in Stock Recovery, I get the following error messages:
Failed to verify package compatibility (result 1): Runtime info and framework compatibility matrix are incompatible: AVB version 0.0 does not match framework matrix 1.0 Installation aborted.
Click to expand...
Click to collapse
Never seen that before and Google/XDA search came up empty or bad results. I also tried to update my adb/tools using Android Studio, still no dice.

The error provided seems to point to Magisk's modification to the dtbo to disable AVB 2.0/dm-verity.
Might have to reflash stock dtbo.img. Or just flash full factory image with the -w flaf removed from the flash-all.bat.

ilal2ielli said:
The error provided seems to point to Magisk's modification to the dtbo to disable AVB 2.0/dm-verity.
Might have to reflash stock dtbo.img. Or just flash full factory image with the -w flaf removed from the flash-all.bat.
Click to expand...
Click to collapse
Yep... that's where I'm at, looking to install the full image with -w omitted. I've even tried to uninstall Magisk (full removal) without luck.

WorldOfJohnboy said:
Yep... that's where I'm at, looking to install the full image with -w omitted. I've even tried to uninstall Magisk (full removal) without luck.
Click to expand...
Click to collapse
Might be able to try restoring images option in Magisk Manager too before installing full image.
I just install the full images each update though, less problems that way.

OK, so I fixed it by going back to stock (December) Boot and DTBO images, then Sideloaded the OTA which worked fine. Worst case, I'll flash the full System without wipe if I have issues. So it looks as if @ilal2ielli was right! Also, credit to THIS post by @sn0warmy for the steps.

Yep, I had the same issue last night and couldn't find anything on Google. Drove me crazy for a good 30 minutes! Then I recalled that you have to be 100% stock to take updates so I flashed stock boot.img and it took the update just fine afterwards. I did not need to flash dtbo.img.

I'm all flashed, but having issues with the Magisk Patched Boot image. Flashed stock back in since it would only boot to recovery or bootloader. I may revert to booting to TWRP and flashing the Magisk that way.

I uninstalled Magisk using the Magisk app and reflashed the stock boot image but I am still getting the January
update installation error. Do I need to use the Magisk-uninstaller zip file?

seckelg said:
I uninstalled Magisk using the Magisk app and reflashed the stock boot image but I am still getting the January
update installation error. Do I need to use the Magisk-uninstaller zip file?
Click to expand...
Click to collapse
Did you flash the December stock boot.img? You may also want to try flashing the December dtbo.img. I did both and my issues are resolved.

WorldOfJohnboy said:
Did you flash the December stock boot.img? You may also want to try flashing the December dtbo.img. I did both and my issues are resolved.
Click to expand...
Click to collapse
Yes, I flashed the boot.img from taimen-opm1.171019.011 and I just did the same with the dtbo.img. Unfortunately the update still won't take. Thanks for the reply though.

seckelg said:
Yes, I flashed the boot.img from taimen-opm1.171019.011 and I just did the same with the dtbo.img. Unfortunately the update still won't take. Thanks for the reply though.
Click to expand...
Click to collapse
Then flash the full image minus the -w from fastboot.

v12xke said:
Then flash the full image minus the -w from fastboot.
Click to expand...
Click to collapse
Funny...i'm having the same issues. I tried all the above..nothing works. I tried flashing the full image -w, I keep getting an error that boot.img is missing. BTW- I did a critical unlock of the bootloader when i got the phone. This is what I get:
target reported max download size of 536870912 bytes
sending 'bootloader' (36344 KB)...
OKAY [ 1.069s]
writing 'bootloader'...
FAILED (remote: Flashing is not allowed for Critical Partitions)
finished. total time: 1.084s
rebooting into bootloader...
OKAY [ 0.004s]
finished. total time: 0.004s
target reported max download size of 536870912 bytes
sending 'radio' (60428 KB)...
OKAY [ 1.769s]
writing 'radio'...
OKAY [ 0.588s]
finished. total time: 2.365s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
error: update package missing boot.img
Press any key to exit...

fastracer said:
Funny...i'm having the same issues. I tried all the above..nothing works. I tried flashing the full image -w, I keep getting an error that boot.img is missing. BTW- I did a critical unlock of the bootloader when i got the phone. This is what I get:
target reported max download size of 536870912 bytes
sending 'bootloader' (36344 KB)...
OKAY [ 1.069s]
writing 'bootloader'...
FAILED (remote: Flashing is not allowed for Critical Partitions)
finished. total time: 1.084s
rebooting into bootloader...
OKAY [ 0.004s]
finished. total time: 0.004s
target reported max download size of 536870912 bytes
sending 'radio' (60428 KB)...
OKAY [ 1.769s]
writing 'radio'...
OKAY [ 0.588s]
finished. total time: 2.365s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
error: update package missing boot.img
Press any key to exit...
Click to expand...
Click to collapse
Looks like you didn't unlock your critical partition, which is preventing the factory image from flashing the bootloader. Google blocks boot.img flashes if the bootloader isn't the most updated or the one that matches the boot.img.
You'll need to fastboot unlock_critical, which will wipe your phone and data currently stored on it to progress any further.

fastracer said:
Funny...i'm having the same issues. I tried all the above..nothing works. I tried flashing the full image -w, I keep getting an error that boot.img is missing. BTW- I did a critical unlock of the bootloader when i got the phone. This is what I get:
Click to expand...
Click to collapse
He's right, you haven't properly unlocked critical. That means you get to go to the back of the class and go through the wipe process again. You'll be a regular pro by the time this is over. :good:

ilal2ielli said:
Looks like you didn't unlock your critical partition, which is preventing the factory image from flashing the bootloader. Google blocks boot.img flashes if the bootloader isn't the most updated or the one that matches the boot.img.
You'll need to fastboot unlock_critical, which will wipe your phone and data currently stored on it to progress any further.
Click to expand...
Click to collapse
v12xke said:
He's right, you haven't properly unlocked critical. That means you get to go to the back of the class and go through the wipe process again. You'll be a regular pro by the time this is over. :good:
Click to expand...
Click to collapse
Thanks guys! I'm sure I critical unlocked it BUT I did mess around with so much stuff since this happened I probably did something I wasn't supposed to I'm gonna redo the crictical unlock and start over...thanks again!

v12xke said:
He's right, you haven't properly unlocked critical. That means you get to go to the back of the class and go through the wipe process again. You'll be a regular pro by the time this is over. :good:
Click to expand...
Click to collapse
Hi. I went through and relocked and then unlocked both the standard "unlock" and the "critical unlock". Then I tried to flash the Feburary image but was met with a "device is corrupt message" that looked like the bootloader warning message except the yellow triangle was red. The sideloading the OTA also gives an error:
E: Failed to verify package compatibility (result 1): Runtime info and framework compatibility matrix are incompatible: AVB version 0.0 does no match framework matrix 1.0
Installation aborted.
Do you have any idea how I could fix this?
Thanks in advance

km00000 said:
Hi. I went through and relocked and then unlocked both the standard "unlock" and the "critical unlock". Then I tried to flash the Feburary image but was met with a "device is corrupt message" that looked like the bootloader warning message except the yellow triangle was red. The sideloading the OTA also gives an error:
E: Failed to verify package compatibility (result 1): Runtime info and framework compatibility matrix are incompatible: AVB version 0.0 does no match framework matrix 1.0
Installation aborted.
Do you have any idea how I could fix this?
Thanks in advance
Click to expand...
Click to collapse
Use the most recent adb from the Google factory image page. Also don't use an edited flash-all.bat.

ilal2ielli said:
Use the most recent adb from the Google factory image page. Also don't use an edited flash-all.bat.
Click to expand...
Click to collapse
I've been using the most recent adb (version 1.0.36). Only thing I can think of is that I somehow I added an older version to my PATH so that I could use it from any folder and now Windows keeps using the older version. Is that the latest version?

km00000 said:
I've been using the most recent adb (version 1.0.36). Only thing I can think of is that I somehow I added an older version to my PATH so that I could use it from any folder and now Windows keeps using the older version. Is that the latest version?
Click to expand...
Click to collapse
You arent' running the lastest version of the binaries due to your current path statement. ADB version now is 10.3.9. You should delete all versions off your PC. Edit your path statement with a single ADB folder (C:\ADB\) . Now add this folder to PATH. Go HERE and download the latest version binaries -27.0.1 (December 2017). Unzip the entire zip file into the C:\ADB folder. Reboot. As a test, open a command window and type path and C:\ADB should be there. Make sure your connection to phone in BOOTLOADER MODE is good by typing "fastboot devices" and you should immediately get your serial number back. Now unzip the entire contents of the full Google image (Not OTA) into your ADB folder. Do not further unzip the nested update.zip. Leave that alone. At this point either type flash-all.bat or double click on the batch file to initiate the script.

v12xke said:
You arent' running the lastest version of the binaries due to your current path statement. ADB version now is 10.3.9. You should delete all versions off your PC. Edit your path statement with a single ADB folder (C:\ADB\) . Now add this folder to PATH. Go HERE and download the latest version binaries -27.0.1 (December 2017). Unzip the entire zip file into the C:\ADB folder. Reboot. As a test, open a command window and type path and C:\ADB should be there. Make sure your connection to phone in BOOTLOADER MODE is good by typing "fastboot devices" and you should immediately get your serial number back. Now unzip the entire contents of the full Google image (Not OTA) into your ADB folder. Do not further unzip the nested update.zip. Leave that alone. At this point either type flash-all.bat or double click on the batch file to initiate the script.
Click to expand...
Click to collapse
I was able to force it to go to the adb I downloaded and got it installed. I actually just changed the flash-all.bat script to use the correct adb version by point it to the freshly downloaded platform-tools. I'm not sure where this old ADB is located. It's not in my PATH when I look at environment variables. I don't have any other ADB or platform-tools downloaded, that I know off.
Anyway I got it to work and I'll just make sure to point it to the correct platform-tools whenever I flash something in the future. Can't believe I've been on the developer preview 2 since like November.

Can't Flash Factory Image.

Hey everyone,
So my Pixel 2 XL is kinda stuck at the moment. I'm having problems getting stock back up on my Pixel 2 XL, When I click onto flash-all command it does the job till it gets near the end of the process and then comes up with the error as 'Target didn't report max-download-size' I've used other factory images for the Pixel 2 XL CMD and the phone isn't having it at all. I really don't know what to do at this point. I need some kind of fix to this. Any advice would be really great.
** NEW ERROR **
target reported max download size of 536870912 bytes
sending 'bootloader' (36356 KB)...
OKAY [ 0.799s]
writing 'bootloader'...
OKAY [ 0.370s]
finished. total time: 1.169s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
target reported max download size of 536870912 bytes
sending 'radio' (60388 KB)...
OKAY [ 1.341s]
writing 'radio'...
OKAY [ 0.570s]
finished. total time: 1.911s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
error: failed to load 'image-taimen-pq2a.190405.003.zip': Not enough space
Press any key to exit...

When you say you flashed others and all was ok, what month are those images from? What I'm wondering is if you have out dated fastboot. Did you already update your platform tools? If not, do that and see if it works.

I usually run into this issue if I don't have enough free space on my C drive (at least 4 GBs; the system partition image is around 2 GBs...). And if it's not the free space issue, usually it's merely just a change/re-initialization of the USB cord. Make sure you have the latest platform-tools (r28.0.2 is the most up-to-date version) as well as using a USB-C to USB-A cord (USB-C to USB-C seems to cause endless amount of issues and is usually the root cause for random unknown reasons...)...it usually sets things up right to work the next time around.
But, if making sure of all the previous things, and you restarted your phone and computer already, then you might try re-downloading the Full Factory image and extracting it once again (don't forget to re-edit the .bat/.sh file to not include the "-w" attribute); and consider even going through the trouble of comparing checksums to make sure you are getting/using the exact proper copy of the factory image...
good luck to you and hope this helps...

Fe Mike said:
When you say you flashed others and all was ok, what month are those images from? What I'm wondering is if you have out dated fastboot. Did you already update your platform tools? If not, do that and see if it works.
Click to expand...
Click to collapse
I uninstalled and reinstalled fastboot, re-downloaded platform tools and reinstalled all drivers. I downloaded the factory file straight from google which was the android 9.0 April 2019 update. Yet I'm still having this problem. It was working fine yesterday as I went to reboot it, it just went straight into a bootloop. The phone was rooted via magisk.

So I got a new error now and fastboot is telling me that there is not enough space to load the zip file. Everything is extracted out of the image zip file and moved into the adb folder

Finally Solved the problem! So I booted the phone into its stock recovery and pushed the adb zip file through and then after waiting for 20 minutes I rebooted the phone and its booted into its stock rom. Thanks everyone!

Knxed_ said:
Finally Solved the problem! So I booted the phone into its stock recovery and pushed the adb zip file through and then after waiting for 20 minutes I rebooted the phone and its booted into its stock rom. Thanks everyone!
Click to expand...
Click to collapse
You can boot twrp and flash the ota as well