Linux is one of the more compelling operating systems you can run on a computer because of its complexity and the chance to pick and choose between a great many distributions. It draws in many geeks with its charm—and the fact that it is open-source and free to download—and rarely loses its grip from people that it has made fall in love with it unless you include the people who found it too complicated and wanted something simpler.

Windows operating systems are known as an operating system that is easy to use, and that is why they are the operating system of choice by so many businesses out there and so many computers around the home. Mac operating systems (although different) are also known as an operating system that is easy to use around the home for personal use and the business, but they are also expensive and completely different to Windows which is why they don’t get used as much.

One thing every desktop operating system has in common (Windows, Mac, and Linux) is that they almost always come with the chance to be in control of the root user account or the admin account when you first set them up. The admin account is what Mac and Windows computer operating systems use for their terminology, and the root user account is how the Linux distributions refer to it.

The root user account also exists in Android operating systems for mobile operating systems, but it is blocked off because Android decided they would not let people have access to it by default. In fact, there is no way they want you to get access to the root user account easily, and it almost always relies on a third-party developer coming along, developing a tool and then getting you out of trouble.


  • Chainfire was running on the MMB29K.T815YDVU2BPF1 firmware build number when the version of the CF-Auto-Root tool that is available in this guide was developed. When he gives that information for people to see, he is not suggesting that they need to be running on the same firmware build number that he was running—although that would undoubtedly be effective. He is just giving you that firmware build number so you can use it as an indicator if you are not finding it working on the firmware you are running or if it becomes relevant information to know for another reason in the future.
  • There is an official CF-Auto-Root tool thread set up by the developer at the XDA-Developers web forum that you can post messages on if you are finding that the rooting file you are using causes your device not to boot after the flashing.
  • You need to have the Samsung Galaxy Tab S2 tablet that comes with the SM-T815Y model number to use this guide. Any of the other model numbers get bricked because this particular one-click rooting tool is only developed to work for one model number only and all model numbers get sperate files generated for them.
  • You need to have a computer that is running on any of the Windows operating system versions to be able to use this guide because the Odin flashing tool that is required to flash the one-click rooting tool only can run from a Windows environment.

Download Samsung Galaxy Tab S2 SM-T815Y CF-Auto-Root and Drivers

How to Root Samsung Galaxy Tab S2 SM-T815Y on the Android 6.0.1 Marshmallow Using CF-Auto-Root

  1. Unlock the Developer Options menu on the Samsung Galaxy Tab S2 SM-T815Y tablet so the options for the developers become available for you to use from the operating system.
  2. Enable the USB Debugging Mode on the Samsung Galaxy Tab S2 SM-T815Y tablet so the chance ot make changes to the Android software that is running on your device is then a possibility.
  3. Extract the rooting file on the computer in the Downloads folder and then run the Odin flahsing tool that then becomes available for you to use from the same Downloads folder.
  4. Install the Samsung USB Drivers on the computer for the Odin flashing tool and the Samsung tablet so they can both talk to one another.
  5. Boot the Samsung Galaxy Tab S2 SM-T815Y tablet into the Download Mode and then connect it to the computer with the USB cable that is used for charging the battery.
  6. Do not make changes to the default settings that you get from the Odin user interface or else you can lose data or even stop the rooting from working.
  7. Click on the AP button that is available over to the right side of the Odin user interface and then browse through to the Downloads folder where you then need to click on the rooting file so that it uploads to the Odin and is ready for the flashing to happen.
  8. Click on the Start button for the rooting to begin and then check the text messages that start to roll down the display of the tablet so you can get a better understanding of what is about to happen because Chainfire has programmed everything to come up on the screen for you to use. (It’s useful because the versions of the CF-Auto-Root tool change the way they go about their business depending on the version of Android and the Android 6.0.1 version of the rooting tool, in particular, can act quite differently to its predecessors).
  9. Wait for the message to show up on the display that it is going to reboot back into the normal mode in 10 seconds and then check for the pass message to show up on the Odin user interface.

In conclusion, that is how to root the Samsung Galaxy Tab S2 SM-T815Y tablets running on the Android 6.0.1 Marshmallow software updates by using the updated version of the CF-Auto-Root tool that works perfectly for this particular version of Android Marshmallow versions.

The rooting tool has just enabled the SuperSu on the smartphone, and it managed to get that done by sneakily installing a modified cache and modified recovery on the tablet first. You don’t need to worry about that though because the rooting tool also removed both of those things because of they are no longer necessary once the SuperSu has been enabled on the device. Therefore, you don’t notice any difference on your device at all, and it still manages to run the same stock recovery partition that is was running before the rooting started doing anything on the device.

The SuperSU keeps you safe from malware, and it also allows the root apps to run with root permissions. The way it works is by blocking the root access to every app that you install by default—even the root apps that you want to grant the rooting permissions to. It then gives you a pop-up message on the display when you try to run a root app and asks you to confirm that you do want to grant that particular application the rooting rights over the operating system. That means it protects you from malware, to begin with, and then it is up to you to confirm anything that you true or deny anything you don’t trust, and it is that element of needing you to make the final call that is the reason you hear it makes a device less secure.

Related Tutorials