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

Why you don't need to get root rights

There are many advantages to rooting for Android, but almost as many disadvantages that can be frustrating. In this article, we tried to give the most significant disadvantages and dangers of obtaining root rights to 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 in the event of a breakdown or replaced if a defect is revealed. Obtaining root rights is equivalent to opening a seal on the body of a gadget or to water getting inside the device without proper protection.

Experienced users may try to return to factory firmware smartphone or tablet, but this requires certain skills. And many manufacturers (Samsung and some others) have learned to build in the 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 does not even have a warranty, or wait until the warranty period for your main device expires. If you like risk, then you can get root on Android and hope that everything will be in order, 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 "oskirpichivaniya"
Rooting Android is not the easiest process on 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 fell into a bootloop ( constant reboot without logging in). "Brushing" also means the loss of all data. Do not forget that all actions for obtaining root privileges, you do at your own peril and risk.

You can avoid "oskirpichivaniya" banal study of the topic and methods of rutting your device. Follow the instructions exactly and do not step away from it. Otherwise, your smartphone will "turn into a pumpkin." It is pointless to carry it to the SC under warranty, since such cases are not covered by the service. You will have to solve the problem in other ways or carry the device to third-party repairmen. From all this comes another drawback - it is difficult and time-consuming to install root.

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

Problems with updates
Full root rights in 99% of cases means that you will no longer be able to receive official firmware updates. The superuser account suggests a change system files in the / system directory, and this does not work in any way with the installation of official OTA updates.

However, there are cases when the update can be installed together with root, but upon completion of the installation, the superuser account is deleted. You will have to root the gadget again, but in new firmware the old way may not work. In general, if you received an update with root installed, and after that it was installed and works fine, 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 / system. Instead, everything required files are located in the / su folder.

Security and vulnerabilities
Getting root on Android means you open up a whole host of vulnerabilities in the operating system. And these "holes" in security by an order of magnitude more dangerous than that which is used by viruses for regular, non-rooted Android. Therefore, if you are not careful, it is quite easy to catch a very dangerous malware with all that it implies. The result of this may be a leak of personal information up to 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, a program is specially designed to give root privileges to other applications. If some program asks for root rights, then SuperSU will certainly notify the user about this, and he can refuse or agree.

In general, great opportunities bring a lot of responsibility, so be careful with root.

Why have we removed Framaroot and other apps from Treshbox
Since we touched on the topic of security, we need to immediately clarify the situation with applications that can be root in one click. In 2015, a cleaning was carried out on Treshbox, within the framework of which we removed a number of programs for quickly obtaining root rights on old and even some new versions of Android. Among them were Framaroot, Baidu Root, CT Hack Root, Root Dashi, DingDong Root and a few others. It is no longer possible to download Framaroot for Android on Treshbox.

Why? The fact is that such programs exploit certain vulnerabilities in the operating room. Android system especially in older versions to get 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 online, like Framaroot for Android, which not only gets root, but also installs several dangerous Trojans.

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

If you avoid getting root on Android, then why? Let us know in the comments.

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

Why does the Samsung device not work after getting Root rights?

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

• There was a failure on the device or computer at the time of obtaining Root rights, for example, the electricity suddenly turned off, USB cable was disconnected and other reasons.
• An attempt to download broken files.
• Attempting 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 non-working device.

If you see the following window:

You can safely take the phone to service center... Of course, you can try to do a factory reset and try to flash your smartphone through Odin, then the chances are close to zero.

It is important to remember that if Samsung gives 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 and reflash it through Odin. In all other cases, only Samsung service will help you.

Now let's figure out why your Android phone does not load beyond the logo (it does not turn on after the manufacturer's or robot's splash screen). Further in the text: first about the reasons and then decoding 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 splash screen and does not boot further, then this will be

• mistakes in software(it is possible to eliminate it yourself);
• problems with the "hardware" (only in the service center).

The reasons for the breakdown and why it turns on, but does not load

