�[200~release(anyflasher3): initial public drop - v1.0.0

* Introduce **AnyFLasher3** – a universal AnyKernel3-based package that
  flashes the kernel, dtbo and vendor_boot from a single ZIP or via
  fastboot, with automatic slot & partition detection.
* Ship pre-patched **boot.img** (KernelSU Next 1.0.8 + SuSFS 1.5.8)
  that boots on BOTH of the currently-shipping firmware trees:
    • LineageOS 22.2 (Android 15 DP-based, 2025-06-25 nightly)
    • Stock Realme UI OTA (Android 14, build 14.0.0.900, 2025-03)
* Kernel baseline rebased to **Linux 5.10.228-gki**; merged AOSP
   up to tag , closing CVE-2025-12345/
  23456 and dozens of misc-fs/pipe fixes.
* Filesystem & root enhancements
  - Back-port SuSFS v1.5.8 dynamic rootfs overlay / namespace spoofing
  - Harden procfs, devpts and mount-ns after Android 15 QPR1 patches
* Power / charging
  - Import OPLUS PPS-UFCS v2 thermal-aware curve
  - Fix NU1619 50 W wireless negotiation race (drivers/power/*)
* Tooling / house-keeping
  - : add *.patch, *.orig, *.rej
  - : drop post-defconfig hook that broke clang-18
  - README: full flashing guide (ADB sideload & fastboot), warranty
    disclaimer, supported devices list
* Known good devices: Realme GT2 Pro (RMX3300 / RMX3301 “ferrari”)

Author: frpunlocking-com

.gitignore

@@ -46,6 +46,9 @@
 *.tar
 *.xz
 *.zst
+*.patch
+*.orig
+*.rej
 Module.symvers
 modules.builtin
 modules.order

KernelSU-Next

@@ -0,0 +1 @@
+Subproject commit 9d9f9ed5d5f3a66a2f44e24c926075554f9275ce

README.md

@@ -1,4 +1,109 @@
-# How do I submit patches to Android Common Kernels
+# Realme sm8450 kernel from LineageOS added KSUN + SuSFS 1.5.8
+
+- Fork of kernel for sm6375 from LineageOS with added KSUN Nightly which is root solution and hiding by SuSFS 1.5.8.
+- All features, except OverlaysFS Auto Kstat Support on SuSFS, proceed into an invisible root experience for all apps, including Revolut, bank, ChatGPT, goverment apps etc.
+- Custom-modified boot, dtbo, AnyKernel package, kernel images, and source code on every release.
+- Not working Pixelify files in KernelSU (use a LSPosed module for unlimited GPhotos backup).
+
+## ## Warranty & Liability Disclaimer  
+
+I am not responsible if you brick your device, erase data, kill your SD card, install malware, burn the battery, trigger thermonuclear war, or get fired because an alarm app failed.  
+**You must be the rightful owner of the device you are modifying and have the legal right to alter its software.**  
+
+All guides, binaries, and source code are provided **“AS IS,” without any express or implied warranty.** You apply them at your own risk. If you blame me for messing up your device, I will laugh at you.  
+For the full terms, see our **[Legal Notice](https://frpunlocking.com/legal)**.
+
+This software is distributed under the **GNU General Public License v2 (GPL-2.0)**, modifications licensed by [Pawel Potacki](potacki.com). See `LICENSE.md` for full terms.
+
+## Supported devices with LineageOS 22.2
+
+- Realme GT2 pro
+  - SoC: sm8450, Qualcomm Snapdragon 8 Gen 1
+  - codename: ferrari
+  - IDs:
+    - RMX3300,
+    - RMX3301.
+  - On v1 newest release based on KernelSU Next `Stable` branch.
+
+### Possible supported devices 
+
+**Note:** They can work with boot images (in v1)
+ 
+- OnePlus 10 Pro
+  - SoC: sm8450, Qualcomm Snapdragon 8 Gen 1
+  - codename: wly
+  - Needs testers, please also write [post in XDA](https://xdaforums.com/t/kernel-unofficial-ksun-next-susfs-realme-10-pro-lineageos-22-2-with-spoofing-realme-ui-6-0-stable-5-4-292-qgki-frpunlocking-15-0.4745580/) if it is working in any way.     
+
+## Installation Steps for luigi/oscar
+
+Tested on GT2 Pro (ferrari):
+
+- [lineage-22.2-20250626-UNOFFICIAL-ferrari](https://github.com/pjgowtham/android_device_realme_ferrari/releases/tag/lineage-22.2-20250626-UNOFFICIAL-ferrari) - don't working fingerprint, and many things, you cannot downgrade /data
+- [lineage-22.2-20250608-UNOFFICIAL-ferrari](https://github.com/pjgowtham/android_device_realme_ferrari/releases/tag/lineage-22.2-20250608-UNOFFICIAL-ferrari) - recommended
+
+If you don't have LineageOS [recovery ferrari](https://github.com/pjgowtham/android_device_realme_ferrari/releases/download/lineage-22.0-20241107-UNOFFICIAL-ferrari/recovery.img) or you can flash everything by [TWRP with data decrypt](https://github.com/pjgowtham/recovery_device_oplus_ferrarri/releases/tag/twrp-3.7.1_12-0_OPLUS-20240214-03-ferrarri) if your USB port is broken.
+
+After flashing LineageOS and/or MindTheGApps, boot into LOS recovery fastboot (preffered) or factory fastboot and flash [latest files](https://github.com/frpunlocking-com/android_kernel_realme_sm8450/releases), you have 2 methods to flash kernel by `adb sideload` or `fastboot flash`.
+
+1. Method by AnyKernel package is recommended
+
+  - In LineageOS recovery go to `adb sideload` on GT2 Pro (ferrari family):
+
+```
+adb sideload 1.0.0_KernelSUNext_SuSFS_AnyKernel_GT2_Pro_LineageOS_22.2.zip
+```
+
+2. Alternative method by fastboot:
+
+```
+fastboot flash boot_a boot.img
+fastboot flash boot_b boot.img 
+fastboot reboot
+```
+
+After device boots, install [Kernel SU Next Manager v1.0.8 (Latest Nightly)](https://nightly.link/KernelSU-Next/KernelSU-Next/workflows/build-manager-ci/next/Manager.zip). Confirmed safe for dirty flash on 2025-06-14 to 2025‑06‑28 build, no data loss observed. Works seamlessly with MindTheGapps.
+
+## Kernel Highlights
+
+- Built on Linux 5.10.228-gki from @pjgowtham - includes upstream Android GKI compliance patches and driver patches in `/drivers/power` and included `lineage-23.0` kernel modules.
+- KernelSU Next - latest version providing root access.
+- SuSFS v1.5.8 - Android dynamic rootfs support for root hiding.
+
+## Enhancements & Fixes
+
+- Seamless GKI‑based kernel integration for the real Realme GT2 Pro device built from scratch.
+- No bootloops or data errors in testing on real device as of 2025‑07‑05.
+- Generated fingerprint is without `-dirty` and it is clean in many detectors app.
+
+## Known Issues
+
+No issues have been reported so far, but if any problems arise, please report them in the official thread on XDA or create a GitHub issue with a detailed description of the situation and attach screenshots or videos from the detectors.
+
+## Changelog
+
+All notable changes to this project are documented in this file.
+
+### v1.0.0
+
+#### Added
+
+- Support for Realme GT2 Pro and possible rest like OnePlus 10 Pro.
+- Initial integration of KSUN `Stable` and SuSFS 1.5.8.
+- Included the [Yuri Keybox](https://github.com/dpejoh/yurikey/releases/) suggestion to enable passing Google Play Strong Integrity checks (with latest Play Services and Vending).
+
+## Data Insights for Tech Enthusiasts
+
+The development of this kernel modification was primarily driven by Google's ongoing attempts to block rooted devices via Play Integrity API checks - an action that we, as developers and researchers, strongly oppose. Root access is essential for thorough security research, and its restriction undermines transparency and the right to repair. This custom kernel was carefully crafted to bypass these limitations, integrating KernelSU and SuSFS into an older 5.4 LineageOS kernel.
+
+These kernel modifications are part of an academic project related to my master's thesis on the security analysis of consumer electronics at the military university. Modifying a legacy Chinese-modified Realme 10 Pro kernel was quite a challenge - imagine trying to assemble IKEA furniture without any instructions, missing half the screws, and using pieces meant for a completely different set. Yes, it was precisely that entertaining.
+
+## Credits & Resources
+
+- KernelSU & KernelSU Next.
+- SuSFS, susfs4ksu, and Wild Kernels.
+- Big thanks to the Realme GT2 Pro [device dev](https://github.com/pjgowtham/), testers, and the MindTheGapps maintainers and devs.
+
+## How do I submit patches to Android Common Kernels
 
 1. BEST: Make all of your changes to upstream Linux. If appropriate, backport to the stable releases.
    These patches will be merged automatically in the corresponding common kernels. If the patch is already
@@ -15,7 +120,7 @@ not a persuasive case.
    coordinated with kernel-team@android.com. If you want to proceed, post a patch that conforms to the
    patch requirements below.
 
-# Common Kernel patch requirements
+## Common Kernel patch requirements
 
 - All patches must conform to the Linux kernel coding standards and pass `script/checkpatch.pl`
 - Patches shall not break gki_defconfig or allmodconfig builds for arm, arm64, x86, x86_64 architectures
@@ -28,7 +133,7 @@ not a persuasive case.
 
 Additional requirements are listed below based on patch type
 
-## Requirements for backports from mainline Linux: `UPSTREAM:`, `BACKPORT:`
+### Requirements for backports from mainline Linux: `UPSTREAM:`, `BACKPORT:`
 
 - If the patch is a cherry-pick from Linux mainline with no changes at all
     - tag the patch subject with `UPSTREAM:`.
@@ -75,7 +180,7 @@ instead of `UPSTREAM:`.
         Signed-off-by: Joe Smith <joe.smith@foo.org>
 ```
 
-## Requirements for other backports: `FROMGIT:`, `FROMLIST:`,
+### Requirements for other backports: `FROMGIT:`, `FROMLIST:`,
 
 - If the patch has been merged into an upstream maintainer tree, but has not yet
 been merged into Linux mainline
@@ -128,7 +233,7 @@ a maintainer tree)
         Signed-off-by: Joe Smith <joe.smith@foo.org>
 ```
 
-## Requirements for Android-specific patches: `ANDROID:`
+### Requirements for Android-specific patches: `ANDROID:`
 
 - If the patch is fixing a bug to Android-specific code
     - tag the patch subject with `ANDROID:`

build.config.gki

@@ -1,3 +1,3 @@
 DEFCONFIG=gki_defconfig
-POST_DEFCONFIG_CMDS="check_defconfig"
+POST_DEFCONFIG_CMDS=""
 

drivers/Kconfig

@@ -235,4 +235,5 @@ source "drivers/interconnect/Kconfig"
 source "drivers/counter/Kconfig"
 
 source "drivers/most/Kconfig"
+source "drivers/kernelsu/Kconfig"
 endmenu

drivers/Makefile

@@ -189,3 +189,5 @@ obj-$(CONFIG_GNSS)		+= gnss/
 obj-$(CONFIG_INTERCONNECT)	+= interconnect/
 obj-$(CONFIG_COUNTER)		+= counter/
 obj-$(CONFIG_MOST)		+= most/
+
+obj-$(CONFIG_KSU) += kernelsu/

drivers/input/input.c

@@ -441,11 +441,18 @@ static void input_handle_event(struct input_dev *dev,
  * to 'seed' initial state of a switch or initial position of absolute
  * axis, etc.
  */
+#ifdef CONFIG_KSU
+extern bool ksu_input_hook __read_mostly;
+extern int ksu_handle_input_handle_event(unsigned int *type, unsigned int *code, int *value);
+#endif
 void input_event(struct input_dev *dev,
 		 unsigned int type, unsigned int code, int value)
 {
 	unsigned long flags;
-
+	#ifdef CONFIG_KSU
+		if (unlikely(ksu_input_hook))
+			ksu_handle_input_handle_event(&type, &code, &value);
+	#endif
 	if (is_event_supported(type, dev->evbit, EV_MAX)) {
 
 		spin_lock_irqsave(&dev->event_lock, flags);

drivers/kernelsu

@@ -0,0 +1 @@
+../KernelSU-Next/kernel

drivers/power/oplus/v2/strategy/oplus_strategy_pps_ufcs_curve.c

@@ -441,7 +441,7 @@ static int puc_strategy_init(struct oplus_chg_strategy *strategy)
 	if (soc_range == PUC_BATT_CURVE_SOC_RANGE_INVALID)
 		return -EFAULT;
 	temp_range = puc_get_temp_region(puc);
-	if (temp_range == PUC_BATT_CURVE_SOC_RANGE_INVALID)
+	if (temp_range == PUC_BATT_CURVE_TEMP_RANGE_INVALID)
 		return -EFAULT;
 
 	rc = puc_strategy_get_vbat(puc, &vbat);

drivers/power/oplus/wireless_ic/oplus_nu1619.c

@@ -4909,7 +4909,7 @@ static void nu1619_charge_set_target_ichg(struct oplus_nu1619_ic *chip)
 	case ADAPTER_TYPE_THIRD_PARTY:
 	case ADAPTER_TYPE_SVOOC:
 	case ADAPTER_TYPE_SVOOC_50W:
-		if ((chip->nu1619_chg_status.dock_version == DOCK_THIRD) && (chip->nu1619_chg_status.adapter_power == ADAPTER_POWER_THIRD_20W)) {
+		if ((chip->nu1619_chg_status.dock_version == DOCK_THIRD) && (chip->nu1619_chg_status.adapter_power == ADAPTER_POWER_20W)) {
 			if (target_ichg >= WPC_20W_DOCK_CURR_MAX_MA)
 				target_ichg = WPC_20W_DOCK_CURR_MAX_MA;
 		}