yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab Pro 12.2, 10.1, 8.4 General] trefe90:
My Tablet is SM-T320

The kernel version is EUR XX T320XXU1ANAG NA26R1

Build Number KOT49H.T320XXU1ANAI

But when connected to the computer that displays Kies PDA: NAI / CSC: NB2 (ZTO)

TowelRoot v2 installed, but unable to root. The unit restarts after clicking on the "Make it Rain" button.

About Knox.

From what I have read, install whatever official firmware (stock) via Odin will not trigger the flag. However I had some doubts:

1 - The fact that I install an earlier version of the firmware I have installed will raise the flag?

2 - Install any different firmware from my region will raise the flag?

About point 1 and 2. Some users report that failed to return the original firmware by Odin after installing a firmware from a different region.

3 - If an erro occurs and the installation via odin not finish successfully, thus leaving the option to restore the Kies, this procedure will also raise the flag?
[Galaxy Tab Pro 12.2, 10.1, 8.4 General] Lolento:
guys,

Is root maintained if you get an OTA software update?
[Galaxy Tab Pro 12.2, 10.1, 8.4 General] RavenY2K3:
1, correct, you can't go back to an earlier firmware you will trigger Knox.

2, not necessarily, providing it's equal to or greater than the currently installed firmware, you should be fine.

3, the worst you'll need to do is just reflash the kernel, but it's that quick you'll be very unlucky if it happened.

No, regardless of what root method you use.You will need to do what practically everyone here does anyway, and flash any new firmware manually.
[Galaxy Tab Pro 12.2, 10.1, 8.4 General] Lolento:
Are you guys experiencing any random reboots after using towel root?

I am seeing some but don't know if it is specifically having to do with towel root.
[Galaxy Tab Pro 12.2, 10.1, 8.4 General] RavenY2K3:
None whatsoever, just as it was before i rooted it.

What sort of root apps have you installed since rooting it? Could be one of those causing the problem, rooting alone shouldn't do what you're experiencing.
[Galaxy Tab Pro 12.2, 10.1, 8.4 General] Lolento:
I am surprised that no one Iis reporting random reboot issue.

This may not be due to towel root but inherent with the NE3 firmware, a lot of people are reporting this if you look around.
[Galaxy Tab Pro 12.2, 10.1, 8.4 General] scomat:
I was getting it a lot after I had disabled all the knox services on NE3. Done fresh install kept knox active and never had a problem since. Do you have knox disabled?
[Galaxy Tab Pro 12.2, 10.1, 8.4 General] RavenY2K3:
That's one big difference in my setup compared to yours I suppose, I'm using the latest firmware for my region which is ND3 but using a NE3 kernel.
[Galaxy Tab Pro 12.2, 10.1, 8.4 General] Lolento:
Thanks guys, unfortunately I cannot downgrade firmware.

I did disable Knox, I will try to enable it. Does Knox mess with root apps?
[Galaxy Tab Pro 12.2, 10.1, 8.4 General] RavenY2K3:
There's no way of downgrading, you may have even tripped it just trying to go down, once rooted, SuperSU by Chainfire will take care of Knox.
[Galaxy Tab Pro 12.2, 10.1, 8.4 General] MaluNoPeleke:
I hope there will be a way to root the SM-T520 without tripping KNOX
[Galaxy Tab Pro 12.2, 10.1, 8.4 General] Lolento:
Ok, reporting back.

Reflashed original firmware, towel root, and let supersu take care of KNOX.

No reboot so far, hope I didn't speak too soon.

For reference, before I had further disabled other KNOX services thru Titianium Backup and this time I didn't.
[Galaxy Tab Pro 12.2, 10.1, 8.4 General] konsolen:
reboot

I had many Reboots since the NB firmware version.

Now i flashed the New NF3 and no reboots.

