I got my phone (SM-G950F a.k.a Samsung Galaxy S8) rooted about a year ago or so...and since, i update MM whenever needed but this time when i tried to update it, it says this:
Unsupported Magisk Version
This versio of Magisk Manager does not support Magisk version lower than v18.0
You can either manually upgrade Magisk, or downgrade the app to an older version.
I cannot go into the app cause that message will pop up and after i press ok it closes by itself!
Any ideea on how to fix this? If i have to re-root the phone please do explain..even then i didn't knew for sure how i did it, but i did it..
Thanks in advance!
Ahh... Me too. I'm sure this somewhere in the extensive Magisk coverage here. Is it too lazy to ask for a pointer to how to
--- downgrade the manager? That's probably easy if I know where to get the apk. Which version should I go for?
--- install the new magisk over the existing version, preferably without wiping the phone?
Sure, I'll search. But it is quite a while since I did anything with magisk, or anything that involved flashing, and I feel a bit lost.
Thad E Ginathom said:
Sure, I'll search. ... ... ...
Click to expand...
Click to collapse
OK, so there's a wiki and stuff. Whilst being babied would be nice, people have better things to do, and I guess I'll just start in reading that wiki and... stuff.
SOLUTION
Deathnes said:
I got my phone (SM-G950F a.k.a Samsung Galaxy S8) rooted about a year ago or so...and since, i update MM whenever needed but this time when i tried to update it, it says this:
Unsupported Magisk Version
This versio of Magisk Manager does not support Magisk version lower than v18.0
You can either manually upgrade Magisk, or downgrade the app to an older version.
I cannot go into the app cause that message will pop up and after i press ok it closes by itself!
Any ideea on how to fix this? If i have to re-root the phone please do explain..even then i didn't knew for sure how i did it, but i did it..
Thanks in advance!
Click to expand...
Click to collapse
Delete the Magisk Manager app as you would do with any other, download the proper version in .apk (check the official thread) and install it.
In the thread, under Sources, you have the link to the GitHub repo. Scrolling down you will find the README.MD file and the link to the Downloads page where all past releases are available.
From https://www.xda-developers.com/how-to-install-magisk/ you can read:
The Magisk framework is now installed on your device. To manage it, you’ll need the aptly named Magisk Manager. This is what will allow you to install modules. Download the latest Magisk Manager APK here and make sure you have “Unknown sources” enabled in the Settings. Install the app and open it up.
The Manager app allows you to adjust root settings and also install modules, which are installable mods. The app doubles as a repository for a bunch of great modules that can easily extend the functionality of your device. Using the Manager app is an important part of getting the most out of this root method.
Click to expand...
Click to collapse
That is, the app Magisk Manager is independent from the Magisk framework you have installed. Deleting the app does not affect Magisk.
vomae said:
... ... ... the Downloads page where all past releases are available.
Click to expand...
Click to collapse
I'd reached there, although not done it yet. As you say, my phone is still working, Magisk is still working, it is just the manager app that needs dealing with. None the less, I appreciate your time and effort. You paint a clear picture for others who come this way.
Thanks.
Open the updated app & ignore the error, then checkout the option showing update magisk(not manager), go for it, dont select any preservations & click on direct install(which is recommended by app itself).
Flashing of the update will begin, then after reboot your problem is solved.
Magisk Manager has many improvements and features over the last year...
Hello I'm looking for information on what current magisk version that is available for Google pixel in the latest magisk manager any help thank you I'm trying to gain root and safety-net pass I tried googling but no real clear answers and I'm not locked down to a carrier on device it's all from Google just confused I flash rom and throw through twrp and I need root
I'd say just flash latest stable magisk, that's all I've ever done (not currently rooted) and it's usually worked perfectly. If in doubt it could be worth a look through the magisk discussion thread for any info. Last time I used it it had to be flashed after ROM and gapps and after you had first booted into system at least once, not sure on the safety test bit as it don't bother me but there are magisk modules or edits to the buildprop that can get round that.
Hope that's some help mate
Here what's going on and I'm looking for help
There are magisk modules that will resolve that, If I remember right it's a build fingerprint issue so if the ROM build fingerprint don't match what's on Google's approved list you get that occur.
Can't remember the module names but it's something along the lines of props config or safetynet pass or similar named modules
i want to say thank you for that push i know what you mean now and i really thank you
https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228
"Can't load Android system" and "Factory data reset" tried and does not work
Hi all,
I bought a Pixel 3a, unlocked the bootloader, upgraded it to Android 10, and then tried to root it with Magisk. I must somehow have missed a step because now the phone only boots to:
Android Recovery
google/sargo/sargo
9/PQ3B.190801.002/5674421
user/release-keys
Use volume up/down and power.
Can't load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device.
Try again
Factory data reset
If I "Try again" I end up in the same place after a long time with the Google logo and a reboot. If I "Factory data reset" I also end up in the same place.
My desktop has adb and fastboot, and was able to access the phone until the failed attempt at rooting. Now it does not detect the phone despite the system "bleeping" as if it has found a new device:
>adb devices
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached
>adb devices
List of devices attached
Is there a way out of this mess?
FD
You're still on P by what recovery says. 0801 image. PQ3B is P. You want QP1A. Please try downloading the recent Q image and follow the official instructions from Google in the link and try again.
https://developers.google.com/android/images
Uzephi said:
You're still on P by what recovery says. 0801 image. PQ3B is P. You want QP1A. Please try downloading the recent Q image and follow the official instructions from Google in the link and try again.
https://developers.google.com/android/images
Click to expand...
Click to collapse
Thank you very much! Using the flash-all script I have managed to get my phone back. I have flashed the original Android 9 the phone came with.
Now, one further question, are there some good (as in unlikely to brick my phone again) instructions on how to root my Pixel 3a? I believe that Android 9 is preferred when using Magisk to Android 10, and I do not mind staying with Android 9, but I would like some instructions on how to root it without bricking it again.
Again, thanks for your prompt reply.
Yours,
FD
Frederick Davies said:
Thank you very much! Using the flash-all script I have managed to get my phone back. I have flashed the original Android 9 the phone came with.
Now, one further question, are there some good (as in unlikely to brick my phone again) instructions on how to root my Pixel 3a? I believe that Android 9 is preferred when using Magisk to Android 10, and I do not mind staying with Android 9, but I would like some instructions on how to root it without bricking it again.
Again, thanks for your prompt reply.
Yours,
FD
Click to expand...
Click to collapse
I followed this guide. it's for a pixel 3 but it's exactly the same for a 3a. There is no TWRP for 10 so doing it this way is the only way for now.
https://android.gadgethacks.com/how-to/root-your-pixel-3-android-10-0200295/
Just use magisk to patch Android 10 boot IMG and Flash it and your rooted on Android 10
Frederick Davies said:
Now, one further question, are there some good (as in unlikely to brick my phone again) instructions on how to root my Pixel 3a? I believe that Android 9 is preferred when using Magisk to Android 10, and I do not mind staying with Android 9, but I would like some instructions on how to root it without bricking it again.
Again, thanks for your prompt reply.
Yours,
FD
Click to expand...
Click to collapse
I have created a (IMHO) very thorough quide on how to root your Pixel 3a. It walks you through rooting with both Android Pie and Android 10 with very clear and precise steps. If you have any questions about it, feel free to post in that thread or reach out to me via a direct message.
There is no limitation on using Magisk or rooting under Android 10. The only thing you cannot do with Android 10 is use TWRP, but that isn't a deal breaker. TWRP is good for making backups of your OS, but as you have found you can still recover from just about any situation using the Google factory images, so while a backup might be beneficial at times, it isn't a necessity. Personally I would definitely recommend using Android 10 because Pie isn't being updated by Google anymore, so you are going to be behind on security updates, etc if you stick with Pie.
Watch this video and you shouldn't have any problems
sic0048 said:
I have created a (IMHO) very thorough quide on how to root your Pixel 3a. It walks you through rooting with both Android Pie and Android 10 with very clear and precise steps. If you have any questions about it, feel free to post in that thread or reach out to me via a direct message.
Click to expand...
Click to collapse
Very detailed indeed, but I still have a question: in your instructions you seem to boot into TWRP to install Magisk, but you do NOT install TWRP itself, just boot it for the installation of Magisk. Is that correct? Why?
sic0048 said:
There is no limitation on using Magisk or rooting under Android 10. The only thing you cannot do with Android 10 is use TWRP, but that isn't a deal breaker. TWRP is good for making backups of your OS, but as you have found you can still recover from just about any situation using the Google factory images, so while a backup might be beneficial at times, it isn't a necessity. Personally I would definitely recommend using Android 10 because Pie isn't being updated by Google anymore, so you are going to be behind on security updates, etc if you stick with Pie.
Click to expand...
Click to collapse
I am going through all this rigmarole to be able to install XPrivacyLua through the Xposed Framework, but the instructions for Xposed (https://www.xda-developers.com/xposed-framework-hub/) seem to indicate you need TWRP as a requisite, hence I think am stuck with Android P (9.0).
On the other hand, I get conflicting information as to whether Xposed for Magisk does (https://www.xda-developers.com/xposed-framework-hub/) or does not (https://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268) pass SafetyNet. Most confusing...
FD
Frederick Davies said:
Very detailed indeed, but I still have a question: in your instructions you seem to boot into TWRP to install Magisk, but you do NOT install TWRP itself, just boot it for the installation of Magisk. Is that correct? Why?
FD
Click to expand...
Click to collapse
There is no need to install or boot into TWRP (btw. there is even no working TWRP for Android 10 yet) to install Magisk. It's sufficents to install Magisk Manager on your phone and patch the boot.img extracted from the factory image. Just follow the instructions which have been quoted here in the thread already.
AndDiSa said:
There is no need to install or boot into TWRP (btw. there is even no working TWRP for Android 10 yet) to install Magisk. It's sufficents to install Magisk Manager on your phone and patch the boot.img extracted from the factory image. Just follow the instructions which have been quoted here in the thread already.
Click to expand...
Click to collapse
Dear AndDisa,
As I said, I am rooting my Pixel 3a because I want to install XPrivacyLua, which requires the Xposed Framework; and to install Xposed with Magisk, it lists TWRP as a pre-requisite (see "Method 2: Magisk" in https://www.xda-developers.com/xposed-framework-hub/). Since it seems there is some kind of reluctance to use/install TWRP in this thread, I am asking why that is so. I understand it is possible to install Magisk without TWRP, I am just asking "why?"
Again, thank you all for your help.
FD
TWRP doesn't work on Android 10 at this point so you can't flash it.
Frederick Davies said:
Dear AndDisa,
As I said, I am rooting my Pixel 3a because I want to install XPrivacyLua, which requires the Xposed Framework; and to install Xposed with Magisk, it lists TWRP as a pre-requisite (see "Method 2: Magisk" in https://www.xda-developers.com/xposed-framework-hub/). Since it seems there is some kind of reluctance to use/install TWRP in this thread, I am asking why that is so. I understand it is possible to install Magisk without TWRP, I am just asking "why?"
Again, thank you all for your help.
FD
Click to expand...
Click to collapse
If you read closely in the guide sic linked, he does state the TWRP method is only for P because you can't use TWRP on 10. It is the way partitions are handled in 10 where you really can't read your internal storage and it would have to require a code rework. Until that's done, no TWRP.
Edit: quote from twrp developer about it. https://twrp.me/site/update/2019/10/23/twrp-and-android-10.html
https://github.com/ElderDrivers/EdXposed/pull/354
https://github.com/ElderDrivers/EdXposedManager/releases
You can flash xposed without TWRP. Just install edxposed by downloading and installing through magisk and install the edxposed manager. You don't need TWRP
Frederick Davies said:
Very detailed indeed, but I still have a question: in your instructions you seem to boot into TWRP to install Magisk, but you do NOT install TWRP itself, just boot it for the installation of Magisk. Is that correct? Why?
FD
Click to expand...
Click to collapse
As other have noted, TWRP does not work with Android 10. However, I also wanted to answer your question because it is valid.....
With Android Pie (9), you cannot permanently install TWRP unless you first flash a custom kernel that supports LZMA compression. Using the stock kernel, you can load TWRP using ADB and use it just like normal, but when you reboot the phone TWRP will not be loaded anymore. My instructions are about rooting the phone and not about installing TWRP permanently on the phone and therefore I provided the simplest method to accomplish that goal.
Most custom kernels have been updated with LZMA support, but you should really read the TWRP thread for more information on how to permanently install TWRP on Android Pie
Dear All,
Thank you for all your help and explanations concerning my questions.
I have now rooted my Pixel 3a running Android 9 following the instructions supplied (no TWRP installation), and It seems that Magisk is installed and happy (at least it thinks it is and FX has root access), but I am afraid that EdXposed and XPrivacyLua are not working as expected.
After Magisk, I installed the "Riru - Core" and "Riru - EdXposed (YAHFA)" modules. I then installed the "EdXposed Framework (YAHFA)" (giving the EdXposed Installer superuser privileges; EdExposed reports it is installed and active), and the XprivacyLua module inside it. But now Magisk complains that the SafetyNet checks are failing (this coincides with installing XPrivacyLua, but it is the only module I have in EdXposed), and XPrivacyLua is not actually blocking anything at all (that is, even when I supposedly block access to some functions, the apps just go ahead and use them).
Why do I get the impression Google does not want people to root their phones?
Yours,
FD
Frederick Davies said:
Dear All,
Thank you for all your help and explanations concerning my questions.
I have now rooted my Pixel 3a running Android 9 following the instructions supplied (no TWRP installation), and It seems that Magisk is installed and happy (at least it thinks it is and FX has root access), but I am afraid that EdXposed and XPrivacyLua are not working as expected.
After Magisk, I installed the "Riru - Core" and "Riru - EdXposed (YAHFA)" modules. I then installed the "EdXposed Framework (YAHFA)" (giving the EdXposed Installer superuser privileges; EdExposed reports it is installed and active), and the XprivacyLua module inside it. But now Magisk complains that the SafetyNet checks are failing (this coincides with installing XPrivacyLua, but it is the only module I have in EdXposed), and XPrivacyLua is not actually blocking anything at all (that is, even when I supposedly block access to some functions, the apps just go ahead and use them).
Why do I get the impression Google does not want people to root their phones?
Yours,
FD
Click to expand...
Click to collapse
It is most certainly the things you have installed that are breaking the SafetyNet check. I don't know anything about XprivacyLua, but I would assume there is a support thread here on XDA for it. I would read that support thread and see if there is a solution to the Safetynet issue.
Dear All,
OK, I have now rooted my Pixel 3a: I am running Android 9, and I flashed Magisk (Magisk Manager version 7.4.0; Magisk version 20.1) without installing TWRP as per the instructions. Then I installed the Riru - Core (version 10) and Riru - Ed Exposed (version 0.2.8_beta) modules, which allowed me to install EdXposedInstaller (version 2.2.5). I am currently running Xposed Framework (version 90.0-0.2.8) with XPrivacyLua (version 1.25).
The result is that XPrivacyLua is working with a few caveats: the SafetyNet Check fails both the ctsProfile and basicIntegrity checks (this is triggered by XPrivacyLua, not (Ed)Xposed), and when I limit access of WhatsApp to the Contacts list, there are constant errors whenever WhatsApp tries to read it (though it seems to work as expected). Also, the Contacts list keeps disappearing from the Contacts app itself, despite WhatsApp actually seeing those contacts in there (go figure).
Other apps that require root (like FX) are working as expected.
In the end, I have decided that since I am not interested in using my mobile for Google Pay, I will have to live with it as it is now, but I have a couple of points for others that may want to follow in my footsteps (this is not necessarily related to the method of rooting; those who helped me here are certainly not at fault for the following):
1. XPrivacyLua is in no way as capable and easy to use as XPrivacy was (XPrivacy is the main reason why I am rooting my phone). If I could install Android 4 on my Pixel 3a, I would do so and go back to XPrivacy (my venerable Nexus 5's second battery is shot, so I had to get new hardware). There is nothing in Android 9 that I actually need that was not there in Android 4.
2. We really need a Nexus Toot Toolkit for Pixel phones. The multitude of versions and steps required in rooting them successfully is too much for those like me who will root their phone for one or two apps and then leave it as it is. I know that these forums are really for tinkerers who want to extract the maximum from their hardware, and hence my point of view is not representative here, but I just want a mobile that will not spy on me, the rest is irrelevant to me.
I guess I will have to open a thread in the XPrivacyLua forums to see if I can sort out my problems, but I would like to thank you all for your help in getting me here and answering my questions (no matter how pointless they may have seemed).
Yours,
FD
Frederick Davies said:
Dear All,
OK, I have now rooted my Pixel 3a: I am running Android 9, and I flashed Magisk (Magisk Manager version 7.4.0; Magisk version 20.1) without installing TWRP as per the instructions. Then I installed the Riru - Core (version 10) and Riru - Ed Exposed (version 0.2.8_beta) modules, which allowed me to install EdXposedInstaller (version 2.2.5). I am currently running Xposed Framework (version 90.0-0.2.8) with XPrivacyLua (version 1.25).
The result is that XPrivacyLua is working with a few caveats: the SafetyNet Check fails both the ctsProfile and basicIntegrity checks (this is triggered by XPrivacyLua, not (Ed)Xposed), and when I limit access of WhatsApp to the Contacts list, there are constant errors whenever WhatsApp tries to read it (though it seems to work as expected). Also, the Contacts list keeps disappearing from the Contacts app itself, despite WhatsApp actually seeing those contacts in there (go figure).
Other apps that require root (like FX) are working as expected.
In the end, I have decided that since I am not interested in using my mobile for Google Pay, I will have to live with it as it is now, but I have a couple of points for others that may want to follow in my footsteps (this is not necessarily related to the method of rooting; those who helped me here are certainly not at fault for the following):
1. XPrivacyLua is in no way as capable and easy to use as XPrivacy was (XPrivacy is the main reason why I am rooting my phone). If I could install Android 4 on my Pixel 3a, I would do so and go back to XPrivacy (my venerable Nexus 5's second battery is shot, so I had to get new hardware). There is nothing in Android 9 that I actually need that was not there in Android 4.
2. We really need a Nexus Toot Toolkit for Pixel phones. The multitude of versions and steps required in rooting them successfully is too much for those like me who will root their phone for one or two apps and then leave it as it is. I know that these forums are really for tinkerers who want to extract the maximum from their hardware, and hence my point of view is not representative here, but I just want a mobile that will not spy on me, the rest is irrelevant to me.
I guess I will have to open a thread in the XPrivacyLua forums to see if I can sort out my problems, but I would like to thank you all for your help in getting me here and answering my questions (no matter how pointless they may have seemed).
Yours,
FD
Click to expand...
Click to collapse
Cool story bro
Hello Everyone,
I recently installed LineageOS 18.1 (build: lineage_kebab-userdebug 11). I have retrieved my Android ID using the ADB commands found here: Device Registration and registered my Android ID a few days ago but Google Play Store still shows: "Device is not certified" under Settings --> About --> Play Protect certification. Is there something I'm doing wrong or something else I need to do in order to get my device certified with Google Play Store?
use magisk hide props config I use the pixel 5 fingerprint and add new props
ro.product.model Pixel 5
ro.product.manufacturer Google
option 5 add those 2 after you change fingerprint you will pass and get stadia discounts just can't run edxposed I do but a few changes in that you fail hope that helps
ecompton59 said:
use magisk hide props config I use the pixel 5 fingerprint and add new props
ro.product.model Pixel 5
ro.product.manufacturer Google
option 5 add those 2 after you change fingerprint you will pass and get stadia discounts just can't run edxposed I do but a few changes in that you fail hope that helps
Click to expand...
Click to collapse
Thank you for the info. So you are saying in order to get my device "certified" with Google Play Store I need to root my device, add new props and change my fingerprint (I assume you mean Android ID)? I'm not sure what you mean by: "stadia discounts" or "edxposed". Also, I do not see where I need to root my device in the LineageOS documentation or the Google documentation so I'm still unclear why this must be done. Does Google block LineageOS devices from getting "certified" or something?
long as you used dual sim oos file to unlock your phone it won't unless you do something like that and Google thinks I have pixel 5 see pics I pass
alteredstate82 said:
Thank you for the info. So you are saying in order to get my device "certified" with Google Play Store I need to root my device, add new props and change my fingerprint (I assume you mean Android ID)? I'm not sure what you mean by: "stadia discounts" or "edxposed". Also, I do not see where I need to root my device in the LineageOS documentation or the Google documentation so I'm still unclear why this must be done. Does Google block LineageOS devices from getting "certified" or something?
Click to expand...
Click to collapse
Unlocking a bootloader breaks SafetyNet passes. This results in the play store as not being certified which usually hides specific apps such as Netflix and some other banking apps and will break them. Magisk is needed to help with spoofing your device to let the play store know your device is certified. Some ROMs have built in patches in which SafetyNet passes fine without root. I believe lineage does not do this with their ROM, so you will need magisk.
This is actually a decent article which describes this if you desire to read it - https://www.hexnode.com/blogs/safetynet-android-security/
azoller1 said:
Unlocking a bootloader breaks SafetyNet passes. This results in the play store as not being certified which usually hides specific apps such as Netflix and some other banking apps and will break them. Magisk is needed to help with spoofing your device to let the play store know your device is certified. Some ROMs have built in patches in which SafetyNet passes fine without root. I believe lineage does not do this with their ROM, so you will need magisk.
This is actually a decent article which describes this if you desire to read it - https://www.hexnode.com/blogs/safetynet-android-security/
Click to expand...
Click to collapse
Okay that makes sense. According to the: Patching Images section of the How to Install Magisk App guide I can install Magisk to the boot ramdisk (see screenshot). However, the LineageOS build I installed does not contain a "boot.img" in the zip file. There is however a "payload.bin" file which according to the: XDA Magisk Installation Guide I need to use "payload-dumper-go" to extract the boot.img from the payload.bin? Does that about sum it up or is there something else I'm missing?
alteredstate82 said:
Okay that makes sense. According to the: Patching Images section of the How to Install Magisk App guide I can install Magisk to the boot ramdisk (see screenshot). However, the LineageOS build I installed does not contain a "boot.img" in the zip file. There is however a "payload.bin" file which according to the: XDA Magisk Installation Guide I need to use "payload-dumper-go" to extract the boot.img from the payload.bin? Does that about sum it up or is there something else I'm missing?
Click to expand...
Click to collapse
Yep. You will need to extract the payload.bin file in which you will use the boot.img, then patch it with magisk, then flash the patched boot.img using fastboot. Then, you will need to use magiskhide to hide magisk itself and use the props spoof module to help with passing safetynet.
I want to say thank you for the help! I successfully installed Magisk and passed the SafetyNet checks! Everything seems to be working good. However, it seems my efforts might be wasted as Magisk is dropping support for hiding root access. This is unfortunate as I have a few job critical apps that will not work unless I hide them from root access in Magisk. Hopefully someone else will pick up the torch and continue development. It's a crime these big tech companies work so hard to prevent us from modifying hardware we own!
Hi, I flashed LineageOS 18.1 to my OnlePlus 8T (KB2003). The device is not rooted.
Since that, he device is no longer Play Protect certified and I am not able to install Netflix or use PayPal anymore.
Therefore I installed Magisk and MagiskHidePropsConf-v6.1.2 and followed the instructions above to change the fingerprint and hopefully hide, that the bootloader is unocked. But the device is still not certified (PayStore App > Settings > Info)
What have I done:
- extracted boot.img from LineageOS payload.bin
- boot.img was patched and fastboot flashed to my device (Patching_Images)
- 2 props added: ro.product.model: "Pixel 5", ro.product.manufacturer: "Google"
Did I forgot something?
But in general, why is it needed to change the fingerprint to Pixel 5? Should not work the default fingerprint of my OnePlus 8T as well?
BR Greg
gregattack said:
Hi, I flashed LineageOS 18.1 to my OnlePlus 8T (KB2003). The device is not rooted.
Since that, he device is no longer Play Protect certified and I am not able to install Netflix or use PayPal anymore.
Therefore I installed Magisk and MagiskHidePropsConf-v6.1.2 and followed the instructions above to change the fingerprint and hopefully hide, that the bootloader is unocked. But the device is still not certified (PayStore App > Settings > Info)
What have I done:
- extracted boot.img from LineageOS payload.bin
- boot.img was patched and fastboot flashed to my device (Patching_Images)
- 2 props added: ro.product.model: "Pixel 5", ro.product.manufacturer: "Google"
Did I forgot something?
But in general, why is it needed to change the fingerprint to Pixel 5? Should not work the default fingerprint of my OnePlus 8T as well?
BR Greg
Click to expand...
Click to collapse
All I needed to do to get Play Protect certified was to change my fingerprint to the OP8T KB2003 fingerprint included in MagiskHide Props Config. No other model spoofing needed.
I am still stuck on Widevine L3, however. Still haven't figured that one out, and may be unrelated.
Did you install and use the Universal SafetyNet Fix module?
If I set the kb2003 OP 8T (EU) fingerprint, it seemed not to work. But I will try again.
Do I need to clear some caches eg: play store, after changing the fingerprint or something else?
cpkelley94 said:
All I needed to do to get Play Protect certified was to change my fingerprint to the OP8T KB2003 fingerprint included in MagiskHide Props Config. No other model spoofing needed.
I am still stuck on Widevine L3, however. Still haven't figured that one out, and may be unrelated.
Click to expand...
Click to collapse
finally I installed Universal SafetyNet Fix and switched to the kb2003 fingerprint and reset all other modification like custom props for the pixel phone. Now it's working. No idea why it fails in previous approach
Strange, on my device. Not on lineage though - I pass safetynet without help from any modules. No props or even USF module. Rooted and bootloader unlocked.
Op8t 5g tmobile.
ykjae said:
Strange, on my device. Not on lineage though - I pass safetynet without help from any modules. No props or even USF module. Rooted and bootloader unlocked.
Op8t 5g tmobile.
Click to expand...
Click to collapse
which image are you using?
I read, that some images like https://evolution-x.org/ pass safetynet out of the box but I did'nt test this.
Finally the unlocked bootloader is the problem.
Mod Note
Closed upon OP request. Solution is in post #3.
Hello,
Ok so i have my Lenovo K33a42 with me, i have rooted it using magisk and installed Pixel Experience (right here). After installing the ROM, i saw i cant pass safety net (cts profile), i ignored it because i dont use any banking apps or such. When i tested safety net again today, i see a weird error saying "Can't access Google Play Services". Help me please. Thanks
Would you like to share your solution with us?
Ah sure,
So i couldnt pass CTS profile before Magisk 24 and after upgrading to Magisk 24 i couldnt pass safetynet at all. So i asked in android's discord and one guy asked me to enable Zygisk and install universal safetynet fix. I did it and i saw now i could pass basic integrity but not CTS profile (Note: my device does not use Hardware backed Attestation). Another guy there asked me to install MagiskHide Props Config module (after installing you have to do "su -c props" in a terminal emulator to do the next steps) and asked me to edit my device fingerprint according to my rom. As i am using Pixel Experience Android 9 i changed my fingerprint to Google Pixel 3 Android 9's. Before rebooting he asked me to enable Force Basic Key Attestation and then my phone automatically rebooted and then boom. I passed safetynet and to see if my device is certified or not i had to clear Google Play Services' data, i did it and after about some hours i checked Play Store and my device was certified. I still can't find Netflix on Play Store idk why. If you guys could help me out?
Thanks