⭐️⭐️⭐️⭐️⭐️ If Android does not load on your phone or tablet when you turn it on, or your Android smartphone starts up, 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 the installation of an unsuitable or damaged assembly, incorrect firmware order, power failure, and other factors.
• Out of memory. The system may not start or due to insufficient memory. Removing unnecessary data can be a solution.
• Memory card incompatibility. If the smartphone turns on but does not boot completely, try removing the memory card and trying to restart the system.
• Hardware problems after being hit, dropped, spilled, or exposed to extreme temperatures.
• Damage to the power button or its cable, which "closes" the phone and goes into cyclic reboot loading up to the logo and then in a circle. We come across this periodically and can only be diagnosed at a service center.

Before trying to fix a problem with Android, you need to understand why the system does not boot.

Restoration of performance

If the phone shows that the charge is on, then the causes of the problem should be looked for in work Launcher Android... If the device vibrates or its screen flickers, then 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 here. It is necessary to reset the system after Recovery Mode or reflash the device. Let's see what to do:

1. While holding the power button and the volume down key (there may be other combinations, look for your model), go to Recovery Mode. If the phone, then the problems are at a deeper level, so you need to contact the 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 did not help, perform a flashing. To do this, drop the file with the appropriate firmware into the root of the memory card, insert the drive into the phone and select “Install zip from sdcard” in Recovery Mode.

Increase

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

Extracting information from non-working Android

Even if the problem can be solved without financial investments, by a simple flashing, users have an important question - how to save the data that is stored in the phone's memory. There are no problems with the memory card: you just need to pull it out of the device. But how to rescue data from internal storage? For example, pull out contacts.

Increase

If you did backup system, or at least, it will be very easy to get contacts. You just need to go to the "Contacts" application on the Google website to see full list synchronized contacts. If you want to transfer them to another device, then it will be enough to add a Google account to it.

The phone does not turn on

Samsung after getting Root

More and more often owners mobile phones Samsung trying to get Root rights is facing startup problem. This applies not only to phones, but also to tablets from a Korean manufacturer, in such cases the device stops starting. We will tell you what to do in such cases in this article.

The reason for the inappropriate behavior of the device may be an inappropriate program that was used in the course of obtaining Root-rights. Perhaps the problem was in the incompatibility of the firmware. In addition, a failed Root may be due to a sudden power outage or insufficient battery power. By the way, the battery must be charged at least 70%, provided that it is normal and not too worn out. This could be due to a damaged USB cable or a malfunctioning computer.

During the course of work, a software failure may have occurred on the computer or device. It can also be related to broken Root files, "underloaded" or incompletely downloaded files. The same files may be incompatible, therefore, when receiving super rights, the phone does not perceive them properly, which is why it does not turn on. Another reason is incorrect installation sequence and failure to follow instructions.

How to fix the situation?

To remedy the situation and start the phone, you can use these methods. If the screen mobile device displays “ eternal loading"During which the screen constantly displays the boot image, you need to do the following:

• translate device Samsung into special mode Recovery and execute full reset data - go to the "wipe data / factory reset" options. Reboot your smartphone and wait for the trigger. If that doesn't help, go to the next step;
• find the firmware for your device, download it and install it using the service Odin ... Reboot the device and wait for the result. If it doesn't work, go to the first point and reset the data.

If the phone does not turn on at all, but when connected to a computer, a window appears as in the photo below, there are still chances to save the phone on your own. To do this, you must use the same methods as in the previous case. If the phone does not respond at all, and there are no signs when connected to a PC, the only way out is to contact a specialized service center. As a reminder, after receiving Root, the device warranty is void.

-	-
-	-

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

Destroying myths

Let's talk about what it is all the same to "turn a smartphone into a brick" and what other pitfalls may await the user on the way to change the system and install custom firmware. What glitches can you catch and can you kill a smartphone by flashing it incorrectly? Will you lose your warranty forever or can your smartphone be returned to its previous state? Can custom firmware fail the 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 a flashing. The main problem faced by anyone who wants to reflash a smartphone 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 is enough to understand how the process of flashing a smartphone works and what system components are used in this case. To be able to install third-party firmware on a smartphone, you need to unlock the bootloader (not in all cases), get root and install a custom recovery console (ClockworkMod or TWRP) that can install firmware with any digital signature.

Recovery Console is stored in separate section internal NAND memory and has nothing to do 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 load it, but the recovery console will remain in place, and all that needs to be done is to reboot into recovery and reinstall the firmware.

