Hi all
Quick inquiry and I didn't see an exact answer to a question that I have. So I have a note 3 rooted and knox flag currently set to 0x0. I was reading I think on here and some other fourms that knox has locked the bootloader. I want to flash a custom recovery and I know it will trip the knox flag. Is the bootloader locked already or am I able to load custom recovery without any issue?
Do you have the T-mobile version? If so, then no, the bootloader is NOT locked.
Flashing a custom recovery WILL trip the Knox flag though.
idtheftvictim said:
Do you have the T-mobile version? If so, then no, the bootloader is NOT locked.
Flashing a custom recovery WILL trip the Knox flag though.
Click to expand...
Click to collapse
Hi. I kind of in the same situation.
I am a Note 2 user since it came out and have tried many ROMs without problems. I recently upgraded to Note 3 and I haven't touched anything (rooting and flashing) because I remember reading before about some problems with Knox and eFuse or something. I got a T-Mobile note btw.
Do I have to treat Note 3 differently when rooting and flashing because of this knox, efuse issues?
I tried to look for a clearer answer but I'm still hesitant to proceed. Or is the process the same as rooting and flashing ROMs on Note 2?
Also, I have a Jump insurance with TMO, is this going to have some problem if later I have to claim replacements or upgrade? Thanks a lot. Really appreciate the help.
jinda628 said:
Hi. I kind of in the same situation.
I am a Note 2 user since it came out and have tried many ROMs without problems. I recently upgraded to Note 3 and I haven't touched anything (rooting and flashing) because I remember reading before about some problems with Knox and eFuse or something. I got a T-Mobile note btw.
Do I have to treat Note 3 differently when rooting and flashing because of this knox, efuse issues?
I tried to look for a clearer answer but I'm still hesitant to proceed. Or is the process the same as rooting and flashing ROMs on Note 2?
Also, I have a Jump insurance with TMO, is this going to have some problem if later I have to claim replacements or upgrade? Thanks a lot. Really appreciate the help.
Click to expand...
Click to collapse
Well, from where we are right now with the Knox counter, if you flash ANY ROM or Kernel, then the Knox will trip, and will void your warranty. You can root using Root de la vega, or Kingo root without tripping the Knox counter.
I am not sure from a T-Mobile standing if they will give you a hard time with warranty if the Knox is 0x1. I have tripped my Knox counter, and have Jump also, but I honestly don't care. I am sure that SOMEHOW in the future we will be able to reset the Knox counter....I hope anyways.
Did that answer your question?
idtheftvictim said:
Do you have the T-mobile version? If so, then no, the bootloader is NOT locked.
Flashing a custom recovery WILL trip the Knox flag though.
Click to expand...
Click to collapse
I have note 3 with tmobile. Thanks for the help
idtheftvictim said:
Did that answer your question?
Click to expand...
Click to collapse
Yes you did! Thanks a lot. Important thing is at least I can root. I think I'll be happy with the stock TW, I'll just install some launcher instead.
But I need root for TB and other stuff.
Thanks!
Related
So... after first being impatient and buying a T-Mobile Note3 on Craigslist to use on AT&T and then later seeing how the bootloader locked AT&T Note3 was rooted by DG and Chainfire I ended up getting a contract renewal with AT&T after all and went with the AT&T Note3.
Now I thought I might try to experiment a little and see if I can replicate that root method on the T-Mobile Note3 because it's so brilliant and doesn't trigger the Know warranty void flag.
I can confirm it works just as well on the T-Mobile Note3 !!
ALL CREDIT for the method goes to DesignGears and Chainfire! The Original Thread is HERE: http://forum.xda-developers.com/showthread.php?t=2474422
All steps are exactly the same. THIS IS ONLY FOR N900TUVUBMI7 firmware, so that must be the current one installed on your phone.
Please follow all steps in the original AT&T thread, just skip the oneclick.exe and start with flashing the root_de_la_vega.tar using ODIN.
There is not really a need to so this if you already rooted with the AutoRoot method and triggered the Knox flag. This is for the careful guys who have NOT rooted yet, only want root (no custom ROM or recovery) and would rather like to preserve that Know Warranty 0x0 Flag
Link to the needed file for T-Mobile Note3 is HERE:
http://www.electron73.org/XDA/N900T/ROOT_DE_LA_VEGA-TMO.ZIP
Enjoy
Nice! If I wanted to go stock again, can I just flash the stock firmware in odin and it wont trip the knox flag?
lm that guy said:
Nice! If I wanted to go stock again, can I just flash the stock firmware in odin and it wont trip the knox flag?
Click to expand...
Click to collapse
Unfortunatley, once you trip the Knox Flag you can't untrip it - doing Odin to Stock will return you to stock but it does not remove the Knox flag...once it's tripped - it's tripped.
mocsab said:
Unfortunatley, once you trip the Knox Flag you can't untrip it - doing Odin to Stock will return you to stock but it does not remove the Knox flag...once it's tripped - it's tripped.
Click to expand...
Click to collapse
Oh no I haven't tripped my Knox flag yet I was asking if I use this method to root and I wanted to go back to stock later down the road, Will I trip the Knox flag if i odin the official stock firmware?
Its good to have this method available for those who are very conscious of Knox falg/warranty. Personally:
I will be doing a full root on my second N3. I have to; in the memory of my first N3... RIP where ever you are now.
lm that guy said:
Oh no I haven't tripped my Knox flag yet I was asking if I use this method to root and I wanted to go back to stock later down the road, Will I trip the Knox flag if i odin the official stock firmware?
Click to expand...
Click to collapse
I am not positive - but I think if you flash anything - it will trip it - if you odin back to stock - it would include a new kernel and that would tirp the flag - I may be wrong - but I believe I read this the other day.
WHy would you want to return to stock? To return the phone or something if something went wrong? Maybe there is another way to remove root.?
I dont think you even have to remove root. There will be now ay to tell if you are rooted using that method. Unless you use app that ask you SU permission. So before return just do Factory Reset. That i think should take care of things. IMHO.
lm that guy said:
Oh no I haven't tripped my Knox flag yet I was asking if I use this method to root and I wanted to go back to stock later down the road, Will I trip the Knox flag if i odin the official stock firmware?
Click to expand...
Click to collapse
No, if you ODIN back to full stock or do a factory reset/wipe the Knox flag will NOT be triggered. That flag only triggers if you install a CUSTOM recovery or kernel (custom rom).
For the Galaxy S3, there's also a "no trip root" thread where you simply flash a root-injected TouchWhiz, which I used, and as long as you never flash anything non-Samsung in ODIN, you'll never trip the flash counter flag (which can be reset with TriangleAway anyway, unlike the KNOX flag afaik). But, once rooted, you don't need ODIN, and flashing TWRP recovery via the GooManager app (or dd'ing the img over the recovery partition) doesn't trip the flag, nor does subsequent ROM flashes from recovery over the system partition.
Is it the same situation here, or is the KNOX flag different, in that it will always get tripped as soon as it sees an unsigned partition on bootup?
Darn.. Wish I came upon this like 2 days after I had my TMO note 3. Ive already tripped my Knox. Oh well.
Has anybody tested this method. Does it work
Sent from my SM-N900T using xda app-developers app
DriftorX said:
Darn.. Wish I came upon this like 2 days after I had my TMO note 3. Ive already tripped my Knox. Oh well.
Click to expand...
Click to collapse
The one thing that will eventually have me tripping my Knox flag is if a nice custom kernel comes along. But until then, a simple way to root without tripping the flag will hold me over :fingers-crossed:. Also I'm returning my phone in a week so it's important I don't trip it right now. I want to root and play around with my phone until then.
bbh4r4l said:
Has anybody tested this method. Does it work
Sent from my SM-N900T using xda app-developers app
Click to expand...
Click to collapse
I will test in about 10 minutes when my phone gets finished charging to 100% and will report back. :laugh:
Edit: everything works Thanks OP for posting this!!
Just rooted via this method. It worked fine and knox is stil 0x0. It also didn't factory reset my phone like I thought it would, I'm going to do it anyway, but I wasn't getting any FCs or anything either. Thank you for getting this out to us TMO users!
I don't get it. Rooting doesn't trip knox regardless. But flashing a custom kernel or rom does. So what is the point of this method if it will trip knox as soon as you flash a kernel or rom anyway.
HughesNet said:
I don't get it. Rooting doesn't trip knox regardless. But flashing a custom kernel or rom does. So what is the point of this method if it will trip knox as soon as you flash a kernel or rom anyway.
Click to expand...
Click to collapse
For one you can use apps that require root. Also, you can uninstall bloatware and push apks to your phone using adb etc. A little more work than flashing a prebuilt custom rom, but you can get many of the same results.
*You also said rooting doesn't trip knox regardless, but it actually does unless you do it via this method.
Just did this. Easy as cake. Now I just need to sim unlock my note to use my ATT sim and I will be good to go!!
effortless said:
For one you can use apps that require root. Also, you can uninstall bloatware and push apks to your phone using adb etc. A little more work than flashing a prebuilt custom rom, but you can get many of the same results.
*You also said rooting doesn't trip knox regardless, but it actually does unless you do it via this method.
Click to expand...
Click to collapse
I know you don't need a custom rom for some things. I run stock deodex myself. I flashed custom recovery immediately after root. I guess I thought that is what triggered knox. Either way matters little to me though. I know tmobile won't check knox counter if I use jump and even if they did I could sell on ebay and come out ahead. So I don't really understand why people worry about it. Insurance covers it if you damage it or need warranty service.
HughesNet said:
I know you don't need a custom rom for some things. I run stock deodex myself. I flashed custom recovery immediately after root. I guess I thought that is what triggered knox. Either way matters little to me though. I know tmobile won't check knox counter if I use jump and even if they did I could sell on ebay and come out ahead. So I don't really understand why people worry about it. Insurance covers it if you damage it or need warranty service.
Click to expand...
Click to collapse
Yeah... Seems to me like a kinda-sorta placebo effect or simply one of those things that people can use who *must* have everything completely untraceable to the "T." Like you said, there's virtually no "real" reason this is very necessary, far's I can tell... But, regardless, good work on this - without a doubt - and definitely always a big "plus" to have multiple working methods! :good:
HughesNet said:
I don't get it. Rooting doesn't trip knox regardless. But flashing a custom kernel or rom does. So what is the point of this method if it will trip knox as soon as you flash a kernel or rom anyway.
Click to expand...
Click to collapse
exactly. I think op might not know everything like he is implying. he just wants some attention
*****es be be like "nice phone"
mocsab said:
I am not positive - but I think if you flash anything - it will trip it - if you odin back to stock - it would include a new kernel and that would tirp the flag - I may be wrong - but I believe I read this the other day.
WHy would you want to return to stock? To return the phone or something if something went wrong? Maybe there is another way to remove root.?
Click to expand...
Click to collapse
If people read up on how KNOX actually works, there wouldn't be so much confusion.
The KNOX WARRANTY VOID flag is set to 0x1 when the bootloader detects (via Qualcomm SecureBoot) that you are booting either a kernel or a recovery that isn't SELinux enforcing (it displays a message such as RECOVERY IS NOT SEANDROID ENFORCING - Set Warranty Bit: recovery). It remembers that the partition you booted was insecure and flags it in its own little memory area. It sets individual warranty bits for each partition - boot (kernel), recovery, cache (if you happen to put something there that it doesn't approve of), system. If ANY of those partition warranty bits are set, the KNOX WARRANTY VOID flag is set to 0x1.
This is all explained in the KNOX white paper available on the Samsung web site.
Now, if someone figures out how to write-enable the protected flash area so the flag can be reset AND disable Qualcomm SecureBoot so that it doesn't set the flag over and over again, we'll be in business. For now, only Samsung knows how to do it.
So i bought a Note 3 and as I do with all my devices i want to root it, but i am hearing some news things like Knox and alternate root methods.
I have some questions.
1. With knox i understand it voids your warranty if you root, but doesnt rooting always void your warranty regardless?
2. Followup question, if i root and the knox flag is tripped, will it affect me on t mobile 6 months from now when i want to upgrade since i have JUMP?
3. Is the rom flashing and recovery flashing the same as always or has anything important changed?
4. Would you recommend I root now or just hold off?
Thank you in advance.
thehobs94 said:
So i bought a Note 3 and as I do with all my devices i want to root it, but i am hearing some news things like Knox and alternate root methods.
I have some questions.
1. With knox i understand it voids your warranty if you root, but doesnt rooting always void your warranty regardless?
2. Followup question, if i root and the knox flag is tripped, will it affect me on t mobile 6 months from now when i want to upgrade since i have JUMP?
3. Is the rom flashing and recovery flashing the same as always or has anything important changed?
4. Would you recommend I root now or just hold off?
Thank you in advance.
Click to expand...
Click to collapse
I can answer number one for you, since yes it does void it no matter what but each flash you do adds to a counter in the phone. Most phones you can just reset it to zero and I believe most roms do flip it back to zero, so they can't see it was rooted. Now with knox efuse the number goes 0x0 to 0x1 and right now you can't reset it and it sounds like you may not be able to ever. I do remember seeing a way to root and not flip it but the moment you do a custom rom it's all over.
With the jump program I don't even think they will look at the phone past does it turn on and is it beat to hell or not, I think the jump program is stupid but that is just me. It's like renting to me. But in short yeah samsung is a ****.
[SIZE=+1]There seems to be a lot of confusion and misunderstanding circling the forums with regards to Knox and the 4.3 OTA.
This is an attempt to clear things up[/SIZE]
UPDATE: It seems that people can find this thread, but are unable to actually READ the information presented. The most important note here is that if you are on 4.3 firmware, you can flash ANY rom you like. No, you are not tied down or locked into stock only or 4.3 roms only. AOSP roms will work fine as well. Now scroll down and READ EVERYTHING IN THIS FIRST POST.
What is Knox? Knox is both a firmware and a software component. The OS has Knox apps, and the MK3 bootloader has a Knox component too. Having Knox apps does not necessarily mean you have the Knox bootloader, or vice-versa.
How does Knox work? Because Knox is both in the OS (apps) and in the firmware (bootloader) it works in two ways. The OS components prevent attempts to obtain root access and make rooting with these Knox apps a pain in the butt. Fortunately they can be removed. In the firmware component (bootloader), Knox works to prevent the flashing of custom kernels and recoveries. If you flash a custom rom or custom recovery WHILE on the Knox bootloader, your Knox flag will be tripped and your Warranty Bit will go from 0x0 to 0x1. The Knox bootloader cannot be downgraded to, say, the MD4 bootloader because of special protections built into it. If you attempt to downgrade it, your phone will instantly brick.
Can I get root on the Knox-enabled update? Yes. For those of us who DID NOT take the official OTA and DO NOT have the Knox bootloader, we can get root on 4.3 by injecting it and removing the Knox apps. For those WITH the Knox bootloader, you will need to wait until a full stock MK3 tar is available, which we can then use to make an Odin-flashable MK3 stock rom with root injected using the de-la-vega root method.
Can I downgrade while on 4.3? You can flash roms no matter what Android version they are. That is perfectly fine. But you cannot downgrade the bootloader if you have the Knox bootloader, or else it will cause your bootloader to become corrupted and give you a fancy paperweight. Again, for those who DO NOT have the Knox bootloader, you needn't worry about this/downgrading firmware since the Knox bootloader is what prevents you from doing this. Downgrading your bootloader includes: attempting to flash full stock tar of software versions < MK3, etc.
How can I tell if I've got the Knox bootloader?
Boot into download mode (through custom reboot menu, or by powering off then holding Power+Home+VolumeDown and then VolUp when prompted). If you see a line that starts with the following, then you've got the Knox bootloader. I will insert a picture showing how it actually looks soon
Warranty Bit:
Click to expand...
Click to collapse
[SIZE=+1]READ THIS TOO: http://forum.xda-developers.com/showthread.php?t=1788313
It's for the Verizon S3, but it applies to all the carrier 4.3 updates[/SIZE]
I will add to this as more questions come up
I hope the above helps to clear up some confusion. Ask questions if you are still concerned and I will do my best to answer them.
is there any way to make this a sticky @kennyglass123
This is great information man!
http://i.imgur.com/qrByUGN.jpg
[Q] For now, once you have Knox you'll always have knox? What's the possibility of removing Knox?
elephant007 said:
[Q] For now, once you have Knox you'll always have knox? What's the possibility of removing Knox?
Click to expand...
Click to collapse
as of right now none.
elephant007 said:
[Q] For now, once you have Knox you'll always have knox? What's the possibility of removing Knox?
Click to expand...
Click to collapse
No way to remove bootloader Knox ATM.
I've seen several posts mention "tripping KNOX" or "voiding KNOX." What does that mean, exactly, regarding rooting a phone? Does it just mean it voids the warranty if you need to get support from Samsung/Sprint? Or are there other adverse effects?
Mostly just a visible warranty void.
Samsung bought crapple disease. So sad, but its my excuse to buy a nexus.
Sent from my SPH-L710 using xda app-developers app
As said above, a voided Knox is mostly just a highly visible warranty void. Your local Sprint store may or may not care, or the specific Samsung rep that you deal with may not care, but it's easier just to not have to deal with it to begin with.
Does this mean there is already a touchwiz 4.3 ROM we can flash or do we still have to wait?
Sent from my SPH-L710 using Tapatalk
The biggest thing here is the fact that there is no full tar file to restore. So even if you do not care about knox or warranty. If something goes wrong with a flash or anything else you can't use an older tar file let's say MD4 or LJ7 or anything because you will end up with a brick. There is nothing to use to ODIN restore your device. Once you go 4.3 with Knox you have to stay 4.3 and even if you wanted to stay 4.3 and wanted to restore that there is no tar file at this time.
Have a great day!
I have a question I think we talked a bit about the problems the knox bootloader brings into the system. My question is the opposite what does it fix / change?
Im thinking along the lines of somebody modding the update so an old bootloader would be with the new rom would that be an issue? I think i remember hearing something about wifi being the problem but any clarification would be nice.
docnas said:
I have a question I think we talked a bit about the problems the knox bootloader brings into the system. My question is the opposite what does it fix / change?
Im thinking along the lines of somebody modding the update so an old bootloader would be with the new rom would that be an issue? I think i remember hearing something about wifi being the problem but any clarification would be nice.
Click to expand...
Click to collapse
Late to the party. CNexus already has a update cooking.
Sent from my SPH-L710 using Tapatalk
the question im trying to ask is what do we lose if we use the old bootloader? any functionality? (besides the knox security bull$hit)
docnas said:
the question im trying to ask is what do we lose if we use the old bootloader? any functionality? (besides the knox security bull$hit)
Click to expand...
Click to collapse
Right now, wifi is broken with the old bootloader and 4.3 rom...happened on the other devices too (tmo s3 and sprint s4)
But there is a fix: flash at&t kernel. But it messes up screen rotation. So i'm trying to come up with another fix that will let wifi turn on properly and let screen rotation work properly too
You = rock. Or some other awesome thing.
Sent from my SPH-L710 using xda app-developers app
CNexus said:
Right now, wifi is broken with the old bootloader and 4.3 rom...happened on the other devices too (tmo s3 and sprint s4)
But there is a fix: flash at&t kernel. But it messes up screen rotation. So i'm trying to come up with another fix that will let wifi turn on properly and let screen rotation work properly too
Click to expand...
Click to collapse
So is this Knox a Sprint thing, or a Samsung thing?
I can understand the reasoning for Knox(money) but, dang, I guess it's a dog eat dog world out there.
This doesn't affect CyanogenMod does it? I'm scared...
edit... I remember reading about a brick api or command, I never executed it, sounds nasty, is this what they use to brick peoples phones if they try to "hack" it?
Edge-Case said:
So is this Knox a Sprint thing, or a Samsung thing?
I can understand the reasoning for Knox(money) but, dang, I guess it's a dog eat dog world out there.
This doesn't affect CyanogenMod does it? I'm scared...
edit... I remember reading about a brick api or command, I never executed it, sounds nasty, is this what they use to brick peoples phones if they try to "hack" it?
Click to expand...
Click to collapse
This would be a we-can't-update-the-bootloader thing lol. And we can't do that because it has Knox, which is Samsung's doing
This shouldn't affect any AOSP roms because it uses a different kernel and builds its own WiFi libs
docnas said:
the question im trying to ask is what do we lose if we use the old bootloader? any functionality? (besides the knox security bull$hit)
Click to expand...
Click to collapse
From what I've read Knox is Samsung's attempt to provide strong security to their phones for the enterprise customers. As you can imagine, allowing system level access to files can be used to get around a lot of security measures that IT people would like to enforce in their client's devices. It makes sense at the enterprise level, but it's a pain for anyone who want's to mod their phone.
So I think the answer to your question is, unless you are using your phone in a locked down corporate environment then there really is no advantage to Knox. Too bad it can't be turned off, at least not officially.
Phone was lost, just got replacement this morning.
My last S4 had been rooted running custom firmware for months w/o issue.
Read through a bunch of threads, ranging from the opinion that the bootloader change + knox wont be a big issue to the sky is falling.
Is it recommended to root my phone at this time, I do have JUMP and would be replacing it once something better comes out? The phone is running 4.2.2, caught it trying to update to already.
Thanks.. I know this may seem redundant but haven't been active on these boards since I got my CFW going. Not seeking help in flashing or anything.. just advice
skrewler said:
Phone was lost, just got replacement this morning.
My last S4 had been rooted running custom firmware for months w/o issue.
Read through a bunch of threads, ranging from the opinion that the bootloader change + knox wont be a big issue to the sky is falling.
Is it recommended to root my phone at this time, I do have JUMP and would be replacing it once something better comes out? The phone is running 4.2.2, caught it trying to update to already.
Thanks.. I know this may seem redundant but haven't been active on these boards since I got my CFW going. Not seeking help in flashing or anything.. just advice
Click to expand...
Click to collapse
Up to you. If the stock rom is bearable and you wanna run the 4.3 stock rom then by all means, go for it.
skrewler said:
Phone was lost, just got replacement this morning.
My last S4 had been rooted running custom firmware for months w/o issue.
Read through a bunch of threads, ranging from the opinion that the bootloader change + knox wont be a big issue to the sky is falling.
Is it recommended to root my phone at this time, I do have JUMP and would be replacing it once something better comes out? The phone is running 4.2.2, caught it trying to update to already.
Thanks.. I know this may seem redundant but haven't been active on these boards since I got my CFW going. Not seeking help in flashing or anything.. just advice
Click to expand...
Click to collapse
Being that your'e using the T-Mobile M919, the whole KNOX bootloader situation doesn't pertain to you as long as you're sure you're on 4.2.2. Root it, flash it, theme it with Hello Kitty... whatever, it doesn't matter; you can still revert back to stock and reset any tripped counters. 4.3 is when the problems begin and the KNOX counter is implemented and can't be reset.
lordcheeto03 said:
Being that your'e using the T-Mobile M919, the whole KNOX bootloader situation doesn't pertain to you as long as you're sure you're on 4.2.2. Root it, flash it, theme it with Hello Kitty... whatever, it doesn't matter; you can still revert back to stock and reset any tripped counters. 4.3 is when the problems begin and the KNOX counter is implemented and can't be reset.
Click to expand...
Click to collapse
I second this.
SO LONG AS YOU ARE ON 4.2.2
- You can root flash do whatever, theme with hello kitty or barbie xD like lordcheeto said or keep it stock
- Install recovery and flash away.
- Will always be able to revert back to 100 percent stock
TAKE 4.3 UPDATE
- I think you are still able to root it without tripping knox counter. Can't remember the last status of that was. But as long as you root it without a custom recovery, i think you are ok. From what i can remember, the bootloader checks the recovery status and trips the knox counter based off the recovery that is on the device. If its different then stock, it trips. But double check with Google about this first.
- If you trip knox counter, you will NEVER (as of now and possibly forever) get it back to zero.
Rooting with safe root won't trip knox and also disables it. But recoveries, kernels, roms, etc will trip the flag
Sent from my SGH-M919 using Tapatalk
Root it with chain fire and never look back.
You're on 4.22, so you're golden. Just flash a rooted stock ROM that's on 4.3 and you'll avoid Knox.
I'm running 4.4.2 and never seen this Knox stuff.
Sent from my SGH-M919 using XDA Premium 4 mobile app
elesbb said:
- I think you are still able to root it without tripping knox counter. Can't remember the last status of that was. But as long as you root it without a custom recovery, i think you are ok.
Click to expand...
Click to collapse
ShinySide said:
Rooting with safe root won't trip knox and also disables it. But recoveries, kernels, roms, etc will trip the flag
Click to expand...
Click to collapse
Correct. I've rooted my my second GS4G on 4.3 MK2 and it did not trip the KNOX counter. If you're still on 4.2.2 MDL, then there is no need to update your bootloader. Simply flash ROMs through recovery and flash the 4.3 modem. You will have the goodness of 4.3 on KNOX-less 4.2.2 bootloader. :highfive:
I'm thinking of upgrading from my GS3, non lte, to the Note 3. As I've looked around the forms here, it would seem as though Knox is an added security measure so t-mobile can more easily detect root?
Is there a way to have root without tripping this counter? Is there a way to flash a custom Rom or kernel without tripping it?
If this has been answered apologize, I did look around before making new thread.
Thanks!
Also on a side note, white or black note 3?
t3tr1s_ said:
I'm thinking of upgrading from my GS3, non lte, to the Note 3. As I've looked around the forms here, it would seem as though Knox is an added security measure so t-mobile can more easily detect root?
Is there a way to have root without tripping this counter? Is there a way to flash a custom Rom or kernel without tripping it?
If this has been answered apologize, I did look around before making new thread.
Thanks!
Also on a side note, white or black note 3?
Click to expand...
Click to collapse
Knox isn't really for T-mobile to detect root/custom firmware but for Samsung warranty. A fair amount of people on here have stated that they still sent their phones in to Sammy for warranty and they still got their phones fixed. T-mobile really only look for cracked screens, water damage and that the phone powers on and boots up. Not to say you'll never have an issue but i would say it's not really that big of a deal to trip the Knox counter. Especially if you bought the insurance like Asurion. I don't think they even care if your rooted and ROM'd
Awesome. My concern here is that I would be disqualified from the jump program... I'd like to get the Note 4 as soon as it comes out.. Is there currently any way to root and flash a room without tripping Knox? Or can we only root without tripping Knox?
Before this gets locked, yes you can root without tripping knox. As mentioned knox is for samsung to deny repairs if they see fit (if the phone is sent to them). Tmobile could care less if the phone is rooted or not. You just have to be careful about warranty repairs for samsung, thats what they may or may not look at.
t3tr1s_ said:
Awesome. My concern here is that I would be disqualified from the jump program... I'd like to get the Note 4 as soon as it comes out.. Is there currently any way to root and flash a room without tripping Knox? Or can we only root without tripping Knox?
Click to expand...
Click to collapse
On the old 4.3 firmware yes you can root with Root De La Vega and not trip the Knox counter but once you put ANY custom recovery it will trip the counter. Now on the OTA 4.4.2 that was released on Wednesday, the only 2 current ways to root (TWRP or Philz CWM) will trip the Knox counter no matter what. So until something comes out like an updated ROOT De La Vega, there's no way to even root without tripping the Knox counter.
Also from what i read, RDLV isn't being developed anymore so unless they decide to do something with it for the all the 4.4.2 releases hitting phones these days there may not be anything for a bit to root without tripping knox.
Jfree3000 said:
Before this gets locked, yes you can root without tripping knox. As mentioned knox is for samsung to deny repairs if they see fit (if the phone is sent to them). Tmobile could care less if the phone is rooted or not. You just have to be careful about warranty repairs for samsung, thats what they may or may not look at.
Click to expand...
Click to collapse
That is true for 4.3 but so far you can't on 4.4 from everything I have seen. Do you now of a way to not trip knox on 4.4?
Jfree3000 said:
Before this gets locked, yes you can root without tripping knox. As mentioned knox is for samsung to deny repairs if they see fit (if the phone is sent to them). Tmobile could care less if the phone is rooted or not. You just have to be careful about warranty repairs for samsung, thats what they may or may not look at.
Click to expand...
Click to collapse
Did I miss something? Is there a way to Root 4.4.2 without tripping Knox? I don't care I've tripped Knox the first night i had my N3 but I didn't think there was a way. Kningo and RDLV i thought borked the phones and caused bootloops.
My t-mobile store says that if you root your phone then it voids your warranty, so obviously they won't allow me to upgrade... So I know they check for it.. How is it you guys have stores where they don't seem to care?