Blu G5 "data too large"? - Treble-Enabled Device Questions and Answers

Update: Worked through many issues below. Latest issue is that all AOSP images that I've tried so far are having infinite boot loops with recovery mode unavailable, but I am now able to revert to stock.
-----------------------------
Blu G5 "data too large"?
Hi! I'm trying to flash Treble AOSP (Android 10 or 11) to a Blu G5 dual-SIM (originally Android 9 Pie) GSM/HSPA/LTE phone. It's got a Unisoc SC9863A Octa-Core 1.6GHz ARM Cortex-A55 chipset, 2 GB of RAM and 32 GB of internal storage. The treblechecker app said it's A-only (single partition) ARM64.
I started with a factory reset, then used adb and a modified fastboot (from Hovatek) under linux to get the identifier token and unlock the bootloader. The issue is that every system image that I've tried to flash failed due to "data too large", and some were even smaller than the stock image!
Code:
[email protected]:~/Desktop/Blu-G5-AndroidUpgrade/platform-tools_r31.0.2-linux/platform-tools# ./fastboot flash system system-roar-arm64-aonly-vanilla.img
target didn't report max-download-size
sending 'system' (1745204 KB)...
FAILED (remote: data too large)
finished. total time: 0.001s
Since there was a newer (r31.0.3) version of fastboot for Windows, I tried that but I'm still getting the same failure:
Code:
C:\platform-tools>fastboot flash system system-arm64-aonly-vanilla-nosu.img
Sending 'system' (1282352 KB) FAILED (remote: 'data too large')
fastboot: error: Command failed
So far, I've tried each of the following separately, but each just hangs on this phone:
Code:
C:\platform-tools>fastboot flash vbmeta vbmeta.img --disable-verity --disable-verification
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta' ^C
Code:
C:\platform-tools>fastboot delete-logical-partition product
Deleting 'product' ^C
Any ideas?
EDIT 1: This is what worked to flash it with AOSP 11.0 v312 (although now it's in an infinite boot loop so I guess I shouldn't have skipped over AOSP 10):
Code:
C:\platform-tools>fastboot -S 300M flash system system-roar-arm64-aonly-gapps.img
Invalid sparse file format at header magic
Sending sparse 'system' 1/9 (307196 KB) FAILED (remote: 'data too large')
fastboot: error: Command failed
C:\platform-tools>fastboot -S 256M flash system system-roar-arm64-aonly-gapps.img
Invalid sparse file format at header magic
Sending sparse 'system' 1/10 (262108 KB) OKAY [ 11.080s]
Writing 'system' OKAY [ 9.083s]
Sending sparse 'system' 2/10 (262112 KB) OKAY [ 11.067s]
Writing 'system' OKAY [ 9.002s]
Sending sparse 'system' 3/10 (262100 KB) OKAY [ 11.080s]
Writing 'system' OKAY [ 14.711s]
Sending sparse 'system' 4/10 (262124 KB) OKAY [ 11.075s]
Writing 'system' OKAY [ 8.981s]
Sending sparse 'system' 5/10 (262128 KB) OKAY [ 11.082s]
Writing 'system' OKAY [ 8.940s]
Sending sparse 'system' 6/10 (262128 KB) OKAY [ 11.074s]
Writing 'system' OKAY [ 8.937s]
Sending sparse 'system' 7/10 (262120 KB) OKAY [ 11.079s]
Writing 'system' OKAY [ 9.004s]
Sending sparse 'system' 8/10 (256832 KB) OKAY [ 10.940s]
Writing 'system' OKAY [ 15.842s]
Sending sparse 'system' 9/10 (262142 KB) OKAY [ 11.120s]
Writing 'system' OKAY [ 11.342s]
Sending sparse 'system' 10/10 (131693 KB) OKAY [ 5.578s]
Writing 'system' OKAY [ 5.648s]
Finished. Total time: 209.427s
Of course it can't connect by adb, and when I try to get it into recovery mode (by Volume Up + Power buttons together until recovery mode screen appears, then when you see the BLU logo release the Power button, but keep holding Volume Up until the recovery mode screen comes), it just freezes. Any unbricking ideas?
EDIT 2: I've just tried the SPD Upgrade Tool (SPDFlashTool.com) R25.20.3901 with the stock ROM BLU_G0090_V9.0.04.04, but the tool can't seem to access the phone during the infinite boot loops or when I freeze it my trying to enter recovery mode...
EDIT 3: I guess it was only soft-bricked since unbricked once with battery pull then Vol-DOWN and Power until knocked down Android ("No Command") icon showed for an instant, then used SPD Upgrde Tool for back to stock. Loaded stock, set USB debugging, used cmd for abd and tried to reboot to fastboot, but it entered bootloop so bricked again. It's almost as if these might have A/B boot partitions after all, but I don't know how to switch between them. I'll try again later...
EDIT 4: Got back to stock with SPD Upgrade Tool again and all seemed fine. Factory Reset, and enabled USB debugging. Then flashed to AOSP 10.0 v201 this time, but got an infinite boot loop with no recovery mode again. Anyone know what I'm doing wrong? At least I found a way to get back to stock more easily afterwards by priming SPD Upgrade then holding power and volume buttons between the automatic reboots until the stock firmware started reflashing.
Code:
Microsoft Windows [Version 10.0.19043.1237]
(c) Microsoft Corporation. All rights reserved.
C:\platform-tools>adb devices -l
List of devices attached
[16 digits redacted] device product:BLU_G5 model:G5 device:G0090 transport_id:1
C:\platform-tools>adb reboot bootloader
C:\platform-tools>fastboot devices
[16 digits redacted] fastboot
C:\platform-tools>fastboot flash -S 256M system system-arm64-aonly-vanilla-nosu.img
Sending sparse 'system' 1/5 (262140 KB) OKAY [ 11.697s]
Writing 'system' OKAY [ 8.947s]
Sending sparse 'system' 2/5 (262140 KB) OKAY [ 11.662s]
Writing 'system' OKAY [ 8.923s]
Sending sparse 'system' 3/5 (262140 KB) OKAY [ 11.703s]
Writing 'system' OKAY [ 8.914s]
Sending sparse 'system' 4/5 (262140 KB) OKAY [ 11.755s]
Writing 'system' OKAY [ 8.919s]
Sending sparse 'system' 5/5 (233792 KB) OKAY [ 10.400s]
Writing 'system' OKAY [ 7.957s]
Finished. Total time: 100.914s
C:\platform-tools>fastboot reboot
Rebooting OKAY [ 0.001s]
Finished. Total time: 0.002s

