Database Users

[Q] 0x0x KNOX and Towelroot success....but SU binaries issue.

Who knew it would be that simple? Towelroot has rooted my Note 3, I'm finally back with Titaniuam Backup Pro and Knox is 0x0!
Amazing.
However I've installed CF's SuperSU and it fails to update the binaries.
I've frozen KNOX in Titanium and rebooted but they still won't update.
Do I even need to update them?
Also, if I try to install CWM will that trip KNOX?

jonboyuk said:
Who knew it would be that simple? Towelroot has rooted my Note 3, I'm finally back with Titaniuam Backup Pro and Knox is 0x0!
Amazing.
However I've installed CF's SuperSU and it fails to update the binaries.
I've frozen KNOX in Titanium and rebooted but they still won't update.
Do I even need to update them?
Also, if I try to install CWM will that trip KNOX?
Click to expand...
Click to collapse
Download http://download.chainfire.eu/448/SuperSU/UPDATE-SuperSU-v1.99r5.zip . Don't flash it. Unzip it. Then go to /common folder and install superuser.apk. Run SuperSU from App Drawer, and let binary to update. Now you have it working. And don't worry about disabling KNOX. Just disable it.
By flashing CWM you will trip knox.

alexpowermetal said:
Download http://download.chainfire.eu/448/SuperSU/UPDATE-SuperSU-v1.99r5.zip . Don't flash it. Unzip it. Then go to /common folder and install superuser.apk. Run SuperSU from App Drawer, and let binary to update. Now you have it working. And don't worry about disabling KNOX. Just disable it.
By flashing CWM you will trip knox.
Click to expand...
Click to collapse
Fantastic. thank you Alex. That worked perfectly. As you're in the know I'll ask you another question (or two)!
Because I don't want to trip knox I won't install CWM. As such I can't make a nandroid backup. I want to install the xposed framework and Wanam modules...but it strongly recommends a backup. Is it risky for me to do this?
Any idea what happens when an OTA update is release by Samsung?

jonboyuk said:
Fantastic. thank you Alex. That worked perfectly. As you're in the know I'll ask you another question (or two)!
Because I don't want to trip knox I won't install CWM. As such I can't make a nandroid backup. I want to install the xposed framework and Wanam modules...but it strongly recommends a backup. Is it risky for me to do this?
Any idea what happens when an OTA update is release by Samsung?
Click to expand...
Click to collapse
I took the yolo approach and installed xposed and wanam with no problems. As you say don't want to risk loosing warranty but knox is still fine and now I have a customisable phone.
No idea about ota samsung update sorry.

pjtb said:
I took the yolo approach and installed xposed and wanam with no problems. As you say don't want to risk loosing warranty but knox is still fine and now I have a customisable phone.
No idea about ota samsung update sorry.
Click to expand...
Click to collapse
Hahaha, I too have just taken the YOLO approach (as much as I hate that phrase!). Thanks mate!

jonboyuk said:
Hahaha, I too have just taken the YOLO approach (as much as I hate that phrase!). Thanks mate!
Click to expand...
Click to collapse
Actually you can make nandroid backup without costume recovery. Just use Online Nandroid Backup. It makes nandroid backup in CWM or TWRP formats.
And then you can use Nandroid Manager to restore your backup. Although I still can't figure it out on how to restore a backup if you soft brick you phone.

alexpowermetal said:
Actually you can make nandroid backup without costume recovery. Just use Online Nandroid Backup. It makes nandroid backup in CWM or TWRP formats.
And then you can use Nandroid Manager to restore your backup. Although I still can't figure it out on how to restore a backup if you soft brick you phone.
Click to expand...
Click to collapse
Cheers, not heard of that before. I'll have to look into it!

alexpowermetal said:
Download http://download.chainfire.eu/448/SuperSU/UPDATE-SuperSU-v1.99r5.zip . Don't flash it. Unzip it. Then go to /common folder and install superuser.apk. Run SuperSU from App Drawer, and let binary to update. Now you have it working. And don't worry about disabling KNOX. Just disable it.
By flashing CWM you will trip knox.
Click to expand...
Click to collapse
Not quite sure what to do here. I've ODINed twice and just tried this approach, but I cannot get the binaries to update successfully. I keep getting the failure. Any ideas?

