Develop Bugs

[Solved] Error while flashing factory images - Zip: unable to truncate file

Hey guys, I've Pixel 2 XL and I'm trying to flash the factory images on the phone using flash-all.bat. I had 8.1 earlier and was doing some tests with custom ROM and then wanted to start afresh. So I did these steps:
1. downloaded the factory image [taimen-opm1.171019.011-factory-2df1c1cb] from here.
2. Extracted it in a folder
3. Downloaded latest platform tools from here and extracted it to same folder
4. Opened command prompt and ran flash-all.bat
5. It flashed radio, bootloader and then while flashing system.img, it gave this error:
extracting system.img (1936 MB) to disk...W/ziparchive( 4084): Zip: unable to truncate file to 2030555488: File too large
Here is the full log:
Code:
The system cannot find message text for message number 0x2350 in the message fil
e for Application.
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
Not enough storage is available to process this command.
D:\Pixel 2 XL\nitin>fastboot --version
fastboot version 0.0.1-4500957
Installed as D:\Pixel 2 XL\nitin\fastboot.exe
D:\Pixel 2 XL\nitin>fastboot devices
710KPJP0210052 fastboot
D:\Pixel 2 XL\nitin>flash-all.bat
target reported max download size of 536870912 bytes
sending 'bootloader_a' (36344 KB)...
OKAY [ 1.170s]
writing 'bootloader_a'...
OKAY [ 0.379s]
finished. total time: 1.551s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s
target reported max download size of 536870912 bytes
sending 'radio_a' (60428 KB)...
OKAY [ 1.967s]
writing 'radio_a'...
OKAY [ 0.571s]
finished. total time: 2.540s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (40 MB) to disk... took 0.226s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
extracting dtbo.img (8 MB) to disk... took 0.037s
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (1936 MB) to disk...W/ziparchive( 4084): Zip: unable to truncate file to 2030555488: File too large
error:
failed to extract 'system.img': I/O error
Press any key to exit...
Any clues? I tried running the command prompt as an Admin to no avail. I know I can flash all imgs manually (and it works without any problems) but why am I getting that error?
Edit:
This was occuring due to low space on C:\drive (it seems it extracts the system.img before sending it to phone). Thanks to @stevexyz0 for the solution!

Is the disk on your PC out of space? Looks like it's trying to unzip the image before sending it to the phone.
Sent from my Pixel 2 XL using Tapatalk

stevexyz0 said:
Is the disk on your PC out of space? Looks like it's trying to unzip the image before sending it to the phone.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Man, you are awesome! :laugh::laugh::highfive::highfive:
I had the factory images on D:\ drive which had 70GB free; but the C:\ drive had only 1 GB. And I think as you rightly said, it extracts the system.img on PC and that too on C:\ drive (may be in Temp older)
I made the space on C:\ drive and it worked like a charm. Thanks once again!
Nitin

A custom ROM sounds yummy!

