im getting this error when im flashing an image
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
MehmetCanWT said:
im getting this error when im flashing an image
View attachment 5694307
Click to expand...
Click to collapse
Newer devices have two modes for fastboot commands.
bootloader (fastboot).
fastboot (fastboot_d, fastbootd, or some other variation of the name).
Depending on the device, you might be able to enter fastboot_d by command.
adb reboot fastboot or fastboot reboot fastboot
Some devices you have to enter recovery and select an option to reboot to fastboot mode.
To enter recovery from command line.
recovery (recovery)
adb reboot recovery or fastboot reboot recovery
Example from OnePlus 7T.
Bootloader (fastboot).
Code:
Invalid sparse file format at header magic
Sending sparse 'system_ext' 1/2 (786356 KB) OKAY [ 32.517s]
Writing 'system_ext' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Invalid sparse file format at header magic
Sending sparse 'system' 1/2 (786288 KB) OKAY [ 32.146s]
Writing 'system' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Fastboot (fastboot_d).
Code:
Invalid sparse file format at header magic
Resizing 'system_ext_b' OKAY [ 0.004s]
Sending sparse 'system_ext_b' 1/6 (262112 KB) OKAY [ 11.085s]
Writing 'system_ext_b' OKAY [ 1.698s]
Sending sparse 'system_ext_b' 2/6 (262128 KB) OKAY [ 11.182s]
Writing 'system_ext_b' OKAY [ 1.708s]
Sending sparse 'system_ext_b' 3/6 (262116 KB) OKAY [ 10.854s]
Writing 'system_ext_b' OKAY [ 1.676s]
Sending sparse 'system_ext_b' 4/6 (262128 KB) OKAY [ 10.923s]
Writing 'system_ext_b' OKAY [ 1.677s]
Sending sparse 'system_ext_b' 5/6 (230160 KB) OKAY [ 9.749s]
Writing 'system_ext_b' OKAY [ 1.481s]
Sending sparse 'system_ext_b' 6/6 (158200 KB) OKAY [ 6.649s]
Writing 'system_ext_b' OKAY [ 1.071s]
Finished. Total time: 69.990s
Invalid sparse file format at header magic
Resizing 'system_b' OKAY [ 0.004s]
Sending sparse 'system_b' 1/6 (262108 KB) OKAY [ 10.725s]
Writing 'system_b' OKAY [ 1.684s]
Sending sparse 'system_b' 2/6 (262120 KB) OKAY [ 10.835s]
Writing 'system_b' OKAY [ 1.675s]
Sending sparse 'system_b' 3/6 (262060 KB) OKAY [ 10.865s]
Writing 'system_b' OKAY [ 1.676s]
Sending sparse 'system_b' 4/6 (262128 KB) OKAY [ 11.052s]
Writing 'system_b' OKAY [ 1.668s]
Sending sparse 'system_b' 5/6 (262140 KB) OKAY [ 11.024s]
Writing 'system_b' OKAY [ 1.676s]
Sending sparse 'system_b' 6/6 (32956 KB) OKAY [ 1.360s]
Writing 'system_b' OKAY [ 0.320s]
Finished. Total time: 64.798s
What device do you have?
If it is a Legion Phone Duel 2, then you more than likely need to flash using fastboot_d mode.
Hope it helps more than confuse.
Cheers.
ipdev said:
Newer devices have two modes for fastboot commands.
bootloader (fastboot).fastboot (fastboot_d, fastbootd, or some other variation of the name).
Depending on the device, you might be able to enter fastboot_d by command.
adb reboot fastboot or fastboot reboot fastboot
Some devices you have to enter recovery and select an option to reboot to fastboot mode.
To enter recovery from command line.
recovery (recovery)
adb reboot recovery or fastboot reboot recovery
Example from OnePlus 7T.
Bootloader (fastboot).
Code:
Invalid sparse file format at header magic
Sending sparse 'system_ext' 1/2 (786356 KB) OKAY [ 32.517s]
Writing 'system_ext' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Invalid sparse file format at header magic
Sending sparse 'system' 1/2 (786288 KB) OKAY [ 32.146s]
Writing 'system' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Fastboot (fastboot_d).
Code:
Invalid sparse file format at header magic
Resizing 'system_ext_b' OKAY [ 0.004s]
Sending sparse 'system_ext_b' 1/6 (262112 KB) OKAY [ 11.085s]
Writing 'system_ext_b' OKAY [ 1.698s]
Sending sparse 'system_ext_b' 2/6 (262128 KB) OKAY [ 11.182s]
Writing 'system_ext_b' OKAY [ 1.708s]
Sending sparse 'system_ext_b' 3/6 (262116 KB) OKAY [ 10.854s]
Writing 'system_ext_b' OKAY [ 1.676s]
Sending sparse 'system_ext_b' 4/6 (262128 KB) OKAY [ 10.923s]
Writing 'system_ext_b' OKAY [ 1.677s]
Sending sparse 'system_ext_b' 5/6 (230160 KB) OKAY [ 9.749s]
Writing 'system_ext_b' OKAY [ 1.481s]
Sending sparse 'system_ext_b' 6/6 (158200 KB) OKAY [ 6.649s]
Writing 'system_ext_b' OKAY [ 1.071s]
Finished. Total time: 69.990s
Invalid sparse file format at header magic
Resizing 'system_b' OKAY [ 0.004s]
Sending sparse 'system_b' 1/6 (262108 KB) OKAY [ 10.725s]
Writing 'system_b' OKAY [ 1.684s]
Sending sparse 'system_b' 2/6 (262120 KB) OKAY [ 10.835s]
Writing 'system_b' OKAY [ 1.675s]
Sending sparse 'system_b' 3/6 (262060 KB) OKAY [ 10.865s]
Writing 'system_b' OKAY [ 1.676s]
Sending sparse 'system_b' 4/6 (262128 KB) OKAY [ 11.052s]
Writing 'system_b' OKAY [ 1.668s]
Sending sparse 'system_b' 5/6 (262140 KB) OKAY [ 11.024s]
Writing 'system_b' OKAY [ 1.676s]
Sending sparse 'system_b' 6/6 (32956 KB) OKAY [ 1.360s]
Writing 'system_b' OKAY [ 0.320s]
Finished. Total time: 64.798s
What device do you have?
If it is a Legion Phone Duel 2, then you more than likely need to flash using fastboot_d mode.
Hope it helps more than confuse.
Cheers.
Click to expand...
Click to collapse
i have fastbootd and bootloader
my phone is trident a24
im flashing image on fastbootd
If you still get the error in fastbootd, then..
- Try a different usb cable or port.
- Make sure to use a USB-2 port on the computer.
Known issues using a USB-3 or USB-C port for flashing devices.
- Incompatible version of fastboot.
- Incompatible image file format or corrupted image file.
Newer versions of fastboot should detect the active slot.
Some older devices (and older fastboot), you have to call the slot you want to flash.
fastboot flash flash system_a legion.img
fastboot system_b legion.img
--
I looked up the trident a24, nice looking phone.
Released with Android 10 (?), it should be a slot device.
I could not find out if it was a normal A/B device or one of the odd few A-Olny slot devices.
You can find the current (active) slot.
fastboot getvar current-slot
You can set the active slot.
fastboot set_active a
fastboot set_active b
Cheers.
PS.
When I updated my main computer, I only have USB-C ports on new computer.
I use a cheap USB-C hub that includes a USB-2 port and do all my flashing using it.
i just waited a night and problem solved thanks to all
Related
Somehow I couldn't copy my music to my phone. Decided to check it out...
So the system image is using 109GB instead of 5-10GB as it should
Running the latest factory images NOF26V, freshly installed
Code:
finished. total time: 1.235s
MacBook-Pro-2:android iichel$ ./fastboot flash bootloader bootloader-sailfish-8996-012001-1611091517.img
target reported max download size of 536870912 bytes
sending 'bootloader_a' (32980 KB)...
OKAY [ 0.843s]
writing 'bootloader_a'...
(bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_a"
(bootloader) Flashing active slot "_a"
OKAY [ 15.964s]
finished. total time: 16.807s
MacBook-Pro-2:android iichel$ ./fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.046s]
finished. total time: 0.046s
MacBook-Pro-2:android iichel$ ./fastboot flash radio radio-sailfish-8996-012511-1611190200.img
target reported max download size of 536870912 bytes
sending 'radio_a' (57192 KB)...
OKAY [ 1.403s]
writing 'radio_a'...
OKAY [ 0.910s]
finished. total time: 2.314s
MacBook-Pro-2:android iichel$ ./fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.046s]
finished. total time: 0.046s
MacBook-Pro-2:android iichel$ ./fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot_a' (24801 KB)...
OKAY [ 0.652s]
writing 'boot_a'...
OKAY [ 0.611s]
finished. total time: 1.263s
MacBook-Pro-2:android iichel$ ./fastboot flash cache cache.img
error: cannot load 'cache.img'
MacBook-Pro-2:android iichel$ ./fastboot flash system system.img
target reported max download size of 536870912 bytes
erasing 'system_a'...
OKAY [ 0.995s]
sending sparse 'system_a' 1/4 (515466 KB)...
OKAY [ 15.869s]
writing 'system_a' 1/4...
OKAY [ 7.944s]
sending sparse 'system_a' 2/4 (495893 KB)...
OKAY [ 15.867s]
writing 'system_a' 2/4...
OKAY [ 10.045s]
sending sparse 'system_a' 3/4 (507843 KB)...
OKAY [ 15.358s]
writing 'system_a' 3/4...
OKAY [ 7.454s]
sending sparse 'system_a' 4/4 (32756 KB)...
OKAY [ 0.904s]
writing 'system_a' 4/4...
OKAY [ 0.651s]
finished. total time: 75.089s
MacBook-Pro-2:android iichel$ ./fastboot flash system_b system_other.img
target reported max download size of 536870912 bytes
erasing 'system_b'...
OKAY [ 1.043s]
sending sparse 'system_b' 1/4 (517080 KB)...
OKAY [ 14.369s]
writing 'system_b' 1/4...
OKAY [ 4.792s]
sending sparse 'system_b' 2/4 (514384 KB)...
OKAY [ 14.517s]
writing 'system_b' 2/4...
OKAY [ 4.998s]
sending sparse 'system_b' 3/4 (524287 KB)...
OKAY [ 14.612s]
writing 'system_b' 3/4...
OKAY [ 4.540s]
sending sparse 'system_b' 4/4 (85786 KB)...
OKAY [ 2.549s]
writing 'system_b' 4/4...
OKAY [ 1.201s]
finished. total time: 62.622s
MacBook-Pro-2:android iichel$ ./fastboot flash vendor vendor.img
target reported max download size of 536870912 bytes
erasing 'vendor_a'...
OKAY [ 0.503s]
sending 'vendor_a' (235186 KB)...
OKAY [ 5.849s]
writing 'vendor_a'...
OKAY [ 6.707s]
finished. total time: 13.060s
MacBook-Pro-2:android iichel$ ./fastboot flash modem modem.img
target reported max download size of 536870912 bytes
sending 'modem_a' (57184 KB)...
OKAY [ 1.431s]
writing 'modem_a'...
OKAY [ 0.849s]
finished. total time: 2.280s
MacBook-Pro-2:android iichel$ ./fastboot flash userdata userdata.img
target reported max download size of 536870912 bytes
erasing 'userdata'...
OKAY [ 29.416s]
sending 'userdata' (136402 KB)...
OKAY [ 3.444s]
writing 'userdata'...
OKAY [ 1.159s]
finished. total time: 34.019s
MacBook-Pro-2:android iichel$ ./fastboot reboot
rebooting...
Found a similar thread, but a factory reset didn't fix my issue either:
https://forum.xda-developers.com/pixel/help/7-1-1-taking-109gb-storage-t3522967
Pluisje89 said:
Somehow I couldn't copy my music to my phone. Decided to check it out...
So the system image is using 109GB instead of 5-10GB as it should
Running the latest factory images NOF26V, freshly installed
Code:
finished. total time: 1.235s
MacBook-Pro-2:android iichel$ ./fastboot flash bootloader bootloader-sailfish-8996-012001-1611091517.img
target reported max download size of 536870912 bytes
sending 'bootloader_a' (32980 KB)...
OKAY [ 0.843s]
writing 'bootloader_a'...
(bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_a"
(bootloader) Flashing active slot "_a"
OKAY [ 15.964s]
finished. total time: 16.807s
MacBook-Pro-2:android iichel$ ./fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.046s]
finished. total time: 0.046s
MacBook-Pro-2:android iichel$ ./fastboot flash radio radio-sailfish-8996-012511-1611190200.img
target reported max download size of 536870912 bytes
sending 'radio_a' (57192 KB)...
OKAY [ 1.403s]
writing 'radio_a'...
OKAY [ 0.910s]
finished. total time: 2.314s
MacBook-Pro-2:android iichel$ ./fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.046s]
finished. total time: 0.046s
MacBook-Pro-2:android iichel$ ./fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot_a' (24801 KB)...
OKAY [ 0.652s]
writing 'boot_a'...
OKAY [ 0.611s]
finished. total time: 1.263s
MacBook-Pro-2:android iichel$ ./fastboot flash cache cache.img
error: cannot load 'cache.img'
MacBook-Pro-2:android iichel$ ./fastboot flash system system.img
target reported max download size of 536870912 bytes
erasing 'system_a'...
OKAY [ 0.995s]
sending sparse 'system_a' 1/4 (515466 KB)...
OKAY [ 15.869s]
writing 'system_a' 1/4...
OKAY [ 7.944s]
sending sparse 'system_a' 2/4 (495893 KB)...
OKAY [ 15.867s]
writing 'system_a' 2/4...
OKAY [ 10.045s]
sending sparse 'system_a' 3/4 (507843 KB)...
OKAY [ 15.358s]
writing 'system_a' 3/4...
OKAY [ 7.454s]
sending sparse 'system_a' 4/4 (32756 KB)...
OKAY [ 0.904s]
writing 'system_a' 4/4...
OKAY [ 0.651s]
finished. total time: 75.089s
MacBook-Pro-2:android iichel$ ./fastboot flash system_b system_other.img
target reported max download size of 536870912 bytes
erasing 'system_b'...
OKAY [ 1.043s]
sending sparse 'system_b' 1/4 (517080 KB)...
OKAY [ 14.369s]
writing 'system_b' 1/4...
OKAY [ 4.792s]
sending sparse 'system_b' 2/4 (514384 KB)...
OKAY [ 14.517s]
writing 'system_b' 2/4...
OKAY [ 4.998s]
sending sparse 'system_b' 3/4 (524287 KB)...
OKAY [ 14.612s]
writing 'system_b' 3/4...
OKAY [ 4.540s]
sending sparse 'system_b' 4/4 (85786 KB)...
OKAY [ 2.549s]
writing 'system_b' 4/4...
OKAY [ 1.201s]
finished. total time: 62.622s
MacBook-Pro-2:android iichel$ ./fastboot flash vendor vendor.img
target reported max download size of 536870912 bytes
erasing 'vendor_a'...
OKAY [ 0.503s]
sending 'vendor_a' (235186 KB)...
OKAY [ 5.849s]
writing 'vendor_a'...
OKAY [ 6.707s]
finished. total time: 13.060s
MacBook-Pro-2:android iichel$ ./fastboot flash modem modem.img
target reported max download size of 536870912 bytes
sending 'modem_a' (57184 KB)...
OKAY [ 1.431s]
writing 'modem_a'...
OKAY [ 0.849s]
finished. total time: 2.280s
MacBook-Pro-2:android iichel$ ./fastboot flash userdata userdata.img
target reported max download size of 536870912 bytes
erasing 'userdata'...
OKAY [ 29.416s]
sending 'userdata' (136402 KB)...
OKAY [ 3.444s]
writing 'userdata'...
OKAY [ 1.159s]
finished. total time: 34.019s
MacBook-Pro-2:android iichel$ ./fastboot reboot
rebooting...
Found a similar thread, but a factory reset didn't fix my issue either:
https://forum.xda-developers.com/pixel/help/7-1-1-taking-109gb-storage-t3522967
Click to expand...
Click to collapse
That only seems to add up to 4 GB. Open up a root Explorer and see what it tells you.
Hello Friends! I'm Getting This Error While I'm Trying To Flash Stock Rom In Lenovo TB-8704X.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
<!-----The Error Msg Start-----!>
Sending 'tz' (1519 KB) OKAY [ 0.071s]
Writing 'tz' FAILED (remote: 'Critical partition flashing is not allowed')
fastboot: error: Command failed
Sending 'sbl1' (378 KB) OKAY [ 0.039s]
Writing 'sbl1' FAILED (remote: 'Critical partition flashing is not allowed')
fastboot: error: Command failed
Sending 'rpm' (170 KB) OKAY [ 0.037s]
Writing 'rpm' FAILED (remote: 'Critical partition flashing is not allowed')
fastboot: error: Command failed
Sending 'aboot' (605 KB) OKAY [ 0.047s]
Writing 'aboot' FAILED (remote: 'Critical partition flashing is not allowed')
fastboot: error: Command failed
Sending 'devcfg' (38 KB) OKAY [ 0.037s]
Writing 'devcfg' OKAY [ 0.020s]
Finished. Total time: 0.111s
Sending 'keymaster' (220 KB) OKAY [ 0.026s]
Writing 'keymaster' OKAY [ 0.005s]
Finished. Total time: 0.160s
Sending 'cmnlib' (200 KB) OKAY [ 0.037s]
Writing 'cmnlib' OKAY [ 0.012s]
Finished. Total time: 0.122s
Sending 'cmnlib64' (254 KB) OKAY [ 0.036s]
Writing 'cmnlib64' OKAY [ 0.017s]
Finished. Total time: 0.110s
Sending 'tzbak' (1519 KB) OKAY [ 0.077s]
Writing 'tzbak' OKAY [ 0.013s]
Finished. Total time: 0.159s
Sending 'sbl1bak' (378 KB) OKAY [ 0.047s]
Writing 'sbl1bak' OKAY [ 0.016s]
Finished. Total time: 0.123s
Sending 'rpmbak' (170 KB) OKAY [ 0.036s]
Writing 'rpmbak' OKAY [ 0.017s]
Finished. Total time: 0.105s
Sending 'abootbak' (605 KB) OKAY [ 0.047s]
Writing 'abootbak' OKAY [ 0.018s]
Finished. Total time: 0.126s
Sending 'devcfgbak' (38 KB) OKAY [ 0.037s]
Writing 'devcfgbak' OKAY [ 0.010s]
Finished. Total time: 0.123s
Sending 'keymasterbak' (220 KB) OKAY [ 0.031s]
Writing 'keymasterbak' OKAY [ 0.009s]
Finished. Total time: 0.112s
Sending 'cmnlibbak' (200 KB) OKAY [ 0.036s]
Writing 'cmnlibbak' OKAY [ 0.005s]
Finished. Total time: 0.117s
Sending 'cmnlib64bak' (254 KB) OKAY [ 0.027s]
Writing 'cmnlib64bak' OKAY [ 0.011s]
Finished. Total time: 0.122s
Erasing 'boot' OKAY [ 0.027s]
Finished. Total time: 0.055s
Sending 'modem' (86016 KB) OKAY [ 3.267s]
Writing 'modem' OKAY [ 0.399s]
Finished. Total time: 3.836s
fastboot: error: cannot load 'system.img': No such file or directory
Sending 'cache' (6248 KB) OKAY [ 0.249s]
Writing 'cache' OKAY [ 0.040s]
Finished. Total time: 0.479s
fastboot: error: cannot load 'userdata.img': No such file or directory
Sending 'recovery' (16587 KB) OKAY [ 0.699s]
Writing 'recovery' OKAY [ 0.079s]
Finished. Total time: 0.896s
Sending 'dsp' (16384 KB) OKAY [ 0.641s]
Writing 'dsp' OKAY [ 0.085s]
Finished. Total time: 0.816s
Sending 'mdtp' (17390 KB) OKAY [ 0.724s]
Writing 'mdtp' OKAY [ 0.093s]
Finished. Total time: 0.919s
Erasing 'splash' OKAY [ 0.025s]
Finished. Total time: 0.057s
Sending 'splash' (313 KB) OKAY [ 0.047s]
Writing 'splash' OKAY [ 0.009s]
Finished. Total time: 0.182s
Erasing 'DDR' OKAY [ 0.018s]
Finished. Total time: 0.045s
Sending 'boot' (11741 KB) OKAY [ 0.366s]
Writing 'boot' OKAY [ 0.053s]
Finished. Total time: 0.723s
Rebooting OKAY [ 0.008s]
Finished. Total time: 0.023s
Press any key to continue . . .
<!-----Error Msg End-----!>
And One MOre Thing! In The Stock Rom, There Is system.img and userdata.img Files Are Missing.
I Have Downloaded Stock Rom From Many Popular Sites, But Those Files Are Missing Also There.
...
Then I Have Tryed To Flash With QFIL
But I Got These Error Here:
Can Any One Please Help Me About This? I Don't Have Any Recovery In This Devices. So I Have To Do This With PC.
Pls If U or Your Any Friend Know a Solution About This Then Tell ME PLS
<!-----More Attachment-----!>
Unlock Critical partitions by means of Fastboot then retry.
jwoegerbauer said:
Unlock Critical partitions by means of Fastboot then retry.
Click to expand...
Click to collapse
So How Can I Unlock It?
Code:
fastboot flashing unlock_critical
jwoegerbauer said:
Code:
fastboot flashing unlock_critical
Click to expand...
Click to collapse
Thanks A Lot. But There Is system.img and userdata.img File are Missing. Can U Please Help Me?
Looks like the ROM you try to flash is corrupted, because the 2 mentioned img-files are missing therein.
jwoegerbauer said:
Looks like the ROM you try to flash is corrupted, because the 2 mentioned img-files are missing therein.
Click to expand...
Click to collapse
No, I Don't think soo. I Have Downloaded Rom From Many Popular Site. But There's Also these files are missing. And In the QcomDloader Tool, When I Try to flash. It Says, "Cannot Read Rawprogram.xml" file
Well, you have a contrary opinion ...
If you're using the same .xml firmware in fastboot as you are in QPST or QFIL the system.img file is most likely system_1.img system_2.img and so on, quite a few of them. Just check your firmware and see what your missing files are named or if they are actually missing.
tek3195 said:
If you're using the same .xml firmware in fastboot as you are in QPST or QFIL the system.img file is most likely system_1.img system_2.img and so on, quite a few of them. Just check your firmware and see what your missing files are named or if they are actually missing.
Click to expand...
Click to collapse
Yes U Are Right! There Is System.img and userdata.img File Are Missing. But system_1.img to system_47.img (47 System.img files) and userdata_1.img to userdata_77.img (77 userdata.img files) are exist. But How Can I Flash Them with QFIL/QcomDloader/Fastboot Mode?? And The Raw program or other xml files are not damaged. I can open them with notepad++ and XML Language is All right.
[email protected] said:
Yes U Are Right! There Is System.img and userdata.img File Are Missing. But system_1.img to system_47.img (47 System.img files) and userdata_1.img to userdata_77.img (77 userdata.img files) are exist. But How Can I Flash Them with QFIL/QcomDloader/Fastboot Mode?? And The Raw program or other xml files are not damaged. I can open them with notepad++ and XML Language is All right.
Click to expand...
Click to collapse
ok, you are looking at the diff between using raw and sparse images. When you ask how to with QFIL/QcomDloader/Fastboot Mode you can't use them the same way. QFIL and the double handful of Qualcomm flashing utilities like it don't use fastboot, they use sahara. They are different protocols dealing with different formats. I linked a short tutorial to point you in the right direction, maybe, or I hope so anyway. tutorial
It's almost done...
D!OS is rolling out the next Days. It's pretty basic for now. Based on latest Android 12.1/12L with Google Apps.
If You want to be one of the first who uses this new Xperia exclusive OS, leave a Comment and become a Tester!
Need Testers for J9110 Xperia 1 Dual Sim
J8110 Xperia 1 Single Sim Builds will come later. But feel free to try out the Xperia 1 Dual Sim Variant...
I'm in!
mikaelgr717 said:
I'm in!
Click to expand...
Click to collapse
Great. You can grab the Zip from here once it's uploaded:
Dev Ice Technologies - AOSXP
AOSXP (PREVIEW)
sites.google.com
Just extract the Zip to Your Fastboot Folder and double click the AOSXP Flash .bat File
Download and extract the Xperia Software Binaries from Sony to the same folder
Rename the Image to oem.img and run the OEM Flash .bat File to flash the Binaries
Done. You can access the Recovery by holding Volume down while turning on the Device. In case You want to wipe or so...
Please leave Feedback here once You tried it
I give it a try.
(J9110)
It's up. Camera may not work and same for Mobile Data but thats due to the SODP and should be fixed soon...
And thanks for Your Interest Folks! Really looking forward to let AOSXP grow as owner of Dev Ice Technologies (The Company behind it). Be prepared for awesome Things!
im stuck on sony boot logo, im not sure maybe i use a wrong Software Binaries??
SW_BINARIES_FOR_XPERIA_ANDROID_12_4.19_V1C_KUMANO.ZIP
xpt1 said:
im stuck on sony boot logo, im not sure maybe i use a wrong Software Binaries??
SW_BINARIES_FOR_XPERIA_ANDROID_12_4.19_V1C_KUMANO.ZIP
Click to expand...
Click to collapse
You did everything right i guess. So it stays at the Sony boot logo not the Android Bootanimation?
Sounds like an SElinux issue in this case. I will set it to permissive and upload an new Zip. Thanks for Your Feedback btw!
Miustone said:
You did everything right i guess. So it stays at the Sony boot logo not the Android Bootanimation?
Sounds like an SElinux issue in this case. I will set it to permissive and upload an new Zip. Thanks for Your Feedback btw!
Click to expand...
Click to collapse
yes it stop at the sony logo.
xpt1 said:
yes it stop at the sony logo.
Click to expand...
Click to collapse
Dang. I played around with Permissions and SElinux. Should be fixed now. I also found some neat things out. The next drop should boot and include some cool stuff from the Pixels
Ill keep You informed...
Miustone said:
Dang. I played around with Permissions and SElinux. Should be fixed now. I also found some neat things out. The next drop should boot and include some cool stuff from the Pixels
Ill keep You informed...
Click to expand...
Click to collapse
did you update/upload the fixed AOSXP_J9110.zip ?
i tryed it again but same problem stuck on sony logo
xpt1 said:
did you update/upload the fixed AOSXP_J9110.zip ?
i tryed it again but same problem stuck on sony logo
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
No, but work is going on. 10 Hours+ each day
Any news about AOSXP for now?
Miustone said:
伟大的。上传后，您可以从此处获取 Zip：
Dev Ice Technologies - AOSXP
AOSXP (PREVIEW)
sites.google.com
只需将 Zip 解压缩到您的 Fastboot 文件夹，然后双击 AOSXP Flash .bat 文件
从 Sony 下载 Xperia 软件二进制文件并将其解压缩到同一文件夹
将映像重命名为 oem.img 并运行 OEM Flash .bat 文件以刷新二进制文件
完毕。您可以通过在打开设备时按住音量来访问恢复。万一你想擦什么……
尝试后请在此处留下反馈
Click to expand...
Click to collapse
惯于
New Builds incoming! Be prepared for something You haven't ever seen before <3
#D!OS
Miustone said:
New Builds incoming! Be prepared for something You haven't ever seen before <3
#D!OS
Click to expand...
Click to collapse
Can you also insert the sony camera apk, I need the dedicated button, the button unfortunately does not work with gcam
D!OS_J9110.zip tested right now, still stuck on sony logo.
xpt1 said:
D!OS_J9110.zip tested right now, still stuck on sony logo.
Click to expand...
Click to collapse
Time for troubleshooting. What did the Script Say? Flashing was fine?
Flashed latest and correct oem with the other Script? Are You on latest Android Stock before flashing D!OS?
Miustone said:
Time for troubleshooting. What did the Script Say? Flashing was fine?
Flashed latest and correct oem with the other Script? Are You on latest Android Stock before flashing D!OS?
Click to expand...
Click to collapse
Miustone said:
Time for troubleshooting. What did the Script Say? Flashing was fine?
Flashed latest and correct oem with the other Script? Are You on latest Android Stock before flashing D!OS?
Click to expand...
Click to collapse
my latest android stock: J9110_Customized EU_55.2.A.4.332-R10C
oem: SW_binaries_for_Xperia_Android_12_4.19_v1c_kumano.img ( renamed to oem.img )
i will flash one more time an copy the script.
D!OS installation started...
Setting current slot to 'a' OKAY [ 0.016s]
Finished. Total time: 0.016s
Sending 'dtbo_a' (8192 KB) OKAY [ 0.188s]
Writing 'dtbo_a' OKAY [ 0.031s]
Finished. Total time: 0.266s
Sending 'dtbo_b' (8192 KB) OKAY [ 0.203s]
Writing 'dtbo_b' OKAY [ 0.047s]
Finished. Total time: 0.297s
Sending 'vbmeta_a' (8 KB) OKAY [ 0.015s]
Writing 'vbmeta_a' OKAY [ 0.000s]
Finished. Total time: 0.031s
Sending 'vbmeta_b' (8 KB) OKAY [ 0.016s]
Writing 'vbmeta_b' OKAY [ 0.000s]
Finished. Total time: 0.031s
Sending 'boot_a' (65536 KB) OKAY [ 1.515s]
Writing 'boot_a' OKAY [ 0.266s]
Finished. Total time: 2.203s
Sending 'boot_b' (65536 KB) OKAY [ 1.531s]
Writing 'boot_b' OKAY [ 0.251s]
Finished. Total time: 2.235s
Sending 'vendor_a' (117496 KB) OKAY [ 2.745s]
Writing 'vendor_a' OKAY [ 0.000s]
Finished. Total time: 2.776s
Sending 'vendor_b' (117496 KB) OKAY [ 2.777s]
Writing 'vendor_b' OKAY [ 0.000s]
Finished. Total time: 4.104s
Sending sparse 'system_a' 1/5 (775200 KB) OKAY [ 18.492s]
Writing 'system_a' OKAY [ 0.000s]
Sending sparse 'system_a' 2/5 (774120 KB) OKAY [ 18.532s]
Writing 'system_a' OKAY [ 0.000s]
Sending sparse 'system_a' 3/5 (774120 KB) OKAY [ 18.708s]
Writing 'system_a' OKAY [ 0.000s]
Sending sparse 'system_a' 4/5 (774120 KB) OKAY [ 18.525s]
Writing 'system_a' OKAY [ 0.016s]
Sending sparse 'system_a' 5/5 (566052 KB) OKAY [ 13.684s]
Writing 'system_a' OKAY [ 0.000s]
Finished. Total time: 89.373s
Sending sparse 'system_b' 1/5 (775200 KB) OKAY [ 18.204s]
Writing 'system_b' OKAY [ 0.000s]
Sending sparse 'system_b' 2/5 (774120 KB) OKAY [ 18.467s]
Writing 'system_b' OKAY [ 0.016s]
Sending sparse 'system_b' 3/5 (774120 KB) OKAY [ 18.560s]
Writing 'system_b' OKAY [ 0.000s]
Sending sparse 'system_b' 4/5 (774120 KB) OKAY [ 18.448s]
Writing 'system_b' OKAY [ 0.000s]
Sending sparse 'system_b' 5/5 (566052 KB) OKAY [ 13.607s]
Writing 'system_b' OKAY [ 0.000s]
Finished. Total time: 94.854s
Sending 'userdata' (544 KB) OKAY [ 0.016s]
Writing 'userdata' OKAY [ 0.000s]
Finished. Total time: 7.708s
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.000s
D!OS installed. Press any Key to exit...
XPERIA OEM installation started...
Rebooting into bootloader OKAY [ 0.001s]
Finished. Total time: 0.005s
Sending 'oem_a' (279196 KB) OKAY [ 7.131s]
Writing 'oem_a' OKAY [ 13.073s]
Finished. Total time: 20.283s
Sending 'oem_b' (279196 KB) OKAY [ 6.522s]
Writing 'oem_b' OKAY [ 13.005s]
Finished. Total time: 19.558s
Erasing 'userdata' OKAY [ 76.212s]
mke2fs 1.46.2 (28-Feb-2021)
Creating filesystem with 28074734 4k blocks and 7020544 inodes
Filesystem UUID: b91d1bf4-c4b1-11ec-a85f-5f6820032de7
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872
Allocating group tables: done
Writing inode tables: done
Creating journal (131072 blocks): done
Writing superblocks and filesystem accounting information: done
Sending 'userdata' (544 KB) OKAY [ 0.016s]
Writing 'userdata' OKAY [ 0.000s]
Erasing 'metadata' FAILED (remote: 'Erasing is not allowed for partition
')
fastboot: error: Command failed
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.000s
XPERIA OEM installed. Press any Key to exit...
Updated the image on a Pixel 6a today and my eye caught this error. So I flased it again and again the same error? Is this normal? What is it? See log below.
Thanks
C:\ADB>adb devices
List of devices attached
12345ABCD12345 device
C:\ADB>adb reboot bootloader
C:\ADB>flash-all.bat
Sending 'bootloader_a' (11558 KB) OKAY [ 0.288s]
Writing 'bootloader_a' (bootloader) Flashing pack version bluejay-1.2-8893284
(bootloader) flashing platform gs101
(bootloader) Validating partition ufs
(bootloader) Validating partition ufs
(bootloader) Validating partition partition:0
(bootloader) Validating partition partition:1
(bootloader) Validating partition partition:2
(bootloader) Validating partition partition:3
(bootloader) Validating partition bl1_a
(bootloader) Validating partition pbl_a
(bootloader) Validating partition bl2_a
(bootloader) Validating partition abl_a
(bootloader) Validating partition bl31_a
(bootloader) Validating partition tzsw_a
(bootloader) Validating partition gsa_a
(bootloader) Validating partition ldfw_a
(bootloader) Flashing partition ufs
(bootloader) Flashing partition ufs
(bootloader) Flashing partition partition:0
(bootloader) Flashing partition partition:1
(bootloader) Flashing partition partition:2
(bootloader) Flashing partition partition:3
(bootloader) Flashing partition bl1_a
(bootloader) Flashing partition pbl_a
(bootloader) Flashing partition bl2_a
(bootloader) Flashing partition abl_a
(bootloader) Flashing partition bl31_a
(bootloader) Flashing partition tzsw_a
(bootloader) Flashing partition gsa_a
(bootloader) Flashing partition ldfw_a
(bootloader) Loading sideload ufsfwupdate
OKAY [ 2.862s]
Finished. Total time: 3.178s
Rebooting into bootloader OKAY [ 0.001s]
Finished. Total time: 0.001s
Sending 'radio_a' (82772 KB) OKAY [ 2.051s]
Writing 'radio_a' (bootloader) Flashing pack version g5123b-102852-220720-M-8851166
(bootloader) Flashing partition modem_a
OKAY [ 0.143s]
Finished. Total time: 2.205s
Rebooting into bootloader OKAY [ 0.001s]
Finished. Total time: 0.002s
--------------------------------------------
Bootloader Version...: bluejay-1.2-8893284
Baseband Version.....: g5123b-102852-220720-B-8851166
Serial Number........: 12345ABCD12345
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.001s]
Checking 'version-bootloader' OKAY [ 0.000s]
Checking 'version-baseband' OKAY [ 0.000s]
Setting current slot to 'a' OKAY [ 0.069s]
extracting boot.img (64 MB) to disk... took 0.250s
archive does not contain 'boot.sig'
Sending 'boot_a' (65536 KB) OKAY [ 1.619s]
Writing 'boot_a' OKAY [ 0.112s]
archive does not contain 'init_boot.img'
extracting dtbo.img (16 MB) to disk... took 0.042s
archive does not contain 'dtbo.sig'
Sending 'dtbo_a' (16384 KB) OKAY [ 0.405s]
Writing 'dtbo_a' OKAY [ 0.024s]
archive does not contain 'dt.img'
extracting pvmfw.img (1 MB) to disk... took 0.003s
archive does not contain 'pvmfw.sig'
Sending 'pvmfw_a' (1024 KB) OKAY [ 0.026s]
Writing 'pvmfw_a' OKAY [ 0.004s]
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta_a' (12 KB) OKAY [ 0.001s]
Writing 'vbmeta_a' OKAY [ 0.002s]
extracting vbmeta_system.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta_system.sig'
Sending 'vbmeta_system_a' (4 KB) OKAY [ 0.000s]
Writing 'vbmeta_system_a' OKAY [ 0.003s]
extracting vbmeta_vendor.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta_vendor.sig'
Sending 'vbmeta_vendor_a' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_vendor_a' OKAY [ 0.002s]
extracting vendor_boot.img (64 MB) to disk... took 0.271s
archive does not contain 'vendor_boot.sig'
Sending 'vendor_boot_a' (65536 KB) OKAY [ 1.618s]
Writing 'vendor_boot_a' OKAY [ 0.116s]
archive does not contain 'vendor_kernel_boot.img'
extracting super_empty.img (0 MB) to disk... took 0.001s
Rebooting into fastboot OKAY [ 0.001s]
< waiting for any device >
Sending 'super' (4 KB) OKAY [ 0.001s]
Updating super partition OKAY [ 0.022s]
Resizing 'product_a' OKAY [ 0.006s]
Resizing 'system_a' OKAY [ 0.004s]
Resizing 'system_ext_a' OKAY [ 0.004s]
Resizing 'system_b' OKAY [ 0.004s]
Resizing 'vendor_a' OKAY [ 0.003s]
Resizing 'vendor_dlkm_a' OKAY [ 0.003s]
Resizing 'vendor_b' OKAY [ 0.003s]
archive does not contain 'boot_other.img'
archive does not contain 'odm.img'
archive does not contain 'odm_dlkm.img'
extracting product.img (2761 MB) to disk... took 11.348s
Invalid sparse file format at header magic
archive does not contain 'product.sig'
Resizing 'product_a' OKAY [ 0.011s]
Sending sparse 'product_a' 1/11 (262116 KB) OKAY [ 6.789s]
Writing 'product_a' OKAY [ 0.414s]
Sending sparse 'product_a' 2/11 (262120 KB) OKAY [ 6.782s]
Writing 'product_a' OKAY [ 0.385s]
Sending sparse 'product_a' 3/11 (262128 KB) OKAY [ 6.773s]
Writing 'product_a' OKAY [ 0.417s]
Sending sparse 'product_a' 4/11 (262120 KB) OKAY [ 6.785s]
Writing 'product_a' OKAY [ 0.378s]
Sending sparse 'product_a' 5/11 (262120 KB) OKAY [ 6.774s]
Writing 'product_a' OKAY [ 0.402s]
Sending sparse 'product_a' 6/11 (262124 KB) OKAY [ 6.781s]
Writing 'product_a' OKAY [ 0.373s]
Sending sparse 'product_a' 7/11 (262124 KB) OKAY [ 6.807s]
Writing 'product_a' OKAY [ 0.437s]
Sending sparse 'product_a' 8/11 (262128 KB) OKAY [ 6.831s]
Writing 'product_a' OKAY [ 0.393s]
Sending sparse 'product_a' 9/11 (262132 KB) OKAY [ 6.804s]
Writing 'product_a' OKAY [ 0.401s]
Sending sparse 'product_a' 10/11 (262096 KB) OKAY [ 6.809s]
Writing 'product_a' OKAY [ 0.408s]
Sending sparse 'product_a' 11/11 (197804 KB) OKAY [ 5.233s]
Writing 'product_a' OKAY [ 0.323s]
extracting system.img (831 MB) to disk... took 3.673s
Invalid sparse file format at header magic
archive does not contain 'system.sig'
Resizing 'system_a' OKAY [ 0.010s]
Sending sparse 'system_a' 1/4 (262116 KB) OKAY [ 6.908s]
Writing 'system_a' OKAY [ 0.411s]
Sending sparse 'system_a' 2/4 (262116 KB) OKAY [ 6.871s]
Writing 'system_a' OKAY [ 0.425s]
Sending sparse 'system_a' 3/4 (262140 KB) OKAY [ 6.825s]
Writing 'system_a' OKAY [ 0.423s]
Sending sparse 'system_a' 4/4 (62708 KB) OKAY [ 1.645s]
Writing 'system_a' OKAY [ 0.173s]
archive does not contain 'system_dlkm.img'
extracting system_ext.img (345 MB) to disk... took 1.538s
Invalid sparse file format at header magic
archive does not contain 'system_ext.sig'
Resizing 'system_ext_a' OKAY [ 0.010s]
Sending sparse 'system_ext_a' 1/2 (262132 KB) OKAY [ 6.850s]
Writing 'system_ext_a' OKAY [ 0.436s]
Sending sparse 'system_ext_a' 2/2 (90052 KB) OKAY [ 2.356s]
Writing 'system_ext_a' OKAY [ 0.166s]
extracting system_other.img (23 MB) to disk... took 0.130s
archive does not contain 'system.sig'
Resizing 'system_b' OKAY [ 0.007s]
Sending 'system_b' (24428 KB) OKAY [ 0.636s]
Writing 'system_b' OKAY [ 0.083s]
extracting vendor.img (489 MB) to disk... took 2.212s
Invalid sparse file format at header magic
archive does not contain 'vendor.sig'
Resizing 'vendor_a' OKAY [ 0.012s]
Sending sparse 'vendor_a' 1/2 (262116 KB) OKAY [ 6.895s]
Writing 'vendor_a' OKAY [ 0.414s]
Sending sparse 'vendor_a' 2/2 (237176 KB) OKAY [ 6.201s]
Writing 'vendor_a' OKAY [ 0.396s]
extracting vendor_dlkm.img (39 MB) to disk... took 0.128s
archive does not contain 'vendor_dlkm.sig'
Resizing 'vendor_dlkm_a' OKAY [ 0.010s]
Sending 'vendor_dlkm_a' (39996 KB) OKAY [ 1.028s]
Writing 'vendor_dlkm_a' OKAY [ 0.115s]
archive does not contain 'vendor_other.img'
Erasing 'userdata' OKAY [ 1.823s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Erasing 'metadata' OKAY [ 0.012s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Rebooting OKAY [ 0.001s]
Finished. Total time: 174.356s
Press any key to exit...
Click to expand...
Click to collapse
Bad Bimr said:
Updated the image on a Pixel 6a today and my eye caught this error. So I flased it again and again the same error? Is this normal? What is it? See log below.
Thanks
Click to expand...
Click to collapse
Yes, it's "normal". You can safely ignore it. I believe it has something to do with fastboot sending an image in an unexpected sparse format. Seriously, nothing to worry about.
It's funny that I flashed hundreds of times and never noticed it. Maybe I should be more attentive. LOL.
This link is a reasonable description of what a "sparse file' is: https://en.wikipedia.org/wiki/Sparse_file
The errors you highlight seem to indicate the downloaded file's contents doesn't match the file's internal description(s), also included in the download. (The so-called "meta data.")
Perhaps the download was incomplete or had an error. I'd re-fetching the material(s) and if there's a hash associated with the downloaded materials, ensure the hash matches. Sometimes files get mucked up during downloads... it happens.
I've not tried what you're doing myself and, as some are saying, perhaps it's normal, if still alarming. ;-)
I'm 99.9% sure I checked the hash file because I always do. But to be certain, I'll check it again just in case this time I didn't.
Bad Bimr said:
I'm 99.9% sure I checked the hash file because I always do. But to be certain, I'll check it again just in case this time I didn't.
Click to expand...
Click to collapse
You'll get that message every time. I do. No worries...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hi, flashing android 9 gsi roms, works fine on my device(TA-1191). But any/all A11 gsi's just don't. Ok so i flashed the a9 nokia firmware from the unlock guide, then did an OTA update and flashed magisk. Everything is fine up to this point. But flashing the following gsi's don't work:
Corvus_vS3.0-Revenant-treble_arm64_ab_vndklite-Beta-Official-0800.img
Corvus_vS4.0-Leviathan-treble_arm64_ab_vndklite-Official-0038.img
lineage-20.0-20230324-UNOFFICIAL-arm64_bvS-vndklite.img
system-roar-arm64-ab-vndklite-floss.img
And a few other unamed/system gsis...
This the method or guide being followed:
Code:
PS C:\adb\platform-tools_r31.0.3-windows> fastboot devices
HZAL1670EAJ81901791 fastboot
PS C:\adb\platform-tools_r31.0.3-windows> fastboot flash system lineage-20.0-20230324-UNOFFICIAL-arm64_bvS-vndklite.img
Invalid sparse file format at header magic
Sending sparse 'system_b' 1/17 (131028 KB) OKAY [ 5.882s]
Writing 'system_b' OKAY [ 1.966s]
Sending sparse 'system_b' 2/17 (131052 KB) OKAY [ 5.944s]
Writing 'system_b' OKAY [ 1.928s]
Sending sparse 'system_b' 3/17 (131064 KB) OKAY [ 5.973s]
Writing 'system_b' OKAY [ 2.396s]
Sending sparse 'system_b' 4/17 (131056 KB) OKAY [ 5.940s]
Writing 'system_b' OKAY [ 2.449s]
Sending sparse 'system_b' 5/17 (131052 KB) OKAY [ 5.922s]
Writing 'system_b' OKAY [ 1.948s]
Sending sparse 'system_b' 6/17 (131056 KB) OKAY [ 5.940s]
Writing 'system_b' OKAY [ 1.919s]
Sending sparse 'system_b' 7/17 (131068 KB) OKAY [ 5.947s]
Writing 'system_b' OKAY [ 1.920s]
Sending sparse 'system_b' 8/17 (131052 KB) OKAY [ 5.899s]
Writing 'system_b' OKAY [ 2.532s]
Sending sparse 'system_b' 9/17 (131068 KB) OKAY [ 5.942s]
Writing 'system_b' OKAY [ 1.920s]
Sending sparse 'system_b' 10/17 (131060 KB) OKAY [ 5.895s]
Writing 'system_b' OKAY [ 1.925s]
Sending sparse 'system_b' 11/17 (130928 KB) OKAY [ 5.920s]
Writing 'system_b' OKAY [ 1.988s]
Sending sparse 'system_b' 12/17 (130525 KB) OKAY [ 5.967s]
Writing 'system_b' OKAY [ 2.680s]
Sending sparse 'system_b' 13/17 (131032 KB) OKAY [ 5.931s]
Writing 'system_b' OKAY [ 2.488s]
Sending sparse 'system_b' 14/17 (131048 KB) OKAY [ 6.210s]
Writing 'system_b' OKAY [ 1.942s]
Sending sparse 'system_b' 15/17 (131060 KB) OKAY [ 5.928s]
Writing 'system_b' OKAY [ 1.927s]
Sending sparse 'system_b' 16/17 (131068 KB) OKAY [ 5.913s]
Writing 'system_b' OKAY [ 1.920s]
Sending sparse 'system_b' 17/17 (57706 KB) OKAY [ 2.675s]
Writing 'system_b' OKAY [ 1.900s]
Finished. Total time: 150.659s
PS C:\adb\platform-tools_r31.0.3-windows> fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta_b' (4 KB) OKAY [ 0.008s]
Writing 'vbmeta_b' OKAY [ 0.002s]
Finished. Total time: 0.032s
PS C:\adb\platform-tools_r31.0.3-windows> fastboot -w
Erasing 'userdata' OKAY [ 0.224s]
CreateProcess failed: The system cannot find the file specified. (2)
fastboot: error: Cannot generate image for userdata
PS C:\adb\platform-tools_r31.0.3-windows> fastboot reboot
Rebooting OKAY [ 0.001s]
Finished. Total time: 0.004s
PS C:\adb\platform-tools_r31.0.3-windows>
And the issue eperienced is either Bootlooping or rebooting into twrp recovery. Also formating data in twrp makes no difference. The vbmeta.img used, is from the ota updated firmware base.
I don't if i might be flashing the wrong gsi images ? If someone could correct me please.
Thanks.
Still can't seem to fix it. Help anyone ?
Ok realized that the los 20 and the above gsi's are a12/13 based. And that the gsi rom should match your base firmware android version. So I tried the following gsi's that are a11 and still no luck:
bless-v306-210502-arm64-bvZ-lite.img
caos-v316-220321-arm64-bvZ-lite.img
HavocOS-arm64-bvN-lite.img (also a11)
system-roar-arm64-ab-vndklite-vanilla.img (also a11)
Could anyone share some links of working android 11 gsi's ? Please ?