There are plenty of Linux distributions out there that are available for you to run in a desktop environment. One of them that most people have heard of is the Ubuntu. In Ubuntu and most of the Linux versions of operating systems that run on desktops, you get given the root user account by default when you first setup the computer for the first time and from then on all you need to do is log into the root user account with the right credentials that you assigned for the account. We all know this process already. We do the same thing when logging into a Windows or Mac computer.
In Android, we do not have the same root user account available to us. Android is based on the same Linux kernel as those operating systems such as Ubuntu from desktops, and the root user account does exist on Android, but it is blocked off by the Android developers before they deliver it to be the operating system running on a particular device. If you want to have the root user account available, then you need to follow a guide that gets you the root access. There are often a few ways to do it, and they all are done with the help from third-party developers.
It’s said that it’s called the root user account on Android because when you are in control of it, you get the full write permissions over the root directory on the operating system that allows you to run any command you please and access all files. That means you get the ability to do what you want to do on the operating system and nothing is locked away or unable to be installed. Most of the fun for your system comes from apps and what apps you can now install with root access and what apps you can remove with root access.
Details We Should Know
- Chainfire was running on the MMB29K.A510MUBU2BPH1 firmware build number when the rooting file that is available in this guide was developed. He lets everyone know the firmware he had running for all of the versions of the rooting tool. By him letting you know the firmware he had running, it is not suggesting that you need to be running on the same as him. As long as you have the right Android version the, guide should work just the same.
- You can reach out to Chainfire by sending messages to the CF-Auto-Root tool thread made on the XDA-Developers website and leave the recovery image file from the firmware you are running if you are flashing the rooting tool and it causes your smartphone not to boot up after the flashing; these are the times when a new bootloader is probably present in the firmware and the rooting file needs updating before it will work again.
- You need to have the Samsung Galaxy A5 smartphone that comes with the SM-A510M model number to be able to flash the version of the rooting tool that is available in this guide. Flashing the wrong one typically means you the need to flash the right stock ROM on the device using the same Odin flashing tool or else the smartphone remains bricked.
- You need a computer that is running on the Windows operating system to be able to flash the rooting file found in this guide because the rooting file is only n Odin-flashable file.
Files We Need
- Download the CF-Auto-Root tool for the Samsung Galaxy A5 SM-A510M smartphone when it is running on the Android 6.0.1 Marshmallow software updates.
- Download the Samsung USB Drivers for the computer that is running on a version of the Windows operating system.
Rooting the Samsung Galaxy A5 SM-A510M smartphone running on the Android 6.0.1 Marshmallow software updates using CF-Auto-Root
- Unlock the Developer Options menu that is always built into the Android operating system on the Samsung Galaxy A5 smartphone, so you can start using the set of options that become available to developed inside.
- Enable the USB Debugging Mode from the Developer Options menu so that the Android software that is running on your device allows for the necessary steps to happen for the rooting to work.
- Install the Samsung USB Drivers on the computer that you are planning on using for the flashing so the flashing application on the computer can identify the type of device you want to connect.
- Extract the rooting file to the Downloads folder on the computer, so you can then use the flashable version of the rooting file and the Odin flashing tool.
- Click on the Odin flashing tool application executable file from the Downloads folder so that the flashing tool user interface opens up on the computer.
- Boot the Samsung Galaxy A5 SM-A510M smartphone into the Download Mode and connect it to the computer with the USB cable that is available for charging the battery that you typically get with the device when you open it out of the box.
- Check that Odin shows a color coming from its ID: COM port and the added message appears so that you know the Samsung USB Drivers are installed correctly and working.
- Do not make changes from the default options that are available from the Odin user interface.
- Click on the AP button and then browse through to the Download folder that the PC had and choose to upload the flashable version of the rooting file to the Odin application.
- Click on the Start button from the Odin and then the rooting of the Galaxy A5 begins; read everything you then start to see rolling down the display of the Samsung Galaxy A5 smartphone that has been programmed to let you know what you can expect from the rooting file and how long this particular version of the rooting file typically takes to complete.
- Wait for the Odin user interface to show the pass message before unplugging the smartphone from the computer.
In conclusion, that is how to root the Samsung Galaxy A5 SM-A510M smartphones running on the Android 6.0.1 Marshmallow software updates by flashing the CF-Auto-Root tool by Chainfire. The one-click rooting tool that Chainfire named CF-Auto-Root does the same thing for each device which is getting the SuperSU program installed and enabled the way it needs to be so it can issue the rooting privileges that the root applications need before they can run.
The way it works is by blocking root access to every app you install by default and ten the apps that you try to run that require root access are detected by SuperSU and the SuperSU then sends you a message asking you to confirm that you want to grant that particular application the root access it is asking for. It is here where anything you accept root access immediately, and you need to be aware of your decision, so you don’t give root access to malware. It'[s for that reason that rooting Android gets a bad name but if you think about it it is no different than using anti-virus on a computer. You block everything by default and then can create an exception to allow something through the same way you are doing it with the SuperSU.