GUIDE: Root your Mudita Kompakt and (optionally) install LiteGapps

MuditaOS
24

I honestly forgot which patch I used. All I remember off the top of my head was I think I first downloaded microg from fdroid. It might have been this one.. GitHub - KOWX712/PlayIntegrityFix: Fix Play Integrity verdicts. · GitHub
I sold my modded Mudita Kompakt otherwise I would have checked.

2 Likes
25

It’s called KillApps

2 Likes
26

I just tried this and it doesn’t work unfortunately

1 Like
27

Awesome guide! Thank you for creating such a detailed resource!

2 Likes
28

@gezimos I found a way to fix this! Or at least I can say that Google Play services are working again at the moment; we’ll see if it lasts.

  1. Disable any Play Integrity Fixes and Shamiko. These might make the device look shady to Google.
  2. Remove Google Play Services, Play Store, and Carrier Services from the Magisk DenyList (or just switch off denylist enforcement if you don’t use it for anything else). Since these services are provided by a Magisk module, having them in the denylist will unload the very thing you need!
  3. Register the device at google.com/android/uncertified. This is a form that tells Google “I know my phone isn’t certified; let me in anyway!” It will give you an ADB command to retrieve your GSF ID, and then you paste it into the form and submit.
  4. Force a check-in: adb shell su -c “am broadcast -a android.server.checkin.CHECKIN”
  5. Clear the cached verdict. Play services caches the “uncertified” answer and keeps showing the block after registration works:
    adb shell su -c “rm -f /data/data/com.google.android.gms/files/gmscompliance/shared/cache.pb”
    adb shell su -c “rm -rf /data/data/com.android.vending/cache/*”
  6. Force stop Play Store and Play Services, then reopen the Play Store to see if the block has been removed. You may need to wait a while for this to propagate and/or force another check-in after a while.
  7. If you clear your Google Services Framework data for some reason, you will need to re-register as this changes your device ID and voids the registration.
2 Likes
29

See my comment above for how to fix this

3 Likes
30

I would like to point out that OTA updates via settings do relock the bootloader, which means that if you update you will need to wipe your phone every update. The workaround I found was that you can intercept the link to the OTA package via logcat and download the OTA ZIP manually. Then you can patch the boot file and run an adb sideload with the patched boot file to keep root.

2 Likes
32

This works for me too thanks a bunch! Hope it continues to work :smiley:

2 Likes