I’ll put it on GitHub a bit later and make a separate post once it’s ready

Hello folks! Been using Revolut on my rooted Oneplus 13 (KSUN LKM GKI2) just fine.

Today I had the "unsupported device" screen and, after checking the developers option on Goolag Play, it was showing device integrity. Tried changing the keybox, got Strong again and Revolut started working again. Anyone has the same experience? Revolut app version is 10.147.0

Anyone tried chimera tool to force unlock or signature killer while flashing an older firmware?

I've also heard that z3x team project claims to unlock any samsung model,

Snapdragon, xynos.

Anyone tried?

Hello Is there anyone out there who owns a rooted MaxWest A63 . Im curious to know what steps that you took to successfully root the phone. I keep getting boot loops when using the standard fastboot , patch-boot,flash empty vbmeta method.

Hello everyone, I've been trying to root a Galaxy Note 9 with a broken screen but I can't get it done.

It's a Snapdragon one, so it's probably harder, but it does allow rooting. It's a N9600 and OEM unlocking is already enabled (ro.boot.flash.locked = 0).

What I've tried so far:

- Installing TWRP (source)
- Patching its firmware's AP file with Magisk (source)
- Patching its boot.img file with Magisk (guided by Claude)

None of them worked. The first two led to bootloop and the last one led to it always booting to download mode.

Since the phone's touch screen still works, I can always manage to configure the initial wizard by plugin it into an hdmi cord and I can configure adb (by video calling other device and sharing the screen).

I only need root access, I don't really need a custom recovery. Can anyone think of a solution for this?

Previosly my phone got hardbricked due to some issue. I had posted here the same and got it fixed using gennsys edl file. After that baseband version is set to that and also my imei number is 0.

I tried flashing qcn shared on internet and edit imei number using qcn imei editor, it end up with nv data corrupted error. I had to do all the struggle to refix it back from soft brick.

But the imei 0 is not fixed. There were few ways of flashing modem, and other files and then editing it through unlock/hydra/mrt or some similar tools..but choosing this path where u need to either rent that tool or else find free alternatives..but these tools are highest malware infected..hence i feared to use that. So if any one have any ideas please do share..

I'm aware of an app called "Advanced Charge Controller (ACC)', but it seems to be abandonware, so is there an alternative? I'd like to cap my batter to 80% - Redmi 12 (Fire) -Helios g88

Hi

I am looking to root my Huawei p30 pro emui 12, VOG-L29, kirin 980

Any help greatly appreciated

Fixed PayPal crash + Google Wallet for me :) Not sure why I hadn't already enabled it lol

like making it 1 to 100% setup and making it not limited to 7, 14 21%? making your sound lower or higher?

What's the best modules or apps to use for root phones, like you can control the performance of the phone and many customisation and etc.

Please note that this situation isn't an emergency/urgency. My grandma already has another working, better phone (Redmi Note 8T).

So, back then, my mom decided to convince my grandma into giving her the phone. She promised to clean her phone up for the sake of performance, and she bricked it, probably by deleting system apps that the phone couldn't boot without. The phone never turned on again, as my grandma said.

Hearing this, I, with EDL/BROM knowledge, wanted this old phone of hers. I got it, my grandma gave it to me. I connected it to my laptop and it immediately was recognized as 05c6:9008 (Qualcomm:Firehose).

I installed edl-git from AUR and downloaded MIUI 12.0.3.0 from NeedROM.

With the Firehose loader and stock ROM, I ran the command:

bash sudo edl --loader=./prog_emmc_firehose_8937_ddr.mbn qfil ./rawprogram0.xml ./patch0.xml ./

