Develop Bugs

4.1.2 to 4.3 or not? t999v

Hey just wondering if I should do the update to stock 4.3 OTA or not. I've been looking at the root66 knox free 4.3 and it sounds good. Any Issues with it? or stock OTA? I've read mixed reviews, and am now confused. Also if I do install root66 on this wind t999v, am I required to install the stock OTA 4.3 update for it to work? Or am I in a better situation if I just install it from 4.1.2? Also any basic instructions on what I would have to do to install root66 would be much appriciated. I'm technologically inclined, just been out of the cellphone moding scene for quite some time, and just want to ask before I start asking how to unbrick. Thanks in advance.:good:

Knox Free Root 66 is always preferred over Stock update. The instructions and all the necessary files are in the Root66 Thread.
In short you need Odin v 3.xx Need to have the Drivers installed for your phone. Make sure Kies is not installed on your PC. Put your phone in Download mode and then connect to pc. Flash the Root66 file and you are done. There are several tutorials on Youtube for how to use Odin.
Note - For your Knowledge, please read on the 4.3 and its locked bootloader.

The root66 works fine on the wind phone and disables knox. it doesn't trip the flash counter so warranty is still intact if you had to flash back to a knox-rom. once you get into custom roms', the flash counter gets tripped though.
i just installed the 4.4.2 likewise rom, and it is smoooooooth. lol. it's not official though.

Perseus71 said:
Kox Free Root 66 is always preferred over Stock update. The instructions and all the necessary files are in the Root66 Thread.
In short you need Odin v 3.xx Need to have the Drivers installed for your phone. Make sure Kies is not installed on your PC. Put your phone in Download mode and then connect to pc. Flash the Root66 file and you are done. There are several tutorials on Youtube for how to use Odin.
Note - For your Knowledge, please read on the 4.3 and its locked bootloader.
Click to expand...
Click to collapse
How do I know which wind pre-installed root firmware to install:
WIND Image
December 2013 - 4.3 JellyBean
Note: This is based off of the stock image GLW T999VVLUEMK5
Download :: Download - root66_GLW_T999VVLUEMK5.7z
June 2013 - 4.1.2 JellyBean
Note: This is based off of the stock image GLW T999VVLDMF2
Perm Mirror: Download - root66_GLW_T999VVLDMF2.7z
December 2012 - 4.1.1 JellyBean
Note: This is based off of the stock image GLW T999VVLDLL1
Perm Mirror: Download - root66_GLW_T999VVLDLL1.7z
my s3 is on 4.1.2 so do I download that one or is that the firmware that will be newly installed? I want 4.3 newly installed.

Please flash root66_GLW_T999VVLUEMK5.7z

Also on http://forum.xda-developers.com/showthread.php?t=1949687 they have 4 files, sorry for all the questions
Wind_VLUEMK5
Updated JB Firmware
Wind_VLDMF2
Updated JB Firmware
Wind_VLDLL1
Updated JB Firmware
Wind_VLALH2
Updated ICS Firmware

Perseus71 said:
Please flash root66_GLW_T999VVLUEMK5.7z
Click to expand...
Click to collapse
Even if my current s3 firmware is 4.1.2 baseband t999vvldmf2 ?

Yes that's fine. It will update your Bootloader.

upgrade not good
kreso3k said:
Hey just wondering if I should do the update to stock 4.3 OTA or not. I've been looking at the root66 knox free 4.3 and it sounds good. Any Issues with it? or stock OTA? I've read mixed reviews, and am now confused. Also if I do install root66 on this wind t999v, am I required to install the stock OTA 4.3 update for it to work? Or am I in a better situation if I just install it from 4.1.2? Also any basic instructions on what I would have to do to install root66 would be much appriciated. I'm technologically inclined, just been out of the cellphone moding scene for quite some time, and just want to ask before I start asking how to unbrick. Thanks in advance.:good:
Click to expand...
Click to collapse
i want to downgrade, but cannot find any way to downgrade.

welcome2you said:
i want to downgrade, but cannot find any way to downgrade.
Click to expand...
Click to collapse
because you cannot downgrade from 4.3 firmware.

