Search results

Magisk 20.4 does not work with Android 11. However, Magisk 21.0 is imminent!

The instructions on Page 1 have evolved over time! Flashing Persist.img was one way to get SafetyNET to work... BUT NOT the only way. However, this method had the unfortunate side effect of downgrading Widevine to level 3. If you read the full thread, then it should have been obvious !

The safe way to get onto Xiaomi.eu ROM from stock, is to get the latest published Fastboot ROM from the link on the first page and follow the instructions. Once on that, you can install TWRP and then the latest ZIP ROM from: https://androidfilehost.com/?fid=8889791610682941542 See this thread...

If you are using your own USB cable, then make sure that it is rated for at least 5A. Avoid cheap cables!

There may not be another Fastboot version, now that a stable TWRP is available. This is what typically happens with Xiaomi.eu ROM releases. Fastboot is phased out in favour of TWRP. Less work for the Devs, I guess. P. S. Don't get obsessed with "official" TWRP as the unofficial ones are often...

If you want the latest version, then TWRP is your only choice as the Fastboot version was withdrawn. TWRP does work with this phone, BTW. https://xiaomi.eu/community/threads/custom-twrp-3-4-1b-for-redmi-note-9-pro-joyeuse.56896/

AFAIK, bootloader MUST be unlocked prior to installing any custom ROM, Xiaomi.eu included. You are correct in your assertion that TWRP is not required, if you use the Fastboot ROMs. Seven day wait is normal for unlocking Xiaomi phones... no idea why though !

Basically, just hide everything with Google in its name, apps and services, with Magisk Hide. Then SafetyNet should pass. Does for me.

The assumption here is that you know how to use TWRP. However, as there is a first time for everyone, you must always grant TWRP full write access to your phone, otherwise it cannot work!

Yes I did. However, I made sure that TWRP was prompting me for my PIN and decrypting the file system correctly BEFORE flashing the ROM. I am guessing that you missed the vital "reboot back into TWRP" step?

Flashing persist.img is not required and is bad advice, IMHO. Really, it should be removed as a suggestion in the instructions.

Sorry, this has nothing to do with TWRP installation, which works fine. It is more to do with the Magisk fingerprint mod and its effect upon Play Protect Certification within Google Play Store. I was expecting my device to show "Certified", rather than "Not Certified". Probably not a question...

No idea... but it did! Luckily I had my son's phone to refer to. Magisk Props instructions are excellent, BTW, however, my RN9P-EU is still not certified on PlayStore. Is this expected, or will it resolve itself after a while, say overnight? In any case, I am very pleased to be back in full...

Just to confirm that I have successfully upgraded from V11.0.4.0 (EU fastboot) to V11.0.5.0 (EU recovery) WITHOUT any need to format Data. So all apps and settings are retained. I knew that this was going to work because TWRP prompted me for my PIN when entering after the first reboot back...

Do all versions of Joyeuse use the same screen manufacturer? I seem to recall a similar TWRP issue discussed on XDA for Curtana.

Indeed, but at least these guys actually own this phone model and have tried it, successfully, themselves.

You read my mind. I'll give it a go this weekend... As no one has mentioned a full ROM restore using this LR-TWRP, I presume that no one has attempted one yet?

Backup AND restore?

Please publish a fastboot version for the latest Redmi Note 9 Pro EU ROM (v11.0.5.0)

You can use fastboot to install the Xiaomi.eu stable ROM for Joyeuse. That's what I'm using at the mo. It's OK, but it fails SafetyNet.