Hi Friends,
I am coming from a Sprint Note 3, last ROM activity more than 6 months ago. I now want to use to a GSM provider, thus I bought the T-Mobile Note 3, and am ready to get it rooted and etc.
But one simple question, in case something is changed in the last 6 months:
There is NO WAY, on Tmo Note 3, to install a Custom ROM, Recovery, and/or themes WITHOUT tripping the Knox counter, correct?
I only ask because I thought in the ATT version they're able to use Safe Strap or something...
Thank you!
re: knox
ProFragger said:
Hi Friends,
I am coming from a Sprint Note 3, last ROM activity more than 6 months ago. I now want to use to a GSM provider, thus I bought the T-Mobile Note 3, and am ready to get it rooted and etc.
But one simple question, in case something is changed in the last 6 months:
There is NO WAY, on Tmo Note 3, to install a Custom ROM, Recovery, and/or themes WITHOUT tripping the Knox counter, correct?
I only ask because I thought in the ATT version they're able to use Safe Strap or something...
Thank you!
Click to expand...
Click to collapse
If your new Tmobile Note 3 has not been upgraded to Android 4.4.2
and your baseband it "N900TUVUBMI7" then you are in luck!
If the above is true then your note 3 has not caught the knox pox yet
and never will unless you upgrade your firmware for a newer version.
What this means is that you can root, install any themes and any custom roms
and you will not catch the knox pox, the android jellybean 4.3 N900TUVUBMI7
firmwares and stock or custom roms do not include knox in the firmware like
Kitkat 4.4.2 NB4 and NE6 updates do.
On the tmobile note 3 its super easy to root, flashing
custom roms and installing/flashing themes.
The tmobile note 3 has no safe-strap or anything like it.
Rooting is a straight forward thing which could not be
easier.
The only way to keep the knox away is not to upgrade to android 4.4.2 NB4 (or newer)
and keep the original jellybean 4.3 with baseband of N900TUVUBMI7 which hopefully
came with your new phone.
You can check the baseband easily, just go into settings and find the "About Device"
and scroll down until you see baseband and see if it's N900TUVUBMI7.
When I first bought my new note 3 it had the N900TUVUBMI7 baseband.
There is not enough difference or improvement in any of the updates available now
for someone who is really worried about warranty issues.
Once you catch knox there is no way to remove or disable it.
Personally I could care less about knox but that's just me.
Good luck!
Misterjunky said:
If your new Tmobile Note 3 has not been upgraded to Android 4.4.2
and your baseband it "N900TUVUBMI7" then you are in luck!
If the above is true then your note 3 has not caught the knox pox yet
and never will unless you upgrade your firmware for a newer version.
What this means is that you can root, install any themes and any custom roms
and you will not catch the knox pox, the android jellybean 4.3 N900TUVUBMI7
firmwares and stock or custom roms do not include knox in the firmware like
Kitkat 4.4.2 NB4 and NE6 updates do.
On the tmobile note 3 its super easy to root, flashing
custom roms and installing/flashing themes.
The tmobile note 3 has no safe-strap or anything like it.
Rooting is a straight forward thing which could not be
easier.
The only way to keep the knox away is not to upgrade to android 4.4.2 NB4 (or newer)
and keep the original jellybean 4.3 with baseband of N900TUVUBMI7 which hopefully
came with your new phone.
You can check the baseband easily, just go into settings and find the "About Device"
and scroll down until you see baseband and see if it's N900TUVUBMI7.
When I first bought my new note 3 it had the N900TUVUBMI7 baseband.
There is not enough difference or improvement in any of the updates available now
for someone who is really worried about warranty issues.
Once you catch knox there is no way to remove or disable it.
Personally I could care less about knox but that's just me.
Good luck!
Click to expand...
Click to collapse
Misterjunky, thank you SO MUCH for the very informative post! Unfortunately, the previous owner of the phone did upgrade to NB4, so it looks like I am quite screwed?
With that said, even if I do go around the Knox trip by Kies update to NE4, and then using TowelRoot, I don't suppose there is anyway to keep the Knox count to 0x0, and still get the Custom Recovery installed for ROMs and Themes, correct?
Thank you again! LOL!
Misterjunky said:
If your new Tmobile Note 3 has not been upgraded to Android 4.4.2
and your baseband it "N900TUVUBMI7" then you are in luck!
If the above is true then your note 3 has not caught the knox pox yet
and never will unless you upgrade your firmware for a newer version.
What this means is that you can root, install any themes and any custom roms
and you will not catch the knox pox, the android jellybean 4.3 N900TUVUBMI7
firmwares and stock or custom roms do not include knox in the firmware like
Kitkat 4.4.2 NB4 and NE6 updates do.
On the tmobile note 3 its super easy to root, flashing
custom roms and installing/flashing themes.
The tmobile note 3 has no safe-strap or anything like it.
Rooting is a straight forward thing which could not be
easier.
The only way to keep the knox away is not to upgrade to android 4.4.2 NB4 (or newer)
and keep the original jellybean 4.3 with baseband of N900TUVUBMI7 which hopefully
came with your new phone.
You can check the baseband easily, just go into settings and find the "About Device"
and scroll down until you see baseband and see if it's N900TUVUBMI7.
When I first bought my new note 3 it had the N900TUVUBMI7 baseband.
There is not enough difference or improvement in any of the updates available now
for someone who is really worried about warranty issues.
Once you catch knox there is no way to remove or disable it.
Personally I could care less about knox but that's just me.
Good luck!
Click to expand...
Click to collapse
Wow thanks so much i was looking for information and i was so lost.
I have the exact baseband and 4.3 . So how can i root it? I'm lost with which one cf auto root, de la vega, kingo etc. which one do you think is better for me? . my last cellphone is a note 2 from verizon. But it was so easy to root it. And the note 3 with all the stuff with knox is exploding my head x_X
I want to root because i'm in DR and i need to sim unlock the phone via region lock away, and i want to update to kitkat without any problem but with my root
Edit: i used Towelroot new root method by geohot and it worked!!!!! really awesome and fast. i used the region lock away it worked too. Now i just want to upgrade to kk without loosing my sim lock :L, any recommendations?
re: root/knox
ProFragger said:
Misterjunky, thank you SO MUCH for the very informative post! Unfortunately, the previous owner of the phone did upgrade to NB4, so it looks like I am quite screwed?
With that said, even if I do go around the Knox trip by Kies update to NE4, and then using TowelRoot, I don't suppose there is anyway to keep the Knox count to 0x0, and still get the Custom Recovery installed for ROMs and Themes, correct?
Thank you again! LOL!
Click to expand...
Click to collapse
Upgrading the firmware/rom to a newer than NE4 or NE6 using Kies or Odin
will NOT touch the KNOX counter but it will still get KNOX if you root the
phone and flash custom roms and or kernels.
Any other rooting method beside cd-autoroot is just asking for trouble.
Unfortunatly we cannot downgrade to jellybean 4.3
There is a complicated way to ROOT NB4/NE4/NE6 official Samsung firmware
without tripping the Knox counter, but it's complicated and even after successful
root you still will not be able to flash custom roms, recoveries or kernels without
tripping the KNOX counter.
Here is a link in case you are interested in "Root De La Vega" which has step
by step instructions how to use Root De La Vega to get root access without
tripping the Knox counter:
http://forum.xda-developers.com/showthread.php?t=2479952
Good luck!
---------- Post added at 04:30 PM ---------- Previous post was at 04:19 PM ----------
Steph4n said:
Wow thanks so much i was looking for information and i was so lost.
I have the exact baseband and 4.3 . So how can i root it? I'm lost with which one cf auto root, de la vega, kingo etc. which one do you think is better for me? . my last cellphone is a note 2 from verizon. But it was so easy to root it. And the note 3 with all the stuff with knox is exploding my head x_X
I want to root because i'm in DR and i need to sim unlock the phone via region lock away, and i want to update to kitkat without any problem but with my root
.
Click to expand...
Click to collapse
Here is the direct download link for the proper cf-autoroot for Note 3 N900T.
http://download.chainfire.eu/354/CF-Root/CF-Auto-Root/CF-Auto-Root-hltetmo-hltetmo-smn900t.zip
1: Unzip this zip file into a NEW folder on your windows desktop.
2: Be sure you have the Samsung USB driver installed in your computer.
3: Open odin and put the cf-autoroot file in the PDA slot in odin.
4: Power down the phone.
5: Plug the USB cable from computer to your phone.
6: You should see the [com:xx] in odin change colors
7: Click RUN in odin
8: It usually takes about 5 minutes for it to flash, after it's successful the phone reboots.
That's all there is to rooting.
Good luck!
Related
I'm currently using stock MF6 firmware and there is no indication of the Knox warranty void flag in download mode. Does anyone know which firmware introduced this flag on the S4 mini or is it not implemented, yet? I'm asking because I want root access and need to know which prerooted firmwares I can choose from without this flag.
kodan2k said:
I'm currently using stock MF6 firmware and there is no indication of the Knox warranty void flag in download mode. Does anyone know which firmware introduced this flag on the S4 mini or is it not implemented, yet? I'm asking because I want root access and need to know which prerooted firmwares I can choose from without this flag.
Click to expand...
Click to collapse
As far as I can tell, there's no Knox flag known on any S4 mini firmware or variant. Definitely mine has no sign of it either. And from what I read, at least ith the S4 it was never transparent, only when the flag appared could you kill it, in older firmwares no matter what you did the flag was never set until you upgraded and there was something considered wrong then.
4.4 is supposed to bring Knox for the mini so it may bring the flag, which could be easier, harder or the same to avoid as the S4, only time will tell I guess. If it's similar, hopefully enough will have been learnt by the time S4 mini get 4.4 that we can easily get around it.
@Nil Einne
Thank you for your reply. Which firmware version are you using?
(I9195XXUA)MG3 (which is 4.2.2 / JDQ39). It's currently the latest for my CSC. I may root soon perhaps using a prerooted firmware (since mine is so old) but I'm waiting to see if anyone has tried it on a 16GB version. I didn't mention before but I guess it's clear now I have an I9195 but I haven't seen any mention of Knox flag seen for any variant of the S4 mini on current firmwares.
My s4 mini (I9195) came with firmware MF7 and was upgraded OTA to MG8.
After that I flashed with Odin to MH2 (Android 4.2.2).
Thereafter I flashed a custom rom (Slim with 4.3.1).
Where and how can I see whether my Knox warranty void might be 0x1 now.
And what if I flash back with Odin to firmware MF7?
Is that still possible without a later upgrade problem?
Curious about your info.
New Rom XXUBMJ7 whit KNOX bootloader (aboot.mbn) and aplications.
After flash this Rom we have on Download Mode:
KnoxKernelLock: 0x0
KnoxWarrantyVoid: 0x0
Like on Note 3 N9005, if we flash something, customer, root, KnoxWarrantyVoid: go to 0x1 and this is not reversible.
To Root
The Root-Kit-V1 install all superuser, SU and busybox but after reboot the SuperSU can't access to system, KNOX not permit.
To solve this we must flash after, on recovery the UPDATE-SuperSU-v1.65.zip from Chainfire. After we have root alright.
My case like on Note 3:
I not need the KNOX, the phone is only for me, then after root I delete all KNOX apk + odex from system/app.
Good luck
Is it possible to go back to old bootloader WITHOUT knox?
ladislav.heller said:
Is it possible to go back to old bootloader WITHOUT knox?
Click to expand...
Click to collapse
See response on Development Thread to this your question.
Always the KNOX:
You can read this post Always the KNOX.
Many info about KNOX.
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:
Hello,
Seeing how future updates to the Note 3 supposedly causes the knox warranty void flag to be tripped for rooting with RDLV... Is it a good idea to root our devices now while we can? As in, rooting before one of these updates will both keep root on the device and have knox warranty flag 0x0 after updating to kitkat?
Bumping! I suppose it would be easy for Samsung to release an update that triggers knox counter if root is detected... I've never rooted a device though. So my question is do phones keep root when you receive an android update?
If you are rooted, you normally don't want an update over the air. There so far have been no updates to the T-Mobile version of the note 3 though.
Well I was wondering about that as well. I keep reading that the Tmo Note 3's bootloader is unlocked. If it is truly unlocked would it not matter to take updates as we should be able to continue to root and put a custom recovery back on the phone? I mean i personally would wait to know if it is safe to take an OTA before actually taking it. I came from the VZW S4 which had that crazy locked down bootloader after the 1st OTA (I luckily never took an OTA and it's on the original FW). I mean I guess they can always lock down a bootloader on any OTA but why would they if it came already unlocked?
All the ota does is download via wifi or data for the update...that is the only difference... it doesn't do any extra checking or anything like that. The only thing that will happen is after the update has been downloaded it will flash your phone and then it will erase root because it will be flashing the phone back to a stock new firmware. You then would have to root your phone again.
Sent from my SM-N900T using XDA Premium 4 mobile app
re: rooting
Dreamgun said:
Bumping! I suppose it would be easy for Samsung to release an update that triggers knox counter if root is detected... I've never rooted a device though. So my question is do phones keep root when you receive an android update?
Click to expand...
Click to collapse
If you are rooted and you accept an OTA or KIES update or if you Odin flash official
stock firmwareyou will lose root but you can root the phone again if you want.
Fortunately all the cwm/twrp flashable custom roms found here in XDA
all come pre-rooted and if you flash one of those you will not lose root.
Either way you will trigger the KNOX if you flash kernels, custom roms or custom recoveries.
The only two things that KNOX does is it prevents you from downgrading to an older version
of the rom and or firmware as well as the possibility of voiding your warrany if you have one.
Good luck!
Hi I'm still on 4.3 MI7, should i update to 4.4? I've heard people saying in the forums that 4.3 is still better. what would you suggest? I just want to root either way i end up going. My pervious note 3 was rooted through ODIN with knox tripped, but when i got my replacement i never rooted it so I'm stock right now. If i stay on MI7 would i be able to use towel method to root? From my understanding NE6 would work with towel method but wasn't sure with MI7. What are some pros or cons to updating to 4.4? Any help would be useful
P.S. if i do update why would be the easiest way to keep all my data, apps , ext.. thanks in advance ~CANGOODZ~
I'm holding off as well. I'm waiting for confirmation that there is a safe way to roll back. Once I see that, I may go for it.
In the interim, I've been considering Darth stalker as a ROM.
Sent from my SM-N900T using Tapatalk
I would want to remain stock without custom recovery and knox 0x0. Just so I can run some tweaks and tb. I ran wicked roms and all my previous devices but it seems for the note 3 evil art hasn't been keeping up with his roms. Is anyone able to help me with what I should do about updating and towel root?
I made last night a thread asking a safe way to update MI7 to NE6 (it's what you need for towel root), maybe you want to keep an eye on it too:
http://forum.xda-developers.com/showthread.php?t=2794032
It's really hard to choose between staying in JB or updating to KK but I think I've been on JB enough time
I know we must suffer the perpetually locked bootloader provided by T-Mobile that should not be an issue; however the LP (OB6) bootloader will be able to load NK3, but for Towel Rooting, NE6 was the last Towel Root compatible version based on the research so far, and generally people are recommending to avoid NK3 if Towel Rooting is the goal, so is it possible using ODIN 3.07 to downgrade to NE6 without tripping KNOX on an unrooted OB6 N900T Note 3?
If it is possible to get the result we're looking for, we intend to follow the directions in the following links to root without tripping KNOX to also have the advantages of Lollipop in the end result:
1 - http://forum.xda-developers.com/not...-to-root-nf4-knox-0x0-effortless-nf4-t2846142 (Effortless Root for NK3 that begins with NE6)
2 - http://forum.xda-developers.com/not...icial-lollipop-n900tuvufob5-t-mobile-t3046295 (To go from NK3 to OB6 without rripping KNOX)
We're looking for input from those with experience downgrading from OB6 to NE6, and we've no desire to impose on our ability to use KNOX features by causing KNOX to become altered. We would appreciate the community's thoughts because the sharing of the results from those already having gone through this experience would be greatly appreciated.
Also, should we be using Heimdall to avoid tripping KNOX, or sticking with ODIN 3.07?
Thanks in advance.
I dunno if you still need the help or If this will help but, as long as it is a STOCK ROM FOR THE DEVICE IN QUESTION Odin shouldn't have any issues, but I recommend a backup of the device first (from recovery) just to be on the safe side