Skip to content

Releases: leegarchat/twrp_device_google_pixels

OrangeFox Recovery - R11.3 RC5

27 Mar 08:55
@leegarchat leegarchat
RC5
b2671dd

Choose a tag to compare

View all tags
OrangeFox Recovery - R11.3 RC5 Latest
Latest
663eb01b-7e99-4e5b-8004-5e45sss29312c6d

Changelog

  • Kernel zip installation (Pixel 7/8/9, WildKSU GKI kernel with Baseband Guard)
    Fixed kernel panic when flashing a kernel zip via AnyKernel3 on devices
    running a WildKSU GKI kernel with the Baseband Guard (BBG) LSM module.

    The bug is in Baseband Guard (vc-teahouse/Baseband-guard): the
    bb_inode_rename hook unconditionally calls page_get_link() for any
    symlink rename, but rootfs and tmpfs symlinks on Linux 6.1 (GKI) have no
    page-cache mapping - causing a NULL pointer dereference and kernel panic.

    The panic triggers in two ways:

    • toybox ln -sf uses renameat() internally and hits the hook; busybox
      ln avoids it (different syscall path), so affected commands were
      already switched to busybox ln as a partial workaround.
    • AnyKernel3 mv during kernel deployment also goes through renameat()
      and cannot be replaced the same way - requiring a kernel-level fix.

    Fix: susfs_rename_fix.ko is loaded automatically at recovery boot. It
    intercepts the faulty hook via kprobe and prevents the crash for symlink
    renames. A source-level fix has been submitted upstream to Baseband Guard.

    Sultan kernel fork (sultan-WildKSU-SUSFS) is not affected - it does
    not exhibit this panic and does not need this module.

    On kernels without Baseband Guard the module loads silently as a no-op.

What's Working

  • Core functions: Decryption, MTP, ADB, ADB Sideload, USB OTG, Charging, Screen Brightness, Flashlight.
  • Recovery features: ZIP/IMG Flashing, Partition Backups, Reflash current OrangeFox.
  • Hardware: Touchscreen and Vibration (⚠️ Requires a live system, see below).

IMPORTANT: TOUCHSCREEN & VIBRATION
The touchscreen and haptics (vibration) will only work if you have a functional system in at least one slot. OrangeFox dynamically loads the required touch and haptics kernel modules directly from your device's vendor and vendor_dlkm partitions.

Why? The Pixel vendor_boot partition has a strict 64MB size limit, and the recovery ramdisk requires at least ~10MB of free space just to boot. It is physically impossible to pack these heavy, device-specific modules directly into the recovery image itself without breaking the boot process.

Supported Devices & Downloads

⚠️ READ CAREFULLY: MATCH YOUR DEVICE CODENAME TO THE CORRECT DOWNLOAD FILE!

Download OrangeFox-R11.3_RC5-gs201.img for Tensor G2:

  • Pixel 7 (panther) | Pixel 7 Pro (cheetah) | Pixel 7a (lynx)

Download OrangeFox-R11.3_RC5-zuma.img for Tensor G3:

  • Pixel 8 (shiba) | Pixel 8 Pro (husky) | Pixel 8a (akita)

Download OrangeFox-R11.3_RC5-zumapro.img for Tensor G4:

  • Pixel 9 (tokay) | Pixel 9 Pro (caiman) | Pixel 9 Pro XL (komodo) | Pixel 9a (tegu)

Initial Installation Guide

On Pixel devices, the recovery is located in the vendor_boot partition.

Method 1: Via PC / Fastboot (RECOMMENDED)

  1. Reboot your phone to Bootloader (Fastboot mode).
  2. Connect to your PC and open a terminal.
  3. Flash the image (Fastboot will automatically flash it to your active slot): 
    fastboot flash vendor_boot OrangeFox-R11.3.img
  4. IMMEDIATELY reboot to recovery: 
    fastboot reboot recovery

Method 2: On-Device (Requires Root)

If you already have Magisk/KernelSU, you can flash it directly from your phone using a terminal emulator (like Termux).

  1. Place OrangeFox-R11.3.img in your internal storage (/sdcard/).
  2. Run these commands: 
    su
dd if=/sdcard/OrangeFox-R11.3.img of=/dev/block/by-name/vendor_boot$(getprop ro.boot.slot_suffix)
  3. Check for errors, then reboot to recovery.

Surviving ROM & OTA Updates (DO NOT SKIP)

