Restoring brick android samsung. Recovering data on Android after a factory reset


Loss of Android performance on a smartphone or tablet, or so-called bricking, occurs according to the most various reasons. Most often, this is facilitated by incorrect firmware, which can turn an advanced phone into a useless brick. The question of whether it is possible to restore a gadget yourself interests many users.

How to eliminate the consequences of unsuccessful firmware

Data-lazy-type="image" data-src="http://androidkak.ru/wp-content/uploads/2016/09/kirpich.png" alt="kirpich" width="200" height="119" srcset="" data-srcset="http://androidkak.ru/wp-content/uploads/2016/09/kirpich..png 300w" sizes="(max-width: 200px) 100vw, 200px"> !}
If after the logo appears when you turn it on, the system does not start for several minutes or the boot constantly resets, then this is not a “brick” and not all is lost. To launch, you need to log in from your smartphone to Recovery menu and make a new flashing.

To do this you need to follow these steps:

If the gadget is turned on, you need to turn it off. Press and hold the volume down key and the power key. The Recovery menu opens, which offers 2 methods:

  1. restore the backup (this is the main requirement for the firmware; if the phone was flashed, then the backup was also restored). The backup starts running in the “Backupand Restore” section when you select the previous system location.
  2. flashing - carried out by selecting the “Install zip fromsdcard” section, in which you need to specify the required operating system component. This option fixes errors incomplete recovery, which may occur, for example, due to the phone being turned off while the files are being written.

Another situation may arise: when starting the firmware, you cannot enter Recovery. This can be easily resolved by returning the console to fix the system. special applications TWRP Manager ROM Manager or Installer. These applications were created to determine the gadget model and independently download all necessary components to launch a suitable Recovery.

If none of the above-mentioned programs corrected the error, you can find instructions for downloading the recovery console for a specific brand of smartphone or tablet.

Read also: How to reflash Windows Phone on Android

How to restore a real Android brick

We looked at what can be done in case of partial loss of smartphone functionality. Now it’s time to talk about how to restore a completely “dead” Android when nothing starts. It is not at all necessary to immediately go to a workshop; you can try to start the system at home using simple steps.

Let's look at what to do step by step:

  1. Install latest version drivers for USB from Samsung to your computer.
  2. Download and install the latest version of the Odin application.
  3. Download licensed firmware that is suitable for specific model and countries.
  4. Turn off the brick, then press the volume down key and the Home key. After a few seconds, a warning will appear on the screen.
  5. By pressing the button on the phone that increases the sound, switch it to Odin mode.
  6. Connect the gadget to the computer.
  7. Launch Odin, press PDA, in it indicate the file tar.md5 in the directory with the firmware.
  8. Press the “Start” key, start the recovery, wait until the end of the operation.
  9. Hurray, the “brick” is working!

How to reflash a smartphone with Flashtool

One hundred percent this option applicable to Sony phones However, devices from other brands can be restored in the same way.

What do you need:

  • “brick” Android;
  • licensed firmware in FTF format;
  • Flashtool program installed on the computer, firmware drivers for it;
  • disabled antivirus, firewall, which can react to Flashtool as a viral component;
  • It is enough to charge the phone well so that it does not turn off during recovery.

Step-by-step recovery instructions via Flashtool

data-lazy-type="image" data-src="http://androidkak.ru/wp-content/uploads/2016/09/Flashtool.png" alt="flashtool" width="200" height="205" srcset="" data-srcset="http://androidkak.ru/wp-content/uploads/2016/09/Flashtool..png 293w" sizes="(max-width: 200px) 100vw, 200px"> !}

To begin with, you can immediately answer the question most frequently asked question which torments!

How much does it cost to repair a wet phone?

We will answer immediately. From 800 rubles! The master will determine more precisely. But as a rule, repairs are much cheaper than buying a new phone.
And one more subtle question

Does it make sense to repair a drowned smartphone?

Of course yes! As we said - it's much cheaper.
Think for yourself...
Cost of a new mid-range phone
10-15 thousand rubles

Repair of drowned man price

average 800-2000 rubles
Does it make sense to buy when your refurbished mobile phone will work like a new one? In this case, you will not need to restore contacts!

