Samsung after receiving Root. The Android phone does not turn on beyond the logo (does not want to boot) After receiving root rights, the phone turns on

Modern phones - this is a rather complex system with its own settings and operating mechanism. When buying a phone, the user cannot immediately access the “internals” of Android, so . But how to completely remove root rights from Android if they are no longer needed or even harmful?

What are ROOT rights and why remove them

ROOT rights are a software project that allows the user to carry out various actions with a smartphone at the system level. These are a number of advantages that relate directly to the operating system. This includes:

• Editing system files . You get access to the Android editor and can delete, add or change a specific folder/archive at your discretion.
• Ad blocking. To completely remove intrusive materials from applications and the browser, you will need special programs and root rights.
• Overclocking the processor to maximum numbers. Yes, the power will increase, but, alas, this often leads to the device burning out.
• Uninstalling apps and tools, which . For example, Google Maps, Calculator, Voice Recorder.

Unfortunately, In addition to the advantages, there are also significant disadvantages, which often become the reason for root removal:

• Does not work Android Pay . Yes, yes, you will not be able to use comfortable contactless payment.
• Warranty immediately expires. Have you recently purchased a phone and already installed ROOT rights? Well, we have to say goodbye to free service.
• Over-the-air updates stop coming. Quite an unpleasant moment. If you want to get a more recent version of the firmware or OS, you will have to reflash it manually.
• Removing what you need system application leads to the device slowing down or completely freezing. In this case, no one excludes the possibility of “bricking” and the complete disappearance of data without the possibility of recovery.

Now, having familiarized yourself with the advantages and disadvantages of Superuser mode, you know for sure whether you should leave root on your phone. If the answer is no, read on.

Types of ROOT access

First, let’s determine what type of rooting is on the smartphone. There are only three of them:

• Temporary Root - temporary root rights, which disappear immediately after rebooting the phone. They are quite easy to get, and they remove themselves. Therefore this the best choice for inexperienced users.
• Shell Root - full root rights, which still do not give access to the system folder.
• Full Root - unlimited permanent root rights. Perfect option for the experienced Android owner.

Checking for ROOT

How can you find out that your smartphone has these same rights? The simplest and surest way is through the SuperSU program. Usually it is automatically installed on the phone immediately after activating the mode, but if this does not happen, you can download the utility yourself from.

Download it from the store, install it and open it. We see a pale green screen where we click "Start". The next page appears and if the message "Your phone is not rooted" – further actions not possible with the program.

Click "PDA" and specify the path to the firmware file. We tick only the items "Auto Reboot" And "PDA", let's not touch anything else. Let's tap "Run". The flashing process begins, taking on average up to 10-15 minutes. After completion, you will see a green flashing light in the utility and the inscription "Done successfully".

For smartphones of other brands, you will need the appropriate official programs: for Xiaomi it is MiFlash, for Lenovo it is FlashTool, and so on.

Possible problems after removing ROOT and ways to solve them

A fairly common complaint from users is that the smartphone starts to restart after the logo is shown. It would seem that such a problem can be attributed to the disadvantages of root rights, because sometimes they disrupt the stable operation of the device. But no, It is after their removal that the operating system refuses to work correctly for many reasons (accidentally damaged an important file, did not notice a virus).

Us Resetting to factory settings will help. Don't forget to sign in front of him backup and move important files to external storage. Turn off the smartphone, hold the “Home” key and the volume rocker.

The mode appears "Recovery", in which go down to the item “Reset to factory settings”. We clean the system and reboot the device. Everything should start.

Video instruction

Answers to popular questions

After flashing via computer, the phone does not turn on. What to do?

First of all, don't panic. The firmware file may have been damaged, which prevented the program from installing the new shell correctly. Try going into recovery mode and repeating the procedure from there, but then the root rights will most likely not be removed. If all else fails, contact the service center immediately.

Today you learned how you can completely erase all traces of root rights from your Android, and whether it’s worth doing it at all. After reading our article and weighing the pros/cons, you will definitely make the right decision and, if necessary, easily clean the device. Good luck!