CRITICAL INFORMATION: Pixel devices use an A/B slot system. When you install an OTA update or flash a custom ROM, the system WILL OVERWRITE the vendor_boot partition with the stock recovery.

To preserve OrangeFox, you MUST follow this exact sequence:

  1. Boot into OrangeFox.
  2. Flash your ROM/Update .zip file.
    (Pro Tip: Check the box to "Automatically reflash recovery after update" during installation. If you do this, skip to Step 5).
  3. DO NOT REBOOT TO SYSTEM YET!
  4. If you didn't check the auto-reflash box, immediately go to Advanced -> Flash current OrangeFox. (This build uses a modified script that reliably flashes the recovery to BOTH slots simultaneously).
  5. Wait for the process to complete.
  6. CRITICAL STEP: Select Reboot -> Recovery. You MUST reboot back into recovery so the device can switch to the new active slot.
  7. Only AFTER you have rebooted back into OrangeFox can you flash other ZIPs (Magisk, KernelSU, Custom Kernels). This ensures they are installed to the correct, updated slot.
  8. Now you can safely select Reboot System.

⚠️ BOOTLOOP WARNING: Monolithic Kernels with DTB

If you flash a custom kernel (like SultanSU forks) and get a bootloop, IT IS NOT AN ORANGEFOX BUG.

What is actually happening:
Some unofficial forks of monolithic kernels that ship with a dtb inside use broken AnyKernel installer scripts.

  1. The script rebuilds the boot partition.
  2. It then moves on to rebuild vendor_kernel_boot.
  3. The bug: The script forgets to delete the kernel image from step 1. AnyKernel picks it up again and incorrectly packs vendor_kernel_boot with the kernel + dtb + ramdisk. The image becomes invalid and your phone bootloops.

OrangeFox is simply executing the zip script provided by the kernel developer. Since OrangeFox now fully supports decryption on Pixels, these installer bugs (which were previously hidden) are finally exposed. Official Sultan releases do not have this bug.

The Fix (For Kernel Maintainers & Advanced Users):
You must add rm -f commands between the boot and vendor_kernel_boot steps inside anykernel.sh inside the kernel zip:

# boot image installation
block=boot;
is_slot_device=1;
. tools/ak3-core.sh;
split_boot;
flash_boot;

# ADD THESE TWO LINES TO PREVENT BOOTLOOPS:
rm -f "$AKHOME/Image.lz4";
rm -f "$home/Image.lz4";

# vendor_kernel_boot installation (for dtb)
block=vendor_kernel_boot;
is_slot_device=1;
reset_ak;
split_boot;
flash_boot;

Note: If fork maintainers refuse to fix their installer scripts, a forced compatibility patch will be added to OrangeFox in the future to protect users.

Assets 5
Loading

OrangeFox Recovery - R11.3 RC4

26 Mar 06:51
@leegarchat leegarchat
RC4
4da4d0d

Choose a tag to compare

View all tags
OrangeFox Recovery - R11.3 RC4
663eb01b-7e99-4e5b-8004-5e45sss29312c6d

Changelog

  • Fastboot
    Fixed fastboot mode: eliminated blocking HAL lookups (health + fastboot,
    AIDL and HIDL), recovery now enters fastbootd instantly without delays

  • Init
    • Fixed Magisk zip extraction at early-init: resolved missing zip binary
    issue in early-init PATH, binaries now unpack correctly on first boot
    • Dynamic twrp.flags patching at early-init:
    – Auto-detects the correct USB OTG block device (next sdX after last
    internal UFS disk)
    – Prunes partition entries absent on the current device (A/B-aware)

  • Logs / Install
    Fixed garbage/corrupt log output during package installation (e.g.
    NikGapps): busybox is now copied to tmpfs before install begins, so
    sleep and mountpoint survive /system/bin overwrites by the installer

  • Reflash Recovery
    Completely reworked reflash script: added step-by-step error checking,
    flash verification via sha256 read-back from both vendor_boot slots,
    parallel post-flash verification to reduce wait time

  • Build
    Updated release versioning: builds are now labeled 11.3_N inside
    OrangeFox UI, where N is the sequential release number

What's Working

  • Core functions: Decryption, MTP, ADB, ADB Sideload, USB OTG, Charging, Screen Brightness, Flashlight.
  • Recovery features: ZIP/IMG Flashing, Partition Backups, Reflash current OrangeFox.
  • Hardware: Touchscreen and Vibration (⚠️ Requires a live system, see below).