So about the cellular “diver-diver”...

This article prompted me to write a large number of calls with the questions “My phone fell into the water, what should I do, how much will it cost to repair a sunken phone?”, or “My phone got wet, it worked right away, then stopped turning on,” or “We washed my phone in washing machine, the phone does not turn on, can it be repaired?" etc.

First, I’ll tell you what to do first if liquid gets into your phone:

  1. The first step is to remove the battery from the phone and do not insert it for at least a day. Oddly enough, it’s not just water that kills the elements inside the phone, but electricity, which oxidizes the elements inside and disables the radioelements and the device board.
  2. Second thing the phone needs to dry inside. But based on practice, I will tell you that liquid gets inside the phone very quickly, but it can dry for a very long time, not just one day. And even if all the liquid dries inside, there are still salts dissolved in the water, which corrode the radio elements when the phone is operating, since salts are conductors of electric current.
  3. Therefore, I recommend the third step in saving your phone after moisture gets into it: contactservice center repairing phones, and it’s better not to hesitate, the sooner you do it, the cheaper the repair will cost, and perhaps only preventive maintenance of phone elements will be enough.

But it's not always so easy. Let's say they dropped it in water iPhone, but the battery in it is not so easy to get out without disassembling the device. In this case, if you cannot contact the service center as soon as possible, I advise put iPhone in rice(just don’t laugh, but it really helps! the most ordinary food rice, at first I didn’t believe it, but after people brought in sunken iPhones dried in rice, during repairs it was really clear that the effects of moisture were minimal). The photo shows the board of a recessed iPhone 4, which was placed in rice and then brought to the service center. The board was perfectly clean, the only thing oxidized was the connector touch screen(marked with a red circle). The red diamond shows an indicator that liquid has entered the iPhone.

And now I want to answer the most common question: “How much will it cost to repair a recessed phone?” If the phone does not turn on after liquid gets inside, then I will answer honestly: “I don’t know.” In this case, it is impossible to do without diagnosing the malfunction, since water could damage any element, and therefore the phone must be disassembled and tested to identify the malfunction.

The most harmless case is when the phone is dropped into water, it continues to work, but there are water stains on the screen. It doesn’t seem to be a big deal, but it looks unpleasant, especially against a light background. The only way out of this situation is to replace the display on your phone. Even after the water has dried, traces of it still remain, and it is impossible to remove them from the old screen, since the display contains several layers of film that diffuse the backlight, and it is unrealistic to disassemble them without damaging them.

The worst case is when water that gets into the phone oxidizes the radio elements and disables them. The degree of oxidation depends on the time the phone was in the water, on the amount of liquid that got inside, on whether the battery was immediately pulled out of the submerged phone or after some time. If you do not immediately take action after liquid gets into your phone, then it will end up with approximately the same thing as the phone in the photo. The elements oxidize, the salts corrode the phone parts, and the recessed phone becomes unusable for repair.

The last picture shows the board of a phone that fell into the water and the battery was not immediately removed from it. The phone worked for a while, then turned off and never came back on. Yes, it won’t turn on anymore, the phone cannot be repaired, since many of the radio elements inside have simply rotted. In this case, it is necessary to completely change the circuit board on the phone, which is usually comparable in cost to the price of a used phone of the same model.

Therefore, to avoid this and extend the life of your phone after liquid gets into it, immediately take the measures that I wrote about at the beginning of the article.

What happens during electrochemical corrosion?

A little theory...
Metal conductors in the phone lose some of their atoms (they pass into the electrolytic solution in the form of ions), electrons replacing the lost atoms charge the metal with a negative charge, while the electrolyte (an electrolyte is a liquid that conducts electric current) has a positive charge. A galvanic couple is formed: the metal is destroyed, gradually all its particles become part of the solution. Accordingly, the solution becomes conductive, which subsequently short-circuits the conductors covered by it.
For the process of electrochemical corrosion, it is not at all necessary to immerse metal conductors in an electrolyte - a thin electrolytic film on its surface is sufficient. Simply put, it is not necessary to drop your phone into water; a damp environment is enough.
In a nutshell: nothing good will happen. The following will occur: either a short circuit of the conductors, or a break in the conductor...

