Develop Bugs

Disabling Knox on Tab S 8.4 4G

I'm brand new to this website, and have only signed up because I cannot find a solution for this problem. I have always used the forum to get answers, but never though to join! My Galaxy Tab S 8.4 4G T705Y was put through the CF-Auto-Root method, and no a glitch at all. Very smooth. By the way I checked the ChainFire website to make sure I was using the latest. When my device started up I noticed, as I have done before with my Nexus phones, that SuperSU has been added. Good Sign!
But when I open SuperSU I was prompted to update the Binary. Then I pressed 'continue', used the 'normal' method, and waited. It then asked me if I would like to Disable Knox. Yes I would! FAILED TO DISABLE KNOX. Shut down SuperSU. Unhappy Face. As you can see at this point, I am not very up to speed with my rooting knowledge.
So then I decided to select the 'never' option to updating SuperSU, and still it failed to update the binary, I'd say due to Knox stopping it from gaining access.
So my pickle is this: I can't update SuperSU because Knox will not allow me to use SuperSU. I cannot simply hit yes to disabling Knox in SuperSU, as that didn't work for me. I also tried finding something called Knox on my tablet and it seems to be very elusive. I tried updating SuperSU on Play Store also, but to no avail!
I am also unable to use any third party app to do so as I need to grant them access in SuperSU before they can begin! And around I go...
There is a guide here http://forum.xda-developers.com/showthread.php?t=2540761 but it's not for my device so I'm a bit hesitant to start trying random things, as my device is working great atm!
Any info or help would be greatly appreciated!

Look in the android development section for my updated builds of cf_autoroot and flash that.
If you still get issues flash supersu v2.49 with twrp.

ashyx said:
Look in the android development section for my updated builds of cf_autoroot and flash that.
If you still get issues flash supersu v2.49 with twrp.
Click to expand...
Click to collapse
That seemed to at least do something, now it's saying there is no SU Binary installed. So I googled how to do that, then saw you needed TWRP to do so. And in order to get that, I needed the SDK and JDK, so I got them, but then in then couldn't find any of the right files in the SDK folder when trying to install through command prompt. There is a cool program called TWRP Manager that claims to do it, but you need root access. Lets not go there. So method 2: you needed to use a program like GooManager. But even then root access seems to be the order of the day. Ive tried Terminal Emulator and Package disabler also.

clint.fish said:
That seemed to at least do something, now it's saying there is no SU Binary installed. So I googled how to do that, then saw you needed TWRP to do so. And in order to get that, I needed the SDK and JDK, so I got them, but then in then couldn't find any of the right files in the SDK folder when trying to install through command prompt. There is a cool program called TWRP Manager that claims to do it, but you need root access. Lets not go there. So method 2: you needed to use a program like GooManager. But even then root access seems to be the order of the day. Ive tried Terminal Emulator and Package disabler also.
Click to expand...
Click to collapse
UPDATE: So now I have managed to try and install the version of superSU that you have released in the dev thread, using TWRP. seemed to work fine, but i still got the same binary missing error.

clint.fish said:
That seemed to at least do something, now it's saying there is no SU Binary installed. So I googled how to do that, then saw you needed TWRP to do so. And in order to get that, I needed the SDK and JDK, so I got them, but then in then couldn't find any of the right files in the SDK folder when trying to install through command prompt. There is a cool program called TWRP Manager that claims to do it, but you need root access. Lets not go there. So method 2: you needed to use a program like GooManager. But even then root access seems to be the order of the day. Ive tried Terminal Emulator and Package disabler also.
Click to expand...
Click to collapse
Whoah way way way over complicating things. You just install twrp with odin and that's it.
Then you flash this with twrp http://download.chainfire.eu/743/SuperSU/BETA-SuperSU-v2.52.zip

ashyx said:
Whoah way way way over complicating things. You just install twrp with odin and that's it.
Then you flash this with twrp
Click to expand...
Click to collapse
So this is what I do.
Power off device.
Restart in Download Mode.
Use Odin to install the cf-autoroot-twrp-t705.tar from the development section.
When device restarts I put supersu version 2.52 (beta) on the devices memory, then turn off device.
Restart in TWRP Recovery mode, hit install, choose the zip file, install, reboot device.
When device reboots, open superuser and get this message: "There is no SU binary installed, and SuperSU cannot install it. This is a problem! If you just upgraded to Android 4.3, you need to manually re-root - consult the relevant forums for your device".
I swear i'm not blonde. :good:

Something is blocking supersu from installing. Which firmware build is this device running and is reactivation lock disabled?

ashyx said:
Something is blocking supersu from installing. Which firmware build is this device running and is reactivation lock disabled?
Click to expand...
Click to collapse
**Googles how to check firmware version** Build Number KOT49H.T705YDOU1ANG1
**Googles how to bypass reactivation lock...** hmm seems hard. And I cant see it as an option in my security menu.

clint.fish said:
**Googles how to check firmware version** Build Number KOT49H.T705YDOU1ANG1
**Googles how to bypass reactivation lock...** hmm seems hard. And I cant see it as an option in my security menu.
Click to expand...
Click to collapse
UPDATE: So I went into my Samsung account and Performed a factory reset. Only had the device a few days so no biggy. Then as it reset i chose not to put in and Samsung details and skip all the options i could, assuming this would help. Flashed cf autoroot with odin, then updated supersu through twrp... still nothing

clint.fish said:
**Googles how to check firmware version** Build Number KOT49H.T705YDOU1ANG1
**Googles how to bypass reactivation lock...** hmm seems hard. And I cant see it as an option in my security menu.
Click to expand...
Click to collapse
UPDATE: SUCCESS! I used the latest version of Kingroot available on this forum. From looking around, you are a very patient person ashyx. Thanks for all your help!

clint.fish said:
UPDATE: SUCCESS! I used the latest version of Kingroot available on this forum. From looking around, you are a very patient person ashyx. Thanks for all your help!
Click to expand...
Click to collapse
This doesn't make sense. Something is amiss if you can't root with cf_autoroot or twrp. You are the only one as far as I'm aware that has experienced this.
Reactivation lock is under 'Find my phone' in security settings.

clint.fish said:
I'm brand new to this website, and have only signed up because I cannot find a solution for this problem. I have always used the forum to get answers, but never though to join! My Galaxy Tab S 8.4 4G T705Y was put through the CF-Auto-Root method, and no a glitch at all. Very smooth. By the way I checked the ChainFire website to make sure I was using the latest. When my device started up I noticed, as I have done before with my Nexus phones, that SuperSU has been added. Good Sign!
But when I open SuperSU I was prompted to update the Binary. Then I pressed 'continue', used the 'normal' method, and waited. It then asked me if I would like to Disable Knox. Yes I would! FAILED TO DISABLE KNOX. Shut down SuperSU. Unhappy Face. As you can see at this point, I am not very up to speed with my rooting knowledge.
So then I decided to select the 'never' option to updating SuperSU, and still it failed to update the binary, I'd say due to Knox stopping it from gaining access.
So my pickle is this: I can't update SuperSU because Knox will not allow me to use SuperSU. I cannot simply hit yes to disabling Knox in SuperSU, as that didn't work for me. I also tried finding something called Knox on my tablet and it seems to be very elusive. I tried updating SuperSU on Play Store also, but to no avail!
I am also unable to use any third party app to do so as I need to grant them access in SuperSU before they can begin! And around I go...
There is a guide here http://forum.xda-developers.com/showthread.php?t=2540761 but it's not for my device so I'm a bit hesitant to start trying random things, as my device is working great atm!
Any info or help would be greatly appreciated!
Click to expand...
Click to collapse
Chimed in with some feedback but noticed your problem solved after I replied. Unable to delete. Glad to see you're good to go though.

Why won't SuperSU update on CM13?

My Tab Pro 8.4 has been bootloader unlocked since I got it months ago. It has always run a custom ROM, usually just CM12 nightlies with root from SuperSU flashed in TWRP and no Xposed or other "fancy" stuff installed. Since the CM nightlies shifted to CM13 I can't get SuperSU to "update" (the notice that says you must update SuperSU). I've tried reflashing, I've tried wiping and doing new installation from CM13, I've tried different versions of SuperSU. Nothing works to successfully install an updated SuperSU. I've never had this problem before. I've read everything I can find and found several places where something like this is being discussed, but no path to resolution. How can I fix this?

