Database Develop

Xposed for the Note 7 after rooting with OvrDriVE's method

Ok here it is: Xposed for the new @OvrDriVE root method. I have not tested method on VZW as i do not have their phone, but this still should being this is a Samsung Note 7.
As with any custom rom's, root, add-on's, you assume all risks with modding your phone. You have been warned.
Make sure you read all of my directions below, before you start posting errors with the install. Worst case you just have to start over with @OvrDriVE s installation.
Here is the way you can install xposed on your phone after you have root. I in no way have made any files or apks, I am just posting ways you get this loaded on your phone.
Please Thank the devolopers and others that have made all these files and apks possible..
The way is to install Xposed framework via FlashFire:
1. Download FlashFire, You can get it from the app store: https://play.google.com/store/apps/details?id=eu.chainfire.flash&hl=en
2. Download the Xposed Installer Apk: http://forum.xda-developers.com/showpost.php?p=58828974&postcount=1&nocache=1&z=3764362361329836
3. Download the Xposed Framework zip. <<< this is the file that you will be flashing via FlashFire: Xposed Framework.zip
4. Once you have all the files downloaded onto you computer/phone: you are ready to start. If you have'nt all ready copied all the files to your phone storage, do so now. If you did then you can move on to the #5.
5. Open FlashFire on your phone. Once it is loaded and open, click on circle with + button on the bottom right of the screen.
Then Click on Flash ZIP or OTA button.
Now select the xposed framework zip that you downloaded from #3.
Next you click the check mark on the top right of
the screen( do not change any of boxes on the left of the screen.<<< You Have Been Warned!!!!! .
Next scroll to the bottom of the screen and click the left button (flash button w the lighting bolt)
Sit back and watch FlashFire do its magic..
6. After #5 completes, you can now install the xposed installer apk from #2. Once installed open and check framework in the app and you should have this : Xposed framework version 86.1 (custom build by wanam / 2016709 is active.
7. Now go to Download in the xposed installer and download: Wanam Xposed 1.3.0 Made for Samsung Android 5 and 6 Roms by Wanam or you can download xTouchwiz by Wanam..
8. Once you downloaded it, install it, and then in the Xposed installer app- modules- you select the the app in #7 by placing a checkmark in the box on the right to activiate the modules.
9. Reboot your phone to activate the module.
10. Enjoy your efforts and customizing your phone:
If you some reason you want to uninstall xposed : flash this:xposed-uninstaller-20160211.zip

Confirmed working on my VZW Note 7 running PH1 firmware, rooted using @OvrDriVE's method.
Edit: for clarification, I used the second method (flashfire) to do this, and it worked like a charm.
Side note, you won't find Wanam Xposed 1.3.0 Made for Samsung Android 5 and 6 Roms by Wanam on xposed, it doesn't exist. Don't use Wanam Xposed either, it's been discontinued in favor of xTouchWiz. I've tested it myself and it works great, it's made by the same developer.
MOD EDIT: Large post quote put in hide tags.
Please don't quote large posts like this as it makes the thread difficult to read for other users.
galaxyuser88 said:
Ok here it is: Xposed for the new @OvrDriVE root method. I have not tested method on VZW as i do not have their phone, but this still should being this is a Samsung Note 7.
As with any custom rom's, root, add-on's, you assume all risks with modding your phone. You have been warned.
Make sure you read all of my directions below, before you start posting errors with the install. Worst case you just have to start over with @OvrDriVE s installation.
Here is 2 different ways you can install xposed on your phone after you have root. I in no way have made any files or apks, I am just posting ways you get this loaded on your phone.
Please Thank the devolopers and others that have made all these files and apks possible..
A. The first way is to use ADB to push the framework to your phone, Here is a link to the post with direction:
ADB Xposed installer
B: The second way is to install Xposed framework via FlashFire:
1. Download FlashFire, You can get it from the app store: https://play.google.com/store/apps/details?id=eu.chainfire.flash&hl=en
2. Download the Xposed Installer Apk: http://forum.xda-developers.com/showpost.php?p=58828974&postcount=1&nocache=1&z=3764362361329836
3. Download the Xposed Framework zip. <<< this is the file that you will be flashing via FlashFire: Xposed Framework.zip
4. Once you have all the files downloaded onto you computer/phone: you are ready to start. If you have'nt all ready copied all the files to your phone storage, do so now. If you did then you can move on to the #5.
5. Open FlashFire on your phone. Once it is loaded and open, click on circle with + button on the bottom right of the screen.
Then Click on Flash ZIP or OTA button.
Now select the xposed framework zip that you downloaded from #3.
Next you click the check mark on the top right of
the screen( do not change any of boxes on the left of the screen.<<< You Have Been Warned!!!!! .
Next scroll to the bottom of the screen and click the left button (flash button w the lighting bolt)
Sit back and watch FlashFire do its magic..
6. After #5 completes, you can now install the xposed installer apk from #2. Once installed open and check framework in the app and you should have this : Xposed framework version 86.1 (custom build by wanam / 2016709 is active.
7. Now go to Download in the xposed installer and download: Wanam Xposed 1.3.0
Made for Samsung Android 5 and 6 Roms by Wanam
8. Once you downloaded it, install it, and then in the Xposed installer app- modules- you select the the app in #7 by placing a checkmark in the box on the right to activiate the modules.
9. Reboot your phone to activate the module.
10. Enjoy your efforts and customizing your phone:
If you some reason you want to uninstall xposed : flash this:xposed-uninstaller-20160211.zip
Click to expand...
Click to collapse

ohblindone said:
Confirmed working on my VZW Note 7 running PH1 firmware, rooted using @OvrDriVE's method.
Edit: for clarification, I used the second method (flashfire) to do this, and it worked like a charm.
Side note, you won't find Wanam Xposed 1.3.0 Made for Samsung Android 5 and 6 Roms by Wanam on xposed, it doesn't exist. Don't use Wanam Xposed either, it's been discontinued in favor of xTouchWiz. I've tested it myself and it works great, it's made by the same developer.
MOD EDIT: Large post quote put in hide tags.
Please don't quote large posts like this as it makes the thread difficult to read for other users.
Click to expand...
Click to collapse
Ok, 1.3.0 does exist on xposed app, and yes you can use xTouchwiz by wanam as well, both are good, xtouchwiz has alot of stuff removed that will not work with the new firmware but he also removed alot of stuff that he didnt think was needed, so you can try both out and you can decide what you want to use..I have used both and they both work.. Now unfortunately Wanam will not be updating any of these, but is only providing support only..

galaxyuser88 said:
Ok, 1.3.0 does exist on xposed app, and yes you can use xTouchwiz by wanam as well, both are good, xtouchwiz has alot of stuff removed that will not work with the new firmware but he also removed alot of stuff that he didnt think was needed, so you can try both out and you can decide what you want to use..I have used both and they both work.. Now unfortunately Wanam will not be updating any of these, but is only providing support only..
Click to expand...
Click to collapse
Apologies, looking at that module and it's description (saying it was only for lolipop) I figuredit wouldn't be good to install on 6.0.
I also went to it's dev page on XDA and it was stated that the module is no longer being supported.

Save for later!!

So really this works just like normal except using Flashfire. I got scared thinking I would white knuckle it like the root. Any other module issues? Using several of them? I like some of the small play store tweaks and battery saving modules on other phones, I know wanam has the only safe 'do everything gravity box for touchwiz' stuff.

Im not sure why, but after installing this to my note 7, The "Android is optimizing # of #" comes up and it optimizes 1 app only... It won't go away and everytime I reboot It happens. I sort of want xposed, but if this is happening everytime I can just go without it....

It stays on or you just get the normal startup type message that lasts for a few seconds? Does it affect anything else? Seems minor.

guthrien said:
It stays on or you just get the normal startup type message that lasts for a few seconds? Does it affect anything else? Seems minor.
Click to expand...
Click to collapse
Were you replying to me? It does 1 of 1 every boot. Its more annoying than anything really. Not worth the trouble. And if I uninstall it, the optimizing screen goes away. No one else is complaining about it so its just my problem.

So what xposed apps have been testing and what are all of you using? I haven't used xposed in a couple of years and the modules I liked seem outdated, and I'm afraid to use them. A lot of them say they are only for AOSP and to not use on Samsung and other modified forks. I was surprised at the amount of modules which were totally outdated, I'd say at least half or more were from 1-2 years ago or longer since they were last updated.
Biff I'm getting that issue as well. The first reboot it optimized all 359 of my apps, but now on every reboot it optimizes just 1 of 1 app, only takes a few seconds but it is annoying. I'm finding little utility in xposed anyhow so am not sure I'm going to bother keeping it. I didn't find the oldies but goodies like wanam, something to turn off the volume nag if too high, gravity box was very explicit not to use on Samsung, etc.

Yea I don't really seem to use anything is xposed anyways. The 1 of 1 thing is quite annoying! No one else seems to think that! I think im just gonna pass on installing this for a while..

I'm not getting the constant optimization like you guys. I did get all at once after adding it.
I'm using Amplify, GlobalS-health, Greenify, Play Store Changelog, XHangouts and Wanam's XTouchwiz, though very lightly on the last.

Optimizing apps on reboot went away after 4 or 5 reboots. Enjoying xposed but still hesitant to install modules.
Sent from my SM-N930V using Tapatalk

Really happy about this work so far. Great job and good guidance!
Ran a quick "safe" test with xTouchWiz by moving the clock from default (right) to the left side. It worked (after phone restart).
Excited, I tried System/Disable tether provisioning... Restarted the phone. Works.
Awesome.
I also have the "Optimizing 1 of 1" issue previously mentioned, but it's not often I reboot, so not too worried. Wondering if there is a way to get a log for which file is being optimized. Always good to know what's happening.

roslof said:
Really happy about this work so far. Great job and good guidance!
Ran a quick "safe" test with xTouchWiz by moving the clock from default (right) to the left side. It worked (after phone restart).
Excited, I tried System/Disable tether provisioning... Restarted the phone. Works.
Awesome.
I also have the "Optimizing 1 of 1" issue previously mentioned, but it's not often I reboot, so not too worried. Wondering if there is a way to get a log for which file is being optimized. Always good to know what's happening.
Click to expand...
Click to collapse
Atleast I know its xposed that is causing this... I believe there is a way to get logs, but I am unsure how to do this or where to get it... I rarely reboot as well, but its just bothersome to see it doinh that.

Awesome module I discovered while trying to figure out how to get rid of the ugly roaming triangle this root puts on the signal bars. It's called Flat Style Bar Indicators, some free stuff and a very nominal cost for full version. I also see that the root took away the carrier name, which can be added back with this module. You can change any aspect of the status bar, it's very cool. I made my signal bars look like an iPhone, much easier and clearer to read.

galaxyuser88 said:
Ok here it is: Xposed for the new @OvrDriVE root method. I have not tested method on VZW as i do not have their phone, but this still should being this is a Samsung Note 7.
As with any custom rom's, root, add-on's, you assume all risks with modding your phone. You have been warned.
Make sure you read all of my directions below, before you start posting errors with the install. Worst case you just have to start over with @OvrDriVE s installation.
Here is the way you can install xposed on your phone after you have root. I in no way have made any files or apks, I am just posting ways you get this loaded on your phone.
Please Thank the devolopers and others that have made all these files and apks possible..
The way is to install Xposed framework via FlashFire:
1. Download FlashFire, You can get it from the app store: https://play.google.com/store/apps/details?id=eu.chainfire.flash&hl=en
2. Download the Xposed Installer Apk: http://forum.xda-developers.com/showpost.php?p=58828974&postcount=1&nocache=1&z=3764362361329836
3. Download the Xposed Framework zip. <<< this is the file that you will be flashing via FlashFire: Xposed Framework.zip
4. Once you have all the files downloaded onto you computer/phone: you are ready to start. If you have'nt all ready copied all the files to your phone storage, do so now. If you did then you can move on to the #5.
5. Open FlashFire on your phone. Once it is loaded and open, click on circle with + button on the bottom right of the screen.
Then Click on Flash ZIP or OTA button.
Now select the xposed framework zip that you downloaded from #3.
Next you click the check mark on the top right of
the screen( do not change any of boxes on the left of the screen.<<< You Have Been Warned!!!!! .
Next scroll to the bottom of the screen and click the left button (flash button w the lighting bolt)
Sit back and watch FlashFire do its magic..
6. After #5 completes, you can now install the xposed installer apk from #2. Once installed open and check framework in the app and you should have this : Xposed framework version 86.1 (custom build by wanam / 2016709 is active.
7. Now go to Download in the xposed installer and download: Wanam Xposed 1.3.0 Made for Samsung Android 5 and 6 Roms by Wanam or you can download xTouchwiz by Wanam..
8. Once you downloaded it, install it, and then in the Xposed installer app- modules- you select the the app in #7 by placing a checkmark in the box on the right to activiate the modules.
9. Reboot your phone to activate the module.
10. Enjoy your efforts and customizing your phone:
If you some reason you want to uninstall xposed : flash this:xposed-uninstaller-20160211.zip
Click to expand...
Click to collapse
Does Gravitybox work as far as nav button is concerned?

Lmax579 said:
Does Gravitybox work as far as nav button is concerned?
Click to expand...
Click to collapse
As far as gravity box goes, i have no idea if it works or not. Give it a try and post your findings.

galaxyuser88 said:
As far as gravity box goes, i have no idea if it works or not. Give it a try and post your findings.
Click to expand...
Click to collapse
It does but navbar might break system UI, is there anyway to fix UI thru adb?

spinedoc said:
Awesome module I discovered while trying to figure out how to get rid of the ugly roaming triangle this root puts on the signal bars. It's called Flat Style Bar Indicators, some free stuff and a very nominal cost for full version. I also see that the root took away the carrier name, which can be added back with this module. You can change any aspect of the status bar, it's very cool. I made my signal bars look like an iPhone, much easier and clearer to read.
Click to expand...
Click to collapse
Okay, I was skeptical at first, but realized I need to fly soon and wanted to stimulate the green battery icon in case security thinks this is a recalled Note 7. There's been so much press about the green icon meaning the phone is safe that *not* seeing one may have folks thinking it's not...
Results with this module exceeded my expectations. And no more voLTE...
Edit: Turns out this didn't permanently resolve the issue where VoLTE appears. It comes back and will linger until reboot. We'll need a real fix, either by a flashable zip or need/updated Xposed module.

FE Heroes not working despite safety net check passing

Hey! First off, thank you to the creator of magisk, it's amazing and very useful
However, I can't seem to get Fire Emblem Heroes to work. OP3T on stock rom, TWRP and magisk 11.1, nothing else. Using MagiskSU for greenify and adaway and everything works. Manager says I pass the safety net check (used to give a profile mismatch but that went away after rebooting) and I've enabled magisk hide for the app, to no avail.
For what it's worth PoGo seems to be working fine.
What further info could I give you to help and where do I get it?
Thanks!!!!

pqueiro said:
Hey! First off, thank you to the creator of magisk, it's amazing and very useful
However, I can't seem to get Fire Emblem Heroes to work. OP3T on stock rom, TWRP and magisk 11.1, nothing else. Using MagiskSU for greenify and adaway and everything works. Manager says I pass the safety net check (used to give a profile mismatch but that went away after rebooting) and I've enabled magisk hide for the app, to no avail.
For what it's worth PoGo seems to be working fine.
What further info could I give you to help and where do I get it?
Thanks!!!!
Click to expand...
Click to collapse
Trying to update the game e get the message "your device isn't compatible with this version"

Rcpbarba said:
Trying to update the game e get the message "your device isn't compatible with this version"
Click to expand...
Click to collapse
I just updated from 1.0.2 to 1.1.0 and keep getting the same error message as before (the good old 803-3001).
This is supposed to be a connection error message, but it doesn't make sense -- if I hotspot off my magisk'd OP3T to a stock OPO or a stock iPad, the game works fine, so it stands to reason the connection is good.
Hence my suspicion that it's probably a SafetyNet issue (FE:H, like PoGo, uses SafetyNet -- might be a Nintendo thing). Any idea how to get around it?
Thanks!

Might be an issue where the app also relies on another app or service to find a rooted device. See this thread, the Hiding root post under "Dependencies": https://forum.xda-developers.com/apps/magisk/magisk-magisk-hide-troubleshooting-tips-t3561828

Didgeridoohan said:
Might be an issue where the app also relies on another app or service to find a rooted device. See this thread, the Hiding root post under "Dependencies": https://forum.xda-developers.com/apps/magisk/magisk-magisk-hide-troubleshooting-tips-t3561828
Click to expand...
Click to collapse
Good idea. I didn't think of that, but alas, the game doesn't ask for any permissions (and none listed in settings) -- so if they do use 3rd party software to check, it doesn't show up in the permission list.
Inspired by Pocket Morty's dependency on Google Play Games, I went and installed that too (I'd removed it as a cruft-reduction exercise) to see if that was it, but it's not. Still doesn't work, same error message.

pqueiro said:
Good idea. I didn't think of that, but alas, the game doesn't ask for any permissions (and none listed in settings) -- so if they do use 3rd party software to check, it doesn't show up in the permission list.
Inspired by Pocket Morty's dependency on Google Play Games, I went and installed that too (I'd removed it as a cruft-reduction exercise) to see if that was it, but it's not. Still doesn't work, same error message.
Click to expand...
Click to collapse
Yeah, I don't think it has to be as a result of permissions (note to self: update the text)... It might also be that the app is looking for certain prop values. Both of these are hard to figure out without decompiling the apk.

Didgeridoohan said:
Yeah, I don't think it has to be as a result of permissions (note to self: update the text)... It might also be that the app is looking for certain prop values. Both of these are hard to figure out without decompiling the apk.
Click to expand...
Click to collapse
Well now, that's substantially more complicated and probably out of my league I'll have to stick to playing it on the iPad. It's not impossible, just annoying.
Thanks!

you could try on nox pc emulator too, it is working on 1.1 (i had to disable root tho)
i will try with magisk on my phone until i install the apps on LineageOS13
EDIT: @pqueiro it works on LineageOS 13 and using Magisk 11.1, without problems, so i guess can be something of the rom (i can pass the net check too, and PoGo without problems)

panchovix said:
you could try on nox pc emulator too, it is working on 1.1 (i had to disable root tho)
i will try with magisk on my phone until i install the apps on LineageOS13
EDIT: @pqueiro it works on LineageOS 13 and using Magisk 11.1, without problems, so i guess can be something of the rom (i can pass the net check too, and PoGo without problems)
Click to expand...
Click to collapse
The plot thickens. Let me check on my "playground" phone if I can replicate that.

@pqueiro
did you install the game when the Phone was already rooted?
I can replicate this issue when installing the game on already rooted devices - but if I install the game on a non-rooted device and apply magisk afterwards the game launches proper.
Create a nandroid backup, flash the rom and try to launch the game while non-rooted and see if it makes a difference for you.

Klassikal said:
@pqueiro
did you install the game when the Phone was already rooted?
I can replicate this issue when installing the game on already rooted devices - but if I install the game on a non-rooted device and apply magisk afterwards the game launches proper.
Create a nandroid backup, flash the rom and try to launch the game while non-rooted and see if it makes a difference for you.
Click to expand...
Click to collapse
FYI, tried this (took the opportunity when updating Oxygen OS) and it worked a treat! All is good. Backup > unroot > update > install > magisk all the things and it's working fine.
Thanks!

Raiffeisen Twint (https://play.google.com/store/apps/details?id=ch.raiffeisen.twint)

Hi everyone,
I am using the application Raiffeisen Twint (version 1.2.16.0, https://play.google.com/store/apps/details?id=ch.raiffeisen.twint) on my Magisk's rooted Google Pixel (Android 8.0, Nov. 2017) without problems for a while, but since Magisk 14 versions, the application stopped working and the application reports that root is detected.
I have successfully updated to Magisk 14.5 (from 14.2), but root is still detected by the application, even with Magisk Hide activated for the application and the Magisk Manager package moved to a random name (could also be related to the updated application).
I have cleared the data of the application several times and it doesn't help and root is still detected by the application...
Anyone has a idea?
Thanks for your answers!

Like I said in the Magisk support thread, I can hide Magisk from that app just fine (on Magisk v14.5 beta)...
You don't happen to have any other mods that might trigger an app looking for root (like Xposed)? Can your device pass SafetyNet? Have you previously been rooted with any other root method and do you have any remnants of that left (root management apps, etc)? Do you have any apps that are known to be used for questionable purposes. By "questionable purposes" I mean getting access to paid features without paying, etc. Not necessarily that you use the app for this, but that the app might be used in such a manner... Etc, etc, etc. Every little detail might count.

Hi Didgeridoohan,
Thanks for helping me!
I do not have any mods installed in Magisk and also no Xposed. My device is passing SafetyNet!
I have performed a factory reset last week and since that I only rooted my device with Magisk 14.2, so no other rooting applications used. For details, I have unlocked bootloader, TWRP recovery installed and developer options and USB debugging activated.
My settings in Magisk are:
I have following applications installed on my device:
https://pastebin.com/pmt4jBMV
Do you see any applications with "questionable purpose"?
I get this message in the application:
Thanks a lot!

At a quick glance everything looks ok...
I did some experimenting with the other Raiffeisen apps you have installed, in case they also detect root and "tell" on you. At least one of them did detect root, but from what I could see it didn't make any difference for Twint.
I also tested installing a few of the root apps you had installed (in case the app looks for certain known apps), but that didn't make any difference either. I could still successfully hide root.
My guess is that it's something along these lines tough. That it's using another app or detecting a root app. You could start experimenting with that. Clearing data for the other Raiffeisen apps and adding them to MagiskHide and also removing root apps. Try disabling USB debugging and developer options as well (didn't make difference for me, but worth a shot).

Simple. Change name of package from settings in Magisk Manager, then MAKE SURE you add twint app to magisk hide list, then ERASE DATA of twint app, change package name once again and run twint. Working with Magisk 14.5. Screens if u want available. Or video.

Hi Didgeridoohan, Hi Mamama07,
Thanks for your help, but sadly none of your suggestions did worked... until the update of the application released yesterday, to fix problem related to rooted devices! [emoji3]
Thanks anyway again for your help! [emoji106]

I had the same problem (with BCV Twint) and after a few tries, changing Magisk Package Name worked!

Xposed causes Snapchat to temporarily lock account?

I have a Samsung Galaxy S6 SM-G920W8 with the UlTiMaTe NouGaT S8+ Full Port V3.1 ROM. I am rooted with Magisk V18.0, and have Snapchat enabled in Magisk Hide. Every time I install Xposed v89.3 by topjohnwu, I get a message from Snapchat team a few hours later saying that my account is being temporarily locked for 12+ hours. Is anyone else experiencing the same issue? Is there a way to stop this? Is this caused by Xposed?

Xposed or root, i dont know but i had to say goodbye to snapchat since there is no way to get it working on rooted devices,i unroot, login, then root and after a couple of hours or maybe a day cant log in...titanium backup didnt do the trick neither, it is server syncd so they find out and block u

Yes, you have to hide root from Snapchat using Magisk Hide and uninstall Snapchat.
Then flash Xposed uninstall by flashing the uninstaller zip in recovery, reboot to system, install Snapchat and hide root from it and login, once logged in reboot to recovery, flash Xposed, reboot to system and it should work and stay working.
Repeat process in future if necessary.

Redline said:
Yes, you have to hide root from Snapchat using Magisk Hide and uninstall Snapchat.
Then flash Xposed uninstall by flashing the uninstaller zip in recovery, reboot to system, install Snapchat and hide root from it and login, once logged in reboot to recovery, flash Xposed, reboot to system and it should work and stay working.
Repeat process in future if necessary.
Click to expand...
Click to collapse
That will work for MAYBE a few days. SC scans your phone now for xposed/root and will instantly ban it. Also, it keeps your device id stored on a blacklist so you'd have to change that too. They've gotten a lot sneaker about it. You can use an app like xprivacy lua or app ops to block this reading permission but it'll probably crash SC constantly. A few guys and I are trying to spoof the reading and device id and not get it to freak out but it's a slow process

agraceful said:
That will work for MAYBE a few days. SC scans your phone now for xposed/root and will instantly ban it. Also, it keeps your device id stored on a blacklist so you'd have to change that too. They've gotten a lot sneaker about it. You can use an app like xprivacy lua or app ops to block this reading permission but it'll probably crash SC constantly. A few guys and I are trying to spoof the reading and device id and not get it to freak out but it's a slow process
Click to expand...
Click to collapse
Can't say I've ever only had it work for a few days, or only ever had it maybe work. It's worked for months now without issue.
I've also not had Snapchat "scan my phone" and I don't do anything special in that department, just regular Magisk Hide.
I've had it stop working once, months ago as I said above, and I just did the process and it started working again, no device ID change or blocking of permissions.

Redline said:
Can't say I've ever only had it work for a few days, or only ever had it maybe work. It's worked for months now without issue.
I've also not had Snapchat "scan my phone" and I don't do anything special in that department, just regular Magisk Hide.
I've had it stop working once, months ago as I said above, and I just did the process and it started working again, no device ID change or blocking of permissions.
Click to expand...
Click to collapse
If you gave sc storage permission, then yes it does scan your phone periodically. It's declared in detail, in apps like app ops. Anyway though, without anyone capturing logs of when the ban is done (I'm talking to everyone that runs a sc mod of any sort) , nobody can really come up with the exact reason for them, only make educated guesses because it seems to not be one thing related \_(•-•)_/ Happy snapping!

Seems to be that Snapchat is detecting Xposed, whether it be non-systemless up to 8.1 oreo (v90 beta-3), systemless by topjohnwu, or systemless for 7.0-9.0 (EdXposed). I used Snapchat with non-systemless Xposed by rovo89 up till a month ago when I upgraded to PIE, then I used EdXposed. My new 9.0 PIE setup worked well with SnapFreedom and EdXposed until I upgraded EdXposed and Snapchat to 10.51.0.0 when I got my first ban.
Plan for attack (haven't tried, banned on alt) to use Snapchat and Xposed (Possibly also Xposed modules?) without ban:
-Use AppCloner to rebuild the snapchat apk with minimal permissions (I have premium version). I was going to go this route, but AppCloner rebuilds com.snapchat.android to com.snapchat.androie, breaking SnapFreedom. Bare permisisons: CAMERA, MICROPHONE, and maybe LOCATION? PHONE permission will give away your IMEI and other stuff, and STORAGE may trigger Xposed detection.
-Use LuckyPatcher to deny snapchat certain perissmions, including read external storage.
This thread got me thinking: https://forum.xda-developers.com/xposed/xposed-root-snapchat-uninstall-xposed-t3909199

I am using Pixen OS android 10 on oneplus 6. I have magisk root and want to install xposed. How to prevent snapchat account lock?

General System root + Passed Safety Net Pixel 5a

Hey everyone,
after some trial and error, I was able to pass Safety Net.
I just want to mention what I did in the process to get there. May have been a combination of things or just one...
1. I followed this guide, but make sure you notice that It's for the Pixel 5 not 5a. But the process is similar. This process didn't fix the issue. However, it's also a good how-to on how to root. I did also modify the props to the 3a.
How to Root the Pixel 5 & Still Pass SafetyNet — Full Guide for Beginners & Intermediate Users
The Pixel 5 is a great value proposition in this era of $1,500 phones. With its reasonable price tag, fully open-sourced software, and unlockable bootloader, it's also an ideal phone for rooting.
android.gadgethacks.com
2. When that didn't work, I followed this video, and hid all my banking apps besides the Google Play Services:
3. When that didn't work, I installed these both using Magisk from this post:
Magisk General Support / Discussion
This is the place for general support and discussion regarding "Public Releases", which includes both stable and beta releases. All information, including troubleshoot guides and notes, are in the Announcement Thread
forum.xda-developers.com
4. Cleared my data and cache with Google Play and GPay + any other banking apps.
That worked for me!
EDIT: IF GOOGLE MAPS reports the wrong location, its likely XPrivacy-LUA, Google Services. Uncheck some of them.

Oh man....the only thing holding me back is the safety net thing, and it looks like we have a work around tell someone has an actual method made for this phone. Not sure if I'm ready to actually mess with this yet...but thanks for the post, bro!

anubis2k3 said:
Oh man....the only thing holding me back is the safety net thing, and it looks like we have a work around tell someone has an actual method made for this phone. Not sure if I'm ready to actually mess with this yet...but thanks for the post, bro!
Click to expand...
Click to collapse
Didnt think it was that big of a deal to me. But it was fun with a new phone with nothing on it.

This was the Magisk module that worked to pass safety net for me. I didn't need any others.
Releases · kdrag0n/safetynet-fix
Google SafetyNet attestation workarounds for Magisk - kdrag0n/safetynet-fix
github.com
Google Pay "appears" to be working too. Haven't gone out and tried it yet though.

joemommasfat said:
Google Pay "appears" to be working too. Haven't gone out and tried it yet though.
Click to expand...
Click to collapse
That's the part that I use the most, and the reason I haven't rooted yet. Please let us know if it works. Much appreciated!

I can confirm that using google pay (newer GPay app) on my rooted 5a works at merchants. I've already used it several times over the last week or so with no problems.

Deadmau-five said:
3. When that didn't work, I installed these both using Magisk from this post:
Click to expand...
Click to collapse
Why? Isn't the shim version just for Samsungs? Either way, it's the same mod, just different versions.
Someone who actually knows what they're doing needs to write up a tutorial. Following instructions posted by people who have no idea what they're doing but "it works" for them is dangerous.

borxnx said:
Why? Isn't the shim version just for Samsungs? Either way, it's the same mod, just different versions.
Someone who actually knows what they're doing needs to write up a tutorial. Following instructions posted by people who have no idea what they're doing but "it works" for them is dangerous.
Click to expand...
Click to collapse
You're absolutely correct about the dangers in following instructions posted by who knows who. I'll go further and say when it comes to root and associated items stay away from anything posted on a site other than XDA. In many cases even if the instructions were correct at some point in time they may well be outdated now.
I haven't rooted yet for a few reasons yet but will, hopefully sometime very soon. In the meantime I can state the following:
They're is no need to modify props. Modifying props to identify as a different phone would only be required for custom ROMs that don't handle it themselves (or some non-certified Chinese phones, which doesn't apply here). If you're running stock just leave that portion alone. And, if I'm not mistaken (although not 100% certain) I think safetynet-fix takes care of that for you in any case.
You will definitely need kdragOn/safetynet-fix.
Hopefully that's all you need.
I'm not sure which version of Magisk you'll need. Unless you know what you're doing and how to get out of trouble I recommend staying away from the current alphas, they're extremely cutting edge and you can expect problems.
Best best is to check the following threads and see what's going on:
Actually see this post and the 2 posts immediately following
Magisk General Support / Discussion
This is the place for general support and discussion regarding "Public Releases", which includes both stable and beta releases. All information, including troubleshoot guides and notes, are in the Announcement Thread
forum.xda-developers.com
That should pretty much cover things for the moment. If nobody else (@hfam ?) has done it by the time I get around to rooting I'll write something up specific for the 5a.

I only mentioned what works for me since there was no step-by-step guide.
Dangerous how? Doing any mods to your phone is "dangerous". I fail to see how this is more so than others. Modifying your phone is risky.
If it didn't work I wouldn't have posted this guide. I only mentioned the steps that I took. It's not really a guide, just how I passed safety net.
But, my 5a has still been working great since then. GPay included.

jcmm11 said:
You're absolutely correct about the dangers in following instructions posted by who knows who. I'll go further and say when it comes to root and associated items stay away from anything posted on a site other than XDA. In many cases even if the instructions were correct at some point in time they may well be outdated now.
I haven't rooted yet for a few reasons yet but will, hopefully sometime very soon. In the meantime I can state the following:
They're is no need to modify props. Modifying props to identify as a different phone would only be required for custom ROMs that don't handle it themselves (or some non-certified Chinese phones, which doesn't apply here). If you're running stock just leave that portion alone. And, if I'm not mistaken (although not 100% certain) I think safetynet-fix takes care of that for you in any case.
You will definitely need kdragOn/safetynet-fix.
Hopefully that's all you need.
I'm not sure which version of Magisk you'll need. Unless you know what you're doing and how to get out of trouble I recommend staying away from the current alphas, they're extremely cutting edge and you can expect problems.
Best best is to check the following threads and see what's going on:
Actually see this post and the 2 posts immediately following
Magisk General Support / Discussion
This is the place for general support and discussion regarding "Public Releases", which includes both stable and beta releases. All information, including troubleshoot guides and notes, are in the Announcement Thread
forum.xda-developers.com
That should pretty much cover things for the moment. If nobody else (@hfam ?) has done it by the time I get around to rooting I'll write something up specific for the 5a.
Click to expand...
Click to collapse
Just a quick note to say I just finished with everything (new Pixel 5a 5G, rooted + Safety net, restored all my apps, etc) and it's a flawless victory, ALL banking apps work great, SafetyNet passes, no hiccups.
I'd be happy to craft up a step by step and post it if there's some interest. It's not often I get to give back to this outstanding community, so it's the least I can do jumping on the opportunity. UFC 266 Main card is just starting, so I'll get started right after the fight and post it here in this thread.
Great to see ya again @jcmm11! Coming back to root a new phone feels like a family reunion, so great to see many of you active folks still here helping out!!
hfam

Alright, as promised, here is my writeup for a step-by-step tutorial for rooting your new Pixel 5a and getting SafetyNet up and going. I know it looks like a book, but I wanted to put it into plain language and attempt to explain the process for everyone, even absolute first timers. I know when I first started I really appreciated when the person helping didn't presume I had any knowledge, so for those that may have some experience, sorry for the wordiness. I'll also include how I apply updates when a new Android security update is pushed out. I understand that there are now elegant ways to accept OTA updates, but that is out of the scope of this tutorial as I have always had issues with OTA, and have to catch up on how that works myself. I can attest to years of using this method though (using a full factory image) to perform the "monthly" security updates, and I have never had anything but full success, so I'll share that here below the rooting tutorial.
*Disclaimer and heads-up* this is for an UNLOCKED PIxel 5a purchased directly from Google Store. At the time of this writing that is the only place I'm aware of which currently offers the PIxel 5a. Once carriers like Verizon, etc, offer this device, there may be some changes to the process, so just know up front this is for the unlocked Pixel 5a*
*WARNING*! When you unlock the bootloader on your phone it WILL WIPE YOUR PHONE and reset it to factory. If you've already used your phone and set it up, you're going to lose that setup. If you can't bear it, then the rest of this isn't for you, as root cannot be achieved without unlocking the bootloader.
First, you'll need a few things
- https://developers.google.com/android/images
and download the latest FACTORY IMAGE for "barbet", which is the Pixel 5a. You want to download the SAME VERSION that is currently installed on your device. At the time of this writing, it's the September release.
From that same page, you will need the ADB+Fastboot platform tools which will allow you to perform the required tasks, download from this link:
- https://developer.android.com/studio/releases/platform-tools.html
I use Windows 10, and extract this tools download to a folder in the root of C: called "platform-tools". You will then need to add "c:\platform-tools" to your environment path.
On the Pixel 5a, you need to enable developer options. Go into Settings/About Phone/and tap "Build Number" 7 times. This enables developer options and it will let you know when you've unlocked this as you tap 7 times. Once developer options is unlocked, go back to Settings/System/Advanced, and you'll see Developer Options is now available.
Select Developer Options, and enable "USB Debugging" and also enable "OEM Unlocking".
(**NOTE** For now at least, until you decide how you want to proceed with handling updates in future (more on that later), I strongly recommend turning OFF "Automatic System Updates" as well, just a few items below "OEM Unlocking". This prevents any updates happening automatically on a phone reboot. You don't want to wake up and find an OTA update pushed out and removed root, or worse. You can always turn it back on later.)
Plug your phone into a USB port on your PC. Allow the PC to do it's thing. You can open up Computer Management on the PC (right click the windows menu button icon lower left of your toolbar and select "Computer Management". Select "Device Manager" on the left panel. You should see "Android ADB Device" appear at the top of the right pane list of devices. if not, then visit:
Install OEM USB drivers | Android Studio | Android Developers
Discover links to the web sites for several original equipment manufacturers (OEMs), where you can download the appropriate USB driver for your device.
developer.android.com
and download the appropriate USB driver for your system and retry the above directions.
First thing we have to do is unlock the bootloader.
On the PC, open a command prompt and change directory to "C:\platform-tools" as discussed above.
Now, type in "adb reboot bootloader". The phone will reboot into bootloader. (you may receive a dialog on the phone which says something to the effect of not recognizing the PC. Go ahead and allow it, check the box to allow it in the future, and proceed.
Phone is now at the bootloader, and shows you some info letting you know it's so, including that the bootloader is locked. Also, look at the Device Manager we opened earlier and confirm that you see Android ADB Device (or similar) which confirms your PC recognizes the phone and setup for ADB commands .
To unlock the bootloader, in the command prompt type:
fastboot flashing unlock
This will unlock the bootloader, you will likely see a warning that it's going to wipe the phone. Proceed and allow the unlock. The phone will then reboot and take you to your wiped phone just as you received it out of the box, except the bootloader is now unlocked and Developer Options are still available. Let the phone continue through it's first-time setup, and leave the phone plugged into the PC. If you unplugged no biggie, but we're going right back to the PC shortly and it will need to be plugged back in before the next step to accept the file we're going to push to it.
Now, you want to open a browser on the phone and go to (at the time of this writing, v23.0 is the current stable Magisk):
Release Magisk v23.0 · topjohnwu/Magisk
This release is focused on fixing regressions and bugs. Note: Magisk v22 is the last major version to support Jellybean and Kitkat. Magisk v23 only supports Android 5.0 and higher. Bug Fixes [App]...
github.com
Scroll down and under "Assets" select that Magisk 23.apk file, download and install it. Open Magisk if it doesn't open on install, and just let it sit, we're coming back to it shortly.
PATCHING THE BOOT.IMG FILE
On the PC, go back to the Factory Image you downloaded, and extract it to a temporary directory. You will see 6 files; a few "flash-all" files, a radio image, a bootloader image, and a ZIP file called "image-barbet-XXXXXXXXXXX.zip (the xxx's are whatever the version number is you've downloaded). Double click that ZIP file and you will see a dozen files. The one we need to root the device is "boot.img".
Copy (don't move!!) this file to c:\platform-tools. Now, go back to your command prompt (still pointing to c:\platform-tools) and type in:
adb push boot.img /sdcard/Download
Now back on the phone, within the Magisk app we left open, at the top where it says Magisk, choose to install. A dialog box will open, select Patch Boot File Image. Point the process to your /sdcard/Download, and select the boot.img file we just pushed there. Now allow it to patch the boot.img and Magisk will show you it's patching it, and in a moment tell you it was successful. Close the Magisk app, open "Files" and direct it to sdcard/Download. Note the name of the patched boot file, which is called "magisk_patched-XXXXX_xxxxx.img (the X's are the Magisk version, and the x's are 5 random chars). Feel free to leave it there as you go back to the PC...
Back on the PC, in the command prompt, now type:
adb pull /sdcard/Download/magisk_patched-XXXXX_xxxxx.img
make certain you get the name exact or it won't go, no worries, just get it correct. The file now resides in the "c:\platform-tools" directory along with the unpatched "boot.img" and your ADB+Fastboot tools.
Just about done rooting, here we go!
Now, in the command prompt type:
adb reboot bootloader
The phone reboots into bootloader. Now type:
fastboot flash boot magisk_patched-XXXXX_xxxxx.img (again, use the numbers and letters in YOUR patched file!)
Lastly, type:
fastboot reboot
Your phone reboots, and you should be rooted!! Unplug your phone from the PC, open up Magisk App and confirm, the Magisk entry at the top of the main Magisk App screen should now show you the version you installed, etc!
Time to get your banking apps (and any others that may detect unlocked bootloaders/root/etc) working!
In the Magisk App, on the bottom of the screen is a 4 item menu bar. Select the right-most icon, which is "Modules". At the top of the screen select "sorting order" and sort alphabetically. Scroll down to "riru" and select the module that is JUST "RIRU", (not any of the other "riru _______" modules). Choose to download it, then choose to install it. You'll be prompted to reboot the phone, so reboot the phone.
Next, we're going to install drag0n's Universal SafetyNet fix (at the time of this writing it's currently v 2.1.1) You will need to download this via a browser on your phone, so open a web browser and go to:
GitHub - kdrag0n/safetynet-fix: Google SafetyNet attestation workarounds for Magisk
Google SafetyNet attestation workarounds for Magisk - GitHub - kdrag0n/safetynet-fix: Google SafetyNet attestation workarounds for Magisk
github.com
On the right-hand side, you'll find "Releases", and v2.1.1 is the latest. Select that, then scroll down to "Assets" and download "safetynet-fix-v2.1.1.zip" By default this will download to sdcard/Download.
Go back into the Magisk App, select the "Modules" menu as above, and at the very top select the "Install from Storage" bar. Point to the file we just downloaded and install it (don't extract it, etc, it requires the zip exactly as downloaded and will do it's thing). Again, it will install the module and prompt you to reboot. Reboot.
Almost there!
At this point, if you havent installed your banking apps, do so. DON'T RUN THEM, just install them. I also have a Nintendo Switch Online app which failed because of root, so if you also have or want this app, install it now, again, do NOT run it yet, just install. Same with any other apps you are aware which have root/bootloader unlocked issues, get them installed, but don't run 'em.
Now, we're going to use MagiskHide to hide these apps and complete the process for passing SafetyNet and running apps which may not run due to root.
in the Magisk App, at that 4 item menu bar at the bottom, select the 2nd from left, or "MagiskHide". Select the MagiskHide item and it will open to a scan of all the apps on your system. By default I believe Magisk sets up to hide Google Play Services. You will see it selected, and all the other apps on your system unselected. Select each of the banking apps, the Nintendo Switch Online (if you have it), and any other apps that YOU ARE SURE will complain about unlocked bootloaders and/or root. Any onilne gaming that's popular are good choices, but again, it's easiest to NOT RUN them PRIOR to hiding them via MagiskHide. Pokemon GO comes to mind as one I've seen that needs hiding, etc, so make it easy on yourself and do a little research on any suspect apps prior to running them, then hide them if needed.
Anyhow, select your banking apps to hide them.
Now, we're going to check SafetyNet to make sure youll now pass.
On the Home menu in the Magisk App, select "Check SafetyNet". You will be prompted to download some proprietary SafetyNet shhhhhhhtuff....so let it download. Once done, SafetyNet check will open, and you should show a blue screen which says SUCCESS, and "basicintegrity" and "ctsProfile" will be checkmarked, evalType will show BASIC.
You're good to go, rooted, SafetyNet works perfect, and you can now open your banking apps and should open right up!!
If you find any specific issues about specific apps not working, or detecting root, etc, the best place to get help is in the Magisk General Discussion forum:
Magisk General Support / Discussion
This is the place for general support and discussion regarding "Public Releases", which includes both stable and beta releases. All information, including troubleshoot guides and notes, are in the Announcement Thread
forum.xda-developers.com
I owe those folks eternally for showing me what I know, and always having the answers for any issues I've ever had. Some of the nicest, smartest people Ive had the pleasure of knowing, they're always helpful, and even maintain fantastic sites for FAQ and chock full of great info about every aspect of Magisk.
BONUS ITEM: As I indicated above, I'd share the method I know, trust, and have used many many times, trouble free, to apply a system update to the phone without overwriting anything, and not hitting any issues many encounter using the OTA method (though I understand that's been vastly improved, I haven't educated myself as to that process and will likely continue to use this method).
Security Update (monthlies) Process using Full System Image
As above, download the newest Full Factory Image from the site. Extract this full image to a directory inside C:\platform-tools
In this directory, if you're on Windows, open the "flash-all.bat" file (don't run it, open it with Notepad or something similar, I really like Notepad++ as it's free, has a LOT of great functionality and, like the native Notepad, doesn't do any goofy formatting/fonting/etc when modifying and saving a file.)
In flash-all.bat, look for the "-w" entry in the fastboot command near the end of the file and REMOVE ONLY THE "-w", leaving the line correctly formatted (don't leave an extra space or something goofy), then save the file over the top of the original with the same name. This will remove the overwriting of your data when pushing the image, the "-w" tells the process to overwrite, so we remove it.
Open up a Windows Explorer and go to your c:\platform-tools directory. Delete (or move to another location) any "boot.img" files along with any "magisk_patched-XXXXX_xxxxx.img" files from previous operations. Also note and confirm that you have correctly extracted the latest Full System Image to it's own directory, residing in c:\platform-tools.
Now, connect your phone to the PC. Open your command prompt and point to "C:\platform-tools" again. Type: cd <name of Full system Image directory>
In command prompt, type:
adb reboot bootloader
The phone is now in bootloader. In command prompt, confirm you're pointing to "C:\platform-tools\<Full System Image extract dir>" Type:
flash-all
This will do a full factory image push to your phone, you'll see a couple quick writes and phone reboots, then begins writing the rest of the image to your phone, but since we removed the "-w" from "flash-all.bat", it's NOT overwriting your data, just the necessary system files to update it to the latest version!
Reboot your phone, let it do any optimizing and updating it needs to do, and don't run anything yet, we're not quite done, just let the phone settle in and finish booting and doing it's thing.
Now, go back and perform the steps above listed under "PATCHING THE BOOT.IMG FILE" to patch the newest boot.img from the Full System Image we just updated the phone with (push the boot.img to sdcard/Download, patch with Magisk App, pull magisk_patched-XXXXX_xxxxx.img to your PC, blast it back using fastboot), and you've now rerooted the phone.
Lemme just say again that I know this was a friggin' book, and I tried to make it as clear and plain language as I could to help even a first timer, so my apologies if it seems like an onerous process. It's really not, and once you've done this once or twice, it's a cakewalk and takes about 10 minutes of your time from start to finish to do the whole system update and reroot. Again, the newer methods to take OTA without losing root may be something you'd like to look into, i definitely will, but I'm very confident in sharing this method as I know it works like a champ and is foolproof if you take your time the first few times and make sure you do what's required (remove the "-w" from the flash-all.bat, etc)
Lastly, I've been using this method since the Pixel 2, and just performed it on my new 5a, it worked exactly as it has for years for me on the P2, so you can be confident moving forward that, if you follow instructions and take your time until it's all familiar, you'll be successful in rooting, passing SafetyNet, and applying system updates without screwing up the A/B slots or overwriting your data in the process.
I hope this helps even one person, and since I rarely find myself able to give back to the community in any real meaningful way (many of these folks are WAAAY beyond my modest skills and know so much!!), I hope that this provides some folks with a useful and meaningful tutorial, providing confidence that anyone can root their P5a (or about any Pixel it seems) without being a Magisk/Android prodigy.
@Didgeridoohan, @pndwal, @zgfg, @jcmm11, and so many others over the years have been so helpful, I couldn't have done any of this without their selfless help, so give those folks a big thanks also if this is any help to you.
Best of luck,
hfam

Thanks for the write-up @hfam, it's good to know that some of the steps that i tried aren't really necessary, like using props config or hiding the actual magisk app.
Appreciate you!

nsoult said:
Thanks for the write-up @hfam, it's good to know that some of the steps that i tried aren't really necessary, like using props config or hiding the actual magisk app.
Appreciate you!
Click to expand...
Click to collapse
Awww, thanks! Glad to do it and really hope it helps some folks tackle rooting their phones and passing SN!

Rooted with magisk v.23 - flashed zip as a module

So has anyone installed the October update yet?

GrandAdmiral said:
So has anyone installed the October update yet?
Click to expand...
Click to collapse
Yep, good to go. I used the same method I shared above.

Is this working with Android 12? Which Magisk version to use?

This method did not work for Android 12. I updated my rooted phone to android 12 OTA. It returned to stock. I followed the method above to patch the factory boot.img file with magisk. After flashing my phone in bootloader with the patched boot.img, my phone will not reboot. says:
failed to load/verify boot images
Any advice? My Magisk is v23. Do I need to use a beta version?

Poking around in this thread, it seems that android 12 root is a much more involved process, requiring factory wipe and additional steps.
[Guide] Flash Magisk on Android 12
Trying to root the Pixel 5 running Android 12 by flashing a magisk-patched boot image results in the phone only booting to fastboot mode ("failed to load/verify boot images") Some users have reported that booting (instead of flashing) the patched...
forum.xda-developers.com

tintn00+xda said:
This method did not work for Android 12. I updated my rooted phone to android 12 OTA. It returned to stock. I followed the method above to patch the factory boot.img file with magisk. After flashing my phone in bootloader with the patched boot.img, my phone will not reboot. says:
failed to load/verify boot images
Any advice? My Magisk is v23. Do I need to use a beta version?
Click to expand...
Click to collapse
As you stated, you are correct. You need to perform a full wipe or flash the factory image with a wipe and then root works fine and phone boots. Tried myself and works fine.