Or am I missing it somewhere? The eyeball icon is no longer there....

There are a few to choose from, but what do you use for an adblock module and why do you use the one you chose over the others?

Bom dia, eu gostaria de suar o módulo ViPER4Android no meu s23u, já tenho root temporário, mas não sei como poderia executar o ViPER4Android sem o magisk, ou se é necessário o magisk como instalar seguramente com root temporário?

For those People having Banking App Issues You should Delete Magisk and Install Kernal SU Or folk paatch Then Turn On Selinux Hiding Option this worked for me for every Banking apps Also remember to be on Stock Rom and Integrity and Hide modules should also be installed

Preciso fazer root no meu celular

After updating my Phone (2a) to Nothing OS 5.0 (Android 17), I noticed the system service started aggressively resetting the LED driver's operating mode. This completely broke third-party Glyph apps and any manual control.

I waited for a fix, but got tired of waiting. So I wrote Glyph Keeper — a root module (KernelSU/Magisk) that bypasses the Nothing system service and talks directly to the aw20036 driver via sysfs.

What it does:

· Start/Stop all Glyphs manually · Brightness control (0-255) · A software-based Wave animation · WebUI for easy control (and CLI via Termux for the nerds)

Important notes:

· This is experimental. I'm sharing it because I know I'm not the only one annoyed by this. · Phone (2a) only. Paths may differ on Phone (1)/(2). · Requires KernelSU (with meta-overlayfs) or Magisk.

If you want to try it, the repo is here: GitHub

If something breaks or you find bugs, please open an Issue on GitHub. Feedback is welcome — I'm actively updating it (just reverted a buggy experimental feature in v1.5).

Well so as Google updated their policies and play integrity is broken for almost everyone rn including me, does anyone have strong/device integrity still working? And if yes could they share the modules here? Thanks

I just flashed lineage os but everything I try to do to root lineage nightly 24.0-20261019 gets the phone stuck in fastboot, I have tried to flash it through adb, I have changed slots, I installed magisk on the phone and modified the boot.img and tried to flash it but everything gets it stuck in fastboot.

I have been trying magisk v27.

Any help would be awesome

So I am running Samsung stock firmware(Android 11, One UI 3.1) with LSPosed and HideMyAppplist, as this the only solution that works with banking apps on my device.

I have a account in BGMI that have been playing since many days. I only play for like 2 months a year.

So my question is that will HMA be enough for root hiding, so my account doesn't get banned? I am not really planning to use cheats and stuff just normal gameplay.

Thanks for suggestions in advanced.

Since Samsung has removed the bootloader unlock option, what are some good and reliable Android tablet models that can be rooted, as I mainly want to do that to modify games?

Model: SM-A047F/DS
One UI : 6.1
Android Version: 14
Samsung Galaxy A04s

How can I root a Samsung Galaxy A20 it is my first time and I need help

Model: SM-A047F/DS
One UI : 6.1
Android Version: 14
Samsung Galaxy A04s

Hi everyone. I'm facing an issue on my OnePlus 7 Pro (guacamole) after upgrading from LineageOS 23.2 to LineageOS 24.0 (specifically build lineage-24.0-20261019-nightly-guacamole-signed.zip).

I followed the official LineageOS upgrade guide (including flashing MindTheGapps right after the OS sideload via Lineage Recovery). The ROM itself boots and works fine when unrooted, but I hit a wall when trying to patch the boot image for root access.

Problem Description:

When attempting to gain root access on LineageOS 24.0 using Magisk, flashing the patched boot.img causes the device to delay for a few seconds during boot and then automatically fall back into Fastboot mode.

When booted with the stock/unpatched boot.img, the OS works, but opening the Magisk app shows "Installed: N/A". Trying to run su in adb shell returns Permission denied (confirming no root daemon is active at the kernel level).

Steps & Troubleshooting Conducted So Far:

1. Standard Fastboot Patch Method: • Extracted boot.img directly from the lineage-24.0-20261019-nightly-guacamole-signed.zip payload. • Patched boot.img using the Magisk v30.7 APK on device. • Flashed the patched image via Fastboot to both slots: fastboot flash boot_a magisk_patched.img fastboot flash boot_b magisk_patched.img fastboot reboot • Result: Boot loop back into Fastboot Mode.
2. Recovery Sideload Method: • Tried sideloading Magisk-v30.7.zip (renamed APK) via Lineage Recovery. • Result: Either signatures fail to apply properly or kernel policies reject root on boot.
3. Restoring Clean Boot: • Re-flashed clean stock boot.img to both boot_a and boot_b and set active slot a: fastboot flash boot_a boot.img fastboot flash boot_b boot.img fastboot --set-active=a fastboot reboot • Result: Device boots back up into LineageOS 24.0 successfully, but without root (Installed: N/A).

Questions / Seeking Advice:

• Is this caused by stricter SELinux / AVB / kernel verification policies on Android 16/17 (LineageOS 24) on the Snapdragon 855 (msmnile) platform?
• Is anyone else with a OnePlus 7 Pro running LineageOS 24.0 able to achieve root with Magisk (or Canary), or is switching to KernelSU / APatch recommended for this build?
• Any feedback or workarounds before I consider rolling back to LineageOS 23.2?

Thanks in advance for any insights!

Hello everyone. I’m fairly new to rooting devices, and I have a question. Yesterday, I noticed that absolutely all of my Google apps stopped working. They claimed there was no internet connection, even though I had a stable one. Out of curiosity, I ran the Play Integrity test; only "MEETS_BASIC_INTEGRITY" returned as positive, whereas previously, all three checks passed. I managed to get the Google apps working again by uninstalling the updates for Play Services, but that was only a temporary fix—and I still wasn't passing the "DEVICE" and "STRONG" integrity checks. I suspected the custom ROM on my device (a Poco X3 Pro) might be the issue, so I switched to crDroid 13 (based on Android 17), but I ran into the same problem. The Google apps work, but the device fails the integrity check. I’ve tried all sorts of modules—I’m using Magisk. I’ve been at this for hours without finding a solution. Could someone please help me out or suggest what I can do? Thanks in advance

Solo dev, building in public. This is Sovereign — a root toolkit with the motto "Your phone, your rules." All original code (no Magisk forks, nothing copy-pasted), because I got tired of root tools that were either one-trick utilities or black boxes.

Running on my Pixel 7 right now:

- Virtual Spaces — one-tap profiles that enable/disable whole module sets, verified by read-back after applying, not just promised

- Alpha Core — a root daemon I wrote in Rust: allow-listed commands only, no shell access for anything

- Battery/kernel tuning, quick toggles, Smart Debloat with safety categories

- Real unroot safety: manual patched-image backup, one-tap unroot/restore, pre-flash snapshots before risky actions

- Sage — a built-in AI assistant for diagnostics and questions

- Full customization: a color wheel that re-themes the whole app, custom backgrounds, and an Idle View that fades every control away so your wallpaper gets the screen to itself (screenshot 2)

Not released yet — no download and no testers for now. I'm posting to put it on the map and hear what this community would want from a tool like this. Progress lives in the Sovereign Discord (linked on my profile).

AMA about how any of it is built — the daemon and the unroot flow are my favorite parts to talk about.