As we all know, Google's princesses (nexus series) have been born with high cost performance and bootloaders (unlocked, all kinds of ROMs take all, such as the famous top brand CM AOKP, MIUI, etc.) are sought after by Android fans, but this cannot prevent the existence of many official controls. For example, the iPhone does not escape from prison, and the accessibility of the nexus without Root is greatly reduced, so the number of users using official ROM plus Root is very high.

The knotty problem is that the official ROM with root cannot be OTA, that is to say, the official upgrade patch can only be received and cannot be used, and cannot enjoy the benefits of the fastest upgrade of the prince, losing the significance of using the prince.

Today we are going to make a painless OTA upgrade plan after the prince machine derailed! To find a solution, we must first find the crux of OTA's inability. This article takes the Nexus 4 as an example. Other Nexus models are universal.

The official OTA needs to verify whether the files in the recovery and system areas are native and complete. Recall the steps of Root. First, the bootloader is unlocked, and the third-party recovery is imported. Finally, the root file is imported.

Unlocking the Bootloader does not affect the OTA, but the recovery change will affect the OTA, and the root file will disappear after the OTA, that is, the root will be removed. Some OTAs also need to verify the baseband. If you have brushed the baseband, please brush back the version consistent with the firmware.

OTA verification can be completed by performing a small operation on the recovery and root files.

For the root part, we use the survival mode of the SuperSU pro version (the root will be self repaired after OTA). For non professional SuperSU users, please download Install and upgrade to Professional Edition, and open the survival mode of Professional Edition.

Now let's process the recovery section, download Install and open USB debugging on the mobile phone. For example, users of 4.2.2 and above, please verify the computer to ensure that it can be connected for debugging. The verification steps can be OEM, such as pea pods. After connecting the phone, call the installed Nexus Root Toolkit and select the correct device and system version.

Click Apply after confirmation

Click the Launch button of advanced tools in the next interface

Select the Stock Recovery button of recovery in the pop-up interface

At this time, a confirmation dialog will pop up, and you can select OK. If the prompt of fastboot device not found appears, please keep the prompt interface, unplug the phone from the computer, and manually restart to the bootloader interface. After shutdown, press and hold the two volume keys together with the power key until the bootloader interface appears. Connect the phone to the computer again, and click OK in the prompt interface to try again

If there is no response for a long time, please open the task manager in the computer to find Adb.exe, and kill the process until a smiling face of recovery completion appears

To ensure that everything is safe, enter the bootloader mode again, select recovery, and confirm whether the robot falls to the ground as shown in the following figure

Press and hold the power key and volume to enter recovery, and select reboot system now to restart the device

Return to the mobile desktop again and click the system upgrade button

After the upgrade is completed, it is finally completed, and it shows that SuperSU has automatically restored access rights. In this way, it is full of blood and blue, and will not lose any data. Check the system, and it has been updated to the latest version.

Finally, I would like to remind you that deleting the built-in programs in the system will also affect the OTA. You can use software such as disabling in the system or freezing titanium backup to achieve the same purpose.

Learn more about new cool devices, stay tuned