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" ?

[Q] Super su binary update making sdcard & system read only XPERIA M2 DUAL 4.4.4

I downgraded my Xperia M2 dual d2302 to 4.3 and rooted with towelroot and then flash 4.4.4 followed by flashtool force towelroot using super su. This would uninstall super su on my phone and install its own super su binaries and busybox content. The super su pro would however, remain installed. So, I would have to redownload the super su and as soon as i would open it, it would ask for binary update and then ask for reboot. I would just follow the prompt without question. As soon as it reboots,though the root would be there but sd card and system rewriteable will be gone and there is no way to make my system rewriteable without flashtool reflashing back to 4.3 and following the long procedure. I till now, would blame kitkat and sony for that. This continued for over 8 days till I realised that the real culprit was not sony or kitkat but super su binary update followed by reboot. This is highly anoying. What is the point of root if system or sd card writing is not allowed? For now, I am living with super su by canceling the binary update everytime I open it. I have OCD and I find it highly annoying. I tried searching for an option to cancel auto search for updates bur in vain. My phone works just fine without update. I need no updates and need a way to stop super su asking for update everytime. Please suggest me something.
I have now discovered that even if I cancel binary updates, supersu auto updates causing the same problem. So, now I have decided to live without Supersu as supersu is not needed for root. I have an unlimited root access for all my apps which have root permission now and to add icing to the cake, my bootloader is locked. If anyone else is searching for a way to make Sony Xperia M2 dual 4.4.4 system writebale without unlocking bootloader, just follow:
LOCKED BOOTLOADER
1. Downgrade to JB, Root your Phone using Towel Root in Jelly Bean
2. Update via OTA to KK 4.4.2 or KK 4.4.4 whatever you need (4.4.4 is recommended)
3. In this process, don't try to install or uninstall anything
4. Wait for booting finish
5. Install latest SuperSU from Play Store
6. Open Flashtool in PC
7. Connect your phone to PC
8. Now flashtool will describe your phone information, then click Root Tab in top, after that choose force root by TowelRoot
And after this, do not install supersu or any other root control app. Just let your phone be as such without updating binaries or anything and you will have root. You will have unrestricted root on Xperia M2 dual, Enjoy and remember not to install supersu, kingsu, cm superuser or any similar app.

I was thinking to help you, but then i was worried if something else goes wrong, then you will blame me, just like you blame super su.

Yeah I'm sure of that. Just a note for you: I already have root. Super Su is not needed for root. It only controls which app gets access to root. The only problem without super su is that there is less safety as any app can get root without restrictions. I just want super su to be polite and less invasive by learning to live with whatever it gets rather than forcing itself on us. If I don't want binary updaye, super su has no business updating on its own. I just want a way to stop super su from updating binaries and I don't think you can help unless you can patch the app which I doubt

gauthamraob said:
Yeah I'm sure of that. Just a note for you: I already have root. Super Su is not needed for root. It only controls which app gets access to root. The only problem without super su is that there is less safety as any app can get root without restrictions. I just want super su to be polite and less invasive by learning to live with whatever it gets rather than forcing itself on us. If I don't want binary updaye, super su has no business updating on its own. I just want a way to stop super su from updating binaries and I don't think you can help unless you can patch the app which I doubt
Click to expand...
Click to collapse
I think you are misunderstand about the binary thing, supersu need to update the binary so it will work properly, its not like updating app on playstore, binary is the root system itself i believe.
Help me out on this one, afaik, root access need atleast 1 superuser app to allow and control the root access for any root app. Any root app will need to request for granted the root at least once ti get the root access.
So tell me, how do you manage to have rooted device without any root management app such [email protected]@cm supersu?
---------- Post added at 02:42 PM ---------- Previous post was at 02:31 PM ----------
BTW, tell us what do you need on your device that will make you feel better. (About the superuser @ root thing of course)