IMPORTANT: TOUCHSCREEN & VIBRATION
The touchscreen and haptics (vibration) will only work if you have a functional system in at least one slot. OrangeFox dynamically loads the required touch and haptics kernel modules directly from your device's vendor and vendor_dlkm partitions.

Why? The Pixel vendor_boot partition has a strict 64MB size limit, and the recovery ramdisk requires at least ~10MB of free space just to boot. It is physically impossible to pack these heavy, device-specific modules directly into the recovery image itself without breaking the boot process.

Supported Devices & Downloads

⚠️ READ CAREFULLY: MATCH YOUR DEVICE CODENAME TO THE CORRECT DOWNLOAD FILE!

Download OrangeFox-R11.3-RC4-gs201.img for Tensor G2:

  • Pixel 7 (panther) | Pixel 7 Pro (cheetah) | Pixel 7a (lynx)

Download OrangeFox-R11.3-RC4-zuma.img for Tensor G3:

  • Pixel 8 (shiba) | Pixel 8 Pro (husky) | Pixel 8a (akita)

Download OrangeFox-R11.3-RC4-zumapro.img for Tensor G4:

  • Pixel 9 (tokay) | Pixel 9 Pro (caiman) | Pixel 9 Pro XL (komodo) | Pixel 9a (tegu)

Initial Installation Guide

On Pixel devices, the recovery is located in the vendor_boot partition.

Method 1: Via PC / Fastboot (RECOMMENDED)

  1. Reboot your phone to Bootloader (Fastboot mode).
  2. Connect to your PC and open a terminal.
  3. Flash the image (Fastboot will automatically flash it to your active slot): 
    fastboot flash vendor_boot OrangeFox-R11.3.img
  4. IMMEDIATELY reboot to recovery: 
    fastboot reboot recovery

Method 2: On-Device (Requires Root)

If you already have Magisk/KernelSU, you can flash it directly from your phone using a terminal emulator (like Termux).

  1. Place OrangeFox-R11.3.img in your internal storage (/sdcard/).
  2. Run these commands: 
    su
dd if=/sdcard/OrangeFox-R11.3.img of=/dev/block/by-name/vendor_boot$(getprop ro.boot.slot_suffix)
  3. Check for errors, then reboot to recovery.

Surviving ROM & OTA Updates (DO NOT SKIP)

CRITICAL INFORMATION: Pixel devices use an A/B slot system. When you install an OTA update or flash a custom ROM, the system WILL OVERWRITE the vendor_boot partition with the stock recovery.

To preserve OrangeFox, you MUST follow this exact sequence:

  1. Boot into OrangeFox.
  2. Flash your ROM/Update .zip file.
    (Pro Tip: Check the box to "Automatically reflash recovery after update" during installation. If you do this, skip to Step 5).
  3. DO NOT REBOOT TO SYSTEM YET!
  4. If you didn't check the auto-reflash box, immediately go to Advanced -> Flash current OrangeFox. (This build uses a modified script that reliably flashes the recovery to BOTH slots simultaneously).
  5. Wait for the process to complete.
  6. CRITICAL STEP: Select Reboot -> Recovery. You MUST reboot back into recovery so the device can switch to the new active slot.
  7. Only AFTER you have rebooted back into OrangeFox can you flash other ZIPs (Magisk, KernelSU, Custom Kernels). This ensures they are installed to the correct, updated slot.
  8. Now you can safely select Reboot System.

⚠️ BOOTLOOP WARNING: Monolithic Kernels with DTB

If you flash a custom kernel (like SultanSU forks) and get a bootloop, IT IS NOT AN ORANGEFOX BUG.

What is actually happening:
Some unofficial forks of monolithic kernels that ship with a dtb inside use broken AnyKernel installer scripts.

  1. The script rebuilds the boot partition.
  2. It then moves on to rebuild vendor_kernel_boot.
  3. The bug: The script forgets to delete the kernel image from step 1. AnyKernel picks it up again and incorrectly packs vendor_kernel_boot with the kernel + dtb + ramdisk. The image becomes invalid and your phone bootloops.

OrangeFox is simply executing the zip script provided by the kernel developer. Since OrangeFox now fully supports decryption on Pixels, these installer bugs (which were previously hidden) are finally exposed. Official Sultan releases do not have this bug.

The Fix (For Kernel Maintainers & Advanced Users):
You must add rm -f commands between the boot and vendor_kernel_boot steps inside anykernel.sh inside the kernel zip:

