Database Develop

[BETA][2017.10.01] SuperSU v2.82 SR5

This thread is for SuperSU releases that are still in testing, and are not yet available through the Play store. The main thread for stable SuperSU releases is located here: https://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703. The changelogs are in the old release thread.
Please keep track of the version numbers in the thread titles, as the latest test release may not always be newer than the latest stable release.
The latest test release is:
SR5-SuperSU-v2.82-SR5-20171001224502.zip
RELEASE NOTES
That is a recovery flashable ZIP (I recommend FlashFire or TWRP). If you want to install via APK, it is also present inside the ZIP, in the common folder.

--- reserved ---

@Chainfire Does 2.05 beta include SELinux workaround for L that you mentioned in other thread? I guess we could move xposed non related discussion about SELinux here as well.

StupidIdea said:
@Chainfire Does 2.05 beta include SELinux workaround for L that you mentioned in other thread? I guess we could move xposed non related discussion about SELinux here as well.
Click to expand...
Click to collapse
2.05 doesn't yet. I've made a lot of headway with it though, and is now a lot less messy and more reliable than when I last posted in that thread. It's fully working with AOSP tree synced and built today. The question is still if it'll work with retail L - probably, but we just don't know.
The mechanism itself may be able to be employed to fix Xposed as well, but I'd like to have @rovo89 's active input on this to make sure we only drop security where needed and not more than that. I haven't seen him comment on the SELinux stuff in a while though.
The code is pretty much ready to be integrated into SuperSU itself, but I'm not really sure whether I should do so now, or wait for L retail to let it loose on the world.

Chainfire said:
2.05 doesn't yet. I've made a lot of headway with it though, and is now a lot less messy and more reliable than when I last posted in that thread. It's fully working with AOSP tree synced and built today. The question is still if it'll work with retail L - probably, but we just don't know.
The mechanism itself may be able to be employed to fix Xposed as well, but I'd like to have @rovo89 's active input on this to make sure we only drop security where needed and not more than that. I haven't seen him comment on the SELinux stuff in a while though.
The code is pretty much ready to be integrated into SuperSU itself, but I'm not really sure whether I should do so now, or wait for L retail to let it loose on the world.
Click to expand...
Click to collapse
No pressure. Its up to you if you decide to publish it before L release or not but I will be glad to test it on L and report if functions that I use in my apps work with it. As for xposed in theory these 5 points rovo89 posted should work with "permissive" but I guess he will verify it himself.
Of topic: I understand its beyond su binary but did you even thought about adding an option to start activity in system or root process? Benefits are simpler interaction with system services and improved service life (faster restarts). Let me know if question is not clear.

Please remove the "Disable Samsung KNOX popups" request the second time that we open the app, or add an option to remove this message at every start of the app, on many Galaxy S4 with the last 4.4.2 firmware a SystemServer Crash make random reboots after Knox disabled via SuperSU
This xposed module http://forum.xda-developers.com/xposed/modules/samsung-kitkat-systemserver-crash-fix-t2806046 not always fix the problem.

CM11s on OnePlus One
Betas 2.04 and 2.05 working like a charm, the autogrand feature didn't work before that.
Thank you for your work!
Suggestion: could you change the default theme from White to Device default? I always use Dark themes and it's kinda frustrating to have to change that on every flash... I think Device default would work great for everyone

cioce said:
Please remove the "Disable Samsung KNOX popups" request the second time that we open the app, or add an option to remove this message at every start of the app, on many Galaxy S4 with the last 4.4.2 firmware a SystemServer Crash make random reboots after Knox disabled via SuperSU
This xposed module http://forum.xda-developers.com/xposed/modules/samsung-kitkat-systemserver-crash-fix-t2806046 not always fix the problem.
Click to expand...
Click to collapse
Not having KNOX disabled and using root in turn can also cause random reboots... so this is a tricky problem, not solved merely by not pressing that button. SuperSU keeps nagging you about it, because really, you have to do this.
Have you tried completely removing the com.sec.knox.seandroid package from your device?
MasterMind33 said:
CM11s on OnePlus One
Betas 2.04 and 2.05 working like a charm, the autogrand feature didn't work before that.
Thank you for your work!
Suggestion: could you change the default theme from White to Device default? I always use Dark themes and it's kinda frustrating to have to change that on every flash... I think Device default would work great for everyone
Click to expand...
Click to collapse
The reason device default theme is not selected by default is because a lot of OEMs have some godawful themes set by default that everybody would nag me about ...

Hmm. I blinked and the master has a new weapon to play with. Superuser apps will always be needed. By the way, Pro could use an update to a nicer icon.

MikeRL100 said:
Hmm. I blinked and the master has a new weapon to play with. Superuser apps will always be needed. By the way, Pro could use an update to a nicer icon.
Click to expand...
Click to collapse
#realworldproblems

I'm so sad, 1.9.4 stable but after that, whatever I did, keep su binary update rooting... I don't know what problem my device have. Lenovo s930 (kitkat4.4.2). normal update su binary makes me break root, using twrp or cwm su binary update loop. I can use only 1.9.4 without problem.

