pndwal

> Doesn't it also trigger Magisk through the safe mode prop being set? What prop is MIUI using? Maybe this part can be resolved that way. Not sure about props...

Well done! I've fielded countless examples of this/similar issue in XDA Magisk discussion thread, so know it's actually a widespread issue affecting many devices... Here's a little strategy I posted...

Same random occurrences observed... Successfully taking Hide the Magisk app (without any user intervention) occurs possibly less than 50% of the time for me... Another issue, ie. failure to update...

Seems your previous issue https://github.com/topjohnwu/Magisk/issues/6061 was 'fixed' by merging this: https://github.com/topjohnwu/Magisk/pull/6040 I don't fully understand why it 'fixed' your issue initially, but notice that the statement "With Android 13 GKI...

> My device has nothing related to GKI or vendor_boot ... And yet it seems that fix worked initially for you... Anyway, I have only a fundamental understanding of Google...

Guess this shouldn't be called 'Universal Play Integrity Fix' as clearly we can't make strongIntegrity verdict pass... Changed issue description to reflect that proposed fix is really a 'Universal deviceIntegrity...

> https://github.com/topjohnwu/Magisk/blob/fe6b658c028e30f2972dd854b02ef2dd9a99d5b7/docs/install.md?plain=1#L128 > > Nothing to do with Magisk, we can't fix odin's issues. What about: > * I flashed always ALL 4 binaries... > * I ALWAYS transfer files...

I can confirm that the issue was NOT fixed... Sorry i'd missed this request... I did put some comments re. Shana's fix and why I was also sceptical that it...

> @pndwal, how about booting into recovery, selecting safe mode, and rebooting into normal mode? Sadly that can't work on either of my devices... Neither Mi Pad 4 w/ LOS...

> This is not possible, magisk must disable modules before system service starts. Therefore the key press must be detected earlier than system. Sorry, is neither alternative I suggested possible?......