Develop Bugs

[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] NB4 to NF4 without losing root or messing up Knox

So, I have a NB4 SM N900T. I rooted with cfautoroot, then installed Phillz Touch CWM, then made a full backup. After I rooted and installed a custom recovery, I was getting that recovery not SEANDROID enforcing/Kernel Warranty error on Boot. I then flashed Hyperdrive and used it for a few weeks. Today I wiped everything, and restored that nandroid backup to bring it back to stock NB4 because I cannot seem to get LTE to work to save my life.
Anyhow, now I see that NF4 is out.
With stock NB4, I'm no longer getting that error. It's still rooted, etc after the backup was restored.
What I would like to know is what would be the best way for me to get the NF4 update without messing up my root/Knox?
I can use ODIN, but if someone could just be a little more specific that would be great.
I downloaded N900TUVUDNF4_N900TTMBDNF4_N900TUVUDNF4_HOME.tar.md5
and Cfautoroot from another thread...
I think I'm going to stay with the stock ROM until I figure out this LTE issue... I am on Straight Talk AT&T (Using Hyperdrive ROM) and get plain 4G and someone with the same phone- stock NB4 and ATT go service standing 2 feet away gets 4Glte. 15mbs+ speeds, while I'm under 5mbs.
Sorry, kinda all over the place here...
Anyhow, thanks for any help everyone.

re: Knox
Ed Murray said:
So, I have a NB4 SM N900T. I rooted with cfautoroot, then installed Phillz Touch CWM, then made a full backup. After I rooted and installed a custom recovery, I was getting that recovery not SEANDROID enforcing/Kernel Warranty error on Boot. I then flashed Hyperdrive and used it for a few weeks. Today I wiped everything, and restored that nandroid backup to bring it back to stock NB4 because I cannot seem to get LTE to work to save my life.
Anyhow, now I see that NF4 is out.
With stock NB4, I'm no longer getting that error. It's still rooted, etc after the backup was restored.
What I would like to know is what would be the best way for me to get the NF4 update without messing up my root/Knox?
I can use ODIN, but if someone could just be a little more specific that would be great.
I downloaded N900TUVUDNF4_N900TTMBDNF4_N900TUVUDNF4_HOME.tar.md5
and Cfautoroot from another thread...
I think I'm going to stay with the stock ROM until I figure out this LTE issue... I am on Straight Talk AT&T (Using Hyperdrive ROM) and get plain 4G and someone with the same phone- stock NB4 and ATT go service standing 2 feet away gets 4Glte. 15mbs+ speeds, while I'm under 5mbs.
Sorry, kinda all over the place here...
Anyhow, thanks for any help everyone.
Click to expand...
Click to collapse
If you have installed any custom recovery like cwm/twrp you have
already tripped knox and there is no way to fix it so you may as well
simply flash whatever firmware and or custom rom you like.
Flashing/installing any custom recovery trips knox.
Good luck!

Fixed LTE issues. Threw away Straight Talk, Picked up AT&T.
Ok, so I'm considering staying on Stock ROM but my NB4 (RAC Build) N900T has no OTA update from Samsung...
So, am I able to just flash straight from NB4 to NF4? Will I lose root?

re: root
Ed Murray said:
Fixed LTE issues. Threw away Straight Talk, Picked up AT&T.
Ok, so I'm considering staying on Stock ROM but my NB4 (RAC Build) N900T has no OTA update from Samsung...
So, am I able to just flash straight from NB4 to NF4? Will I lose root?
Click to expand...
Click to collapse
Yes you will loose root however if you simply flash cf-autoroot after
flashing the official N900T NF4 firmware you will have root again.
Here is the direct download link for the official N900T NF4 firmware:
http://www.mediafire.com/download/f...VUDNF4_N900TTMBDNF4_N900TUVUDNF4_HOME.tar.md5
Here is the direct download link for the Odin flashable cf-autoroot:
https://dl.dropboxusercontent.com/u/45687485/CF-Auto-Root-hltetmo-hltetmo-smn900t.tar.md5
Good luck!