Chainfire said:
Not having KNOX disabled and using root in turn can also cause random reboots... so this is a tricky problem, not solved merely by not pressing that button. SuperSU keeps nagging you about it, because really, you have to do this.
Click to expand...
Click to collapse
Hi Chainfire and thanks for reply,
I know that the random reebots can happen also on not modified firmware (without root), but in the Italian forum androidiani.com (http://www.androidiani.com/forum/mo...-root-towelroot-knox-0x0-galaxy-s4-i9505.html) some user report that after the root and Knox Disabled via SuperSU, the Galaxy S4 start to make random reebots, and before to do the root on the same firmware they have never seen a reboot, this is the reason why I ask you to give to the user the possibility to disable the Samsung KNOX popup.
Chainfire said:
Have you tried completely removing the com.sec.knox.seandroid package from your device?
Click to expand...
Click to collapse
No, but if Knox doesn't make any problem on my device, is it really necessary to disable it? Maybe someone want to use it.

cioce said:
Hi Chainfire and thanks for reply,
I know that the random reebots can happen also on not modified firmware (without root), but in the Italian forum androidiani.com (http://www.androidiani.com/forum/mo...-root-towelroot-knox-0x0-galaxy-s4-i9505.html) some user report that after the root and Knox Disabled via SuperSU, the Galaxy S4 start to make random reebots, and before to do the root on the same firmware they have never seen a reboot, this is the reason why I ask you to give to the user the possibility to disable the Samsung KNOX popup.
Click to expand...
Click to collapse
I'm not talking about not having root at all. The problem (as I understand it) is caused by having any packages at all in a "disabled" state. This may ultimately cause a crash which triggers a reboot.
At the same time, keeping that package enabled in combination with root, will break various root commands, which you may not even notice (root apps will just appear to randomly fail and be unreliable) which in turn is also known to cause reboots.
No, but if Knox doesn't make any problem on my device, is it really necessary to disable it? Maybe someone want to use it.
Click to expand...
Click to collapse
Just because you haven't noticed the issue doesn't mean it isn't there. As for using it, having root prevents KNOX from working anyway.
...
The point is, solving this problem is not as easy as making that popup optional.

dhampire said:
I'm so sad, 1.9.4 stable but after that, whatever I did, keep su binary update rooting... I don't know what problem my device have. Lenovo s930 (kitkat4.4.2). normal update su binary makes me break root, using twrp or cwm su binary update loop. I can use only 1.9.4 without problem.
Click to expand...
Click to collapse
Please clarify what happens in the following circumstances:
- in-app binary update: normal, and reboot
Keeps saying binary needs updating? Or also results in bootloop?
- in-app binary update: TWRP/CWM
Bootloop?
- latest flashable ZIP with TWRP/CWM
Also bootloop?
It's strange if they don't all result in bootloops...
I know testing is very annoying for you because you need to reflash your system every failed test, but if you want to help solve this problem it's going to require some work.
First test:
- If you have SuperSU 1.94 installed, use the "full unroot" option from settings to remove it.
- Reboot into CWM/TWRP
- Install the latest BETA ZIP but do not reboot
- Adb shell into the device
- "mount /system"
- "ls -l /system/xbin/*su*", post the output here
- "ls -lZ /system/xbin/*su*", post the output here
- Remove /system/app/Superuser.apk
- Reboot into Android
- See if there is a bootloop

Sorry for my poor english. not bootloop. never bootloop. but su binary update loop -> need su binary update again on every boot after update su binary....continue...keep saying need update.
---------- Post added at 09:10 AM ---------- Previous post was at 09:07 AM ----------
I also did full unroot before, and I can't root my device again (finally I flashed rom again).
---------- Post added at 09:14 AM ---------- Previous post was at 09:10 AM ----------
When I choose normal su binary update, it makes broke root(unroot), and it also I can't root again, I have to flash rom finally.
---------- Post added at 09:15 AM ---------- Previous post was at 09:14 AM ----------
If 1.9.4, there are no problem like that. but only twrp use su binaly update. normal update makes unroot.

dhampire said:
I also did full unroot before, and I can't root my device again (finally I flashed rom again).
Click to expand...
Click to collapse
Not even using the full update ZIP linked in the first post of this thread? What happens then, still asks for binary update?
dhampire said:
When I choose normal su binary update, it makes broke root(unroot), and it also I can't root again, I have to flash rom finally.
Click to expand...
Click to collapse
Again, not even using the full update ZIP linked in the first post of this thread? What happens then, still asks for binary update?
...
Please:
- Install the attached version
- Update binaries at least once
- Reboot
- Post logcat (specifically looking for "[SuperSU][APK][Installer]" lines)

Version 2.06 installed on:
-Note SGH-I717 Android 4.0.3
-Note 3 SM-N900V Android 4.3
No problem.
With v2.04 and v2.05 on the Note, the SuperSU apps-list activity was stuck trying to display the list and the preferences activity froze the system while toggling survival mode, both only on the first run. With v2.06 this did not happen.
Was it a 'busybox' issue? I have two versions installed in different locations and there are significant differences. I use the better applets of each. Maybe developers should build a mini version containing only the applets they need to rely on and use it from their data directory.
Frank

Frank Westlake said:
Version 2.06 installed on:
-Note SGH-I717 Android 4.0.3
-Note 3 SM-N900V Android 4.3
No problem.
With v2.04 and v2.05 on the Note, the SuperSU apps-list activity was stuck trying to display the list and the preferences activity froze the system while toggling survival mode, both only on the first run. With v2.06 this did not happen.
Was it a 'busybox' issue? I have two versions installed in different locations and there are significant differences. I use the better applets of each. Maybe developers should build a mini version containing only the applets they need to rely on and use it from their data directory.
Click to expand...
Click to collapse
No it was not a busybox issue, it was an odd bug somewhere in the binary

Hi, Master.
Q:Again, not even using the full update ZIP linked in the first post of this thread? What happens then, still asks for binary update?
A: Yes.
I did this method.
- Install the attached version
- Update binaries at least once
- Reboot
- Post logcat (specifically looking for "[SuperSU][APK][Installer]" lines)
The attached file is the log.txt (Is it enough? or wrong? If wrong please teach me easy way, I'm newbie)
Still continue to mention " Need Su Binary update".
Regards.

dhampire said:
Hi, Master.
Q:Again, not even using the full update ZIP linked in the first post of this thread? What happens then, still asks for binary update?
A: Yes.
I did this method.
- Install the attached version
- Update binaries at least once
- Reboot
- Post logcat (specifically looking for "[SuperSU][APK][Installer]" lines)
The attached file is the log.txt (Is it enough? or wrong? If wrong please teach me easy way, I'm newbie)
Still continue to mention " Need Su Binary update".
Regards.
Click to expand...
Click to collapse
Please confirm the app actually says 2.06
This logcat does not list the output I expect. Did you open SuperSU again after rebooting?
How did you make the logcat? "adb logcat > logcat.txt" ?

[Guide] Pass Safetynet on a rooted 7.0 AOSP based ROM - Updated 11-01-2016

Update (11/09) - This method no longer works with the november security updates from Google as it causes suhide to break.
Here are the steps to follow
If you are already rooted, fully unroot. I do this by doing the following.
1) In the SuperUser app, go to settings and choose to do a full unroot. Choose "No" when it prompts you to restore your stock boot.img
2) Let the system reboot normally.
3) Reboot to recovery
4) If you have Magisk installed, flash the Magisk uninstaller Link
5) If you have suhide installed, flash rm-suhide 0.51 Link
6) Flash your ROM's boot.img extracted from your ROM (simply dirty flashing should also work), or install a custom kernel of your choice
At this point you should have a stock boot.img (or custom kernel) with no traces of SuperUser anywhere
Install SuperUser 2.78 Link
Install suhide 0.55 Link
Reboot into system. Verify that you have root. I'm not 100% sure this is necessary, but I like to do it before proceeding.
Reboot back into recovery.
Flash xsetpropSu.zip (attached to this post) Link
Reboot the system
Install RootSwitch 1.3.3.2 Link
Open up RootSwitch, uncheck disable all SU daemons. Disable Root
Pass SafetyNet
Optional
Using tasker to automatically disable root when certain applications are run. @NYZack made a little writeup here
Credits:
@NYZack - Helping me figure out how to put all of this together
@Captain_Throwback - For help with xsetprop
@Chainfire - SuperSU + SuHide
@topjohnwu - Magisk