Related

Update 7.1.1 Rooted XL to 7.1.2 Without Losing Data?

Please explain throughly and provide the download links, I've only had an android for a month and I am still learning the OS / Phone
tryfont said:
Please explain throughly and provide the download links, I've only had an android for a month and I am still learning the OS / Phone
Click to expand...
Click to collapse
Third post in the thread below. Just get the 7.1.2 full image instead of the 7.1.1 I mention in that post.
Pay attention to removing the -w from the flashall bat file. That is the key to saving your data.
And second to the last post in the thread are the​ instructions for getting root back.
https://forum.xda-developers.com/pixel/help/stupidly-bootloop-help-t3554242
SOLVED
TonikJDK said:
Third post in the thread below. Just get the 7.1.2 full image instead of the 7.1.1 I mention in that post.
Pay attention to removing the -w from the flashall bat file. That is the key to saving your data.
And second to the last post in the thread are the​ instructions for getting root back.
https://forum.xda-developers.com/pixel/help/stupidly-bootloop-help-t3554242
Click to expand...
Click to collapse
I'm on a mac, not sure how to do the last step with running the .bat file
Edit: went into the bat file and ran the equivalent commands in terminal
(fastboot flash bootloader bootloader-marlin-8996-012001-1702151126.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio radio-marlin-8996-012901-1702171013.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot update image-marlin-n2g47e.zip)
Here is the terminal messages I got
Last login: Mon Apr 3 18:00:13 on ttys000
Tryfons-MBP:~ tryfon$ cd /Users/tryfon/Desktop/platform-tools
Tryfons-MBPlatform-tools tryfon$ ./fastboot flash bootloader bootloader-marlin-8996-012001-1702151126.img
target reported max download size of 536870912 bytes
sending 'bootloader_b' (32380 KB)...
OKAY [ 0.811s]
writing 'bootloader_b'...
(bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_b"
(bootloader) Flashing active slot "_b"
OKAY [ 4.163s]
finished. total time: 4.974s
Tryfons-MBPlatform-tools tryfon$ fastboot reboot-bootloader
-bash: fastboot: command not found
Tryfons-MBPlatform-tools tryfon$ ./fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.046s]
finished. total time: 0.046s
Tryfons-MBPlatform-tools tryfon$ fastboot flash radio radio-marlin-8996-012901-1702171013.img
-bash: fastboot: command not found
Tryfons-MBPlatform-tools tryfon$ ./fastboot flash radio radio-marlin-8996-012901-1702171013.img
target reported max download size of 536870912 bytes
sending 'radio_b' (57240 KB)...
OKAY [ 1.444s]
writing 'radio_b'...
OKAY [ 0.704s]
finished. total time: 2.148s
Tryfons-MBPlatform-tools tryfon$ ./fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.050s]
finished. total time: 0.050s
Tryfons-MBPlatform-tools tryfon$ ./fastboot update image-marlin-n2g47e.zip
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 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
--------------------------------------------
Bootloader Version...: 8996-012001-1702151126
Baseband Version.....: 8996-012901-1702171013
Serial Number........: HT72A0200395
--------------------------------------------
checking product...
OKAY [ 0.050s]
checking version-bootloader...
OKAY [ 0.050s]
checking version-baseband...
OKAY [ 0.050s]
sending 'boot_b' (25997 KB)...
OKAY [ 0.701s]
writing 'boot_b'...
OKAY [ 0.260s]
erasing 'system_b'...
OKAY [ 0.457s]
sending sparse 'system_b' 1/4 (514854 KB)...
OKAY [ 14.106s]
writing 'system_b' 1/4...
OKAY [ 6.005s]
sending sparse 'system_b' 2/4 (524140 KB)...
OKAY [ 14.606s]
writing 'system_b' 2/4...
OKAY [ 4.937s]
sending sparse 'system_b' 3/4 (512784 KB)...
OKAY [ 14.072s]
writing 'system_b' 3/4...
OKAY [ 6.243s]
sending sparse 'system_b' 4/4 (32756 KB)...
OKAY [ 0.905s]
writing 'system_b' 4/4...
OKAY [ 0.297s]
erasing 'system_a'...
OKAY [ 0.411s]
sending sparse 'system_a' 1/4 (520579 KB)...
OKAY [ 13.904s]
writing 'system_a' 1/4...
OKAY [ 3.787s]
sending sparse 'system_a' 2/4 (521193 KB)...
OKAY [ 13.721s]
writing 'system_a' 2/4...
OKAY [ 4.103s]
sending sparse 'system_a' 3/4 (510216 KB)...
OKAY [ 14.206s]
writing 'system_a' 3/4...
OKAY [ 3.788s]
sending sparse 'system_a' 4/4 (128745 KB)...
OKAY [ 3.513s]
writing 'system_a' 4/4...
OKAY [ 1.049s]
erasing 'vendor_b'...
OKAY [ 0.154s]
sending 'vendor_b' (242238 KB)...
OKAY [ 6.003s]
writing 'vendor_b'...
OKAY [ 3.653s]
Setting current slot to 'b'...
OKAY [ 0.087s]
rebooting...
finished. total time: 131.364s
Tryfons-MBPlatform-tools tryfon$
Everything turned out fine!!!

