Hello,
I've been researching whole day about .bin OTA updates, but I didn't find a solution.
I own a Galaxy Tab 8.9 P7300, which has some OTA updates (ICS!). Great.
My tablet has an unlocked bootloader so I can flash in APX mode in case of a hard brick, even better.
The .bin file's structure is unknown, it contains the .delta files and the info file (this one is placed at the end), like the .zip OTA updates. But it also includes a redbend_ua binary.
My question is, what, when and where splits and executes this .bin file & performs the update?
Some devices allow "reboot arm11_fota" into a bootmode that executes fota.rc (and /sbin/redbend_ua). But that needs the .delta files in /cache/fota. And why would they include another redbend_ua in the OTA package?
I've been also thinking about dd-ing the .bin to /preload, though I have no idea what effect would it have.
Ideas?
I've been researching whole day about .bin OTA updates, but I didn't find a solution.
I own a Galaxy Tab 8.9 P7300, which has some OTA updates (ICS!). Great.
My tablet has an unlocked bootloader so I can flash in APX mode in case of a hard brick, even better.
The .bin file's structure is unknown, it contains the .delta files and the info file (this one is placed at the end), like the .zip OTA updates. But it also includes a redbend_ua binary.
My question is, what, when and where splits and executes this .bin file & performs the update?
Some devices allow "reboot arm11_fota" into a bootmode that executes fota.rc (and /sbin/redbend_ua). But that needs the .delta files in /cache/fota. And why would they include another redbend_ua in the OTA package?
I've been also thinking about dd-ing the .bin to /preload, though I have no idea what effect would it have.
Ideas?