Database Develop

AT&T Software Update

After rooting I deleted all of the AT&T and Facebook software. I note that the AT&T Software Update check button remains under Phone Settings, but more disturbingly was a pop-up this morning stating that AT&T Update was checking for updates! Fortunately I happen to be in a wifi-only area right now -- no cell coverage so the "network is not available".
So far Google has NOT been my friend. Is anyone aware of a switch to fully disable or script to remove this? Thanks! --Larry

Assuming you've flashed a custom recovery image, then when it asks to install the update, just "let it". It will reboot the phone into the recovery, and you can immediately cancel. The phone will never prompt you to update after that even though you're still on the old version.
Sent from my HTC first using xda premium

nuclear_eclipse said:
Assuming you've flashed a custom recovery image, then when it asks to install the update, just "let it". It will reboot the phone into the recovery, and you can immediately cancel. The phone will never prompt you to update after that even though you're still on the old version.
Sent from my HTC first using xda premium
Click to expand...
Click to collapse
But if doesn't find an update & reboot to recovery, will it simply keep searching (& using battery)?
I rebooted and the popup hasn't returned, but I still would like to disable/remove the whole thing.

amphi66 said:
But if doesn't find an update & reboot to recovery, will it simply keep searching (& using battery)?
I rebooted and the popup hasn't returned, but I still would like to disable/remove the whole thing.
Click to expand...
Click to collapse
Nuke the 2 zips in /system/etc/security. That will kill OTAs altogether
Sent from my HTC first using Tapatalk 2

jmz said:
Nuke the 2 zips in /system/etc/security. That will kill OTAs altogether
Sent from my HTC first using Tapatalk 2
Click to expand...
Click to collapse
"zips" deleted. Thank you!

amphi66 said:
"zips" deleted. Thank you!
Click to expand...
Click to collapse
Because I can't leave well enough alone (& with "zips" deleted & other AT&T apps deleted) since I couldn't remove it, I pressed the "AT&T Software Update" button in Settings. Surprisingly, after a brief search the phone began to download an update! I forced an immediate reboot to recocery and did a backup restore to insure it was stopped.
Question: As I am running build 1.08.502.1 CL180011, Baseband version 1.15.40.00.13_2_10.64.40.33AL what is this update trying to do and should I let it try to install. I certainly do not want to impact my s-off, root, or deodexed ROM.
Thanks.

[Q] Disable Hands Free Activation

I've seen several discussions about this around the web, but none of the solutions I've read have helped me.
I have the Sprint HTC One M8 with custom ROM (ViperOneM8). The phone is activated and works fully, yet on reboot I always get the 'Hands Free Activation' wizard. If I hit Activate and then Done it goes away and I can use my phone normally, but every reboot brings it back up again.
Ideas?

I'll add that I have custom recovery (TWRP), rooted, custom ROM, and S-Off.

Htc m8 and sprint
aprwx said:
I've seen several discussions about this around the web, but none of the solutions I've read have helped me.
I have the Sprint HTC One M8 with custom ROM (ViperOneM8). The phone is activated and works fully, yet on reboot I always get the 'Hands Free Activation' wizard. If I hit Activate and then Done it goes away and I can use my phone normally, but every reboot brings it back up again.
Ideas?
Click to expand...
Click to collapse
Sorry I have the same issue with mine and finally ive called htc for a swap out phone to see if its a software defect. htc said that if it still occures it may bee an issue with sprint...

Are you running stock, or did you install a custom rom?
Sent from my Sprint HTC One M8

... I ask because when I first bought the phone it activated fine (with delay because it was the same day that the Galaxy S5 was released and Sprint had a delay activating phones that day)....but then I installed a custom ROM and am having this problem now with the custom ROM.

Thought I'd post here to help others who stumble on this thread....
This removed Hands Free Activation for me on Sprint's HTC One M8:
j to the 4n said:
Re: Hands Free Activation ... http://forum.xda-developers.com/showpost.php?p=50392144&postcount=2287
Click to expand...
Click to collapse
This worked for me, but a couple notes:
- I wasn't able to do the command line or Root Explorer. Both methods gave me errors, seemingly that I didn't have permissions to rename or delete the file. Why would that be? I went into TWRP and 'Fixed Permissions' but that didn't help. -- found it interesting that boot up is a LOT slower now that I fixed permissions.
- I ended up going into TWRP, mounting system and then going into TWRP's file manager to rename the file. Now Hands Free Activation no longer comes up (Thank you!), but I also note that neither PRL Update or Update Profile do anything now. Not a huge deal because before they just errored out anyway, but I would think it would be important to be able to do PRL/Profile updates.

