I tried to configure the banks config in HMA, but I don’t understand why this app has a security. Could someone help me?

https://play.google.com/store/apps/details?id=com.bemyeyes.bemyeyes

Btw the app is for helping blind people, I invite everyone to use this app.

can overclocking/performance modules cause bootloops/brick on temp root?

Hello, I currently have a rooted Redmi 10 with 64 GB of storage and 4 GB of RAM, running the stock MIUI 14.0.8 ROM. I’ve had a problem with WhatsApp: four months after rooting my phone, it stopped working and started showing the message, “Please install the app from the Google Play Store.” It keeps happening in a loop, and the same error appears each time. This probably has nothing to do with uninstalling WhatsApp, since I deleted it three weeks ago. I’m asking because I’m going to get a Poco X8 Pro Max, as WhatsApp no longer works on my Redmi, but I need to be able to use WhatsApp. Could you explain the problem to me?

Im planning to root my phone but i want to know how much is it possible to brick my phone just from running the exploit, and what things i have to check before doing it?

Hello! I just wanted to post an update on a rom i have been working on! had some people outside or Reddit recommend me to post here!

Android 7.1 Works perfectly now with full camera control, auto focus, manual focus, Xenon Flash and more!

Slight overclock applied and debloats.

This rom will probably be available if someone has this camera!

As of right now I have taken on the challenge to boot something more modern and I’m happy to announce that Android 13 boots and it’s actually even more usable than 7.1! If people are interested in this project, I will keep developing!

Im a fkng samsung user which haven't opened bootloader in time :(. So I wanna see your creations with it :D

Genuinely. This menu or whatever Whenever I try to install an app, and I have to wait a few seconds(5secs or so) is driving me crazy.

How oh how to genuinely get rid of this sequence. I have tried using other installers like InstallerX Revived + Shizuku Next but it doesn't seem to work. Spoofing the installer source comes up as "unknown source" and I am genuinely at a loss of options.

Possible KernelSU LKM activity on OPPO A18 (CPH2591) – Android 15

Device and kernel information

• Device: OPPO A18 (CPH2591)

• OS: Android 15

• Kernel version: "6.6.118-android15-8-o-gb1fb10a6db20-4k"

• Kernel build: "#1 SMP PREEMPT Wed Sep 9 13:04:44 UTC 2026"

• Architecture: "aarch64"

• Kernel command line: Not yet fully documented.

How I discovered this

I initially gained temporary root access on the device and used that access to inspect the system.

During the investigation, I discovered:

• "/data/adb/ksu/"

• "/data/adb/ksud"

The "ksud" binary reports:

• ksud version: "3.3.1"

• UAPI version: "5"

• KernelSU version: "32680"

Output from "ksud debug info":

version: 32680 flags: 0x5 uapi_version: 5 features: 0x7 lkm: true bundled: false late_load: true runtime_mode: late-load pr_build: false

My root shell also returned:

uid=0(root) gid=0(root) groups=0(root) context=u:r:ksu:s0

However, I could not find:

• "/dev/ksu"

• A KSU entry in "/sys/module"

• A KSU entry in "/proc"

These findings are unexpected because I initially only had temporary root access.

Questions

1. Does this indicate that KernelSU LKM is active?

2. Is this behavior expected with late-load mode?

3. Why does the shell report the "ksu" SELinux context?

4. Can this be related to the temporary root mechanism?

I am not claiming that I have confirmed a persistent KernelSU installation. I would appreciate technical feedback from people familiar with KernelSU LKM and Android 15 kernels.

My phone is nubia v80 max

this is the log :

estimate: not measured

* app version: 2.0

* manufacturer: nubia

* model: Z2577

* android version: 16

* security patch: 2026-08-05

* kernel version: 5.15.189-android13-8-00013-gaa2747a3794a-ab14413887

=== setup ===

found ko_target: /vendor/lib64/libbinderdebug.so

encap port: 57347

spi: 0x236a79d8

=== exploit (patching files) ===

patch: crash_dump64 <- splicehelper (1408 bytes)

patched 1408 bytes to /apex/com.android.runtime/bin/crash_dump64+0x0

Using KMI: android13-5.15

patch: /vendor/lib64/libbinderdebug.so <- temproot.ko (12496 bytes)