work around found

no longer relevant post..

I don't know if the kernel can be modified to pull that trick. Even if someone does though, it's not going to last long. Every bypass you can find, Google can find. Then they know what to fix. The only way to win, is not to play.
And no, you can't lock the bootloader without wiping data.

Well I got it to work...I will turn this thread into a Guide. Who knows how long it will last, but...at least it's working for now.

Thread updated with instructions. I hope this can help someone!

So there's no way to do this without rooting and magisk?

3dawg said:
So there's no way to do this without rooting and magisk?
Click to expand...
Click to collapse
I want root, so I did not try to do that. If your bootloader is unlocked, I do not think there's a way to do it.

Thanks
skaforey said:
Thread updated with instructions. I hope this can help someone!
Click to expand...
Click to collapse
Yes I just followed these instructions and I am green panel. I have to check at a terminal to pay with phone but it probably will work. One note that was kinda unclear in case others do same....It should read :
Turn the Root switch ON....not OFF....when wanting to use AP. You can turn it back on when you want to do other things that require root permissions. I believe this is dynamic and working with the magisk mount point in addition to tricking the boot process into thinking the bootloader is locked.
Thanks so much for this. I was so angry with Google. And I was just going to say FK it and not use AP.
WORKS! Do all the steps in the order he says above and you can turn root off and on at will and have Android Pay work just fine! YAY!

skaforey said:
This thread started as a plea for help, but thanks to @NYZack I have gotten it to work.
Here are the steps to follow
If you are already rooted, fully unroot. I do this by doing the following.
1) If you have suhide installed, download rm-suhide 0.51 Link
2) In the SuperUser app, go to settings and choose to do a full unroot. Choose "No" when it prompts you to restore your stock boot.img
3) Let the system reboot normally.
4) Reboot to recovery
5) Flash rm-suhide 0.51
6) Flash your ROM's boot.img extracted from your ROM (simply dirty flashing should also work), or install a custom kernel of your choice
At this point you should have a stock boot.img (or custom kernel) with no traces of SuperUser anywhere
Install SuperUser 2.78 Link
Install Magisk v8.zip Link
Install suhide 0.55 Link
Reboot into system
Install Magisk Manger 2.1 (apk) Link
Open up Magisk Manager app and go to modules. Click on the + button. Add the following zip for xsetprop Link
Install RootSwitch 1.3.1.2 Link
Reboot system
Using Root Explorer (or some other file manager capable of root access), browse to /magisk/xsetprop and modify post-fs-data.sh . Add the following line to the end of the file, save and exit
Code:
xsetprop ro.boot.flash.locked 1
Reboot system
Open up RootSwitch, uncheck disable all SU daemons. Disable Root
Pass SafetyNet
Click to expand...
Click to collapse
FYI - The latest version of the xSetProp zip (0.2.1 as of this post) handles setting that prop automatically, and has additional logging. I'd recommend using that and you can remove that portion of your guide.

Captain_Throwback said:
FYI - The latest version of the xSetProp zip (0.2.1 as of this post) handles setting that prop automatically, and has additional logging. I'd recommend using that and you can remove that portion of your guide.
Click to expand...
Click to collapse
Thank you! Instructions updated (also tried to give proper credit all around).
I think Chainfire might be in the process of doing something similar without the need for Magisk.
I suppose we could also probably use the xsetprop binary along with a su.d script to run the necessary commands on startup? This would avoid having to use Magisk all together.
If I get some time I might try that out.

No longer works after I reboot the device. It's almost like it knows about my hack. It passes the safety net thing with green screen yet I get message saying that can't verify blah blah...your phone might be rooted! I've updated to 0.2.1 of the xprop and double checked the other things like suhide and magisk and so on. Wth ... Less than a day and Google changed something? I'm baffled. Help!