NeoLogY said:
I think you are misunderstand about the binary thing, supersu need to update the binary so it will work properly, its not like updating app on playstore, binary is the root system itself i believe.
Help me out on this one, afaik, root access need atleast 1 superuser app to allow and control the root access for any root app. Any root app will need to request for granted the root at least once ti get the root access.
So tell me, how do you manage to have rooted device without any root management app such [email protected]@cm supersu?
Click to expand...
Click to collapse
No, I am already having root . I have integrated most of the updates to my system app to my sys/app folder through lucky patcher and have installed the modded play store . I can even edit and delete system files in "ES explorer" file manager and stop items from startup using "all-in-one-toolbox" boot manager. I have an older version of su binaries which was installed automatically into my phone by "flashtool by androxide" using the force root mode using towel root :good: . But the supersu app was not installed and if the app existed before rooting, flashtool would uninstall it and also replace the new su binaries with an older version ! So, I already have full root access without the supersu app.
As far as i know, supersu is not needed for root. It is only a gatekeeper app which restricts the unlimited access of root to any app by making the apps that need root to ask for permission first. Without supersu installed, root apps get root access without asking permission provided binaries (any version) are already present. Also, for normal people who don't know or can't install binaries directly, they rely on apps like supersu, CM etc for installing the binaries. But once the binaries are installed, the supersu app is no longer needed for root (except in cases of OTA updates or updation of binary to a newer version) but instead works as a security guard for root.
Edit:
What I want is a way to make supersu submissive and to make do with whatever binaries are already present. If it is not broken, then there is not need to fix/update it. But supersu is extremely adamant. Even when I cancel the update, it gets the binary updated by itself when it gets an internet connection. And after reboot, my system rewriteable access would be gone! And how do I know for sure that Supersu updated binaries without my consent? That is because when I open supersu, it no longer asks for binary updates implying that it updated it on its own. I want supersu to understand that it is my phone and I will install only those things that i deem fit to be installed. Auto update services are something which i don't like.

What I want is a way to make supersu submissive to my command and to make do with whatever binaries are already present. If it is not broken, then there is not need to fix/update it. But supersu is extremely adamant. Even when I cancel the update, it gets the binary updated by itself when it gets an internet connection. And after reboot, my system rewriteable access would be gone! And how do I know for sure that Supersu updated binaries without my consent? That is because when I open supersu, it no longer asks for binary updates implying that it updated it on its own. I want supersu to understand that it is my phone and I will install only those things that i deem fit to be installed. Auto update services are something which i don't like and must not be done

Actually, you do have a good point here, as by mean we want root for full control of our property. And i just realize about the binary being updated thru network without our consent. I am hoping if you could get a logcat of the device when this happened next time. Including modem log, system, main, event, audit log, if possible. Im not sure if i can help you on this one, but i really want to look deeper into this one. Hope you can help me, using SysLog app. Can you do that, please?

NeoLogY said:
Actually, you do have a good point here, as by mean we want root for full control of our property. And i just realize about the binary being updated thru network without our consent. I am hoping if you could get a logcat of the device when this happened next time. Including modem log, system, main, event, audit log, if possible. Im not sure if i can help you on this one, but i really want to look deeper into this one. Hope you can help me, using SysLog app. Can you do that, please?
Click to expand...
Click to collapse
At present I am using my phone without supersu as I will have to spend a lot of time downgrading to 4.3 and then rooting followed by painfully slow 4 OTAs in succession (there is no single direct OTA from 4.3 to 4.4.4 on Xperia M2 dual, unfortunately :crying: ) followed by installation of all my apps. I too wish there was a fix for supersu but the time I'll have to spend on that will be enormous and also considering that in this september my phone will mostly get lollipop 5.1, the 4.4.4 woes will soon be history.
Also, I want to mention that I haven't unlocked my bootloader yet. If I unlock my bootloader, all these problems with supersu will vanish. The actual difficulty I am facing is because there is no single post on the internet that says how to get system to be rewriteable without unlocking bootloader in Xperia M2 devices. Every post I have read of only has people with unlocked bootloader saying what to do and people with locked bootloader complaining that they aren't able to make their system rewriteable. I am probably one of those rare people who managed to get complete root with locked bootloader and hence facing the issue of lack of peer help.
Anyways, I really appreciate your interest shown in helping me. If I ever have to update my binaries in the future I will definitely take a log of it and pm it to you in case similar situation arises.
Cheers.