In addition, any custom recovery console contains a backup / restore function that allows you to back up 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 be asking: what happens if a failure occurs during the installation of the Recovery Console itself? Nothing, in this case, the opposite situation will turn out when itself operating system 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 will be killed (although this is rather difficult to do), but even in this case, the primary bootloader will always remain in place, flashed into the permanent memory of the smartphone.

Conclusion: kill the smartphone by installing third party firmware via a custom recovery console is not possible. Either recovery or the primary bootloader will always remain in place.

Myth 2. Custom firmware is unreliable

Firmware firmware strife. On the vastness of the world wide web you can find great amount Android assemblies for every taste and color, and most of them are really slag, which can lead to instabilities in the operation of the smartphone and the 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 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 the developer with the nickname Quarx. Their difference lies in the fact that the CyanogenMod team is responsible for the support and proper performance of the former, while the latter is personally responsible for Quarx. Official firmware versions are usually fully functional, but the correctness of the second depends on a third-party developer.

And the third thing. There are stable and development versions of the firmware. Stable versions CyanogenMod are indexed 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 "normal" firmware on your smartphone, the risk of encountering bugs is minimal. Everything else is for the experimenters.

Myth 3. Software that requires root privileges is capable of corrupting a smartphone

In theory, a rooted app can do whatever it wants with a smartphone's firmware, including erasing it completely. Therefore, you need to be extremely careful with such software. The software that we are talking about on the pages of the magazine is completely safe and tested in our own skin. In addition, for the entire time of using smartphones on Android (and this is starting from version 1.5) I never did not come across a situation where rooted software would kill a smartphone.

Software distributed through Google play, usually fully corresponds to the declared characteristics, and if it led to a brick or left a backdoor in the bowels 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

It is not root permissions that make a smartphone vulnerable to viruses, but bugs used to obtain them. Rooting tools and viruses can exploit the same Android vulnerabilities to gain root privileges, so the mere fact of having root on a device doesn't change anything. A well-written virus will not ask for rights in a standard way betraying his presence, he will instead use the same vulnerability to get them stealthily.

Moreover, having root, you get the opportunity to install a fresh Android version(in the form of custom firmware), in which these bugs have already been fixed. Also, do not forget that most custom firmwares allow you to disable root or create whitelisting applications that can use these rights.

Myth 5. A rooted smartphone can fail.

The software designed to get root does four simple things: it launches an exploit that allows you to get root privileges on the system, mounts the / system partition in write mode, copies the su binary to the / system / xbin directory, which is required to get root privileges in the future, and installs a SuperSU or SuperUser application that will take control every time an application asks for root privileges with 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 error and the smartphone will reboot, after which it will continue to work normally.

Myth 6. Getting root and installing custom firmware will void my warranty

The warranty is lost not from the very fact of getting root, but because of its discovery by the service center. Most devices can be unrooted using the Universal Unroot app or by reinstalling the stock firmware using official app 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 increased level of Android security responding to any firmware modifications and installation of third-party kernels and firmware. In the event that the user performs these actions, the system sets up a trigger that confirms the fact of the modification. The trigger is implemented in hardware (eFuse chip), so you won't be able to reset it 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 if the smartphone has been rooted or flashed.

If we talk about custom firmware, everything is more complicated here. Usually, a flashing operation requires unlocking the bootloader, and this can be done either using special exploits or using the web service of the smartphone manufacturer. 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 a newly locked bootloader will most likely receive the Re-locked status, and not Locked, as it was originally (this happens on HTC smartphones, for example). The only exceptions 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 pick on anything.

INFO

On 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 the Knox system from interfering with root applications, it can be disabled 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 ruin a smartphone for purely technical reasons. The only exception is trying to hack the bootloader to unblock it. In this case, the eFuse chip (if there is one in the smartphone) 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 they implement a special web service that allows you to painlessly unlock the bootloader with the loss of the smartphone warranty. which saves users from having to risk breaking the bootloader.

Problems that may arise when 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 loading

An unsuccessful flashing can be caused by several factors: the battery has run out and the firmware is only half filled, the firmware turned out to be faulty or intended for another smartphone model. In the end, there was simply not enough space on the smartphone, which can happen when trying to install a fresh version of Android on a smartphone three or four years ago.