Pkt_Lnt said:
http://www.xda-developers.com/android-safetynet-now-reportedly-tripped-by-unlocked-bootloaders/
Click to expand...
Click to collapse
Thanks so much for taking the time to write this out.
I am 100% successful with M ROMs like ResRemix
However on my Nexus 6 with N ROMs (like Nitrogen or cDroid) I can't get SafetyNet to pass this way. With Root Switch I can get PoGo to work but following these instructions to a T I still don't have green SN
I wonder if it is the kernel ? What kernel have you been successful with?
Lastly are you aware of any way to find success with 7.1 ROMs?
---------- Post added at 12:31 AM ---------- Previous post was at 12:27 AM ----------
photolarry said:
No longer works after I reboot the device. It's almost like it knows about my hack. It passes the safety net thing with green screen yet I get message saying that can't verify blah blah...your phone might be rooted! I've updated to 0.2.1 of the xprop and double checked the other things like suhide and magisk and so on. Wth ... Less than a day and Google changed something? I'm baffled. Help!
Click to expand...
Click to collapse
Is the message you are getting coming up with SafetyNet or with PoGo ... or when ??

jcrompton said:
Thanks so much for taking the time to write this out.
I am 100% successful with M ROMs like ResRemix
However on my Nexus 6 with N ROMs (like Nitrogen or cDroid) I can get SafetyNet to pass this way. With Root Switch I can get PoGo to work but following these instructions to a T I still don't have green SN
I wonder if it is the kernel ? What kernel have you been successful with?
Lastly are you aware of any way to find success with 7.1 ROMs?
---------- Post added at 12:31 AM ---------- Previous post was at 12:27 AM ----------
Is the message you are getting coming up with SafetyNet or with PoGo ... or when ??
Click to expand...
Click to collapse
Yea I know I think it's something to do with either the kernel I've selected or perhaps suhide no longer works...I'm not sure what the deal is. I'm running Franco #55 and even without root, I get failure but inside the testing app ...see attached

Thanks for this write-up! I was able to pass SafetyNet in both apps while running Pure Nexus 7 w/ Stock OpenGapps.
I think one key thing that was skipped in the OP - be sure your ROM is SafetyNet compatible to begin with. I've run numerous ROMs that even before Google started checking bootloaders, wouldn't pass SafetyNet even if unrooted. For example, I just tried the OP method with Despair's new 7.1 ROM and it failed (probably won't work on 7.0 either). But with Pure Nexus 7.0 it works great.

MrBrady said:
Thanks for this write-up! I was able to pass SafetyNet in both apps while running Pure Nexus 7 w/ Stock OpenGapps.
I think one key thing that was skipped in the OP - be sure your ROM is SafetyNet compatible to begin with. I've run numerous ROMs that even before Google started checking bootloaders, wouldn't pass SafetyNet even if unrooted. For example, I just tried the OP method with Despair's new 7.1 ROM and it failed (probably won't work on 7.0 either). But with Pure Nexus 7.0 it works great.
Click to expand...
Click to collapse
I'm using stock Rom and only custom kernel so this should work on Nbd90z....I'd think. Last test was dreaded message but I'm trying to add few things to suhide blacklist. We shall see

I get the green screen. But then when I tap at store nfc terminal...it claims error....I'm going to try hiding nfc service, and what I think is play services based on uid chainfire explained. I'll try a small purchase and remember to screen capture the error if occurs

skaforey said:
Thank you! Instructions updated (also tried to give proper credit all around).
I think Chainfire might be in the process of doing something similar without the need for Magisk.
I suppose we could also probably use the xsetprop binary along with a su.d script to run the necessary commands on startup? This would avoid having to use Magisk all together.
If I get some time I might try that out.
Click to expand...
Click to collapse
I built the mod for people that were already using Magisk. If you're not using Magisk, then of course you can try just putting the binary in /su/xbin and put the post-fs-data.sh in /su/su.d and see if that works for setting the props at boot time.
I don't use Xposed, so using Magisk + phh's Superuser was my target for the module. I also did try the su.d method with SuperSU, but it wasn't working on my device. I also didn't want to have to use RootSwitch. But feel free to unpack the zip and try whatever combinations you want.

photolarry said:
No longer works after I reboot the device. It's almost like it knows about my hack. It passes the safety net thing with green screen yet I get message saying that can't verify blah blah...your phone might be rooted! I've updated to 0.2.1 of the xprop and double checked the other things like suhide and magisk and so on. Wth ... Less than a day and Google changed something? I'm baffled. Help!
Click to expand...
Click to collapse
Still working for me. Are you sure you disabled root in Root Switch? It automatically re-enables upon logon. Also be sure your xsetprop file is correct.
You can check by using the getprop command

skaforey said:
Still working for me. Are you sure you disabled root in Root Switch? It automatically re-enables upon logon. Also be sure your xsetprop file is correct.
You can check by using the getprop command
Click to expand...
Click to collapse
I'm using it for android pay not pogo. And I did. I'm sure the prop is right or wouldn't get green go. It's an error from AP saying something about unable to verify and might be rooted....or words to that effect

New oxygenOS or xposed?

Hey guys,
Just wanted to know how many of you ditched the Xposed on marshmallow for the latest 7.1.1 Android based oxygenos?
Since we don't know when nougat will be supported by xposed, is staying on marshmallow worth it?
Even though most of the modules I use are more or less esthetical, there's one thing I can't live without - youtube background playback and ad block.
Share your thoughts!

Xposed over any OS without Xposed. I have never even flashed Nouget because I know its just a waste of time for me. Ive been on cm13 since the day it came out. DEC 11 2016.

If all you need is the youtube modules, there's modded youtube apps out now with adblock and background playback. Check it out here.
I've also packaged the app in a convenient Magisk module, which you can find here.
It works exactly like the xposed-modified YouTube app, but it works on Nougat.

Anova's Origin said:
If all you need is the youtube modules, there's modded youtube apps out now with adblock and background playback. Check it out here.
I've also packaged the app in a convenient Magisk module, which you can find here.
It works exactly like the xposed-modified YouTube app, but it works on Nougat.
Click to expand...
Click to collapse
Hey Anova, what is this Magisk thingy you're talking about?
Also... For me The most important is gravitybox then come youtube modules and mock mock locations.
You think it's worth the upgrade? I personally never had a phone that would get updates so quickly or even at all. So I have no idea what to expect.. Would I have to reroot, reinstall recovery or it's all a piece of cake and only the exposed won't affect anything? Lemme know.

