What does rooting android does

What does rooting your phone actually mean?

We love getting your questions. It’s always a good thing when we can help each other, and we learn stuff ourselves when looking for the answers. While we can’t find time to answer all of them, sometimes a certain question comes up enough that it deserves a detailed answer.

«What does root mean?» is one of those questions. The concept may be simple for some of us, but for many folks who haven’t spent time fiddling around with Android or any other permissions-based operating system, it’s something to ask questions about. I’m going to try and answer them all as best I can.

Permissions

Before we define root, it’s important to understand why it exists and how it works. It’s because Android uses permissions (Linux-based permissions, to be exact) in the file structure. Every file, every folder and every partition has a set of permissions. These permissions decide who can read a file (look at or access the contents without changing them), write to a file (be able to change the contents of that file, or create a new file inside a folder or partition) and execute a file (run the file if it’s a type that can run, like an app). This is done based on users and permissions — certain users have access, while users who don’t have the right permissions are blocked from having access.

When you first set up your phone and turn it on for the first time, you are assigned a user ID. If another user logs in via Google, they are assigned a different user ID. When an app is installed on your phone, it’s also assigned a user ID of its own. The system itself is a user and other processes that need to run on your phone may have their own user ID. Everything that can do anything to any files on your Android is a user.

A system of users and permissions is how Android keeps track of who can do what.

Let’s say you install a messaging app. It gets assigned a user ID when you install it. It also gets a spot on your data partition of it’s own, that only it has access to. You have permissions to execute the app, and when the app runs it has permission to access its own data folder and files. The app may also request permission to access things like your address book or SD card or photo library. If you say yes to these requests (or if you agree to the permissions on older versions of Android) the app’s user ID is granted permission to the data files of those things, meaning it can look at the data folder and its contents and possibly change them or add new files. The app can’t access any data files it doesn’t have permission to «look» at. That means (in our example) it can’t do things like look at the settings database, or access the data folder of another application. The term sandbox is often used for this — apps are sandboxed and can only play in the sandboxes they have permission to be in.

For files that are programs and can run (like apps), the same permission model applies. Your user ID has permission to run the apps you installed while you are signed in. The system user has permission to run them and other system-level users may have access to the apps or certain processes the apps use. Other apps can’t start up apps they don’t have permission to start. If you added a secondary user, they don’t have access to your apps or files and vice-versa. There are files, folders and apps on your phone that your user ID doesn’t have permission to see, alter or run. Usually those parts of Android require system-level permissions (the system user ID) to do anything with, and you aren’t the system user or a user that has system-level permissions.

Switching permissions

While it’s technically possibly to change the way your phone boots up and the files it uses to start the running system and assign your user ID elevated permissions, that’s neither safe nor practical. But Android (and most Unix or Linux based systems) have what’s called a root user, and support the SubstituteUser binary (think of a binary as a small app) to change user IDs. Those are used to administrate the system at the core level.

Because the people who made your phone don’t want you to have easy access to the root user ID — and not all the reasons are selfish because it also protects you and your private data — the SubstituteUser binary isn’t included in most builds of Android. Without SubstituteUser, we can’t switch our user ID. Most system level things in Android have similar easy names, by the way. The core security (files in the bootloader and/or the kernel itself) are also built in a way to prevent you from switching user IDs as part of the SELinux (Security-Enhanced Linux — told you the names are easy) kernel module. Some phones (Samsung’s Knox comes to mind) have further protections, and nearly all the companies who make Androids require that, in order to make changes, the bootloader would need to be unlocked so these files can be changed and allow you to switch user IDs. Some phones, like the BlackBerry Priv even go a step further and aren’t going to boot if we change anything (even if we could).

To become root, you need a way to change your user ID.

Once we get past all that — either by unlocking the bootloader through authorized means or using some sort of exploit — we can place the SU binary (SubstituteUser) in a spot that it can run when it’s called to run — that’s called a PATH. If any app is in your user ID’s PATH it will run without telling the system exactly where it is. You also need to make sure the SU binary is in a spot that your user ID has permission to execute (run) files. Any other app (Google Play has plenty of apps that need root permissions) will also need the same access. When you use a method to root your phone, all this is sorted out by the folks who built the root method.

