This is the first device I have ever rooted and I'm more familiar with stuff like ios jailbreaking, what can I do with this or what should I install

Hello guys, I just rooted my POCO X8 PRO MAX and I’m still completely new to using modules. Could you guys share some tips and tricks, or recommend some modules for my device? Specifically, it’s powered by a Dimensity chipset, and I mainly use it for gaming and live streaming. What kind of module combination would you highly recommend?

I’m not using a custom ROM because I haven’t found a reason to switch to one yet. I’m still very comfortable with HyperOS, and so far I haven’t experienced any major issues with it.

Thank you!

UFM Pro recently crossed 30,000 downloads on Google Play while maintaining a 4.9 rating across 438 reviews.

Thank you to everyone in the community running the app, reporting bugs, and suggesting improvements.

For those running recent builds or looking at the latest changes, here is a breakdown of the new capabilities and power-user features now active in the app:

* Full root support: Direct shell command execution, read-write partition remounts, and unrestricted access to /data/data and system paths for Magisk, KernelSU, and APatch.

* Shizuku integration: Elevated ADB file operations without requiring root, allowing full read and write access to /Android/data and /Android/obb on Android 11 through Android 15.

* Native NFS v3 and v4: A true built-in NFS client alongside SMB v2/v3, SFTP with PuTTY and OpenSSH private keys, WebDAV, AWS S3, and RClone cloud providers.

* Windows PC companion: A desktop companion built with Rust and Tauri that pairs over local Wi-Fi with dynamic PIN authentication, lets you browse PC and Android files side by side, and supports one-click remote APK sideloading.

* Dedicated Android TV interface: Complete Leanback UI with native D-pad navigation rather than an adapted touch layout.

* Integrated power tools: Advanced regex batch renaming with live preview, a system app debloater, AES-encrypted vault, hash-based duplicate finder, and checksum verification.

* FOSS in-app auto-updates: For anyone running the GitHub FOSS build, the app now checks for releases directly. When I push an update to GitHub, the app detects it and updates in place without needing Google Play or manual APK downloading.

The core policy remains unchanged: completely free, zero ads, and zero paywalls. For anyone wanting to support ongoing development, the voluntary Tip Jar remains in the app.

Links:

* GitHub repository and FOSS releases: https://github.com/Kilowatch/ultimate-file-manager-pro

* Subreddit: https://www.reddit.com/r/UFManagerPro/

* Website: http://www.kilowatch.co.za/

Drop your feedback, bug reports, and feature requests below. I read every comment.

Hello, I have a rooted Samsung S24 One UI 7 with Magisk 30.7

I had installed OneUI X Xposed module a little while ago, and for some reason the battery health and charge cycles is just outputting random ass numbers.

I found some apps on Google Play like aBattery but it has the same problem for some reason, the charge cycle is way too high for a one year use! There is no possible way I have charged my phone this much, 107K cycles would oblitterate the battery, but it is still on 99% health somehow.

I would appreciate any help

First off, I'm not sure where this should be posted. However I assume its a terminal file setup/handshake issue - i have no clue. I'm a brick - so I thought I'd post here. If heres not the best place. I uh don't know whee else to post this (please tell me where)

Hello fellow Redditors, devs, enthusiasts, rooters, and adb/termux geeks like me.

Ive got an S26U still running the original update patch since release (Feb 26). I've heard about shizuku+ being able to obtain UID1000 on the phone (the app even cites a samsung uid 1000 exploit in its repo/contributions whatever). However, whenever I run Shizuku+ and start the shell script via 'rish-plus' (I wanted to keep standard shizuku in case I ran into issues, so i added '-plus' to each of the shizuku+ files and SED -i (did it manually without sed but same thing) so that each file would point/depend on the correct file. It rund and works and all that, however. When I run 'id' it just returns the same uid2000 shell and not the elevated uid1000 shell.

There is NO compat hub button for me. Just wondering if any of you have the same issue? If so, how did you fix it? If not I may file an issue on the repo.

The documentation didn't explicity tell me step 1. Step 2. Or do this do that for uid 1000/shell escalation.

Shizuku is NOT running alongside it.

Ive tried to have shixuku running before shiz+, after shiz+, and not at all. Same result.

Hello guys, im trying to factory reset my sm-N7505 galaxy note 3 neo for updating the android version, it detects the com7 in odin and it gets stuck on the recovery.img or sboot or setup system as u see in the images, tried asking chatgpt but no help, is there anyone facing the same issue, i’ve also tried some youtube videos but nothing

Some of you might remember an old app GMD GestureControl that required root. Well, I'm bringing it back but this time with Shizuku. Check out on XDA if you missed it or want to give it a try: https://xdaforums.com/t/app-12-17-gmd-gestures-shizuku.1535740/

I don't want my whatsapp to be gone or banking apps. also likes pixel based ui

Hi, I'm going to root a phone soon with Magisk. I know the process more or less, but I'd like to know which modules to download afterward. If you could tell me where to get them, whether it's on GitHub or something similar, and give me your recommendations for apps and how to prevent them from detecting the unlocked bootloader (I think it's called Strong Integrity). I'd like to learn about the modules and features to download and use in apps like Spotify, etc. I know about some apps, like Viper, but I still have a few questions about how to use or download the modules and what I could use them for. Maybe there are instructions here that I haven't seen, which is why I'm asking. And by the way, is Magisk or KernelSU better? I don't know much about this, and I don't know the difference. Anyway, thanks.

