Disclaimer: I am not a developer. I am posting this to help others who are trying to achieve the same results. I wasted a few hours of time trying various sequences of installation, different files, etc., until i finally got it right. Posting this up so it hopefully helps someone else!
Various problems I was running into:
Camera would stop working (any app) and show only the bottom buttons, a black screen and a camera icon in the middle.
Snapchat wouldn't let me login.
Snapprefs wouldn't work.
Android Pay wouldn't work. (Heads up: you cannot have Xposed and Android Pay both working...it's not possible as of 2016/01/29. If ever and when it is...and I test it myself, I'll update this thread.)
Here are the steps I took to get the phone Systemless rooted, get Xposed functioning, and then get SnapPrefs working (but no Android Pay).
Note: I am not providing step-by-step detailed instructions -- these are more of the general process. Make sure to read all of the information from the sources I reference.
Disclaimer: This worked for me, but I cannot guarantee this will work for everyone. I am not responsible for anything that happens to your phone if you try to repeat these steps. Also, this probably voids your warranty.
Hat tip to the following threads for information on the various stages of the process, developers for their hard work, and everyone else who has put up any info about this subject!
[GUIDE] Unlock/Root/Flash for Nexus 6P
[Help] Unfortunately, Nfc service has stopped
Files Used:
Nexus 6P Factory Image 6.0.1 (MMB29P) --- "angler-mmb29p-factory-25ed9560.tgz"
TWRP Recovery for angler 2.8.7.0 --- "twrp-2.8.7.0-angler.img"
Systemless SuperSU 2.67 --- "BETA-SuperSU-v2.67-20160121175247.zip"
Xposed 3.0 Alpha --- "XposedInstaller_3.0_alpha4.apk"
Xposed Framework v79 SDK23 for ARM64 --- "xposed-v79-sdk23-arm64.zip" (optional: grab "xposed-uninstaller-20150831-arm64.zip" while you're there)
Snapchat 9.21.1.0 --- "com.snapchat.android_9.21.1.0-771_minAPI16(armeabi-v7a)(nodpi).apk"
Snapprefs 1.6.5 (No need to download -- you can install via Xposed app)
Steps I took (NOTE: Do not allow TWRP to install root when it asks, "Install SuperSU now?" when exiting Recovery. Always click "Do not install."):
Optional: Flash the latest official system image from Google (MMB29P). I did because I had trouble with previous attempts and wanted to start fresh.
Unlock bootloader using Step 1 from this guide.
Download TWRP 2.8.7.0 from above link, then install using Step 2 from this guide.
Optional: Follow Steps 3 - 6 from this guide. You will now have Systemless Root.
Reboot into Android, use Play Market to install a file browser (I prefer Astro) then browse-to and install the Snapchat 9.21.1.0 apk. Once it's done, open and log-in to Snapchat. Make sure you are fully logged-in and can view/send snaps.
Use the file browser again to browse-to and install Xposed 3.0 Alpha apk. Once it's done, open it, go to Settings and change Installation mode to "Recovery (flash zip automatically)".
Open SuperSU, go to Settings, and check the box next to "Enable su during boot" (if you don't do this, when you reboot, NFC service will enter a neverending crash loop).
Reboot into Recovery, install Xposed Framework v79 SDK23 for ARM64, reboot. (Remember: click "Do not install," when prompted to install SuperSU.)
After this it will take a few minutes to do the "Optimizing app # of #" thing.
Once rebooted, open Xposed search-for and download Snapprefs 1.6.5. After installed, enable the Snapprefs module in Xposed, then reboot.
Once rebooted, open Snapprefs and customize your settings. Set your save location, etc.
That's it. You should now have functioning root, functioning Xposed, logged-in Snapchat, and functioning Snapprefs.
I know some people are going to say, "It's pointless to do Systemless root since Xposed modifies /system and breaks Android Pay," but the reason I went this route is because I normal rooting kept breaking my Camera (in any app). Maybe in the future there might be some way to keep Android Pay functioning and run Xposed modules without modifying /system...who knows.
It's pointless to install systemless now because Google modified the CTS check and it'll fail no matter how you loaded
LeoRex said:
It's pointless to install systemless now because Google modified the CTS check and it'll fail no matter how you loaded
Click to expand...
Click to collapse
It's not pointless actually. With Systemless you can still temporarily disable the SuperSu app through it's settings to use Android Pay, then re-enable SuperSU after you're done.
Sent from my Nexus 6P using Tapatalk
bouchigo said:
It's not pointless actually. With Systemless you can still temporarily disable the SuperSu app through it's settings to use Android Pay, then re-enable SuperSU after you're done.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Nah, go into Xda Forums SuperSU forums. There's a thread dedicated to systemless root and Android pay. Those steps only allow you to pass the SafetyNet app, but attempts to use Android Pay still failed in store for several users. Any future workarounds will only be temporary until patched again... It's over. :/
RoyJ said:
Nah, go into Xda Forums SuperSU forums. There's a thread dedicated to systemless root and Android pay. Those steps only allow you to pass the SafetyNet app, but attempts to use Android Pay still failed in store for several users. Any future workarounds will only be temporary until patched again... It's over. :/
Click to expand...
Click to collapse
If that's the case then yeah, Systemless is pointless.
Sent from my Nexus 6P using Tapatalk
@RoyJ
Have you actually tried using AP after doing this (I haven't yet, but worked for that guy):
http://forum.xda-developers.com/showpost.php?p=65085317&postcount=303
Yeah I had a feeling Google would make systemless obsolete... But like I said, I used systemless method because normal rooting methods kept breaking my camera functions.
theorie said:
Yeah I had a feeling Google would make systemless obsolete... But like I said, I used systemless method because normal rooting methods kept breaking my camera functions.
Click to expand...
Click to collapse
Why are people still on this 'systemless is now obsolete' thinking all of a sudden? One of systemless main original intents is to make ota/updates easier to do when you're rooted; AP working was just a side, albeit temporary, benefits of this.
---------- Post added at 11:57 PM ---------- Previous post was at 11:56 PM ----------
bouchigo said:
If that's the case then yeah, Systemless is pointless.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Its not pointless but if you want to keep that sky is falling thinking, by all means
Bootup said:
Why are people still on this 'systemless is now obsolete' thinking all of a sudden? One of systemless main original intents is to make ota/updates easier to do when you're rooted; AP working was just a side, albeit temporary, benefits of this.
---------- Post added at 11:57 PM ---------- Previous post was at 11:56 PM ----------
Its not pointless but if you want to keep that sky is falling thinking, by all means
Click to expand...
Click to collapse
Everyone has their own use case, and for some it's pointless, no matter the initial intent of Systemless root. But, I'll make sure to go into a building, or underground so I won't get hurt when the sky falls ?
Sent from my Nexus 6P using Tapatalk
bouchigo said:
Everyone has their own use case, and for some it's pointless, no matter the initial intent of Systemless root. But, I'll make sure to go into a building, or underground so I won't get hurt when the sky falls ?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Anyone that thinks it's pointless..... Hasn't a clue... Sorry, not sorry! ?
Sent from my Nexus 6P using Tapatalk
Very detailed guide, but you could have simply said:
Root/TWRP your phone <insert root guide>
Install Xposed <insert xposed thread>
Download Snapprefs <insert snapprefs thread>
I never experienced any issues with the Snapchat camera not working when following those guides, and the login issue isn't 6P specific, the Snapprefs thread has info on this as well. I went back to stock though, even though I miss snapprefs.
geoff5093 said:
Very detailed guide, but you could have simply said:
Root/TWRP your phone <insert root guide>
Install Xposed <insert xposed thread>
Download Snapprefs <insert snapprefs thread>
I never experienced any issues with the Snapchat camera not working when following those guides, and the login issue isn't 6P specific, the Snapprefs thread has info on this as well. I went back to stock though, even though I miss snapprefs.
Click to expand...
Click to collapse
Well excuse me for trying to be helpful. lol
I haven't been able to get this working, though of course I'm doing it with different versions.
I'm running the MMB29Q build, SuperSU 2.67, TWRP 3.0.0-0.
Process:
1) Flash full stock build.
2) Reboot to system, set up device
3) Flash TWRP, SuperSU.
- fully functioning, rooted device. All is good here.
4) Select "Enable SU During Boot" and "Trust system user"
5) Reboot to TWRP, install xposed-v80-sdk23-arm64.zip
6) Wipe cache/Dalvik, reboot to system
NFC Stopped working loop.
I've tried several variations on the above and been googling fiercely, but to no success. Always NFC force closure loop.
Any advice?
Wintersdark said:
I haven't been able to get this working, though of course I'm doing it with different versions.
I'm running the MMB29Q build, SuperSU 2.67, TWRP 3.0.0-0.
Process:
1) Flash full stock build.
2) Reboot to system, set up device
3) Flash TWRP, SuperSU.
- fully functioning, rooted device. All is good here.
4) Select "Enable SU During Boot" and "Trust system user"
5) Reboot to TWRP, install xposed-v80-sdk23-arm64.zip
6) Wipe cache/Dalvik, reboot to system
NFC Stopped working loop.
I've tried several variations on the above and been googling fiercely, but to no success. Always NFC force closure loop.
Any advice?
Click to expand...
Click to collapse
Aha! Quoting myself, as I've fixed it.
There's a new release of SuperSU 2.68BETA, and installing that has allowed me to perform the steps above successfully.
So, if anyone else is having my problem, give that a go.
No matter what I do I can't get snapprefs to work. I am using Casper as an alternative. I was able.to use Android Pay before Google submarined the work around but never snapprefs. Any ideas would be greatly appreciated.
thanks for the guide, is the snapchat apk version specific/modified in some way, or can we just grab the latest version off the site that was linked/google play?
Related
This is for both US Cellular Samsung S6 and S6 Edge variant. Thanks also goes to @g.lewarne for his work on Unikernel as a couple of their ramdisk/kernel commits were needed to get this going. Also, thanks to @datajosh for this template And @bpdev for testing the 925R4 version...
This will trip KNOX. It will. Trip. KNOX. IF YOU HAVE NOT TRIPPED KNOX YET - THIS WILL TRIP IT. ALSO - you CANNOT downgrade after you take the OTA so be sure you want it.
I hope that's clear enough?
Instructions:
After you've booted into OF7, go to Settings > About device and tap Build number 7 times to enable Developer Mode.
Go back and select Developer options and turn on OEM unlocking
Reboot in to download mode (Power + Home + Volume Down)
Use ODIN to flash 925R4root.tar or 920R4root.tar (depending on your device)
After your phone boots you will now have root!
If you notice constant messages about security issues because of KNOX and the kernel being permissive. To get rid of these, open Titanium Backup (or your personal favorite app freezing app) and freeze SecurityLogAgent.
Downloads
925R4 - http://1drv.ms/1HeDWXO
925R4 Source
920R4 - http://1drv.ms/1NUVJ8B This is untested...I did not have a tester for this version....
920R4 Source
The 925R4 version may or may not work with the Sprint 925P variant...no working data confirmed!
ENJOY!
Man I wish we could just find a damn exploit already lol gone this long without tripping Knox. And with the fact that I've received the "Fingerprint scanner has encountered an error, use your backup password." error 4-5x already I'm worried about tripping Knox, although you'd think they'd still fix that considering just rooting shouldn't break the scanner lol.
So this requires me to stay on that kernel huh? I couldn't go back to stock kernel huh?
cpfeifer said:
Man I wish we could just find a damn exploit already lol gone this long without tripping Knox. And with the fact that I've received the "Fingerprint scanner has encountered an error, use your backup password." error 4-5x already I'm worried about tripping Knox, although you'd think they'd still fix that considering just rooting shouldn't break the scanner lol.
So this requires me to stay on that kernel huh? I couldn't go back to stock kernel huh?
Click to expand...
Click to collapse
You could go back to the stock kernel, but you would loose root. Also as stated above you would trip knox.
someone on a sprint s5 edge said the only thing they noticed didnt work was data..just posting for them since they under 10 post..so thats awesome! if we could get data goin..we can have root!!
---------- Post added at 03:29 PM ---------- Previous post was at 03:17 PM ----------
this kernel has working data on the edge...if you could port the data stuff in yours it should be fine http://forum.xda-developers.com/spr...t/5-1-1-stock-of7-kernel-root-7-4-15-t3150350
Does this method then require flashing a custom recovery then SuperSU.zip (or CF Auto Root)? Just curious because all that's in the .rar is a boot.img and some are having issues with following the method and not having root immediately.
borxnx said:
Does this method then require flashing a custom recovery then SuperSU.zip (or CF Auto Root)? Just curious because all that's in the .rar is a boot.img and some are having issues with following the method and not having root immediately.
Click to expand...
Click to collapse
It should be flashed using ODIN...I believe I updated the link in the OP to fix that issue since I derp'd...
Sent from my SM-G920P using Tapatalk
Flashed on a 920r4, but it is not rooted.
Funny enough, I get knox warnings about threats and stuff. But when I check with root checker, I don't have root.
sintro said:
Flashed on a 920r4, but it is not rooted.
Funny enough, I get knox warnings about threats and stuff. But when I check with root checker, I don't have root.
Click to expand...
Click to collapse
Perhaps you still have to install SuperSU or another super user app.
Sent from my SM-G925R4 using Tapatalk
cpfeifer said:
Perhaps you still have to install SuperSU or another super user app.
Sent from my SM-G925R4 using Tapatalk
Click to expand...
Click to collapse
I reflashed back to stock, then installed supersu. Then opened it up, obviously it said "supersu binary not installed". Next, I flashed this kernel and once booted up supersu still repeats the previous message. In addition, root checker shows that phone is not rooted.
The only thing in the .tar file, for 920r4 at least because that's all I downloaded, is a modified kernel. Nothing about SuperSU or its binaries. This method alone does not root. This merely installs a modified SELinux permissive stock kernel. More steps are necessary to obtain root. You must flash either CF Auto Root or a custom kernel + SuperSU.zip.
Bump? Nobody? OP, amirite? Because the method you describe, and thank you so much for the SELinux permissive kernel, does not complete all of the steps between stock and fully rooted.
borxnx said:
Bump? Nobody? OP, amirite? Because the method you describe, and thank you so much for the SELinux permissive kernel, does not complete all of the steps between stock and fully rooted.
Click to expand...
Click to collapse
920R4 http://1drv.ms/1HzSj73 try this...
I've redone the ramdisk and use the exact same files on my 920P...and kept the carrier parts for US Cellular...
Let me know if this works...
djvoleur said:
920R4 http://1drv.ms/1HzSj73 try this...
I've redone the ramdisk and use the exact same files on my 920P...and kept the carrier parts for US Cellular...
Let me know if this works...
Click to expand...
Click to collapse
Thank you for redoing the ramdisk.
Will try out and let you know.
Anyone experiencing issues with 925r4? I have service but see no signal bars no matter where I go.
https://youtu.be/y7EpSirtf_E
djvoleur said:
920R4 http://1drv.ms/1HzSj73 try this...
I've redone the ramdisk and use the exact same files on my 920P...and kept the carrier parts for US Cellular...
Let me know if this works...
Click to expand...
Click to collapse
This does indeed work. Thank you so much!
Edit...Added instructions I used to complete the root process.
First of all, I wanted to thank the OP of this thread for posting this guide and getting me headed in the right direction.
Credit to @djvoleur
I just wanted to share the method I used to root my USC Galaxy S6 with the Android 5.1.1 update. You will notice that the instructions are similar in the beginning. I added the extra steps that I used to complete the root process. I do not know if this method works for the Edge version.
As the OP states: This will trip knox. Personally, it doesn’t matter to me. I am too impatient and too much of a flash-a-holic to wait for a method that doesn’t trip knox.
Also, I am not a dev and I am unable to answer any questions other than how I obtained root. I am not responsible for any damage that might happen to your phone. Follow this procedure at your own risk.
Having stated these disclaimers, it really isn’t very difficult to implement. I’ve done it twice and both times worked perfectly.
Files you will need for flashing in Odin:
Odin 3.10.7 found here: http://tinyurl.com/puyq4v9
Rooted kernel 920R4root.tar found in the OP.
TWRP 2.7.8.0 (Sprint version, but I can confirm it worked for me. YMMV.) Here: http://tinyurl.com/phvrkaf
Files for flashing in TWRP:
Updated V-Kernel 920R4-071615.zip found here: http://tinyurl.com/o2h8rv4
Super SU v2.49 (beta) found here: http://tinyurl.com/or6mmqr
Now, PLEASE read these instructions before starting so that you will have a good understanding of what to do. After reading, you may begin.
Don’t forget to put the files for flashing in TWRP on your SD card (phone) before beginning this process.
After you've booted into OF7, go to Settings > About device and tap Build number 7 times to enable Developer Mode.
Go back and select Developer options and turn on OEM unlocking
Boot into download mode (Power + Home + Volume Down)
Use ODIN to flash 920R4root.tar
Use ODIN to flash TWRP and make sure that reboot is NOT checked in options.
Unplug the phone and hold the Power + Volume Down key to reboot. When the screen goes blank, quickly hold the Power + Home + Volume Up key to boot into TWRP. If it doesn’t boot to TWRP, you may have to start over.
In TWRP flash the updated V-Kernel file first, then the Super SU file, and then reboot.
After your phone boots you will now have root!
If you notice constant messages about security issues because of KNOX and the kernel being permissive. To get rid of these, open Titanium Backup (or your personal favorite app freezing app) and freeze SecurityLogAgent. (Worked for me.)
You now should be able to install Chainfire's Super SU app from the Play Store, and you can also use Root Checker to confirm you are rooted.
Good Luck!
Would this work on G920R7... J4 (rather than OF7) 5.1.1? That's what I have.
I see there is a PC1 update available also for my G920R7 which is 6.0 marshmallow.
Hard to believe I've had this device for a year with no root... Anyone can help me get this rooted? Thanks!
so after installing the intial kernel that did not work I scrolled through and saw the updated version...you should probably update the link for the untested r4 to the working version later posted...
my problem is that Im unable to load in anything but download mode due to kernel not seandroid enforcing basically not enabling me to load into recovery mode so I need the zipped version of the kernel to install via odin in download mode if possible otherwise im waiting on a 2 hour download of the stock kernal to install
i just picked up a us cellular note 5 (SM-N920R4 on OJ5)
its trying to download and update to a new firmware so i turned off wifi and that appears to stop it but i cant do any of the gazillion updates from play store like we normally do after you receive a new phone or do a factory data reset.
please advise what i need to do since im already on OJ5 and can not connect to wifi as it will auto install whatever update its trying to download.
thanks again
en11gma said:
i just picked up a us cellular note 5 (SM-N920R4 on OJ5)
its trying to download and update to a new firmware so i turned off wifi and that appears to stop it but i cant do any of the gazillion updates from play store like we normally do after you receive a new phone or do a factory data reset.
please advise what i need to do since im already on OJ5 and can not connect to wifi as it will auto install whatever update its trying to download.
thanks again
Click to expand...
Click to collapse
Use TB to remove the update apps - green phone icons in TB. That's how it always gets stopped on any samsung.
*** 10/13/2016 - This method is obviously VERY buggy and uses very depreciated files. I'm not going to troubleshoot more on this and am going to be testing/banging on Magisk v7 here on out as that's the most future proof. If I get this working I will post those instructions in the place of this guide***
10/3/2016 - I have updated the order of steps and provided files where I can redistribute them hopefully this resolves the issues people have been having.
You must be rooted and bootloader unlocked
1. Update SuperSu to v2.78 SR1 using my modified installer (workaround for .zip installer crash)
Download UPDATE-SuperSU-v2.65-Superuser_apk_v2.78_SR1_lokismile.zip (attached)
After install open SuperSu, update binary
Reboot
2. Download and install suhide-0.53.zip here (cannot be redistributed) http://forum.xda-developers.com/apps/supersu/suhide-t3450396
3. Download and install *exactly* xposed-v86.2-sdk23-topjohnwu.zip (attached)
4. Downoad and install Install xposed manager 3.0 alpha4 (attached)
Note: You will get an error from any cold boot, soft boot to enable xposed (The first softboot will take a while)
Tested on B27 with SafetyNet and Pokemon Go, need someone to test Android Pay and B20
Note: I had trouble on one of my machines getting it to prompt for ADB authorization, so be sure to pair with your desktop before attempting.
It goes without saying; brick is possible. Have fun! Please provide feedback if the updated method works for you or not.
10/13/2016 - This method is obviously VERY buggy and uses very depreciated files. I'm not going to troubleshoot more on this and am going to be testing/banging on Magisk v7 here on out as that's the most future proof.
<reserved>
Android Pay does not work and with SafetyNet I get a fail for the CTS profile match. Sorry
Did you make sure you soft rebooted in Xposed? Was it a clean systemless xposed install?
lokissmile said:
Did you make sure you soft rebooted in Xposed? Was it a clean systemless xposed install?
Click to expand...
Click to collapse
I followed your instructions exactly so yes
lokissmile said:
You must be rooted and bootloader unlocked
Update SuperSu to v2.78 SR1 (workaround for .zip installer crash)
Get SuperSU v2.78 SR1 .zip here http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Extract SuperUser.apk (v2.78 SR1) from "common" folder in .zip
Install Superuser.apk (v2.78 SR1)
Open SuperSu, update binary
Reboot
Download and install *exactly* xposed-v86.2-sdk23-topjohnwu.zip here http://forum.xda-developers.com/attachment.php?attachmentid=3832616&d=1470277034
Downoad and install Install xposed manager 3.0 alpha4 from here http://forum.xda-developers.com/devdb/project/dl/?id=20416&task=get
Note: You will get an error from any cold boot, soft boot to enable xposed (The first softboot will take a while)
Download and install suhide here http://forum.xda-developers.com/apps/supersu/suhide-t3450396
Tested on B27 with SafetyNet and Pokemon Go, need someone to test Android Pay and B20
Note: I had trouble on one of my machines getting it to prompt for ADB authorization, so be sure to pair with your desktop before attempting.
It goes without saying; brick is possible. Have fun!
Click to expand...
Click to collapse
Can you uploaded xposed 86.2? Seems like it was recently taken off the link you posted.
Oogar said:
Can you uploaded xposed 86.2? Seems like it was recently taken off the link you posted.
Click to expand...
Click to collapse
Attached to OP, please try the updated method including the new install order and modded SuperSu installer. Feedback positive or negative appreciated!
Great, worked for me! Thank you. Haha tried this for hours on end last week, but I guess I didn't do the right steps with the right files in the right order.
Oogar said:
Great, worked for me! Thank you. Haha tried this for hours on end last week, but I guess I didn't do the right steps with the right files in the right order.
Click to expand...
Click to collapse
Super glad to hear it!
lokissmile said:
Super glad to hear it!
Click to expand...
Click to collapse
Should mention it *looks* like android pay works too - I'm in Canada so I can't test officially, but I definitely got farther in the app then I did last week. Was able to get to the step where you add a credit card.
lokissmile said:
Super glad to hear it!
Click to expand...
Click to collapse
Sorry to be dense but how are you soft rebooting on this device?
I'm referring to your step 4
*mj13* said:
Sorry to be dense but how are you soft rebooting on this device?
I'm referring to your step 4
Click to expand...
Click to collapse
When you are in the Xposed software and the installed but not active is up and yellow. It's the menu in the upper right.
So...after having this work, I noticed my Facebook/FB Messenger were crashing on launch. Tried fixes, no luck.
Started from scratch, the apps break right after installing xposed 86.2. Not sure what's going on there... can you test OP?
Went a step further and tried throwing Magisk v7 in the mix so I could use the new 86.6 xposed, but Pokémon Go won't open at the end of it all.
Oogar said:
So...after having this work, I noticed my Facebook/FB Messenger were crashing on launch. Tried fixes, no luck.
Started from scratch, the apps break right after installing xposed 86.2. Not sure what's going on there... can you test OP?
Went a step further and tried throwing Magisk v7 in the mix so I could use the new 86.6 xposed, but Pokémon Go won't open at the end of it all.
Click to expand...
Click to collapse
Have you tried wiping cache/davlik after installing xposed. It definitely needs to rebuild the davlik files.
I'm currently testing Magisk v7 myself and will report back and update the OP.
lokissmile said:
Have you tried wiping cache/davlik after installing xposed. It definitely needs to rebuild the davlik files.
I'm currently testing Magisk v7 myself and will report back and update the OP.
Click to expand...
Click to collapse
Did the cache wipe work for xposed? I'm having the same issue with POGO on Magisk v7. If you just need root then my supersu installer + suhide should work as is. The instability may be the exact reason that the 85.2 of xposed was pulled., with no thread that's just wild speculation on my part. If we can get it working Magisk v7 would be the way to go as xposed 86.6 works without a soft reboot.
lokissmile said:
Did the cache wipe work for xposed? I'm having the same issue with POGO on Magisk v7. If you just need root then my supersu installer + suhide should work as is. The instability may be the exact reason that the 85.2 of xposed was pulled., with no thread that's just wild speculation on my part. If we can get it working Magisk v7 would be the way to go as xposed 86.6 works without a soft reboot.
Click to expand...
Click to collapse
No dice with the cache wipe... FB works up until I install xposed 86.2, then right after crashes on open. Tried wiping dalvik and cache before and after the installation of xposed 86.2 - still the same result.
Thought maybe the next step was to Frankenstein an installation of 86.6 using the 86.2 zip - although I have no idea if that dependency on Magisk for xposed 86.6 is necessary or just a road block. Tried with no luck so far.
Facebook
Oogar said:
No dice with the cache wipe... FB works up until I install xposed 86.2, then right after crashes on open. Tried wiping dalvik and cache before and after the installation of xposed 86.2 - still the same result.
Thought maybe the next step was to Frankenstein an installation of 86.6 using the 86.2 zip - although I have no idea if that dependency on Magisk for xposed 86.6 is necessary or just a road block. Tried with no luck so far.
Click to expand...
Click to collapse
Yes, I'm also having the same problem with Facebook and messenger. Tired wiping and installing cashe, reinstalling, still no luck. It's seems to be the xpose version cuasing the issue not suhide.
I know this seems obvious but have you tried clearing data on facebook through the application manager or an uninstall / reinstall of Facebook
? I personally have not had any problems myself but I always started from a factory reset and a wipe/ restore of system and boot in my testing. Are either of you comfortable trying out those steps and reporting back.
1. Try clearing Facebooks data/cache through app settings.
2. Try a reisntall of facebook through the play store.
3. If you are brave; try a factory reset, get SU and xposed working then install Facebook.
lokissmile said:
I know this seems obvious but have you tried clearing data on facebook through the application manager or an uninstall / reinstall of Facebook
? I personally have not had any problems myself but I always started from a factory reset and a wipe/ restore of system and boot in my testing. Are either of you comfortable trying out those steps and reporting back.
1. Try clearing Facebooks data/cache through app settings.
2. Try a reisntall of facebook through the play store.
3. If you are brave; try a factory reset, get SU and xposed working then install Facebook.
Click to expand...
Click to collapse
I've tried 1 and 2, factory reset cannot do with bricking like last time lol.
lokissmile said:
I know this seems obvious but have you tried clearing data on facebook through the application manager or an uninstall / reinstall of Facebook
? I personally have not had any problems myself but I always started from a factory reset and a wipe/ restore of system and boot in my testing. Are either of you comfortable trying out those steps and reporting back.
1. Try clearing Facebooks data/cache through app settings.
2. Try a reisntall of facebook through the play store.
3. If you are brave; try a factory reset, get SU and xposed working then install Facebook.
Click to expand...
Click to collapse
Tried some variation of all three with no luck.
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.
(All credit goes to wanam for providing Xposed for TouchWiz roms)
I am not sure if this needs a thread but since i was searching for this information i'm making one for the Xposed fans with an A3 2017.
Because i don't have enough time to test more configurations i can't say if this will or will not work on any other configuration besides the one i have. Feel free to backup everything (using a recovery like TWRP or CWM) and try flashing Xposed yourself. Read the bottom of the post on how to get into your recovery when having a bootloop. I do not take any responsibility for bricked devices and any other damages.
I mostly followed the steps in this thread but i'll write the steps here as well.
This will only work with stock or stock-based roms, for AOSP based roms, use normal Xposed flashables
A recovery like CWM or TWRP (guide) is required.
Backup your /system partition or reckon that you might lose data. Flashing Xposed only affects /system
Install the Xposed 3.1 apk (requires "Unknown sources" to be allowed in system settings)
Go to your recovery by shutting down your phone and holding Volume Up + Home while powering it on
Flash this zip file for Xposed on Samsung devices (ARM). You might find newer versions here (choose ARM for this phone, not ARM64).
Reboot and wait for up to 15 minutes. It might bootloop a couple times and you might have to wait for app optimization for some more minutes
Enjoy the flexibility of Xposed
If your device is bootlooping for more than 10 minutes it's highly likely that Xposed is not working for you.
Note that using Volume Down + Power will restart your device but will always attempt to restart Android. In order to get to your recovery charge your device which will make VolDown + Power shut down the phone instead of restarting it. From there you can VolUp + Home and power it on to boot into recovery.
You can attempt to flash the uninstaller in order to fix the bootloop or if Xposed is just not working and you wanna get rid of it. If that doesn't help, restore your backup (will always work, flashing the uninstaller is just quicker).
Known bugs on the A3 2017:
- none (will add from comments or if i find any)
Sources:
https://github.com/wanam/Xposed
https://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960
https://forum.xda-developers.com/sa.../samsung-sm-a520f-2017-kernel-source-t3557622
Hello,
why is arm64 version not working / 64bit ist not recognised by xposed?
It's definitely a 64bit CPU with arm64v8a instruction set (Aarch64).
So why the installation of arm64 is blocked?
SinusStudios said:
(All credit goes to wanam for providing Xposed for TouchWiz roms)
I am not sure if this needs a thread but since i was searching for this information i'm making one for the Xposed fans with an A3 2017.
Because i don't have enough time to test more configurations i can't say if this will or will not work on any other configuration besides the one i have. Feel free to backup everything (using a recovery like TWRP or CWM) and try flashing Xposed yourself. Read the bottom of the post on how to get into your recovery when having a bootloop. I do not take any responsibility for bricked devices and any other damages.
I mostly followed the steps in this thread but i'll write the steps here as well.
This will only work with stock or stock-based roms, for AOSP based roms, use normal Xposed flashables
A recovery like CWM or TWRP (guide) is required.
Backup your /system partition or reckon that you might lose data. Flashing Xposed only affects /system
Install the Xposed 3.1 apk (requires "Unknown sources" to be allowed in system settings)
Go to your recovery by shutting down your phone and holding Volume Up + Home while powering it on
Flash this zip file for Xposed on Samsung devices (ARM). You might find newer versions here (choose ARM for this phone, not ARM64).
Reboot and wait for up to 15 minutes. It might bootloop a couple times and you might have to wait for app optimization for some more minutes
Enjoy the flexibility of Xposed
If your device is bootlooping for more than 10 minutes it's highly likely that Xposed is not working for you.
Note that using Volume Down + Power will restart your device but will always attempt to restart Android. In order to get to your recovery charge your device which will make VolDown + Power shut down the phone instead of restarting it. From there you can VolUp + Home and power it on to boot into recovery.
You can attempt to flash the uninstaller in order to fix the bootloop or if Xposed is just not working and you wanna get rid of it. If that doesn't help, restore your backup (will always work, flashing the uninstaller is just quicker).
Known bugs on the A3 2017:
- none (will add from comments or if i find any)
Sources:
https://github.com/wanam/Xposed
https://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960
https://forum.xda-developers.com/sa.../samsung-sm-a520f-2017-kernel-source-t3557622
Click to expand...
Click to collapse
knzsys said:
Hello,
why is arm64 version not working / 64bit ist not recognised by xposed?
It's definitely a 64bit CPU with arm64v8a instruction set (Aarch64).
So why the installation of arm64 is blocked?
Click to expand...
Click to collapse
To be honest i flashed 32 bit xposed because i searched for the phones architecture and found 32 bit but that must be a misinformation.
I'm surprised now that it's working on my phone!
Thanks for mentioning this, if you have time feel free to safely try out both versions and report back what's working and what's not.
knzsys said:
why is arm64 version not working / 64bit ist not recognised by xposed?
It's definitely a 64bit CPU with arm64v8a instruction set (Aarch64).
So why the installation of arm64 is blocked?
Click to expand...
Click to collapse
Can't find a reason why our 64-bit phone is not recognized bit the 64-bit Xposed
I you want to install the 64-bit Xposed: got through Magisk
Don't know if it has a direct link: had lotz of reboot with 32-bit Xposed; nearly no reboot with 64-bit Xposed.
PS: Don't get too addict to Xposed has it will stop running when we'll get Nougat
The 64bit version will not work because Samsung shipped the SM-A320F with 32bit Android, even though it has a 64bit-capable SoC.
Im Wondering something here ... 32 bit os on our phone, no custom roms .. etc ... but the J7 2016 has the same CPU, same ram, storage, screen res ... you get the point .. i just wonder if a rom from that would ... and its 64 bit ... i mean, its the same damm SoC
are there any news for android 7 to get xposed without magisk. I have supersu root
y2kadir said:
are there any news for android 7 to get xposed without magisk. I have supersu root
Click to expand...
Click to collapse
Yes, you just have to search the Xposed thread and read.
Pat750 said:
Yes, you just have to search the Xposed thread and read.
Click to expand...
Click to collapse
ok but I just did it and coulnd`t find anything. can you tell me where to find?
y2kadir said:
ok but I just did it and coulnd`t find anything. can you tell me where to find?
Click to expand...
Click to collapse
Well I did, but if you can't even find it, I think it's better for you not to use it. Sorry.
Pat750 said:
Well I did, but if you can't even find it, I think it's better for you not to use it. Sorry.
Click to expand...
Click to collapse
why are you talking foolish ****. if you don't wanna help other people go home.
y2kadir said:
why are you talking foolish ****. if you don't wanna help other people go home.
Click to expand...
Click to collapse
OK here's something to start with.
https://forum.xda-developers.com/showthread.php?t=3034811
but please read the threads there are some good advice's.
Pat750 said:
OK here's something to start with.
https://forum.xda-developers.com/showthread.php?t=3034811
but please read the threads there are some good advice's.
Click to expand...
Click to collapse
I only found this in the thread "The first fixes have found their way into version 88.1, only available for Nougat. That includes especially some fixes for Samsung ROMs, but might also fix bootloops and slowdowns on other devices. Besides that, I think I fixed a MIUI incompatibility, not sure if it works now (and to be honest, I don't give much priority to MIUI). There are still unfixed issues on the queue, and again, please keep reporting whatever you find." but this information is not confirming me that its working.
Hey there, yesterday I've updated my phone to OOS 10.0.8. Everything went fine, phone is running, but since I've installed that update SafetyNet keeps failing in both, basicIntegrity and ctsProfile.
I have installed Magisk 20.4 and Magisk Manager 7.5.1.
Magisk hide is enabled. I have no modules installed.
Anyone else having this issue or know how to fix it?
Yep, same problem here. Can't seem to fix it either.
Exentric90 said:
Yep, same problem here. Can't seem to fix it either.
Click to expand...
Click to collapse
Do some reading ... https://twitter.com/topjohnwu/status/1237656703929180160
(and for me it is still OK)
foobar66 said:
Do some reading ... https://twitter.com/topjohnwu/status/1237656703929180160
(and for me it is still OK)
Click to expand...
Click to collapse
Yeah I've updated to the beta. So that might be it.
Anyway that sucks. So we're basically screwed if we'd like to have the latest security updates and still keep root.
Sajito said:
Hey there, yesterday I've updated my phone to OOS 10.0.8. Everything went fine, phone is running, but since I've installed that update SafetyNet keeps failing in both, basicIntegrity and ctsProfile.
I have installed Magisk 20.4 and Magisk Manager 7.5.1.
Magisk hide is enabled. I have no modules installed.
Anyone else having this issue or know how to fix it?
Click to expand...
Click to collapse
i have exactly the same configuration, and my safetynet test passes both, cts and basic, as it was before the update
foobar66 said:
Do some reading ... https://twitter.com/topjohnwu/status/1237656703929180160
(and for me it is still OK)
Click to expand...
Click to collapse
I've read about that. I know that since those changes Magisk Hide is not enabled in default installation, that's why I made sure it is enabled on my device. Also as far as I know, those changes should only affect ctsProfile, but not basicIntegration. For me both is failing.
kaiowas82 said:
i have exactly the same configuration, and my safetynet test passes both, cts and basic, as it was before the update
Click to expand...
Click to collapse
But since it's working for you two: Do you use any modules?
Sajito said:
But since it's working for you two: Do you use any modules?
Click to expand...
Click to collapse
systemless hosts and google dialer framework
kaiowas82 said:
systemless hosts and google dialer framework
Click to expand...
Click to collapse
kaiowas82 said:
i have exactly the same configuration, and my safetynet test passes both, cts and basic, as it was before the update
Click to expand...
Click to collapse
I toggled the Magisk hide button in settings and rebooted and it passed both. But, if you click on safetynet a second time it fails. So far I haven't received notification of Google Pay software issue I'm assuming it's good. Guess I'll find out when I go to pay for something at the store.
slapman said:
I toggled the Magisk hide button in settings and rebooted and it passed both. But, if you click on safetynet a second time it fails. So far I haven't received notification of Google Pay software issue I'm assuming it's good. Guess I'll find out when I go to pay for something at the store.
Click to expand...
Click to collapse
just done the test 3 times in a row and always passes, i think you have some other underlying issue
kaiowas82 said:
just done the test 3 times in a row and always passes, i think you have some other underlying issue
Click to expand...
Click to collapse
I have no idea what it could be unless when I did
OTA update from local storage and then restored images on Magisk and installed to inactive slot (after ota). Maybe I should redo the whole thing and use 10.0.8 patched boot.img besides that I have no clue before update had no issues. Anyway I have Viper4android installed OOS native call recording YouTube Vanced and a slew of other modules working so if I can't pay with GP no big deal but it would be nice to have everything working. Be safe stay home and God bless.
I've tried several things that came to my mind, but they all don't work.
So I'll list what I've done, maybe anyone has an idea how to pass SafetyNet again without having to factory reset.
I got the OTA notification, so I downloaded and installed it. Before rebooting I went to Magisk Manager and installed Magisk to the inactive slot.
I forgot to disable the Riru Core and EdXposed Module, but the update went fine.
After the reboot I've noticed that SafetyNet test is failing. I know for sure SafetyNet was succeeding before the udate, since I was playing Pokemon Go before the update. That's impossible while SafetyNet fails.
As I said the weird thing is, both tests are failing, not just ctsProfile. First I made sure Magisk Hide was on and set for all required apps. Also toggled the setting, to make sure it's active. Root hiding is working fine btw.
So I thought maybe having EdXposed installed broke something. I uninstalled EdXposed completely, toggled everything again and rebooted. No luck.
I downloaded the OOS 10.0.8 Update again and installed it through "Locale Update", installed Magisk to inactive partition and rebooted. This time no modules installed at all. Still no luck.
I uninstalled Magisk (completely, not just the manager), rebooted and installed Magisk again. Got root, but the test still failing.
I've not used any module except EdXposed and there's only one Xposed Module I use, to enable background playback for YouTube.
Any ideas what's broken?
I really don't want to factory reset. Alongside Google Pay I use an App from my bank called "Mobiles Bezahlen". It's similar to Google Pay, but it's like using the physical card. Problem with that app is, a card can only be registered 7 times before the app will deny to register that card again. The only way to be able to register my card again is to order a new physical card.
I have not found a way to make a backup of that virtual card.
man i swear i tried somthing and it worked and i pass SafetyNet right now. i'am not a professional and i dont know what exactly i did that fixed the problem. but i will tell you what i did.
- i had some problems with my phone so i did MSM-flashtool it to get it back to clean
- then i installed latest magisk application 7.5.1 from github.
-patched my boot image and flashed it
-i got safetynet check failed.
-i then removed magisk by installing the stock boot image again.
-then i downloaded an older version of magisk which is 7.4.0.
-flashed the same patched boot image again.
WALLAH! i passed safteynet and magisk hide works with bank and google pay apps agian ! <3
-then i updated magisk from the app both manager and magisk zip
-rebooted
-still my safetynet passes! try it and tell me guys!
mastrok said:
man i swear i tried somthing and it worked and i pass SafetyNet right now. i'am not a professional and i dont know what exactly i did that fixed the problem. but i will tell you what i did.
- i had some problems with my phone so i did MSM-flashtool it to get it back to clean
- then i installed latest magisk application 7.5.1 from github.
-patched my boot image and flashed it
-i got safetynet check failed.
-i then removed magisk by installing the stock boot image again.
-then i downloaded an older version of magisk which is 7.4.0.
-flashed the same patched boot image again.
WALLAH! i passed safteynet and magisk hide works with bank and google pay apps agian ! <3
-then i updated magisk from the app both manager and magisk zip
-rebooted
-still my safetynet passes! try it and tell me guys!
Click to expand...
Click to collapse
Very cool, I did something else cause I really like my setup and to tell you the truth I didn't want to go through the whole process again. I did a Google search and found a tutorial on YouTube using edxposed. I followed the tutorial and I passed Safety net I already tested like 5 times but wait a minute... I just tried still passed. Wasn't sure if we can post from other sites but if we can just reply and I will post the link to the video.
mastrok said:
man i swear i tried somthing and it worked and i pass SafetyNet right now. i'am not a professional and i dont know what exactly i did that fixed the problem. but i will tell you what i did.
- i had some problems with my phone so i did MSM-flashtool it to get it back to clean
- then i installed latest magisk application 7.5.1 from github.
-patched my boot image and flashed it
-i got safetynet check failed.
-i then removed magisk by installing the stock boot image again.
-then i downloaded an older version of magisk which is 7.4.0.
-flashed the same patched boot image again.
WALLAH! i passed safteynet and magisk hide works with bank and google pay apps agian ! <3
-then i updated magisk from the app both manager and magisk zip
-rebooted
-still my safetynet passes! try it and tell me guys!
Click to expand...
Click to collapse
How did you install Magisk using 7.4.0? I've installed Magisk Manager 7.4.0, but it doesn't allow me to install Magisk itself without updating first to 7.5.1.
slapman said:
Very cool, I did something else cause I really like my setup and to tell you the truth I didn't want to go through the whole process again. I did a Google search and found a tutorial on YouTube using edxposed. I followed the tutorial and I passed Safety net I already tested like 5 times but wait a minute... I just tried still passed. Wasn't sure if we can post from other sites but if we can just reply and I will post the link to the video.
Click to expand...
Click to collapse
What EdXposed Module are you using? HiddenCore Module? I've tried that. After enabling it the test in Magisk Manager will succeed, but any other SafetyNet Checker fails. Still no Pokemon Go and SafetyNet for me
Sajito said:
How did you install Magisk using 7.4.0? I've installed Magisk Manager 7.4.0, but it doesn't allow me to install Magisk itself without updating first to 7.5.1.
What EdXposed Module are you using? HiddenCore Module? I've tried that. After enabling it the test in Magisk Manager will succeed, but any other SafetyNet Checker fails. Still no Pokemon Go and SafetyNet for me
Click to expand...
Click to collapse
bro just remove any rooting method you have right now. install the old 7.4.0 version. patch your boot image and if you cant try to find the patched image on the internet. flash it via fast boot and your root is successful. now update magisk and you are done
m4str0k said:
bro just remove any rooting method you have right now. install the old 7.4.0 version. patch your boot image and if you cant try to find the patched image on the internet. flash it via fast boot and your root is successful. now update magisk and you are done
Click to expand...
Click to collapse
I tried exactly that, but I can't patch the boot image with 7.4.0, since it tells me I have to update to 7.5.1 first.
edxposed it's the reason why you cannot pass safetynet
kaiowas82 said:
edxposed it's the reason why you cannot pass safetynet
Click to expand...
Click to collapse
As I already said in first post, EdXposed is not installed anymore. I could pass SafetyNet even with EdXposed before the update though.
Also SafetyNet passes with EdXposed installed on my LG G6.
10.3.2 - Device does not meet the minimum security requirements for this application
Hello, there.
I badly need your assistants. I'm not able to use a bank application as it states as "This device does not meet the minimum security requirements for this application", I flashed patched recovery for Magisk Maanger (7.5.1)& the SafetyNet Check shows as "Success". Both ctsProfile & basicIntegrity is green with true against it.
I repacked the Magisk Manager to different and enabled Magisk Hide option; also under "Magisk Hide" section, I have enabled the said bank application but still the above said error message popups. I badly want to access this application. I also face same issue with other gov application.
NOTE: I have other bank app which works perfectly by hiding it under "Magisk Hide" section but some Gov & this bank application doesn't work.
Please help.
vinu4u4ever said:
Hello, there.
I badly need your assistants. I'm not able to use a bank application as it states as "This device does not meet the minimum security requirements for this application", I flashed patched recovery for Magisk Maanger (7.5.1)& the SafetyNet Check shows as "Success". Both ctsProfile & basicIntegrity is green with true against it.
I repacked the Magisk Manager to different and enabled Magisk Hide option; also under "Magisk Hide" section, I have enabled the said bank application but still the above said error message popups. I badly want to access this application. I also face same issue with other gov application.
NOTE: I have other bank app which works perfectly by hiding it under "Magisk Hide" section but some Gov & this bank application doesn't work.
Please help.
Click to expand...
Click to collapse
Use another SafetyNet Checker app to see if SafetyNet really passes on your device.
If it passes then please create another thread for your problem, since it's not related to this thread at all.