aprwx said:
Thought I'd post here to help others who stumble on this thread....
This removed Hands Free Activation for me on Sprint's HTC One M8:
This worked for me, but a couple notes:
- I wasn't able to do the command line or Root Explorer. Both methods gave me errors, seemingly that I didn't have permissions to rename or delete the file. Why would that be? I went into TWRP and 'Fixed Permissions' but that didn't help. -- found it interesting that boot up is a LOT slower now that I fixed permissions.
- I ended up going into TWRP, mounting system and then going into TWRP's file manager to rename the file. Now Hands Free Activation no longer comes up (Thank you!), but I also note that neither PRL Update or Update Profile do anything now. Not a huge deal because before they just errored out anyway, but I would think it would be important to be able to do PRL/Profile updates.
Click to expand...
Click to collapse
Thanks for the heads up about this. I just changed the .apk to .bak with root explorer, noted the path and file name so I can change it back to update the pir and prl. Mine didn't usually error out.

aprwx said:
I've seen several discussions about this around the web, but none of the solutions I've read have helped me.
I have the Sprint HTC One M8 with custom ROM (ViperOneM8). The phone is activated and works fully, yet on reboot I always get the 'Hands Free Activation' wizard. If I hit Activate and then Done it goes away and I can use my phone normally, but every reboot brings it back up again.
Ideas?
Click to expand...
Click to collapse
I'd find another ROM.
I think you are always safest to stay with Sprint "Native" ROMs on a Sprint Phone. Mainly because the developer usually doesn't have a Sprint Phone to fully flesh it out on a regular day to day basis. There are subtle differences between all the carriers. You also end up with a Build of Android that exactly matches the corresponding build of Firmware.
Once you do get back on a native ROM you *MIGHT* have to do a ##72786# (full wipe) to get things back in order.

What I think are related issues lead me to a fix that was common to several problems I was having:
http://forum.xda-developers.com/sprint-htc-one-m8/general/fix-data-issues-t2819915

simply freeze vDM

[HELP] OTA KitKat update error on rooted D950

I have a (previously) rooted D950, and I can't get the OTA At&t update to install. I've completely removed root, and double checked through root checker that it's gone, and the update errors out every time with a message about having been rooted.
I read another thread where some people report being able to retain root after receiving the update THEN downgrading and rooting 4.2.2., then installing the OTA again, but it seems that I jumped the gun and rooted first, which is now causing the install to error out.
Has anyone else experienced this? Found a workaround? Ideas? Totally frustrating.
Sent from my LG-D950 using xda premium

Here is the link to a detailed guide . Dev hyelton's page includes links to AT&T ROMs.
If you need help with LG Flash Tool:
- Connect your phone with usb to laptop/computer and open device manager
- seek for Ports: COM & LPT, right click onto Android LTE usb port connection, click "properties", click "Advanced", then change port number to number 41, click "OK"
- DOWNLOAD LG Flash Tool and install .exe
- DOWNLOAD MegaLock.zip (3kb), unzipped (7kb)
- Exchange MegaLock.dll in your system folder "LG" with the unzipped MegaLock.dll file that you have downloaded
- Open LG Flash Tool, input .dll file of downloaded stock rom.zip folder and input .tot file of this folder
- Click onto USB instead of LAN, then click "OK"
- Left arrow at the window top should be enlightened now
- Click onto this arrow
- Wait for all popup windows telling milky way download and connections to fail
- Wait then for the check of CRC and .dll files
- One or all ports should be opened, "READY" enlightened
- Disconnect your phone from computer
- Connect again and watch the immediate start of the flashing process
- After completion you must install most of the app updates, update your LG and/or AT&T profile before installing kitkat update.zip
If you'll stick in updating stock rom to kitkat, watch my video on YouTube (it's about LS995 Sprint, but AT&T LG Flex will proof the same installation process):
Visit my blog at http://www.myreviewsofreviews.for the detailed description how to avoid bootloop during the installation of LG Kitkat update.zip via ADB sideload

Thanks, but this is not a fix. Unfortunately, that guide is of no use since his links are still down. Further, I was hoping for feedback from others who have experienced this issue, and found a resolution. I have read that this is also happening on devices that have not been rooted.
I am not looking to flash a rom through FlashTool. I'm looking to fix the OTA error. All I want to do is install the OTA update.