nitin.chobhe said:
Hey guys, I've Pixel 2 XL and I'm trying to flash the factory images on the phone using flash-all.bat. I had 8.1 earlier and was doing some tests with custom ROM and then wanted to start afresh. So I did these steps:
1. downloaded the factory image [taimen-opm1.171019.011-factory-2df1c1cb] from here.
2. Extracted it in a folder
3. Downloaded latest platform tools from here and extracted it to same folder
4. Opened command prompt and ran flash-all.bat
5. It flashed radio, bootloader and then while flashing system.img, it gave this error:
extracting system.img (1936 MB) to disk...W/ziparchive( 4084): Zip: unable to truncate file to 2030555488: File too large
Here is the full log:
Code:
The system cannot find message text for message number 0x2350 in the message fil
e for Application.
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
Not enough storage is available to process this command.
D:\Pixel 2 XL\nitin>fastboot --version
fastboot version 0.0.1-4500957
Installed as D:\Pixel 2 XL\nitin\fastboot.exe
D:\Pixel 2 XL\nitin>fastboot devices
710KPJP0210052 fastboot
D:\Pixel 2 XL\nitin>flash-all.bat
target reported max download size of 536870912 bytes
sending 'bootloader_a' (36344 KB)...
OKAY [ 1.170s]
writing 'bootloader_a'...
OKAY [ 0.379s]
finished. total time: 1.551s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s
target reported max download size of 536870912 bytes
sending 'radio_a' (60428 KB)...
OKAY [ 1.967s]
writing 'radio_a'...
OKAY [ 0.571s]
finished. total time: 2.540s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (40 MB) to disk... took 0.226s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
extracting dtbo.img (8 MB) to disk... took 0.037s
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (1936 MB) to disk...W/ziparchive( 4084): Zip: unable to truncate file to 2030555488: File too large
error:
failed to extract 'system.img': I/O error
Press any key to exit...
Any clues? I tried running the command prompt as an Admin to no avail. I know I can flash all imgs manually (and it works without any problems) but why am I getting that error?
Edit:
This was occuring due to low space on C:\drive (it seems it extracts the system.img before sending it to phone). Thanks to @stevexyz0 for the solution!
Click to expand...
Click to collapse
I'm getting this error if U try with manual command,
{ H:\taimen-pq1a.181105.017.a1\platform-tools> fastboot update H:\taimen-pq1a.181105.017.a1\platform-tools\image-taimen
-pq1a.181105.017.a1.zip
error: failed to load 'H:\taimen-pq1a.181105.017.a1\platform-tools\image-taimen-pq1a.181105.017.a1.zip': Not enough space }
I'm getting this error if U try with flash-all command,
target reported max download size of 536870912 bytes
sending 'bootloader' (36336 KB)...
OKAY [ 0.789s]
writing 'bootloader'...
OKAY [ 0.375s]
finished. total time: 1.164s
rebooting into bootloader...
OKAY [ -0.000s]
finished. total time: -0.000s
target reported max download size of 536870912 bytes
sending 'radio' (60388 KB)...
OKAY [ 1.304s]
writing 'radio'...
OKAY [ 0.569s]
finished. total time: 1.878s
rebooting into bootloader...
OKAY [ -0.000s]
finished. total time: -0.000s
error: failed to load 'image-taimen-pq1a.181105.017.a1.zip': Not enough space
Press any key to exit...
My drives are enough empty to perform this action as you can see below screen shot. I've kept these files in drive H:/
Please help here. @stevexyz0
I'm rooted from oct patch, and want to update to nov patch full OTA.

wow thank you
stevexyz0 said:
Is the disk on your PC out of space? Looks like it's trying to unzip the image before sending it to the phone.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
sheesh i tried flashing the new android 10 update and got the same error error above and man you saved me!!! omg thank you. spent hrs trying to see whats wrong and came across this post. i couldnt even get passed the google logo thought i bricked my pixel 3 xl!! thank you!!

nitin.chobhe said:
Man, you are awesome! :laugh::laugh::highfive::highfive:
I had the factory images on D:\ drive which had 70GB free; but the C:\ drive had only 1 GB. And I think as you rightly said, it extracts the system.img on PC and that too on C:\ drive (may be in Temp older)
I made the space on C:\ drive and it worked like a charm. Thanks once again!
Nitin
Click to expand...
Click to collapse
hi ...i am getting this error while flashing ruu through my pc.....
sending 'zip'... (2426128 KB) FAILdata too large, 2484355788 > 1973424128
FAILED (data size is too large(2426128 KB) for device to download ZIP file 'rom.zip'
)
please helpppppppppppppp
Execution time is 2(s)

Novair said:
hi ...i am getting this error while flashing ruu through my pc.....
sending 'zip'... (2426128 KB) FAILdata too large, 2484355788 > 1973424128
FAILED (data size is too large(2426128 KB) for device to download ZIP file 'rom.zip'
)
please helpppppppppppppp
Execution time is 2(s)
Click to expand...
Click to collapse
Other than making sure you have enough space on your PC drives, we can't really help you. You'll need to ask your question in the HTC forums. Google devices don't use RUUs.

Novair said:
hi ...i am getting this error while flashing ruu through my pc.....
sending 'zip'... (2426128 KB) FAILdata too large, 2484355788 > 1973424128
FAILED (data size is too large(2426128 KB) for device to download ZIP file 'rom.zip'
)
please helpppppppppppppp
Execution time is 2(s)
Click to expand...
Click to collapse
A simple google search showed this as fist result: https://forum.xda-developers.com/t/q-cannot-flash-failed-remote-download-size-too-large.1286751/

