[APP] microG GmsCore - lightweight free software clone of Google Play Services

[kurtn]

I used this one "https://github.com/lineageos4microg...ofing_patches/android_frameworks_base-R.patch"
It seems to work ok? According to the spoofing checker and microg both of which report that signature spoofing is supported.

All spoofing related boxes have to be checked in microG

And delete signal app data.

 

[wombatch]

All spoofing related boxes have to be checked in microG

And delete signal app data.

they are all ticked, i'll try deleting the app and all the data and see what happens, thank you.

 

[ale5000]

You also need FakeStore and a proper sysconfig file to work rebliably.

To note: the installers exists because 9 time out of 10 people do errors when doing things at hand.

 

[wombatch]

You also need FakeStore and a proper sysconfig file to work rebliably.

To note: the installers exists because 9 time out of 10 people do errors when doing things at hand.

A proper sysconfig file? where is this documented?
Why would I want to use an installer that does a whole load of other things?
also I see that this patch "https://github.com/lineageos4microg...es/packages_apps_PermissionController-R.patch" exists too, do I need that as well?

 

[ale5000]

A proper sysconfig file? where is this documented?
Why would I want to use an installer that does a whole load of other things?
also I see that this patch "https://github.com/lineageos4microg...es/packages_apps_PermissionController-R.patch" exists too, do I need that as well?

They are a whole load of other needed things (in most cases).
If you are talking about additional apps, in most cases there are options to exclude them.
Also all installers that I know are open source.

You can see an example of the sysconfig here.
You can skip the parts about apps that you don't have installed.
The file come from real life use, I'm not sure if it is documented properly, it is just used to lift some limitation of newer Android versions.

