Database Users

[Q] Problems with root access / KNOX

Hello,
So I rooted, or I at least think I did, my I9505. I have installed cwm und the superSU-Update.zip.
Then when I am normally running my device and want to use apps with root access, KNOX denies it. When I start SuperSU, the following message appears: "There is no SuperSU-file installed and SuperSU can't install it. This is a problem. If you switched to Android 4.3, you have to manually root your device"
I have Android 4.3.
So how do I get my root access running?
Thanks in advance for your help,
Best regards, Simon

- I dont think u are rooted by that method
- I dont know if u void ur warranty still. You have here a method for root ur phone without void the warranty: HERE
- For stop knox (when ur phone will be rooted) u only have to install one app (root explorer for ex.) and delete this files:
KNOX in System/App folder:
ContainerAgent.apk
KNOXAgent.apk
ContainerEventsRelayManager.apk
KLMSAgent.apk
KnoxAttestationAgent.apk
KNOXStore.apk
KNOXStub.apk
SPDClient.apk
KNOX in DATA/DATA folder:
com.sec.knox.containeragent
com.sec.knox.eventsmanager
com.sec.enterprise.knox.attestation
com.sec.knox.app.container
com.sec.knox.seandroid
com.sec.knox.store
com.samsung.klmsagent
More KNOX remains:
Folder = Data/clipboard/knox
Folder = system/containers
Folder = system/etc/secure_storage/com.sec.knox.store
Lib = libknoxdrawglfunction.so
File = system/tima_measurement_info ---- TIMA is a Trust-Zone of KNOX

Thanks so far. I now flashed the superSU again and now I have root access, somewhat strange because I am sure I installed the superSU before. I have root access with es file Explorer, but I cannot delete any system apk :/

cH33zBurGer said:
Thanks so far. I now flashed the superSU again and now I have root access, somewhat strange because I am sure I installed the superSU before. I have root access with es file Explorer, but I cannot delete any system apk :/
Click to expand...
Click to collapse
Install Root Explorer app -> HERE and if u are rooted u will can

Does it make a difference? I activated root access for the es file Explorer

cH33zBurGer said:
Does it make a difference? I activated root access for the es file Explorer
Click to expand...
Click to collapse
Install Root Checker for see if u are rooted. Good luck :highfive:

Actually I followed every step, except rooting without voiding the warranty. I took your hint that my device probably doesn't have root access und flashed the superSU again, that gave me root (now verified by root checker). Then I tried deleting the files you told me, but that I could not do. I asked if es file Explorer is ok too, because I don't want to spend 4€ when the es explorer works too and there is just another problem why I cannot delete files from my phone storage.
I am glad for every tip you give me

cH33zBurGer said:
Actually I followed every step, except rooting without voiding the warranty. I took your hint that my device probably doesn't have root access und flashed the superSU again, that gave me root (now verified by root checker). Then I tried deleting the files you told me, but that I could not do. I asked if es file Explorer is ok too, because I don't want to spend 4€ when the es explorer works too and there is just another problem why I cannot delete files from my phone storage.
I am glad for every tip you give me
Click to expand...
Click to collapse
Es file Explorer is ok too but maybe u have to give root perms in superSU manually. I use Root Explorer normally coz it takes own root perms :highfive:

I checked again and it has root, but I discovered it is a read only system. I really had that different in mind with my old rooted phone, I thought it worked back then...
Then every Problem is solved for me, thanks alot Joku

Titanium backup not working on 6.0.1

I can't delete any system apps with it anymore, does anybody else have the same problem or even a fix for it?

Working fine on 6.01 for me, Did you try uninstalling and reinstalling it?

I just updated to 6.0.1 myself, rooted using superSU 2.61. I too cannot delete system apps using titanium. I tried to uninstalled and reinstall the app (via playstore) but it didn't help.
I also tried to do the same via the root explorer option in ES file explorer and it didn't work. I tried to toggle the root explorer option in ES, but after I turned it off I couldn't turn it on again. Root checker does say that I have root, and other root apps e.g. adaway, xprivacy still work.
Any help and suggestion is most welcome!

