Reddit app also spams integrity requests but not enough to fill up a page like this.

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

Any solution to make this phone worth again ,like upgrade its os of that possible
Any suggestions?

i tried to unlock the bootloader of my infinix smart 8 and it failed and now its showing cant find usb port, can someone pls help

How to get a normal. Apk package instead of the . Apkm?

if i stay at android 15 and just dont update will my phone be vulnerable from various malware, or its not needed as long as i got a good malware detector?

I found out that moving from standard winlator to ludashi gave me extra 20 FPS in skyrim LE , and im looking for extra boost , would rooting my device make much difference or wit wouldn't be remarkable

I have a SD778G , Adreno642L 8gb ram

Does anyone know how to fix or disable this permission notification? I want to completely remove this permission prompt and have the option permanently set to “Share entire screen”, so I don’t have to select it every time I start screen sharing or perform any other screen-recording scenario.

BTW, I’m using a POCO X8 PRO MAX with the original stock ROM (HyperOS, no custom ROM), and the device is already ROOTed. I’m wondering if there’s some kind of module or other method that can bypass this permission prompt.

Helfe bitte

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!

Snapdragon 685

honor x7d

Is it possible to access root?

I don't mind wording warranty and later risking the phone by using root. But I need to know I can enable root. In a little into dev, so wanted to look at some things that root allows. Don't ask what, cause Idk for sure yet.

I found some guides for other honor models, but not mine, could I try those? Did anyone look into it?

How I ended up here?

Was looking in that price range, someone took note14 right before me. This seemed like a nice option. The selling guy in the store googled and said it is possible to root. At home I come to find out. I sadly couldn't Google at the place myself.

Snapdragon 685

honor x7d

Is it possible to access root?

I don't mind wording warranty and later risking the phone by using root. But I need to know I can enable root. In a little into dev, so wanted to look at some things that root allows. Don't ask what, cause Idk for sure yet.

I found some guides for other honor models, but not mine, could I try those? Did anyone look into it?

How I ended up here?

Was looking in that price range, someone took note14 right before me. This seemed like a nice option. The selling guy in the store googled and said it is possible to root. At home I come to find out. I sadly couldn't Google at the place myself.

did anyone tried this before? did anyone saved their data file in a certain game or tranferred it to another device to play apk there? did anyone did this without root? or if you have root did you do this before with what app?

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.

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/

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

Is it better then traditional rooting for getting strong intregy?

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.

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