# boot image installation
block=boot;
is_slot_device=1;
. tools/ak3-core.sh;
split_boot;
flash_boot;

# ADD THESE TWO LINES TO PREVENT BOOTLOOPS:
rm -f "$AKHOME/Image.lz4";
rm -f "$home/Image.lz4";

# vendor_kernel_boot installation (for dtb)
block=vendor_kernel_boot;
is_slot_device=1;
reset_ak;
split_boot;
flash_boot;

Note: If fork maintainers refuse to fix their installer scripts, a forced compatibility patch will be added to OrangeFox in the future to protect users.

Loading

OrangeFox Recovery - R11.3 RC3

23 Mar 19:48
@leegarchat leegarchat
RC3
cffea70

Choose a tag to compare

View all tags
OrangeFox Recovery - R11.3 RC3
663eb01b-7e99-4e5b-8004-5e45sss29312c6d

Changelog

  • KernelSU/susfs Compatibility: Fixed a critical issue where the device would kernel panic and reboot during the OrangeFox splash screen when using GKI kernels with inline KernelSU (specifically WildKSU/susfs).
  • Core Init: Switched the ln applet implementation in the recovery ramdisk from Toybox to Busybox. This safely bypasses a known null-pointer dereference bug in the KSU bb_inode_rename hook by avoiding the rename() syscall on fast symlinks in tmpfs.

What's Working

  • Core functions: Decryption, MTP, ADB, ADB Sideload, USB OTG, Charging, Screen Brightness, Flashlight.
  • Recovery features: ZIP/IMG Flashing, Partition Backups, Reflash current OrangeFox.
  • Hardware: Touchscreen and Vibration (⚠️ Requires a live system, see below).

IMPORTANT: TOUCHSCREEN & VIBRATION
The touchscreen and haptics (vibration) will only work if you have a functional system in at least one slot. OrangeFox dynamically loads the required touch and haptics kernel modules directly from your device's vendor and vendor_dlkm partitions.

Why? The Pixel vendor_boot partition has a strict 64MB size limit, and the recovery ramdisk requires at least ~10MB of free space just to boot. It is physically impossible to pack these heavy, device-specific modules directly into the recovery image itself without breaking the boot process.

Supported Devices & Downloads

⚠️ READ CAREFULLY: MATCH YOUR DEVICE CODENAME TO THE CORRECT DOWNLOAD FILE!

Download OrangeFox-R11.3-RC3-gs201.img for Tensor G2:

  • Pixel 7 (panther) | Pixel 7 Pro (cheetah) | Pixel 7a (lynx)

Download OrangeFox-R11.3-RC3-zuma.img for Tensor G3:

  • Pixel 8 (shiba) | Pixel 8 Pro (husky) | Pixel 8a (akita)

Download OrangeFox-R11.3-RC3-zumapro.img for Tensor G4:

  • Pixel 9 (tokay) | Pixel 9 Pro (caiman) | Pixel 9 Pro XL (komodo) | Pixel 9a (tegu)

Initial Installation Guide

On Pixel devices, the recovery is located in the vendor_boot partition.

Method 1: Via PC / Fastboot (RECOMMENDED)

  1. Reboot your phone to Bootloader (Fastboot mode).
  2. Connect to your PC and open a terminal.
  3. Flash the image (Fastboot will automatically flash it to your active slot): 
    fastboot flash vendor_boot OrangeFox-R11.3.img
  4. IMMEDIATELY reboot to recovery: 
    fastboot reboot recovery

Method 2: On-Device (Requires Root)

If you already have Magisk/KernelSU, you can flash it directly from your phone using a terminal emulator (like Termux).

  1. Place OrangeFox-R11.3.img in your internal storage (/sdcard/).
  2. Run these commands: 
    su
dd if=/sdcard/OrangeFox-R11.3.img of=/dev/block/by-name/vendor_boot$(getprop ro.boot.slot_suffix)
  3. Check for errors, then reboot to recovery.

Surviving ROM & OTA Updates (DO NOT SKIP)

CRITICAL INFORMATION: Pixel devices use an A/B slot system. When you install an OTA update or flash a custom ROM, the system WILL OVERWRITE the vendor_boot partition with the stock recovery.

