Recent content by Igor Eisberg

Maybe when we learn how to magically conjure devices.

Some issues happen regardless of our modifications. That's the nature of using custom ROMs. Knowing whether they exist on stock ROMs or not doesn't help with fixing them.

We're not 14 years old, we have better things to do than to babysit people in a "beta program". We deal with issues we can identify, and we don't bother with things that have nothing to do with our modifications.

https://xiaomi.eu/community/threads/hyperos-2-0-stable-release.74372/post-744208

I don't know what you're referring to.

We don't have a ROM for this device.

No. Support for apollo ended long ago.

No, and obsessing over having the highest version numbers for everything doesn't make much sense.

Not just the package installer, and what you're trying to do is your right but we don't provide any support for it.

There is no link for it anymore. No. The modem I made had nothing to do with charging, it was for SIM and eSIM to work without breaking the camera. If it coincidentally fixed the charging issue then great, but I'm not about to build modem images on demand.

@RonanTheAccuser That error is unrelated to matrix2012xman's error. I can't reproduce it, it works fine here, although I found an issue that I just fixed, but it doesn't cause any crashes.

I'm trying to understand what data you're trying to regain access to. You said that user 0 was successfully decrypted using TWRP and you were able to backup some files. You won't be decrypting user 999 (reserved for dual apps, as far as I remember) with TWRP, as it doesn't use your pattern and...

There is no Link to Windows crash on our ROMs. Read reply above.

The TWRP was included in the ROM back then, it was a Chinese TWRP with default language set to Chinese, and can be easily changed within TWRP. It has nothing to do with the region of boot.img. Sounds like uninstalling Magisk corrupted the boot.img. All you had to do to fix the boot failure was...

The original Link to Windows app (com.microsoft.appmanager) doesn't have "com.samsung.android.mdx.windowslink.tileservice", so that's not the source of the crash. By the looks of it, it comes from an app called "Link to Windows Service" (com.samsung.android.mdx), something meant for Galaxy...