Most of the articles in the X-Mobile section are devoted to hacks and tweaks that require obtaining root rights, modifying the firmware, or replacing it with a custom one. However, not every reader is ready to subject their smartphone to such operations, fearing that they can turn the device into a brick or lead to instability in operation. Today I will debunk these myths and show that even in the most stalemate situation, bringing a smartphone back to life is not so difficult.

Destroying myths

Let's talk about what it really means to “turn a smartphone into a brick” and what other pitfalls can await the user on the way to changing the system and installing custom firmware. What glitches can be caught in this case and is it possible to kill a smartphone by reflashing it incorrectly? Will you lose the warranty forever or can the smartphone be returned to its previous condition? Can custom firmware really fail a smartphone owner at the most inopportune moment and are they worth it?

Myth 1. Incorrect flashing can kill a smartphone

A fall from the fifth floor can kill a smartphone, but not flashing it. The main problem that anyone who wants to reflash a smartphone faces is that during the installation of the firmware, a failure may occur, which will lead to its inoperability, and the smartphone will actually turn into a brick.

All this is true, but only on paper. To understand why, it’s enough to understand how the process of flashing a smartphone works and what system components are used. To be able to install on a smartphone third party firmware you need to unlock the bootloader (not in all cases), get root and install a custom recovery console (ClockworkMod or TWRP), capable of installing firmware with any digital signature.

The recovery console is stored in a separate partition of the internal NAND memory and is in no way connected with the installed operating system. After installing a modified version of the console, it will be possible to flash custom firmware or even another OS (Firefox OS, for example). If a failure occurs during the installation of the firmware, the smartphone will not be able to boot it, but the recovery console will remain in place, and all you need to do is boot into recovery again and reinstall the firmware.

In addition, any custom recovery console contains a backup/restore function, which allows you to make a backup copy of the main firmware and restore it unchanged (with all applications, settings and data) in the event that something goes wrong. In fact, the smartphone can be returned to its original state.

You may ask: what happens if the installation of the Recovery Console itself fails? Nothing, in this case the situation will be the opposite, when the operating system itself will remain in place, and the console will be lost. To deal with it, you just need to re-flash recovery directly from Android.

Hypothetically, one can imagine a situation where both the firmware and the recovery console are killed (although this is quite difficult to do), but even in this case the primary bootloader, flashed in permanent memory smartphone.

Conclusion: it is impossible to kill a smartphone by installing third-party firmware through a custom recovery console. Either the recovery or the primary bootloader will always remain in place.

Myth 2. Custom firmware is unreliable

Firmware is different from firmware. In the vastness world wide web you can find a huge number of Android builds for every taste and color, and most of them are really slag, which can lead to instability in the operation of the smartphone and loss of some functionality. Therefore, the first thing to remember is that you should only deal with serious custom firmware developed by large teams of experienced developers. First of all, these are CyanogenMod, Paranoid Android, AOKP, OmniROM and MIUI.

Second. There are two types of firmware: officially supported and ported by third-party developers. The same CyanogenMod, for example, has official version for the Nexus 4 smartphone, but does not have one for the Motorola Defy. But for Defy there is an unofficial port of CyanogenMod 11 from a developer with the nickname Quarx. The difference between them is that the CyanogenMod team is responsible for the support and proper operation of the first, while the second is Quarx personally. Official firmware versions are usually fully functional, but the correct operation of the latter depends on the third-party developer.

Well, third. There are stable and development versions of the firmware. Stable versions of CyanogenMod have the index M (CyanogenMod 11.0 M7, for example). This firmware version usually does not contain bugs. Development versions (in the case of CyanogenMod these are daily nightly builds) may contain bugs and are therefore not recommended for everyday use.

Conclusion: if you install a stable official version of the “normal” firmware on your smartphone, the risk of encountering bugs is minimal. Everything else is for experimenters.

Myth 3. Software that requires root rights can brick a smartphone

In theory, an application with root rights can do anything with the smartphone's firmware, including erasing it completely. Therefore, you need to be extremely careful with such software. The software we talk about on the pages of the magazine is completely safe and tested in our own skin. In addition, for all the time I have been using smartphones on Android (and this is starting from version 1.5), I never I haven’t encountered a situation where software with root support killed a smartphone.

