Announcement

**blinkone** · 28 April 2015, 22:41

Its worth trying another lead if you can & even another pc before you try & send it back to china

**darrenireland** · 28 April 2015, 23:00

tried 3 leads, only got one to recognize, will bring it into work tomorrow and try it also

i read somewhere someone having the exact same problem and flashed 108 and then updated from there, so fingers crossed

sending back to china is a pain in the hoop!

**Ichijoe** · 29 April 2015, 11:20

There is a trick to recovering a MXIII (As I found out the hard way...),

It would likely help to have a few things first, though:

USBDeview to clean up such static USB Drivers, and insure that such Drivers are properly installed!

The Amlogic USB Burner Tool: It seems you have that too.

A Firmware *.img File... It seems like you already found it. [i]Just note that 108k4 will likely break your AP-6181 WiFi, as 109k4 IS the first Officially available Firmware to have that Driver set.

An old striped Q-Tip with which to reset / get the Device into Recovery Mode.

So when you first install the USB Burning Tool, you should be presented with the Alert that it is trying to install the unsigned WorldCup Driver, and if you wish to continue. NOTE Windows 8.x. People will need to figgure out how to re-enable the installation of such Drivers since MicroSoft, have blocked such installations there!

e.g. No WorldCup Diver no work-ie! i.e. ~ca. 2~3% then crash!

So the "Trick" here is when you first use the USB Burning Tool even if you have managed to otherwise properly install the WorldCup Driver! Is to connect the "Device" to your PC via the USB > OTG Cable then press the Reset Button (Inside the AV Port), while powering up the "Device", and CONTINUE HOLDING THE RESET SWITCH UPWARDS OF 90 SECONDS. Till Windows goes "ting", and then actually searches for, and finds, and then loads the WorldCup Diver into Memory!

Only then does this work!

Should you still be fortunate enough to still have your Recovery, or even if you don't you should probably stop here, and give this a try first!

1) Go HERE: and download the k200.img File
then rename this to read as recovery.img, and then place this onto a MicroSD Card. (This should now allow you to boot into the TWRP Recovery which is IMHO a far superior Recovery then google's stock 3e Recovery.)

2) Along with this you should also download the 109k4 Firmware... I have a Copy of it posted on my Google Drive. This is the Three-File *.zip File, though you'll need either 7zip (free), or WinRAR (Shareware), to unpack it into its Three separate Files. Once you unpack it, you'll ONLY need the "k200-ota-20140917.zip", which you should place on the same MicroSD Card along with the renamed recovery.img File.

3) Get a USB Mouse, as TWRP recovery on Amlogic does NOT allow you to use a Remote... yet?!

4) Assuming you can actually boot into TWRP (That is!), I don't think it should be a problem though. Click on "Install" <Your MicroSD Card> (If need be flip the "Image" Button to "Zips" to get the File(s) to pop up), then click said k200-ota-20140917.zip File, then Slide to install this should hopefully install what is in my humble opinion the BEST Firmware for all 1G users. i.e. 109k4 / 110k4. Since everything after 111k4 basically sucks on 1G... 2G People might have more luck? I wouldn't know though, as I like you I have the 1G Version. and the amcodec breaks HARD on 111k4, and its never been fixed since, so 114k4 is just as broken! Such is my reason for sticking to 109k4

*BTW I think I'll reiterate unless you have a Realtek 8188 version of the MXIII (Literally a First Gen Box...), I'm gonna take Odds that you most likely have an AP-6181 (Second Gen MXIII), even if your "Box" had 108k4 as Stock (Like mine was before I bricked it!). There IS NO 108k4-ap6181 firmware anywhere on the net! Every 108k4 on the 'Net is for the Realtek 8188, and if you install this on a Second Gen 1G MXIII, IT WILL BREAK YOUR WIFI!

However it will NOT brick your Device, in the same way as installing an S82 Firmware would. Which is what happened to me. Of course we didn't have TRWP back then. So USB Burning Tool was my only option at that time... Thankfully this is no longer the case!

**darrenireland** · 29 April 2015, 13:58