Strephon Alkhalikoi said:
Other than making sure you have enough space on your PC drives, we can't really help you. You'll need to ask your question in the HTC forums. Google devices don't use RUUs.
Click to expand...
Click to collapse
I have 500gb free space on pc .......
But i think this error is because of allocated partition in device [(htv 10) htv32]

Confused With Update After Root

I rooted my phone near the launch of the Pixel 2 so I could get wifi tether to work with my gUDP Verizon plan (device is from Google). I am still on 8.0 and having issues updating to 8.1. I'm having a lot of issues with crashing apps etc so I'm hoping updating will help.
I've tried a few methods unsuccessfully. I tried to do the uninstall with Magisk but it stated that the boot files weren't there. I deleted Magisk per another set of instructions and attempted to sideload and failing there as well.
I can get the phone connected with ADB. The bootloader is unlocked still. After that, I'm at a loss at what to do next. Any assistance would be appreciated its been a few years since I've messed around this stuff and obviously, things have changed and/or I've gotten dumber.

Download the full factory image, the latest.
Unzip it into your platform tools folder.
Find the flash-all.bat file and open it with notepad and edit out the -w and save it. Removing that saves your data apps and settings.
Open a command prompt in your platform tools folder
Connect the phone to the PC
Adb reboot bootloader
flash-all.bat
Reboot, redo your root and wifi tether haxk

I attempted this and the following occured. I attempted to use the Dec update and got the same errors. Do I have to start from the Nov update, then do Dec, then Jan?
Code:
target reported max download size of 536870912 bytes
sending 'bootloader_b' (36344 KB)...
OKAY [ 6.458s]
writing 'bootloader_b'...
FAILED (remote: Flashing is not allowed for Critical Partitions
)
finished. total time: 6.461s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s
target reported max download size of 536870912 bytes
sending 'radio_b' (60428 KB)...
OKAY [ 4.517s]
writing 'radio_b'...
OKAY [ 0.572s]
finished. total time: 5.091s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.002s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (40 MB) to disk... took 0.228s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
extracting dtbo.img (8 MB) to disk... took 0.029s
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (1936 MB) to disk... took 21.596s
archive does not contain 'system.sig'
extracting system_other.img (568 MB) to disk... took 6.476s
archive does not contain 'system.sig'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
extracting vendor.img (349 MB) to disk... took 3.851s
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
--------------------------------------------
Bootloader Version...: TMZ10n
Baseband Version.....: g8998-00164-1710262031
Serial Number........: 711KPED0781084
--------------------------------------------
checking product...
OKAY [ 0.001s]
checking version-bootloader...
FAILED
Device version-bootloader is 'TMZ10n'.
Update requires 'TMZ12b'.
finished. total time: 0.016s
Press any key to exit...

jdougal11 said:
I attempted this and the following occured. I attempted to use the Dec update and got the same errors. Do I have to start from the Nov update, then do Dec, then Jan?
Click to expand...
Click to collapse
Did you first unlock your bootloader critical partition?
fastboot flashing unlock_critical

Same here, my apps crash like crazy and i factory reset like 3 times but still same problem except that now is only social apps and a couple games that keeps crashing and not even reinstalling and fixes the problem

Help, I need to revert to stock!