Once all that is in place, we can run the SU binary (or another app can run the SU binary).

Getting root access

This is where root comes in. The SU binary uses flags when it’s run to tell the system what user ID you want to switch to. For example, if I run the SU binary on my Ubuntu computer like this «su Jim -c nano» I will run the nano command as the user Jim (after supplying Jim’s password). If you run the SU binary with no flags or arguments, it switches you to the root user. Normally you would need to supply a password, but since «root» is an unused user on Android it has no password. Running the command «su» will switch you to the user root, and assign you the user ID of 0, and put you in the root group. You are now the Super User.

As the Super User you can do anything to any file, folder or partition on your Android. By anything, we mean literally anything. You can remove bloatware apps and you can also remove essential system files that break your phone. You can also do things to the hardware like change the CPU frequency and ruin your phone forever.

Root is the super user, who can do anything. And we mean anything.

Apps can do the same thing. SU is placed where it’s in the application PATH and any app can call it and run it. That app then has Super User permissions, and can do anything it likes to any file any place on your phone. This is why the people who made your phone really don’t want you to have this level of access, and the companies who allow you to unlock the bootloader and change things still don’t place the SU binary on your phone by default. Having root access with no way to control who or what can use it is dangerous to your phone’s software and your personal data.

That’s why you need to install an app that forces you to allow root access any time you or another app tries to invoke the Super User permissions. Most times when you use a root method for your phone one will be included, along with some other useful binaries like the BusyBox toolset. If you did things by hand, you’ll need to install one yourself. SuperSU by Chainfire in Google Play is a good one to start with.

Odds and ends

Many phones and some root methods do things a little differently (Android 4.3 brought a lot of changes) and require scripts or a daemon (you’ll see words like daemonsu or su.d mentioned) instead of just dropping the SU binary in place. These are used to call SubstituteUser so you can switch to the root user just like the raw binary method. The people who figured out how to root your phone have sorted all this out and it will work the same on the user-facing side.

It’s also possible to «temp-root» some Androids. This means you can have Super User permissions and do a few things you need to do, but a reboot takes root access away. Likewise, you can have a «shell-root» where you can only access the root user through adb from your computer.

Finally, I want to stress that if you had these questions, you need to consider if you’re ready to have a rooted Android. We weren’t kidding when we said it’s easy to ruin your phone with SuperUser access. There’s no reason to be ashamed that you need to do a little reading or ask a few more questions before you do things that can break your phone or give some random rouge app access to all your data.

That’s what we’re here for.

We may earn a commission for purchases using our links. Learn more.

Samsung needs to bring back its iPod competitor

I don’t want to buy an iPod Touch. Since I want a reasonably priced PMP with acceptable audio hardware that can install a few crucial apps, I might have to.

VoLTE: How to use it and why you should care

VoLTE — or Voice over LTE — is the new standard for calling throughout the U.S., Canada, and parts of Europe. Not only does it facilitate much higher call quality between cell phones, but it allows devices to stay connected to LTE while on a call, improving data speeds for everyone.

PlayStation reportedly planning service to compete with Xbox Game Pass

Sony is planning to create a service similar to Xbox Game Pass, according to a new report. The service could launch as early as sometime in the spring of 2022, with multiple tiers.

These are the best USB-C cables you can find for Android Auto

Android Auto is an absolute necessity when driving, regardless of whether you’re headed out to the grocery store or for a long road trip. These cables will ensure your phone stays protected and charged, no matter what.

Источник

Root Android: Everything you need to know!

One of the best things about Android is how customizable and flexible it is. Android lets you use it the way you want to, whether that means changing the launcher, or setting up a host of unique automatic functions with Tasker. But for some, that isn’t enough. You can gain near full control of the OS if you root Android.

This isn’t as common as it once was, but there are still benefits to rooting Android. If you like the sounds of that, but find yourself feeling a little anxious about “hacking” your much-loved (and probably expensive) device, then read on to learn everything you need to know about rooting Android. It’s actually easier than you might think.

Rooting Android:

