Android does not see the memory card. Instructions on how to recover data in the internal memory of an Android phone

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 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 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, which allows you to make a backup copy of the main firmware and restore it unchanged (with all applications, settings and data) in the event that something goes wrong. In fact, the smartphone can be returned to its original state.

You may ask: what happens if the installation of the Recovery Console itself fails? Nothing, in this case the 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 into the permanent memory of the smartphone, will always remain in place.

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

Myth 2. Custom firmware is unreliable

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

Second. There are two types of firmware: officially supported and ported 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 use the same Android vulnerabilities to obtain root rights, so the very fact of having root on the device does not change anything. A well-written virus will not ask for permissions in the standard way, revealing its presence; instead, it will take advantage of the same vulnerability to obtain them covertly.

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

Myth 5. A rooted smartphone may fail

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

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

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

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

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

If we talk about custom firmware, everything is more complicated. 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 the following command from the terminal: su pm disable com.sec.knox.seandroid.

conclusions

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

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

Problems that may arise during flashing

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

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

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

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

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

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

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

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

Scenario three: neither firmware nor recovery is available

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

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

To access fastboot, you will need drivers and the Android SDK. When they are installed, open command line, go to the 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 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 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 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:

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

With the Galaxy S5 smartphone everything 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 latest version 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 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 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 firmware utility. 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 the 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 PC it doesn't scare anyone.

Problems with smartphones are quite common. They are caused by many reasons that do not always depend on the user. There are also software errors. Why doesn't 7-Data Android Recovery see my phone? What kind of program is this anyway? How to work with it correctly? The answers to these questions are presented in the article.

Program

So, 7-Data Android Recovery is a program that was Russified not so long ago. It is needed to recover data from a smartphone in the operating room. Android system. If, through your fault or due to software failures, personal data was lost, in order to restore it, you need just such an application. The interface is intuitive, so no problems should arise when returning your photos.

Beginning of work

Before we understand why 7-Data Android Recovery does not see the phone, what to do in this case and what are the causes of this problem, let’s look at how exactly the program works. You can download and install the application from the official website. Here you will also find a version for PC. If any data has been lost from your computer, 7-Data Recovery Suite will help you recover it.

This application has a special section for Android devices. The operation of both utilities is almost identical, at least regarding the mechanism.

Preparing your phone

To try to recover lost photos, you need to connect your smartphone via USB to your computer. As practice shows, it is advisable to immediately disable USB debugging on the device. Sometimes users forget about this operation, then a problem may arise that 7-Data Android Recovery does not see the phone.

Let's go to settings. Here you need to find the line “For developers”. It also has a USB debugging function. You may not find such a section; to do this, you will need to configure it.

Connection

So, you have connected your smartphone via cable. You need to open the program. A simple menu will appear in front of you, in which everything is clearly indicated and described. There are recommendations here that need to be followed. This refers to USB storage and connection via a device cable. Then you need to click “Next” to continue the setup.

You will see a list of storage devices that are on your smartphone. There may be a section of internal memory and external storage. If you don’t have a memory card, then there will be only one section. You need to select it and click “Next”. Choice the desired section depends on where your files disappeared from.

Next, the program begins scanning the device. Upon completion of this process, the utility indicates lost, deleted, damaged files. The list may be empty if the device has irretrievably destroyed the documents. There may be a huge number of folders among which you need to look for what you need.

If you find a file or folder, click on it and click “Save”. If several files have been lost, you can check the box next to each one and save it again. Afterwards you will have to specify the folder where you want to restore the found data. It is recommended to send them to a PC rather than a smartphone.

Error

But the instructions described above are suitable for those who were able to connect the device. What if 7-Data Android Recovery does not see the phone? This can be caused by many errors. But most often this is due to the fact that the computer itself does not want to detect the smartphone.

The problem is common. There are many possible solutions, as well as reasons. Maybe the wire is simply damaged, or maybe there is an error in the PC system itself.

Debugging

This is one of the common options that occurs when 7-Data Android Recovery does not see the Lenovo phone. What some users miss is that they need to enable USB flashing. This process makes it possible to indicate to our computer that we want to turn on the device in a special mode.

Depending on the OS revision, you need to approach configuring this mode differently. If you have Android 2.3, then in the settings you need to go to the “Applications” section and find the “Development” line there. In later versions, the “Developer Options” option appeared directly in the settings.

Starting with a newer version of the OS, you need to go to the “About phone” line in the settings. Here we look for “Build number”. This line is not active, but we can click on it. You need to do this several times, as practice shows, about seven clicks. Information will appear at the bottom indicating that you have become a developer. Now the “Developer Options” line will appear in the settings.

