Search results

Nice, thanks I'm going to try

I know that MIUI/HyperOS is closed source but I said that because I know xiaomi.eu (and certainly all Chinese MIUI/HyperOS ROMs) is based on AOSP which IS open source so maybe that part of the system could have been open source (and it's not so it's ok)... I'll try to make a magisk module that...

@Igor Eisberg I have found a solution that could satisfy both you and me. See this part of the Tricky Store readme, you can probably add the commit to the ROM (if source built, else idk) and people without root can use your mods and people with root can use Tricky Store.

Well I tried to remove the props and it did not change much do I guess this is not the main cause. Technically, that is not modifying the ROM because it is done systemlessly (so the ROM stays unchanged). Can you at least give an indication on what other modifications has been done please?

@Igor Eisberg I might have found something, in /system_ext/etc/init/, there is a file named init.xeu.ext. rc containing the following: on property:sys.boot_completed=1 exec u:r:init:s0 root root -- /system_ext/xbin/resetprop ro.boot.flash.locked 1 exec u:r:init:s0 root root --...

Did I tell you to give me the source code of your mods? No, that's completely off topic. I don't care that your mods are closed source, that's not my problem. What I care about is the following: Where is your script that does modifications related to play integrity? There is nothing about source...

If that's not being rude, I don't know what is. Also, your assumption is wrong, if I don't know what I'm searching for, I can't find it. And I don't have enough information to find that, all I know is my device doesn't pass strong integrity and I know it should. You're saying there is something...

He kind of is in a way, he could just say what is breaking strong integrity because it seems he knows where the problem comes from instead of saying there is no way to modify init scripts (which is not entirely true).

Can you please tell me which init script(s) modified some props? It can 100% be reverted by a magisk module since magisk has it's own init scripts, so just putting a module that reverts the changes right after the other init script will fix it if that's the issue. Everything is possible. And...

Hey @Igor Eisberg Would it be possible to know what modifications were made that prevents Tricky Store to pass Strong Integrity apart from the disabled app? That would be useful to make a Magisk module that nukes the props for example. Thanks