But towelroot doesnt work anymore.
[Galaxy Tab Pro 12.2, 10.1, 8.4 General] cheeb:
Thanks for these very straightforward directions on applying root to this device without tripping knox. Loving this tablet just a little bit more now!:good:
[Galaxy Tab Pro 12.2, 10.1, 8.4 General] treier57lol:
I tried it on my SM-T525 and it worked but my wifi doesn't work anymore even after data wipe. Plz help, have to waste my cellular. (Root also success)
[Galaxy Tab Pro 12.2, 10.1, 8.4 General] karimrim:
Hi, getting one soon (seemed to me the best tablet even if old ^^)

Are you on SM-T320 ?
[Galaxy Tab Pro 12.2, 10.1, 8.4 General] osssinator:
Instead of flashin a rootable kernel, can't we just flash a rootable firmware? And then to run the procedure with towelroot.
[Galaxy Tab Pro 12.2, 10.1, 8.4 General] RavenY2K3:
Double post
[Galaxy Tab Pro 12.2, 10.1, 8.4 General] RavenY2K3:
Doing that will trigger the counter, which this method doesn't do.
[Galaxy Tab Pro 12.2, 10.1, 8.4 General] bbsc:
Yes, it's definitely possible.

But you'll have a rooted device with firmware which is not up-to-date.

Or you'll lose root if you upgrade this firmware.

That's why this trick with temporary kernel change is needed.
[Galaxy Tab Pro 12.2, 10.1, 8.4 General] osssinator:
In my i9505 after the procedure kitkat/rootable kernel/towelroot, you were able to flash back the previous kernel, and still to keep the counter not tripped.
[Galaxy Tab Pro 12.2, 10.1, 8.4 General] bbsc:
Exactly the same is with TabPro.

And one thing more.

It may be a little tricky to find a proper kernel. AOC1 for T320 doesn't let Wi-Fi work in some firmwares.

I've tried to use kernels from several different firmwares and found that BNE4 works for my T320 fine with towelroot v3.

So I place it here. Just in case.
[Galaxy Tab Pro 12.2, 10.1, 8.4 General] ClintE1956:
A year later, GTP8.4 still running great. Now off warranty.

Finally an AICP MM build for the SM-T320 is available, so time to update to latest stock firmware to make sure radio etc. is current, then start testing MM goodness.

Currently running KOT49H.T320UEU1ANK1 original out-of-box KK build, rooted with this thread's method. Replaced the custom kernel with original after towelroot was successful. I think at some point I installed a patch to fix mpdecision processor sticking:

http://xdaforums.com/galaxy-tab-pro-12-10-8/help/governor-issue-t2962238/post57452140#post57452140

Is there anything special I need to do beyond factory reset to get the tab back to stock, before updating to latest Samsung factory firmware? Or, is it best to just flash lastest Samsung factory image (after TiBkp of app data) without doing the factory reset on current build?

Also, I dislike downloading firmware from Samsung via the tab's software update function over wifi, so is there anywhere that has latest stock firmware to flash via Odin?

Thanks in advance
[Galaxy Tab Pro 12.2, 10.1, 8.4 General] rnwalker7:
I got the AOC1 build from SamMobile and flashed via Odin (use the Cellular South image for US, Rogers for Canada). Although, I was able to unlock the bootloader on ANK1 using CF Autoroot. I'm not sure Towelroot will allow you to flash non-Samsung ROMs...but then again, I only used Towelroot on my old Galaxy S3 after taking the Verizon 4.3 OTA (which permanently locked my bootloader). NOTE: Unlocking the bootloader WILL void your warranty, since it blows a Q-fuse (thanks to Knox).
[Galaxy Tab Pro 12.2, 10.1, 8.4 General] ClintE1956:
Duh me, SamMobile, Samsung owners' savior. That one slipped my mind completely. Think it had me create an account to grab something there some time ago.

So, you're saying there is a possibility I could permanently lock the bootloader?

I don't mind voiding warranty, since it's expired now. It's custom rom time. Been waiting for AICP rom availability, and looks like it came at just the right time. (Anyone interested in custom roms, look into AICP. Best I've seen so far, especially for the GS3.)

