Database Users

Root de la Vega (doesnt trigger knox) possible to port N900/N9005

UPDATED POST:
Hello,
As @Dumbo53 has mentioned below posts, there is a root method by the developer @designgears and it seems that this root method does NOT trigger the knox flag.
Unfortunately, it is just for the AT&T Note 3 devices.
Maybe someone could port this root method for our international N900 and N9005 model devices?
Root de la Vega:
http://forum.xda-developers.com/showthread.php?t=2474422
----------------------------------------------------
Hello there,
I wanted to share something from Chainfire's Auto-Root thread.
Chainfire has mentioned:
Using this root method sets current binary and system status to custom. Additionally, it will also trigger the KNOX warranty void status.
This device store the traditional flash counter. Nor is is possible with Triangle Away to reset the current binary status. You will need to flash a stock kernel and stock recovery to reset the binary status.
The KNOX warranty status change is permanent, and a service center may deny warranty based on this flag - even if the other flags are reset correctly. The KNOX flag being tripped may also prevent certain Samsung KNOX features from working (enterprise security features).
If this is something you care about, use a root method not based on custom kernels or recoveries, like a modified system partition. These are possible, but I don't personally make them, so look around!
Click to expand...
Click to collapse
So my question is simple:
Is there any talented developer who can look at the system partition on the devices N900/9005 and somehow to look if he can modify it to root without triggering the knox counter. Iaw chainfire's post, it seems to be possible, but we need a talented developer to look for this
I would be really so happy, if it can be done this way...

No because if you do anything you alter the md5 checksum m8 and knox watch this
Sent from my SM-N9005 using Tapatalk 4

BlueChris said:
No because if you do anything you alter the md5 checksum m8 and knox watch this
Sent from my SM-N9005 using Tapatalk 4
Click to expand...
Click to collapse
I was talking according to Chainfire, dude. He just showed us that there could "may be" a way to root without knox would recognise this.
I think may be knox watches only the bootloader and recovery situation (if it is custom or official).
Chainfire's root method includes to flash first insecure recovery and after root flashes back the official recovery. During this process knox recognise the shortly time with the insecure recovery and the counter goes to 0x1. But iaw Chainfire's post, i think if someone could root without touching the recovery or kernel, it could be possible not to trigger the knox during the root process.

I don't think we will have a way to bypass it. I think once you get root it will still trigger it.
Funny how this is something from an Android device and not an iDevice.
Guess Samsung got tired of fixing devices after someone oc the hell out of it!
Sent from my SM-N9005 using XDA Premium 4 mobile app

There already is a root method that doesn't trigger the Knox flag by designgears, but as of now only for At&t Note 3 (Root de la Vega). It however only gives root, not a custom recovery. There are already people begging him to port it to other devices and he seems to be willing to do them one by one.
Sent from my SAMSUNG-SGH-I317

Dumbo53 said:
There already is a root method that doesn't trigger the Knox flag by designgears, but as of now only for At&t Note 3 (Root de la Vega). It however only gives root, not a custom recovery. There are already people begging him to port it to other devices and he seems to be willing to do them one by one.
Sent from my SAMSUNG-SGH-I317
Click to expand...
Click to collapse
Thanks mate, i will also look to his thread and beg him for n900

Sounds promising. Don't really need a custom recovery thanks to xposed.
Sent from my SM-N9005 now Free

Knox problem thanks (lovelesss)

we are waiting for n900 please

n900 I want to wait for the Root de la Vega.

What about N9005?

vinokirk said:
What about N9005?
Click to expand...
Click to collapse
+1
Sent from my SM-N9005 using Tapatalk 4

vinokirk said:
What about N9005?
Click to expand...
Click to collapse
Yeah I can add N9005 also as request on this topic.
Changing the subject of this thread just a sec

I don't have any information showing Knox flag in Odin mode, Exynos SM-N900. Does this mean my phone doesn't have this flag?

Xposed Issues

I love using Wanam Xposed along with the extra power the Xposed framework gives to Greenify but I found an issue with it on the S5. When you install the framework S Health no longer works. Anyone else find this or is it just my S5?