Same thanks to you. Actually, i think it is better to put the log here, as more hands and mind will be able to reach it, meaning higher percentage on discovering any hidden in the log. You are right about the lock bootloader, even until now i still unable to manage to truely understand about bootloader, as i didn't have any device with it to get inhand with the system. As always, i do appreciate any kinda knowledge exchange. Thanks in any way.

That's exactly why your system is read only and you can't move apps/data to sd ect without supersu installed and the binaries updated and Sony ric killed you don't have full root r/w access to system. The way you have rooted your device is the same way I did mine it's the easiest way there is if you can't get it right doing that way then maybe you should put your Phone back to stock. Flash jb, root with towelroot apk(at this point do not update anything), now update over the air to 4.4.2 then again to 4.4.4(again update nothing but phone)root will stick after each update. Download supersu connect your phone to flashtool and click on the force root tab(kills Sony ric installs supersu binaries and busybox) making system r/w
Search on here for the m2 forum if you still have problems
D2303,18.3.1.C.1.15 kk, deodexed, debloated, rooted, philz touch recovery, bravia engine 2+x-reality+z3 super vivid, viper audio, xposed mods.

[SOLVED] Safe to continue?? or start again? please help

This is driving me nuts... I was on 5.1.1 and I am trying to get it rooted.
I'm following a guide which goes like this..
1. downgrade to kitkat 4.4 using flashtool
2. root 4.4
3. Install custom recovery
4. Flash 5.1.1 pre-rooted zip
I have had problem after problem and I think something may have screwed up along the way.
I finally managed to get kitkat installed using flashtool and a generic C6903 .108 ftf.
Problem 1... I used 'Easy Root tool' from xda to root kitkat... but it seemed to hang at the cleaning up' stage - is this a problem?
Problem 2... every time I restart my phone - kitkat asks what language etc. Whats that all about?
PROBLEM 3. The guide Im following says to install busybox after rooting kitkat.
I've tried 2 different busybox installers and both of them fail when trying to install bb.
QUESTION: Are these 3 problems linked and will it prevent me from continuing with the guide I am trying to follow??? i.e. do I need busybox to install XZ Dual Recovery and therefore a pre-rooted zip?
Root Checker basic says kitkat is rooted, as does the first busybox installer.
I'm taking a short break from this nightmare, so in the meentime if any of you chaps could advise me on whether or not its ok to continue or if I have fecked up the whole process, that would be great.
Thanks in advance

problem 1 : re run the installer again, don't use administrator mode
problem2 : use any simcard on your phone
others, sorry i have no idea, you could download busybox from playstore ?

I would just start over and try a different root program. busybox is failing to install because the root didn't work.

Gamer4Life said:
problem 1 : re run the installer again, don't use administrator mode
problem2 : use any simcard on your phone
others, sorry i have no idea, you could download busybox from playstore ?
Click to expand...
Click to collapse
Problem1... thank you, I'll try again
Problem2... Thanks. I thought It could be the lack of a SIM card and then I thought no! that can't be it lol... as usual - I was wrong ha
others... yeah mate, tried 2 different installers from play store - no joy with either.
Thanks for your help

xasbo said:
I would just start over and try a different root program. busybox is failing to install because the root didn't work.
Click to expand...
Click to collapse
Cheers bud, I'll try 'easy root tool' once more without admin priv, if its the same story I'll start over and try a different root tool. Any suggestions on that?
Also: how come root checker says I'm all good and rooted but busybox wont install? even one of the busybox installers says "Your device is rooted"!?!?
Thanks for all the help mate

i think you don't have supersu installed, and busy box couldn't get root rights
so download supersu from playstore, open it and update binaries as normal, then reboot
and you would be able to install bb

