YuKongA

亲测可用！CVE-2026-43499漏洞确实离谱，已经有大神通过漏洞制作了apk，根据项目说明YuKongA/ghostlock-app 只要内核与列表中的完全一致就可以实现临时root 。 更离谱的是 另外还有有人把 CVE-2026-43499 包成 KSuRoot 4.0.0：122 条厂商载荷、50 档内核基线、免 ADB，还能拿你本机的 boot.img t.co

[SUCCESS] OnePlus 15: TimerRoot + CVE-2026-98260 on ColorOS 17 / Android 17 Successfully tested TimerRoot + CVE-2026-98260 on OnePlus 15 (Android 17 / ColorOS 17) Finally got it working! 🎉 I successfully tested TimerRoot using the CVE-2026-98260 exploit on my OnePlus 15 running Android 17 / ColorOS 17. A little background: My OnePlus 15 was originally running completely stock OxygenOS 16.0.500.10. I had previously relied on GhostLock for temporary root access, but that method was patched in later OxygenOS updates. However, thanks to TimerRoot and CVE-2026-98260, I managed to get root access working again and moving to the newer ColorOS 17 build,. After a few attempts, the exploit successfully loaded KernelSU in jailbreak mode. Device information Device: OnePlus 15 Model: CPH2747 Previous OS: Stock OxygenOS 16.0.500.10 Current OS: ColorOS 17 Android: 17 Build: CPH2747_17.0.0.102 Kernel: 6.12.69-android16-6-g242e1a07f878-ab15865446-4k KernelSU: v3.2.5 (32525-2) ksud: 3.2.5 Results The first attempt failed during page-event detection, but a subsequent attempt succeeded. The logs confirmed: [child] woke uid=0 euid=0 [ksu] start uid=0 selinux=Permissive [ksu] late-load rc=0 KSU_LOADED [+] child exit status=0 KernelSU successfully loaded and its app reported: Jailbreak mode: Working LKM: Working SELinux: Enforcing (as shown in the app after loading) Root shell available Important: This is temporary root. TimerRoot explicitly reports that root access disappears after reboot. It is not a permanent root installation. Projects TimerRoot: kpgc10kai/TimerRoot CVE-2026-98260: YuKongA/CVE-2026-98260 Credits to the developers of TimerRoot and CVE-2026-98260!

@lyrasgrimoire @AbhraMistriCODM Don't go for shady telegram apks, install from the official GitHub YuKongA/ghostlock-app

YuKongA/ghostlock-app これなんだが端末のリストには載ってないのにExploit実行できる

One-click temp root One-click temp root for Xiaomi/Poco/Redmi devices using CVE-2026-43499 exploit Its temp root, no OEM unlock You can remove the root by restarting the device Github link IT IS WORKING ONLY IN SUPPORTED KERNELS