carbonize said:
I love using Wanam Xposed along with the extra power the Xposed framework gives to Greenify but I found an issue with it on the S5. When you install the framework S Health no longer works. Anyone else find this or is it just my S5?
Click to expand...
Click to collapse
im also having the same problem , try posting on there thread and see if you can get anyhelp
this is my log file for the error when s health crashes
http://forum.xda-developers.com/xposed/framework-xposed-rom-modding-modifying-t1574401
http://forum.xda-developers.com/xposed/framework-xposed-rom-modding-modifying-t1574401

I have posted in the Xposed forum so will see if I get anywhere.

Hmm I did have a reply but tapatalk wasn't showing there being one. http://forum.xda-developers.com/showthread.php?t=2725405

The problem has something to do with disabling knox after rooting. If you do not disable knox, s-health seems to be ok, but after disabling it, it has issues. Some people have restored, rerooted, keeping knox and resolved the issue.

risestar2 said:
The problem has something to do with disabling knox after rooting. If you do not disable knox, s-health seems to be ok, but after disabling it, it has issues. Some people have restored, rerooted, keeping knox and resolved the issue.
Click to expand...
Click to collapse
happen to have a link to thread where users have done the above looking for a bit more info on this.
far I knew knew there was no way to root and recovery without tripping knox

Tripping the Knox flag us not the issue, the issue us when you disable know in #su afterwards. You can root and keep Knox running and it eliminates these issues
ex-28 said:
happen to have a link to thread where users have done the above looking for a bit more info on this.
far I knew knew there was no way to root and recovery without tripping knox
Click to expand...
Click to collapse

risestar2 said:
Tripping the Knox flag us not the issue, the issue us when you disable know in #su afterwards. You can root and keep Knox running and it eliminates these issues
Click to expand...
Click to collapse
So how do you root and keep knox in intact with recovery?
Sent from my SM-G900W8 using Tapatalk 2

Yes, when it asks you if you want to disable Knox, you choose no
ex-28 said:
So how do you root and keep knox in intact with recovery?
Sent from my SM-G900W8 using Tapatalk 2
Click to expand...
Click to collapse

risestar2 said:
Yes, when it asks you if you want to disable Knox, you choose no
Click to expand...
Click to collapse
Ok thanks do
You have the thread handy should how to revert back when Knox is disabled?
Sent from my SM-G900W8 using Tapatalk 2

I used Chainfire's root and don't remember disabling Knox.

risestar2 said:
Tripping the Knox flag is not the issue, the issue us when you disable knox in #su afterwards. You can root and keep Knox running and it eliminates these issues
Click to expand...
Click to collapse
carbonize said:
I used Chainfire's root and don't remember disabling Knox.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2696537
Using this root increases your flash counter and trips the KNOX warranty flag!
maybe i'm reading what other post said key word "disable"
I never disabled knox but did trip the flag

Pretty much any rooting method to date or any unsecured bootloader will trip the Knox flag. If you don't want to trip the flag, you're going to have to stay bone stock. There's a difference in tripping the flag and disabling the Knox software. When you root and choose to disable Knox, that's when people have issues with some Sammy apps
Sent from my SM-G900T using xda app-developers app

I'm trying to understand... are people disabling Knox themselves before/after they install Xposed, or is Xposed disabling Knox automatically?

Anyway to test if Knox is enabled or not?

risestar2 said:
Pretty much any rooting method to date or any unsecured bootloader will trip the Knox flag. If you don't want to trip the flag, you're going to have to stay bone stock. There's a difference in tripping the flag and disabling the Knox software. When you root and choose to disable Knox, that's when people have issues with some Sammy apps
Sent from my SM-G900T using xda app-developers app
Click to expand...
Click to collapse
risestar2 said:
The problem has something to do with disabling knox after rooting. If you do not disable knox, s-health seems to be ok, but after disabling it, it has issues. Some people have restored, rerooted, keeping knox and resolved the issue.
Click to expand...
Click to collapse
can you explain this more please you stated that some people are restoring and rerooting and keeping knox enabled then s health works fine. but searching the forums I am unable to find any reference to this or how to do this.;
would also like to know a way to tell if knox is enabled or disabled , I know my knox flag is tripped but far as I know I never disabled it , if that's the case then if knox is the issue then my s health should be working fine.
---------- Post added at 10:37 AM ---------- Previous post was at 10:35 AM ----------
maybe a better question is this
risestar2 are you rooted with recovery and have xposed installed with s health working fine ? on the galaxy s5

Surely the big question is what is Xposed doing that stops it working as it works fine until I install Xposed.

