Error during USB burning - UBOOT/Partition boot/Initialize partition/Error result

F

frienemy

New member
My X8-H won't show any display via HDMI although there is blue light (on for a while) during power on.
I open up the box and replaced the CR2032 battery which was drained, but it does not solve the problem.
So I decided to burn the firmware... got the error on 3 attempts trying "Normal erase" and "Force erase all".

See screen shot and the error log below.
Does it mean that the internal RAM/ROM is dead beyond recovery?
Thanks for any feedback before I toss the box away; it's a pity, seems like a solid box with good quality components and such ;)

[18:54:11 177][Global][Inf]--Burning thread HUB1-2 start
[18:54:11 228][HUB1-2][Inf]--Open device handle \\?\usb#vid_1b8e&pid_c003#5&18aa68bf&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed} 0x00000b50
[18:54:11 279][HUB1-2][Inf]--Connect path=USB xHCI Compliant Host Controller/P0/P1
[18:54:11 279][HUB1-2][Inf]--Start burning...
[18:54:11 342][HUB1-2][Inf]--------------ERASE BOOTLOADER------------
[18:54:11 342][HUB1-2][Inf]--0-7-0-16
[18:54:11 342][HUB1-2][Inf]--Identify status success
[18:54:11 342][HUB1-2][Inf]-- low_power
[18:54:11 342][HUB1-2][Inf]--Low power command success
[18:54:11 342][HUB1-2][Inf]--Read low power success
[18:54:11 342][HUB1-2][Inf]--bootloader_is_old
[18:54:11 342][HUB1-2][Inf]--Bootloader command success
[18:54:11 358][HUB1-2][Err]--failed: bootloader is new
[18:54:11 358][HUB1-2][Inf]--Bootloader is new
[18:54:11 358][HUB1-2][Inf]-------------Download DDR.USB-----------
[18:54:14 370][HUB1-2][Inf]--0-7-0-16
[18:54:14 370][HUB1-2][Inf]--No need download
[18:54:14 370][HUB1-2][Inf]-------------Download UBOOT_COMP.USB-----------
[18:54:14 370][HUB1-2][Inf]--0-7-0-16
[18:54:14 370][HUB1-2][Inf]--No need download
[18:54:14 370][HUB1-2][Inf]-- low_power
[18:54:14 370][HUB1-2][Inf]--Send command success
[18:54:14 370][HUB1-2][Inf]--Read command status success
[18:54:14 370][HUB1-2][Inf]-------------ERASE FLASH-----------
[18:54:14 370][HUB1-2][Inf]--disk_initial 4
[18:54:14 370][HUB1-2][Inf]--Send command success
[18:54:14 385][HUB1-2][Inf]--Read command status success
[18:54:14 385][HUB1-2][Inf]-------------Download meson.dtb-----------
[18:54:14 385][HUB1-2][Inf]--0-7-0-16
[18:54:14 385][HUB1-2][Inf]-- download mem dtb normal 45056
[18:54:14 385][HUB1-2][Inf]--Send download command success
[18:54:14 401][HUB1-2][Inf]--Read command status success
[18:54:14 432][HUB1-2][Inf]--Transfer complete
[18:54:14 432][HUB1-2][Inf]--Send download get_status command succeed
[18:54:14 432][HUB1-2][Inf]--get_status success
[18:54:14 948][HUB1-2][Inf]-------------Download boot.PARTITION-----------
[18:54:14 949][HUB1-2][Inf]--0-7-0-16
[18:54:14 949][HUB1-2][Inf]--download store boot normal 8344218
[18:54:14 950][HUB1-2][Inf]--Send download command success
[18:54:14 966][HUB1-2][Err]--failed:
[18:54:15 014][HUB1-2][Err]--[0x30402004]UBOOT/Partition boot/Initialize partition/Error result
[18:54:15 014][HUB1-2][Inf]--Close device handle 0x00000b50
 

Attachments

  • minix error 2.JPG
    minix error 2.JPG
    88.2 KB · Views: 28
I aplogise in advance for this basic question but it has to be asked, are you 100% sure it is X8-H? Check the lable on the underneath of the box just to confirm please.
 
Hello! Thanks for the reply, yes it's stated NEO X8-H. See pciture.
IMG_5254.jpg
 
Last edited by a moderator:
Marty said:
Perfect, thanks for clarifying. Could you please try flashing again with a newer version of the burning tool and see if that works:
https://theminixforum.com/index.php?threads/neo-u22-xj-amlogic-usb-burning-tool-v2-2-0.2767/
Click to expand...

