Too small "main" partition prevents resizing during flashing about android_device_unihertz_atom_lxl

[ADeadTrousers]

That's one thing I feared/expected would happend.
The "super.img" has internally a "main partition" which is segmentd into "system", "product" and "vendor".
I just raised the minimum size for "system" to support bigger gapps. Now, if "system", "product" and "vendor" exceed the size of "main" this error occours.
With the first stock ROM release I never had any problems raising and shrinking the size but with one of the two updates unihertz release since then they seemed to have downsized "main". Since one stock ROM reflash I wasn't able to flash my LOS anymore. So I needed to build a new super.img "externally" and flash that directly:
https://github.com/ADeadTrousers/android_device_Unihertz_Atom_LXL/blob/master/docs/HOW-TO-FLASH-SUPER.md
For now you would need to that manually.
Maybe in the future I'll provide a super.img which only conatains stock "vendor" and empty (to reduce size) "system" and "product".

[ADeadTrousers]

For the "current" sizes see https://github.com/ADeadTrousers/android_device_Unihertz_Atom_LXL/blob/master/BoardConfigCommon.mk

-->
BOARD_SYSTEMIMAGE_PARTITION_SIZE := 3670016000
BOARD_PRODUCTIMAGE_PARTITION_SIZE := 681574400
BOARD_MAIN_SIZE := 4829741056
BOARD_SUPER_PARTITION_SIZE := 4831838208

Vendor size you need to get like I described in the how-to.

[SepticFuddy]

While trying to initialize the LOS repo using your build instructions, I get this error:

File "~/android/lineage/.repo/repo/main.py", line 79
    file=sys.stderr)
        ^
SyntaxError: invalid syntax

Being unfamiliar with python, I'm not sure how to resolve it and could use a tip. I tried deleting that section since it was just checking for my installed python version and I meet the requirements, but the same syntax error for the same text shows up later in the script.

[ADeadTrousers]

That's an error from the repo-command ... strange.
But you only need imjtool and lpmake which both can be obtained in binary format:
http://newandroidbook.com/tools/imjtool.tgz
https://forum.xda-developers.com/t/guide-ota-tools-lpunpack.4041843/

[SepticFuddy]

Ok, now when I try to extract super.img with imjtool, I get this and a 0kb image.img file:

Sparse image v1.0 detected, 1179648 blocks of 4096 bytes
1179648 blocks of 4096 bytes compressed into 2615 chunks (73% compressed)
read_all returned -22
Failed to import sparse file

Worse yet, I get permission errors when I try to run ./imjtool.ELF64 in the ~/unihertz folder I just created and opened permissions on... but if I run it from ~/Downloads, it returns that failure. If I move unihertz into Downloads, permission error again. I can't run the command as just imjtool as in the guide and spending half a day figuring out how to fix that leaves me without time to move forward today anyway. As long as that's not the issue I'm ignoring it

[ADeadTrousers]

Just updated some docs and added more vendor information to BoardConfigCommon.mk.
2208c65

[ADeadTrousers]

Next I will create some precompiled super.img for every device.

[ADeadTrousers]

super.img-files are now part of the releases which corresponds the latest stock rom release.
They need to be updated only when a new stock gets released:
https://github.com/ADeadTrousers/android_device_Unihertz_Atom_L_EEA/releases/download/20210226-alpha/super.img-eea.7z
https://github.com/ADeadTrousers/android_device_Unihertz_Atom_XL_EEA/releases/download/20201219-alpha/super.img-seea.7z
https://github.com/ADeadTrousers/android_device_Unihertz_Atom_L_TEE/releases/download/20210415-alpha/super.img-tee.7z
https://github.com/ADeadTrousers/android_device_Unihertz_Atom_XL_TEE/releases/download/20210415-alpha/super.img-stee.7z
I also added a "troubleshooting"-section to the install guide for this.
03ecd82

[SepticFuddy]

STEE super.img confirmed working