If liquid gets into your phone...

Ingress of liquid and mechanical damage(falls, impacts) cause the most severe damage to your cell phone. Therefore, to restore the device in this case, repairs are required. highest category difficulties. We often encounter a situation where a client brings a wet device with the words: “Please clean the phone, it’s a little wet and now it won’t turn on.” However, not many people realize that any cell phone (even the oldest one, released several years ago) is complex electronic device, the operation of which is controlled by digital and analog processors, RAM and Flash memory chips, and numerous peripheral devices (display controllers, keyboards, audio controllers, etc.). Let's not forget that the most important function of a cell phone is to provide stable and high-quality communication; this task is performed by a separate functional module, or radio unit, which consists of special processor(or several processors) for processing high-frequency signals and numerous components of the transceiver path. Failure of any of the listed modules may result in serious violations in the operation of the phone, or its complete failure. In case of any, even minor, ingress of liquid, when only a few drops have leaked inside, on the components motherboard Within a few minutes, electrochemical corrosion occurs rapidly, which stops only when completely discharged battery(hereinafter referred to as the battery), or when the liquid evaporates.

What to do if liquid does get into the device?

1) Immediately remove and do not reinsert the battery! This will avoid the most serious damage. Remember, while the battery is removed, electrochemical corrosion processes do not occur, and damage to the phone’s system board will stop. At the same time, you should not try to charge the device if it does not turn on - this will significantly aggravate the current situation.
2) Promptly contact a qualified service center (hereinafter referred to as “SC”) for diagnostics and repairs. During this time, the battery must be removed.

If you are sure that very little liquid has entered, or there is no way to contact a service center, try to carefully dry the device. For this purpose, under no circumstances should you use heating devices (hair dryer, heater, etc.), as well as a microwave oven! Dry the device, avoiding heating above the temperatures specified in the instructions and observing the described operating conditions; dry the battery only at room temperature. It is impossible to dry the device well in 5 minutes, or even in 5 hours. Required longer time, no need to rush. After completing the operation, try to turn on the phone, check charging, communication, and all other functions. Everything is working? This means that you are lucky, carefully monitor the behavior of the device for several days, and in case of any problems, immediately contact the service center. If the device does not turn on, or there are any malfunctions, contact the service center immediately.

One of the misconceptions, which undoubtedly reflects national ingenuity, is the assertion that a wet device should be washed with vodka or alcohol. This is absurd. From vodka that gets inside the device, the alcohol will evaporate much faster than water, and the situation will only get worse. Washing with any alcohol-containing liquid, including “pure” alcohol, will not remove or stop the corrosion that has begun.

Let's look at the nature of damage caused by liquid ingress using the example of a device that came to us for repair. Nokia N70.

On photos 1 Oxides and corrosion of the motherboard components are clearly visible in the area of ​​the power controller chip (in the center of the photo). Not only the external elements, which are relatively easily accessible for restoration or replacement, are damaged by water, but also the soldering, which is located directly under the microcircuit - liquid flows inside, and in this case, replacement of the soldering of the microcircuit is required (in case of extensive liquid ingress - several microcircuits), or replacement the microcircuit itself. So the phrase "clean my phone" is absolutely unacceptable for such an example, since corrosion, in addition to external components, has gotten under the microcircuit. In addition to damage to components and microcircuits, numerous miniature board conductors (the so-called “tracks”) rot; in the photograph they are visible as light green broken lines connecting the elements. The diameter of these conductors varies, but generally they are approximately equal to the thickness of a human hair; the process of searching for breaks and rotten connections is very difficult, and in some cases impossible.

photo 2

On Photos 2 Oxides and corrosion of the motherboard components are clearly visible in the area of ​​the power controller chip (in the center of the photo). Not only the external elements, which are relatively easily accessible for restoration or replacement, are damaged by water, but also the soldering, which is located directly under the microcircuit - liquid flows inside, and in this case, replacement of the soldering of the microcircuit is required (in case of extensive liquid ingress - several microcircuits), or replacement the microcircuit itself. Thus, the phrase “clean my phone” is absolutely not acceptable for such an example, since corrosion, in addition to external components, has gotten under the microcircuit. In addition to damage to components and microcircuits, numerous miniature board conductors (the so-called “tracks”) rot; in the photograph they are visible as light green broken lines connecting the elements. The diameter of these conductors varies, but generally they are approximately equal to the thickness of a human hair; the process of searching for breaks and rotten connections is very difficult, and in some cases impossible.