[INFO][FAQ] All things KitKat - How to update, ROOT, return to stock, & more!

This thread contains information about the KitKat 4.4.2 update to the T999 variants of the Samsung Galaxy S3. Here you will be able to find information on updating, rooting, installing custom recoveries and roms, as well as how to return to stock should you feel the need to. If you feel you need additional help or would like further clarification on a subject just leave a reply in this thread and myself or someone familiar with the matter will do our best to answer and provide promptly help. This is a work in progress since KitKat is new to our devices. As we learn more, additional info and links will be posted. Huge thanks to DocHoliday77 for giving me ideas and helping me make things clearer!
Below I tried to put together a list of questions regarding KitKat in hopes to alleviate confusion and educate others.
F.A.Q.
[Q] Can I just flash the KitKat modem on my older firmware to see if my signal will improve?
WARNING! WARNING!
A) I feel like this is probably the most important thing to know about the KitKat update as of now. DO NOT I repeat DO NOT flash any 4.4.2 modems if you have not taken the official 4.4.2 update for your device via OTA or Odin. If you do, you will brick your device and you will not be able to unbrick it. The current debrick method does not work! Also please do not try to downgrade your bootloader, any such attempt can also brick your device.
YOU HAVE BEEN WARNED!!
Click to expand...
Click to collapse
[Q] My signal has been terrible with KitKat, how can I downgrade my modem to see if I will get a better signal?
A) You cannot use older modems with 4.4.2. You will have no service.
Click to expand...
Click to collapse
[Q] Will KitKat give me Knox?
A) Unsurprisingly, Knox is present in 4.4.2 as it was in 4.3. For more info on Knox, scroll down to the second post.
Click to expand...
Click to collapse
[Q] Is it possible to root my device without tripping the Knox/warranty bit counter, and how can I make sure it stays untripped?
A) Yes, it is possible to root and keep your counter untripped. Scroll down to "How to root" and you will find your answer. To keep the counter at 0, avoid flashing custom recoveries and kernels.
Click to expand...
Click to collapse
[Q] I have tripped my Knox/warranty bit counter, how can I reset it?
A) There is currently no way to reset this counter.
Click to expand...
Click to collapse
[Q] Can I still flash a custom recovery with KitKat firmware?
A) Yes. Please scroll to the end of this post for more info and recommendations.
Click to expand...
Click to collapse
[Q] I am in developer options and I cannot find the option to change my runtime to ART, how can I change it? I'm confused.
A) ART runtime cannot be chosen as default because the option is disabled by Samsung in all of their KitKat firmwares. The default will be Dalvik.
Click to expand...
Click to collapse
If your device has not yet received the KitKat update, please be patient and wait for your carrier to update. If you feel you cannot wait for an official update, there is the option to update unofficially by flashing a custom Rom, just remember that they will be taken from other device's firmware so it may not work the same with your device or it have missing features native to yours. For more information and what you need to update unofficially, check method 3 below on "How to update or return to stock."
General F.A.Q.s
[Q] What Rom's can I safely flash?
A) Any Rom and kernel in this section of the fourms should be okay. Roms labeled for d2lte will work for any d2 device, and T999 Roms will work on T999V & T999N for example.
BUT....some ROM's will not flash without a little intervention, so to speak. If you get a Status 7 error and the ROM will not flash, this is what you do:
Unzip the Rom.
In the Meta-Inf folder, delete the signatures (CERT.RSA, CERT.SF, MANIFEST.MF)
Browse to META-INF\com\google\android\ and open the updater-script in Notepad++
At the top of the script, there will be one or several lines beginning with "Assert". Delete these Lines. Save the updater-script.
Re-Zip the Rom and try again to flash.
Click to expand...
Click to collapse
[Q] Why is my WiFi and/or Bluetooth not working after flashing a T999 based Rom?
A) Most likely this is due to a kernel/module mismatch. Try flashing a custom kernel or a stock modified kernel to fix this.
Click to expand...
Click to collapse
[Q] Why does my phone say it is a T999 or other model?
Because you flashed a rom that was based on or intended for the original T999 model. This is perfectly normal.
If you really want to change it, go to /system/build.prop and edit all lines that say SGH-T999, to your model or whatever you like.
(WARNING!!!) If you change this to a different model than the T999 or T999L, some apps may think they are on that different model device. This can cause a brick if you try to flash firmware with Mobile Odin. Other apps may not function as intended. Use Caution!
Click to expand...
Click to collapse
How to update or return to stock:
Method 1:
The simplest method. If you are on official and unrooted stock firmware, you can simply check for update to your device by going into settings, more, about device, software update. This option is if you do not want root access or plan to root at another time.
Click to expand...
Click to collapse
Method 2:
You can use this method to update your device or return it to its factory state, should you need to. Simply download the stock firmware linked below and flash it with Odin. Just remember, you cannot downgrade your device once you have updated to 4.3 or higher firmware. You can, however, flash an equal or higher version. For example, you updated your device to 4.3 MJC firmware, you can only flash 4.3 MJC, 4.3 NC2, or 4.4.2. If on NC2 firmware you cannot downgrade to MJC even though it is 4.3 because it is a lower firmware. If you flashed 4.4.2, you can only flash 4.4.2. Follow the link below and scroll past the words "root66" where you will see "Official Firmware." Detailed instructions on how to use and flash firmware with Odin will also be found there. Thanks to my good friend @DocHoliday77 for the thread and mrRobinson for the firmwares!
Stock Firmware:
Download
Click to expand...
Click to collapse
Method 3:
You can flash a custom Rom with your custom recovery, but you will need at least a 4.3 bootloader and modem. Bootloader update is required otherwise your device will not boot, modem is needed for data. If you decide to go this route and are on 4.3 bootloader and modem do not upgrade them under any circumstance unless you want a brick and headaches! I will link stock Roms here overtime, meanwhile search for one you like in the development section Click to go to Development Section
Stock NB8 4.4.2 port from Sprint. Daily driver stable! Thanks Doc!
Download Sprint port here
Click to expand...
Click to collapse
How to root:
Method 1:
If you are looking to update your device and be rooted out of the box, check out the pre-rooted root66 firmware thread by @DocHoliday77. Just find the 4.4.2 firmware for your device, download it, and flash with Odin. Detailed instructions on how to use and flash with Odin can also be found in the link below. Make sure you click the box below the words "root66." Knox counter should remain untripped, but it is unconfirmed as of now. If you want to be safer about your counter staying untripped, continue to method 2.
Download root66
Click to expand...
Click to collapse
Method 2:
Use TowelRoot by the legendary geohot. This method is very simple and useful if you have already updated to 4.4.2 and want root access nice and easy. Confirmed to keep your Knox counter untripped!
Download TowelRoot
Click to expand...
Click to collapse
How to install a custom recovery:
Remember, any and ALL methods to flash custom recovery will trip Knox/warranty counter. After installing a custom recovery you will be able to flash custom ROMs, scripts, and mods!
Method 1:
Download your recovery tar file and flash it with Odin in download mode.
Instructions:
Flash File In ODIN
- Power down your device
- Simultaneously press and hold VOL DOWN + HOME BUTTON + POWER BUTTON
- At *Warning* screen, press VOL UP
- Connect your device to its USB cable and plug cable into PC
- Start ODIN on PC
- Verify that "Auto Reboot" and "F. Reset Time" are UNCHECKED
- Click PDA button ("AP" in newer versions)
- Browse PC and select your tar file
- WAIT for "START" button to be enabled (may take a minute)
- Click START button to begin recovery install
- Disconnect USB only when download is finished and you see the message "PASS!" in a green box.
- Remove battery and reboot straight to recovery, very important!
- Now you can either flash whatever you want, or reboot back into system.
Instructions were taking from a thread by az_biker and edited for our device
Click to expand...
Click to collapse
Method 2:
Use an app from the playstore to flash custom recovery like goomanager, ROM Manager, or my favorite, flashify! These method is useful if you have root access on your device, would prefer avoid using Odin, or do not have access to a computer to use Odin.
Click to expand...
Click to collapse

