[MODULE] Signature Spoof & Update Location Services (Stock 34.4.A.2.85 Customized_DE)
Magisk Module to Signature Spoof & Update Location Services (Stock 34.4.A.2.85 Customized_DE)
!!!!DISCLAIMER: Please know what you are doing. I take no responsibility for breaking your device you are doing this on your own accord and take full responsibility for whatever happens to your device. This has been tested on my daily phone which has Stock firmware 34.4.A.2.85 (Customized_DE). I also take no responsibility for any other related or unrelated issues in your life that may happen after looking at this disclaimer.
Prerequisites:
Sony Xperia X Compact (F5321)
Magisk 16.0 (may work with 16+ but not tested)
Stock Customized_DE Firmware (v34.4.A.2.85) but may work with other Customized_XX version
TWRP (any version that can flash Magisk Module Scripts)
Install Instructions:
Reboot into TWRP
Flash Magisk Module Script
What To Do If It Didn't Work:
Dont panic. The best part of Magisk is there is low risk with systemless modules.
1.) Reboot into TWRP (with phone off hold power button and volume down)
2.) adb push the Magisk Mount Script (link)
3.) flash Magisk Mount Script
3.) delete the f5321_sigspoof folder
4.) reboot back to previous
Q&A
What does this do?
This module updates the framework.jar, services.jar, ext.jar, and framework-res.apk files through systemless interface to save stock functionality.
How was this accomplished
1.) Latest stock firmware flashed to Sony device F5321 version 34.4.A.2.85 Customized_DE
2.) /system/framework was downloaded and dodexed using Fulmics Deodexer (link)
3.) Deodexed services.jar, framework.jar, ext.jar, some other jars were used in processing with Haystack (link) to create signature spoofing.
4.) Framework-res-overlay was created to support the modifications needed for Location Services to work with MicroG (ref1) (ref2)
5.) Magisk Module template was downloaded and all the files were added to be replaced.
6.) ...
7.) profit
Why would you want this?
Honestly I don't know why you want this but I want this so that I can control and limit the exposure for location based service tracking that happens on my device on a minute by minute basis. MicroG (and by extension) UnifiedNlp allows this through locally stored location service backends. Also, MicroG allows the use of basic google services without sucking my battery dry. Can go ~3 days with light/moderate use. So thats also good.
Why use stock rom and not other custom rom (like OMNIRom)?
OMNIRom is great and amazing but I often find myself addicted to flashing the next best ROM. I also find that the one feature that is fixed in one ROM has two other unstable features that render the phone just barely stable enough for daily use.
reserved ...
JenItols said:
Magisk Module to Signature Spoof & Update Location Services (Stock 34.4.A.2.85 Customized_DE)
.
Click to expand...
Click to collapse
Don't know much about this stuff, but question - flashing module succeeded in checking unlp boxes in Microg settings, but still get no location fix when in battery-saving mode, and GPS apps show 'GPS disabled' . Any ideas? Thanks (latest stock fw... 85)
levone1 said:
Don't know much about this stuff, but question - flashing module succeeded in checking unlp boxes in Microg settings, but still get no location fix when in battery-saving mode, and GPS apps show 'GPS disabled' . Any ideas? Thanks (latest stock fw... 85)
Click to expand...
Click to collapse
Are you using UnifiedNlp.apk or NetworkLocation.apk?
UnifiedNlp.apk package is com.microg.nlp
NetworkLocation.apk package is com.google.android.gms
This fix specifies com.google.android.gms as the network location provider. This means UnifiedNlp isn't specified. I can make a separate version with UnifiedNlp but UnifiedNlp was meant to be used with true GApps like normal google services. One would argue that if you are wanting to use regular google apps then you would use MicroG which allows the use of google apps. MicroG is com.google.android.gms also and provides the UnifiedNlp package built in.
If needed I can create a version of this with UnifiedNlp.apk (com.microg.nlp) as the location provider but I would highly recommend using MicroG if you want to use the location provider along with normal google apps.
Have you configured a location provider backend?
You have to also download and install an additional location provider backend. Additional information/packages can be found here
JenItols said:
Are you using UnifiedNlp.apk or NetworkLocation.apk?
UnifiedNlp.apk package is com.microg.nlp
NetworkLocation.apk package is com.google.android.gms
This fix specifies com.google.android.gms as the network location provider. This means UnifiedNlp isn't specified. I can make a separate version with UnifiedNlp but UnifiedNlp was meant to be used with true GApps like normal google services. One would argue that if you are wanting to use regular google apps then you would use MicroG which allows the use of google apps. MicroG is com.google.android.gms also and provides the UnifiedNlp package built in.
If needed I can create a version of this with UnifiedNlp.apk (com.microg.nlp) as the location provider but I would highly recommend using MicroG if you want to use the location provider along with normal google apps.
Have you configured a location provider backend?
You have to also download and install an additional location provider backend. Additional information/packages can be found here
Click to expand...
Click to collapse
Thanks - I do know enough to configure backend, (I've used microG since a few years ago, but I don't know much technical stuff), but I didn't catch the difference between the two providers. Indeed, mine is org.microg.nlp. Don't go making a new one for me - I can just change it.
Thanks again
JenItols said:
Are you using UnifiedNlp.apk or NetworkLocation.apk?
UnifiedNlp.apk package is com.microg.nlp
NetworkLocation.apk package is com.google.android.gms
This fix specifies com.google.android.gms as the network location provider. This means UnifiedNlp isn't specified. I can make a separate version with UnifiedNlp but UnifiedNlp was meant to be used with true GApps like normal google services. One would argue that if you are wanting to use regular google apps then you would use MicroG which allows the use of google apps. MicroG is com.google.android.gms also and provides the UnifiedNlp package built in.
If needed I can create a version of this with UnifiedNlp.apk (com.microg.nlp) as the location provider but I would highly recommend using MicroG if you want to use the location provider along with normal google apps.
Have you configured a location provider backend?
You have to also download and install an additional location provider backend. Additional information/packages can be found here
Click to expand...
Click to collapse
Seems like the issue is that GMScore has unlp built in, so when installing apps for MicroG, there's no apktool needed for location provider, and trying to install NetworkLocation apktool as an update fails.
(sorry, I just got back around to this...)
JenItols said:
Are you using UnifiedNlp.apk or NetworkLocation.apk?
Click to expand...
Click to collapse
figured it out. ..
**CONTINUE AT YOUR OWN RISK**
**I ASSUME YOU KNOW HOW TO SAFELY NAVIGATE /SYSTEM & ADJUST FILES AND THEIR PERMISSIONS**
This is a write up on how to install and use the stock Google Phone app.
Yes there are simpler ways to achieve something similar. There are a few developers on xda who have patched the Google Phone app so you don't have to do the following.
I personally enjoys the harder things in life. Along with just jumping on Apkmirror and installing any new updates to the phone app without waiting for someone to patch it.
Google Play Store won't allow you to find or update (as far as I know) the Google Phone app unless your phones identifies itself to the store as a pixel. If you did manage to get your hands on the apk it'll fail to install.
(I've seen a few magisk modules that will work)
However thanks to Apkmirror and the opengapps GitHub you could get around this.
First you need to get the files that the Google Phone app requires to be within the /system partition.
com.google.android.dialer.support.xml
com.google.android.dialer.support.jar (I use API 27)
The .xml goes in /system/etc/permissions with root permissions and the .jar goes in /system/Framework also with root permissions.
So either use your favorite root file manager, TWRP, adb, and place the files in their respective location and adjust the permissions. I personally either use TWRP or adb and adjust the permissions via the chmod 0644 command on the files.
Once you have verified the files are where they belong and have the correct permissions. Install the apk, set it as the default phone app and enjoy. (Adjust all permissions to your liking)
https://github.com/opengapps/all/tree/master/
View the code and find the files.
Thank you GitHub, Opengapps, and who ever uploads the files to Apkmirror.
Information I gathered over the years and random old xda threads. Also serves as a post I can reflect back on two months from now when I forget again.
ENJOY and don't do something if you don't understand, accept responsibility for your own actions because I won't for you. Go explore the wonders of learning Linux, and have plenty of backups to fix your non fatal mistakes.
It works great, thanks!
Tachi91 said:
**CONTINUE AT YOUR OWN RISK**
**I ASSUME YOU KNOW HOW TO SAFELY NAVIGATE /SYSTEM & ADJUST FILES AND THEIR PERMISSIONS**
This is a write up on how to install and use the stock Google Phone app.
Yes there are simpler ways to achieve something similar. There are a few developers on xda who have patched the Google Phone app so you don't have to do the following.
I personally enjoys the harder things in life. Along with just jumping on Apkmirror and installing any new updates to the phone app without waiting for someone to patch it.
Google Play Store won't allow you to find or update (as far as I know) the Google Phone app unless your phones identifies itself to the store as a pixel. If you did manage to get your hands on the apk it'll fail to install.
(I've seen a few magisk modules that will work)
However thanks to Apkmirror and the opengapps GitHub you could get around this.
First you need to get the files that the Google Phone app requires to be within the /system partition.
com.google.android.dialer.support.xml
com.google.android.dialer.support.jar (I use API 27)
The .xml goes in /system/etc/permissions with root permissions and the .jar goes in /system/Framework also with root permissions.
So either use your favorite root file manager, TWRP, adb, and place the files in their respective location and adjust the permissions. I personally either use TWRP or adb and adjust the permissions via the chmod 0644 command on the files.
Once you have verified the files are where they belong and have the correct permissions. Install the apk, set it as the default phone app and enjoy. (Adjust all permissions to your liking)
https://github.com/opengapps/all/tree/master/
View the code and find the files.
Thank you GitHub, Opengapps, and who ever uploads the files to Apkmirror.
Information I gathered over the years and random old xda threads. Also serves as a post I can reflect back on two months from now when I forget again.
ENJOY and don't do something if you don't understand, accept responsibility for your own actions because I won't for you. Go explore the wonders of learning Linux, and have plenty of backups to fix your non fatal mistakes.
Click to expand...
Click to collapse
You could use Magisk an PIX3LIFY module, it should do all that for you...
Anyway, does Google Phone work just fine without any crash? Because I have Android Oreo 8.0 on my HTC 10 and I've tried to get Google Phone working but it crashes when you give contacts permissions and access your call history or the dialer keypad. Do you not have these problems on your U12+ with Android Oreo 8.0?
rfgamaral said:
You could use Magisk an PIX3LIFY module, it should do all that for you...
Anyway, does Google Phone work just fine without any crash? Because I have Android Oreo 8.0 on my HTC 10 and I've tried to get Google Phone working but it crashes when you give contacts permissions and access your call history or the dialer keypad. Do you not have these problems on your U12+ with Android Oreo 8.0?
Click to expand...
Click to collapse
Works fine for me, no issues.
In the past ive seen it crash from either wrong file permissions or incorrect framework or xml file.
I changed phone and It works great on the Rog Phone too. No crashes at all.
Hi. Newbie here. Want to install the Google dialer on wife's HTC U12+ but the link is dead? Any assistance would be greatly appreciated. Happy wife happy life?
I've been using Pixel 3 only for two weeks, and haven't understood its security mechanism fully yet.
Usually on other phones, I simply run TWRP and modify hosts to avoid ads. After doing the same on Pixel 3 and booting into system, ads are still there, which means hosts modification didn't work properly.
So I installed Magisk from TWRP, and did the same modification on Android, and I confirmed ads were all gone as usual. Then, I uninstalled Magisk with the modified hosts left in /system/etc, and reboot the system to find ads were all back...
It looks like you need Magisk installed on Pixel 3 to keep system file modifications working. I haven't tried font modifications, but I assume the result would be the same.
Could someone explain to me what causes this system file modifications fail without Magisk installed? A new Pixel-unique system security mechanism?? Thanks in advance!
QT
Does Pixel 3 checks whether system files are signed by Google or not??
qtotter said:
Does Pixel 3 checks whether system files are signed by Google or not??
Click to expand...
Click to collapse
It is my understanding that this mod requires root.
Yes, system files have checks. That's why when you edit system files you use the original signature.
Tulsadiver said:
Yes, system files have checks. That's why when you edit system files you use the original signature.
Click to expand...
Click to collapse
Thanks for your info. Google's security policy is getting tighter...
I'm working on porting "CIT test" application from MIUI to custom Android 11 ROMs (for calibrating proximity and fingerprint sensors), with end goal of creating a Magisk module. I'm stuck now with the application calling android.os.ServiceManager/addService, which fails with SecurityException -- I presume because I removed android:sharedUserId="android.uid.system" from its manifest, so it doesn't run with system app permissions. Currently I place it in /system/priv-app instead, which allows me to give it at least all the manifest permissions that it requires.
AFAIU, there is no way for me to simply use android.uid.system, as it requires one to sign the package with the same keys that were used for the ROM itself. As my idea is to have a general Magisk module, this is out of the question. However, because obviously I expect devices to be rooted (and can require Xposed), I want to find some way of circumventing signature check for this one package. Say, using Xposed to patch signature check, and to allow my public key to be used for android.uid.system apps. I don't want to completely disable signature checks, as this greatly compromises security.
I also thought of somehow using su to run this application as root, but apparently this is also not possible.
Is there a way to do this or something similar? Maybe I miss another way of implementing what I want? Any help or links are greatly appreciated.
I am curious about this too. It would help install the nReal nebula service on non-carrier devices and use nRreal Light AR glasses with the Nebula app.
Re-add the android.uid.system line
disable your Android Signature Verification
install with magisk to /system/app or priv-app
This is a tutorial on how to set up your phone so that you can consistently pass SafetyNet. Note that all this is from my own experience, and if what works on one device blows up another, that's not my problem and I'm not responsible for that. I will attempt to keep this tutorial as clean and simple as possible, but if you have any further questions that are more specific you are welcome to ask.
In order to be as simple as possible to understand, this guide assumes the following:
- You have a PC. Windows, Mac, the almighty Linux, it makes no difference.
- You have the android platform tools on your PC
- Your device has an unlocked bootloader.
- Your device does not have support for signature spoofing.
- Your device does not have Google's official play services on it.
- You have a working brain.
If one or more of the above is incorrect, you'll have to make more use of the last item on the list.
If the last item on the list is incorrect, you're beyond hope.
Now, the guide:
Step 1: Get some magisk on your phone
Setting up magisk is incredibly simple, and I won't be going into detail here. I would recommend installing the regular magisk app and patching your boot image, as that is what I've done.
Note that you do not need the magisk manager app for this guide at all.
I've attached the magisk app I used to this post. You'll need to install the app and make use of the "install" section of the home page.
Once magisk is installed and set up, you'll need to enable zygisk in the magisk settings. Then reboot.
Step 2: Installing MicroG
I am not going to list through all the possible way you can install microG. Instead, have a link to microG's wiki:
index - MicroG
r/MicroG: Subreddit about microG, a free-as-in-freedom re-implementation of Google’s proprietary Android user space apps and libraries. This …
www.reddit.com
Now here comes the important bit:
From everything I have seen, it appears clear that google stores information about each device that registers with it, and that this in turn will affect SafetyNet.
Therefore, the best way to prevent this leading to SafetyNet failing is to prevent connection with google completely - till the phone is ready.
Before you install microG, make sure your phone has both wifi and data turned off. Leave these off till the setup is complete. Note that only the phone needs to be disconnected, nothing else matters.
In essence, this means that google sees nothing till your device is setup correctly, and then SafetyNet has nothing to complain about.
Now that you've read every word of the above paragraph, go ahead and install microG on your phone.
Make sure you've got all the different components: Core, GSF Framework, FakeStore, and DroidGuard helper. If your installation method does not handle all of this for you, then it sucks, and you shouldn't have used it. Regardless, you can find apks for all of these at https://microg.org/
Step 3: Don't touch
As I've already made clear above, do not change any microG settings at this point. Don't enable device registration (if it's disabled), don't enable safetynet, and just generally leave microG settings alone for now. Oh yeah, and don't turn on wifi or data.
Step 4: Tricking SafetyNet
Everything up till now has just been preparation for actually tricking SafetyNet. So now that we've got all that out the way, let's get down to details:
First, downloads:
Download the latest zip: https://themagisk.com/magiskhide-props-config/
Download the latest zygisk zip: https://themagisk.com/universal-safetynet-fix/
Move these over to your phone and install them both as magisk modules.
Once these modules are installed and you've rebooted, connect your phone to your pc.
Open a terminal/command prompt in your platform tools folder, and type "adb shell props". You may need to grant the superuser permission from your phone.
Then choose option 1.
You'll then need to choose a device from the list available.
The key here is that we need to spoof our device fingerprint, so google thinks the device is certified, even if it actually isn't.
If your device is approved by google, then simply select your device model.
If not, things get a bit more unclear. Not every fingerprint will work for every device - If your device is vastly different from the one you are trying to spoof things may not always work correctly. The best advice I can give here is to choose a device that matches yours as closely as possible. As an example: if your device is made by Xiaomi but is not approved by google, I would select a fingerprint belonging to a Xiaomi device.
Keep in mind that if you try a fingerprint that does not work, you cannot simply switch it to something else and try again, as the SafetyNet history for the device has to be clean.
Once you've spoofed your device fingerprint and rebooted, you're almost ready to test out SafetyNet and google sign in. But first:
Step 5: Do you need signature spoofing?
To ensure things work as smoothly as possible, it's important to make sure you have signature spoofing working before you test SafetyNet. If you've got your own solution to that great. If not:
The first thing I have to point out is that a lot of sigspoof methods on google nowadays are outdated and semi-functional at best, working for a handful of devices. As this guide is intended to be a universal solution regardless of your device, the only answer is lsposed and fakegapps.
Download the latest zygisk zip: https://themagisk.com/lsposed/
Transfer it to your phone and install it as a magisk module.
I've attached the full lsposed manager apk to this post, as the parasitic one sucks. Install it and the fakegapps apk which I've also attached to this post.
You'll now need to enable fakegapps, and turn it on for anything that might need access to spoofing. This includes the system framework, all the microG stuff, and any app that needs to be fooled by microg. Then reboot.
Step 6: Ready to test
Everything should now be set up correctly.
Check the microG settings to make sure signatures are correctly being spoofed.
Enable device registration (if disabled).
Enable SafetyNet attestation.
At this point your phone should still be completely disconnected from the internet.
If you're happy everything is set up correctly, turn on your wifi or data, and test SafetyNet attestation.
Step 7: Done.
Hopefully you now have working SafetyNet and google sign in. If this does work for you, it means that safetynet is now stable on your device, and you are free to install whatever you want on it.
If it didn't work, keep in mind that this hasn't been tested on every device in existence. All I know is that this consistently works for me.
If your phone doesn't turn on, you probably need to charge it.
If your phone has exploded, you probably have a Samsung.
Thanks everyone for reading my guide, I hope you enjoyed! (Maybe it even worked)
RESERVED FOR STUFF
Your guide is well made but I have some things I would change.
1) Since everything has to be done offline and adb is used in linux installation at least I would recommend adding an tip with adb push ~/Downloads/safetynet-tools.zip /storage/emulated/0/Downloads.
Furthermore cause of it I recommend attaching a single zip with
tools so they can be moved easily to the device.
2) there is missing Information: you said in the guide that safety net trips extremely easily. During the entire process the device cant be connected to the internet but what if you want to install another app. For example what if you want to install another app later lets say Netflix for example. I know for a fact it requires safetynet. It would be configured automatically will it? This would conclude to permanetley lock safety net till its reinstalled.
hypethetime said:
Your guide is well made but I have some things I would change.
1) Since everything has to be done offline and adb is used in linux installation at least I would recommend adding an tip with adb push ~/Downloads/safetynet-tools.zip /storage/emulated/0/Downloads.
Furthermore cause of it I recommend attaching a single zip with
tools so they can be moved easily to the device.
Click to expand...
Click to collapse
Hi, I think you may have misunderstood slightly. Only the phone has to be offline, you can still connect it to a PC and download the files on the PC. The only important thing is that the device doesn't communicate with google till you are ready for it to.
hypethetime said:
2) there is missing Information: you said in the guide that safety net trips extremely easily. During the entire process the device cant be connected to the internet but what if you want to install another app. For example what if you want to install another app later lets say Netflix for example. I know for a fact it requires safetynet. It would be configured automatically will it? This would conclude to permanetley lock safety net till its reinstalled.
Click to expand...
Click to collapse
Once the process is complete, you can install whatever else you want and safetynet will not stop working. The main thing is that the process of setting up the device so that it can be approved is very easy to mess up, so that part has to be done carefully.
I'll edit the guide to make these points more clear.
Sense_101 said:
Hi, I think you may have misunderstood slightly. Only the phone has to be offline, you can still connect it to a PC and download the files on the PC. The only important thing is that the device doesn't communicate with google till you are ready for it to.
Click to expand...
Click to collapse
I knew you always were able to use pc and you miss understood me. I at least often had the problem with transferring files for some reseason and for this adb push is extremey helpful.
Regarding instaling more apps thank you for the answer and how quickly it came.
Sense_101 said:
This is a tutorial on how to set up your phone so that you can consistently pass SafetyNet. Note that all this is from my own experience, and if what works on one device blows up another, that's not my problem and I'm not responsible for that. I will attempt to keep this tutorial as clean and simple as possible, but if you have any further questions that are more specific you are welcome to ask.
In order to be as simple as possible to understand, this guide assumes the following:
- You have a PC. Windows, Mac, the almighty Linux, it makes no difference.
- You have the android platform tools on your PC
- Your device has an unlocked bootloader.
- Your device does not have support for signature spoofing.
- Your device does not have Google's official play services on it.
- You have a working brain.
If one or more of the above is incorrect, you'll have to make more use of the last item on the list.
If the last item on the list is incorrect, you're beyond hope.
Now, the guide:
Step 1: Get some magisk on your phone
Setting up magisk is incredibly simple, and I won't be going into detail here. I would recommend installing the regular magisk app and patching your boot image, as that is what I've done.
Note that you do not need the magisk manager app for this guide at all.
I've attached the magisk app I used to this post. You'll need to install the app and make use of the "install" section of the home page.
Once magisk is installed and set up, you'll need to enable zygisk in the magisk settings. Then reboot.
Step 2: Installing MicroG
I am not going to list through all the possible way you can install microG. Instead, have a link to microG's wiki:
index - MicroG
r/MicroG: Subreddit about microG, a free-as-in-freedom re-implementation of Google’s proprietary Android user space apps and libraries. This …
www.reddit.com
Now here comes the important bit:
From everything I have seen, it appears clear that google stores information about each device that registers with it, and that this in turn will affect SafetyNet.
Therefore, the best way to prevent this leading to SafetyNet failing is to prevent connection with google completely - till the phone is ready.
Before you install microG, make sure your phone has both wifi and data turned off. Leave these off till the setup is complete. Note that only the phone needs to be disconnected, nothing else matters.
In essence, this means that google sees nothing till your device is setup correctly, and then SafetyNet has nothing to complain about.
Now that you've read every word of the above paragraph, go ahead and install microG on your phone.
Make sure you've got all the different components: Core, GSF Framework, FakeStore, and DroidGuard helper. If your installation method does not handle all of this for you, then it sucks, and you shouldn't have used it. Regardless, you can find apks for all of these at https://microg.org/
Step 3: Don't touch
As I've already made clear above, do not change any microG settings at this point. Don't enable device registration (if it's disabled), don't enable safetynet, and just generally leave microG settings alone for now. Oh yeah, and don't turn on wifi or data.
Step 4: Tricking SafetyNet
Everything up till now has just been preparation for actually tricking SafetyNet. So now that we've got all that out the way, let's get down to details:
First, downloads:
Download the latest zip: https://themagisk.com/magiskhide-props-config/
Download the latest zygisk zip: https://themagisk.com/universal-safetynet-fix/
Move these over to your phone and install them both as magisk modules.
Once these modules are installed and you've rebooted, connect your phone to your pc.
Open a terminal/command prompt in your platform tools folder, and type "adb shell props". You may need to grant the superuser permission from your phone.
Then choose option 1.
You'll then need to choose a device from the list available.
The key here is that we need to spoof our device fingerprint, so google thinks the device is certified, even if it actually isn't.
If your device is approved by google, then simply select your device model.
If not, things get a bit more unclear. Not every fingerprint will work for every device - If your device is vastly different from the one you are trying to spoof things may not always work correctly. The best advice I can give here is to choose a device that matches yours as closely as possible. As an example: if your device is made by Xiaomi but is not approved by google, I would select a fingerprint belonging to a Xiaomi device.
Keep in mind that if you try a fingerprint that does not work, you cannot simply switch it to something else and try again, as the SafetyNet history for the device has to be clean.
Once you've spoofed your device fingerprint and rebooted, you're almost ready to test out SafetyNet and google sign in. But first:
Step 5: Do you need signature spoofing?
To ensure things work as smoothly as possible, it's important to make sure you have signature spoofing working before you test SafetyNet. If you've got your own solution to that great. If not:
The first thing I have to point out is that a lot of sigspoof methods on google nowadays are outdated and semi-functional at best, working for a handful of devices. As this guide is intended to be a universal solution regardless of your device, the only answer is lsposed and fakegapps.
Download the latest zygisk zip: https://themagisk.com/lsposed/
Transfer it to your phone and install it as a magisk module.
I've attached the full lsposed manager apk to this post, as the parasitic one sucks. Install it and the fakegapps apk which I've also attached to this post.
You'll now need to enable fakegapps, and turn it on for anything that might need access to spoofing. This includes the system framework, all the microG stuff, and any app that needs to be fooled by microg. Then reboot.
Step 6: Ready to test
Everything should now be set up correctly.
Check the microG settings to make sure signatures are correctly being spoofed.
Enable device registration (if disabled).
Enable SafetyNet attestation.
At this point your phone should still be completely disconnected from the internet.
If you're happy everything is set up correctly, turn on your wifi or data, and test SafetyNet attestation.
Step 7: Done.
Hopefully you now have working SafetyNet and google sign in. If this does work for you, it means that safetynet is now stable on your device, and you are free to install whatever you want on it.
If it didn't work, keep in mind that this hasn't been tested on every device in existence. All I know is that this consistently works for me.
If your phone doesn't turn on, you probably need to charge it.
If your phone has exploded, you probably have a Samsung.
Thanks everyone for reading my guide, I hope you enjoyed! (Maybe it even worked)
Click to expand...
Click to collapse
I have a Samsung galaxy note 10 plus running LineageOS 19.1. I'ts unlocked, and rooted with Magisk. Is there something about Samsung phones that are more likely to "explode" trying to install MicroG?
WheelingPigeon said:
I have a Samsung galaxy note 10 plus running LineageOS 19.1. I'ts unlocked, and rooted with Magisk. Is there something about Samsung phones that are more likely to "explode" trying to install MicroG?
Click to expand...
Click to collapse
Yeah, that's a joke
WheelingPigeon said:
I have a Samsung galaxy note 10 plus running LineageOS 19.1. I'ts unlocked, and rooted with Magisk. Is there something about Samsung phones that are more likely to "explode" trying to install MicroG?
Click to expand...
Click to collapse
Samsung phones have a history of "blowing" up. First they were actually dangerous in very few cases but now they can expand and pop of the back of your phone. As long as you switch the battery then your safe to use it.
AOSP Rom (signature spoofing unsupported, without MicroG installer)
After Root install patch for spoofing via NanoDroid Patcher
Open Magisk settings -> Enable Zygisk + Enforce DenyList, install module MagiskHide Props Config -> reboot
Open Termux or ADB, type su to set root permission then type props (option 1)
Install MicroG via APK or offical F-Droid app, grant Signature spoofing permission
If you want using play store, install patched version (F-Droid add repo NanoDroid)
Open MicroG Settings -> Self-Check -> make sure all box checked
Turn on Google device registration, Google SafetyNet, if CTS fail then install Universal SafetyNet Fix
Install magisk module App Systemizer, Busybox for Android NDK to change MicroG to system app