Technically a repost with more info (also I may or may not have forgotten about tags on the first thread).
Trying to fastboot flash to any partition gives the error:
FAILED (remote: 'sparse image size span overflow.')
Tried specifying size with -S, flashing stock image, erasing the partition and flashing (which gave the same error, making me unable to write to the empty partition. Did this with boot (magisk root) and had to reflash to stock using sp flash tool, which is why I'm sure of the stock images being fully functional), and trying two versions of the android platform tools (from the arch repos, as well as developer.android.com)
Originally I thought it was just the boot partition, but trying to flash twrp (built using the mtk auto twrp porter) gave the same error.
Did you later successfully flash it?
And did it work
please share the image file if it works
Related
Hi
I'm trying to flash the factory image recently posted but getting the following error:
Code:
target reported max download size of 518205818 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 1814213396 bytes
error: update package missing system.img
Looks like the Nexus 9 doesn't have enough allocated space to take the 820+MB zip file that contains the system images. I've updated to the latest version of SDK tools and have the newest Fastboot EXE, and device state is saying UNLOCKED on the HTC Fastboot screen.
Anyone have any ideas?
Regards
Phil
PhilipL said:
Hi
I'm trying to flash the factory image recently posted but getting the following error:
Code:
target reported max download size of 518205818 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 1814213396 bytes
error: update package missing system.img
Looks like the Nexus 9 doesn't have enough allocated space to take the 820+MB zip file that contains the system images. I've updated to the latest version of SDK tools and have the newest Fastboot EXE, and device state is saying UNLOCKED on the HTC Fastboot screen.
Anyone have any ideas?
Regards
Phil
Click to expand...
Click to collapse
I would trying to flash each image in factory image individually (Flash bootloader, flash boot, flash recovery, etc.), flashing them in the order the flash-all script would flash them (If your not sure which order it would flash them in just open the flash-all.bat or flash-all.sh as a text file and look at the order they are flashed in).
PhilipL said:
Hi
I'm trying to flash the factory image recently posted but getting the following error:
Code:
target reported max download size of 518205818 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 1814213396 bytes
error: update package missing system.img
Looks like the Nexus 9 doesn't have enough allocated space to take the 820+MB zip file that contains the system images. I've updated to the latest version of SDK tools and have the newest Fastboot EXE, and device state is saying UNLOCKED on the HTC Fastboot screen.
Anyone have any ideas?
Regards
Phil
Click to expand...
Click to collapse
The missing.sig errors are normal. The missing system.img is not. Try downloading the factory image again.
Sent from my Nexus 5 using XDA Free mobile app
Same here, get the same error when trying to flash factory image. I did flash the files individually, but wasn't sure how to flash the vendor.img?
any update on this?
what do we do with vendor.img?
mingiunate said:
any update on this?
what do we do with vendor.img?
Click to expand...
Click to collapse
Just an update - based on the size of vendor.img, I assumed it was the same as userdata.
here are the steps i took to manually flash:
unzip image-volantis-lrx21l.zip
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash boot boot.img
fastboot flash userdata vendor.img
from tablet - select hboot
select factory reset
Done!
Hm, I successfully flashed vendor.img using
Code:
fastboot flash vendor vendor.img
But I'm not sure whether that was the correct way to go about things.
Hi
Thanks everyone for the replies/responses.
I will try and flash each image separately, however this shouldn't be necessary and means the image (or some setting on the Nexus 9) is wrong or broken. The whole point of the factory image is that it flashes with ease to get us back to a clean slate (well tablet), so a bit worrying they've not seemingly tested it too well.
Note I've flashed factory images dozens of times to Nexus 4, 5, 7 (both years) and never had this problem.
Perhaps Google will post a fix soon.
Best Regards
Phil
I think you need to run these two commands before you flash the rest of the .img files?
fastboot flash bootloader bootloader-flounder-3.43.0.0114.img
fastboot reboot-bootloader
ilatimer1 said:
I think you need to run these two commands before you flash the rest of the .img files?
fastboot flash bootloader bootloader-flounder-3.43.0.0114.img
fastboot reboot-bootloader
Click to expand...
Click to collapse
here are the steps i took to manually flash:
run the flash-all.bat up until the point where it fails
unzip image-volantis-lrx21l.zip
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash boot boot.img
fastboot flash userdata vendor.img - looks like userdata should be vendor? - mine worked with userdata regardless
from tablet - select hboot
select factory reset
Done!
Hi
ilatimer1 said:
I think you need to run these two commands before you flash the rest of the .img files?
fastboot flash bootloader bootloader-flounder-3.43.0.0114.img
fastboot reboot-bootloader
Click to expand...
Click to collapse
I did this as the first step as that is what is in the batch file with all/most Nexus factory images, didn't make a difference though. Something is definitely broken somewhere. However installing the images separately seems to work.
Best Regards
Phil
When was the last time you updated your SDK? Try downloading the latest SDK and run the flash-all
Hi
cundiffr said:
When was the last time you updated your SDK? Try downloading the latest SDK and run the flash-all
Click to expand...
Click to collapse
As I mentioned in the first post, after the first failure I updated my SDK to the very latest version, the result was the same. The image doesn't flash unless you separate out the individual parts and do it separately. Either the Nexus 9 isn't configured to allow enough space to accept the entire image (which clearly Google think it should as that is how they instruct it to be installed), or the image is broken in some way.
I'm sure it will get fixed at some point.
Regards
Phil
The same thing happened to my while I tried to flashed the newly released lollipop image to my nexus 5. I only had to restart my laptop and it worked.
mingiunate said:
[*]fastboot flash userdata vendor.img - looks like userdata should be vendor? - mine worked with userdata regardless
Click to expand...
Click to collapse
Yep, vendor should be flashed to the "vendor" partition.
userdata is emptied during factory reset.
Are you sure the prollem is with the tablet? When running a full ruu on other HTC devices, the failure to allocate space prollem arises from not having enough ram on the pc. Could be why flashing the images separately is working.
scotty1223 said:
Are you sure the prollem is with the tablet? When running a full ruu on other HTC devices, the failure to allocate space prollem arises from not having enough ram on the pc. Could be why flashing the images separately is working.
Click to expand...
Click to collapse
It's the image or tablet that's at fault. I ran the flashing process on a high-end machine equipped with 32 GB of RAM.
Restart your computer!
I sat here forever trying to figure why the hell i couldn't get 5.0 to flash to my nexus 5. I looked everywhere and didn't find anything that helped at all. I restarted my computer and tried again and it worked instantly. The first thing i said to myself was are you ****ing kidding me.... my computer was the issue. Dont tell yourself bull**** about how your computer is the bees knees. Mine may only have 16 gb of ram but restarting it worked perfectly.
Do i make a fullwipe, befor i flash the Image Files, if yes how i do this.
format system
format data
format cache
????????
fastboot flash userdata vender.img actually worked for me
Hello,
I soft-bricked my Padfone A86 when I tried to flash my own kernel using TWRP 2.7.1.1. Before that I was running a rooted Android 5.0.2 (fw version WW-12.4.0.59) with TWRP recovery that I installed like described in an article at padfoneclub.com.
Installing the custom ROM damaged (at least) the boot and recovery partitions. That means I only have access to fastboot which I can not use to flash to those partitions:
Code:
fastboot flash recovery twrp-2.7.1.1-unofficial.img
target reported max download size of 1879048192 bytes
sending 'recovery' (10124 KB)...
OKAY [ 0.321s]
writing 'recovery'...
FAILED (remote: Security is Enable, close 'flash' function !!)
finished. total time: 0.338s
The remote: Security is Enable, close 'flash' function !! error must have been introduced by a patch to the bootloader because I don't recall having this issue when I first flashed TWRP back then when I was running some previous firmware version.
What I can do though is to boot the boot.img (only from fw versions 10.12.3.116 and 10.12.3.130) like this: fastboot boot boot.img
Using saferoot I managed to get root access which enables me to write to the recovery and boot partitions like this:
Code:
dd if=/sdcard/twrp-2.7.1.1-unofficial.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery bs=4096; sync;
Although I can confirm that the memory gets changed using the dd command the bootloader neither loads recovery nor the system on the boot partition.
I looked at a hexdump of the recovery partition and it seems like the only thing stored in it is the TWRP image followed by zeroes. Trying different block sizes didn't help neither.
Confusingly that method seemed to work for some people. Maybe TWRP requires to be written over some stock recovery and can't boot on its own?
I was only able to try to flash the stock recovery for fw versions above 10.12.3.13 as ASUS only included patch-files for the recovery partition before. That didn't work neither. I was assuming that the recovery is running on its own and does not depend on being the same version as the system (or the bootloader). Or might there be something on a different partition that prevents the recovery from working properly?
Booting into recovery results in getting into fastboot mode (fastboot continue doesn't help).
Booting the system stops at the bootloader which shows the error message: ERROR: Can not load Invalid boot image!!
The frustrating thing is that although I seem to have full access to the device memory I still don't manage to fix the recovery partition.
Any help or ideas would be greatly appreciated.
Thunder Storm said:
Hello,
I soft-bricked my Padfone A86 when I tried to flash my own kernel using TWRP 2.7.1.1. Before that I was running a rooted Android 5.0.2 (fw version WW-12.4.0.59) with TWRP recovery that I installed like described in an article at padfoneclub.com.
Installing the custom ROM damaged (at least) the boot and recovery partitions. That means I only have access to fastboot which I can not use to flash to those partitions:
Code:
fastboot flash recovery twrp-2.7.1.1-unofficial.img
target reported max download size of 1879048192 bytes
sending 'recovery' (10124 KB)...
OKAY [ 0.321s]
writing 'recovery'...
FAILED (remote: Security is Enable, close 'flash' function !!)
finished. total time: 0.338s
The remote: Security is Enable, close 'flash' function !! error must have been introduced by a patch to the bootloader because I don't recall having this issue when I first flashed TWRP back then when I was running some previous firmware version.
What I can do though is to boot the boot.img (only from fw versions 10.12.3.116 and 10.12.3.130) like this: fastboot boot boot.img
Using saferoot I managed to get root access which enables me to write to the recovery and boot partitions like this:
Code:
dd if=/sdcard/twrp-2.7.1.1-unofficial.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery bs=4096; sync;
Although I can confirm that the memory gets changed using the dd command the bootloader neither loads recovery nor the system on the boot partition.
I looked at a hexdump of the recovery partition and it seems like the only thing stored in it is the TWRP image followed by zeroes.
Confusingly that method seemed to work for some people. Maybe TWRP requires to be written over some stock recovery and can't boot on its own?
I was only able to try to flash the stock recovery for fw versions above 10.12.3.13 as ASUS only included patch-files for the recovery partition before. That didn't work neither. I was assuming that the recovery is running on its own and does not depend on being the same version as the system (or the bootloader). Or might there be something on a different partition that prevents the recovery from working properly?
Booting into recovery results in getting into fastboot mode (fastboot continue doesn't help).
Booting the system stops at the bootloader which shows the error message: ERROR: Can not load Invalid boot image!!
The frustrating thing is that although I seem to have full access to the device memory I still don't manage to fix the recovery partition.
Any help or ideas would be greatly appreciated.
Click to expand...
Click to collapse
Try getting rid of the bs part. Flash the image at it's normal size.
Sent from my XT1609 using Tapatalk
Thanks for your reply.
I flashed both TWRP and stock recovery without the bs parameter. Same results as before: it doesn't boot into recovery.
Hi all, I tried to flash twrp after unlocking bootloader but the site I followed was wrong, ended up with twrp on boot partition! I've since tried to fastboot various system and boot images with no luck, keeps giving file size errors. Booted twrp from fastboot to flash lineage but that ends with error code 7?! Tried to fastboot update stock room too but same problem with file size, the system img is actually broken up into 50 odd files, I presume to avoid the file size problem, however there's no flash all script. Help!!
Current State:
TWRP Installed, no OS, no system partition, instead a super partition.
I also flashed an orange_state_disabler which seems to have worked just fine.
ADB Sideload:
When I try to start ADB Sideload Feature this is what I get:
https://pastebin.com/k3gJ048P
when trying to use the adb sideload command:
Code:
adb: sideload connection failed: no devices/emulators found
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: no devices/emulators found
I converted the lineageos img file I have to a flashable zip using the tool from here:
https://forum.xda-developers.com/nu.../swapper-generate-flashable-zips-img-t4133591
but when I try to flash that zip file tho it returns this:
Code:
Installing zip file '/usbotg/system.zip'
Checking for Digest file...
Unmounting System...
Invalid zip file format!
Error installing zip file '/usbotg/system.zip'
Updating partition details...
...done
so... yeah, I don't know what else to do right now.
A Custom ROM like LineageOS can only get installed via TWRP, not by any other means: in no case by "adb sideload".
jwoegerbauer said:
A Custom ROM like LineageOS can only get installed via TWRP, not by any other means: in no case by "adb sideload".
Click to expand...
Click to collapse
Heh, I was just trying to get the ROM on the device so I could flash it then via TWRP but maybe I just misunderstood what adb sideload does
0
Seppppx said:
The Oneplus 8 Pro has a dynamic partition layout and you flash a system image by doing "fastboot flash system system.img"
See : https://forum.xda-developers.com/oneplus-8-pro/development/rom-lineageos-17-1-t4122983
Click to expand...
Click to collapse
Yeah I tried that already, the problem is that it doesn't have a system partition
MoonPadUSer said:
Yeah I tried that already, the problem is that it doesn't have a system partition
Click to expand...
Click to collapse
Your posted error messsage suggests the zip install has failed. So no change to device should have happened.
Current twrp cannot flash system.img
Only super.img(combined system.img, vendor.img, and product.img)
The systemswapper you refered to is from a qualcom device thread, and uses some *qti* device binaries that are not in your recovery. It is unlikely to have worked. (I might be wrong about the *qti* binary being only a qualcom device tool)
These new devices with dynamic partition have 2 fastboot modes.
The bootloader mode (adb reboot bootloader)
This is used for unlocking bootloader, flashing standard partitions
There is fastbootd mode (adb reboot fastboot)
This mode is only available if stock recovery is installed.
It also requires r30 or higher fastboot binary file on PC.
From fastbootd you can flash the sub partitions on super.img
There is alot of changes that take place with this new partition setup.
As for your phone no longer booting into original system, and bootlooping to recovery, I suggest first try boot to bootloader, and flash stock recovery, see if this stopps the bootlooping.
If not then use sp flash tool and flash full stock room and start fresh
mrmazak said:
From fastbootd you can flash the sub partitions on super.img
Click to expand...
Click to collapse
How?
MoonPadUSer said:
How?
Click to expand...
Click to collapse
Fastbootd is part of stock recovery, it will look different than what you may be used to as being fastboot mode.
You should see options on screen to select just like stock recovery has.
One for boot to bootloader
One for boot to recovery.
When you confirm you are in fastbootd
You just use
Code:
fastboot flash system /some-directory-on -pc/gsi-system.img
You should see messages on screen
Resizing system
Sending sparce system chunck. 1 of x
Writing system chunck 1 of x
There could be more descriptive guide on flashing gsi on dyniamic partitions if your Search google, (xda).
But it is hard to guide you to fixing device, when I'm not sure how you got stuck. I mean the description you have said should not have made you loose system partition or fail to boot, so I said it before and will suggest it again. If you have a non booting device , the FIRST thing you should do is flash it with sp flash tool and full factory rom, before messing around with other stuff before you get into worse condition
MoonPadUSer said:
How?
Click to expand...
Click to collapse
I did another post about using fastbootd on similar device. The information is all relevant to your a7pro too.
https://forum.xda-developers.com/showpost.php?p=83241985&postcount=3
mrmazak said:
Fastbootd is part of stock recovery, it will look different than what you may be used to as being fastboot mode.
You should see options on screen to select just like stock recovery has.
One for boot to bootloader
One for boot to recovery.
When you confirm you are in fastbootd
You just use
You should see messages on screen
Resizing system
Sending sparce system chunck. 1 of x
Writing system chunck 1 of x
There could be more descriptive guide on flashing gsi on dyniamic partitions if your Search google, (xda).
But it is hard to guide you to fixing device, when I'm not sure how you got stuck. I mean the description you have said should not have made you loose system partition or fail to boot, so I said it before and will suggest it again. If you have a non booting device , the FIRST thing you should do is flash it with sp flash tool and full factory rom, before messing around with other stuff before you get into worse condition
Click to expand...
Click to collapse
Ok, I am back to a fully working device again, where I got stuck was that I do not have a system partition, thus I can't flash it. Whenever I try to flash it using fastboot flash system or anything else, it just says that I do not have a system partition
Where I am right now:
I am back to a fully working device after downloading the stock ROM from my manufacturer and plugging that into SP Flash tool
After that I researched and figured out that the super partition I have basically acts like a container for
system.img, boot.img and vendor.img
which explains while simply flashing LineageOS.img to my super partition (
Code:
fastboot flash system Lineage.img
) resulted in
my device not booting anymore.
I found a tool which can unpack those super.img into system, boot and vendor
(using this youtube video: https://youtu.be/J5cQdzivtXk)
I used that to unpack the super.img which I got from my stock ROM and
now I have system.raw, boot.raw and vendor.raw, I do not know what kind of file these are but my plan is to replace system.whatever with the lineageos.img and then repack it into super.img which I can then use to flash the super partition on my phone
MoonPadUSer said:
Ok, I am back to a fully working device again, where I got stuck was that I do not have a system partition, thus I can't flash it. Whenever I try to flash it using fastboot flash system or anything else, it just says that I do not have a system partition
Click to expand...
Click to collapse
Can you show picture of this .
Of both pc screen and phone screen, please
mrmazak said:
Can you show picture of this .
Of both pc screen and phone screen, please
Click to expand...
Click to collapse
I'd love to but how am I supposed to take a picture of my phone screen in fastboot mode? (I don't have any other devices with a camera)
@MoonPadUSer
Code:
fastboot flash system Lineage.img
must have failed.
Reason: This command tries to write a complete Lineage OS ( what itself contains a partition named /system, too ) into phone's Android's current /system partition - what only is 1 partition of multiple ones that exist.
Note: You can't flash a Custom ROM by means of Fastboot.
Re-read post #2
0
Seppppx said:
That's not true when you are flashing a Generic System Image.
Click to expand...
Click to collapse
ROFL
Remember OP wants to install LineageOS 17.1 what isn't a GSI as it is with LineageOS 18.x
jwoegerbauer said:
ROFL
Remember OP wants to install LineageOS 17.1 what isn't a GSI as it is with LineageOS 18.x
Click to expand...
Click to collapse
Actually... I don't really care about the version all that much, whatever works, just didn't know if 18x is supported
Downside to Lineage GSI is for Umidigi you can't flash gapps. So unless someone adds it to the gsi for you it's best to use something else.
I went with this
https://forum.xda-developers.com/pr...velopment/aosp-10-0-quack-phh-treble-t3992559
You have to get the AB version with GAPPS if you want them
Comes pre rooted as well and gave my phone a huge speed boost
Flash the stock ROM
Unlock bootloader
fastboot flashing unlock
(unnecessary if already unlocked)
fastboot flashing unlock_critical
enter fastboot
fastboot reboot (to enter fastbootd)
fastboot erase system
(optional but I had to do this myself)
fastboot delete-logical-partition product - deletes the product partition, allowing a larger system partition
fastboot flash system (gsi file)
And you're good
Don't try to install magisk because it causes a bootloop. Even when installing it through the app. Once the boot image is patched you're in a bootloop until you reflash the stock boot
Made a generic ish Umidigi flashing tutorial because it's the same in all of them I've had so far
https://forum.xda-developers.com/an...ng-rom-gsi-t4182673/post83803205#post83803205
Trying to build a custom TWRP for my phone using this guide, but pulling files from /system is locked behind root perms.
Attempting to use the magisk root method, yet I'm unable to write to the boot partition (even when using the stock image) whatsoever. Each attempt giving this error:
Writing 'boot' FAILED (remote: 'sparse image size span overflow.')
Tried specifying size (using -S), as well as erasing the partition before flashing (both with and without specifying size), each time giving the same error (wouldn't even work with the stock image, so i had to reflash using SP flash tool). Trying to flash from fastbootd instead gives:
Writing 'boot' FAILED (remote: 'Operation not permitted.')