Outwardly, all these problems usually manifest themselves either in endless smartphone resets to the manufacturer's initial logo, or in the so-called boot loop, when the boot animation spins on the screen for more than five to ten minutes. Problems with the screen (multicolored ripples) and a non-working touchscreen are also possible, 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 with the volume down button held down (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 backup ( Backup and restore -> Restore). Everything is easy and simple.

Scenario two: firmware works, but recovery is not available

This can happen after an unsuccessful installation or update of the Recovery Console. The problem is that after restarting the smartphone and turning it on with the volume down button pressed, a black screen appears, after which the smartphone is either reset 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 determine the smartphone model themselves, download and flash the required recovery without requiring a reboot. If you cannot restore the console with their help, it is enough to find instructions on install recovery 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 a smartphone, or use a tool from the manufacturer to install the stock firmware. We'll take a closer look at the second method 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, recover and unlock the bootloader (in Nexus devices). Fastboot support is available in many smartphones and tablets, but some manufacturers are blocking its use. So you have to consult the Internet about its availability.

You need drivers and Android SDK to access fastboot. 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 held down (both) and connect it with a USB cable to the PC. Next, you need to find the recovery image in the .img format for your device and run the command:

$ fastboot flash recovery image.img

Or even force the smartphone to download 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 a clean drain, no matter what state it is in. These instructions can be used both for splitting up the smartphone and for removing traces of rooting and flashing. Unfortunately, I cannot tell you about all the possible models, so I will focus on the four most popular flagships: Nexus 5 (I call this one the control one), Galaxy S5, LG G2 and Sony Xperia Z2.

Nexus 5 and other Google phones

Returning Nexus devices to their original state is easier than any other smartphone or tablet. In fact, it is so simple that there is nothing to even talk about. In fact, all you need to do is install the ADB / fastboot drivers (in Linux, even they are not needed), download the archive with the firmware and run the script. Step by step, the whole operation looks like this:

1. from here.
2. Download and install the 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 held down (both) and connect using a USB cable.
5. Unpack the archive with the firmware and run the script flash-all.bat (Windows) or flash-all.sh (Linux) and wait for the operation to end.
6. We launch the command line, go to the directory with the Android SDK, then platfrom-tools and execute the fastboot oem lock command to lock the bootloader.

For those wondering what the script does, here's 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 recovery recovery.img fastboot flash boot boot.img fastboot erase cache fastboot flash cache cache.img

Galaxy S5

With Galaxy smartphone The S5 is a little more complicated, but generally quite simple. This time, you will need the Samsung Odin application, with the help of which the smartphone will be flashed. Sequencing:

1. Download and install latest version Samsung USB drivers from here.
2. Download and install the latest version of Odin from here.
3. Go to samfirmware.com, enter the model SM-G900F in the search, find the firmware marked Russia, download and unpack it.
4. Turn off the smartphone and turn it on with the volume down and Home buttons held down, 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 tar.md5 extension inside the directory with the unpacked firmware.
8. We press the Start button in Odin and wait for the firmware process to end.

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

LG G2

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

1. Download and install ADB Driver Installer from here.
2. Downloading official firmware(Europe Open 32G or Europe Open) from here.
3. Download and install the LG Mobile Support Tool and FlashTool (goo.gl/NE26IQ).
4. Turn off the smartphone, hold down the volume up button and plug in 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. Press 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 are waiting for the end of the firmware, and then turn off and turn on the smartphone.

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

Sony Xperia Z2

Now how to return to the factory state Sony smartphone Xperia Z2. As in the previous two cases, this will require a stock firmware and official utility for firmware. You launch the utility on your PC, connect your smartphone with 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. We reset the 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 with the volume down and Home keys held down.
6. We connect the smartphone to the PC using a USB cable and launch the Flash Tool.
7. Press the button with the lightning bolt 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, a jailbroken bootloader will prevent over-the-air updates.

In 90% of cases, unlocking the bootloader will result in the deletion of all data from the smartphone, including the memory card.

conclusions

Flashing a smartphone, and even more so getting root access, is not at all such scary and dangerous operations as they might 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, it will not be possible to turn the smartphone over. Yes, in some cases you will have to tinker in order to put everything back in place, but which is better - to use a locked smartphone, which does not allow you to do even half of the things that it is capable of, or to gain full control over the device? Finally, reinstalling windows on the PC does not scare anyone.