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
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
So i decided to root a couple days ago and when i went to update to 4.3 it gave me the "Custom" padlock. I care more about warranty than root at this point and will do whatever to get back to it. Dumb of me, i know. The only other way is triangle away but the boot loader hasn't been unlocked yet, has it?
Thanks.
My plan of attack is thus: reroot, triangle away, no wipe flash vrudmi1, accept ota.
In case anyone is wondering.
Once the knox counter gets tripped theres no resetting it.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
I concur...
Sent from my SCH-I545 using xda app-developers app
schimm1 said:
So i decided to root a couple days ago and when i went to update to 4.3 it gave me the "Custom" padlock. I care more about warranty than root at this point and will do whatever to get back to it. Dumb of me, i know. The only other way is triangle away but the boot loader hasn't been unlocked yet, has it?
Thanks.
Click to expand...
Click to collapse
The "Custom" flag that shows up when you boot is not related to the Knox Warranty Void counter. You haven't done anything to trip the Knox counter so you should be fine. If you want to check it, start your phone in downloader mode and check the value there.
I'd re-root, then flash the no-wipe. That should clear the "custom" flag. If not, use Triangle Away. Then, once you're rooted on MI1, update to MJ7.
k1mu said:
The "Custom" flag that shows up when you boot is not related to the Knox Warranty Void counter. You haven't done anything to trip the Knox counter so you should be fine. If you want to check it, start your phone in downloader mode and check the value there.
I'd re-root, then flash the no-wipe. That should clear the "custom" flag. If not, use Triangle Away. Then, once you're rooted on MI1, update to MJ7.
Click to expand...
Click to collapse
Still at 0x0, thank deity
rerooted and custom/padlock disappeared. flashed no wipe, uninstalled all my root apps, going to accept OTA.
Update: OTA took as if i had never deviated from samsung's creepily obsessive grasp. Hopefully this thread helps someone in the future.
OTA took as if i had never deviated from samsung's creepily obsessive grasp. Hopefully this thread helps someone in the future.
schimm1 said:
rerooted and custom/padlock disappeared. flashed no wipe, uninstalled all my root apps, going to accept OTA.
Update: OTA took as if i had never deviated from samsung's creepily obsessive grasp. Hopefully this thread helps someone in the future.
Click to expand...
Click to collapse
can you explain that a little more? i am hoping to do the same
HwaA18 said:
can you explain that a little more? i am hoping to do the same
Click to expand...
Click to collapse
I rooted a little while ago and tried to update to MJ7 but it did a flash check (i think) and gave me the padlock and wouldn't update. So i re-rooted the root de la vega for MI7 (which got rid of the "custom" padlock,) then flashed the MI7 no-wipe factory and removed root, essentially giving me a "clean/untouched" stock samsung. I deleted all of my root apps (supersu, rootchecker, barnacle) just in case the update checks for them and tried the OTA update. It worked.
Link to No-Wipe stock image
Hopefully that helps. I'm not great at this stuff, just a script kiddie who follows guides.
So I finally rooted MJ7. Everything went well and SuperSu worked upon opening. Today SuperSu updated and a little while after I opened it, the binaries had to be updated. It then asked me if I wanted to disable Knox and I clicked "yes" to avoid any complications. Again, everything worked fine. I heard this happened to other people too and their Knox Void was still 0x0. I didn't check mine yet, but I just want to know if this really effects anything. Also is there a way to re-enable if for some odd reason if I needed to? Thanks.
tredonkulous said:
So I finally rooted MJ7. Everything went well and SuperSu worked upon opening. Today SuperSu updated and a little while after I opened it, the binaries had to be updated. It then asked me if I wanted to disable Knox and I clicked "yes" to avoid any complications. Again, everything worked fine. I heard this happened to other people too and their Knox Void was still 0x0. I didn't check mine yet, but I just want to know if this really effects anything. Also is there a way to re-enable if for some odd reason if I needed to? Thanks.
Click to expand...
Click to collapse
There's a whole lot of things under the "KNOX" umbrella. The SEAndroid policy enforcement and reporting is what SuperSU is disabling.
The "Knox Warranty Void" flag is the way that the phone records attempts to flash a custom kernel or bootloader. The only thing that those two things have in common is they're called "Knox".
k1mu said:
There's a whole lot of things under the "KNOX" umbrella. The SEAndroid policy enforcement and reporting is what SuperSU is disabling.
The "Knox Warranty Void" flag is the way that the phone records attempts to flash a custom kernel or bootloader. The only thing that those two things have in common is they're called "Knox".
Click to expand...
Click to collapse
Ok, thanks for clearing it up!
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.
.
So I have been looking and reading I remember back on 4.2.2 kingo was able to root without tripping knox I am now finding it that king root is the only option as of 4.4.2 my question is will this trip knox and if so will it lock down my phone. I saw some other users report that king root tripped knox and they were totally locked out I am not trying to brick or flash the rom I had some of my own tricks but from what I have found they have been patched and trip knox now so my question is does anyone know if its safe to use king root on i527ucubnj1 thanks for anyones reply.
Edit: Should mention this is the ATT version.
Does anyone have any idea I see people are viewing the thread but no replies. Trying to avoid bricking the phone and I dont want to jump on this without knowing more because its a hit and miss on all the other posts.
Well I couldnt get an answer from anyone so i took the leep. Don't let the phone screen timeout just keep it awake and working you can change the settings or just keep tapping an area of the app while its rooting. It does say on the program its not rootable but if you root it the root will work as for tripping knox after installing a status checker because im to lazy to check it by rebooting my counter is still 0x0 so we are still good. As for rebooting it I did a reboot right after rooting it I did not get a custom lock as I use to before so I am not sure about that however I did get an "android updating" message could just be random. This was running the 4.4.2 version with all and most current samsung policy apps installed updated all the apps last night.
So with that all being said seems the root held through a reboot and seems to be running fine. I will post and update if any changes happen.
Update: While i dont know if its related I opened kinguser which informed me about knox being active rather than answering cancel or deny I just held home and closed out all apps then I did a second reboot. After the second reboot I now have a custom unlock icon at boot. After a third reboot it seems to be holding root with a custom unlock icon. Shall keep people posted with more updates as I go on if anything else changes as I said above.