Last Updated on May 13, 2023 by Mathew Diekhake

Android 4.3 Jelly Bean brought a lot of great features with it, but it also brought some changes behind the scenes that people did not see also. One of those was the new way of handling the request for root access called the su daemon process. The su daemon has to run at startup of the device or else it just won’t work, and there is no way to become the root user. The older of getting root access before Android 6.0 Marshmallow handled that from the system partition. However, with Android 6.0 Marshmallow software updates, there was no way to launch the su daemon during the booting process. It is at that time that a modified boot image came to fruition. The new version that handles the modified boot image was when the systemless root version of the CF-Auto-Root tool was born, and that is the version you have here—as it always is when you have a version of the CF-Auto-Root tool that roots the Android 6.0.1 Marshmallow updates.

None of the mentally challenging aspects that developers like Chainfire go through to bring you guys root access need to matter to you unless you have an interest in understanding what is happening. It does not help you being able to get root access any easier just by learning what was just told. The great thing about one-click rooting tools is that they are never more difficult or challenging than the last because all they ever take is just one click and they are complete. Thus, the way the CF-Auto-Root tool works for the Android 4.3 Jelly Bean software updates with the Odin flashing tool is still the same way that it works for the Android 6.0.1 Marshmallow software updates even though so much as changed since then.

Moreover, there is nothing different with the sheer amount of new apps available and at your disposal when you are the root user and have the root access granted over the operating system. The same apps that were available to you after you rooted using the one-click rooting tool by Chainfire for the version that did start up the su daemon process from the system partition are still the same applications that are available to you now with this systemless root version.

Notes:

  • Chainfire had the MMB29M.T355XXU1BPF1 firmware build number running on the Samsung Galaxy Tab A SM-T355 tablet when the rooting file available for you to download in this guide was developed. He makes that information readily available, but it is not suggesting that you need to run on the same firmware build number before you do the flashing of the rooting file. He is giving that information so you can use it as an indicator if that information ever becomes relevant.
  • Just like all good rooting tool, the CF-Auto-Root tool has a thread set up for it over at the XDA-Developers website. You can use that thread for letting Chainfire know if one of the files needs updating. You can tell a file needs updating if you flash the rooting file using the flashing tool and yet the device will not boot up after the flashing. Before he can fix that issue, though, he also needs the recovery image file from the firmware, and he needs you to leave that recovery image file in your message for him
  • You need to have the Samsung Galaxy Tab A tablet that has the SM-T355 model number if you are going to flash the rooting file available in this guide. If you try to flash the rooting file that is accessible in this guide on any of the other model numbers that device often gets bricked, and you need to flash the stock ROM on it again to get it working.
  • You need a computer to use the Odin flashing tool that flashes the rooting file, but the only computer that can run the Odin flashing application is one that runs on a version of the Windows operating system. It does not matter what version of Windows as long as it is at least Windows XP.

Download Samsung Galaxy Tab A SM-T355 CF-Auto-Root and Drivers

How to Root Samsung Galaxy Tab A SM-T355 on Android 6.0.1 (Marshmallow) Using CF-Auto-Root

  1. Unlock the Developer Options menu on the Samsung Galaxy Tab A SM-T355 tablet so you can use the options that become available to the developer.
  2. Enable the USB Debugging Mode on the Samsung Galaxy Tab A SM-T355 from the Developer Options menu that you just unlocked so you can make the changes that are required on the Android software.
  3. Install the Samsung USB Drivers on the computer so the Odin flashing application is then able to detect your smartphone when you have it connected to the computer and waiting for the flashing to happen.
  4. Extract the rooting file to the Downloads folder that is on the computer and should be your default downloads location for files unless you have changed it.
  5. Boot the Samsung Galaxy Tab A SM-T355 tablet into the Download Mode and connect it to the computer with the USB cable that is available for the charging of the battery.
  6. Run the Odin flashing application that is available as one of your files in the Downloads folder after you extracted the rooting file earlier.
  7. Check that Odin shows a color coming from the ID: COM port as well as the added message from the user interface which means that the Samsung USB Drivers are working.
  8. Do not make any changes that change the Odin app from its default settings that you get from its Options tab.
  9. Click on the AP button that it has available from the user interface and then click through to the Downloads folder and click on the rooting file so that it uploads to the Odin.
  10. Choose the start button that Odin has available from its user interface, and then the rooting for the Samsung Galaxy tablet begins.
  11. Read all of the information that starts rolling down the display as the rooting is happening so you know what to expect and what is going to happen with the new version of the rooting tool.
  12. Wait for the pass message to show up on the Odin user interface before unplugging the Samsung Galaxy tablet from the computer and the USB cable.

In conclusion, that is how to root the Samsung Galaxy Tab A SM-T355 tablet running on the Android 6.0.1 Marshmallow software updates. The SuperSU application is now installed, and it is already completely enabled and ready for you to begin installing the root applications that you were hoping to run. You can unroot by taking a factory reset with this version of the rooting tool, but apart from that not much else has changed.

Related Tutorials