错误提示：发生了异常
抱歉！系统发生了错误!
麻烦您立即或发邮件至与管理员联系（联系电话：021-）。
网站导航：&&&&&&&&
技术改变世界！From Matricom Knowledge Base
was released in 2012 as the official successor to the . It sports a dualcore Amlogic A9 and the Mali400 video processor. It is capable of scaled 1080p playback, as well as nonscaled 1080p playback.
This was the first
device to support OTA updating and also migrated from 4.1 to android 4.2.
For all firmware and reflashing related issues with the MX2, see the
There are a few types of remotes that were featured with this device:
The stock IR remote that was included with the
The two remotes sport obvious differences:
G-Mouse II & G-Mouse FlyMote
Gyro Mouse control, similar to that of a Wiimote
USB Dongle
Rechargeable
Has the menu key (The
has this key as well)
Here is a link to the user manual that is included with the MX2.
This is for advanced users only. Changing these settings without proper knowledge can lead to catastrophic consequences.
Navigate to the Android settings.
Scroll to the very bottom and choose “About G-Box”
Highlight the “Build Number” and press “Ok” on the remote about 7~12 times until it says “You are now a developer”.
Congratulations you now have Developer options enabled.
Note: If you are using 1.1.7 or below, will say "About MediaBox".
To get shift and function keys working Navigate to:
Settings&Language & input&Keyboard & input methods&Default
Select the the hardware keyboard option and toggle the switch to the on position.
You can make your MX2 a hotspot for other wireless devices if you find the need to do so.
You will need the following items:
Ethernet Cable
Plug your MX2 into the Ethernet cable attached to your router or modem. Navigate to the android settings and under Wireless & Networks, choose Portable Hotspot. Before enabling the Hotspot, take a moment to set up the hotspot. You can configure the Network SSID, Security, and Password. Once set to your liking, enable the portable hotspot. This will disable your wireless connection and allow devices to connect to the MX2.
Using ES File Explorer to mount the root / as R/W.
First open up the ES File Explorer.
Once there, navigate to the left hand side where it says "Tools". Choose Root Explorer.
Check the dot under "R/W" to make sure that the partition is read and write.
As of this writing, the is fully rooted but not accessible by the user until you install a root manager or su manager. The 1.1.6 Firmware is preinstalled with a SuperUser application. On your box, go to your app drawer. You will see an application called "SuperUser". Open the application. Once you have opened the application you will be presented with a prompt to install the SuperUser "Su" binary. Choose the option to "install" and the application will install the "Su" binary. Now when you use an application the following prompt will display:
Note: Be extremely cautious of what apps you give root privileges. Some apps use root maliciously and Matricom is not responsible for sensitive information lost or stolen.
If you need to access files on an external SD card you can find them under: /storage/external_sd
Files on your USB drive are located in:/storage/usb/
(sda1, sdb1, sdc1, sdd1)
A common issue is how to setup a VPN on the . There are several steps involved with setting up the VPN.
First, navigate to the android settings screen. Under the "Wireless and Networks" settings, choose the "More" option.
Next, you will need to choose the "VPN" setting on the screen. It will prompt you to adjust your security settings on the MX2. Choose "OK" to be taken to the security settings screen. You will the option to choose between "Pattern", "Pin", and "Password".
Pattern - Allows you to set a pattern that needs to be swiped. This is not recommended.
Pin - A numerical password.
Password - An alphanumeric password.
Once you have your security settings completed, in the upper right hand corner, you will see a plus. Click on that and the VPN screen will appear. You will need your account information for the VPN to be able to successfully set it up. You will need to know the:
Server Address
The VPN is now completed and you can use it as you need.
Buffering is a common question within the XBMC application. Most users will want to resolve the buffering issue. To do so, follow the guide below:
First and foremost, we need to isolate the causes for the slow buffering. This can be achieved by a quick speed test. Download SpeedTest app from the Google Play Store and run the application or navigate to
on your browser. Once the results are in, navigate to
on your PC and run the same test. Compare both results and follow the scenario below:
The speeds do not match
The speeds do match
If the speeds do not match, the common issue is how it's connected. If you are using WiFi, connect to the Ethernet port if possible and run the speed test again. This will allow us to isolate the WiFi as a problem. If the speeds improve, the product may be to far from the access point or have a faulty wireless card. Contact a support representative for more information.
Please keep in mind that the MX2 has a limited wifi range and you would want to stay within 30-50 feet with no obstructions.
If the speeds match, you need to have the appropriate internet speeds to be able to play certain content. Refer to the table below for more information on what is recommended for proper streaming.
Down Stream (In Megabits Per Second)
SD Minimum
SD recommended
HD Minimum
HD recommended
If your speeds are above the recommended speeds, send a support email to our representatives for further assistance. In the email, please include your product, order number, and network configuration (including model numbers of your router or modem). The email is .
Another common issue is the servers are sometimes not operating at maximum potential. For instance, some
will be under heavy operating load and users will experience slow buffering. Isolate the add-on and perform a buffering test on your MX2. If you also have slow buffering, it's more than likely a sign that the server is experiencing high traffic. Remember that we have no control over
and so we will not have an ETA of a fix.
You can visit the
website(s) for more information
Always make sure that you are up-to date with the latest firmware updates which include updates to XBMC.
article for more information.
If you are having issues with the display ensure that you have auto detect disabled by going to:
Settings & Display & Auto Detect & Disable
Then navigate into your android settings and locate the display resolution:
Settings & Display & Display resolution
Adjusting the resolution for your screen should resolve the issue. Start at 720p and if this resolves the issue then go back into your display settings and readjust it to another resolution your TV supports.
This needs to be done if you are running an older firmware such as 1.1.2f and would like to update to 1.1.5.
This also needs to be done if you get the following error: “Cache wipe failed.” (See picture)
Download this file and extract the contents to the root of an SD Card:
Insert the SD Card into the MX2 and power the device off by unplugging the machine if it is not already unplugged.
Insert a toothpick into the back of the A/V port to press the hidden reset switch. Holding the reset switch down, plug the MX2 into the power source.
When the Matricom Logo appears, continue holding down the reset button for about 20 seconds until the screen changes to the green android with a progress bar at the bottom.
At this point you can remove the toothpick from the A/V port. Allow up to 5 minutes for the firmware to flash. Afterwards you can flash the latest firmware on the box.
Miracast is a protocol for mirroring one device to another. In this case, the MX2 supports Miracast for devices that support the Miracast protocol. To enable Miracast, open the Miracast application. Once it is opened on the device you wish to connect, choose the device name that matches the device name on the MX2. If prompted, press allow for the device to connect.
Note: When using miracast please disable your wifi connection.
Note: Samsung's Allshare is not a compatible Miracast stream with the MX2.
If there is no sound on 1.1.6, it is good to verify that the correct audio settings are in place. Navigate to the SettingsMbox & Advanced & Sound and make sure that "PCM" is the default.
Next it's good to isolate where the sound is not coming from. First, open up any Android app to see if the sound works here. If the sound works in the Android system, we can isolate it to . If sound does not work, then it's a system wide issue.
Preliminary Steps
Verify that all cables are plugged in correctly
Make sure Volume is up
Check volume on another device
Steps to fix Android Sound
Verify that the Volume is up on both devices
Make sure the HDMI cable is seated correctly
Power off both devices
Verify PCM is checked under Audio Settings
Test with an app
If this does not resolve the issue, a reflash is necessary in order to regain sound. If a reflash does not fix the issue, then a
claim must be made.
Steps to fix XBMC Sound
Follow the steps for the Android Sound
From the System & Settings & System & Audio Output:
Make sure the Speaker configuration matches.
Make sure "Output stereo to all speakers" is not checked.
Some may try to plug in a TOSLINK or a optical cable into the S/PDIF port of the MX2. This will not work because the port is analog. It still sends the digital signal, but it's converted to an analog signal only as a means of transport. A coaxial rca cable is required for S/PDIF to function properly.
The provided RCA cable that comes with the box will work for the S/PDIF output. You plug the 3.5mm Jack into the S/PDIF port and the Red RCA jack into the S/PDIF coaxial port on your receiver. Here is an example of such cable:
Currently Airplay is not supported in android versions of 13.0 Gotham.
This is a limitation of the XBMC software and relates to iOS7 and above.
If you are running on the Aeon Nox skin, you may notice the main menu disappear. In order to recover from it you will need to do the following:
With Aeon Nox, when you get the blank screen,
plug in a keyboard, press the "M" key. In the drop down menu select "Movies", once your movies display press the "Return" button on the remote and presto Nox is working again.
You can find the full discussion here:
If your device get's stuck at the Matricom Logo Screen, you can repair the bootloader file by simply following the below instructions.
First download the . Next you will need to download the latest
from above.
Extract the Boot Loop Recovery files onto an empty SD card. (Your SD card should have two files: u-boot.bin and recovery.img).
Insert the SD card into your MX2 and boot the MX2 holding the reset button located in the A/V port on the back of the device. You must hold this button with a toothpick while applying power to the device for about 10 seconds. You will see the “Matricom” logo appear on the screen. After about 10-12 seconds you will be presented with the Android recovery menu. Please unplug your unit (Your remote control will not be functional until after the next step).
Follow the instructions for installing the latest firmware located here: .
Your MX2 will now be back up and operational.
See the below video for visual instructions:
If you flashed the 1.2 update, and ended up with a useless MX2 that doesn't output any video, this post should help you recover it. Make sure to follow it step by step. Even the little things are important.
The recovery.img for 1.1.5 is the only way we have to recover this bug. Doing a manual update with 1.1.5 and allowing it to boot. Then reboot back into recovery, wipe data, and reboot again with 1.1.6 on the SD card. Let 1.1.6 install itself, then let it boot again. Follow the same process once more with 1.2.
Going from 1.1.5 to 1.2 caused the soft brick again, as did going from 1.1.5 to 1.1.7 and 1.1.8. I had to go up to 1.1.6 before any other beta versions or the 1.2 "stable" would flash properly.
Please use caution during this process as it is very easy to get confused and mix up the firmware files. Make sure that you keep the recovery.img together with its respective firmware zip. They are NOT interchangeable, so mixing them up will disrupt the whole process.
This guide assumes the device is currently stuck with you MX2 having the blue light on the front indicating it is powered on, but there is no video signal.
A minimum 2GB SD card is necessary and about 15 minutes of time for this guide. This guide will NOT work via USB.
Preparations:
Download the 1.1.5 and 1.1.6 firmware zips from this page.
Download the 1.2 firmware zip and recovery.img from the same link as above. (You do not need the AML script)
Copy all four files to the root directory (not in a folder) of your SD card.
Create three folders and name them 1.1.5, 1.1.6, and 1.2.
Move the 1.2 firmware zip and the recovery.img into the 1.2 folder.
Extract the 1.1.5 zip to the root directory.
Put the 1.1.5 recovery.img and mx2update.zip into the 1.1.5 folder, then delete the factory_update_param.aml from the SD card.
Extract the 1.1.6 zip to the root directory.
Put the 1.1.6 recovery.img and mx2update.zip into the 1.1.6 folder, then delete the factory_update_param.aml from the SD card.
Your SD card should now look like this
Flashing 1.1.5
Move the mx2update.zip and recovery.img from the 1.1.5 folder, and put them on the root of your SD card (outside of the folder).
Power off the MX2, if it isn't already.
Insert the SD card into the MX2, and use the toothpick method to boot into recovery.
Perform a Factory Reset.
Once it is finished, navigate to the Update from EXT option, and then choose SD card.
Select the mx2update.zip and allow it to flash.
When it's finished, power down the MX2.
Remove the SD card, then toothpick yourself back into recovery and factory reset again.
Reboot the MX2, and allow it to boot all the way up to the initial setup screen. You don't need to go any further. Just confirm that it does boot up now.
Power down the MX2 now.
Flashing 1.1.6
. Remove the SD card, go back to your PC, and delete the 1.1.5 firmware zip and recovery.
You may wish to move the 1.1.5 firmware zip and recovery.img back into the 1.1.5 folder. This is up to you.
Whatever you do, remember that you SHOULD NOT MIX UP THE FIRMWARE FILES OR RECOVERY.IMG FOR EITHER THE 1.1.6 or the 1.1.5 firmware. They are named the same, and they are not compatible with one another if you're following this guide!
Move the mx2update.zip and recovery.img from the 1.1.6 folder, and put them on the root of your SD card (outside of the folder).
Use the toothpick method to boot into recovery.
Do not insert the SD card just yet.
Perform a Factory Reset.
Power down the MX2.
Insert the SD card.
Toothpick yourself back into recovery.
Navigate to the Update from EXT option, and then choose SD card.
Select the mx2update.zip and allow it to flash.
When it's finished, power down the MX2.
Flashing 1.2
31. Remove the SD card, go back to your PC, and delete the 1.1.6 firmware zip and recovery.
You may wish to move the 1.1.6 firmware zip and recovery.img back into the 1.1.6 folder. This is up to you.
Whatever you do, remember that you SHOULD NOT MIX UP THE FIRMWARE FILES OR RECOVERY.IMG FOR THE 1.2, 1.1.6, or the 1.1.5 firmware. They are named the same, and they are not compatible with one another if you're following this guide!
Move the 1.2 firmware zip and recovery.img out of the folder you stored them in and onto the root of your SD card.
Use the toothpick method to boot into recovery.
Do not insert the SD card just yet.
Perform a Factory Reset.
Power down the MX2.
Insert the SD card.
Toothpick yourself back into recovery.
Navigate to the Update from EXT option, and then choose SD card.
Select the matricom_g18_1.2.zip and allow it to flash.
When it's finished, navigate back to the main recovery menu and select Reboot System.
It should take about 5-10 minutes to boot.
This process seems long, but it really shouldn't take more than about 15 minutes or so from start to finish. The devs have said that 1.2.1 will fix a lot of these sort of problems when they release it. The current ETA on the 1.2.1 update is Friday. Given the numbering, it will be a beta version, not a stable one.
The forum links are sometimes mislinked, so here they are in text form.
1.2 firmware -&
1.2 recovery -&
There is a bug with the 1.1.5 -& 1.1.6 firmware migration where the display will turn off. In order to recover, you will have to reflash the box (sometimes the display does not come back up). Follow the reflashing procedure above, but when you turn the box on leave the toothpick in the A/V port for 60 seconds. If you still do not have a display, wait 10 minutes (as the box may be reflashing) and once it resets you should see the screen again.
If this does not recover the box, it has an HDMI failure and will need to be followed up with a .
The wpa_supplicant file that needs to be deleted.
If your Wifi is turning on and off on it's own:
Using a Root Explorer (in this instance we are using ES File Explorer) go to device&data/misc/wifi.
Click and hold the OK button on wpa_supplicant file. (See picture to the right).
Click Delete And Confirm
Go to Settings or SettingsMBox and turn on your Wifi
Select your wireless network and enter your password
If the WiFi stops responding, there are two routes you can go:
Clear the Cache partition.
Reflash the box
Try the first option first!
You can do this by the toothpick method with NO SD card inserted. Once at the recovery menu for the MX2, choose "Reset Cache Partition". This will flush the cache and should allow the user to maintain settings and jumpstart the WiFi.
For common XBMC troubleshooting unrelated to the MX2, see the
If XBMC is not behaving as it's supposed to and clearing the data does not fix the issue, you can reinstall it to start from scratch.
To Uninstall XBMC:
Go to SETTINGS
Choose APPS
Choose XBMC and then Clear app data and uninstall the app.
To Reinstall XBMC:
Download the file and copy to your SD card.
Go to the App menu on your box (where you launch XBMC, Play Store, etc)
Use a app like app installer or locate the APK using a file explorer application
Install the App
Once the file finishes installing, you can open up XBMC and enjoy!
Note: If you download the APK on the MX2 using the browser you can locate the APK in the "Downloads" App.
If the player is small, but only in XBMC and not any other system, press the "\" key using a USB keyboard.
Sometimes you might get an error message indicating that the connection to the PVR client has been lost.
To disable this message navigate to Settings & Live TV & General and remove the check from the box next to "Enabled"
Refer to the
article for more information.}