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

[polys]

I managed to install the mbox fw using the magic SD card. Booted fine but then would still not get into recovery to go to the next step and install Matricom's original 1.1.5. Tried dextar's nand scrubber again but this time followed by Mbox installation (again) but this time nothing appeared on the screen. Now it won't boot into the ROM.

[sukhbeer]

no this is not normal which is why your most likely failing the flashes. Maybe something is wrong with your card reader or the actual sd card. If you ahve another card to test and if it says the same thing then you have a bad card reader. Your best bet is to use a cheap sd to usb converter off **** to do the job


hmmm something else i thought off. Did you uncompress the zip file first to get the raw hdd image file? it wont work if your selecting the zip file

Couple of things -

I was using Windows 8 (Asus laptop in built memory card reader), 8 gb Ultra Sandisk SD card, and I did not compressed the Benibenassai's downloaded file just used HDD tool to make the card

I will use Kingston 8 GB SD card today and also I will use my mac where in I have windows 7 in other partition installed.

Will see how I go once I get home and will let you guys know.

[kerikhaos]

I managed to install the mbox fw using the magic SD card. Booted fine but then would still not get into recovery to go to the next step and install Matricom's original 1.1.5. Tried dextar's nand scrubber again but this time followed by Mbox installation (again) but this time nothing appeared on the screen. Now it won't boot into the ROM.

the nand scrub basically wipes everything from the rom disk - all partitions and all hidden partitions leaving it a blank space ready to install the new firmware on the sd.

Your problem seems to be revolving around unsuccessful flashes. Your nand manages to install the system ok but for some reason does not install the recovery partition.

test for you..........

once you install any working firmware and it boots ok - go to play store and download the terminal emulator and then run it. It will be like a dos command windows - type in the window exactly this command and then press enter

cat /proc/mtd

this will print out your partition table.

write it down somewhere and then post it back on here so we can see what partitions you have ready to compare with a working partition layout.

[kerikhaos]

Couple of things -

I was using Windows 8 (Asus laptop in built memory card reader), 8 gb Ultra Sandisk SD card, and I did not compressed the Benibenassai's downloaded file just used HDD tool to make the card

I will use Kingston 8 GB SD card today and also I will use my mac where in I have windows 7 in other partition installed.

Will see how I go once I get home and will let you guys know.

thats your problem - the large file you downloaded containing the image file needs to be extracted to give you the 1x large disk image file. Make sure the file is not in zip or rar format. then proceed to make the magic sd card

[sukhbeer]

thats your problem - the large file you downloaded containing the image file needs to be extracted to give you the 1x large disk image file. Make sure the file is not in zip or rar format. then proceed to make the magic sd card

Tried that -

Did complete nand scrub using Dexsta's file
created Magic card with success this time and there were firmware files in the SD card this time

Booted into recovery and left it on for 30 minutes and restarted the device still blue light only and black screen

[kerikhaos]

Tried that -

Did complete nand scrub using Dexsta's file
created Magic card with success this time and there were firmware files in the SD card this time

Booted into recovery and left it on for 30 minutes and restarted the device still blue light only and black screen

something still must be wrong with the way the card is being read or formatted. I know that windows 8 could be the problem as sometimes can the internal card readers of some systems especially laptops cause incorrect formatting. To be sure of the formatting use 2 different sd cards and possible do the format on a different machine with an older OS. Windows 7 or XP have usually the best results from what i can tell. You sd card reader may also need changing (see if you have a usb adapter to use)

You should be getting a flashing colour show up just at the beginning of the recovery so you can sure your going in the correct direction.

also try take your motherboard out of the casing and try again - check board for signs of damage also (sometimes there may be a burn smell present if you have sustained electrical damages)

let us know how you get on

[goldorak]

MX Android 4.2 Dual-Cotex A9 1.5GHz TV Box - unable to flash proper firmware



Hello,
I have two MX BOX / Amlogic 8726MX_V1.1 and cannot install MXlinux as I regularly do on my box. I think it is about the firmware. The steps Itook initially is as follows :

1. Flashed Matricom 1.1.5 – unable to flash –installation aborted
   
   
2. I tried Matricom 1.1.6 instead installedcorrectly. Now I tried to install MX linux with Gotham and also tried MX linuxnew MTD. All are acting strange either stuck on XBMC Gotham 13.2 loading andflashing.
   
   
3. I tried running matricom 1.1.8 over 1.1.6.Unable to install any MX Linux – error assert failed
   
   
4. At some point I had lost everything and had ablack screen since I tried so many stuff I did not even kept track but was ableto get it back to matricom firware 1.1.6 using dextars-nandscrubber.zip on POST #301
   
   

