I have found the root directions that was posted on this site for rooting my s5 with 5.1.1. But I have 2 questions I was hoping someone could help me out with here. Please forgive me if these seem like stupid questions, as I have only rooted one phone before some years ago.
1 There is much discussion about rooting the s5 will "trip Knox". What exactly does this mean if you do root your phone? Will you have constant error messages popping up on device about Knox? Can you simply uninstall Knox after root?
2 I currently do not have the Tmobile hotspot feature activated on my s5, but I do plan on adding it on later. If I root now, will I still be able to add the Tmobile hotspot feature on my s5?
Much gratitude and appreciation ahead of time for any and all info.
Thanks,
Dave
Hi nissandave,
1) Knox, in terms of the s5, has two meanings. One in the Android OS, and one deep in the firmware of the device. You'll find in most roms that the Android Knox application has been removed, which most people prefer. "Tripping Knox" refers to modifying the firmware of the phone, where the counter in download mode goes from 0x0 to 0x1, voiding your "knox warranty." Knox is tripped when you flash when you flash a custom recovery. Root AND know can be achieved though ODIN in some cases, but you'll be stuck on a stock rooted rom (no CM, bliss, etc) Tripping this switch has no serious repercussions in terms of your phone being fully operational, but there have been VERY few reports of Samsung not performing warranty exchanges for devices with a tripped knox counter. The counter is also impossible to reset, and once tripped, will always be tripped, no matter what rom, BL, tar, or md5 you install.
2) Yes, and as a matter of fact, some roms have a workaround version installed to where you don't have to activate it through tmobile. It just works. Twisted v7 in the G900T dev sections is once of these roms.
From what I I have found and read about twisted v7, you must be running 5.0. How do I get my phone back to 5.0?
Related
Edited this original post here, it was 3:30am when I typed the original.. Anyway - anyone know if rooting can cause any type of instability on it's own? Without installing custom mods, roms, etc - does the act of rooting potentially cause things to not work as intended from the carrier? (my friend had an S3, rooted, and allshare stopped working - he was only rooted). I know there is some type of exploit involved in gaining root access, so that's why I ask. It's not a critique on rooting, I want to do it myself.
Disregard this second post
Sent from my SM-N900P using xda app-developers app
Anyone? I know it says "at your own risk", but i am curious - are there inherent known issues that can crop up just from rooting alone, maybe from just the method of gaining root through the system?
sjr19 said:
Anyone? I know it says "at your own risk", but i am curious - are there inherent known issues that can crop up just from rooting alone, maybe from just the method of gaining root through the system?
Click to expand...
Click to collapse
There may be a few things that don't function properly as a result from rooting. But it's 99.99999% of the time not an actual issue with the files on the phone. Nothing should be modified except for root access.
One of the ones for sure would be ota updates. I read someone else was having issues with one of the Samsung apps for streaming video to devices. These issues and others like them were caused by the system status being changed to custom and can be solved quite easily by setting the system status back to official with wanam xposed. With root and the status set to official your phone should preform exactly as stock in every way except you'll have root.
But be aware if you accept the ota while rooted you may lose root. Would have to re root or use supersu pro to maintain root during the ota.
From my Note 3
Rooting will give you many benefits. Some of these include unauthorized apk installation, developer mode, custom firmware/modem improvements and fixes for some less functional stock features. This list could go on and on...
Most carriers frown upon customers rooting their devices for a few reasons; liability, damage control and profit above all.
When your device is rooted, custum, unofficial, and/or the Samsung KNOX binary counter has been tripped, Sprint/Samsung will consider your warranty void. Basically you will need to return the device to official stock and unrooted if you need to have your phone serviced.
Sent from my Rooted, TWRP'd & JellyBombed SM-N900P using XDA...
Kompster said:
Rooting will give you many benefits. Some of these include unauthorized apk installation, developer mode, custom firmware/modem improvements and fixes for some less functional stock features. This list could go on and on...
Most carriers frown upon customers rooting their devices for a few reasons; liability, damage control and profit above all.
When your device is rooted, custum, unofficial, and/or the Samsung KNOX binary counter has been tripped, Sprint/Samsung will consider your warranty void. Basically you will need to return the device to official stock and unrooted if you need to have your phone serviced.
Sent from my Rooted, TWRP'd & JellyBombed SM-N900P using XDA...
Click to expand...
Click to collapse
Fully agree.
However just to say it again because I see the question everywhere.
YOU CAN NOT RESET KNOX TO 0X0 AFTER IT HAS BEEN TRIPPED TO 0X1.
There is a root method that doesn't flip the knox flag though if that is a concern.
http://forum.xda-developers.com/showthread.php?t=2484095
YOU CAN NOT RESET KNOX TO 0X0 AFTER IT HAS BEEN TRIPPED TO 0X1.
From my Note 3 using Tapatalk
I've never had issues when just rooting a device granted I've only had the s3 and note 2 and now the note 3. But with the note 3 if you use the auto root method it will trip knox and that can't be undone and will void the warranty. The root de la vega method will give you just root access if it's what your looking for with out messing up knox.
Thanks guys. Yeah, like I said my buddy's allshare cast stopped when he rooted, so now he's reluctant to do that again. I know about not accepting OTAs. I think I am going to wait to see what other root methods may crop up, and also see if anyone finds away to reverse any accidental knox trips. Right now, i'm just enjoying the damn thing lol! Thanks all.
sjr19 said:
Thanks guys. Yeah, like I said my buddy's allshare cast stopped when he rooted, so now he's reluctant to do that again. I know about not accepting OTAs. I think I am going to wait to see what other root methods may crop up, and also see if anyone finds away to reverse any accidental knox trips. Right now, i'm just enjoying the damn thing lol! Thanks all.
Click to expand...
Click to collapse
If your knox is already flipped no need to wait for a new method. Just cm auto root. Use xposed to set system status official. And optionally get supersu pro and select the keep root ota option or don't update to any ota .the files will be in the development section to flash after its released. Like this and you should be 100% functional and stock/rooted.
I'm currently rooted with the vega root .status official. And everything appears to work for me including allshare.
There is always a risk with changing anything. But in my opinion the benefits out way the risks. And all of this is easily undone by just flashing back to a stock system.
From my Note 3 using Tapatalk
rooting
It is hard to get rooting because they limit the resource.
kelvinzhou905 said:
It is hard to get rooting because they limit the resource.
Click to expand...
Click to collapse
its not hard. all the resources you need are here!
http://forum.xda-developers.com/show....php?t=2484095
I had long been using a rooted phone before I got the S5, but things seem a little different now. I held off on rooting the S5 because I wanted to be sure that I was going to keep it long term before I did. So yesterday I did some research on here and elsewhere and ended up rooting via towelroot and getting SuperSU installed without flashing. Now I just need to figure out a few things and was hoping to get some help understanding what comes next.
I've been reading about concerns over tripping "Knox" holding folks back from flashing custom recover and ROMs. I'm not a touchwiz fan but I can tolerate it. If there were no cost, I'd probably just install Xposed or something like that but is this Knox thing important? What am I giving up if I flash a custom recovery?
SuperSU "disabled" Knox when I started it. What functions of Knox are disabled? Can I flash recovery and roms without incident now that it is disabled?
Almost as soon as I got done rooting and installing SuperSU last night, I got a notification from samsung saying that "an update is required to access samsung services". Was that triggered by the rooting of the phone? Can I install that update without loosing root access?
Last question: Now that I have root, what do I need to do to keep it? Will it be rolled back by any OTA update, and if so, what must I do to prevent that?
Any help would be greatly appreciated.
RobsterCraw said:
SuperSU "disabled" Knox when I started it. What functions of Knox are disabled? Can I flash recovery and roms without incident now that it is disabled?
Click to expand...
Click to collapse
You wouldn't have had to search or read very far in the forum to find answers to all of your questions. These get asked over and over, pretty much every day.
If you are contemplating a custom recovery, then read a thread about e.g. TWRP to learn about it's advantages. As just one of many advantages, it's the only way that you can make a proper, 100% backup.
Installing a custom recovery will increment Knox because Knox has not been removed from the bootloader. However most people don't obsess about the Knox flag. The only significant downside to the flag is that it might invalidate a minority of warranty claims.
Block e.g. rename or freeze the OTA updater to avoid losing root. An update will generally break it and there is no assurance that you will always be able to reroot. SuperSU Pro has a feature that attempts to restore root after an update.
.
I have Verizon Samsung Galaxy S4 with 4.4.2. It has been rooted since I bought it at the end of May 2013. I re rooted many times to keep up with software updates. I used Kies 3 to flash back to default 4.4.2. I mean a complete nuke. I then flashed with towelroot and rebooted to see if the custom broken padlock was present at boot. The padlock was not present and no padlock icon present yay!!!. I installed SuperSu by chainfire and disabled knox as per SuperSu suggestion. I rebooted to check if custom flag had been tripped. The broken padlock was there god dammit.
SuperSu seems to have triggered knox or tripped the counter.
How do I maintain root and have the boot screen display everything is normal.
AND how do I get settings to display official instead of custom.
Please help as XDA and Google searches are not providing ansers.
You won't find a lot of info because most people would tell you if you don't want the custom padlock don't use custom software. You can use "Triangle Away" or the option in the Security Hacks section of the Wanam Xposed module.
Thanks
joshm.1219 said:
You won't find a lot of info because most people would tell you if you don't want the custom padlock don't use custom software. You can use "Triangle Away" or the option in the Security Hacks section of the Wanam Xposed module.
Click to expand...
Click to collapse
Well. I looked at triangle away. It messes with the hardware startup code and I don't want to do that. So ill be fine for now. My phone is out of warranty so it's not a big deal and I have insurance on my pbone. I was only bothered because I like pretty visuals.
purplenate26 said:
I have Verizon Samsung Galaxy S4 with 4.4.2. It has been rooted since I bought it at the end of May 2013. I re rooted many times to keep up with software updates. I used Kies 3 to flash back to default 4.4.2. I mean a complete nuke. I then flashed with towelroot and rebooted to see if the custom broken padlock was present at boot. The padlock was not present and no padlock icon present yay!!!. I installed SuperSu by chainfire and disabled knox as per SuperSu suggestion. I rebooted to check if custom flag had been tripped. The broken padlock was there god dammit.
SuperSu seems to have triggered knox or tripped the counter.
How do I maintain root and have the boot screen display everything is normal.
AND how do I get settings to display official instead of custom.
Please help as XDA and Google searches are not providing ansers.
Click to expand...
Click to collapse
Well, perhaps you could start with the sticky threads here?
One: Assuming that "triped" is just a typo for "tripped": No, that's wrong. First, the phrase "tripped Knox" is usually how people refer to something that sets the "Knox Warranty Void" flag. Installing SuperSU will not set the Warranty Void flag.
You're apparently seeing the "Custom" flag show up at boot, and claiming that's evidence that something "tripped Knox". That's wrong. That's been discussed in the sticky threads here and in the General forum. The "Custom" status means that your phone is no longer running stock.
If you care about the "Custom" flag, flash stock. It'll get cleared after a while. Or, run one of the several techniques to clear it (Triangle Away, Xposed framework, etc.)
The easy way to clear that flag is to flash a stock ROM. If you want to run non-stock, you'll need to live with it, or use one of the work-arounds. I use TA to clear Custom.
something i kinda want to add to this, SuperSU will actively disable knox upon installing it. There is absolutely no way you can trip Knox just with SuperSU. From what i can tell, Knox only gets tripped when you modify the kernel or boot stuff (recovery, etc.) and by that point you'd end up bricking a phone if you didnt have the MDK bootloader
Clear syscope with titanium backup
Sent from my GT-I9505G using XDA Free mobile app
Hi all, thanks in advance for any help on this. I have a few general s5 rooting questions. I'm an experienced 'rooter' having rooted and installed custom ROMs on many previous devices.
- I've ready that the s5 has an 'e-fuse' that gets 'blown' when the device is rooted. this then voids the warranty and prevents things like Fort Knox from running. I get that, and understand the risks. But, I've also read that the lollipop update will remove root. These two things seem to contradict themselves.
- on other devices I've rooted, I've then installed a custom ROM. I don't plan to do this with my s5. I haven't been able to find much written on the experience of a rooted s5 running the samsung stock ROM/firmware. I'd like to use something like xposed to change parts of the ROM (like the white background that's so pervasive in the s5 flavor of lollipop). I'm curious if anyone is running lollipop on an s5 that is rooted but running stock samsung firmware and xposed.
thanks!
Rooting won't trip Knox. Installing a custom recovery will. If you have insurance on your device tripping Knox doesn't matter, your covered anyway.
thanks!
stncldtex said:
Rooting won't trip Knox. Installing a custom recovery will. If you have insurance on your device tripping Knox doesn't matter, your covered anyway.
Click to expand...
Click to collapse
very interesting, thanks! can I run xposed/titanium backup pro/other root things without a custom recovery? all I'm really interested in is modifying Samsung-dictated things (like apps that can't be frozen and colors/elements that can't be changed) + making complete backups to the SD card. If I recall from my previous experiences, a custom recovery was the way to create a nandroid backup...but I think perhaps titanium backup pro can do that from the android front-end (with root).
I assume that I should wait to root until the tmobile s5 gets lollipop? i.e. that update will kill root?
scwtech said:
very interesting, thanks! can I run xposed/titanium backup pro/other root things without a custom recovery? all I'm really interested in is modifying Samsung-dictated things (like apps that can't be frozen and colors/elements that can't be changed) + making complete backups to the SD card. If I recall from my previous experiences, a custom recovery was the way to create a nandroid backup...but I think perhaps titanium backup pro can do that from the android front-end (with root).
I assume that I should wait to root until the tmobile s5 gets lollipop? i.e. that update will kill root?
Click to expand...
Click to collapse
Right now there are threads that show you how to get rooted lollipop on your phone without tripping Knox which basically involves downgrading the kernel so you can root with towelroot, then using mobile Odin to flash lollipop and inject root in the process. It seems people are able to do this without issues. To this point, I do not think that anyone has found an exploit for lollipop.
The problem you will run into is that Xposed still does not run on lollipop so you cannot do much in the way of customization. Most of the G900F ROMs can run on the G900T so you might poke around in those threads to pick up more info.
Hope this helps a little.
If I or anybody on XDA helps you, please hit the "Thanks" button.
scwtech said:
very interesting, thanks! can I run xposed/titanium backup pro/other root things without a custom recovery? all I'm really interested in is modifying Samsung-dictated things (like apps that can't be frozen and colors/elements that can't be changed) + making complete backups to the SD card. If I recall from my previous experiences, a custom recovery was the way to create a nandroid backup...but I think perhaps titanium backup pro can do that from the android front-end (with root).
I assume that I should wait to root until the tmobile s5 gets lollipop? i.e. that update will kill root?
Click to expand...
Click to collapse
System runtime is different. Art for lollipop compared to dalvik.. So it's not compatible as of now
Sent from my SM-G900T using XDA Free mobile app
This does not work with lollipop
---------- Post added at 07:30 PM ---------- Previous post was at 07:25 PM ----------
gspears said:
Right now there are threads that show you how to get rooted lollipop on your phone without tripping Knox which basically involves downgrading the kernel so you can root with towelroot, then using mobile Odin to flash lollipop and inject root in the process. It seems people are able to do this without issues. To this point, I do not think that anyone has found an exploit for lollipop.
The problem you will run into is that Xposed still does not run on lollipop so you cannot do much in the way of customization. Most of the G900F ROMs can run on the G900T so you might poke around in those threads to pick up more info.
Hope this helps a little.
If I or anybody on XDA helps you, please hit the "Thanks" button.
Click to expand...
Click to collapse
are you sure ? I have been able to downgrade. towelroot and flash lollipop and it boots but supersu does not work properly. root apps ask permission and supersu grants permission but the apps dont actually work
stncldtex said:
Rooting won't trip Knox. Installing a custom recovery will. If you have insurance on your device tripping Knox doesn't matter, your covered anyway.
Click to expand...
Click to collapse
I don;t know where you heard that rooting won;'t trip Knox but I beleive you are wrong about that At least I know that Flashing cf auto root - flashing recovery or flashing custom roms all trip knox. If your phone can use Towel Root - that rooting process does not trip knox - but I am not sure if Towel Root works on Lollipop or on the S5 for that matter. (I may be wrong about Towel Root - I have never used that process so I can't say for sure)
Flashing a new rom via ODIN does not trip knox. It is just like getting an UPDATE from the carrier OTA.
BUT, If you are already rooted - you already have tripped knox - flashing Lollipop will remove root - but it will not do anything to change the fact that you tripped knox on your phone already.
As far as I know everything I have said is correct - based on what I have learned thru reading - flashing and using several different samsung phones -
finally, I see a lot of people paranoid as hell about tripping knox - and I can tell you without any hesitation that I have never had a problem getting service or replacements after rooting a phone - there have been a few times back when I first started flashing roms that I had issues with my phone and I took it in and got a replacement without any issue - once I broke my screen and got a replacement then too - both times I was rooted, running custom recovery - etc.
I hope this helps you
I used towel root on NE6. You can downgrade to that via Odin and not trip knox. As far as flashing 5.0 and losing root. I came from Alliance flash Twisted lollipop and kept root. Then used Odin to flash the bootloader and modem for OB1.
Do you still have Knox 0?
How did you flash lollipop?
Going to cut it as short as I can, and I'll probably sound like a noob and annoying at the same time. Can I root my Galaxy S5 T-Mobile 4.4.2 G900TUVU1CNK2 without triggering knox? I don't want to touch anything (no rom or loader or anything) - I just want it to be rooted so I have some access.
If that can't be done, can I root and yet still send back to T-Mobile as a warranty replacement without them charging me?
If I were to root, can I still use the OTA upgrade from Lollipop once it comes out or does it have to be done a different way?
You can root without tripping Knox. Follow @galaxyuser88 here
http://forum.xda-developers.com/showthread.php?t=2909352
If you upgrade, OTA to 5.0, you will lose root privileges and have to re-root