Editor’s note: Rooting Android devices requires a high level of tinkering and modifying your phone’s software. This can be risky, and there is a chance you’ll damage your handset. This is bad news considering rooting Android may void your warranty. Always do your research and be sure you’re confident about the steps you’re taking, as no one but you will be responsible should anything happen to your device.

What is rooting?

While it might sound scary, rooting simply refers to the act of obtaining access to commands, system files, and folder locations that are usually locked off. Rooting Android can be thought of as promoting yourself from a system user to an administrator, with the additional freedom and risks that come from more control over the deeper workings of your device. With great power comes great responsibility and all that!

More specifically, adding root to Android means becoming a superuser, which is a Linux function you may be familiar with. In many ways, then, you could view this more as restoring a function that should have been there, to begin with!

Users can install and run applications on rooted Android phones and tablets that require special privileges, bypass carrier installed software, and even remove bloatware applications (as opposed to simply disabling them). Root access is even needed if you want to install trivial things like certain custom fonts, and rooting Android can also unlock new features in certain apps and launchers.

Rooting is no longer always essential for flashing a custom ROM. However, it is advisable to root Android in some cases to make use of the most interesting features.

Handy rooting terminology:

• Bootloader: Lowest level software on your phone that starts up recoveries and then the main operating system.
• Recovery: Low-level software that can create and restore full system backups. Accessed before the main OS.
• ADB (Android Debug Bridge): A command-line tool that is part of the Android SDK, which supports communication between a computer and an Android device.

To root or not to root?

The next question is whether you should root Android or leave it as it is. That, of course, is a matter of personal preference, but there are some compelling arguments both for and against.

On the plus side, it gives you more access to several cool apps and customization options. It also lets you upgrade older phones to newer versions of Android, long after your manufacturer and carrier have stopped supporting it. As mentioned, rooting Android will let you change things that you otherwise couldn’t, and it will also let you use a host of cool apps.

Android root apps and options

Here are just a few things you can do with a rooted Android device:

• Overclock or underclock the CPU.
• Increase battery life.
• Greatly enhance the power of Tasker.
• Remove preinstalled bloatware apps.
• Make real backups.

• Install custom ROMs.
• Further customize your phone’s looks.
• Install apps that do more than basic ones.
• You can even do things like installing Ubuntu for desktop.

For some people, rooting Android is also something of a statement. You paid for this device, so why shouldn’t you use it exactly as you wish? Especially if it means removing cynical and unhelpful bloatware. There’s also a certain status that comes from it, and a great sense of accomplishment when you achieve root access for the first time.

And obviously, if you’re a developer hoping to create your own root apps, you need to start somewhere!

Will you damage your device?

That said, there are also some potential downsides to rooting.

For one, even once you know how to root Android, there are some risks involved. Get this wrong, and there is a slight chance of bricking your device (it’s happened to me). It’s definitely easier and safer on some devices than others, but if you’re not overly confident with your tech wizardry, then you may prefer to leave well enough alone.

Furthermore, rooting can cause some issues with official OTA handset updates – but it is usually fine to install new software manually once you’re rooted. Updating will often cause root permissions to be lost, in which case the procedure will need to be performed again. Occasionally, an update will block old root methods, and sometimes rooted devices will fail to install updates. If your device stops booting after an attempted root exploit, you can usually restore it to factory specifications rather easily.

Warranties and legalities – is rooting legal?

This leads us nicely onto warranties, which is another grey area in the world of rooting. While carriers don’t like you tampering with their hardware and software, some manufacturers have become kinder to rooters and even those who install third-party software. However, few have a clear stance on what software tweaks will void your warranty, and you certainly can’t count on having your rooted handset fixed if something goes wrong. Devices with locked bootloaders, the very low-level software that starts up your phone, are designed specifically to prevent rooting, so don’t expect any sympathy from these companies.

Manufacturers and sellers can often identify root, even after you unroot, thanks to clues like Knox on Samsung. Note that there are ways to hide evidence of having rooted your device, but these won’t always work. There’s a kind of arms race going on between hackers and manufacturers, and your chances of unrooting and covering your tracks will often come down to who is winning at the time! This is why a lot of people only root older phones that are already out of warranty.