Gotta look into the bootloader thing...

Thank you, very much appreciated!
[Galaxy Tab Pro 12.2, 10.1, 8.4 General] rnwalker7:
Yes...download it from https://autoroot.chainfire.eu, search for SM-T320, and download. Flash via Odin, and you're set! I've run a lot of different ROMs on this device, both TW and AOSP. However, I think NK1 is the last update that is vulnerable to Chainfire's Autoroot, so don't update until after you unlock! Better yet, just extract the radio image and flash it.
[Galaxy Tab Pro 12.2, 10.1, 8.4 General] ClintE1956:
Ok, so you're saying that I need to unlock the bootloader via chainfire's cf-autoroot first (since I have an earlier build), then flash the latest stock samsung firmware. That should update all relevant devices such as radio etc. This way the bootloader *stays* unlocked, correct? I (incorrectly?) figured if the entire stock firmware is flashed, then it will flash newer bootloader (if available) and lock it.

Apologies and please excuse redundant / noob questions about this particular point, but I want to make sure I have a completely unlocked device (don't care about warranty bits etc. because the tab is now off warranty) so that I am free to do anything I need/want to do without fear of locking something down permanently.

Thanks for quick reply and advice!
[Galaxy Tab Pro 12.2, 10.1, 8.4 General] rnwalker7:
Correct...the bootloader will remain unlocked. I tested it out by flashing TWRP last night, since I had noticed I had the stock recovery. ;) So to recap, flash CF Autoroot, boot, (optional, but recommended...make a backup,) reboot into Download Mode, flash the new AOC1 image, then start into that and install SuperSU.

However, I'm holding off on installing anything MM until the SD card and Bluetooth bugs are fixed. Resurrection Remix 5.1.1 works very well on my Droid Turbo, so I may run that on my Tab Pro until then. And no worries on the questions...we've all been there. I was just a lurker until recently.
[Galaxy Tab Pro 12.2, 10.1, 8.4 General] ClintE1956:
Now I am confused. Visited ChainFire's CF-AutoRoot page, downloaded proper file for SM-T320. While reading info/instructions at top of page, I see:

CF-AUTO-ROOT IS CURRENTLY NOT OPERATIONAL FOR ANDROID 6.0+, OR SAMSUNG ON ANDROID 5.1+

I'm assuming that means stock Samsung MM or LP builds, which of course are not available for the SM-T320.

But, I notice at end of info for Odin flashing:

UNLOCK BOOTLOADERS

If you have locked bootloaders, flashing one of these will probably brick your device - with the exception of Nexus devices, which will usually automatically "OEM unlock" and wipe your data !

I'm assuming I have a locked bootloader, since all I did to root this on the stock KOT49H.T320UEU1ANK1 build was the procedure described in this thread. I did flash original kernel back to the tab after rooting with the custom kernel (also per this thread), and that's the way it has stayed ever since then (a little over a year ago).

Download mode screen shows:

ODIN MODE

PRODUCT NAME: SM-T320

CURRENT BINARY: Samsung Official

SYSTEM STATUS: Custom

KNOX KERNEL LOCK: 0x0

KNOX WARRANTY VOID: 0x0

QUALCOMM SECUREBOOT: ENABLE (CSB)

AP SWREV: S1, T1, R1, A1, P1

WRITE PROTECTION: Enable

UDC START

And when I start stock recovery, it shows:

Android system recovery <3e>

KOT49H.T320UEU1ANK1

and the recovery options menu.

I see several advantages to running 5.1.x, and if there are sdcard and bluetooth issues with 6.x that would be a deal-breaker (for me) with the current test 6.x AICP rom build that I'm interested in. However, I think I prefer to just wait until those MM issues are fixed instead of taking the time to get used to a 5.1.x rom (no 5.1.x AICP available), then switching again to MM . One big advantage I can see with unlocking & flashing TWRP is having nandroid backup capabilities, which I have used extensively on my GS3.