Crishien said:
Hey Anova, what is this Magisk thingy you're talking about?
Also... For me The most important is gravitybox then come youtube modules and mock mock locations.
You think it's worth the upgrade? I personally never had a phone that would get updates so quickly or even at all. So I have no idea what to expect.. Would I have to reroot, reinstall recovery or it's all a piece of cake and only the exposed won't affect anything? Lemme know.
Click to expand...
Click to collapse
Magisk is a framework that allows you to make temporary changes to your /system partition at boot, without actually modifying the partition. It works by superimposing user-defined changes to files in /system during boot; changes are reverted to their stock state afterwards. These user-defined changes are loaded into Magisk through Magisk modules. While a lot of people may think it's similar to Xposed, they're really nothing alike. I mentioned Magisk for the YouTube app because it is merely convenient. You could manually replace the YouTube APK in system without any additional software, but Magisk will do it for you while applying all the correct permissions, etc. As a bonus, Magisk also includes its own rooting method that works, for the most part, as well as SuperSU. This means that you can flash only Magisk to root your phone (flashing SuperSU is optional and is really based on personal preference, Magisk will work with SuperSU if you flash that first).
Because of what Magisk is and how it works, it is not able to modify your device in the same way that Xposed can. This means that mods like gravitybox and mock mock locations cannot be implemented with Magisk. Technically, all Magisk modules can be installed without Magisk by manually editing/replacing things in the /system partition. What is special about it is that Magisk does these things systemlessly, meaning that (with the proper configurations), you can modify /system without triggering safetynet.
For the modified YouTube app I was talking about, that was actually modded and compiled as a stand-alone APK by someone on XDA. It does not alter your current YouTube app, but rather outright replaces it.
As for upgrading to Nougat, it's really up to personal choice. I personally never used Xposed for anything other than YouTube Adaway and Background Playback, and to top it off I rarely use YouTube on my phone anyways so upgrading was an easy choice for me. If you do end up wanting to upgrade, do the following:
1) Download the full ROM of whatever version of OOS you want to use (4.1.0 is the latest, on Android 7.1.1). Do not use the "Upgrade Phone" option in settings if you are already rooted or have modified anything in your /system partition, as it will cause problems.
2) Flash the full zip in TWRP, wipe cache/Dalvik, then immediately flash the latest Magisk.zip (from the main Magisk thread on XDA)
3) Boot, then download Magisk Manager from the Play Store
At this point, Magisk will have been fully installed and your phone should be rooted. You can confirm through the Magisk Manager app

Anova's Origin said:
Magisk is a framework that allows you to make temporary changes to your /system partition at boot, without actually modifying the partition. It works by superimposing user-defined changes to files in /system during boot; changes are reverted to their stock state afterwards. These user-defined changes are loaded into Magisk through Magisk modules. While a lot of people may think it's similar to Xposed, they're really nothing alike. I mentioned Magisk for the YouTube app because it is merely convenient. You could manually replace the YouTube APK in system without any additional software, but Magisk will do it for you while applying all the correct permissions, etc. As a bonus, Magisk also includes its own rooting method that works, for the most part, as well as SuperSU. This means that you can flash only Magisk to root your phone (flashing SuperSU is optional and is really based on personal preference, Magisk will work with SuperSU if you flash that first).
Because of what Magisk is and how it works, it is not able to modify your device in the same way that Xposed can. This means that mods like gravitybox and mock mock locations cannot be implemented with Magisk. Technically, all Magisk modules can be installed without Magisk by manually editing/replacing things in the /system partition. What is special about it is that Magisk does these things systemlessly, meaning that (with the proper configurations), you can modify /system without triggering safetynet.
For the modified YouTube app I was talking about, that was actually modded and compiled as a stand-alone APK by someone on XDA. It does not alter your current YouTube app, but rather outright replaces it.
As for upgrading to Nougat, it's really up to personal choice. I personally never used Xposed for anything other than YouTube Adaway and Background Playback, and to top it off I rarely use YouTube on my phone anyways so upgrading was an easy choice for me. If you do end up wanting to upgrade, do the following:
1) Download the full ROM of whatever version of OOS you want to use (4.1.0 is the latest, on Android 7.1.1). Do not use the "Upgrade Phone" option in settings if you are already rooted or have modified anything in your /system partition, as it will cause problems.
2) Flash the full zip in TWRP, wipe cache/Dalvik, then immediately flash the latest Magisk.zip (from the main Magisk thread on XDA)
3) Boot, then download Magisk Manager from the Play Store
At this point, Magisk will have been fully installed and your phone should be rooted. You can confirm through the Magisk Manager app
Click to expand...
Click to collapse
Thanks for such a detailed description of everything! You're the best! I seriously decided to upgrade tomorrow.
Just last couple questions before I do... Should I delete anything? Like xposed itself with it's modules, or does the system upgrade wipe everything itself? Should I perform any backups other than usual titanium ones?
Thanks in advance

Crishien said:
Thanks for such a detailed description of everything! You're the best! I seriously decided to upgrade tomorrow.
Just last couple questions before I do... Should I delete anything? Like xposed itself with it's modules, or does the system upgrade wipe everything itself? Should I perform any backups other than usual titanium ones?
Thanks in advance
Click to expand...
Click to collapse
You should delete the Xposed modules prior to updating, as they are saved as user apps and will not be wiped with an upgrade. Delete the Xposed framework app as well for the same reason. Updating should erase all of the background stuff that the Xposed originally installed in /system. Take a nandroid prior to updating just in case.

Anova's Origin said:
You should delete the Xposed modules prior to updating, as they are saved as user apps and will not be wiped with an upgrade. Delete the Xposed framework app as well for the same reason. Updating should erase all of the background stuff that the Xposed originally installed in /system. Take a nandroid prior to updating just in case.
Click to expand...
Click to collapse
Thanks again, mate!
Is this the one I should download? https://forum.xda-developers.com/oneplus-3t/how-to/rom-oos4-0-nougat-op3t-leaked-t3523482

