Develop Bugs

[App] [SafetyNet Passer] Pass SafetyNet after 2017-07-17 on Magisk V13

Hello XDA,
As we are all aware that once again Google broke SafetyNet Passing as they have extended their property scanning | Original Article here
The temporary fix was originally mentioned on this thread by @[email protected]
However you had to do the terminal commands after every reboot, thus Me and a few friends took this idea and created an app that does the same for you in the background and thus an easy temporary fix.
All you have to do is to install the apk as usual, grant it supersu permission and click to fix :laugh:
GitHub: https://github.com/Agusyc/SafetyNetPasser | Credits @Agusyc15
Download APK
Made a Quick Video Here
Tested Working on Oneplus 5 & Pixel XL | Magisk V13.2
Development Credits: @Agusyc15 & @unknownblkman
Magisk Credits as always @topjohnwu
Original Fix & ADB Commands: @[email protected]
PS: This is a temporary fix, I am sure @topjohnwu is aware of this situation and an official fix should be out soon :fingers-crossed:
Never Settle :highfive:

Reserved

You can use the module I attached, it works and does it systemlessly.
I didn't make it but I forgot who did lol

Interceptor777 said:
You can use the module I attached, it works and does it systemlessly.
I didn't make it but I forgot who did lol
Click to expand...
Click to collapse
What is that sharingan symbol in your quick settings.
Which rom and which SST themes.?

Bewildered Wolf said:
What is that sharingan symbol in your quick settings.
Which rom and which SST themes.?
Click to expand...
Click to collapse
Resurrection Remix with Spectrum kernel app, running lightning kernel LOS version which supports it.
The symbol on the quick settings is a quick profile switcher for spectrum, this is what it looks like on balanced profile.
Also, theme is also called spectrum on the play store.

Thanks OP! Works well. I'd tried all the recommended steps in other threads from terminal emulator and adb shell su, but they didn't work for me. Many thanks.

GitHub along with the Updated apk now uploaded on the OP | Credits @Agusyc15

hachamacha said:
Thanks OP! Works well. I'd tried all the recommended steps in other threads from terminal emulator and adb shell su, but they didn't work for me. Many thanks.
Click to expand...
Click to collapse
Please try the new apk uploaded on the OP :fingers-crossed:

Funk Wizard said:
Please try the new apk uploaded on the OP :fingers-crossed:
Click to expand...
Click to collapse
Just tried it and it works fine as did your first. Thanks!

@Funk Wizard you can also purpose the recovery flash solution (by noahajac) available from Github : here
Personaly i prefer flash the fix by this way instead of install a apk/service for fix SafetyNet each boot

Magisk 13.2 has been released and fixes the SafetyNet test failing.
Magisk 13.2
I can confirm that it's working for me.

Magisk 13.3 already available, and everything is fixed

Anyone having issues upgrading ?
I'm using stock rom (4.5.5) with a. Custom kernel
Iupgrades to 13.3 via Magisk manager (was on Magisk 13.0 previously so whichever Magisk manager goes with that).
Rebooted and now Magisk manager force closes upon boot.
Downloaded 13.3, cleared all data from Magisk manager, uninstalled Magisk manager, went to TWRP, dirty flashed 4.5.5 to restore the stock kernel, flashed Magisk 13.3, wiped cache and dalvik then rebooted. Same issue on start. Magisk force closes.
Reinstalling Magisk 13.0 allows Magisk manager to run.
Root still works when upgrading to 13.3, but Magisk manager still force closes.
Any ideas?

13.3 fixed for me

Binary Assault said:
Anyone having issues upgrading ?
I'm using stock rom (4.5.5) with a. Custom kernel
Iupgrades to 13.3 via Magisk manager (was on Magisk 13.0 previously so whichever Magisk manager goes with that).
Rebooted and now Magisk manager force closes upon boot.
Downloaded 13.3, cleared all data from Magisk manager, uninstalled Magisk manager, went to TWRP, dirty flashed 4.5.5 to restore the stock kernel, flashed Magisk 13.3, wiped cache and dalvik then rebooted. Same issue on start. Magisk force closes.
Reinstalling Magisk 13.0 allows Magisk manager to run.
Root still works when upgrading to 13.3, but Magisk manager still force closes.
Any ideas?
Click to expand...
Click to collapse
I'm having this issue too.
EDIT: I just flashed Magisk uninstaller, wiped cache/dalvic and then flashed v13.3 and now all is working well. I think the issue is I flashed a 13.2 fix yesterday which probably messed with it.