Hi Ichijoe
Thanks for the advice. Its been recognised as a worldcup driver alright. But when flashing starts at 2% it disconnects and then recommects and loops. I am aware of the wifi issue with 108 but I just wanted to get it back up and running and then would update the firmware from there as at the moment its just a red light paperweight :-(

I have friday off so will try a differnt pc and cable. thanks for the guidance though, much appreciated.

**Ichijoe** · 29 April 2015, 15:31

If you have a MicroSD, just go grab the TWRP Recovery from the Thread in the Parent Board (i.e. the One above this Board!), and install that as I said. Then when you try to get into the Recovery Mode, it'll load the TWRP Recovery off the MicroSD instead. Then just install the 108k4/109k4 k200-ota*.zip. And save yourself the stress with USB Burning Tool.

**darrenireland** · 30 April 2015, 13:31

Originally posted by Ichijoe View Post

If you have a MicroSD, just go grab the TWRP Recovery from the Thread in the Parent Board (i.e. the One above this Board!), and install that as I said. Then when you try to get into the Recovery Mode, it'll load the TWRP Recovery off the MicroSD instead. Then just install the 108k4/109k4 k200-ota*.zip. And save yourself the stress with USB Burning Tool.

Cheers, will try that tomrorow, thanks for the help, really appreciate uit

**darrenireland** · 30 April 2015, 20:55

Originally posted by Ichijoe View Post

If you have a MicroSD, just go grab the TWRP Recovery from the Thread in the Parent Board (i.e. the One above this Board!), and install that as I said. Then when you try to get into the Recovery Mode, it'll load the TWRP Recovery off the MicroSD instead. Then just install the 108k4/109k4 k200-ota*.zip. And save yourself the stress with USB Burning Tool.

tried this, I have a working mxiii and booted into recovery no problems with TWRP. Tried it with the non working one and nothing, its dead, red light is on the power button but it doesnt do anything or send any signal to the tv.

**Ichijoe** · 01 May 2015, 16:17

So its in essence bricked then?
then in that case you don't have much choice BUT, to use the Amlogic USB Burner Tool then. by, proxy with the 108k4-RTL8188.img (or a there-abouts...) Firmware, like you were trying to....

I was also at One time in the exact same position as you were. The really sad thing was, at the time I never even got to use it. As I stupidly tried to flash an incorrect version of TWRP (For S82 Devices), on my M82 MXIII (1G), and blue-light bricked it, before stupidly flashing the accompanying S82 Firmware on it. After having it for roughly ~20-ish Minutes.

Needless to say it was a very l o n g d a y ! ! Before I managed to find this bit of advice....

When you setup Amlogic's USB Burner Tool, and you've also loaded up the correct *.img File (ex: 108k4), you MUST HOLD THE RESET Button for exactly 90+ Seconds, its not enough for the "Device" to pop-up with some Chinese Script on the Screen! You have to continue to really hold the Reset Switch for nearly the entire 90 Seconds (or... so), till Windows itself "sees" the "Device", and then pulls the WorldCup Driver into Memory. It's at this point where Windows will go "Ting!", and you will see that Windows will start searching for the "Driver(s)", and eventually loads it [sic: WorldCup Diver]

Now you can hopefully install any *.img File you'd like 108k4 (As a kind of Stock), 111k4, 112k4, 113k4 or 114k4 are only in *.img IIRC.

Thankfully you only really need to do this once., But if you don't do this... Chances are great that you'll have the exact problems of which your describing.
I know this, as I'm writing this as someone that's been there.

Besides (Before you write me off....), what do you have to loose? Yeah pressing the Reset Switch that long is a PitA, and it does seem like forever, but its a fair trade off for sending it to the Landfill.

BTW: Some other advice I'd be happy to pass on stick to either 109k4, or 110k4. the amcodec breaks on 111k4, which is a new AiO Buld, that should cover most, if not all S802 Devices. So no more bricking like with the S82 Firmwares. But, then with a badly broken amcodec that remains broken on 114k4... At least for my 1G MXIII, Since I do not have a 2G Box... I can NOT attest if those users suffer this bug or not.

**darrenireland** · 02 May 2015, 06:38

Thanks again for the advice. I will try this again today. It's so strange. When I am flashing I also have device manager open. It sees the box as a world Cup device. But when it hits 2% it's like the connection breaks. Like the box disconnects. Disappears from device manager and reappears again and the process starts all over again. .

**Ichijoe** · 02 May 2015, 11:24

Originally posted by darrenireland View Post

Thanks again for the advice. I will try this again today. It's so strange. When I am flashing I also have device manager open. It sees the box as a world Cup device. But when it hits 2% it's like the connection breaks. Like the box disconnects. Disappears from device manager and reappears again and the process starts all over again. .

Ok Here is a suggestion... Go HERE: and download USBDeview, and run it. Remove any, and all traces of the WorldCup Driver you might find under it, along with any other Android related Drivers Ex: Android Composite ADB Interface (if it exists!) from this Program. (Short story doing this will de-list the Diver(s) from your PC. It won't uninstall them as such. But it will force Windows to go and look for them again.

Which is the "Trick" right there in the Nutshell!

On the first "clean" connection with the Amlogic USB Burner Tool. You MUST HOLD THE RESET BUTTON UNTIL YOU GET THE SWIRLY PC THINGY. (Down by the Clock!), Like what you may have seen time from time when you inset a USB Mouse or a USB Stick. This is Windows actually loading the Driver. In this instance the WorldCup Driver, and until this happens... Your gonna get stuck with the ~3% Error! Such as you have. in order to ensure that the Drivers actually get loaded... YOU MUST CONTINUE HOLDING THE RESET BUTTON FOR UPWARDS OF 90 SECONDS! Until Windows starts to actually call up the WorldCup Driver.

Again ITS NOT ENOUGH just to have:
[DEVICE ID] - [Status] etc...
[HUB-n] (indecipherable Chinese Runes) ...Connected?!

On USB Burning Tool THIS MUST NOT BE SEEN AS A FULL DRIVER CONNECTION!!! ITS NOT! And, its why you, I, and so many others here in this situation get stuck with the never ending ~3% Bug!

Thankfully this is mostly a one time deal, after you successfully completed this process you should be able to reconnect your (WorldCup), Device back up again without that problem ever again.

**darrenireland** · 02 May 2015, 14:10

Tried all that again joe, still 2% , so so annoying!

**Ichijoe** · 02 May 2015, 15:42

Then try it nce more but with all the Erase Flags unchecked!

**darrenireland** · 02 May 2015, 20:26

Originally posted by Ichijoe View Post

Then try it nce more but with all the Erase Flags unchecked!

No joy, lovely paperweight with a red light! Grrrrr!! appreciate all the help though

**darrenireland** · 04 May 2015, 22:44

Appreciate the effort Joe though

Announcement

Announcement

Mxiii 2% Flash loop

Mxiii 2% Flash loop

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

What's Going On