Experience 5.2 Update?

The new update is allegedly out. But for me there is no update.
Has anyone a zip or some infos about it?
It's out only for preview program members.
I don't read too well
Out now for everyone now, currently updating now
out now but wont update, just loops for me
ricflairandy said:
out now but wont update, just loops for me
Click to expand...
Click to collapse
Same here, downloads the update, reboots, says its installing, doesn't finish, reboot, back to square one prompting to install.
So happy that it's not just me. I am also having the issue do you think the problem is with the rooted ROMs
jonsharky said:
So happy that it's not just me. I am also having the issue do you think the problem is with the rooted ROMs
Click to expand...
Click to collapse
I don't think so... Just restored with latest factory image, wiping everything and still doesn't work! I have a 2015 16GB model.
On the official shield forums it's been confirmed that the ota update won't work for rooted devices. The flash will be up on developer.nvidia.com in about a week.
JohnRossJennings said:
On the official shield forums it's been confirmed that the ota update won't work for rooted devices. The flash will be up on developer.nvidia.com in about a week.
Click to expand...
Click to collapse
My shield isn't rooted but im getting the same looping problem. I noticed recently though that on boot up my shield says the device is corrupt etc etc as though it has been rooted, but I've not modified anything.maybe this looping update caused that?
Will I need to wait and try and flash a factory image when it comes out?
Sent from my Pixel C using Tapatalk
You can NOT use OTA Updates if you are rooted. END!
The only way back is to factory reset the Shield. In the case of the Pro. This usually means a 2h wait.
Perhaps a quick reset might be enough? Though I have never attempted it before. But simply restoring a Recovery Image won't overwrite the /system Partition, clearing out the remnants of root. Thus allowing you to then update.
adam_purkis said:
My shield isn't rooted but im getting the same looping problem. I noticed recently though that on boot up my shield says the device is corrupt etc etc as though it has been rooted, but I've not modified anything.maybe this looping update caused that?
Will I need to wait and try and flash a factory image when it comes out?
Sent from my Pixel C using Tapatalk
Click to expand...
Click to collapse
Hi , i am new , having 2015 model
i getting a boot looping when updating and now stay at Nvida Logo page , can you or members here help me how to flash back 5.1 ?
sorry to trouble you.
thank you
Also, the update will definitely not take with TWRP. Looks like I have to wait until the developer release.
chow9229 said:
Hi , i am new , having 2015 model
i getting a boot looping when updating and now stay at Nvida Logo page , can you or members here help me how to flash back 5.1 ?
sorry to trouble you.
thank you
Click to expand...
Click to collapse
Hi, sorry can't give you detailed instructions right now. You'll find the info but a word of advice: Flash manually command by command in fastboot, DO NOT use the flash-all.bat and if you had 5.1 previously then there is no need to flash the bootloader (blob file). You need to be careful with that file, most hard bricks are caused by corrupted bootloader. Pay attention when downloading the Nvidia recovery image, make sure you get the one for your specific device model.
Cheers.
Sent from my Tapatalk beta Hub
If I helped hit the Thanks button. Follow Me! ~ DroidMote user ~ Full Android for Shield TV and Nexus Player
lavero.burgos said:
Hi, sorry can't give you detailed instructions right now. You'll find the info but a word of advice: Flash manually command by command in fastboot, DO NOT use the flash-all.bat and if you had 5.1 previously then there is no need to flash the bootloader (blob file). You need to be careful with that file, most hard bricks are caused by corrupted bootloader. Pay attention when downloading the Nvidia recovery image, make sure you get the one for your specific device model.
Cheers.
Sent from my Tapatalk beta Hub
If I helped hit the Thanks button. Follow Me! ~ DroidMote user ~ Full Android for Shield TV and Nexus Player
Click to expand...
Click to collapse
Hi , here my flash details
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 67108864 bytes
sending 'recovery' (13698 KB)...
OKAY [ 0.374s]
writing 'recovery'...
OKAY [ 0.580s]
finished. total time: 0.958s
C:\Program Files (x86)\Minimal ADB and Fastboot>
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot boot.img
target reported max download size of 67108864 bytes
sending 'boot' (10288 KB)...
OKAY [ 0.254s]
writing 'boot'...
OKAY [ 0.453s]
finished. total time: 0.712s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
target reported max download size of 67108864 bytes
erasing 'system'...
OKAY [ 0.347s]
sending sparse 'system' 1/31 (62437 KB)...
OKAY [ 1.594s]
writing 'system' 1/31...
OKAY [ 2.723s]
sending sparse 'system' 2/31 (62993 KB)...
OKAY [ 1.622s]
writing 'system' 2/31...
OKAY [ 2.720s]
sending sparse 'system' 3/31 (65443 KB)...
OKAY [ 1.810s]
writing 'system' 3/31...
OKAY [ 3.066s]
sending sparse 'system' 4/31 (65512 KB)...
OKAY [ 1.651s]
writing 'system' 4/31...
OKAY [ 2.788s]
sending sparse 'system' 5/31 (65532 KB)...
OKAY [ 1.671s]
writing 'system' 5/31...
OKAY [ 2.674s]
sending sparse 'system' 6/31 (63893 KB)...
OKAY [ 1.635s]
writing 'system' 6/31...
OKAY [ 2.673s]
sending sparse 'system' 7/31 (58260 KB)...
OKAY [ 1.475s]
writing 'system' 7/31...
OKAY [ 2.320s]
sending sparse 'system' 8/31 (59088 KB)...
OKAY [ 1.502s]
writing 'system' 8/31...
OKAY [ 2.355s]
sending sparse 'system' 9/31 (65533 KB)...
OKAY [ 1.680s]
writing 'system' 9/31...
OKAY [ 2.747s]
sending sparse 'system' 10/31 (64176 KB)...
OKAY [ 1.622s]
writing 'system' 10/31...
OKAY [ 2.494s]
sending sparse 'system' 11/31 (58956 KB)...
OKAY [ 1.504s]
writing 'system' 11/31...
OKAY [ 2.454s]
sending sparse 'system' 12/31 (65532 KB)...
OKAY [ 1.652s]
writing 'system' 12/31...
OKAY [ 2.736s]
sending sparse 'system' 13/31 (60898 KB)...
OKAY [ 1.555s]
writing 'system' 13/31...
OKAY [ 2.704s]
sending sparse 'system' 14/31 (62455 KB)...
OKAY [ 1.627s]
writing 'system' 14/31...
OKAY [ 2.751s]
sending sparse 'system' 15/31 (65532 KB)...
OKAY [ 1.707s]
writing 'system' 15/31...
OKAY [ 2.698s]
sending sparse 'system' 16/31 (65532 KB)...
OKAY [ 1.667s]
writing 'system' 16/31...
OKAY [ 2.690s]
sending sparse 'system' 17/31 (61848 KB)...
OKAY [ 1.551s]
writing 'system' 17/31...
OKAY [ 2.666s]
sending sparse 'system' 18/31 (61428 KB)...
OKAY [ 1.498s]
writing 'system' 18/31...
OKAY [ 2.491s]
sending sparse 'system' 19/31 (65532 KB)...
OKAY [ 1.650s]
writing 'system' 19/31...
OKAY [ 2.736s]
sending sparse 'system' 20/31 (65533 KB)...
OKAY [ 1.677s]
writing 'system' 20/31...
OKAY [ 2.791s]
sending sparse 'system' 21/31 (63217 KB)...
OKAY [ 1.610s]
writing 'system' 21/31...
OKAY [ 2.736s]
sending sparse 'system' 22/31 (65533 KB)...
OKAY [ 1.671s]
writing 'system' 22/31...
OKAY [ 2.857s]
sending sparse 'system' 23/31 (65053 KB)...
OKAY [ 1.714s]
writing 'system' 23/31...
OKAY [ 2.962s]
sending sparse 'system' 24/31 (65534 KB)...
OKAY [ 1.746s]
writing 'system' 24/31...
OKAY [ 3.063s]
sending sparse 'system' 25/31 (63170 KB)...
OKAY [ 1.623s]
writing 'system' 25/31...
OKAY [ 2.748s]
sending sparse 'system' 26/31 (60468 KB)...
OKAY [ 1.535s]
writing 'system' 26/31...
OKAY [ 2.602s]
sending sparse 'system' 27/31 (64617 KB)...
OKAY [ 1.618s]
writing 'system' 27/31...
OKAY [ 2.686s]
sending sparse 'system' 28/31 (65532 KB)...
OKAY [ 1.626s]
writing 'system' 28/31...
OKAY [ 2.682s]
sending sparse 'system' 29/31 (65532 KB)...
OKAY [ 1.644s]
writing 'system' 29/31...
OKAY [ 2.773s]
sending sparse 'system' 30/31 (65532 KB)...
OKAY [ 1.653s]
writing 'system' 30/31...
OKAY [ 2.734s]
sending sparse 'system' 31/31 (16061 KB)...
OKAY [ 0.496s]
writing 'system' 31/31...
OKAY [ 0.808s]
finished. total time: 131.663s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash userdata userdata.img
target reported max download size of 67108864 bytes
erasing 'userdata'...
OKAY [ 1.750s]
sending sparse 'userdata' 1/3 (65532 KB)...
OKAY [ 1.644s]
writing 'userdata' 1/3...
OKAY [ 2.672s]
sending sparse 'userdata' 2/3 (65532 KB)...
OKAY [ 1.617s]
writing 'userdata' 2/3...
OKAY [ 2.620s]
sending sparse 'userdata' 3/3 (5158 KB)...
OKAY [ 0.182s]
writing 'userdata' 3/3...
OKAY [ 0.386s]
finished. total time: 10.884s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash staging blob
target reported max download size of 67108864 bytes
sending 'staging' (3443 KB)...
OKAY [ 0.100s]
writing 'staging'...
OKAY [ 0.175s]
finished. total time: 0.278s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem dtbname
...
(bootloader) tegra210-foster-e-p2530-0930-e02-00.dtb
OKAY [ 0.006s]
finished. total time: 0.007s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash dtb tegra210-foster-e-p2530-0930-e02-00.dtb
error: cannot load 'tegra210-foster-e-p2530-0930-e02-00.dtb'
So i stuck at DTB flash, then i just fast reboot and it back alive, but it back factory default my SSD 500GB storage all gone.
I need to be reformat, remount as storage again and reinstall applications again. I also upgraded to 5.2 too.
just don't know why this update have problem, previously 3 updates (since june 2016) all no issue,
moreover this 5.2 update is the smallest files (140+MB) size compare to the other 3 updates.
can someone explain why? hopefully the next update it would not happen again.
I rather prefer big size file update then this.
BTW i wish to thanks everyone here share and help.
Thank You
I unrooted and still couldn't update. Factory reset did nothing.
adam_purkis said:
My shield isn't rooted but im getting the same looping problem. I noticed recently though that on boot up my shield says the device is corrupt etc etc as though it has been rooted, but I've not modified anything.maybe this looping update caused that?
Will I need to wait and try and flash a factory image when it comes out?
Sent from my Pixel C using Tapatalk
Click to expand...
Click to collapse
Did you unlock bootloader? If so that is why you are getting the device is corrupt message...
chow9229 said:
just don't know why this update have problem, previously 3 updates (since june 2016) all no issue,
moreover this 5.2 update is the smallest files (140+MB) size compare to the other 3 updates.
can someone explain why? hopefully the next update it would not happen again.
I rather prefer big size file update then this.
BTW i wish to thanks everyone here share and help.
Thank You
Click to expand...
Click to collapse
This update was different, it is a progressive update and it is the first time nvidia do that.
Enviado desde mi Redmi Note 4 mediante Tapatalk
AndroidUser00110001 said:
Did you unlock bootloader? If so that is why you are getting the device is corrupt message...
Click to expand...
Click to collapse
Nope didn't unlock anything it's fully stock and only bought it about 3 weeks ago.
If I flash the factory rom when they release it do you think that will help?
Sent from my D6503 using Tapatalk
adam_purkis said:
Nope didn't unlock anything it's fully stock and only bought it about 3 weeks ago.
If I flash the factory rom when they release it do you think that will help?
Sent from my D6503 using Tapatalk
Click to expand...
Click to collapse
Yes, most likely but are you able to boot into 5.1 system and use your shield normally?.

