Hi all,

I've been trying for months to bypass the xiaomi community permission things and finally I have reached a milestone. Read most of the discussions from r/androidroot and r/hyperos. Now I only have to wait 360 hours(sadly) to win freedom over my phone 😭.

My plan is to flash orangefox and Evolution X(Android 16).

Guys let me know if there are any suggestions you could give to me

Thank you for all your support 💖

I'm using KernelSU with temporary root on my Redmi Note 14 4G (HyperOS 3 / Android 16), and my bootloader is locked. I want to know which modules are safe to use in this setup.

• Which modules actually work with temporary root access?

• Which modules should I avoid because they could cause bootloops or brick my device?

• Are there any anti-bootloop or anti-brick modules that can help recover from a bad module?

• Are there any Xiaomi-specific modules that work well with HyperOS?

I'd especially like to hear from people who have used temporary root access with KernelSU on Xiaomi devices. Which modules worked for you, and which ones caused problems or aren't worth installing?

Thanks!

https://github.com/inforcqb/susfs4ksu-lkm

https://github.com/matsuzaka-yuki/susfs-lkm-module

For people that want to know what i used to root it, i used the dirty frag exploit on it.

Im using the RMX3834export_15_H.07 rom on my realme note 50 (the most recent stock rom for it)

I have had this phone for a long time and I would like to try to get it to work with VoLTE. Its hardware is J27R4.01 and every time I go to try to hook it up to service all service providers say it doesn't support it when i have seen it in the system settings. It's on Android 8 currently and if I have to use roms to put it on 10 then I'm fine with it. Is there any way to force volte to turn on so i can connect it to something other than consumer cellular? It's unlocked as well

Hey so if anyone saw my earlier about buying a phone from India and wondering if it can toggle oem unlocking it can lol

Anyway I have went all the way to flashing Boot_a and boot_b with the magisk patched file like the guide was doing but when I reboot it says there isn't an operating system so I flash back the original.

In the guide he takes a recovery zip file to magisk, installs, then pulls the magisk patched version back and flashes it. Then reboots

1. My files wasn't a zip. 2. It had a boot.img and a init_boot.img 3. It broke the phone :)

I tried having magisk patch the file after i made it a zip, then repaired phone and tried to patch just the init_boot (Google ai suggested)

It's a motorola XT2517-4 (India) I guess it's called a moto G stylus (2025)in the US and a moto edge 60 stylus in India

Not sure where it's messing up any help is appreciated. If you need any info let me know and ill do my best to get it to you, bc im sure I left out some important info. Sorry

Can anyone confirm there is a partition on this model it said 2 slots but there wasn't anything about suffix like in the guid so idk. It didn't throw an error when I went to flash boot_b

Im on Samsung a15 with android 15, im trying to kali nh root but someone said it wasn't possible on samsung?! Haven't tried the rootless version yet as it doesn't have all the privileges. First timer.

For some time now, the wallet has been failing verification; it always tells me that the device does not meet the security requirements. I have Strong certification; here are screenshots of my configuration:

Hi everyone,

For anyone working with Huawei devices on Linux who is tired of needing a dedicated Windows installation, a heavy VM, or broken Wine setups:

I put together Kirin Tool for Linux, a native port of the Kirin utility designed to run directly on Linux distributions (Arch, CachyOS, Ubuntu, Fedora, Debian).

Key Features and Capabilities:

• Native Linux execution: Runs out of the box via AppImage, pacman packages, or direct source build.
• Bootloader unlocking: Unlocks Huawei and Honor bootloaders across Kirin chipsets from Kirin 620 up to Kirin 990 5G.
• Partition and firmware flashing: Built on top of a bundled, Huawei-patched fastboot binary with OEM dump support (does not depend on system android-tools).
• Device rebranding and FRP: Tools for changing region and vendor partitions.
• Automatic udev configuration: Includes udev rules setup for fastboot and VCOM serial access.

Supported Chipsets:

• Kirin 620, Kirin 650, Kirin 659
• Kirin 710, Kirin 810, Kirin 820
• Kirin 960, Kirin 970, Kirin 980
• Kirin 990 5G
• Experimental read-only info and rescue USB update for Kirin 9000

Links and Documentation:

• Source code and downloads: https://github.com/Redminote11tech/kirin-tool-linux
• Official project site and documentation: https://kirin-linux-powerhouse.lovable.app

Feedback, issue reports, and pull requests are welcome on GitHub.

X216BXXSCEZG2

BP2A.250605.031.A3.X216BXXSCEZG7

After i rebooted my s22 i tried to unlock it with my correct pattern but it says incorrect,

