How to restore your phone after unsuccessful Samsung firmware. Recovering data on Android after a factory reset. Life after hard reset. Other rollback methods

Scrapping is a complete or partial loss of functionality of an Android device. Not a single user who independently flashes a gadget is immune from turning smart phone into a meaningless “brick”, so the question of how to perform restoration at home arises quite often on various forums.

Correcting the consequences of unsuccessful firmware

If the smartphone constantly resets when loading or the logo appears on the screen for 5-10 minutes, but the system does not start, then technically it is not yet a “brick”. Such a device can be quickly restored via Recovery menu, reflashing it again.

Turn off your phone.
Hold down the Volume Down key and press the Power button to get to the Recovery menu.

You have two options - restore the backup if you made one (this is one of the main requirements for flashing), or re-flash the phone. To start a backup, go to the " Backup and Restore" and start recovery previous state systems.

To flash the firmware, select the “Install zip from sdcard” section and specify required file operating system. This method corrects errors that occur when the firmware is incomplete: for example, when the phone turns off while writing files.

The opposite situation is that the firmware starts, but you cannot get into Recovery. This problem can be resolved even easier: you can use applications to return the recovery console TWRP Manager, ROM Installer or ROM Manager. After installation, these applications determine the smartphone model and independently download the required recovery.

If the listed applications did not cope with the task, find instructions for installing the recovery console for your model mobile device.

Restoring the "brick"

Let's consider more difficult option, when the smartphone actually turns into a “brick”, neither the system nor the Recovery menu starts. It is also possible to restore it at home: for this you need to use official firmware from the manufacturer. Let's look at the recovery procedure using a Samsung phone as an example:

Your “brick” will again become a working device, returning to its original state.

Firmware using Flashtool

This method is suitable for Sony phones, but it can be used on mobile devices from other manufacturers. You will need:

The “brick” itself that you want to restore.
Official firmware in FTF format.
Installed on a computer Flashtool program with firmware drivers.

Before starting work, it is advisable to disable your antivirus and firewall to avoid incorrect operation Flashtool utilities. In addition, when starting to restore the brick, make sure that the phone is fully charged.

The recovery program will prepare the Android firmware and offer to connect the “brick” to the computer. Press the Volume Down key on your device and connect your phone to your computer.

The Flashtool program must identify the “brick” connected to the computer and run the firmware on it. If the recovery is successful, then at the end of the log you will see the message “Flashing finished”. After this, you can disconnect the phone from the computer and turn it on - Android should start without errors.

(root access) or, the device stops functioning. This manifests itself in the inability to log into the mobile device and even load the environment Recovery. This state of a phone or tablet is popularly called “brick”.

No matter how serious the problem of “scrapping” may seem, in most cases you can revive the gadget at home. Let's look at how to restore Android if it has turned into a brick.

Methods for resuscitating Android when “bricked”

There are three effective methods Android recovery if they lose their ability to work:

using the standard recovery environment Recovery;
through a computer and special software.

Which method to use directly depends on the state of the system on the device.

Restoring a brick using standard Recovery

If you try to log in work area devices are monitored constant reboots or the phone freezes on the system logo, but the Recovery environment is working, which means you are in luck, since you can restore the Android firmware through it. To do this you need:

After rebooting, the factory settings should appear on the smartphone. If it doesn’t help fix the problem, we try to reanimate Android after unsuccessful firmware using a previously created system backup or a file with firmware downloaded from the Internet.

When deciding to gain root access or perform other potentially dangerous actions, it is recommended to create a full device backup. In this case, even after “bricking” you will be able to return all user data and old firmware.

To restore Android from a previously created backup, you need to do the following:

If you did not take care of creating a return point in advance, then you can return Android to your tablet or smartphone using the downloaded firmware. IN in this case We revive the gadget as follows:

Once the Android “brick” has been restored, the downloaded file can be deleted.

Using custom recovery

If the “bricking” led to the crash of not only the operating system, but also the standard Recovery, then you can restore the system using a custom recovery environment - the program CWM Recovery.

Before restoring a brick on Android, you need to install a recovery mod on the problematic device:

Will begin CWM installation Recovery, at the end of which you can disconnect the smartphone from the computer and proceed directly to resuscitation:

After completing these steps and rebooting, the phone (tablet) should work.

