Database Develop

[Q] Cannot flash XZ system with fastboot - data too large

Hi!
I'm trying to root my XZ with new .253 firmware. I repeated the procedure which I know well from my XS (I did it there several times, always with success): dumping system.sin from ftf, extracting ext4 with sin2raw, loopmounting it, adding su and Superuser.apk, creating new img with make_ext4fs and finally flashing it with fastboot.
But now, I'm stuck here:
Code:
[email protected]:/home/patrol/sxs# FlashTool/x10flasher_lib/fastboot.linux flash system ./system.img
< waiting for device >
sending 'system' (1111575 KB)...
FAILED (remote: data too large)
finished. total time: 0.002s
It looks that the phone refuses to load such a long data - but it's just a few kilobytes longer than the original one... Of course I'm using -s option to make_ext4fs, otherwise it would be almost twice as long (I suppose that the /system is 2GB)... And forgot to say my BL is unlocked... I've tried about 4 different fastboot binaries (two of them compiled by myself, the last one coming from the latest FlashTool/Linux beta package... Any help ?
With regards,
Pavel
Today's news: I continued with experiments. I've tried to remove files from the fs to decrease the size below 1G. However, the same thing appeared, just the reported size was 998239 K. So, 1G is not any magic boundary .

Help - Stuck in Bootloop

The point in which everything took a turn for the worst was while trying to update firmware via SD update method. At which point it just stayed on android boot screen.
Recovery was broken at this point
I successfully flashed an older CWM version, but that was useless for reflashing the latest Asus firmware.
I tried flashing stock recovery again and it appeared to succeed, but now when I try to boot to recovery, it just goes back to bootloop.
I'm trying to flash the US version now via fastboot I get bootloop again and I'm getting weird errors every time I try regarding filesize. (See below)
I tried flashing CROMbi as well and it went through the install process successfully, but that resulted in bootloop as well.
Tried flashing Asus US firmware again without success,
Kind of pissed that this all started when following the instructions on the Asus site to upgrade to their latest firmware via SD card.
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot -i 0x0B05 flash system
asusus.zip
target reported max download size of 643825664 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 425021387 is not a multiple of t
he block size 4096
erasing 'system'...
OKAY [ 1.457s]
sending sparse 'system' (628732 KB)...
error: write_sparse_skip_chunk: don't care size 425021387 is not a multiple of t
he block size 4096
error: write_sparse_skip_chunk: don't care size 425021387 is not a multiple of t
he block size 4096
OKAY [ 86.837s]
writing 'system'...
OKAY [ 17.080s]
sending sparse 'system' (415060 KB)...
OKAY [ 57.305s]
writing 'system'...
OKAY [ 11.353s]
finished. total time: 174.042s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot -i 0x0B05 reboot
rebooting...
finished. total time: 0.021s
C:\Program Files (x86)\Minimal ADB and Fastboot>

Last time something like this happened, I had to wipe everything and reflash. so I did the following.
fastboot -i 0x0b05 erase boot
fastboot -i 0x0b05 erase cache
fastboot -i 0x0b05 erase userdata
fastboot -i 0x0b05 erase recovery
fastboot -i 0x0b05 erase staging
fastboot -i 0x0b05 erase system
and now I get a bootloader error on startup
I was able to successfully flash CWM 6037 again. I tried newer ones, but 6037 is the only one that will work.
Stock firmware from custom recovery fails every time. "Installing update... Installation aborted."
Crombi installer goes through without any problems. but just never boots once completed.
I tried installing the latest Cyanogen Nightly and got the following error "This package is for tF701T devices; this is a K00C."
But the K00C is a TF701T
After installing CROMbi again, I'm no longer getting the bootloader error in red letters, but I am still bootlooping.
When crombi installer completes I do get one error at the very end. "set_metadata_recursive:some changes failed".
I looked at the log and it says Cant partition non-vfat datamedia.
Does bootloop after apparently successful fstboot flash have anythignt o do with why in the FAW's ASUS recommends ignoring the software update for 4.3? Afterall this is what put me in this situation.

