I have a QTAQZ3 currently running 4.2.2. I captured the OTA url and downloaded an update bin file. I'm not exactly sure how bins compare to flashable zips, nor do I know what to do with a bin file. It seems as though this file has been hard to come by. I am hoping that by posting it, someone with the right know-how can help us fix all these bricked tablets.
https://drive.google.com/open?id=1LmyrA3eGcVL3sCMB3okBdsoqA0Gv5RZE
Using the Unix
file
tool reveals that .bin file to be a java archive:
Code:
$ file QZ3_31F27_0423_to_QZ3_31F28_0415.bin
QZ3_31F27_0423_to_QZ3_31F28_0415.bin: Java archive data (JAR)
So it can be opened & extracted as a regular .zip archive. The bundled manifest hints at an exported APK created with the .bin filename extension:
Manifest-Version: 1.0
Created-By: 1.0 (Android SignApk)
Contained within the archive are two main files:
delta.bin
&
recovery.bin
. It is evident which file is intended for the recovery partition. But I don't know what
delta.bin
is used for.
I don't know how OTA updates work, but it appears that it is an installable Android package whose contents are organized for the OTA updater to handle. I'm guessing that this bin/apk/zip archive is actually what is considered a "flashable zip", containing the binaries to be flashed to partitions by the updater or recovery utility. The contained .bin files can likely be extracted from the archive & flashed manually with
fastboot
:
Code:
$ file delta.bin recovery.bin
delta.bin: FoxPro FPT, blocks size 256, next free block index 1297241676, field type 0
recovery.bin: FoxPro FPT, blocks size 256, next free block index 1297241676, field type 0
I may get my bricked QTAQZ3 out eventually & see if I can flash these files.
--- EDIT ---
I could be wrong about it being a flashable zip. I downloaded
this sample TWRP flashable zip & it is a standard .zip archive (not jar/apk). It similarly contains a
META-INF
directory. But instead of only including signatures/certificates this directory houses the binary data to be installed & the script to execute installation instructions. It's possible they are both valid "flashable zip" packages & the updater/utility knows how handle both formats.