Help me please erro [0x30405004] USB burning tool

[Nebojsa]

Think that was 7.1.
Yes, box is recognized and I plug the power adapter
or, plug the power adapter then USB, box is recognized like it should.
Tried SD card method but nothing happened, no reaction at all. I tried with all roms I have found. Once I leave the box for half an hour to see if anything will happen, but nothing.

[Nebojsa]

OK, thanks for trying.

[bumerc]

Nebojsa
Apparently you have damaged the Bootloader, so that the eMMC Memory can not be initialized. You must perform a full erase of eMMC Storage and reinstall Bootloader. Do you have the possibility to connect your box via UART to the computer?

[Nebojsa]

As a matter of fact, I do.
I already have disassembled the box and solder RX TX GND and 3.3v to adapter.
What to do next?

[bumerc]

Now start the box and post the bootlog here

[Nebojsa]

If you think that I use some terminal emulator program, like Putty, and see what it says when connect box to PC, I already tried that.
There is just bunch of crap, sequence of signs, numbers and letters without any meaning. Something like:
1@$$$&%5(£[]][[§
\\[[]]]]§«»><}}{qgjvbbn64#@$$%+++&%##!$%&&&&&&&
&7$&6#@5tchuxc<>|°°°.........
You got the picture.
Can I somehow force it to install bootloader?

[X92-2GB]

Just a wee bit of info from my unbricking from the dead. With various ways of bricking the same unit. To me these boxes are impossible to brick into total death.

i have seen every error posted here with my box, and never been stumped at recovery. The NAND mask flash seems to be the best method as long as power, cable and proper flash tool is used.

I use 2.0.8 flash tool, if using newer, uninstall and reboot. Then install 2.0.8 and reboot.

hardware brick...

When you power on with power cable only, does the SPDIF LED light up inside the connector?

If not, there is not enough power is at the RAM and CPU.

Jumpering USB 5v power to the power input connector pin should initialise the dead portion of the system.

Start the flash tool with your loaded image, and connect the USB cable from the computer to the box's USB port to flash.

Short the pins for NAND mask.



Bootloader brick...

Obtain 5 different firmwares... M8S, Beelink, Ugoos, and two custom firmwares. Try Superceleron, and Tillas97.

Each firmware will give a different error. But always try factory first with force erase, on each USB port. Take note on how far it goes. If they all go to to the same area and fail, untick erase boot loader.

Once you find a USB port that seems to go further than the others, stick with it for all flashes.

My bootloader is locked, and i have done full erase, with stock firmware, so that may be something you cannot do with your device, as you loose MAC, serial number, and other device specific data needed for firmware to properly function.

[bumerc]

Nebojsa
You have connected and configured it incorrectly.

Putty Settings:

baud = 115200

Data bits = 8

Stop bits = 1

Parity = none

Flowcontrol = none



Wiring Conf.:

PCB GND <———> GND Comp.

PCB RX <————> TX Comp.

PCB TX <————> RX Comp.


I need to know exactly what happened to the old bootloader to describe the correct installation process

[Nebojsa]

You are wright, I configured it incorrectly.
Done like you wrote and I have something in Putty:

LOOP:4;EMMC:0;READ:800;SD:800;USB:8;LOOP:5;EMMC:0; READ:800;SD:800;USB:8;LOOP:6;EMMC:0;READ:800;SD:80 0;USB:8;LOOP:7;EMMC:0;READ:800;SD:800;USB:8;LOOP:8 ;EMMC:0;READ:800;SD:800;USB:8;LOOP:9;EMMC:0;READ:8 00;SD:800;USB:8;LOOP:A;EMMC:0;READ:800;SD:800;USB: 8;LOOP:B;EMMC:0;READ:800;SD:800;USB:8;LOOP:C;EMMC: 0;READ:800;SD:800;USB:8;

And on and on...

"When you power on with power cable only, does the SPDIF LED light up inside the connector?"
No, there is no light on SPDIF, but there is light when I insert the usb cable and the USB burning tool recognize the box. Is that ok, or I have to short some pins (don't know which)?

[bumerc]

the eMMC Bootloader Partition is empty, you have deleted the Bootloader. I'll write a short tutorial later on how to install the Bootloader. I'm still on the go.

[Nebojsa]

OK, thanks a lot!

[bumerc]

Please install u-boot.bin.sd.bin first on the MicroSD card, see the instructions -> “METHOD 3 – Update from a MicroSD Card“

You need to do the first 2 steps for now.

You can download u-boot.bin.sd.bin for your box HERE. In the ZIP archive there are 2 u-boot binary files, u-boot.bin will be needed later for the eMMC installation.

If you have prepared the sdcard, put it in the box, and try to boot the box first, you do not have to press anything, because the bootloader partition is empty and the BL1 starts the BL2 code directly from the sdcard. Please post the bootlog after booting.

[Nebojsa]

Ok, I make micro sd card with u-boot.bin.sd.bin, here is the bootlog:

GXM:BL1:dc8b51:76f1a5;FEAT:ADFC318C:80;POC:2;RCY:0 ;USB:0;EMMC:0;READ:800;SD:0;READ:0;0.0;CHK:0;
no sdio debug board detected
TE: 146208

BL2 Built : 20:32:17, Sep 8 2017.
gxl g6296b83 - xiaobo.gu@droid12

set vdd cpu_a to 1120 mv
set vdd cpu_b to 1050 mv
set vddee to 1000 mv
Board ID = 6
CPU clk: 1200MHz
DQS-corr enabled
DDR scramble enabled
DDR3 chl: Rank0+1 @ 912MHz - FAIL
DDR3 chl: Rank0 @ 912MHz - FAIL
DDR3 chl: Rank0 16bit @ 912MHz - FAIL
DDR4 chl: Rank0+1 @ 912MHzGXM:BL1:dc8b51:76f1a5;FEAT:ADFC318C:80;POC:2 ;RCY:0;USB:0;EMMC:0;READ:800;SD:0;READ:0;0.0;CHK:0 ;
no sdio debug board detected
TE: 146107

BL2 Built : 20:32:17, Sep 8 2017.
gxl g6296b83 - xiaobo.gu@droid12

set vdd cpu_a to 1120 mv
set vdd cpu_b to 1050 mv
set vddee to 1000 mv
Board ID = 6
CPU clk: 1200MHz
DQS-corr enabled
DDR scramble enabled
DDR3 chl: Rank0+1 @ 912MHz - FAIL
DDR3 chl: Rank0 @ 912MHz - FAIL
DDR3 chl: Rank0 16bit @ 912MHz - FAIL
DDR4 chl: R▒▒+1 @ 912MHzecGXM:BL1:dc8b51:76f1a5;FEAT:ADFC318C:80;POC :2;RCY:0;USB:0;EMMC:0;READ:800;SD:0;READ:0;0.0;CHK :0;
no sdio debug board detected
TE: 146126

BL2 Built : 20:32:17, Sep 8 2017.
gxl g6296b83 - xiaobo.gu@droid12

set vdd cpu_a to 1120 mv
set vdd cpu_b to 1050 mv
set vddee to 1000 mv
Board ID = 6
CPU clk: 1200MHz
DQS-corr enabled
DDR scramble enabled
DDR3 chl: Rank0+1 @ 912MHz - FAIL
DDR3 chl: Rank0 @ 912MHz - FAIL
DDR3 chl: Rank0 16bit @ 912MHz - FAIL
DDR4 chl: R▒-Z▒GXM:BL1:dc8b51:76f1a5;FEAT:ADFC318C:80;POC:2;RCY :0;USB:0;EMMC:0;READ:800;SD:0;READ:0;0.0;CHK:0;
no sdio debug board detected
TE: 146117

BL2 Built : 20:32:17, Sep 8 2017.
gxl g6296b83 - xiaobo.gu@droid12

set vdd cpu_a to 1120 mv
set vdd cpu_b to 1050 mv
set vddee to 1000 mv
Board ID = 6
CPU clk: 1200MHz
DQS-corr enabled
DDR scramble enabled
DDR3 chl: Rank0+1 @ 912MHz - FAIL
DDR3 chl: Rank0 @ 912MHz - FAIL
DDR3 chl: Rank0 16bit @ 912MHz - FAIL
DDR4 chl: R▒-Z▒▒912MHzGXM:BL1:dc8b51:76f1a5;FEAT:ADFC318C:80;PO C:2;RCY:0;USB:0;EMMC:0;READ:800;SD:0;READ:0;0.0;CH K:0;
no sdio debug board detected
TE: 146122

BL2 Built : 20:32:17, Sep 8 2017.
gxl g6296b83 - xiaobo.gu@droid12

set vdd cpu_a to 1120 mv
set vdd cpu_b to 1050 mv
set vddee to 1000 mv
Board ID = 6
CPU clk: 1200MHz
DQS-corr enabled
DDR scramble enabled
DDR3 chl: Rank0+1 @ 912MHz - FAIL
DDR3 chl: Rank0 @ 912MHz - FAIL
DDR3 chl: Rank0 16bit @ 912MHz - FAIL
DDR4 chl: R▒▒+1 @ 912MHzeGXM:BL1:dc8b51:76f1a5;FEAT:ADFC318C:80;POC: 2;RCY:0;USB:0;EMMC:0;READ:800;SD:0;READ:0;0.0;CHK: 0;
no sdio debug board detected
TE: 146134

BL2 Built : 20:32:17, Sep 8 2017.
gxl g6296b83 - xiaobo.gu@droid12

set vdd cpu_a to 1120 mv
set vdd cpu_b to 1050 mv
set vddee to 1000 mv
Board ID = 6
CPU clk: 1200MHz
DQS-corr enabled
DDR scramble enabled
DDR3 chl: Rank0+1 @ 912MHz - FAIL
DDR3 chl: Rank0 @ 912MHz - FAIL
DDR3 chl: Rank0 16bit @ 912MHz - FAIL
DDR4 chl: R▒kZ▒@ 912MHz

This continues like this as long as box is connected to pc.

[bumerc]

Okay, in about 1 hour I put a different bootloader version available, the clk rate has to be reduced. It is very sad that Beelink has such a poor RAM memory quality.

[Nebojsa]

Ok, thanks.