Android 2.3 & 4.0 WiFi Internet HD 1080P HDMI Google TV Box ARM Cortex A9 Firmware

[dgcruzing]

Stane1983,

Thanks a lot for the info, I'll try it. Right now I want to use XBMC with this box, I have tested many versions (nightly, midnight, futeko) and all crashes after few minutes....I wondering if I can upgrade the firmware to stable version or find another XBMC version, could you suggest me?

thanks in advanced

Were55,
Head to the dedicated XBMCANDROID forum that's been setup up.. I am sure you will be able to find one from the source.. As they are getting better by the day..

 

[naismith]

VS-ATV-106

bluetooth speaker|shenzhen visson technology|card speaker|cheap|good quality|portable speaker

Hi.

This is a AML8726-M6 model... looks trekie

 

[MartinCC]

Wowww... VS-ATV-106 looks very nice and powerfull ! Any ideas of prices yet ? And where to get one with Argentina delivery ?

Thanks !

 

[were55]

Just info, Visson will start mass production of their MX devices next month (November).

Their MX device will be packed in their standard case as ATV-102/ATV-108 and in new 'space' design case which looks cool (I don't know if I'm allowed to post picture so I'm not going to )

Hi Stane,

What is the difference between ATV-102 and ATV-108? I found a FW for test ATV-102 in V-play...are you testing it?

regards

 

[naismith]

Hi

Two new models are upcomming

ATV 102S in november (classic design with dual core)
ATV 106 in december (space design)

You can see more info here
Vissontech nos presenta su gama de TV-BOX hasta final de a

 

[stane1983]

Hi Stane,

What is the difference between ATV-102 and ATV-108? I found a FW for test ATV-102 in V-play...are you testing it?

regards

Hi,

ATV-102 is renamed ATV-108 (rev 2). There are also 2 versions of ATV-102. One with 512Mb DDR3 and another one with 1Gb DDR3. Firmwares on my download section are not prepared for 1Gb device (firmwares do have minor changes in bootloader, kernel and android core system).

 

[gamajunior]

Hello stane1983

Do you have an estimate of when a new firmware comes out for the VS ATV-102? I ask because I'm using the latest firmware and failure in wi-fi and external keyboard this limited use.

Again thank you for the excellent work you have been doing.

----------------------------------

Ol

 

[b0b0]

Hello everybody

I have a question for you guys... Do you think I can safely try to flash my box with you latest c03ref version?

I bought an Energy Sistem Smart TV Box
h*ttp://www.energysistem.com/en-en/products/centro_multimedia/serie_media_center/38313-energy_android_smart_tv_box/specs
report:
h*ttp://androidfragmentation.com/database/v/dr/592149/oem/MBX/dm/Android%20Smart%20TV%20Box/carrier/Unknown

It looks very similar to the c03ref box you guys are "playing" with.

Couple of specs:
cat /proc/mtd
dev: size erasesize name
mtd0: 00800000 00200000 "aml_logo"
mtd1: 00800000 00200000 "recovery"
mtd2: 00800000 00200000 "boot"
mtd3: 18000000 00200000 "system"
mtd4: 04000000 00200000 "cache"
mtd5: 80000000 00200000 "userdata"
mtd6: 62000000 00200000 "NFTL_Part" <- now this is weird
mtd7: 00002000 00001000 "ubootenv"
mtd8: 00400000 00001000 "ubootwhole"

cat /proc/cpuinfo
Processor : ARMv7 Processor rev 1 (v7l)
BogoMIPS : 1466.36
Features : swp half thumb fastmult vfp edsp neon vfpv3
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x1
CPU part : 0xc09
CPU revision : 1

Hardware : AMLOGIC MESON-M1 8726M
Revision : 0020
Serial : 000000000000000b

uname -a
Linux version 2.6.34 (liuese@ThinkCenter) (gcc version 4.4.1 (Sourcery G++ Lite 2010q1-202) ) #80 PREEMPT Mon Sep 10 15:03:40 CST 2012

My main concern is that in the latest firmware update available from the constructor, there is no such thing as u-boot-aml-ucl.bin/ethmac.efuse/uImage_recovery, I just have a factory_update_param.aml & an update.zip file, nothing else.
So I wonder if I should only try to flash with the update.zip & factory_update_param.aml. What do you think?

I saw as well that the recovery/recovery-from-boot.p from the 4.0.3 constructor's firmware (h*ttp://storage.energysistem.com/archivos/drivers_y_actualizaciones/cjmcgogljdff_FW_Android_4.0.3_10-09-2012_rev01.rar) is different from the one available in your latest update. Is this bad?

Please let me know what you think, I already rooted my box, but I'm not sure I should go ahead with this update if my bootlader is at risk

Many thanks in advance for your help

b0b0

 

[stane1983]

Hello everybody

I have a question for you guys... Do you think I can safely try to flash my box with you latest c03ref version?

I bought an Energy Sistem Smart TV Box
h*ttp://www.energysistem.com/en-en/products/centro_multimedia/serie_media_center/38313-energy_android_smart_tv_box/specs
report:
h*ttp://androidfragmentation.com/database/v/dr/592149/oem/MBX/dm/Android%20Smart%20TV%20Box/carrier/Unknown

It looks very similar to the c03ref box you guys are "playing" with.

Couple of specs:
cat /proc/mtd
dev: size erasesize name
mtd0: 00800000 00200000 "aml_logo"
mtd1: 00800000 00200000 "recovery"
mtd2: 00800000 00200000 "boot"
mtd3: 18000000 00200000 "system"
mtd4: 04000000 00200000 "cache"
mtd5: 80000000 00200000 "userdata"
mtd6: 62000000 00200000 "NFTL_Part" <- now this is weird
mtd7: 00002000 00001000 "ubootenv"
mtd8: 00400000 00001000 "ubootwhole"

cat /proc/cpuinfo
Processor : ARMv7 Processor rev 1 (v7l)
BogoMIPS : 1466.36
Features : swp half thumb fastmult vfp edsp neon vfpv3
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x1
CPU part : 0xc09
CPU revision : 1

Hardware : AMLOGIC MESON-M1 8726M
Revision : 0020
Serial : 000000000000000b

uname -a
Linux version 2.6.34 (liuese@ThinkCenter) (gcc version 4.4.1 (Sourcery G++ Lite 2010q1-202) ) #80 PREEMPT Mon Sep 10 15:03:40 CST 2012

My main concern is that in the latest firmware update available from the constructor, there is no such thing as u-boot-aml-ucl.bin/ethmac.efuse/uImage_recovery, I just have a factory_update_param.aml & an update.zip file, nothing else.
So I wonder if I should only try to flash with the update.zip & factory_update_param.aml. What do you think?

I saw as well that the recovery/recovery-from-boot.p from the 4.0.3 constructor's firmware (h*ttp://storage.energysistem.com/archivos/drivers_y_actualizaciones/cjmcgogljdff_FW_Android_4.0.3_10-09-2012_rev01.rar) is different from the one available in your latest update. Is this bad?

Please let me know what you think, I already rooted my box, but I'm not sure I should go ahead with this update if my bootlader is at risk

Many thanks in advance for your help

b0b0

From V-Play download section download DeviceChecker apk and see what you will get.

NFTL_Part is nand partition formatted as fat32 (usually) and mounted as media partition or internal nand storage or...

If you decide to try my firmware (only if DeviceChecker reports c03ref), replace my u-boot-aml-ucl.bin with original one.

EDIT: Also you probably should edit updater-script to remove date checks and resign update.zip. More info on that you can find in this thread.

 

[b0b0]

Hi Stane, thanks for your answer.

I already tried your "DeviceChecker" and it reports c03ref.
Now, about replacing your u-boot-aml-ucl.bin with original one is where the problem is... I don't find it anywhere.
Any idea on that one?
I understand perfectly the updater-script edition to replace the check and recompile the update.zip...

About "NFTL_Part is nand partition formatted as fat32 (usually) and mounted as media partition or internal nand storage or...":
Is this a bad thing that I do have this, compare with your model that doesn't? Will your update whipe this out and break my box or will I be fine without it? (sorry for all these questions, I've been through the WHOLE thread and couldn't find anything related to this)... I'm really desperate to try other firmwares on my box, but looking at the partitions that don't match other firmwares, I'm a bit reluctant...

Thanks a lot for your thoughts on that one, as Energy sistem release another firmware update today, and so far, no news of cifs, which i want A LOT...

b0b0

 

[stane1983]

Hi Stane, thanks for your answer.

I already tried your "DeviceChecker" and it reports c03ref.
Now, about replacing your u-boot-aml-ucl.bin with original one is where the problem is... I don't find it anywhere.
Any idea on that one?
I understand perfectly the updater-script edition to replace the check and recompile the update.zip...

About "NFTL_Part is nand partition formatted as fat32 (usually) and mounted as media partition or internal nand storage or...":
Is this a bad thing that I do have this, compare with your model that doesn't? Will your update whipe this out and break my box or will I be fine without it? (sorry for all these questions, I've been through the WHOLE thread and couldn't find anything related to this)... I'm really desperate to try other firmwares on my box, but looking at the partitions that don't match other firmwares, I'm a bit reluctant...

Thanks a lot for your thoughts on that one, as Energy sistem release another firmware update today, and so far, no news of cifs, which i want A LOT...

b0b0

Hi,

you can extract uboot from installed firmware first by reading ubootwhole partition and then extracting bootloader part with some hex editor.

Example of extracting bootloader:
in your cat /proc/mtd you can see that ubootwhole is on mtd8, so
install Terminal on your box, type su (you said you rooted your device) and give su permission to Terminal app.

now:

dd if=/dev/mtd/mtd8 of=/sdcard/uboot.bin

this will copy content of your SPI chip to uboot.bin on your sdcard. Upload it somewhere and I'll see what I can do about extracting bootloader from it.

About media partition, my fw doesn't use media partition so it will be erased and overwritten with new partitioning my fw uses (it's possible you'll have to install fw twice).

 

[b0b0]

Wicked!
Here's the uboot.bin, thanks a lot for looking into it, it's really nice of you.
Download uboot.bin from Sendspace.com - send big files the easy way

One question about media partition: do you think that if I ever want to go back to original firmware it's gonna bring me problems?

I think cifs.ko is included in your firmware, since I read it somewhere, but could you confirm it before us going ahead with all this?

Thanks again in advance,

b0b0

 

[Andolini]

I too own a energy sistem. Stane's firmware works perfectly in it. Sin Problemas.

The real deal for me is to get dd/dts passthrough for a real HD multimedia system. Other android platforms like xios have this ability. Stane, have you plans in this way?

thank you

 

[b0b0]

@Andolini: thanks a lot for the confirmation...
Where do you get the uboot file u-boot-aml-ucl.bin to start with?
Did you just flash it straight away without modifying anything?

 

[Andolini]

@Andolini: thanks a lot for the confirmation...
Where do you get the uboot file u-boot-aml-ucl.bin to start with?
Did you just flash it straight away without modifying anything?

The only change was replacing the remote file with the one who comes into our original firm, because the remote from visson has different codes. Then just flash with a usb (edit param file and change "sdcard" with "udisk").

 

[b0b0]

Thanks a lot, it's very reassuring...
I already have my hands on that remote file...
from what Stane is saying, you need to replace the uboot file to keep the bootloader intact... is your recovery still working OK? (I think if you keep the power button pressed 3 seconds you should access the recovery... at least it works this way for the moment).

 

[Andolini]

No problem in recovery. Yo can flash visson firm and then energy firm without problems. You almost can flash gb firm. No need to replace uboot ( i think exact partition table on both)

 

[b0b0]

ok then I'll give it a try....
done and...
if I update the factory_update_param.aml file to say:
--update_package=/udisk/update.zip
--update_patch=/udisk/market_patch.zip
and go through the applications/update app, and reboot to update the box, here

 

[stane1983]

Thanks a lot, it's very reassuring...
I already have my hands on that remote file...
from what Stane is saying, you need to replace the uboot file to keep the bootloader intact... is your recovery still working OK? (I think if you keep the power button pressed 3 seconds you should access the recovery... at least it works this way for the moment).

Hi,

seems you found an answer to your question

Anyway, I extracted bootoader (indeed, it seems to be the same as Vissons) and uImage_recovery from binary file you sent me.

You guys can store zip for just in case. Download from here:
Download bootloader_recovery.zip from Sendspace.com - send big files the easy way

Regards

 

[stane1983]

ok then I'll give it a try....
done and...
if I update the factory_update_param.aml file to say:
--update_package=/udisk/update.zip
--update_patch=/udisk/market_patch.zip
and go through the applications/update app, and reboot to update the box, here

 

[b0b0]

Thanks so much Stane,

I'm RE-flashing the box just now... and I've downloaded the bootloader_recovery.zip you just uploaded.

When you say "make sure you use my uImage_recovery", you mean the one in your firmware or the one you just sent me?

Rebooting box... I just had the flat green android logo and now a black screen (haven't seen the android glowing logo for the moment...).

 

[stane1983]

Thanks so much Stane,

I'm RE-flashing the box just now... and I've downloaded the bootloader_recovery.zip you just uploaded.

When you say "make sure you use my uImage_recovery", you mean the one in your firmware or the one you just sent me?

Rebooting box... I just had the flat green android logo and now a black screen (haven't seen the android glowing logo for the moment...).

Hi,

"My uImage_recovery" means uImage_reovery from my firmware There is also part which is responsible for system partitioning, and partitioning for my fw is not the same as for yours.

 

[b0b0]

lol fair enough, thanks for the warning!

DAMMIT !!!! IT'S WORKING !!!!
YIHAAAA ... man I'm so glad!! Thanks so much !!
It seems that I tried to update everytime with usb stick, and I should have done it via the sdcard slot from the start !!...

Ok, now let's play !!! I'll get back to update you guys... thanks again for the help !! I'm loving it !!
Merci !!!

 

[b0b0]

Looks like I was too happy too fast
Anyway... no worries, I'm glad to have been able to flash my box with this firmware...
For now,
-I don't have adb access to the box (no idea why)...
-I don't have root neither,
-wifi is not working,(stuck while trying to activate)
-and the TV app is missing...I tried to take it out of the official firmware but no luck...

Once I manage to move forward with these then I'll be a bit happier

*and of course, most keys of the remote like Web, App, Settings etc do not work... (I took the remote.conf file out of the official firmware)

Thanks again A LOT for all your help, I'm quite happy to search more about it...

b0b0

 

[chrisdroid33]

Hi Stane1983,
i have an energy sistem Android tv box.
i miss some feature and would like to modify the original rom.
but i'm unable to unpack boot.img. I tried extractboot and unpack-bootimg.pl unsuccessfully :

$ ./extractboot boot.img

Android Magic not found in ./boot.img. Giving up.

gzip: ../../boot.img-ramdisk.gz: No such file or directory

cpio: fin prématurée de l'archive


$ ./unpack-bootimg.pl boot.img

*Subroutine Cwd::cwd redefined at /usr/lib/perl5/5.14/i686-cygwin-threads-64int/Cwd.pm line 407.

Subroutine Cwd::fastcwd redefined at /usr/lib/perl5/5.14/i686-cygwin-threads-64int/Cwd.pm line 819.

Name "DynaLoader::CARP_NOT" used only once: possible typo at /usr/lib/perl5/5.14/Carp.pm line 345.

Name "Cwd::CARP_NOT" used only once: possible typo at /usr/lib/perl5/5.14/Carp.pm line 345.

Name "File:ath::CARP_NOT" used only once: possible typo at /usr/lib/perl5/5.14/Carp.pm line 345.

Name "Exporter::CARP_NOT" used only once: possible typo at /usr/lib/perl5/5.14/Carp.pm line 345.

Could not find any embedded ramdisk images. Are you sure this is a full boot image?

any idea ?
how did you do it when you customized yours ?
thanks