Crishien said:
Thanks again, mate!
Is this the one I should download? https://forum.xda-developers.com/oneplus-3t/how-to/rom-oos4-0-nougat-op3t-leaked-t3523482
Click to expand...
Click to collapse
Yes, that will work. OnePlus has not yet released the official zip through their website at this time, otherwise I would advise you to use the official zip.

Anova's Origin said:
Yes, that will work. OnePlus has not yet released the official zip through their website at this time, otherwise I would advise you to use the official zip.
Click to expand...
Click to collapse
Great, thank you. Imma let you know how it goes later today.

Anova's Origin said:
Yes, that will work. OnePlus has not yet released the official zip through their website at this time, otherwise I would advise you to use the official zip.
Click to expand...
Click to collapse
Not sure if I did anything wrong or I'm just impatient... But I flashed the update successfully and deleted dalvik. But got stuck at boot logo. Been hanging like this for 15 minutes, phone got hot and drained half its juice. So I reverted for now.... I'll try again at home with a charger... ?

954wrecker said:
Xposed over any OS without Xposed. I have never even flashed Nouget because I know its just a waste of time for me. Ive been on cm13 since the day it came out. DEC 11 2016.
Click to expand...
Click to collapse
what can xposed do that you actually need that you can't do with magisk?

EuEra said:
what can xposed do that you actually need that you can't do with magisk?
Click to expand...
Click to collapse
I don't think magisk can handle what xposed can handle.

954wrecker said:
I don't think magisk can handle what xposed can handle.
Click to expand...
Click to collapse
Indeed I will miss gravitybox. But if there is any other way to make my buttons do what I like which is (on the left - menu button with double tap for previous app/ home is home and recents on long press / right is back.)
Other than that it's all purely visual enhancement such as perfect color bar, media visualizer, and ****.
On the other hand I've just encountered a slight difficulty... Magisk won't work properly if I had Supersu previously installed, right?

Crishien said:
Indeed I will miss gravitybox. But if there is any other way to make my buttons do what I like which is (on the left - menu button with double tap for previous app/ home is home and recents on long press / right is back.)
Other than that it's all purely visual enhancement such as perfect color bar, media visualizer, and ****.
On the other hand I've just encountered a slight difficulty... Magisk won't work properly if I had Supersu previously installed, right?
Click to expand...
Click to collapse
What are you gaining if I may ask? I have never tried 7.0 or magisk because I see ZERO benefit and Id lose all my favorite modules.

954wrecker said:
What are you gaining if I may ask? I have never tried 7.0 or magisk because I see ZERO benefit and Id lose all my favorite modules.
Click to expand...
Click to collapse
That's what I wanna find out. I wanna see what's the new Android about. And I'm sure rovo will find a solution soon. And we will see xposed for nougat.

GravityBox is terrible and has slowed down every phone it's ever been put on (from my experience).
Xposed is a hack and it's shameful how it's holding back advancement.
Nougat > any hack

MattBooth said:
GravityBox is terrible and has slowed down every phone it's ever been put on (from my experience).
Xposed is a hack and it's shameful how it's holding back advancement.
Nougat > any hack
Click to expand...
Click to collapse
My phone is just as fast with xposed as it is without. All my apps work perfectly so I say any OS with Xposed is > Nougat

954wrecker said:
I don't think magisk can handle what xposed can handle.
Click to expand...
Click to collapse
Most of that is either completely unnessecary, pointless, or magisk can do it if people start developing for it. I have none of it (except no ads on youtube and the ability to turn off the screen) and i am completely fine. I think you tell yourself you need all that stuff but you actually don't, staying versions behind on the OS for it seems stupid.

954wrecker said:
My phone is just as fast with xposed as it is without. All my apps work perfectly so I say any OS with Xposed is > Nougat
Click to expand...
Click to collapse
Well that's your opinion and you're entitled to it, but I've noticed the total opposite across several devices. I always try Xposed on a new phone and I always massively dislike the way it works. Intercepting code that was not supposed to be intercepted just adds overhead. There's a good reason AOSP devs will refuse to look at any bug report that has Xposed in the logs.
EDIT:
Anyway, the battery savings from Nougat are too good to pass over. The only thing I need to customise on my phone is having the Google Dialer, and AdAway, whilst still keeping SafetyNet as passing, which Magisk does perfectly.
EuEra said:
Most of that is either completely unnessecary, pointless, or magisk can do it if people start developing for it. I have none of it (except no ads on youtube and the ability to turn off the screen) and i am completely fine. I think you tell yourself you need all that stuff but you actually don't, staying versions behind on the OS for it seems stupid.
Click to expand...
Click to collapse
Exactly, unless you use every setting on GravityBox then it's not entirely necessary, yet even if those functions are off or there are features of GravityBox you don't use, their code is still run. The bigger it gets the more the overhead there is. If you don't use, say, the network speed monitor, it's hook is still active. I could be wrong, but last time I dabbled with Xposed, this was the case.
If anything, smaller more granular modules would be better for GB. One module for network speed. One module for changing the on-screen buttons, etc. That way you only install modules that you use, rather than a whole library of them where you might only use 2-3 of the actual features.

Apps refuse to start because phone being rooted but it isn't!

At least 2 of my Apps refuse to start. One is my banking app and they do not offer any other way of interaction.
The problem is that the phone in fact is not rooted! It's just "OEM unlocked" to be prepared for root (which I need for E.g. titanium backup, but only maybe once a month).
Please give me a way out of this vicious circle!
I cannot remove the OEM unlock because it requires full wipe every time. Or is there a way?
Or what can I possibly tell the App Provider to improved their Code so that Oneplus phone state is being recognized (more) correctly?
Any help would be greatly appreciated.