danjng said:
Not quite sure what to do here. I've ODINed twice and just tried this approach, but I cannot get the binaries to update successfully. I keep getting the failure. Any ideas?
Click to expand...
Click to collapse
Now you can install SuperSU from play store as it was updated and now it should update binaries without a problem. Install SuperSU, open it, press "update binaries", use "normal" method (not CWM/TWRP), when it will ask you to disable knox, press "disabled knox" and then reboot.

I'm having a similar issue that's pretty frustrating. I root my phone and install supersu, asks to disable knox and everything works great until about a day after, I try to open Supersu and it says I need to update binaries but it will not update. So I have to uninstall supersu, root again then install Supersu again! Right now it's working fine but I'm scared to open Supersu in fear that it will happen all over again. It's been a pain! I even tried flashing the supersu zip through Safestrap to see if it helps but it did the same thing. Is anyone having a similar issue or can anyone help with this?

alexpowermetal said:
Download http://download.chainfire.eu/448/SuperSU/UPDATE-SuperSU-v1.99r5.zip . Don't flash it. Unzip it. Then go to /common folder and install superuser.apk. Run SuperSU from App Drawer, and let binary to update. Now you have it working. And don't worry about disabling KNOX. Just disable it.
By flashing CWM you will trip knox.
Click to expand...
Click to collapse
Isn't the point of using towelroot to prevent tripping KNOX? When trying to update my SuperSU binaries it asks me to disable KNOX, won't this trip it?

toews said:
Isn't the point of using towelroot to prevent tripping KNOX? When trying to update my SuperSU binaries it asks me to disable KNOX, won't this trip it?
Click to expand...
Click to collapse
As far as I understand, it disables software part of knox, so it (knox) wont prevent you to update binaries. Anyway it won't trip knox.

Binary issue
fsolares said:
I'm having a similar issue that's pretty frustrating. I root my phone and install supersu, asks to disable knox and everything works great until about a day after, I try to open Supersu and it says I need to update binaries but it will not update. So I have to uninstall supersu, root again then install Supersu again! Right now it's working fine but I'm scared to open Supersu in fear that it will happen all over again. It's been a pain! I even tried flashing the supersu zip through Safestrap to see if it helps but it did the same thing. Is anyone having a similar issue or can anyone help with this?
Click to expand...
Click to collapse
I have the same problem with binary issues on the towelroot method. It works at first but after a reboot it says "Update binary files" So i do that and then it says "Failed" I have the verizon Note 3 on 4.4.2. I found a temp fix for this when having issues with binary update. You don't have to re-root your phone.
1. Save the apk super su to your phone.
2. After having problems with binary then uninstall the supersu app from your phone
3. Install the supersu apk using "ES File Explorer" Then load the app it'll still say failed.
4. Reboot the phone and open up Supersu and you won't get the binary issue
I know its annoying work around but its what i have figured out and it works.

Guys, can you help with 2 questions please?
I have a I9505 with 4.4.2 branded rom (ZTO) with towel root (know still 0x0) and disable OTA updates, I can't find a perfect custom rom (always a feature not working, missing or the interface it's a mess/colorfull), now I just want the stock unbranded rom.
1 - What is the safest way to flash the stock rom without trip knox?
2- After that, can I enable back OTA updates with root?
Thanks!

fsolares said:
I'm having a similar issue that's pretty frustrating. I root my phone and install supersu, asks to disable knox and everything works great until about a day after, I try to open Supersu and it says I need to update binaries but it will not update. So I have to uninstall supersu, root again then install Supersu again! Right now it's working fine but I'm scared to open Supersu in fear that it will happen all over again. It's been a pain! I even tried flashing the supersu zip through Safestrap to see if it helps but it did the same thing. Is anyone having a similar issue or can anyone help with this?
Click to expand...
Click to collapse
Why are you re-rooting?
---------- Post added at 03:01 PM ---------- Previous post was at 02:57 PM ----------
jashton23 said:
I have the same problem with binary issues on the towelroot method. It works at first but after a reboot it says "Update binary files" So i do that and then it says "Failed" I have the verizon Note 3 on 4.4.2. I found a temp fix for this when having issues with binary update. You don't have to re-root your phone.
1. Save the apk super su to your phone.
2. After having problems with binary then uninstall the supersu app from your phone
3. Install the supersu apk using "ES File Explorer" Then load the app it'll still say failed.
4. Reboot the phone and open up Supersu and you won't get the binary issue
I know its annoying work around but its what i have figured out and it works.
Click to expand...
Click to collapse
Same phone and carrier. Thanks for this. :good:

alexpowermetal said:
Download http://download.chainfire.eu/448/SuperSU/UPDATE-SuperSU-v1.99r5.zip . Don't flash it. Unzip it. Then go to /common folder and install superuser.apk. Run SuperSU from App Drawer, and let binary to update. Now you have it working. And don't worry about disabling KNOX. Just disable it.
By flashing CWM you will trip knox.
Click to expand...
Click to collapse
I downloaded SuperSU from the link your provided, copied just the superuser.apk from /common folder to my Note 3 and then install.
Run SuperUser, which asked to disable KNOX (I clicked OK). KNOX disabled.
However, there is no prompt for the binary update. Am I doing anything wrong?

you could also flash the zip with mobile odin pro (available in play store)
*flies away*
Sent from my SM-N9005 using XDA Premium 4 mobile app

Killberty said:
you could also flash the zip with mobile odin pro (available in play store)
*flies away*
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Wouldn't this require TWRP? I don't have that, since installing TWRP will trip KNOX.

Mod Edit quote removed
and i just told u another method man...
i am not tired of it, i enjoy helping people, giving back support i once recieved myself when i was a noob
but if i post something, you should read it, and maybe you are even smart enough to type in "mobile odin pro" in that play store instead of just commenting - if you had done that, you'd have seen that no custom recovery is required for flashing
Sent from my SM-N9005 using XDA Premium 4 mobile app

Mod Edit
Thread cleaned
If you want to help users , great.
If you do not want to help users , that is also fine.
But there is no need to insult each other.
Please respect the XDA RULES
Thank you
malybru
Forum Moderator

Root galaxy s4 on lollipop

Is there a root procedure for the galaxy s4 that's on the newest lollipop update ? I was able to root with kingroot but read its not safe to use kingroot and try install a custom rom ?

dpmeeks said:
Is there a root procedure for the galaxy s4 that's on the newest lollipop update ? I was able to root with kingroot but read its not safe to use kingroot and try install a custom rom ?
Click to expand...
Click to collapse
CF-autoroot or flash TWRP then in TWRP flash SuperSU

Kingroot and SuperSU_me method works also... Watch the entire process in 2 parts... https://www.youtube.com/watch?v=IWnYFDQ1Vio

K94U said:
Kingroot and SuperSU_me method works also... Watch the entire process in 2 parts... https://www.youtube.com/watch?v=IWnYFDQ1Vio
Click to expand...
Click to collapse
Have you lost root since? I've read a lot about people loosing root after a few hours to a couple of days. Any other issues, like random crashes / freezes / reboots?

Ezintn said:
Have you lost root since? I've read a lot about people loosing root after a few hours to a couple of days. Any other issues, like random crashes / freezes / reboots?
Click to expand...
Click to collapse
That's why flashing TWRP and SuperSU is the safest/easiest way to root, it's about as straightforward as it gets

mattzeller said:
That's why flashing TWRP and SuperSU is the safest/easiest way to root, it's about as straightforward as it gets
Click to expand...
Click to collapse
Wasn't aware I could flash a custom recovery on a stock unrooted phone. I don't use the s4, that's why both of the ones I own aren't rooted already, my personal phones are often rooted before I even get home from the store! I need root and su without tripping knox or making any significant changes to the current set-up on either phone. I would prefer the recovery was stock on at least one of 'em. So how should I go about this? One is a tri band and the other isn't. The dual band one needs to be as stealth as possible. Losing root really won't matter as long as the system permissions remain as is prior to losing root.

Ezintn said:
Wasn't aware I could flash a custom recovery on a stock unrooted phone. I don't use the s4, that's why both of the ones I own aren't rooted already, my personal phones are often rooted before I even get home from the store! I need root and su without tripping knox or making any significant changes to the current set-up on either phone. I would prefer the recovery was stock on at least one of 'em. So how should I go about this? One is a tri band and the other isn't. The dual band one needs to be as stealth as possible. Losing root really won't matter as long as the system permissions remain as is prior to losing root.
Click to expand...
Click to collapse
Flashing a custom recovery is going to trip knox. Why do you care about knox? Triband or not flashing TWRP and SuperSU is the same. If you lose root and have things that require root to operate, you will lose the function of those things, unless it's a one off type of thing

