[TouchPad General] DoubleStuff:
Journey #1: How files get populated to /boot. ( The Original Journey )

Ok staying with the landing on the moon theme, now that I have landed, I went to explore a moon crater ( the HP Ramdisk ) its dark and filled with scary monsters. But like HP_TOUCHPAD might say, "you have 2 weapons on your journey: your brain, and asking questions"..

So I am on CM11 KitKat by JC Sullins, and there are 4 HPTP_Universal_settings files ( UOS ), looking within those zip files there is a boot.img which eventually gets copied to /boot as uImage.CyanogenMod. ( UOS ) also contain the build.prop file which gets copied to /system.

There is also a small file called moboot.default which also gets copied to /boot, it just contains a text string "CyanogenMod" and that would be the default on the moboot menu.

My pics below are not meant as instruction, they are meant to tell a story of a man who visited the moon and explored a crater called HP Ramdisk. While there, he saw a winding stream, where on a boat, CYAN martians were creating the /boot directory, he also saw a tree where the famous JC Sullins carved his name in 2014. Take look at the pictures to see his other adventures. I tell you once you go to HP RAMDISK you want to visit again, and again!!! because HP_TOUCHPAD has created a vehicle where its possible to visit, and stay away from danger.

After C:/boot is run to fix the "Bermuda triangle boot corruption" the C:/boot process creates the /boot directory but its missing the files and directories that should be in /boot. So I am assuming when I flash the UOS file, that it will begin to populate /boot. I am interested in finding out how uImage.CyanogenMod gets to boot. That was the goal of this first journey. On subsequent journeys I want to find out how all the files get populated to boot namely:

the files of /boot:

*android.default.recovery ( copied to /boot by an updater-script via a TWRP3.2 flash, this contains one string: "Recovery" )

*moboot.default

( copied to /boot by an updater-script via a UOS flash, this contains one string: "CyanogenMod" )

*uImage

( is a symbolic link to /boot/uImage.moboot, but did not see where this link was created )

*uImage.CyanogenMod

( copied to /boot by an updater-script via UOS flash: boot.img to /boot/uImage.CyanogenMod )

*uImage.moboot

( did not see how it was copied to /boot )

*uImage.Recovery

( copied to /boot by the updater-script via TWRP3.2 flash, this is what gets ran when selecting "boot Recovery" )

Here was my key finding the goal of my 1st journey:

uImage.CyanogenMod is copied to /boot by an updater-script via UOS flash which copies boot.img to /boot/uImage.CyanogenMod.

Also in CM11 a file called moboot.splash.CyanogenMod.tga gets placed in /boot by the original ROM zip, and its an image of a "CYAN Martian" that the user sees during a reboot into the ROM.

In the 4 Universal Optimized Settings ( UOS ) files, I have these observations so far:

1) It appears that the boot.img which is the uImage.CyanogenMod file ( extracted from the Original ROM cm-11-20151116-SNAPSHOT-jcsullins-tenderloin.zip ) is being modified, because CPU settings need to be different, maybe HP_TOUCHPAD can tell us if there are any other modifications to boot.img.

2) It appears that the build.prop files are exactly the same, in each of the 4 UOS files for CM11 KitKat.