Binary Assault said:
Anyone having issues upgrading ?
I'm using stock rom (4.5.5) with a. Custom kernel
Iupgrades to 13.3 via Magisk manager (was on Magisk 13.0 previously so whichever Magisk manager goes with that).
Rebooted and now Magisk manager force closes upon boot.
Downloaded 13.3, cleared all data from Magisk manager, uninstalled Magisk manager, went to TWRP, dirty flashed 4.5.5 to restore the stock kernel, flashed Magisk 13.3, wiped cache and dalvik then rebooted. Same issue on start. Magisk force closes.
Reinstalling Magisk 13.0 allows Magisk manager to run.
Root still works when upgrading to 13.3, but Magisk manager still force closes.
Any ideas?
Click to expand...
Click to collapse
I kinda had that problem, but it would only crash when going to the part of the app that lets you manage apps which have been granted/denied root.
I tried clearing data and it still did it, so I completely uninstalled the app and I think that fixed it.
My guess is you are using an out of date app. The current version of the manager is 5.1.0 and can be found here.
Latest Magisk Manager
Uninstall whatever manager you have now and install that one and remember that the manager seems to get updates more often than Magisk does.

crumble6 said:
I'm having this issue too.
EDIT: I just flashed Magisk uninstaller, wiped cache/dalvic and then flashed v13.3 and now all is working well. I think the issue is I flashed a 13.2 fix yesterday which probably messed with it.
Click to expand...
Click to collapse
That didn't work for me unfortunately.
ArkAngel06 said:
I kinda had that problem, but it would only crash when going to the part of the app that lets you manage apps which have been granted/denied root.
I tried clearing data and it still did it, so I completely uninstalled the app and I think that fixed it.
My guess is you are using an out of date app. The current version of the manager is 5.1.0 and can be found here.
Latest Magisk Manager
Uninstall whatever manager you have now and install that one and remember that the manager seems to get updates more often than Magisk does.
Click to expand...
Click to collapse
This seemed too do it. I assumed that the version that came with Magisk was up to date. Maybe there was another update after 13.3.
Thanks guys!

Binary Assault said:
That didn't work for me unfortunately.
This seemed too do it. I assumed that the version that came with Magisk was up to date. Maybe there was another update after 13.3.
Click to expand...
Click to collapse
Apparently there's issues with certain modules. If I install the V4A module the same thing occurs. Lots of other people are having the same issue. So just be careful which modules you install.

crumble6 said:
Apparently there's issues with certain modules. If I install the V4A module the same thing occurs. Lots of other people are having the same issue. So just be careful which modules you install.
Click to expand...
Click to collapse
Ya, I just discovered this. I actually noticed a few things,
My original issue was caused by a module I installed
It seems anything I flash via TWRP makes Magisk manager fail.
Most modules I installed in TWRP that fails, will properly install within Magisk manager.
For me, the culprit was doze for Google play services. Even installing it via Magisk manager froze Magisk manager.
Is there any way to uninstall any Magisk modules without Magisk manager? I've been going to recovery, flashing Magisk uninstall, reinstalling Magisk then manually enable each module in Magisk manager. Kind of a pain.

Binary Assault said:
Is there any way to uninstall any Magisk modules without Magisk manager? I've been going to recovery, flashing Magisk uninstall, reinstalling Magisk then manually enable each module in Magisk manager. Kind of a pain.
Click to expand...
Click to collapse
Just delete the module folder from /magisk and reboot. You will need root access for this but from what I've found, root access still works even though Magisk Manager is not responding.

