Can you clear the cache before aplying the firmware
1 tacke out the sd fro the player.
2 in the back you have a reset button. Pressit start the player it will thake tou tothe firmware flashing menu.
There do a factoy reset.wipe cache.
Then reboot the device. And see uf dies boot if npt inset the sd an try AGAIN to flash it
UPDATE: AndyTacker FIRMWARE IS SUPPOSED TO BE COMPATIBLE WITH MEASY X7 PLAYER THAT HAS ANDROID 2.2 INSTALLED BY DEFAULT.
Quote:
Originally Posted by tatubias
1 - download this firmware. it is stock latest firmware that measy provieded. it is andoird 2.2 its for the first version of the device Download update.zip from Sendspace.com - send big files the easy way
2 - format a SD card into fat
3 - copy the update.zip file into the root of the sd card (DONT UNCOMPRESS THE FILE)
4 - Power off the x7
4 - insert the sd into the media player
5 - power ON the x7 player will read the SD and will install the firmware
it may take form 10 to 20 minutes.
be patient.}
UPDATE: AndyTacker FIRMWARE IS SUPPOSED TO BE COMPATIBLE WITH MEASY X7 PLAYER THAT HAS ANDROID 2.2 INSTALLED BY DEFAULT.
I tried to implement this solution, it doesn't work.
Any othe suggestions?
hi its me. i tried to install its old firmware but doesnot work. pls help
Lets start from the biggining.
1 - when you bought the device wich version of andorid or firmware has installed?
2 - what do you mean with "does not work"
3 - sed us a video. or somthing explainig what is happening to you.
I tried to implement this solution, it doesn't work.
Any othe suggestions?
Lets start from the biggining.
1 - when you bought the device wich version of andorid or firmware has installed?
2 - what do you mean with "does not work"
3 - sed us a video. or somthing explainig what is happening to you.
1 - when you bought the device wich version of andorid or firmware has installed?
2 - what do you mean with "does not work"
3 - sed us a video. or somthing explainig what is happening to you.
I received the device some days ago. I didn't know which version was installed. The device didn't work.
Thank you very much for any help.
20120326-S8500-01.jpg Means that the recovery cant read the USB or the SD card. to fix this issue format the SD or the usb into fat.
20120326-S8500-02.jpg 20120326-S8500-03.jpg
About this too screen its odd. that boot screen of the recovery is different that the one o got in mine. i dont know if yours is the one with 2.3 android.
Do the following.
do a complete format in fat of the SD or USB drive that you are using (dont use fast format). then copy the update.zip into the root directory of the SD or the USB.
RUN CLEAR DATA / FACTORY RESET and CLEAR CACHE PARTITION before installing the firmware?? if not doit.
The apply the firmware.
if does not work with upgrading firmware v1026 and v1110 try installing the one that AndyTacker provided. also send an email to support@measy.com.cn so they can send you the firmware 2.3 for the device.
if not you will need to return the device.
NOTE:
if you have modified the update.zip will never work because it is a signed file. so you will need to re signe the file to be a valid one.
20120326-S8500-01.jpg Means that the recovery cant read the USB or the SD card. to fix this issue format the SD or the usb into fat.
20120326-S8500-02.jpg 20120326-S8500-03.jpg
About this too screen its odd. that boot screen of the recovery is different that the one o got in mine. i dont know if yours is the one with 2.3 android.
Do the following.
do a complete format in fat of the SD or USB drive that you are using (dont use fast format). then copy the update.zip into the root directory of the SD or the USB.
RUN CLEAR DATA / FACTORY RESET and CLEAR CACHE PARTITION before installing the firmware?? if not doit.
The apply the firmware.
if does not work with upgrading firmware v1026 and v1110 try installing the one that AndyTacker provided. also send an email to support@measy.com.cn so they can send you the firmware 2.3 for the device.
if not you will need to return the device.
NOTE:
if you have modified the update.zip will never work because it is a signed file. so you will need to re signe the file to be a valid one.
i have spent more time investigation about hte error you get there.
It seems when you install a firmware it does some pre checks before installing your update.
so, it will then extract system/build.prop Then, it checks the:
ro.product.device
ro.build.date.utc
ro.build.id
If, ro.build.date.utc is not equal to, or newer than the current version - the update errors out If, ro.build.date.device is not for, the device - the update errors out
So it seams that you will not be able to install 1026 or 1110 version due the ro.build.date.utc is not so current as the one that is installed on the device.
here we have 2 options by the moment.
1 Install AndyTacker firmware. if this works it will not work the remote control that was reported. but you can also test if my fix works.
2 - we can tune firmware 1110v to have ro.build.date.utc=1322136440.
updated. (this i have never done and i do not have the device to test. if you want i can try to repack the firmware with that data updated. but i cant garanty NOTHING.
The first option then if does not work let me know i will study how to do the package re signing.
NOTE: now im repacking the update.zip for 1110v. if you want to wait little more time i will be posting here.
UPDATE2: i have uploaded the firmware for soltan74 (this rom is 1110v with utc updated only) http://www.mirrorcreator.com/files/NDQ8R0JK/
This should only be used by soltan74 its designed to fix his issue. if you install this on your device you will never be able to install any stock measy 1110v or earlier firmware again. this may brick any player so install it at your own risk i do not take any responsibility.
Last edited by tatubias; March 27th, 2012 at 12:03 PM.
I have repacked the firmware that ANDYTRACKER provided. it has the update for the remote control only. if you want can test it. i will not guaranty nothing. remember that i cant test due my device got burn in a storm. (keep in mind that you may brick the device if does not work)
LINK REMOVED FILES NOT WORKING
Please let us know if you decide to apply ti. if does it work and if the remote works and if it possible a video.
Last edited by tatubias; March 28th, 2012 at 02:47 PM.
It seems when you install a firmware it does some pre checks before installing your update.
so, it will then extract system/build.prop Then, it checks the:
ro.product.device
ro.build.date.utc
ro.build.id
If, ro.build.date.utc is not equal to, or newer than the current version - the update errors out If, ro.build.date.device is not for, the device - the update errors out
So it seams that you will not be able to install 1026 or 1110 version due the ro.build.date.utc is not so current as the one that is installed on the device.
here we have 2 options by the moment.
1 Install AndyTacker firmware. if this works it will not work the remote control that was reported. but you can also test if my fix works.
2 - we can tune firmware 1110v to have ro.build.date.utc=1322136440.
updated. (this i have never done and i do not have the device to test. if you want i can try to repack the firmware with that data updated. but i cant garanty NOTHING.
The first option then if does not work let me know i will study how to do the package re signing.
NOTE: now im repacking the update.zip for 1110v. if you want to wait little more time i will be posting here.
UPDATE2: i have uploaded the firmware for soltan74 (this rom is 1110v with utc updated only) Download mirrors for update.zip - Mirrorcreator - Upload files to multiple file sharing sites
This should only be used by soltan74 its designed to fix his issue. if you install this on your device you will never be able to install any stock measy 1110v or earlier firmware again. this may brick any player so install it at your own risk i do not take any responsibility.
Hi
I tried first method and received message "signature verification failed".
About second method, where can I download AndyTacker firmware.
20120326-S8500-01.jpg Means that the recovery cant read the USB or the SD card. to fix this issue format the SD or the usb into fat.
20120326-S8500-02.jpg 20120326-S8500-03.jpg
About this too screen its odd. that boot screen of the recovery is different that the one o got in mine. i dont know if yours is the one with 2.3 android.
Do the following.
do a complete format in fat of the SD or USB drive that you are using (dont use fast format). then copy the update.zip into the root directory of the SD or the USB.
RUN CLEAR DATA / FACTORY RESET and CLEAR CACHE PARTITION before installing the firmware?? if not doit.
The apply the firmware.
if does not work with upgrading firmware v1026 and v1110 try installing the one that AndyTacker provided. also send an email to support@measy.com.cn so they can send you the firmware 2.3 for the device.
if not you will need to return the device.
NOTE:
if you have modified the update.zip will never work because it is a signed file. so you will need to re signe the file to be a valid one.
Hi
I didn't modify update.zip file.
I tried propose solution, result is the same.
I written to Measy support, no answer.
Any other solutions?
Thank you very much
Hi
I didn't modify update.zip file.
I tried propose solution, result is the same.
I written to Measy support, no answer.
Any other solutions?
Thank you very much
did you down load and install he version that I have signed specialty for your issue¿
Hi
I tried first method and received message "signature verification failed".
About second method, where can I download AndyTacker firmware.
Thanks for you help
Seems that we are mixing things here. Try the one I designed for you if does not work send me a screen shot so I can see the error
LINK REMOVED FILES NOT WORKING
Provide a screen shot if does not work I will be signing again the from if it is that the issue
if that file is reporting you that is not signed. im uploading a new one with an other sign method. i will be send it to you though personal message to avoid confusion.
Last edited by tatubias; March 28th, 2012 at 02:48 PM.
guys if you dont test the solution proposed int he same day or nest that i post i will not be providing support any longer. due its a lot of work that i have to do and i dont even have the player.
when i tried to update new update provided by tatubias link i have signature fail and update aborted error.
i also tried to sign the file using signapk but not suceeded
i have sent an other package to soltan74 it was different signed thatn yours. so lets wait if that signnign works if not we will need to find other way.
you can try. look any other signing app. and sing the zip file that i have sent. then re test it.
Shamlotlikar this error is because you have installed a newer version of a firmware: !less_than_int(1320917475) than the one you want to install so you need to edit the build probfile add that value to ro.build.date.utc then sign the package.
UPDATE: Shamlotlikar please explain wich is the problem that you have we are mixing things here. we have 2 issues going on.
1 - trying to make a rom with the rom that provided ANDY that has the remote controler "fixed"
2 - trying to install the version 1110v into the device of soltan74 that has the ro.build.date.utc issue.
Please explain PERFECT which is your issue.
Last edited by tatubias; March 28th, 2012 at 02:26 PM.
SignApk is a tool included with the Android platform source bundle, you can download it from http://developer.android.com/sdk. To use SignApk.jar you can create a own key with it’s corresponding certificate/public key.
To create private/public key pair, you can use Openssl. Openssl is relatively easy to use under unix/linux system. For Windows user, you can download Windows version of Openssl @http://code.google.com/p/openssl-for-windows/
How to create private/public key pair using openssl (windows version)
Download openssl package from link given above
Extract it anywhere on your drive (eg. C:\openssl)
- openssl genrsa -out key.pem 1024
- openssl req -new -key key.pem -out request.pem
- openssl x509 -req -days 9999 -in request.pem -signkey key.pem -out certificate.pem
- openssl pkcs8 -topk8 -outform DER -in key.pem -inform PEM -out key.pk8 -nocrypt
Download SignApk.rar from link given above
Extract it anywhere on your drive (eg. c:\SignApk)
If you don’t have java installed, download and install it.
Copy certificate.pem and key.pk8 into your extracted SignApk directory
now i have signed with singapk with private keys i hope this work.
now im uploading the file i will be sending though PM.
please explain PERFECT what is your issue what is happening to you and what do you want to do or fix.
Thank you
UPDATE: i have finished uploading the rom for Shamlotlikar i have sent it to him thought PM. need verification ans explanation what is your problem and what do you want to do.
Last edited by tatubias; March 28th, 2012 at 02:43 PM.
Seems that we are mixing things here. Try the one I designed for you if does not work send me a screen shot so I can see the error
LINK REMOVED FILES NOT WORKING
Provide a screen shot if does not work I will be signing again the from if it is that the issue
if that file is reporting you that is not signed. im uploading a new one with an other sign method. i will be send it to you though personal message to avoid confusion.
Hi
I tried to upgrade firmware, the result you can at the next screenshot: 20120328-S8500-02.jpg
Thanks for you help
Last edited by El Presidente; May 9th, 2012 at 02:28 AM.
my dealer had agreed to look in the problem got his mail. i shall be going to his place today
if he changes the faulty player its ok otherwise my hard earned money just washed up in this messy measy.
i shall update the status afterwards.
thanks all for co-operation
Last edited by Shamlotlikar; March 30th, 2012 at 09:32 PM.
my dealer had agreed to look in the problem got his mail. i shall be going to his place today
if he changes the faulty player its ok otherwise my hard earned money just washed up in this messy measy.
i shall update the status afterwards.
thanks all for co-operation
thank you to you. I hope you dealer can replace the device
Just wanted to say that the wistarmedia, update.zip worked out of the box with my Measy X7 (only exception was the broken remote control).
My original Measy X7
HW AMLOGIC MESON-M1 8726M DVBC
RAM 192 MB
INT Storage 2GB
AMLogic M1 Reference Board
Android API Level 8
Firmware 2.2.1
Process that worked for me is the following sequence.
1. This came with the stock firmware that I had updated earlier to v1110 by just copying on to SDCARD and using the FW update icon.
2. Now apply the Z4Root apk and Ghost Commander apk.
This is so that later on you can update the remote controller file
3. Now update with the Wistar update.zip using the Firmware update icon and wait for the box to reboot into the Wistar android 2.3.3 screen
4. From the v1110.zip extract on you laptop from /system/etc the file remote.conf to a SDCard.
5. Connect a regular keyboard (In my case I used the wireless FlyMouse keyboard). reboot box so that it detects and boots into the new UI.
6. Navigate to apps and using ghost commander change options
a. Allow root access and remount as rw
b. Set path to busybox as /system/bin/busybox
7. Now navigate to /system/etc and rename remote.conf on orig_remote.conf
8. Copy from Sdcard remote.conf to /system/etc.
9. Long click on /system/etc/remote.conf and from the busybox dialog for chmod change permission to rw-r-r and owner/group to root/root.
Reboot now and the regular Measy Remote controller should work properly.
Last edited by blrdude39; April 1st, 2012 at 09:26 AM.
Reason: Extraneous line removed..
Just wanted to say that the wistarmedia, update.zip worked out of the box with my Measy X7 (only exception was the broken remote control).
My original Measy X7
HW AMLOGIC MESON-M1 8726M DVBC
RAM 192 MB
INT Storage 2GB
AMLogic M1 Reference Board
Android API Level 8
Firmware 2.2.1
Process that worked for me is the following sequence.
1. This came with the stock firmware that I had updated earlier to v1110 by just copying on to SDCARD and using the FW update icon.
2. Now apply the Z4Root apk and Ghost Commander apk.
This is so that later on you can update the remote controller file
3. Now update with the Wistar update.zip using the Firmware update icon and wait for the box to reboot into the Wistar android 2.3.3 screen
4. From the v1110.zip extract on you laptop from /system/etc the file remote.conf to a SDCard.
5. Connect a regular keyboard (In my case I used the wireless FlyMouse keyboard). reboot box so that it detects and boots into the new UI.
6. Navigate to apps and using ghost commander change options
a. Allow root access and remount as rw
b. Set path to busybox as /system/bin/busybox
7. Now navigate to /system/etc and rename remote.conf on orig_remote.conf
8. Copy from Sdcard remote.conf to /system/etc.
9. Long click on /system/etc/remote.conf and from the busybox dialog for chmod change permission to rw-r-r and owner/group to root/root.
Reboot now and the regular Measy Remote controller should work properly.
excellent update thank you very much. I did sing the firmware that Andy posted but it was told that the sijgnig was not working . The idea was to simplify the process to people that does not know how to do that . All s we can add some other modifications like the host file . Google DNS, fingerprints for the market and much more.
Last edited by tatubias; April 1st, 2012 at 10:24 PM.
Hi everyone, I would like some help please. When I put my X7 in WiFi mode it always bumbs my laptop off of the internet, which is also on my home network, and then disconnects itself, although I have a static IP. What can be the cause of this?
Thanks
Hi everyone, I would like some help please. When I put my X7 in WiFi mode it always bumbs my laptop off of the internet, which is also on my home network, and then disconnects itself, although I have a static IP. What can be the cause of this?
Thanks
Configure your network using dhcp.
Probablt the issue is that the player is using the same ip than your notebook.
I have bricked by Measy X7 by trying to update to 2.3.4 update.zip for a similar device (8726M based).
Has anyone figured out if the MeasyX7 has adb support using a male to male usb cable. I mean if I were to connect one of the USB ports to my lab top can I use adb command (assuming I have the sdk installed).
This is usually a problem when the static ip configured clashes with the dhcp ip provided.
Can you provide an output from a cmd prompt on the laptop for command
c:\>ipconfig /all
This will confirm if your laptop is using dhcp or static address.
It is quite likely that dhcp pool is over lapping the static ip address you have configured.
For this simple solution is to go to the broadband router admin screen and configure the pool to not overlap with static addresses.
e.g In my home setup that I have configure
192.168.155.1 - Router G/w
192.168.155.101 - 192.168.155.110 - DHCP pool (I am not expecting more than 10 devices. 3 PCs, 2 Laptops, Measy X7, Samsung TV DLNA, HTC Salsa)
So the static IP address I need once in a while for my Linux experiments I use in the range 192.168.155.51-60 range.
Quote:
Originally Posted by Jerocrop
Hi everyone, I would like some help please. When I put my X7 in WiFi mode it always bumbs my laptop off of the internet, which is also on my home network, and then disconnects itself, although I have a static IP. What can be the cause of this?
Thanks
Now that I have soft bricked by Measy X7 and the usual revival techiniques dont seem to work, I am thinking may be buiding a custom SDCard with aml bootfiles (uboot ...), aml_autoscript, factory_update_param.aml will do the trick.
Is there anybody here knowledgeable that can help with this.
1. How do I verify that aml_autoscript is actually being read when the system goes into recovery mode
2. What is the meaning of upgrade_step 3, upgrade_step 4, ... in the aml_autoscript
3. What is the difference between mtd and mmc or are they the same.
2. Now given the contents of the mtd partitions then one can create a custom aml_autoscript that
a. Erases nand / mmc whatever it is called as and creates the partitions again exactly as given by cat /proc/mtd
b. Copies the img files into the proper mtd parititions.
c. Extract from output of dmesg and get the boot command line params and put it in aml_autosrcipt and do a saveenv kind of thing.
3. With step 2 now, the nand should become a replica of the working box.
a. Now set flag (would this be ugrade_step ??? and go into normal reboot.
4. Since nand is now a replica of a working box setup, it should go into normal boot up and come up properly.
a. What probably can be done is create empty data partition so that there are no user settings (like market ...) that get carried over but only a bare bones minimum system needed.
blrdude39 did fix his issue. finally what he did done was. edit the factory_update_param.aml from the amlogic boot files.
It was a problem with the entry in the factory_update_param.aml file.
you have to modify the following entry.
--update_package=SDCARD:update.zip
to
--update_package=/sdcard/update.zip
I had the same issue as you and was able to resolve the problem with a simple tweak of adding a factory_update_param.aml file onto the SDCARD.
What this does is solve the problem of remote not working on the recovery screen. It forces the recovery process to load the file referred to in the .aml file.
Do let me know some details on:
1. Is yours a Measy X7 originally - What version of firmware was on it
Was it v1026 or v1110
2. When you tried to upgrade to Gingerbread OS which firmware did you try to use
- AndyTacker firmware - The one that seems to be the WEPAD6 from www.wistarmedia.com downloadable from their firmware section
or
- MBOX 2.3 firmware from Cool Gadgets at the Right Price - Worldwide Free Shipping - DealExtreme
The screen shot you have shown indicates a non stock Measy SPI in use.
I went through the Measy v1026->v1110->wistarmedia->Mbox series of transitions..
I now have a Measy X7 box that thinks its a MBOX from Dealextreme. Have even got it recognize the Measy remote but however the launcher still expects a touch screen / tablet operation. This I am able to overcome since in addition to the Measy remote I have a Fly Mouse II which is recognized by the box.
If it was just a case of verification failed, then it can be overcome by repackaging update.zip and signing it. This process is highly simplified if one uses the update-zip-packager and there is also a youtube video that demonstrates its usage.
In short what is causing the verification to fail ...
Usually -
a. A revision time stamp mismatch
or
b. Board name mismatch.
Unzip the update.zip
Remove those offending lines from updater-script and update-script
Remove CERT.RSA, CERT.SF, MANIFEST.MF
Replace remote.conf with the remote.conf from the v1110.zip package.
Now sign the contents and recreate update.zip.
The youtube video shows it very nicely.
Let me know if this works for you.
Quote:
Originally Posted by soltan74
Hi
I tried to upgrade firmware, the result you can at the next screenshot: 20120328-S8500-02.jpg
Thanks for you help
Last edited by blrdude39; April 9th, 2012 at 01:32 PM.
Reason: Added explanation for signing .. and replacing remote.conf
I had the same issue as you and was able to resolve the problem with a simple tweak of adding a factory_update_param.aml file onto the SDCARD.
What this does is solve the problem of remote not working on the recovery screen. It forces the recovery process to load the file referred to in the .aml file.
Do let me know some details on:
1. Is yours a Measy X7 originally - What version of firmware was on it
Was it v1026 or v1110
2. When you tried to upgrade to Gingerbread OS which firmware did you try to use
- AndyTacker firmware - The one that seems to be the WEPAD6 from www.wistarmedia.com downloadable from their firmware section
or
- MBOX 2.3 firmware from Cool Gadgets at the Right Price - Worldwide Free Shipping - DealExtreme
The screen shot you have shown indicates a non stock Measy SPI in use.
I went through the Measy v1026->v1110->wistarmedia->Mbox series of transitions..
I now have a Measy X7 box that thinks its a MBOX from Dealextreme. Have even got it recognize the Measy remote but however the launcher still expects a touch screen / tablet operation. This I am able to overcome since in addition to the Measy remote I have a Fly Mouse II which is recognized by the box.
If it was just a case of verification failed, then it can be overcome by repackaging update.zip and signing it. This process is highly simplified if one uses the update-zip-packager and there is also a youtube video that demonstrates its usage.
In short what is causing the verification to fail ...
Usually -
a. A revision time stamp mismatch
or
b. Board name mismatch.
Unzip the update.zip
Remove those offending lines from updater-script and update-script
Remove CERT.RSA, CERT.SF, MANIFEST.MF
Now sign the contents and recreate update.zip.
The youtube video shows it very nicely.
Let me know if this works for you.
Excelent news.
i have sent you the links to down load geniatech andoird 4.0 firmware and 2.3 you can play with it and let us know who did you went.
I have the same problem like soltan but with an other box. I have made an upgrade to android 4.0 but I cant downgrade to 2.3 anymore. Can anybody help me with this issue?
I have the same problem like soltan but with an other box. I have made an upgrade to android 4.0 but I cant downgrade to 2.3 anymore. Can anybody help me with this issue?
regards
hans
what is the error you get when you want to do the down grade.
send us a screen shot.
if you get the error ro.build.date.utc=xxxxxx you will need to tweek your 2.3 firmware to do it.
send us the screen shot.
also provide the model of the device and the firmware you are using. we cant do much if you dont provide all the information.
Add the reduced size pictures to the 6 files mentioned previously.
Zip the 8 files so that you get a small zip file called DiagInfo.zip and attach to your posting
With this it will help us diagnose to some extent what may be causing the problem.
Quote:
Originally Posted by hansmaiser
Hi,
I have the same problem like soltan but with an other box. I have made an upgrade to android 4.0 but I cant downgrade to 2.3 anymore. Can anybody help me with this issue?
regards
hans
The Following User Says Thank You to blrdude39 For This Useful Post:
Unzip what you download from Drop Box link above and follow
HOWTO instructions below
This update contains firmware upgrade files repackaged to
a. skip the verification checks for time stamps and board numbers
b. remote.conf replace to work with the Measy X7 remote
c. Signed again to pass the signature checks
d. Does a wipe-data so that it simulates a fresh factory boot (Note will remove all customized settings)
d. Uses factory_update_param.aml method to automatically do the firmware update (over comes inability to choose which update if box does not respond to remote)
NOTE: Wistarmedia update is more inclined to touch tablet. So you probably need a wireless or wired USB mouse once the upgrade is done to get to the UI. In my case I was able to work it with a FlyMouse ...
If you are getting verification errors
?????36640 verification failed - copy update_wistarmedia.aml to factory_update_param.aml
?????17475 verification failed - copy update_measyv1110.aml to factory_update_param.aml
Format SD card for FAT32
On the root directory copy files
factory_update_param.aml
wistarmedia_update.zip
measyv1110_update.zip
Put SDCARD into the MeasyBox. Pull out the power plug of the box.
Now using hair pin/blunt needle whatever and keep the reset button on the back of the box pressed and insert the power plug into the box.
Keep holding the pin till you see the little android logo and progress bar loading the update file. At this point you can let go of the hairpin.
When box starts to reboot remove SDCARD
Now you should see the green Android robo splash screen for about a minute or two.
Following this would be the Android kind of 3D splash for about a minute.
If it hangs at this stage a simple power off and on by pulling the plug off (ensure SDcard removed) and putting plug back in should do the trick and restore you back to normal functioning.
The Following User Says Thank You to blrdude39 For This Useful Post:
I have solved the problem. My box is this here: Android 4.0 TV Box advice.
It had the "ro.build.date.utc"-error.
My mistake was that I tried to update with the update.zip only, without the other 6 files (uImage_recovery, factory_update_param, u-boot-aml-ucl, etc). After putting the update.zip with these files together on the sdcard, the downgrade back to 2.3 was successful.
I have solved the problem. My box is this here: Android 4.0 TV Box advice.
It had the "ro.build.date.utc"-error.
My mistake was that I tried to update with the update.zip only, without the other 6 files (uImage_recovery, factory_update_param, u-boot-aml-ucl, etc). After putting the update.zip with these files together on the sdcard, the downgrade back to 2.3 was successful.
I tried the firmware atv300 Geniatech
I do not know how to force device model, certainly have to modify some file within upgrade.zip
With respect to the nick, I have it long ago and is quite original
before doing any tweek into the zip file you will need to know that you can brick the device.
what you need to do is. edit the file /system/build.prop file inside there it is the field that should be updated "ro.product.device". copy it form the measy original rom you can play arround with that.
then you will need to re sign the zip and you can test. brick possibility.
Last edited by tatubias; April 11th, 2012 at 01:55 PM.
did you got the firmware 4.0 ??? installed? or only 2.3?
send us a video and screenshots please!!!!
Hi,
I had installed both. The box was delivered with 2.3, I upgraded to 4.0, now I switched back to 2.3, because no root, no flash, youtube was buggy in 4.0.
I will not update to 4.0 again, so I cant make videos or screenshots.
I had installed both. The box was delivered with 2.3, I upgraded to 4.0, now I switched back to 2.3, because no root, no flash, youtube was buggy in 4.0.
I will not update to 4.0 again, so I cant make videos or screenshots.
Hans
can you post a detail tutorial how to install andorid 4.?
obiouly provide the linkt to download the firmware.
Last edited by tatubias; April 11th, 2012 at 02:47 PM.
I had installed both. The box was delivered with 2.3, I upgraded to 4.0, now I switched back to 2.3, because no root, no flash, youtube was buggy in 4.0.
I will not update to 4.0 again, so I cant make videos or screenshots.
Hans
I would agree I have also been following the 4.0 Geniatech threads on this site. 4.0 is still in beta state and apparently quite buggy. However their 2.3 updates seem to make the box more functional like in add Samba, making box as hotspot for WiFi, custom flash support (see dynamic .so in the upgrade package) that allows hardware acceleration kind of thing.
However got to say Geniatech seems to be most popular. I was kind of surprised to see locally (in Bangalore, India where I am from) I saw a company selling what looked like a rebranded Geniatech ATV1000 box calling it the Wow TV box .
See Mobility Makes A Difference and retails for about USD 150 here.
Another interesting firmware seems to be the SumVision Cyclone Android box. They seem to have melded the Geniatech firmware and put in the Measy X7 UI explorer which is more remote friendly (as opposed to the phone screen friendly version).
See Cyclone Andriod Internet TV for the product description. The screen shot shows the familiar Measy X7 home screen with its various categories.
See SUMVISION - We Sell PC Hardware, Software, Digital Media, Digital Cameras, MP3 Players, Components, Networking Equipment and more... under Cyclone Android media center for the original box firmware and a recent upgrade they have done. NOTE: Both firmwares are still 2.3 though.
I will be away for a week and then on coming back will do some compare of the firmwares at a file level (will be doing it on linux with the cksum cmd and such) so see who is copying from whom and probably we can come up with a custom ROM that is reasonably stable, has say 5-10 of the most popularly sought after APKs built in and such.