Use Magisk I guess? Use it to hide root from that app.

Reeb_Lam said:
Use Magisk I guess? Use it to hide root from that app.
Click to expand...
Click to collapse
In fact I already flashed an official image and still (with no zip installed via TWRP) I'm getting refusals from these apps.
So for sure some apps decide from something else then simply an installed "root" manager or the installed "su" binaries.
What else could they decide from? "OEM unlock" was my first guess (and it would also be the worst, because as far as I know it can't be "hidden" temporarily, or can it?), but maybe there are other settings. Does anybody know more?

ako673de said:
In fact I already flashed an official image and still (with no zip installed via TWRP) I'm getting refusals from these apps.
So for sure some apps decide from something else then simply an installed "root" manager or the installed "su" binaries.
What else could they decide from? "OEM unlock" was my first guess (and it would also be the worst, because as far as I know it can't be "hidden" temporarily, or can it?), but maybe there are other settings. Does anybody know more?
Click to expand...
Click to collapse
You need to do some reading about Safetynet. If you're OEM unlocked you fail Verified Boot checks. Most custom Kernels include a bypass for this. Magisk alone should also work. I think you missed one important step:
Open Play Store Settings. Scroll down. It says 'Uncertified' at the bottom, right? Now install and set up Magisk. Go to system App Settings and clear Data and Cache for Play Store. Return to the Play Store Settings and scroll down. Now it should say 'Certified'. It might not be immediate, but it will happen. Now your Banking Apps work.
If you don't want, or have no luck with Magisk, simply flash a Custom Kernel that bypasses Verified Boot, and works with OOS.
Simple.

Thank you. That was for sure a major part of the overall issue. Unfortunately it didn't yet fix it. I'm now certified in play store and magisk succeeds with both safety net checks (which however it also did before). And root is disabled in magisk. dm-verity does not show the warning during Boot and the Check itself should be disabled (I followed the recommendation in another Thread to Patch the Boot Image).
Anything else you can imagine?

ako673de said:
Thank you. That was for sure a major part of the overall issue. Unfortunately it didn't yet fix it. I'm now certified in play store and magisk succeeds with both safety net checks (which however it also did before). And root is disabled in magisk. dm-verity does not show the warning during Boot and the Check itself should be disabled (I followed the recommendation in another Thread to Patch the Boot Image).
Anything else you can imagine?
Click to expand...
Click to collapse
Link to other Thread?
I don't know Magisk but are you hiding Root from your Banking App? Have you cleared Data and Cache for the Banking App since getting Certified?

First my phone did not Boot any more after installing superSU. Fixed that by patching Boot.img (to disable dm-verity) according to this thread: https://forum.xda-developers.com/oneplus-3t/how-to/disable-dm-verity-force-encryption-op3t-t3688748
Now data and cache of all (now) 3 affected Apps has been cleared and Magisk is configured to be hidden for them, but still no change.
However, in Magisk there is the "extended" option "AVB 2.0/keep dm-verity", which is unticked. I'm not sure, should I try to set it?
Any other idea?

ako673de said:
Any other idea?
Click to expand...
Click to collapse
Nope. If Play Store says Certified you should be good to go. I can only imagine it's a Magisk issue. Post screenshots of your config and let the Magisk experts pick through them. Maybe there's something not set up correctly.

ako673de said:
First my phone did not Boot any more after installing superSU. Fixed that by patching Boot.img (to disable dm-verity) according to this thread: https://forum.xda-developers.com/oneplus-3t/how-to/disable-dm-verity-force-encryption-op3t-t3688748
Now data and cache of all (now) 3 affected Apps has been cleared and Magisk is configured to be hidden for them, but still no change.
However, in Magisk there is the "extended" option "AVB 2.0/keep dm-verity", which is unticked. I'm not sure, should I try to set it?
Any other idea?
Click to expand...
Click to collapse
Hide Magisk Manager. I had to do that to get my banking app to work.
Edit: you may need to reboot after hiding Magisk Manager and clear you banking app's data before it works.
Sent from my OnePlus3T using XDA Labs

Thank you, indeed that WORKED! Well, at least for 2 out of 3 Apps. I think I can tell which one: "HVB banking". Maybe could somebody cross-check this one on his/her phone?

After firmware update to OOS 5.0.5 I now have the problem that my PlayStore can no longer be convinced in any way to show that it's certified. But interestingly my banking Apps work (currently really no root app installed). I even waited for one day because earlier in this thread somebody mentioned that it might take awhile. Is there anything special I need to care about under the new OS version?

ako673de said:
After firmware update to OOS 5.0.5 I now have the problem that my PlayStore can no longer be convinced in any way to show that it's certified. But interestingly my banking Apps work (currently really no root app installed). I even waited for one day because earlier in this thread somebody mentioned that it might take awhile. Is there anything special I need to care about under the new OS version?
Click to expand...
Click to collapse
Did you reflash custom kernel after update?

I'm not using any. What I did right after the update is to disable dm-verity (with a patched boot.img), like I did last time. But magisk is not yet re-installed because I wanted to see at least once the HypoVereinsbank App working, which it in fact does (different to last time when the phone was not rooted as well, and the store not certified!).

ako673de said:
But magisk is not yet re-installed
Click to expand...
Click to collapse
That's why... You can't pass the ctsProfile check if your bootloader is unlocked, and if you can't pass the ctsProfile check the Play Store won't be certified. You need Magisk for that...

Now I'm getting confused. The initial mail of this thread explains the situation as it was when I opened this thread:
--> Original ROM, no root, and banking apps didn't work <--
The advice to clear data of the PlayStore immediately brought the PlayStore back to "certified".
This is clearly in contrast to what you're saying now.
I can imagine only one reason: Maybe the older PlayStore had a bug and therefore was able to "certify" even with unlocked bootloader?
Sidenote: My main intention to do the firmware upgrade was that the "safety net checks" in Magisk suddenly stopped working one day (with the error message "invalid response", most probably you know what I'm talking about, I've read some comments from you on this issue). Therefore it's maybe really not too unlikely that Google has changed something very basic. Could you please confirm?
Edit: Now magisk is back, version 16.7, and in fact PlayStore is back to "certified" AND now even the HypoVereinsbank App works. Just one thing remains: magisk safety net check still says "invalid response" (after it downloaded some "FOSS" code, which it didn't do last time, when it was still working).

ako673de said:
Edit: Now magisk is back, version 16.7, and in fact PlayStore is back to "certified" AND now even the HypoVereinsbank App works. Just one thing remains: magisk safety net check still says "invalid response" (after it downloaded some "FOSS" code, which it didn't do last time, when it was still working).
Click to expand...
Click to collapse
https://www.didgeridoohan.com/magisk/MagiskHide#hn_The_response_is_invalid

Sorry, now comes a probably often asked question: do I need the safetynet check option in magisk for something real? Or do the alternative apps fulfill all possible needs? What are these needs? Isn't that exactly what the PlayStore does to determine "certified"?

After quite some months of absolutely no "root" problems with any of my apps, since today o2banking again doesn't work.
I tried to update Magisk, but after update of the Magisk manager app to v7.1.1(203) it reports that Magisk is not installed at all, and any update of Magisk itself resulted in just the same. So I reverted back to v6.1.0(165) and everything seems to be okay, except that o2banking doesn't work. SafetyNet is clean, Magisk is hidden for o2banking and Magisk manager is repacked.
Does anybody know what the problem might be? Especially with that new version of the manager app, but also with Magisk v19.0 which cannot be installed from v6.1.0 (max. is v18.1). Any ideas welcome! I'm now on OOS 5.0.8 by the way.
SOLVED it myself: As mentioned somewhere in the update FAQ of Magisk there was a bug in manager v6.1.0 that causes the updated v7.1.1 to co-exist with the old version if the old version has been re-packed. If anybody encounters the same problem, the solution is at the bottom of this page: https://www.didgeridoohan.com/magisk/ManagerIssues.
o2banking will then still not work. Update to v19.0 is mandatory. But that is no problem then any more...

probably your banking app identified oxygen os as custom rom and have root. 1 out of 3 banking app in my phone doesn't work with lineageos even though i already hide magisk, but when running oxygen os with magisk hide, and also hide magisk manager (turn it on in magisk manager setting) all 3 banking app work just fine. maybe try sending a message to bank app developer to add oxygen os as exception.

Did you notice my edit? It was a problem with magisk manager update and magisk main version. Now everything is back up and running.

Modules not working, can't return to old version, wipe needed on Galaxy S8 / Nougat

Hi,
I was running stock ROM with stock recovery plus Magisk v16 and MagiskManager v5.9.1 on my Galaxy S8 and Nougat. As far as I remember I did install MagiskManager using adb, pushed, patched and pulled the boot.img, flashed it using Heimdall. Both apk and patched_boot.img are available on my hard disk...
I then updated MagiskManager using the in app update. Afterwards I used the "direct install" to update Magisk. That took me to 20.4 / 8.0.2. I don't remember if it asked to install the runtime.
I installed modules busybox, sqlite3 and movecertificates, but with no effect (e.g. there is no /system/bin/sqlite3, no nc in my path, user certs remain user certs). I also can't find any indication in MagiskManager that modules are installed.
I didn't have time to figure out what's wrong and tried to revert back to my old versions.
That's what I did: Full uninstall from MagiskManager 8.0.2. Reboot without Magisk, adb push MagiskManager-v5.9.1.apk. Flash my old patched_boot with Magisk v16 using Heimdall. But unfortunately that gives me Magisk Manager stuck on the splash sceen. No applet can get root access, e.g. su on adb shell blocks (needs ctrl+c). Ok, uninstalled MM.
I installed the stock boot img in the intention to load MM 8.0.2 before I flash M 20.4. That didn't accept my pattern for the "your device is encrypted" screen. Well... I flashed M 20.4 patched boot.img again. After first try it shows an integrity issue and offers to wipe the phone.
* Anyway to go from here besides wipe?
* What residuals might be blocking when returning to the old versions?
* Why are modules not working on current version?
Thank you

urbancubb said:
* Why are modules not working on current version?
Click to expand...
Click to collapse
Are they current module zips, or ones that you had laying around from before updating? The modules might be using outdated installation scripts (that's my prime suspect at least).
* What residuals might be blocking when returning to the old versions?
Click to expand...
Click to collapse
Magisk v16 is soooo old. It's gonna be almost impossible to give any kind of help with that. Better to update to a current Magisk release.
* Anyway to go from here besides wipe?
Click to expand...
Click to collapse
I have no idea, you'd wan't someone who knows Samsung for that. Your device's forum might be a good place to start.

Didgeridoohan said:
Are they current module zips, or ones that you had laying around from before updating? The modules might be using outdated installation scripts (that's my prime suspect at least).
Click to expand...
Click to collapse
I installed them from within Magisk Manager from the online repo.
I noticed that this might be the case, but as there was updates this year I think on at least two of them and none worked, I think its a general problem and not caused by the module itself. Any module I could use to test wich works for sure?
Didgeridoohan said:
Magisk v16 is soooo old. It's gonna be almost impossible to give any kind of help with that. Better to update to a current Magisk release.
Click to expand...
Click to collapse
Which didn't work... We'll see.
Didgeridoohan said:
I have no idea, you'd wan't someone who knows Samsung for that. Your device's forum might be a good place to start.
Click to expand...
Click to collapse
Good hint, I started a new thread.
Thank you!

For the modules issue, the only way to know for sure what happened is to look at the install logs and the Magisk log for the following reboot.
So if you get things up and running again, and the issue still persists, make sure to provide those.

One thing I didn't think of before: I recently tried the SafatyNet check (which failed), maybe the failed reboot was the first one after checking, I don't remember exactly.