This might also lead you to wonder whether rooting your device is even legal? This is tough to answer as it depends on your own country’s laws. Many countries allow for the bypassing of digital rights management and locks, providing that this is not used for other illegal purposes, such as circumventing copyrights. Rooting has been legal in the USA since 2013.

Security

It’s also worth noting that some apps and features will stop working once you root. For example, banking apps will often stop working due to the perceived security risk. Even Snapchat and Pokemon Go take issue with root! That said, there are also often countermeasures to these limitations – though your mileage may vary. As you can probably tell by now, rooting typically means creating more work for yourself, but it’s really fun work!

The final major point to be aware of is security. With a greater level of control comes a greater level of risk, and rooting your phone can open up your device to more dangerous pieces of malware. This is where governor applications come in, which monitor and control which processes are given root permissions. You may be familiar with SuperSU or other similar apps. These are very straightforward to use and simply display a pop-up whenever an app or process wants root access, which you can either deny or allow and save your preference if you trust the app.

Of course, if you aren’t automatically receiving the usual updates, it also falls on you to ensure you are getting all the latest security patches. In theory, with the right root apps, you could actually improve your privacy. But it’s on you. It should also be noted that SuperSU developer Chainfire hung up his root apps, so most rooters have now switched over to Magisk.

So, should you root Android?

With all that in mind then, should you root your Android device?

Ultimately, that comes down to what you intend to use your device for. Do you even need to root Android? If you have a specific use-case scenario in mind, and you understand the risks and limitations, then there’s nothing to stop you from learning how to root Android and giving yourself that extra freedom.

On the other hand, the argument for rooting isn’t quite as compelling as it once was. These days, one can do many things that were once limited to root users (adding a custom ROM, recording your screen, and so on). Not to mention that even budget phones are fast these days, so overclocking is no longer an important reason to root Android.

Seeing as root might also mean you lose functionality, it’s no longer a straight win across the board. It’s fun, powerful, and useful, but it’s not quite as useful as it once was.

For me, the obvious answer is to only root on older devices. Keep your daily driver clean while it’s still getting new updates and patches, but root secondary gadgets that you want to tinker with. That way, you get to have your cake and eat it too.

How to root Android devices

Should you decide to go ahead, then you’ll probably be wondering how to root Android. Let’s lead you in the right direction!

The bad news is there isn’t a one-size-fits-all solution when you root Android phones and tablets. Different brands and even software versions can make the rooting process vary. Even within handset variants, you may find that some techniques work and others don’t.

The good news is that in many cases, rooting is much easier than it once was. In fact, the easiest method is usually to use a simple root app. These apps let you root Android with a single tap, with some popular examples being KingRoot, KingoRoot, and OneClickRoot. Simply download your app of choice. The application will first check compatibility, then go ahead and root your device for you.

This is a minimum-fuss method that will work in a large number of cases. However, it’s worth noting that some come with annoying push notifications and ads. I’d advise checking reviews before settling on which one to use. Some would even say that if you can’t figure out how to root your device without one of these apps that perhaps you shouldn’t be doing it at all (because if you encounter problems during the process, you won’t know what to do).

If a one-click solution doesn’t appeal to you, though, things get a little more complex, and you’ll need to look for specific instructions for your device. This might mean using PC software and connecting your phone via USB. It might also mean using a custom recovery, or downloading additional software like Odin for Samsung devices. The best part about these options is that you learn a lot along the way.

I recommend either Googling “root [YOUR DEVICE NAME HERE]” or heading over to XDA Developers, which is a great place to start. Many of the best root apps available today were developed by members of this community. Just be sure to use the search function first before asking noob questions! And don’t forget to thank and support the devs that make rooting possible.

Before rooting your device, it’s always a good idea to backup first. Then settle in, read a lot, triple-check the instructions, and dive in. Crossing your fingers and holding your breath would be a good idea, too, because you just took the red pill! The world of Android rooting is exciting, empowering, frustrating, and engaging – you’ll learn tons about how Android works, what your phone can do, and how awesome Android can be when you get in the driver’s seat.

Источник