thesweeney80 said:
Cheers bud, I'll try 'easy root tool' once more without admin priv, if its the same story I'll start over and try a different root tool. Any suggestions on that?
Also: how come root checker says I'm all good and rooted but busybox wont install? even one of the busybox installers says "Your device is rooted"!?!?
Thanks for all the help mate
Click to expand...
Click to collapse
Try the suggestion made by @Gamer4Life, just in case you somehow got root but it failed to install the APK needed to manage it. Might save you some work. That would explain why everything thinks you're rooted.
As for an alternative, if you still need it, I think I used kingroot successfully on 4.4.4.

Gamer4Life said:
i think you don't have supersu installed, and busy box couldn't get root rights
so download supersu from playstore, open it and update binaries as normal, then reboot
and you would be able to install bb
Click to expand...
Click to collapse
thanks for the tip mate but no joy see my reply to xasbo, cheers

xasbo said:
Try the suggestion made by @Gamer4Life, just in case you somehow got root but it failed to install the APK needed to manage it. Might save you some work. That would explain why everything thinks you're rooted.
As for an alternative, if you still need it, I think I used kingroot successfully on 4.4.4.
Click to expand...
Click to collapse
Thanks mate. I was hoping Gamer4life might be right as there was no Supersu installed.
I installed supersu from play store no problem... but when I try to update binaries it says' update failed. Please reboot and try again.'. tried reboot but same story.
I guess I'll try 'easy root tool' again and then will give kingroot a bash if needbe.
One last pre-emptive question...
If I root kitkat using kingroot... should I replace kinguser with supersu before proceeding with XZDR and a pre-rooted zip or will kinguser be sufficient to continue.
Many thanks to you and everyone else who has tried to help me with this clusterf*ck,.. I appreciate it

can you screenshot the error you got ?
i reread your op, you don't need busybox to install dual recovery, it installs like the easy root installer, very easy
just one click and you are ready to go
also xzdualrecovery will root your device and install supersu by default if you have kitkat, so you can skip that.
edit (i don't think this will work because towelroot doesn't work on z1 4.4.4 108)

Gamer4Life said:
can you screenshot the error you got ?
i reread your op, you don't need busybox to install dual recovery, it installs like the easy root installer, very easy
just one click and you are ready to go
also xzdualrecovery will root your device and install supersu by default if you have kitkat, so you can skip that.
edit (i don't think this will work because towelroot doesn't work on z1 4.4.4 108)
Click to expand...
Click to collapse
must have been a glitch in the matrix mate becuase its now working (Possibly thanks to your suggestion of installing Supersu?).
I reconnected to PC in order to give 'easy root tool' another crack at it.
As soon as I start install.bat It says checking if device is rooted AND I get a superuser request on my phone for adb.shell - Happy days!
I granted root access to adb shell and the root tool says Job Done. Root success etc.
So I disconnect and try to update su binaries and it worked first go!!!
*Touch wood* I think I'm now past the tricky part and it should be plain sailing from here on in. lol
THANKS for the help Gamer4Life, and everyone else who has chipped in.... hopefully my next post will be to report a fully rooted 5.1.1 :fingers-crossed:

Gamer4Life said:
also xzdualrecovery will root your device and install supersu by default if you have kitkat, so you can skip that.
edit (i don't think this will work because towelroot doesn't work on z1 4.4.4 108)
Click to expand...
Click to collapse
Correct, TowelRoot doesn't work for this version.
---------- Post added at 01:27 PM ---------- Previous post was at 01:26 PM ----------
thesweeney80 said:
THANKS for the help Gamer4Life, and everyone else who has chipped in.... hopefully my next post will be to report a fully rooted 5.1.1 :fingers-crossed:
Click to expand...
Click to collapse
:good: godspeed

@thesweeney80 you are welcome have fun

xasbo said:
:good: godspeed
Click to expand...
Click to collapse
Gamer4Life said:
@thesweeney80 you are welcome have fun
Click to expand...
Click to collapse
you fellas are the muts nuts.
All done, everything went smoothly once I got kitkat rooted properly.
MANY thanks for all your help.
Honestly I wouldnt even bother owning a smartphone if it wasnt for the peeps on XDA... F*cking awesome. THANKS :good: :highfive:

