My Beelink Mini MXIII BOX bricked

akela · 29 April 2020 10:00

Hello!

I installed coreelec on my box, but during power outage lett.

Now i cant flash usb burning tool and sd card method with the original firmware.

UBT error message:

[0x30405004]UBOOT/Partition boot/Verify patition/Error result

UART log with SD method: https://pastebin.com/C8eU0q2F

Can anyone help me?

rho-bot · 29 April 2020 12:36

Looks like your eMMC lost all content (corrupted PT).
You need to recover with a stock Android image.
Seems a problem with aml_sdc_burn.ini file, which should be on the SDcard.

akela · 29 April 2020 13:14

Thanks for your reply.

I have stock firmware: MINI_MXIII_107L1_0425.img

This box S905 version not S905X MXIII II.

I burned SD card with BurnCardMaker.

SD card contents:

aml_sdc_burn.ini
aml_sdc_burn.UBOOT
MINI_MXIII_107L1_0425.img

rho-bot · 30 April 2020 15:42

Strange…
If AML Factory mode Procedure by SDcard does not work, you could try the USB method.

As your box is still booting, another idea:
Boot to Android recovery on SD-Card, flash firmware as ZIP:
http://bee-link.com/forum.php/forum.php?mod=redirect&goto=findpost&ptid=906&pid=4487
But not sure if this will fix partitions, maybe you need to format system/data upfront before flashing.

akela · 30 April 2020 17:27

System is read only on TWRP.

I use HDMI-VGA adapter therefore, the color is bad.

rho-bot · 30 April 2020 17:43

As you have booted the recovery from SDcard, it doesn’t matter if it is persistent. Just ignore.
Last sentence already says that ZIPs will be processed anyway.
If it doesn’t work, allow R/W access.

akela · 30 April 2020 17:46

If it doesn’t work, allow R/W access. How I know?

I dont know that hardware error, or software.

gxb_p200_v1#mmc dev 1
emmc/sd response timeout, cmd8, status=0x3ff2800
emmc/sd response timeout, cmd55, status=0x3ff2800
[mmc_init] mmc init success
mmc read lba=0x14000, blocks=0x400
Amlogic multi-dtb tool
Cannot find legal dtb!
start dts,buffer=0000000073ef0400,dt_addr=0000000073ef0400
get_partition_from_dts: FDT_ERR_BADMAGIC
!!!get dts FAILED
mmc get partition error!
switch to partitions #0, OK
mmc1(part 0) is current device
gxb_p200_v1#mmcinfo
Device: SDIO Port C
Manufacturer ID: 65
OEM: 646f
Name: M MOR
Tran Speed: 25000000
Rd Block Len: 512
MMC version 4.41
High Capacity: Yes
Capacity: 7.2 GiB
Bus Width: 8-bit
gxb_p200_v1#

UART only see 7.2 GB but this 16 GB chip. Maybe 107L1 firmware 2/8GB version? Is from this aml_sdc_burn.UBOOT.

bubblegum57 · 30 April 2020 18:31

I am uploading some files for this device, I’ll post back when they are on my Gdrive account.

factory_update_param.aml
MINI MXIII_107L1_0425.img
MiniMXIII Firmware Download.zip
p200_2G-ota-20160425.zip
recovery (1).img

https://drive.google.com/open?id=0B4qBL4ABMEuMNGZYVXgwLXVUWXc

try this link

akela · 30 April 2020 19:04

Thank you, I have all files, but redownload your link.

I use aml_sdc_burn.UBOOT from this MINI MXIII_107L1_0425.img. I burned bootcardmaker, before rename u-boot.bin.

And copy your recovery (1).img and rename recovery.img.

After boot came recovery menu.

I attach UART log: https://pastebin.com/SfaN1nTk

I see UART log: WARNING: No OPTEE provided by BL2 boot loader

How can I flash u-boot into emmc?

bubblegum57 · 30 April 2020 19:07

if you have got your box running from sd or usb, you used to be able to installtointernal

akela · 30 April 2020 19:12

The installtointernal method kill all partition.

bubblegum57 · 30 April 2020 19:28

I assume you had the box running a CE image from sd or usb?

Because I used installtointernal on my beelink, no problems

