| commit | 283495390ed5f8f7f377baa65bcb9b1a77469e8b | [log] [tgz] |
|---|---|---|
| author | Alexander Martinz <amartinz@shiftphones.com> | Mon Jan 10 17:05:19 2022 +0100 |
| committer | Caleb Connolly <caleb.connolly@protonmail.com> | Mon Jan 10 19:02:02 2022 +0000 |
| tree | 6313d89c79bdce42b270611a3d687318085ddc6a | |
| parent | 902faac35570009ce7bc4a3e8f7adc08fad05164 [diff] |
sdm845: commonize BoardConfigs As beryllium and enchilada can already boot using the same images, unify the kernel and system image configuration. Change-Id: I2458e11959bbb88e91c233df7e6f613839d74bc3 Signed-off-by: Alexander Martinz <amartinz@shiftphones.com>
This device repo aims to support booting AOSP on SDM845 devices supported by the mainline Linux kernel.
IMPORTANT NOTICE --> UNLOCKING AND ROOTING MAY VOID YOUR PHONE WARRANTY AND MAY BRICK YOUR DEVICE AS WELL. I'M NOT RESPONSIBLE FOR EITHER OF THAT.
Here is a reasonable guide to get you started on unlocking and rooting Poco F1 --> https://forum.xda-developers.com/poco-f1/how-to/xiaomi-poco-f1-unlock-bootloader-custom-t3839405
Just for the records I downloaded and installed following external packages to unlock and root my device-->
Also Dont forget to take a backup of your images from TWRP and copy them to your Host machine. It will come very handy. Believe me :)
mkdir aosp-repo cd aosp-repo repo init -u https://android.googlesource.com/platform/manifest -b master git clone https://github.com/aospm/android_local_manifests .repo/local_manifests -b main repo sync -j$nproc source build/envsetup.sh # See table above lunch <codename>-userdebug # Where <codename> is the codename of your device make -j$nproc
NOTE: To get display working on SDM845, we need supported Adreno firmware binaries, otherwise the device will not boot to UI.
Adreno binaries are shipped with non-distributable license,
hence I'm not shipping them in my build setup. You can
extract Adreno a630_* firmware binaries from a working
device build. I extracted mine from
lineage-16.0-20190612-nightly-beryllium-signed.zip ;)
OnePlus 6 firmware can be obtained here: https://gitlab.com/sdm845-mainline/firmware-oneplus-sdm845/-/tree/aosp
Make sure you clone the aosp branch.
Copy the contents to `out/target/product/sdm845/vendor/firmware`
(adjust sdm845 to your lunch target) and run "make -j$nproc" to#
create vendor.img again.
fastboot flash system system.img fastboot flash vendor vendor.img fastboot flash userdata userdata.img fastboot flash boot boot.img fastboot reboot
These steps only work for android-mainline kernels which android build files included. You may also want to build your own kernels manually and copy the output. After building your kernel, do:
make <make flags> INSTALL_MOD_PATH=modules modules_install
Then see this gist for an example script to copy kernel build output.
mkdir kernel-repo cd kernel-repo repo init -u https://android.googlesource.com/kernel/manifest -b common-android-mainline git clone git@github.com:pundiramit/android-local-manifests.git .repo/local_manifests -b kernel repo sync -j$nproc BUILD_CONFIG=beryllium/build.config.beryllium ./build/build.sh
cd aosp-repo source build/envsetup.sh lunch beryllium-userdebug make TARGET_KERNEL_USE=mainline -j$nproc
Now reflash the images as above and boot with your custom kernel.
NOTE:
By default the above instructions will sync/download beryllium-android-mainline branch to kernel-repo/beryllium directory. If you want to reproduce android12-5.4 or GKI build then checkout common-android12-5.4 repo manifest and beryllium-android-5.4 branch instead.
If the latest AOSP manifests don't boot for you, I (try to) maintain a known-booting manifest for AOSP builds with fixed SHA's for each project, try the following:
# First save the current broken manifest for later debugging repo manifest -r -o upstream-broken-manifest.xml # Check out the known-booting manifest pushd .repo/manifests git remote add aospm https://github.com/aospm/platform_manifest.git git fetch aospm git checkout aospm/aospm/booting popd repo init -m aospm-booting.xml repo sync -j4
Then try and build again, if that fixes your build you can start to narrow down the problem by generating a diff between the booting manifest and the upstream one
diff .repo/manifests/aospm-booting.xml upstream-broken-manifest.xml