Database Develop

[Q] bionic jb 98.72.22 su binary help! root access?

So from the beginning I updated from notification on phone from 4.0.4 to 4.1.2. Then bricked after trying to gain root acess. Finally able to flash jb 98.72.22. Tried for days to find a root that worked. Couldn't get motochopper to gain root. Tried god knows how many others. Finally got virtual box, imported Root_Bionic_JB.ova and still wouldn't work. Keep coming across su binary issues. The closest i got was with the virtual box installing superuser. But when I trying to update the binary says unable and to send a log report. What am i doing wrong? is it a step im missing when unzipping to desktop? everything goes smooth until cmd gets to rooting, then says failed. cleaning. press enter to reboot and close. Im about to lose my mind! Please some assistance. I sick of failing every attempt from every suggest forum (quietly sobbing )

You need to go back to what has been proven to work. Moto chopper 2. Not to be insulting BUT I know from experience, just BC you can't get something to work the first couple of times you try it doesn't mean it does not work. Period. Now, where did you get hung up on the Ubuntu exploit? List all that you did.
Sent from my XT875 using xda premium

linux minimal screen shot, and unbuntu hang up
DanRyan85 said:
You need to go back to what has been proven to work. Moto chopper 2. Not to be insulting BUT I know from experience, just BC you can't get something to work the first couple of times you try it doesn't mean it does not work. Period. Now, where did you get hung up on the Ubuntu exploit? List all that you did.
Sent from my XT875 using xda premium
Click to expand...
Click to collapse
Well, not to be insulting, but it was my understanding that moto chopper would only work if temp rooted or had gained root acess previously? I may be wrong. Anyways, the prob. with unbuntu is thing i guess froze (but still ran) after patiently running it like six hours. Last screen at was installing-reinstalling previous "somethings" but I figured need a system clean and would try again. gotta be easier way. so here is my linux minimal screenshot attempt. running root bionic jb ovf file. noticed where it starting going wrong is
chmod: pwn: operation not permitted.
rooting phone...
phone may appear to.......
/system/bin/sh: /storage/rfs0/pwn: not found <-------Right here i noticed the file path on the phone and it's ---> storage/rfs1 Would that have something to do w/ it?
nothing ever vibrates and reboots in flash. got bad flash or something?

MotoChopper works on non TI (OMAP) CPus that are in Motoroal devices.
Coincidentally, it also works on ASUS Tranformer Infinity (and the Prime as well, IIRC).
It does not work on the BIONIC.
The method that works on rooting the JB build on the BIONIC is one that is based upon the older RAZR method - see http://www.droidrzr.com/index.php/topic/16518-root-motoshare-2-old-bug-new-exploit/

Bionic and JB OVA flash superuser binary outdated
Naughtybutbritt said:
So from the beginning I updated from notification on phone from 4.0.4 to 4.1.2. Then bricked after trying to gain root acess. Finally able to flash jb 98.72.22. Tried for days to find a root that worked. Couldn't get motochopper to gain root. Tried god knows how many others. Finally got virtual box, imported Root_Bionic_JB.ova and still wouldn't work. Keep coming across su binary issues. The closest i got was with the virtual box installing superuser. But when I trying to update the binary says unable and to send a log report. What am i doing wrong? is it a step im missing when unzipping to desktop? everything goes smooth until cmd gets to rooting, then says failed. cleaning. press enter to reboot and close. Im about to lose my mind! Please some assistance. I sick of failing every attempt from every suggest forum (quietly sobbing )
Click to expand...
Click to collapse
I am having same issue. Using Marty OVA in virtual box. works great, no issues w/ samba or USB. Root is successfully run. however.
root checker indicated that I am not rooted and as mentioned above, superuser needs to update the binaries.
" the Superuser binary (su) must be updated
please choose an installation method
recovery mode installation is recommended for HTC devices.
Cancel <> Recovery Install<> Install
hit install
there was an error installing superuser. Please send a log of the error to the developer.
<ok>
wonder if I could replace the superuser.adk file in the /home/guest/share directory with a newer adk file?
could not get post on droidrzr.com on a thread there. ( link not permitted by Noobs )
Marty45714 informed us He posted this here as well. can anyone answer this?
T