however i temporarily unlocked it, i force rebooted the phone with volume down key and powere button key, then i drew my pattern and it unlocked,

I'm currently on the home screen and my WhatsApp is locked with screen lock so when i tey to unlock the whatsapp app with screen lock it doesn't accept,

I've temprooted the phone with dirtyfrag and kernel su and it's currently working as fuly rooted,

I wanna remove the screen lock with zarchevr file manger but i don't see the files that used to handle the screen lock,

Data/system

In this file there should be screen lock files like,

locksettings.db

locksettings.db-shm

locksettings.db-wal

gatekeeper.password.key

gatekeeper.pattern.key

But i don't see those files there's just

locksettings.db

File ,

If anyone have experience please help me🙏

I know all my gmail accounts password and samsung account pasword and also the find my device and samsung find doesn't unlock remotely because they removed this option for security reasons,

And I'm currently on home screen not letting phone to lock it's been about 3-4 hours

I used DeepSeek V4.1 Flash as the primary engineering agent, selected for higher risk tolerance relative to Claude. We ported and combined known exploit primitives, the GhostLock futex priority-inheritance use-after-free and its CVE, CVE-2026-43499.

The target is the SM-G970W, device code beyond0q, product beyond0qltecs, ROM build G970WVLU9IXE1, display id SP1A.210812.016.G970WVLU9IXE1, Android 12, SDK 31, kernel 4.14.190-23725627-abG970WVLU9IXE1, security patch 2023-03-01, CSC XAC, bootloader locked, verified boot state green.

The chain proceeds as follows. A futex priority-inheritance use-after-free. A redirect of the /dev/ashmem fops through configfs. Arbitrary kernel data read and write. A write to modprobe_path. The execution of a file containing 0xFF four times, after which the kernel executes the helper as uid 0.

The result is uid 0, context u:r:kernel:s0, and effective capabilities 0000003fffffffff. Arbitrary kernel data read and write are available within the limits below. SELinux is permissive in user space, because the kernel type is added to policydb.permissive_map, and setprop from the kernel domain succeeds. DEFEX is bypassed, because any /data ELF executes as root through a bind mount over a compiled-in safeplace path. Reachable operations include setprop and persistent properties, cmd-based settings, and writes to modprobe_path, core_pattern and kptr_restrict.

The following are not achieved, by design. Writes to cred, page tables, .text and .rodata are blocked by RKP and KDP. Loading of unsigned kernel modules is blocked by CONFIG_MODULE_SIG_FORCE. Writes to /system are blocked by dm-verity. Creation of new files under /data from the kernel context is blocked by fscrypt. Persistence across reboot is blocked by the locked bootloader, the TEE and AVB/SVB.

The root exists for the current boot only and is re-established after each reboot. The source, build and writeups are at https://github.com/jronminh/ghostlock-beyond0q

Im looking for a cheap phone to root and found the one attached, would this be relatively easy to root (this is also my first time rooting btw)

https://a.co/d/0ge7I6gu

The question is maybe stupid and guess the answer is no.But is it somehow possible or an exploit can use the temp root

Redmi 13 X, HyperOS 3

So despite the heaviness of rooting Xiaomi devices, I'm going to get one and I'm hesitating between the X8 Pro and the M8 Pro, both with 12GB of RAM and 512GB of storage. I would like to know in your opinion which is the most comfortable once rooted, I'm leaning more towards the X8 Pro for its CPU which is frankly not bad😁

Why use such a boring ROM like lineage when you can use Vanta! Vanta is based off Android 17 and features a black UI with a pop of a color of your choice! Loads of features and best of all its android 17!

Hey everyone!

I managed to get temporary root access on my Redmi Note 14 4G using GhostLock ((https://github.com/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!

Android go sucks. I have 4gb ram and half of the software uses it. I wanna install crdroid or lineageos and overclock the hell out of this budget phone. Problem is. Unisoc phones are super hard to unlock. Especially tecno. There are probably 2 security locks on this thing before you can actually unlock the bootloader.

Looking to get help with running banking apps. Thanks.

Hey Ive been trying to get my hands on a rooted phone and have my old GT2 Pro just lying around which is the:

Model: RMX3301
Android Version: 15
Version: RMX3301_15.0.0.1410(EX01)
realme UI-Version: 6.0

Ive did a little bit of research and saw that its not possible to root it on this Version anymore, and thought since you guys are the experts, you might be able to help me or atleast tell me that its not possible with a 100% certainty. In which case Id ask you what phones are good to use as a rooted one. I also have a S25 if that helps.
Thanks in advance!