How to update Android to version 7.0 Nougat

Many users still use devices released during the heyday of the Android 6.0 Marshmallow ecosystem and want to gain access to the functions of the newer operating system. Upgrading to Android 7.0 Nougat enables multi-window mode, improved notification management, and increased energy efficiency thanks to Doze technology. However, the process of migrating to this version in modern realities requires a special approach, since the official update servers for most older models have long been disabled.

Before you begin any manipulations with the software, you need to clearly understand the risks. Installing outdated firmware or using custom solutions can lead to loss of warranty, although for devices of this age this is no longer relevant, or to complete failure of the gadget. Smartphones Different manufacturers have unique procedures for unlocking the bootloader and installing recovery, so there is no universal "Update" button for everyone.

In this article we will analyze in detail all the legal and technical ways to obtain the seventh version of Android. You will learn how to check for official patches, where to look for custom builds, and what tools you will need for manual installation. Remember that any flashing requires preliminary preparation of data and an understanding of the architecture of your device.

Checking official support and compatibility

The first step should always be to check the possibility of receiving an update over the air (OTA). Despite the age of the system, some carriers or regional divisions of brands may have delayed the release, and there is still a chance to catch the official package. To do this, go to the menu Settings → About phone → System update and click the check button.

If the system reports that you are using the latest available version, this does not always mean a dead end. Manufacturers often release updates in stages for different regions. It is possible that your device is locked to a specific operator, which is blocking the receipt of new software versions. In this case, changing the region in the settings or resetting the network parameters sometimes helps to “wake up” the update server.

There is a list of devices that are guaranteed to have received the update from the manufacturer. If your model is not in this list, you will not be able to update officially. Nougat from the manufacturer. If your model is not on this list, you will not be able to update officially.

• 📱 Google Nexus 5X, 6P and Pixel (first generation)
• 📱 Samsung Galaxy S7, S7 Edge and Note 7
• 📱 Motorola Moto G4, G4 Plus and Moto X Play LG G5, V20 and some K series models data-i="49">It is also worth considering the amount of internal memory. To install Android 7.0 correctly, at least 2-3 GB of free space is required, since the installation package must be unpacked before use. If the memory is full, the system simply will not be able to complete the file verification process.
• 📱 LG G5, V20 and some K series models

⚠️ Attention: An attempt to install official firmware from another model or region through the engineering menu may lead to the device being “bricked” due to incompatibility of modem drivers.

It is also worth considering the amount of internal memory. To install Android 7.0 correctly, at least 2-3 GB of free space is required, since the installation package must be unpacked before use. If the memory is full, the system simply will not be able to complete the file verification process.

Preparing the device for flashing

If the official path is closed, you will have to resort to manual installation. This stage is critically important, since any errors during the preparation stage may make further system recovery impossible. The first step is to create a complete backup of all personal data, since the process of unlocking the bootloader invariably leads to a complete reset of the device to factory settings.

You will need to enable USB debugging mode. Go to Settings → About phone and click on the "Build number" item 7 times to activate the menu for developers. Then in the section that appears For developers activate the switch USB debugging. Without this option, the computer will not be able to send commands to the device via the ADB interface.

Next, you need to install the drivers for your smartphone on your computer. For devices on Qualcomm chips these are often Qualcomm USB Drivers, for MediaTek - SP Drivers, and for Samsung - special Odin drivers. Incorrectly installed drivers are the cause of 90% of flashing failures, when the computer simply does not see the phone in bootloader mode.

Don't forget to check the integrity of the downloaded firmware file. Often files are damaged during download, and attempting to install a damaged archive will result in a verification error in recovery. Use the hash sums (MD5 or SHA-1) provided by the firmware developer for verification.

Installation via stock Recovery (Official OTA Zip)

If you found an official update file in ZIP format, but the automatic update does not work, you can try installing it manually through the stock recovery menu. This method is safer than custom solutions, since it does not require unlocking the bootloader and maintaining the factory warranty (conditional).

Copy the downloaded update file to the root of the device’s internal memory or to an SD card. It is important that the file is located in the root directory, and not in folders, and has an original name, if required by the specifics of your manufacturer.

Turn off the smartphone and enter Recovery mode. The key combination depends on the model: most often it is Volume Up + Power or Volume Down + Power. In the menu that appears, select Apply update from ADB or Apply update from SD card.

Action	Key combination	Description
Login to Recovery	Vol + Power	Standard for most brands
Selecting a menu item	Volume buttons	Moving the cursor up/down
Confirmation	Power button	Start the selected operation
Exit/Reboot	Reboot system now	Complete recovery

If you chose installation from a memory card, the system will find ZIP archive and will ask you to confirm the installation. After confirmation, the verification and unpacking process will begin. The screen may go dark and turn on several times - this is normal.

Using custom Recovery and firmware

For devices that have not officially received Android 7.0, the only option is to install custom firmwares such as LineageOS, Resurrection Remix or Paranoid Android. These assemblies are based on the AOSP source code and are optimized by enthusiasts for specific hardware.