Software distributed through Google Play, usually fully corresponds to the stated characteristics, and if it led to a brick or left a backdoor in the depths of the smartphone, it would not last even a week in the store. In any case, here you need to follow the “trust but verify” rule and carefully read the instructions for using root applications.

Myth 4. Root rights make a smartphone vulnerable to viruses

What makes a smartphone vulnerable to viruses is not root rights, but the bugs used to obtain them. Rooting tools and viruses can exploit the same Android vulnerabilities to gain root privileges, so the fact presence of root does not change anything on the device. A well-written virus will not ask for permissions in a standard way, giving away his presence, he will instead take advantage of the same vulnerability to obtain them covertly.

Moreover, having root, you get the opportunity to install the latest version of Android (in the form of custom firmware), in which these bugs are already fixed. Also, do not forget that most custom firmware allows you to disable root or create white lists of applications that can use these rights.

Myth 5. A rooted smartphone may fail

Software designed to obtain root does four simple things: launches an exploit that allows you to gain root rights in the system, mounts the /system partition in write mode, copies the su binary required to obtain root rights in the future to the /system/xbin directory, and installs the SuperSU or SuperUser application, which will take control whenever any application requests root privileges using su.

None of these steps can crash or kill the smartphone. The only thing that can happen is that the exploit will cause a segmentation fault and the smartphone will reboot, after which it will continue to work normally.

Myth 6. By getting root and installing custom firmware, I will lose the warranty

The guarantee is lost not from the fact of obtaining root, but due to its detection by the service center. Most devices can be unrooted using the Universal Unroot app or by reinstalling the stock firmware using official application from the manufacturer.

There are, however, two exceptions to this rule. The first is the Knox system, pre-installed on new smartphones and samsung tablets, such as Galaxy S4, S5, Note 3 and Note 10.1. Knox delivers an elevated level Android security, responding to any firmware modifications and installation of third-party kernels and firmware. If the user performs these actions, the system sets a trigger that confirms the fact of the modification. The trigger is implemented in hardware (eFuse chip), so it cannot be reset to its initial position. On the other hand, it is not entirely clear whether the service center will refuse to repair the device on this basis. Second: the eFuse chip is installed on some other devices (for example, smartphones from LG), and it also allows you to accurately determine whether the smartphone has been rooted or flashed.

If we talk about custom firmware, everything is more complicated here. Typically, the flashing operation requires unlocking the bootloader, and this can be done either using special exploits or using the smartphone manufacturer's web service. In any case, the unlocked bootloader will definitely indicate that the smartphone did not belong to a blonde.

On some smartphones, it is possible to lock the bootloader back, but you should learn about this separately, and also keep in mind that the newly locked bootloader will most likely receive the status Re-locked, and not Locked, as it was originally (this happens on HTC smartphones, For example). The only exceptions here are smartphones and tablets of the Nexus line, the bootloader of which can be locked and unlocked in three clicks without any dancing with a tambourine, and no one will find fault with anything.

INFO

IN Linux ADB and Fastboot can be installed separately from the Android SDK. On Ubuntu: sudo apt-get install android-tools-fastboot. On Fedora: sudo yum install android-tools.

To prevent Knox from interfering with root applications, you can disable it using the following command from the terminal: su pm disable com.sec.knox.seandroid.

conclusions

Getting root and flashing a smartphone are absolutely safe operations that cannot brick the smartphone for purely technical reasons. The only exception is an attempt to hack the bootloader in order to unlock it. In this case, the eFuse chip (if the smartphone has one) may work and block the ability to turn on the smartphone.

Fortunately, today smartphone manufacturers either prefer not to block the ability to turn on a smartphone with a hacked bootloader (by setting a trigger indicating the fact of such an action, as Knox does), or implement a special web service that allows you to painlessly unlock the bootloader with loss of warranty on the smartphone. which saves users from having to risk breaking the bootloader.

Problems that may arise during flashing

So, now let's talk about what problems can arise when getting root and flashing and how to deal with them.

Scenario one: after an unsuccessful flashing, the smartphone stopped booting