case-sensitive said:
I just updated to 6.0.1 myself, rooted using superSU 2.61. I too cannot delete system apps using titanium. I tried to uninstalled and reinstall the app (via playstore) but it didn't help.
I also tried to do the same via the root explorer option in ES file explorer and it didn't work. I tried to toggle the root explorer option in ES, but after I turned it off I couldn't turn it on again. Root checker does say that I have root, and other root apps e.g. adaway, xprivacy still work.
Any help and suggestion is most welcome!
Click to expand...
Click to collapse
hey guys, "system less root"

That would modify system... Just freeze the apps.

geoff5093 said:
That would modify system... Just freeze the apps.
Click to expand...
Click to collapse
Some people still want to recover the space.
With systemless root you will need to modify the system in TWRP to get titanium and ES working correctly.
It's as simple as going into TWRP and mounting the system R/W.
You then need to open the terminal in the following places:
/system/bin and execute "touch su"
/system/xbin and execute "touch su"
This will create zero byte files for SuperSu to come along and swap/link to on boot so that ES and TiBu can ask for root and get it.
They will then operate as you expect.; with the caveat that you are on your own when you start tinkering and may break something.

tech_head said:
Some people still want to recover the space.
With systemless root you will need to modify the system in TWRP to get titanium and ES working correctly.
It's as simple as going into TWRP and mounting the system R/W.
You then need to open the terminal in the following places:
/system/bin and execute "touch su"
/system/xbin and execute "touch su"
This will create zero byte files for SuperSu to come along and swap/link to on boot so that ES and TiBu can ask for root and get it.
They will then operate as you expect.; with the caveat that you are on your own when you start tinkering and may break something.
Click to expand...
Click to collapse
Pretty sure you lose Android Pay with this method though, just FYI if you care about that.

But if you are running Xposed you broke it anyway. There is a way to get it working.
You will need to remove the empty su files you just created to be able to add cards.
You will need to use a Xposed module to hide modifications to the system so that the device check comes back clean.
It's a pain, but if you want Xposed, TiBu, ES and Android Pay, that is the price.
Sent from my Nexus 6P using Tapatalk

I usually use this app:
https://play.google.com/store/apps/details?id=com.jumobile.manager.systemapp
I'm not on 6.0.1 at the moment so I can't test if it works. Anyone wanna test it out and report back?

WizeGuyDezignz said:
I usually use this app:
https://play.google.com/store/apps/details?id=com.jumobile.manager.systemapp
I'm not on 6.0.1 at the moment so I can't test if it works. Anyone wanna test it out and report back?
Click to expand...
Click to collapse
Doesn't work. Apps restore themselves.

Deleting /su/xbin_bind on SuperSu 2.62

I recently re-rooted my phone to install 6.0.1, and installed SuperSu 2.62 thinking it was systemless root. Android pay didn't work, so I re-downloaded Xposed. After reading that you need to delete the /su/xbin_bind folder to get Android Pay to work, I uninstalled Xposed (flashing the uninstaller) as well as Emoji Switcher (forums say it modifies /system) and set out to try it.
However, when I try to delete /su/xbin_bind, it says failed/cannot be deleted. I've tried with both ES File Explorer and Root Explorer. According to SuperSu, the only things left with root permissions are Nova Prime Launcher, Tasker, and AdAway. Any reason I can't seem to delete this file when everyone else can? I also tried temporary disabling SuperSu, but no go.
Edit: I am a moron. I didn't have root permissions for ES File Explorer, so I couldn't delete the folder. Added that and deleted no problem. Leaving my idiocy here in case anyone else runs into this problem.

So to clarify, if we want android pay to work we can't use xposed?
Sent from my Nexus 6P using Tapatalk

