The situation when a smartphone stops responding to touches or gets stuck on the logo when loading is familiar to many device owners. In such cases, a standard reset through the settings menu becomes impossible, and the only option is to use personal computer. Connecting to a PC allows you to bypass the locked interface and send a command to completely clear the device's memory.
This method is often called a โhard reset,โ but unlike using the volume buttons, it gives the user more control over the process. You can select the operating mode, check the bootloader status, or even reflash the device if a simple reset does not help. The main advantage is the ability to control Android at a low level, when the operating system does not boot.
Before you begin, you need to prepare your workplace and make sure that all the necessary drivers are available. Improper preparation may result in the computer simply not recognizing your phone. We will look at two main tools: ADB (Android Debug Bridge) for working with the phone turned on and Fastboot for manipulations in bootloader mode.
Preparing tools and drivers for working with Android
The first step is to install the platform Android SDK Platform-Tools. This is an official set of utilities from Google, which contains all the necessary components to communicate with the device. Without this package, not a single command will be executed, since the Windows or macOS operating system simply will not understand what you want from it.
After downloading the archive from the developerโs website, you need to unpack it into a convenient folder, for example, the root of drive C. This is where the executable files adb.exe and fastboot.exe. It is important that the folder path does not contain Cyrillic characters, as this may cause errors when executing commands in the console.
โ ๏ธ Attention: Installing only ADB drivers is often insufficient. Fastboot mode may require separate USB drivers, which usually come bundled with firmware or are installed manually through the device manager.
The next critical step is to enable debugging mode on the smartphone itself. If the phone is at least partially responsive to presses, go to Settings โ About phone and quickly click on the build number 7 times. This activates the menu for developers, where you need to find the item USB debugging and move the switch to the active position.
When you connect the cable to the computer, a request to confirm debugging will appear on the phone screen. Be sure to click Allow, otherwise the computer will only have access to the file system (if available) but will not be able to send system commands. Without this confirmation, a reset via ADB is impossible.
โ๏ธ Preparing for reset
Resetting settings via the console using ADB
Usage method ADB suitable for cases when the phone turns on, shows the screensaver, but the sensor does not work or the system is stuck in a reboot loop. This method is less risky than working with the bootloader, since the command is sent through a running system shell.
First, open the command line in the folder with the utilities. In Windows, this can be done by holding Shift and right-clicking on an empty space in the folder, selecting โOpen PowerShell window hereโ or โOpen command windowโ. On macOS and Linux, simply launch a terminal and go to the tools directory.
Type command adb devices and press Enter. If everything is done correctly, you will see your device's serial number in the list. If it says unauthorizedinstead of the number, unlock the phone screen and confirm access. If the list is empty, check the cable or reinstall the drivers.
The reset command itself looks extremely simple, but its execution requires caution. Enter the following instruction:
adb reboot recovery
This command does not erase data instantly, but reboots the phone into Recovery Mode. From there, you'll be able to perform a reset using the volume buttons, which is often safer than blindly sending a format command. However, if you are confident in your actions, you can send a command to the wipe directly:
adb shell recovery --wipe_data
What to do if ADB does not see the device?
If the adb devices command does not return the serial number, try replacing the USB cable with the original one or using another USB 2.0 port on the motherboard. Also, in Windows Device Manager, check to see if there is a device with a yellow exclamation point under "Portable Devices" or "Other Devices." If it is, update the driver manually, specifying the folder with platform tools.
Using Fastboot mode for a complete cleanup
Mode Fastboot (or Bootloader Mode) is a deeper level of interaction with the device. It is used when the Android system is so damaged that Recovery mode is unavailable or does not start. Working in this mode allows you to erase memory sections directly.
To get into this mode, you usually need to turn off the phone and hold down the button combination (often Volume Down + Power) when connecting to a PC. An Android robot image or text menu will appear on the screen. After this, enter the connection test command in the computer console:
fastboot devices
If the device is displayed, you can begin cleaning. The command for resetting user data in Fastboot mode is as follows:
fastboot -w
Flag -w means wipe (erase). This command will wipe the userdata and cachepartitions, returning the phone to its factory state. The process may take several minutes, during which technical logs may appear on the screen. Do not disconnect the cable until the message appears finished.
โ ๏ธ Attention: The fastboot -w command permanently deletes all personal data, including photos, contacts and applications. It is impossible to restore them after executing this command using standard means.
It is important to note that on some modern smartphones, especially from manufacturers like Huawei or Honor, the Fastboot reset command may be blocked by the manufacturer for security reasons. In such cases, the device will simply ignore the command or generate an error.
Specifics of working with different smartphone manufacturers
Although the ADB and Fastboot protocols are standard, each manufacturer makes its own adjustments to the process. This applies to both methods of entering special modes and requirements for locking the bootloader. Understanding these nuances will save you a lot of time and nerves.
Devices from Samsung often require the use of a specific mode Download Mode for firmware via Odin, but for resetting data via a PC, standard ADB works well. However, if protection is enabled, some low-level commands may not be available without unlocking the bootloader, which will trigger the security trigger. Smartphones have strict restrictions on working with Fastboot. By default, the bootloader is locked and write or erase commands may be disabled. Full control often requires official unlocking of the bootloader through the manufacturer's servers, which takes up to 7 days of waiting. Knox, some low-level commands may not be available without unlocking the bootloader, which will trigger a security trigger.
Smartphones Xiaomi And Poco have strict restrictions on working with Fastboot. By default, the bootloader is locked and write or erase commands may be disabled. Full control often requires official unlocking of the bootloader through the manufacturer's servers, which takes up to 7 days of waiting.
| Brand | Login to Fastboot | Reset features |
|---|---|---|
| Samsung | Volume Down + Bixby + Power | Often requires Odin for a full reset |
| Xiaomi | Volume Down + Power | Needs bootloader unlocking |
| Pixel / Nexus | Volume Down + Power | Full support for standard commands |
| OnePlus | Volume Up + Power | Fast login, standard Fastboot |
Device owners Google Pixel are the luckiest: these phones were originally created for developers, so support for ADB and Fastboot commands is implemented as fully as possible and without unnecessary restrictions. The reset is quick and predictable.
If you do not know the exact combination of buttons for your smartphone, try alternately holding Volume Down or Up together with the Power button when connecting to a PC. One of the options will definitely put the device into driver loading mode.
Solving problems with connection and device recognition
The most common problem when trying to reset is that the computer does not see the phone. This can be caused by both physical cable faults and software driver conflicts in the operating system. Diagnostics should start with the simplest.
Try using a different USB port, preferably located directly on the motherboard (at the back of the system unit), and not on the front panel or through a USB hub. USB 3.0 (blue) ports are sometimes unstable with older devices, so it makes sense to switch to a USB 2.0 (black) port.
If Device Manager shows "Unknown Device" with error code 43 or 10, try manually updating the driver. Select "Update driver" โ "Browse this computer for drivers" โ "Select a driver from the list of available drivers." In the list, find MTP USB Device or Android ADB Interface.
โ ๏ธ Attention: Antivirus apps and firewalls sometimes block the ADB connection, considering it suspicious activity. During the reset procedure, it is recommended to temporarily disable the protection.
It is also worth checking whether the โCharge Onlyโ mode is enabled on the phone. When connecting the cable, lower the notification shade and select file transfer mode (MTP) or PTP. Although this is not always critical for ADB, the correct data exchange mode improves the stability of the connection.
A stable connection is the key to a successful reset. If the command takes a long time to complete and freezes, most likely the problem is with the cable or USB port, and not with the smartphone itself.
Data recovery and initial setup after a reset
After the reset command is successfully completed, the phone will reboot and begin the initial setup process as if you just took it out of the box. You have to select a language, connect to Wi-Fi and log into your account Google.
If you made a backup in the Google Drive cloud before resetting, the system will offer to restore applications and settings. This process may take a significant amount of time depending on the amount of data and internet speed. Do not interrupt it to avoid conflicts in the operation of the system.
It is important to remember about theft protection FRP (Factory Reset Protection). After the reset, the phone will require you to enter the password for the Google account that was synchronized with the device before the reset. This is a security measure, and it is extremely difficult to bypass it without the legitimate data of the owner.
If the phone asks for an account that you do not remember or do not know the password, you will not be able to gain access to the device. In this case, the only solution is to restore access to the account through the Google website on another device.
Is it possible to reset the phone if it is completely turned off?
No, for ADB and Fastboot to work, the phone must be at least in download mode. If the device does not turn on at all (black screen, no response to buttons), the problem is most likely a hardware one (dead battery, faulty board), and a soft reset via a computer will not help.
Will a reset via a computer delete your Google account?
A reset will delete account data from the device, but the account itself will remain active on Google servers. However, due to FRP protection, the first time you set up after a reset, you will still have to enter the login and password of this account to confirm ownership.
Is it safe to use third-party apps to reset?
Using unverified software carries risks. Google's official ADB and Fastboot tools are the most secure. Third-party utilities may contain malware or work incorrectly with specific phone models, which will lead to the device becoming bricked.
What to do if after resetting the phone is stuck on the logo?
This may mean damage to the system partition. Try entering Recovery mode again and resetting the cache partition (Wipe Cache Partition). If this does not help, you will need to completely flash the device using the official firmware.