Misterjunky said:
Yes you will loose root however if you simply flash cf-autoroot after
flashing the official N900T NF4 firmware you will have root again.
Here is the direct download link for the official N900T NF4 firmware:
http://www.mediafire.com/download/f...VUDNF4_N900TTMBDNF4_N900TUVUDNF4_HOME.tar.md5
Here is the direct download link for the Odin flashable cf-autoroot:
https://dl.dropboxusercontent.com/u/45687485/CF-Auto-Root-hltetmo-hltetmo-smn900t.tar.md5
Good luck!
Click to expand...
Click to collapse
You're welcome for the firmware link.
I asked you nicely in pm to link to my thread instead of stealing my links, but since you ignored that, be prepared to have me comment on your posts where you try to pass them off as your own, or at least fail to attribute.
I appreciate that you want to help others, but please attribute links and/our abide by the posters requests when they ask you.
Thanks
Sent from my leanKernel 3.4 powered stock 4.4.2 (NF4) SM-N900T

Thanks, both of you, for the info and links.
Can I use Mobile Odin to do this?

Ed Murray said:
Thanks, both of you, for the info and links.
Can I use Mobile Odin to do this?
Click to expand...
Click to collapse
You can, but just be aware that Mobile Odin cannot flash bootloaders, so if you're just looking to go straight up, you can either follow the directions in post #2 of this link: http://forum.xda-developers.com/not...900tuvudnf4-extracted-stock-firmware-t2834398 or use desktop odin.
If you want to do it all in one shot, desktop odin is your best bet. Just power your device down for about 15-30 seconds (or power off using power menu and battery pull for a bout 10 seconds), then boot straight into download mode (this helps ensure the modem and bootloader stick), and flash the full package in the AP (or PDA) slot of desktop odin.

toastido said:
You can, but just be aware that Mobile Odin cannot flash bootloaders, so if you're just looking to go straight up, you can either follow the directions in post #2 of this link: http://forum.xda-developers.com/not...900tuvudnf4-extracted-stock-firmware-t2834398 or use desktop odin.
If you want to do it all in one shot, desktop odin is your best bet. Just power your device down for about 15-30 seconds (or power off using power menu and battery pull for a bout 10 seconds), then boot straight into download mode (this helps ensure the modem and bootloader stick), and flash the full package in the AP (or PDA) slot of desktop odin.
Click to expand...
Click to collapse
Alright, thanks for the help. I'm out of "thanks" for the day, but will click the crap outta it tomorrow. Much appreciated.

UCUFNE4 to UCUFNJ1 update 16 gig AT&T I747