Unsuccessful flashing can be caused by several factors: the battery died and the firmware was only half filled; the firmware turned out to be faulty or intended for a different smartphone model. In the end, there was simply not enough space on the smartphone, which can happen when trying to install the latest version of Android on a smartphone that is three or four years old.

Outwardly, all these problems usually manifest themselves either in endless resets of the smartphone to the initial manufacturer logo, or in the so-called boot loop, when the boot animation plays on the screen for more than five to ten minutes. There may also be problems with the screen (multi-colored ripples) and a non-working touch screen, which also prevent the use of the smartphone.

In all these cases, it is enough to do one simple thing: turn off the smartphone by long pressing the power button, then turn it on while holding down the volume down button (some smartphones use a different combination), and after you get into recovery, reinstall the firmware (Install zip from sdcard - > Chooze zip from sdcard) or restore the backup (Backup and restore -> Restore). Everything is easy and simple.

Scenario two: the firmware works, but recovery is not available

This can happen after a failed installation or update of the Recovery Console. The problem is that after rebooting the smartphone and turning it on while holding down the volume down button, a black screen appears, after which the smartphone either resets or freezes.

Solving this problem is not easy, but very simple. You can install the recovery console on the vast majority of smartphones using the TWRP Manager, ROM Manager or ROM Installer applications. They themselves determine the smartphone model, download and flash the required recovery, without requiring a reboot. If you can’t restore the console with their help, just find instructions on the Internet for recovery installation to your device.

Scenario three: neither firmware nor recovery is available

To be honest, it is difficult for me to imagine such a scenario, but, as practice confirms, it is quite real. There are two ways to get out of this situation: use fastboot to upload recovery to your smartphone, or use a tool from the manufacturer to install stock firmware. We'll look at the second method in more detail in the next section, and I'll talk about fastboot here.

Fastboot is a tool that works directly with the device’s primary bootloader and allows you to upload firmware to your smartphone, recovery, and unlock the bootloader (in Nexus devices). Fastboot support is available in many smartphones and tablets, but some manufacturers block the ability to use it. So you will have to consult the Internet about its availability.

To access fastboot, you will need drivers and the Android SDK. When they are installed, open command line, go to the SDK installation directory, then to the platform-tools directory, turn off the smartphone, turn it on with the volume buttons pressed (both) and connect it using a USB cable to the PC. Next, you need to find the recovery image in .img format for your device and run the command:

$ fastboot flash recovery image.img

Or even force the smartphone to boot recovery without actually installing it:

$ fastboot boot image.img

In the same way you can flash official firmware update:

$ fastboot update update-file.zip

You can find a recovery suitable for your device either on the TWRP website or in the XDA-Developers and w3bsit3-dns.com forums.

We return the smartphone to its original state

In this section, I will talk about ways to return your smartphone to clean stock, no matter what state it is in. These instructions can be used both to unbrick your smartphone and to remove traces of rooting and flashing. Unfortunately, I can’t talk about all possible models, so I’ll focus on the four most popular flagships: Nexus 5 (I call this sample the control one), Galaxy S5, LG G2 and Sony Xperia Z2.

Nexus 5 and other Google phones

Restoring Nexus devices to their original state is easier than any other smartphone or tablet. In fact, it is so simple that there is not even anything to talk about. In fact, all you need to do is install the ADB/fastboot drivers (on Linux you don’t even need them), download the archive with the firmware and run the script. The whole operation looks like this step by step:

1. from here.
2. Download and install Android SDK.
3. Download the archive with the firmware for the desired device from the Google website.
4. Turn off the device, turn it on with the volume buttons pressed (both) and connect using a USB cable.
5. Unpack the archive with the firmware and run the flash-all.bat (Windows) or flash-all.sh (Linux) script and wait for the operation to complete.
6. We launch the command line, go to the directory with the Android SDK, then platfrom-tools and execute fastboot command oem lock for bootloader lock.

For those who are interested in what the script does, here is a list of commands:

Fastboot flash bootloader bootloader-DEVICE-NAME-VERSION.img fastboot reboot-bootloader fastboot flash radio radio-DEVICE-NAME-VERSION.img fastboot reboot-bootloader fastboot flash system system.img fastboot reboot-bootloader fastboot flash userdata userdata.img fastboot flash recovery recovery.img fastboot flash boot boot.img fastboot erase cache fastboot flash cache cache.img