[MAGISK] [8.0] ARCore with modded Google Camera

Hey,
I've created a small magisk module, with that you can use the Argument Reality function inside the Google Camera.
It works on AOSP 8.0 Beta and Stable, maybe it also works on nougat.
When you want to test it on other devices than the Mi A1, please don't forget to make a backup even if bootloop and such things are very unlikely.
Wehen you have a device where it also works you are allowed to create a thread, only condition link me and very important Arnova8G2 because without his work it would not be possible.
Installation instructions:
The modules can easily flashed inside the Magisk Manager or with TWRP.
To get it fully working you have to flash both modules
Downloads:
All in one version:
https://forum.xda-developers.com/mi...re-modded-google-camera-t3720269/post75090632
ARcore Basic files:
https://drive.google.com/folderview?id=1C3pylJpeK9bc93L56v1JWrjJNXnNbU06
ARcore Basic files V2:
https://drive.google.com/file/d/16YyJN1PTDMZ5WPQ_F2VFZuyTJlAOmAyi/view?usp=sharing
Apps Module:
https://drive.google.com/file/d/12t5jRzlEM0tz1mkyKqjwu0RS8yZ37IeY/view?usp=sharing
Apps Module V2:
https://drive.google.com/file/d/19rtu2nUAcH2WKCBbGbm2F75uXsfwKXt4/view?usp=sharing
Do not thank me, just thank him @Arnova8G2

Thanks for your contribution! Will try as soon as I get the oreo beta working on my phone.

Unable to flash via magisk

Unable to flash via TWRP nor Magisk, maybe cause data partition is encripted

fosco_ said:
Unable to flash via TWRP nor Magisk, maybe cause data partition is encripted
Click to expand...
Click to collapse
My storage is also encrypted and it works.

AnnePunk said:
My storage is also encrypted and it works.
Click to expand...
Click to collapse
What version of Magisk and Magisk Manager?

fosco_ said:
What version of Magisk and Magisk Manager?
Click to expand...
Click to collapse
Latest Magisk Beta: v14.5 (code: 1456)
Magisk Manager: v5.4.3

AnnePunk said:
Latest Magisk Beta: v14.5 (code: 1456)
Magisk Manager: v5.4.3
Click to expand...
Click to collapse
I can't get Magisk Manager to install any module, it says something like /data/magisk not setup....

Yash98 said:
I can't get Magisk Manager to install any module, it says something like /data/magisk not setup....
Click to expand...
Click to collapse
Had the same bug, reinstall magisk with the Magisk Manager, reboot and try again.

I can flash other zip.. But these two can't be flashed on magisk

Rakibboss said:
I can flash other zip.. But these two can't be flashed on magisk
Click to expand...
Click to collapse
Hmm for me it works

Whatever, i managed to do it via this method
https://forum.xda-developers.com/redmi-note-3/themes/mod-updated-6-11-17-google-camera-hdr-t3701190

Yash98 said:
I can't get Magisk Manager to install any module, it says something like /data/magisk not setup....
Click to expand...
Click to collapse
"I can flash other zip.. But these two can't be flashed on magisk"
You must create an folder "magiskmanager" on internal sd card...then it works

I will try for Android Nougat. Thank you

It doesn't work on nougat .i tried

Hello, install without problems, but I would like to know which Gcam application exactly should I I must use, Thanks.

anyone got it working ?

jeneb11 said:
anyone got it working ?
Click to expand...
Click to collapse
Not working on Redmi Note 4 stock global miui9 with camera2 api enabled. Tried with both magisk, and TWRP, AR Stickers stoped.

how can you install magisk on oreo? when i booted to the twrp, it asks for my pattern and when i draw the pattern, it says pattern failed. so please tell me how can you install magisk on oreo

jigs4wkiller said:
Hmm for me it works
Click to expand...
Click to collapse
Which magisk version??

GravityBox on 10/Dec release

I posted this question on the GravityBox Beta-05 thread a few days ago, but have not gotten an answer.
Has anyone tried to run GravityBox Beta-05 (along with Edxposed, Riru) on the December release?
thanks,