Still failed...
[22:38:32 952][Global][Inf]--USB_Burning_Tool soft Version: V2.1.9.0
[22:38:32 952][Global][Inf]--Windows Version: Microsoft Windows 10, Bit: 64
[22:38:32 955][Global][Inf]--Scan usb device
[22:38:32 955][Global][Inf]--Aml scan WorldCup Device
[22:38:32 966][Global][Inf]--Host: USB xHCI Compliant Host Controller
[22:38:32 966][Global][Inf]--DevPath:\\?\pci#ven_8086&dev_9d2f&subsys_84b3103c&rev_21#3&11583659&2&a0#{3abf6f2d-71c4-462a-8a92-1e6861e6af27}
[22:38:32 966][Global][Inf]---->Roothub:USB#ROOT_HUB30#4&ca8032&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}
[22:38:32 967][Global][Inf]-------->[Port0]NoDeviceConnected
[22:38:32 967][Global][Inf]-------->[Port1]NoDeviceConnected
[22:38:32 967][Global][Inf]-------->[Port2]NoDeviceConnected
[22:38:32 967][Global][Inf]-------->[Port3]NoDeviceConnected

:
:
:
:

[22:39:25 851][HUB1-16][Inf]--Update device path
[22:39:25 851][Global][Inf]--Update HUB1-17
[22:39:25 851][HUB1-17][Inf]--Update device path
[22:39:25 851][Global][Inf]--Update HUB1-18
[22:39:25 851][HUB1-18][Inf]--Update device path
[22:39:25 851][Global][Inf]--Scan end
[22:39:25 881][HUB1-1][Inf]--Device is connected
[22:39:25 881][HUB1-1][Inf]--Close device handle 0x00000970
[22:39:25 932][HUB1-1][Inf]--Open device handle \\?\usb#vid_1b8e&pid_c003#5&18aa68bf&0&1#{a5dcbf10-6530-11d2-901f-00c04fb951ed} 0x00000f40
[22:39:30 984][HUB1-1][Inf]--0-7-0-16
[22:39:30 984][HUB1-1][Inf]--CheckFileRunState succeed
[22:39:30 984][HUB1-1][Inf]-- low_power
[22:39:30 989][HUB1-1][Inf]--Send command success
[22:39:30 992][HUB1-1][Inf]--Read command status success
[22:39:30 992][HUB1-1][Inf]-------------ERASE FLASH-----------
[22:39:32 993][HUB1-1][Inf]--send command diskinit
[22:39:32 993][HUB1-1][Inf]--disk_initial 3
[22:39:32 993][HUB1-1][Inf]--Send command success
[22:39:43 510][HUB1-1][Err]--failed:[22:39:43 510][HUB1-1][Inf]--Read command diskinit status
[22:39:43 510][HUB1-1][Err]--Check command return failed
[22:39:43 535][HUB1-1][Err]--[0x32030201]Uboot/Get result/DiskInitial error
[22:39:43 535][HUB1-1][Inf]--Close device handle 0x00000f40

--------------

Trying out the SD card flash method next.
 

Attachments

  • minix error 3.JPG
    minix error 3.JPG
    82 KB · Views: 27
Last edited:
Marty said:
If that doesn't work then next step is to try flashing the stock ROM via SD Card:
https://theminixforum.com/index.php...8-h-by-flashing-plus-firmware.2561/post-19107
Click to expand...

I read the README instructions and found that all 3 options require me to "see the minix logo" at some point, but the problem is that I don't get any signals to my monitor to start with. Anyway, I tried the steps giving time for that imaginary logo to appear before I release the recovery button hold, still nothing happens. Tried a few times.

Therefore it's probably a hardware problem?
The monitor shows no signal/cable connected, and I'm sure the cable is working well as I tested the cable with a PC output.y

BTW, when I power it on, only the optical audio out is lighted up in red. The other blue led in the front does NOT light up anymore (it used to give a single blink and then was off permanently)

In any case, I thank you very much for trying to help!
 
Last edited:
frienemy said:
I read the README instructions and found that all 3 options require me to "see the minix logo" at some point, but the problem is that I don't get any signals to my monitor to start with. Anyway, I tried the steps giving time for that imaginary logo to appear before I release the recovery button hold, still nothing happens. Tried a few times.

Therefore it's probably a hardware problem?
The monitor shows no signal/cable connected, and I'm sure the cable is working well as I tested the cable with a PC output.y

BTW, when I power it on, only the optical audio out is lighted up in red. The other blue led in the front does NOT light up anymore (it used to give a single blink and then was off permanently)

In any case, I thank you very much for trying to help!
Click to expand...
Thats a pity, you don't have another monitor or TV to test on, could be an unsupported resolution that it is stuck on? Although the blue light would remain on then and flashing with USB Burning Tool would be unaffected too....

Last resort I would say contact the customer support team – support@minix.com.hk
 
You must log in or register to reply here.
Back
Top