ksud: support vendor_boot patching for some odd devices #2650
Conversation
|
For this to work, |
|
For ak3 GKI flashing, this fix is also needed for these devices. Kernel-SU/AnyKernel3#6 |
|
Hold this PR a bit i will work on the pixel vendor_boot too |
|
KernelSU-Next/KernelSU-Next#541 (comment) fully finished and tested |
|
should fix #2325 |
|
@ukriu now pick this commit too KernelSU-Next/KernelSU-Next@b74e953 |
ukriu
force-pushed
the
main
branch
2 times, most recently
from
799a37a to
bcfad42
Compare
|
@5ec1cff could you review it Edit: it's tested on both vendor_boot (Xiaomi & Pixel) |
|
The devices affected by this: (as far as I'm aware of) |
Pixel 7 also iirc |
|
I want to know whether the devices that require patching vendor_boot have init_boot or boot partitions. If they do, do those partitions contain a ramdisk? And if so, does the ramdisk include /init? |
Some devices have ramdisk is at vendor_boot/vendor_ramdisk/init_boot.cpio and some other devices have ramdisk in vendor_ramdisk/ramdisk.cpio |
|
The logic I did is fail proof and is working fine for ksunext tested for a whole month without issues it basically checks for correct ramdisk for all boot partitions |
Oh and no the device that require the vendor_boot patching doesn't have init_boot partition but has boot partition but doesn't contain a ramdisk so patching won't work, but vendor_boot patching works as should |
|
Also do note that the vendor_boot/vendor_ramdisk/ramdisk.cpio requires permission 750 instead of the usual 755 or else the init & kernel driver files won't be copied over since the original files are symlinks |
ukriu
force-pushed
the
main
branch
5 times, most recently
from
07eb80d to
51d00bd
Compare
ukriu
force-pushed
the
main
branch
3 times, most recently
from
dc89bd3 to
4a27d82
Compare
|
Please rebase and run clippy fix |
…ily needed for some pixel devices
Co-authored-by: 5ec1cff <[email protected]>
|
Guys, Can anyone look into it? Has been tested and Flashed in Wild Kernels for multiple releasess. |
* 'main' of https://github.com/tiann/KernelSU: (42 commits) Unmount isolated process which forks from zygote unconditionally (tiann#2747) fix 'for' loop problem (tiann#2745) update resetprop (tiann#2733) Strip JNI debug logs on release build (tiann#2732) manager: Support search module (tiann#2730) manager: Add uninstall 2nd confirm (tiann#2729) manager: Fix some issues (tiann#2725) manager: fix button issues in module cards (tiann#2719) manager: switch ui to miuix design style (tiann#2710) Revert "Handle unmount for isolated process correctly" (tiann#2718) Handle unmount for isolated process correctly (tiann#2696) Reset seccomp filter count when escaping to root (tiann#2708) kernel: selinux: rules: Micro-optimize get_policydb() and fix illegal RCU lock usage in handle_sepolicy() (tiann#2695) Update resetprop from Magisk v30.2 (tiann#2700) ksud: support vendor_boot patching for some odd devices (tiann#2650) ksud: make clippy happy (tiann#2683) feat(ui): improve predictive back animations (tiann#2675) kernel: added new prctl CMD_GET_MANAGER_UID to get the uid of the crowned manager (tiann#2673) kernel: selinux: rules: Fix illegal RCU lock usage in apply_kernelsu_rules() (tiann#2646) manger: fix lkm detection (tiann#2654) ... Conflicts: kernel/core_hook.c kernel/selinux/rules.c kernel/throne_tracker.c Change-Id: Iebf7dd870a7d9e35f4cecbf97fa13eeb174b7b5d
6 participants
This will add support to patch vendor_boot with LKM for devices which have their init ramdisk inside of vendor_boot and not boot/init_boot.