I have a doubt, I have tried the ROM oos and I love it, but the only negative thing is that after installing it and putting the dfe without root, safetynet does not pass and although it installs magisk hide, and if it passes safetynet but I can not play fortnite, I get out of the game when I jump from the bus, then I tried pixel expirience without installing root too, this ROM passes the safetynet and without doing anything I could play the fortnite, my question is that I see that the customized ROMs can not all be played fortnite, what is the difference between some ROMs and others so that you can play the fortnite, I want to try more ROM, but I do not want to lose the power to play the fortnite, what difference there is between these roms, thanks
luiwii said:
I have a doubt, I have tried the ROM oos and I love it, but the only negative thing is that after installing it and putting the dfe without root, safetynet does not pass and although it installs magisk hide, and if it passes safetynet but I can not play fortnite, I get out of the game when I jump from the bus, then I tried pixel expirience without installing root too, this ROM passes the safetynet and without doing anything I could play the fortnite, my question is that I see that the customized ROMs can not all be played fortnite, what is the difference between some ROMs and others so that you can play the fortnite, I want to try more ROM, but I do not want to lose the power to play the fortnite, what difference there is between these roms, thanks
Click to expand...
Click to collapse
The device fingerprint. There's a Magisk module that can spoof that for you. Use Search.
understood, but because one ROM implements it as standard and another does not, it is the Kernel, something must have to not have to be dizzy with magisk, if I do not want to root, because in pixel ROM you do not have to do anything
Related
So I think most of you already know about Google's strict update to their SafetyNet API, which is used by Android Pay, and Pokemon Go among other apps.
If you don't, SafetyNet is a protocol used by Google Play Services that returns whether your device has been "tampered with". Having Root Access, Xposed installed, or a custom ROM or Kernel, have been known to trip this check, which will prevent the apps that utilize SafetyNet's functionality from running on the device.
Several developers on XDA and in the rooting community have been working overtime in an attempt to find a loophole in SafetyNet's code - enter the likes of Magisk and SuHide, each of which no longer work to hide root from SafetyNet as of the date of this writing.
Now, my personal belief is that after a person has purchased an Android device (and in effect that copy of the device's software) they should be free to make any and all modifications they choose to it - at the risk of their own security of course. Additionally, with apps like Pokemon Go, which offer in-game purchases and then change user agreements through app updates which block potential users after they may have made these same in-game purchases, the argument could be made that the SafetyNet API is even promoting fraud.
It isn't my intention to convince anyone of my position, only understand it. At this time, I am trying to gain a better understanding of exactly what elements found on a device prompt SafetyNet to return that a device has been tampered with. I was once rooted, with Xposed installed, but have since uninstalled both, and even re-flashed stock firmware. Even still, the SafetyNet Helper App I have been using for research always returns a failure. For posterity, I am also unable to log into Pokemon Go on stock firmware with no root or Xposed.
If root access is enabled, I have found that the SafetyNet check itself (step 1) will fail and the app will present a red screen, whereas if root access is not installed, the SafetyNet check will pass, but the Device Signature Verification with Google (step 2) will fail, which results in an overall failure where apps like Android Pay and Pokemon Go are concerned. The most modern counter I have found to hide root from SafetyNet is found here but even it states that the device must be able to pass the SafetyNet check on its own before this modifies SuperUser can be installed, so I feel a bit stuck.
I haven't seen anyone address SafetyNet and the Xperia Z5 Compact in the same sentence, and so my question is, can the Z5C pass SafetyNet at all since its most recent update? Please, download the SafetyNet Helper App from the Play Store and run it on your Z5C. Let me know if you get a red screen (failure at first step) a blue screen (failure at second step) or a green screen (passing). Also tell me about your device, and any modifications you have made to it. Seeing as how I can no longer pass the SafetyNet check at all on newly flashed stock firmware, I worry that the Xperia Z5C may not have been given Google's "Device Signiture Verification" - like many other international Android devices.
And if anyone else can shed some light on this situation, I would be most grateful.
Blue screen error.
Krypton custom rom based on .253 with zach's kernel. xposed installed
Sent from my iPad using Tapatalk
What about downgrading Google Play Services? as far as i remember the Safetynet APi is included in this package. Don't know if it is server based or written inside the package, though.
Has anyone found a way to bypass SafetyNet for Nougat?
grayleshy said:
Has anyone found a way to bypass SafetyNet for Nougat?
Click to expand...
Click to collapse
I also want to know this, when running safetynet test it shows me a red screen, even though I already removed root and flashed stock firmware.
rolo143 said:
I also want to know this, when running safetynet test it shows me a red screen, even though I already removed root and flashed stock firmware.
Click to expand...
Click to collapse
because of unlocked bootloader
im using magisksu + magiskhide and its bypassing the safetynet
meistr91 said:
because of unlocked bootloader
Click to expand...
Click to collapse
There is a workaround?
meistr91 said:
because of unlocked bootloader
Click to expand...
Click to collapse
Can I relock it again?
https://forum.xda-developers.com/z5-compact/general/recovery-nougat-7-0-android-bootable-t3609358
rolo143 said:
Can I relock it again?
Click to expand...
Click to collapse
Magisk changes the properties and "relocks" it for you during the start up procedures.
--- previous post
NeoBeum said:
https://forum.xda-developers.com/z5-compact/general/recovery-nougat-7-0-android-bootable-t3609358
Magisk changes the properties and "relocks" it for you during the start up procedures.
Click to expand...
Click to collapse
But magisk requires root. I remove root because there are some games and apps that detect it. So I wanted to pass SafetyNet but still can't.
I have Magisk working, I'm just rebuilding the recovery project and fixing some stuff
Has one been able to patch libandroid to make suhide work on Nougat with security patches after October 2016?
I have CarbonROM 5.1 Moo installed on my Zperia Z5 compact. This along with Magisk 14.3. (And... yeah... As it seems, the Magisk module "Universal SafetyNet Fix" is also required in my case. )
With this, it all works fine. SafetyNet checks out as valid/okay. No problems.
I maintain a few devices for my family members, and as I'm seeing more and more apps requiring SafetyNet checks for compatibility, I'm afraid I'm going to need to change my typical phh SuperUser setup I've been using in favor of using Magisk for root, since it can pass a SafetyNet check. I want to get working first on my 6P, and then once I'm comfortable with the procedure, requirements, and stability, I'll adjust the setup on my family's devices.
Are most ROMs out there able to pass SafetyNet if rooted with Magisk? I'm currently using OmniROM on most of my devices, but the dev team has explicitly stated that they don't support or recommend rooting. I know that some ROMs (AquariOS and DARK ROM) specifically claim that they pass SafetyNet with Magisk. Is this the exception, or the norm?
If only a few can pass SafetyNet, I'd love to hear from the 6P community which ROMs you are using with Magisk that don't trip SafetyNet.
Thanks!
Most ROMs pass SafetyNet checks, though the only rom I can personally verify is CarbonROM
Netflix is not working since I have android 10, I installed from 0 and Netflix doesn't appear in Google play, and official apk doesn't work for me.
Recently CTS won't pass with Magisk installed (even with Magisk hide). Google must have changed SafetyNet rules, Magisk did not catch up yet. It's not clear if this issue is impacting all Magisk users or only some. I can't pass CTS anymore, Android 9.
_mysiak_ said:
Recently CTS won't pass with Magisk installed (even with Magisk hide). Google must have changed SafetyNet rules, Magisk did not catch up yet. It's not clear if this issue is impacting all Magisk users or only some. I can't pass CTS anymore, Android 9.
Click to expand...
Click to collapse
Likewise on stock android 10 for the past 2 or 3 days. No mods installed as such and failing CTS.
Play store is still showing verified device but I hear some users are getting non verified message which will not allow them install certain apps
How about those who become L3 in the attempt to fix sensors of downgraded to Android 9 and flashed persist partition ?
amnher said:
How about those who become L3 in the attempt to fix sensors of downgraded to Android 9 and flashed persist partition ?
Click to expand...
Click to collapse
Probably out of luck, DRM certificates are gone forever. At least that was the case for Mi A1 phone, but seems to be the same for A3.
_mysiak_ said:
Probably out of luck, DRM certificates are gone forever. At least that was the case for Mi A1 phone, but seems to be the same for A3.
Click to expand...
Click to collapse
Will warranty be a solution? Phone is less than two weeks old
amnher said:
Will warranty be a solution? Phone is less than two weeks old
Click to expand...
Click to collapse
No, you screwed it up. As far as I know, service center can't restore DRM keys even if they wanted to, they are flashed in factory and unique to each phone. The only solution is probably to replace whole motherboard. This was the case with Mi A1 and all Sony phones where unlocking of bootloader removed DRM keys as well. Nevertheless, you can try your luck and contact your service center..
_mysiak_ said:
No, you screwed it up. As far as I know, service center can't restore DRM keys even if they wanted to, they are flashed in factory and unique to each phone. The only solution is probably to replace whole motherboard. This was the case with Mi A1 and all Sony phones where unlocking of bootloader removed DRM keys as well. Nevertheless, you can try your luck and contact your service center..
Click to expand...
Click to collapse
This is worst I really did not expect that in messing with persist image really permanently destroys it and I will not be able to enjoy HD videos of Netflix on my a3. Other than that, what are the disadvantages of loosing L1 (messed up DRM) ?
they pulled back the update maybe that's the reason.
and if your device is bootloader unlocked it's also a reason...
i installed Netflix from apkpure.
amnher said:
This is worst I really did not expect that in messing with persist image really permanently destroys it and I will not be able to enjoy HD videos of Netflix on my a3. Other than that, what are the disadvantages of loosing L1 (messed up DRM) ?
Click to expand...
Click to collapse
Yeah, it's unfortunate, many people are advising to "just flash persist.img and it will solve your issues", but it doesn't seem to help in first place and additionally damages the phone beyond repair. Lesson learned for you I guess, don't trust some random folks on the Internet..
Btw. as far as I know, 720p videos should be still playable on Netflix, it affects only full HD and 4K content (which need L1), which you wouldn't enjoy on 720p screen anyway. On Mi A1 I had only L3 (that was the default DRM level) and I did not notice any usability issues, Netflix, Google play music etc. were working nicely. On the small screen I did not notice that Netflix was playing at lower resolution.
_mysiak_ said:
Yeah, it's unfortunate, many people are advising to "just flash persist.img and it will solve your issues", but it doesn't seem to help in first place and additionally damages the phone beyond repair. Lesson learned for you I guess, don't trust some random folks on the Internet..
Btw. as far as I know, 720p videos should be still playable on Netflix, it affects only full HD and 4K content (which need L1), which you wouldn't enjoy on 720p screen anyway. On Mi A1 I had only L3 (that was the default DRM level) and I did not notice any usability issues, Netflix, Google play music etc. were working nicely. On the small screen I did not notice that Netflix was playing at lower resolution.
Click to expand...
Click to collapse
Im at service center and they do not know what DRM is... but they will flash via testpoint i dunno if it will help
amnher said:
Im at service center and they do not know what DRM is... but they will flash via testpoint i dunno if it will help
Click to expand...
Click to collapse
I'm afraid that not, DRM keys are lost already, they would have to generate/obtain new ones. In each case, let us know how it went..
_mysiak_ said:
I'm afraid that not, DRM keys are lost already, they would have to generate/obtain new ones. In each case, let us know how it went..
Click to expand...
Click to collapse
It came back to 10.3.3.0 which is lower than before when i purchase it. Sadly L3 and they opened a brand new mi a3 and it was L1 so they are surprised. The technicial now is tying to do an ota. Though i doubt it will be fixed
Ps. Failed now they will change the motherboard
Check this out:
forum.xda-developers.com/yureka/themes-apps/fix-device-isnt-compatible-version-t3892194
I dunno it helps, but it worked for me
callmegov said:
Check this out:
forum.xda-developers.com/yureka/themes-apps/fix-device-isnt-compatible-version-t3892194
I dunno it helps, but it worked for me
Click to expand...
Click to collapse
It changes these things in build prop, I doubt that it will help with anything for Netflix and even OP says that it's only to show Netflix in playstore (for phone models which are "unsupported" by Netflix officially, which is not the case for Mi A3).
ro.product.model=Pixel 3 XL
ro.product.brand=google
ro.product.name=crosshatch
ro.product.device=crosshatch
ro.product.cpu.abi=arm64-v8a
ro.product.cpu.abilist=arm64-v8a,armeabi-v7a,armeabi
ro.product.cpu.abilist32=armeabi-v7a,armeabi
ro.product.cpu.abilist64=arm64-v8a
ro.product.manufacturer=Google
ro.product.locale=en-US
Basically, f*ck Netflix and Google. We can't even watch the things, even if we want to pay for it, so f*ck them, I'll just download the movies/shows from somewhere else and put it on my SD card.
[Solved]
Hey guys! Good news
:victory: Got Netflix back to work with unlocked bootloader, current Bliss Rom and Magisk installed. :victory:
I believed that ctsProfile failure was the culprit of not being able to install Netflix from Google Play so I get it to pass thanks to @pkdon123 suggestion and files shared by @rudranshrajput and off course some G search. Here's what I've done (not sure if all steps are needed, I went throught it just once):
Solved ctsProfile with flashing two files through Magisk and rebooting.
Used Magisk Hide to hide it from GP and Google Services Framework. Then run SafetyNet check and ctsProfile passed without any issue.
Clear cache and data from both apps - GP and GSF. Then I had to reboot twice to get GP to work again but finally was able to find and install Netflix from there straight away and everything is working perfectly.
Let me know if it works for you guys. Good luck :fingers-crossed:
Horstorm said:
Hey guys! Good news
:victory: Got Netflix back to work with unlocked bootloader, current Bliss Rom and Magisk installed. :victory:
I believed that ctsProfile failure was the culprit of not being able to install Netflix from Google Play so I get it to pass thanks to @pkdon123 suggestion and files shared by @rudranshrajput and off course some G search. Here's what I've done (not sure if all steps are needed, I went throught it just once):
Solved ctsProfile with flashing two files through Magisk and rebooting.
Used Magisk Hide to hide it from GP and Google Services Framework. Then run SafetyNet check and ctsProfile passed without any issue.
Clear cache and data from both apps - GP and GSF. Then I had to reboot twice to get GP to work again but finally was able to find and install Netflix from there straight away and everything is working perfectly.
Let me know if it works for you guys. Good luck :fingers-crossed:
Click to expand...
Click to collapse
Hiding the full play services causes battery drain.
You only need to hide com.google.android.gms.unstable from play services.
All of this is already mentioned in the magisk documentation.
Also Netflix will still work with rooted device you just need to download it from a different source like apkmirror. It doesn't download from the playstore because play store isn't certified which is why we hide it in magisk.
If people took the time to read the applicable documentation then threads like this wouldn't have to exist
garylawwd said:
Hiding the full play services causes battery drain.
You only need to hide com.google.android.gms.unstable from play services.
All of this is already mentioned in the magisk documentation.
Also Netflix will still work with rooted device you just need to download it from a different source like apkmirror. It doesn't download from the playstore because play store isn't certified which is why we hide it in magisk.
If people took the time to read the applicable documentation then threads like this wouldn't have to exist
Click to expand...
Click to collapse
I was having the same exact problem and I solve this problem by enabling magiskhide and doing exactly what you have said I also tested by downloading the apk from the APK mirror and it was working absolutely fine but my problem was that I wouldn't be able to get Netflix updates from the play store also my device was uncertified and I was trying to make it certified which was easily done by flashing magisk also keep in mind that if you have only unlock the bootloader on stock ROM CTS won't pass and device will be non certified so if you want to stay on your stock ROM you need to lock the bootloader but I would suggest that instead of locking the bootloader you can flash magisk and use magisk hide just as a precaution as if she does anything wrong in future ota you can save yourself easily just by having and unlock bootloader.
garylawwd said:
Hiding the full play services causes battery drain.
You only need to hide com.google.android.gms.unstable from play services.
All of this is already mentioned in the magisk documentation.
Also Netflix will still work with rooted device you just need to download it from a different source like apkmirror. It doesn't download from the playstore because play store isn't certified which is why we hide it in magisk.
If people took the time to read the applicable documentation then threads like this wouldn't have to exist
Click to expand...
Click to collapse
Thanks for a suggestion. I didn't read the Magisk documentation and the truth is that I should but 'ain't nobody got time for that'... I consider myself just as an Android enthusiast and spending time to read all documentation I should to install custom rom and get root access would take enormous amount of precious time. I totally agree that If everyone would read the documentation (also write it responsibly) no such forums would be necessary. On the other hand this is why forums like this (Q&A, Guides,...) exist -> to share the knowledge.
And to the actual problem:
I had no clue that it could be actually connected to Magisk itself due to it worked on same device for several months on different custom roms without any issue. That's why I was looking for an answer in the ROM's thread. After disabling full GP Services I didn't notice higher battery drain, but disabling gms.unstable is sufficient. Installing Netflix from other sources is short-term solution which I off course did but I was looking for a solution that will last.
Off Topic: I've noticed that you're quite active in this forum and seems to have the knowledge. Keep it up and keep the patience. Thank you :good:
Hey folks
Xperia XZ1 (Canada) G8343 per topic header.
I recently unlocked my BL following the Sony instructions to run Lineage OS on my phone. Needless to say this has caused some challenges with apps like Google Play, Netflix, and banking apps that need a verified Android device that passes SafetyNet. Magisk has not helped at all, though I confess I am not 100% convinced I have it installed correctly.
Not a huge issue outside of those Apps though.
I have searched high and low for instructions on how to lock the BL again by flashing the phone with stock firmware etc. Seems odd, but also indicates not possible. Thought to check here with the big brains at XDA to see if I have missed anything obvious.
Basically I want to take my phone back to factory state.
Appreciate your help in advance if you can.
Swaziboy said:
Hey folks
Xperia XZ1 (Canada) G8343 per topic header.
I recently unlocked my BL following the Sony instructions to run Lineage OS on my phone. Needless to say this has caused some challenges with apps like Google Play, Netflix, and banking apps that need a verified Android device that passes SafetyNet. Magisk has not helped at all, though I confess I am not 100% convinced I have it installed correctly.
Not a huge issue outside of those Apps though.
I have searched high and low for instructions on how to lock the BL again by flashing the phone with stock firmware etc. Seems odd, but also indicates not possible. Thought to check here with the big brains at XDA to see if I have missed anything obvious.
Basically I want to take my phone back to factory state.
Appreciate your help in advance if you can.
Click to expand...
Click to collapse
Maybe just change your way of thinking and directly think of bypassing safetynet.
jjgvv said:
Maybe just change your way of thinking and directly think of bypassing safetynet.
Click to expand...
Click to collapse
Care to elaborate on that any? From my research bypassing it is increasingly difficult as Google has worked to include more advanced tech in the platform.
Install magisk and activate magisk hide.
Download and install Magisk Hide Props Config module in magisk, use this module to install XZ1 fingerprint.
Hi to all, this is my first post here on XDA.
I Was doing a little of research to get Safety Net pass on custom rom's (I Have tested this fix on Z Rom V6, Illussion OS 1.7 and Z Rom Lite v2) And by now, here is the solution, It's not a fake screen telling you that you have passed Safety net like the one you get when you use the Hidden Core Method. This is a real fix.
So now, we're using 2 Magisk modules.
1.-safetynet-fix-v1.1.1
2.-MagiskHidePropsConfig-v5.4.0
Ok, after the download of the 2 zips you need to flash through Magisk, (You need to enable MagiskHide) we'll need to use a terminal emulator to get the safety net pass, then after downloading a terminal emulator we need to follow this tutorial:
After that we need to set the new fingerprint of our device to be ''Samsung Galaxy A20 A205W'' After selecting that fingerprint we need to finish the setup, and then Reebot. after that.... Voila, now our device pass Safety Net on custom roms.
Credits to all of the creators of the modules.
Thanks for this info, will try it out once I rooted my phone again.
I cannot find safetynet-fix on magisk modules.
Did they removed it?
In theory magiskhidepropsconfig alone should do the job, sadly i cannot pass ctsProfile test on my phone that has a custom ROM (Xiaomi Mi note 10).
Not out of the box at least.
It has instructions on how to manually change the fingerprint and the security patch date so to pass the ctsProfile test but they are...complicated
I even followed the instructions on the video but still no dice.
Nadaaaaa said:
I cannot find safetynet-fix on magisk modules.
Did they removed it?
In theory magiskhidepropsconfig alone should do the job, sadly i cannot pass ctsProfile test on my phone that has a custom ROM (Xiaomi Mi note 10).
Not out of the box at least.
It has instructions on how to manually change the fingerprint and the security patch date so to pass the ctsProfile test but they are...complicated
I even followed the instructions on the video but still no dice.
Click to expand...
Click to collapse
You should use the .zip file attached to this thread bro, SafetyNet fix is for hardware attestation and unlocked bootloaders, That's why you should use MagiskHidePropsConfig + SafetyNetFix. Google play services must be enabled and not frozen in order to have SafetyNet working. Check if there is a specific fingerprint for your device. And yes, the module has been removed from magisk repository, You can find the latest version here: https://github.com/kdrag0n/safetynet-fix
@PhillipVilla , i am sorry but could you elaborate a bit more?
I have flashed Havoc 4.6 and Magisk v23 onto my Samsung S8+. I have downloaded the two files you attached. But what do you mean by "flash through Magisk"?
My Google Play Store is working fine my problem is no Netflix in Play Store and my TV provider app is not working. So i am trying to get SafetyNET to pass and possibly hide the fact that the phone is rooted.
TheGeneral said:
@PhillipVilla , i am sorry but could you elaborate a bit more?
I have flashed Havoc 4.6 and Magisk v23 onto my Samsung S8+. I have downloaded the two files you attached. But what do you mean by "flash through Magisk"?
My Google Play Store is working fine my problem is no Netflix in Play Store and my TV provider app is not working. So i am trying to get SafetyNET to pass and possibly hide the fact that the phone is rooted.
Click to expand...
Click to collapse
Magisk is an app you should install. You can search in this forum
I have a Moto G6 and I'm having trouble getting the SafetyNet to go green. Installed Magisk v23 and the SafetyNet Fix and the MagiskHidePropConfig and still no dice. Any suggestions?