Solution for stuck in Android load AML8726-MX Dual Core TV Box Android 4.2.2

[daemonium]

Re: Solution for stuck in Android load AML8726-MX Dual Core TV Box Android 4.2.2

this is a confirmed solution by thousands worldwide (in addition the 2 extra files provided by dexstar is only if you are in the small group of people who have managed to do something nasty to their nand beyond the standard procedure).

My opinion is that its 90% user faults not following the correct instructions as i have seen in the past but in the given circumstances those who have got more serious bricks have now the ability to use the dexstar method (which looks like the software version of the uart method) - then use the magic sd from bennibenassi afterwards

Be careful, there are a lot of tvboxes that look equal to mx2 but are not really compatible. So using, magic sdcard only will work if the proper uboot and rom are used but not matricom's.

[kerikhaos]

Be careful, there are a lot of tvboxes that look equal to mx2 but are not really compatible. So using, magic sdcard only will work if the proper uboot and rom are used but not matricom's.

Thats why the owner must confirm the following references to the board

G18REF
HD18 V2.0 - V2.22

If you have these boards then you have original matricom compatible board and you should be safe to flash (providing you follow the procedure carefully and exactly as described in the instructions)

the risk is down to the owner and if followed correct then your box should bounce back to life unless its hard bricked with a physical hardware problem

[kerikhaos]

to follow up my earlier post about jumping matricom firmware 1.1.5 to 1.1.6:

has anyone found a way to do this properly (upgrade to 1.1.6 without problems - after first boot a rstart results in a brick and no space available to install anything)

i have tried left right and center to do this but without success - please post if you have got a procedure which works. Matricom have knocked out the OTA software in 1.1.5 and 1.1.6 and this can only be done now through recovery or upgrader software - both which fail

also another thing i need is for someone to post me the mtd partitions on a successful flashed matricom 1.1.6 or newer firmware so i can compare some newer chinese roms i have from this month and last whcih have also changed in partition layouts.

For those who need instructions on how to do this please do the following:

log into play store and download terminal emulator (any version will do)

when the program installs open it and type the following command exactly as you see it here

cat /proc/mtd

this will produce a list of partitions (around 7-10 depending on what you have)

can you please print this out for me to analyze in order to help e find a way for us to successfully jump to matricom 1.1.6 and above to the newer 1.2.2

thanks

[Jarv1ss]

I've created the SD card and when I attempt it the green android appears and a full progress bar appears then sticks, then starts again. This is like it's trying to verify the update and is in a loop. Only lasts a couple of seconds but an infinite loop of these 2 seconds. I'm using the correct board btw. Anyone ever experienced this?

[kerikhaos]

I've created the SD card and when I attempt it the green android appears and a full progress bar appears then sticks, then starts again. This is like it's trying to verify the update and is in a loop. Only lasts a couple of seconds but an infinite loop of these 2 seconds. I'm using the correct board btw. Anyone ever experienced this?

take your sd out when it goes black to restart - otherwise it will go through the recovery process again.

if its not this then you need to use the 2 files dexstar has provided earlier in the thread

[Jarv1ss]

take your sd out when it goes black to restart - otherwise it will go through the recovery process again.

if its not this then you need to use the 2 files dexstar has provided earlier in the thread

OK. I'll try that in a bit but first I want to confirm I'm doing the card right. When I downloaded the 1.1.5 I extracted it and in side there is an image. This is the file I select as the source in hdd/raw? Then I select the 4gb SD card as the target?This is what I did and it took about 10 minutes to write to the card. Then I closed hdd/raw and eject safely. That all correct? Or do I use the 115.zip as the source without extracting? I expect it's the first option.

[kerikhaos]

OK. I'll try that in a bit but first I want to confirm I'm doing the card right. When I downloaded the 1.1.5 I extracted it and in side there is an image. This is the file I select as the source in hdd/raw? Then I select the 4gb SD card as the target?This is what I did and it took about 10 minutes to write to the card. Then I closed hdd/raw and eject safely. That all correct? Or do I use the 115.zip as the source without extracting? I expect it's the first option.

this is how you use the hdd tool - you need to extract the image file to that image file out of the zip. You then run the hdd tool and select the image you extracted from the zip file. You then need to select the sd card and then wait for the image to install. Once its done you can now use to recover

[kerikhaos]

ok so from reading multiple threads, posts and articles about the HD18 V2.22 boards there definitely has some hardware checking system from version 1.1.6 matricom fw and above.

The system no matter what and how a upgrade is executed there is a small abortion at the end - the firmware does successfully load once then after reboot black screen of death.

I have compared mtd layouts and everything else under the sun to figure out why all of a sudden upgrades from a matricom 1.1.5 flashed box wont successfully upgrade to new mtd layout matricom 1.1.6

im calling this a day and admit the limits of the unit matricom has somehow managed to block upgrades via either hardware checking the mac address or some other ID on the motherboard - the standard upgrade process ota has stopped from pre 1.1.6 fw and anything from a sd card to usb stick just fails

if anyone else has had success please send instructions of what you did so we can follow by example. (This is for education purposes only and to be honest matricom fw is miles behind the newer chinese mbox fw which have come out in the last month or so)

any feedback on this is welcome - thanks

[orest]

vigica c60s blocked with green led help

Hello everyone
I have a Android DVB-S2 Satellite TV Receiver
Vigica C60S AML8726 MX 1G-4G Dual Core Android 4.2
and is Blocked and no makes boot from sd card and not reset button
sometimes the update starts but gives me error.
someone who can help me please.

https://yadi.sk/d/VrJW_VtBJqfJJ/vs_ip015_sdboot_PINs.jpg

[kerikhaos]

https://forum.matricom.net/index.php?topic=12396.0

just so everyone knows where I am with this issue about the 1.1.6 fw - this is something I posted earlier on the matricom website waiting for some help on the matter before I give up completely on the matricom fw totally (means no openelec for my boxes though)

check the link in title thread

[c2k]

just so everyone knows where I am with this issue about the 1.1.6 fw - this is something I posted earlier on the matricom website waiting for some help on the matter before I give up completely on the matricom fw totally (means no openelec for my boxes though)

check the link in title thread

I had an issue with a 2.22 board that would not update correctly, an Openelec install would fail with the black screen after the openelec logo appeared - attaching a keyboard and pressing return showed the error message about unable to connect to the terminal.

I finally managed to update it by:

1. Installing the original Chinese firmware
2. Installing the Finless rom over the top
3. Using daemoniums' files on a 'magic card' to erase the flash - leaving it for a few minutes to finish
4. Recreated the 'magic card' and recovery booted with it in box to install 1.15 software
5. Rebooted box with no SD card in it, to recovery. Used same 'magic card', deleted files off it and copied 1.16 files onto it. From recovery menu then selected 1.16 file and installed.
6. Booted box completely after install to complete setup of 1.16
7. Rebooted into recovery and installed Openelec from a different SD card.

Suprised to see that it actually worked as I was expecting the usual black screen.

[kerikhaos]

I had an issue with a 2.22 board that would not update correctly, an Openelec install would fail with the black screen after the openelec logo appeared - attaching a keyboard and pressing return showed the error message about unable to connect to the terminal.

I finally managed to update it by:

1. Installing the original Chinese firmware
2. Installing the Finless rom over the top
3. Using daemoniums' files on a 'magic card' to erase the flash - leaving it for a few minutes to finish
4. Recreated the 'magic card' and recovery booted with it in box to install 1.15 software
5. Rebooted box with no SD card in it, to recovery. Used same 'magic card', deleted files off it and copied 1.16 files onto it. From recovery menu then selected 1.16 file and installed.
6. Booted box completely after install to complete setup of 1.16
7. Rebooted into recovery and installed Openelec from a different SD card.

Suprised to see that it actually worked as I was expecting the usual black screen.

can you please point us to the correct finless rom you used for this job and also to the daemoniums files which you used for the nand erase. I guess these are different to the dexstar files for erasing?

thanks in advance

[c2k]

can you please point us to the correct finless rom you used for this job and also to the daemoniums files which you used for the nand erase. I guess these are different to the dexstar files for erasing?

thanks in advance

I used Finless Beta 1.1 (finless_beta_1_1_mx2) and it was dexstars erase file - I'd been using daemoniums files for something else yesterday and so wrote the wrong name (sorry)

[kerikhaos]

I used Finless Beta 1.1 (finless_beta_1_1_mx2) and it was dexstars erase file - I'd been using daemoniums files for something else yesterday and so wrote the wrong name (sorry)

thanks i will give it a try and let you know how it goes. I think the newer finless is version 1.4? I will use the one you used to simulate the same results

thanks for feedback and i will post back as soon as i can prove this theory works

[kerikhaos]

thanks i will give it a try and let you know how it goes. I think the newer finless is version 1.4? I will use the one you used to simulate the same results

thanks for feedback and i will post back as soon as i can prove this theory works

it just occurred to me that anything you before the nand erase would of most likely been pointless since after this step the nand is zeroed and is waiting new firmware from being wiped clean.

I cant see the logic of why it would effect the process rather than starting from the nand flash but to clarify again so im sure of your steps

once you erased the nand with dexstars files

1. you used the magic card again with the 1.1.5 image creation to begin an automatic hard flash of matricom 1.1.5

2. you rebooted back into recovery (you didnt boot into the 1.1.5 firmware at all im guessing) and flashed with the same memory stick 1.1.6 (3 files in root). You didnt first data reset or cache wipe?

3. installation passed with no errors in recovery terminal?

thanks again for your feedback