carbonize said:
Surely the big question is what is Xposed doing that stops it working as it works fine until I install Xposed.
Click to expand...
Click to collapse
would like to know as well
mine works fine even after installing xposed ,its when you install the framework in xposed that makes s health crash as if I uninstall the framework from within xposed and reboot , s health is fine again , I took my logcat files and have posted them but no luck form anyone yet

I'll try to find the thread, but essentially it's this.
You root your phone using one of the 2 preferred methods, both of which trigger your one time Knox flag.
Installing root installs the #su app. Upon starting this for the first time, you should be prompted that Knox is running, do you want to disable? Yes/No.
People that choose yes are having difficulty using some Sammy apps, including so health and private mode. People that don't disable Knox are not having these issues.
You may be able to re-enable Knox in #su, or your best bet is factory restore and then reroot and choose not to disable Knox (root and everything still works fine)
You can troubleshoot it by Uninstalling all xposed framework and modules and testing all Sammy apps. If they work fine then the issue is a compatibility issue with xposed or xposed and another app or modification. If they don't work with xposed Uninstaller then the issue is likely Knox related and you likely need to re-enable Knox.
The Knox flag is a one time flag, not a counter so once it's tripped, it's tripped (e-fuse) and it doesn't really matter what you do afterwards. You can load a hundred different rooms and it will still be 0x1 Knox warranty void.

Risestar2 I've already said the issue only occurs after installing Xposed and goes away one I uninstall it. So the problem definitely lies with Xposed and not knox.

[Q] Does tripping KNOX disable full system functionality and flash without tripping?