Think I'm going to have to ponder all the plus/minus sides of changing systems on the tab at this time.

I'd like to apologize for sort of hijacking this thread to discuss these topics. Hope I'm not stepping too far away from the original intent of the thread.

Thanks again, all your info is very much appreciated. Hope you have safe and happy holiday season!
[Galaxy Tab Pro 12.2, 10.1, 8.4 General] rnwalker7:
Sorry for the delay, been on the road the last few days visiting family. Anyways, I think that warning is posted for those who have a carrier-locked bootloader...which doesn't apply to WiFi-only devices. Usually they have some code in their aboot that breaks the bootloader chain if you try to flash an unofficial image; these are almost always fixable by flashing the stock firmware via Odin or Kies. Anyways, I'll let you decide which route you want to go...feel free to PM me if you need any help!
[Galaxy Tab Pro 12.2, 10.1, 8.4 General] Ichijoe:
Done this wanted to say Thanks (To the Op!), for posting this howto. And, that it works like a dream for me.

I managed to fudged'up my T325 a few times by ditching something related to the Calender Database, without which I was unable to use Google's Calender App.

So I managed to track down the exact DBT XXU1BOC1 Firmware from the Net. (Of which I flashed on occasion about 3, or 4 times now).

Flashing this over Odin has NOT tripped up my Knox counter, and neither has TowelRoot!

So I'm grateful to be able to at least be able root enough to ditch the most obvious Bloatware(s), and be able to install AdAway onto this Device.

God how I love AdAway!
[Galaxy Tab Pro 12.2, 10.1, 8.4 General] ClintE1956:
Thanks for the info about gtp bootloader; thought that was the case, but wasn't sure. Also not sure if I want to go through all the reloading etc. on LP at this time if they're working on fixes for the 6.x issues.

Thanks again for all the info, much appreciated. Cheers!
[Galaxy Tab Pro 12.2, 10.1, 8.4 General] osssinator:
Hi there,

1. Which firmwares are recommended for the T320?

2. Can I flash back the default kernel, after I root the device, or I should keep the rootable one?

Kind Regards,
[Galaxy Tab Pro 12.2, 10.1, 8.4 General] ObiDanKenobi:
you can flash the one of your current firmware back, after you rooted.
[Galaxy Tab Pro 12.2, 10.1, 8.4 General] MiMo1111:
Towelroot - use older kernel

Im new on these things, can i revert back to an older kernel?

And Does it matter if my Tab Pro 8.4 WiFi SM-T320 is a Nordic countries device, can i still use these provided files?

And which one should i use, there are two different versions provided in this thread for the 8.4 Tab Pro SM-T320. I currently have Android 4.4.4 if i remember correct, or maybe it was 4.4.2?

I want to use Towelroot but my device is newer than the latest accepted date for Towelroot, so according to instructions i should use this kernel file in this thread to revert back to an older one.

Thanks for some help.
[Galaxy Tab Pro 12.2, 10.1, 8.4 General] rnwalker7:
I don't think you can flash an older kernel with a locked bootloader, especially with the Knox bootloader Samsung shipped out (you'll probably brick your device). The only way to revert to an older kernel (i.e. older firmware) is to unlock the bootloader. At which point, it's kinda pointless to use Towelroot, since I assume you don't want to void warranty. You might try Kingroot, but being Chinese, I'd be careful. Some other devs have been wary of the data the app sends back to its servers.
[Galaxy Tab Pro 12.2, 10.1, 8.4 General] waylo:
No, that's the whole point of this thread. You can flash older kernels and not trip Knox. You flash the kernel through Odin, run towel root, then flash back the newer kernel. Knox gets tripped if you flash an unofficial kernel, recovery, or system partition.

