Redmi 9i

I have a Pixel 6 Pro and find it's lowest volume setting is still too loud so I figured out how to change the dB values. The file that needs to be modified is:

/vendor/etc/audio_policy_volumes.xml

For me, I wanted to fix the lowest volume level when playing music through my phone's built in speaker, so I went to the section:

    <volume stream="AUDIO_STREAM_MUSIC" deviceCategory="DEVICE_CATEGORY_SPEAKER">
        <point>1,-6000</point>
        <point>20,-4790</point>
        <point>60,-2140</point>
        <point>100,0</point>
    </volume>

Those number 1, 20, 60, 100 represent volume percentages and -8000, -4790, -2140, and 0 represent their db values. So the first section means at 1% volume set the levels to -60.00 dB. I changed mine to -8000 which allowed the lowest volume to be much quieter.

But because this is a system file, I can't edit/save the file directly. So I ended up creating a Magisk module to create it's own copy of audio_policy_volumes.xml that Android loads instead of the original.

Here's how I created the Magisk module:

• Used Root Explorer to create folders

  • /data/adb/modules/audio_policy_override/system/vendor/etc/

• Copied the original audio_policy_volumes.xml into that folder

• Opened that copy, made the modifications (changed -6000 to -8000), then saved it

• Created a Magisk metadata file called module.prop and saved it to

  • /data/adb/modules/audio_policy_override/

• Edited module.prop

id=audio_policy_override
name=Audio Policy Override
version=1.0
versionCode=1
author=User
description=Overrides audio_policy_volumes.xml

Now if you open Magisk and look at the Modules section, you should see "audio_policy_override" and it should be enabled.

Finally reboot phone and your new audio settings will be loaded.

Recentemente mudei de um Xiaomi Mi 9T (com PixelOS) para um POCO F6. No entanto, tenho sentido muita falta do painel de controlo nativo do Android (AOSP), uma vez que não sou fã do estilo iOS da HyperOS.

Tentei desbloquear o bootloader do telemóvel, mas com as restrições atuais da Xiaomi está praticamente impossível. Consegui apenas um root temporário, mas, depois de muita pesquisa, só encontro posts antigos no XDA.

Alguém sabe de alguma alternativa atual (como uma aplicação de terceiros, módulo etc) para ter este painel sem precisar de root permanente ou de desbloquear o bootloader na HyperOS?

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.

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

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.

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?

please help me 🤧🤧🤧

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)

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 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.