lorawithano said:
Thanks, but this is not a fix. Unfortunately, that guide is of no use since his links are still down. Further, I was hoping for feedback from others who have experienced this issue, and found a resolution. I have read that this is also happening on devices that have not been rooted.
I am not looking to flash a rom through FlashTool. I'm looking to fix the OTA error. All I want to do is install the OTA update.
Click to expand...
Click to collapse
Not sure what you were hoping for but the guide is correct process for your problem. You need to flash back to 4.2, don't touch anything in the way of modifying system files or deleting bloatware, sign into your main Google account, update all your apps...then root the phone and when it reboots look for the ota. I would give it a couple min to setup after flashing back to 4.2 so that it successfully finds the update rather than telling you you're on the most current software. I had your exact problem too, I was one of the first AT&T users on here to take the update I tried everything to
A: retain root with supersu features and some root cloaker programs etcetera
B: factory reset, call AT&T, to get them to push the update again because I just could not get it to successfully flash without detecting suspicion of root.
Flashing back to 4.2 to retain root worked for me over 4 times now on 3 different flex phones (I had some hardware and then software issues on my replacement model)
Sent from my LG-D950 using XDA Premium 4 mobile app

brittoking said:
Not sure what you were hoping for but the guide is correct process for your problem. You need to flash back to 4.2, don't touch anything in the way of modifying system files or deleting bloatware, sign into your main Google account, update all your apps...then root the phone and when it reboots look for the ota. I would give it a couple min to setup after flashing back to 4.2 so that it successfully finds the update rather than telling you you're on the most current software. I had your exact problem too, I was one of the first AT&T users on here to take the update I tried everything to
A: retain root with supersu features and some root cloaker programs etcetera
B: factory reset, call AT&T, to get them to push the update again because I just could not get it to successfully flash without detecting suspicion of root.
Flashing back to 4.2 to retain root worked for me over 4 times now on 3 different flex phones (I had some hardware and then software issues on my replacement model)
Sent from my LG-D950 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You say flash back to 4.2, but I am already on 4.2. Never left 4.2. That's the issue. The device is defective. They're sending me a new one.

lorawithano said:
You say flash back to 4.2, but I am already on 4.2. Never left 4.2. That's the issue. The device is defective. They're sending me a new one.
Click to expand...
Click to collapse
You didn't understand my post at all it seems, I gave you the instructions to flash back to STOCK which would have fixed your problem. I did accidentally word my post incorrectly saying "flash BACK to 4.2" obviously I knew you were on 4.2, so clearly I meant use the aforementioned guide to flash back to stock then take the update. Looks like you went another route, congrats
Sent from my LG-D950 using XDA Premium 4 mobile app

Huh? Wut
Not sure where things went wrong here.....
Me thinks some thread cleaning is in order...
Stand-by....
Cleaning finished.
Come on folks, let's relax and take a breath. Sometimes things just don't work and there's little to be done about it. If common known procedures don't work, then hopefully something else will, and just move along to something else.
Or in this case, the device is being returned which of course solves all.
No need for anybody to get all bent out of shape, what started out as being helpful, just took a bad turn somewhere for unknown reasons.
Relax, be cool....
MD

KitKat update on ATT G FLEX running on Tmobile.
This might be a stupid question . I have my ATT G FLEX D950 running on Tmobile. It is on Jellybean . I am unable to pull the Kitkat update and it says "Phone is not registered on network". I am assuming I need to get my phone on ATT network to pull the update. Am I right? is there any other way out ?

santy83 said:
This might be a stupid question . I have my ATT G FLEX D950 running on Tmobile. It is on Jellybean . I am unable to pull the Kitkat update and it says "Phone is not registered on network". I am assuming I need to get my phone on ATT network to pull the update. Am I right? is there any other way out ?
Click to expand...
Click to collapse
Kinda, yes.
I had the same problem. My phone was never activated on the ATT network so it would not recognize it. You have 2 options:
Get a prepaid sim from ATT, use it once and than put your Tmobile sim back in there or ask a friend that has ATT to use the sim for a few minutes. A text or a phone call is all you need.
Worked great for me.

NG2 Baseband unlock without downgrading

First this is only a guide not a repost
NG2 Baseband
1. Use ssu.apk to unlock it first
2.use cf auto root to it
3 use adb:
su
am broadcast -a android.provider.Telephony.SECRET_CODE -d android_secret_code://27663368378
UMTS -> DEBUG SCREEN -> PHONE CONTROL -> NETWORK CONTROL -> GCF
There the phone is domestic unlock without downgrading the modem

Haven't tested this but if it works, Bravo!
Sent from my SPH-L720 using Tapatalk

@AndroidKing, after doing just pop up domestic sim and go?
how you discovered this? lol
I have not tested yet, but this kill all other methods
thanks,

yea pop the sim and go i found this method when i was nae frimware and baseband and kept updating it went NG2 and lost the unlock for some reason so I tried so this i seen for the note 3/l720t and it worked

So Does this method make my device works on CDMA&GSM carriers (standby),or GSM only carriers?