To Naughty: Sorry about the mix up that was what I meant to say Moto share 2 NOT Motochopper. I had all the same problems as you after some number of tries with motoshare2 I was in business.
To martin: have you already tried the motoshare 2 on Ubuntu?
Sent from my XT875 using xda premium

toddmartin- you're gonna love me...i gotcha
toddmartin said:
I am having same issue. Using Marty OVA in virtual box. works great, no issues w/ samba or USB. Root is successfully run. however.
root checker indicated that I am not rooted and as mentioned above, superuser needs to update the binaries.
" the Superuser binary (su) must be updated
please choose an installation method
recovery mode installation is recommended for HTC devices.
Cancel <> Recovery Install<> Install
hit install
there was an error installing superuser. Please send a log of the error to the developer.
<ok>
wonder if I could replace the superuser.adk file in the /home/guest/share directory with a newer adk file?
could not get post on droidrzr.com on a thread there. ( link not permitted by Noobs )
Marty45714 informed us He posted this here as well. can anyone answer this?
T
Click to expand...
Click to collapse
Ok so using virtual box the ova Root_Bionic_JB_20130501-4 the fourth ubdate of the orginal release. Now i suggest erasing all superuser apps installed your self and anything to do with them. When it's done right, it will appear on it's own and work flawlessly. No uncertianties about it. Then i've posted a screen shot of the commands with notes to help understand easiest. The instant the command to press hardware key or power/or each volume itself is the instant you want to press it. Now the reboot is instantious kinda itself and gotta be noticing phone unless have ungodly long boot up let me know if the screen shot helped what you were asking.

Compiled Guide on Rooting GT-I9305 (S3 LTE)