swieder711 said:
I posted this question on the GravityBox Beta-05 thread a few days ago, but have not gotten an answer.
Has anyone tried to run GravityBox Beta-05 (along with Edxposed, Riru) on the December release?
thanks,
Click to expand...
Click to collapse
did it work on Nov update?

J32A said:
did it work on Nov update?
Click to expand...
Click to collapse
GravityBox 10.0 Beta5 works with the Nov update once you installed the prerequisite pieces (EdXposed and RiRu-core). I am running it now and it is great!

swieder711 said:
GravityBox 10.0 Beta5 works with the Nov update once you installed the prerequisite pieces (EdXposed and RiRu-core). I am running it now and it is great!
Click to expand...
Click to collapse
If you decide to try it on dec update let us kno what happens

Always odd when someone wants another person to be the guinea pig

wangdaning said:
Always odd when someone wants another person to be the guinea pig
Click to expand...
Click to collapse
If I had a good TWRP backup of my phone then I would be happy to be a guinea pig.
I was hoping to hear from the GB developer on whether it works on the December release,.

swieder711 said:
If I had a good TWRP backup of my phone then I would be happy to be a guinea pig.
I was hoping to hear from the GB developer on whether it works on the December release,.
Click to expand...
Click to collapse
I understand, only said it in jest. I would try myself, but just recently went through the hassle of going from DU Pie to stock 10. It is a pain for me because it completely fried my LTE ability. If you throw it on there and it bootloops, you can always flash the magisk disabler boot.img, remove it and reflash your patched boot.img.

Someone on the Gravitybox beta thread said that they have it running on the Dec release.

Yes. Exposed and riru with gb beta 5 already installed. I flashed December firmware with -w removed and then rerooted by patching boot.img via magisk and then flashed the patched boot.img with fastboot.

rhewins2268 said:
Yes. Exposed and riru with gb beta 5 already installed. I flashed December firmware with -w removed and then rerooted by patching boot.img via magisk and then flashed the patched boot.img with fastboot.
Click to expand...
Click to collapse
Did you disable Magisk before flashing the Dec update? I thought that was recommended.

swieder711 said:
Did you disable Magisk before flashing the Dec update? I thought that was recommended.
Click to expand...
Click to collapse
I've never disabled magisk. All I do is edit the flash-all.bat file by removing the "-w" and save it. Then put phone in bootloader mode and then open a command prompt in the same folder and type flash-all.
Let the phone boot.
Extract the boot.img from image-crosshatch-******
Copy it to your phone. Open magisk and select install, patch boot.img.
Copy the patched boot.img to your PC and flash it with fastboot.
Profit!

rhewins2268 said:
I've never disabled magisk. All I do is edit the flash-all.bat file by removing the "-w" and save it. Then put phone in bootloader mode and then open a command prompt in the same folder and type flash-all.
Let the phone boot.
Extract the boot.img from image-crosshatch-******
Copy it to your phone. Open magisk and select install, patch boot.img.
Copy the patched boot.img to your PC and flash it with fastboot.
Profit!
Click to expand...
Click to collapse
Last few questions before I take the plunge. I am running the following
Magisk 20.1
RiRu-Core 19.5
EdXposed 0.4.6 YAHFA
GravityBox 10-Beta-5
EDIT: SUCCESS. With no changes to the state of Magisk, I ran Flash-all nowipe and then patched/installed the boot.img file. Everything seems to have worked! Root, GravityBox and all my files seem intact!
With so many war stories, I am pleasantly surprised this went so smoothly.
thanks,
Scott

What do you guys use GravityBox for nowadays..?
Sent from my Pixel 3 XL using Tapatalk

Pie controls, data indicators, center clock, qs tile management, and more. What do you not use it for?

I have at least eight tweaks setup in Gravitybox.
Quick unlock
Center clock
Menu button
Progress bar for downloads
Battery as a %
Charging indicator
Advanced reboot menu
Long back key to kill app

swieder711 said:
Last few questions before I take the plunge. I am running the following
Magisk 20.1
RiRu-Core 19.5
EdXposed 0.4.6 YAHFA
GravityBox 10-Beta-5
EDIT: SUCCESS. With no changes to the state of Magisk, I ran Flash-all nowipe and then patched/installed the boot.img file. Everything seems to have worked! Root, GravityBox and all my files seem intact!
With so many war stories, I am pleasantly surprised this went so smoothly.
thanks,
Scott
Click to expand...
Click to collapse
Is this with the December update? Edxposed modules do not recognize it as installed, although I have the green *active* indication.
I have used the latest canary builds for magisk and Edxposed and no work ing modules for me. Even with a clean install. Any idea?

Any tips on how to install gravitybox? I'm already on the December update and rooted

dirtyreturn said:
Is this with the December update? Edxposed modules do not recognize it as installed, although I have the green *active* indication.
I have used the latest canary builds for magisk and Edxposed and no work ing modules for me. Even with a clean install. Any idea?
Click to expand...
Click to collapse
Im on the December release with Gravitybox beta-05 running great. Are you using the Yahfa version of EdXpored? And have the Riru core installed?

swieder711 said:
Im on the December release with Gravitybox beta-05 running great. Are you using the Yahfa version of EdXpored? And have the Riru core installed?
Click to expand...
Click to collapse
I have installed everything you specified and keep getting the GB system framework not reponding message. Is there anything else that needs to be done?
Magisk 20.2
EdXposed Manager 4.5.2
GB Q 10.0.0-beta-5
Riru Core 19.5
Riru EdXposed 0.4.6.0_beta(4478)(YAHFA)
I also tried sandyhook as well with the same result on the Dec update

uodii said:
I have installed everything you specified and keep getting the GB system framework not reponding message. Is there anything else that needs to be done?
Magisk 20.2
EdXposed Manager 4.5.2
GB Q 10.0.0-beta-5
Riru Core 19.5
Riru EdXposed 0.4.6.0_beta(4478)(YAHFA)
I also tried sandyhook as well with the same result on the Dec update
Click to expand...
Click to collapse
Have you tried using another Xposed module as a test?

Problem with BHIM UPI and Adaway on rooted 10.3.2.HD65AA, OP7T India.

I am on 10.3.2, rooted with Magisk Manager version 07f712a1 and Magisk 87de0e7a. These are the version numbers I can see when i open Magisk Manager. Magisk Hide is enable for banking apps mainly, systemless host module is enabled and Magisk package name is also hidden.
Most apps needing root are working fine and most Banking apps requiring root to be hidden are also working fine.
However BHIM UPI is not working, I get a message of root detected after putting the PIN and it does not open. If I uninstall or clear storage and register my mobile again, it gives the root detected error but still logs in. However as soon as I exit and open again, it does not log in. Any way to get this working?
Adaway had been working properly but now it is not able to update hosts, says Root permission not granted, even though in Magisk default permission is Grant. I have tried to uninstall and reinstall, change options in Magisk, install F-droid version but nothing works. Systemless host is enabled. I have restored a working app version and data using Titanium backup so ad-blocking is working. But unable to update with new host file. How to fix this?

Did you try to remove root and root again? Maybe something with Magisk isn't right.
For BHIM UPI I have no idea what that app is but there are a lot of apps that use really good root detection which Magisk can't fully circumvent. It could be that this is the case here

Macusercom said:
Did you try to remove root and root again? Maybe something with Magisk isn't right.
For BHIM UPI I have no idea what that app is but there are a lot of apps that use really good root detection which Magisk can't fully circumvent. It could be that this is the case here
Click to expand...
Click to collapse
BHIM UPI is a Banking App.
I am currently on Magisk Canary and also having problem with Adaway. I tried to change channel to Stable and the manager changed to version 7.5.1 but Magisk remained Canary version. When I tried to install the latest stable version the installation fails so I had to revert back to Canary version. If I clear storage the Manager comes back to Canary version and then I am able to install Canary Magisk version, it installs properly.
How do I properly uninstall Canary version Magisk and install Stable Magisk, maybe this will resolve the issues.

^^Review this thread, specifically first post
https://forum.xda-developers.com/apps/magisk/magisk-unified-hosts-adblocker-t3559019

gpz1100 said:
^^Review this thread, specifically first post
https://forum.xda-developers.com/apps/magisk/magisk-unified-hosts-adblocker-t3559019
Click to expand...
Click to collapse
Is this meant as a reply to my post? My issue with Adaway on Magisk Canary is that suddenly it is not able to get root permission.

So it worked before? I had to mess with the systemless hosts to get it working. It didn't have issues acquiring root though.

jesrani said:
BHIM UPI is a Banking App.
I am currently on Magisk Canary and also having problem with Adaway. I tried to change channel to Stable and the manager changed to version 7.5.1 but Magisk remained Canary version. When I tried to install the latest stable version the installation fails so I had to revert back to Canary version. If I clear storage the Manager comes back to Canary version and then I am able to install Canary Magisk version, it installs properly.
How do I properly uninstall Canary version Magisk and install Stable Magisk, maybe this will resolve the issues.
Click to expand...
Click to collapse
I would advise to use the stable Magisk version. You can either flash the Magisk uninstaller via TWRP or uninstall Magisk in Magisk Manager and then flash the stable Magisk version in TWRP

Macusercom said:
I would advise to use the stable Magisk version. You can either flash the Magisk uninstaller via TWRP or uninstall Magisk in Magisk Manager and then flash the stable Magisk version in TWRP
Click to expand...
Click to collapse
Is there a working TWRP for OnePlus7T, I thought there wasn't but I am not sure because I rooted it many months back.

jesrani said:
Is there a working TWRP for OnePlus7T, I thought there wasn't but I am not sure because I rooted it many months back.
Click to expand...
Click to collapse
Afaik only for custom ROMs. Otherwise, you can still remove Magisk in Magisk Manager and then patch the boot.img with the stable Magisk version or you remove ALL modules first, then make an OTA update to your existing version.
Then patch boot.img and flash it via "fastboot flash boot.img".

@jesrani What was the solution finally ?

Yea I'm having the same issue, tried everything i could and even using 'hide my applist' and it IS working. Its just that all apps except BHIM just won't even open now.

Latest Magisk crashes

So I tried to root a Pixel 2 XL with Android 8 and 9, installed the Magisk apk 7.5.1 and when it comes to patch the boot.img, it always requires to update the manager first. I didnt choose update, but it wont let me use the old version anymore, might be a bug.
However, when I then use the latest Magisk APK, it crashes when I select "Install". Any ideas what to do?

You could basically just flash the latest magisk canary build (the beta one) with twrp and you'll have root on your device in no time.
BTW this method is tested by me on android 11, and if it works on android 11 I think it'll work on previous versions of android as well. But, just to be on the safer side make sure you backup your device beforehand.

MridulDR said:
You could basically just flash the latest magisk canary build (the beta one) with twrp and you'll have root on your device in no time.
BTW this method is tested by me on android 11, and if it works on android 11 I think it'll work on previous versions of android as well. But, just to be on the safer side make sure you backup your device beforehand.
Click to expand...
Click to collapse
Thanks for the hint. I used the zipped Magisk and flashed it with TWRP. It still crashes when hitting the "Install" button but since the phone is rooted is not really necessary. Also, installing modules is
now possible again. Only renaming Magisk (for hiding) is something I didnt find yet, but the "Magisk Hide" Option should do the job.

Venomiz said:
Thanks for the hint. I used the zipped Magisk and flashed it with TWRP. It still crashes when hitting the "Install" button but since the phone is rooted is not really necessary. Also, installing modules is
now possible again. Only renaming Magisk (for hiding) is something I didnt find yet, but the "Magisk Hide" Option should do the job.
Click to expand...
Click to collapse
Which version of magisk are you using?
If you are on normal magisk manager(not canary), I'd suggest flashing the canary build(v21.0) and see if you are able to rename magisk manager.