mattzeller said:
Flashing a custom recovery is going to trip knox. Why do you care about knox? Triband or not flashing TWRP and SuperSU is the same. If you lose root and have things that require root to operate, you will lose the function of those things, unless it's a one off type of thing[/QU
It's imperative that root is stealth. Just need to give one app already running su permissions. On one device knox is monitored, that's why I care. I wouldn't care on my s5, but I never tripped it anyway - rooted with modified stock recovery, flashed MOAR, flashed TWRP. Been using MAOR and TWRP since each was first released. Been rooted on my personal devices since 3 days after the Hero was released. I've just never rooted the s4 or "stealth rooted" any device. That's why Kingroot / SSM looks promising. Any help would be appreciated.
Click to expand...
Click to collapse

Lost root after 1-2 days

I recently got a Galaxy S5 (SM-G900T with LMY47X.G900TUVS1FOJ4).
I grabbed chainfire autoroot and flashed it with the Odin 3.10.6 that came with the CF file. It successfully rooted the phone. I installed Titanium Backup and restored all the stuff I wanted from my old device.
I've been using the device for 1-2 days now and lost root. I opened TB and it says I'm no longer rooted. I confirmed this by downloading a root checker and it also says I'm not rooted.
According to TB, I had BusyBox for root. There was no application icon nor was it in my list of installed applications. When I used chainfire's autoroot on my S4, it installed a super user program that I could open from my app list.
I would really like to continue using Titanium Backup. Does anyone know how I can gain root access again? I already messed it up once by reflashing the autoroot. This caused an infinite bootloop and I eventually got out of it by doing a factory reset. I've returned my S4 to T-Mobile and don't want to soft brick my phone again.
Thanks.

Anyone have any suggestions of how I can reroot my phone?

If you successfully used cf autoroot then that's not the issue.....My money is on a deleted or disabled or un-updated super user app.... this is what will give you (or prevent you from having) root access to your device.
http://i.imgur.com/rVnFwJM.jpg

Using supersu v2.65 works well for me
whynoteel said:
Anyone have any suggestions of how I can reroot my phone?
Click to expand...
Click to collapse
Some days ago I get same problem ( lost root ) because i use supersu v2.67 on cm13 for sg s5 : g900f
therefore, after installed cfroot you can use twrp 3.0.0.0 as custom recovery
Then , Download. & update supersu to v2.65 by using twrp recovery ZIP version
Thanks i'm waiting for a reply

A normal or a systemless root (S5 Neo G903F)

I want to root my phone, and I haven't been doing that kind of stuff since S3 so I'm a bit lost.
I've read the thread about root by Chainfire. From what I understand, this can be used for a phone with Android 6.01, right? On the other hand, I've read about a systemless root. Can this be done with my phone model and this Android version?
My main concern is the warranty. I know the first solution will trip the knox. What about the latter? Would this be better in my situation?
(And a minor question: my phone has found a software update. Should I do it before or after rooting my phone, or does it matter at all?)

for me and it can be different for other users, i have a preference for system root.