COMPLETE GUIDE TO ROOTING SAMSUNG GALAXY S3 WITH 4G/LTE
CAUTION: YOUR WARRANTY WILL BE VOID AFTER YOU ROOT. HOWEVER, YOU CAN GAIN BACK YOUR WARRANTY BY FLASHING A STOCK ROM. (the Galaxy S3 LTE ROM, go to Samsung Updates website)
Quick and easy steps to root S3 4G:
Step 1: Download Odin (Can be v3.04 to v3.07). Download the CF-Auto-Root file. Extract the CF-Auto-Root (.tar.md5 file) onto your desktop.
Step 2: Open Odin zip by WinRAR/7zip/WinZip. Open Odin. Select PDA. Now choose the CF-Auto-Root file.
Step 3: Make sure your phone is in DOWNLOAD MODE. (Power OFF your phone if you haven't done so.
Press Volume Down + Home Button + Power Button. You will see a screen saying "Warning!". Just ignore what it says and PRESS THE Volume Up button.
Step 4: Now, connect the phone to your Windows computer/laptop. (Connect the USB cable to your phone first then to your computer.) Let it detect your phone. In the Message Box (located at the bottom left corner of Odin), you should see "Added!!" there. Now, click on START. Wait for like 5 seconds or so and you're done! The rectangular box (close to the top left of Odin) should say PASS! with a green background. In the message box, you should see "Removed!!" at the end. Disconnect your phone now. Your S3 4G should have a RED "Pirate" Android logo as your background.
Step 5: You should see at the bottom of this script "Rebooting in 10 sec...". Let it reboot. You're DONE! Your device is finally rooted!
(To check if your device is rooted, download Root Checker and verify if your S3 4G has root. You can now download apps like Titanium Backup.)
CF Auto Root File Download (not Hotfile): http://www.ge.tt/2B7Oh8h/v/0?c
Odin Package (from AndroidJinn): http://ge.tt/2B7Oh8h/v/1?c
Regards,
Have Fun!
entertainer99

You forget to mention your last post /
I have already sent the device for repair as I was unable to flash a stock ROM despite closely following the instructions on the internet.
prev
EMERGENCY! I can't boot my Samsung Galaxy SIII LTE (GT-I9305) after rooting it and installing ninphetamin overclocking software on the device, one file at a time. It just stays at the "Samsung GALAXY S III GT-I9305" logo forever and I noticed there is a small RED exclamation mark on the top-left corner of the boot screen.

Whats wrong with my phone.
I followed the steps in the links above and everything happened according to the steps, except the device is now stuck in downloading..... do not turn off target!!
Is there a resoliution or is the phone bricked?

Phatpat007 said:
I followed the steps in the links above and everything happened according to the steps, except the device is now stuck in downloading..... do not turn off target!!
Is there a resoliution or is the phone bricked?
Click to expand...
Click to collapse
Boot to download mode flash stock rom .
Fails its a service centre
jje

Hi,
I'm using I9305ZHBMI4 version on my i9305, but after I did the process to enable the root, it did not works.
It is as if the root was not installed.
Do I have to use other version of CF-Auto-Root-m3-m3zh-gti9305 ?
Thanks

Please wait for Root Check to Complete. System appears to be running slow
Hi
I followed the steps above and all appeared to be good with ODIN returning the message PASS.
When I tested to see if SGS3 (I9305 or LTE) has been rooted using "Root Checker Basic" the phone "hangs" with the message below :
Code:
Please wait for Root Check to Complete. System appears to be running slow
Tried purchased titanium Backup and the app never loads beyond the message :
Code:
Asking for root rights
And similar issue in the below link
http://honai-android.blogspot.com.au/2013/06/how-to-root-galaxy-s3-canadian-sgh.html
Thanks

Shouldn't this dangerous advice be removed...

Thanks
Did it as instructed in first thread, done in <10 minutes, all great, thanks.

zillah2004 said:
Hi
I followed the steps above and all appeared to be good with ODIN returning the message PASS.
When I tested to see if SGS3 (I9305 or LTE) has been rooted using "Root Checker Basic" the phone "hangs" with the message below :
Code:
Please wait for Root Check to Complete. System appears to be running slow
Tried purchased titanium Backup and the app never loads beyond the message :
Code:
Asking for root rights
And similar issue in the below link
http://honai-android.blogspot.com.au/2013/06/how-to-root-galaxy-s3-canadian-sgh.html
Thanks
Click to expand...
Click to collapse
What version are you running? I ran into exactly the same problem and I'm running JSS15J.I9305ZHUCNA1

mike-s said:
What version are you running? I ran into exactly the same problem and I'm running JSS15J.I9305ZHUCNA1
Click to expand...
Click to collapse
this problem is due to KNox....search XDA for DE_SAMSUNGNIZER remove knox script...you should be able to root it after that...
i was able...did it for a friend...

spiderman07 said:
this problem is due to KNox....search XDA for DE_SAMSUNGNIZER remove knox script...you should be able to root it after that...
i was able...did it for a friend...
Click to expand...
Click to collapse
I had a look and i don't have knox installed. I have a link that prompts me to download knox though.
edit: after reading, yeah I've got that blasted knox in there. time to give that script a whirl.

spiderman07 said:
this problem is due to KNox....search XDA for DE_SAMSUNGNIZER remove knox script...you should be able to root it after that...
i was able...did it for a friend...
Click to expand...
Click to collapse
I tried to run chainfire's autoroot again and then install supersu. Finally it worked and disabled knox and i now have root access. I'm glad it's finally sorted. Thankyou for your suggestion though.

mike-s said:
I tried to run chainfire's autoroot again and then install supersu. Finally it worked and disabled knox and i now have root access. I'm glad it's finally sorted. Thankyou for your suggestion though.
Click to expand...
Click to collapse
And You tripped a flag in Knox?

Yes, but as I bought a grey import phone Knox' & Samsung's opinion on warranty isn't a massive concern to me. the opinion of the importer matters a whole lot more.
If it turns into a physical defect then I'm sure they'll help (though I hope it never gets that far). Software wise I should be OK as I'm not going to mess with the rom now that I've got root.
Sent from my GT-I9100 using xda app-developers app
---------- Post added at 02:47 PM ---------- Previous post was at 02:45 PM ----------
Oh and I might get lucky and a work around for the software only Knox security is found and I can rest to zero.
Sent from my GT-I9100 using xda app-developers app

[How-To] Update to G870A(Active Model)_OJ3 - 5.1.1 (Unrooted Stock ROM)

**You can begin the following process from any Build/ROM but you must already have Root Access**
**Required** FlashFire - Play BETA - PREVIEW
**Note** Rooting all Samsung 5.1.x builds currently requires a modified kernel therefore, due to the locked bootloader, achieving root on this build/device is not currently possible.
Downloads:
- G870A_OJ3_Stock_ROM.zip
1. Place the ROM onto your device (use either internal or ext-sdcard).
2. Open the FlashFire app and "Agree" to the Terms and Conditions.
3. Press "(+)" twice to bring up the "Actions" menu.
4. Press "Flash Zip or OTA" and locate and select the ROM. Leave "Auto-mount" unchecked under the "Options" menu and press the checkmark to continue.
5. From the main menu Uncheck all options under "EverRoot" and set "Reboot" setting to *"Download."
6. Press the lightning bolt then "Ok" to begin the **flash .
7. Once the flash is complete and the device reboots into "Download" mode, flash the G870A_OC5_Bootloader using Odin's PDA/AP slot.
*If you are already on the OC5 bootloader, set "Reboot" setting to "Normal" and skip Step 7.
**The screen will turn black then display the contents of your system before beginning the flash. FlashFire will pause for about 1 minute while flashing the "system" partition.
Once complete your device will reboot and pause on the AT&T splash screen for about 1 - 2 minutes before completely rebooting. Done!
Tip: for blazing fast speed turn off animations from Developer Options and reboot!
Recommended: Package Disabler Pro to disable unwanted bloatware (root access not required).
Known Issues:
- None!
Notes:
1. The above process will not affect your Knox Warranty Flag.
2. The process will update your Modem, Non-hlos, System, Kernel, and Stock Recovery. The bootloader will not be flashed in order to allow for downgrading to previous firmware versions.
3. No need to wipe prior to flashing! The ROM will automatically perform a factory data reset.
4. If you do not already have root access (or to unbrick) you must flash the G870AUCU1ANE4_Full_Odin.tar using Odin's PDA/AP slot (Caution! Do not flash if you have taken the OF2, OF3 or OJ3 ota update) and root with TowelRoot, before continuing with the above process.
5. To learn more about FlashFire's capabilities on locked bootloader devices see here: http://forum.xda-developers.com/showpost.php?p=60070810&postcount=2

Sweet! I have been anxiously waiting for this for my active. Thank you!
Sent from my SAMSUNG-SM-G900A using Tapatalk

I want to try it so bad, but I need my root!
Could everybody tell us what you think performance/battery wise though?
Thanks a lot!

Awesome gna do some flashn!

Thanks @muniz_ri.
Sent from my SAMSUNG-SM-G870A using Tapatalk

Followed the directions and it worked fine.
Used the suggested package disable pro with the defaults and then updated everything. Phone seems to be working fine so far.
I did read in one of the other threads that the battery life and such might not be as good as expected because we are still on the old bootloader, is this true or does the bootloader have nothing to do with the operating system?

Oh man....now do I...or don't I....

Install went well. Now to test.
Sent from my SAMSUNG-SM-G870A using Tapatalk

AnarchoXen said:
Oh man....now do I...or don't I....
Click to expand...
Click to collapse
Do it!
Sent from my SAMSUNG-SM-G870A using Tapatalk

If it requires root to flash... I would hope that I could then keep root after the flash.
I'm holding off on 5.1.1 until root is available. Just can't do without it I don't think.

Well i went ahead and did it, no problems at all. Now to see if I really can live without root!

Gonna try my hands at rooting this >_> i will update status.
Did some testing bricked my device 5 times. doesnt get past the bootloader part, so :/
For those of you that are testing this yourselves. You will ave to use the stock firmware for 4.x to unbrick. and then upgrade from 5.0 -> 5.1 in that order. So i guess im going to ave to wait for a root method too >_>
Within further testing, the files do update via flashfire, i just ave no clue how to get the system files to mount/unmount without bricking because it's unpacked.

Very good. Running smooth and fast. I do miss some root features.
SM-G870A Peace

Teranode said:
Gonna try my hands at rooting this >_> i will update status.
Did some testing bricked my device 5 times. doesnt get past the bootloader part, so :/
For those of you that are testing this yourselves. You will ave to use the stock firmware for 4.x to unbrick. and then upgrade from 5.0 -> 5.1 in that order. So i guess im going to ave to wait for a root method too >_>
Within further testing, the files do update via flashfire, i just ave no clue how to get the system files to mount/unmount without bricking because it's unpacked.
Click to expand...
Click to collapse
You can save yourself some time, or not, but all that has already been tried. No current way to root 5.1.1 on locked bootloader devices.

Meh I have a bunch of nexus and 2 one plus phones I just wanted to see of I can get this working on a s5 model. Att still committed to their locked bootloaders

berniesteven said:
Do it!
Sent from my SAMSUNG-SM-G870A using Tapatalk
Click to expand...
Click to collapse
I am! Now...at the ATT logo screen currently.
Well that was quick.

So use to this tutorials that I didn't read (or see) the UNROOTED part.....darn it
Can this be undone ?
If so, how
Thanks!

orion2323 said:
So use to this tutorials that I didn't read (or see) the UNROOTED part.....darn it
Can this be undone ?
If so, how
Thanks!
Click to expand...
Click to collapse
Odin back to ne4. See the op.
SM-G870A Peace

berniesteven said:
Odin back to ne4. See the op.
SM-G870A Peace
Click to expand...
Click to collapse
Thank you...did it; up and running with the previous build
"4. If you do not already have root access (or to unbrick) you must flash the G870AUCU1ANE4_Full_Odin.tar using Odin's PDA/AP slot (Caution! Do not flash if you have taken the OF2, OF3 or OJ3 ota update) and root with TowelRoot, before continuing with the above process"
I was afraid to try it but needed my root
I'm hoping to get a 128GB card next week and wanted to erase my phone anyway...

orion2323 said:
Thank you...did it; up and running with the previous build
"4. If you do not already have root access (or to unbrick) you must flash the G870AUCU1ANE4_Full_Odin.tar using Odin's PDA/AP slot (Caution! Do not flash if you have taken the OF2, OF3 or OJ3 ota update) and root with TowelRoot, before continuing with the above process"
I was afraid to try it buy needed my root
I'm hoping to get a 128GB card next week and wanted to erase my phone anyway...
Click to expand...
Click to collapse
Glad it worked out well for you. If I helped, don't forget to hit thanks.
SM-G870A Peace

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

[Guide] Unlocking Bootloader and gaining root on the A90 5G

Notes: This trips KNOX so you will void your warranty, read all the steps carefully before beginning, flashing can be dangerous if you do it wrong. Don't blame me if you brick your device.
Backup all of your data and settings before starting as you will need to reset to factory defaults during this process.
With that being said, the process is relatively straightforward and easy.
PS: my device is the A908B, there is also an A908N if anyone wants to test on that be my guest.
Needed:
ADB
SamFirm
Odin
Magisk Manager
Step 1 - Downloading your firmware.
Go to SamMobile SM-A908B
Find the correct firmware for your device according to country and operator.
Note: You can use generic country firmware instead, this will remove carrier added software and limitations but may remove features and disables OTA updates.
Note the 'product code'.
Now open SamFirm.
Type SM-A908B for model
In the region box type the product code you noted earlier.
Click Check Updates.
When it has found the firmware, make sure decrypt automatically is checked and then click download rom.
The firmware is around 4gb.
Part 2 - Unlocking the Bootloader
Go to settings > about phone > software information. Hit build number a bunch of times until you activate developer options.
Go back to settings > developer options
Enable OEM unlocking
Enable USB debugging
Turn off the phone
Hold volume up and volume down whilst inserting the USB cable
This should take you to the bootloader unlock screen.
Long press Volume up to unlock the bootloader.
Part 3 - Obtaining root
After SamFirm finished downloading the rom it should have extracted it into 5 tar files.
Copy the tar file beginning with AP to your device.
Download Magisk Manager on the device and install.
Press Install on Magisk Manager
Confirm the Install
Select the option 'select and patch file', then locate the APdjkfgrsdkfhgkjrg.tar.md5 on your device and select it.
Magisk will then patch the file and dump the patched version to your phone.
Copy the patched.tar to your PC
Reboot phone into download mode
Open Odin
For BL use the BL.tar.md5 file from stock firmware
For AP use the patched.tar file
For CP use the CP.tar.md5 file from stock firmware
For CSC use the CSC.tar.md5 file from stock firmware (not the CSC_HOME)
Press Start and wait for it to flash
After flashing, the phone will reset.
After initial setup, install magisk manager again.
Remove the USB cable and turn off the phone.
Turn on the phone by holding volume up and power, let go when you see the bootloader warning.
Open Magisk Manager Click Install.
Phone is now rooted.
Note: Powering on the device normally will disable root, you must hold volume up to power on the device to activate root.

Awesome job thanks a lot

Going to put a few hours into compiling twrp tonight but this might take me forever, I'm really busy with work and I got 2 kids too so free time is scarce. So feel free to have a go at it yourself.

After root activation with the volume button start up will the root persist? Can the device be restarted without any hidden key?
Thank you

Yes the root persists, but every time you turn the phone off and back on again you will have to hold up to activate the root. Resetting the phone while root is enabled does not disable it though iirc.
More work done on twrp last night, nearly ready to attempt compiling.
Edit: So I made a device tree and compiled twrp fine. Unfortunately it needs a custom kernel to be able to boot. Working on this now.

Any further progress??

No not really. I need to reach out to the twrp Devs of the S10 and see what modifications they did to theirs, but super busy at the moment. Sorry.

johnoponi said:
Any further progress??
Click to expand...
Click to collapse
Ok so I made a lot of progress since last post. I'm compiling the kernel as I type. But the process takes a long time. If we are lucky it will boot twrp straight away if not I'll keep at it until I manage.

triggz881 said:
Ok so I made a lot of progress since last post. I'm compiling the kernel as I type. But the process takes a long time. If we are lucky it will boot twrp straight away if not I'll keep at it until I manage.
Click to expand...
Click to collapse
Are you still trying?

Failure on Model SM-A9080 (China Version)
Today I did this on model SM-A9080 but unluckily failed, and the OS could not be loaded, with boot loop on the phone.
Really the specified TWRP should be developed.

triggz881 said:
Ok so I made a lot of progress since last post. I'm compiling the kernel as I type. But the process takes a long time. If we are lucky it will boot twrp straight away if not I'll keep at it until I manage.
Click to expand...
Click to collapse
Hey - did you manage to get anywhere with this? If you'd like help, i'd be happy to get stuck in. Could you put the code on Github?

Hello,
I tried to root my phone today, and I followed every step exactly, but now I am stuck in a Boot Loop, after the Step of Flashing. Can someone help, or knows why this happened? Thank you.
---------- Post added at 07:48 PM ---------- Previous post was at 07:03 PM ----------
Okay I fixed it myself. The Problem was, I only Flashed the BL File. After that I flashed the other files one by one, did a Factory Reset in Recovery mode and now it worked! I even have root now.

Do we have a custom rom yet? Can't stand the samsung rom or whatever its called.

xijaw said:
Do we have a custom rom yet? Can't stand the samsung rom or whatever its called.
Click to expand...
Click to collapse
So why did you buy a Samsung.

Srbija2012 said:
So why did you buy a Samsung.
Click to expand...
Click to collapse
Lmao, true. He could of easily went for one plus etc..
And bull****, Samsung ui is definitely top it's really nice.. just the notifications could be improved

Srbija2012 said:
So why did you buy a Samsung.
Click to expand...
Click to collapse
I live in Australia and here we don't have a market like Europe and India. We only have couple of brands- Apple and Samsung.
---------- Post added at 01:31 PM ---------- Previous post was at 01:30 PM ----------
underdog_656 said:
Lmao, true. He could of easily went for one plus etc..
And bull****, Samsung ui is definitely top it's really nice.. just the notifications could be improved
Click to expand...
Click to collapse
Lets stick to the topic and get the damn custom rom built. Aren't there any devs who willing to take A90 as a project ?

can you get the ctsprofile pass in the magisk manager？

Steveee101 said:
Hey - did you manage to get anywhere with this? If you'd like help, i'd be happy to get stuck in. Could you put the code on Github?
Click to expand...
Click to collapse
can i ask you whather you can get the cts profile pass or false or not after you root by magisk？

Hello please can someone help me root this phone, i have followed the steps but i just seem to be missing something so can someone take me through this step by step for a dumb person like myself lol?
At first i was struggling with part one of this tutorial but once i updated samfirm i was able to download it without a problem. moving over to the last step which is using odin to do its thing with the tar files and upon finishing where it should reboot it is stuck into a boot loop saying "this phone is not running samsungs offical software", i am not sure what i am missing and i am able to fix the phone without any problems but no root is achieved

Hello. May I ask about the progress on TWRP for this phone?