But really, this tablet is old enough that the manufacturers warranty is over, so Knox trip doesn't matter anymore.
[Galaxy Tab Pro 12.2, 10.1, 8.4 General] MiMo1111:
Thats what i thought but then i saw that the warranty is 24 month from the store this is bought from, so thats why i started to look for this root method without voiding the warranty.

Anyway would you mind telling me which file i should use in Odin, since i can see two different files in the first post of this thread that are for the tab Pro 8.4 WiFi SM-T320.

I have a nordic model Tab Pro, i don't know if that matters and if i can use these files anyway for my Tab Pro SM-T320 Wifi?
[Galaxy Tab Pro 12.2, 10.1, 8.4 General] waylo:
Can you read off the model # from the box? Also, what kernel are you on? Located under the device settings.

We have to make sure the kernel is compatible, and you would also want a flashable copy of the existing kernel. This thread is a bit old so not sure how available that might be.
[Galaxy Tab Pro 12.2, 10.1, 8.4 General] MiMo1111:
Thanks for your answer. The model number on the box says SM-T320 (8.4 inch screen, WIFI only), and the Kernel in the device settings says 3.4.0-2690686 / dpi@SWDD5510 #1 (Wed, Sep 3, 13:34:57, KST 2014)

And build number says: KOT49H. T320XXU1BNI1

Thanks in advance.
[Galaxy Tab Pro 12.2, 10.1, 8.4 General] :
Great work man.
[Galaxy Tab Pro 12.2, 10.1, 8.4 General] waylo:
Here are some general steps. There are a few unknowns here though.

1. We would want to flash back a kernel that is before 6/3/2014. Yours is from afterwards, so the towelroot exploit is patched, probably. You can try running towelroot to see if it works and then test for root, but most likely it won't work.

2. First, get the necessary backups in case something goes odd.

You are currently running version NI1. Your region model is XXU1B, which seems to be most of Europe and some South American countries.

Go here: http://updato.com/firmware-archive-select-model?r=NEE&v=&q=t320

and download it. This is the Nordic version of the firmware, though it's probably the same as the other countries with the XXU1B designation. This is the backup zip for exactly what you have now. In case something goes really weird, you can ODIN this and your tablet will be back to its current state, though your data may be wiped.

3. From what I've read from other users with the NI1 firmware, you can ODIN the rootable kernel in the original post here. If it doesn't work, you have your backup file to ODIN restore back to normal.

ODIN the rootable kernel from the first post, for the T320 wifi-only (that is what you have right?). See if it boots up and runs. If so, then run towelroot. Then install supersu.

4. Here's the decision point:

You can continue to run with the same kernel on this thread. I don't know if it matters at all.

OR

You can make your own kernel tar to restore yourself to the newer kernel specific for your region build. Or you can see if someone here has made it already. My quick and dirty search has not turned up any NI1 kernel links on this thread, though several users have done it.

If you decide you want to flash your original kernel back, and no one has it for you, you'll have to make it yourself. Go to this thread:

http://xdaforums.com/showthread.php?t=2446269

and use the utility to make the boot.img from your downloaded backup into a flashable N1 kernel tar file.
[Galaxy Tab Pro 12.2, 10.1, 8.4 General] MiMo1111:
Wow, thanks for the detailed information. About the kernel, what would the downsides be to continue using a kernel from another region and a older kernel? Other language than my current?

EDIT: I tested Towelroot on my Tab pro, it said my tab pro is not compatible. Sorry for not understanding the process of creating an own kernel. I read the instructions on the provided link, it said that one is suppose to make a md5 file from a img file or from a boot file or something similar to that, but which file is the original file i should use to make my own kernel?

So which is the image file i should use to make the tar.md5 file?
[Galaxy Tab Pro 12.2, 10.1, 8.4 General] waylo:
The kernel is in the boot.img file. It's pretty small, usually <10 megs. So take that from the backup zip you downloaded and use the script to make your flashable tar.md5 file. I've never used the script personally, but you can post on that thread.