To install such systems, you will need to replace the stock recovery with a custom one, most often TWRP (Team Win Recovery Project). The process begins with unlocking the bootloader using the Fastboot command. Connect the phone to the PC in bootloader mode and enter the command:

fastboot oem unlock

Or, for some new devices:

fastboot flashing unlock

After unlocking the bootloader via Fastboot, you need to flash the recovery image:

fastboot flash recovery twrp-image.img

Now, by logging into TWRP, you will have access to advanced features: installing ZIP archives from any signing, creating full backups (Nandroid) and cleaning partitions. Before installing a new system, be sure to perform a full Wipe: Data, Cache, Dalvik/ART Cache sections. It is not necessary to clear the system partition if you are simply updating from above, but for the purity of the experiment it is recommended to format it too.

⚠️ Attention: Unlocking the bootloader irreversibly erases all data from the device. Make sure you save photos, contacts and messages before executing the unlock command.

When choosing custom firmware, pay attention to the build status: Stable (stable), Nightly (night/test) or Beta. For everyday use, it is better to choose Stable, even if it was released later.

What are GApps and why you need them?

Custom firmware is often supplied without Google services (GApps). This is pure Android without the Play store, maps and synchronization. To use familiar applications, you need to immediately after installing the system, without rebooting, flash a separate ZIP archive with the GApps package corresponding to the version of Android 7.0 and the processor architecture (ARM, ARM64 or x86).

Firmware via computer (Odin, SP Flash Tool, Fastboot)

Some manufacturers, including in particular Samsung and devices on chips MediaTekhave specific tools for firmware that work only from a computer. For Samsung, the Odin app is used, into which BL, AP, CP and CSC files are loaded.

For MediaTek devices, the SP Flash Tool utility is used. It allows you to flash the device even when it is turned off (BROM mode), which is useful if the phone does not turn on. However, working with this tool requires extreme caution: choosing the wrong scatter file or formatting format can change the IMEI or damage the NVRAM partition.

Google Pixel and Nexus devices, as well as many other Android smartphones, are easiest to flash using a clean Fastboot. The unpacked firmware image contains a script flash-all.bat (for Windows) or flash-all.sh (for Linux/Mac). Running this script automatically clears partitions and writes all images (boot, system, recovery, userdata) to the phone memory.

• 💻 Make sure that the USB cable is original and supports data transfer, and not just charging.
• 💻 Disable your antivirus and firewall during the firmware update, they may block access to ports.
• 💻 Do not use USB hubs, connect the phone directly to the motherboard port (on the back of the system unit).

During the process of flashing the firmware via a PC, do not touch the cable or press the buttons on the phone. Interrupting data recording into flash memory is the surest way to get a “brick” that will have to be restored through a programmer or service center.

Possible errors and ways to eliminate them

Even if you strictly follow the instructions, errors may occur. One of the most common is error 7 in TWRP when installing an update. It means that the installation script cannot find the required Android version or an incompatible build. This can be solved by updating the recovery itself to the latest version or using a special patch.

Another common problem is “Bootloop” (cyclic reboot). The phone turns on, shows the logo and reboots again. This can often be cured by logging into Recovery and clearing the Cache and Dalvik partitions. If it doesn’t help, a complete flashing with Data formatting is required.

Users are also faced with a lack of network or non-working Wi-Fi after installing custom firmware. This indicates incompatibility of the modem part (Radio/Modem). In such cases, you need to separately flash the stock modem and bootloader from the original firmware of your model, leaving the custom system.

⚠️ Attention: If after flashing the device does not turn on for more than 15 minutes and does not respond to buttons, the boot partition may have been damaged. Try to force restart the device by holding down the power and volume buttons for 10-20 seconds.

Remember that the developer community is constantly updating its creations. What worked a month ago may require new security patches today. Always read the latest comments on the forum (for example, 4PDA or XDA Developers) before downloading the file.

Frequently asked questions (FAQ)

Is it possible to update to Android 7.0 without losing data?

When updating over the air (OTA) or via stock Recovery data is usually saved. However, when unlocking the bootloader, installing a custom recovery, or switching to custom firmware, a complete data reset occurs in 100% of cases. Always make a backup copy.

Is it safe to use custom firmware for banking applications?

The default is no. An unlocked bootloader and the presence of root access violate the integrity of the security system (SafetyNet), which is why banking applications and Google Pay may not work. However, there are methods of hiding these facts (Magisk Hide), but this is an arms race with bank security systems.

What to do if after an update the phone quickly runs out of power?

After a major update, the system requires time (from 1 to 3 days) to optimize applications and rebuild databases. During this period, increased battery consumption is normal. If the problem persists, try resetting the settings to factory settings or flashing the device completely (Clean Install).

Is it possible to return to the old version of Android after updating?

Yes, it is possible, but the procedure is complicated. You will need to find a complete dump of the stock firmware of your model (preferably the version you were on) and flash it through your computer (Fastboot/Odin). There is no simple rollback in the settings menu.