AML8726-MX Android Box MX jaibreak

[LuisF76]

Thanks for the firmware Luis, will have a look at it. This is for generic MX box, correct? Can you take a screenshot of Settings>About and the MTD layout (cat /proc/mtd in the terminal app)? That would be greatly appreciated.
I just went from 1.1.4 fw to MX Linux (Gotham 13.1, one from Matricom's forum) for now, and may have to stay with it. It is stable and runs good. I was just tempted with the OpeElec release....

Sent from my TF300T using Tapatalk

is for generic MX box from yeyeat
about MTD I don't know how to do it

[kozmo2k4]

Re: AML8726-MX Android Box MX jaibreak

is for generic MX box from yeyeat
about MTD I don't know how to do it

Install Terminal Emulator from Play, open it; type:
su
you'll be prompted to grant SU access, allow
then type:
cat /proc/mtd
it will print to screen the partition layout. To exit the Terminal, type
exit
twice, that will close the app.

Sent from my TF300T using Tapatalk

[dairug]

Hi Guys

Had a brainwwave this morning.

I opened up the following files for a look this morning, bearing in mind my MX box will only factory reset with these files on the card along with the rom image and recovery.img.

AML_Autoscript

'VÇ_DSà)`°9˛/amlogic auto scriptXif mmcinfothen
if fatexist mmc 0:1 u-boot.bin
then fatload mmc 0:1 82000000 u-boot.bin
echo @@@@@@@@@@@@@@@@@@@@@@@@ erase spiflash : need about one minute @@@@@@@@@@@@@@@@@@@@@@
sf probe 2
sf erase 0 600000
sf write 82000000 0 60000
echo @@@@@@@@@@@@@@@@@@@@@@@@ erase nandflash @@@@@@@@@@@@@@@@@@@@@@
nand erase 0
reset
fi
fi

Also there is this one
factory_update_param.aml

--update_package=/sdcard/g18ref-ota-20140620.zip
--wipe_data
--wipe_cache
--wipe_media



I suspect the key to loading up the desired roms onto my box as well as Luis's comes from here. I have amended the file on the card and amended the factory_update_param.aml to point it to the amended image and I can now factory reset my choice of images on an SD card that will also unbrick the device.

Ssying that, I still get the same behaviour when loading up images. For example, 1.1.4 matrcom won't flash as previously. Am Linux will flash but fails on the second boot getting stuck on the @9 boot screen as it did when I flashed it from the Android recovery or from the OTA menu.

Does anyone understand the commands in the aml_autoscript as it appears to completely reflash the nand. I'm hoping there may be a solution to flash the desired image and update the boot loader or MTD partitions at this stage which could then fundamentally change the way the box behaves (and maybe make the recovery process less restrictive).

Are there linux images that are old MTD as well as New MTD. If I'm correct, presumably one of these images should work nicely?

Any thoughts?!

Thanks
Chris

[kozmo2k4]

The AML_autosript I wouldn't touch, above "my paygrade". The param.aml can be changed to specify your update.zip.
There are MX-Linux 13.1 builds for both Old and New MTD (have a look over at Matricom's forum...). You have to use caution as not to mix those two, because NewMTD has a different Bootloader on top of the partition layout...
I flashed the 13.1 Old MTD MX-Linux over 1.1.4, and everything is running good, so I'll leave it like it is, for now...

Sent from my TF300T using Tapatalk

[Meltdown]

The market is being flooded with these cheap boards. It's getting ridiculous.

[dairug]

Hi Meltdown - you're not wrong by the looks of it. I never thought for one minute I'd end with a box that has become nigh on impossible to flash.

Kozmo - If i upload my MTD layout, is it possible to determine whether I am old or new? I'm presuming I'm old being I was on a knock off 1.4.1 firmware. Maybe a Linux build for old MTD will do the trick. Will try again anyway. I've devoted two days into getting nowhere - what's another one!? You seem to have sorted yourself out then?

Luis - how you getting on?

Thanks
Chris

[kozmo2k4]

MTD Layout

Here is my initial (when I first bought the box) layout:


This is the ROM it came with:

Then I flashed Matricom 1.1.4, the OTA kicked in and I let it up to 1.1.5, but not the 1.1.6.

My current MTD as of yesterday:


Hop this helps...

[Finless]

OK a little help.

This error
Assert failed:write_raw_image ("/tmp/bootloader.img", "boot loader).

Is because the edify script in the ZIP is not correct for the labels of your partitions! Edit that script. Remove and assertion checks at the beginning, and edit the write line to say bootloader not boot loader.

You cannot use a kernel with different MTD. So you will need a kernel that uses YOUR MTD. Learn to pack and unpack boot.img. You can take a known good kernel and put it in boot.img from the ROM your trying to use. Usually this works but not always.

Also if it wont boot into recovery then the recovery partition does not have recovery in it! Some ROM you flashed or something erased that and did not write a good recovery in there. If uboot is good, just putting a recovery.img on sdcard should work without having to make a special sdcard. special sdcard is only needed when uboot is hosed up.

I am sure if I had this box I could get this solved for you.

Bob

[dairug]

Hi Bob

Thanks very much for the info. I'll go away and look at these files and see if I can figure out which route to take. May have a few further questions if you don't mind as this is reasonably new to me but I'm sure I'll grasp it at some stage!

Unfortunately for Luis and I, these boxes from this particular vendor came with the caveat that you have to pre prepare the SD card with an embedded Uboot.bin on a hidden partition that their card maker creates for you. Perhaps some weird way of them locking you into their awful firmware which is about as counter productive as it gets!

Anyways, thanks for the support!
Chris

[Finless]

Hi Bob

Thanks very much for the info. I'll go away and look at these files and see if I can figure out which route to take. May have a few further questions if you don't mind as this is reasonably new to me but I'm sure I'll grasp it at some stage!

Unfortunately for Luis and I, these boxes from this particular vendor came with the caveat that you have to pre prepare the SD card with an embedded Uboot.bin on a hidden partition that their card maker creates for you. Perhaps some weird way of them locking you into their awful firmware which is about as counter productive as it gets!

Anyways, thanks for the support!
Chris

I find it hard to believe they told you this is the only way. I think they told you that to recovery if your soft bricked. This certainly is not normal for AML to not be able to boot from recovery in NAND or even a recovery.img on SDcard.

Usual boot order for recovery is this:
1) Boot from recovery partition in NAND.
2) If recovery partition is bad in NAND boot a recovery.img from sdcard (but not using s special formatted sdcard).
3) If it cant boot at all bootloader is bad, then you use a special SDcard.
4) Hard brick is uboot totally gone and NAND is corrupt. Use pin to short NAND chip and boot from special card.