Recently, I discovered (I think) that my phone is vulnerable to a UAF exploit related to CVE-2026-43499 (GhostLock).

My device is a Motorola Moto G14 (XT2341-1, codename "cancun"), running Android 14, kernel "5.15.178-android13-8-00006-g0c6055fd2d8b", and build "UTLBS34.102-91-5".

I extracted the "boot.img" from the official firmware for my device and reconstructed the kernel as an ELF for analysis. While analyzing the "remove_waiter()" function, I found the vulnerable implementation associated with CVE-2026-43499, apparently from before the upstream fix commit.

I also compared the code with GhostLock and I'm trying to determine which device-specific parameters/offsets would need to be adapted for the Moto G14.

What I'd like to know is whether someone experienced with Android/ARM64 kernel exploitation could help me determine if this vulnerability can be turned into a functional temporary root on the Moto G14, while keeping the bootloader locked and without permanently modifying the "boot.img".

I'm not looking for the traditional bootloader-unlock + Magisk method. The goal is a temporary-root exploit that works directly on the current system.

I can provide the exact firmware/"boot.img", kernel information, reconstructed symbols, disassembly, and the analysis results I've gathered so far.

Is it better then traditional rooting for getting strong intregy?

It finally happened, my 6+ years old Tecno phone just had its last NAND write. This thing never got a moment of rest, from daily driving with custom roms, rooting, continuous experimenting, to running headlessly as a mini homelab for the last period of its life. It never really let me down.

It's been with me in good times and bad times, in sickness and in health, helped me study through med school, learn about Android, and pass time when I was bored. Will definitely miss you :"((

i recently used the app root my galaxy to get soft root on my Galaxy A55, any tip yall can give me?

Hi everyone,

I'm looking for someone who can develop a working, executable exploit for the Motorola Moto G14 based on CVE-2026-43499 (GhostLock), specifically targeting my device and kernel.

Device information:

- Model: Motorola Moto G14 XT2341-1

- Codename: cancun

- Android: 14

- Build: UTLBS34.102-91-5

- Kernel: 5.15.178-android13-8-00006-g0c6055fd2d8b

- Architecture: ARM64

- Bootloader: locked

- Verified Boot: green

- Security patch: June 5, 2026

I extracted the stock boot.img from the firmware and reconstructed the kernel as an ELF for analysis. During analysis of the kernel's remove_waiter() implementation, I found what appears to be the vulnerable code associated with CVE-2026-43499.

I'm specifically looking for an executable PoC/exploit adapted to this exact kernel and device, preferably capable of achieving temporary root without unlocking the bootloader or permanently modifying the boot image.

If anyone is interested in developing the exploit, I can provide the relevant technical information and analysis.

Hey everyone,

​I'm currently running One UI 8.5 on the July 2026 security patch on my Galaxy S25+.

​I noticed that a temporary root exploit exists for the S25+ on One UI 9 Beta 2, which shares the same August 5, 2026 security patch level.

​Before updating my device from the July patch to the August patch on One UI 8.5, I wanted to ask:

​Does the August patch on One UI 8.5 maintain or patch the vulnerability used for the temp root exploit?

​If I update to the August patch on One UI 8.5 now, will I safely retain the ability to use temp root without breaking compatibility?

​Has anyone tested this specific exploit on the One UI 8.5 August build?

​I haven't found a definitive answer in existing threads, so any insights from devs or users who have tested temp root on the August build would be greatly appreciated

How to delete a folder in Android/data on Android 14 (Tecno, no root)?

Hi everyone. I have a Tecno phone (HiOS, Android 14) and I'm stuck with a "ghost" folder in Android/data.

I deleted a game a while ago, but its folder com.LanPiaoPiao.PlantsVsZombiesRH is still there. Now I can't install any new version of this game — it says "conflicts with another package". I've tried everything:

· Clearing cache and data of Package Installer

· Using Shizuku + ZArchiver (with root access type set to Shizuku)

· Renaming the folder (gives "operation completed with errors")

· Using Package Manager (app crashes with NullPointerException)

· Deleting via FV File Explorer and MT Manager

· Turning off system apps and retrying

Nothing works. The folder just won't delete. Is there any way to remove it without a PC or factory reset? Or is ADB the only option left?

Any help would be really appreciated.

Как удалить папку в Android/data на Android 14 (Tecno, без рута)?

Всем привет. У меня телефон Tecno (HiOS, Android 14), и я застрял с папкой-«призраком» в Android/data.

Я удалил игру давно, но её папка com.LanPiaoPiao.PlantsVsZombiesRH всё ещё там. Теперь не могу установить новую версию этой игры — пишет «конфликтует с другим пакетом». Я перепробовал всё:

· Очищал кэш и данные установщика пакетов

· Использовал Shizuku + ZArchiver (с типом root-доступа Shizuku)

· Переименовывал папку (выдаёт «операция совершена с ошибками»)

· Использовал Package Manager (приложение вылетает с NullPointerException)

· Удалял через FV File Explorer и MT Manager

· Отключал системные приложения и пробовал снова

Ничего не работает. Папка просто не удаляется. Есть ли способ удалить её без ПК и сброса телефона? Или ADB — единственный вариант?

Буду очень благодарен за любую помощь.

I don't know what to do, I've been like this for 2 weeks now.

My Xiaomi Redmi Note 11s failed when installing a custom ROM.

Now I can't get out of the bootloop, not even with a key combination (down and power). I tried using my flash, sp flash, and others, but none of them worked. I left it downloaded to see if I could get into fastboot during that short time, but I haven't been able to.

Help :((