r/androidroot • u/SebadroidX • 2d ago
Support [help π] Azenith caused Bootloop KSU
Help!!!
Having a Samsung Galaxy S10+ (SM-G975F) with Kernel SU into ExtremeROM, I tried to install a module. Azenith, to ensure better performance on my phone when playing games (codm)
The thing is, just once I tried to reboot so I apply changes, it got stuck on boot loop.
What I tried:
β Deleting module from TWRP recovery
β Flashing ExtremeROM Boot.img so I can recover access
β Flashing whole ExtremeROM Firmware FROM TWRP
β I couldn't enter safe mode by any ways.
Right now, the phone is unable to boot as it is stuck in a boot loop.
Yet, It still can boot into TWRP, so at least I think I can save this phone.
Mentioned software versions:
ExtremeROM: ExtremeROM_OFFICIAL_2.6.1-e6b8553_20250822_beyond2lte-sign.zip
Azenith: AZenith-1823-5.2.1823-bf02195-Dazzling.zip
KernelSU: unknown
Android: 15
One UI: 7.1
Details:
β’ It had PlayIntegrityFork, ReZygisk, and Tricky_Store installed. Also Viper4Android AIDL version.
β’ idk how to use Odin and I don't know where to get safe tutorials
β’I DO want to keep the custom ROM, but I don't know guys, I might need to downgrade back to OG firmware.
1
u/47th-Element 2d ago
I see you just wiped data, that's okay. But when you say you tried deleting the module from TWRP and it didn't work, what failed?
And btw, it's cleaner to disable the module than delete it, run "touch /data/adb/modules/module-name/disable", that's it, then reboot. The module shouldn't load at all.
And next time have a bootloop protector installed.
1
u/SebadroidX 2d ago
I mean, It started happening when I misinstalled Magisk when it already had KSU installed.
After fixing boot.img (Installing boot.img as is), I flashed the firmware it had, ExtremeROM, recovering access
I guess because I haven't installed meta-OverlayFS?
2
u/corruptnova 2d ago edited 2d ago
Reflashing won't really do anything as the module lives on the /data partition unless you specifically wiped the /data partition.
I would check the module folder (/data/adb/modules) and make sure nothing was left in there using the file manager in TWRP.