akela · 30 April 2020 19:32

Yes. Running from SD. Power went out during installtointernal. Later not boot SD and eMMC.

bubblegum57 · 30 April 2020 19:37

so it wasn’t a problem with the installtointernal command

problem caused by power going off

akela · 30 April 2020 19:42

Yes. Not finished yet.

rho-bot · 30 April 2020 21:06

What was this picture coming from?
AML Factory mode Procedure or Android Recovery Procedure???
I’m confused because you wrote

Did you try the Android Recovery Procedure (Link to Beelink forum)?
Did it work for you?

If the eMMC identifies as 7.2GB, your box HAS 7.2GB, not more!
Maybe then you have to search for a different Recovery FW.

Last but not least:
If you get access to internal UART console, you can erase the flash by command:

github.com

khadas/documents/blob/master/HowtoEraseEMMC.md

# Howto Boot Erase the onboard EMMC Storage

There are many different ways to wipe out all the data on EMMC, and list as following:

### Keys Mode(U-Boot is running)
1. Power on Vim.
2. Long press `Power` and `Function` buttons simultaneously without release
3. Short press ‘Reset’ key and release
4. After the operations above, the system will begin to earse automately, and it will take around 10 seconds to done that.
5. The display/monitor will display as a black screen when the wiping process is done.


### Serial Mode(For developers)
1. Refer this [guidance](https://github.com/khadas/documents/blob/master/SetupSerialTool.md) to setup serial tool for Vim.
2. Make sure again you've done the right connections and setup.
3. Hit any keys at the moment of booting to stop autoboot. This step will let Vim boot into u-boot mode.
4. Type `store init 3` on the terminal of u-boot, and wait the wiping process to complete.
5. Type `reboot` or press the `Reset` button
6. References as following:
```

This file has been truncated. show original

akela · 30 April 2020 22:48

If the eMMC identifies as 7.2GB, your box HAS 7.2GB, not more!
Maybe then you have to search for a different Recovery FW.

No, FORESEE NCEMBSF9-16G is on the motherboard chip.

store init 3 result

gxb_p200_v1#store init 3
emmc/sd response timeout, cmd8, status=0x3ff2800
emmc/sd response timeout, cmd55, status=0x3ff2800
[mmc_init] mmc init success
mmc read lba=0x14000, blocks=0x400
      Amlogic multi-dtb tool
      Cannot find legal dtb!
start dts,buffer=0000000073ed0420,dt_addr=0000000073ed0420
get_partition_from_dts: FDT_ERR_BADMAGIC
!!!!get dts FAILED
mmc get partition error!
switch to partitions #0, OK
mmc1(part 0) is current device
Device: SDIO Port C
Manufacturer ID: 65
OEM: 646f
Name: M MOR
Tran Speed: 25000000
Rd Block Len: 512
MMC version 4.41
High Capacity: Yes
Capacity: 7.2 GiB
Bus Width: 8-bit
[store]amlmmc erase 1emmckey_is_protected : protect
 gxb_p200_v1#

Beelink forum method not work, dont know mount partitions, /dev /boot /data etc… can not find.

rho-bot · 30 April 2020 23:10

What to say? If it’s a genuine FORESEE NCEMBSF9-16G, according Datasheet (link) the ManufacturerID has to be 0x88, and it’s a emmc v5.0 device. Yours is totally different, so looks like a fake device.
Maybe send some pictures from the pcbs…

Anyhow, you have a broken Partition table, so it needs an erase.
Then you need a proper recovery image for S905 | 2GB RAM | 8GB EMMC
For burning via SDcard, check also this tool, maybe works better than the leaked AML Tools.

Good Luck!

akela · 30 April 2020 23:26

Thank you this tool link. I see tomorrow.

I hope this picture good quality.

rho-bot · 1 May 2020 00:23

For me yours is clear Fake, quick milled/etched & lasered.
But decide on your own - do they look similar?
https://forum.freaktab.com/filedata/fetch?id=657272&d=1500508885
https://forum.freaktab.com/filedata/fetch?id=676448&d=1507467268
https://img.alicdn.com/imgextra/i4/2529891966/TB2c.2.vb4npuFjSZFmXXXl4FXa_!!2529891966.jpg