photo 3

This Photo 3 illustrates damage in the area of ​​the battery connector (lower left corner) and camera (upper right corner), as well as nearby components.
Severe corrosion leads to damage not only external elements, microcircuits and conductors. The motherboard of any cell phone has a complex multilayer structure; conductors from the outer layers go inside the motherboard to connect electrical circuits in different parts of the board. It is extremely difficult to identify and eliminate on-board breaks caused by rotting conductors, and often completely impossible.
Corrosion leads to oxidation of the solder; the products of this reaction can cause short circuits in various electrical circuits. This is dangerous due to the failure of electronic components, including those not subject to corrosion, as well as the appearance of the so-called “leakage” - a significant increase in energy consumption (sometimes even when turned off), which leads to a rapid discharge of the battery, reducing the operating time of the device.

This photograph also shows numerous damages and signs of extensive corrosion. IN in this case The electronic micro-BGA component is severely damaged (it functions as a backlight controller). This electronic component it is necessary to change it, and the area under it must be thoroughly cleaned. Such small micro-BGA components in modern phone there can be a lot.

Thus, restoring any device after liquid ingress is a very labor-intensive and complex process, the success of which is largely due to your the right actions when a malfunction occurs. In general, the repair of any flooded device must be considered strictly individually and it is IMPOSSIBLE to immediately say about the possibility and cost of repair!!! It is imperative to diagnose the device, identify damaged units and/or components, as well as thoroughly check the operation of the device after replacing these components. This type of repair requires availability in a service center modern equipment and highly qualified engineers, therefore, Dear Customers, do not repair your phones in unknown and unqualified “workshops”. Remember the old saying: “The miser pays twice!”

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 let a smartphone owner down? 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 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 separate section internal NAND memory and is in no way related to 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 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 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: 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 assemblies 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 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 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 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 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 application or by reinstalling the stock firmware using the 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 an increased level of Android security by 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. 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 destroy 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 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 TWRP applications Manager, ROM Manager or ROM Installer. 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 the command line and go to the directory SDK installation, 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 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 4PDA 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 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 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 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:

  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 return everything to its 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 get full control above the device? In the end, reinstalling Windows on a PC doesn't scare anyone.

Self-flashing mobile phone on Android - a simple task that rarely leads to bad consequences if you did not make a mistake with the selection of files. But if something goes wrong, the device may refuse to boot.

Today we will learn how to restore a phone after unsuccessful firmware. It does not require much time, just downloading the necessary software and a few additional steps.

Recovering with the help of official support

If you tried to update Android using the official firmware, then utilities from the manufacturer will help with recovery.

  • look at the company’s website, download drivers and other software there
  • connect your computer to your phone
  • restore the device to its original state

Each company's software has a specific section responsible for this, but finding it is usually not difficult.

Let's use Recovery

If you tried to install third-party firmware on your device, then at best it will be possible to restore the system by resetting the settings. It can be launched by simultaneously pressing the volume and power buttons. On various devices combinations may vary. Select the line " wipe data", then start resetting the device contents. You can try to install operating system again, to do this, select “choose zip from sdcard”. We find the archive with the firmware and start the installation process again. It's better to use another version because old version can lead to the same problems.

Using Flash Tool

It is this program that will help you in all those cases when you need to return your mobile device to its original state. The method is applicable to almost all smartphones. First, download and install ADB Driver Installer. Copy the firmware file to the Firmwares folder located in the Flashtool directory. We take the device and connect it to the PC using a USB cable. Now click the button with the lightning icon in the Flash Tool, and then select the device firmware in the program.

Note that in cases where your smartphone is rooted, installing the official firmware will be problematic; usually such actions lead to failures.

In addition to the video from detailed instructions by “rolling back” the firmware.







2024 gtavrl.ru.