Hi,
I have been with AT&T for a long time. AT&T locks boot loader so there were limited options in rooting.
My understanding is that T-Mobile does not lock the boot loader. So the easiest way to root is to install TWRP using Odin and then use TWRP to flash SuperSU.apk. Is this correct? Does it trip KNOX?
Once installed, is there a way to uninstall it and revert back to full stock?
Thanks
redhonker said:
Hi,
I have been with AT&T for a long time. AT&T locks boot loader so there were limited options in rooting.
My understanding is that T-Mobile does not lock the boot loader. So the easiest way to root is to install TWRP using Odin and then use TWRP to flash SuperSU.apk. Is this correct? Does it trip KNOX?
Once installed, is there a way to uninstall it and revert back to full stock?
Thanks
Click to expand...
Click to collapse
Same AT&T situation here. Yes you can root with twrp and supersu zip. It does trip Knox. If you factory reset and flash a stock Odin firmware that should revert to full stock
Hmm, tripping KNOX would need void warranty right? Is there an alternative to root? Thanks
redhonker said:
Hmm, tripping KNOX would need void warranty right? Is there an alternative to root? Thanks
Click to expand...
Click to collapse
I've successfully brought in a device with a tripped Knox flag for warranty. I said Kies caused the problem (the word "lie" has such a negative connotation, but this was patently not true) and they were completely fine with that explanation, in fact they were tripping over themselves to make sure they could fix it for me. I guess that's my long-winded way of saying a tripped Knox flag doesn't prevent you from taking advantage of your warranty. Besides, I could swear I remember reading an article recently saying Samsung will now honor warranties even on devices where the Knox flag is tripped.
TLDR: A tripped Knox flag is no longer the black mark of death that it used to be
Related
I have rooted and installed a custom rom on my GS4 and it still says official. Is this normal?
I expected that after bricking and flashing stock and rerooting and everything I must have tripped the flash counter.
I don't really care as I don't plan on needing the warranty, I'm just surprised. I even previously had the custom unlock boot screen before bricking the phone.
Am I just looking in the wrong place?
DanGerousDroid said:
I have rooted and installed a custom rom on my GS4 and it still says official. Is this normal?
I expected that after bricking and flashing stock and rerooting and everything I must have tripped the flash counter.
I don't really care as I don't plan on needing the warranty, I'm just surprised. I even previously had the custom unlock boot screen before bricking the phone.
Am I just looking in the wrong place?
Click to expand...
Click to collapse
Flash counter will only register non Samsung images which we cannot flash successfully with a locked boot loader. Unless you are unlucky enough to accidently use Odin to install cwm or push a rom, them a factory restore via Odin should for all intents be undetectable as previously rooted. There might be something on a hidden partition I am unaware of but I have heard nothing yet.
Sent from my Galaxy S4
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 new to rooting devices. If I root my phone and don't flash a custom rom, would that still make the flash counter turn and still void my warranty? I don't want custom roms but there are some apps I need to be rooted to use.
If u will root your phone will lose warranty. ..
s4shoaib4u said:
If u will root your phone will lose warranty. ..
Click to expand...
Click to collapse
can you un-root it and still have warranty or is this not possible?
williamguile said:
I'm new to rooting devices. If I root my phone and don't flash a custom rom, would that still make the flash counter turn and still void my warranty? I don't want custom roms but there are some apps I need to be rooted to use.
Click to expand...
Click to collapse
Ok, first what version of Kikat are you running? If you upgraded to 4.4.4 you are out of luck for now. If you are still on 4.4.2 NC5, you can use Towel root. This will give you root access, and will NOT trip KNOX 0x0 !!! However the minute you install a custom recovery like TWRP or CWM that will trip KNOX and void your warranty. REMEMBER Sprint will warranty your device with the KNOX warranty counter tripped 0x1 as long as you unroot the device before you take it in or sent it back to Sprint !!! If the device is hard bricked, there is no way to tell it was rooted and they automatically replace the phone. With rooted access and no recovery you can Debloat the device and run rooted apps. Enjoy !!!
jimzweb1 said:
Ok, first what version of Kikat are you running? If you upgraded to 4.4.4 you are out of luck for now. If you are still on 4.4.2 NC5, you can use Towel root. This will give you root access, and will NOT trip KNOX 0x0 !!! However the minute you install a custom recovery like TWRP or CWM that will trip KNOX and void your warranty. REMEMBER Sprint will warranty your device with the KNOX warranty counter tripped 0x1 as long as you unroot the device before you take it in or sent it back to Sprint !!! If the device is hard bricked, there is no way to tell it was rooted and they automatically replace the phone. With rooted access and no recovery you can Debloat the device and run rooted apps. Enjoy !!!
Click to expand...
Click to collapse
darn I guess i'm boned then. I have 4.4.2 but I used Odin to root my phone :-/
I guess if something does happen to where I need to replace it, there's always the *nuke* method or *it's lost or stolen + nuke* method as i do have Sprint's TEP plan.
williamguile said:
darn I guess i'm boned then. I have 4.4.2 but I used Odin to root my phone :-/
I guess if something does happen to where I need to replace it, there's always the *nuke* method or *it's lost or stolen + nuke* method as i do have Sprint's TEP plan.
Click to expand...
Click to collapse
I run a stock rooted 4.4.2 NC5 with Philz custom recovery version 6.12.9 hltespr. The device was rooted and warranty tripped the second day I owned it. I was in a Sprint corporate Store a couple of wks ago. Showed the tech my rooted note 3. He said I can't touch that, I said what if I unrooted the phone. He said no problem, now I can warranty the phone. He didn't care that the KNOX flag was tripped at all 0x1. Just can't be rooted when you bring it in for service. Sprint doesn't care about KNOX only Samsung cares about KNOX. When Samsung paid millions to the NSA to design a security system to track and spy on others than they care !!!
I used pingroot in order to not trip knox and it worked
But now i used simplekernel using flashify but it tripped knox i dont know why
Is there any way to untrip it and
Whats the point of ping pong if knox it going to get tripped by a rom or a kernel
hadihawat12 said:
I used pingroot in order to not trip knox and it worked
But now i used simplekernel using flashify but it tripped knox i dont know why
Is there any way to untrip it and
Whats the point of ping pong if knox it going to get tripped by a rom or a kernel
Click to expand...
Click to collapse
Any custom firmware trips it. Good kernel choice though :angel: See it positive, you're not alone with this. Knox blew a physical fuse, there is no way to reset it. On the Exynos Note 4 it was apparently possible to rewrite parts of the bootloader to change 0x1 to 0x0, but thats only a visual change, if someone looks deeper than that, they'll notice easily that it's blown.
The point of PingPong is to provide Root without tripping Knox, it's not made for anything beyond that
Sadly no way to reset Knox. Any custom recovery or kernel will trip it. The point of PingPong was to root devices without tripping Knox. For example, I'm running completely stock software, but wanted to root for AdBlocker, Greenify, and a couple other root-only programs. I did not want to trip Knox (not at least until Samsung Pay comes out). PingPong was for people like me who want root but not necessarily a custom kernel or ROM. Sorry.
Ohh thats a bummer now i have to stick with the annoying knox thing that keeps on going into my notifications
hadihawat12 said:
Ohh thats a bummer now i have to stick with the annoying knox thing that keeps on going into my notifications
Click to expand...
Click to collapse
I think you can use TitaniumBackup or something to freeze the Knox apps. I forget which one(s) but I believe I've seen threads around here that discuss it.
I was wondering if I could use flashfire to flash XtreStoLite Deo-Mod Edition 2.1 ROM without tripping knox. Any help would be appreciated!
As far as I know in order to flash a rom needs changes to bootloader as soon as you touch the bootloader it trips knox. You can only root without tripping knox
Sent from my SM-G925F using Tapatalk
I had rooted via Pingpong root fine (no knox tripped) and then downloaded Echoe rom with standard kernel after being told that it would not trip knox (it worked for that guy) but it tripped knox anyway. So I though well, why not go all the way.
dwarfer66 said:
I had rooted via Pingpong root fine.
Click to expand...
Click to collapse
Ping Pong root uses an exploit in the 5.0.2 Stock rom to get root access, without flashing.
Anytime the bootloader partition gets written to, the Knox counter gets incremented.
Flashing with Flashfire will trip Knox.
I do not believe there is a way to flash without accessing the Bootloader.