Thanks for the steps and instruction. Quick question:
- if step 1 (ssu.apk) does the unlock, then why do we need to do steps 2 and on?
Thanks !
Sent from my SPH-L720 using XDA Free mobile app

I'm not a noob by any means, but I haven't been keeping up with all the s4 updates. I recently broke my s4 witch was running mf9(that tells you how long its been) and the replacement i recieved is OF COURSE ng2. My question is .... will this method root my mk2 s4? Tripping knox doesnt bother me one bit(gotta love blacktie coverage)
Thanks in advance
Mario

mario182005 said:
I'm not a noob by any means, but I haven't been keeping up with all the s4 updates. I recently broke my s4 witch was running mf9(that tells you how long its been) and the replacement i recieved is OF COURSE ng2. My question is .... will this method root my mk2 s4? Tripping knox doesnt bother me one bit(gotta love blacktie coverage)
Thanks in advance
Mario
Click to expand...
Click to collapse
No this is NOT for rooting
This is only for unlocking. To root the NG2 build you have to use chainefires method which will trip Knox. But you said you don't mind. So root and flash away!

can any confirm?
and, can we get a cleaner instruction for noobs?
also does it matter which ROM u'r using?

agentcelsius said:
can any confirm?
and, can we get a cleaner instruction for noobs?
also does it matter which ROM u'r using?
Click to expand...
Click to collapse
also, do we have to adb? can u use the terminal emulator?

ssu step didn't work for me. I'm on NG2.
Edit: It didn't work b/c I was on custom NG2 with custom recovery.
Sent from my SPH-L720

I can't believe it was this easy. I temp flashed back to stock rooted ng2, used ssu.apk to unlock, then restored my GPE Lollipop 5.0.1 backup, popped in my Metro sim(t-mobile), set it to World mode, and bam, says I'm on T-mobile's network, calls and data seem to work. It even shows up as MetroPCS as the active network under status. Put the Sprint sim back in, and it's back to my Ting account.
So to recap, I went to stock NG2 rom, did step one only, skipped the other steps, then went back to custom rom and it now works great. Thanks dude

Stock or stock rooted NG2
Zhono said:
I can't believe it was this easy. I temp flashed back to stock rooted ng2, used ssu.apk to unlock, then restored my GPE Lollipop 5.0.1 backup, popped in my Metro sim(t-mobile), set it to World mode, and bam, says I'm on T-mobile's network, calls and data seem to work. It even shows up as MetroPCS as the active network under status. Put the Sprint sim back in, and it's back to my Ting account.
So to recap, I went to stock NG2 rom, did step one only, skipped the other steps, then went back to custom rom and it now works great. Thanks dude
Click to expand...
Click to collapse
I'm slightly confused. Did you root NG2? 1. Stock NG2, 2. SSU.apk, 3. Restore rooted Lollipop?

