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.
Related
Hey Guys,
I own a Samsung Galaxy S4 from Verizon and have followed the guide on how to root it posted on the forums. For a while things were good. My phone booted up with the correct loading screen and my device detected that I was on an official kernel. Now for reasons I'm not sure of, my phone is saying that the kernel is custom and the lock icon has returned when I restart or cold boot my phone. I'm not running custom firm ware, I'm running a stock Verizion kernel. I tried to delete SuperUser, but it isn't installed. My binaries for SuperSU are up-to-date. I'm still rooted, but I would like to get rid of the unlock icon when I boot up and I would like to get the system to recognize that this is an official kernel.
Also ES File Explorer is unable to mount r/w privilages on my phone in order to delete busybox and su so that I could try to re-root the phone again. Any help would be appreciated, thanks!!
Theres no way so far to get rid of it. Mine actually goes back and for between custom and official all the time. Maybe when the bootloader gets unlocked it will do away with it, but until then it does no harm. So if you want to root, that's the price we pay.
sneekerpimpz said:
Theres no way so far to get rid of it. Mine actually goes back and for between custom and official all the time. Maybe when the bootloader gets unlocked it will do away with it, but until then it does no harm. So if you want to root, that's the price we pay.
Click to expand...
Click to collapse
Most of the time mine is gone. Maybe once a week I might see it.
sneekerpimpz said:
Theres no way so far to get rid of it. Mine actually goes back and for between custom and official all the time. Maybe when the bootloader gets unlocked it will do away with it, but until then it does no harm. So if you want to root, that's the price we pay.
Click to expand...
Click to collapse
So I managed to get rid of it. I'm not sure if it's permanent, but here's what I did. I couldn't delete the stuff in the root directory (and this was before I found solid explorer which has better root access programming than es does). So I did a factory reset and found that that worked for a while, but then I noticed that downloading Triangle Away seemed to be causing the problem because the lock icon returned after I installed it and gave it root access. So I deleted it and chose the 'unroot' option from the list of options in supersu. Then I re-rooted the phone using the guide. Now the lock icon hasn't returned, and the device status under the about phone menu says that my firmware is the official one. Another thing I noticed is that I'm running an older version of busybox (version 1.17.1 I think, as installed by motochopper).
Again I'm not sure what I did differently, or changed as a result of my method, but it seems to have worked. Perhaps someone with more development knowledge can let me know what's happened for my own personal information.
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
I'm looking for some help/advice. I did search and didn't find anything on this although I would think it would have been covered before so my apologies if I missed it and it's already been answered.
I'm currently running Stang5Litre 5.0 OC1 V2 which I installed with Flashfire and I'm having a lot of issues with Good For Enterprise and it's root check. I can get it to work with Xposed as long as I stay on an old version of Good, but I've had two accidental upgrades that triggered a compliance failure and it's a long process with my work to get a new pin to get it going again. Using the detach from market in Titanium doesn't stick. I'm also interested in using Android Pay and can't get that to work at all. So I'm now considering getting rid of root. There isn't that much I do anymore that truly requires a rooted phone other than I really like being able to get rid of all the bloat and being able to freeze and unfreeze in Titanimum.
So my question is what options do I have? Can i fully unroot a debloated ROM or would I need to flash a stock unrooted OC1 ROM? Also, is the fact that my Samsung boot screen shows as unlocked an issue? I know that simply removing SuperSU isn't enough. I don't want to do anything that is going to prevent me from changing my mind down the road and going back to a rooted ROM which I know means not installing anything after OC1.
Any help would be appreciated.
Thanks
After doing a little more research on Good, I think I have no choice but to flash a completely stock unrooted ROM. Apparently it checks too many things to simply remove Root. So what are my options for going back to stock and still keeping the ability to root down the road if I choose?
Thanks