Rooting the Samsung Galaxy Note 3 using the CF-Auto-Root tool will do little to your operating system apart from installing the SuperSU on the device. SuperSU is by far the most common way to root an Android operating system. Whether the rooting guide you are using makes you install a custom recovery and then upload the SuperSU, or whether you can only flash a file and get SuperSU installed, they both result in the same thing. SuperSU becomes an app on your device, and it grants your system the root access. That then allows you to install apps from sources online like the Google Play Store. Once you open an app that requires root, the SuperSU app will bring up a message asking whether or not you want to grant it root access. It’s at this time that you must say yes, and then the app will start working. Should you attempt to install a root requiring application without SuperSU installed, as soon as you try opening it, the app will tell you that it cannot run or that it needs root access to run.

As far as rooting apps go, there are many to choose. One root app I always recommend to Samsung device owners is the Titanium Backup application — though you must be an advanced Android user to use Titanium Backup. Speaking from my Android rooting experience, it is very easy to think you know what it is okay to uninstall and then end up with a bricked device. Tread very carefully when choosing to uninstall something. To this day, I’m not quite sure how I managed to brick my device using Titanium Backup, but I think the instability might have happened when I chose to uninstall everything to do with Samsung Kies security. Each day now I use my smartphone with an operating system that will freeze or start pressing keys without my fingers touching anything. The phone is usable but very annoying. These are the type of brick symptoms you can expect to find should you delete something you shouldn’t have when using the Titanium Backup app.

Samsung Galaxy Note 3

The firmware that the root exploit in this guide is based on comes with the LRX21V.N900XXUEBOA6 build number. Chainfire states that it does not mean you have to flash that firmware on your Samsung Galaxy Note 3 smartphone. It just is there for people to use as an indicator because some of the older Samsung devices like the Samsung Galaxy Note 3 smartphone may not boot old images when they become old.

Files You Need

  • Download the new CF-Auto-Root file for the Note 3 SM-N900 on Android 5.0 from here.
  • Download the Samsung USB Drivers for the Note 3 SM-N900 smartphone from here.

There will be some Android updates that arrive over the air and become available to install by flashing them manually on your device. Some of the larger updates that update the Note 3 to newer numbered versions of Android can sometimes bring new bootloaders with them. These new bootloaders can present a problem for Chainfire — the man behind the CF-Auto-Root tool. The problem is a temporary one where he will need to update the files on his end, and those changes will then be automatically reflected in our guides. For Chainfire to update the data when they need updating, he relies on people like you to submit the new recovery image files to the official CF-Auto-Root tool thread at the XDA-Developers website.

Rooting the Samsung Galaxy Note 3 SM-N900 running on the Android 5.0 Lollipop software updates

  1. Enable the USB Debugging Mode on the Samsung Galaxy Note 3 smartphone so you can connect it to the Windows computer with the USB cable.
  2. Extract the rooting file to the desktop of the computer so you can see the Odin flashing application and the rooting package inside.
  3. Install the Note 3’s Samsung USB Drivers on the computer so you can connect the device and have it detected by the flashing tool.
  4. Boot the Samsung Galaxy Note 3 smartphone in download mode and connect it to the computer with the USB cable you usually require to charge the battery in the device.
  5. Double-click on the Odin executable file and the Odin flashing tool will open on the desktop of the computer.
  6. Make sure you can see a blue or yellow ID: COM port box from the Odin user interface.
  7. Click the AP button available from Odin and then browse the desktop for the rooting package.
  8. Do not change any of the default settings from the Odin user interface.
  9. Click the Start button and then wait for the rooting to complete.
  10. Check that you can see the screen of the Samsung Galaxy Note 3 smartphone say that it is installing the SuperSU, cleaning up the cache partition and then flashing the stock recovery.
  11. Look back up at the computer display for the green pass box coming from the Odin user interface.

In conclusion, that was how to root the Samsung Galaxy Note 3 smartphone with the SM-N900 model number running on the Android 5.0 Lollipop software updates by flashing the new version of the CF-Auto-Root tool. Your Note 3 smartphone should no automatically reboot to the normal mode, and you will find the SuperSU application available from the app drawer. That SuperSU app is going to be granting your device the rooting permissions it needs to run. It is also going to act as though it is the gatekeeper to all applications on your device, so you will be prompted with a message every time an app wants root access. It’s your job to keep out anything that looks like it might be malware.

Anyone who needs to some tips for getting a Samsung Galaxy Note 3 rooted with the CF-Auto-Root tool will need to try installing a new version of the Odin flashing application if the version you are using in this guide does not work. Those who still face problems can try checking if the Samsung Galaxy Note 3 smartphone did end up making it into the recovery mode after the flashing completed. Your device does need to get into the recovery mode for it to be rooted — Chainfire tells us this from his official repository age.

What is more, there will be times when for whatever reason the CF-Auto-Root tool does not automatically boot into the recovery mode at the end like it is supposed to. When that happens, you will find the device is not properly rooted when checking for root access from apps like the basic root checker app from the Google Play Store. The root checker app won’t be lying, and your device most likely isn’t rooted because it getting into the recovery mode was a requirement. You can fix that recovery problem by booting into the recovery mode manually using the hardware keys as soon as your device is finished with the flashing.