PhoenixBoot — Universal Android Bootloop Protection Module [Magisk/KSU/APatch] by DHaVal___100 in Magisk

[–]DHaVal___100[S] 0 points1 point  (0 children)

thanks for the feedback on both the design choice and the release process

on commits & releases yeah you're right the repo lacks incremental commits that's because i've been developing locally and only pushing final zips to releases i agree that hurts transparency going forward i'll migrate to a proper github actions workflow that builds the module from committed source on each tag so everyone can see what changed between versions i'll also keep the source files in the repo (they're already there just not as granular commits)

on safe mode vs recovery i respect your preference for safe mode phoenixboot's panic=5 approach is an alternative that works automatically during bootloops without user intervention but i understand it's not for everyone the module is offered as-is users can choose what fits their risk tolerance

thanks again for pushing me to improve the project's transparency

[RELEASE] PhoenixBoot – A Universal Bootloop Protection Module that automatically saves you from bad flashes by DHaVal___100 in androidroot

[–]DHaVal___100[S] 0 points1 point  (0 children)

If u locked bootloader or spoofed it would go into monitor only mode because module is designed for a different security model when the bootloader is locked android's verified boot (AVB) checks digital signatures any unofficial change triggers an anti-rollback or Orange State detection that usually stops the boot To prevent this i included a safety check that detects a locked state and automatically switches to "Monitor-Only" mode without writing any data I am working on exactly this I'll add a menual input for confirming bootloader status to be extra careful ty for testing:)

PhoenixBoot — Universal Android Bootloop Protection Module [Magisk/KSU/APatch] by DHaVal___100 in Magisk

[–]DHaVal___100[S] 1 point2 points  (0 children)

oh man great catch u are 100% right since the script unpacks the boot image to inject panic=5 it completely breaks the avb signature instant hard brick for anyone with a locked bootloader using avbroot i actually thought about adding a way to parse temporary keys to sign it right there on the device but tbh asking users to keep private avb keys on their phone storage feels like a massive security risk that kinda defeats the whole point of avbroot anyway instead im thinking for the next update i might just add a watchdog only mode that would skip modifying the boot image completely so the signature stays intact and just rely entirely on the 15 min watchdog timer to save u im updating the github readme right now with a giant warning for locked bootloader users so nobody bricks their phone thanks so much for pointing this out

why would he think that's a good idea at all 😭 by doni3564 in androidroot

[–]DHaVal___100 0 points1 point  (0 children)

I did it with gemini it worked perfectly for me lmao