11.2.1.8.2.0_beta5.ius - SYNET7LP update Hardware ID "hwver" 11.2.1.8

[cfrockit]

Thanks to st0ne's post in the Custom Sylvania ROM development thread, using the file naming pattern a SYNET7LP Hardware ID "hwver=11.2.1.8" 11.2.1.8.2.0_beta5.ius update file can be download even though the update server in not returning an update link when queried.

Substitute the "hwver" in the known update server GET command with the new file name to pull the InfoTMIC Update Wrap (.ius) file.

Post any observations/comment/warnings.

The update file appears to be the same image as shipped on newly purchased/repaired/replaced tablets.



build.prop

# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=FRF85B
ro.build.display.id=FRF85B
ro.build.version.incremental=eng.liuqi.20110221.141106 [COLOR=#0000ff]< Note date[/COLOR]
ro.build.version.sdk=8
ro.build.version.codename=REL
ro.build.version.release=2.2
ro.build.date=2011å¹´ 02æ&#339;&#710; 21æ&#8212;¥ æ&#732;&#376;æ&#339;&#376;ä¸&#8364; 14:11:37 CST
ro.build.date.utc=1298268697
ro.build.type=user
ro.build.user=liuqi
ro.build.host=liuqi-desktop
ro.build.tags=test-keys
ro.product.model=p7901ui
ro.product.brand=generic
ro.product.name=p7901ui
ro.product.device=p7901ui
ro.product.board=
ro.product.cpu.abi=armeabi
ro.product.manufacturer=unknown
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=imap210
# ro.build.product is obsolete; use ro.product.device
ro.build.product=p7901ui
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=p7901ui-user 2.2 FRF85B eng.liuqi.20110221.141106 test-keys
ro.build.fingerprint=generic/p7901ui/p7901ui/:2.2/FRF85B/eng.liuqi.20110221.141106:user/test-keys
# end build properties

#
# ADDITIONAL_BUILD_PROPERTIES
#                                                     [COLOR=#0000ff]< Note: No ro.versioncode ?[/COLOR]
persist.app2sd.enabled=0
ro.suspend.unloadWifiDriver=true
ro.config.notification_sound=OnTheHunt.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
media.stagefright.enable-player=true
media.stagefright.enable-meta=true
media.stagefright.enable-scan=true
media.stagefright.enable-http=true
ro.setupwizard.mode=DISABLED
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt

Warning: Use this information at your own risk. It is being provided by users of the device NOT the manufacturer/distributor.

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 the identified update file may / will brick the tablet.

 

[Jv90]

so you think it would work on a sytabex7 mini taller express?

Sent from my Sytabex7 Tablet

 

[cfrockit]

so you think it would work on a sytabex7 mini taller express?

The appropriate thread for the SYTABEX7 is http://www.androidtablets.net/forum...bex7-update-hardware-id-hwver-11-2-1-5-a.html.

Caution: Confirm the tablets Hardware ID "hwver" as described in Step 1 of http://www.androidtablets.net/forum...date-synet7lp-sytabex7-android-2-2-froyo.html before burning any update file.

 

[Jv90]

thanks cfrockit; do you know if this update comes Whit the autorotation screen apk thats missing in this model?

I'm going to install right on to check it

Sent from my Sytabex7 Tablet

 

[cfrockit]

thanks cfrockit; do you know if this update comes Whit the autorotation screen apk thats missing in this model?

I'm going to install right on to check it

Sent from my Sytabex7 Tablet

Moving your question to the SYTABEX7 thread to keep on topic. Please post your observations there so other SYTABEX7 can view.

 

[giveen]

So whats new with this Beta-5 edition?

 

[cfrockit]

So whats new with this Beta-5 edition?

Without installing it, here's my approach to see what's different -

• Use vio's IusEdit_0.04 utility to export the zSYS.img from ADR_AS section of InfoTM Update Wrap (.ius)

• Cut the 64 bytes u-boot header from the file. (Frhed - Free hex editor)

• Extract the gzipped image - system.img.tmp (7-Zip)

• Rename to system.img

Note: The Linux folks do all those steps something like this:

dd if=zSYS.img bs=64 skip=1 of=system.img.gz
gzip -d system.img.gz

• Extract the contents of system.img using the "dsixda's HTC Android Kitchen (xda-developers.com)" to "Set up working folder from ROM" which unyaffs the image to the /system folders.

• Use kdiff3 Tool for Comparison and Merge of Files and Directories

• Visually inspect files/directories identified as changed or missing

• Decode resources of identified applications (.apk) using android-apktool

• Debug smali code step by step to identify any modifications

Then after all this research, research and more research to see if anything is different and then post observations.

In this instance 11.2.1.8.2.0_beta4.ius and 11.2.1.8.2.0_beta5.ius system.img are the same. So on the the other images to compare.



U0 - u-boot-nand.bin - Files beta4 and beta5 are binary equal.
LK - Kernel - Files beta4 and beta5 are binary equal.
RD - ramdisk - Files beta4 and beta5 are binary equal.
ADR_USER - userdata - Files are different.

As only the Userdata image is of a different size, there seems to be no difference between beta4 and beta5.

Any suggestions welcome!

 

[Cat88Extreme]

I can't. download the file.

 

[MuffinTopped]

I can't. download the file.

Can this be used with the sytab10mt?

 

[cfrockit]

Can this be used with the sytab10mt?

Yes, but really NO! While the system.img from this update could be installed by extracting the image using vio's IusEdit utility and burning with IUW.exe in USB Mode: Expert burn it will not provided much functionality. The internal and external memory locations are mapped differently therefore you can't mount the SD card to side load applications such as Root. You'll lose the cool 3D animation. The wireless function does not work it just shows scanning. This could be fixed by loading the correct /system/lib/modules/rt2070sta.ko however, without being able to gain root the system.img would need to be modified before installing. As of yet, no one has developed a method to build a custom system.img.

In summary, No!

 

[TitaniumRat]

the method you just described is how I've been able to load Flytouch 2 system.img files on to my 7LP.

for Flytouch 2, they have been able to create custom system.img files, so it shouldn't be too hard. I had actually just assumed that you can mount the image files as loopback devices with yaffs support compiled into your kernel, or create a fs with the yaffs tools. I think Stragulus's git repository has it in the android configuration a method to create these as well. (if I'm not mistaken, TV is working on CWM with the people in the flytouch 2 forums?)

I think that maybe it's been taken for granted a bit too much that all infotm devices are massively different, but from playing with ROMs from other devices, I've found that most of the critical differences are in the kernel(and supplied modules) and sometimes some small changes to the ramdisk. the actual android build for these devic es seem to come from some simple template that InfoTM distributes to the various tablet makers. if we don't mess with uboot, use our kernel+mods, and our ramdisk as much as possible(most of the ramdisks looks about identical with a tweak here and there), we can run other firmwares with some tweaks.

well, the ZT180 actually is different, but I think Zenithink is responsible for that. sadly, I have not yet had a chance to build android for our tablet from the infotm configurations on github. with android's repositories being down for a while, not trusting anyone else's and not wanting to spend the time, I only briefly started when I first got my 7LP.

(btw, thanks to cfrockit and vio, with all the work everyone's already done, along with work from other tabs, there's tons of resources available for these things.)

EDIT:

if things aren't mounting quite properly, try loading the system with the original ramdisk for the firmware and the kernel that matches your tablet. it might be in a different place than you're used to it being mounted.

 

[cfrockit]

the method you just described is how I've been able to load Flytouch 2 system.img files on to my 7LP.

Welcome to this forum, awesome first post! We could use more detailed how-to's like yours based on experience. My limited experimentation with the various images has only with the "stock" infoTMIC system images just for comparison sake not as a daily build. We would (I really would) appreciate insight to your experience with a "Flytouch 2" image on a 7LP. There are so many, which one? Did you have to make any mods? What works? What doesn't? What's better? Thanks

 

[lohtse]

could this be used on the disgo 6000???

 

[cfrockit]

could this be used on the disgo 6000???

Probably not as you don't want to burn the incorrect U0 image. Search the posts related to Disgo most seem to reference Hardware ID "hwver" 12.2.0.5 but a 2.2 update image has not been identified. Best to request from Disgo mydisgo - my music, my video, my documents. If you obtain an updated firmware please post.

 

[lohtse]

all ready emailed them will get back to you when they reply.