I have rootrd my phone and used magisk, safety net keeps saying invalid reply. I tried it on stock, Lineage KS and how Hades Rom to get the same response. I have tried reinstalling,isabling magisk hide and what was recommended on the main site but to no avail. Can someone please help me. I am running the newest magisk manager, phone is SM-A520F
As I understand, invalid response doesn't mean saftynet fails. Just check fails because google changed their code again. Do you have issues with application requiring safety net pass? I have the same response as you, yet I use my safety net app just fine. Updating Magisk should probably fix this as it is GUI issue not bypass issue (I assume you use v16) but v17 has issues - bootloops and slow unlock (for me at least). In my case bootloop resulted in encrypted phone somehow. I would highly recommend you do backup before trying magisk 17.
Related
I can not install magisk modules and my device constantly loses its root without a reason.
I have the same problem. Magisk seems to be still buggy. But at least I haven't seen the "losing root" issue after disabling "Magisk Hide" in the settings.
Thanks
romhippo.com said:
I have the same problem. Magisk seems to be still buggy. But at least I haven't seen the "losing root" issue after disabling "Magisk Hide" in the settings.
Click to expand...
Click to collapse
Thanks Romhippo.com for responding!
If anyone knows more about it, I'd be happy to know.
Had that issue on a One Plus 3T. Finally updated Magisk in the app and it fixed itself. Was really flakey on root.
larsdennert said:
Had that issue on a One Plus 3T. Finally updated Magisk in the app and it fixed itself. Was really flakey on root.
Click to expand...
Click to collapse
Cool! I hope they also correct here.
Loosing root + possible fix
I was getting the same problem, magisk loosing root and phone getting encryptation problems... making me to format my phone twice.
After i noticed the problem was with magisk 13.3, so i tried to install 13.6 beta but no success, it give me error "Unable to detect boot image" during instalation.
Then i decided to mod magisk zip file (updater_script) , installed then and jrummy busybox (I think oldversions are conflicting with magiskSu)... and now i got 2 days without problem.
Magisk 13.6 beta modded
https://drive.google.com/open?id=0B1UKyTc_LCSOc09UMFhHNVFTd1U
raphamfc said:
I was getting the same problem, magisk loosing root and phone getting encryptation problems... making me to format my phone twice.
After i noticed the problem was with magisk 13.3, so i tried to install 13.6 beta but no success, it give me error "Unable to detect boot image" during instalation.
Then i decided to mod magisk zip file (updater_script) , installed then and jrummy busybox (I think oldversions are conflicting with magiskSu)... and now i got 2 days without problem.
Magisk 13.6 beta modded
https://drive.google.com/open?id=0B1UKyTc_LCSOc09UMFhHNVFTd1U
Click to expand...
Click to collapse
LoL Many thanks for your help. It's all normal here.
I'm going to agree on conflict issues being the likely cause. Between custom roms having su built in like Resurrection remix, SuperSU and standalone magisk, there are plenty of possibilities for messed up boot images.
In fact, 2 things bother me the most.
1. I can not install magisk modules
2. The magisk does not pass SafetyNet.
I do not know if that happens to you.
My Z2 is a verizon one so this is where my advice stops on that phone. I've Magisk on the 3T and pixel only
anyone have a guide to install Magisk?
Refer the following threads completely. Junior answered all my querries. His Moto Brazil blog has systematic and structured guides as well. Very well done.
https://forum.xda-developers.com/z2-play/help/indian-stock-firmware-xt1710-10-t3711423
http://motozbrasil.blogspot.in/search/label/TutorialZ2Play
Kind of a long story:
I have the TIM branded Zenfone 3 Deluxe 570KL and everything was ok (safetynet pass on both CTS and Basic integrity with Magisk root).
Then i updated Magisk to the 15.0 version and got my device encrypted randomly at the restart (and yes this is a problem with this version but hangon), after the upgrade to 15.0 and the device encrypted now the CTS verification fails so i tried to downgrade back to version 14 of magisk to no avail.
From there i downloaded the WW version of the firmware, formatted the phone (inc data), convert the zip to a flashable img file and flashed the stock WW with no root.
Device still encrypted despite the complete format and fails again the safetynet.
Tried to flash the TIM version downloadable from ASUS with the same result.
Somehow i flashed the stock WW and safetynet fails only on CTS but as soon as i install the version 15.1 of magisk and enabling Magisk hide on google apps i fail safetynet also on basic integrity.
Do you know any way to remove this dammned encryption since there is no option to disable it in the security settings and flash a fresh stock firmware that passes safetynet?
Maybe with a twrp backup of a stock firware i can do something?
Regards and happy holydays
exico91 said:
Kind of a long story:
I have the TIM branded Zenfone 3 Deluxe 570KL and everything was ok (safetynet pass on both CTS and Basic integrity with Magisk root).
Then i updated Magisk to the 15.0 version and got my device encrypted randomly at the restart (and yes this is a problem with this version but hangon), after the upgrade to 15.0 and the device encrypted now the CTS verification fails so i tried to downgrade back to version 14 of magisk to no avail.
From there i downloaded the WW version of the firmware, formatted the phone (inc data), convert the zip to a flashable img file and flashed the stock WW with no root.
Device still encrypted despite the complete format and fails again the safetynet.
Tried to flash the TIM version downloadable from ASUS with the same result.
Somehow i flashed the stock WW and safetynet fails only on CTS but as soon as i install the version 15.1 of magisk and enabling Magisk hide on google apps i fail safetynet also on basic integrity.
Do you know any way to remove this dammned encryption since there is no option to disable it in the security settings and flash a fresh stock firmware that passes safetynet?
Maybe with a twrp backup of a stock firware i can do something?
Regards and happy holydays
Click to expand...
Click to collapse
I am having the same problem with Magisk v15.1. What I did for a temporary solution is I flashed back to Magisk v14.0 and it now passes safety checks. I am using Android 7.0 and I have the 2.15 ghz version of the phone (Asus_Z016D) Hope this helps.
---------- Post added at 08:48 PM ---------- Previous post was at 08:45 PM ----------
https://forum.xda-developers.com/showpost.php?p=75017953&postcount=5170
Thanks for the suggestion. Flash back the 14 is the first thing I tried but it failed and then I tried to reset and reflash the stock firmware but now, like I said, nothing that I tried works.
I know is asking a lot but can you make a TWRP backup of your phone except the data partition obviously? Maybe that encryption f** up something that I can't fix just by reset and flash the stock
I have the same problem. Safetynet fails... Are you sure that encryption is the cause?
Ryder. said:
I have the same problem. Safetynet fails... Are you sure that encryption is the cause?
Click to expand...
Click to collapse
I believe so, i got encrypted only when i installed the 15.0 but even if i format system and data and i flash a clean stock the options says that my phone is encrypted even if the phone has no password or i didnt activate it
exico91 said:
I believe so, i got encrypted only when i installed the 15.0 but even if i format system and data and i flash a clean stock the options says that my phone is encrypted even if the phone has no password or i didnt activate it
Click to expand...
Click to collapse
I updated to magisk 15.2 and magisk hide works now. Now i can see nintendo games on play store for example. However ctsprofile doesn't pass safetynet check
Ryder. said:
I updated to magisk 15.2 and magisk hide works now. Now i can see nintendo games on play store for example. However ctsprofile doesn't pass safetynet check
Click to expand...
Click to collapse
Would be nice to pass also CTS like before but Im ok with just the integrity check.
And yeah i can confirm that it works now with 15.2.
That was driving me mad; interesting fact: Fire Emblem Heroes go into connection error loop if the integrity check fails or detect that the phone is rooted and that happens at random times. I hate this approach of Nintendo and such, if i want to have control of my phone you shouldnt penalize me for that.
Anyway if someone is brave enough to share a stock/rooted backup that pass the CTS i would gladly try it out.
exico91 said:
Would be nice to pass also CTS like before but Im ok with just the integrity check.
And yeah i can confirm that it works now with 15.2.
That was driving me mad; interesting fact: Fire Emblem Heroes go into connection error loop if the integrity check fails or detect that the phone is rooted and that happens at random times. I hate this approach of Nintendo and such, if i want to have control of my phone you shouldnt penalize me for that.
Anyway if someone is brave enough to share a stock/rooted backup that pass the CTS i would gladly try it out.
Click to expand...
Click to collapse
I agree. Even Gangstar New Orleans isn't downloadable if you have root. It's root the cause! I tought it was the fact that it's available only for some devices for certain reasons. Now even gameloft seems to penalize root users...
Did you go on magisk hide section and selected the apps/games which you are interested in?
Ryder. said:
I agree. Even Gangstar New Orleans isn't downloadable if you have root. It's root the cause! I tought it was the fact that it's available only for some devices for certain reasons. Now even gameloft seems to penalize root users...
Did you go on magisk hide section and selected the apps/games which you are interested in?
Click to expand...
Click to collapse
To download the apps/games, obviously, you have to use hide on google play then, when are installed, on the apps
Since i want to use Android Pay but got this issue, is there any stock rom which passes certification?
Could you please check:
Open the Google Play Store app Google Play.
Tap Menu Menu and then Settings.
Under “Device certification” you’ll see if your device is certified
Edit: After some research i can say it happens because of unlocked bootloader.
Any solution to pass cts verification?
I'm trying to use a Bank app from my country, named BT pay (Banca transilvania), and coudn't get it to work on lasted 5.1.5 rom with magisk.
I clean-installed the lasted Open Beta 14, without magisk/kerner, and safetynet checker still shows me FAILED.
I tried EssentialX Kernel + Magisk (hiding the safetynet app) and still didn't worked for me...
My Safety Net Request: fail(SafetyNetApi.AttestationRestul success == false or empty payload)
I'm i missing something ?
Wait, even though the safety net apps including magisk manager may say safety net fails, actually your safety net would be passing in real due to some update in policy by google. You have to use updated safety net apps to find correct status. Search magisk threads to know more.
Aswin08 said:
Wait, even though the safety net apps including magisk manager may say safety net fails, actually your safety net would be passing in real due to some update in policy by google. You have to use updated safety net apps to find correct status. Search magisk threads to know more.
Click to expand...
Click to collapse
lol, indeed i used a different safetynet checker, and my phone passes even with magisk, but the bank app isn't working either.. "your device may be rooted"
prologikus said:
lol, indeed i used a different safetynet checker, and my phone passes even with magisk, but the bank app isn't working either.. "your device may be rooted"
Click to expand...
Click to collapse
Well I don't understand now, i thought you where saying in previous post that safety net didn't pass. Btw, hope rechecked that you added ur bank app in magisk hide.
It may be detecting /sdcard/MagiskManager/ folder.
Hi all,
Got a new phone and finally decided to see if I could root the old Pixel 2 XL. It's unlocked, bought directly from Google. Never before unlocked bootloader until now.
It was flashed to factory Android 11 2020-12, and rooted from there. Magisk 21.1 beta was installed from zip while booted into TWRP 3.0.4, as advised in this thread. The latest Play System Update (Oct 5, 2020) was automatically installed while I was messing around afterwords.
I confirmed root access thru a checker and Termux, which is pretty neat! Hadn't rooted a device in a long time!
Unfortunately, device certification fails in Play Store, Magisk SafetyNet check and being unable to add a credit card to Google Pay. Magisk says basicIntegrity passes, but CTSprofile fails.
Things I've tried, mostly from this exhaustive guide:
Hidden Magisk Manager
Enabled MagiskHide, rebooted
Remove Magisk zip from storage
Lock bootloader again, rebooted
Clear app storage for Play store and Play services, rebooted
Disable USB debugging
Disable Play Protect scanning
Looked over XDA boards, Magisk changelog/documentation/guides
Things I haven't done (yet?):
Spoofing device fingerprint. I wouldn't expect this to be necessary, since it's actually authentic! But maybe there's more to it that I don't understand?
Start over from scratch, with Magisk Canary build - doesn't appear to be any improvements to MagiskHide according in current release notes
Is this possible to achieve?
composition said:
Is this possible to achieve?
Click to expand...
Click to collapse
SafetyNet:Magisk and MagiskHide Installation and Troubleshooting guide
www.didgeridoohan.com
Google I believe is using hardware-backed CTS profiling, which Magisk cannot circumvent. Your only chance of passing CTS is to hope Google ISN'T using the hardware-backed version, so you can employ one of the workarounds I gave in the link above.
There is a setting in magisk manager that let's you switch the attestation check. I'm having a brain fart as to where it is atm but I'll poke around and if/when I find it, I'll reply again.
Larzzzz82 said:
There is a setting in magisk manager that let's you switch the attestation check. I'm having a brain fart as to where it is atm but I'll poke around and if/when I find it, I'll reply again.
Click to expand...
Click to collapse
Apparently we're both having brain farts. I didn't even think there was such a setting. Then again, I don't use Google Pay.
Since updating to C.48 (2125 [phone], coming from C.47, my Google Play and Pay have stopped working on my rooted phone (Magisk 24.3), even though it passes SafetyNet with YASNAC. When I try to open Play I get a "Try Again" screen. When I try to open Pay, I get "Google Pay is updating right now...". I've got Universal SafetyNet Fix 2.2.1 and MagiskHide Props Config installed, and Play and Pay in the Deny List. Tried using Shamiko 0.4.4 (while disabling deny) with no better results. Cleared cache and data on both apps multiple times. Uninstalled Magisk and unrooted, and everything worked again. Re-rooted w/o opening either app, put them both into "deny" and, for a brief time, both worked -- but eventually (without my doing anything that I could tell), they both reverted to the behavior described above.
I'm wondering if this behavior has anything to do with the April security update included in C.48? Because it's really odd that I YASNAC still shows safetynet as having passed. More likely, it's user error on my part, but has anyone else run into this yet on C.48?
I have a LE2127 running your firmware and I don't notice issues. One thing you could try is just flashing the update zip over your current OS using the OPlocalupdate apk here https://oxygenos.oneplus.net/OPLocalUpdate_For_Android12.apk
Thanks. I presume you're rooted? Which version of Magisk are you using and are you using Deny List or Shamiko?
rogerinnyc said:
Thanks. I presume you're rooted? Which version of Magisk are you using and are you using Deny List or Shamiko?
Click to expand...
Click to collapse
Yes, I'm rooted. I'm using Denylist on Magisk 24.3.
No problems on my end with Gpay while rooted
I gave up and did a total restore with MSM and then made sure to root and fill up the Deny List (and add SafetyNet Fix) before opening up Google Pay or Play. That seemed to work. Not sure how I messed it up in the first place, but I think it was in upgrading from C47 to C48 and my sequencing of unrooting, upgrading, clearing storage in the apps and re-rooting. Thanks all.