Information about Knox
Knox allows people to use their device on a secure business (work) network. It allows the data which belongs to the business to be encrypted per DoD standards. Once the Knox/warranty bit is tripped, you can no longer use this service because it proves the device has been tampered with. You can imagine how much simpler it would be to manipulate this service without the restrictions Samsung had to enforce in order to protect sensitive data. This is the main reason I believe the Knox bootloader was added and why root access, once gained, is still limited in some cases. There is also claims that a tripped warranty bit means your warranty will be void, but I have not seen any cases where people have been denied warranty. However it is better to play it safe than sorry if you really do care about warranty.
Wikipedia sums it up pretty nicely.
Read more about Samsung Knox on Wikipedia
How to remove Knox
If you do not use or plan to use Knox, the limitations imposed by Samsung can affect your overall experience with root access, or make the service become bloatware. For this reason you may want to remove it. Follow the link below to make your device Knox free. Flash in custom recovery and do not forget to nandroid before you flash! Thanks to bilgerryan over in the Sprint forums!
Get Knox removal zip here

Ill take one!
---------- Post added at 02:08 AM ---------- Previous post was at 02:07 AM ----------
And another!
---------- Post added at 02:08 AM ---------- Previous post was at 02:08 AM ----------
Good write up btw! Thanks!

Just a heads up for T999 users who are going to flash root66 in Odin: flashing root66 in Odin DID trip the warranty bit for my device. I was running NC2 on my T999 (T-Mobile), flashed root66 NC2 and the bit was tripped. If you're worried about maintaining warranty eligibility you should take note.