To preserve OrangeFox, you MUST follow this exact sequence:

  1. Boot into OrangeFox.
  2. Flash your ROM/Update .zip file.
    (Pro Tip: Check the box to "Automatically reflash recovery after update" during installation. If you do this, skip to Step 5).
  3. DO NOT REBOOT TO SYSTEM YET!
  4. If you didn't check the auto-reflash box, immediately go to Advanced -> Flash current OrangeFox. (This build uses a modified script that reliably flashes the recovery to BOTH slots simultaneously).
  5. Wait for the process to complete.
  6. CRITICAL STEP: Select Reboot -> Recovery. You MUST reboot back into recovery so the device can switch to the new active slot.
  7. Only AFTER you have rebooted back into OrangeFox can you flash other ZIPs (Magisk, KernelSU, Custom Kernels). This ensures they are installed to the correct, updated slot.
  8. Now you can safely select Reboot System.

⚠️ BOOTLOOP WARNING: Monolithic Kernels with DTB

If you flash a custom kernel (like SultanSU forks) and get a bootloop, IT IS NOT AN ORANGEFOX BUG.

What is actually happening:
Some unofficial forks of monolithic kernels that ship with a dtb inside use broken AnyKernel installer scripts.

  1. The script rebuilds the boot partition.
  2. It then moves on to rebuild vendor_kernel_boot.
  3. The bug: The script forgets to delete the kernel image from step 1. AnyKernel picks it up again and incorrectly packs vendor_kernel_boot with the kernel + dtb + ramdisk. The image becomes invalid and your phone bootloops.

OrangeFox is simply executing the zip script provided by the kernel developer. Since OrangeFox now fully supports decryption on Pixels, these installer bugs (which were previously hidden) are finally exposed. Official Sultan releases do not have this bug.

The Fix (For Kernel Maintainers & Advanced Users):
You must add rm -f commands between the boot and vendor_kernel_boot steps inside anykernel.sh inside the kernel zip:

# boot image installation
block=boot;
is_slot_device=1;
. tools/ak3-core.sh;
split_boot;
flash_boot;

# ADD THESE TWO LINES TO PREVENT BOOTLOOPS:
rm -f "$AKHOME/Image.lz4";
rm -f "$home/Image.lz4";

# vendor_kernel_boot installation (for dtb)
block=vendor_kernel_boot;
is_slot_device=1;
reset_ak;
split_boot;
flash_boot;

Note: If fork maintainers refuse to fix their installer scripts, a forced compatibility patch will be added to OrangeFox in the future to protect users.

Loading

OrangeFox Recovery - R11.3 RC2

22 Mar 12:29
@leegarchat leegarchat
RC2
5ccc1f1

Choose a tag to compare

View all tags
OrangeFox Recovery - R11.3 RC2
663eb01b-7e99-4e5b-8004-5e45sss29312c6d

Changelog

  • Decryption: Fixed a bug where data decryption would sometimes fail.
  • USB OTG: Fixed an issue where USB OTG would not work until an ADB cable was plugged into the device.
  • USB Mode Auto-Switching: Added a background tracker service that automatically switches the device to host/OTG mode. You no longer need to manually disable MTP to use OTG.
  • Flashlight: Fixed flashlight functionality for all supported devices.
  • CPU Temperature: Fixed CPU temperature display for all supported devices.
  • Backups: Added all available device partitions to the backup options.
  • Backups: Added a separate backup option specifically for Internal Storage (photos, downloads, media, etc.).
  • Magisk: Updated the built-in Magisk to v30.7.
  • Boot system: Possibly fixed booting into the system if it has erofs partitions. Should work, but not confirmed by the tester.
  • Fox Addons: Fixed the missing Magisk installer in the Advanced -> Fox Addons menu.

What's Working

  • Core functions: Decryption, MTP, ADB, ADB Sideload, USB OTG, Charging, Screen Brightness, Flashlight.
  • Recovery features: ZIP/IMG Flashing, Partition Backups, Reflash current OrangeFox.
  • Hardware: Touchscreen and Vibration (⚠️ Requires a live system, see below).

IMPORTANT: TOUCHSCREEN & VIBRATION
The touchscreen and haptics (vibration) will only work if you have a functional system in at least one slot. OrangeFox dynamically loads the required touch and haptics kernel modules directly from your device's vendor and vendor_dlkm partitions.

Why? The Pixel vendor_boot partition has a strict 64MB size limit, and the recovery ramdisk requires at least ~10MB of free space just to boot. It is physically impossible to pack these heavy, device-specific modules directly into the recovery image itself without breaking the boot process.

Supported Devices & Downloads