I am really hoping someone could help identify what boardare these and how to get mx Linux properly installed. I spent 2 week almost trying to get linux xbmc gotham 13.2 runningon it. I have attached pictures of both motherboard . Thank you for all theprevious resources provided in the previous post of this forum.

[kerikhaos]

Hello,
I have two MX BOX / Amlogic 8726MX_V1.1 and cannot install MXlinux as I regularly do on my box. I think it is about the firmware. The steps Itook initially is as follows :

1. Flashed Matricom 1.1.5 – unable to flash –installation aborted
2. I tried Matricom 1.1.6 instead installedcorrectly. Now I tried to install MX linux with Gotham and also tried MX linuxnew MTD. All are acting strange either stuck on XBMC Gotham 13.2 loading andflashing.
3. I tried running matricom 1.1.8 over 1.1.6.Unable to install any MX Linux – error assert failed
4. At some point I had lost everything and had ablack screen since I tried so many stuff I did not even kept track but was ableto get it back to matricom firware 1.1.6 using dextars-nandscrubber.zip on POST #301
   
   

I am really hoping someone could help identify what boardare these and how to get mx Linux properly installed. I spent 2 week almost trying to get linux xbmc gotham 13.2 runningon it. I have attached pictures of both motherboard . Thank you for all theprevious resources provided in the previous post of this forum.

It looks to me you have the original boards from back in the old days when matricom started issuing the first mx boards in the series. They seem to be fine taking the current firmware a as well
as those from ace max, android gadget and droid player UK. The reason you are failing flashes on matricom 1.1.5 and possible other older firmwares because you are already on newMTD layout. You can't install 1.1.6 if 1.1.5 fails unless the fw is already on their with newMTD.

you should test with the following method. If your 1.1.6 then go and test the condition of fw by checking if the storage space. Does the fw detect all the partitions of the disk and can you install software without errors? If yes you go flash direct the openelec fw downloadable at the matricom forum. Read carefully instructions. Mx Linux is old school now and uses old mtd. You are on new mtd so don't bother flashing it with that. Good luck

[goldorak]

It looks to me you have the original boards from back in the old days when matricom started issuing the first mx boards in the series. They seem to be fine taking the current firmware a as well
as those from ace max, android gadget and droid player UK. The reason you are failing flashes on matricom 1.1.5 and possible other older firmwares because you are already on newMTD layout. You can't install 1.1.6 if 1.1.5 fails unless the fw is already on their with newMTD.

you should test with the following method. If your 1.1.6 then go and test the condition of fw by checking if the storage space. Does the fw detect all the partitions of the disk and can you install software without errors? If yes you go flash direct the openelec fw downloadable at the matricom forum. Read carefully instructions. Mx Linux is old school now and uses old mtd. You are on new mtd so don't bother flashing it with that. Good luck

Thank you. I will check and revert back again. Openelec is great but one app that I need does not work on it. Pulsar. But I will try as recommended. Thanks again

[goldorak]

Thank you. I will check and revert back again. Openelec is great but one app that I need does not work on it. Pulsar. But I will try as recommended. Thanks again

@kerikhaos i finally was able to test. Yesterday i had the 1.1.6 to 1.1.8 on the box. Tried to upgrade the firmware to Matricom 1.2 using update option in Android. Installed Openelec over it from matricom forum..works fine as you suggested. I am hoping not to have any issues with the matricom 1.2 looks good until now.

I have one more question though since i can't use Pulsar on Openelec, do you know why i can't install MX linux new MTD (pulsar works fine on it) on the matricom firmwares. I would like to keep the openelec but not being able to use Pulsar is killing me...Any suggestions?

Thanks a lot for all the good job here and advise you provide to us.

[kerikhaos]

@kerikhaos i finally was able to test. Yesterday i had the 1.1.6 to 1.1.8 on the box. Tried to upgrade the firmware to Matricom 1.2 using update option in Android. Installed Openelec over it from matricom forum..works fine as you suggested. I am hoping not to have any issues with the matricom 1.2 looks good until now.

I have one more question though since i can't use Pulsar on Openelec, do you know why i can't install MX linux new MTD (pulsar works fine on it) on the matricom firmwares. I would like to keep the openelec but not being able to use Pulsar is killing me...Any suggestions?

Thanks a lot for all the good job here and advise you provide to us.

the pulsar feature is still a work in progress service which uses torrents to stream as far as im aware. Another similar plugin service is the p2p which uses pretty much the same technology but streams mostly live channels rather than media threads.

My advice would be to post your question to codesnake (developer of the openelec fw) directly on the matricom forum specifically for the openelec software and see if you can get some support on that problem from him hes usually good at responding to questions and bug finding.

You can find the specific thread here but you must sign up to post