The patch you linked is related to signature spoofing patch (and it isn't the complete one, the complete one is here), in most cases it is simpler to get a ROM that already include it.

 

[ale5000]

Hi,
I have created a script to automatically generate a device profile (usable by microG) from a device connected via adb: https://github.com/micro5k/microg-unofficial-installer/blob/main/utils/profile-generator.sh
Only adb and a device are needed (on Windows you also need busybox to execute the script).

I would like a feedback from all interested people.

PS: It can create a profile from most devices and even emulators but it only make sense to create a profile from devices that pass SafetyNet.

 

[AnonVendetta]

Hi,
I have created a script to automatically generate a device profile (usable by microG) from a device connected via adb: https://github.com/micro5k/microg-unofficial-installer/blob/main/utils/profile-generator.sh
Only adb and a device are needed (on Windows you also need busybox to execute the script).

I would like a feedback from all interested people.

PS: It can create a profile from most devices and even emulators but it only make sense to create a profile from devices that pass SafetyNet.

Where/how would I "feed" this profile to MicroG?

 

[ale5000]

- Connect that phone (that pass SafetyNet) that you want to profile to the pc
- Run this on the pc:

sh ./profile-generator.sh > profile-name.xml

- Transfer the file

profile-name.xml

to the phone
- Choose it from microG settings => Google device registration => Import custom profile

 

[kurtn]

- Connect that phone (that pass SafetyNet) that you want to profile to the pc
- Run this on the pc:

sh ./profile-generator.sh > profile-name.xml

- Transfer the file

profile-name.xml

to the phone
- Choose it from microG settings => Google device registration => Import custom profile

And that cheats safetynet attestation into a phone without GApps or magisk or ih8sn?

 

[AnonVendetta]

- Connect that phone (that pass SafetyNet) that you want to profile to the pc
- Run this on the pc:

sh ./profile-generator.sh > profile-name.xml

- Transfer the file

profile-name.xml

to the phone
- Choose it from microG settings => Google device registration => Import custom profile

Do you think the busybox package offered in Cygwin's repository, will work as well in place of/instead of what you linked?

Edit: Not sure if this will work on a Note 20 Ultra 5g/Tab S7 Plus 5g, that only has an unlocked bootloader, but is otherwise currently bone stock (not rooted, no custom recovery, etc). If both pass SN, I'll try the script. If not, I'll relock the bootloader to see if that changes anything. Knox is permanently tripped on both, that isn't reversible no matter what, not sure if it affects SN status.

Edit #2: Everything passes except CTS profile. I'm on the latest stock with no modifications, so it must be the bootloader.

 

[ale5000]

And that cheats safetynet attestation into a phone without GApps or magisk or ih8sn?

The requisite to pass is that your device doesn't have hardware attestation or that the ROM block hardware attestation for SafetyNet (there are patches available and some ROMs already include them).

After this you mainly need to spoof info (with device profiles) in one of the way:
- Create a profile from a device that pass SafetyNet and doesn't physically have hardware attestation: you can use it directly;
- Create a profile from a device that pass SafetyNet and does have hardware attestation: you need to add a space in the model name and then you can use it.

 

[AnonVendetta]

The requisite to pass is that your device doesn't have hardware attestation or that the ROM block hardware attestation for SafetyNet (there are patches available and some ROMs already include them).

After this you mainly need to spoof info (with device profiles) in one of the way:
- Create a profile from a device that pass SafetyNet and doesn't physically have hardware attestation: you can use it directly;
- Create a profile from a device that pass SafetyNet and does have hardware attestation: you need to add a space in the model name and then you can use it.

Need more clarification. So the steps are?:
1. Generate profile while SN fully passes
2. Once the profile file is generated, literally add a space in the model name of the file, like SM-N986N would become SM- N986N(?)
3. Import into microg

My intention is to generate the profile on stock rom, then use it with MicroG running on a custom gsi rom

I can already pass SN with Magisk and a few modules, but I'd like to find a way to fully pass without needing root stuff. So basically, unlocked bootloader + gsi + MicroG + no Magisk

 

[ale5000]

Need more clarification. So the steps are?:
1. Generate profile while SN fully passes
2. Once the profile file is generated, literally add a space in the model name of the file, like SM-N986N would become SM- N986N(?)
3. Import into microg

My intention is to generate the profile on stock rom, then use it with MicroG running on a custom gsi rom

I can already pass SN with Magisk and a few modules, but I'd like to find a way to fully pass without needing root stuff. So basically, unlocked bootloader + gsi + MicroG + no Magisk

The space thing is explained better here:
https://github.com/ProtonAOSP/android_frameworks_base/commit/a99ac1b48a9b

The ROM patch is explained here:

keystore: Block key attestation for SafetyNet · ProtonAOSP/[email protected]

SafetyNet (part of Google Play Services) opportunistically uses hardware-backed key attestation via KeyStore as a strong integrity check. This causes SafetyNet to fail on custom ROMs because the ve...

github.com

PS: I can't test this thing specifically since my device doesn't support hardware attestation so I don't have any problem.

 

[ale5000]

Do you think the busybox package offered in Cygwin's repository, will work as well in place of/instead of what you linked?

The script is "almost" POSIX-compliant with just minor exceptions, hopefully it will works in all shells.

 

[AnonVendetta]

The script is "almost" POSIX-compliant with just minor exceptions, hopefully it will works in all shells.

I intend to run it in Linux anyway, even though I dualboot Windows 10 and several Linux distros.

 

[AnonVendetta]

The space thing is explained better here:
https://github.com/ProtonAOSP/android_frameworks_base/commit/a99ac1b48a9b

The ROM patch is explained here:

keystore: Block key attestation for SafetyNet · ProtonAOSP/[email protected]

SafetyNet (part of Google Play Services) opportunistically uses hardware-backed key attestation via KeyStore as a strong integrity check. This causes SafetyNet to fail on custom ROMs because the ve...

github.com

PS: I can't test this thing specifically since my device doesn't support hardware attestation so I don't have any problem.

Still need more clarification on the space. I've checked the github link. I'm not sure if the space goes in the name of the generated profile file. Or if the file is meant to be edited, with a space added somewhere inside it. Can you give an actual example of without space vs with space?

How to check whether the device supports hardware attestation? I'm still running the stock firmwares. I also relocked the bootloaders, SN does now fully pass on both devices. I'm sure that they do support attestation, since they're not ancient, but I'd like to check. Both are currently running stock Android 13.

 

[ale5000]

Still need more clarification on the space. I've checked the github link. I'm not sure if the space goes in the name of the generated profile file. Or if the file is meant to be edited, with a space added somewhere inside it. Can you give an actual example of without space vs with space?

I cannot test it but it should be like this, from:

<data key="Build.MODEL" value="SM-N986N" />

to:

<data key="Build.MODEL" value="SM-N986N " />

 

[ale5000]

How to check whether the device supports hardware attestation? I'm still running the stock firmwares. I also relocked the bootloaders, SN does now fully pass on both devices. I'm sure that they do support attestation, since they're not ancient, but I'd like to check. Both are currently running stock Android 13.

Run this app and check if it say HARDWARE_BACKED or BASIC.

 

[AnonVendetta]

Run this app and check if it say HARDWARE_BACKED or BASIC.

For both of my devices, it says HARDWARE_BACKED.

 

[ale5000]

For both of my devices, it says HARDWARE_BACKED.

Then they both support hardware attestation.