10,000 - 50,000 downloadsAdd this app to your lists
+ By scary alien
So, I decided to try to write an app that would help folks figure-out what the issues might be so that they can get their OTA update installed.
The OTA Verifier app can be used to evaluate an over-the-air (OTA) update.zip or other flashable .zip file before you attempt the install or afterwards to help you figure-out why the installation may have failed. OTA Verifier will point-out what files and conditions are being tested so that you can more easily attempt to correct these issues.
Q: Do I have to be rooted to use this?
A: No, but rooted devices will have more conditions that the app will be able to test/evalute because it will have access to protected files that non-rooted devices don't.
Q: Will the app actually do the installation or change anything on my device?
A: No. The app will only evaluate the expressions and conditions contained inside the updater-script file inside the .zip file that's trying to be installed. None of the functions or commands that try to modify your device (i.e., delete/patch/format/extract, etc.) will be evaluated or executed. The app basically operates in "read-only" mode with respect to the .zip file being evaluated.
Q: Will this app work on older devices or flashable .zip files that use the amend update-script files?
A: No, this app evaluates and interprets the newer edify updater-script files (notice the "r" in "updater").
How do I use this app?
1. Install and launch the app
2. Click the "Select File" button and navigate to desired .zip file
3. Long-press (press and hold) the file entry for the desired .zip file
4. Click the "Verify OTA .zip" file pop-up
5. Wait for the app to process the file (should take under a minute, depending on your device)
6. View the displayed results (text will also be copied to the clipboard)
1. Savvy root users probably already know that after a failed .zip file installation, you should be able to view the /cache/recovery/last_log file to view the information about what might have failed. OTA Verifier will try to uncover all of the issues and not just the first one that causes the installation to fail.
2. While I wrote this app principally to evaluate OTA update.zip files, the edify updater-script files are used and written by ROM devs and others who created flashable .zip files. This app can be used to evaluate those file's updater-script files, too.
How does this all work?
Here's the basic outline/structure of what the app does:
1. the .zip file is selected by the user via the file selector
2. the updater-script file is extracted from the META-INF/com/google/android folder in the .zip file
3. this updater-script file is parsed and converted into reverse polish notation (RPN) for execution
4. edify functions that might modify your device are NOT evaluated
5. note: the update-binary executable is not used by or involved in this app; the edify script interpreter that the app uses was written by me, in Java, specifically for this app
6. the remaining edify script functions that test conditions are evaluated using an operand/operator stack from the RPN expression parsed from the updater-script statements
7. expressions that fail (return a null-string) or are bypassed (usually because a resource (file/partition) is protected/secured against read-access) are reported for the user
8. after the entire script has been processed, the results are displayed in a pop-up window on the device and the text of those results are copied to the clipboard
Questions? Contact me at firstname.lastname@example.org
Keywords: OTA, over-the-air update, updater-script, edify, amend, update-binary
Tags: hot to add ota zip to, ota verifier, testing on ota, betazip, why cause ota failed.
[version 2.4 - 18-June-2014]:
- change (back) apply_patch_space logic to check free space on /cache instead of /system
[version 2.3 - 10-June-2014]:
- fix issue w/apply_patch_check tests on read/access-protected files and partitions (for those with root access, of course)