kauboy2 said:
I'm slightly confused. Did you root NG2? 1. Stock NG2, 2. SSU.apk, 3. Restore rooted Lollipop?
Click to expand...
Click to collapse
I responded to your PM. I hope you have time to read a book. lol
For anyone else that's wondering:
1. be on stock NG2. ssu.apk force-closes on aosp/custom roms, at least for me.
2. Run ssu.apk and do the unlock. This does not require root.
3. do the other commands through ADB(step 3 from Androidking's original post), just in case. You may or may not need them. I don't know why it worked for me without them. That step DOES require root.
4. Test your sim card and make sure your phone can read it, and if possible, make a call, try text/data, whatever.
5. Flash to the rom of your choice. I recommend this excellent Lollipop rom by Danvbh: http://forum.xda-developers.com/gal...-5-0google-play-edition-lrx219-12-24-t2982384
It allows easy selection of any band/technology that the phone is capable of(which will not actually mean anything until after this unlock procedure). It also automatically gives you many choices for APN's related to your chosen band(not sure if that is a feature of the rom, or if it is standard Android behavior.) Easily select the correct APN for all sorts of carriers, including many popular prepaid services. No manual entry of info needed(probably).
One thing to note: on the custom rom, when I have my Sprint sim in, it says "Invalid Sim" on the lockscreen. The phone does read the sim though, it just says it doesn't. Not sure why that happens. It may be due to the fact that I deactivated my Ting service and haven't gotten new service elsewhere yet, so it can't actually connect to any 4g lte service. It doesn't do that in the stock rom though, it displays normally. Probably just an odd quirk that will work itself out when I switch services. Nothing to worry about.

agentcelsius said:
also, do we have to adb? can u use the terminal emulator?
Click to expand...
Click to collapse
I tried terminal emulator and it opens up the secret menu that opens when you dial *#0011# everytime. I couldnt get into it dialing that tho. I cant get it to work in adb for some reason. So I just used this to get into the menu and change everything manually. The only problem I have now is when I flash a lollipop rom, the network mode gets stuck on LTE only. Even if I change it to world mode, when I go back it just goes back to LTE only. Any ideas?

Jacob030 said:
I tried terminal emulator and it opens up the secret menu that opens when you dial *#0011# everytime. I couldnt get into it dialing that tho. I cant get it to work in adb for some reason. So I just used this to get into the menu and change everything manually. The only problem I have now is when I flash a lollipop rom, the network mode gets stuck on LTE only. Even if I change it to world mode, when I go back it just goes back to LTE only. Any ideas?
Click to expand...
Click to collapse
so u got it unlocked? and the, data mode might be ROM related

sounds like rom problem as the looks of it

AndroidKing said:
First this is only a guide not a repost
NG2 Baseband
1. Use ssu.apk to unlock it first
2.use cf auto root to it
3 use adb:
su
am broadcast -a android.provider.Telephony.SECRET_CODE -d android_secret_code://27663368378
UMTS -> DEBUG SCREEN -> PHONE CONTROL -> NETWORK CONTROL -> GCF
There the phone is domestic unlock without downgrading the modem
Click to expand...
Click to collapse
Hi all, I'm new to this. I have a SPH-L720 that is never being rooted before. Is there any link that show step by step how to unlock domestic for this NG2 baseband like AndroiKing mention ? I can understand step 1 and did the unlock but what I'm going to do in the step 2 after you download cf auto root? What is adb and how you get to the following steps? Thanks in advance for your help.

Can anyone share the ssu.apk file?
Sent from my SM-G925P using Tapatalk

http://forum.xda-developers.com/spr...print-samsung-unlocker-unlock-sprint-t2928250

[GUIDE] How to root Salaxy Tab S2 T817T

How to Root Samsung Tab S2 T817T (Step-By-Step Guide)
Obligatory notices
This procedure is only for the Samsung Tab S2 SM-T817T
Performing any of the operations in this post risks bricking your device
Performing any of the operations in this post will irreversibly void your warranty
Performing any of the operations in this post will irreversibly trip Knox and make it unusable for Samsung Pay (and any other features which require Knox)
I am not using a SIM card with my device, so I have no idea how this procedure will impact that functionality. People on the XDA thread (forum.xda-developers.com/tab-s2/help/sm-t817t-root-t3206079) where I pieced together these instructions from suggested that the SIM card still works for mobile data. UPDATE: Later in this thread people have confirmed that mobile data DOES work after rooting. Yay!
Introduction
OK, so a brief story of how/why I was forced to figure this method out. I found a listing on eBay for the Samsung Tab S2 T810N, paid $300 for it and received it into my impatient hands. Without checking the specific version of the tab I push right into the rooting procedure I had thoroughly researched for the T810N. Suddenly my tablet is in a bootloop and I am panicking that it is ruined. In the recovery mode I see that I have the T817T. Anger towards the seller aside, I frantically research how to recover the T817T. There is virtually no documentation for this procedure, so I am forced to mix-and-match. After about 5 hours, the tablet is finally up, running, and rooted!
TL;DR - verify your model number before attempting root
Files
All the files can be found here (drive.google.com/folderview?id=0BxPb6XhrMsaoa01zdjVUVWMzQWs&usp=sharing). Let me explain what each file is:
T817TUVS2AOL1_T817TTMB2AOL1_TMB.zip (drive.google.com/file/d/0BxPb6XhrMsaoeGpmbnRoeFA5MUU/view?usp=sharing) - This is an Android 5.1.1 image for Samsung Tab S2 T817T. You may not even need this, but just in case. If you use this, unzip the file to get the .md5 file!
SAMSUNG_USB_Driver_for_Mobile_Phones_v1.5.51.0.exe (drive.google.com/file/d/0BxPb6XhrMsaoc09qNm41OFhKLWc/view?usp=sharing) - Necessary Windows drivers for Samsung devices. Install this!
Odin3_v3.10.6.zip (drive.google.com/file/d/0BxPb6XhrMsaoLWtkek9UYWZGNGM/view?usp=sharing) - A flashing tool for Windows. Unzip these files!
twrp_2.8.7.1_LL_5.1.1_t810.tar (drive.google.com/file/d/0BxPb6XhrMsaoN0N6V3JzX290aGc/view?usp=sharing) - This is a custom recovery tool for Android. Although designed for the T810 series, it does work on the T817T. Do not untar these files!
Tab_S2_t817T_boot.zip (drive.google.com/file/d/0BxPb6XhrMsaob0hyME0zV2EtSnc/view?usp=sharing) - A custom bootloader for the T817T which is required to root. Do not unzip these files!
BETA-SuperSU-v2.52.zip (drive.google.com/file/d/0BxPb6XhrMsaoNk9uWkxRZ0wwTE0/view?usp=sharing) - A newer version of SuperSu which works on the T817T. Do not unzip these files!
Preparation
Download all the files above. Install, unzip, and untar (or not) as instructed.
Settings -> About device - Verify that you have the SM-T817T
Settings -> About device - Verify that you are running Android 5.1.1
Backup all your files, contacts, apps, etc.
Verify that your device has at least 80% charge
Rooting Procedure
(OPTIONAL) Flash Android 5.1.1 image. This step is not necessarily required. If you are running Android 5.1.1, then you should be fine. However, this is what I had to do, since I got into a bootloop by not checking my version number first (yes, stupid me). Further, if you have any errors or issues below you absolutely will need to perform this step to recover and restart the rooting procedure. Anyway:
Turn off your tablet
Boot into 'download mode' by holding POWER + VOLUME DOWN + HOME. Verify by pressing VOLUME UP
Run program Odin3 v3.10.7.exe
Plug your device to the computer with a USB cable
Verify that Odin message window states "<ID:#/###> Added!!"
Click the "AP" button in Odin and select T817TUVS2AOL1_T817TTMB2AOL1_T817TUVS2AOL1_HOME.tar.md5 file
Press "Start" button and wait for Green "PASS" message to appear. This will take a long time since this is a large file
Your device will automatically reboot
Perform basic setup procedures on Android so that you can access the Settings menu
From this point onward your must perform every step in the exact order as stated. Not doing so seriously risks putting your device into a bootloop or bricking it. You should be able to recover from that, but still...
Enable developer options:
Settings -> About device - click on "Build number" like 10 times until "Developer options" are enabled and button is added to Settings menu
Settings -> Developer options - enable:
Developer options - ON
OEM unlock - ON
USB debugging - ON
Flash TWRP recovery software:
Turn off your tablet
Boot into 'download mode' by holding POWER + VOLUME DOWN + HOME. Verify by pressing VOLUME UP
Run program Odin3 v3.10.7.exe
Plug your device to the computer with a USB cable
Verify that Odin message window states "<ID:#/###> Added!!"
Click the "AP" button in Odin and select twrp_2.8.7.1_LL_5.1.1_t810.tar (drive.google.com/file/d/0BxPb6XhrMsaoN0N6V3JzX290aGc/view?usp=sharing) file
Press "Start" button and wait for Green "PASS" message to appear
Your device will automatically reboot, verify that the tablet boots properly
Copy bootloader and SuperSu to tablet:
With your tablet on, attach it to your computer with a USB cable
Navigate to the root directory of the tablet storage
Copy Tab_S2_t817T_boot.zip (drive.google.com/file/d/0BxPb6XhrMsaob0hyME0zV2EtSnc/view?usp=sharing) and BETA-SuperSU-v2.52.zip (drive.google.com/file/d/0BxPb6XhrMsaoNk9uWkxRZ0wwTE0/view?usp=sharing) files to the root directory
Detach tablet from your computer
Flash custom bootloader with TWRP:
Turn off your tablet
Boot into 'recovery mode' by holding POWER + VOLUME UP + HOME
Select "Install"
Select Tab_S2_t817T_boot.zip and click "Install"
Verify install with slider
STOP HERE!!! READ THE NEXT STEPS CAREFULLY!!!
TWRP will now offer to install SuperSu for you. DON'T DO IT!! Doing this will cause your tablet to bootloop because it is not the right version of SuperSu
Decline the SuperSu installation and restart your tablet
Verify that the tablet boots properly
REPEAT "Flash TWRP recovery software:" instructions. This is a necessary step. Without it your tablet will go into a bootloop and you will need to start the root procedure over. Weird, I know. Just do it.
Flash SuperSu with TWRP:
Turn off your tablet
Boot into 'recovery mode' by holding POWER + VOLUME UP + HOME
Select "Install"
Select BETA-SuperSU-v2.52.zip and click "Install"
Verify install with slider
Reboot the tablet
DONE! Assuming your tablet boots properly your should now be rooted and see the SuperSu app installed on your tablet.
Recovery
If you need to recover from some error you will need to start over completely. Use the Android 5.1.1 image file T817TUVS2AOL1_T817TTMB2AOL1_TMB.zip (same as above) to perform this. You can also use this Android image to restore the device to an unrooted version. This will not restore your warranty or Knox.
Extras
To get rid of the pesky KNOX security notification which will persist, use a program like ROM Toolbox Lite (play.google.com/store/apps/details?id=com.jrummy.liberty.toolbox&hl=en). In the App Manager select the following apps and 'freeze' them:
SecurityLogAgent 4.1.4 (this one is critical to freeze!)
KNOX 2.3.0
KNOX 2.3.1
KNOX II 2.3.0
KNOX SetupWizardClient 2.3.0
KnoxFolderContainer 2.4.0
To get rid of the "No SIM card inserted" notification (if you aren't using a SIM card) use the build.Prop Editor in ROM Toolbox Lite. Add the following entry:
Property Name: ro.config.donot_nosim
Property Value: 1
Conclusions
I put this guide together for people who are having trouble finding a simple and easy-to-follow guide for rooting the T817T. Hopefully this can save you a number of frustrating and worrisome hours (not that rooting your Android device is ever a calm undertaking).
Please let me know if there are any errors in the procedure or if you have any suggestions regarding the steps or presentation of the material. Enjoy being a super-user!
Original content: blog.mchristian.co/blogs/post/How-to-Root-Samsung-Tab-S2-T817T/

phduhblog said:
Long time user, first time poster.
First off, let me say, THANK YOU XDA! You guys have been a crazy valuable resource over the years.
However, with regard to the T817T, the documentation is lacking severely. I have created a comprehensive step by step guide to rooting the T817T. Unfortunately, as a first time poster, I cannot post links or anything like that so...if somebody could fix that I would appreciate it. I spent a long time formatting the posting and adding file download links with the XDA formatter so that it wouldn't look like I was link whoring to my blog, just to be told to **** off... . Seeing as that's not possible, here is the url to my blog with the rooting instructions:
blog.mchristian.co/blogs/post/How-to-Root-Samsung-Tab-S2-T817T
Click to expand...
Click to collapse
http://blog.mchristian.co/blogs/post/How-to-Root-Samsung-Tab-S2-T817T
Thanks my friend
Edit: Completely professional and well done how to.. written just the way I like it, fantastic!! I think you should just edit your first post and paste all this in here on XDA... and ill be happy to carry your url link for you.

Complete text of the GUIDE
Edited and posted it above. Good luck with the rooting. Thanks!

An excellent guide. I'd spent the last few hours reading post after post gathering the correct information for the T817T specifically. I had come to the same basic conclusion as your guide states but its great to have some confirmation! I have a few differences in my install process than you did though. I did things in this order:
Enable developer options:
Copy bootloader and SuperSu to tablet:
THEN
Flash TWRP recovery software:
and between 6 and 7
Uncheck AutoReboot in the Options tab
7. Press "Start" button and wait for Green "PASS" message to appear
8. Use Power+VolumeDown+Home to reboot from bootloader and AS SOON as the screen goes black slide your finger from VolumeDown to VolumeUp
This should boot you into TWRP
Flash custom bootloader with TWRP:
after 4:
press "add another zip" and select the SuperSU zip as well.
5. Verify install with slider
6. Reboot
Done
By booting directly into TWRP the stock recovery doesn't have a chance to overwrite it. It won't need to be flashed a second time. You can also flash the kernel (...boot.zip) and SuperSU zip in the same pass. Saves a couple steps.
Either way I can confirm this works and all of the files are correct!
Thanks again for organizing all of this and making this great guide!

patrioticparadox said:
An excellent guide. I'd spent the last few hours reading post after post gathering the correct information for the T817T specifically. I had come to the same basic conclusion as your guide states but its great to have some confirmation! I have a few differences in my install process than you did though. I did things in this order:
Enable developer options:
Copy bootloader and SuperSu to tablet:
THEN
Flash TWRP recovery software:
and between 6 and 7
Uncheck AutoReboot in the Options tab
7. Press "Start" button and wait for Green "PASS" message to appear
8. Use Power+VolumeDown+Home to reboot from bootloader and AS SOON as the screen goes black slide your finger from VolumeDown to VolumeUp
This should boot you into TWRP
Flash custom bootloader with TWRP:
after 4:
press "add another zip" and select the SuperSU zip as well.
5. Verify install with slider
6. Reboot
Done
By booting directly into TWRP the stock recovery doesn't have a chance to overwrite it. It won't need to be flashed a second time. You can also flash the kernel (...boot.zip) and SuperSU zip in the same pass. Saves a couple steps.
Either way I can confirm this works and all of the files are correct!
Thanks again for organizing all of this and making this great guide!
Click to expand...
Click to collapse
I'm glad you have figured out another way! This is turning into what a proper thread on rooting should look like
I had actually tried the non-auto-reboot from Odin method too, but couldn't time the change to VOLUME UP correctly. After a couple times I just gave up and tried things the long way around. Never thought to flash the zip files in the same TWRP session though. I generally like doing things the long way around and getting confirmation that things still work after each and every step. Whatever works though!
Thanks for the reply

phduhblog said:
I'm glad you have figured out another way! This is turning into what a proper thread on rooting should look like
Click to expand...
Click to collapse
Indeed it is.
Are your volume buttons functioning properly after this? Just noticed yesterday mine aren't adjusting the volume.

patrioticparadox said:
Indeed it is.
Are your volume buttons functioning properly after this? Just noticed yesterday mine aren't adjusting the volume.
Click to expand...
Click to collapse
Hmmm, odd. Sorry to hear that. Yes, mine work just fine.

Turns out my volume buttons are fuctioning just fine. I think I just pressed it wrong and didn't have a minute to double check it at the time.

patrioticparadox said:
Turns out my volume buttons are fuctioning just fine. I think I just pressed it wrong and didn't have a minute to double check it at the time.
Click to expand...
Click to collapse
Whew! I'm glad to hear that. Now people can root their T817T without concern!

Yep! Been using this for two weeks now and no problems!

Can anyone confirm that the mobile internet still work when you have a SIM card in? Thanks.

phduhblog said:
Can anyone confirm that the mobile internet still work when you have a SIM card in? Thanks.
Click to expand...
Click to collapse
SIM does not work-- just restored back to stock.. going to wait a little bit before re-rooting.

androidcues said:
SIM does not work-- just restored back to stock.. going to wait a little bit before re-rooting.
Click to expand...
Click to collapse
Hmmm. Well that's good to know at least. Thanks for the update!
Also I'm glad you were able to revert to stock and get it working.

Yeah... Ive fully unrooted and gone back to samsung for a bit.. wont be long because I automatically gravitate back to CM. hehe.
vibration doesnt work on CM... that was a big thing because i rely on tactile vibration for notifications.... (i am deaf so.. the noisy parts are useless ?)
but anyway... taking a moment to thank you again for your writeup...i really needed that...soon after i read your blog i was rooted and rocking!
But Samsung sucks bro... i cant stand all these ****ty apps on my tablet so maybe I'll come back sooner.
0x1
Sent from my Nexus 5X using XDA Premium HD app

androidcues said:
Yeah... Ive fully unrooted and gone back to samsung for a bit.. wont be long because I automatically gravitate back to CM. hehe.
vibration doesnt work on CM... that was a big thing because i rely on tactile vibration for notifications.... (i am deaf so.. the noisy parts are useless )
but anyway... taking a moment to thank you again for your writeup...i really needed that...soon after i read your blog i was rooted and rocking!
But Samsung sucks bro... i cant stand all these ****ty apps on my tablet so maybe I'll come back sooner.
0x1
Sent from my Nexus 5X using XDA Premium HD app
Click to expand...
Click to collapse
Yep, I can definitely see why vibration notifications would be important for you!
As much as I dislike bloatware, from any company, Samsung just makes the most powerful tablets/phones. My best solution is to root and disable all the bloatware.
I'm glad the guide was well received and it seems to work for people.

My mobile data and SIM functions all work fine. Not sure why yours didn't

patrioticparadox said:
My mobile data and SIM functions all work fine. Not sure why yours didn't
Click to expand...
Click to collapse
Awesome! That is weird it didn't work for the other guy. Did you flash the provided Android version first or just go straight into the rooting? Thanks for the update!

phduhblog said:
Awesome! That is weird it didn't work for the other guy. Did you flash the provided Android version first or just go straight into the rooting? Thanks for the update!
Click to expand...
Click to collapse
Sorry for the late reply. I Odined the latest firmware to reset everything to a stock base before then flashing as your steps suggest (with the noted exceptions from my first post). My mobile data has worked flawlessly and I have had zero SIM related issues. In fact, I have had no issues what-so-ever. (I did think I had an issue with my volume rocker not working but that was user error. I have my tablet in a case of sorts and was not pressing hard enough). @phduhblog and @androidcues are you both still experiencing mobile data and SIM issues as of now?

patrioticparadox said:
Sorry for the late reply. I Odined the latest firmware to reset everything to a stock base before then flashing as your steps suggest (with the noted exceptions from my first post). My mobile data has worked flawlessly and I have had zero SIM related issues. In fact, I have had no issues what-so-ever. (I did think I had an issue with my volume rocker not working but that was user error. I have my tablet in a case of sorts and was not pressing hard enough). @phduhblog and @androidcues are you both still experiencing mobile data and SIM issues as of now?
Click to expand...
Click to collapse
Wording changed! Thanks for the update.

One question pls. I have the T817V tab 9.7 w/OEM bootloader option button. Is any of this available to use for my tab? TWRP recovery maybe? Any files? Any reply is appreciated. Novice seeking knowledge. Thank you so much.