Search results

Usually you don't need Strong (Google, themselves, for Wallet requires Basic and Device only, not Strong) Now, the problem is that you (and some others reported similarly for Stable or Weekly Xiaomi.eu) do not pass Device Integrity Moderators will tell you to wait, that Google will solve...

It has nothing with a few months old Security Update Google Pay/Wallet require to pass Basic and Device Integrity (not Strong) Download Play Integrity API Checker from Playstore and test And if you fail Basic Integrity, then that's the problem with unlocked Bootloader and custom ROM

Not root but unlocked Bootloader and custom ROM

SafetyNet is deprecated, Play Integrity is relevant If you NOW install your old 14.6, are you sure that Play Integrity would still work? And specially that your banking app will work? Google slowly but constantly improve 'detections' in Play Integrity and more important, every new version of...

If ROM updates boot.img, it means that your previous boot.img that was patched by Magisk is gone. You must root again - modules and everything will be preserved, will show again after you reinstall Magisk again (if you didn't do Factory reset or wiped your /data partition)

It's generally a known issue (users have to be aware of), that banking, payment and similar apps look for and detect unlocked Bootloaders, installed custom ROMs and treat those phones as insecure environments per their definitions There are methods to spoof, but they require rooting (Magisk)...

By 'root' apps report the fact that you have unlocked Bootloader and flashed an unofficial, custom ROM (and custom Recovery). That banking app wants the official, stock ROM, certified by Google - when it's not, it doesn't and cannot check if your custom ROM is as secure for them as the official...

Please read the OP post #1, first page, it says: "Installing with Fastboot: ... Run one of the installation scripts... first_install_with_data_format - with data wipe, if you're flashing Xiaomi.eu ROM for the first time or downgrading. - update_rom - without data wipe"

Rule #1, in the OP post #1, on the page #1

Good luck in waiting...

https://xiaomi.eu/community/threads/guide-how-to-install-viper4android.66751/post-671953 https://xiaomi.eu/community/threads/guide-how-to-install-viper4android.66751/post-680981

Official Google FAQ: https://www.google.com/android/uncertified "If you are a User wanting to use custom ROMs..." The other way is to install Magisk, etc

Did you just test MTP in TWRP or did you make backup in TWRP on Lisa and tested are you able to access the backup files from Android

Just one comment about the TWRP 3.7.0_12 as provided with Xiaomi.eu Stable for Lisa (Mi 11 Lite 5G NE) AFAIK, that's the only custom Recovery that works for MIUI 14 on Lisa But there is one issue - and a workaround. It was all discussed and confirmed on XDA forum When you make a backup, it...

TWRP flashed by Stable 14.0.10 works fine for me I did install (previous) Stable by Fastboot and as that, Xiaomi.eu ROM installed the TWRP Next time I updated through OTA, by use of that TWRP PS. I see now brand New v14.0.12 Stable for Lisa, didn't install yet

By the way, with latest Magisk v26202 (Canary), you can select the whole downloaded OTA zip (can be 5 or so GB), Magisk will unzip and extract the boot img itself, will patch it and will save the patched boot.img (like 192 MB) to Download folder. Screenshot 1 shows the steps: - processing zip...

Use Repackaged V4A from #2 and/or 64bit Beta from post #3 They provide the same functionality and more Please see the other posts above

On my Lisa, 14.0.10 works fine Since I had a brick with another ROM, I made a clean install two months ago

Xiaomi.eu is custom ROM custom ROMs are not certified custom ROMs can be flashed only with unlocked Bootloader banking apps will detect sooner or later if you want to avoid any 'root detection' you should flash stock ROM and relock bootloader I hope you understood I tried to use your style no...

If you delete Data for Google Play Services and Google Play Store, you will just need to set some things again (like, if you have two Google accounts, which one to be selected for Playstore, if you disabled auto-updates for some apps to disable them again and so). Nothing critical will happen...