friedchocolatesoda said:
Just a heads up for T999 users who are going to flash root66 in Odin: flashing root66 in Odin DID trip the warranty bit for my device. I was running NC2 on my T999 (T-Mobile), flashed root66 NC2 and the bit was tripped. If you're worried about maintaining warranty eligibility you should take note.
Click to expand...
Click to collapse
Thanks, but this thread is for touchwiz kitkat. Its not intended for 4.3 or any other build unless specifically related.
But still, im not sure why it tripped the bit on yours. It did just fine on mine and others...

I know this is a kitkat thread but it also tripped the warranty bit on my t999l
Sent from my SGH-T999 using XDA Premium 4 mobile app

friedchocolatesoda said:
Just a heads up for T999 users who are going to flash root66 in Odin: flashing root66 in Odin DID trip the warranty bit for my device. I was running NC2 on my T999 (T-Mobile), flashed root66 NC2 and the bit was tripped. If you're worried about maintaining warranty eligibility you should take note.
Click to expand...
Click to collapse
chalky7880 said:
I know this is a kitkat thread but it also tripped the warranty bit on my t999l
Sent from my SGH-T999 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
this is odd as it should not trip the counter even though it was in jellybean.. to my knowledge the counter is tripped when you flash a custom recovery, but I will edit the OP until further confirmation.. thanks for the heads up guys
Edit: flashing kernel will also trip counter
Sent from my SGH-M919 using Tapatalk

Your probably right. I did flash a custom recovery so I bet that's what tripped it
Sent from my SGH-T999 using XDA Premium 4 mobile app

chalky7880 said:
Your probably right. I did flash a custom recovery so I bet that's what tripped it
Sent from my SGH-T999 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It's all good, all feedback is appreciated. Believe it or not, it actually gave me the idea to mention in the OP how to keep the warranty bit from being tripped for those who want to avoid tripping it. Thank you!
Sent from my SGH-M919 using Tapatalk

Just fyi for everyone, there have been claims for both in the root66 thread. Some say it tripped the bit, while for others like myself it did not. No idea why, but I do not believe it has anything to do with the root66 firmware. There have been people who tripped the warranty bit just by taking the ota!

DocHoliday77 said:
Just fyi for everyone, there have been claims for both in the root66 thread. Some say it tripped the bit, while for others like myself it did not. No idea why, but I do not believe it has anything to do with the root66 firmware. There have been people who tripped the warranty bit just by taking the ota!
Click to expand...
Click to collapse
That would be a big screw up for Samsung. Really hope this is not the case
Sent from my SGH-M919 using Tapatalk

