2. Where is the official OTA upgrade package after downloading?
It's here. Mobile phone storage and directory under OTA folder. When upgrading with a third-party REC, pay attention to taking it out. Zip upgrade package in. Ota folder, otherwise. OTA will be automatically deleted after the official rec upgrade fails.
3. Can 3.OTA upgrade cross versions?
Yes, the official OTA upgrade will automatically put all
Download the upgrade package to. Ota then brushes them in one by one. For example, if your version is 0530, then you can upgrade to 0630.
You will download two upgrade packages, one for 0624 (kernel number 8545) and one for 0630 (kernel number 8704). You take out the corresponding brush package and upgrade it in order with a third-party REC!
4. Why does 4.OTA upgrade fail?
The main reason for OTA upgrade failure is that you modified the system file, such as brushing the baseband that is not this version and brushing the GMS(google Service Framework) package, which may lead to OTA upgrade failure!
The OTA upgrade package will check the original file of the system before updating. If it is found that the signature is different from that of the upgrade package script file, it will report an error and prompt that the verification failed (when you brush the OTA upgrade package with a third-party rec, the error will display detailed information and the file failed to verify).
5. How to solve the failure of 5.OTA upgrade system file verification?
Two schemes: 1. Restore related system files to the original version of ROM.
2. Modify the script file in the OTA upgrade package and delete the related verification content! The specific operation method is as follows:
Open the zip upgrade package, enter the META-INF\com\google\android directory, modify the updater-script file and replace it, as shown in the following figure:
If you report an error when using a third-party REC to update the OTA package, you can find the corresponding statement in this script and kill it!
6. The so-called OTA upgrade after root will fail, make mistakes and so on.
I don't think so. To put it bluntly, ota upgrade is only to write files into the system partition and replace system files, while root operation is only to write several files into the system partition. One is the BIN directory.
Under su, the other is apk program, which is generally called authorization management (super user or supersu), and root failure is often caused by the SU file in the bin directory.
Linux kernel dislocation caused root to fail.
Before the ota upgrade, I will go to the bin directory to find Sue and make sure that this machine is already root. If it is already root, a scary warning will pop up. I think this is just an official immunity!