The development for the AT&T I747 has been discontinued by the developer. Thank you for your support.
WARNING: YOU COULD BRICK YOUR PHONE
UCUFNJ1 4.4.2 incremental update contains firmware.... bootloaders and modem baseband.
MUST BE ON UCUFNE4 FIRMWARE TO CONTINUE!!! Guide can be found here. http://forum.xda-developers.com/gal...are-update-t2808654/post53984772#post53984772
This is the perfect time to use this update to return your S3 to stock for resale or whatever. Download and save these files for when you are ready to return your phone to stock.
*This is a rooted NE4 system.img, stock recovery.img and boot.img. The install script will format system and factory data reset. /media is safe.*
1. Flash restore zip in a custom recovery. CWM, TWRP, Philz. https://www.androidfilehost.com/?fid=95784891001611561
2. Boot your phone and go through setup.
3. Use triangle away and clear your counter. http://forum.xda-developers.com/galaxy-s2/orig-development/2014-01-15-triangleaway-v3-26-t1494114
4. *Optional* If you want a clean un-rooted phone for the update do this now! , Go into SuperSu >settings>full unroot.
5. Reboot your phone.
6. Search for the OTA in the about settings, download and let the phone update.
Or download this and place in the root of your phones internal storage. Reboot into recovery and select the update from update.zip https://www.androidfilehost.com/?fid=95784891001611091
Advanced users.
The original OTA cfg file. https://www.androidfilehost.com/?fid=95784891001611092
.cfg file goes in root/cache/fota
Rename the .cfg extension to .zip and you can rename it update.zip yourself or you can actually flash it in a custom recovery once renamed. if you choose not to use the stock recovery to update.
*You will loose root during the update* But the bootloader is not locked so you can still Odin your favorite recovery and flash SuperSU.
TWRP 2.8.1.0 Odin tar. http://techerrata.com/file/twrp2/d2att/openrecovery-twrp-2.8.1.0-d2att.tar
SuperSU http://download.chainfire.eu/589/SuperSU/UPDATE-SuperSU-v2.16.zip?retrieve_file=1
Once you flash your favorite recovery via Odin, you need to be ready to hold the Volume Up, Power and Home button combo when Odin reboots your phone. If you don't catch it, once the OS boots it will replace recovery with the stock version. Once SuperSU is installed your recovery will stick.​
Flashable Rooted NJ1 system.img and boot.img
MD5: 6df80e42df56ddf90512f4162e645cb3
Download: https://www.androidfilehost.com/?fid=95784891001613266
Flashable NJ1 Bootloaders and modem. *Must be on NE4 bootloaders prior to flashing.*
Download: https://www.androidfilehost.com/?fid=95832962473396872

Thanks enewman for writing this up.

Doing Vice Versa Method?
Just to be clear, what if my galaxy s3 is on UCUFNJ1 and I want to go back to UCUFNE4, I can still ODIN the custom recovery and flash SuperSU?
Galaxy S3 I747
Baseband: I747UCUFNJ1

For the advanced users, should we be able to install the update without any issues? I saw in another thread that someone had installed but now their phone will not boot past the Samsung logo to anything other than a black screen.
Also, do we know what this update contains yet? Other than new bootloaders, removal of root, etc.

mattsternc said:
For the advanced users, should we be able to install the update without any issues? I saw in another thread that someone had installed but now their phone will not boot past the Samsung logo to anything other than a black screen.
Also, do we know what this update contains yet? Other than new bootloaders, removal of root, etc.
Click to expand...
Click to collapse
You know if your not wanting to return your phone to stock I really wouldn't mess with this update. Far as the user who couldn't boot... Idk I wasn't there to watch them update. This whole mess with the S3 is exhausting. We haven't got a real Odin release so I'm woking with what I can extract from my phone after updating. The system.img in ne4 zip is 100% stock except for root. So I know the update worked because I did it. Also not sure what was updated either... The kernel yes... Firmware yes, all the system apps get patched so without decompiling ne4 and nj1 apps and comparing them afraid I have no idea what the update fixes or improves.

Thanks for all you do for us S3 owners, enewman17.
If we upgrade to the new NJ1 firmware, and then flash your latest SRX Rom, I assume we cannot then use your "restore.zip" to once again go back to NE4 stock since we would be on NJ1 bootloader? If so, is there a way to go back to NJ1 stock if we later want to sell our phone?

OKAstro said:
Thanks for all you do for us S3 owners, enewman17.
If we upgrade to the new NJ1 firmware, and then flash your latest SRX Rom, I assume we cannot then use your "restore.zip" to once again go back to NE4 stock since we would be on NJ1 bootloader? If so, is there a way to go back to NJ1 stock if we later want to sell our phone?
Click to expand...
Click to collapse
I have the nj1 system dump, I'll get it uploaded so anyone who updates can restore back to stock.

enewman17 said:
I have the nj1 system dump, I'll get it uploaded so anyone who updates can restore back to stock.
Click to expand...
Click to collapse
Thanks again my man.

Towelroot no longer works after the NJ1 update. Can the CF-AutoRoot still be used? The only version at http://autoroot.chainfire.eu/ says it's for 4.0.4.