I don't know of any real downside to having the mismatched kernel. I ran with the towelroot-able kernel for quite a while before flashing back the matching one and really did not see anything noticeable. But I was at least on the same country-build, so your results may differ somewhat. The hardware is the same though.
[Galaxy Tab Pro 12.2, 10.1, 8.4 General] MiMo1111:
Thanks, do you mean from the original Kernel from the link you provided, in that case its only 1 file that is a tar.md5 file and its a big file around over 1 GB or something like that, how do i get the kernel /boot file from that big file?

Or do you mean the boot.img file from the rootable kernel from this thread, that files is about 10 Mbyte?

In that case i can not open / unzip the "boot" file in Win XP, it says:

"ERROR: internal error processing ISO image"

The rootable kernel downloaded from this thread is a ZIP file named T320_Kernel, when i unzip that file i get another ZIP file called "boot", and that file i can not unzip.

It seems it is not a WinZip compatible file even though it has a WinZip file icon?

Also in Mac OS X it says that the "image not recognized".
[Galaxy Tab Pro 12.2, 10.1, 8.4 General] waylo:
The file you need to bake your own kernel is within the large 1gb file. You have to find a utility (7zip works fine) and pull out the boot.img from there. Easy peezy.
[Galaxy Tab Pro 12.2, 10.1, 8.4 General] dboy 14:
Wtf...does nobody else have a ****ing smt560. Like i have not seen that model number menyioned one ****ing time
[Galaxy Tab Pro 12.2, 10.1, 8.4 General] MagicianPe:
Post only to confirm that the method of the OP:

- Flash the lastest firmware with ODIN

- Install Towelroot, do not execute, copy SuperSU to SD

- Flash the old vulnerable kernel

- Execute Towelroot and reboot

- Install and execute SuperSU in System

- Flash the new original Kernel from the latest Firmware

- Boot into recovery Format Data / Factory reset.

- Verify SuperSU, reinstall if necessary

Is working for the 2017 security update of the firmware for the SM-T320: T320XXU1BQB2_T320UVS1BQA1_PEO

Regards.
[Galaxy Tab Pro 12.2, 10.1, 8.4 General] jacomail95:
This method worked also for me, thank you. Can I now modify build prop, or to put scripts in system or to flash TWRP using the TWRP app without tripping Knox?

Inviato dal mio SM-T325 con Tapatalk 2
[Galaxy Tab Pro 12.2, 10.1, 8.4 General] tinasoft:
Ok Merci
[Galaxy Tab Pro 12.2, 10.1, 8.4 General] nagendraps:
Thanks for tip RavenY2K3, My T-325 has NF3 firmware procured from Hong Kong, If I flash this NE5 repackaged kernel (lower version than NF3) via odin will it trigger the flag?

thanks
[Galaxy Tab Pro 12.2, 10.1, 8.4 General] TabLife:
anyone tried this with 8。4 3G (sm-t321)?
[Galaxy Tab Pro 12.2, 10.1, 8.4 General] RavenY2K3:
Oooooh, that, I don't know! I seem to recall it's triggered by trying to lower the boot loader, not the kernel. But everyone runs the risk each time they mess around with flashing.
[Galaxy Tab Pro 12.2, 10.1, 8.4 General] csjneek:
I did that and knox remained 0, but random reboots came back, then I reinstalled NF3 kernel only (thought is newer and better) root remained, knox also remained 0, but still random reboots.

Next day got tired of all this and rooted normally with cf-autoroot in odin (knox banged) but then never had a reboot.

Then later installed CM11 and I'm satisfied with it, veery fast and very stable also better battery.

PS. previous I had NF3 BTU from samfirmware which with original kernel unrooted was rockstable.
[Galaxy Tab Pro 12.2, 10.1, 8.4 General] LyuboA:
did same thing man rooted my T325 XXU1BNF3 with this kernel after that flashed with odin XXU1BNF3 kernel everything remained official knox 0x0 but a lot of random reboots i dont really care for knox so i flashed custom recovery and root again with CF-Root = no more random reboots