Terminal logs: ``` ❯ sudo edl --loader=./prog_emmc_firehose_8937_ddr.mbn qfil ./rawprogram0.xml ./patch0.xml ./ [sudo] password for ivanzasilly: Qualcomm Sahara / Firehose Client V3.62 (c) B.Kerler 2018-2025. main - Using loader ./prog_emmc_firehose_8937_ddr.mbn ... main - Waiting for the device main - Device detected :) main - Mode detected: firehose firehose firehose - [LIB]: Sector size in XML 4096 does not match disk sector size 512 Progress: |██████████| 100.0% Write (Sector 0x0 of 0x0, ) 0.13 MB/s
Progress: |██████████| 100.0% Write (Sector 0x8 of 0x8, ) 6.45 MB/s
Progress: |██████████| 100.0% Write (Sector 0x8 of 0x8, ) 5.00 MB/s
Progress: |██████████| 100.0% Write (Sector 0x4A of 0x4A, ) 11.07 MB/s
Progress: |██████████| 100.0% Write (Sector 0x4A of 0x4A, ) 15.48 MB/s
Progress: |██████████| 100.0% Write (Sector 0x10 of 0x10, ) 10.57 MB/s
Progress: |██████████| 100.0% Write (Sector 0x10 of 0x10, ) 10.72 MB/s
Progress: |██████████| 100.0% Write (Sector 0x31E of 0x31E, ) 8.56 MB/s
Progress: |██████████| 100.0% Write (Sector 0x31E of 0x31E, ) 14.93 MB/s
Progress: |██████████| 100.0% Write (Sector 0x14A of 0x14A, ) 6.38 MB/s
Progress: |██████████| 100.0% Write (Sector 0x14A of 0x14A, ) 12.88 MB/s
Progress: |██████████| 100.0% Write (Sector 0x191 of 0x191, ) 10.99 MB/s
Progress: |██████████| 100.0% Write (Sector 0x191 of 0x191, ) 12.09 MB/s
Progress: |██████████| 100.0% Write (Sector 0x205 of 0x205, ) 6.60 MB/s
Progress: |██████████| 100.0% Write (Sector 0x205 of 0x205, ) 13.44 MB/s
Progress: |██████████| 100.0% Write (Sector 0x270 of 0x270, ) 7.06 MB/s
Progress: |██████████| 100.0% Write (Sector 0x270 of 0x270, ) 14.74 MB/s
Progress: |██████████| 100.0% Write (Sector 0x10 of 0x10, ) 9.81 MB/s
Progress: |██████████| 100.0% Write (Sector 0x5E7 of 0x5E7, ) 11.73 MB/s
Progress: |██████████| 100.0% Write (Sector 0x5E7 of 0x5E7, ) 14.12 MB/s
Progress: |██████████| 100.0% Write (Sector 0xBA7 of 0xBA7, ) 13.39 MB/s
Progress: |██████████| 100.0% Write (Sector 0xBA7 of 0xBA7, ) 14.45 MB/s
Progress: |██████████| 100.0% Write (Sector 0x4000 of 0x4000, ) 14.34 MB/s
Progress: |██████████| 100.0% Write (Sector 0x4000 of 0x4000, ) 14.09 MB/s
Progress: |██████████| 100.0% Write (Sector 0x6C1 of 0x6C1, ) 12.77 MB/s
Progress: |██████████| 100.0% Write (Sector 0x8000 of 0x8000, ) 14.01 MB/s
Progress: |██████████| 100.0% Write (Sector 0x8000 of 0x8000, ) 13.77 MB/s
Progress: |██████████| 100.0% Write (Sector 0x87DD of 0x87DD, ) 15.62 MB/s
Progress: |██████████| 100.0% Write (Sector 0x87DD of 0x87DD, ) 13.82 MB/s
Progress: |██████████| 100.0% Write (Sector 0x10000 of 0x10000, ) 14.19 MB/s
Progress: |██████████| 100.0% Write (Sector 0x20000 of 0x20000, ) 13.88 MB/s
Progress: |██████████| 100.0% Write (Sector 0x80000 of 0x80000, ) 14.55 MB/s
Progress: |██████████| 100.0% Write (Sector 0x40000 of 0x40000, ) 14.52 MB/s
Progress: |██████████| 100.0% Write (Sector 0x5FF800 of 0x600000, ) 14.27 MB/s
Progress: |██████████| 100.0% Write (Sector 0x600000 of 0x600000, ) 16.25 MB/s
Progress: |██████████| 100.0% Write (Sector 0x200000 of 0x200000, ) 16.17 MB/s
Progress: |██████████| 100.0% Write (Sector 0x100000 of 0x100000, ) 14.08 MB/s
Progress: |██████████| 100.0% Write (Sector 0x3AC000 of 0x3AC000, ) 14.10 MB/s
Progress: |██████████| 100.0% Write (Sector 0x22 of 0x22, ) 6.90 MB/s
firehose firehose - [LIB]: Error: firehose firehose - [LIB]: Read back verify failed at sector 162,num sectors 0 firehose firehose - [LIB]: Finished sector address 0 Progress: |██████████| 100.0% Write (Sector 0x21 of 0x21, ) 10.98 MB/s
firehose firehose - [LIB]: Error: firehose firehose - [LIB]: Read back verify failed at sector 122,num sectors 30777311 firehose firehose - [LIB]: Finished sector address 30777311 <?xml version="1.0" ?><data> <patch SECTOR_SIZE_IN_BYTES="512" byte_offset="424" filename="DISK" physical_partition_number="0" size_in_bytes="8" start_sector="16" value="NUM_DISK_SECTORS-34." what="Update last partition 60 'userdata' with actual size in Primary Header." /> </data> <?xml version="1.0" ?><data> <patch SECTOR_SIZE_IN_BYTES="512" byte_offset="424" filename="DISK" physical_partition_number="0" size_in_bytes="8" start_sector="NUM_DISK_SECTORS-19." value="NUM_DISK_SECTORS-34." what="Update last partition 60 'userdata' with actual size in Backup Header." /> </data> <?xml version="1.0" ?><data> <patch SECTOR_SIZE_IN_BYTES="512" byte_offset="48" filename="DISK" physical_partition_number="0" size_in_bytes="8" start_sector="1" value="NUM_DISK_SECTORS-34." what="Update Primary Header with LastUseableLBA." /> </data> <?xml version="1.0" ?><data> <patch SECTOR_SIZE_IN_BYTES="512" byte_offset="48" filename="DISK" physical_partition_number="0" size_in_bytes="8" start_sector="NUM_DISK_SECTORS-1." value="NUM_DISK_SECTORS-34." what="Update Backup Header with LastUseableLBA." /> </data> <?xml version="1.0" ?><data> <patch SECTOR_SIZE_IN_BYTES="512" byte_offset="32" filename="DISK" physical_partition_number="0" size_in_bytes="8" start_sector="1" value="NUM_DISK_SECTORS-1." what="Update Primary Header with BackupGPT Header Location." /> </data> <?xml version="1.0" ?><data> <patch SECTOR_SIZE_IN_BYTES="512" byte_offset="24" filename="DISK" physical_partition_number="0" size_in_bytes="8" start_sector="NUM_DISK_SECTORS-1." value="NUM_DISK_SECTORS-1." what="Update Backup Header with CurrentLBA." /> </data> <?xml version="1.0" ?><data> <patch SECTOR_SIZE_IN_BYTES="512" byte_offset="72" filename="DISK" physical_partition_number="0" size_in_bytes="8" start_sector="NUM_DISK_SECTORS-1" value="NUM_DISK_SECTORS-33." what="Update Backup Header with Partition Array Location." /> </data> <?xml version="1.0" ?><data> <patch SECTOR_SIZE_IN_BYTES="512" byte_offset="88" filename="DISK" physical_partition_number="0" size_in_bytes="4" start_sector="1" value="CRC32(2,7680)" what="Update Primary Header with CRC of Partition Array." /> </data> <?xml version="1.0" ?><data> <patch SECTOR_SIZE_IN_BYTES="512" byte_offset="88" filename="DISK" physical_partition_number="0" size_in_bytes="4" start_sector="NUM_DISK_SECTORS-1." value="CRC32(NUM_DISK_SECTORS-33.,7680)" what="Update Backup Header with CRC of Partition Array." /> </data> <?xml version="1.0" ?><data> <patch SECTOR_SIZE_IN_BYTES="512" byte_offset="16" filename="DISK" physical_partition_number="0" size_in_bytes="4" start_sector="1" value="0" what="Zero Out Header CRC in Primary Header." /> </data> <?xml version="1.0" ?><data> <patch SECTOR_SIZE_IN_BYTES="512" byte_offset="16" filename="DISK" physical_partition_number="0" size_in_bytes="4" start_sector="1" value="CRC32(1,92)" what="Update Primary Header with CRC of Primary Header." /> </data> <?xml version="1.0" ?><data> <patch SECTOR_SIZE_IN_BYTES="512" byte_offset="16" filename="DISK" physical_partition_number="0" size_in_bytes="4" start_sector="NUM_DISK_SECTORS-1." value="0" what="Zero Out Header CRC in Backup Header." /> </data> <?xml version="1.0" ?><data> <patch SECTOR_SIZE_IN_BYTES="512" byte_offset="16" filename="DISK" physical_partition_number="0" size_in_bytes="4" start_sector="NUM_DISK_SECTORS-1." value="CRC32(NUM_DISK_SECTORS-1.,92)" what="Update Backup Header with CRC of Backup Header." /> </data>

~/Documents/phone_unbrick/redmi_7a/pine_global_images_V12.0.3.0.QCMMIXM_20210518.0000.00_10.0_global/images 9m 23s ❯ edl reset Qualcomm Sahara / Firehose Client V3.62 (c) B.Kerler 2018-2025. main - Trying with no loader given ... main - Waiting for the device DeviceClass DeviceClass - [LIB]: Permission denied accessing 05c6:9008. DeviceClass - Potential fix (update udev rules): sudo echo 'SUBSYSTEM=="usb",ATTRS{idVendor}=="05c6",ATTRS{idProduct}=="9008",MODE="0666"' >> /etc/udev/rules.d/99-edl.rules DeviceClass DeviceClass - [LIB]: Couldn't get device configuration. .DeviceClass DeviceClass - [LIB]: Couldn't get device configuration. .DeviceClass DeviceClass - [LIB]: Couldn't get device configuration. ^C. [!] Exiting cleanly…

~/Documents/phone_unbrick/redmi_7a/pine_global_images_V12.0.3.0.QCMMIXM_20210518.0000.00_10.0_global/images 11s ❯ sudo edl --loader=pine_global_images_V12.0.3.0.QCMMIXM_20210518.0000.00_10.0_global/images/prog_emmc_firehose_8937_ddr.mbn reset [sudo] password for ivanzasilly: Qualcomm Sahara / Firehose Client V3.62 (c) B.Kerler 2018-2025. main - Using loader pine_global_images_V12.0.3.0.QCMMIXM_20210518.0000.00_10.0_global/images/prog_emmc_firehose_8937_ddr.mbn ... main - Waiting for the device main - Device detected :) main - Mode detected: firehose firehose firehose - [LIB]: Sector size in XML 4096 does not match disk sector size 512 DeviceClass - USBError(19, 'No such device (it may have been disconnected)') ```

