mer-hybris/hybris-boot

hybris-boot

This project enables the building of boot images for Google Android fastboot based devices.

It can be built either in the android build tree as part of the normal kernel/android pre-requisited build or in a Mer SDK as a standalone package

Android Build

We need to extend subdir_makefiles in build/core/main.mk to include hybris/Android.mk; that then includes any additional Android.mk files in subdirs

Note the default boot.img is created by $(INSTALLED_BOOTIMAGE_TARGET) target in build/core/Makefile and that is used for inspiration.

Add as a normal make/mka target: $ mka hybris-boot hybris-recovery

SDK Building

In the SDK you'll need the kernel, module and static busybox packages available

$ git clone https://github.com/mer-hybris/hybris-boot
$ cd hybris-boot
$ make <device>

Operating System Bootstrap

The initramfs boots into a Mer derived OS installation by loading first the default Android /data partition and then bind mounting a root filesystem under /data/media/0/.stowaways/sffe. This behaviour is easily modified by editing the ./initramfs/init shell script.

Initial RAM FS Debug Console

With your device booted to fastboot, boot the boot.img in debug mode:

$ sudo fastboot boot boot.img -c bootmode=debug

Wait for your host computer to pick up DHCP lease from usb network device:

$ telnet 192.168.2.15

hybris-boot's Issues

[update-binary][Android 8+] Broken flashable zips because set_metadata is no longer available

The command set_metadata() is no longer available from Oreo's recovery
https://github.com/mer-hybris/hybris-boot/blob/master/Android.mk#L231

Will investigate whether we can leave the permission change set out or whether we have to switch the update-binary to a shell script.

This issue is present in community adaptations which do not use the lvm-based approach to installation.

:question can you ssh into onyx after installing hybris boot?

after installation of hybris boot can you ssh and not just telnet?

Reason for hybris-boot instead of using AOSP boot code

This is not a bug, just a question.

I am wondering why hybris-boot is used as a ramdisk instead of modifications in AOSP itself? Is it purely because of maintenance overheard? Please help me understand. Thanks

Please remove device-specific hacks from fixup-mountpoints

Adding device- or vendor-specific hacks to platform-agnostic repositories is poor form and detracts from code readability and interoperability. Device family common repos especially would have trouble with such a system. Device hacks should be written in from vendor or device repos--you may need to add a variable to facilitate this. I would recommend something like TARGET_HYBRIS_FSTAB, which could be set from a device-specific repo and provide device-specific fstab locations.

[Idea] CI verification of fixup-mountpoints

It's more than easy to make a small mistake in fixup-mountpoints (forget the trailing ;;, for instance). Thus I'd suggest using some CI service [1] [2] to validate its correctness using shellcheck. [3] There's an official Docker image for shellcheck CI [4]

Similarly, pylint could be used to verify assert-device (please keep in mind that pylint is sometimes overzealous). Still, the main concern is fixup-mountpoints, because it's the one most PRs target.

[1] https://github.com/ligurio/Continuous-Integration-services/blob/master/continuous-integration-services-list.md
[2] https://github.com/marketplace/category/continuous-integration
[3] https://github.com/koalaman/shellcheck
[4] https://hub.docker.com/r/koalaman/shellcheck/

init-script: configfs based usb configuration not working on Nexus 5X (bullhead).

ad27186 will cause Nexus 5X to bootloop because the init script could not initialize USB gadget correctly.

Here is the init.log: https://pastebin.ubuntu.com/p/XXr6frWFn5/
Here is my kernel config: https://github.com/RedL0tus/android_kernel_lge_bullhead/blob/cm-14.1/arch/arm64/configs/lineageos_bullhead_defconfig

Maybe we should prefer using USB gadget mode than configfs for compatibility.

Line 36 will cause error

So in the hybris-updater-script line 36 is blank this causes an error in make sed: -e expression #2, char 36: unknown option to `s'
A simple fix is to remove line 36 and keep only 35 lines 😄