*** 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.
Related
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?
Attached is a Magisk installer zip patched to work on Acclaim. I can only test that it does install properly; if someone that has the hardware could verify that it actually works, I'd be very grateful. Please be sure to not have another root zip installed, as it could effect the outcome. Thanks in advance to any takers.
fddm said:
Attached is a Magisk installer zip patched to work on Acclaim. I can only test that it does install properly; if someone that has the hardware could verify that it actually works, I'd be very grateful. Please be sure to not have another root zip installed, as it could effect the outcome. Thanks in advance to any takers.
Click to expand...
Click to collapse
So might this theoretically work on the Unlegacy AOSP ROMs? Do I need to go through first boot and then flash the zip or can I do all the flashing at once?
nmyshkin said:
So might this theoretically work on the Unlegacy AOSP ROMs? Do I need to go through first boot and then flash the zip or can I do all the flashing at once?
Click to expand...
Click to collapse
Yes, it should work and you don't need to go through first boot. I've had the best luck rebooting back into recovery after flashing the rom, then flashing Magisk.
fddm said:
Attached is a Magisk installer zip patched to work on Acclaim. I can only test that it does install properly; if someone that has the hardware could verify that it actually works, I'd be very grateful. Please be sure to not have another root zip installed, as it could effect the outcome. Thanks in advance to any takers.
Click to expand...
Click to collapse
Does this work on 16GB only or does this include 8GB version?
It should work on both, they run the same ROMs, only requirement is Lollipop+.
Edit: I'm making the assumption users know which ROMs accommodate the 512mb models. Obviously, the ROM needs to be functional for Magisk to work.
fddm said:
Yes, it should work and you don't need to go through first boot. I've had the best luck rebooting back into recovery after flashing the rom, then flashing Magisk.
Click to expand...
Click to collapse
OK, no joy here. After waiting for a couple of hours to download a ROM (!) I finally put it all together. The system hangs at the "N" screen, never getting to the Cyanoboot screen. I tried this on an 8 GB tablet because I didn't want to mess majorly with my 16 GB one, but as you say, the result should be the same
BTW, there were no error messages I detected as the Magisk zip installed.
If you can, these three things might help to catch the problem:
TWRP log from after flashing Magisk(advanced->copy log)
A TWRP backup of your boot partition after flashing Magisk
A link to the ROM you tested
fddm said:
If you can, these three things might help to catch the problem:
TWRP log from after flashing Magisk(advanced->copy log)
A TWRP backup of your boot partition after flashing Magisk
A link to the ROM you tested
Click to expand...
Click to collapse
Sure. I've attached the log and boot backup below (I just zipped the boot backup folder). This is the ROM: https://builds.unlegacy-android.org/aosp-7.1/acclaim/ua_acclaim-7.1.2-20180215-0240.zip
Let me know if there's anything else I can do.
nmyshkin said:
Sure. I've attached the log and boot backup below (I just zipped the boot backup folder). This is the ROM: https://builds.unlegacy-android.org/aosp-7.1/acclaim/ua_acclaim-7.1.2-20180215-0240.zip
Let me know if there's anything else I can do.
Click to expand...
Click to collapse
I repacked the fix with the latest to fix a crash I see. The main problem I see is "- Magisk patched image detected", it thinks it's already patched so it skips it. I got this error with while testing on Ovation with an old TWRP3 SD recovery, please try rebooting back into recovery after flashing the rom if you haven't already (basically reloading TWRP between flashing the rom and Magisk, you do have to flash your rom again to restore the boot image).
fddm said:
I repacked the fix with the latest to fix a crash I see. The main problem I see is "- Magisk patched image detected", it thinks it's already patched so it skips it. I got this error with while testing on Ovation with an old TWRP3 SD recovery, please try rebooting back into recovery after flashing the rom if you haven't already (basically reloading TWRP between flashing the rom and Magisk, you do have to flash your rom again to restore the boot image).
Click to expand...
Click to collapse
Same behavior. I've attached the stuff you asked for before. And I did recycle through TWRP each time as you had suggested.
Your right, sorry, after testing again I can reproduce this error. Going to have a closer look, see if I can correct it. Thank you!
Edit: problem found, fix incoming
nmyshkin said:
Same behavior. I've attached the stuff you asked for before. And I did recycle through TWRP each time as you had suggested.
Click to expand...
Click to collapse
Ok, I found and fixed the bug. I was trying to check for acclaim by cmdline header, where it needs to check the name header. Should work now, and it doesn't seem to need the reboot. Thank you again!
fddm said:
Ok, I found and fixed the bug. I was trying to check for acclaim by cmdline header, where it needs to check the name header. Should work now, and it doesn't seem to need the reboot. Thank you again!
Click to expand...
Click to collapse
OK, so I've got boot
But I did have to do the recycle of TWRP. The first time I tried it without and it threw out all kinds of red errors. Yipes!
Anyway, I now have questions as I'm no magiskan I read about Magisk before and even tried it on a similar ROM (to no avail, of course), but there are many things I don't fully understand.
1. It seems to want to update when I start Magisk Manager. Is that a good or bad idea, considering I'm working with a custom patch? Just say "no" or......?
2. I need to install an SU manager, yes? MM seems to indicate that it can't find any. Seems like I recall it was based on the phh su so can I just install the manager app for that? Is that what I need to effect "root" or do I already have it?
OK, scratch that second one. I just installed AdAway and it started up asking for root privleges which I was able to give it. But.....it keeps saying "copy failed" which would indicate to me that it does not have write access to where the hosts file is, so something's not "complete" about the root access?
nmyshkin said:
OK, so I've got boot
But I did have to do the recycle of TWRP. The first time I tried it without and it threw out all kinds of red errors. Yipes!
1. It seems to want to update when I start Magisk Manager. Is that a good or bad idea, considering I'm working with a custom patch? Just say "no" or......?
OK, scratch that second one. I just installed AdAway and it started up asking for root privleges which I was able to give it. But.....it keeps saying "copy failed" which would indicate to me that it does not have write access to where the hosts file is, so something's not "complete" about the root access?
Click to expand...
Click to collapse
Yes!
I'm thinking some partition fail is failing to mount after wiping to give the errors, using rm -f in TWRP settings might avoid it.
Yes you can download and install a Magisk Manager update if it asks, just not Magisk updates yet(has to say 'Manager').
With the root problem, I'd try rebooting or maybe clean installing and using AdAway on the first boot. Or try a Magisk module for it. Basically, just need to experiment to see how it behaves. If nothing helps, a logcat from adb might give an idea of what's going on.
Edit: Are you installing anything extra or taking extra steps apart from installing the ROM, Magisk, and AdAway? I'm trying to see if it is reproducible on Nook HD+ on equivalent firmware, but am having no luck so far.
fddm said:
Yes!
I'm thinking some partition fail is failing to mount after wiping to give the errors, using rm -f in TWRP settings might avoid it.
Yes you can download and install a Magisk Manager update if it asks, just not Magisk updates yet(has to say 'Manager').
With the root problem, I'd try rebooting or maybe clean installing and using AdAway on the first boot. Or try a Magisk module for it. Basically, just need to experiment to see how it behaves. If nothing helps, a logcat from adb might give an idea of what's going on.
Edit: Are you installing anything extra or taking extra steps apart from installing the ROM, Magisk, and AdAway? I'm trying to see if it is reproducible on Nook HD+ on equivalent firmware, but am having no luck so far.
Click to expand...
Click to collapse
Things are looking up I searched the AdAway issue and see there is a newer version that seems to solve the problem for people using Nougat ROMs (including someone running Magisk!). Worked like a charm. ES File Explorer seemed to have root access issues but I went into MM to see what the issue was and managed to manually turn on root access. Seems OK now.
As you say, part of this is getting used to it. I'm not seriously thinking this ROM is going to be good for the 8 GB tablet (for one thing I cannot tolerate the shutdown bug) but it's fun to see what's going on and try out this approach. Who knows? Someday there may be an Unlegacy AOSP 8.1 "mini-me" that will run (and maybe even shut down...) and I'll have the know-how to deal with it.
Thanks for your efforts. Sorry to have been a bit of a pain.
nmyshkin said:
Thanks for your efforts. Sorry to have been a bit of a pain.
Click to expand...
Click to collapse
No, you were perfect. You provided essential information and kept trying when you hit a wall, and we got working Magisk in the end. Couldn't be happier, thank you!
Official Oreo has finally been leaked thanks to @NFound and since I've been extensively testing it this thread will be to teach you how to install it and to tell you what works and what doesn't.
Special THANK YOU to @NFound, @raystef66, @DrakenFX, @Oki, @WesTD and to everyone else who has helped with the development of the Axon 7 and with this thread
How to unlock the bootloader?
Follow this guide https://forum.xda-developers.com/axon-7/how-to/guide-unlock-bootloader-easily-t3704595 by @WestTD
Unlocked bootloader message removal:
Have not found a working method yet.
Always backup your intSD before flashing ROMs and other TWRPs (Recoveries)
Stock user, need to install TWRP?
Flash TWRP 3.2.1-0 https://androidfilehost.com/?fid=673791459329066789 by @raystef66
If you already have TWRP installed, any version will do since the ROM will replace it with TWRP 3.2.1-6 after installation.
Installation:
Download: https://androidfilehost.com/?fid=818222786056032764 (I hope this is allowed now, please forgive me if the links is still not allowed by XDA)
Move the .ZIP into your internal memory as you would by moving any other file into your phone through USB.
Boot into TWRP: adb reboot recovery or by turning the phone off and pressing VolUp+Power
Do a full backup!
Wipe to perform a clean install. Recommended.
Press Install
Select the .ZIP
Install with TWRP only! During installation it will be asked which modem you want to install. In my case this was the A2017G but that might not be yours. Please select correctly.
Wipe Cache and Dalvik Do not reboot yet if you want to root.
Rooting Download and install Magisk V16.4 or V16.0 exactly as you just installed the ROM.
Flash the safetynet fix linked below.
Wipe Cache and Dalvik
Reboot
Edit: Changing partitions to ext4 might be necessary for some non-stock users on f2fs.. Still updating
What's not working and how to fix it:
Magisk doesn't pass Safetynet? (ctsProfile: False). Download and flash https://androidfilehost.com/?fid=674106145207489292 Thank you @raystef66
Google play store shows as uncertified? The .ZIP above from @raystef66 fixes this as well. Your device is now certified.
How do I disable force encryption? Go to post #63 by @DrakenFX
Bad battery life? Flash Jojoc V2.1 or V3.1 module within Magisk or via TWRP V3.2 : https://androidfilehost.com/?fid=962187416754476535 V2.1 : https://androidfilehost.com/?fid=673956719939820457 by @raystef66
AdAway cannot install hosts file: Open Magisk -> Settings and select Systemless hosts.
Daydream is not working? Check post #23 B12 Thread by @kountry83 Download: Daydream.zip
How do I enable or disable the Navigation bar?: Check thread [A2017G][TWRP-ZIP]NAVIGATION BAR Enabler/Disabler by @raystef66 or Direct Link download for aroma installer
How do I remove the carrier label and center the clock on the status bar? Check thread [PATCH][A2017X V1.3.0B01] Remove Carrier & Center Clock by @raystef66 Download: A2017X_V1.3.0B01_carrier&clock
Remove carrier label only: Check post #342 by @raystef66 Download: A2017X_V1.3.0B01_carrierremover
Need modems, boot or bootstack? Download below by @raystef66
Modems:
ZTE_A2017X_Oreo_V1.30B01_Gmodem
ZTE_A2017X_Oreo_V1.30B01_Umodem
ZTE_A2017X_Oreo_V1.30B01_CNmodem
Boot:
A2017X-O_beta-B01-boot
Bootstack: twrp 3.2.1.6 included
ZTE_A2017X_V1.3.0B01_OREO_BootStack_twrp3216
What's working:
Pretty much everything other than what I wrote above it seems. The ROM is very fast and stable, my phone feels considerably snappier than it did on stock Nougat and there doesn't seem to be many bugs at all. Only thing I've noticed is the battery life doesn't seem to be great but that could just be some installed apps or my phone. Fixed by Jojoc V3.2 by @raystef66. Link above.
Testing Camera...
Working HDR+ Patch by @NFound: : HDR+ for v1.3.0 B01
GCAM: GCAM
Flashed an older version of that HDR+ Patch by @NFound and does your Magisk not pass the safetynet anymore? Flash this safetynet fix by @raystef66: A2017X-V1.30B01_safetynet_fix_HDR
Dual Sims: Fully working
I'll continue updating the thread according to your feedback and my testing.
Victor13f said:
Official Oreo has finally been leaked thanks to @NFound and since I've been extensively testing it this thread will be to teach you how to install it and to tell you what works and what doesn't.
Thank you @NFound once again for your hard work!
Thank you @Oki for having written https://forum.xda-developers.com/axon-7/how-to/guide-axon-7-custom-oreo-roms-newbies-t3786693 If you need a better guide visit this thread and follow this guide simply using different files and not installing the bootstack separately.
How to unlock the bootloader?
Follow this guide https://forum.xda-developers.com/axon-7/how-to/guide-unlock-bootloader-easily-t3704595 by @WestTD
Unlock boot message removal:
If you want to remove the unlocked bootloader message at boot, you just need TWRP Exclusive. Just boot to recovery and go to the Advanced Menu -> More -> Del Inscription. You must to do this every time you update the bootloader. Thank you @Oki
Need to install TWRP?
Flash TWRP exclusive by @NFound https://androidfilehost.com/?fid=673956719939822011
Installation:
Download: https://androidfilehost.com/?fid=818222786056032764 (I hope this is allowed now, please forgive me if the links is still not allowed by XDA)
Move the .ZIP into your internal memory as you would by moving any other file into your phone through USB.
Boot into TWRP or ADB: adb reboot recovery or by turning the phone off and pressing VolUp+Power
Press Install
Select the .ZIP
Install with TWRP only! During installation it will be asked which bootstack you want to install. In my case this was the A2017G but that might not be yours. Please select correctly.
Wipe Cache and Dalvik Do not reboot yet if you want to root.
Rooting Download and install Magisk V16.4 or V16.0 exactly as you just installed the ROM or with TWRP Exclusive go to Advanced -> More -> Root -> Magisk
Wipe Cache and Dalvik
Reboot
What's not working?:
Magisk root doesn't pass Safetynet (ctsProfile: False). Tested with V16.4, V16.0 and V15.3. None of them passes the safetyNet. Have also tried installing the props module to no avail.
Google play store shows as uncertified (yet all the apps are available and install with no restrictions).
Battery charging light turns off when I turn the screen on and turns back on when the screen is off (Maybe it's intended to be like that, not sure)
What's working:
Pretty much everything other than what I wrote above it seems. The rom is very fast and stable, my phone feels considerably snappier than it did on stock Nougat and there doesn't seem to be many bugs at all. Only thing I've noticed is the battery life doesn't seem to be great but that could just be some installed apps or my phone. I haven't tested the dualsims yet but I will soon and I'll post the result here.
Testing Camera...
I'll continue updating the thread according to your feedback and my testing.
Click to expand...
Click to collapse
Sigh. First of all. Link is not allowed, delete it before we get trouble. Furthermore your guide isn't really helping anyone, since all information can be get in the other thread (nfound announced official oreo). You just snacked away Oki's guide and inserted a different ROM link. Tbf your information about magisk is fine and new, but that's it.
Cool, an easy guide to get you started.
Thanks man.
GabbaGandalf42 said:
Sigh. First of all. Link is not allowed, delete it before we get trouble. Furthermore your guide isn't really helping anyone, since all information can be get in the other thread (nfound announced official oreo). You just snacked away Oki's guide and inserted a different ROM link. Tbf your information about magisk is fine and new, but that's it.
Click to expand...
Click to collapse
I belive the link is allowed. A Forum mod said so on NFounds AEX thread.
I didn't snatch anything. I used guides that exist because they work and I gave props to every single person I could think of. I never claimed this was all my work. Just trying to help other people who want to try the ROM or are interested in how it performs.
I think the rom has something to do with CTS because it's a beta rom. It might not CTS approved. That's why magisk won't work. Similar to Android P DP.
https://developer.android.com/preview/release-notes
However, We can try to change or add ro.build.fingerprint in the build.prop file to the valid one. Not sure that it will work or not.
For example.
Code:
ro.build.fingerprint=ZTE/P996A04_N/ailsa_ii:7.0/NRD90M/20170215.164309:user/release-keys
Can /system be mounted as RW in this rom?
blackpac said:
Can /system be mounted as RW in this rom?
Click to expand...
Click to collapse
You can edit system just from TWRP.
mickey36736 said:
I think the rom has something to do with CTS because it's a beta rom. It might not CTS approved. That's why magisk won't work. Similar to Android P DP.
https://developer.android.com/preview/release-notes
However, We can try to change or add ro.build.fingerprint in the build.prop file to the valid one. Not sure that it will work or not.
For example.
Code:
ro.build.fingerprint=ZTE/P996A04_N/ailsa_ii:7.0/NRD90M/20170215.164309:user/release-keys
Click to expand...
Click to collapse
Didn't work unfortunately. Edited the ro.build.fingerprint and it still failed safetynet check.
SAFETYNET-FIX
Here you go : https://androidfilehost.com/?fid=674106145207489292
Fixes the safetynet - tested on 16.4 and 16.0
raystef66 said:
Here you go : https://androidfilehost.com/?fid=674106145207489292
Fixes the safetynet - tested on 16.4
Click to expand...
Click to collapse
Thank you, it works
all set up and running
Predatorhaze said:
all set up and running
Click to expand...
Click to collapse
How is battery life? Did you get substratum running? How is the sound without v4a and ainur. How is the sound with v4a+ainur?
battery dont know yet,but i dont use any sound mods on stock rom.Didnt try substratum.....i can try,but not gonna use it
GabbaGandalf42 said:
How is battery life? Did you get substratum running? How is the sound without v4a and ainur. How is the sound with v4a+ainur?
Click to expand...
Click to collapse
Accubattery says 5 hours SOT but I have only actually gotten 2. Again, this is probably a problem on my side and not the ROM. I need to check over the installed apps. Overall, actually better than 7.1.1 Nougat IMO since I was getting those bad results there too (Shouldn't have restored all the apps on first start).
Soundwise you shouldn't need anything. It's an official ROM and everything works properly. I haven't tested with any mods and I personally won't.
Victor13f said:
Accubattery says 5 hours SOT but I have only actually gotten 2. Again, this is probably a problem on my side and not the ROM. I need to check over the installed apps. Overall, actually better than 7.1.1 Nougat IMO since I was getting those bad results there too (Shouldn't have restored all the apps on first start).
Soundwise you shouldn't need anything. It's an official ROM and everything works properly. I haven't tested with any mods and I personally won't.
Click to expand...
Click to collapse
Battery doesn't sound too good. And personally I won't try it out until someone checked if substratum works. Cause if substratum works, I am able to enjoy the 'swift Black's theme, which boosts battery life by having real black everywhere. That means that the amoled screen will use less power. Also it's beautiful af and I don't want to miss it
Two questions please:
1. would flashing no-verity-opt-encrypt do anything for this ROM? as in, making encryption optional?
2. would it be a good idea to flash FASTBOOT_UNLOCK_EDL_N if I want to change my recovery now that I am no longer on N?
GabbaGandalf42 said:
Battery doesn't sound too good. And personally I won't try it out until someone checked if substratum works. Cause if substratum works, I am able to enjoy the 'swift Black's theme, which boosts battery life by having real black everywhere. That means that the amoled screen will use less power. Also it's beautiful af and I don't want to miss it
Click to expand...
Click to collapse
Substratum works, used swift black theme 8.0 pixel or nexus
GabbaGandalf42 said:
Battery doesn't sound too good. And personally I won't try it out until someone checked if substratum works. Cause if substratum works, I am able to enjoy the 'swift Black's theme, which boosts battery life by having real black everywhere. That means that the amoled screen will use less power. Also it's beautiful af and I don't want to miss it
Click to expand...
Click to collapse
Batterywise, I flashed the jojoc battery module and it's looking a lot better already
Here is working fine but how do I remove the operator name from the status bar?
Battery is absolutely horrible, coming from a beta tester. If you experience terrible battery it isn't a problem on your side, it's the beta rom. At best, I get barely 3 hours of screen on time only browsing Facebook
Updated OP since this thread became useful to track if magisk works with our stock ROM.
The most recent version you can use at the moment is magisk 16.7 and magisk manager 5.8.3.
I suggest that you change the update channel to custom and set the address to 127.0.0.1
For the most recent Magisk version:
mickey36736 said:
I tested 19.3 on B01 oreo and it still bootloop.
Click to expand...
Click to collapse
Thanks for checking @mickey36736
rzarectha said:
It bootloops
Click to expand...
Click to collapse
I don't have any problems on Magisk 17.0 - safetynetpass on AEX(O), NitrogenOS(P) and PE(P) :cyclops:
Open Manager and update. Download latest stable one and flash it. Reboot.
raystef66 said:
I don't have any problems on Magisk 17.0 - safetynetpass on AEX(O), NitrogenOS(P) and PE(P) :cyclops:
Open Manager and update. Download latest stable one and flash it. Reboot.
Click to expand...
Click to collapse
mine bootlooped on stock. I'm naive enough to wait for the big update also, I got it from the beta channel. I'll try the stable and see what happens. I was assuming it's the same build
update: it bootloops on stock no matter what channel (stable/beta) you get it from.
I'll try to get a mod to help me change the OP title, I can't seem to be able to do it myself.
rzarectha said:
mine bootlooped on stock. I'm naive enough to wait for the big update also, I got it from the beta channel. I'll try the stable and see what happens. I was assuming it's the same build
update: it bootloops on stock no matter what channel (stable/beta) you get it from.
I'll try to get a mod to help me change the OP title, I can't seem to be able to do it myself.
Click to expand...
Click to collapse
You can change the OP tittle by pressing Go Advanced button next to the Save button when editing the OP post.
Not only on stock...
I am on LOS 14.1, saw the update notification, did update, and now also a bootloop...
I installed the zip of an earlier version to no avail.
Prophet 5 said:
I am on LOS 14.1, saw the update notification, did update, and now also a bootloop...
I installed the zip of an earlier version to no avail.
Click to expand...
Click to collapse
use the uninstaller zip first
Try 17.1. supposedly solves the bootloops.
bootloops are easily fixed by using the uninstaller first.
koftheworld said:
Try 17.1. supposedly solves the bootloops.
Click to expand...
Click to collapse
Nope, it doesn't. I'm on B35 and it still bootloops. Had to use the uninstaller to remove and revert to v16.7
KwesiJnr said:
Nope, it doesn't. I'm on B35 and it still bootloops. Had to use the uninstaller to remove and revert to v16.7
Click to expand...
Click to collapse
You have to use the uninstaller first and then flash 17.1.
Too late for me. I was on last years' Darkrom (LOS14.1 based, really stable, so no recent backup) and immediately got a bootloop which I'm still working to recover from... :crying:
pnin said:
Too late for me. I was on last years' Darkrom (LOS14.1 based, really stable, so no recent backup) and immediately got a bootloop which I'm still working to recover from... :crying:
Click to expand...
Click to collapse
Did you use the magisk uninstaller? If not, just reflash your bootloader
koftheworld said:
Did you use the magisk uninstaller? If not, just reflash your bootloader
Click to expand...
Click to collapse
Excuse my ignorance but how would reflashing the bootloader help. Doesn't Magisk modify the boot image?
I figure that if flashing the uninstaller and then flashing v17.1 still results in a bootloop I (personally speaking) would go into TWRP and manually remove any Magisk related directories/files, maybe flash the uninstaller again (might catch something I missed), and then dirty flash Dark ROM (fresh boot image). Flash Magisk 17.x afterward.
That said, I am a non-Magisk kind of guy (not present on any ROMs or devices) so I might not know what I'm talking about. [emoji16]
Dark ROM. FTW. [emoji41]
ZTE Axon 7 A2017U, AospExtended v4.6 ROM, LlamaSweet 0.5 Kernel, microG (NoGapps), Multiboot, XDA Legacy
marcdw said:
I (personally speaking) would go into TWRP and manually remove any Magisk related directories/files, maybe flash the uninstaller again (might catch something I missed), and then dirty flash Dark ROM (fresh boot image).
Click to expand...
Click to collapse
Care to clue me in on those directories/files? I'm having a hard time here, dirty flashing my previous ROM, getting up to setup and then have something fail catastrophically over and over again...
I have even had to restore recovery through fastboot mode now. :silly:
I did not flash Magisk 17.x on Stock B35 (stayed with v16.4), but installing the latest Magisk Manager (v5.9.1) resolved the previous SafetyNet Check errors
Using stock anything above and v17.0 will bootloop using stock,
Just my 2cents, if that your issue just do the following:
-Download v16.7 first in case you don't have it yet, and move it to the SDCard.
* Head back to TWRP
* Flash v16.7 or your preferred release.
* You're good to go.
pnin said:
Care to clue me in on those directories/files? I'm having a hard time here, dirty flashing my previous ROM, getting up to setup and then have something fail catastrophically over and over again...
I have even had to restore recovery through fastboot mode now. :silly:
Click to expand...
Click to collapse
Not sure to be honest. Last time I had Magisk was around v15.x. When I initially rooted my Moto Magisk was part of the process. Even though the stock ROM is using SuperSU it seems I didn't fully remove Magisk. I have the following remnants visible in TWRP...
/data/magisk
/data/magisk.img
and files in /data/adb/
Not sure why everything is failing so badly on your end. I can't test things on my Axon 7 since I use DualBoot Patcher where Magisk is a no go.
Moto G5S Plus XT1806, MSM-Xtended v2.5 ROM, MultiROM, XDA Legacy
So I have managed to fully restore the phone, including updating Magisk to v17.1 (v16.0 didn't work at all, v14 did).
Apart from Goggle Messages that is, which FC whenever I try to start it (both current and past versions).
I was careful with Magisk in the past, I will be even more so in the future. No dot zero releases for me from now on. Thanks for your tips, people.
pnin said:
So I have managed to fully restore the phone, including updating Magisk to v17.1 (v16.0 didn't work at all, v14 did).
Apart from Goggle Messages that is, which FC whenever I try to start it (both current and past versions).
I was careful with Magisk in the past, I will be even more so in the future. No dot zero releases for me from now on. Thanks for your tips, people.
Click to expand...
Click to collapse
I'm not currently having Magisk issues, but Google Messages, after the recent update, does the same here. Gave up on it & switched to Textra.
New beta version released. Still bootloop
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.