FAILED (remote: 'Chunk data size exceeds partition size') when flashing system.img

Hi, guys.
I couldn't install update 10.0.3.0 after restoring boot.img from Magisk.
So, I flash boot.img in fastboot but still cannot.
And then I found out maybe because Substratum modified system.img
Then I tried to flash 10.0.2.0 system.img using this command:
Code:
fastboot flash system_a system_10.0.2.0.img
and this error shown:
Code:
Sending sparse 'system_a' 1/3 (462332 KB) OKAY [ 10.736s]
Writing sparse 'system_a' 1/3 FAILED (remote: 'Chunk data size exceeds partition size')
Finished. Total time: 30.924s
I also tried these 2 commands get from this solution:
Code:
fastboot flash -S 256M system_a system_10.0.2.0.img
fastboot flash -S 128M system_a system_10.0.2.0.img
but same error.
Any help is appreciated.
current-slot:
Code:
D:\platform-tools>fastboot getvar current-slot
current-slot: a
Finished. Total time: 0.003s
Sorry guys, problem solved.
I don't know what happened, my phone suddenly stuck in bootloop?
no animation just black screen, increase brightness to 100 then drop to 0 then increase to 100 and cycle.
then I boot into fastboot and try flash again
Code:
D:\platform-tools>fastboot getvar current-slot
current-slot: a
Finished. Total time: 0.012s
D:\platform-tools>fastboot flash boot_a boot_10.0.2.0.img
Sending 'boot_a' (27219 KB) OKAY [ 0.633s]
Writing 'boot_a' OKAY [ 0.339s]
Finished. Total time: 0.996s
D:\platform-tools>fastboot flash system_a system_10.0.2.0.img
Sending sparse 'system_a' 1/4 (522236 KB) OKAY [ 17.728s]
Writing sparse 'system_a' 1/4 OKAY [ 5.516s]
Sending sparse 'system_a' 2/4 (522236 KB) OKAY [ 17.947s]
Writing sparse 'system_a' 2/4 OKAY [ 5.576s]
Sending sparse 'system_a' 3/4 (522236 KB) OKAY [ 17.854s]
Writing sparse 'system_a' 3/4 OKAY [ 5.629s]
Sending sparse 'system_a' 4/4 (447916 KB) OKAY [ 15.042s]
Writing sparse 'system_a' 4/4 OKAY [ 4.804s]
Finished. Total time: 148.451s
D:\platform-tools>fastboot reboot
Rebooting
Finished. Total time: 0.012s
now the system.img split into 522.236 MB instead of 462.332 MB and got 4 parts instead of 3?
wtf is happening!
Anyway, the updated is installed successfully.

