Related
Hey everyone, I had ADT in my shop earlier today installing a security system. It comes with an app they call ADT Pulse which lets me arm/disarm/receive alerts/update profiles/all the usual stuff you'd expect. The problem is for some ridiculous reason it's checking for root and I don't know why but Magisk Hide isn't able to hide it.
Are there any other options I have on this one? (attached a couple screenshots)
Thanks everyone.
Does your phone pass safetynet? If so, it could be detecting magisk which you could repackage to a random name
Are you running a custom kernel with the unlocked bootloader flag patched ?
While you certainly can post for help here, you're probably better off posting in the Magisk General Support Discussion thread. The most basic of questions is whether you're passing SafetyNet.
krash2k said:
Hey everyone, I had ADT in my shop earlier today installing a security system. It comes with an app they call ADT Pulse which lets me arm/disarm/receive alerts/update profiles/all the usual stuff you'd expect. The problem is for some ridiculous reason it's checking for root and I don't know why but Magisk Hide isn't able to hide it.
Are there any other options I have on this one? (attached a couple screenshots)
Thanks everyone.
Click to expand...
Click to collapse
i had an app that magisk hide wasn't working with (i think it was concur or thinkorswim or an auth/2step app). also have patched kernel (flash 1.06) and passing safety net
i added the following to magisk hide and it started working. don't know which one did the trick, just added several to try, but haven't experienced any problems in over a month so i left em all added
android services library
android shared library
android_auto_generated_rro_....
chrome
come.google.android.gms.setup
device configuration
google connectivity services
google partner setup
google services framework
google support services
intent filter verification service
keep
key chain
Hey everyone sorry I wasn't getting alerts that there were responses here.
Magisk says:
SafetyNet Check Success
ctsProfile: true
basicIntegrity: true
I am not running a custom kernel.
Does your phone pass safetynet? If so, it could be detecting magisk which you could repackage to a random name
Click to expand...
Click to collapse
When I read this I remembered seeing a setting in Magisk to repackage itself so I went in and did that without expecting it to be that easy of a fix. Turned out that it was!
Problem solved, many thanks as always for the input here.
Hello I want to play this game but I can't because it force closes. I don't have root I only have custom rom because I don't like miui. Can I bypass it? What are the possible solutions?
The Custom ROM in use may contain a rooted Android. Check this with
Root Validator (Android)
Manage your root installation
root-validator.en.uptodown.com
Lupa031 said:
Hello I want to play this game but I can't because it force closes. I don't have root I only have custom rom because I don't like miui. Can I bypass it? What are the possible solutions?
Click to expand...
Click to collapse
Is your device passing SafetyNet? And even if you get a visual pass that may not be sufficient. You need to:
- Install LSPosed/Xprivacy and run the latest SafetyNet FIX patch for Magisk and complete the process for hiding root.
- Add the game itself in LSPosed too and block tracking too to isolate it
- Clear cache+data and possibly do a clean re-install
That should in principle do it. However if the game server has banned you because root was detected you need to spoof the SSAID assigned to the game too.
Andrologic said:
Is your device passing SafetyNet? And even if you get a visual pass that may not be sufficient. You need to:
- Install LSPosed/Xprivacy and run the latest SafetyNet FIX patch for Magisk and complete the process for hiding root.
- Add the game itself in LSPosed too and block tracking too to isolate it
- Clear cache+data and possibly do a clean re-install
That should in principle do it. However if the game server has banned you because root was detected you need to spoof the SSAID assigned to the game too.
Click to expand...
Click to collapse
Hi, where can I find the step by step on those? This is the first time I've heard of LSPosed, Xprivacy, Safety Net Fix patch.
Lupa031 said:
Hi, where can I find the step by step on those? This is the first time I've heard of LSPosed, Xprivacy, Safety Net Fix patch.
Click to expand...
Click to collapse
This is a good guide to what needs to be done:
[2023 FIX] Fix Magisk CTS Profile False Error - Bypass Safetynet
Magisk CTS Profile False Error is now popping up on almost everyone's device since Google made some changes in March. To Bypass Safetynet...
droidholic.com
In addition, add the game to LSPosed as well and block tracking for it in Xprivacy (same steps as done for Google Play Services). And clear cache+data and reset the game after doing above.
If done correctly, there should be no way your game can detect root.
Andrologic said:
Is your device passing SafetyNet? And even if you get a visual pass that may not be sufficient. You need to:
- Install LSPosed/Xprivacy and run the latest SafetyNet FIX patch for Magisk and complete the process for hiding root.
- Add the game itself in LSPosed too and block tracking too to isolate it
- Clear cache+data and possibly do a clean re-install
That should in principle do it. However if the game server has banned you because root was detected you need to spoof the SSAID assigned to the game too.
Click to expand...
Click to collapse
Hello how do I spoof the SSAID? I think my ip is blocked now or something after it's latest update.
Lupa031 said:
Hello how do I spoof the SSAID? I think my ip is blocked now or something after it's latest update.
Click to expand...
Click to collapse
There are different ways and apps to do it, I like using App Manger - you can get it on F-Droid (link below). Stop and Disable the game. Clear cache + data. Then give the game a new SSAID. Reboot. Done. All can be done from App Manager.
Note, this will completely de-link your device and the game and reset everything - as if you're on a new phone. Also, if you haven't fully hidden root from the game/app, you will just get banned again so you want to make sure of that first.
App Manager - Android package manager | F-Droid - Free and Open Source Android App Repository
A full-featured open source package manager for android.
f-droid.org
Saw on reddit that some people have issues with google pay, since the new update added some new checks. So here is what you do:
- Update Magisk to 25.2, Update magisk app to 25.2 as well
- Rename Magisk app if you havent already
- [ OPTIONAL ] Add all google apps on deny list (good practice in case google wants to detect root throught their other apps)
- install these modules: https://github.com/Magisk-Modules-Repo/MagiskHidePropsConf and https://github.com/kdrag0n/safetynet-fix
- then:
step 1.) Download any terminal (I use termux)
step 2.) type SU
step 3.) type props
step 4.) edit device fingerprint
step 5.) follow the onscreen promt
step 6.) once successfully changed, reboot device
optional (i didnt have to but you can try) reset google play, play services and google wallet appdata.
step 7.) enjoy working google wallet.
- Reboot
NOTE: Remeber to clear google wallet just in case.
ANOTHER NOTE: If your device is not on this list: https://github.com/Magisk-Modules-Repo/MagiskHidePropsConf/blob/master/common/prints.sh
then you'll have to manually obtain an old fingerprint for your device, its all on here how to do:
MagiskHidePropsConf/README.md at master · Magisk-Modules-Repo/MagiskHidePropsConf
This tool is now dead... Contribute to Magisk-Modules-Repo/MagiskHidePropsConf development by creating an account on GitHub.
github.com
Enjoy.
EDIT: Alternatively try this:
https://github.com/Displax/safetynet-fix/releases/
it wont work for all from what I know but it was successful for some.
I only had to update magisk then add Wallet to the deny list.... Haven't tested an actual payment yet, but it stopped complaining about root when I open it.
I probably already had some of those modules installed from before. Some of the names look familiar.
Tried it at McDonald's... Didn't work. I guess the app stops complaining after a few goes of starting it up... Need to check in the "contactless setup" part of the Wallet app to be sure. Has a warning there if your device is "unsafe".
I'll try the full list of steps above tonight and confirm tomorrow if I can pay with it.
ahhh, it was not only with me... going to install to see if it passes...
None of the above works. If you try to pay contactless it will fail. If you try to add card it will fail also. I think that the new google wallet can detect if bootloader is unlocked. I don't see any workaround on this.
covar said:
None of the above works. If you try to pay contactless it will fail. If you try to add card it will fail also. I think that the new google wallet can detect if bootloader is unlocked. I don't see any workaround on this.
Click to expand...
Click to collapse
Yeah I removed Magisk and I still failed. It seems bootloader related I think.
covar said:
None of the above works. If you try to pay contactless it will fail. If you try to add card it will fail also. I think that the new google wallet can detect if bootloader is unlocked. I don't see any workaround on this.
Click to expand...
Click to collapse
works fine for me, I added something you should try as well in case it didnt work for you.
Danishblunt said:
works fine for me, I added something you should try as well in case it didnt work for you.
Click to expand...
Click to collapse
Still nothing. Have you try to make payment????
covar said:
Still nothing. Have you try to make payment????
Click to expand...
Click to collapse
I made 4 payments after the fix, latest being 12 minutes prior to this reply. it works fine.
I suggest starting from my post 1point by point. If it still doesnt work then you may have an app that somehow triggers the root detection that I don't have on my phone.
You should probably mention that picking correct CTS fingerprint is crucial. Sometimes its one version down for your device, but other times you have to use entirely different (but probably related somehow?) device FP, either because prior version doesn't exist, or Google simply doesn't accept it. The Google Pay thread has a scattered reports of working combos somebody should probably make a nicer list of.
I think some steps are not necessary. Like hiding all Google apps and SQ Lite
Also, momo-hider is depreciated. Use shamiko.
Lastly, I just installed magisk hide props (and configured it) and now it works.
Thanks its work✓ !! Is it permanent? Or someday its gonna pop out because some updates?
Magisk user
Paulo_1307_ said:
I think some steps are not necessary. Like hiding all Google apps and SQ Lite
Also, momo-hider is depreciated. Use shamiko.
Lastly, I just installed magisk hide props (and configured it) and now it works.
Click to expand...
Click to collapse
You are correct. The only thing to do is to configure props. I personally change the fingerprint and now works fine.
Paulo_1307_ said:
I think some steps are not necessary. Like hiding all Google apps and SQ Lite
Also, momo-hider is depreciated. Use shamiko.
Lastly, I just installed magisk hide props (and configured it) and now it works.
Click to expand...
Click to collapse
You're right, just listed old modules i gathered over time just in case without testing if they are needed anymore. Tested if they were needed and indeed, they arent.
Hiding the google apps is a good idea regardless if its needed or not.
Fixed the original post to reflect the changes.
Danishblunt said:
Saw on reddit that some people have issues with google pay, since the new update added some new checks. So here is what you do:
- Update Magisk to 25.2, Update magisk app to 25.2 as well
- Rename Magisk app if you havent already
- [ OPTIONAL ] Add all google apps on deny list (good practice in case google wants to detect root throught their other apps)
- install these modules: https://github.com/Magisk-Modules-Repo/MagiskHidePropsConf and https://github.com/kdrag0n/safetynet-fix
- then:
step 1.) Download any terminal (I use termux)
step 2.) type SU
step 3.) type props
step 4.) edit device fingerprint
step 5.) follow the onscreen promt
step 6.) once successfully changed, reboot device
optional (i didnt have to but you can try) reset google play, play services and google wallet appdata.
step 7.) enjoy working google wallet.
- Reboot
NOTE: Remeber to clear google wallet just in case.
ANOTHER NOTE: If your device is not on this list: https://github.com/Magisk-Modules-Repo/MagiskHidePropsConf/blob/master/common/prints.sh
then you'll have to manually obtain an old fingerprint for your device, its all on here how to do:
MagiskHidePropsConf/README.md at master · Magisk-Modules-Repo/MagiskHidePropsConf
This tool is now dead... Contribute to Magisk-Modules-Repo/MagiskHidePropsConf development by creating an account on GitHub.
github.com
Enjoy.
Click to expand...
Click to collapse
hi may I ask what does step 5 mean? Thanks!
darkhunter9 said:
hi may I ask what does step 5 mean? Thanks!
Click to expand...
Click to collapse
baisically just means follow instructions on your screen.
Paulo_1307_ said:
I think some steps are not necessary. Like hiding all Google apps and SQ Lite
Also, momo-hider is depreciated. Use shamiko.
Lastly, I just installed magisk hide props (and configured it) and now it works.
Click to expand...
Click to collapse
Can confirm this works
I had both GPay and Wallet installed on my Pixel 5; yesterday I got the "security requirements" notification.
I've now removed both apps. When I tap on the GPay tile in Quick Settings, it says "Hold to reader", but when I tap Show All, it says "Not set up". I'll test it later today.
Does anyone know how to clear cache for embedded GPay?
V0latyle said:
I had both GPay and Wallet installed on my Pixel 5; yesterday I got the "security requirements" notification.
I've now removed both apps. When I tap on the GPay tile in Quick Settings, it says "Hold to reader", but when I tap Show All, it says "Not set up". I'll test it later today.
Does anyone know how to clear cache for embedded GPay?
Click to expand...
Click to collapse
It will show an error when you try to do a transaction if you havent done the above. Minr also showed that it was reafy but when trying to pay it would throw error.
Danishblunt said:
It will show an error when you try to do a transaction if you havent done the above. Minr also showed that it was reafy but when trying to pay it would throw error.
Click to expand...
Click to collapse
I just went to Dollar General and successfully used tap to pay. I do not have either of the discrete apps installed, just embedded GPay.
Danishblunt said:
Saw on reddit that some people have issues with google pay, since the new update added some new checks. So here is what you do:
- Update Magisk to 25.2, Update magisk app to 25.2 as well
- Rename Magisk app if you havent already
- [ OPTIONAL ] Add all google apps on deny list (good practice in case google wants to detect root throught their other apps)
- install these modules: https://github.com/Magisk-Modules-Repo/MagiskHidePropsConf and https://github.com/kdrag0n/safetynet-fix
- then:
step 1.) Download any terminal (I use termux)
step 2.) type SU
step 3.) type props
step 4.) edit device fingerprint
step 5.) follow the onscreen promt
step 6.) once successfully changed, reboot device
optional (i didnt have to but you can try) reset google play, play services and google wallet appdata.
step 7.) enjoy working google wallet.
- Reboot
NOTE: Remeber to clear google wallet just in case.
ANOTHER NOTE: If your device is not on this list: https://github.com/Magisk-Modules-Repo/MagiskHidePropsConf/blob/master/common/prints.sh
then you'll have to manually obtain an old fingerprint for your device, its all on here how to do:
MagiskHidePropsConf/README.md at master · Magisk-Modules-Repo/MagiskHidePropsConf
This tool is now dead... Contribute to Magisk-Modules-Repo/MagiskHidePropsConf development by creating an account on GitHub.
github.com
Enjoy.
Click to expand...
Click to collapse
Even tho Xiaomi Mi 11 Lite 5g (European version) is not on either list, I got Google Wallet to play nicely (ie work! ) using this guide. In effect the Xiaomi Mi 11 Lite Indonesia Xiaomi:M2101K9AG must have similar coding to Xiaomi M2102K9G. I am now on 13.0.6 SKIEUXM MIUI version. I was worried in the termux app re warnings about ensuring device fingerprint is compatible etc, but when I got the sae warning in adb shell command within minimal adb & fastboot command, I decided to see what happens and it all worked for me. Have carried 2 transactions within Google wallet over yesterday & today with complete success. My device was already certified within Play protect part of Google Play Store.
So I have rooted phone with Magisk 25.2 version, zygisk and deny list set up ; magisk hidden (Hide) then froze Magisk Hide within SD Maid so my fully rooted phone runs Ad Away, no ads & all my banking apps eg Santander & Halifax work fine, so root is hidden from them. Given up trying to get Chase banking app tho
Hi guys. Does anyone have any step by step guide on how to root the Mix Fold 2 and add the Global ROM-ify?
I can't pair my Galaxy watch 4 classic due to region lock and saw global ROM-ify may be the only way.
Any help would be much appreciated as I've never rooted a phone before.
Thanks
The first step is to install "Minimal ADB and Fastboot"on your desktop computer: https://www.gadgetsdr.com/minimal-adb-and-fastboot-tool/
The second step is to unlock the bootloader on your phone. The third step is to install Magisk, which provides seemless root that allows root to hide from banking apps, etc., and the fourth step is to install various modules for Magisk, such as AndroPlus's CN-Global module.
To begin read this guide to unlocking your device:
Xiaomi Community
c.mi.com
Once you have completed the preliminary steps in this guide Xiaomi will assign a one week waiting period before you can unlock. Be patient. If you try before your waiting period expires you will be assigned another waiting period.
Once you have unlocked your bootloader and are ready to root, you can follow these instructions (for devices with RamDisk A/B slots) written by the author of Magisk: https://topjohnwu.github.io/Magisk/install.html
Thank you. I will take a look and give it a shot
Is it possible to use banking apps after rooting the device?
Yes. Install the Universal SafetyNet module and turn on Zygisk in Magisk settings and add Google Services, Google Play Store, Google Wallet, and each of your banking apps to the Zygisk deny list.
frcraig said:
Yes. Install the Universal SafetyNet module and turn on Zygisk in Magisk settings and add Google Services, Google Play Store, Google Wallet, and each of your banking apps to the Zygisk deny list.
Click to expand...
Click to collapse
Is there any tutorials online for this?
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