Just wondering:
Is it possible to keep the fingerprint scanner, while rooting a SM-G925F? Also, is this possible with the combination of keeping KNOX not tripped?
And a bonus question: Is it possible to unroot the phone, without tripping Knox then? Cuz Knox is tripped when you change the system, I've heard.
Related
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
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.
It's kind of difficult to determine where the T-Mobile variant stands with 5.1.1. I know that root is obtainable and that Knox tripping can be avoided, but the caveat is that the fingerprint sensor is disabled.
Does anyone know if that has changed? I'm rooted on 5.0.2, everything unlocked, and I'm using it on AT&T. I want to be able to update to alleviate the RAM issue, but I want to keep root, the fingerprint sensor, and eventually be able to use Samsung Pay etc.
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
Hi,
I own a galaxy s9+ (SG-G965F) exynos build. My WARRENTY VOID shows 1 (0x030c).
I understand that my warrenty is void(1) but,
can you please help me understand what does the (0x030c) mean?
The KNOX status samsung app shows 0x0. Does that mean though my warrenty is void but the KNOX has not been tripped?
If the Knox hasn't been tripped, can I get microsoft intune, samsung pay etc. working again by just reflashing stock firmware?
Thanks
1. It's probably some binary or something that explains how the tripped KNOX happened to Samsung Engineers. No idea though because no one asked so far
2. This is because you use a custom rom which patches the KNOX counter once you boot up your rom, so SHealth works again.
3. Nope. Once you trip the KNOX, it stays tripped. Samsung Pay will never work with a tripped KNOX and cannot be patched as the SHealth is
Oh kk got it.
Is there anyway i can get a workaround for microsoft intune similarly?
Basically i want to access ny organization email via outlook.
My organization needs Microsoft intune which checks knox status.
Is there any way to get this done?
Thanks in advance