if you just want a stable root on your phone, and don't care about passing google security checks (safetynet) you should choose chainfires supersu. just download the latest zip (assuming you already have a custom recovery) and flash it. supersu will "decide" which rooting method (system/systemless) fits to your phone.
The more advanced method is magisk-root which gives you no option for system-root. the whole magisk concept is based on systemless changes to the system partition. it gives you the opportunity to pass safetynet and to add systemless modules. the downside is, that the usability (due to it's complexity) can sometimes be a bit tricky (trial and error )
hope this helped for your decision..
BTW: afaik is knox triggered with both methods

drei.liter.milch said:
if you just want a stable root on your phone, and don't care about passing google security checks (safetynet) you should choose chainfires supersu. just download the latest zip (assuming you already have a custom recovery) and flash it. supersu will "decide" which rooting method (system/systemless) fits to your phone.
The more advanced method is magisk-root which gives you no option for system-root. the whole magisk concept is based on systemless changes to the system partition. it gives you the opportunity to pass safetynet and to add systemless modules. the downside is, that the usability (due to it's complexity) can sometimes be a bit tricky (trial and error )
hope this helped for your decision..
BTW: afaik is knox triggered with both methods
Click to expand...
Click to collapse
To add something: if supersu installs in systemless mode you can bypass it.
Flash the supersu zip
Reboot
Go to supersu and select full root wipe
Click no when asked to restore boot image
Your phone will automatically reboot don't let it go to system, go to recovery
With twrp go to terminal and enter this command without quotes "echo SYSTEMLESS=false>>/data/.supersu
Reinstall supersu zip
Reboot
You yave system root :good:
Sent from my Samsung Galaxy S5 Neo using XDA Labs

Thanks for your replies! I do not care about safetynet. I do care about warranty but from what I see, there is no way around this.
Would you update phone's software first?

Joanka said:
Thanks for your replies! I do not care about safetynet. I do care about warranty but from what I see, there is no way around this.
Would you update phone's software first?
Click to expand...
Click to collapse
Yeah update your system first and if you need warranty just full wipe root and select yes for biit image restore from supersu let us know if it works for you and don't hesitate to ask if you need anything
Sent from my Samsung Galaxy S5 Neo using XDA Labs

Thanks for your help! I'm updating the sofware right now and I will proceed with the root.
"just full wipe root and select yes for biit image restore from supersu" -I think I'm not sure what it means. Would you explain it a little bit more?

Joanka said:
Thanks for your help! I'm updating the sofware right now and I will proceed with the root.
"just full wipe root and select yes for biit image restore from supersu" -I think I'm not sure what it means. Would you explain it a little bit more?
Click to expand...
Click to collapse
Yes, click full unroot and click yes for boot image restore but no for recovery restore
Sent from my Samsung Galaxy S5 Neo using XDA Labs

I have mine (S5 Neo G903W) rooted and as far as I can tell if you want your warranty you can unroot it anytime
The phone provider however doesn't state anything about rooting or whatnot and I am not a type of person who does stupid stuff that needs a warranty anyway lol

For warranty they can check knox status, if is tripped usually is void

Can't Root My galaxy s7 edge android 7.0 since 1 month...help

Hey guys,
For the first time which i got this phone i was able to root it using cf-auto root... after a month i decided to unroot my device and clear some space cuz everything works bad. i did full unroot using super su app then full reset my phone. after that i tried to re-root my phone using the same cf-auto root it gives me dm verifcation failed i taught that its because my phone security then i did flashed my phone by its correct firmware download from sammobile, after that i got my phone back with official status but right now i can't root my phone. till this moment i did googled my issue but didn't found any solution.
i tried rooting using kingo root (PC & phone) method, cf auto root but still i am not able to root my phone idk what is the problem. any expert here to help me out ? i would be sooo glad. and thanks alot for this site, waiting for help please.:crying:

directx3 said:
Hey guys,
For the first time which i got this phone i was able to root it using cf-auto root... after a month i decided to unroot my device and clear some space cuz everything works bad. i did full unroot using super su app then full reset my phone. after that i tried to re-root my phone using the same cf-auto root it gives me dm verifcation failed i taught that its because my phone security then i did flashed my phone by its correct firmware download from sammobile, after that i got my phone back with official status but right now i can't root my phone. till this moment i did googled my issue but didn't found any solution.
i tried rooting using kingo root (PC & phone) method, cf auto root but still i am not able to root my phone idk what is the problem. any expert here to help me out ? i would be sooo glad. and thanks alot for this site, waiting for help please.:crying:
Click to expand...
Click to collapse
anyone help ?

S7 edge I do root via the SuperSU flashable zip file via a custom recovery. Other methods don't seem to work well with S7 on nougat because the user data partition needs to be reformatted in custom recovery (TWRP usually) in advance when you want to root the phone.
You'll need to backup the phone before hand and set it up from its initial state after rooting it.

benjamen50 said:
S7 edge I do root via the SuperSU flashable zip file via a custom recovery. Other methods don't seem to work well with S7 on nougat because the user data partition needs to be reformatted in custom recovery (TWRP usually) in advance when you want to root the phone.
You'll need to backup the phone before hand and set it up from its initial state after rooting it.
Click to expand...
Click to collapse
can u please help me on how to root via superSU flashable zip ? and will I lose all my data by this method ?
thanks,

Do not use SuperSu to root S7 as its not compatible and only meant to be used on older phones. It will not work on Android 8.