Galaxy S5

Co Galaxy smartphone S5 is a little more complicated, but overall quite simple. This time you will need the Samsung Odin application, which will be used to flash the smartphone’s firmware. Sequencing:

1. Download and install the latest version of Samsung USB drivers from here.
2. Download and install the latest version of Odin from here.
3. Go to the website samfirmware.com, enter the SM-G900F model in the search, find the firmware marked Russia, download and unpack.
4. Turn off the smartphone and turn it on with the Volume Down and Home buttons pressed, wait five seconds until a warning message appears.
5. Press the volume up button to put the smartphone into Odin mode.
6. We connect the smartphone using a USB cable.
7. Launch Odin, press the PDA button and select the file with the extension tar.md5 inside the directory with the unpacked firmware.
8. Click the Start button in Odin and wait until the firmware process is completed.

As I already said, this operation will return the smartphone to its original state, but will not reset the trigger, installed by the system Knox (if she was in standard firmware). Therefore, the service center may refuse to repair.

LG G2

Restoring the LG G2 to its factory state will also not cause any problems. The number of steps in this process is somewhat larger, but they themselves do not require special preparation and knowledge. So what to do to return to G2 factory firmware:

1. Download and install ADB Driver Installer from here.
2. Download official firmware(Europe Open 32G or Europe Open) from here.
3. Download and install LG Mobile Support Tool, as well as FlashTool (goo.gl/NE26IQ).
4. Turn off the smartphone, hold down the volume up button and insert the USB cable.
5. Expand the FlashTool archive and run the UpTestEX.exe file.
6. In the window that opens, select Select Type -> 3GQCT, Phone Mode -> DIAG, in the Select KDZ file option select the firmware downloaded in the second step.
7. Click the CSE Flash button at the bottom of the screen.
8. In the window that opens, click Start.
9. In the next window, select the country and language and click Ok.
10. We wait for the firmware to finish, and then turn off and turn on the smartphone.

This is all. But keep in mind that, as in the case of Samsung, the smartphone will still have Rooted status, and this cannot be fixed.

Sony Xperia Z2

Now about how to return to factory condition Sony smartphone Xperia Z2. As in the previous two cases, this will require stock firmware and the official utility for firmware. You launch the utility on your PC, connect your smartphone using a USB cable and start the update process. Step by step it all looks like this:

1. Download and install ADB Driver Installer from here.
2. Reset your smartphone to factory settings.
3. Download and install Flash Tool from the official Sony website and latest firmware from here.
4. Copy the firmware file to the C:/Flashtool/Firmwares directory.
5. Turn off the smartphone and turn it on while holding down the Volume Down and Home keys.
6. We connect the smartphone to the PC using a USB cable and launch the Flash Tool.
7. Click the button with the lightning icon in the Flash Tool. In the window that opens, select Flashmode, double-click on the firmware in the list that opens.

WARNING

In many smartphones, an unlocked bootloader will not allow an over-the-air update.

In 90% of cases, unlocking the bootloader will entail deleting all data from the smartphone, including the memory card.

conclusions

Flashing a smartphone, and even more so gaining root access, is not at all such a scary and dangerous operation as it may seem at first glance. If you do everything correctly and do not resort to tools that unlock the smartphone’s bootloader, bypassing the manufacturer’s tools, you will not be able to brick your smartphone. Yes, in some cases you will have to tinker to get everything back in place, but what is better - to use a locked smartphone that does not allow you to do even half of the things that it is capable of, or to gain complete control over the device? In the end, reinstalling Windows on PC it doesn't scare anyone.

Now let’s figure out why your Android phone doesn’t load beyond the logo (it doesn’t turn on after the manufacturer’s or robot’s splash screen). Further in the text: first about the reasons and then a deciphering of what to do in this or that case.

This article is suitable for all brands that produce phones on Android 10/9/8/7: Samsung, HTC, Lenovo, LG, Sony, ZTE, Huawei, Meizu, Fly, Alcatel, Xiaomi, Nokia and others. We are not responsible for your actions.