Ark42 said:
Towelroot no longer works after the NJ1 update. Can the CF-AutoRoot still be used? The only version at http://autoroot.chainfire.eu/ says it's for 4.0.4.
Click to expand...
Click to collapse
Not sure if it still works but read the op you can Odin a custom recovery then flash super su.

enewman17 said:
Not sure if it still works but read the op you can Odin a custom recovery then flash super su.
Click to expand...
Click to collapse
Yeah, I saw that, but I never had a custom recovery before, that I know of at least, and I suspect a lot of other people finding this thread in the coming days are going to be in the same boat as me. They just want SuperSU so their favorite 1 or 2 apps that require SU can continue to work.
Has anybody tried CF-AutoRoot yet on the NJ1 4.4.2?

Ark42 said:
Yeah, I saw that, but I never had a custom recovery before, that I know of at least, and I suspect a lot of other people finding this thread in the coming days are going to be in the same boat as me. They just want SuperSU so their favorite 1 or 2 apps that require SU can continue to work.
Has anybody tried CF-AutoRoot yet on the NJ1 4.4.2?
Click to expand...
Click to collapse
Agreed! I'm the same boat as you.
Sent from my SAMSUNG-SGH-I747 using Tapatalk

Ark42 said:
Yeah, I saw that, but I never had a custom recovery before, that I know of at least, and I suspect a lot of other people finding this thread in the coming days are going to be in the same boat as me. They just want SuperSU so their favorite 1 or 2 apps that require SU can continue to work.
Has anybody tried CF-AutoRoot yet on the NJ1 4.4.2?
Click to expand...
Click to collapse
Tell you what, when I get home from work I will try cfauto root and see if it works.

