- [MagiskBoot] Don’t pad zeros if signed boot image is larger
- [MagiskPolicy] Fix genfscon and filename_trans
- [MagiskPolicy] Fix bug in libsepol
- [Zygisk] Fix and simplify file descriptor sanitization logic
- [App] Prevent OOM when patching AP tarfiles
- [App] Fix bug in device configuration detection
- [Daemon] Fix certificate parsing of APKs
- [General] Fix logging errors from C++ code being ignoredq
Most custom ROMs support custom recoveries if I’m not wrong.
Yeah they do generally, and I can install and run a custom recovery (Orange Fox, had more luck with that on my device than TWRP). When I’m in recovery, I can see all the root storage, I can see all the installed apps, but
sdcard
just has Fox’s log folder whilestorage
has a bunch of folders with encrypted names. I think maybe it’s the ROM specifically (DivestOS) that’s doing some extra encryption, I’m not sure. In any case, I struggle to flash things because of this, sometimes I’ve had to stick with the stock LineageOS recovery and sideload to get Magisk on.Maybe with more tinkering I could figure out the issue, but I don’t really have the time so much anymore.
Doesn’t Divest use its own recovery? It did when I flashed it last week.
Maybe, but it looks the same as the LineageOS one, and doesn’t have any functionality really beyond ADB Sideload. At least, that’s all I’ve ever had for my alioth version.
deleted by creator
I faced this without an OS installed, my storage wasn’t encrypted. Something to do with orangefox, because twrp worked normally.
Maybe, I had OrangeFox working on other ROMs, might give TRWP a try again. Tbh it could just be my phone (Poco F3), never really been able to get things working smoothly, eg backup and restore at recovery level.
Plus Google doing all they can to make rooting harder. Beginning to think it isn’t worth it anymore. I definitely need it now to get rid of the horrid MIUI skin, but for my next phone I might just go for one with a stockish skin and keep it as is.