Wehdota said:
I recently re-rooted my phone to install 6.0.1, and installed SuperSu 2.62 thinking it was systemless root. Android pay didn't work, so I re-downloaded Xposed. After reading that you need to delete the /su/xbin_bind folder to get Android Pay to work, I uninstalled Xposed (flashing the uninstaller) as well as Emoji Switcher (forums say it modifies /system) and set out to try it.
However, when I try to delete /su/xbin_bind, it says failed/cannot be deleted. I've tried with both ES File Explorer and Root Explorer. According to SuperSu, the only things left with root permissions are Nova Prime Launcher, Tasker, and AdAway. Any reason I can't seem to delete this file when everyone else can? I also tried temporary disabling SuperSu, but no go.
Edit: I am a moron. I didn't have root permissions for ES File Explorer, so I couldn't delete the folder. Added that and deleted no problem. Leaving my idiocy here in case anyone else runs into this problem.
Click to expand...
Click to collapse
sweet, i flashed 2.62 thinking it was systemless root too and android pay stopped working. came here looking for a solution, deleted /su/xbin_bind and android pay is working again!

Giving Root Access?
How do you go about giving ES File Explorer root access? Usually that is an automatic question asked.

how important or whats the purpose of /su/xbin_bind ??
if its included on the SU install, and we delete it... im trying to gauge if we are damaging something since it was meant to be there....

chaco81 said:
how important or whats the purpose of /su/xbin_bind ??
if its included on the SU install, and we delete it... im trying to gauge if we are damaging something since it was meant to be there....
Click to expand...
Click to collapse
I'd like to know this as well

leamdav said:
How do you go about giving ES File Explorer root access? Usually that is an automatic question asked.
Click to expand...
Click to collapse
Some apps don't ask for root by default, and only do so when you tell them you want to enable the features that require root. ES File Explorer is one such app, and to enable root features you have to open the side menu and toggle the option.
IMO this is the way all apps should be, as I don't always need the root features of every app, as it adds a security risk. I like how BoldBeast Call Recorder does this for example.

bkkzak said:
I'd like to know this as well
Click to expand...
Click to collapse
chaco81 said:
how important or whats the purpose of /su/xbin_bind ??
if its included on the SU install, and we delete it... im trying to gauge if we are damaging something since it was meant to be there....
Click to expand...
Click to collapse
It's a compatability mode that was automatically enabled for a while in older SuperSu.zips to allow developer's apps to work until they update their app to work with systemless root. It is now disabled by defult in newer SuperSu.zips, with the user having to explicitly enable it for its use.
Some apps that requires this to work (becuse they haven't updated their app to work with systemless yet) include:
- Secure Settings
- Es File Explorer.
Etc.Etc.
Hope this helps clarify things for you

Looking for a Root Text Editor that works with SuperSU

I have Root Explorer and EX file Explorer but both don't work with SuperSU 2.66 to edit the build prop. Does anyone know of a text editor that gives you root privileges and works with SuperSU 2.66
Thanks in Advance!

rsalas187 said:
I have Root Explorer and EX file Explorer but both don't work with SuperSU 2.66 to edit the build prop. Does anyone know of a text editor that gives you root privileges and works with SuperSU 2.66
Thanks in Advance!
Click to expand...
Click to collapse
Works for me with root explorer and SuperSU 2.66. You could use adb instead to pull, edit and push back. Did you allow twrp to make system writeable when you first used it? That can cause issues if you didn't.

Buildprop cannot write changes

Lineage 17 and last version Magisk installed.
Buildprop last version installed.
Buildprop shows SuperUser rights
I want the entry then
ro.product.system.brand
change from samsung to htc
Why? To get the Samsung Wear app working for Watch 3 ...
But I got an error.
Report from BuildProp:
Please ensure the app has root ...
But they are there and are displayed under properties ...
What am I doing wrong?

Problem solved with a workaround.
Finding: You don't need a BuildProp ...
After installing MagisK you have root rights.
As a file manager you take the TotalCommander and give it root rights.
You can then access the build.prop file in the system directory and change it with the integrated text editor.
Just stupid:
My SamsungWear app still does not start.
But this is another story...