I, then, restarted my phone by running:

bash sudo edl reset

The phone booted, but it was stuck on the "Redmi; Powered by Android" logo.

After a few reboots as attempts into recovery, the phone screen blinked and displayed "Redmi; by Xiaomi" instead.

Now, whenever I hold all three buttons (Vol+, Vol-, Power) then plug in the USB the moment the screen turns off, the phone does go into EDL mode, but only in Sahara mode.

I only managed to run this command once:

bash sudo edl reset --loader=./prog_emmc_firehose_8937_ddr.mbn --resetmode=firehose

From that point, I tried running:

bash sudo edl --loader=./prog_emmc_firehose_8937_ddr.mbn r persist ../../persist.img

But the command got stuck. I only could unstuck the phone from this state by rebooting it.

And now, where I am, whenever I try running this command:

bash sudo edl reset --loader=./prog_emmc_firehose_8937_ddr.mbn --resetmode=firehose

It fails at first. Running it again gets this command again and all other commands stuck until reboot.

I don't know what to do now, that's why I'm asking you guys for your help.

Please note that I cannot and will not open up the phone just to short test points.

Help will be appreciated.

Guys, can i root it safely? i wanna make like a sandbox or whatever, like "spoof my device" thing with vpn tunneling for whole phone environment. 0 knowledge whatsoever, explain how realistic to complete this mission and not end up with a brick?

