The new #Xiaomi phone with #HyperOS2 is now fully #rooted, with #Magisk installed plus some modules, including a de-bloater that, if I understand that correctly, gets rid of system apps using filesystem overlays (so, they're still there in the system partition, but really unaccessible on a very low layer). The other modules are there for fixing integrity checks, I got google wallet, paypal and my bank's app to work flawlessly. 馃コ

Now it should be possible to install some linux dist in a chroot, will probably test that soon.

There were quite a few issues on the way, e.g. a weird location of the init-boot that needs patching to install magisk: a cpio archive inside vendor-boot, unsupported by vanilla magisk, so I had to patch the magisk app first to move on 馃く. Getting magisk installed and the necessary tweaks in place for certain apps to work again took me half a day. Well, the phone model isn't the most widespread one, so finding infos took some time.

And there's still the same general issue with #android #modding community that I already observed 15 years ago, although back then, things were generally simpler: It seems most of the time, people only share some step-by-step instructions without ANY explanation, and people are also only looking for that. It's weird, you see forum posts from people doing the dumbest things by varying these instructions if they don't work for them, because they have no background knowledge whatsoever. What's even worse now, people started putting crappy videos on youtube and tiktok. Don't ever watch any of them, it's a pure waste of time. Instead, work through all the stuff on XDA, it's also full of that pointless "do that, then do that, type foo, click here" nonsense, but occasionally you will find the background info you need to understand what's going on and how to fix your own issues. 馃お

What I'm still missing is a custom #recovery that can actually do any useful stuff (especially full #backup).

My device has recovery as a #ramdisk in vendor_boot, and there are some prebuilt vendor_boot images with #twrp around, which I don't want to use directly because there's also an init-boot ramdisk in there that needs patching for root with #magisk ... and as far as I understood now, these ramdisks are userland only, using the shared #kernel from the boot partition, so it's unlikely a recovery built for #HyperOS1 (#Android 14, #Linux 5) will work with #HyperOS2 (Android 15, Linux 6).

What I did try nevertheless was modifying my vendor_boot using Magisk's #magiskboot utility, replacing ONLY the recovery ramdisk. It resulted in #bootloop trying to boot the normal system, so there seems to be something I still don't understand (I thought this ramdisk would only ever be loaded when booting to recovery).

For now, I'll live with the useless stock #Xiaomi recovery. Attempting to do my own build of twrp or orangefox really is too much hassle 馃檲