[TouchPad General] mpgrimm2:
My Current ROM installation "Updater-Scripts" Notes

(3-10-14)
​

DISCLAIMER: I'm not a dev, nor do I play one on t.v. Use the information and links at your own risk. READ and UNDERSTAND what your doing before flashing is the best bet. I take no responsibility or credit for the information.

This is just an FYI, a work in progress, it should not be considered wholly accurate and is just a reference on the various regular vs current data/media builds and their "updater-scripts".

---------------------------------------------------------​

Summary:

1) The /boot partition is about 30.99mb and is shared with both WebOS, Moboot 0.3.8, any recoveries, and any android Roms.

- The Rom's "kernel" or boot.img is stored here as a .uImage file with a "splash" file (is this the rom's splash screen image? IDK ) .

- As a reference, my previous install of JC's CM10.1 VPN build takes up about 25mb-27mb, so there is very limited free space for ANY redundancy without causing installation or reboot issues.

- data/media roms and recoveries have larger /boot/ "uImage" files so keep an eye out for left over ROM and Recovery files that "may" need to be manually removed.

2) Both the CM and Evervolv Roms (regular and data/media versions) currently format the /system partition for you during the installation process.

3) ONLY the Evervolv Rom install scripts currently delete a few "Select" Roms from the boot partition for you during installation.

(only CM, AOKP, ICS, & ClassicNerd)

4) If you are coming from Evervolv or another ROM to a CyanogenMod ROM, the CM installation scripts WILL NOT remove ANY other ROM from the /boot partition and you may run out of room or get an installation error.

5) Removing previous ROM files from the /boot is not specifically a function of the recovery but a command issued to the recovery by the ROM's installation script!

- One of the main differences I noticed between the CM10.2 and CM11 data/media build install scripts is that CM11 scripts appear to need Recovery support for "set_metadata" where as Evervolv and the CM10.2 currently do not for "setting permissions".

2-22-14 TESTING UPDATE (Moving from Evervolv to CM):

- If you are coming from an Evervolv ROM to a CyanogenMod ROM (Regular or Data/Media), I have modified JcSullin's "Set CyanogenMod as Moboot Default zip to also delete the Evervolv ROM from /boot to prevent you from running out of space.

Flash the zip after a wipe/format and before flashing a CM rom zip.

Thanks to JcSullins and Flintman for the original zips and script templates.

- Here you go: JCs-update-boot-cm-default_Plus-DELETE-EV .zip - 143.89 KB

If you prefer to manually push or remove files from the /boot partition, there is some discussion in Flintman's Evervolv thread starting here.

BONUS:

Please see my additional thoughts on the install scripts, naming conventions, and AcmeInstallers after the screenshots.

image

image

image

image

A Request to the Devs on install scripts, naming conventions, and AcmeInstallers

(again, I am not a Dev! )

Now that we have explored some of the reasons why the /boot partition might run out of space, some of us have also wondered why there was a need for some of the "extra" AcmeInstallers (ie iMarck90's Acme5, 5M, 5E, 5T, & 5ET) beyond just having a larger "system" partition size.

Now take a look again at the above updater-script screenshots. Pay attention to the bottom sections where the /boot.img gets installed. On dedicated android devices with only one /boot.img the installation is easy because the filename never has to change from one rom name to another, just extract/copy the boot.img to the /boot and it will overwrite the previous one. Done.

On the TP:

- CM's boot.img file gets copied to the /boot as a custom filename "uImage.CyanogenMod"

- CM's splash file gets copied to the /boot as a custom filename "moboot.splash.CyanogenMod.tga"

- Evervolv's boot.img file copies to the /boot as a custom filename "uImage.Evervolv"

- Evervolv's splash file gets copied to the /boot as a custom filename "moboot.splash.CyanogenMod.tga"

- CWM's boot.img file is copied to the /boot as a custom filename "uImage.ClockworkMod"

- TWRP's boot.img file is copied to the /boot as a custom filename "uImage.TWRP"

- Moboot's boot.img file is copied to the /boot as a custom filename "uImage.moboot"

Perhaps if the devs would consider something similar to the following for the TP, we could avoid any space issues in the /boot:

- Copy all ROM's boot.img's to the /boot partition with the standard filename of "uImage.Android"

- Copy all ROM's splash files to the /boot partition with the standard filename of "moboot.splash.Android.tga"

- Copy all recovery boot.img's to the /boot partition with the standard filename of "uImage.AndroidRecovery"

Then there would never be any doubt about left over files in the /boot. And AcmeInstaller wouldn't need modified for specific /boot.img filenames between roms other than data/media builds that require "metadata" in the install scripts which may be a work in progress by iMarck90 for SeLinux 3.x kernel builds and recoveries (we hope).

TP Developers please note:

I appreciate all your hard work and can only hope that no one takes offense to the above thoughts or is discouraged as I promise no slight is intended. As an average user I am merely peaking behind Oz's curtain whenever I manage to learn something new and seek to share with others. Perhaps a properly placed question like mine, even one without all the information, can be useful.

Comments welcome.

Sincerely,

Mpgrimm2

^^ Back to the OP ^^