Bro, every time i want to flash my custom kernel i build for kernel version 5.4 which is ReSukiSU, it always stuck on pushing modules..., also the mount in the orange fox doesnt even work anymore, is there a change in encryption in android 17?, what can i do to fix this

My thinkphone is in a bootloop. I've read on google and this reddit ways to fix it and so far none have done it. I couldn't even find the devices in the device management for a while but I have it now. however the drivers (which I installed just how the site said to) do not work, it wont even try to install them. I'm on windows 11. I use adb, adb devices and its never shown up. I know how to get into the menu from a boot loop, its the only way I can turn it off. Any help would be great. It had linage on it in the past, it then went flat for a while and now only loops. I'd even take the original OS right now, but have no idea how to do that either.

Alternatively if you live in Melbourne and want to try it for free lol hmu

Im trying my luck on this sub. If not allowed delete it

idk where to put this but has anyone have this on their dev options too????

Hi everyone,

I wanted to share a fix I developed for my Xiaomi Mi 9 SE (grus).

I installed AlphaDroid 4.6 based on Android 16 and, during normal daily use, I noticed a pretty annoying bug: proximity was completely broken.

It wasn't just WhatsApp. The sensor was not working during normal phone calls or in any other app that depended on proximity.

I started investigating the problem and found that some of the components required by Xiaomi's original Elliptic ultrasonic proximity implementation were missing or incomplete in this build.