Attention! You can ask your question to a specialist at the end of the article.

If we divide all the reasons why your Android phone hangs on the logo screensaver and does not load further, then this will be

• errors in software(possibly eliminated yourself);
• problems with hardware (only in the service center).

Causes of failure and why it turns on but does not boot

⭐️⭐️⭐️⭐️⭐️ If Android does not load on your phone or tablet when you turn it on, or your Android smartphone starts but does not go beyond the logo splash screen, then the reasons for this may be the following:

• Errors when flashing the device. These include installing an inappropriate or damaged assembly, out-of-order firmware, power failure, and other factors.
• Lack of memory. The system may not start due to lack of memory. The solution may be to delete unnecessary data.
• Incompatible with memory card. If your smartphone turns on but does not boot completely, try removing the memory card and trying to restart the system.
• Hardware problems that occur after impact, fall, liquid ingress, or exposure to extreme temperatures.
• Damage to the power button or its cable, which “shorts” the phone and it goes into a cyclic reboot, loading up to the logo and then in a circle. We encounter this from time to time and can only be diagnosed at a service center.

Before you try to troubleshoot Android, you need to understand why the system won't boot.

Restoring functionality

If the phone shows that the charge is coming, then the causes of the problem must be looked for in the operation of Launcher Android. If your device vibrates or its screen flickers, there is a possibility that the screen is damaged.

If you determine that the problem is software in nature (for example, the problem arose after a firmware update), then a simple reboot will not help. The system must be reset via Recovery Mode or reflash the device. Let's see what to do:

1. While holding down the power button and the volume down key (there may be other combinations, look for your model), go to Recovery Mode. If the phone is , then the problems are at a deeper level, so you need to contact a service center.
2. Perform a factory reset by selecting “Wipe data factory”.
3. Select "Reset" to reboot the device.

This will delete the user's personal data and settings. If this method does not help, perform a flashing. To do this, upload the file with the appropriate firmware to the root of the memory card, insert the drive into the phone and select “Install zip from sdcard” in Recovery Mode.

Increase

WITH software glitch You can do it yourself, but how to fix hardware problems? The most reasonable option is to contact a service center for diagnostics and repairs.

Extracting information from a broken Android

Even if the problem can be solved without financial investment, by simply flashing it, users have an important question - how to save the data stored in the phone’s memory. There are no problems with the memory card: you just need to remove it from the device. But how to save data from the internal drive? For example, pull out contacts.

Increase

If you backed up the system or at least, then getting contacts will be very easy. All you have to do is go to the Contacts app on the Google website to see full list synchronized contacts. If you want to transfer them to another device, all you need to do is add a Google account to it.

After receiving ROOT rights, an Android smartphone or tablet from Samsung stops starting. In this article I will tell you about the reasons for this behavior of the device and ways to solve the problem.

Why doesn't a Samsung device work after Rooting?

Basically, all errors boil down to the fact that at the time of receipt Root is right, the device user did something wrong. Let's look at some reasons:

• The device or computer crashed while getting Root rights, for example, there was a sudden power cut, the USB cable was disconnected and other reasons.
• Attempting to download broken files.
• Trying to download files that are not compatible with your device
• Incorrect sequence of actions when obtaining Root rights

The main thing is not to panic. Now we will try to solve the problem of the device not working.

If you see the following window:

Then you can safely take the phone to a service center. Of course, you can try to reset the settings and try to flash your smartphone via Odin, but the chances are close to zero.

It is important to remember that if Samsung shows at least some signs of life, for example, an eternal boot window appears, there is a cyclic reboot, then you need to try to reset it and reflash it via Odin. In all other cases, only Samsung service will help you.

In our articles on Trashbox you could find out what it is. Now it's time to deal with the shortcomings that root rights bring to Android. Why you shouldn’t install root on your smartphone or tablet - read on Trashbox.

Why you don't need to get root rights

There are many advantages to rooting Android, but almost as many disadvantages that can lead to disastrous consequences. In this article, we tried to highlight the most significant disadvantages and dangers of obtaining root rights for Android.