⚠️ READ CAREFULLY: MATCH YOUR DEVICE CODENAME TO THE CORRECT DOWNLOAD FILE!

Download OrangeFox-R11.3-RC2-gs201.img for Tensor G2:

  • Pixel 7 (panther) | Pixel 7 Pro (cheetah) | Pixel 7a (lynx)

Download OrangeFox-R11.3-RC2-zuma.img for Tensor G3:

  • Pixel 8 (shiba) | Pixel 8 Pro (husky) | Pixel 8a (akita)

Download OrangeFox-R11.3-RC2-zumapro.img for Tensor G4:

  • Pixel 9 (tokay) | Pixel 9 Pro (caiman) | Pixel 9 Pro XL (komodo) | Pixel 9a (tegu)

Initial Installation Guide

On Pixel devices, the recovery is located in the vendor_boot partition.

Method 1: Via PC / Fastboot (RECOMMENDED)

  1. Reboot your phone to Bootloader (Fastboot mode).
  2. Connect to your PC and open a terminal.
  3. Flash the image (Fastboot will automatically flash it to your active slot): 
    fastboot flash vendor_boot OrangeFox-R11.3.img
  4. IMMEDIATELY reboot to recovery: 
    fastboot reboot recovery

Method 2: On-Device (Requires Root)

If you already have Magisk/KernelSU, you can flash it directly from your phone using a terminal emulator (like Termux).

  1. Place OrangeFox-R11.3.img in your internal storage (/sdcard/).
  2. Run these commands: 
    su
dd if=/sdcard/OrangeFox-R11.3.img of=/dev/block/by-name/vendor_boot$(getprop ro.boot.slot_suffix)
  3. Check for errors, then reboot to recovery.

Surviving ROM & OTA Updates (DO NOT SKIP)

CRITICAL INFORMATION: Pixel devices use an A/B slot system. When you install an OTA update or flash a custom ROM, the system WILL OVERWRITE the vendor_boot partition with the stock recovery.

To preserve OrangeFox, you MUST follow this exact sequence:

  1. Boot into OrangeFox.
  2. Flash your ROM/Update .zip file.
    (Pro Tip: Check the box to "Automatically reflash recovery after update" during installation. If you do this, skip to Step 5).
  3. DO NOT REBOOT TO SYSTEM YET!
  4. If you didn't check the auto-reflash box, immediately go to Advanced -> Flash current OrangeFox. (This build uses a modified script that reliably flashes the recovery to BOTH slots simultaneously).
  5. Wait for the process to complete.
  6. CRITICAL STEP: Select Reboot -> Recovery. You MUST reboot back into recovery so the device can switch to the new active slot.
  7. Only AFTER you have rebooted back into OrangeFox can you flash other ZIPs (Magisk, KernelSU, Custom Kernels). This ensures they are installed to the correct, updated slot.
  8. Now you can safely select Reboot System.

⚠️ BOOTLOOP WARNING: Monolithic Kernels with DTB

If you flash a custom kernel (like SultanSU forks) and get a bootloop, IT IS NOT AN ORANGEFOX BUG.

What is actually happening:
Some unofficial forks of monolithic kernels that ship with a dtb inside use broken AnyKernel installer scripts.

  1. The script rebuilds the boot partition.
  2. It then moves on to rebuild vendor_kernel_boot.
  3. The bug: The script forgets to delete the kernel image from step 1. AnyKernel picks it up again and incorrectly packs vendor_kernel_boot with the kernel + dtb + ramdisk. The image becomes invalid and your phone bootloops.

OrangeFox is simply executing the zip script provided by the kernel developer. Since OrangeFox now fully supports decryption on Pixels, these installer bugs (which were previously hidden) are finally exposed. Official Sultan releases do not have this bug.

The Fix (For Kernel Maintainers & Advanced Users):
You must add rm -f commands between the boot and vendor_kernel_boot steps inside anykernel.sh inside the kernel zip:

# boot image installation
block=boot;
is_slot_device=1;
. tools/ak3-core.sh;
split_boot;
flash_boot;

# ADD THESE TWO LINES TO PREVENT BOOTLOOPS:
rm -f "$AKHOME/Image.lz4";
rm -f "$home/Image.lz4";

# vendor_kernel_boot installation (for dtb)
block=vendor_kernel_boot;
is_slot_device=1;
reset_ak;
split_boot;
flash_boot;

Note: If fork maintainers refuse to fix their installer scripts, a forced compatibility patch will be added to OrangeFox in the future to protect users.

Loading