Problems flashing a clean crosshatch 10 AOSP build to Pixel3XL

So, I just got a Pixel3 XL and am trying to build and flash my own clean AOSP build (as a starting point). I'm pretty technical, but new to the ROM world. (Would have posted in the ROM sub-forum, but my acct is brand new, if a mod wants to move it, cool.)
After successfully building, I'm getting an error halfway through running fastboot flashall now, after the reboot. Has anyone hit an error at Writing 'product_a'?
For my setup, I basically followed this awesome guide by @codevalley : https://forum.xda-developers.com/pixel-3/how-to/noobs-guide-to-building-aosp-scratch-t4012293
Since it was a new phone, the additional steps I had to do were:
* Connect to network in order to enable OEM unlock
* install the right drivers so fastboot would work, not just adb
* re-flash the OEM firmware, otherwise fastboot fails right away
The only oddball thing about my setup is that I'm building in an ubuntu VM and flashing it from windows after copying the whole target/product directory over.
Code:
C:\android-target\target\product\crosshatch>fastboot flashall
--------------------------------------------
Bootloader Version...: b1c1-0.2-5946827
Baseband Version.....: g845-00086-191011-B-5933466
Serial Number........: 95FY1XXXX
--------------------------------------------
Checking 'product' OKAY [ 0.044s]
Setting current slot to 'a' OKAY [ 0.512s]
Sending 'boot_a' (65536 KB) OKAY [ 0.432s]
Writing 'boot_a' OKAY [ 0.400s]
Sending 'dtbo_a' (8192 KB) OKAY [ 0.126s]
Writing 'dtbo_a' OKAY [ 0.087s]
Sending 'vbmeta_a' (4 KB) OKAY [ 0.099s]
Writing 'vbmeta_a' OKAY [ 0.039s]
Rebooting into fastboot OKAY [ 0.045s]
< waiting for any device >
Sending 'system_a' (4 KB) OKAY [ 0.002s]
Updating super partition OKAY [ 0.006s]
Resizing 'product_a' OKAY [ 0.006s]
Resizing 'system_a' OKAY [ 0.005s]
Resizing 'vendor_a' OKAY [ 0.006s]
Resizing 'product_a' OKAY [ 0.009s]
Sending 'product_a' (299008 KB) OKAY [ 1.783s]
Writing 'product_a' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Anyone got any thoughts? Googling this error is really not turning up much....
sam_242 said:
So, I just got a Pixel3 XL and am trying to build and flash my own clean AOSP build (as a starting point). I'm pretty technical, but new to the ROM world. (Would have posted in the ROM sub-forum, but my acct is brand new, if a mod wants to move it, cool.)
After successfully building, I'm getting an error halfway through running fastboot flashall now, after the reboot. Has anyone hit an error at Writing 'product_a'?
For my setup, I basically followed this awesome guide by @codevalley : https://forum.xda-developers.com/pixel-3/how-to/noobs-guide-to-building-aosp-scratch-t4012293
Since it was a new phone, the additional steps I had to do were:
* Connect to network in order to enable OEM unlock
* install the right drivers so fastboot would work, not just adb
* re-flash the OEM firmware, otherwise fastboot fails right away
The only oddball thing about my setup is that I'm building in an ubuntu VM and flashing it from windows after copying the whole target/product directory over.
Code:
C:\android-target\target\product\crosshatch>fastboot flashall
--------------------------------------------
Bootloader Version...: b1c1-0.2-5946827
Baseband Version.....: g845-00086-191011-B-5933466
Serial Number........: 95FY1XXXX
--------------------------------------------
Checking 'product' OKAY [ 0.044s]
Setting current slot to 'a' OKAY [ 0.512s]
Sending 'boot_a' (65536 KB) OKAY [ 0.432s]
Writing 'boot_a' OKAY [ 0.400s]
Sending 'dtbo_a' (8192 KB) OKAY [ 0.126s]
Writing 'dtbo_a' OKAY [ 0.087s]
Sending 'vbmeta_a' (4 KB) OKAY [ 0.099s]
Writing 'vbmeta_a' OKAY [ 0.039s]
Rebooting into fastboot OKAY [ 0.045s]
< waiting for any device >
Sending 'system_a' (4 KB) OKAY [ 0.002s]
Updating super partition OKAY [ 0.006s]
Resizing 'product_a' OKAY [ 0.006s]
Resizing 'system_a' OKAY [ 0.005s]
Resizing 'vendor_a' OKAY [ 0.006s]
Resizing 'product_a' OKAY [ 0.009s]
Sending 'product_a' (299008 KB) OKAY [ 1.783s]
Writing 'product_a' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Anyone got any thoughts? Googling this error is really not turning up much....
Click to expand...
Click to collapse
The only thing I see is that it is only flashing to slot_a. It is my understanding that you need to flash to both partitions a and b before the process will work. For me it has only worked when I flashed to both partitions. Also adding .\ before the command may help. For some reason it only flashes for me when I add it.
Sent from my Pixel 3 XL
Does the AOSP build process generate full OTA images similar to what are found here: https://developers.google.com/android/ota?
If so, try flashing just the bootloader in fastboot, boot into recovery, and sideload the full OTA.
sam_242 said:
So, I just got a Pixel3 XL and am trying to build and flash my own clean AOSP build (as a starting point). I'm pretty technical, but new to the ROM world. (Would have posted in the ROM sub-forum, but my acct is brand new, if a mod wants to move it, cool.)
After successfully building, I'm getting an error halfway through running fastboot flashall now, after the reboot. Has anyone hit an error at Writing 'product_a'?
For my setup, I basically followed this awesome guide by @codevalley : https://forum.xda-developers.com/pixel-3/how-to/noobs-guide-to-building-aosp-scratch-t4012293
Since it was a new phone, the additional steps I had to do were:
* Connect to network in order to enable OEM unlock
* install the right drivers so fastboot would work, not just adb
* re-flash the OEM firmware, otherwise fastboot fails right away
The only oddball thing about my setup is that I'm building in an ubuntu VM and flashing it from windows after copying the whole target/product directory over.
Code:
C:\android-target\target\product\crosshatch>fastboot flashall
--------------------------------------------
Bootloader Version...: b1c1-0.2-5946827
Baseband Version.....: g845-00086-191011-B-5933466
Serial Number........: 95FY1XXXX
--------------------------------------------
Checking 'product' OKAY [ 0.044s]
Setting current slot to 'a' OKAY [ 0.512s]
Sending 'boot_a' (65536 KB) OKAY [ 0.432s]
Writing 'boot_a' OKAY [ 0.400s]
Sending 'dtbo_a' (8192 KB) OKAY [ 0.126s]
Writing 'dtbo_a' OKAY [ 0.087s]
Sending 'vbmeta_a' (4 KB) OKAY [ 0.099s]
Writing 'vbmeta_a' OKAY [ 0.039s]
Rebooting into fastboot OKAY [ 0.045s]
< waiting for any device >
Sending 'system_a' (4 KB) OKAY [ 0.002s]
Updating super partition OKAY [ 0.006s]
Resizing 'product_a' OKAY [ 0.006s]
Resizing 'system_a' OKAY [ 0.005s]
Resizing 'vendor_a' OKAY [ 0.006s]
Resizing 'product_a' OKAY [ 0.009s]
Sending 'product_a' (299008 KB) OKAY [ 1.783s]
Writing 'product_a' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Anyone got any thoughts? Googling this error is really not turning up much....
Click to expand...
Click to collapse
I had this exact error running fastboot from shell on a Chromebook. Simply booting into the full Ubuntu installation I had installed on the Chromebook allowed me to flash.
I believed in my case the error was due to running out of memory. Though using an old fastboot version or a c -> c cable could also cause trouble.
You can also manually flash partitions instead of using the script. Remember, to get to fastbootd, you have to "fastboot reboot fastboot" from the bootloader.
ktmom said:
Though using an old fastboot version or a c -> c cable could also cause trouble.
Click to expand...
Click to collapse
Both of these are good points. You wouldn't think a USB-C to USB-C cable could cause fastboot problems but I've experienced this first hand. I can't quite remember the error I had, but I couldn't flash the stock factory images while using a USB-C to C cable. Switching to a USB-A to C cable (USB 2.0) resolved it.