Bob

[no_spam_for_me]

I find it hard to believe they told you this is the only way. I think they told you that to recovery if your soft bricked. This certainly is not normal for AML to not be able to boot from recovery in NAND or even a recovery.img on SDcard.

Usual boot order for recovery is this:
1) Boot from recovery partition in NAND.
2) If recovery partition is bad in NAND boot a recovery.img from sdcard (but not using s special formatted sdcard).
3) If it cant boot at all bootloader is bad, then you use a special SDcard.
4) Hard brick is uboot totally gone and NAND is corrupt. Use pin to short NAND chip and boot from special card.

Bob

+1

I'm also wondering in and thought that I misunderstand it at the past because that's also my understanding how it will work (but BenniBenassi was able to brick one of his devices so "deap", that also special SD didn't work)...

[dairug]

Guys, apologies this is now spread over two threads.

I definitely didn't amend the behaviour of the device with any failed flashing attempts. Other than the stock firmware flashed as per the manufacturers instructions (which I'll post up shortly) the box hasbn;t successfully flashed any other images other than a few soft flashes through the OTA updater which fail and hang upon boot after the initial flash.

Bennibenassi's method didn't do anything so can't have ruined my boot loader?

Cheers
Chris

[cowley26]

HELP

HELLO PEOPLE i have a mx box wich i factory reset yesterday, i was passed a file wich was matricon firmware 1.2 installed it n did a reboot.....
and now alls im getting is the blue light on me box is on and me tv is sying no signal on all hdmi ports
is there any way of me plugging it usb-usb with me laptop and fixing this someway or another
please help thanks

[no_spam_for_me]

First you have to know which PCB this box use ...
and why do you try to flash 'matricon firmware 1.2'?

http://www.freaktab.com/showthread.php?15971-Which-firmware-for-this-box-Photo&p=214223

[cowley26]

First you have to know which PCB this box use ...
and why do you try to flash 'matricon firmware 1.2'?
http://www.freaktab.com/showthread.p...Photo&p=214223

Someone told me to download a file n put it on and when I did thishappened

how do I find out pcb it is mate my head is chocker mate