In new operating systems, this menu may also be located in “ Accessibility" Here you will have to look in the settings in different tabs.

Modes

7-Data Android Recovery does not see your LG phone because you have set the wrong connection mode. Some users connect their smartphone and see that it just starts charging. Of course, sometimes this is due to problems with the device itself, but most often the wrong connection is selected.

You need to go to settings and find the menu for connecting a device via USB. Depending on the phone model, you will also have to look for this item. For example, Meizu hid this item in “About phone” - “Memory”. Quite illogical, especially for those who have previously used other models.

There are four modes in this menu. You need to use “Connect as media device (MTP)”.

USB

The 7-Data Android Recovery utility does not see the Samsung phone if there are any connection problems. This is the first thing to check. Maybe just cable is damaged, or maybe the problem is in the connector.

To do this, you need to try changing the wire and connecting through other ports. If the program sees the smartphone, then the problem is clear. If not, move on.

Drivers

The computer, and therefore the 7-Data Android Recovery utility, does not see the Sony phone because the drivers for the USB controllers, or more precisely, for the smartphone, are outdated. To check all this, you need to go to “Device Manager”. All connected devices to our PC will appear in the window in front of us. We are looking for controllers, and in them is our connected device.

You need to click on it and select “Properties”. We look for the “Driver” tab at the top, go to it and click “Update”. If there are drivers on the PC itself, you can manually specify the path to them. If they are not there, then run an automatic search.

Additional options

There are even less probable reasons for such an error, but they should still be excluded. As practice shows, perhaps the problem is that the memory is full. You can try cleaning and removing unnecessary files. The system may be busy third party processes and simply does not allow you to connect to your PC.

If 7-Data Android Recovery does not see your phone, there is a possibility that the utility does not support your device model. Unfortunately, this sometimes happens, especially with outdated models. If this is the case, you can find other analogues of the application on the Internet. For example, a good option Android Data Recovery. The utility is practically a copy of 7-Data Android Recovery.

It recovers data, finds lost files, and returns incorrectly deleted ones. The program runs on the Android operating system. Due to the fact that the interface of this utility is just as simple and clear, working with it will not cause difficulties.

But remember that you should also not forget about the “USB Storage” mode. Despite the fact that many people neglect these instructions, without them errors and failures will occur. So first set up this mode. Then connect your smartphone to your PC.

After launching the program, it will immediately be clear whether it sees your phone or not. There is another option - connect the device via a wireless interface via Wi-Fi.

conclusions

If you have lost any data, you can still recover it using similar programs. The question is: what to do if they don’t see the phone. Then you have to sit for an hour or two to figure out the problem and find out whether the wire is simply damaged, or the smartphone is not working correctly, or you are doing something wrong.

Very often, data is deleted not from the SD card, but from the internal memory of Android. In this situation, not a single file recovery program for Android helps. That is, users not only lose valuable data, but are also limited in recovery methods.

This method of recovering data from the internal memory of an Android phone cannot be called very simple. But it works and has been successfully tested by me. The described recovery method was proposed by the user Wartickler on the forum.xda-developers.com and supplemented by a very useful article on Habrahabr (most of the relevant information is given from there. Thanks to the author for the presentation).

Who will benefit from this guide on how to recover data from your phone? File deletion scripts

It turns out that it is possible to deep scan Android internal memory. Everything you need to recover data from your phone:

1. download free utilities recovery
2. carefully read the data recovery instructions
3. repeat the steps described in it on Android.

Difficulty in restoring from the phone's internal memory

Android internal memory is not connected as a disk, as is the case with an external SD card, which you can always connect to your computer. External memory allows you to use data recovery tools that scan deleted files and help return them to working condition.

Typically, the operating system simply removes the reference pointer in the index, which indicates that the file exists with such and such a name and is located at that location on the hard drive/memory. Eat effective tools to delete data, they overwrite the deleted file in several cycles, preventing recovery in this way.

The catch is that data recovery programs need the actual disk to deeply scan photos that were accidentally deleted. New phone models often do not support external SD cards, which are very easy to mount as disks using a card reader. This complicates Android recovery slightly: the internal memory is mounted as MTP/PTP, which is not considered a mounted drive and is therefore not recognized by data recovery applications. However, we can solve this problem.

Stages of restoring internal memory

I have a Samsung Galaxy Nexus Toro phone. I believe the recovery method is suitable for any android phone with internal memory. We will also need Windows 7 or higher to:

• Back up a partition of your phone's internal memory to your computer as a single massive file in RAW format,
• Convert RAW file to virtual hard disk,
• Mount the virtual hard disk as a disk in Disk Manager,
• Scan the mounted virtual hard disk,
• Find deleted files, recover data from an Android phone using the Recuva recovery program

Checklist of necessary tools for data recovery

• Android phone with root access
• Installed BusyBox (a set of Linux console utilities)
• Installed linux environment for Windows - Cygwin on pv and util-linux from the repository. You need to open the Cygwin application at least once to ensure that the /bin folder is created. In addition, I made a folder in to place the exported file in .raw format,
• Netcat Unix utility (download the zip file and extract nc.exe into ),
• (make sure adb.exe is in the Windows environment path),
• USB debugging on the device,
• VHD tool from the mighty Microsoft. Place the VhdTool.exe file in .
• Piriform Recuva or your favorite data recovery tool (Recuva finds only the most well-known file types: images, videos, etc. To recover more exotic file types on Android, use more specialized programs)

Install BusyBox on your phone and provide root access

We will need a copy of the phone's internal memory partition; making it is not so easy. You will need a set of BusyBox unix utilities and root access to perform operations with these applications.

You can download BusyBox and KingoRoot from our website or directly to 4pda (registration is required to download files). We install the utilities in the following sequence: KingoRoot, then BusyBox.

The KingoRoot root manager is easy to install: turn on the Internet on your phone and run the installer. It "roots" the phone - that is, it enables full access to the Android system. Next we install BusyBox. We leave the default path as the installation directory.

Install KingoRoot on your phone

Recover from Android internal memory. We connect the phone to the PC in ADB mode

Connect the turned on phone to the computer in ADB mode. The easiest way to do this is to download adb drivers for your phone model and install them on your computer. It is advisable to restart your PC after this.

On the phone, enable debugging mode (Options - Developer options - check the box " USB Debugging"). If there is no such section, go to the About the device section, click on the "Build number" line 7 times.

We connect the phone to the computer via a USB cable. If a request for debugging mode appears on the phone, we agree.

Making a raw copy of a partition from your phone

The recovery method from the phone's internal memory is based on complaints from people who have problems following the guide. I recommend recovering a full block of memory instead of a data partition. I call it mmcblk0. Check if your disk name is different from mine. Determine which block or section you want to return. I needed to restore the partition with user data: /dev/block/mmcblk0p12.

Open your Cygwin console (assuming BusyBox is installed at ) although it may be . Run the following commands in the console:

Adb forward tcp:5555 tcp:5555 adb shell /system/bin/busybox nc -l -p 5555 -e /system/bin/busybox dd if=/dev/block/mmcblk0p12

Open another Cygwin terminal and type:

Adb forward tcp:5555 tcp:5555 cd /nexus nc 127.0.0.1 5555 | pv -i 0.5 > mmcblk0p12.raw

Brew a mug of coffee. Copying internal memory of 32 GB takes about 3 hours.

Converting the internal memory image into readable RAW

We need to convert the raw file to a virtual partition hard drive. The VhdTool.exe utility simply places the VHD footer at the end of the raw file. Open Windows Command Prompt, go to and run the command:

VhdTool.exe /convert mmcblk0p12.raw

Mounting an internal memory image in Windows

Now you need to mount the VHD image in Windows OS. Go to Computer Management (Start - Computer - Management). Go to Disk Management.

Menu Action - Attach virtual hard disk.

Please indicate as source

Right-click the name to the left of the unallocated space and select Initialize Disk. Select GPT.

Right button on Unallocated File Space - Create Simple Volume.

A window will appear asking you to format the disk. DO NOT agree to format the drive at this point. not always possible!

Click right click mouse on RAW space and select Format... Specify the file system type FAT32. Set the allocation block size to "Default". Make sure the Quick Format option is checked. You don't want to overwrite the entire new disk with zeros (0) and destroy the data. A quick format means that Windows will try to destroy the index for the disk by creating a new index. Without this option, the Windows operating system will wipe the disk with zeros (0), destroying your data. Click OK.

A window will appear informing you that formatting this partition will delete all data on it. This would be doubly true if you didn't actually check the Quick Format option. Double check that you actually checked the box and click OK.

Recovering files from an Android internal memory image using Recuva

Open the Piriform Recuva application. In the recovery wizard, click Next. Select "Other" and "Next". Click the "In a specific location" button and enter: K:\ (assuming K is the drive letter of the mounted drive...). Click "Next". Select the Deep Scan option. This is the magic option that finds files that have been deleted... but aren't actually deleted. Click the "Run" button to scan the disk.

The application can scan deleted files for about an hour in Deep Scan mode. Brew two more mugs of coffee!

After Rekuva displays the scan results, you can select files to recover using the checkboxes. Click the "Recover..." button and specify the location where you want to save the data from your phone.

Recovering data from your phone using Recuva

Question answer

I have a GALAXY 3 NOTE phone. Accidentally erased recorded voice recordings on . I heard that there is free program recovery. Help if you know how to find it.

Answer. If the audio files were stored on an SD card, almost any file recovery application on Android and PC will do. Among the popular ones is Tenorshare Data Recovery, from universal ones, we recommend downloading Recuva. If the files were stored in the internal memory of the phone, then things are more complicated. Try the Android program called or follow these instructions to recover from internal memory.

Should I download the program to my computer or to my smartphone itself? I started downloading the program to my smartphone and it says “not enough space,” although there is enough internal memory. Will Renee Undeleter help you recover photos from your phone's internal memory? There was no memory card.

Answer. Firstly, do not copy files to where you are going to recover Android data from. Secondly, Renee Undeleter will not recover files in your situation. Try Recuva or choose another if unsuccessful.

I moved my important photos to the running game folder "Android/data/com.supercell.clashofclans". Then when I went to the folder on my phone, the photos disappeared. Will I be able to restore my photos to internal memory? SAMSUNG phone GALAXY J2 OC ANDROID 5.1.1?

Answer. Yes, if you follow all the steps as described in the instructions. The main thing is to determine which disk the photos were on and make a raw copy of this particular partition. Recuva should recover photos from internal memory if the recovery status is yellow or green.

Tell me how to understand whether the block recovery process is in progress? Everything seemed to be going fine, but after typing all the commands in the terminal, a couple of lines with zeros appeared in the second window, a *.raw file was created in the nexus folder with a size of 0 bytes, and that was the end of it. However, after some time, on drive E: (in my case, Cygwin was installed from there), a file with a name of something like vhd with a size of 499 MB was discovered (it restored a 12 GB block), but the most interesting thing was that a virtual disk was created with the only empty recovery.txt file! Something went wrong?

Answer. Everything is correct, the vhd is mounted, and after a quick format there should be no files on it at all. Now you need to launch Rekuva and specify this disk to search for files on it. If the snapshot of Android's internal memory was taken correctly, the files should appear in the list of found files during a deep scan.

If the raw file is not suitable for recovery, try another way to create a snapshot of the internal memory - by creating an FTP server when the phone is used as a USB modem. The process is described in the above-mentioned article on Habrahabr (link at the top of this article).

I have a Samsung GT-P7510 tablet. Android 4.0.4. I did everything as in your post. I have a Samsung folder. The vhdtool file appeared in it - 184KB and raw file, but it's 0KB. I can’t try the second method with FTP, because... There is no USB-Modem option.

Answer. Try downloading netcat 64-bit version. When entering commands in the console, use nc64 instead of nc.

If it doesn’t help, here are some more instructions for restoring from internal memory.

Files disappear from the flash drive and internal memory of Android. I’m not doing this because I’m not sure that the information is in the folder correctly! Tell me the reason and programs for recovering lost files from the internal memory of Android! The information on your site is purely for the computer!

Answer. Quality programs There is no way to restore from the phone's internal memory. Gaining access to the system is not so easy. This article provides a working method for recovering files from Android internal memory.

The problem is this: the tablet froze, some photos were restored at the service center, but the huts were reflashed and it seemed like the internal memory was formatted. I tried to restore it with programs, but the tablet connects as an MTP, and not as a flash drive, and it is impossible to scan. Is it possible to recover data from internal memory on Android by copying an image of the memory and its partitions?

Answer. Yes, the process is described in detail above. Using an ftp server, you can make an exact image of a memory card in the form of a raw file and mount it on your computer, then use any program (in this case Recuva) to restore photos from the image of the phone’s internal memory.

Updates have arrived for xiaomi redmi 3 special. Updated, installed - everything works. But the videos and photos saved on the phone’s internal memory disappeared. The most interesting thing is that the total memory of the phone shows 25 Gb, but it should be 32. Perhaps they are there lost files. I searched all the folders, but found nothing. How to recover deleted files in the internal memory of the phone, where to look for them?

Answer. Photos and videos are stored in the DCIM/Camera folder. If you did not use an external SD card to save, it means that the multimedia files were located in the internal memory, therefore, that’s where you need to look for them.

The photo folder may have been overwritten during the mobile device update process. By the way, part of the phone's memory is occupied by system files, so this does not indicate that the files you need are stored hidden.

Try searching for files with DiskDigger for Android; if that doesn’t help, make an image of the phone’s internal memory, then scan the connected disk with Reucva on your computer.

I decided to delete a bad photo, but accidentally deleted some of the others necessary photos. The photos were on the memory of the phone itself. When connecting to a computer, the phone does not show up as separate disk. Therefore, as I understand it, I won’t be able to restore the files with a simple program, since they were on the phone itself, in the internal memory. What program can I use to restore them? For me, some simple option is better, because I hardly understand this. If possible, with a description of actions and steps.

Answer. Simple methods There is no way to restore your phone's internal memory. As a rule, resuscitation programs for Android work only with external memory or require root to access the phone’s memory, while searching far and wide in all areas of the internal memory. Accordingly, the only possible way– make an image of the phone’s memory, at the next stage you can use any program. It is important that you do not operate the phone until this point, otherwise the files may be overwritten.

I am tormented by the question: is it possible to recover photos from the phone’s memory itself, and not from a memory card. I really need photos from the Camera folder. When I myself try to recover deleted photos through the programs that you recommended, some unnecessary photos from Telegram, someone’s avatars, but not photos from the camera at all. Is it possible to restore them?

Answer. Indeed, although developers claim that their programs will recover files in all areas of memory, in fact most of the data is ignored during scanning - either there are not enough rights, or the program simply does not know how to do it. If you have enough experience, take a snapshot of the device’s internal memory according to our instructions. The process takes a lot of time, but there is a chance that among other garbage you will find exactly the photos you need. In addition, it is absolutely free way recovery, so you can experiment in your free time.

1. I bought a new phone ( ZTE Blade X3), wanted to move the memory card from the old phone, but forgot to turn off the new phone before doing so. All the photos from the phone’s internal memory disappeared somewhere, but those that were on the memory card remained. There is only one question: how to recover photos from the phone’s internal memory?

2. Accidentally deleted a folder with photos in the internal memory of the phone. As a result, the photos remained in the Android Gallery, but in black and gray, with the inscription “file deleted or damaged.” Is there any way I can restore the photo?

Answer. First, check whether the photos have been copied to the memory card (they may be hidden), check for errors using the chkdsk utility (Windows).

If there are no photos, you can quickly follow the DiskDigger program or take a snapshot of the phone’s internal memory and then, with using PhotoRec or Recuva, return photos.

Trying to return a lost album from the Gallery, I downloaded two Android photo recovery programs. Some of the photos were returned, but not the most valuable ones. How can I try again with minimal risk? I want to try to return the missing photos, is this realistic in the current situation? The photos were stored in the Android's internal memory.

Answer. By repeatedly scanning your phone's internal memory, you do not risk anything. But the longer you use your phone after deleting photos, the lower the chances of recovering them. Any program uses internal memory for its work and can write files to free place. In your case, it is better to take a snapshot of the phone’s internal memory and conduct experiments with it in reading mode.

I want to use your method of restoring Android internal memory, but I don’t have enough space on my C drive - only 17GB, and the partition of the phone takes up 53GB. Is it possible to somehow create a folder for a virtual disk on drive D? Telephone Xiaomi Redmi Note 4x.

1. The next problem happened. Images from the camera were saved in the Camera folder on the SD card. When trying to transfer other image folders from internal memory to external memory, the Camera folder was automatically duplicated. I deleted one of the Camera folders, as a result of which the second folder was also deleted. Can you tell me if it is possible to restore these images? The transfer was carried out using a computer, maybe the images remained in the PC’s memory? Information is very important.
2. There was little memory left on the phone, since all the photos were saved in the internal memory. I found a way - I reset everything from the phone to the PC, while deleting everything from the internal memory. And when I transferred the folder with files to the flash drive, the necessary photos were not there. I tried all recovery programs - nothing worked.

Answer. Check all storage locations for images - hard drive, internal memory and SD card. Most likely, nothing was saved on the hard drive because it did not act as an intermediary (i.e., no files were copied to it).
In the future, we advise you to copy files and delete them only after checking them on the recipient. Copying via ctrl + x is quite unsafe: there are many cases where files were simply lost along the way this way.

my son deleted the photo from his phone (from the internal memory of the device). However, there is no flash card on the phone. How can I restore photo and video materials? I tried it through some programs - some of the photos were restored, but I noticed that these were photos that were once sent to my friends. Is it possible to restore the rest - the ones that I photographed myself? They are very dear to me

Answer. It is possible that the recovery programs you use do not scan those areas of memory from which programs were deleted. If photos are truly important, take the time to recover photos from a copy of your internal memory. We described this method in detail above.

[How to recover a deleted photo from internal memory?]

The phone's internal storage was full, so I deleted the data from the cache. After that, I realized that all my photos and videos were deleted! No backup was performed. I've tried apps to recover deleted photos, but I can't get the photos back. I deleted the files on 5/23/2018 around 10:53 am. What can I do to get the photo back?

Answer. If there is no space left in the internal memory, the data may have been overwritten many times. Therefore, the chances of recovering the photo are minimal. Check if the required files are on the memory card: what if the Android camera recorded files there, for lack of free space in internal memory.

If you are using mobile device Samsung and backup has been enabled, please check your cloud backup files. It's also a good idea to check your Google Photos albums to see if there are any photos there.

A week ago I bought a simple phone for myself, or rather a Beeline Smart 2 smartphone, also known as ZTE V811. After twirling it in my hands for a couple of days and getting a little acquainted with the new Android 4.4.2 KitKat, I realized that this was a rotten matter. The inability to transfer applications to an SD card and the non-functioning of some vital applications without superuser rights immediately prompted me to install ClockworkMod and be sure to get Root!

How to get Root on Beeline Smart 2 (ZTE V811) and install ClockworkMod on it is a separate topic, but today we will talk about something else...

Closer to the point:

First I needed to get Root rights. I uploaded the Zip archive with the update onto a flash drive, launched the phone into the Recovery menu and was about to install the update when ClockworkMod told me that it could not mount an external SD card ( E: Can’t mount /external_sd/).

I decided to put off solving this problem for a while. As a result, I transferred the archive to the internal memory and updated the phone from it.

A few days later, when I had already installed all the applications I needed and needed to make a backup of all the firmware, I returned to our sheep again

Instead of the memory card I had for 32Gb, I inserted another one for 2Gb. The card was mounted perfectly and a backup was recorded on it. Both cards are in the FAT32 system, which is necessary to work with ClockworkMod, the only difference is the cluster size.

I thought that 32Gb is too large and therefore Recovery cannot mount it. But as it turned out, the whole problem was in the Windows system and its discrepancies with formatting standards.

Solution to the problem:

For correct formatting memory cards we will need a free program SD Formatter or its continuation SD Card Formatter.

This program, unlike standard formatting Windows formats according to the SD/SDHC/SDXC flash card specification.

Starting from version 5, SD Formatter is called SD Card Formatter and has a different interface, settings (more simplified) and Windows support 10.

Doesn't matter full formatting you chose or fast. After processing the SD card with this program, everything works fine. There is also a version for Mac OS on the official website. Description and system requirements inside the archive.

Any device with Android OS starts in Recovery mode. This is a standard feature. However, with the factory version you can perform too narrow a range of tasks. So, this is resetting the phone to initial settings, clearing the cache, as well as updating the system from the update.zip file. Obviously, users who are expanding their knowledge in the IT field are very dissatisfied with such a meager list. This is where specially developed Recovery Mode s. CWM Recovery is a popular tool among Android users and a worthy replacement for the factory one.

Why do you need CWM Recovery mode?

Clockworkmod Recovery (CWM) is a famous alternative to factory recovery mode developed by Koushik Dutta. You can install it on most Android devices. CWM Recovery helps even in situations that sometimes seem hopeless to the average owner. That is why it is necessary to know about its existence, and also be able to use it.

CWM mode has many options

What exactly does the utility do:

Installs unofficial custom firmware and kernels.

Installs factory system updates, add-ons and OS patches.

Connects to a computer via USB in removable storage mode and for working with the ADB program.

Creates a complete backup copy of the current firmware and its individual parts (system, settings, applications).

Restores the device from a previously created backup.

Resets settings to factory settings (Wipe - data/factory reset), clears cache ( wipe cache), clears the Dalvik-cache, clears the battery statistics.

Creates partitions on a memory card and formats them.

CWM: installation instructions

ClockworkMod is sewn into the internal memory of the device in place of the factory mode. In some cases, work is carried out on the gadget itself with access to Root rights, and in others - on a PC.

The article discusses such basic methods as Rom Manager, FastBoot, Rashr and Odin. For many devices, companies themselves produce separate utilities, for example, Acer Recovery Installer for Acer devices. CWM is embedded in the device memory on these devices also through ADB software, which is suitable for devices manufactured by HTC.

Rom Manager: Rooting and embedding

Rom Manager is a utility created by the CWM developers. It is available for download on Google Play Market. Allows you to install CWM Recovery on the device itself without using a computer and a USB cable. Before using it, you must root the device, that is, obtain administrator rights.

Obtaining Root rights

The procedure is simple and can be easily carried out using special software. As an example, we can take the Framaroot program. Anyone can navigate its simple and intuitive interface, even without instructions.

Download the app from the store and open it. In the drop-down line, give preference to the “Install SuperSU” or “Install SuperUser” item. Click on the drop-down window

Select a method for obtaining Root rights. Follow the advice - restart the device for the changes to take effect.

For the changes to take effect, restart the device

Launching Rom Manager

Now is the time to use the program:

Launch the software and click on the first Recovery section Setup, and then click on ClockworkMod Recovery. Select Recovery Setup

Find and select the device model from the list of available ones. If the model is not in the list, then this method of flashing Recovery is not suitable and you need to use another one. After confirming the action, the files will begin to download, as indicated by the progress bar. Next, a notification will pop up stating that you need to grant Root rights to the program. Then the CWM installation itself will be carried out. Click on ClockworkMod Recovery to install

Video: how to flash Recovery with Rom Manager

Although the method is easy, it has a drawback: it is not suitable for all devices, as mentioned earlier. Before you start using this method, it would be logical to first determine that this program is compatible with the gadget. The list is available on the official Rom Manager website.

FastBoot Mode: Complex Method

The CWM installation method using FastBoot will require skill from the user, as it is much more complex than the previous one. It runs not on the device, but on the computer. It is recommended to use it only if you already have skills in such operations. Before installation, you must download it to your computer or laptop. certain files. This list also includes the Android SDK platform, available for Windows, Mac and Linux.

Preparatory stage

What you need to have before installing CWM using FastBoot mode:

A computer with Windows OS and a USB cable to connect the device to the PC.

USB drivers for correct device detection. They can be downloaded from the official website of the manufacturer.

Android SDK platform.

Recovery file.

The Android SDK utility will help you install required packages Android SDK Tools and Android SDK Platform tools:

Go to the bottom official page. There will be three options. In this case, it is the Windows version. Click on tools_version-windows.zip.
Download the Anroid SDK zip archive for Windows from the official website

Extract all contents from the archive to drive C. Open and click on tools. The android file needed to download the packages directly is there. Double click on the file and the manager is open.
Find the android file in the unzipped folder and open

Check the box to the left of Android SDK Platform-tools and click Install 1 package.

Select Android SDK Platform-tools and click Install package

Standard Acceptance Request license agreement. Check the Accept License box and then click Install. The direct installation of the packages necessary for the firmware, which were mentioned earlier, will begin.
Accept the license agreement

After the installation process is complete, find platform-tools in tools_version-windows. It will contain important fastboot and adb files.
The fastboot and adb files are located in the tools_version-windows folder after installing the Android SDK Platform-tools package

What else needs to be done before starting the firmware itself? Judging by the list above, you need the recovery-clockwork.img file. This is one of the key tools for further work. Downloading it won't be difficult, but it doesn't end there. It is important to place this file in the platform-tools folder. For further convenience in the firmware, you need to rename it to recovery.img.

Place the file in the platform-tools folder

Get straight to the point!

Now everything is ready for the CWM firmware itself, so you can safely get to work. Below is a detailed description of the actions, in which it is quite difficult to get lost.

First, connect the device to be flashed to your computer via USB. At the same time, FastBoot mode is launched (a combination of the power and volume down keys). Although this combination works most often, it is not suitable for everyone. In some cases, this is the Home key and the same volume reduction. When the first option doesn't work out, nothing will happen if you use the second.
Start your device in FastBoot mode

The main procedure is performed on the command line. First you need to open it. In the Windows terminal window (press Win + R keys) write cmd command.
To open the command prompt, go to Start and type cmd

The command line is immediately ready to use. Type cd / immediately after the last entry and press Enter.
Type cd / and press Enter

Next, you need to go to the platform-tools folder in the terminal itself. The path to the folder may differ among users, so it is extremely important to use your own option so that the operation ends with a certain success. Copying the path from the window line would be the correct solution.

The next line in the black window should look like cd path_to_folder_platform-tools. Press Enter again.
Enter the command with the path to the folder

The next step is the adb devices command. It will help determine whether the PC sees the device. Next type adb reboot bootloader. Wait until the device turns on as a bootloader. Finally, go to the final part of the firmware: enter fastboot flash recovery recovery.img. and press Enter.
The adb devices command will help determine whether the PC sees the device

If successful, a message will appear. Check the installation the next time you restart the phone in recovery mode new firmware. If all is well, the device will enter ClockworkMod Recovery mode.

