device/generic/sdm845 (AOSP device config for SDM845 devices)
This device repo aims to support booting AOSP on SDM845 devices supported by the mainline Linux kernel.
- OnePlus 6 (enchilada)
- Xiaomi PocoPhone F1 (beryllium)
How to unlock and root Poco F1?
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-->
- miflash_unlock-en-3.3.525.23.zip (MS Windows only tool for unlocking)
- twrp-3.3.0-0-beryllium.img (Recovery)
- beryllium-9.6.10-9.0-vendor-firmware.zip (LineageOS dependency)
- Magisk-v19.3.zip (Root)
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 :)
How to build and flash AOSP images?
- Download source and build AOSP images
mkdir aosp-repo cd aosp-repo repo init -u https://android.googlesource.com/platform/manifest -b master git clone https://github.com/pundiramit/android-local-manifests.git .repo/local_manifests -b master repo sync -j$nproc source build/envsetup.sh # See table above lunch <codename>-userdebug # Where
is the codename of your devicemake -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, copy the contents of the postmarketos subdirectory up a level. It will need to be supplemented by a630_sqe.fw from linux-firmware. Then copy the binaries to out vendor directory i.e. out/target/product/beryllium/vendor/firmware, and run "make -j$nproc" to create vendor.img again.
- Flash and boot AOSP images -->
fastboot flash system system.img fastboot flash vendor vendor.img fastboot flash userdata userdata.img fastboot flash boot boot.img fastboot reboot
How to run custom kernels?
- Run following commands to clone the kernel source and prebuilt Android toolchains and build scripts:
mkdir kernel-repo cd kernel-repo repo init -u https://android.googlesource.com/kernel/manifest -b common-android-mainline git clone [email protected]:pundiramit/android-local-manifests.git .repo/local_manifests -b kernel repo sync -j$nproc BUILD_CONFIG=beryllium/build.config.beryllium ./build/build.sh
- Delete all objects in aosp-repo/device/generic/sdm845/prebuilt-kernel/android-mainline/ then copy build artifacts from kernel-repo/out/beryllium-android-mainline/dist/ to aosp-repo/device/generic/sdm845/prebuilt-kernel/android-mainline/ build AOSP images again.
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.
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.
- LEDs and Brightness Control
- Modem / RIL / Voice Call
- Battery Stats
- Sensors and Accelerometers