How to restore the lighted preloader MTK 6753. Return the chipped smartphone to life

A frequent problem when firmware firmware based on MTK - incorrect installation of USB drivers. You are going to flash your smartphone using SP_FLASH_TOOL, connect your device to a computer, but it simply does not see your device and does not respond to its connection. With such a problem, you need to check the correct installation of the drivers. We will tell about the three main ways to install.

In Windows 10, the installation of the MTC driver for correct operation SP_FLASHTOOL is not always required, most often it is pre-installed there.

Method 1. Automatic driver installation

If the automatic installation of the MTK driver through.exe or.bat installer did not help, either in the folder with the drivers no.exe or.bat file and sp_flash_tool continues to ignore your smartphone, then try the manual MTK driver installation method.

Method 2.

Video Instrument MTC Driver

Method 3. Manual installation driver MTK Preloader

1. Download and unzip drivers specifically for your smartphone model or universal - (Dropping: 2673)
2. For Windows 8 and 10 - before installing, be sure
3. Open Device Manager
   
4. In the Device Manager, set the cursor on any item from the list, then click Action\u003e Install an old device

   

5. Click Further and select "Installing the equipment selected from the manual list". Click Further

   

6. Paragraph "Show all devices" - Next
7. "Install from disk"

   

8. Overview, find the unzipped driver folder and select the driver file depending on the bit of your operating system (x64, or x32 - it is x86). For example, a universal driver for Windows 10 64x - "Windows 10 x64 MTK USB Drivers"

   

9. Choose "MediaTek Preloader USB VCOM PORT" from the list. Click Next Several times
10. During the driver installation, press "Anyway to install this driver". In the end - Ready.

    

11. A new device with exclamation sign will appear in the device manager. Right click on it and click "Delete device"

Sp Flash Tool - Smart and convenient tool designed to firmware devices built on the basis of MediaTek chipsets. If you decide to flash an Android smartphone or a tablet with such a processor "under the hood", then you need to take care of the opportunity to make backup ROM apparatus if something goes wrong. In addition to the usual reason (precautions), there is another reason here: not every firmware you chose can approach specifically for your device. Therefore, it is necessary to make sure that the requirements for the characteristics of the display, the amount of memory and the other regulated new firmware parameters are fully observed. Otherwise, the software, and with it the device, may be partially or completely inoperative. Practice shows that when the Android-smartphone firmware is coincided with the SP Flash Tool, it goes smoothly, but we still decided to lead the backup instructions.

Creating a full backup of the flash memory of the smartphone

To create a backup copy of the Android-smartphone flash memory, you must have the utility itself and.

1. Run the flash drive, then in the "Download" tab, download the scatter file (it can be borrowed from the Android device with a similar processor). Do not be afraid if you do not see any firmware files in the folder with the Scatter file - this is normal. Leave a tick on the first line (Preloader), remove the rest.

2. Determine how much information and from where you need to read. After that, go to the "Memory Test" tab. Here, too, only one tick on " Ram Test", the rest must be removed.

Next, act in the following way:
2.1. Press the START button;

2.2. Through the USB port, connect the android device turned off to the PC;

2.3. The memory test that will occur after the connection will show you the information you need on the EMMC blocks (not pay attention to the blocks with zero volume, you will need only having size;

3. Copy the information received into Notepad, then go to the "Readback" tab and click "Add".

3.1. Double click on the appeared line;

3.2. Set the file name (by default ROM_0), and also specify the place where the memory block will be saved;

3.3. Focusing on the data obtained earlier, fill out three parameters in the window that appears.

You received the names of your regions, the size is known, and the starting address in each of them will be 0x0.
Example:
Region: Emmc_user Start Address: 0x0 Length: 0x3ab400000
After filling in the parameters, it remains to click the "OK" button.

note : on the device taken as an example, there are 4 regions, but this does not mean that they are as much on other gadgets. Flash memory can be 3, 2 or even one region ("User"). In the latter case, you do not have to choose the region - in the menu, designed to enter the block read options, this option will be absent. As a rule, such a situation occurs when working with Android devices based on the chipsets of the early anniversary.

3.4. Press the "READBACK" button, reconnect to the USB port of the off gadget - reading will begin;

3.5. After the block reading is completed, repeat the manipulation described in clause 3 with all other regions.

So you get a full copy of your Android flash memory.

If you decide to use the Sp Flash utility, it is easier to take to firmware (modified recovery for your device) and download the appropriate MTK gadget processor to the home computer. All old drivers belonging to Android devices will need pre-delete. You will also need to download the option for Windows or Linux. And do not forget that the SP Flash Tool utility for MTK devices can be compatible with a 32 or 64-bit version of the PC OS - it is important to choose the correct corresponding system installed on the home computer.

From the hardware will be needed:
1. Home computer Windows / Linux;
2. Good USB cord for switching with an Android device;
3. Android smartphone or tablet computer.

SP Flash Tool can flash devices based on MT 6575 chipset, MT6577, MT6577T, MT6582, MT6572, MT6582, MT6572, MT6589, MT6589T.

Installation Driver

Suppose that your PC already has an archive of drivers - for example MTK_DRIVERS.RAR.. The first step is to turn off the smartphone or tablet and run the "Device Manager" from the control panel. Connect the Android device to a computer via USB cord and wait until the "Dispatcher" updates and detect an unknown device. Next, you need to act very quickly: while the smartphone has not switched to charging mode, right-click on an unidentified device and select the item in the window that opens. Refresh Driver".

Driver installation is performed manually. In the next window, select "Install the driver from the specified location", then specify the path to the driver archive (it must be pre-unpacked) and set the desired one. Now you can disconnect the Android device from the PC, but it is too early to turn it on. But you can go directly to the firmware itself.

Instructions for firmware smartphones based on MTK

Here we give a complete step-by-step instruction, following which you can independently perform the firmware of the Android smartphone or tablet based on MediaTek processors.

1. Download the SP Flash Tool and unpack the archive to the computer;
2. If you have a device with a MT6575 or MT6577 processor based on the AGOLD project, download the SP_MDT program to the computer with the ability to select components in UBoot and unpack it;
3. Download and install VCOM USB drivers;
4. Unpacking the archive with the factory firmware for your Android device (the name of the directory for the unpacked folder with the factory firmware files should not include the Cyrillic characters);
5. Turn off your smartphone or tablet, the USB cord must not be connected to the computer;
6. Remove the battery, then insert it back;
7. If the drivers are not yet installed, connect the machine to the PC by using a USB cord. The operating system will then find a new device, and you must specify a folder with the USB VCOM driver for your version of the OS. Install the drivers and disconnect the PC cord.
8. Run SP Flash Tool;

9. Click on the Scatter-Loading button and in the firmware folder, select the MTXXXX_Android_scatter_emmc.txt file (in MTXXXX LITERA X, replace the numbers corresponding to the processor of your device - the scatter file for each of them your own).

ATTENTION! For machines based on MT6575 and MT6577 processors, remove the checkboxes from the Preloader and DSP_BL items, for all other devices with MediaTek chipsets, remove the checkbox from the Preloader item;

10. Click the download button;

11. Disabled smartphone or tablet Connect to a computer via a USB cable. As soon as the new device is detected, its firmware should begin. If this did not happen, disconnect the machine from the PC, remove and insert it back its battery and connect to the computer again. In the process of firmware, subject to the correctly installed drivers, MTK USB Port must be observed in the device manager (MediaTek Preloader USB VCOM Port). If an error occurs, the gadget will stop displaying. Upon completion of the firmware, it also disappears from the device manager.

Firmware safely completed? It remains only to disconnect the Android device from the computer and turn it on.

Most of the articles in the X-Mobile heading are devoted to hacks and tweaks that require root rights, modify the firmware or its replacement on the custom. However, not every reader is ready to expose his smartphone similar operations, fearing that they are able to turn the device into a brick or lead to the appearance of instability in the work. Today, I will debunk these myths and show that even in the very waters, it's not so difficult to return the smartphone to life.

Destroy myths

Let's talk about what is still "to turn a smartphone in a brick" and what other pitfalls can wait for users on the way of changing the system and install custom firmware. What glitches can you catch at the same time and is it possible to kill the smartphone, incorrectly reflashing it? Will you lose a guarantee forever or smartphone can be returned to the previous state? Are custom firmwares can bring the owner of the smartphone at the most inopportune moment and are they worth it?

Myth 1. Incorrect flashing can kill a smartphone

Kill your smartphone can fall from the fifth floor, but not a flashing. The main problem with which anyone who wants to reflash the smartphone is facing - during the installation of the firmware, a failure may occur, which will lead to its inoperation, and the smartphone will actually turn into a brick.

All this is so, but only on paper. To understand why it is enough to figure out how the process of flashing a smartphone works and what system components are used. To obtain an ability to install a third-party smartphone, you must unlock the bootloader (not in all cases), get root and install the Recovery Custom Console (ClockworkMod or TWRP), capable of installing firmware with any digital signature.

The recovery console is stored in a separate section of the internal NAND memory and is not related to the installed operating system. After installing the 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 on the spot, and everything that needs to be done is to boot again in Recovery and re-install the firmware.

In addition, any custom recovery console contains the backup / recovery function, which 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 the initial state.

You can ask: what will happen if a failure occurs during the installation of the recovery console itself? Nothing, in this case, the reverse situation is when the operating system itself remains in place, and the console will be lost. To deal with it, it is enough to flash recovery directly from Android.

It is hypothetically imagine the situation when the firmware will be killed, and the recovery console will be killed (although it is quite difficult to do), but even in this case there will always be a primary loader, stitched into a permanent memory of the smartphone.

Conclusion: Kill your smartphone, establishing a third-party firmware through a custom recovery console, is impossible. On the spot will always be left either recovery or primary bootloader.

Myth 2. Castom Firmware Unreliable

Firmware firmware Maine. On the unrestrained worldwide web you can find a huge amount of Android assemblies for every taste and color, and most of them are really a slag that can lead to instability in the work of the smartphone and the loss of part functionality. Therefore, the first thing to be remembered is to have only serious custom firmware developed by large teams of experienced developers. First of all it is CyanogenMod, Paranoid Android, Aokp, Omnirom and Miui.

Second. Firmware There are two types: officially supported and portable by third-party developers. The same CyanogenMod, for example, has the official version for the Nexus 4 smartphone, but does not have such for Motorola Defy. But for Defy there is an unofficial port of CyanogenMod 11 from the developer with Nick Quarx. Their difference is that the CyanogenMod team is responsible for the support and proper performance, while the second - Quarx personally. Official firmware versions are usually fully operational, but the correctness of the second work depends on the third-party developer.

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

Conclusion: If you install a stable official version of the "normal" firmware to the smartphone, the risk to face bugs is minimal. Everything else - for experimenters.

Myth 3. Software, requiring ROOT rights, is able to surpit smartphone

In the theory, the application with root rights can make anything with a smartphone firmware, including erase it completely. Therefore, with such a software, it is necessary to be extremely careful. The software that we tell on the magazine pages is fully safe and tested on your own skin. In addition, for all the time of using smartphones on Android (and this is from version 1.5) I never I did not come across a situation where the software with the support of Root would kill the smartphone.

The software distributed through Google Play is usually fully consistent with the stated characteristics, and if he led to a brick or left a backdoor smartphone in the depths, he would not hold out the week in the store. In any case, here you need to follow the rule "Trust, but check" and carefully read the instructions for using root applications.

Myth 4. ROOT rights make a smartphone vulnerable to viruses

The smartphone is vulnerable to viruses do not root rights, but the bugs used to receive them. Ruting and viruses can use the same Android vulnerabilities to get root rights, so the fact of the presence of root on the device does not change anything. A competently written virus will not request rights to the standard way, issuing its presence, instead it will take advantage of the same vulnerability to get them secretive.

Moreover, having a root, you get the opportunity to establish a fresh version of Android (as a custom firmware), in which these bugs have already been corrected. Also, do not forget that most custom firmware allow you to turn off the root or create white application lists that can use these rights.

Myth 5. A tangled smartphone can get used

Software, designed to get root, makes four simple things: runs an exploit that allows you to get root rights in the system, mounts the / System in recording mode, copies the SU binarrick to the / System / XBIN directory required to get root rights in the future and Installs the SuperSU or SuperUser application, which will receive management every time any application will request root rights using SU.

None of these stages can lead to a failure or kill the smartphone. The only thing that can happen is - the exploit will cause a segmentation error and the smartphone will go to the reboot, after which it will continue to work normally.

Myth 6. Having received root and installing custom firmware, I will lose a guarantee

The warranty is not lost from the very fact of obtaining root, and due to its detection to the service center. Most devices can be delivered from root rights using the Universal Unroot application or re-installing the stock using the official application from the manufacturer.

From this rule, however, there are two exceptions. The first is the KNOX system, pre-installed on new smartphones and Samsung plates, such as Galaxy S4, S5, Note 3 and Note 10.1. KNOX provides an increased Android security level, responding to any firmware modifications and installing third-party kernels and firmware. In the event that the user performs the action data, the system establishes a trigger that confirms the fact of modification. The trigger is implemented hardware (EFUSE chip), so it will not be possible to reset it in the 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: EFUSE chip is installed on some other devices (for example, LG smartphones), and it also allows you to accurately determine whether the smartphone was ruled or reflash.

If we talk about custom firmware, everything is more complicated. Usually, 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 loader will accurately indicate that the smartphone belonged to far from blonde.

On some smartphones there is an opportunity to block the bootloader back, however, it should be recognized separately, and also keep in mind that a re-locked loader will most likely receive the status of the RE-Locked, and not locked, as was originally (this happens on HTC smartphones, eg). The exclusion here is only the smartphones and tablets of the Nexus line, the loader of which can be blocked and unlocked without any dancing with a tambourine, and no one will hold anything.

Info

Linux ADB and FastBoot can be installed separately from Android SDK. In Ubuntu: Sudo Apt-Get Install Android-Tools-FastBoot. In Fedora: Sudo Yum Install Android-Tools.

So that the KNOX system does not interfere with the operation of root applications, it can be turned off using the following command from the terminal: SU PM Disable com.sec.knox.seAndroid.

conclusions

Obtaining root and flashing a smartphone - absolutely safe operations that can not drop the smartphone for purely technical reasons. The only exception is an attempt to hook an initial loader in order to unlock it. In this case, there may be an EFUSE chip (if there is such in the smartphone) and block the ability to turn on the smartphone.

Fortunately, today manufacturers of smartphones or prefer not to block the possibility of incorporating a smartphone with a naked bootloader (setting a trigger, indicating the fact of such actions, as the KNOX does), or implement a special web service that allows you to painlessly unlock the bootloader with a loss of warranty on a smartphone, That eliminates users from the need to risk, breaking the loader.

Problems that may arise when flashing

So, now let's talk about what problems may occur when receiving root and flashing and how to deal with them.

Scenario First: After unsuccessful flashing, the smartphone stopped loaded

Unsuccessful flashing can be caused by several factors: the battery sat down, and the firmware was filled only by half, the firmware turned out to be failed or intended for another model of the smartphone. In the end, the smartphone simply did not have enough space that could occur when trying to establish a fresh version of Android on a smartphone of three or four-year limitations.

Externally, all these problems are usually manifested either in endless discharges of the smartphone to the initial logo of the manufacturer, or in the so-called boot-loupe when the load animation is spinning on the screen for more than five to ten minutes. Problems with the screen (multicolored ripple) and non-working touchscreen, which also prevent the use of the smartphone are possible.

In all these cases, it is enough to make one simple thing: turn off the smartphone by long pressing the power button, then turn on the volume with the volume button with a drop-down button (some smartphones use another combination), and after you come to recovery, reinstall the firmware (Install Zip From SDCard - \u003e Chooze Zip from SDCard) or restore backup (Backup and Restore -\u003e Restore). Everything is easy and simple.

Scenario Second: Firmware Works, but Recovery is not available

This can occur after an unsuccessful installation or updating of the recovery console. The problem is manifested in the fact that after rebooting the smartphone and turn on with a swollen volume button, a black screen appears, after which your smartphone is either reset or hangs.

It is not easy to solve this problem, but very simple. Install the recovery console to the absolute majority of smartphones using TWRP Manager, Rom Manager or Rom Installer applications. They themselves define the smartphone model, download and flash the necessary recovery, without requiring a reboot. If you cannot restore the console with them, it is enough to find the Recovery Installation Instructions on your device on the Web.

Scenario Third: Neither firmware nor recovery

Honestly, it is difficult for me to imagine such a scenario, but, as the practice confirms, it is quite real. You can exit this situation in two ways: use fastboot to fill Recovery on your smartphone or use the tool from the manufacturer to install the stock firmware. We will consider the second way in more detail in the next section, and I will tell you about FastBoot here.

FastBoot is a tool that runs directly with the primary loader of the device and allows you to make fill to the smartphone firmware, recovery and the loader unlock (in the Nexus line devices). FastBoot support is in many smartphones and tablets, but some manufacturers block the possibility of using it. So you have to consult about its availability with the Internet.

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

$ FastBoot Flash Recovery Image.img

Or even make the smartphone download recovery without its actual installation:

$ FastBoot Boot Image.img

In the same way you can flash official Firmware update:

$ FastBoot Update File Update.zip

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

We return the smartphone to the initial state

In this section, I will tell you about the ways to return the smartphone to clean drain, in what would be it was. These instructions can be used both for emptying the smartphone and to remove traces of routine and flashing. Unfortunately, I can not tell about all possible models, so I will stop at the four most popular flagships: Nexus 5 (I call this copy), Galaxy S5, LG G2 and Sony Xperia Z2.

Nexus 5 and other googlephones

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

1. From here.
2. Download and install Android SDK.
3. Download the archive with the firmware for the desired device from the Google site.
4. Turn off the device, turn on with clamping volume buttons (both) and connect using a USB cable.
5. Unpack the archive with the firmware and run the Flash-All.bat script or Flash-all.sh (Linux) and waiting for the end of the operation.
6. We run the command line, go to the directory with the Android SDK, then Platfrom-Tools and execute the FastBoot OEM Lock command for the loss of the bootloader.

For those who are interested, what the script does, here's a list of teams:

Fastboot flash bootloader bootloader-NAME-devayse-VERSIYa.img fastboot reboot-bootloader fastboot flash radio radio-NAME-devayse-VERSIYa.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.

With a smartphone Galaxy S5, everything is somewhat more complicated, but in general is quite simple. This time it will take the Samsung Odin application, with which the smartphone firmware will occur. 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. We go to the site samfirmware.com, we enter the SM-G900F model in the search, we find the firmware with the mark of Russia, download and unpack.
4. Turn off your smartphone and turn on the volume and "home" buttons with clamping buttons, we wait five seconds until a warning message appears.
5. Press the volume button to translate your smartphone to ODIN mode.
6. We connect your smartphone using a USB cable.
7. We start ODIN, press the PDA button and select the file with the extension tar.md5 inside the directory with the unpacked firmware.
8. Press the Start button in ODIN and wait until the firmware process is over.

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

LG G2.

LG G2 recovery to the factory state will also not cause special problems. The number of steps in this process is somewhat more, but by themselves they do not require special training and knowledge. So, what to do to return the factory firmware to G2:

1. Download and install ADB Driver Installer from here.
2. Download the 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 your smartphone, clamp the volume button and insert the USB cable.
5. We deploy the FlashTool archive and launch the UPTestEx.exe file.
6. In the window that opens, select Select Type -\u003e 3GQCT, Phone Mode -\u003e 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, choose 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 in the case of Samsung, the smartphone still will have the status of rooted, and it is not corrected.

Sony Xperia Z2.

Now about how to return to the factory state Sony Xperia Z2 smartphone. As in the previous two cases, it will take stock firmware and the official firmware utility. You run the utility on the PC, connect your smartphone using a USB cable and run the update process. Step by all this 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 site and the last firmware from here.
4. Copy the firmware file to C: / Flashtool / Firmwares directory.
5. Turn off your smartphone and turn on the volume and "home" with clamping keys.
6. We connect a smartphone to a PC using a USB cable and run Flash Tool.
7. Press the button with the zipper icon in Flash Tool. In the window that opens, select Flashmode, twice click on the firmware in the list that opens.

Warning

In many smartphones, the unlocked bootloader will not allow you to perform an update by air.

In 90% of cases, the loader unlock entails the deletion of all data from the smartphone, including the memory card.

conclusions

The firmware of the smartphone, and even more so, getting root-access is not at all such terrible and dangerous operations, what they may seem at first glance. If you do everything correctly and not resort to tools that unlock the smartphone bootloader into the manufacturer's tools bypass, the smartphone will not succeed. Yes, in some cases will have to be tinked to return everything to the place, but what is better to use a lociated smartphone that does not allow and half of those things to which it is capable of, or get full control over the device? In the end, reinstalling Windows does not scare anyone on PC.

Brick - Not one novice user asked this question: "How to display a device from a brick state?" But for starters, let's see what brick is and if you really got a brick. If for some reason the phone or tablet does not turn on, then there may be two options here: the preloader flew or failed memory. In the case when the preloader flew the body is enlivened without problems, but when the flash memory burned out - only the service center. In one and in another case, the symptoms are the same, and it is immediately difficult to distinguish with the fact that it really is, but it is worth trying. So, let's consider on the real example how can you revive or output a smartphone from a brick condition.

When writing this manual was used on the basis of the MTK processor. We want to note that restoring bricks for other MTK devices in principle is identical.

Well, that, proceed. If you got a brick, instead of a new firmware, then the archive of your downloaded firmware is damaged. To do this, download the archive with the firmware from the proven source, for example, from the nidrome. In this case, you need to pay attention to which version of the device - 8 or 4 GB of memory, we also recommend re-installing your gadget drivers on your computer.

They are not responsible for the damage to your phone, if something went wrong.

Next, all make strictly according to the instructions:

1. Unpack the downloaded firmware in the root of the disk C (C: \\);

2. Download a new preloader from here (this specifier is only for Lenovo S820), in some cases you can do without it, but if you do not turn out then follow further instructions;

3. Go to the folder of the firmware folder Target.bin, now it needs to be replaced with the native Preloader file to a new one, to the one that was downloaded in paragraph 2.

4. In the same folder TARGET.BIN, now delete the checksum.ini file.

6. We put a tick opposite Da DL All WITH CHECK SUM;

7. Specify the path to the scant-file, and then press the Firmware Upgrade button;

8. We take your phone, more precisely brick, pull out a battery from it and connect it to a computer.

9. All, now waiting for the end of the firmware process.

Here, in fact, everything, now you have a manual to restore bricks. We are waiting for new comments from you.

Stay with us, there is still a lot of interesting things.