Reanimation of a “brick” via a PC and special software

When considering how to restore Android after being bricked, it is worth noting specialized software developed individually for each manufacturer mobile devices. Thus, the FlashTool recovery program is used for gadgets from Sony and some other brands, and

Many users are eagerly waiting for manufacturers to release a new firmware update for their Android smartphone. As a rule, they fix bugs previous versions OS, new features are added and the overall operation is optimized. But what should you do if, after the update, your phone starts working worse than it did initially? Let's take a closer look at why and how to restore your phone after unsuccessful Android firmware.

Self-firmware of an Android device is always a risky undertaking, the consequences of which are borne by the user himself. Unless, of course, we are talking about installing a standard official update over the air or using proprietary program on the computer. In this case, responsibility for the consequences of the update lies with the developer, so you can safely contact the warranty service center. But before you panic and everyone possible ways try to restore original firmware, you need to understand whether a failure actually occurred. There are several main reasons that can lead to failure when flashing:

Emergency interruption (the phone was disconnected from the computer, the smartphone battery was low, etc.)
Inappropriate OS version.
Incorrect settings, user errors.

Any of the above problems can cause incorrect operation of the mobile device, constant system failures etc. In the event that the phone does not turn on or begins to work worse than before installing the update, you need to proceed active actions on restoration.

How to roll back firmware

At failed update The question arises, how to return the old OS? Depending on whether you used the official or custom version of the firmware, the recovery options will be different. Let's consider both cases in more detail.

Crash caused by installing official firmware from the developer

This does not happen often, but in some situations the phone may not work correctly even when an official update is installed. In this case, it is quite simple to roll back and restore the factory version of the mobile phone operating system. To do this, the user will need a computer with installed drivers to your mobile device and special program. Depending on the manufacturer of your smartphone or tablet, the required utility must be downloaded from the developer’s official website. Further actions for installing native firmware can be written in two points:

Connect your mobile device to desktop computer or laptop via USB cable.
Run the program, find the recovery partition in it and start rolling back the changes made.

Website with Samsung program Kies

After this, the program will automatically search for and install the required OS version and return the mobile phone to its original state.

Program interface on a computer

Crash caused by installing custom (custom) firmware

In this case, updating again from Recovery mode will help. In order to enter recovery mode, you need to turn off your mobile device and simultaneously hold down the key combination. In most cases, these are the buttons: power + volume down.
The Recovery menu is controlled by the same keys: volume and power. In the case when you made a backup of the system before flashing, then just select the “Backup” item and restore" If no backup was made, the recovery procedure will take a little longer. You need to do the following:

Reset all settings by selecting “wipe data/factory reset”.
Format the cache partition by clicking on “ wipe cache partition".
Try to reinstall the firmware by selecting “install zip from sdcard” and clicking on the file with a pre-created archive on the memory card.

After this, the phone should work normally. You can also try downloading and installing another version of the OS in a similar way. For more information on how to roll back newly installed firmware, see the training video below.

How to return factory firmware?

If you want to return the factory version of the OS by correcting the accumulated system errors, then you can do this directly from the main settings menu of your smartphone. To do this you will need:

Turn on your mobile device, go to the main settings (via the application menu or by clicking on the gear icon in the right top corner when the curtain is lowered).
Find the “restore and reset” tab, then click “Hard reset” and agree to the necessary conditions.

After successfully completing this operation, your phone or tablet will return to its factory OS settings. We recommend that before resetting the settings, you back up important data or save it to a separate media, as it will be deleted from memory.
The training video below explains how to perform a factory reset. mobile gadget, running on Android OS bases, up to factory ones.

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 is to “turn a smartphone into a brick” and what other underwater rocks can wait for 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 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), 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 installation modified version 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 that allows you to backup copy 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 opposite situation will turn out when 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 are killed (although this is quite difficult to do), but even in this case the primary bootloader, flashed in permanent memory smartphone.

Conclusion: kill your smartphone by installing third party firmware through a custom recovery console, impossible. 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 can be found great amount 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, this is 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 Nexus smartphone 4, but does not have one for 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 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, 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 use the same Android vulnerabilities to obtain root rights, so the fact itself 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 Android version(in the form of custom firmware), in which these bugs have already been 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 sets SuperSU app or SuperUser, which will take control every time 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 removed from root rights using Universal applications Unroot or reinstall stock firmware by 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 provides increased 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 reset it to starting position will not work. 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. 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