I believe SuperSU doesn't work in CM13. Just use the built-in root method. Open the developer options and use the root method in there.

Sicron said:
I believe SuperSU doesn't work in CM13. Just use the built-in root method. Open the developer options and use the root method in there.
Click to expand...
Click to collapse
I've tried using only the built-in root method. I set it to "both APPS and ABP" (or whatever that last option is). That's not enough for Root Explorer, not enough for PIE Control, not enough for AdAway, at least in my case. All those apps still indicate that I'm not rooted.

Both AdAway and Rootexplorer work fine for me. Actually, I haven't seen a root app that doesn't work with the built-in root.

Sicron said:
Both AdAway and Rootexplorer work fine for me. Actually, I haven't seen a root app that doesn't work with the built-in root.
Click to expand...
Click to collapse
Hmmm. Well, that'd be a great solution for me so I'll give it another go. Wipe wipe wipe, flash a CM13 daily, flash CM13 GAPPS, wipe Dalvic cache and cache, reboot. In Settings, enable Developer Options, set Root Access to Apps and ADB. Reboot. If that's not the recommended procedure I hope someone will let me know.

Sicron said:
Both AdAway and Rootexplorer work fine for me. Actually, I haven't seen a root app that doesn't work with the built-in root.
Click to expand...
Click to collapse
Well, maybe the problem I have is different than the one I THOUGHT I had. Wiped, installed CM13 daily, installed CM13 GAPPS, set Root Access in System/Developer Options/Root Access to Apps and ADB. I guess root access exists but I'm not sure. In Root Explorer I CAN switch folders from Read/Write to Read Only (normally a root only option) and AdAway installed and ran fine. BUT -- in PIE Control I still get "Can not, rooted only" when I try to use the "Back" command. There is often a "hashtag" (or "pound sign") symbol in the Status Bar, just as there would be if I needed to update SuperSU, but the symbol is on the far RIGHT and doesn't correspond to any message in the drop down box. Plus, I have never seen the pop up box that normally appears to ask me if I want to grant root access to an app or process. So, what am I? Partially rooted?