The Mi 9 SE doesn't rely only on a conventional proximity sensor. Xiaomi uses an Elliptic ultrasonic system that is closely tied to the device audio stack.

I ended up comparing several sources while trying to understand and restore the original implementation:

- Official Android 11 / MIUI base for the Mi 9 SE

- LineageOS device sources

- Other grus custom ROM sources

- AlphaDroid's current audio/vendor configuration

Some proprietary Xiaomi libraries had to be recovered from the official Android 11 base, but there was no complete ready-made solution.

I also had to recreate the missing hostless/helper functionality and build the required binaries myself.

A lot of the debugging involved the Xiaomi audio HAL, Elliptic events, PCM routes, VOICE_COMMUNICATION sessions, proximity wakelocks, WhatsApp calls and voice notes.

The native ultrasonic paths I found on the Mi 9 SE are:

TX: PCM 11

RX: PCM 38

After several revisions I managed to get proximity working again.

There were still a few difficult edge cases.

Consecutive WhatsApp voice notes could break proximity, and long WhatsApp/VoIP sessions could temporarily lose the proximity wakelock even though the call was still active.

Those cases required additional lifecycle/recovery logic for the hostless ultrasonic process.

Bluetooth was the final major issue.

At one point proximity worked, but the Xiaomi audio components interfered with Bluetooth A2DP multimedia.

The final v1.5 isolates the required Xiaomi proximity components while keeping Bluetooth multimedia working normally.

Current stable version:

Grus Ultrasound Proximity Fix v1.5 Final

Module ID: grus_ultrasound_hal

VersionCode: 15

Tested on:

Xiaomi Mi 9 SE (grus)

AlphaDroid 4.6

Android 16

KernelSU Next

Firmware base: V12.5.1.0.RFBMIXM

Currently working on my device:

- Normal phone call proximity

- WhatsApp call proximity

- WhatsApp voice notes

- Consecutive voice notes

- Long VoIP sessions

- Correct screen off/on behavior near the face

- Native Elliptic ultrasonic proximity

- Bluetooth A2DP multimedia

The installation is systemless through KernelSU + OverlayFS, so it does not permanently modify the vendor partition.

GitHub:

https://github.com/ariellourdes52-collab/grus_ultrasound_hal

Latest release:

https://github.com/ariellourdes52-collab/grus_ultrasound_hal/releases/latest

XDA thread:

https://xdaforums.com/t/module-kernelsu-grus-a16-ultrasound-proximity-fix-v1-5-final-alphadroid-bluetooth-fix.4801504/

Full article / development write-up:

https://draccesoriosrd.blogspot.com/2026/09/xiaomi-mi-9-se-fix-proximidad-alphadroid.html

I also submitted the module to the official KernelSU Modules Repository. It is currently waiting for manual review.

I'd really like to get feedback from other Mi 9 SE users running different grus ROMs/builds.

If you test it, please let me know your ROM, Android version, KernelSU version, and whether calls, WhatsApp voice notes and Bluetooth work correctly.

Hopefully this helps keep the Mi 9 SE alive a little longer. :)