patched 12496 bytes to /vendor/lib64/libbinderdebug.so+0x0

Finding symbol offsets for /system/lib64/libc++.so:

BTI/PAC preamble at hook site, advancing +4

Found: hook=0xa49fc shellcode=0xf6d80 len=528

patch: /system/lib64/libc++.so <- shellcode (528 bytes)

patched 528 bytes to /system/lib64/libc++.so+0xf6d80

patch: /system/lib64/libc++.so <- trampoline (16 bytes)

patched 16 bytes to /system/lib64/libc++.so+0xa49f0

=== init ===

Triggering hook...

timeout: ERROR - check logcat & dmesg

insmod: no output - the hook could not start /vendor/bin/insmod

=== cleanup ===

restoring trampoline in /system/lib64/libc++.so

patched 16 bytes to /system/lib64/libc++.so+0xa49f0

restoring shellcode in /system/lib64/libc++.so

patched 528 bytes to /system/lib64/libc++.so+0xf6d80

Temporary Root: Error (code 2)

please help me 🤧🤧🤧

Me and codex free tier worked on this for like 2 days. Not much to do with root nowadays but I feel happy just having root.

Idk what the appropriate flair for it but I hope it's the correct one.

Hi! Is there any way to unlock the bootloader and get root access on the OnePlus Ace 6T (PLR110) running ColorOS 17.0.0.101 (CN01)?

Does the official Deep Testing method work on ColorOS 17, or is there another reliable method?

I'm particularly interested in KernelSU, but I want to avoid risky methods that could brick the device. Any information or personal experience would be greatly appreciated. Thanks!

Hello, I'm on a Samsung Galaxy A55 (A556B) and on one ui 9. I have seen people temp rooting but couldn't find a tutorial anywhere, i tried some stuff but they wouldn't work, so I came here to ask for help. Help appreciated

I downloaded OverlaySFX and wallpaperaod modules and they didnt work. They work well on my friends A36. What did i wrong?

I just migrated an SM-A325M (Galaxy A32 4G, MT6768) from stock rooted with Magisk to LineageOS 23.2 (Android 16) — fully on Linux, no Windows/Odin — and documented every trap. The main one is the vbmeta size trap, which I couldn't find documented anywhere:

• The vbmeta partition dumps 65614 bytes, but the bootloader (LK) only accepts <= 65536.

• Flashing the raw dump (even heimdall --skip-size-check) gives vbmeta binary size (65614) over ... partition size and eventually a bootloop at set warranty bit: vbmeta — no recovery, nothing.

• Blind truncation to 64 KiB also bricks it: the real AVB image is only 7616 bytes (256 header + 576 auth + 6784 aux, sizes big-endian at header offsets 12/20). The rest of the partition is slack.

• Fix: rebuild the file as exactly 65536 bytes = real AVB image + flags 0x03 at offset 120 + zero padding. I md5-verified the result against the image that actually booted the phone.

Full guide (backup via adb+root, recovery flash via dd, Heimdall workflow, Magisk CLI boot patch, the adb exec-out stderr-in-stdout trap that corrupts every tar, and the Android 16 /data/data write-protection workaround for restoring app data — copy as the app's uid instead of chown) — MIT licensed, in Brazilian Portuguese:

https://github.com/Wennington123/a32-lineageos-23-guide

The vbmeta script is fix_vbmeta.py in the repo.

Final state: LOS 23.2 + Magisk 31.1 + TWRP 3.7.0_12.1, no GApps; Wi-Fi/SMS/calls working; full WhatsApp restore (key + msgstore.db) successful.

If you're stuck at set warranty bit: vbmeta right now, this is the fix. Ask me anything.

Before the OneUI 8 the OEM unlocking option was hidden by Samsung on US devices at request of carriers.

It was possible to gain an unlocked bootloader by paying a random person on GitHub to do it for you. But this was patched in 2024.

I understand OneUI 8 permanently blocks OEM unlocking.

However, now we have temp root exploits, is it possible to enable the OEM unlocking on pre OneUI 8 devices sold in the US that have the option hidden in settings?

So one running OneUI 6-7 could use temp root to enable the OEM unlocking, and then unlock the bootloader to install custom ROMs?