[Android Stick & Console AMLogic based Computers] rawrico:
UNBRICK and flash into 1.3.106

I would like to share my experience of unbricked my mibox MDZ-16-AA.

It is a bright hope that i am able to unbricked it and flash the firmware back to stable version...

Cause the beta firmware DOESN'T work with Recovery mode, i am almost destroyed my remote because of this.

Below is the step i take to try my luck, but fortunately it is working, but i didn't root it later on, cause i let it update until the latest firmware (i'll check back later if you need to know what is the latest firmware now on MDZ-16-AA).

At first, i follow the first post, to unbricked my MIBOX,

once is done, and able to access into the usual boxes interface,

i follow some guide from "rdma.co/mdz-16-aa" to installed/flashed TWRP the recovery "firmware" in to recovery partition, the bat file may not work, so i copy paste the command manually.

Then by using adb command, i type in "adb reboot recovery", the result is it enter the recovery mode without problem.

In this TWRP recovery mode, the Remote are not supported in this part, we will need USB hub and mouse to do this. But instead, i reboot back in to system.

By using my laptop, i've download 1.3.106 firmware and extract it, transfer the update.zip firmware file in to the MIBOX sdcard. Any method i think should do, i am using adb push in this case...

So once the 1.3.106 update.zip firmware is transfer complete, i reboot it in to recovery mode using adb command again. In recovery mode, im using mouse to navigate the interface.

Cause of the following part i did it once, i'm not too sure i still remember what i choose to do...

In this part, i've wipe the SYSTEM, DALVIK and DATA, then update the system by choosing the update.zip that i have previously transfer. I've wait for few minutes, watching the interface loading, once it show the update is successful, i've wipe the dalvik again, and reboot the mibox in to system.

In this part, i think the system it self have some bug to reboot from TWRP to system, cause it seems like stucked in the GITV loading screen. But once i did a hard reboot by turn off and on, it worked.

I have unbricked the MDZ-16-AA and back in to 1.3.106 version of MIBOX. By theory, i think this way actually will left many many bugs in it, so i update the firmware over internet.

Things i've tested so far after firmware successfully restore and update to latest version,

Connect internet by WIFI - OK

Connect my Bluetooth joypad - OK (at first it closed off immediately when i opened the bluetooth interface, but reboot few times, is working already)

INSTALL APP MANUALLY BY USING ASSISTANT - OK (In my case, i've tested to transfer small APK and big APK, big APK need to use other method to transfer, not sure why it crashed the assistant app when i start transfer it; but small APK work fine.)

INSTALL APP USING ES FILE EXPLORER - OK (i've test RetroArch APK, 32bit or 64bit, unable to install 64bit, 32bit got no problem to install)

WATCH Video that store in SMB or Local storage - OK

Hope my reference help.

---------- Post added at 02:08 AM ---------- Previous post was at 02:04 AM ----------

I forgot to mention,

once i've update to latest version over internet

the recovery button are working again.

Cause i've reboot few times to let it update the firmware by it self, but at specific version, it stuck at GITV again, so i use recovery mode to wipe the dalvik (This part is chinese, and i'm not to remember the keyword in recovery mode)