https://forums.matricom.net/viewtopic.php?f=9&t=11823

Im glad you managed to get your openelec sorted on your box, its always good practise to jump from 1.1.6 to openelec rather than a higher matricom fw since its been declared people get many problems jumping from any other fw other than 1.1.6. - im not sure if this relates to your problem with pulsar

[barnesy91]

Hey guys,

Having serious issues with one of my MX boxes, Blue light no display.

Heres what i've done;

1.Create magic sd card using 1.1.5 image on an 8gb sd card
2.All copies ok, reached 100% and successfully written
3.Remove all files off sd card and put in a temporary folder, and copy Dextars nand scrubber files onto root
4.insert SD card into mx box, hold down recovery button and insert power. Keep recovery button held down for 2 minutes, Leave box for 20 minutes. Remove sd card and copy original files back onto it.
5.Unplug mx box, insert sd card, Hold down recovery button and insert power, Keep held down for 2 minutes. Leave box for 30 minutes.
6.Unplug mx box, remove sd card, and plug power back in.

Still nothing

Here's a picture of my board.



Hope somebody can help.

Thank you

[kerikhaos]

Hey guys,

Having serious issues with one of my MX boxes, Blue light no display.

Heres what i've done;

1.Create magic sd card using 1.1.5 image on an 8gb sd card
2.All copies ok, reached 100% and successfully written
3.Remove all files off sd card and put in a temporary folder, and copy Dextars nand scrubber files onto root
4.insert SD card into mx box, hold down recovery button and insert power. Keep recovery button held down for 2 minutes, Leave box for 20 minutes. Remove sd card and copy original files back onto it.
5.Unplug mx box, insert sd card, Hold down recovery button and insert power, Keep held down for 2 minutes. Leave box for 30 minutes.
6.Unplug mx box, remove sd card, and plug power back in.

Still nothing

Here's a picture of my board.



Hope somebody can help.

Thank you

wow wow wow, relax a bit because your jumping the gun with many of the steps and not doing the absolute minimum first to make sure the problem is far more serious than it is.....

my opinion (from the pic you have a HD18 V2.22 board) is to do the following.

1. Format sd card (8gb - make sure its class 10) on a windows machine preferably on a windows sp XP machine but nothing higher than windows 7.

2. Make you are not formatting the SD card in a built in card reader of a laptop (use either a usb converter or a usb card reader drive)

3. Confirm all file are present on the sd card from the magic hdd image creation process

4. Without touching any files on the sd card begin recovery process with toothpic - this means all plugs disconnected accept power and hdmi cable. While you have recovery button pressed and then carefully power on you need to check for a flash of colour on the screen to confirm card is being read correctly

5. Even if no flashing colours are seen leave the recovery button pressed for a good 2 mins and then release. Wait 30 mins and then power off the system by pulling the power.

6. Remove SD card and power on again with no other cable inserted

7. Wait for a matricom log to pop up

good luck

[barnesy91]

wow wow wow, relax a bit because your jumping the gun with many of the steps and not doing the absolute minimum first to make sure the problem is far more serious than it is.....

my opinion (from the pic you have a HD18 V2.22 board) is to do the following.

1. Format sd card (8gb - make sure its class 10) on a windows machine preferably on a windows sp XP machine but nothing higher than windows 7.

2. Make you are not formatting the SD card in a built in card reader of a laptop (use either a usb converter or a usb card reader drive)

3. Confirm all file are present on the sd card from the magic hdd image creation process

4. Without touching any files on the sd card begin recovery process with toothpic - this means all plugs disconnected accept power and hdmi cable. While you have recovery button pressed and then carefully power on you need to check for a flash of colour on the screen to confirm card is being read correctly

5. Even if no flashing colours are seen leave the recovery button pressed for a good 2 mins and then release. Wait 30 mins and then power off the system by pulling the power.

6. Remove SD card and power on again with no other cable inserted

7. Wait for a matricom log to pop up

good luck

Followed to the tee mate, Nothing.

No flash of colour either, Just a black screen.

[kerikhaos]

Followed to the tee mate, Nothing.

No flash of colour either, Just a black screen.

in my experience its a very small percentage you have hard bricked the box since you get a blue light etc. Either something is wrong with your process of creating the sd card or something physical is the problem (ie bad sd card etc). Try getting another sd card to test also try and see if you get any actvity by plugging in a live ethernet cable in the back. Do lights come on and off to show activity?

The black screen is just because the nand is screwed up and there is no functional software on the rom. Use the nand scrub files again....leave them to work for about 20 mins. Then use the magic sd files as they were installed by default to run recovery. Leave again for 30 mins

If its not working then you may have to to send it out to get unbricked - providing you have not damaged it physically