Overview - There are various models of infoTMIC devices supported by different manufacturers/distributors however, they all seem to utilize the same base firmware and automatic update process.
The are many currently known infoTMIC CPU based devices are:
7" I7Y-MP1 - Superpad i7
7" Zenithink ZT180 v1
7" Zenithink
7" Disco 6000
7" Sylvania SYNET7LP/SYTABEX7, SYTABBL7/SYTABBL7-0608/SYTABEX7-2, SYTAB7MX
7" AIRIS OnePAD 700 Model: TAB700x iMAPx210 supported in Spain
8" Klu by Curtis International LT8025
ICAN! 10 - 10" Tablet PC
10" FlyTouch II, SuperPAD, WOWpad, WWE10, PC1002I, HyPE-Pad, ZH10X2, APad GF10, CEM111, Daystar MD10, Careeror CM10104
I10Y
10" Sylvania SYTAB10MT (SYNET10LP), SYTAB10ST
10" SuperPAD II
10" Zenithink ZT180 v2
Each of these devices is best identified by their Hardware ID "hwver" as the information displayed on the "Settings > About device" screen is often incorrect since the "Model number" is hard coded in to the Settings application (.apk) or extracted from the build.prop.
Example - DeviceInfoSettings.smali in Settings.apk from SuperPad decoded with android-apktool
The infoTMIC tablet's Hardware ID "hwver" is determined by reviewing the "Kernel command line" output of either shell command "dmesg" or "cat /proc/cmdline".
On some devices, the Hardware ID "hwver" is displayed on the initial boot screen in the lower right corner followed by the U0 - u-boot-nand.bin version in parenthesis (###).
dmesg - Example from SuperPad "WWE10" initial firmware did not include "hwver=" output, it was added in a later firmware update.
Note: On some of the newer Sylvania tablets the update server is coded in the build prop - persist.sys.server=dg-support2a.com
The #'s after "data=" are subsituted with the values returned for the "hwver=" as seen in "dmesg" or "cat /proc/cmdline". The "vcode=" is the Version code are returned by "getprop ro.versioncode" if it exists in the build.prop.
If an update file (*.ius) is available, a download link is returned. Preceding the link separated by a pipe "|" symbol is the current available version. If nothing is available or the update server database is "turned off" a "1" is returned. Many times no file was identified but by using the previous update files names the additional files were identified.
The currently known InfoTM Update Wrap (IUW) multi-part update files for each of the various Hardward ID's "hwver" are listed below.
The multi-part update file contains an IUW header, U0 - u-boot-nand.bin, UBOOT, RD - RAMDISK, LK - KERNEL, ADR-USER - UserData, and ADR-AS - system.img. The Wrap Information details can be viewed for each *.ius using the IUW Version 1.2 InfoTM Update Wrap Tool attached in post #2.
WARNING - Burning the incorrect update file (more specifically the U0 "u-boot-nand.bin" image) can brick the device.
Most of the files above are Android 2.2 "Froyo", however some Android 2.1update1 files are the only ones identified for a specific Hardware ID.
These are infoTMIC supplied updates as directed by the distributor, so not all devices have not been updated.
Query the update server to see if an update link is returned. If the server is "offline" or no update is posted a "1" is returned.
Many of the Hardware ID's "hwver" included below do NOT exist but were made up using the sequence of known "hwver" in order to search for previously unknown files.
If no update link was returned using the GET command above, and since it is not possible to browse the update server directories, one way to find an update is to try different variations of known update files names and apply them to another hwver.
Many but not all of the links to the update files all follow the same pattern. It would be nice if they would all use the same naming nomenclature.
"http : //222.73.93.45/update/" + the results from /proc/cmdline where hwver=##.#.#.# + "/" and the file name *.ius.
By concatenating the various parts together using different hwver and update file names, it will produce a link like the EXAMPLE below where the hwver is 11.2.1.8 and using the structure of the file names above.
Attached is Version 1.2 of the InfoTM Update Wrap tools.
This utility is used to burn updates to various infoTMIC powered tablets.
The utility has a "Boot Disk" option which creates a bootable microSD card to update the tablet directly from the infoTM Update Wrap file (*.ius).
The utility also has a "Link USB" option which allows the tablet to be connected to a PC through the tablet's OTG port using a USB 2.0 Male to Mini Cable.
The USB Mode: has two (2) methods: Easy burn or Expert Burn.
Easy burn - Utilizes the infoTM Update Wrap file (*.ius) Expert burn - Allows for the selection of the various parts of the firmware
The configuration files included with this version of the update tools provide insight to the naming nomenclature of the "FileNum:" (Firmware Version) above.
It is now obvious how the various Hardware ID's "hwver" are derived based on Company and config_board.
Instructions on how to use the "InfoTM Update Wrap tools" utility have been copied directly from "Introduction of IUW burning-20110118.docx" which was included in a various previous update file (*.ius) archives and posted here - Introduction of IUW Burning Tools
androidtablets.net Member vio has released an application "Ius Editor" that extracts images from InfoTM Update Wrap (*.ius) multi-part update files.
Some of the images still require manual removal of the uImage header, uncompressing, and unyaffs but additional functionality is planned. See post #71 in Custom Sylvania ROM development for detail and download.
An updated version of the InfoTM Update Wrap (.ius) editor application IusEdit_0.03 has been posted by vio at androidtablets.net with the following description.
Quote:
It allows adding and removing for images as well as saving the modified IUS file. You can also edit version info, magic number and checksum value. I had little time to test it, but it is at least consistent with itself - I have exported the "system" image, removed the image from IUS file, saved it, then added the image from the previously created "system.img" and the final file was binary identical with the original one.
PLEASE USE WITH CARE! I don't have a solution for computing the checksum bytes, as noted above, so the resulting IUS file might be deemed incorrect by the flashing application. Also, please note that I don't have too much validation code added, so you could technically create a IUS file containing 2 "U0" images, or some other invalid configuration. Try to avoid any "exotic" configurations if you decide to try to use it.
I've updated the editor with the new image types found by cfrockit (thanks). Plus, added the option to change the order of the images inside the file (it might be important) and a quick sort button that arrange images by type.
I also added a protection when adding images, so it is no longer possible to add more images of the same type.
In regards with checksum bytes, still no progress. I've run multiple algorithms (including a few CRC32 implementations) over both the header and the image part of the file, but the results are not close to the expected values.
The visual inspection of the "U0" image suggests that there is indeed a "header crc" and a "data crc", but so far I couldn't break the code.
Hi! I just bought an superpad (1ghz, 256MB Ram...) On startup, bottom right it shows 0.6.3.2 (677). I tried to flash froyo with an SD card and I ended with a brick in my hands. Can anybody help me?
Hi! I just bought an superpad (1ghz, 256MB Ram...) On startup, bottom right it shows 0.6.3.2 (677). I tried to flash froyo with an SD card and I ended with a brick in my hands. Can anybody help me?
ezequias, 0.6.3.2 is a previously unknown Hardware ID "hwver" as well as the 677 version of U0 u-boot-nand.bin.
The update server doesn't provide a current upgrade file link and randomly searching various known file names didn't provide any results.
In the recently discovered IUW Version 1.2 InfoTM Update Wrap tools one of the "initialization" .ini files strings references "WWE8 down from FTP" however, we're not aware of an infoTMIC FTP update file server yet.
I have updated the Original Post (OP) to include this Hardware ID "hwver".
ezequias, 0.6.3.2 is a previously unknown Hardware ID "hwver" as well as the 677 version of U0 u-boot-nand.bin.
The update server doesn't provide a current upgrade file link and randomly searching various known file names didn't provide any results.
In the recently discovered IUW Version 1.2 InfoTM Update Wrap tools one of the "initialization" .ini files strings references "WWE8 down from FTP" however, we're not aware of an infoTMIC FTP update file server yet.
I have updated the Original Post (OP) to include this Hardware ID "hwver".
Updated Original Post (OP) to include two recently identified InfoTM Update Wrap files.
11.2.1.5.2.0_beta5.ius
11.2.1.8.2.0_beta5.ius
Caution: Use this information at your own risk. It is being provided by users of the device NOT the manufacturer/distributor.
Warning: Confirm the tablets Hardware ID "hwver" as described to ensure you have the appropriate file before updating.
Note: The incorrect update file (*.ius) CANNOT / SHOULD NOT be burned to the device. If you can't determine the "hwver" attempting to burn with an incorrect update file may / will brick the tablet.
The update is applied using an older method requiring a WinImage disk image, however the disk image includes a complete InfoTM Update Wrap (.ius) file.
Caution: Use of this update on other tablets may cause irreparable damage (brick) to the device.
Would you like to know one of the things that really annoys me on a daily basis? Tough, … more
XDA Developers was founded by developers, for developers. It is now a valuable resource for people who want to make the most of their mobile devices, from customizing the look and feel to adding new functionality. Are you a developer?
New: XDA launches forum for app developers. Discuss coding, tools, marketing, and more.
>
infoTMIC Hardware ID's "hwver" and updates (*.ius)
Print
Email
infoTMIC Hardware ID's "hwver" and updates (*.ius)
View Profile
View Forum Posts
Subscribe
