cfrockit
Senior Member
- Dec 26, 2010
- 627
- 191
As suspected there are various versions of hardware thus different software updates are being detected.
Confirm your hardware version using /proc/cmdline
This file shows the kernel parameters that were passed during boot.
Example output:
Then insert your hwver after "data=" in the example url below the paste it in a new browser session to identify what update is being downloaded.
Example - 222.73.93.45/sysup.php?data=hwver&vcode=0
http://222.73.93.45/sysup.php?data=11.2.0.6&vcode=0
Returns
http://222.73.93.45/sysup.php?data=11.2.1.5&vcode=0
Returns
Neither of which has been confirmed to get past the Loading. . . step of the update process therefore isn't updating the device.
An initial comparison of the files shows they are different. You can interrupt the process when your device states "Loading ..." push the "Reset" pin on the back. The file will be saved in "/local". If you allow to go past "Loading ..." and it reboots the file will be wiped.
Once there is a working update file , (insert your complaint here) the process should follow in these steps - Downloading..., Loading..., Reading update package, Expanding..., Burning ..., reboot.
Please post your Hardware Version until we identify a version that will actually update.
Update: Try at your own risk.
Way before my time forum member gottahavit made some valuable discoveries in this thread http://www.androidtablets.net/forum...vania-synet7lp-work-progress-4.html#post13195 about the update process. Now that we have an update file, I followed his steps without bricking my device. However, nothing noticeable has changed so more work to do. Maybe if you have the "update from SD" issue you may different results. So, if you're a risk taker and don't fear bricking your device give it a go. Here are the steps.
Using the information above, download the appropriate file.
Rename the file system.bin and place on device in /local (This assumes you have a working knowledge of using adb)
Then from a shell command run the following -
Returns
Then issue to following command to Reboot.
Returns
The device should reboot to the INFOtm and hopefully load normally. Good luck. Post your results if you get a Firmware version other than DG2.02
Confirm your hardware version using /proc/cmdline
This file shows the kernel parameters that were passed during boot.
Example output:
Code:
C:\Documents and Settings\Owner>adb shell
# cat /proc/cmdline
cat /proc/cmdline
console=ttySAC3,115200 androidboot.mode=normal bmagic=0xeef07901 hwver=11.2.0.6
#
Example - 222.73.93.45/sysup.php?data=hwver&vcode=0
http://222.73.93.45/sysup.php?data=11.2.0.6&vcode=0
Returns
PHP:
11|http://222.73.93.45/update/11.2.0.6/11.2.0.6.2.0_beta3.ius
Returns
PHP:
12|http://222.73.93.45/update/11.2.1.5/11.2.1.5.2.0_beta3_1.ius
An initial comparison of the files shows they are different. You can interrupt the process when your device states "Loading ..." push the "Reset" pin on the back. The file will be saved in "/local". If you allow to go past "Loading ..." and it reboots the file will be wiped.
Once there is a working update file , (insert your complaint here) the process should follow in these steps - Downloading..., Loading..., Reading update package, Expanding..., Burning ..., reboot.
Please post your Hardware Version until we identify a version that will actually update.
Update: Try at your own risk.
Way before my time forum member gottahavit made some valuable discoveries in this thread http://www.androidtablets.net/forum...vania-synet7lp-work-progress-4.html#post13195 about the update process. Now that we have an update file, I followed his steps without bricking my device. However, nothing noticeable has changed so more work to do. Maybe if you have the "update from SD" issue you may different results. So, if you're a risk taker and don't fear bricking your device give it a go. Here are the steps.
Using the information above, download the appropriate file.
Rename the file system.bin and place on device in /local (This assumes you have a working knowledge of using adb)
Then from a shell command run the following -
Code:
C:\Documents and Settings\Owner>[B]adb shell[/B]
# [B]infoup inject /local/system.bin[/B]
Code:
infoup inject /local/system.bin
Partition: /dev/mtd/mtd2
Size: 134217728
progress:
67312128..............................................................
......................................Program OK. blocks:16434
#
Code:
# infoup reboot
Code:
infoup reboot
Last edited: