Mxiii 2% Flash loop

[mpj220]

I had mine fail when using the USB burning tool - if I recall, it was around the 2% progress.
I found it to be that the USB Burning tool did not like anything but USB port 1 on my laptop. Don't know why but, port 1 was the only one that would work.

I posted the procedure that worked for me - any deviation would give me a fail.

http://freaktab.com/forum/tv-player-support/amlogic-based-tv-players/beelink-aml-devices-s82-m8-round-mxiii-etc/22971-help-think-ive-bricked-my-mxiii-2gb-box?p=397501#post397501

Hope it helps!

[darrenireland]

Thanks mpj220 - will try that later,

on your instructions...
Press and hold power button (now with toothpick still pressed)
Burning tool would then recognize and connect.
Press start on burning tool
Wait for complete
Press stop on loader


When did you release the powerbutton and toothpick?

[Ichijoe]

Check your Private message... I think you might have to build a recovery MicroSD specifically with the correct u-boot.bin File, as this is triggers Windows into finding a new USB Device.

You also only need to press the power Button once to turn it on. (i.e. Just press it once, and release it), THAT'S IT. The Reset Switch however must be continuously depressed until the time Windows Discovers a new USB Device. This may take upwards of ~90+ Seconds though.
Again Windows has to discover the "Device" which is NOT the same thing as the "Device" just showing up under Amlogic USB Burner Tool. So you have to be patient.

It may also help to have a MicroSD formatted with the BootcardMaker.exe (Which should also be in the same *.rar File as the Burner Tool).
As I stated in your PM, you need to use the u-boot.bin File on the Main Directory. You'll know it as its the slightly larger One @ 352KB, the u-boot.bin packe with the BootcardMaker is only 340KB, and to my knowledge doesn't work!

Once you have your MicroSD pepped, you will need to recopy that File (u-boot.bin), + a File called: usb刷机工具说明.wps along with the correct recovery.img from an Update.zip File... Barring that I'd think that a renamed TWRP Recovery to recovery would also work here. as long as its an AM S802 SoC [K200] Device.

Again with that MicroSD installed, just connect it back up to the PC via the OTG Port, and while depressing the Reset Switch, tap the Power Button once, and continue holding the Reset Switch... You'll know when you can let it go, after the "Ting", and Windows starts its search for the WorldCup Driver.

Now you shouldn't have any more problems.

[darrenireland]

Thanks Joe, when I get the "ting" do I flash it with Usb burning tools are previously?

[Ichijoe]

Thanks Joe, when I get the "ting" do I flash it with Usb burning tools are previously?

Yes... I don't know how to describe the "Ting!" Its the "Ting!" you sometime get when you add your Phone (Or other USB Device), to your Windows PC, before it goes off to load up the needed Driver(s).
Assuming your bricked sooo hard that you also muffed up the u-boot (Bootloader Partition), the BootcardMaker should allow you to load that bit off, of the MicroSD Card, and hopefully allow you to make the "Handshake" with Windows. Which you'll need if you don't want to keep crashing at ~3%!

[darrenireland]

i know exactly what you mean about the tink, its the handshake between the devices to show the drivers are loaded and the device is recognized property.

i will try that tonight and report back! If I get it working after all this i owe you a pint!

[darrenireland]

tried it last night, no joy, still the same 2% - system discommects it, recommects it, starts again, 2% - loop..

[Ichijoe]

Try this... Point 2

After you have formatted the your MicroSD Card... With the BootcardMaker.exe, and the u-boot.bin (352KB), File.
You should then copy the following to your MicroSD Card...

• factory_update_param.aml
• k200-ota-<DATESTAMP>.zip ← (Your Firmware File i.e. 108k4 ~ 114k4)
• recovery.img
• The u-boot.bin File you used to format the MicroSD with again it should be the 352KB version, and NOT the other 340KB one a bit further inside the *.zip File.

With the only exception of u-boot.bin File. You'll should be able to obtain the other Three Files from any freely available Update ZIP File....

If you've done the above correctly a Android should hopefully appear, with a progress bar underneath it.... (Its should then hopefully go on to restoring your Device back to your Firmware of Choice.
In the case of 108k4... Again you SHOULD expect broken WiFi Drivers, until you're able to get back to 109k4 ~ 110k4 (or higher)...

[prahjister]

do you have the latest burning tool? I believe i had the same issue when i was using the wrong one. I think this is the latest http://chinagadgetsreviews.com/downl...-v2-0-4-3.html

[darrenireland]

thanmks agaon joe, i will try that tongiht, Prah, i assumed i did, but just in case i will try that one, did you have the same 2% issue?

[Ichijoe]

Yeah, about ~20 Minutes after I first got One. lol It took me like 13h+ to finally figure it out.
But that was like last October. IIRC I think that was how I managed to unbrick it. Just make sure that if you do this you have a 1G Firmware 108k4 ~ 110k4, are device specific 111k4~114k4 are AiO Firmwares. Flashing a 2G Firmware on a 1G Box is BAD NEWS!
So make sure you have the correct version. With 108k4 its not so tragic to lose the WiFi until you update it. But, again you not gonna do yourself any favors by flashing a 2G ROM on a 1G Device,

[darrenireland]

tried latest burning tool and joes newest method, i think i must admit defeat!

[JustMe]

Appreciate the effort Joe though

what operating system you using and what version burning tool?

[darrenireland]

what operating system you using and what version burning tool?

win7 and v2.0.4.3

[mpj220]

Thanks mpj220 - will try that later,

on your instructions...
Press and hold power button (now with toothpick still pressed)
Burning tool would then recognize and connect.
Press start on burning tool
Wait for complete
Press stop on loader


When did you release the power button and toothpick?

Sorry for not getting back earlier.... life has been.... work, sleep, work, sleep

I release power and toothpick once burning tool recognize on USB port 1