It has full root, sounds like the app needs updating for CM13 and / or other root methods. (not CM13's fault)

otyg said:
It has full root, sounds like the app needs updating for CM13 and / or other root methods. (not CM13's fault)
Click to expand...
Click to collapse
What I'm reading here makes sense but there must be another variable. My phone (Moto X Pure) is running a custom MM ROM, SuperSU DOES install and run just fine, I get all the expected root prompts and controls and the Back button (which requires root) works in PIE Control. I'm guessing, therefore, that the "problem" lies with CM13 as a specific MM ROM rather than with all MM ROMs. Time to flash a different MM ROM on my SM-T320.

[Guide] Android Pay on rooted T-Mobile G5 - UPDATE: Workaround developed!

Android Pay use after rooting has been discussed in a few other threads, here on XDA, notably the 6P and 5X Nexi:
http://forum.xda-developers.com/nexus-6p/general/android-pay-root-t3309072
http://forum.xda-developers.com/nexus-5x/general/passing-safetynet-root-t3307659
With our newly rooted H830s (courtesy of http://forum.xda-developers.com/tmobile-lg-g5/development/root-h830-t3384526), it'd be nice to collect our information here.
I am very interested in how Android Pay may or may not work after our TOT flash. Here's a quick tutorial:
SuperSU must install via a 'systemless' root method due to security changes with Marshmallow. Thus, when SuperSU is flashed in TWRP as described in the TOT root thread, it can only install this way. It should not affect the /system partition.
Android Pay uses the "Safetynet API" to detect for tampering/root. What they classify as tampering is not entirely clear. But they do check /system among other things. It looks like apps that have altered the /system partition in some way are detected via this method.
(more boring info here http://www.howtogeek.com/241012/saf...y-and-other-apps-dont-work-on-rooted-devices/ )
It must also check the permissions of the /su/bin folder, as it should have a 751 permission profile (which is the described fix in the TOT root original post).
That is:
-Run "adb shell"
-From the shell run "su"
-On the # prompt run "chmod 751 /su/bin/"
Or, you can use root explorer to change the permissions octal to 751 for that folder.
It is set to this permission state in the rooted TOT upon first install. Obviously other root alterations you do may change it.
There are apps, such as Safetynet Helper sample (https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample), which can utilize the API to see if the API is tripped.
Right after installing the TOT and getting everything to boot properly, the app shows everything is still kosher. I was able to run Android Pay, add credit cards, and have confirmed with a payment transaction.
I believe any root app that doesn't make permanent changes to /system in and of itself will probably keep Android Pay working. Obviously, for instance, if you have a terminal program app with root, and run some commands that alter your system partition/files, it may trip SafetyNet, though just having the app installed does not.
EDIT1: As of 7/25/16, a change was made to the SafetyNet API and it now detects systemless root. Android Pay no longer works on rooted devices, regardless of method. A new method will need to be developed.
EDIT2: As of 8/22/16, a workaround has been developed and tested!​Developer @topjohnwu has created Magisk (http://forum.xda-developers.com/android/software/mod-magisk-v1-universal-systemless-t3432382). This is a new way of integrating systemless changes into Android devices. This includes root, xposed, etc. The unique thing with Magisk is that you can instantly un-root your device, run Android Pay, and then reactivate root, all without rebooting. It is pretty seamless.
See the referenced thread for the latest information. It does take some work to install but it's fairly straightforward.
If you want to start from a clean install, @Gungrave223 has detailed the steps here:
http://forum.xda-developers.com/showpost.php?p=68353051&postcount=22
If you want to keep your data, it's just slightly more work. Assuming you are starting with a rooted install, here is a quick summary on how to do this:
0. You may want to first un-register the cards you have in Android Pay. Some banks apparently only allow a set # of installs before they block additional installs, thus requiring you to call the bank directly to have them reset that number. If Android Pay resets (unsure what security changes trigger this), it will forget your cards, thus leaving those cards registered on a phantom install. Un-registering first may prevent this.
1. Get the Magisk flashable zip, the Magisk-altered phh-superuser.zip, and the Magisk manager apk from the referenced thread.
2. Go to SuperSU and select full unroot. DO NOT restore the stock boot.img. DO NOT restore the default recovery. The phone should reboot and your root will be lost.
3. You should now restore the stock boot.img. This can be done without losing your data or re-encrypting your data. There are 2 ways.
Flash autoprime's stock boot.img zip file through TWRP (recommended), OR
Flash the TWRP-ed TOT file through LGUP, using the UPGRADE (not refurbish) setting
Why not just allow SuperSU to restore the stock boot.img in step 2? Because it will reboot instantly into system and start encrypting your data, with no way for you to intervene and boot into TWRP first!
4. You likely did not have data encryption on your initial rooted installation. If you want to keep yourself un-encrypted, you MUST immediately boot into TWRP before the next power on. If you do not, it will re-encrypt your data. This is the default behavior of the stock boot partition, which you just restored in the step above. You can make this easy for yourself by TWRP flashing autoprime's stock boot.zip and then immediately doing the next steps. Note: Magisk can be installed just fine on a phone with an encrypted data partition if you don't care about data encryption.
Flash the magisk.zip from the Magisk thread. This installs Magisk and also disables the forced encryption (just like the dm-verity zip)
Re-establish root by then flashing the special modified phh-superuser.zip
Note: Chainfire's SuperSU is NOT compatible if you want to use Android Pay
5. Reboot into system. You need to then install from the Playstore phh's superuser app. You also need to install the Magisk manager apk. Grant all your usual apps root permission in the superuser app.
6. Run Magisk Manager and grant it superuser access. You'll find a simple toggle to mount/unmount root. Unmount! Check that SafetyNet will pass. If you've done everything right, it will!
7. Run Android Pay. Add your card(s) back. Mount root back and go about your business.
8. When you want to use Android Pay, unmount root and run the app. Here's a tricky part (and currently a work in progress). We do not know how often or when Android Pay checks for root. We DO know that it does this when you initiate adding a new card. So you can try an Android Pay transaction. If it fails (they often do, even if you are unmounted root at that time), pretend to add a card, cancel it, and then do the transaction again. It should work now!

pay was not working after I installed the Fluence patch, uninstalled xposed and Android Pay is working with no issues with root.

fatapia said:
pay was not working after I installed the Fluence patch, uninstalled xposed and Android Pay is working with no issues with root.
Click to expand...
Click to collapse
The Fluence patch has a huge # of system changes. I would totally expect xposed to break the SafetyNet.
So do you have Fluence still installed, with only xposed removed?

waylo said:
The Fluence patch has a huge # of system changes. I would totally expect xposed to break the SafetyNet.
So do you have Fluence still installed, with only xposed removed?
Click to expand...
Click to collapse
Yup you got it, I had been running Xposed off Fluence for a while until I left my wallet at home and didn't feel like starving. So I downloaded the Xposed uninstaller only, ran it in recovery and then let it reboot and Pay was working again.

I followed the instructions for rooting in this thread, http://forum.xda-developers.com/tmo...p-step-guides-rooting-t-mobile-lg-g5-t3388272 and then the instructions here to change the permissions but an still having problems. The only app root app I installed after rooting was an app to export google play music with track names intact.

What problems specifically are you having?
Did you install the safetynet helper app? What happens when you run it?
What root app did you install? Was it this one? http://forum.xda-developers.com/showthread.php?t=2620331 (play music exporter) aka https://www.david-schulte.de/en/play-music-exporter/
Looks like that app doesn't work in MM regardless, per the developer's page.

waylo said:
What problems specifically are you having?
Did you install the safetynet helper app? What happens when you run it?
What root app did you install? Was it this one? http://forum.xda-developers.com/showthread.php?t=2620331 (play music exporter) aka https://www.david-schulte.de/en/play-music-exporter/
Looks like that app doesn't work in MM regardless, per the developer's page.
Click to expand...
Click to collapse
Yes, that is the app. I noticed MM was not supported after I had it installed
I have installed and run the safetynet app and it shows it gets tripped on the CTS profile
---------- Post added at 02:03 PM ---------- Previous post was at 01:40 PM ----------
I just realized I also had Adguard installed. I have uninstalled it and turned off suppersu and restarted but the phone still does not pass the CTS profile check

Wondering if any of those apps made some changes to /system that were not completely reversed.
Doesn't look like that music app does any permanent changes anyway, rather just copies cache not normally accessible into another folder.
Can you check the permission profile of your /su/bin folder?
Briefly looking at the Adguard website I can't make out how its root version works exactly.
What other apps are listed under your SuperSU app list? You're not running xposed, right?

Apps listed in supersu are adb shell, root checker basic, and Titanium backup.
Titanium backup was installed after safetynet app test failed.
I'm not 100% sure what the permissions are but I followed your instructions above to change the permissions and it appeared to run correctly

eremeya said:
Apps listed in supersu are adb shell, root checker basic, and Titanium backup.
Titanium backup was installed after safetynet app test failed.
I'm not 100% sure what the permissions are but I followed your instructions above to change the permissions and it appeared to run correctly
Click to expand...
Click to collapse
SafetyNet still failing after the permissions change?

It was today. I can try changing them again tonight when I'm at my computer and report back.

I have confirmed that the folder permissions are set to 751

eremeya said:
I have confirmed that the folder permissions are set to 751
Click to expand...
Click to collapse
Well if we can't track down the actual changes made, and you're interested in getting Android pay to work, you could try reflashing the system partition.

It looks like from reports on other threads (Nexus mostly), that something has changed with the SafetyNet check. Phones that were working just fine yesterday now fail. Most likely something server-side was patched so now Android Pay will not work with systemless root.
Details updated as I find them.

For those interested in this topic, a pretty major development has occurred at this thread:
http://forum.xda-developers.com/android/software/mod-magisk-v1-universal-systemless-t3432382
Essentially, this is a brand new way to implement root systemless, which can be toggled via an app, without rebooting. This does allow the SafetyNet api to remain untripped. The steps involved include flashing back to stock kernel/system, flashing the application .zips, and flashing special SuperSU or SuperUser .zips. I have not done any of this yet as it is still very early.
There are some reports, unfortunately, such as this post:
http://forum.xda-developers.com/showpost.php?p=68045722&postcount=121
which reports that despite SafetyNet passing, Android Pay still does not work (user is on Nexus 6P).
I have read of no G5 users doing this yet, but there is a V10 user who has. Stay tuned.

I've been watching the Magisk threads for the past week and decided to take the plunge today. Many Nexus phones seem to have a lot of trouble with Android Pay, but other makes seem to do better. There were confirmations from LG G4 owners. As of this writing Magisk is on v3.
The install steps from the Magisk thread are this:
1. Reflash a stock boot.img to reset your systemless root
2. Flash Magisk.zip
3. Flash modified phh-superuser.zip (not the official one). Chainfire's SuperSU does not currently have as much support, but there is a modified supersu zip as well.
4. Boot and install phh's superuser app from the App store.
5. A 'magisk manager' app is installed via the flashed .zips. This allows you to turn off root for a set # of minutes, without rebooting.
Given the unique way the G5 is rooted, with automatic encryption, I figured it might not be so simple to install this if I wanted to keep my data without a full wipe. It quickly became much more complicated than what I wanted. Here's exactly what happened.
First, I made a full boot+system+data backup.
Then, these were my thoughts/concerns:
I have Adaway installed with the systemless addon zip and SuperSU installed. Magisk installation requests flashing back the stock boot.img. What would this do to the supersu install and Adaway?
The adaway systemless zip makes a script file which is kept in the /su/su.d/ folder. I removed this.
The SuperSU has a complete uninstall feature. As part of this uninstall process, it asks if you want to restore the boot.img (yes--this stock one is backed-up after the initial supersu.zip flash during our initial root/TOT process) and/or the recovery (no, don't do this, but it probably would not have done anything as there is no stock recovery backup). I thought this would accomplish our goal. It does warn you that you may have re-encrypting of the data partition if you go this route.
And unfortunately, after rebooting, it automatically and immediately encrypted the data partition.
Well shoot. Correct me if I'm wrong, but an encrypted data partition cannot be worked on. It booted just fine, but without root.
I started having some doubts at this time so I decided to try to restore back to my initial setup. Through TWRP, I wiped the data partition and flashed the no-verity.zip, to hopefully stop any re-encryption.
Then, after figuring out how to mount system properly (TWRP defaulted to mount system as r/o), I restored my nandroid backup in its entirety.
But upon reboot, it went immediately into bootloader mode. And it continued to do this after every battery pull and power on. I had never heard of this before! Finally, I realized I could still boot into TWRP. I flashed the 10Dcomplete.zip made by autoprime, restoring the boot and system partitions to stock. And then I flashed the magisk v3.zip and the modified phh-superuser zip.
It finally rebooted into Android, with data intact! Oddly, my unlock pattern had changed without my knowledge, but the backup PIN worked. I installed the market phh Superuser. Magisk is installed properly and it passes SafetyNet, and I can add cards to the app. I'll test out Android Pay next opportunity I have.
If I had to do it all again and wanted to keep data intact, this is what I would do.
1. Autoprime did make a 10D boot flashable zip. So this would restore the stock boot.img as intended. There are some files to clean up, such as data/su.img, but that can be dealt with later.
2. I do not know if just flashing the stock boot.img would result in re-encrypting. It probably would. So, immediately after flashing the boot.img in TWRP I would flash magisk and the phh-superuser.
Alternatively, they say you should not dirty flash for things this complex. So consider starting completely new from a 10Dcomplete flash with wiped data.

I've learned that Magisk will work fine with an encrypted data partition, so if you are set on having that, it won't be a problem.

waylo said:
I have a thread here discussing Android Pay while rooted on our G5s:
http://forum.xda-developers.com/tmob...le-g5-t3395036
I thought I was the only one who cared about this kind of stuff!
Which version Magisk did you install?
I just did this 2 days ago but haven't had the opportunity to test AP yet.
What rooted apps are you running? AdAway?
Click to expand...
Click to collapse
To answer your question... I'm using v3 with his v2 of his modified phh superuser.
As for rooted apps...yes AdAways still works perfectly....TB...my one time use of System App Remover etc...
I haven't been able to test Android util tomorrow....but SafetyNet did pass when Magisk was disabled and failed when enabled.
I'll report back tomorrow after I go buy my weekly chicken at my local Fresh Mart.

I'm using the same install as you.
I tried it this AM for the first time and it failed.
On the Magisk-AP thread, someone has posited that maybe the AP app caches any root inquires during that boot. So if you test out AP and it fails while the root is active, it will remember that failure until the next reboot.
That could explain how so many people are getting weird inconsistent results. I'm testing out that theory later today.

Bah, still doesn't work, even if done immediately after a reboot =(

Root access problems on Cyanogenmod 13

Hello to all (i have no idea if i am posting this in the right place sorry)
I have recently installed Cyanogenmod 13 on my Asus Zenfone 2 Laser/Selfie (1080p) (Asus-Z00T)
My phone works grate besides the fact that i have root access problems.
First i enabled developer options then enabled root (as now since Cyanogenmod 12 it is hidden) i installed busybox i grant it root access .So far so good nothing unusual i then install clean master then give it root access then when i try to use clean master to stop apps auto starting and i got an error no root access i then installed lucky patcher granted it root access no problem then when i tried patching a app to remove adds i got another root access error.
(I have had problems like this on Cyanogenmod 12)
Now with Cyanogenmod 11 if i get a little root bug i just go to super user app under system settings and delete the app access and then give it new root access again that solves the problem.
IT would seam that since CM12/CM13 there is no superuser app on board and no superuser settings either i have looked everywhere and i just can't find it.
I have the feeling that now root has become just a developer option it is not as good as on Cyanogenmod 11 but i could be wrong.
Could anyone help me please ?? is there a way to fix root access errors ???

The supersu type settings are in settings /privacy/privacy guard
Sent from my ASUS_Z00A using Tapatalk

Try re-rooting your device, in the worst case, flash stock rom, then flash cyanaogenmod and then root your device.
Hope this solves your problem.

Need help getting Viper/ARISE working on stock, rooted setup

I've spent way too long trying to get this working without any success.
If I flash a custom ROM (ie. Pure Nexus), I can flash the ARISE zip (ARISE+Deuteronomy+2.94+Modular+AROMA+Installer.zip) and it works perfectly. No driver issues, or anything.
When running stock, rooted, after flashing the above zip file, it appears to flash successfully, but when I open the app after rebooting, it always says that the drivers are missing and offers to install them. If I choose the option to install the drivers, it always fails.
I learned that if you're on stock, you have to flash a custom kernel before it'll actually flash (and auto install the apk), so I tried with franco and elemental kernels.
Does anyone know the steps I'm missing? I'm wondering if maybe it's because I need busybox, but I'm not sure where to install busybox (or the best method).
I know there has to be a way to get this working. I'm sure I'm missing something simple.
Thanks in advance!

eleazar123 said:
I've spent way too long trying to get this working without any success.
If I flash a custom ROM (ie. Pure Nexus), I can flash the ARISE zip (ARISE+Deuteronomy+2.94+Modular+AROMA+Installer.zip) and it works perfectly. No driver issues, or anything.
When running stock, rooted, after flashing the above zip file, it appears to flash successfully, but when I open the app after rebooting, it always says that the drivers are missing and offers to install them. If I choose the option to install the drivers, it always fails.
I learned that if you're on stock, you have to flash a custom kernel before it'll actually flash (and auto install the apk), so I tried with franco and elemental kernels.
Does anyone know the steps I'm missing? I'm wondering if maybe it's because I need busybox, but I'm not sure where to install busybox (or the best method).
I know there has to be a way to get this working. I'm sure I'm missing something simple.
Thanks in advance!
Click to expand...
Click to collapse
I think not only do you need Busybox (you should just be able to download this from the play store now you're rooted) you will also need a way of setting SELinux to permissive. Try The SELinux toggler.

rename/remove /vendor/etc/audio_effects.conf

grifforama said:
I think not only do you need Busybox (you should just be able to download this from the play store now you're rooted) you will also need a way of setting SELinux to permissive. Try The SELinux toggler.
Click to expand...
Click to collapse
Shawn haz root said:
rename/remove /vendor/etc/audio_effects.conf
Click to expand...
Click to collapse
Thank you both! I will try all of those solutions right now.
When I tried to install busybox via the play store installer to /system/xbin/, it says "It looks like the installation of BusyBox was not successful. Try installing to a different location, that may resolve the issue".
My understanding is that I need to put it in /system/xbin. Do you guys have any ideas? The busybox installer was granted root when I first opened it, so I know it has root access. :\

eleazar123 said:
Thank you both! I will try all of those solutions right now.
When I tried to install busybox via the play store installer to /system/xbin/, it says "It looks like the installation of BusyBox was not successful. Try installing to a different location, that may resolve the issue".
My understanding is that I need to put it in /system/xbin. Do you guys have any ideas? The busybox installer was granted root when I first opened it, so I know it has root access. :\
Click to expand...
Click to collapse
I'd be interested to hear how you get on.
I have Viper4Arise installed, Busybox installed, and it appears to be working (sometimes it just doesn't) but when it does, I don't hear any difference when I apply my convolver irs .

grifforama said:
I'd be interested to hear how you get on.
I have Viper4Arise installed, Busybox installed, and it appears to be working (sometimes it just doesn't) but when it does, I don't hear any difference when I apply my convolver irs .
Click to expand...
Click to collapse
When I was running custom roms, it worked perfectly and I could tell a major difference in the music.
How did you get busybox installed? I can't figure out why the play store installer is failing. It's also failing for my friend on his Pixel XL (also rooted)

eleazar123 said:
When I was running custom roms, it worked perfectly and I could tell a major difference in the music.
How did you get busybox installed? I can't figure out why the play store installer is failing. It's also failing for my friend on his Pixel XL (also rooted)
Click to expand...
Click to collapse
If you install an app called "root browser classic", the second you open it, it requests to install an add on which is busy box. Then close and open it again and it asks to update which takes you to the Google play store then installed the busy box app. Not exactly a conventional way but I just tried and it installed. Not sure if that will help you or not.
Root browser
https://play.google.com/store/apps/details?id=com.jrummyapps.rootbrowser.classic
Busy box
https://play.google.com/store/apps/details?id=com.jrummy.busybox.installer
I also installed this with no issues
https://play.google.com/store/apps/details?id=stericson.busybox

Shawn haz root said:
If you install an app called "root browser classic", the second you open it, it requests to install an add on which is busy box. Then close and open it again and it asks to update which takes you to the Google play store then installed the busy box app. Not exactly a conventional way but I just tried and it installed. Not sure if that will help you or not.
Root browser
https://play.google.com/store/apps/details?id=com.jrummyapps.rootbrowser.classic
Busy box
https://play.google.com/store/apps/details?id=com.jrummy.busybox.installer
I also installed this with no issues
https://play.google.com/store/apps/details?id=stericson.busybox
Click to expand...
Click to collapse
Thank you! That jrummy busy box installer worked perfectly the first time. I confirmed in the stericson version that busy box is really installed.
I went ahead and flashed the arise zip file, and it has an option to set SELinux to permissive. Unfortunately upon reboot, it was the same drivers not installed error
I'm now thinking my issue might be the audio_effect.conf file. I've tried Solid Explorer (my go to file explorer) and Root Browser that you linked above. Both explorers have been granted root, but neither can actually rename the file (or delete it). Jrummy's app just says operation denied, while solid explorer shows the file gone, but if you refresh, it's right back where it was. I'm struggling to find a way to mount system r/w in either app. Do you have any ideas? :\
I tried to find a tool to set SELinux to permissive and i found lots of kernel tuning apps, but none that actually allowed setting permissive. Even Franco's own app for his kernel doesn't have that option (he said it's something about trying to keep it more secure). Hopefully the arise zip is really setting it properly, it's just the audio_effects issue causing my problem.
Thanks again for your help, guys!