Hi, I recently changed to a Custom ROM (Resurrection Remix) and stupid me forgot to backup before unlocking the bootloader, meaning I don't have a stock image. Here's the whole thing:
Resurrection Remix is based on LOS, so I have Lineage recovery atm.
I don't have TWRP flashed, but even when I used fastboot boot twrp.img it booted into TWRP and kept flashing the TWRP logo you see when you boot into it. If you have a TWRP backup I can try and use, that would be great. When I try flashing the official factory image, it just flashes a few things, says it can't find the file 'userdata' and says it failed, here's what happens:
HTML:
C:\Program Files (x86)\Minimal ADB and Fastboot>flash-all.bat
target reported max download size of 536870912 bytes
sending 'bootloader_a' (32424 KB)...
OKAY [ 2.031s]
writing 'bootloader_a'...
(bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_a"
(bootloader) Flashing active slot "_a"
OKAY [ 1.949s]
finished. total time: 3.985s
rebooting into bootloader...
OKAY [ 0.050s]
finished. total time: 0.054s
target reported max download size of 536870912 bytes
sending 'radio_a' (57140 KB)...
OKAY [ 3.132s]
writing 'radio_a'...
OKAY [ 0.461s]
finished. total time: 3.601s
rebooting into bootloader...
OKAY [ 0.050s]
finished. total time: 0.055s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (30 MB) to disk... took 0.998s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
archive does not contain 'dtbo.img'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (1938 MB) to disk... took 127.844s
archive does not contain 'system.sig'
extracting system_other.img (311 MB) to disk... took 104.834s
archive does not contain 'system.sig'
archive does not contain 'vbmeta.img'
extracting vendor.img (260 MB) to disk... took 13.234s
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
CreateProcess failed: The system cannot find the file specified. (2)
error: Cannot generate image for userdata
Press any key to exit...
My Pixel XL is in bootloader mode and I do have an OS installed, so I still can access the phone.
Please help, thanks!

Lol. Why do you try to flash stock image using minimal ADB/Fastboot? Did you try following the Google way?
Basically: unzip the factory image and double click flash-all.bat script ?
Here is a proper how-to:
https://developers.google.com/android/images
Good luck...

Agree with @5.1's thoughts. Update to latest/greatest platform tools from Google Developers site...then ensure you have downloaded the proper Factory Image. Then flash per the instructions on the Google site.
---------- Post added at 09:09 AM ---------- Previous post was at 09:07 AM ----------
Agree with @5.1's thoughts. Update to latest/greatest platform tools from Google Developers site...then ensure you have downloaded the proper Factory Image. Then flash per the instructions on the Google site.

Having trouble returning to stock from LineageOS

Trying to return to stock but for some reason it keeps failing. Any help is appreciated! Using Ubuntu.
Terminal out is:
sudo ./flash-all.sh
target reported max download size of 536870912 bytes
sending 'bootloader_a' (32424 KB)...
OKAY [ 1.193s]
writing 'bootloader_a'...
(bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_a"
(bootloader) Flashing active slot "_a"
OKAY [ 4.603s]
finished. total time: 5.795s
rebooting into bootloader...
OKAY [ 0.046s]
finished. total time: 0.147s
target reported max download size of 536870912 bytes
sending 'radio_a' (57140 KB)...
OKAY [ 2.304s]
writing 'radio_a'...
OKAY [ 0.488s]
finished. total time: 2.792s
rebooting into bootloader...
OKAY [ 0.050s]
finished. total time: 0.100s
extracting android-info.txt (0 MB)...
extracting boot.img (30 MB)...
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
archive does not contain 'dtbo.img'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (1953 MB)...
archive does not contain 'system.sig'
extracting system_other.img (312 MB)...
archive does not contain 'system.sig'
archive does not contain 'vbmeta.img'
extracting vendor.img (259 MB)...
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
mke2fs 1.44.4 (18-Aug-2018)
/tmp/TemporaryFile-vc741h: Unimplemented ext2 library function while setting up superblock
/usr/lib/android-sdk/platform-tools/mke2fs failed with status 1
mke2fs failed: 1
error: Cannot generate image for userdata

I had the same issue yesterday. Fixed it by downloading the latest SDK platform tools here https://developer.android.com/studio/releases/platform-tools and extracting all the files into the same folder as the factory image with the flash-all script.

christanya99 said:
Trying to return to stock but for some reason it keeps failing. Any help is appreciated! Using Ubuntu.
Terminal out is:
sudo ./flash-all.sh
target reported max download size of 536870912 bytes
sending 'bootloader_a' (32424 KB)...
OKAY [ 1.193s]
writing 'bootloader_a'...
(bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_a"
(bootloader) Flashing active slot "_a"
OKAY [ 4.603s]
finished. total time: 5.795s
rebooting into bootloader...
OKAY [ 0.046s]
finished. total time: 0.147s
target reported max download size of 536870912 bytes
sending 'radio_a' (57140 KB)...
OKAY [ 2.304s]
writing 'radio_a'...
OKAY [ 0.488s]
finished. total time: 2.792s
rebooting into bootloader...
OKAY [ 0.050s]
finished. total time: 0.100s
extracting android-info.txt (0 MB)...
extracting boot.img (30 MB)...
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
archive does not contain 'dtbo.img'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (1953 MB)...
archive does not contain 'system.sig'
extracting system_other.img (312 MB)...
archive does not contain 'system.sig'
archive does not contain 'vbmeta.img'
extracting vendor.img (259 MB)...
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
mke2fs 1.44.4 (18-Aug-2018)
/tmp/TemporaryFile-vc741h: Unimplemented ext2 library function while setting up superblock
/usr/lib/android-sdk/platform-tools/mke2fs failed with status 1
mke2fs failed: 1
error: Cannot generate image for userdata
Click to expand...
Click to collapse
The problem is "/usr/lib/android-sdk/platform-tools/mke2fs"
* Check that you have a mke2fs in that directory. If yes, install the latest platform-tools
* If you don't, install the full platform-tools (not the small pack containing only fastboot, adb, and a few other stuff...)
The fix from the other answer will work, but you shouldn't have the install platform-tools in every stock image you want to install...

I was having similar errors with my google Pixel C. Its stock .zip file has again another .zip file.I also extracted that .zip file and manually flashed each .img one by one and it did worked for me.
sudo fastboot flash bootloader bootloader_dragon-google-smug.img
sudo fastboot reboot bootloder
sudo fastboot devices
sudo fastboot flash boot boot.img
sudo fastboot flash cache cache.img
sudo fastboot flash recovery recovery.img
sudo fastboot flash system system.img
sudo fastboot flash vendor vendor.img
(I used sudo to be extra safe.)

[SOLVED]Failed at rooting my phone or so

pics, pardon the **** quality
Tried rooting it, fastboot works but ADB doesn't seem to recognise my device. I went to the link it gave me and followed the tutorial it gave me clicked on it hopes of at least getting back to stock, but at the step were I run the bash script (flash-all.sh) it errors out.
Spoiler: flash-all.sh output
Code:
target reported max download size of 536870912 bytes
sending 'bootloader' (4610 KB)...
OKAY [ 0.212s]
writing 'bootloader'...
OKAY [ 0.154s]
finished. total time: 0.366s
rebooting into bootloader...
OKAY [ 0.019s]
finished. total time: 0.069s
target reported max download size of 536870912 bytes
sending 'radio' (56630 KB)...
OKAY [ 1.463s]
writing 'radio'...
OKAY [ 0.535s]
finished. total time: 1.998s
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.070s
extracting android-info.txt (0 MB)...
extracting boot.img (11 MB)...
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'dtbo.img'
archive does not contain 'dt.img'
extracting recovery.img (17 MB)...
archive does not contain 'recovery.sig'
extracting system.img (1909 MB)...
archive does not contain 'system.sig'
archive does not contain 'vbmeta.img'
extracting vendor.img (185 MB)...
archive does not contain 'vendor.sig'
wiping userdata...
Couldn't parse erase-block-size '0x'.
Couldn't parse logical-block-size '0x'.
mke2fs 1.44.5 (15-Dec-2018)
/tmp/TemporaryFile-QFwJ4m: Unimplemented ext2 library function while setting up superblock
/usr/lib/android-sdk/platform-tools/mke2fs failed with status 1
mke2fs failed: 1
error: Cannot generate image for userdata
Where/how can I fix my mess via fastboot or something else?

Extract Android 10 rom and flash the images.

jjgvv said:
Extract Android 10 rom and flash the images.
Click to expand...
Click to collapse
Wouldn't Android 10 run like crap on the Nexus 5X, though? I've only tried some of the 8.1 ROMs, that's the highest it goes on the official page.

seething_n00b said:
Wouldn't Android 10 run like crap on the Nexus 5X, though? I've only tried some of the 8.1 ROMs, that's the highest it goes on the official page.
Click to expand...
Click to collapse
It will not run like crap but will also not be very fast.

seething_n00b said:
Wouldn't Android 10 run like crap on the Nexus 5X, though? I've only tried some of the 8.1 ROMs, that's the highest it goes on the official page.
Click to expand...
Click to collapse
custom rom, 8.1 is Google Offical firmware, offical firmware wont extract ot so

Solved on my own by realising I could just flash TWRP via fastboot. Duh.
jjgvv said:
custom rom, 8.1 is Google Offical firmware, offical firmware wont extract ot so
Click to expand...
Click to collapse
"8.1 won't work, so try 10!" You're even more of an idiot than me.

nope,8.1 is offical ota and can not be flashed in fastboot but only in recovery.