enewman17 said:
Not sure if it still works but read the op you can Odin a custom recovery then flash super su.
Click to expand...
Click to collapse
I can confirm this as a root method for NJ1. You were exactly right regarding immediately booting into recovery after installing TWRP thru Odin. The files provided in your links (TWRP 2.8.1.0 Odin tar. http://techerrata.com/file/twrp2/d2a....1.0-d2att.tar and
SuperSU http://download.chainfire.eu/589/Sup...etrieve_file=1)
worked exactly as stated.
A BIG thanks to you. I can't live without AdAway, TiBackup and Xposed anymore! The few days without root left me a little grumpy.
And regarding the NJ1 update as a whole...I THINK the baseband upgrade IS an actual upgrade. Since NE4, I always thought Wifi operated was somewhat choppy/throttled. THIS looks to have been improved back to ICS "standards". Re: voice, I've had a handful of dropped calls, broken up calls, and choppy data in low signal areas over the past few months on with NE4. Initial observations (albeit a tad premature) lead me to believe that this has improved as well based on a weeks worth of data use and a few calls in a "controlled" environment (the area and physical structure of my work office complex is not cellular signal friendly to begin with) I have also noticed that boot-up time has improved a bit as well. Thanks again for your efforts with the ATT GS3!

I flashed CF-Auto ROOT via Odin without success, unable to gain root access. Followed your instructions via TWRP and flashed SuperSu 2.16, my SGS3-i747 is properly rooted and functioning perfectly on UCUFNJ1. As always, thank you very kindly for all your valuable time, effort, hard work and guidance. Be well, sir!

mwrobe1 said:
I can confirm this as a root method for NJ1. You were exactly right regarding immediately booting into recovery after installing TWRP thru Odin. The files provided in your links (TWRP 2.8.1.0 Odin tar. http://techerrata.com/file/twrp2/d2a....1.0-d2att.tar and
SuperSU http://download.chainfire.eu/589/Sup...etrieve_file=1)
worked exactly as stated.
Click to expand...
Click to collapse
What version of Odin do we need to flash that TWRP, or do you have a link handy?
I've seen quite a lot of different Odins out there and don't want to brick my phone by using the wrong one.
Any pitfalls to watch out for if using TWRP for the first time? I'm sure there is going to be a bunch of people having to do this now that both CF-AutoRoot and TowelRoot doesn't work anymore.
For me, personally, I just use root for AdFree and to edit the font fallback order to properly support Japanese instead of Chinese glyphs on shared Han-unified Unicode codepoints.

Ark42 said:
What version of Odin do we need to flash that TWRP, or do you have a link handy?
I've seen quite a lot of different Odins out there and don't want to brick my phone by using the wrong one.
Any pitfalls to watch out for if using TWRP for the first time? I'm sure there is going to be a bunch of people having to do this now that both CF-AutoRoot and TowelRoot doesn't work anymore.
For me, personally, I just use root for AdFree and to edit the font fallback order to properly support Japanese instead of Chinese glyphs on shared Han-unified Unicode codepoints.
Click to expand...
Click to collapse
Use Odin 3.0.7
Not really any pitfalls to TWRP. It has an easy clean user interface and it works.
Once you have flash Super Su, in my how to ne4 update there is a flashable stock recovery. You just flash it with TWRP and once you reboot, stock recovery will be back on you phone.

Hi enewman17,
Thanks for your posts and work. I'm hoping you can help me get the new NJ1 update installed and rooted.
Here's where I'm at: AT&T SGS3 on rooted stock NE4, installed using your guides from back in June this year.
The OTA NJ1 update downloaded but failed to install (as did the NE4 OTA back then, I assume because I was rooted).
My phone still has the TWRP recovery from the previous update, so I was hoping I could install using the original OTA cfg file download from the "advanced" section in your OP so as to avoid factory reset, etc.
I downloaded the file, renamed to update.zip, and copied to my SD card. However, when I boot into TWRP and try to install it, I get an error after the system check, something like "assert failed ro.secure==1". I guess I'm doing something wrong, maybe I'm mistaken about how the original OTA is supposed to work?
Again, I'm trying to end up with a stock, but rooted, NJ1 firmware but hopefully without having to reset/lose data and settings on the phone. I don't really care right now about resale or making it look like I haven't messed with it.
Thanks for any help you can provide! Let me know if I can provide any additional details.

I am actually looking to do the exact same thing. Currently rooted, with a lot of the AT&T apps frozen via Titanium Backup.
Hope there is some way to accomplish this without returning to stock!
Thanks in advance!
Bob2014 said:
Hi enewman17,
Thanks for your posts and work. I'm hoping you can help me get the new NJ1 update installed and rooted.
Here's where I'm at: AT&T SGS3 on rooted stock NE4, installed using your guides from back in June this year.
The OTA NJ1 update downloaded but failed to install (as did the NE4 OTA back then, I assume because I was rooted).
My phone still has the TWRP recovery from the previous update, so I was hoping I could install using the original OTA cfg file download from the "advanced" section in your OP so as to avoid factory reset, etc.
I downloaded the file, renamed to update.zip, and copied to my SD card. However, when I boot into TWRP and try to install it, I get an error after the system check, something like "assert failed ro.secure==1". I guess I'm doing something wrong, maybe I'm mistaken about how the original OTA is supposed to work?
Again, I'm trying to end up with a stock, but rooted, NJ1 firmware but hopefully without having to reset/lose data and settings on the phone. I don't really care right now about resale or making it look like I haven't messed with it.
Thanks for any help you can provide! Let me know if I can provide any additional details.
Click to expand...
Click to collapse

Bob2014 said:
Hi enewman17,
Thanks for your posts and work. I'm hoping you can help me get the new NJ1 update installed and rooted.
Here's where I'm at: AT&T SGS3 on rooted stock NE4, installed using your guides from back in June this year.
The OTA NJ1 update downloaded but failed to install (as did the NE4 OTA back then, I assume because I was rooted).
My phone still has the TWRP recovery from the previous update, so I was hoping I could install using the original OTA cfg file download from the "advanced" section in your OP so as to avoid factory reset, etc.
I downloaded the file, renamed to update.zip, and copied to my SD card. However, when I boot into TWRP and try to install it, I get an error after the system check, something like "assert failed ro.secure==1". I guess I'm doing something wrong, maybe I'm mistaken about how the original OTA is supposed to work?
Again, I'm trying to end up with a stock, but rooted, NJ1 firmware but hopefully without having to reset/lose data and settings on the phone. I don't really care right now about resale or making it look like I haven't messed with it.
Thanks for any help you can provide! Let me know if I can provide any additional details.
Click to expand...
Click to collapse
I'll get my stock rooted system dump up later so you can flash in TWRP or CWM.
Do you guys want it packaged with the stock recovery?
mattsternc said:
I am actually looking to do the exact same thing. Currently rooted, with a lot of the AT&T apps frozen via Titanium Backup.
Hope there is some way to accomplish this without returning to stock!
Thanks in advance!
Click to expand...
Click to collapse

[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
.

[Q] What is the best & safest rooting method

Hi everyone.
Is there any way to root the Note 2 N7100 on Samsung official firmware Kitkat without tripping Knox. ??
My bootloader is ND4
My baseband is ND3
My PDA is ND4
If there is a safe method, what is it ...
I tried TR but got that my device is not supported.
My Knox is 0x0
If there isn't & I must trip Knox to root, so what's the best & safest method for rooting my N7100?? My warranty is gone long time ago anyway.
And if I'm gonna trip Knox so I prefer to have a custom recovery, what should I use? I thought of TWRP but found some complaining that 2.8.6 caused loss of signal... What should I use??
One more question, please.
Will rooting my phone & tripping Knox prevent future OTA update to the long awaited official Samsung Lollipop??
If the answer is yes is there a way around it ?? Will I be able to flash it by Odin after getting it from any where like Sammobile ?
Sorry for being long & Thanks

zoghrob said:
Hi everyone.
Is there any way to root the Note 2 N7100 on Samsung official firmware Kitkat without tripping Knox. ??
My bootloader is ND4
My baseband is ND3
My PDA is ND4
If there is a safe method, what is it ...
I tried TR but got that my device is not supported.
My Knox is 0x0
If there isn't & I must trip Knox to root, so what's the best & safest method for rooting my N7100?? My warranty is gone long time ago anyway.
And if I'm gonna trip Knox so I prefer to have a custom recovery, what should I use? I thought of TWRP but found some complaining that 2.8.6 caused loss of signal... What should I use??
One more question, please.
Will rooting my phone & tripping Knox prevent future OTA update to the long awaited official Samsung Lollipop??
If the answer is yes is there a way around it ?? Will I be able to flash it by Odin after getting it from any where like Sammobile ?
Sorry for being long & Thanks
Click to expand...
Click to collapse
Just root it as posted in sticky thread.
You don't have warranty, so just don't bother. Use odin, root and install recovery, then rom.
You can flash stock rom via odin if you want, you can install custom roms via recovery.
I'm using TWRP for 2 years and never had any problem. You can also use Philz. For normal user it doesn't really matter.

yaro666 said:
Just root it as posted in sticky thread.
You don't have warranty, so just don't bother. Use odin, root and install recovery, then rom.
You can flash stock rom via odin if you want, you can install custom roms via recovery.
I'm using TWRP for 2 years and never had any problem. You can also use Philz. For normal user it doesn't really matter.
Click to expand...
Click to collapse
Thank you very much for your help.
Actually I found no sticky threads for rooting 4.4.2. Most of the sticky threads are dating since 2012 with 4.1.2 & 4.3.
However by searching I found 2 threads for 4.4.2, one of them is
http://forum.xda-developers.com/showthread.php?t=2767604
This one uses CF-auto-root... but no mention about any custom recovery. Will I lose root or mess things up if I install TWRP after that??
The other thread is
http://forum.xda-developers.com/showthread.php?t=2730764
This one uses the typical steps that I know, custom recovery then SuperSU. But it uses Philz recovery. Can I substitute it with TWRP??
Thank you for your help & patience.

The most important question: Why do you want to root?
If you like to flash a custom rom no need for root, any custom recovery - TWRP or CWM - flashed with Odin will do.

Androidwizzard said:
The most important question: Why do you want to root?
If you like to flash a custom rom no need for root, any custom recovery - TWRP or CWM - flashed with Odin will do.
Click to expand...
Click to collapse
I'm not planning to flash custom rom right now, may be later.
I want to root to be able to use some apps that require root. Plus, having full control over my phone.

In odin you have option to choose recovery file - AP.
After flashing recovery just install superSU via recovery.
DO a backup of your device and EFS before you flash anything.

yaro666 said:
In odin you have option to choose recovery file - AP.
After flashing recovery just install superSU via recovery.
DO a backup of your device and EFS before you flash anything.
Click to expand...
Click to collapse
Thank you for your help.
I don't know how to make a backup without recovery. So I flashed TWRP 2.8.6, took a backup then installed SuperSU via TWRP.
All went well except that I lost the signal and IMEI.
I found that I flashed TWRP t03gup while I should flashed t03g.
I reflashed the correct file then flashed the modem.bin of XXUFND3.
Everything thing is back to normal again except 2 things:
The icon of my service provider shifts place to the last app page after reboot, no matter where I place it...
The phone status shows custom (expected) but stays so even after using Triangle Away.
Is it better if I flash the stock firmware then recovery then SuperSU? ?? Or flashing the modem as I did was enough to straighten things up? ?
Thank you for your patience and help.

zoghrob said:
Thank you for your help.
I don't know how to make a backup without recovery. So I flashed TWRP 2.8.6, took a backup then installed SuperSU via TWRP.
All went well except that I lost the signal and IMEI.
I found that I flashed TWRP t03gup while I should flashed t03g.
I reflashed the correct file then flashed the modem.bin of XXUFND3.
Everything thing is back to normal again except 2 things:
The icon of my service provider shifts place to the last app page after reboot, no matter where I place it...
The phone status shows custom (expected) but stays so even after using Triangle Away.
Is it better if I flash the stock firmware then recovery then SuperSU? ?? Or flashing the modem as I did was enough to straighten things up? ?
Thank you for your patience and help.
Click to expand...
Click to collapse
It should be OK just as it is now, but if you have 30min free time, you can flash stock, root, custom rom with full wipe to make sure you have everything straighten up

yaro666 said:
It should be OK just as it is now, but if you have 30min free time, you can flash stock, root, custom rom with full wipe to make sure you have everything straighten up
Click to expand...
Click to collapse
30 min or even an hour is ok by me...
I'll do it right away. Flash stock, TWRP recovery then root with SuperSU.
As for the custom rom it'll have to wait as I didn't make up my mind which Lollipop to get... I'm kinda confused about it very much. I can't decide which to get.
I'm open for suggestions. lol
Thanks a million for your support.

If you need your phone for business don't flash lollipop. Still in beta phase, so bugs are occuring often.
I use dr. ketan's V14 and it's the most stable rom I have used

yaro666 said:
If you need your phone for business don't flash lollipop. Still in beta phase, so bugs are occuring often.
I use dr. ketan's V14 and it's the most stable rom I have used
Click to expand...
Click to collapse
My phone is for personal use not for business.
But I think I'll follow your advice & give Dr. Ketan's V14 a try.
I did flash stock firmware then flashed TWRP 2.8.6 (correct file this time.. lol) then installed root.
I did backup my phone & EFS by TWRP. All is excellent now.
Now I'll backup my contacts, sms, apps & data using Titanium back up then go for Dr. ketan's rom.
Wish me luck.
Thanks.

you will be positively surprised if youhad stock the whole time.
cheers
salute

yaro666 said:
you will be positively surprised if youhad stock the whole time.
cheers
salute
Click to expand...
Click to collapse
Wow... it's awesome. ..
Thumbs up. ..
You are right.
I'm wondering right now how did I stuck to the stock firmware all the past time.
Thanks.