@RadioAzureus As far as I know, you will have "success" with any #Xiaomi device if it's about obtaining root access:

For the first step, unlocking the boot loader, it's now unfortunately a gambling game hitting exactly the right time to "request permission", but doable. AFAIK, that's now the same crap for any Xiaomi device.

For root, you probably want to install #Magisk, this is straight-forward on most devices, but was cumbersome on mine because patching was required to some non-standard ramdisk contained inside vendor_boot, which the most recent Magisk app can't do yet out of the box.

On ANY rooted Android device, you'll have this constant battle against apps trying to detect root and/or unlocked bootloader and refusing to work with that ...

So to answer your question, my model has the codename 'iron' (or 'gold'), and if you're looking specifically for modding, I would NOT recommend it. First because of the non-standard patching required for root with Magisk, second because there's not a single custom recovery to be found that works on my device. The latter is probably related to the #Mediatek SoC used, there are also no "custom ROM" builds available.

JFTR, I didn't experience any issues with #HyperOS2 killing any of my apps after I told it not to do that.

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

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.

@kaixin was indeed a bit cumbersome. I had to patch the #magisk apk (modified boot_patch.sh) to get it installed at all. For google wallet, I needed an extra "play integrity" module to make it work, and my banking app required hiding installed apps (worked with lsposed and "hide my applist") ... but hey, all good for now

OpenEUICC for Magisk

#android #magisk #aosp #esim #euicc

OpenEUICC is an eSIM LPA (Local Profile Assistant) implementation for Android. It can provide eSIM support on Android devices that do not support eSIM. This requires a removable eSIM card. It has two variants, OpenEUICC and EasyEUICC. OpenEUICC is the full-fledged privileged variant. EasyEUICC is the unprivileged version that can run as a user app.

The author of OpenEUICC is PeterCxy. This repository is just compiled and packaged OpenEUICC as a Magisk module. The unpriv version is also compiled. No changes were made to the source code. Compilation, packaging and release are completely automated by Github Actions. It checks the OpenEUICC repository for new commits every day. If there are any new commits, it compiles, packages and release the module. This process is entirely automated, so install it at your own discretion.

https://github.com/hzy132/OpenEUICC_for_Magisk