• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Measy X7 - Android TV Box - HDD - ARM Cortex A9

  • Thread starter Thread starter SpiderX
  • Start date Start date
@Tatubias.
Sorry to go off track a bit. Did see couple of your postings on dealextreme.

I got curious and wanted to try the firmware from that particular box on the Measy since they had the same AMlogic specs

My posting here describes the problem I am facing
Firmware upgrade? [Update: Download Link here] ? DealExtreme Forum
What I have now is kind of soft bricked device.

My hunch is that I should be able to fix the problem one of two ways
1. Restore using amlogic boot files that are specific to the Measy box.
Firmware upgrade? [Update: Download Link here] ? DealExtreme Forum
Firmware upgrade? [Update: Download Link here] ? DealExtreme Forum
But I am not sure if the files here would match the specs of the MeasyX7.
The Measy X7 shows only 192 MB and not 512MB
OR
2. Using something similar to rest_oem.zip .. Can this be duplicated for the Measy X7 using the contents of the v1110 zip file?
See Firmware upgrade? [Update: Download Link here] ? DealExtreme Forum for info

Note:
In this condition if I connect the USB3.0 connector to my laptop (blue USB) I can see the HDD of the Measy as drive on my laptop
 
blrdude39 said:
@Tatubias.
Sorry to go off track a bit. Did see couple of your postings on dealextreme.

I got curious and wanted to try the firmware from that particular box on the Measy since they had the same AMlogic specs

My posting here describes the problem I am facing
Firmware upgrade? [Update: Download Link here] ? DealExtreme Forum
What I have now is kind of soft bricked device.

My hunch is that I should be able to fix the problem one of two ways
1. Restore using amlogic boot files that are specific to the Measy box.
Firmware upgrade? [Update: Download Link here] ? DealExtreme Forum
Firmware upgrade? [Update: Download Link here] ? DealExtreme Forum
But I am not sure if the files here would match the specs of the MeasyX7.
The Measy X7 shows only 192 MB and not 512MB
OR
2. Using something similar to rest_oem.zip .. Can this be duplicated for the Measy X7 using the contents of the v1110 zip file?
See Firmware upgrade? [Update: Download Link here] ? DealExtreme Forum for info

Note:
In this condition if I connect the USB3.0 connector to my laptop (blue USB) I can see the HDD of the Measy as drive on my laptop
Click to expand...


note: measy x7 is supposed to be 512ram but the firmware is not showing that amount of memory.

try installing 1110v firmware. and let us know what does it?

can you get into the firmware flash utilitie when you boot pressing the reset button?
 
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
 
Jerocrop said:
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
Click to expand...

Configure your network using dhcp.

Probablt the issue is that the player is using the same ip than your notebook.

Or try changing by hand the ip, if the notebook.

This is a simple missconfigured network
 
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).
 
I have not tested you will need to try.

Aldo if you open the device you will see connectors you can the with them.

Does you device even boot when you press the reset button. Then re install measy firmware,)?
 
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.

Jerocrop said:
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
Click to expand...
 
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.

What I am thinking of is something on the lines of this.
1. From the information on
How to Modify Android Boot Images | HackSlurp
HOWTO: Unpack, Edit, and Re-Pack Boot Images - Android Wiki
If someone had access to a working device, once can dump all the mtd partitions on to an external/removable SDcard.

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.

Can someone validate this approach for me..
 
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
 
@soltan74

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.

soltan74 said:
Hi
I tried to upgrade firmware, the result you can at the next screenshot:
20120328-S8500-02.jpg
Thanks for you help
Click to expand...
 
blrdude39 said:
@soltan74

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.
Click to expand...

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.
 
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
 
hansmaiser said:
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
Click to expand...


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.
 
HOWTO SEND DIAGNOSTIC INFORMATION

Create a zip file that contains the following

From your old firmware update.zip/update.img file
build.props
updater-script
update-script

From your new firmware update.zip/update.img file
build.props
updater-script
update-script

Put these into two separate directories say like
v_old
v_new

If you have a working box install the Android Terminal emulator from
https://github.com/jackpal/Android-Terminal-Emulator/downloads

Once this application is installed then run the application.
You will get a linux line command prompt on the screen.
Enter on the screen

cat /proc/cpuinfo <enter key>

Take a digicam picture of monitor output

cat /proc/mtd <enter key>

Take a digicam picture of monitor output

mount <enter key>

Take a digicam picture of monitor output

Convert these pictures to 800x600, 256 colours format to reduce the size

You can use a tool like IrfanView to do this
IrfanView - Official Homepage - one of the most popular viewers worldwide

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.

hansmaiser said:
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
Click to expand...
 
soltan74 said:
Hi
I tried to upgrade firmware, the result you can at the next screenshot:
20120328-S8500-02.jpg
Thanks for you help
Click to expand...

For those who have problems similar to this this I have made an update package availabe on drop box that attempts to fix this.

NOTE: Only use this if you are facing a similar problem.

http://dl.dropbox.com/u/72213575/MeasyX7_fixsoftbrick.zip

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.
 
Hi,

I have solved the problem. My box is this here:
http://androidforums.com/google-tv/513616-android-4-0-tv-box-advice.html
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.

Here is the link for the 2.3 firmware:
Download latest 2.3 firmware.rar from Sendspace.com - send big files the easy way

Anyway thanks for you help!
 
hansmaiser said:
Hi,

I have solved the problem. My box is this here:
http://androidforums.com/google-tv/513616-android-4-0-tv-box-advice.html
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.

Here is the link for the 2.3 firmware:
Download latest 2.3 firmware.rar from Sendspace.com - send big files the easy way

Anyway thanks for you help!
Click to expand...


did you got the firmware 4.0 ??? installed? or only 2.3?

send us a video and screenshots please!!!!
 
Hi all. Yesterday try to install the version 4 in the x7 but me back an error and could not continue installation
The error was

ro.product.device

regards
Marcelo from Argentina
 
tobulman said:
Hi all. Yesterday try to install the version 4 in the x7 but me back an error and could not continue installation
The error was

ro.product.device

regards
Marcelo from Argentina
Click to expand...


send us the screen shot. please.
btw your nick is not much original.. lol

which version of andoird did got your device before?
by the moment no x7 has installed andoird 4.

me too form arg.
 
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;)
 
tobulman said:
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;)
Click to expand...


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.
 
tatubias said:
did you got the firmware 4.0 ??? installed? or only 2.3?

send us a video and screenshots please!!!!
Click to expand...

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.

Hans
 
hansmaiser said:
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.

Hans
Click to expand...


can you post a detail tutorial how to install andorid 4.?

obiouly provide the linkt to download the firmware. ;)
 
hansmaiser said:
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.
Hans
Click to expand...

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.

Geniatech has put out a new update to 4.0 yesterday or so.
See http://androidforums.com/google-tv/408166-geniatech-enjoy-tv-24.html look for post by gboijhpok
URL is http://www.geniatech.com/down-eng/Androidtvbox/update_M1_4.0_20120411.zip

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.
 
You must log in or register to reply here.
Back
Top Bottom