Not everyone has heard of Linux, but it is one of the top three desktop operating systems out there in existence, only trailing the likes of MacOS and Windows in terms of use.

Linux is often used by the “techies” because it is an outstanding operating system with an emphasis on security. The drawback with Linux is that it can be tricky to use by newcomers and those who don’t want to spend a lot of time learning tech, due to its heady use of typed commands required to make things happen. With a more user-friendly operating system like Windows, things have been softened to some degree, and now you just navigate by using buttons instead, though the command line does still exist for executing some commands should one choose to use it.

Android is based on the same Linux kernel that desktop computers are familiar with, but thank goodness you don’t need to be entering commands to make things happen. Due to mobile operating systems being fairly straightforward compared to some versions of desktop environments, i.e., Windows 10 Pro, there’s simply no need for commands to exist.

So in many ways, the Linux kernel and what Google has done with Android is near the ideal mobile operating system. There are one or two caveats, like the fact that it wouldn’t be as secure as it is now if it weren’t for Android choosing to remove automatic access to the root filesystem; now if you want to get there, you need to “root” the Android operating system with a fitting guide that’s made for your software version.

Not allowing root access by default has taken away the option of using root applications, the apps that cannot run unless they get access to the root filesystem. But there’s also something else that stock Android does which is block of the installation of unsigned zip files. It does this from the recovery partition, which users will know by booting into the recovery mode. By stopping the installation of unsigned zips, Android has blocked the chance for users to install custom software. But just like with rooting, there is a way that you can change that, too, if you would like.

Installing a custom recovery image is going to allow you to flash custom software, often referred to just as custom ROMs. What’s more, you can also use the custom recovery to flash rooting files like SuperSu now too, since the rooting files are also unsigned zips.

How to Install TWRP Recovery on Samsung Galaxy A3 2016 (Exynos) Using Odin

Note: The Odin flashing tool is really easy to use, but it only works on the Windows operating system. You won’t get the flashing tool to load on a Mac or Linux computer. It doesn’t really matter what version of the Windows operating system that you’re using as long as it is something above Windows XP.

1. Download and install the Samsung USB drivers on the computer if you don’t have them already.

2. Download the TWRP Recovery for the Samsung Galaxy A3 2016 (Exynos) smartphone from one of the mirror links below that’s for your region:

3. Download the Odin flashing tool.

It doesn’t matter what version, but the latest is the most up to date so grab that one. Extract the Odin file and then double-click on the Odin executable file (.exe) that is found from within the Odin folder after extraction. You should now have the Odin interface open on the computer and waiting for you to connect to it.

4. Boot the Samsung mobile device into the Download Mode by first powering it down and then rebooting by holding the Volume Down + Home + Power keys at the same time.

5. A yellow warning triangle will come up on the device’s display. At this time you need to press the Volume Up button. You’ll then see the device getting into the Download Mode. It’s then ready for the flashing.

6. When in Download Mode, connect the Samsung mobile device to the computer with the USB cable.

7. If you have installed the USB drivers correctly, the Odin flashing tool should detect your device. You can tell this by observing the ID: COM port lighting up with a color, usually yellow or blue.

It doesn’t matter what color, it’s the lighting up that counts.

8. After the device is picked up by Odin, click on the PDA or AP button, depending on what button your version of the Odin flashing tool has.

9. Navigate to the stock ROM folder and upload the tar.md5 file to this location in Odin.

10. Without changing any of the default settings, click on the Start button in Odin, and the flashing then begins.

11. Wait until Odin shows a Pass message before disconnecting your device.

That’s all.