:good: awesome! don't forget to pay it forward sometime.

[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

Phone stuck on booting screen after install

Hello,
first off, sorry. I was stupid and didn't read into it before installing (or trying to install) Xposed to my Samsung S8. Yes, i've read now that it doesn't work with the official ROM, but now it's a bit to late.
So. After rooting my S8 today (using TWRP) i wanted to install Xposed. I downloaded an installer from this site because.. umm, i had a brain fart. For some reason my brain took that site as the official website, so i downloaded it from a 3rd Party site instead of the actual website.
I installed the apk and granted root access. After that i clicked on install and Xposed installed successfully. After that it obviously asked me to reboot my device, which i did. But now i am stuck on the Samsung screen of the boot progress. I know i could technically just wipe the phone (again) and start anew, but i'd like to avoid that if possible. I can access TWRP, but if i try to access the system files in the file browser, it shows "0MB" and i can't access them.
I tried downloading an uninstaller linked in this thread, but i don't know which one i should download.
Sorry again for me being so stupid and not reading into it and downloading from some weird 3rd Party site.
Thanks in advance for the help!
EDIT: And yea, of course i didn't create a backup before installing Xposed. So if there is no way to properly uninstall it, i gotta wipe everything once again

Emilia-Chan said:
Hello, first off, sorry. I was stupid and didn't read into it before installing (or trying to install) Xposed to my Samsung S8.......
Click to expand...
Click to collapse
I don't have this device but, I believe that you should be able to flash (via TWRP) the Framework Uninstaller located on the following Official XPosed link. Just select the correct ARCH (ARM, ARM64, etc...) for your device.
http://dl-xda.xposed.info/framework/uninstaller/
If necessary, you can always try to obtain some additional member guidance and support from the following Q&A thread that's specific to your device and variants.
https://forum.xda-developers.com/showthread.php?t=3582142
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.

In the link provided by @lbuprophen use the arm64 zip uninstaller (latest version) to uninstall exposed.
Just curious how long did you let it try to boot for,mine took 10-15 minutes for it to do it's thing and boot up.
Sent from my Samsung Galaxy S8 using XDA Labs

Ibuprophen said:
I don't have this device but, I believe that you should be able to flash (via TWRP) the Framework Uninstaller located on the following Official XPosed link. Just select the correct ARCH (ARM, ARM64, etc...) for your device.
Click to expand...
Click to collapse
I tried that before, unfortunately without success. It also may be noteworthy that my brain turned off and downloaded the XPosed installer off some 3rd Party site. I know. Stupid. But it happened.
spawnlives said:
In the link provided by @lbuprophen use the arm64 zip uninstaller (latest version) to uninstall exposed.
Just curious how long did you let it try to boot for,mine took 10-15 minutes for it to do it's thing and boot up.
Click to expand...
Click to collapse
I waited over an hour for my phone to boot, before and after flashing the uninstaller. I also tried wiping it and even completely formatting the data, everything without any success. It kept on not passing the Samsung screen and eventually bootlooping.
I fixed the issue by just flashing the stock rom with odin and then reinstalling TWRP and rooting my device again. Will stay away from XPosed with this phone for now.
Thanks for the advice anyways!

Emilia-Chan said:
.... I fixed the issue by just flashing the stock rom with odin and then reinstalling TWRP and rooting my device again. Will stay away from XPosed with this phone for now. Thanks for the advice anyways!
Click to expand...
Click to collapse
You did what I would have probably done myself in this situation by starting from scratch.
I just wanted to let you know that I believe that I had saw somewhere (within the dedicated area of the forum for your device) that individuals were successful with Magisk XPosed.
Though I do understand if you want to stay away from XPosed until your ready again and I'm happy to see that your at least up and running again.
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.

I got the same even just after the installation of the apk for Systemless Xposed on an Xperia (XposedInstaller_3.1.5-Magisk.apk) found here: https://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268
I made a reboot as I like to isolate the issues while they happen. That was it: bootloop..