Rooting the Samsung Galaxy S5 SM-G900I smartphone running on the latest Android 6.0.1 Marshmallow software update will give you those Sudo permissions over your Linux operating system that you have been waiting for now for a long time. Without full administrator access to the operating system, you cannot do things like install apps like Triangle Away, Titanium Backup, Xposed Framework, Viper4Android, Greenify, Tasker, NANDroid Manager or the Quick Boot application. The Quick Boot app is the app that allows you to boot your smartphone in the many unique modes like download mode or recovery mode before flashing.

Out of all the root apps listed above, the NANDroid Manager is the one to own if you plan on installing a custom recovery after this guide. There are a few ways one can take an NANDroid backup — using the ROM Toolbox and other apps or directly from the custom recovery images like ClockworkMod and TWRP — but those of you who are wanting to install a custom recovery anyhow should go with the NANDroid option from your new recovery. The reason we suggest using the NANDroid option instead is because it’s the most efficient. Your custom recovery gives you an option to backup and restore. The backup will backup everything, and the restore button will restore everything. Where the NANDroid Manager shines is with restoring your data. With it, we can restore partitions at a time instead of the entire data that was saved. That means if you just want to restore the apps and leave everything else the same, you can do that with the NANDroid Manager.

Root Samsung Galaxy S5

The rooting exploit in this guide is based on the MMB29M.G900IDDU1CPD2 firmware which was part of an Android 6.0.1 Marshmallow update that rolled out for some regions. You do not need to install the same firmware on your Samsung Galaxy S5 smartphone so don’t worry about what region that update rolled out. The developer of the rooting tool gives us the firmware build ID the root exploit is based off so we can use it as an indicator only. Sometimes a Samsung smartphone will not want to boot an image that is too old.

What Is Rooting the Android Operating System?

When you buy a new smartphone, you might not know it, but the Android operating system is in a “locked” state. For the most part, it will not make much difference to you: most apps are still available to use, and there are benefits to this locked state such as better security. When you root the Android operating system, you are gaining full administrative rights over the OS.

Why Would You Want to Root Android?

Gaining full administrative rights over the operating system has some perks to some people. For example, out of the millions of applications available on Google Play, some of them will not be able to run on your device unless it has root access. Until you have a specific need for wanting Android rooted, you probably want to leave Android as it comes out of the box. But if you need to unlock an app, then that is when you want to look into rooting methods. Using more apps is only one example of why you may want root access, here is the full list of benefits:

  • Unlock more applications. Some of the apps available for Android cannot run unless you have root access. This is because the app’s features cannot run without the root permissions because the features require the full system access before they can be useful.
  • Better battery life. Smartphones are great, but they have one caveat, which is each time you recharge the battery, it loses some of its overall lifespan. That means smartphones, in general, do not make great investments, and if your weekly paycheck is low, you will want to limit the number of smartphones you go through. One of the ways you can do that is by removing bloatware and creating a better battery life.
  • Bolster performance. If you are the budget-conscious shopper, you may want to increase the device’s performance. This can be done by removing the bloatware as well. The more processes you have running, the more memory that is used. By removing some of the apps, it can help lighten the load on your hardware.
  • Customize Android with themes. With root access, you can download and install any theme that’s at your disposal. That includes any customized theme you can find.

What Are the Risks of Rooting?

If you are buying a smartphone that is not running iOS, then it is probably the Android operating system that you want running as the ideal software to pair with your shiny new hardware. It is, in fact, the Android OS that offers you the chance to customize the OS considerably more than iOS: custom themes, run any app you know about, the works. For many users, the “openness” of an operating system is important, because it offers them more freedom which means running into fewer problems with their investments. But there is a reason iOS likes a far more locked approach: the ability to customize is not for everyone, and if you do not know what you are doing it can lead to a lot of problems which can define your time with the OS rather than freedom.

