I was under the impression this was impossible, rooting without tripping Knox. However, I saw another member say this in another thread:
"You don't trip Knox as long as you leave system untouched, i think (i did not check download mode yet).
I installed TWRP via ODIN and did NOT "swipe to the right" in TWRP. Why should i anyway? Then i installed Magisk for systemless root.
Everything that needs Knox works, stock system partition is untouched, Knox is not tripped according to "Phone Info+" for Samsung.
I want to use it that way as long the phone gets official security updates to maintain warranty."
Would this work or is it BS? Thanks in advance.
When you flash TWRP which is an unsigned firmware, it will immediately trip Knox, regardless you modify the system or not. By installing TWRP, you are already modifying the firmware.
Just in short bull****. You are changing recovery and that is one of the checkpoints of Knox it sees a different hash, value, or missing a file and that triggers it.
tothehawks said:
I was under the impression this was impossible, rooting without tripping Knox. However, I saw another member say this in another thread:
"You don't trip Knox as long as you leave system untouched, i think (i did not check download mode yet).
I installed TWRP via ODIN and did NOT "swipe to the right" in TWRP. Why should i anyway? Then i installed Magisk for systemless root.
Everything that needs Knox works, stock system partition is untouched, Knox is not tripped according to "Phone Info+" for Samsung.
I want to use it that way as long the phone gets official security updates to maintain warranty."
Would this work or is it BS? Thanks in advance.
Click to expand...
Click to collapse
I don't know too much about how it works, but maybe it is VMOS?
Swarai said:
I don't know too much about how it works, but maybe it is VMOS?
Click to expand...
Click to collapse
lol hes almost certainly tripped knox.. magisk actually sets the warranty bit to 0x0 (this is only visual) to trick apps that check it into thinking device is not unlocked so it can pass safetynet n such apps that detect root
Related
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
Samsung I9505 Galaxy S4 - OS v4.4.2 | Downgrading & SD-Card Restrictions & 4.4 vs 4.3
Hey guys,
Just got this phone in immaculate condition from a friend. As it has been updated from OS 4.2 to 4.4, I now have restricted SD-Card access.
Before I start using the device, is there:
- Any way to overcome the SD-Card restrictions?
- Any way to down-grade (reliably) to 4.3.x?
I will root the device once everything is up and running (or before, should you recommend it).
Thank you very much guys!
Flip.
Root the device, download SD Card Fix from the Play Store, then run it. The app will modify platform.xml and enable full access.
Thanks mate. Appreciate the response.
I'll use KingoRoot again to root it. Then install SuperSU and BusyBox.
So is downgrading not an option? or just too risky?
OS 5 doesn't have full App support yet, so that's not really an option... I'll wait for OS 5.1
You don't even need Kingroot. Just flash CF-Autoroot through Odin to root and install SuperSU.
Downgrading may be possible. However, it's more likely the radios (cellular and WiFi) will not work. If you want Android 5.x you probably should look into the custom ROMs in I9505 Original Android Development rather than staying on Touchwiz.
Samsung Knox + SuperUser on SGS4 i9505 OS v4.4.2 Root
Samsung KNOX is preventing SuperSU and KingoUser (either) from installing. Neither of them appear to be "sticking".
When I open Knox, it says it is initialising, then closes. I cannot access any of the settings to disable and remove (and backup settings) Knox and its components.???
I've googled and there are just topics of people with the same problem and no answers to the problems!
The only answers say to perform actions that require root \ elevated actions (when you cannot elevate access without a SuperUser app installed!!!)...
Here are some screen shots. I appreciate any suggestions from you guys!
Thank you.
p.s. Hmm some Root functions are working. i.e. those that don't require SU!
Screen Shots: http://imgur.com/a/Qbxeb
Flash SuperSU through recovery. The first time you run SuperSU after flashing, you should get the option to disable Knox. Let SuperSU disable Knox, then reboot. On my device, trying to disable Knox the first time caused SuperSU to hang, so I hard rebooted the device and went back into SuperSU. I got the prompt a second time and this time I successfully disabled Knox.
When I hold down Vol Down I get this info and no options:
ODIN MODE
PRODUCT NAME: GT-I9505
CURRENT BINARY: CUSTOM
SYSTEM STATE: CUSTOM
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x1
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
eMMC BURST MODE: enabled
Click to expand...
Click to collapse
Message: Downloading..... Do not turn off target !!
Wtf? That doesn't even make sense!! Target? lol
This is word for word, character for character, and exact case.
So how do I get in to the good ol' menu with half a dozen options as my two HTC's and Samsung have??
Thank you!
Since I haven't followed this thread for a little while, let's make sure we're on the same page.
1. You flashed CF-Autoroot using Odin to root the S4.
2. SuperSU successfully removed Knox from the equation.
2. You then installed a custom recovery (TWRP recommended) using Odin.
3. You now want to flash a custom ROM through the recovery?
If the answer to 3 is "yes", hold down power for about ten seconds to get out of download mode. Then press volume up, home, and power to boot into the recovery. If the answer is anything else, then start over with the first item and go down from there. Some confusion may be generated thanks to my previous post, where it mentions installing SuperSU through recovery. Installing SuperSU through recovery is only possible if a custom recovery has been installed previously. For that, I apologize.
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
Hello everyone. I want to know, if I unlock my bootloader with TWRP then root with Magisk manager, then do I lose my next Official OTG update? I'm using Stock Samsung Galaxy S8 Oreo. TIA.
najmulbappy said:
Hello everyone. I want to know, if I unlock my bootloader with TWRP then root with Magisk manager, then do I lose my next Official OTG update? I'm using Stock Samsung Galaxy S8 Oreo. TIA.
Click to expand...
Click to collapse
Yep. Your Knox get busted and you won't be able to get another official OTA update..
You can still upgrade though, by flashing it using Odin, but I wouldn't recommend using that every time since it wipes your data.
StardustGeass said:
Yep. Your Knox get busted and you won't be able to get another official OTA update..
You can still upgrade though, by flashing it using Odin, but I wouldn't recommend using that every time since it wipes your data.
Click to expand...
Click to collapse
I heard that Magick is not same as SuperSU. It won't make any change in system and partition. It is systemless root process so if I unlock just my bootloader and root with Magick why I won't be able to get another official OTA update!
najmulbappy said:
I heard that Magick is not same as SuperSU. It won't make any change in system and partition. It is systemless root process so if I unlock just my bootloader and root with Magick why I won't be able to get another official OTA update!
Click to expand...
Click to collapse
The Knox system got busted not because of magisk, but because you're unlocking your bootloader and installing TWRP.
Yes, magisk does offer systemless root, and it ables you to pass safetynet check that is needed to turn on features like Android pay and some bank apps.. But, Samsung pay, and several Samsung apps that relies on Knox is busted once the Knox is tripped.
StardustGeass said:
The Knox system got busted not because of magisk, but because you're unlocking your bootloader and installing TWRP.
Yes, magisk does offer systemless root, and it ables you to pass safetynet check that is needed to turn on features like Android pay and some bank apps.. But, Samsung pay, and several Samsung apps that relies on Knox is busted once the Knox is tripped.
Click to expand...
Click to collapse
Thank you so much for nice explanation
Hi
I have a few questions about rooting, before I actually take this step.
In the past I rooted my S6 when I owned the S8.
I have never paid attention to the following points.
Is KNOX triggered after just installing TWRP?
If that is the case then the end message is.
If KNOX is not triggered, I have another question.
After I have installed TWRP I want to make a full backup and then root the device.
If I later want to undo the root and then use the backup. Is KNOX then in the old state again?
Thanks for answering!
Greetz Jeffarson
jeffarson said:
Hi
I have a few questions about rooting, before I actually take this step.
In the past I rooted my S6 when I owned the S8.
I have never paid attention to the following points.
Is KNOX triggered after just installing TWRP?
If that is the case then the end message is.
If KNOX is not triggered, I have another question.
After I have installed TWRP I want to make a full backup and then root the device.
If I later want to undo the root and then use the backup. Is KNOX then in the old state again?
Thanks for answering!
Greetz Jeffarson
Click to expand...
Click to collapse
Flashing anything that is not officially signed by Samsung will trip your Knox.
So flashing TWRP alone will trip Knox.
There is currently no fix for a tripped Knox. So restoring from a backup or flashing stock firmware will not fix this.