Search results

Thanks. I've messaged to the guy on XDA who wants to flash on Cepheus and he will try File size is now ok and 3.6 should fit to A11

I have downloaded twrp-3.7.0_9-0-cepheus-TeamWin.zip for Cepheus (Mi 9) but it is 67,682,304 Bytes AFAIK, Cepheus has Recovery of 64 MB = 64 x 1024 x 1024 = 67,108,864 Bytes Hence the file is cca 580 Bytes too big and indeed Fastboot reports no space to flash On TWRP.me there is only TWRP...

Xiaomi.eu has built-in spoof to pass Play Integrity/ SafetyNet but some apps may use other andndirect methods to detect that Bootloader is unlocked. In that case it will only work with the official ROM that can be installed and then and used with (Re')locked Bootloader. Xiaomi.eu is custom ROM...

Use Zygisk-LSPosed and of course prior to that enable Zygisk in Magisk app Settings (and reboot). And don't use Riru modules (not compatible with Zygisk). Download from TG channel (see screenshots)

Have you tried first with clean installation of Xiaomi.eu - that is, without Magisk, even before enabling Developer options Although bootloader is unlocked, Xiaomi EU has built-in some protections. But once you install Magisk, you opened more and more possibilities to detect

Not related to that nodule but to LSPosed and CustoMIUIzer14 Smart (in)lock on the eg home WiFi and car Bluetooth

Q: How to do A: See below Although it's generally not necessary, there are various modules that pin-point and systemlessly mount only particular changes for particular purposes, what their developers took care about, it's generally possible to mount /system, /vendor, /product, /system_etc...

Thanks for your continued work Finally I upgraded my Lisa to Stable MIUI14 / A13 (for two years I was on MIUI 13 / A12 ROMs) and it really gave a new life to my aging Lisa I upgraded by Fastboot, first-time script (hence clean installation) and everything works stable and smooth (as always I...

If talking about V4A 64-bit Reverse Engineering, it's still WIP (Beta v0.5.0 latest), watch the progress on the GitHub: https://github.com/AndroidAudioMods/ViPERFX_RE/issues/2

Does maybe this command regenerates Dalwik: adb shell cmd package bg-dexopt-job

Did you see post #6 above - same device and it works for that user (64-bit V4A Alpha version, and you must use the Legacy mode)

See the screenshots how to follow links on the page to go back to the old MIUI releases

OP = Original post(er) It means the posts #1 and #2 in this thread. Aren't there the links to Download the ROM zip installations from sourceforgenet and androidfilehost Unzip and look for the IMG files for the various partitions

I stay on the latest 12.5.2 (A11) on my Mi 9T since that was the last Xiaomi.eu ROM released for that phone. There are custom ROMs with A12 but at some point the old phones do no more work smooth with the newer OS versions and the ROMs are no more tuned for them Probably that Mi 9T worked...

Could anybody check pls on Lisa with Xiaomi.eu MIUI 14 Stable if the Orange Fox: OrangeFox-R11.1_2-Unofficial-lisa from https://sourceforge.net/projects/recovery-for-xiaomi-devices/files/lisa/ (that OFox was integrated to Xiaomi.eu MIUI 13 Recovery type ROMs for Lisa) still works on MIUI 14/A13...

You should be better off by asking about passing Play Integrity API: https://play.google.com/store/apps/details?id=gr.nikolasspyr.integritycheck since by June this year or so SafetyNet will be deprecated and apps published to Playstore will have to switch to PI API (eg, Google Wallet has...

For some countries access to Xiaomi.eu 'OTA' servers is blocked and in that case you would need to check in this thread and manually at the download servers

Smart (un)lock fully works but with Magisk (root), LSPosed and CustoMIUIzer14: System, Lock screen, (Selectively) Disable screen lock and there you have options: Trusted WiFi networks and Trusted Bluetooth devices Eg, I tested with BT in my car and my home WLAN

You should not need. Besides, you can not install USNF without Magisk - it's a Magisk module

Thanks Which device and MIUI 13 or 14 please do you use? Which version of V4A (which of my posts above)? Just for the others to know... PS: I'm still on MIUI 12.5 and 13 (two devices) and all three ways worked for me and I'm now using this latest 64-bit V4A beta 0.2.0