Related
hey guys,
I need help asap! I tried using the video on this website to root my tmobile S4. I downloaded Kies, Odin 3.07, ROOT_M919UVUAMDL.zip, and CWM as recovery-clockwork-touch-6.0.3.2-jfltetmo.tar, I did NOT install triangle away( i forgot). I went through the steps and passed in Odin. then, when I pulled the battery and booted in CWM i couldnt find the file so i went to the store to buy a sdcard. when I came home i re-ran through Odin and found the root zip on the external sdcard. I successfully installed the root zip and clicked reboot. my problem arose when it showed a "KERNEL IS NOT SEANDROID ENFORCING" in red, and a "SET WARANTY BIT: KERNEL" in yellow. it seems to be frozen in this screen and i can only use the CWM and Download mode. I have tried re-using Odin .
Please help!!
That's an old root method. You can either
1) flash a custom ROM and go about your business
2) Odin back to stock firmware and root with cf-auto root or towelroot
Sent from my SGH-M919 using Tapatalk
serio22 said:
That's an old root method. You can either
1) flash a custom ROM and go about your business
2) Odin back to stock firmware and root with cf-auto root or towelroot
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
I'm sorry, I'm a Noob. but 1) where can I get a custom ROM and how do i apply it? 2) can you elaborate on your #2?
scott560 said:
I'm sorry, I'm a Noob. but 1) where can I get a custom ROM and how do i apply it? 2) can you elaborate on your #2?
Click to expand...
Click to collapse
1) You can find tons of Custom ROMs here: http://forum.xda-developers.com/galaxy-s4-tmobile/development
You usually flash them to your phone via a Custom Recovery such as CWM or TWRP. Or, is some cases you can use ODIN. Read, Read, Read, Read before your flash. It is very easy to do, but you need to understand what you are doing. All Custom ROMs come pre-rooted.
2) You can download a stock ROM from here:
http://www.sammobile.com/firmwares/
Or, you can use Kies to download and install the most recent firmware for your phone.
TowelRoot is a new option for rooting stock ROMs that are version 4.4.2 (KitKat). This method of rooting doesn't trip the Knox flag.
Here's a video: https://www.youtube.com/watch?v=ZGwMs8JPBhE
Rob
rlichtefeld said:
1) You can find tons of Custom ROMs here: http://forum.xda-developers.com/galaxy-s4-tmobile/development
You flash them to your phone via ODIN. Read, Read, Read, Read before your flash. It is very easy to do, but you need to understand what you are doing. All Custom ROMs come pre-rooted.
2) You can download a stock ROM from here:
http://www.sammobile.com/firmwares/
Or, you can use Kies to download and install the most recent firmware for your phone.
TowelRoot is a new option for rooting stock ROMs that are version 4.4.2 (KitKat). This method of rooting doesn't trip the Knox flag.
Here's a video: https://www.youtube.com/watch?v=ZGwMs8JPBhE
Rob
Click to expand...
Click to collapse
Thanks for replying however, you do not flash custom ROMs via Odin, you need a custom recovery like twrp or cwm.. Stock firmware you do flash via Odin.. And their Knox flag is already tripped, wouldn't matter
serio22 said:
Thanks for replying however, you do not flash custom ROMs via Odin, you need a custom recovery like twrp or cwm.. Stock firmware you do flash via Odin.. And their Knox flag is already tripped, wouldn't matter
Click to expand...
Click to collapse
Thanks for correcting me that most of the time you flash Custom ROMs via a Custom Recovery on the S4.
But, if I'm not mistaken you can flash Custom ROMs via ODIN as long as in the right format and you select the correct partition.
However, most of my Custom ROM history is with a HTC device, so I may be mistaken.
rlichtefeld said:
Thanks for correcting me that most of the time you flash Custom ROMs via a Custom Recovery on the S4.
But, if I'm not mistaken you can flash Custom ROMs via ODIN as long as in the right format and you select the correct partition.
However, most of my Custom ROM history is with a HTC device, so I may be mistaken.
Click to expand...
Click to collapse
It is possible but 99% of custom ROMs are not made to be flashed with Odin, in the past two years I've only seen about 1. And it is also inconvenient
My Note have 4.3 and it's rooted with Kingosoft. KNOX has NOT been trip.
I am wondering if I can upgrade to 4.4.2 and use TowelRoot to root WITHOUT tripping KNOX, as follow:
1. Unroot with Kingosoft (the Windows app is capable of this)
2. Hard reset the phone
3. Obtain 4.4.2 via OTA (or KIES?)
4. Use TowelRoot
re: upgrading
lanwarrior said:
My Note have 4.3 and it's rooted with Kingosoft. KNOX has NOT been trip.
I am wondering if I can upgrade to 4.4.2 and use TowelRoot to root WITHOUT tripping KNOX, as follow:
1. Unroot with Kingosoft (the Windows app is capable of this)
2. Hard reset the phone
3. Obtain 4.4.2 via OTA (or KIES?)
4. Use TowelRoot
Click to expand...
Click to collapse
You don't need to un-root the phone.
#1: Perform a hard reset.
#2: Download and odin flash the official stock N900T Kitkat 4.4.2 NF1 firmware
from http://SamMobile.com or other trusted source. (it will not trip the knox)
#3: Use Towelroot to root the phone.
As you most likely know already you will not be able to flash any custom
recovery like twrp or cwm if you don't want to trip the knox flag which
means that you will not be able to flash any custom roms either.
Good luck!
Towelroot does not work on NF1.
Dam Phone
grose65 said:
Towelroot does not work on NF1.
Dam Phone
Click to expand...
Click to collapse
Really? So is there no way to root a 4.4.2 stock T-Mobile ROM WITHOUT tripping KNOX?
re: towelroot
lanwarrior said:
Really? So is there no way to root a 4.4.2 stock T-Mobile ROM WITHOUT tripping KNOX?
Click to expand...
Click to collapse
Yes, follow the guide I posted, I did make an error about NF1,
however you can download the N900T NE6 4.4.2 firmware from
http://SamMobile.com or other trusted source, then you can use
Towelroot successfully without tripping the knox counter.
Good luck,
Misterjunky said:
Yes, follow the guide I posted, I did make an error about NF1,
however you can download the N900T NE6 4.4.2 firmware from
http://SamMobile.com or other trusted source, then you can use
Towelroot successfully without tripping the knox counter.
Good luck,
Click to expand...
Click to collapse
Thanks, Misterjunky! I'll do the upgrade and will update this thread.
grose65 said:
Towelroot does not work on NF1.
Dam Phone
Click to expand...
Click to collapse
Misterjunky said:
Yes, follow the guide I posted, I did make an error about NF1,
however you can download the N900T NE6 4.4.2 firmware from
http://SamMobile.com or other trusted source, then you can use
Towelroot successfully without tripping the knox counter.
Good luck,
Click to expand...
Click to collapse
Guys, quick question: once I successfully upgraded to 4.4.2 NE6 and root it with Towelroot, I should be able to upgrade to NF1 and root it with MobileOdin Pro following this method, right?
Link 1: http://www.andromods.com/root-unlock/knox-safe-tmobile-galaxy-note-3-nf1-rooted-volte.html
1. Extract the NF1 firmware, then copy the ‘tar.md5′ to your sd card.
2. Run the Mobile ODIN Pro and scroll down to ‘Open file…’.
3. Here’s some options you should enable prior to flashing, ‘inject root’, ‘mobile odin boxes’ and ‘reboot to download mode after flashing’.
4. Once flashing completes and your phone boot into download mode, connect it to your computer.
5. Now run Odin3 desktop version, we use v.3.09 with only the reboot and update bootloader boxes are ticked.
6. In order to make the VoLTE working, you need to reflash the CSC file from NF1 firmware.
Link 2: http://forum.xda-developers.com/showthread.php?p=53574142
You'll want to flash the full firmware through mobile odin pro, tick the inject root and mobile odin boxes, and select reboot to download mode after flashing. Once in download mode, flash the bootloader with regular desktop odin 3.09 with only the reboot and update bootloader boxes checked. No guarantees, but that SHOULD retain knox 0x0 and root.
EDIT: Forgot to ask: how do flash the CSC file? Just select "CSC" from Odin and point to the NF1 firmware?
Quick update: upgraded to NE6 via Odin, run TowelRoot, success! KNOX 0x0! No need to unroot first.
I "chickened" out on upgrading to NF1 with CSC install, though. Seems that there maybe some problem in the long run if I upgrade following my post above. So I'll wait for now.
Tried downgrading too NE6 and Odin says no memory and failed.
Dam Phone
Guys...Im not a total newbie but I have a couple of question. I have my SM-N900T rooted with N900TTMBBMI7..used odin, CF-Root etc etc and its working great...so I have dabbled enough in this so I am a bit dangerous. I have CWM recovery and Titanium backup and can/do make backups before I add any apps, etc.
I would like to upgrade to N900TUVUDNF1 and I have seen that in this thread http://forum.xda-developers.com/showthread.php?t=2761451 there is a deodexed, rooted version by Jovy23 so that is great...I do have a couple of questions I want to be clear on before I start this process :
1) I see that people talk about needing a specific bootloader...do I? Can anyone clarify that for me?
2) I have lots of apps installed on my N900TTMBBMI7 now as you can imagine. Would the process be to install N900TUVUDNF1 with odin as per the instructions and THEN, install Titanium backup and restore my apps? I dont want to spend a lot of time getting the phone back to what I have now if I can avoid it.
3) Will the N900TUVUDNF1 install wipe out my CWM recovery ? Do I need to re-install it after flashing N900TUVUDNF1 ?
4) If something goes really wrong, the process to revert would be to install CWM recovery and restore my N900TTMBBMI7 backup?
Anything else you guys would like to advise me of will be greatly appreciated...
thanks!!
re: NF1 firmware
calderonr said:
Guys...Im not a total newbie but I have a couple of question. I have my SM-N900T rooted with N900TTMBBMI7..used odin, CF-Root etc etc and its working great...so I have dabbled enough in this so I am a bit dangerous. I have CWM recovery and Titanium backup and can/do make backups before I add any apps, etc.
I would like to upgrade to N900TUVUDNF1 and I have seen that in this thread http://forum.xda-developers.com/showthread.php?t=2761451 there is a deodexed, rooted version by Jovy23 so that is great...I do have a couple of questions I want to be clear on before I start this process :
1) I see that people talk about needing a specific bootloader...do I? Can anyone clarify that for me?
2) I have lots of apps installed on my N900TTMBBMI7 now as you can imagine. Would the process be to install N900TUVUDNF1 with odin as per the instructions and THEN, install Titanium backup and restore my apps? I dont want to spend a lot of time getting the phone back to what I have now if I can avoid it.
3) Will the N900TUVUDNF1 install wipe out my CWM recovery ? Do I need to re-install it after flashing N900TUVUDNF1 ?
4) If something goes really wrong, the process to revert would be to install CWM recovery and restore my N900TTMBBMI7 backup?
Anything else you guys would like to advise me of will be greatly appreciated...
thanks!!
Click to expand...
Click to collapse
#1: The NF1 bootloader is part of the official Samsung N900T NF1 Kitkat firmware.
Here is the direct download link for the firmware:
chrome://mega/contenthttp:
https://mega.co.nz/#!ioglFaQD!IzrjOKfoQXnfzTVjItUnjVvqzVSoG4s0wkKLTvit9BY
#2: You will need to restore your apps with titanium backup after odin
flashing the official stock NF1 firmware.
#3: Odin flashing the NF1 firmware will wipe cwm recovery so you will need
to odin flash TWRP recovery which can be found here:
https://dl.dropboxusercontent.com/u/45687485/openrecovery-twrp-2.7.2.0-hltetmo-4.4.img.tar
#4: Before flashing TWRP you will need to odin flash cf-autoroot which
can be found here:
https://dl.dropboxusercontent.com/u/45687485/CF-Auto-Root-hltetmo-hltetmo-smn900t.tar.md5
#5: Once you flash NF1 firmware you cannot revert back to MI7 firmware
it will either bootloop or get stuck on boot screen if you try doing it.
In other words you cannot downgrade the firmware once it's updated to NF1.
Good luck!
Misterjunky said:
#1: The NF1 bootloader is part of the official Samsung N900T NF1 Kitkat firmware.
Here is the direct download link for the firmware:
chrome://mega/contenthttp:
https://mega.co.nz/#!ioglFaQD!IzrjOKfoQXnfzTVjItUnjVvqzVSoG4s0wkKLTvit9BY
#2: You will need to restore your apps with titanium backup after odin
flashing the official stock NF1 firmware.
#3: Odin flashing the NF1 firmware will wipe cwm recovery so you will need
to odin flash TWRP recovery which can be found here:
https://dl.dropboxusercontent.com/u/45687485/openrecovery-twrp-2.7.2.0-hltetmo-4.4.img.tar
#4: Before flashing TWRP you will need to odin flash cf-autoroot which
can be found here:
https://dl.dropboxusercontent.com/u/45687485/CF-Auto-Root-hltetmo-hltetmo-smn900t.tar.md5
#5: Once you flash NF1 firmware you cannot revert back to MI7 firmware
it will either bootloop or get stuck on boot screen if you try doing it.
In other words you cannot downgrade the firmware once it's updated to NF1.
Good luck!
Click to expand...
Click to collapse
Wow, thanks for the quick reply..I am glad you answered because I was totally under the impression that reverting back was indeed possible..I would have been in a wold of hurt if something went wrong and I could not revert since I use this device for work as well. So this of course begs a few more followup questions
1) The firmware at https://mega.co.nz/#!ioglFaQD!IzrjOK...4s0wkKLTvit9BY I assume is NOT rooted and therefore I would have to root with CF-Root etc...correct?
2) What is exactly the bootloader in this context? You are not refering to TWRP/CWM I assume? Is it the built in code to get the startup going? I am familiar with Linux bootloader like LILO and GRUB...is it the same concept?
3) Understood on restoring apps with Titanium backup...you refer only to the official firmware. Are you suggesting that I should not use the stock rooted NF1 I found?
4) Understood that flashing NF1 will wipe out CWM. You state to odin flash TWRP. Does that mean I should NOT use CWM and switch to TWRP? I am more familiar with CWM and I would like to continue using that one if possible.
5) Lastly and more importantly, why will reverting back to MI7 will cause the bootloop or stuck on boot screen? Any solution to that at all?
Again, thanks for your suggestions and quick reply!!
calderonr said:
Wow, thanks for the quick reply..I am glad you answered because I was totally under the impression that reverting back was indeed possible..I would have been in a wold of hurt if something went wrong and I could not revert since I use this device for work as well. So this of course begs a few more followup questions
1) The firmware at https://mega.co.nz/#!ioglFaQD!IzrjOK...4s0wkKLTvit9BY I assume is NOT rooted and therefore I would have to root with CF-Root etc...correct?
2) What is exactly the bootloader in this context? You are not refering to TWRP/CWM I assume? Is it the built in code to get the startup going? I am familiar with Linux bootloader like LILO and GRUB...is it the same concept?
3) Understood on restoring apps with Titanium backup...you refer only to the official firmware. Are you suggesting that I should not use the stock rooted NF1 I found?
4) Understood that flashing NF1 will wipe out CWM. You state to odin flash TWRP. Does that mean I should NOT use CWM and switch to TWRP? I am more familiar with CWM and I would like to continue using that one if possible.
5) Lastly and more importantly, why will reverting back to MI7 will cause the bootloop or stuck on boot screen? Any solution to that at all?
Again, thanks for your suggestions and quick reply!!
Click to expand...
Click to collapse
Be careful who you listen to on xda.
If your knox warranty flag is 0x0 DO NOT follow those instructions if you want it to stay that way.
To check, boot into download mode (reboot with volume+power+voldown.
If it's 0x0 and you want to keep it that way, you'll want to know that if you upgrade, flashing a custom recovery WILL ALWAYS trip knox once your bootloader is on kitkat.
The caveat is that if you want kitcat, you have to upgrade your bootloaders for things to work properly.
Now, with all that out of the way...
I would recommend going up to NF4 (bypassing NF1) as it is the latest.
I have a link in my sig with all the files for NF4 which also contains the upgrade method that doesn't trip knox.
Sent from my leanKernel 3.4 powered stock 4.4.2 (NF4) SM-N900T
---------- Post added at 11:27 AM ---------- Previous post was at 11:16 AM ----------
In case you can't see my sig due to being in xda app or tapatalk:
NF4 files and instructions: http://forum.xda-developers.com/showthread.php?t=2834398
Or if you're dead set on NF1, there's a link to that thread at the top of the NF4 post. The instructions in post 2 of the nf4 thread are valid for nf1 add well.
Sent from my leanKernel 3.4 powered stock 4.4.2 (NF4) SM-N900T
toastido said:
Be careful who you listen to on xda.
If your knox warranty flag is 0x0 DO NOT follow those instructions if you want it to stay that way.
To check, boot into download mode (reboot with volume+power+voldown.
If it's 0x0 and you want to keep it that way, you'll want to know that if you upgrade, flashing a custom recovery WILL ALWAYS trip knox once your bootloader is on kitkat.
The caveat is that if you want kitcat, you have to upgrade your bootloaders for things to work properly.
Now, with all that out of the way...
I would recommend going up to NF4 (bypassing NF1) as it is the latest.
I have a link in my sig with all the files for NF4 which also contains the upgrade method that doesn't trip knox.
Sent from my leanKernel 3.4 powered stock 4.4.2 (NF4) SM-N900T
Click to expand...
Click to collapse
Toastido...Thanks for the reply...I have already tripped the warranty counter so lets say that at this point I am OK with that
So a few questions for you :
1) I am OK going to NF4 and I assume that the files/links you pointed me to below will still work on a tripped knox flag? Correct?
2) Does the same apply that if I go to NF4 there is no way to revert back to MI7?
3) Does your NF4 upgrade link/instructions contain the bootloader needed ? I assume so but want to make sure just in case I need anything else other than what you pointed me to. I am asking this because you stated "if you want kitcat, you have to upgrade your bootloaders for things to work properly. "
4) Can I continue to use CWM or do I have to switch to TWRP?
5) What about rooting? Is your firmware rooted or do I need to do it myself? If so, what do you recommend for rooting?
Thanks!!!
calderonr said:
Toastido...Thanks for the reply...I have already tripped the warranty counter so lets say that at this point I am OK with that
So a few questions for you :
1) I am OK going to NF1 and I assume that the files/links you pointed me to below will still work on a tripped knox flag? Correct?
2) Does the same apply that if I go to NF1 there is no way to revert back to MI7?
3) Does your NF1 upgrade link/instructions contain the bootloader needed ? I assume so but want to make sure just in case I need anything else other than what you pointed me to. I am asking this because you stated "if you want kitcat, you have to upgrade your bootloaders for things to work properly. "
4) Can I continue to use CWM or do I have to switch to TWRP?
Thanks!!!
Click to expand...
Click to collapse
Hey!
1) yes. I'd recommend just flashing the full package in desktop odin in that case. Power of your device completely for 10 to 30 seconds then boot directly to download mode.
2) yes. Once you go up from jb to kk you cannot go back. This is due to bootloader update efuses.
3) yes they do.
4) you can use cwm if you want, just make sure to get the correct one. Usually they are tagged kk or 4.4. Using jb versions will no longer work.
I assume you meant nf4, but the same applies to either.
Sent from my leanKernel 3.4 powered stock 4.4.2 (NF4) SM-N900T
toastido said:
Hey!
1) yes. I'd recommend just flashing the full package in desktop odin in that case. Power of your device completely for 10 to 30 seconds then boot directly to download mode.
2) yes. Once you go up from jb to kk you cannot go back. This is due to bootloader update efuses.
3) yes they do.
4) you can use cwm if you want, just make sure to get the correct one. Usually they are tagged kk or 4.4. Using jb versions will no longer work.
I assume you meant nf4, but the same applies to either.
Sent from my leanKernel 3.4 powered stock 4.4.2 (NF4) SM-N900T
Click to expand...
Click to collapse
Yeap...I meant NF4 and I sent in an edit but you beat me to it..ok...I will give this a try...I did ask one more question on the edit that I am not sure where it went...
5) About rooting...if I use odin to flash the full package as I have done before (selecting PDA), how would you recommend I root the NF4 since I assume the stock firmware is NOT rooted. Do you recomend CF-Root?
thanks aod sorry to pestering I want to make sure I do this right the first time!!
calderonr said:
Yeap...I meant NF4 and I sent in an edit but you beat me to it..ok...I will give this a try...I did ask one more question on the edit that I am not sure where it went...
5) About rooting...if I use odin to flash the full package as I have done before (selecting PDA), how would you recommend I root the NF4 since I assume the stock firmware is NOT rooted. Do you recomend CF-Root?
thanks aod sorry to pestering I want to make sure I do this right the first time!!
Click to expand...
Click to collapse
Np. As for number 5, yes, CF-Auto-Root is the best (maybe the only?) method for fw beyond ne6. If you do this and find supersu missing, a simple install from the play store afterwards will fix you right up.
Sent from my leanKernel 3.4 powered stock 4.4.2 (NF4) SM-N900T
toastido said:
Np. As for number 5, yes, CF-Auto-Root is the best (maybe the only?) method for fw beyond ne6. If you do this and find supersu missing, a simple install from the play store afterwards will fix you right up.
Sent from my leanKernel 3.4 powered stock 4.4.2 (NF4) SM-N900T
Click to expand...
Click to collapse
Toastido :
Not trying to be dense here but help me understand this. Its re. the inability to go back to MI7 from NF4. You say it has to do with the bootloader, BUT, if I take a CWM backup BEFORE I flash NF4, would not that backup contain the MI7 bootloader in it, so when/if I restore the backup, would not that also restore the MI7 bootloader and the device would not even notice it had flashed NF4 before? Granted I would have to re-clash the JB compatible CWM before I restored, but would that not work? If not, can you explain why?
Thanks!!
calderonr said:
Toastido :
Not trying to be dense here but help me understand this. Its re. the inability to go back to MI7 from NF4. You say it has to do with the bootloader, BUT, if I take a CWM backup BEFORE I flash NF4, would not that backup contain the MI7 bootloader in it, so when/if I restore the backup, would not that also restore the MI7 bootloader and the device would not even notice it had flashed NF4 before? Granted I would have to re-clash the JB compatible CWM before I restored, but would that not work? If not, can you explain why?
Thanks!!
Click to expand...
Click to collapse
No it would not work. The reason, as stated in a previous post, is due to eFused bootloaders. Once the efuse is tripped, it cannot be reset, and the bootloader will fail if it's value is lower than the fused value. Otherwise just flashing the bootloader backwards would work. If you go the odin route you will be protected by odin mode. If you try via recovery of a nandroid that contains the bootloader, it'll either just not work, or (worse) brick your device.
The fuses are tripped in a sequential order. 0,1,2,3 etc. JB BL can only operate on fused value of 1 or lower. KK BL can only install and function (depending on current version) at 3 or lower.
NB4 will fuse to 2. NE6 through NF4 I believe will fuse to 3, thus preventing the JB BL from functioning.
Hope that helps.
Sent from my leanKernel 3.4 powered stock 4.4.2 (NF4) SM-N900T
Let me know how it goes. I have to update mine to.. I'm on NB4 with no issues but I should update anyways.
Sent from my SM-N900T using XDA Free mobile app
What is the best practice procedures from going from root de la vega MI7 running wicked rom knox 0x0 to a current kitkat recovery, bootloader, kernel, rom... I no longer care about knox.
If someone can give me just the basic steps I can figure everything else out but I am confused if I cf autoroot or after upgrade to kitkat and what can or cant be done in odin or what would be the best method to go straight to current builds...
Re: upgrade to latest N900T latest firmware.
c-pimp said:
What is the best practice procedures from going from root de la vega MI7 running wicked rom knox 0x0 to a current kitkat recovery, bootloader, kernel, rom... I no longer care about knox.
If someone can give me just the basic steps I can figure everything else out but I am confused if I cf autoroot or after upgrade to kitkat and what can or cant be done in odin or what would be the best method to go straight to current builds...
Click to expand...
Click to collapse
The very best thing you can do if you don't care about knox is to go to
http://SamMobile.com and download the official kitkat NF9 4.4.2 stock
firmware to start with. You can also download it from this link below:
http://tinyurl.com/of4dgnr
Use Odin to flash this firmware. (you cannot flash this using twrp/cwm)
Be sure to do a full wipe before odin flashing.
Then you need to flash cf-autoroot and twrp custom recovery.
Here are the direct download links for cf-autoroot and twrp custom recovery.
Use odin to flash both cf-autoroot and twrp but flash cf-autoroot first.
CF-Autoroot:
https://dl.dropboxusercontent.com/u/...mo-smn900t.zip
TWRP custom recovery:
https://dl.dropboxusercontent.com/u/...ltetmo-4.4.zip
Once you have rooted the phone and flashed twrp recovery you are
ready to go, and you can then flash any of the custom roms available
here in the Note 3 N900T threads.
Good luck.
Confused about rooting with T999UVUEOH1
ok
If the phone is running a stock 4.3 Samsung ROM, the phone will have knox. Best thing to do would be to run OTA updates until the phone is running the latest ROM. This will ensure that the phone has the most recent bootloader and modem.
Once updated, you can easily root the phone by flash TWRP for the d2tmo via Odin. After installing TWRP, you can flash supersu 2.45 or 2.46 via TWRP and have root access.
Note that flashing TWRP will trip the knox counter.
Ok
The method I recommended should not cause any loss of data. To be safe, always backup before flashing anything.
Is there any warranty left on the phone? If not, tripping knox isn't going to matter.
Any attempts to downgrade the bootloader may result in a bricked phone.
Looks like the root66 method involves flashing a prerooted stock ROM. If you want to try the root66 method, just make sure the root66 ROM's bootloader and modem are the same or newer than the phone's version. If the phone has oh1, I would not use the root66 method.
Ok
Flashing TWRP and supersu from TWRP is the easiest in my opinion.
Just make sure to get the tar version of TWRP to flash in Odin.
audit13 said:
Flashing TWRP and supersu from TWRP is the easiest in my opinion.
Just make sure to get the tar version of TWRP to flash in Odin.
Click to expand...
Click to collapse
Nahh!! The easiest way is use TowelRoot
Only need to press a button! I'm using that firmware so I CONFIRM that it's working
I guess it depends on the rom. It wouldn't work on stock 4.4.2 for me.
The kernel was patched against Towelroot in 4.4.2. We were never updated past 4.3 so it should work fine.
Sent from my SGH-T999 using Tapatalk