Soft/Hard Brick help needed please

From the start: I was previously running the PixelDust ROM and wanted to try the 11 preview so i attempted to flash it via ADB commands. Script ran through the first time and finished overall but had some failed parts under the formatting section and rewriting partitions. With the first time using it i did forget to take out the -W string, well i purposely left it as i dont mind resetting the phone. Fast forward 8 hours, my phone still wont boot past the white google screen after NUMEROUS retries with flashing the 11 preview through ADB as well as using the flash-all. It also now shows the RED "your device is corrupted" screen on initial boot (not the standard yellow warning after unlocking) and seems like it bootloops to the bootloader or google screen and stays there. ANY help greatly appreciated.
Currently trying to use the Deuces flash-all script and latest version of Android 10. Will report
Welcome to Deuces Flashing Script!
v5.0-Windows
Checking if Fastboot exe is accessible..
Checking if Fastboot works correctly
fastboot version eac51f2bb6a8-android
Fastboot Detected!
Checking if device is detected via Fastboot.
Device Detected in Fastboot!
Are you SURE you want to continue?
Press Enter to continue...:
This tool will reformat partitions in your device!
It will attempt to keep your user data!
Data could be lost! - Use At Your Own Risk!
Continue? (y/N) y
Checking if bootloader is unlocked.
Look at device to confirm if script is waiting...
Preparing files for flash...
Extracting C:\Users\Tiffany\Downloads\Deuces-Bootloop-Recovery-Flashing-Script-master\Deuces-Bootloop-Recovery-Flashing-Script-master\taimen110.zip...
target reported max download size of 536870912 bytes
sending 'bootloader' (36356 KB)...
OKAY [ 0.940s]
writing 'bootloader'...
OKAY [ 0.388s]
finished. total time: 1.412s
target reported max download size of 536870912 bytes
sending 'radio' (60388 KB)...
OKAY [ 1.601s]
writing 'radio'...
OKAY [ 0.576s]
finished. total time: 2.198s
rebooting into bootloader...
OKAY [ 0.005s]
finished. total time: 0.008s
Extracting C:\Users\Tiffany\Downloads\Deuces-Bootloop-Recovery-Flashing-Script-master\Deuces-Bootloop-Recovery-Flashing-Script-master\_work\taimen-qq2a.200501.001.b3\image-taimen-qq2a.200501.001.b3.zip.
Flashing B-Slot items first.
target reported max download size of 536870912 bytes
erasing 'system_b'...
OKAY [ 0.033s]
sending 'system_b' (313556 KB)...
OKAY [ 8.515s]
writing 'system_b'...
OKAY [ 1.475s]
finished. total time: 10.358s
target reported max download size of 536870912 bytes
sending 'boot' (40960 KB)...
OKAY [ 1.086s]
writing 'boot'...
OKAY [ 0.372s]
finished. total time: 1.462s
target reported max download size of 536870912 bytes
sending 'dtbo' (8192 KB)...
OKAY [ 0.217s]
writing 'dtbo'...
OKAY [ 0.079s]
finished. total time: 0.302s
target reported max download size of 536870912 bytes
sending sparse 'system' (524284 KB)...
OKAY [ 26.436s]
writing 'system'...
OKAY [ 2.457s]
sending sparse 'system' (524284 KB)...
OKAY [ 25.678s]
writing 'system'...
OKAY [ 2.472s]
sending sparse 'system' (524284 KB)...
OKAY [ 24.613s]
writing 'system'...
OKAY [ 2.464s]
sending sparse 'system' (524284 KB)...
OKAY [ 25.794s]
writing 'system'...
OKAY [ 2.462s]
sending sparse 'system' (340260 KB)...
OKAY [ 15.858s]
writing 'system'...
OKAY [ 1.593s]
finished. total time: 129.943s
target reported max download size of 536870912 bytes
sending 'vbmeta' (4 KB)...
OKAY [ 0.004s]
writing 'vbmeta'...
OKAY [ 0.006s]
finished. total time: 0.012s
target reported max download size of 536870912 bytes
sending 'vendor' (349176 KB)...
OKAY [ 9.269s]
writing 'vendor'...
OKAY [ 1.645s]
finished. total time: 10.922s
Format UserData? (y/N) n
Done!
Press Enter to continue...:
Android 10 worked....

Categories

Resources