The level of complexity, as you can see, is high, so before the procedure it is strongly recommended to check that this method is suitable for the device, since it may not work in all gadgets. In practice, this method is good if the manufacturer of the device is HTC.

Rashr app

The installation method using Rashr is convenient and easy to perform; it is recommended for beginners. However, ironically, it also requires administrator rights. You can get them in a few steps. Detailed instructions were given earlier in the section on Rom Manager.

How to work with Rashr

First you need to download the application itself. It is located in free access in Play Market (Rashr - Flash Tool). You can also view the program on a third-party site, but you must beware of suspicious web pages so as not to catch a virus.

When the program is already on the phone, you need to open it and provide it with previously acquired Root rights upon request. Then everything is simple:

Select CWM Recovery. Click CWM Recovery

The software will provide available versions of Recovery for the given device being flashed, such as the touch ClockworkMod and the option with key control.
Select Recovery from the list of options available for your device

Choose the most suitable version and click Yes to confirm the download.
Click Yes to confirm download

After downloading, a notification will pop up that the new recovery has been successfully downloaded and installed. To go there, click Yes.
To go to Recovery, click Yes

Video: CWM and Rashr

Odin: solution for Samsung

The previous three methods are suitable for different models devices. The same method is effective for Samsung devices. This is a proprietary utility, so it cannot be used for devices from other manufacturers. There are many versions of this application. The latest one is Odin 3.09.

Here the standard factory version of Recovery is changed to a modified one using a PC, as with FastBoot:

Download Samsung Odin on the official site.
Download the Odin program on PC

Establish a connection between the PC and the gadget via a USB cable and switch the device to Download Mode. There are two options depending on the device model. If one doesn't work, another will definitely work:

• power/lock button and volume down (on older devices released before mid-2011);
• power/lock button, Home and volume down (all other devices).

Pressing the volume up button confirms entering recovery mode. Next, launch the already downloaded Odin program. A program window will open, where I will list available files for download. In the case of Recovery firmware, you need to check the box to the left of AP. In other versions of the software, the field may be called PDA.

Click the Start button and wait until the firmware is completed successfully.
Click the Start button and wait for the firmware to finish

How to enable CWM Recovery mode after flashing

After CWM mode was installed using one of the above methods, you need to check if it works. You can launch ClockworkMod Recovery:

by using ROM programs Manager by selecting the “Load Recovery Mode” section on its initial page;

by pressing the keys simultaneously after turning off the device. Combinations may vary depending on the model and manufacturer of the device. In most cases, these are the volume down and power buttons;

by using ADB programs via the adb reboot recovery button.

Possible difficulties

During the installation of an alternative Recovery Mode, in particular CWM, various difficulties and errors may arise. Which of them are the most common and how to solve them?

CWM Recovery does not recognize the memory card

CWM makes it possible to update your phone using an archive. When opening Recovery, the user sees a message that the flash card cannot be mounted. After installing another card, even with smaller volume memory problem disappears. The reason lies in the Windows system itself. The fact is that it diverges from card formatting standards. To ensure formatting is performed in accordance with the specification of SD/SDHC/SDXC flash cards, and not just in standard form, it is recommended to use specialized software, for example, SD Formatter.

The SD Formatter program allows you to correctly format the SD card

CWM does not see the internal memory of the device: problem solution

When the recovery files are located on the internal memory, and therefore can only be recovered from there, a problem may arise. When you connect the USB cable to the PC and enable “USB Debugging”, the program reports that Android device not detected and you need to enable “USB Debugging”.

To solve this problem:

Connect the device as a camera, not a storage device. If there are more available options, select them.

Install universal drivers.

Find a more suitable Recovery program for your device.

Recovery menu doesn't work

If at startup alternative mode recovery (volume + Home button or power) a picture appears with a lying robot, then the recovery was flashed, but when the device was restarted it was overwritten by the stock Recovery.

The problem is solved as follows.

Before flashing the Odin3 program, you need to uncheck the Auto restart checkbox and disconnect the cable after flashing. From Download mode on the device, go to recovery mode by pressing the volume up + home screen + power keys in sequence and hold them until the recovery menu appears. So you should get into the custom recovery menu anyway.

In it, select Reboot system now and then check Yes. This action will overwrite the stock recovery with a custom one and the “No command” error will be corrected.

Flash new mode Recovery means getting new ones functionality. Firmware methods vary in complexity, but ironically, the simplest of them require access to Root, that is, device administrator rights. When choosing a firmware method, you need to be guided by the phone model first. Rom Manager is not suitable for all devices. For HTC, the FastBoot method is more suitable, while for Samsung it would be more correct to choose Odin.