Loss of warranty service
If you decide to root your Android device, then be prepared that your gadget will lose warranty service from the seller. In almost all cases, obtaining superuser privileges entails a loss of warranty, which means that the device cannot be repaired free of charge if it breaks down or replaced if it is defective. Obtaining root rights is equivalent to breaking the seal that is on the body of some gadget or getting water inside the device without proper protection.

Experienced users can try to return to the factory firmware of a smartphone or tablet, but this requires certain skills. And many manufacturers (Samsung and some others) have learned to build in a so-called “counter” for obtaining root rights and carrying out other dangerous actions. What are the ways out of this situation? You can experiment on some cheap gadget from China that doesn’t even have a warranty, or wait until the warranty period for your main device expires. If you like risk, then you can root Android and hope that everything will be fine, and otherwise contact third-party service centers.

It is worth noting that some manufacturers sell smartphones with built-in root out of the box and with warranty service. These are mainly Chinese companies.

Risk of “scaling”
The process of getting root on Android is not the easiest for some devices. If the user does something not according to the instructions, then with a high probability he will turn his gadget into a brick that does not turn on, or will fall into a bootloop (constant reboot without logging in). "Scrapping" also means losing all data. Do not forget that you perform all actions to obtain root privileges at your own peril and risk.

You can avoid being “bricked” by simply studying the topic and methods of rooting your device. Follow the instructions exactly and do not deviate one step from them. Otherwise, your smartphone will “turn into a pumpkin.” It makes no sense to take it to the service center under warranty, since such cases are not covered by service. You will have to solve the problem in other ways or take the device to third-party repairmen. From all this comes another drawback - installing root is difficult and time-consuming.

If you have already installed root and are now just experimenting with applications and firmware, then do not forget to do full backups operating system (NanDroid) using . In this case, the device can be brought back to life, even if Android does not load.

Problems with updates
Full root rights in 99% of cases mean that you will no longer be able to receive official updates firmware. A superuser account requires changing system files in the /system directory, and this does not fit in with the installation of official OTA updates.

However, there are cases when the update can be installed together with root, but after installation is complete, the superuser account is deleted. You'll have to root the gadget again, but new firmware the old way may not work. In general, if with installed by root you received an update, and after that it installed and works normally, then consider yourself very lucky.

To receive updates, you can install a non-system root (systemless root) - a type of root rights that does not involve modifying the /system directory. Instead everything necessary files are located in the /su folder.

Security and Vulnerabilities
Gaining root privileges on Android means you're opening up a whole host of vulnerabilities in operating system. And these security holes are an order of magnitude more dangerous than those used by viruses for regular, non-rooted Android. Therefore, if you are not careful, it is quite easy to catch very dangerous malware with all that it implies. The result of this may be a leak of personal information, including account data and bank cards, as well as the introduction of viruses into the system.

But all this can be avoided if you use special utilities and do not install suspicious programs. For example, the program is specifically designed to distribute root privileges to other applications. If some program requests root rights, SuperSU will definitely notify the user about this, and he can refuse or agree.

In general, with great power comes great responsibility, so handle root carefully.

Why we removed Framaroot and other applications from Trashbox
Since we touched on the topic of security, we need to immediately clarify the situation with applications that can be used to get root in one click. In 2015, Trashbox was cleaned, during which we removed a number of programs to quickly obtain root rights on old and even some new ones Android versions. Among them were Framaroot, Baidu Root, CT Hack Root, Root Dashi, DingDong Root and several others. You can no longer download Framaroot for Android on Trashbox.

Why? The fact is that such programs use certain vulnerabilities in the operating system. Android system, especially in older versions, to gain superuser rights. At the same time, they often work incorrectly and can even lead to unforeseen consequences. There are many fake versions of these applications on the Internet, like Framaroot for Android, which not only gets root, but also installs several dangerous Trojans.

Another argument against all of these applications is that Google's Safe Browsing technology blocks access to Framaroot and other similar "rooters". Most The best way obtaining root rights is using a computer or by installing good third-party firmware. If you can avoid resorting to one-click rooters, then avoid them. One of the few safe programs for one-click rooting - .

If you avoid getting root on Android, then why? Tell us about it in the comments.