Its not a common occurrence, but it has happened.

[Q] N900TTMBBMI7 to N900TUVUDNF1 Upgrade

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

Help needed for unrooting

Hi guys I've had my note II for quite awhile (2 years) and I've rooted it back then installed custom ROM and recovery, not quite sure if a custom kernel is installed. Currently still on 4.1.2 and TWRP installed.
To unroot, I researched that i'll just have
Use Triangle Away and reset my counter.
Flash official firmwares from sammobile
The question here now is that do will my device be kept as official/normal and flash counter 0?? Because some of the steps shown are quite ambiguous and I just want to make sure that I can sell the phone!
Thanks in advance!!

droidgg said:
Hi guys I've had my note II for quite awhile (2 years) and I've rooted it back then installed custom ROM and recovery, not quite sure if a custom kernel is installed. Currently still on 4.1.2 and TWRP installed.
To unroot, I researched that i'll just have
Use Triangle Away and reset my counter.
Flash official firmwares from sammobile
The question here now is that do will my device be kept as official/normal and flash counter 0?? Because some of the steps shown are quite ambiguous and I just want to make sure that I can sell the phone!
Thanks in advance!!
Click to expand...
Click to collapse
Well, you will need to flash official firmware 4.1.2 first. The status of the phone will be official.
Then, root the phone and install + update Super SU. Use triangleaway to reset the counter.
Then, fully unroot using Super SU. Your phone should certainly fetch you a good dowry.
Press thumps up if you found this suggestion helpful.

ceomaverick said:
Well, you will need to flash official firmware 4.1.2 first. The status of the phone will be official.
Then, root the phone and install + update Super SU. Use triangleaway to reset the counter.
Then, fully unroot using Super SU. Your phone should certainly fetch you a good dowry.
Press thumps up if you found this suggestion helpful.
Click to expand...
Click to collapse
Thank you for your reply!
hmm is there anywhere that I can find the official 4.1.2 firmware? Sammobile only has the latest versions.. Also, is it possible to retain root when I flash the original firmware?

droidgg said:
Thank you for your reply!
hmm is there anywhere that I can find the official 4.1.2 firmware? Sammobile only has the latest versions.. Also, is it possible to retain root when I flash the original firmware?
Click to expand...
Click to collapse
Go to samsung-updates.com and click firmware archive.
There is a list of 4.1.2 firmwares. Find one for your country.
Also, if your country is not listed, you can flash 4.1.2 from any country in your region provided that your phone is Galaxy Note 2 international (N7100)
If not, you may have to settle from may be 4.3 or 4.4.
Lastly, you cannot retain root. You will have to follow the procedure mentioned in the earlier reply.

