Last Updated on May 13, 2023 by Mathew Diekhake

If a person were to buy a computer and turn it on only to find out that they were not able to install the programs that they wanted running on it there would be problems because that is obviously not going to work.

Android get away with this kind of things on a daily basis because all of the mobile devices that are bought that run the Android operating system on them do not give people full control over what is installed and what is uninstalled. Most people do not notice that they are not in control of the root user account because they live their lives and don’t download anything that needs root permissions before it can run.

The term “root permissions” is unique to the Linux kernel which is what the Android operating system is based on. The root user account is always there, but it is locked up, so you do not have control over it by default. It is that root user account that is the same as logging into a computer running Windows that allows you to install the things you want to install as well as uninstall any programs that you want to be removed.

There are certain types of people that notice things that cannot be installed on Android more than the rest of us and those people are the ones who like anything to do with developing. When you go to develop an operating system, you need to have access to the most lowest levels of permissions possible or else no app is powerful enough to do anything worthwhile. It is that access to the lower levels of Android that are taken away to everyone unless they are in control of the root user account.

Notes:

  • Chainfire tells us that he had the MMB29M.G900FQJVU1CPE2 firmware build number running on the Samsung Galaxy S5 SM-G900FQ smartphone at the time of developing the rooting file found in this guide. He gives you that information of the firmware that he had running so you can use it as an indicator. He is not suggesting you should flash that same firmware on your Samsung Galaxy S5 smartphone before you follow this guide.
  • There is a proper CF-Auto-Root tool thread setup at the XDA-Developers web forum and if you post messages there Chainfire, the developer of the CF-Auto-Root tool sees them. He does not mind if you post messages there asking for new requests for new devices that do not yet have a version of the CF-Auto-Root tool available. You can find out that information by visiting his repository page for the tool. Additionally, you need to leave a message containing the recovery image from the firmware you are running if you flash the CF-Auto-Root tool and your device will not boot up afterward because that is a sign that the rooting file needs updating.
  • You need to have the Samsung Galaxy S5 smartphone that comes with the SM-G900FQ model number if you are going to use this guide. Any of the other model numbers require a different version of the rooting file and flashing the wrong one does come with consequence—you brick the device and need to flash another stock ROM on it to get it working again.
  • You need a computer that has one of the versions of the Windows operating systems running on it. If you try flashing the rooting file in this guide on any other operating system, it does not work because the Odin flashing tool you are using to flash it with does not run unless it is on a Windows operating system. Trying a virtual machine for Mac or Linux is not the way to make it work either and can potentially do damage.

Download Samsung Galaxy S5 SM-G900FQ CF-Auto-Root and Drivers

How to Root Samsung Galaxy S5 SM-G900FQ on Android 6.0.1 (Marshmallow) Using Chainfire’s CF-Auto-Root

  1. Unlock the Developer Options menu on the Samsung Galaxy S5 SM-G900FQ smartphone so you can use all of the options that are available to developers inside.
  2. Turn on the USB Debugging Mode from the Developer Options on the Samsung Galaxy S5 SM-G900FQ smartphone so you can change the Android software that is running on your device.
  3. Install the Samsung USB Drivers on the Windows computer so that the flashing app can detect your device.
  4. Extract the rooting file to the Downloads folder on the computer, so you can see the flashing app file and the flashable version of the rooting file.
  5. Run the Odin flashing application that is available in the Downloads folder.
  6. Boot the Samsung Galaxy S5 SM-G900FQ smartphone into Download Mode and connect to the computer with the USB cable.
  7. Check that Odin shows a blue or yellow ID: COM color and the added message shows up on the Log so you know the Samsung USB Drivers are working and that your smartphone is prepared for the flashing to begin.
  8. Do not make changes to the default options available inside Odin or you might lose data.
  9. Click on the AP button from Odin and navigate to the Downloads folder again and click on the rooting file there to upload it to the Odin.
  10. When you can see the rooting file extension appear in Odin next to the AP, just click on the Start button from Odin for the rooting for the Samsung Galaxy S5 smartphone to begin.
  11. Read all of the information that starts rolling down the display of the Samsung Galaxy S5 smartphone, so you know what it about to happen and what to expect.
  12. Wait until the smartphone screen says it is rebooting in ten seconds and for the Odin user interface to show a pass message inside a green box.

In conclusion, that is how to root Samsung Galaxy S5 SM-G900FQ smartphones running on the Android 6.0.1 Marshmallow software updates by using the CF-Auto-Root tool by Chainfire. The SuperSU is now installed and enabled on the smartphone, and you notice it as an application. You can enter the SuperSU app by tapping on it just like you can any other app, but you do not need to enter it for it to help you install the root apps. Just open up the Google Play Store or your preferred web browser and search for the rooting apps that you wanted to install. When you go to open them up after the download completes the SUperSu prompts you with a new message on the display that makes you confirm that you do want to grant the app rooting permissions over the operating system. Once that is done the root apps runs just like a typical app and you can start using it.

Related Tutorials