The SD update is designed to work with the stock recovery. What made you think it would work with CWM?
The only successful recovery from a similar situation I remember is the following (and I'm quoting from memory here - it's too late here for me to find the thread, but it is somewhere here in this forum - search for it.
Download the stock recovery to your fastboot folder from here: http://droidbasement.com/db-blog/?p=3210
Also download the 10.26.1.18 firmware, unzip it once, put it on a microSD and insert into tablet.
Enter fastboot mode
Issue:
Code:
fastboot [b]boot[/b] recovery.img
Note: You do not flash the recovery, you boot it!
The recovery should recognize the firmware on the microSD and start to flash it.
If that is successful, you would have stock recovery and firmware again.
Then download the latest firmware, unzip it, put into microSD or internal and the stock recovery should flash it.
Good luck!
Sent from my K00C using Tapatalk

berndblb said:
The SD update is designed to work with the stock recovery. What made you think it would work with CWM?
The only successful recovery from a similar situation I remember is the following (and I'm quoting from memory here - it's too late here for me to find the thread, but it is somewhere here in this forum - search for it.
Download the stock recovery to your fastboot folder from here: http://droidbasement.com/db-blog/?p=3210
Also download the 10.26.1.18 firmware, unzip it once, put it on a microSD and insert into tablet.
Enter fastboot mode
Issue:
Code:
fastboot [b]boot[/b] recovery.img
Note: You do not flash the recovery, you boot it!
The recovery should recognize the firmware on the microSD and start to flash it.
If that is successful, you would have stock recovery and firmware again.
Then download the latest firmware, unzip it, put into microSD or internal and the stock recovery should flash it.
Good luck!
Sent from my K00C using Tapatalk
Click to expand...
Click to collapse
The attempted SD update was done with custom recovery as I couldn't get stock recovery to work after the initial SD update with stock recovery.
Thanks for the info. I'll update.

gorilla p said:
Last time something like this happened, I had to wipe everything and reflash. so I did the following.
fastboot -i 0x0b05 erase boot
fastboot -i 0x0b05 erase cache
fastboot -i 0x0b05 erase userdata
fastboot -i 0x0b05 erase recovery
fastboot -i 0x0b05 erase staging
fastboot -i 0x0b05 erase system
and now I get a bootloader error on startup
I was able to successfully flash CWM 6037 again. I tried newer ones, but 6037 is the only one that will work.
Stock firmware from custom recovery fails every time. "Installing update... Installation aborted."
Crombi installer goes through without any problems. but just never boots once completed.
I tried installing the latest Cyanogen Nightly and got the following error "This package is for tF701T devices; this is a K00C."
But the K00C is a TF701T
After installing CROMbi again, I'm no longer getting the bootloader error in red letters, but I am still bootlooping.
When crombi installer completes I do get one error at the very end. "set_metadata_recursive:some changes failed".
I looked at the log and it says Cant partition non-vfat datamedia.
Does bootloop after apparently successful fstboot flash have anythignt o do with why in the FAW's ASUS recommends ignoring the software update for 4.3? Afterall this is what put me in this situation.
Click to expand...
Click to collapse
That error message means that your internal sdcard is no t available to format. Erasing all partitions is a dangerous thing to do.
The only way you will get back to normal is to try and flash the stock asus rom now as that will recreate everything. I recommend you start with the 4.2.2 one - need to flash it over fastboot - I can't see anything else working as you have erased it all.....
Also you used 0x0b05 which is the code for the last generation of transformers..... You don't need it for the TF701 but not sure if that has caused additional grief now. Probably not but you never know .....

Yeah IO'm getting the same issue that I was having before. I tried both the 4.3 and 4.2 boot.img and the recommended recovery.img file. Each time I ran
fasboot boot recovery.img
downloading 'boot.img'...
OKAY [ 1.121s]
booting...
OKAY [ 0.032s]
finished. total time: 1.157s
booting from downloaded boot.img (on tablet)
Then it goes to boot into the image and...bootloop.
C:\Program Files (x86)\Minimal ADB and Fastboot\asus>fastboot flash system asus4
22.zip
target reported max download size of 643825664 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 346827884 is not a multiple of t
he block size 4096
erasing 'system'...
OKAY [ 1.515s]
sending sparse 'system' (628732 KB)...
error: write_sparse_skip_chunk: don't care size 346827884 is not a multiple of t
he block size 4096
error: write_sparse_skip_chunk: don't care size 346827884 is not a multiple of t
he block size 4096
OKAY [ 86.861s]
writing 'system'...
OKAY [ 17.098s]
sending sparse 'system' (338700 KB)...
OKAY [ 46.823s]
writing 'system'...
OKAY [ 9.280s]
finished. total time: 161.586s
Bootloop...
Could the inability to flash or boot from stock recovery have anything to do with the CWM recovery protection?

Well after those attempts it's totally shot.
Now I can't even get to fastboot. Every reboot results in "Unrecoverable bootloader error..."
Files RMA. Returned.
Moral of story. Don't do anything on a Tegra device without previous documentation that doesn't have NVFlash available.

Honor 9 Lite "my test with other devices developer-ROMs"

@VigneshS007
test system-arm64-ab.img
boot to custom-recovery
wipe cache (formatting cache .. down)
wipe data/factory reset / confirm yes / confirm yes - format 0..100%
vol-up and power and usb-wire in phone and pc : boot to bootloader
fastboot devices (phone is online!)
fastboot flash system system-arm64-ab.img
target reported max download size of 471859200 bytes
sending sparse 'system' (460796 KB)...
FAILED (status read failed (Protocol error))
finished. total time: 1.547s
usb-wire out phone / return in phone
fastboot devices (phone is online!)
fastboot flash system system-arm64-ab.img
target reported max download size of 471859200 bytes
sending sparse 'system' (460796 KB)...
OKAY [ 14.497s]
writing 'system'...
OKAY [ 3.356s]
sending sparse 'system' (421628 KB)...
OKAY [ 13.025s]
writing 'system'...
OKAY [ 2.928s]
sending sparse 'system' (388444 KB)...
OKAY [ 11.666s]
writing 'system'...
OKAY [ 2.704s]
finished. total time: 48.177s
now is in phone custom-recovery, data fresh formated, system-arm64-ab.img
usb-wire is in phone
fastboot reboot
phone boot... / black screen / <- 3x / Huawei eRecovery "Factory data reset(recommended)" yes(do it)
low-level format 0..5% / reset failed! / reboot system now
phone boot 2x and go to Huawei eRecovery (this flash dont work / shutdown)
vol-down press and hold, usb-wire put in phone, phone boot to bootloader
fastboot devices (phone is online!)
fastboot flash system system-arm64-ab.img
target reported max download size of 471859200 bytes
sending sparse 'system' (460796 KB)...
OKAY [ 14.281s]
writing 'system'...
OKAY [ 3.511s]
sending sparse 'system' (421628 KB)...
FAILED (status read failed (Protocol error))
finished. total time: 21.386s
usb-wire out phone
usb-wire in phone
fastboot devices (phone is online!)
fastboot flash system system-arm64-ab.img
target reported max download size of 471859200 bytes
sending sparse 'system' (460796 KB)...
OKAY [ 14.359s]
writing 'system'...
OKAY [ 3.235s]
sending sparse 'system' (421628 KB)...
OKAY [ 12.947s]
writing 'system'...
OKAY [ 2.931s]
sending sparse 'system' (388444 KB)...
OKAY [ 11.664s]
writing 'system'...
OKAY [ 2.710s]
finished. total time: 47.846s
fastboot reboot and fast usb-wire out phone
You device is booting now... /black screen <- 2x /Huawei eRecovery /THIS way not work!!!
vol-down press and hold, usb-wire put in phone, phone boot to bootloader
fastboot devices (phone is online!)
fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' (458906 KB)...
FAILED (status read failed (Protocol error))
finished. total time: 14.487s
usb-wire out phone
vol-up press and hold and power /boot to eRecovery/ factory reset
phone off
vol-down press and hold, usb-wire put in phone, phone boot to bootloader
fastboot devices (phone is online!)
fastboot flash system system.img
phone off
power
phone boot to factoryOS !!! this is the best: my phone work, no bootloop or other error
i think, the problem is "i am" or the instructions or "what else"
i think, if i do factory-reset the phone low-level format "data" and set inside instructions "test by next boot what system.img is installed" or other test
this test i now 5x do and the way is by all the same.
anyone info i missing to get out of this loop
i hope very powerful: anyone developer write twrp and system(LOS or RR) for this phone !
at the moment i could nail it to the wall / i am very frustrated / a little bit
excuse me for long writing text, i hope the mistake is easier to find

Flash this https://forum.xda-developers.com/pr...opment/resurrection-remix-phh-treble-t3767688 ARM 64 A only device @JamesBott

now, lets go, next test :good:
download run... finish
test system-arm64-aonly.img
fastboot devices (phone is online!)
fastboot flash system system-arm64-aonly.img
fastboot reboot
the rest is "the same procedure as test bevor"
this phone (my H9L) not boot in other system.img
by now in nothing else
the problem must inside my phone
or other question : have anyone other system.img in H9L and this work ? H9L with LLD-L31 ? not from india or ..., from EU (European Union)
what is different in my phone than other users ? i don't know it
now is custemOS inside again. different to last rom-install: SU is now outside! only different what i see

For everyone who is interested: I have build my first treble build based on pure AOSP 8.0... As my 6X didn't received EMUI 8.0 already I would be glad if some Honor 9 Lite or P Smart user could try to install and run my build on his device as it is based on P Smart blobs: Install it like a normal treble build. Extract the zip (it isnt flashable zip !), unlock BL, flash system.img via fastboot - boot to stock recovery and perform a factory reset - reboot... if booted up report back and provide some screenshots! Here is DL: https://www.androidfilehost.com/?fid=962187416754471220

JamesBott said:
now, lets go, next test :good:
download run... finish
test system-arm64-aonly.img
fastboot devices (phone is online!)
fastboot flash system system-arm64-aonly.img
fastboot reboot
the rest is "the same procedure as test bevor"
this phone (my H9L) not boot in other system.img
by now in nothing else
the problem must inside my phone
or other question : have anyone other system.img in H9L and this work ? H9L with LLD-L31 ? not from india or ..., from EU (European Union)
what is different in my phone than other users ? i don't know it
now is custemOS inside again. different to last rom-install: SU is now outside! only different what i see
Click to expand...
Click to collapse
Firstly... Honor 9 lite dont have a/b partition so you have to take the a-Partition images...
Secondly... V9 of the treble image would work (its on android 8.0)...

Hi @felix-development,
that what i reed - sounds very interesting. my next test is your download.
question : have you "twrp full function" ?
i mean twrp backup/restore "system, data..." ?
my twrp do backup/restore system "yes" data "no" (de- en-cryption ?)

JamesBott said:
Hi @felix-development,
that what i reed - sounds very interesting. my next test is your download.
question : have you "twrp full function" ?
i mean twrp backup/restore "system, data..." ?
my twrp do backup/restore system "yes" data "no" (de- en-cryption ?)
Click to expand...
Click to collapse
you should be on normal emui 8 with just bl unlocked... flash system.img via fastboot - and after that do a factory reset in erecovery (if didn't do by unlocking bl already)
Gesendet von meinem BLN-L21 mit Tapatalk
---------- Post added at 09:35 AM ---------- Previous post was at 09:33 AM ----------
JamesBott said:
Hi @felix-development,
that what i reed - sounds very interesting. my next test is your download.
question : have you "twrp full function" ?
i mean twrp backup/restore "system, data..." ?
my twrp do backup/restore system "yes" data "no" (de- en-cryption ?)
Click to expand...
Click to collapse
by the way you are free to pm me as i saw we speak the same lanuage
Gesendet von meinem BLN-L21 mit Tapatalk

Hi @felix-development,
ALL Test's ending in eRecovery, "Download latest version and recovery / Reboot / Shutdown"
That's no problem, i flash stock and all good! Phone work with stock It's only work.
Procedure:
flash other system; reboot; (phone boot / black screen) 3x / eRecovery "reset data" .... low-level-format 0..100% / reboot / (phone boot / black screen) 3x / eRecovery, "Download latest...
i think, the problem sit on the frontside from phone
any idea, what i doing false ?
or is in this moment fact: no other rom work on H9L ?
last step: flash system system.img (stock) phone boot "normal" and work !
My daily driver is my old elephon p8 mini.
Honor 9 Lite sleep and wait for next test

JamesBott said:
Hi @felix-development,
ALL Test's ending in eRecovery, "Download latest version and recovery / Reboot / Shutdown"
That's no problem, i flash stock and all good! Phone work with stock It's only work.
Procedure:
flash other system; reboot; (phone boot / black screen) 3x / eRecovery "reset data" .... low-level-format 0..100% / reboot / (phone boot / black screen) 3x / eRecovery, "Download latest...
i think, the problem sit on the frontside from phone
any idea, what i doing false ?
or is in this moment fact: no other rom work on H9L ?
last step: flash system system.img (stock) phone boot "normal" and work !
My daily driver is my old elephon p8 mini.
Honor 9 Lite sleep and wait for next test
Click to expand...
Click to collapse
A logcat could help to fix or to see wheres the problem...

@Darkest-Dark
logcat is a good word: how & who i find on end test (stand in eRecovery) the logcat ?
or if i reflash stock: if logcat from last test available ( how & who) ?
i can all do what hav to do with system and recovery. that's no risk. reflash system and/or recovery and stock work!

@Darkest-Dark
logcat is a good word: how & who i find on end test (stand in eRecovery) the logcat ?
or if i reflash stock: if logcat from last test available ( how & who) ?
i can all do what hav to do with system and recovery. that's no risk. reflash system and/or recovery and stock work!

JamesBott said:
@Darkest-Dark
logcat is a good word: how & who i find on end test (stand in eRecovery) the logcat ?
or if i reflash stock: if logcat from last test available ( how & who) ?
i can all do what hav to do with system and recovery. that's no risk. reflash system and/or recovery and stock work!
Click to expand...
Click to collapse
Look here...
https://forum.xda-developers.com/showthread.php?t=2303834

i found
Now type this in the terminal
Code:
adb logcat -v long > logcat.txt
or
Code:
adb logcat > logcat.txt
you shall have a log file called name of logcat.txt inside your ADB folder.
i test next day !
if this work we have backup from stock without twrp, simple & good
i write my experiences after test !

Hi, TWRP now available. Look https://forum.xda-developers.com/9-lite/development/honor-9-lite-twrp-3-2-1-0-available-t3771358
From now Backup/Restore NO problem

principle question & understand question
all test's NOT work.
last test made with twrp : twrp/install system.img, twrp flash this image with no errors.
now reboot to system : twrp write "no OS is installed .."
i mean, the problem is the differences from Android 7 and 8
i mean : in Android 8 is boot-sequence other as in Android 7
why : i have updated one+ 3T and Sony Z 2, inside LOS 14.1, updated to LOS 15.1, this 2 phones work no with OREO.
i mean, this updates for Android 7 core and i need now LOS 15.1 for installing on Android 8 core.
my knowledge : i am wait on LOS 15.1, written for OREO-Core.
the first version H9L came with factory-Android 7, all LOS 14.1 (RR ...) work on this
my phone is from February 2018 and have factory-OREO on board
with OREO begin a new era
essence : i am to fast with this phone and OREO wait on developer's
but - the factory-OREO work good enough for me (with root) - only : i am LOS-fan since many year :angel:

i am test https://forum.xda-developers.com/9-lite/development/kangvip-rom-emui-8-0-t3775904
for first oreo-developer-rom work good. it is stock-rom with modified menu ( menu / advanced settings).

Bricked my phone

Hey,
I think I might have bricked my phone.
Whenever I want to instal my recovery fiile it keeps saying "Cannot mount /cust"& /vendor
I've tried almost anything I can think of. I've tried the dload method but it keeps giving me error about the firmware not being supported or so.
I've manually tried to flash the cust.img through adb :
PS C:\adb> fastboot flash recovery cust.img
target reported max download size of 471859200 bytes
sending 'recovery' (361698 KB)...
OKAY [ 12.789s]
writing 'recovery'...
FAILED (remote: partition error)
finished. total time: 12.815s
PS C:\adb>
I wiped everything and tried to instal a stock B381 firmware but no luck also.
Any help would be appreciated

Hola compañero, prueba esto.
https://forum.xda-developers.com/showpost.php?p=66570915&postcount=11
But where it says
mmcblk0p23
Change it to
mmcblk0p44
Besides. instead of using the sdcard partition, which is the internal memory, I advise you to do it from the external memory. So don't forget to trade one for the other on the command line.
My advice is that if you have TWRP installed you do it from the terminal of that recovery.
With VENDOR, the command line I used is the following
dd if=/external_sd/VENDOR.img of=/Vendor
I used the CUST and the VENDOR extracted from the B103 version, so if you don't have it I advise you to download it, and extract what you need from that version with Huawei Extractor, if everything works out well, I recommend that the first thing you do is, reinstall the official recoveries, and with the method of the 3 buttons, install that same version (Vie-l09B103C432), that in case your P9 is an L09 and you are in Rom international, if it is another version, you have to look for the files suitable for your terminal.
Good luck.
Translated with www.DeepL.com/Translator

[ROM][UNOFFICIAL] LineageOS 17.1 for Xperia 10 II [OTA][SODP]

Lineage 17.1 for the Sony Xperia 10 II
Please note this is currently for the dual-sim model ONLY. When you need a single-sim variant leave a comment, so we can work an that...​
Code:
/*
* Disclaimer - your warranty may be void.
*
* I'm not responsible for bricked devices, dead OTGs or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Features
OTA updates - always delayed for 1 day (to prevent broken rollouts); when you want it immediately, checkout my GitLab pipelines
Increased volume steps to 25
Over-provisioned system image (580MiB), to allow install of OpenGApps and other stuff
Open Source (it is based on SODP, you can view all my patches and ci scripts here or here)
Package signature spoofing (needed by MicroG)
What does not work?
Stock camera app with wide and zoom cameras, you may use Open Camera to circumvent that.
Notification LED blinking - kernel driver bug (see here)
LiveDisplay
You tell me...
Download
There you have multiple options:
To get the complete package (both including the ota and imgparts; only needed for the initial setup) visit...
AndroidFileHost
GitLab (make sure to download the artifacts from the master branch)
To get ONLY the OTA package to update your system later on, visit (or open up the LineageOS Updater) ota.simonmicro.de - please note that only the last recent 14 days are accessible there.
Changelog
2021-02-28
Fixed wifi hotspot.
2020-12-18
Fixed cameras.
2020-11-27
Fixed ADB security.
2020-11-25
Added SELinux support.
2020-11-20
Added OpenGApps support.
2020-11-17
Initial release.
How to install your system
The following guide assumes, you have setup adb and fastboot already (make sure to always use the latest version of the toolkit, otherwise you'll may get problems during flashing) - for that take a look into the internet. Also you should already downloaded the complete package from above!
Unlock the bootloader - a "how to" is here...
Download the oem binaries from here, make sure to use exactly that version!
Boot into the bootloader (hold "Volume up + Insert the USB cable" until led lights blue) and then update the oem partition:
Code:
fastboot flash oem_a [EXTRACTED_OEM_IMAGE_FILE]
fastboot flash oem_b [EXTRACTED_OEM_IMAGE_FILE]
Flash now the Lineage recovery partition as well as the dtbo partition (they are inside the img folder of the complete package):
Code:
fastboot flash recovery [EXTRACTED_RECOVERY_IMAGE_FILE]
fastboot flash dtbo [EXTRACTED_DTBO_IMAGE_FILE]
Disable the verity checks for now, as your new recovery violates the Sony verity profiles of the Stock ROM:
Code:
fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
fastboot flash --disable-verity --disable-verification vbmeta_system vbmeta_system.img
Okay, you are now ready to boot the first time into the Lineage recovery, unplug the phone NOW!
To boot into recovery: Hold "Volume down + Power" until it vibrates...
You should now be booted into the recovery. We now clean any old data from Sonys Stock ROM - this is just to make sure you have a really clean install: Choose the "Factory reset" option.
The phone is now clean and ready to accept the new system. You now can either install just the OTA package and be done or flash every .img from the full package manually - the coice is yours. When you plan to flash the images manually, make sure to include boot, system, product, vendor, vbmeta_system, as these are normally part of the OTA update (I extracted the payload.bin to verify this!). For the latter approach you may orient yourself on my flashall.sh. I'll choose the simpler OTA-sideload approach for now.
Select "Apply update -> Apply from ADB" (now make sure the adb server runs as root - may use adb kill-server && sudo adb start-server to fix that) and execute (the OTA zip is inside the ota subdir):
Code:
adb sideload [OTA_SYSTEM_UPDATE_ZIP_FILENAME]
Something went wrong - help!
(Step 7-8) When you now see a device corrupt error
Don't panic!
You messed up the verity disable step from before - try again.
Try to switch the current boot slot (get current fastboot getvar current-slot and set new fastboot --set-active=, you can choose between a and b) and retry disableing verity disable again!
When your device fails to boot too many times (and crashes) the current slot could also get marked as corrupt. To reset that counter you'll need to reflash the boot partition - to see what is going on, try fastboot getvar all and look out for something like a unbootable flag.
(Step 9) When you get Operation not permitted during flashing
This is commonly caused by relocking and then reunlocking the bootloader (yay - buggy firmware). You'll need to relock, restore (and boot) the device with Flashtool using Sonys original ROM and start from fresh.
(Step 10) When you get the kDownloadPayloadPubKeyVerificationError error
Well, that's caused by using an other recovery than the provided one, as I use my own private keys to sign the build the recovery must also know them. Using an other recovery than the one from
the img folder of the complete package will most likely not include them (and when they do - I am in big trouble), and therefore fail. But you are in luck: It seems that the recovery writes
the data to the currently inactive slot and then fails. You could simply switch the system slot like described above!
Want to install Magisk?
Install the Magisk zip like the OTA system update by using adb sideload [MAGISK_FILE_NAME].
Want to install OpenGApps?
Make sure to use the pico-variant, as the system partition is even with over-provisioning really small (as the installer extracts some more stuff on the first boot) - then install the OpenGApps zip like the OTA system update by using adb sideload [OPENGAPPS_FILE_NAME].
Credits
As much I would like, I can't do everything by myself. A huge thank you to...
@MartinX3 for the used local_manifests and his device tree from his LineageOS organization
...the team behind @sonyxperiadev, for their great work (and their kernel sources)!
XDA:DevDB Information
LineageOS 17.1 for pdx201, ROM for the Sony Xperia 10 II
Contributors
Simonmicro, MartinX3
Source Code: https://gitlab.simonmicro.de/android/lineage/lineage-pdx201
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: Sony OEM Package
Based On: AOSP
Version Information
Status: Beta

Hey,
as you guys may have already noted, I have stopped the active development phase for this LOS port a while ago. This was caused by me just not having enough time to do everything and additionally maintain a LOS port.
Today I'll upload the last maintenance build to the OTA server and mirrors. Of course I somehow included a little bug, which causes the system to complain about "an internal problem", which seem to be caused by some interaction with the OpenGApps package installer. Now, it is a feature. I'll may post one more update, if I figure this one out.
Nevertheless, I'll shut down the OTA service at 2022-06-01 (see https://status.simonmicro.de) and will then archive all project data. It was a great time to learn many (new/nasty) things about Android and how everything works. I have to say "thank you" to everyone, who supported me and was on board with this project.
See you next time,
simonmicro
-> https://forum.xda-developers.com/t/...r-xperia-10-ii-ota-sodp.4191601/post-86352693 <-

Reserved

First

At last The guide, source code looks great! Will install, check it next

hmm, i flashed everything according to the instructions, but the system still looks the same as Sjll's ROM and there is no updater in settings>system. anyone else getting this?
EDIT: nevermind, all is well, i was on the wrong slot.. : / wish we wouldn't have to deal with this, TWRP+lineage+one slot was perfect. this is not about the ROM though, it's awesome.

bamdadkhan said:
hmm, i flashed everything according to the instructions, but the system still looks the same as Sjll's ROM and there is no updater in settings>system. anyone else getting this?
EDIT: nevermind, all is well, i was on the wrong slot.. : / wish we wouldn't have to deal with this, TWRP+lineage+one slot was perfect. this is not about the ROM though, it's awesome.
Click to expand...
Click to collapse
- you made my day. Now I know which ROM you used before
No serious: Did you follow the guide step-by-step or did you altered it in some way (maybe forgot to reboot after switching slots) - as it should normally flash both slots (when using ota), even when not you should be at least on the right slot after flashing?!

Simonmicro said:
- you made my day. Now I know which ROM you used before
No serious: Did you follow the guide step-by-step or did you altered it in some way (maybe forgot to reboot after switching slots) - as it should normally flash both slots (when using ota), even when not you should be at least on the right slot after flashing?!
Click to expand...
Click to collapse
lol it's easy to know when the ROM in question is the only available aside from yours xd
seriously: i followed all the steps to the letter. flashed the SW binaries on both oem_a and oem_b. really everything.
i have a theory though. i originally flashed your ROM when 'side b' had previously been set active. if this persists across reboots - i really don't know, this whole 'dual ROM' concept is new to me - then there's your answer: the lineage install script probably has a command to use 'side a' for flashing. is completed successfully, but then i went ahead and booted the 'side b', which still had Sjll's ROM on it.

bamdadkhan said:
lol it's easy to know when the ROM in question is the only available aside from yours xd
seriously: i followed all the steps to the letter. flashed the SW binaries on both oem_a and oem_b. really everything.
i have a theory though. i originally flashed your ROM when 'side b' had previously been set active. if this persists across reboots - i really don't know, this whole 'dual ROM' concept is new to me - then there's your answer: the lineage install script probably has a command to use 'side a' for flashing. is completed successfully, but then i went ahead and booted the 'side b', which still had Sjll's ROM on it.
Click to expand...
Click to collapse
Well, I also tested my guide to the letter - and there i saw on my device screen that the ota flashed on both partitions. Did you also used my recovery? When you did: Lets see if others also have that problem... :angel:

Simonmicro said:
Well, I also tested my guide to the letter - and there i saw on my device screen that the ota flashed on both partitions. Did you also used my recovery? When you did: Lets see if others also have that problem... :angel:
Click to expand...
Click to collapse
Great job, thank you. Can I install NikGapp? Or does it also cause bootlaps?

Thapsus-cz said:
Great job, thank you. Can I install NikGapp? Or does it also cause bootlaps?
Click to expand...
Click to collapse
On their website:
Code:
OpenGapps Team (for base package and providing Open Gapps)
Therefore is a really good chance that the installer has the same problems like OpenGApps - but I can't say that for sure, I guess you'll need to try it out (when is does bootloop / never starts, please send me a adb logcat -b all for further diagnostics).

Done till the step 9.
Tried the second way first (flashing images). Please see the log for this below.. Then tried OTA way. OTA way did with 0 exit status (it sent files) but when I boot device it writes "Your device is corrupt. It can't be trusted and will not boot. Your device will be powered off in 5 seconds". How to fix?
Also when I load into recovery it writes this:
E: Failed to bind mount /mnt/staging/mulated/media/0 to /storage/emulated: NO such file or directory.
E: emulated failed to bind mount /mnt/stagingemulated/media/0 on /storage/meulated: No such file or directory.
Click to expand...
Click to collapse
See full log for flashing images:
sudo fastboot flash boot boot.img
sudo fastboot flash system system.img
sudo fastboot flash product product.img
sudo fastboot flash vendor vendor.img
sudo fastboot flash vbmeta_system vbmeta_system.img
[sudo] пароль для :
Sending 'boot_b' (65536 KB) OKAY [ 2.441s]
Writing 'boot_b' OKAY [ 0.358s]
Finished. Total time: 2.812s
Sending sparse 'system' 1/2 (785636 KB) OKAY [ 29.722s]
Writing 'system' FAILED (remote: 'No such partition.')
fastboot: error: Command failed
Sending 'product' (432072 KB) OKAY [ 16.440s]
Writing 'product' FAILED (remote: 'No such partition.')
fastboot: error: Command failed
Sending 'vendor' (48084 KB) OKAY [ 1.725s]
Writing 'vendor' FAILED (remote: 'No such partition.')
fastboot: error: Command failed
Sending 'vbmeta_system' (4 KB) OKAY [ 0.005s]
Writing 'vbmeta_system' OKAY [ 0.003s]
Finished. Total time: 0.016s
❯ sudo fastboot flash boot boot.img
sudo fastboot flash system system.img
sudo fastboot flash product product.img
sudo fastboot flash vendor vendor.img
sudo fastboot flash vbmeta_system vbmeta_system.img
❯ sudo fastboot flash boot boot.img
sudo fastboot flash dtbo dtbo.img
sudo fastboot flash product product.img
sudo fastboot flash recovery recovery.img
sudo fastboot flash super_empty super_empty.img
sudo fastboot flash system system.img
sudo fastboot flash vbmeta vbmeta.img
sudo fastboot flash vbmeta_system vbmeta_system.img
sudo fastboot flash vendor vendor.img
Sending 'boot_b' (65536 KB) OKAY [ 2.438s]
Writing 'boot_b' OKAY [ 0.378s]
Finished. Total time: 2.831s
Sending 'dtbo' (8192 KB) OKAY [ 0.302s]
Writing 'dtbo' OKAY [ 0.046s]
Finished. Total time: 0.357s
Sending 'product' (432072 KB) OKAY [ 16.212s]
Writing 'product' FAILED (remote: 'No such partition.')
fastboot: error: Command failed
Sending 'recovery' (98304 KB) OKAY [ 3.699s]
Writing 'recovery' OKAY [ 0.557s]
Finished. Total time: 4.265s
Sending 'super_empty' (4 KB) OKAY [ 0.011s]
Writing 'super_empty' FAILED (remote: 'No such partition.')
fastboot: error: Command failed
Sending sparse 'system' 1/2 (785636 KB) OKAY [ 29.755s]
Writing 'system' FAILED (remote: 'No such partition.')
fastboot: error: Command failed
Sending 'vbmeta' (4 KB) OKAY [ 0.009s]
Writing 'vbmeta' OKAY [ 0.003s]
Finished. Total time: 0.021s
Sending 'vbmeta_system' (4 KB) OKAY [ 0.003s]
Writing 'vbmeta_system' OKAY [ 0.004s]
Finished. Total time: 0.014s
Sending 'vendor' (48084 KB) OKAY [ 1.770s]
Writing 'vendor' FAILED (remote: 'No such partition.')
fastboot: error: Command failed
Click to expand...
Click to collapse

xdauserart said:
Done till the step 9.
Tried the second way first (flashing images). Please see the log for this below.. Then tried OTA way. OTA way did with 0 exit status (it sent files) but when I boot device it writes "Your device is corrupt. It can't be trusted and will not boot. Your device will be powered off in 5 seconds". How to fix?
Also when I load into recovery it writes this:
See full log for flashing images:
Click to expand...
Click to collapse
I had the same problem yesterday with the same results. I struggled with it until morning. Eventually I downloaded the latest version of adb, flashed the stock rom again and started over. It was done in twenty minutes. Try the latest version of adb (I guess version 35 for Windows)

xdauserart said:
Done till the step 9.
Click to expand...
Click to collapse
...
Code:
Sending sparse 'system' 1/2 (785636 KB) OKAY [ 29.722s]
Writing 'system' FAILED (remote: 'No such partition.')
fastboot: error: Command failed
This indicates you tried to use the bootloader (which also has fastboot support) to flash the images. I made sure to write the guide the way that it states you should use the fastbootd service of the recovery. I have the dumb feeling that many more will go your way and fail. Damn it.
Code:
E: Failed to bind mount /mnt/staging/mulated/media/0 to /storage/emulated: NO such file or directory.
E: emulated failed to bind mount /mnt/stagingemulated/media/0 on /storage/meulated: No such file or directory.
Is fine, as you just erased all data - this also kills the partion so it cant be mounted anymore (that's the errors). This is indeed intentional as the system is now forced to really start fresh!
xdauserart said:
Your device is corrupt. It can't be trusted and will not boot. Your device will be powered off in 5 seconds"
Click to expand...
Click to collapse
Did you tried the help of my guide? When you failed that and your device rebooted too many times (or it just could not boot and crashed too many times) you'll need to reflash the boot partition to reset the counter (and therefore the failure message).

Two PR to fix back triple cam. But front cam is still broken.
https://github.com/sonyxperiadev/device-sony-seine/pull/29
https://github.com/sonyxperiadev/device-sony-pdx201/pull/15
--------------EDIT-----------------
Switch to CAF powerhal, better performance we have.
https://github.com/sjllls/device-sony-common/commit/de3b2bbbc33130891263d9e81ea2178a0f6783c4
https://github.com/sjllls/device-sony-sepolicy/commit/72059258eb0ff2c854996a05a5a23a8b73b55459
--------------EDIT-----------------
Renmember to let users flash with latest platform-tools, or they could not boot because of logical partition is not resized.
https://developer.android.com/studio/releases/platform-tools

Simonmicro said:
On their website:
Code:
OpenGapps Team (for base package and providing Open Gapps)
Therefore is a really good chance that the installer has the same problems like OpenGApps - but I can't say that for sure, I guess you'll need to try it out (when is does bootloop / never starts, please send me a adb logcat -b all for further diagnostics).
Click to expand...
Click to collapse
I can confirm that Opengapps pico can now be installed without a bootloop. I'm at work and I don't have adb. I installed them directly as an update from the sd card using recovery. Everything works fine.

Can we get OpenGapps Nano support?
I know that OpenGapps pico are supported, but most people use the nano package as it contains some functions that aren't possible to obtain in any other way
so is that possible?

KriiXOne said:
I know that OpenGapps pico are supported, but most people use the nano package as it contains some functions that aren't possible to obtain in any other way
so is that possible?
Click to expand...
Click to collapse
As I already drastically over-provisioned the system partition, I guess it could be possible that the nano package already works: In that case try it for yourself! When it goes wrong you can just switch over to your slot used before flashing the bad OpenGApps zip. Please PN me about your result, so I could extend the guide!

Simonmicro said:
As I already drastically over-provisioned the system partition, I guess it could be possible that the nano package already works: In that case try it for yourself! When it goes wrong you can just switch over to your slot used before flashing the bad OpenGApps zip. Please PN me about your result, so I could extend the guide!
Click to expand...
Click to collapse
I'll try tomorrow after the math test that i'm studying for today, and will let ya know ^^'

Simonmicro said:
...
Did you tried the help of my guide? When you failed that and your device rebooted too many times (or it just could not boot and crashed too many times) you'll need to reflash the boot partition to reset the counter (and therefore the failure message).
Click to expand...
Click to collapse
Fixed it Just repeated the steps from the first one and used OTA on step 9. Thanks!