[Samsung Galaxy Tab A series Guides, News, & Discus] System23:
Hi,

NP only ASK 4 what that you dont Understand!!!

Directory 12 is short 4 Android 12 ROM Files

Directory 13 is short 4 Android 13 ROM Files

when you would use your own Directory like lineageos,ROM,Files,System,etc...... dont Forgett to Change the Path for the affected lines in the "META-INF\com\google\android\updater-script"!!!!!

Dont Forgett to Pack system.img in 12 to zip with best-save-compression,

and

Pack system.img in 13 to xz

i have Test different Packing/Compressing Methods so that i dont exceed the Max. Filesize of the Complete ZIP Package than AROMA_INSTALLER dont work over 2GB Filesize!!!! and the 4GB Filesize AROMA_INSTALLER i have searched but not Found!!!!

So a little bit KnowHow 4 You!!!

1#

The system.img must Compressed to ZIP and XZ so you see in the Example Pack, in order not to exceed the file size of 2GB

2#

The system.img in

12/los19.zip

13/los20.xz

would Copy/Extract to /sdcard you must do it so, than /tmp is to small and cannot handle the Filesize of the Compressed Archive ZIP/XZ, and additionally unpack the Compressed Archive ZIP/XZ in /tmp, the assigned size of /tmp is not sufficient for this

3#

The Folder "extra" Included the Rest of the Flashed Files

extras/vendor.img

extras/vbmeta.img

extras/param.bin

they you need 4 19.1/12 and 20.0/13 System.img they are declared in COPY Process of each ROM in "META-INF\com\google\android\updater-script"

on "line 7" package_extract_dir("extras", "/sdcard/extras");

4#

The Folder "addons" Include root/noroot/magisk/recovery!!!

When you Add a Actually Build Release of the System.img in 12/19.1 or 13/20.0 you dont need to create the root/noroot boot.img new, you can use the Included Examples!!!

these are patched with Magisk 26.1, if you want to patch them with the current Magisk 26.2 then the boot.img file in noroot will remain untouched and will be used to copy this to the device and patch it with Magisk 26.2 and then again copied from the device to the root folder and the existing boot.img will be overwritten.

Then you have it up to date, otherwise after flashing ROM via AROMA_INSTALLER in System Install Magisk 26.2 App and Update boot.img via App Option!!!

you don't have to specify or change these changes/modifications in "META-INF\com\google\android\updater-script"!!!! if you want to update the Magisk_26.1.apk in "addons/magisk" to Magisk_26.2.apk then just save it in "addons/magisk"!!! In "META-INF\com\google\android\updater-script" is declared

on "line 69" "package_extract_dir("addons/magisk", "/sdcard");"

so it COPYs the Directory "addons/magisk" to "/sdcard", the Only change you must do is in

"META-INF\com\google\android\updater-script"

on "line 67" ui_print("Flash ROOTed Boot.img Magisk 26.1...");

on "line 72" ui_print("Flashed ROOTed Boot.img Magisk 26.1");

on "line 73" ui_print("In System goto /sdcard and Install Magisk-v26.1.apk");

only Change 26.1 to 26.2

5#

When you would add your own Menu Option to AROMA_INSTALLER you must Edit

"META-INF\com\google\android\aroma-config" with the Menu variables and must these Menu Box configure in

"META-INF\com\google\android\updater-script" with the Correct Menu Box Config variables!!!

Feel free to add New Menu Options with usefull Stuff!!!!

You can ASK ME if you need more Infos about ,to write your own AROMA_INSTALLER Scripts!!!!

6#

when you are done editing/modifying and the existing example is the basis for your new AROMA_INSTALLER then don't forget to declare your changes in

"META-INF\com\google\android\aroma\changelog.txt"

and in detail Describe what it includes, what build, what release date, what version, where you got files from.

You can expand or rewrite the Example changelog.txt.

But I have one request for you, please add these lines.

<*> Example Build from AROMA_Installer Release by System23 - 21.07.2023 </*>

<*> Modded by "YOUR NAME" "Current creation date" </*>

7#

When you Finished, Compress all Directorys

12/

13/

extras/

addons/

META-INF/

sbin/

to a ZIP Archive and give it a Name xxxxxxxxx.zip

Now you can Test your created AROMA_INSTALLER ZIP!!!!

on Device start TWRP and COPY ZIP to /sdcard

and Flash the ZIP

enjoy the Installer Menu with Options

make a Test Flash of your modified Options

start System if it Runs after Flash

when AROMA_INSTALLER ZIP in TWRP Install not starts than is the Problem the Filesize of the 12/13 Compressed Archives ZIP/XZ, than Compress it again in the Highest Compression you can choose!!!! repack ZIP and Copy it in TWRP to /sdcard and try Install ZIP again!!!!

If the new Release of 12/13 is Bigger than the Older so that Highest Compression of 12/13 not enought, to hold 2GB Filesize than you must remove one of them 12 or 13, so you can only use 1 ROM, dont forgett to modify the scripts, and remove the Menu variables in aroma-config and updater-script!!!!

WHEN YOU HAVE FINISHED/TESTED A WORKING AROMA_INSTALLER THAN FEEL FREE TO UPDATE IT 4 ALL USERS IN THIS THREAD (USE GOOGLE-DRIVE/MEGA/ONEDRIVE/etc.....)