On Linux, ADB and Fastboot can be installed separately from 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 next command from the terminal: su pm disable com.sec.knox.seandroid.

conclusions

Getting root and flashing a smartphone are absolutely safe operations that cannot completely brick the smartphone. 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 unsuccessful installation or recovery console updates. 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 tell you about everyone possible models, so I’ll focus on the four most popular flagships: Nexus 5 (I call this copy 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:

from here.
Download and install Android SDK.
Download the archive with the firmware for the desired device from the Google website.
Turn off the device, turn it on with the volume buttons pressed (both) and connect using a USB cable.
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.
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 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 a Samsung one Odin app, with the help of which the smartphone’s firmware will be flashed. Sequencing:

Download and install latest version Samsung USB drivers from here.
Download and install the latest version of Odin from here.
Go to the website samfirmware.com, enter the SM-G900F model in the search, find the firmware marked Russia, download and unpack.
Turn off the smartphone and turn it on with the Volume Down and Home buttons pressed, wait five seconds until a warning message appears.
Press the volume up button to put the smartphone into Odin mode.
We connect the smartphone using a USB cable.
Launch Odin, press the PDA button and select the file with the extension tar.md5 inside the directory with the unpacked firmware.
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 factory condition will also not cause special 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 the G2 to factory firmware:

Download and install ADB Driver Installer from here.
Download the official firmware (Europe Open 32G or Europe Open) from here.
Download and install LG Mobile Support Tool, as well as FlashTool (goo.gl/NE26IQ).
Turn off the smartphone, hold down the volume up button and insert the USB cable.
Expand the FlashTool archive and run the UpTestEX.exe file.
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.
Click the CSE Flash button at the bottom of the screen.
In the window that opens, click Start.
In the next window, select the country and language and click Ok.
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 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:

Download and install ADB Driver Installer from here.
Reset your smartphone to factory settings.
Download and install Flash Tool from the official Sony website and latest firmware from here.
Copy the firmware file to the C:/Flashtool/Firmwares directory.
Turn off the smartphone and turn it on while holding down the Volume Down and Home keys.
We connect the smartphone to the PC using a USB cable and launch the Flash Tool.
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’s better than using a locked smartphone that doesn’t allow you to do even half of the things it’s capable of, or get full control above the device? In the end, reinstalling Windows on PC it doesn't scare anyone.

Flashing a phone or tablet yourself is a risky endeavor, especially if the procedure is performed by the user for the first time. As a result of inept actions or software errors The device may stop turning on, and then you have to look for ways to restore it.

Why could there be a fight?

There are several reasons why the firmware fails:

The update crashed (the phone was disconnected from the computer, the battery was low).
Incorrect firmware version.
User errors when flashing.

Problems after the update can be resolved.

In the worst case, the phone will turn into a “brick”, but even from this state Android device is being restored.

Crash after official update

If for Android updates If you used official tools, then you can restore your phone after unsuccessful firmware using a utility from the manufacturer. Download what you need software on the company’s website, in the “Support” or “Service” section. In addition, you will need mobile device drivers, which must be installed on your computer.

Connect your phone to your computer.
Find the partition that allows you to perform a restore and roll back the changes you made.

Each manufacturer has own program updates, so look carefully at all items and menus. If you have an LG phone, then in the LG utility Mobile Support Tool in the section " Additional features» you will see the item “Recovery after an update error”.

After running this tool, the utility will download from the Internet suitable version Android and will return the phone or tablet to a working state.

Problems after custom firmware

If problems in Android work arose after installation via mode Recovery custom firmware, then you can restore the phone repeated update. If you installed the firmware yourself, you should already know how to open Recovery mode. It is usually launched by simultaneously pressing the power button and the volume key.

The Recovery menu is navigated using the volume keys and the power button. If you did before the unsuccessful firmware Android backup, then use the “Backup and restore” item to restore the phone to a previously saved state. If there is no backup:

Once the installation is complete, the phone should start working correctly. You can install another firmware version if the first one was unsuccessful - just replace the archive on the SD card and follow the above recommendations.

Firmware reset

If the phone works after re-flashing, it is recommended to reset Android settings to factory condition. This procedure will correct any errors that may arise and return the original version of the operating system.