With power (full admin permissions) comes greater responsibility. Here are some of the main risk factors when it comes to rooting:

  • Malware becomes a larger threat. You might read the occasional news article about how new malware is wreaking havoc in parts of the world on Android. But the Android operating system with root access becomes considerably more vulnerable to exploits because applications are no longer prisoned off in their own sandbox environments. This means if you accidentally download malware, it can do more damage because it can spread throughout the operating system and even jump into other applications and potentially view sensitive data.
  • You can accidentally brick the smartphone. There is always a chance that you end up bricking the smartphone before you had the opportunity to use it with root access. That is because if you are going to brick it, it is going to happen during the rooting process.
  • You may void the warranty. Most manufacturers do not allow you to root the Android operating system and still get to bring it in for repairs under warranty. Whether they are legally meant to do that or not is another question, but it is now common knowledge that most do not want to help you if they find out you have unlocked the OS with root access.

Files You Need

  • Download the Galaxy S5 SM-G900I rooting file for the 6.0.1 Marshmallow update from here.
  • Download the Samsung Galaxy S5’s USB Drivers for the Windows computer from here.

You must have a computer that is running a version of Windows operating system to use this guide or else you will not get the rooting file to flash, and it will not work.

You must have the Samsung Galaxy S5 smartphone with the SM-G900I model number to use this guide or else it will get bricked using one of the other model numbers in the S5’s range. You can find out the smartphone model number of your S5 by tapping on the Settings > About Device > Model Number.

The Samsung Galaxy S5 smartphone will be subject to certain software updates in the future. Some of those updates could potentially update the Android operating system of yours with a new bootloader. When that happens, the CF-Auto-Root tool will need to be updated. The way in which that works is Chainfire — the developer of the CF-Auto-Root tool — relies on people like you to submit the new recovery image to the official XDA-Developers forum page so he can then use it to update the files. These changes should happen relatively quickly, so if you are here using the guide and haven’t just updated to a new version of Android the files should be in perfect working order. Furthermore, the changes Chainfire makes will be automatically reflected in our guides, so you do not have to worry about relying on us to update the files.

Rooting the Samsung Galaxy S5 SM-G900I smartphone running on Android 6.0.1 Marshmallow updates

  1. Enable the USB Debugging Mode for the Samsung Galaxy S5 smartphone first.
  2. Extract the rooting package to the desktop of the computer so you can use the rooting file and the Odin executable file.
  3. Install the Samsung USB Driver on the Windows computer so the smartphone can be detected by the flashing tool.
  4. Boot the Samsung Galaxy S5 device into the download mode and then connect it to the computer with the USB cable.
  5. Wait for about five to ten seconds for the ID: COM port color to change to a yellow or blue color from the Odin user interface letting you know that the drivers are working, and the device is connected securely.
  6. Do not change any of the default settings you get from the Odin flashing tool user interface.
  7. Click the AP button from Odin and then browse the desktop for the rooting file ending in the tar.md5 file extension that will root your S5 smartphone.
  8. Click the Start button from the Odin user interface and wait until you can see some text appearing on the display of the smartphone.
  9. Wait until you can see the text say that it is installing the SuperSU on the device, cleaning up the cache partition for a smoother experience, and then reflashing the stock recovery.
  10. Look up at the computer display once again and then check that the Odin flashing application gives you a green light box with the pass text message inside letting you know that your Samsung Galaxy S5 smartphone is now rooted and ready to disconnect from the computer.

In conclusion, that is how to root the Samsung Galaxy S5 smartphone with the SM-G900I model number running on the Android 6.0.1 Marshmallow updates. You will find the smartphone reboots by itself, and the SuperSU will appear in your app drawer for the first time if you haven’t done this before. That SuperSU app is what is acting as your Samsung Galaxy S5’s gatekeeper and will not let any app through without your permission. Now once you install an app from the Google Play Store the SuperSU will notify you and ask whether you want that app to be granted root access or not. This part is important, and you should only say yes to the message if you can see the app that is requesting the permission. Do not allow access to anything that you do not trust or feel should not have access to your system. For example, if you get a request from the Navy to get access to your messaging applications, you probably do not want to allow that.