Hi guys so I'm really sorry if this has been asked millions of times but what I want to know is, does tripping the KNOX flag open a huge risk to normal system functionality not working? Now I know KNOX tripping, prevents you from using KNOX related stuff but does it stop you from an average joe using their phone normally, installing apps, sideloading apps, using the camera. That sort of thing.
The other thing is, I want to have a go at flashing custom ROMs to my device. My warranty runs out next month so this would be perfect, providing the above question is true (that it doesn't disable full functionality) I will go and follow normal tutorials.
Now I've been reading about SafeStrap and how it creates the ability to flash ROMs without touching vital system parts that would trip KNOX. Is this true? Could I really root without tripping, install SafeStrap and finally install custom ROMs without tripping KNOX or am I in a dream world haha?

WhaleTrain said:
Hi guys so I'm really sorry if this has been asked millions of times but what I want to know is, does tripping the KNOX flag open a huge risk to normal system functionality not working? Now I know KNOX tripping, prevents you from using KNOX related stuff but does it stop you from an average joe using their phone normally, installing apps, sideloading apps, using the camera. That sort of thing.
The other thing is, I want to have a go at flashing custom ROMs to my device. My warranty runs out next month so this would be perfect, providing the above question is true (that it doesn't disable full functionality) I will go and follow normal tutorials.
Now I've been reading about SafeStrap and how it creates the ability to flash ROMs without touching vital system parts that would trip KNOX. Is this true? Could I really root without tripping, install SafeStrap and finally install custom ROMs without tripping KNOX or am I in a dream world haha?
Click to expand...
Click to collapse
Tripping knox does not affect phone performance, as for safestrap, as far as I know that has to be used on locked bootloader phones (like US carrier ones).
Once knox is tripped knox is tripped, I have heard the proggy that does not trip knox when rooting is Towelroot, but some people are having big problems with battery life.

WhaleTrain said:
Hi guys so I'm really sorry if this has been asked millions of times but what I want to know is, does tripping the KNOX flag open a huge risk to normal system functionality not working? Now I know KNOX tripping, prevents you from using KNOX related stuff but does it stop you from an average joe using their phone normally, installing apps, sideloading apps, using the camera. That sort of thing.
The other thing is, I want to have a go at flashing custom ROMs to my device. My warranty runs out next month so this would be perfect, providing the above question is true (that it doesn't disable full functionality) I will go and follow normal tutorials.
Now I've been reading about SafeStrap and how it creates the ability to flash ROMs without touching vital system parts that would trip KNOX. Is this true? Could I really root without tripping, install SafeStrap and finally install custom ROMs without tripping KNOX or am I in a dream world haha?
Click to expand...
Click to collapse
Yes, it seems to be possible that you can flash custom roms without tripping Knox.
http://forum.xda-developers.com/galaxy-s4/general/guide-how-to-install-custom-roms-t2852310
Sent from my Galaxy S4 using Tapatalk

Without tripping knox you can get root, and modify the actual rom filesystem, for example you can change all /system of the rom using mobile odin pro.
You cannot change kernel or recovery, or you get knox 0x1.
Flashing roms with mobile odin pro is possible only if rom is compatible with your current official kernel you have, or the results would be bad (wifi not working or so on..).

fear_factory84 said:
Without tripping knox you can get root, and modify the actual rom filesystem, for example you can change all /system of the rom using mobile odin pro.
You cannot change kernel or recovery, or you get knox 0x1.
Flashing roms with mobile odin pro is possible only if rom is compatible with your current official kernel you have, or the results would be bad (wifi not working or so on..).
Click to expand...
Click to collapse
Can you flash roms after knox has been tripped

bottom661 said:
Can you flash roms after knox has been tripped
Click to expand...
Click to collapse
Yes
Sent from my GT-I9505 using XDA Free mobile app

[Q] Re-enable KNOX after root (with KNOX counter 0x0 intact)

Been trying to look for an answer but all related thread seem to talk about KNOX tripped (counter 0x1)... But my case is different here.
I have rooted my S5 G900F with Towelroot without tripping KNOX. Right now the phone is running stock NG2 firmware with root and KNOX disabled (KNOX counter remain 0x0, device status Custom).
Due to work requirement, I need to encrypt my phone, but encryption won't works with KNOX disabled. My question is, is it possible to enable KNOX (while rooted), then go on with encryption and disable KNOX after the encryption. If so, how? What is the effect of having KNOX enabled while remain rooted?

Good question

This question has been asked in the CF-Root thread many times. CF recommends to keep it disabled. Otherwise, the phone will be unstable (autoreboot) and other strange things could happen. Read CF-Root thread for more details.

After some reading, it seems like you can restore KNOX by: unrooting with superSU, flashing a stock rom, and do a data factory reset.
Check this link for more info: http://forum.xda-developers.com/galaxy-s5/help/unroot-rooted-towelroot-sm-g900f-t2804788
Hope this helps.

TheSamWolf said:
After some reading, it seems like you can restore KNOX by: unrooting with superSU, flashing a stock rom, and do a data factory reset.
Hope this helps.
http://forum.xda-developers.com/galaxy-s5/help/unroot-rooted-towelroot-sm-g900f-t2804788
Click to expand...
Click to collapse
The system status and current binaries both have to be showed as official in downloadmode to use KNOX.

Dark_Avenger said:
This question has been asked in the CF-Root thread many times. CF recommends to keep it disabled. Otherwise, the phone will be unstable (autoreboot) and other strange things could happen. Read CF-Root thread for more details.
Click to expand...
Click to collapse
I read that, but I didn't use CF-Root to obtain root (as it well trip KNOX), i used TowelRoot (without tripping KNOX). Don't know if it would behave the same as the CF-Root method.
Thanks for pointing out.

TheSamWolf said:
After some reading, it seems like you can restore KNOX by: unrooting with superSU, flashing a stock rom, and do a data factory reset.
Check this link for more info: http://forum.xda-developers.com/galaxy-s5/help/unroot-rooted-towelroot-sm-g900f-t2804788
Hope this helps.
Click to expand...
Click to collapse
That means I have to unroot it, not exactly what i'm looking for...

AFAIK Knox (the software container) will never ever be enabled when you are rooted (even with Knox counter set to 0x0).
I believe it checks on root access.
As I understand it correctly, the company where you work for only requires that your phone is encrypted and not manageable ?
I work for one of the largest companies in the world and my phone (S3) is not allowed to be rooted.
The container software (Airwatch) checks on that.
When every check is confirmed, only then will it make a container and encrypts the data in that container.
And from administrators it can be managed, like remote wipe, anti-theft, etc

speedme said:
AFAIK Knox (the software container) will never ever be enabled when you are rooted (even with Knox counter set to 0x0).
I believe it checks on root access.
Click to expand...
Click to collapse
That was my understanding too!
To re-enable KNOX, reflash stock firmware as described. After that, you can try again (towel) rooting your device, and Do Not disable KNOX. Though, I read that root will not work quite correctly?
Please write back with your results if you try it!!!

You probably right that Knox won't work when phone is rooted...
Well, with My Knox available now, no full phone encryption is required (as encryption will only be within the Knox container). Maybe one fine day I'll reset my phone, root then unroot temporary in order to try My Knox...
Sent from my SM-G900F using Tapatalk

Hey Guys,
I have a doubt on using KNOX.
Actually I don't care about tripping my Knox Counter. (0x1) but I just require to know whether I can use KNOX just like before rooting without any problems?
If Warranty is the only concern to be worried about , due to rooting of the phone; I can live with it, but does rooting limits/restricts the users from using KNOX and any/all of its functionality totally?

xda rocks said:
Hey Guys,
I have a doubt on using KNOX.
Actually I don't care about tripping my Knox Counter. (0x1) but I just require to know whether I can use KNOX just like before rooting without any problems?
If Warranty is the only concern to be worried about , due to rooting of the phone; I can live with it, but does rooting limits/restricts the users from using KNOX and any/all of its functionality totally?
Click to expand...
Click to collapse
In my experience(for what it's worth, lol), I have seen no performance issues with Knox functionality by rooting. Flashing through Odin trips the warranty counter and voids warranty. There are apps that disable Knox but the ones I've seen warn you before doing so. Hope that helps. Good luck
Sent from my SM-G900P using XDA Free mobile app

xda rocks said:
Hey Guys,
I have a doubt on using KNOX.
Actually I don't care about tripping my Knox Counter. (0x1) but I just require to know whether I can use KNOX just like before rooting without any problems?
If Warranty is the only concern to be worried about , due to rooting of the phone; I can live with it, but does rooting limits/restricts the users from using KNOX and any/all of its functionality totally?
Click to expand...
Click to collapse
You will NEVER be able to use the Knox Container EVER again after ur counter says 0x1... Samsung made it for business enterprises for security concerns, if these *Android Hackers and Modders* will just bypass the Knox security then Samsung wouldn't have business enterprises using the Knox Container because it can just easily be bypassed..
Sent from my SM-G900F using XDA Free mobile app

trettet said:
You will NEVER be able to use the Knox Container EVER again after ur counter says 0x1... Samsung made it for business enterprises for security concerns, if these *Android Hackers and Modders* will just bypass the Knox security then Samsung wouldn't have business enterprises using the Knox Container because it can just easily be bypassed..
Sent from my SM-G900F using XDA Free mobile app
Click to expand...
Click to collapse
Makes sense...!!! But I see almost everyone requesting to get a root access mentioning about Warranty void. I was wondering if that is the only reason can we use knox even after making our phone warranty void. Anyways I got the idea. :sly:

I need help
please some one .. i need help and it's so important . one of my friend encrypted his data though knox and regardless of what super su and root do with knox and it's disabling knox ... he rooted his phone ! (he is todler and didn't take notice )
anyway his knox now is disabled and he can't access to his data because in security knox is disabled .. how can we enable knox so he can decrypt knox with password and access to his data ... thanks in advance and keep in mind that please guys if you are not sure about how can solve problem without losing data , guide me . data encrypted with knox is so important to him .
target device is Galaxy note 3 n9005 .

You cant use knox on rooted device
When uroot your device, ur device status nd binaries change to custom. KNOX checks that. If the binaries are custom, you cant use KNOX ever.

Is there a way to completely unroot and go back to KNOX 0x0, all official? Even if we pay Samsung service centre?

true sir, my Samsung Galaxy S7 edge unable to even install myknox after flash back to stock rom

Root without tripping knox idea (will not work)

Hawke84 said:
Lots of work went I to finding a solution on S4 when knox first came out including by chainfire with no luck. Also since october people have been trying to root note 4 without tripping knox with no luck.
There is no difference in the system of tripped and not tripped. Soon as anything unsigned or insecure is flashed the bootloader burns the efuse
Sent from my SM-G920F using XDA Premium 4 mobile app
Click to expand...
Click to collapse
As you can see my idea was a bust but here is the original op
Okay, Lets try this here because nobody seems interested in helping in the T-Mobile section.
ThePagel said:
Correct me if I am wrong here, the reason knox is being tripped by cf auto root is because of the way it acquirers root not because it is rooted. With that in mind I would Like to make a tar ball with a pre rooted system.img. To make sure it will have the best possibility to not trip knox and not cause a soft brick I want to use a system dump from a running phone that has only been rooted. I am pretty sure this has worked on every galaxy phone before the s6 and the only reason you don't hear more about it recently is because of the success of towelroot. I am getting this phone on the 1st (so excited) and would like root but want to try samsung pay more.
If you are willing to help I need the following:
Be on a 100% stock samsung bloated system with root (absolutely no tweaked systems I need pure stock with root)
Install supersu into /system (supersu settings)
Make a system.img dump with adb or terminal emulator and upload it for me (as long as you do not dump the data partition no personal data will be dumped)
At this point I will make the tarball and upload it and have the person who made the system dump flash the tarball. If he/she boots up fine I will the need a volunteer who has not rooted and verified that knox has not been tripped on his/her phone to flash it and see if knox still has its warranty. Obviously the volunteer should go into this not caring if knox gets tripped.
To make things completely clear I need the following:
Somebody who knows how to dump with adb/terminal emulator and already rooted
Somebody without a tripped knox warranty who doesn't care if it gets tripped
Click to expand...
Click to collapse

As soon as you flash an unsigned image Knox is going to be tripped.

Lots of work went I to finding a solution on S4 when knox first came out including by chainfire with no luck. Also since october people have been trying to root note 4 without tripping knox with no luck.
There is no difference in the system of tripped and not tripped. Soon as anything unsigned or insecure is flashed the bootloader burns the efuse
Sent from my SM-G920F using XDA Premium 4 mobile app

Drumrocker said:
As soon as you flash an unsigned image Knox is going to be tripped.
Click to expand...
Click to collapse
^^^ This, unfortunately, ends the discussion altogether.

Drumrocker said:
As soon as you flash an unsigned image Knox is going to be tripped.
Click to expand...
Click to collapse
Hawke84 said:
Lots of work went I to finding a solution on S4 when knox first came out including by chainfire with no luck. Also since october people have been trying to root note 4 without tripping knox with no luck.
There is no difference in the system of tripped and not tripped. Soon as anything unsigned or insecure is flashed the bootloader burns the efuse
Sent from my SM-G920F using XDA Premium 4 mobile app
Click to expand...
Click to collapse
CafeKampuchia said:
^^^ This, unfortunately, ends the discussion altogether.
Click to expand...
Click to collapse
Indeed now I get closure, thank you.

So how does safestrap work?

lowspeed said:
So how does safestrap work?
Click to expand...
Click to collapse
Doesn't matter in this instance because you need root to use safestrap. He is pretty open on how safestrap works if you look at his threads and website.

Sorry guys, which signature needs to be applied? I found a guide to sign Windows modded drivers, I don't know if this can be applied here, too...

The real trick is getting it signed. There might be no easy way to do that unless the key method can be replicated to make signed binaries. This could be a samsung proprietery tool. That said I did find an interesting nugget of info hxxp://galaxys4root.com/what-is-binary-counter/ in the comments section.
HI,
I flashed pre rooted firmware 4.2.2 using ODIN on my Samsung I-9500 4.2.2. Then the status is remain same
Binary : Samsung Official
System : Official.
Then I installed Wanam apk to modify the UI, It asked me to download Xposed framework I grant Super user permission. Once It completed I checked the status
Binary : Samsung Official
System : Custom.
I flashed stock firmware 4.2.2 and did the reset factory reset. Then it changed to
Binary : Samsung Official
System : Official.
My question, Is the hidden binary count or knox counter triggered or not ?
If I updated to stock 4.3 Is the Knox Warranty bit 0×0 or 0×1 ?
Please help me.
The rooted aspect only seems to be possible provided nothing in the UI itself is changed? There is a trigger file in the rom. Something that obviously a Wanam install triggers. All that seems to indicate that it might actually be possible to have a pre-rooted rom and install via recovery. But considering the phone model referenced, its possible this particular workaround has been plugged. On the off chance that it has not. It might be the only viable way to do root without tripping knox. I imagine the existing stock roms with root preloaded however trip knox (I saw no indication of that in posts but I did not dig that deep).
If anyone can answer that in the affirmative or negative it might be worth noting. Will knox get tripped on a stock (but pre-rooted) rom?

The point of this thread is to point out something we already know and have known for some time? WTF

shollywood said:
The point of this thread is to point out something we already know and have known for some time? WTF
Click to expand...
Click to collapse
I don't think the OP was aware of all the information when he started the thread. I think the thread title has since been changed.
But yeah, i guess the thread could be closed.