[Q&A] [Firmware/OTA's] [root66] SGH-T999(All Variants!) Official & Root66 FW & OTA U

[Q&A] [Firmware/OTA's] [root66] SGH-T999(All Variants!) Official & Root66 FW & OTA U
Q&A for [Firmware/OTA's] [root66] SGH-T999(All Variants!) Official & Root66 FW & OTA Updates!
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [Firmware/OTA's] [root66] SGH-T999(All Variants!) Official & Root66 FW & OTA Updates!. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

Can I flash the root666 T999_UVUEMJC (or even the stock) firmware on top of stock T999_UVUENC2 without bricking the phone? I got the latest T999_UVUENC2 OTA update and my wifi won't work anymore . Any help would be appreciated. Thanks

GS3 t999l T999LUVUBNF4 update TowelRoot
hi just unrooted my GS3 and updated via kies to T999LUVUBNF4, went back to towelroot and it says phone is not supported. Does anyone know another quick way to root? Also is anyone else using this update and can tell me how its behaving. appreciate the info

gs3goodtome said:
hi just unrooted my GS3 and updated via kies to T999LUVUBNF4, went back to towelroot and it says phone is not supported. Does anyone know another quick way to root? Also is anyone else using this update and can tell me how its behaving. appreciate the info
Click to expand...
Click to collapse
cf-auto root, or flash SuperSU with custom recovery.

T999LUVUBNF4 Root
Hey, I've been trying to root my S3 running the T999LUVUBNF4 firmware, but I'm having trouble. Towelroot doesn't support it, I haven't seen anything about a Root66, and I've heard mixed reports on CF-auto root. Does anyone know if there is a workable solution yet? How would I go about flashing SuperSU? Thanks.

Okay I've recently just flashed the root66 firmware that gave me supersu and all that.
My question is... Where do i go from here?
How would i proceed to
1) Install TWRP?, which version as well? Is 2.8 d2tmo fine? Can i have some instructions whether i use TWRP manager(goomanager doesn't seem to exist anymore) or do i have to go into download and flash through odin 3.09?
2) Installing a custom rom? I want to install Paranoid Android 4.6 beta 5 for D2lte but i'm not sure how to go about it. I have already downloaded the rom itself but not sure how to proceed from here. Also, how would i get the working and latest version of Gapps? (Also, can you tell me how to install Cyanogenmod 11 for d2lte as well?)
3) What are some cool apps to get?
4) Which root apps/roms/softwares will brick my phone? I'm never sure which thing will work and which won't.
5) how do i install xposed?
6) How do i remove all the bloatware? and how would i got about flashing through my phone without using the computer? is mobile odin compatible with my phone?
My phone is the SGH-T999L and i have no idea if i have a locked bootloader and how i would go about and bypass the limitations of this locked bootloader

rocket540 said:
Hey, I've been trying to root my S3 running the T999LUVUBNF4 firmware, but I'm having trouble. Towelroot doesn't support it, I haven't seen anything about a Root66, and I've heard mixed reports on CF-auto root. Does anyone know if there is a workable solution yet? How would I go about flashing SuperSU? Thanks.
Click to expand...
Click to collapse
Did you read my post above yours?
IceHism said:
Okay I've recently just flashed the root66 firmware that gave me supersu and all that.
My question is... Where do i go from here?
How would i proceed to
1) Install TWRP?, which version as well? Is 2.8 d2tmo fine? Can i have some instructions whether i use TWRP manager(goomanager doesn't seem to exist anymore) or do i have to go into download and flash through odin 3.09?
2) Installing a custom rom? I want to install Paranoid Android 4.6 beta 5 for D2lte but i'm not sure how to go about it. I have already downloaded the rom itself but not sure how to proceed from here. Also, how would i get the working and latest version of Gapps? (Also, can you tell me how to install Cyanogenmod 11 for d2lte as well?)
3) What are some cool apps to get?
4) Which root apps/roms/softwares will brick my phone? I'm never sure which thing will work and which won't.
5) how do i install xposed?
6) How do i remove all the bloatware? and how would i got about flashing through my phone without using the computer? is mobile odin compatible with my phone?
My phone is the SGH-T999L and i have no idea if i have a locked bootloader and how i would go about and bypass the limitations of this locked bootloader
Click to expand...
Click to collapse
Please don't post the same thing on multiple threads. Not being rude but it doesn't help at all

Rooting SGH-T99L with T999LUVUBNF4
I've read most of the more recent posts, and it is still unclear to me how to root my T999L which is already on the T999LUVUBNF4 baseband and build. I've seen references to cf-auto-root (like serio22 above), but the T999 (which I believe works for T999L) is based on T999UVALEM, which is 4.0.4 ICS. I certainly don't want to downgrade that far. The latest firmware on the first page of this Root66 thread is T999L_UVUBNC1, and there was a post indicating better reception with the newer modem, so I'd rather not downgrade that either. If I flash T999L_UVUBNC1 will my baseband remain intact (BNF4)? Or should I wait for a pre-rooted T999L_UVUBNF4? Or is there a better way altogether to root my T999L/BNF4?
Also, for other n00bs reading this, it's pretty clear that towelroot doesn't work on BNF4.
Thanks!!

