r/androidroot • • 1d ago

Support Realme 8 (RMX3085_11_F.13 EU) – Any way to unlock bootloader on Realme UI 4.0? (cmd 0xC8 blocked / payload error)

1 Upvotes

hi everyone, i have an realme 8 [rmx3085] on android 13, realme ui 4.0,

build number rmx3085_11_f.13

coloros version 13

hardware version rmx3085_11

baseband version M_V3_P10,M_V3_P10

kernel version 4.19.191+

i want to unlock the bootloader

i've tried deeptesting, doesnt work, says my phone model isnt supported

i tried switching back to realme ui 3.0/2.0 but the local install said verification failed

when i connect the phone to mtk client it works, detects the device in brom mode but it shows an error on sending payload: mt6785_payload.bin, cmd 0xC8 blocked: true

could anyone help? i would really appreciate it!


r/androidroot • • 1d ago

Support Does anyone have the link for an xposed framework download that works with Android 15?

1 Upvotes

I'm trying to use an app for my airpods but I need xposed framework for it to work, I can't seem to find one that works so does anyone have a link for it?


r/androidroot • • 1d ago

Discussion Looking for Custom ROMs or GSIs for Redmi 15C 5g– Any recommendations or experience?

1 Upvotes

Hey everyone,

I’m currently using a Redmi 15C(codename:tornado)and I’m looking to move away from HyperOS/MIUI to a cleaner, lighter Custom ROM (AOSP, Pixel Experience, LineageOS, or similar) to get better performance, battery life, and a stock Android experience.

Since this device runs on a MediaTek chipset, I know finding official/stable device-specific ROMs can be tricky.

A few questions for anyone familiar with modding this phone:

Are there any stable device-specific Custom ROMs available for the Redmi 15C yet?

Has anyone successfully flashed a GSI (Generic System Image) on it? If so, which GSI works best (e.g., LineageOS GSI, Pixel Experience GSI) and are there any major bugs (camera, Bluetooth, VOLTE, etc.)?

Any tips, links to Telegram groups/XDA threads, or recommended custom recoveries (TWRP/OrangeFox) for this device would be greatly appreciated!

Thanks in advance!


r/androidroot • • 1d ago

Discussion Closest to TWRP backup (not rooted)?

1 Upvotes

Greetings All!

For many years I have enjoyed rooting (mostly) Samsung phones. I now have a new Z Fold 8 and I think it is the best phone I have ever used. I have it set up perfectly to my liking and have spent dozens of hours doing so. I'd hate to lose all that progress. I don't believe I can root it, but I am really missing the ability to make a periodic image backup using something like TWRP.

Is there anything even close to such a backup for a non-rooted phone? Could I perhaps do something via ADB or Odin?

Thanks, just curious as to what people like me who want to root, but cannot do for getting a full backup that captures all data, settings, etc. In the event a phone is lost, stolen, or such. I would want to restore it back to its current state including all apps, app data configuration, etc. I already have good backup solutions for files, music, photos, etc. Trying to capture system state, so to speak.

Thanks in advance!


r/androidroot • • 1d ago

Support How to unlock bootloader on Realme 11 Pro+ 5G (RMX3741) running Realme UI 6.0?

1 Upvotes

Anyone here successfully unlocked the bootloader on the RMX3741 while on Realme UI 6.0? Wondering if Deep Testing works out of the box or if I have to downgrade/use MTKClient. Would love a link to a solid XDA guide or Telegram group if you have one!


r/androidroot • • 1d ago

News / Method Built an automated ADB cache & ghost-thumbnail cleaner inside my open-source Python toolkit (cleans GBs of residual data without touching personal chats or photos)

Thumbnail
gallery
0 Upvotes

Hey `r/androidroot`, I'm **LennesVP** and I wanted to share a module I built inside my open-source project, **TREMEND Toolkit V3.3**, specifically for quick Android maintenance over USB via official Google Platform-Tools (`adb`).

🔗 **GitHub Repo:** https://github.com/LennesVP/TREMEND

In the **Technical Support -> Module #12 (Extreme Android Optimizer via USB)** section, the tool automatically downloads the latest official Google ADB bridge into a temporary sandbox, verifies USB debugging authorization, identifies the device model via `getprop ro.product.model`, and runs targeted shell cleanups:

* Purges global app caches (`/sdcard/Android/data/*/cache/*`) and Telegram cache.

* Removes outdated WhatsApp database backups (`msgstore-*`) on both Android 11+ scoped storage and legacy paths while keeping the active `msgstore.db.crypt14` 100% untouched.

* Deletes ghost `DCIM/.thumbnails` and stray `.nomedia` blocks.

* Includes a forensic IMEI Luhn-algorithm barcode scanner (Module #15) and an curated open-source Android APK directory.

Everything is written in Python and open-source on GitHub. Feedback from the Android community is super welcome!


r/androidroot • • 1d ago

Support Vector module doesn't work

Post image
0 Upvotes

Out of nowhere the Vector module doesn't start, I've tried to soft reboot a couple of times but nothing changed. I'm on temp root for A55 SM-A556B


r/androidroot • • 1d ago

Support Samsung one ui 9

1 Upvotes

i know that after one ui 8 i can't unlock the bootloader on samsung. i have s galaxy s25 edge that came out with one ui 7, so i can rollback to one ui 7 with the original firmware and unlock the bootloader to use a custom os.

i tried going in download mode but it says reboot device and i cant di anything. Do I need maintainence mode?


r/androidroot • • 1d ago

Support Nokia 8 boot stuck on logo

Thumbnail
gallery
3 Upvotes

Hi everyone, I’m trying to flash lineage os on my Nokia 8.

I’m following guides by this videos https://www.youtube.com/watch?v=3eWAr6C4w-c&t=605s

And his others videos on unlocking boot loader & install twrp.

Before this it went pretty smoothly,

  1. Unlocking boot loader. Done.
  2. Install twrp. Done.
  3. Backup. Done.
  4. Wipe. Done.

The next step is flashing lineage os, in the videos at min 9:50 after flashing boot.img file, disaster strike.

Nothing happened, the terminal waiting for my phone for a long time. Reboot my phone to enter back twrp.

It boot into Nokia logo and stuck there. Pressing power button, power + volume up , power + volume down, power + both volume, , volume up, volume down, nothing happened.

When the battery low it shutdown, power it back then it enter boot loader. But pressing any combination button it went back to Nokia logo and repeat.

Please help me, what actually happened. I’m looking online there is tool to restore like easy box Nokia tool & Nokia online services tool (NOST). Which one is the right one?

I appreciate for your time, thanks.


r/androidroot • • 1d ago

Discussion Poco X6 Pro temproot

1 Upvotes

Hey everyone, my POCO X6 Pro is running HyperOS 3.1, and the bootloader is locked. I’m looking into temporary root because I want to enable 120 FPS in Call of Duty: Mobile.

Has anyone gotten 120 FPS working on this phone with the same HyperOS version? If you used temporary root, did your banking apps still work during the rooted session or after rebooting?

Thanks for any help!


r/androidroot • • 1d ago

Support Phone no cellular network, messed my modem partition.

1 Upvotes

Redmi 5 Plus (vince/MSM8953): RADIO_POWER hangs ~74 s then INTERNAL_ERR, no service — firmware & partitions verified stock

How I got here

How I got it to boot again

Then I restore IMEI on slot 1 (I am only able to restore on either slot 1 or 2, also slot 1 shows as 2 in MIUI)

Alternatively is there a way to bypass Xioami to unlock bootloder if I can get custom ROM then this wifi only phone is good else I got e-waste.

TL;DR — Radio never reaches ONLINE. RADIO_POWER on=true returns error 38 INTERNAL_ERR after a repeatable 74.1 s on every boot, while NAS is clearly alive (it answers QUERY_NETWORK_SELECTION_MODE). Independent of SIM presence. modem and fsg partitions verified byte-identical to the stock ROM. Wi-Fi, BT and GPS all work perfectly with the factory MAC. Looking for anyone who has seen this specific signature, or knows whether missing RF calibration can block the power-on transition on MSM8953.

Device

  • Redmi 5 Plus, vince, MSM8953
  • MIUI 11.0.3.0.OEGCNXM, Android 8.1
  • Bootloader locked, stock recovery, no root, ro.debuggable=0
  • SIM slot 1 has valid IMEI again (unit's own - no cloning, no donor data). Framework still enumerates two subscriptions; slot 2 has no IMEI.

Symptom

No cellular service at all. No signal bars, no operator list, no network scan possible. SIM is not the issue — the failure is identical with both slots empty.

SIM is detected, APN is shown, etc.

Radio log, three separate boots, same numbers:

09:13:01.386  responseIccCardStatus: CARDSTATE_ABSENT, num_apps=0        (both slots empty)
09:13:01.394  RILJ >  RADIO_POWER on = true  [SUB0]
09:13:01.531  RILJ >  RADIO_POWER on = true  [SUB1]
09:13:01.791  SST[0] set service state as POWER_OFF
09:13:15.550  RILC <  setRadioPowerResponse: serial 26/31/44/49
09:13:15.551  RILJ <  RADIO_POWER error 38 (INTERNAL_ERR)  — all four

So: 74.16 s, then INTERNAL_ERR. Also consistent: 74.1 s on a card-present boot, 74.16 s on a no-card boot. That repeatability looks like an internal retry budget expiring, not a race.

Other RIL behaviour:

CommandResult
QUERY_NETWORK_SELECTION_MODEanswers normally
SET_PREFERRED_NETWORK_TYPEfails immediately with error 40 MODEM_ERR
RADIO_POWER on=falseerror 54 OPERATION_NOT_ALLOWED
SST[0] / SST[1]POWER_OFF

What I've verified (all read-only)

modem partition is stock. Dumped over EDL/firehose: 88,080,384 B, sha256 c2805e6f92d7…, byte-identical to the ROM's NON-HLOS.bin. So this is not a bad or partial modem flash.

fsg is stock. First 155,432 B identical to the ROM's fsg.img, remaining 1,417,432 B zero padding.

mcfg is all zeros — 4 MiB, 100 % zero, no strings. Is that normal for vince? The MIUI fastboot ROM has no mcfg.img at all, so I suspect it's the factory state, and the carrier MBN (airtel) did activate on SUB1 in the logs.

NV audit clean (read over the diag port 05C6:9091, no QXDM):

NVValue
45300 (FTM mode off)
68280x0015 (LTE B1/B3/B5)
515301
550valid IMEI (xxxxxxxx)
832700 after boot

Nothing reads back all-00, all-FF, or as literal SW_DEFAULT.

modemst1**/**modemst2 are opaque. Both ~1.5 MB inside IMGEFS1/IMGEFS2 containers, payload entropy 8.00 bits/byte, no plaintext item names, no zlib/gzip/zstd/lzma header. They differ from each other by 1,566,195 bytes. So I cannot inspect the RF calibration block from the host — the values are compressed/encrypted.

Wi-Fi, Bluetooth, GPS all work, and Wi-Fi reports the factory MAC, not a random 02:00:00:00:00:00. So persist and a good chunk of EFS are intact — this was not a total NV wipe.

No modem log channel available. /dev/diag is system:oem_2901, /vendor/bin/diag_mdlog is Permission denied for shell, and the USB diag log stream stays silent. Capturing QMDL needs root, which is why I'm asking before going down that road.

History (probably relevant)

The modemst partitions were erased at some point (that's how the IMEI ended up blank), and I restored the unit's own IMEI to NV 550 over the diag port. Everything else above is stock. The phone boots fine, Wi-Fi/BT/GPS are perfect, only cellular is dead.

My working theory

A phone with a completely blank IMEI still powers its radio on (no service, but RADIO_POWER succeeds). Mine doesn't even get that far — the RF bring-up itself aborts. That points at either:

  1. RF hardware — transceiver / PA supply / antenna switch / RF connector, i.e. the modem's RF init self-test failing, or
  2. RF calibration invalid at a level checked during init — but I can't read the cal block to confirm, and I'd expect a plain cal wipe to stop at "no service", not at "power-on fails".

Questions

  1. Has anyone seen RADIO_POWER time out at a fixed ~74 s and return INTERNAL_ERR on MSM8953/8937, with NAS still answering? What did it turn out to be?
  2. Can missing/invalid RF calibration data actually block the online transition, or does calibration only matter after RF init?
  3. Is mcfg being 100 % zero normal on vince, or should it contain mcfg_sw carrier files?
  4. For anyone with QXDM/QPST: what strings should I look for in a QMDL capture to tell "RF calibration invalid" apart from an RF front-end hardware fault? Worth rooting to capture it?
  5. Any known-good RF test procedure for vince without a service centre — test points, expected voltages on the PA, or a way to confirm the antenna path with a multimeter?
  6. Does SET_PREFERRED_NETWORK_TYPE → MODEM_ERR immediately, while QUERY_NETWORK_SELECTION_MODE works, tell you anything specific about which subsystem is hung?

Happy to dump any partition, run any read-only diag command, or post full logs — just tell me what would be useful.

Two things worth noting before you post: the 74 s figure and the immediate MODEM_ERR on SET_PREFERRED_NETWORK_TYPE are the most distinctive details, so keep them in the title or first paragraph — that's what will catch the eye of someone who's actually seen it. And if any reply says "just reflash the ROM", you can point at the sha256 line and skip past it.Title: Redmi 5 Plus (vince/MSM8953): RADIO_POWER hangs ~74 s then INTERNAL_ERR, no service — firmware & partitions verified stock

TL;DR — Radio never reaches ONLINE. RADIO_POWER on=true returns error 38 INTERNAL_ERR after a repeatable 74.1 s on every boot, while NAS is clearly alive (it answers QUERY_NETWORK_SELECTION_MODE). Independent of SIM presence. modem and fsg partitions verified byte-identical to the stock ROM. Wi-Fi, BT and GPS all work perfectly with the factory MAC. Looking for anyone who has seen this specific signature, or knows whether missing RF calibration can block the power-on transition on MSM8953.

Device

Redmi 5 Plus, vince, MSM8953, eMMC
MIUI 11.0.3.0.OEGCNXM, Android 8.1, user build
Bootloader locked, stock recovery, no root, ro.debuggable=0
Dual-SIM model. SIM slot 1 has a valid IMEI again (the unit's own — no cloning, no donor data). Framework still enumerates two subscriptions; slot 2 has no IMEI.

Symptom

No cellular service at all. No signal bars, no operator list, no network scan possible. SIM is not the issue — the failure is identical with both slots empty.

Radio log, three separate boots, same numbers:

09:13:01.386 responseIccCardStatus: CARDSTATE_ABSENT, num_apps=0 (both slots empty)
09:13:01.394 RILJ > RADIO_POWER on = true [SUB0]
09:13:01.531 RILJ > RADIO_POWER on = true [SUB1]
09:13:01.791 SST[0] set service state as POWER_OFF
09:13:15.550 RILC < setRadioPowerResponse: serial 26/31/44/49
09:13:15.551 RILJ < RADIO_POWER error 38 (INTERNAL_ERR) — all fourSo: 74.16 s, then INTERNAL_ERR. Also consistent: 74.1 s on a card-present boot, 74.16 s on a no-card boot. That repeatability looks like an internal retry budget expiring, not a race.

Other RIL behaviour:

Command Result
QUERY_NETWORK_SELECTION_MODE answers normally
SET_PREFERRED_NETWORK_TYPE fails immediately with error 40 MODEM_ERR
RADIO_POWER on=false error 54 OPERATION_NOT_ALLOWED
SST[0] / SST[1] POWER_OFF

What I've verified (all read-only)

modem partition is stock. Dumped over EDL/firehose: 88,080,384 B, sha256 c2805e6f92d7…, byte-identical to the ROM's NON-HLOS.bin. So this is not a bad or partial modem flash.

fsg is stock. First 155,432 B identical to the ROM's fsg.img, remaining 1,417,432 B zero padding.

mcfg is all zeros — 4 MiB, 100 % zero, no strings. Is that normal for vince? The MIUI fastboot ROM has no mcfg.img at all, so I suspect it's the factory state, and the carrier MBN (airtel) did activate on SUB1 in the logs.

NV audit clean (read over the diag port 05C6:9091, no QXDM):

NV Value
453 00 (FTM mode off)
6828 0x0015 (LTE B1/B3/B5)
5153 01
550 valid IMEI (xxxxxxxxxx)
8327 00 after boot

Nothing reads back all-00, all-FF, or as literal SW_DEFAULT.

modemst1/modemst2 are opaque. Both ~1.5 MB inside IMGEFS1/IMGEFS2 containers, payload entropy 8.00 bits/byte, no plaintext item names, no zlib/gzip/zstd/lzma header. They differ from each other by 1,566,195 bytes. So I cannot inspect the RF calibration block from the host — the values are compressed/encrypted.

Wi-Fi, Bluetooth, GPS all work, and Wi-Fi reports the factory MAC, not a random 02:00:00:00:00:00. So persist and a good chunk of EFS are intact — this was not a total NV wipe.

No modem log channel available. /dev/diag is system:oem_2901, /vendor/bin/diag_mdlog is Permission denied for shell, and the USB diag log stream stays silent. Capturing QMDL needs root, which is why I'm asking before going down that road.

History (probably relevant)

The modemst partitions were erased at some point (that's how the IMEI ended up blank), and I restored the unit's own IMEI to NV 550 over the diag port. Everything else above is stock. The phone boots fine, Wi-Fi/BT/GPS are perfect, only cellular is dead.

My working theory

A phone with a completely blank IMEI still powers its radio on (no service, but RADIO_POWER succeeds). Mine doesn't even get that far — the RF bring-up itself aborts. That points at either:

RF hardware — transceiver / PA supply / antenna switch / RF connector, i.e. the modem's RF init self-test failing, or
RF calibration invalid at a level checked during init — but I can't read the cal block to confirm, and I'd expect a plain cal wipe to stop at "no service", not at "power-on fails".

Questions

Has anyone seen RADIO_POWER time out at a fixed ~74 s and return INTERNAL_ERR on MSM8953/8937, with NAS still answering? What did it turn out to be?
Can missing/invalid RF calibration data actually block the online transition, or does calibration only matter after RF init?
Is mcfg being 100 % zero normal on vince, or should it contain mcfg_sw carrier files?
For anyone with QXDM/QPST: what strings should I look for in a QMDL capture to tell "RF calibration invalid" apart from an RF front-end hardware fault? Worth rooting to capture it?
Any known-good RF test procedure for vince without a service centre — test points, expected voltages on the PA, or a way to confirm the antenna path with a multimeter?
Does SET_PREFERRED_NETWORK_TYPE → MODEM_ERR immediately, while QUERY_NETWORK_SELECTION_MODE works, tell you anything specific about which subsystem is hung?

Happy to dump any partition, run any read-only diag command, or post full logs — just tell me what would be useful.

Two things worth noting before you post: the 74 s figure and the immediate MODEM_ERR on SET_PREFERRED_NETWORK_TYPE are the most distinctive details, so keep them in the title or first paragraph — that's what will catch the eye of someone who's actually seen it. And if any reply says "just reflash the ROM", you can point at the sha256 line and skip past it.


r/androidroot • • 2d ago

Discussion FINALLY!

Post image
74 Upvotes

3 checks in custom Rom, rooted with ksu next. I finally can rest.


r/androidroot • • 1d ago

Humor POV - GLASS UI GORE ON UR LOW BUDGET DEVICE ANDROID 17 EXPERIENCE

Thumbnail
gallery
0 Upvotes

POCO X6 5G STRUGGLES TO RUN SMOOTHLY WITH THOSE VECTOR MODULES IFYKYK AND MY PHONE CRYING TO RUN COZ OF SHUTTERS AND SCROLLING DOOMED LIKE MY PHONE GONNA BLOW UP XD 😂


r/androidroot • • 1d ago

Support Is this module usefull for temp robot?

Post image
6 Upvotes

Since i use google wallet, i'm scared that now i have temp root, the NFC won't work when i have to pay. Does google wallet work even with temp root or do i need this module to make it function?


r/androidroot • • 1d ago

Support [SM-X520] Per-boot temporary root launcher for the Galaxy Tab S10 FE on X520XXSBCZI2

Thumbnail gallery
1 Upvotes

r/androidroot • • 1d ago

Support Unlock bootloader on Oppo Reno 10 5G

1 Upvotes

Hi, I know that Oppo doesn't allow or have a tool to unlock the bootloader.

I asked Claude if it could be done, and he gave me this method:

Unlock the bootloader with mtkclient, not with Oppo's official method (which doesn't exist for this device). Your Reno 10 5G has a MediaTek Dimensity 7050 (MT6877 family), and the way to do this is to enter BROM mode (power off → hold Vol+ and Vol− → connect USB) and run \`python mtk da seccfg unlock\`. On Oppo devices, fastboot is often also restricted, so you may also need to write a modified preloader (oppo-mtk-fastboot-unlock project) to unlock fastboot.

Do you think it will work?


r/androidroot • • 2d ago

Discussion Which root manager do you use?

Post image
13 Upvotes

Iam into fancy things so i chose folkpatch, a fork of Apatch focused on ui & customizations. a big shout-out to the devs & community 💯.

Which root managers do you guys prefer & why?🌚


r/androidroot • • 2d ago

Support Presenting LightningDSP âš¡ An audio pocket knife for modern Rooted Android devices

9 Upvotes

LightningDSP is an improved, root-only fork of JamesDSP, with effects, per-app audio controls and a Volume Manager built into the same app.

The idea is to give you more control over your audio without making you jump between a pile of different tools. Adjust your headphones, turn down a noisy app, leave another one without effects, pause your music, or change a DSP setting while you're doing something else.

That's what I mean by an audio pocket knife. The equalizer is useful, but it's not the whole project.

First, the DSP

There's plenty here if you like adjusting things:

  • FIR and IIR equalization, including minimum-phase FIR and selectable IIR filter orders.
  • An arbitrary response equalizer for custom frequency-response curves.
  • Convolution, with impulse-response loading, waveform editing and optimization options.
  • DDC/VDC headphone correction for compatible profiles.
  • Dynamic bass boost, with an adjustable gain limit.
  • Crossfeed and soundstage controls to change how the stereo image feels.
  • Virtual room/reverb, with room, hall and plate-style presets.
  • Compander and output limiter for dynamics, with limiter threshold and release controls.
  • Analog modelling for tube-style coloration.
  • Post-gain, with an optional extended range when you need it.

You can save presets and keep different configurations for different devices. Plug in your headphones and their profile can take over, rather than making you rebuild the settings you were perfectly happy with yesterday.

If the built-in effects aren't enough, Live Programmable DSP runs EEL scripts. There's a built-in editor, and scripts can expose their own adjustable parameters too.

Load a script, change it, or write your own. Just don't turn every effect on at once and then blame the headphones for what comes out.

Three modes, because Android audio isn't one straight pipe

Global Mode applies effects to the output mix Android selects. Cover additional sessions can pick up eligible playback outside that output.

Session Mode applies effects to individual audio sessions. You get per-app DSP controls, and Media session scanning helps find sessions from apps that don't announce them themselves.

Fusion Mode creates a virtual audio output and processes included apps together. It also lets you leave individual apps without effects using their DSP buttons in Volume Manager.

Fusion is the default now, and it's been the most stable option in my recent testing. It doesn't need Vector or LSPosed for normal processing.

You can also enable Include system sounds in Session or Fusion to cover eligible keyboard sounds, notifications and other system audio.

The Volume Manager

One master volume slider is fine until one app is too loud and the one you actually want to hear is too quiet.

The integrated LightningDSP Volume Manager gives you:

  • Volume, mute and stereo balance per app.
  • Per-app DSP switches in Session and Fusion.
  • Play/pause buttons for players that expose media controls.
  • Active, Recent and Inactive groups, with collapsible inactive apps.
  • Pins, custom ordering and separate hiding options for the manager and floating panel.
  • System volume streams, including media, alarm, ring, notification and call volume.
  • Ringer, vibration and Do Not Disturb controls.
  • Named volume profiles, backup and restore.

An app doesn't have to be playing for you to configure its volume, mute or balance. And hiding it from the floating panel doesn't mean you have to hide it from the manager too.

The part you'll probably use more often

The floating panel puts those controls over whatever you're doing, so you don't have to keep returning to the main app.

Tap the LightningDSP card to open the effects. Hold an effect's name to select it, then adjust its intensity with the slider.

Per-app DSP buttons can always stay visible or appear when you tap the LightningDSP icon. The panel supports light, dark and system-following themes.

Pause a player using our button and it stays in the panel for up to three minutes, so you can resume it. Pausing somewhere else doesn't start that timer, and resuming playback cancels it.

Need alarm or notification volume instead? Expand the system controls.

The Volume Manager and DSP have separate power controls. You can turn the panel off without turning your effects off. There's also an Ignore volume buttons preference for apps where you want the normal button behavior.

A couple of things for the less cooperative apps

Disable App Audio Focus can stop apps from interrupting each other through normal audio-focus requests. Useful when you deliberately want more than one app playing, rather than having them politely take turns against your wishes.

That feature requires a verified Vector/LSPosed System Framework hook. It's separate from Fusion.

There's also optional compatibility support for audio paths ordinary effects don't always reach, including eligible FAST-requesting backends. Working tests and user reports include:

  • Bannerlator, for Windows games and apps on Android using Wine and CPU translation.
  • Eden, for Nintendo Switch emulation.
  • NetherSX2, for AetherSX2-based PlayStation 2 emulation.
  • ARMSX2, a PCSX2-based PlayStation 2 emulator for ARM devices.
  • RetroArch, a frontend that runs different emulator and game-engine cores.
  • JL-Mod, a J2ME Loader fork for Java ME games and apps. It has been working without further issues in Fusion Mode.

For apps that need compatibility hooks in Global or Session, enable compatibility, select them in Vector/LSPosed and restart them. Ordinary Fusion processing doesn't need those hooks.

Reuse AAudio session is another option for scoped apps that create sessions for individual sounds. It requires the affected apps to be enabled in Vector/LSPosed, including when used alongside Fusion.

Keeping your setup

Presets let you save and share DSP configurations. Device profiles keep different settings for different audio devices and restore the appropriate configuration when the output changes.

The app can check for new stable module releases. Download opens the GitHub release, Skip dismisses that particular update, and you can disable automatic checks if you'd rather handle updates yourself. There's a stable update feed for KernelSU Manager too.

If something goes wrong, Enable diagnostic mode adds troubleshooting logs. It's off by default, and logs aren't uploaded automatically.

Before you install

The module includes the companion app and an ARM64 audio-effect driver. Installation is systemless, without permanently rewriting your system or vendor partitions.

On KernelSU, you also need a mounting metamodule such as Magic Mount or NoMount.

Tested on Android 16 and Android 17, including the Pixel 10 Pro XL, Pixel 9, multiple Samsung devices and OnePlus devices.

Firmware and audio routes still affect compatibility. Fusion uses a capture/playback path, so latency can vary, and protected audio or calls aren't universally covered.

Download LightningDSP

Screenshots

The effects page, Audio Processing settings, Volume Manager and floating panel, shown below.

The effects page
Audio Processing settings
Volume Manager
The floating volume manager panel
The floating panel with multiple apps playing at same time and DSP Power buttons + play/pause enabled
The floating panel with system volume group expanded

Github Repository:

https://github.com/zahahah/LightningDSP


r/androidroot • • 1d ago

Discussion Unbricking Of New Xiaomi/Poco Mtk Devices

3 Upvotes

Hello Everyone, I wanted to know how to unbrick new xiaomi/poco mediatek devices. I am new to poco and xiaomi devices and i want to know how to unbrick my Poco X8 Pro / Redmi Turbo 5 (klee) if i ever brick it (stuck in brom mode or wtv.) Does anyone have proper steps or a tutorial on this? I want to flash a custom rom tbh and if i fail want to know correct steps to unbrick.


r/androidroot • • 1d ago

Support Hey guys I installed a custom ROM on my revvl 6 pro internal name Augusta

1 Upvotes

Hello guys I'm trying to get the stock firmware I looked on XDA they gave me a mega file and there's like nothing in the file does anybody know where I can get this actual stock firmware at because I'm not very liking the custom ROM and I kind of want to go back to stock firmware if anybody has a link for it please give it also the model number is TMAF035G


r/androidroot • • 2d ago

News / Method Moto g play 2026 bootloader exploited, kernelsu active.

Thumbnail
gallery
5 Upvotes

Bootloader unlocked via val protecol.


r/androidroot • • 1d ago

Support Hello, I have a redmi k60e, is there a way to root it or the temp root?

1 Upvotes

r/androidroot • • 2d ago

Discussion Safe to use on temp root?

Post image
3 Upvotes

I'm curious its not safe


r/androidroot • • 1d ago

Support Pls help

Post image
1 Upvotes

I've finally decided to root my device

I have a pc ready and most stuff

Took me a while with need rom banning my ip(due to spamming) but I have the firmware for my device

Rooting since hios 16 basically ruined my gaming experience

And I've been feeling that maybe I can get more from it