This repository records the tested BakaSU + SUSFS v2.3.0 GKI 6.6.118 kernel for POCO C85 5G. The tested phone runs the existing ProjectInfinity-X Android 16 GSI with unchanged EEA vendor OS3.0.301.0.WBNEUXM. The kernel's release string is 6.6.118-android15-8-ge56cf6b09cca-ab15511674-4k, matching the stock vendor module ABI. The AnyKernel3 package patches the active slot's boot image; it does not replace vendor, vendor_boot, or the GSI.
Only this firmware/GSI combination and slot A have been tested. A successful recovery flash alone does not establish that Android will boot. Check the device codename, current slot, and firmware before proceeding.
The v6.6.118-20261010 release contains:
- BakaSU-dew-GKI6.6.118-SUSFS-AnyKernel3-20261010.zip — the recovery-flashable kernel tested on the phone.
- BakaSU-v4.2.0-rc3-dew-local-arm64-v8a.apk — the matching manager APK. Its local signing certificate is accepted by this kernel.
- ASSET_SHA256SUMS — SHA-256 hashes for both assets.
Verify downloads with sha256sum -c ASSET_SHA256SUMS in the directory containing all three files. The release record at releases/dew-bakasu-20261010/README.md contains source revisions, patches, checksums, validation, and the tested backup path.
- Confirm the phone is
dew, the bootloader is unlocked, Android boots normally, and the vendor is stillOS3.0.301.0.WBNEUXM. Back up important data. In Android, runadb shell getprop ro.product.vendor.device,adb shell getprop ro.vendor.build.fingerprint, andadb reboot bootloader; in bootloader fastboot, runfastboot devicesandfastboot getvar current-slot. Record the slot. - Keep a known-working image of that phone's active
bootpartition before changing the kernel, and copy it to your computer. If you already have root or a recovery that can readboot, back up the active slot and verify the saved image is nonempty. Alternatively, keep theboot.imgfrom the exact firmware currently installed only if you know that image boots your current setup. A matching vendor version alone does not prove that the firmware image matches a modified GSI boot setup. The backup in the release record belongs to one tested phone and must not be used as another phone's rollback image. Do not flash if you have no verified rollback image. - Boot the working OrangeFox r2 recovery for this phone. Use its Install screen to choose the downloaded AnyKernel3 ZIP (or its ADB Sideload screen with
adb sideload BakaSU-dew-GKI6.6.118-SUSFS-AnyKernel3-20261010.zip). Wait forDone!andProcess ended with no errorsbefore rebooting to System. The ZIP is for recovery, notfastboot flash, and recovery flashing still changes the active slot'sbootimage. - Once Android fully boots, install the matching APK with
adb install -r BakaSU-v4.2.0-rc3-dew-local-arm64-v8a.apkor Android's package installer. Open BakaSU and confirm it reports Working, driver v4.2.0-rc3 (35222/5), and SUSFS v2.3.0. If Android fails to boot, restore the saved boot image before trying another package.
Do not use fastbootd for a boot or vendor_boot rollback. Do not flash the kernel ZIP or the backup image to vendor_boot. No userdata wipe is needed to reverse this kernel change.
Enter bootloader fastboot with Power + Volume Down, connect USB, and check fastboot devices, fastboot getvar is-userspace, and fastboot getvar current-slot. Continue only with is-userspace: no and the same slot recorded before installation. If that slot was a, restore your own verified, known-working slot-A image:
fastboot flash boot_a ./boot_a-known-working.img
fastboot rebootReplace the filename with the actual path to your saved image; the example file is not supplied by this repository. For another slot, use that phone and slot's own known-working boot image. If the current slot differs from the one recorded before installation, determine why before writing anything. A module-related boot loop may be recoverable through BakaSU module safe mode (press and release Volume Down at least three times after the first boot screen), then remove the offending module.
The repository's build.sh pins the kernel, BakaSU, and AnyKernel3 commits. The rest of the Android build dependencies come from the named AOSP manifest branch, which may change after this release. The release directory stores the exact tracked-source patches and added files for the tested build. These are the important inputs:
| Component | Pinned source |
|---|---|
| Android GKI/Kleaf | common-android15-6.6-2026-01; kernel/common commit 3b2ca55a1d9636b971b6110ec760604f12a36af0 |
| BakaSU kernel | Baka-SU/BakaSU commit 5b76b884c75f729a220bb317aa4a4fc78f0e0e9c |
| SUSFS | gki-android15-6.6 commit a0f9c59e2243f8a5db955f4ad1686d5e0ad26e1a; its tested source is captured in common-added-files.tar.gz |
| AnyKernel3 | osm0sis/AnyKernel3 commit 020dfeccf9d7e962a48400fc94d3e451df92eead plus packaging/anykernel.sh |
Use a Linux x86-64 build host with sufficient disk space (the Android/Kleaf checkout and build cache take many gigabytes), git, Google's repo launcher, python3, tar, rsync, zip, unzip, sha256sum, and the tools Kleaf installs through its manifest. Network access is needed for a fresh checkout. The script leaves existing checkouts in place and stops if a pinned Git revision does not match; it never silently upgrades the stock vendor or changes the GSI.
git clone https://github.com/0xra0/Dew_Kernel.git
cd Dew_Kernel
repo --version # install Google's repo launcher first if absent
./build.sh prepare # sync pinned Android source, apply recorded patches
./build.sh build # Kleaf //common:kernel_aarch64_dist, stamped thin LTO
./build.sh package # create a local recovery ZIP with the tested dew installer scriptThe default work and output directories are .build/dew-6.6.118/workspace and .build/dew-6.6.118/output. They can be placed on another disk:
WORKSPACE=/mnt/sata/dew-build/workspace OUTPUT=/mnt/sata/dew-build/output ./build.sh allThe script checks the built Image for the exact stock-compatible release string before packaging and checks the ZIP archive. The new ZIP is named BakaSU-dew-GKI6.6.118-SUSFS-AnyKernel3-local.zip. A rebuild is a new binary, not the phone-tested release asset; compare its ABI and test it with a rollback image before using it. Do not flash a raw Kleaf Image or a newly generated standalone boot.img to this phone.
The released APK is the tested manager. Its source is the same pinned BakaSU revision with BakaSU-manager.patch. The manager uses Android Gradle, Rust/Cargo, Android SDK/NDK, and a signing key. For an independent build, use a separate checkout and apply the recorded manager patch:
git clone https://github.com/Baka-SU/BakaSU.git BakaSU-manager
cd BakaSU-manager
git checkout --detach 5b76b884c75f729a220bb317aa4a4fc78f0e0e9c
git apply /path/to/Dew_Kernel/releases/dew-bakasu-20261010/BakaSU-manager.patch
cd manager
# Configure Android SDK/NDK, Rust/Cargo, and your own signing key.
# See sign.example.properties for KEYSTORE_FILE, KEYSTORE_PASSWORD,
# KEY_ALIAS, and KEY_PASSWORD; keep the real values private.
./gradlew assembleReleaseSign with your own key. A differently signed APK will not be accepted by the shipped kernel's local-signature entry and may not upgrade the installed package. To use another signing key, rebuild the kernel with its matching manager certificate and install the APK according to Android's package-signature rules. The signing private key is not in this repository.