¡ROOT en CUALQUIER ANDROID! Fácil y SIN DESBLOQUEAR el BOOTLOADER 💎 ÚNETE YA A TELEGRAM (GRATIS 🚀 Módulos Magisk 👉 t.me Módulos 2 t.me 👉 👉DFRooT:github.com/diabl0w/DFRoot/releases/tag/v4.6 👉Kernetsu:github.com/tiann/KernelSU/releases 👉KSuRoot:github.com/hmascs/KSuRoot/releases/tag/v4.1.2 👉Dispositivos compatible Samsung:BuSung-dev/Root-My-Galaxy-Payloads 👉Dispositivoscompatible:github.com/YuKongA/ghostlock-app/blob/main/docs/k… #RootAndroid #RootSinBootloader #AndroidRoot #Root2026 #Android #TutorialAndroid #PersonalizacionAndroid #TrucosAndroid #RootSinPC [ar] روت لأي جهاز أندرويد! بطريقة سهلة ودون الحاجة لفتح البوتلودر 💎 صوّت لك على تيليجرام (مجانًا) 🚀 وحدات Magisk 👉 t.me الوحدة 2 t.me 👉 👉DFRoot: github.com/diabl0w/DFRoot/releases/tag/v4.6 👉Kernetsu: github.com/tiann/KernelSU/releases 👉KSuRoot: github.com/hmascs/KSuRoot/releases/tag/v4.1.2 👉الأجهزة المتوافقة: سامسونج: BuSung-dev/Root-My-Galaxy-Payloads 👉متوافق device:github.com/YuKongA/ghostlock-app/blob/main/docs/k… #RootAndroid #RootSinBootloader #AndroidRoot #Root2026 #Android #TutorialAndroid #PersonalizacionAndroid #TrucosAndroid #RootSinPC [en-US] ROOT on ANY ANDROID! Easy and WITHOUT UNLOCKING the BOOTLOADER 💎 VOTE YOU ON TELEGRAM (FREE 🚀 Magisk Modules 👉 t.me Module 2 t.me 👉 👉DFRooT:github.com/diabl0w/DFRoot/releases/tag/v4.6 👉Kernetsu:github.com/tiann/KernelSU/releases 👉KSuRoot:github.com/hmascs/KSuRoot/releases/tag/v4.1.2 👉Compatible devices Samsung:BuSung-dev/Root-My-Galaxy-Payloads 👉Compatible device:github.com/YuKongA/ghostlock-app/blob/main/docs/k… #RootAndroid #RootSinBootloader #AndroidRoot #Root2026 #Android #TutorialAndroid #PersonalizacionAndroid #TrucosAndroid #RootSinPC [pt-BR] ROOT em QUALQUER ANDROID! Fácil e SEM DESBLOQUEAR o BOOTLOADER 💎 VOTE EM VOCÊ NO TELEGRAM (GRÁTIS) 🚀 Módulos Magisk 👉 t.me Módulo 2 t.me 👉 👉DFRoot:github.com/diabl0w/DFRoot/releases/tag/v4.6 👉KernelSU:github.com/tiann/KernelSU/releases 👉KSuRoot:github.com/hmascs/KSuRoot/releases/tag/v4.1.2 👉Dispositivos compatíveis Samsung:BuSung-dev/Root-My-Galaxy-Payloads 👉Compatível dispositivo:github.com/YuKongA/ghostlock-app/blob/main/docs/k… #RootAndroid #RootNoBootloader #RootAndroid #Root2026 #Android #TutorialAndroid #PersonalizaçãoAndroid #TruquesAndroid #RootNoPC

[Discussion] How to Get Root on the Redmi Note 14 4G with a Locked Bootloader Using GhostLock + Shizuku (HyperOS 3 / Android 16) Just to clarify, I'm not offering or promoting any bootloader unlocking service. I'm only sharing my personal experience with my own device and documenting what worked for me. Hey everyone, I wanted to share this guide for anyone with a Redmi Note 14 4G Global who wants to get root access without unlocking the bootloader, using GhostLock, KernelSU, and Shizuku. Before getting started, there's one important warning: having a locked bootloader limits your recovery options if something goes wrong. Although I managed to get root on my Redmi Note 14 4G without any issues, I can't guarantee that the procedure will be equally safe on other devices or firmware versions. Also, once you have root access, modifying partitions, installing modified boot images, or using incompatible modules can cause a bootloop or even leave your phone unusable. Proceed at your own risk, and don't assume you'll be able to recover your device if something goes wrong. My device specifications - Device: Redmi Note 14 4G Global - ROM: HyperOS 3.0.303.0 - Android: 16 - Kernel: "6.12.30-android16-5-g6e872b4863d6-ab13847919-4k" - Bootloader: Locked Do you have a different device? If you have a device other than the Redmi Note 14 4G Global, the procedure is basically the same. However, that doesn't mean it'll work on every device, since compatibility depends on your kernel and whether the vulnerability used by GhostLock is still present. To check whether your kernel is supported, open GhostLock and check the information displayed by the app. You can use it to see whether your kernel is supported before proceeding. Important: Even if GhostLock indicates that your kernel is supported, that doesn't guarantee the entire procedure will work without issues on your device. Be especially careful if your bootloader is locked. What are the benefits of getting root this way? You can access many of the features root provides without having to unlock your bootloader. For example, you can explore system modifications, use tools that require superuser permissions, and experiment with apps such as LSPosed and modules like HyperCeiler, provided they're compatible with your setup. You can also restore features or customizations that you couldn't use before. However, there's one major downside: root access also lets you make modifications that could compromise your phone's functionality. That's why you should be careful about what you install and modify, especially with a locked bootloader. How to get root 1 . Install the required apps You'll need these three apps: - GhostLock: YuKongA/ghostlock-app - KernelSU: github.com/tiann/KernelSU/releases/tag/v3.3.0 - Shizuku-Next: github.com/rushiranpise/Shizuku-Next/releases/tag… I recommend Shizuku-Next because that's what I use, but you're not required to use that particular fork. You can use another compatible version of Shizuku. 2. Grant GhostLock permission to use Shizuku Open Shizuku and look for GhostLock in the list of authorized apps. Grant it permission to use Shizuku. Make sure Shizuku is running and GhostLock has the required permission before continuing. 3. Run GhostLock Open GhostLock and tap Run. You'll see a bunch of log messages showing the exploit's progress. Wait for it to finish and pay attention to the result. In my case, GhostLock finished by indicating that KernelSU was ready and then opened the KernelSU app. 4. Verify that root access works You can use an app such as Root Checker or Termux to verify root access. If you're using Termux, first open KernelSU, go to SuperUser, and grant Termux root permissions. Then open Termux and run "su". In my case, it worked, and I was able to obtain root access. I also verified it using a root checker app. Is root permanent? Root access works until you reboot your phone. After rebooting, you need to run GhostLock again to obtain root access. In other words, you don't need to unlock the bootloader, but root access doesn't survive a reboot, so you have to repeat the procedure. What should you avoid doing? With a locked bootloader, you need to be especially careful about the modifications you make after obtaining root access. - Avoid modifying system partitions or installing modified boot images unless you know exactly what you're doing. - Don't install KernelSU modules without checking their compatibility and reliability. - Don't assume a module is safe just because it works on other devices. - Before making important modifications, research your recovery options in case your phone stops booting. I can't guarantee that you'll be able to recover your device from every possible issue with a locked bootloader, so it's better to be safe than sorry. What are the downsides of this method? The main limitation is that it relies on the vulnerability GhostLock uses to achieve kernel privilege escalation. If Xiaomi patches that vulnerability in an update, the method may stop working. That's why your HyperOS version, Android version, and kernel are important details when checking whether your device is compatible. In my case, I obtained root access on HyperOS 3.0.303.0 and Android 16. I can't guarantee it'll work on later versions, and I wouldn't recommend updating under the assumption that the exploit will continue to work. Has anyone else tried this? I'd like to know if anyone else has managed to obtain root access using GhostLock on a Redmi Note 14 4G or another Xiaomi device with a locked bootloader. I'd also appreciate hearing about your experiences with KernelSU, especially regarding compatible modules and precautions worth taking in this situation. If you've tried this method on a different HyperOS version or kernel, let us know how it went.

Tutorial: Enabling Android Auto on CN Rom devices Hey everyone, 17 Pro Max user here. Managed to get Android Auto working! This method requires root, temporary or not doesn't matter. The main reason Android Auto doesn't work on CN devices is very simple... the app needs to be installed as a system app! If you can't unlock your device's bootloader, like me, check the supported list of firmwares and devices for GhostLock to enable temporary root. If you use GhostLock, it won't break Google Pay, or banking apps, so don't worry. You can do pretty much whatever you'd do on normal root as long as it's systemless. Pros are that if you break something, you can usually fix by rebooting (which closes the root session, which must be enabled each time you turn on the phone), or, in worst cases, HyperOS will automatically repair system files (don't ask me how I know..) Now, onto the steps: 1. Have Root access 2. Download this module: Android Auto for MicroG (don't get fooled by the name!) and install in KSU or ReSukiSu manager, whatever you use. It will ask you if you want to install stubs. Answer yes if you don't have those apps installed and don't plan on installing them, say no if you have them. Then reboot or soft reboot your device depending on your root method. 3. Enable Google Play Store on your device from Mi GetApps if you haven't already (Just search Google Play and install) 4. In Play Store, search Android Auto, and update the app. 5. From Play Store, (or from phone settings), search Android Auto again, and open its settings menu 6. Connect like you'd usually do In my case, I noticed GPS was not working, but maybe it's a me issue. I did this just for fun and don't need Android Auto in my life (I don't even have a car lmfao). Tested on Xiaomi 17 Pro Max with another phone running Open Headunit!

Got temporary root on my Redmi Note 14 4G with GhostLock — what should I avoid? Hey everyone! I managed to get temporary root access on my Redmi Note 14 4G using GhostLock ((YuKongA/ghostlock-app). I installed KernelSU beforehand, ran the exploit, and verified that root access works through both a root checker app and Termux using su. My device is running HyperOS 3.0.303.0 / Android 16, AND MY BOOTLOADER IS LOCKED. Since this is my first time getting root access, I want to be careful not to mess anything up. Are KernelSU modules safe to use with temporary root, or could they cause a bootloop or brick my phone? Are there any types of modules I should completely avoid? Are there any KernelSU options I shouldn't touch, especially anything related to installing or patching boot images? What other things should I avoid doing while I have temporary root? If something goes wrong, what recovery options would I have with a locked bootloader? I'm not looking to modify partitions or risk making my phone unusable. I just want to understand the limitations of temporary root before experimenting with anything. Any advice from people who've used GhostLock on Xiaomi devices would be appreciated. Thanks!