https://github.com/MercuryWorkshop/RecoMod
RecoMod is a script that will install a custom utility toolkit into a standard chromeOS recovery image. This is essentially the spiritual successor to MrChromebox's fixflags images and is useful for getting past certain bricks, and performing debugging and utility actions on the chromebook, especially if you have RW_LEGACY bios installed. If you find yourself in a situation where you either can't boot chromeos from the internal storage or it would be annoying to, this can help you perform whatever actions you need to. This project utilizes MrChromebox's RW_LEGACY and UEFI roms.
https://github.com/sebanc/chromeos-ota-extract
Extract Android firmware images from an OTA payload.bin file.
With the introduction of the A/B system update, the OTA file format changed. This tool allows to extract and decompress the firmware images packed using the 'brillo' toolset.
Incremental firmware images are not supported (source_copy, source_bsdiff operations).
https://github.com/jay0lee/chromeos-update-directory
Tools for generating and managing a directory of Chrome OS updates
https://github.com/velzie/crumpet
Chromium OS Chroot Environment for Linux (crouton in reverse) . . .
Crumpet is a set of scripts that bundle up into an not-so-easy to use, linux-centric chroot environment that packages a working version of the chromiumos ui
Similarly to crouton, you can install it and switch between the chromiumos UI and the normal linux desktop environment at the press of a button, and enter a chroot terminal inside both
https://github.com/BlueManCZ/automatic-ebuild-maker
This script assists with converting .deb packages to .ebuild files. It is focused especially on packages based on Electron framework. The script tries to extract as much as possible information from .deb archive and fill extracted data to the .ebuild template.
https://github.com/sakaki-/genup
genup is a utility intended to simplify the process of keeping your Gentoo system up to date. When invoked, it automatically performs the following steps, in order:
updates Portage tree (and active overlays), and syncs eix(1) (using emaint sync / eix-sync)
removes any prior emerge(1) resume history (using emaint --fix cleanresume)
on aarch64, attempts to apply any pending fixups (if desired, by running /etc/cron.weekly/fixup; errors non-fatal)
ensures Portage(5) itself is up-to-date (using emerge --oneshot --update portage)
ensures genup itself is up-to-date (restarting if not) (using emerge --oneshot --update genup)
updates all packages in the @world set (first using emtee(1), if the matching USE flag is set, and then using emerge --deep --with-bdeps=y --changed-use --update @world)
removes unreferenced packages (using emerge --depclean)
rebuilds any external modules (such as those for VirtualBox) (using emerge @module-rebuild --exclude '*-bin')
rebuilds any packages depending on stale libraries (using emerge @preserved-rebuild)
updates any old perl(1) modules (using perl-cleaner --all)
resolves clashing config file changes (in interactive mode) (using dispatch-conf)
upgrades the kernel if possible (to staging, in /boot) (using buildkernel --stage-only)
removes unreferenced packages (again) (using emerge --depclean)
fixes missing shared library dependencies (using revdep-rebuild)
rebuilds any packages depending on stale libraries (again) (using emerge @preserved-rebuild)
removes any unused source tarballs (if desired) (using eclean --deep distfiles)
deploys new kernel from staging (if desired and available) (using buildkernel --copy-from-staging)
updates environment settings (as a precautionary measure) (using env-update)
updates eix package metadata (using eix-sync -0)
runs any custom updaters in /etc/genup/updaters.d
The genup utility can be invoked in non-interative (default) or interactive mode (see the --ask option in the manpage). Non-interactive mode is suitable for use in a scripted invocation, for example as part of a nightly cron(8) job.
https://github.com/fabnicol/mkg
MKG, an automated Gentoo installer
For MKG installation and guidelines, please refer to the companion Wiki:
https://github.com/fabnicol/mkg/wiki
Dependencies
More specifically for dependencies:
https://github.com/fabnicol/mkg/wiki/Frequently-Asked-Questions-(FAQ)#what-dependencies-should-be-installed
Docker images should be not be fetched in the Packages section of this site, but as Releases in the mkg_docker_image repository.
Portability source code
The auxiliary tool uuid is an obligatory dependency of MKG.
On Debian-style platforms, use sudo apt install uuid.
On Gentoo itself as a host, use emerge -u sys-apps/util-linux.
MKG will then make use of uuidgen instead of uuid.
For other platforms, the source package of the uuid auxiliary tool has been added to enhance portability.
Should you need to install it, please perform installation as follows:
unpack: tar xzvf libuuid-1.0.3a.tar.gz
cd libuuid-1.0.3
./configure && make && sudo make install
Finally check that which uuid has zero exit code.
https://github.com/Sharrisii/TAZ
TAZ stands for temporary autonomous zone. Gentoo linux livecd/liveusb iso's can be found for x86 (32-bit) and amd64 (64-bit, both for amd as intel 64-bit cpu's). The 32-bit version can be run on all 32-bit machines and also on some 64-bit machines (the latter, only if the bios allows 32-bit legacy boot mode and that the 32-bit kernel offers the drivers needed for the 64-bit system). The 64-bit version can be run on all 64-bit machines however, and is hence advised if you have a 64-bit machine. The TAZ livecd's differ from the official x86 and amd64 gentoo live media by being rather small (able to fit on a cd) while still having full livecd functionality (so not an install cd). We focus on low-end pc's so you can expect this distro to work fast regardless of system specs. Preferably use either refurbished pc's or 2nd hand pc's as these have a lower environmental impact. Our motto is also to "use your machine untill it breaks" rather than swapping it out for whatever latest fancy that just appeared on the market. That way, the environmental impact of your machine is again reduced, and you also save money at the same time. Also, repair the machine when broken (if still possible) and maintain it properly to prevent early breakdown. Repairing the machine is possible at a local computer repair shop, or you might be able to do it yourself in some cases. If repairing the machine is not possible, you could scavenge any working parts and reuse or sell them (or just give them) to a second-hand shop. If you don't feel like bothering with this, then at least dispose the broken-down machine to a civic amenity site for proper recycling. To maintain the machine properly, make sure adequate cooling is present (preferably water cooling, heat pipes, larger/more powerful fans or just by improving air flow inside the computer case) and vacuum clean the pc internally every once in a while (to clear out dust buildup which can damage the circuit boards). Upon boot, the data of the selected boot setup on the livecd or liveusb is written to tmpfs (RAM) -so there's not even a need for a regular hard disk to be present (although you will require a fair amount of RAM)-. The TAZ livecd/liveusb iso's also include the files found in the /files_included_in_TAZ_isos/ github folder. These files allow the iso to retrieve the settings, scripts, ... found in the "TAZ_optional_usb_stick"-repo which are to be downloaded and placed on a USB-stick (or memory card placed in a memorycard-to-usb/memorycard-to-pci_express adapter). In the x86 version, besides these scripts, settings, ... this USB stick/memory card also holds the programs for boot setup2to6 (as well as a possible 7th boot setup). So, this USB stick/memory card needs to be inserted to the PC before every boot for these settings, scripts, and the 2nd to 7th boot setup to work (booting the cd without the USB stick/memory card is possible but you then don't get any of these.) For x86, the lowest supported class of cpu's are the SSE-cpu's, so Pentium 3 / Athlon Xp. For the amd64-version, bootsetup 2 to 6 will be on the iso instead (so you can write the iso with bootsetup 1 to 6 to a dvd or a USB stick (writing to a USB stick is not recommended for safety reasons, but possible). The 7th boot setup and the settings and scripts will remain on the optional usb stick repo for writing to a USB stick/memory card.
https://github.com/mthfrr/gentoo-patch-iso
Gentoo ISO patching tool
About
This script modifies a bootable Gentoo ISO to facilitate unattended installation.
This script:
reduces grub's timeout to 1 sec
enables sshd at boot
adds the ssh public keys from a GitHub account to authorized_keys
Dependencies
cdrtools (mkisofs)
curl
mksquashfs (mksquashfs)
p7zip
sed
sudo
Usage
Running this script requires sudo to be available.
⚠ edit the script to change your GitHub username
./patch.sh source.iso patched.iso
https://github.com/MercuryWorkshop/RecoMod
RecoMod is a script that will install a custom utility toolkit into a standard chromeOS recovery image. This is essentially the spiritual successor to MrChromebox's fixflags images and is useful for getting past certain bricks, and performing debugging and utility actions on the chromebook, especially if you have RW_LEGACY bios installed. If you find yourself in a situation where you either can't boot chromeos from the internal storage or it would be annoying to, this can help you perform whatever actions you need to. This project utilizes MrChromebox's RW_LEGACY and UEFI roms.
https://github.com/sebanc/chromeos-ota-extract
Extract Android firmware images from an OTA payload.bin file.
With the introduction of the A/B system update, the OTA file format changed. This tool allows to extract and decompress the firmware images packed using the 'brillo' toolset.
Incremental firmware images are not supported (source_copy, source_bsdiff operations).
https://github.com/jay0lee/chromeos-update-directory
Tools for generating and managing a directory of Chrome OS updates
https://github.com/velzie/crumpet
Chromium OS Chroot Environment for Linux (crouton in reverse) . . .
Crumpet is a set of scripts that bundle up into an not-so-easy to use, linux-centric chroot environment that packages a working version of the chromiumos ui
Similarly to crouton, you can install it and switch between the chromiumos UI and the normal linux desktop environment at the press of a button, and enter a chroot terminal inside both
https://github.com/BlueManCZ/automatic-ebuild-maker
This script assists with converting .deb packages to .ebuild files. It is focused especially on packages based on Electron framework. The script tries to extract as much as possible information from .deb archive and fill extracted data to the .ebuild template.
https://github.com/sakaki-/genup
genup is a utility intended to simplify the process of keeping your Gentoo system up to date. When invoked, it automatically performs the following steps, in order:
updates Portage tree (and active overlays), and syncs eix(1) (using emaint sync / eix-sync)
removes any prior emerge(1) resume history (using emaint --fix cleanresume)
on aarch64, attempts to apply any pending fixups (if desired, by running /etc/cron.weekly/fixup; errors non-fatal)
ensures Portage(5) itself is up-to-date (using emerge --oneshot --update portage)
ensures genup itself is up-to-date (restarting if not) (using emerge --oneshot --update genup)
updates all packages in the @world set (first using emtee(1), if the matching USE flag is set, and then using emerge --deep --with-bdeps=y --changed-use --update @world)
removes unreferenced packages (using emerge --depclean)
rebuilds any external modules (such as those for VirtualBox) (using emerge @module-rebuild --exclude '*-bin')
rebuilds any packages depending on stale libraries (using emerge @preserved-rebuild)
updates any old perl(1) modules (using perl-cleaner --all)
resolves clashing config file changes (in interactive mode) (using dispatch-conf)
upgrades the kernel if possible (to staging, in /boot) (using buildkernel --stage-only)
removes unreferenced packages (again) (using emerge --depclean)
fixes missing shared library dependencies (using revdep-rebuild)
rebuilds any packages depending on stale libraries (again) (using emerge @preserved-rebuild)
removes any unused source tarballs (if desired) (using eclean --deep distfiles)
deploys new kernel from staging (if desired and available) (using buildkernel --copy-from-staging)
updates environment settings (as a precautionary measure) (using env-update)
updates eix package metadata (using eix-sync -0)
runs any custom updaters in /etc/genup/updaters.d
The genup utility can be invoked in non-interative (default) or interactive mode (see the --ask option in the manpage). Non-interactive mode is suitable for use in a scripted invocation, for example as part of a nightly cron(8) job.
https://github.com/fabnicol/mkg
MKG, an automated Gentoo installer
For MKG installation and guidelines, please refer to the companion Wiki:
https://github.com/fabnicol/mkg/wiki
Dependencies
More specifically for dependencies:
https://github.com/fabnicol/mkg/wiki/Frequently-Asked-Questions-(FAQ)#what-dependencies-should-be-installed
Docker images should be not be fetched in the Packages section of this site, but as Releases in the mkg_docker_image repository.
Portability source code
The auxiliary tool uuid is an obligatory dependency of MKG.
On Debian-style platforms, use sudo apt install uuid.
On Gentoo itself as a host, use emerge -u sys-apps/util-linux.
MKG will then make use of uuidgen instead of uuid.
For other platforms, the source package of the uuid auxiliary tool has been added to enhance portability.
Should you need to install it, please perform installation as follows:
unpack: tar xzvf libuuid-1.0.3a.tar.gz
cd libuuid-1.0.3
./configure && make && sudo make install
Finally check that which uuid has zero exit code.
https://github.com/Sharrisii/TAZ
TAZ stands for temporary autonomous zone. Gentoo linux livecd/liveusb iso's can be found for x86 (32-bit) and amd64 (64-bit, both for amd as intel 64-bit cpu's). The 32-bit version can be run on all 32-bit machines and also on some 64-bit machines (the latter, only if the bios allows 32-bit legacy boot mode and that the 32-bit kernel offers the drivers needed for the 64-bit system). The 64-bit version can be run on all 64-bit machines however, and is hence advised if you have a 64-bit machine. The TAZ livecd's differ from the official x86 and amd64 gentoo live media by being rather small (able to fit on a cd) while still having full livecd functionality (so not an install cd). We focus on low-end pc's so you can expect this distro to work fast regardless of system specs. Preferably use either refurbished pc's or 2nd hand pc's as these have a lower environmental impact. Our motto is also to "use your machine untill it breaks" rather than swapping it out for whatever latest fancy that just appeared on the market. That way, the environmental impact of your machine is again reduced, and you also save money at the same time. Also, repair the machine when broken (if still possible) and maintain it properly to prevent early breakdown. Repairing the machine is possible at a local computer repair shop, or you might be able to do it yourself in some cases. If repairing the machine is not possible, you could scavenge any working parts and reuse or sell them (or just give them) to a second-hand shop. If you don't feel like bothering with this, then at least dispose the broken-down machine to a civic amenity site for proper recycling. To maintain the machine properly, make sure adequate cooling is present (preferably water cooling, heat pipes, larger/more powerful fans or just by improving air flow inside the computer case) and vacuum clean the pc internally every once in a while (to clear out dust buildup which can damage the circuit boards). Upon boot, the data of the selected boot setup on the livecd or liveusb is written to tmpfs (RAM) -so there's not even a need for a regular hard disk to be present (although you will require a fair amount of RAM)-. The TAZ livecd/liveusb iso's also include the files found in the /files_included_in_TAZ_isos/ github folder. These files allow the iso to retrieve the settings, scripts, ... found in the "TAZ_optional_usb_stick"-repo which are to be downloaded and placed on a USB-stick (or memory card placed in a memorycard-to-usb/memorycard-to-pci_express adapter). In the x86 version, besides these scripts, settings, ... this USB stick/memory card also holds the programs for boot setup2to6 (as well as a possible 7th boot setup). So, this USB stick/memory card needs to be inserted to the PC before every boot for these settings, scripts, and the 2nd to 7th boot setup to work (booting the cd without the USB stick/memory card is possible but you then don't get any of these.) For x86, the lowest supported class of cpu's are the SSE-cpu's, so Pentium 3 / Athlon Xp. For the amd64-version, bootsetup 2 to 6 will be on the iso instead (so you can write the iso with bootsetup 1 to 6 to a dvd or a USB stick (writing to a USB stick is not recommended for safety reasons, but possible). The 7th boot setup and the settings and scripts will remain on the optional usb stick repo for writing to a USB stick/memory card.
https://github.com/mthfrr/gentoo-patch-iso
Gentoo ISO patching tool
About
This script modifies a bootable Gentoo ISO to facilitate unattended installation.
This script:
reduces grub's timeout to 1 sec
enables sshd at boot
adds the ssh public keys from a GitHub account to authorized_keys
Dependencies
cdrtools (mkisofs)
curl
mksquashfs (mksquashfs)
p7zip
sed
sudo
Usage
Running this script requires sudo to be available.
⚠ edit the script to change your GitHub username
./patch.sh source.iso patched.iso