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.
Well, I have a Note 3 and the only thing I have done is root it, I did not trip the knox counter, made sure of it. It read 0x0. Well today when using my phone it randomly shut off on me while browsing my email and it threw itself into a boot loop.
Nothing I did was able to fix it so at that point I went into kies and did the firmware upgrade to put it back to stock and I was quite surprised when I entered download mode. The knox counter now read 0x1. I went through with the firmware and it didn't fix it. Since the knox counter was tripped at this point I just said screw it and loaded a custom recovery on the device to wipe everything out of it that way including system and data, then tried to flash the stock rom. It didn't work.
I then tried Kies again, didn't work. How is this possible? How do I randomly trip the Knox counter doing nothing and my phone randomly bricks on me? I now am stuck with a paperweight that is out of warranty even though I made sure it was prior to doing anything.
In that many rooted with triggering the knox flag and it didn't prevent them from using their phone, that is not the issue.
You may just have a hardware issue. There are those that might be able to figure it out though.
krelvinaz said:
In that many rooted with triggering the knox flag and it didn't prevent them from using their phone, that is not the issue.
You may just have a hardware issue. There are those that might be able to figure it out though.
Click to expand...
Click to collapse
I thought hardware issue as well, but why did it randomly trip the counter? That's why it is concerning to me.
What method did u use to root.
NOTE 3
BACARDILIMON said:
What method did u use to root.
NOTE 3
Click to expand...
Click to collapse
Root De La Vega
The only things that are supposed to trip the Knox flag with that method are:
Flashing a custom ROM will trip the flag
Flashing a custom Kernel will trip the flag
Flashing a custom Recovery will trip the flag
What recovery did you use did you wipe the system or format the system. If you did the latter you and can get into download mode I would flash the stock ROM with the pit to repartition your memory. I had to do this with my s4
If u have insurance. Moderator edit, discussion or intimation of fraud of any kind is forbidden on XDA...
Sent from my SM-N900T using xda app-developers app
What does this truely mean. I just rooted via ODIN and my flag was tripped 0x1, does the flag geg tripped regardless if you root or install custom roms ?
Sent from my SM-N900T using xda premium
Seriously, there are tons of threads on this. You didn't do any research before rooting your phone?
Once tripped it can't be reset. If you planned on flashing roms, there it's no way around reporting the Knox flag. Now that you have already tripped it, you can't go back.
Whether or not it will effect you depends on how you use your phone, software out hardware issues you may have and if you try to get warrantee repair. For many it it's not a big deal.
I did do my research Im just asking a question maybe there was an update on how to change the void but obviously kot . Thanks anyway. Dont get all hyped thats what xda is for
Sent from my SM-N900T using xda premium
Hi, I got my note 3 recently and all i have done is just root my note 3 so far. but i have been doing some readings. from what i had found is Knox is a software on your phone, i am guessing and this is just a guess if you use the bloatware remover it might delete the knox program and files from your phone. It might trigger a reset on the counter. I remember reading the list of files it deletes, and it delete all of knox files and folder and a bunch of other stuff but you can edit the script to make it only delete the knox. It might delete the counter or reset it. And you can just reinstall it back and see if the counter is back at 0. remember i am just taking a guess here, does any 1 think this might work?
You cannot reset the Knox flag once it had been tripped.
megaearth77 said:
Hi, I got my note 3 recently and all i have done is just root my note 3 so far. but i have been doing some readings. from what i had found is Knox is a software on your phone, i am guessing and this is just a guess if you use the bloatware remover it might delete the knox program and files from your phone. It might trigger a reset on the counter. I remember reading the list of files it deletes, and it delete all of knox files and folder and a bunch of other stuff but you can edit the script to make it only delete the knox. It might delete the counter or reset it. And you can just reinstall it back and see if the counter is back at 0. remember i am just taking a guess here, does any 1 think this might work?
Click to expand...
Click to collapse
Try that and you might blow the efuse they have with removing Knox.
TWEAKED 1.0 NOTE 3
wow didn't know that
megaearth77 said:
wow didn't know that
Click to expand...
Click to collapse
It what chain fire was afraid of and reason why triangle away won't work
TWEAKED 1.0 NOTE 3
krelvinaz said:
Seriously, there are tons of threads on this. You didn't do any research before rooting your phone?
Once tripped it can't be reset. If you planned on flashing roms, there it's no way around reporting the Knox flag. Now that you have already tripped it, you can't go back.
Whether or not it will effect you depends on how you use your phone, software out hardware issues you may have and if you try to get warrantee repair. For many it it's not a big deal.
Click to expand...
Click to collapse
So rude all that extra was not really needed on do your research. You were probably once new to something too
Sent from my SM-N900T using Tapatalk
BACARDILIMON said:
Try that and you might blow the efuse they have with removing Knox.
TWEAKED 1.0 NOTE 3
Click to expand...
Click to collapse
By just deleting Knox? Pretty sure lots of us have removed it by now and not blown any fuse. I deleted it right out of the box and my phone works just fine...
Sent from my SM-N900T using XDA Premium 4 mobile app
Kalm_Traveler said:
By just deleting Knox? Pretty sure lots of us have removed it by now and not blown any fuse. I deleted it right out of the box and my phone works just fine...
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You didn't delete Knox fully or it would not have the counter. Trust me chain fire tried with no success. He has been one of the pioneers in getting things done and could not.
TWEAKED 1.0 NOTE 3
Can someone explain to me what Knox does and why it get's "tripped"?
BACARDILIMON said:
You didn't delete Knox fully or it would not have the counter. Trust me chain fire tried with no success. He has been one of the pioneers in getting things done and could not.
TWEAKED 1.0 NOTE 3
Click to expand...
Click to collapse
I was referring to what I quoted you saying about blowing an e-fuse by removing Knox. I'm not talking about the check component in the bootloader or wherever it's stored - just the software components that are very easily removable, and do not seem to have caused any adverse effects (aside from the arguably undesired Knox 0x1 flag).
---------- Post added at 08:43 PM ---------- Previous post was at 08:37 PM ----------
dinggus said:
Can someone explain to me what Knox does and why it get's "tripped"?
Click to expand...
Click to collapse
It's a component Samsung decided to build into their new phones and Android builds that is allegedly supposed to be helpful for device security, especially when used with a corporate mobile device system.
Currently, if you flash a phone that has Knox installed with non-factory ROM, Recovery software, etc an at-bootup counter is "permanently" tripped indicating that the device has been tampered with.
I put that word in quotes because we all know with enough time and resources someone will surely figure out a way to reset that counter, if not remove it altogether.
SHORT VERSION: it's a piece of garbage that Samsung and Tmo can use to not uphold your warranty (since it technically voids the entire warranty if you flash custom stuff).
Kalm_Traveler said:
It's a component Samsung decided to build into their new phones and Android builds that is allegedly supposed to be helpful for device security, especially when used with a corporate mobile device system.
Currently, if you flash a phone that has Knox installed with non-factory ROM, Recovery software, etc an at-bootup counter is "permanently" tripped indicating that the device has been tampered with.
I put that word in quotes because we all know with enough time and resources someone will surely figure out a way to reset that counter, if not remove it altogether.
SHORT VERSION: it's a piece of garbage that Samsung and Tmo can use to not uphold your warranty (since it technically voids the entire warranty if you flash custom stuff).
Click to expand...
Click to collapse
Guess I'll stay away from Samsung devices then. If I could get a Note 3 that has the camera features and S-Pen, I'd be happy.
Interesting, i got a few question i want to ask. I root my t mobile note 3 recently using the new method that don't trip the knox counter. And i install several apps that require root access. I know if you install custom rom it will trigger the knox, but i won't on my and its still stock at 4.3. My Question is what about apps that require root access? I got ES file explorer, es task manager, game guardian, cachemate for root users free, cpu tuner, and titanium backup, does those trigger the knox? And is efuse short for eletronic fuse? if it is, can't you just replace it to undo the knox?
Apps don't trigger the Knox flag, flashing a kernel roms etc do. Efuse is in the snapdragon processor.
Kalm_Traveler said:
I was referring to what I quoted you saying about blowing an e-fuse by removing Knox. I'm not talking about the check component in the bootloader or wherever it's stored - just the software components that are very easily removable, and do not seem to have caused any adverse effects (aside from the arguably undesired Knox 0x1 flag).
---------- Post added at 08:43 PM ---------- Previous post was at 08:37 PM ----------
It's a component Samsung decided to build into their new phones and Android builds that is allegedly supposed to be helpful for device security, especially when used with a corporate mobile device system.
Currently, if you flash a phone that has Knox installed with non-factory ROM, Recovery software, etc an at-bootup counter is "permanently" tripped indicating that the device has been tampered with.
I put that word in quotes because we all know with enough time and resources someone will surely figure out a way to reset that counter, if not remove it altogether.
SHORT VERSION: it's a piece of garbage that Samsung and Tmo can use to not uphold your warranty (since it technically voids the entire warranty if you flash custom stuff).
Click to expand...
Click to collapse
It voids Samsung warranty not TMOBILE. So ur good for 1 year
TWEAKED 1.0 NOTE 3
Yes, Knox is Samsung thing, T-mo has nothing to do with it and some people already suggested, T-mo doesn't even check Knox flag for replacements etc, at least so far. I asked here before if it's e-fuse and got different answers, so I ask again : are we sure it's e-fuse or we just speculating? The reason is, there was a guy in international forum claiming Samsung reset his Knox flag, which would be not possible with e-fuse. BTW I just updated my old GS3 to 4.3 and it added Knox to it, so I got mad and rooted it to just to delete this stupid Knox, so now how do I check that flag on it? It says custom because is rooted, but where is the Knox flag?
You see the Knox setting when you put your phone in download mode.
As for resetting the Knox flag, I've not seen a confined resetting of it or better said, if it can be done, no one outside of Samsung has been able to do it and prove they have.
So I've been searching around and have not found out the answer to these questions... I'm assuming the answer is "Yes" to the first but want to confirm:
If the KNOX flag is tripped, the KNOX software will no longer work. Ever (assuming we never get a 0x0 reset). Correct?
Now for the next question, assuming "No":
If I use the RDLV to root without tripping KNOX, will the KNOX software still work?
I ask because my company does have MDM and supports KNOX and I may want to use it in the future.
I am apparently one of 3 people who actually use Knox... Is there a way to get root without tripping the Knox counter? There are two methods listed in the One-Stop Shop thread, but it looks like both of them disable Knox. Any and all help would be greatly appreciated!
Edit: Forgot to mention that I am on the latest AT&T OTA (MK6). I have flashed plenty of times before, just trying to keep Knox on this phone since it is fresh from warranty service.
Delete.....
I'm gonna go out on a limb here...and say that the root binary...will be detected by knox....even if the root attempt does not trip the counter...
The rom will detect root and flag you constantly...
And here is the bigger problem in my mind...
If you manage to root...without tripping the knox counter...and you use the device normally...
If/when the day comes you need service....the bootloader flash counter will still show a custom binary flash count even though knox does not...and if you attempt to unroot....you will never be able to return to full stock with the official 4.3 loader....(gasping for air )...LOL
Long story short...
Root and Knox do not get along...and your warranty will be gone even if Knox and it's container remain intact...
Leave it stock...IMHO...g
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Okay so i got the g920 p today, rooted with pingpong root method and the knox is 0x0 cool. My question i have is if i twrp with odin will it trip the knox? I know on my old note 2 it never did but i was 4.1.1 bootloaders forever lol. Any help with this would,be great. Im a flash a,holic and came from att to sprint.
Side question i have is if in fact the knox trips is/will there be a way to reset the counter? Triangle away,worked for me on the s5, s4 and note 2 when accidntally happened. Wouldnt uninstaling knox keep it from tripping or what about disabling it? My bad for noob questions lol
if i twrp with odin will it trip the knox
--yes
is/will there be a way to reset the counter
--not currently/maybe (doubtful)
Wouldnt uninstaling knox keep it from tripping or what about disabling it?
--no, the OS level components have little to do with the KNOX bit baked into the boot loader.
Triangle away,worked for me
--Triangle away only resets the soft counters (ie flash counter). I don't believe it resets the binary flag.
From other reports the KNOX bit doesn't matter for warranty stuff.
Thanks. I found that flashfire lets me do the same as twrp minus the custom stuff aosp and the like.