I need some help repairing my imei
I'm on the t999
nc2 radio
on a t mobile based rom 4.3

Stock root image for Baseband ver
IM TRYING TO FIND OUT HOW TO ROOT MY s3, A baseband version of SGL99L t mobile samsung s3 T999LUVUBNF4, what file do i want?

Best root and 4.4 rom for NF4 t999L
Did you find one DKARMANN?

@DocHoliday77 is there any root66 for UVUBNF4? I tried searching everywhere in the forums and I can't seem to find anything.

android_noob12 said:
@DocHoliday77 is there any root66 for UVUBNF4? I tried searching everywhere in the forums and I can't seem to find anything.
Click to expand...
Click to collapse
not root66 , but did you read post #4?

mrrocketdog said:
not root66 , but did you read post #4?
Click to expand...
Click to collapse
See post #8, re cf-root and downgrading.

rooted Windmobile 4.4.4
anyone have 4.4.? for wind mobile what ever is the new one stock that is rooted ?

I tried flashing UVDLJC - UVDMD5 (latest OTA update) using Multiboot Recovery v2.2 - (twrp2.8.3.0)
When flashing directly onto blank partition, I got some error about missing build.prop, and so decided to try flashing on top of stock ROM.
Stock I have installed as Flash PureStock Rom + Secure UVAMB7 Kernel (from http://forum.xda-developers.com/showpost.php?p=43772060&postcount=3) -- again, in multiboot -- and tried installing OTA on top of that. Got "error executing updater binary in zip"
What am I doing wrong?
Thanks

slimkat v9 to stock tw
Please help me. I have a sgh-t999. I want to know is it safe to install stock tw t999_uvuenc2. I'm currently running slimkat v9. My baseband is t999uvuenc2 and my android version is 4.4.4 i really want my s3 to revert back to stock. Ive been asking to the roms posted in this unit if it safe to direct flash but i havent got a good advice. I really want the stock touchwiz. Pls help me.

Which firmware to use
After I un-bricked my SGH-T999 with the debrick image sdcard ( YAYYY), I was able to boot with the stock 4.3 rom again.
I reflash the root66 4.3 firmware hoping it could get the correct boot image back in place. However it got stuck at the Samsung logo.
So I went into stock recovery and did a wipe/factory reset. Now I can still boot with the debrick sdcard but I am back in JellyBean (4.1.2 T999UVDMD5).
Which firmware should I flash 4.3 or 4.1.2? And did I miraculously downgraded my firmware ( I thought it wasn't possible) ?

iam.alucard said:
Please help me. I have a sgh-t999. I want to know is it safe to install stock tw t999_uvuenc2. I'm currently running slimkat v9. My baseband is t999uvuenc2 and my android version is 4.4.4 i really want my s3 to revert back to stock. Ive been asking to the roms posted in this unit if it safe to direct flash but i havent got a good advice. I really want the stock touchwiz. Pls help me.
Click to expand...
Click to collapse
Late, but yes you can, you'll have to factory reset
pancakemiz said:
After I un-bricked my SGH-T999 with the debrick image sdcard ( YAYYY), I was able to boot with the stock 4.3 rom again.
I reflash the root66 4.3 firmware hoping it could get the correct boot image back in place. However it got stuck at the Samsung logo.
So I went into stock recovery and did a wipe/factory reset. Now I can still boot with the debrick sdcard but I am back in JellyBean (4.1.2 T999UVDMD5).
Which firmware should I flash 4.3 or 4.1.2? And did I miraculously downgraded my firmware ( I thought it wasn't possible) ?
Click to expand...
Click to collapse
What does download mode display?

Unsure which firmware to use
serio22 said:
What does download mode display?
Click to expand...
Click to collapse
Odin Mode
Product Name: SGH-T999
Custom Binary Download: No
Current Binary: Samsung Official
System Status: Official
Qualcomm Secureboot: Enable
Warranty Bit: 1
Bootloader AP SWAEV: 1
Am I correct that if the root66 firmware had installed correctly, it should read:
Custom Binary Download: Yes
Current Binary: Custom
Click to expand...
Click to collapse
.