[Bricked] VONTAR X3 Amlogic S905X3 4/64GB

[loocas]

Hi!

I bought Amlogic S905X3 4/64GB 1Gbit Ethernet Android Box (VONTAR X3) and it was DOA. No input from HDMI, only two LEDs are glowing and that’s it.

I tried Amlogic Burning Tool, without success. My PC doesn’t see the device despite using USB male-male cable capable of data transfer.

I tried shorting some ‘pins’ as shown here (source: 4pda) but that didn’t work either. Maybe these aren’t the ‘pins’ I am looking for?

Also tried the reset button behind the AV/jack port but nothing happened.

Anyway, I’ve connected the device using UART and here’s my PuTTY log:

=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2020.10.03 19:16:17 =~=~=~=~=~=~=~=~=~=~=~=
SM1:BL:511f6b:81ca2f;FEAT:A0F83180:20282000;POC:F; RCY:0;EMMC:0;READ:0;0.0;CHK:0;
bl2_stage_init 0x01
bl2_stage_init 0x81
hw id: 0x0001 - pwm id 0x00
bl2_stage_init 0xc0
bl2_stage_init 0x02

L0:00000000
L1:00000703
L2:00008067
L3:15000020
S1:00000000
B2:20282000
B1:a0f83180

TE: 101694

BL2 Built : 20:29:41, Jun 18 2019. g12a ga659aac - luan.yuan@droid15-sz

Board ID = 1
Set cpu clk to 24M
Set clk81 to 24M
Use GP1_pll as DSU clk.
DSU clk: 1200 Mhz
CPU clk: 1200 MHz
Set clk81 to 166.6M
eMMC boot @ 0
sw8 s
DDR driver_vesion: LPDDR4_PHY_V_0_1_15 build time: Jun 18 2019 20:29:37
board id: 1
Load FIP HDR from eMMC, src: 0x00010200, des: 0xfffd0000, size: 0x00004000, part: 0
fw parse done
Load ddrfw from eMMC, src: 0x00060200, des: 0xfffd0000, size: 0x0000c000, part: 0
Load ddrfw from eMMC, src: 0x00038200, des: 0xfffd0000, size: 0x00004000, part: 0
PIEI prepare done
fastboot data load
00000000
emmc switch 1 ok
ddr saved addr:00016000
Load ddr parameter from eMMC, src: 0x02c00000, des: 0xfffd0000, size: 0x00001000, part: 0
00000000
emmc switch 0 ok
fastboot data verify
verify result: 0
enable_fast_boot
dmc_margin_rx==12 dmc_margin_tx==11 steps
DDR3 probe
ddr clk to 672MHz
Load ddrfw from eMMC, src: 0x0002c200, des: 0xfffd0000, size: 0x0000c000, part: 0

dmc_version 0001
Check phy result
INFO : End of initialization
INFO : Training has run successfully!
aml_ddr_fw_vesion: LPDDR4_PHY_V_0_1_15 build time: Jun 18 2019 20:29:43
DDR cs0 size: 3928MB
DDR cs1 size: 0MB
DMC_DDR_CTRL: 0000002dDDR size: 3928MB
DATA-W[0x00000000]:0xaaaaaaaa,R:0xaaafaaaa
fail D16 18
DATA-W[0x00000000]:0x55555555,R:0x55515555
fail D18
DATA-W[0x00000000]:0x00000001,R:0x00010001
fail D16
DATA-W[0x00000000]:0x00000002,R:0x00010002
fail D16
DATA-W[0x00000000]:0x00000004,R:0x00010004
fail D16
DATA-W[0x00000000]:0x00000008,R:0x00010008
fail D16
DATA-W[0x00000000]:0x00000010,R:0x00010010
fail D16
DATA-W[0x00000000]:0x00000020,R:0x00010020
fail D16
DATA-W[0x00000000]:0x00000040,R:0x00010040
fail D16
DATA-W[0x00000000]:0x00000080,R:0x00010080
fail D16
DATA-W[0x00000000]:0x00000100,R:0x00010100
fail D16
DATA-W[0x00000000]:0x00000200,R:0x00010200
fail D16
DATA-W[0x00000000]:0x00000400,R:0x00010400
fail D16
DATA-W[0x00000000]:0x00000800,R:0x00010800
fail D16
DATA-W[0x00000000]:0x00001000,R:0x00011000
fail D16
DATA-W[0x00000000]:0x00002000,R:0x00012000
fail D16
DATA-W[0x00000000]:0x00004000,R:0x00014000
fail D16
DATA-W[0x00000000]:0x00008000,R:0x00018000
fail D16
DATA-W[0x00000000]:0x00040000,R:0x00010000
fail D16 18
DATA-W[0x00000000]:0x00080000,R:0x00090000
fail D16
DATA-W[0x00000000]:0x00100000,R:0x00110000
fail D16
DATA-W[0x00000000]:0x00200000,R:0x00210000
fail D16
DATA-W[0x00000000]:0x00400000,R:0x00410000
fail D16
DATA-W[0x00000000]:0x00800000,R:0x00810000
fail D16
DATA-W[0x00000000]:0x01000000,R:0x01010000
fail D16
DATA-W[0x00000000]:0x02000000,R:0x02010000
fail D16
DATA-W[0x00000000]:0x04000000,R:0x04010000
fail D16
DATA-W[0x00000000]:0x08000000,R:0x08010000
fail D16
DATA-W[0x00000000]:0x10000000,R:0x10010000
fail D16
DATA-W[0x00000000]:0x20000000,R:0x20010000
fail D16
DATA-W[0x00000000]:0x40000000,R:0x40010000
fail D16
DATA-W[0x00000000]:0x80000000,R:0x80010000
fail D16
cs0 DataBus test failed
ADDR-W[0x00000004]:0xaaaaaaaa,R:0xaaaeaaaa
cs0 AddrBus test failed
fail address pin cs 0 add 0x 00000004
Cfg max: 5, cur: 1. Board id: 255. Force loop cfg
DDR3 probe
ddr clk to 672MHz
Load ddrfw from eMMC, src: 0x0002c200, des: 0xfffd0000, size: 0x0000c000, part: 0

dmc_version 0001
Check phy result
INFO : End of initialization
INFO : ERROR : Training has failed!
1D training failed
Cfg max: 5, cur: 2. Board id: 255. Force loop cfg
DDR3 probe
ddr clk to 672MHz
Load ddrfw from eMMC, src: 0x0002c200, des: 0xfffd0000, size: 0x0000c000, part: 0

dmc_version 0001
Check phy result
INFO : End of initialization
INFO : End of read enable training
INFO : End of fine write leveling
INFO : ERROR : Training has failed!
1D training failed
Cfg max: 5, cur: 3. Board id: 255. Force loop cfg
DDR3 probe
ddr clk to 672MHz
Load ddrfw from eMMC, src: 0x0002c200, des: 0xfffd0000, size: 0x0000c000, part: 0

dmc_version 0001
Check phy result
INFO : End of initialization
INFO : End of read enable training
INFO : End of fine write leveling
INFO : ERROR : Training has failed!
1D training failed
Cfg max: 5, cur: 4. Board id: 255. Force loop cfg
LPDDR4 probe
ddr clk to 1008MHz
Load ddrfw from eMMC, src: 0x0003c200, des: 0xfffd0000, size: 0x0000c000, part: 0

dmc_version 0001
Check phy result
INFO : ERROR : Training has failed!
1D training failed
Cfg max: 5, cur: 5. Board id: 255. Force loop cfg
DDR3 probe
ddr clk to 672MHz
Load ddrfw from eMMC, src: 0x0002c200, des: 0xfffd0000, size: 0x0000c000, part: 0

dmc_version 0001
Check phy result
INFO : End of initialization
INFO : End of read enable training
INFO : End of fine write leveling
INFO : ERROR : Training has failed!
1D training failed
All ddr config failed...
Reset...
boot times 0

And it loops from there to eternity so I decided to post only one loop. Looks like faulty RAM?

Here are some PCB photos (sorry for using imgur but I got an error when I tried to upload photos directly):

https://imgur.com/a/JH8OAEn

Is it dead like disco or can it be reanimated somehow?

Any help would be greatly appreciated.

[freddy]

Hmmmmmmmmmmmmmmm

Is that PuTTy Log from Original Factory Firmare?

Drivers in kernel are LPDDR4....

Vontar is DDR3 Ram.....

Thats all i can see in session...


Others with more knowledge will help maybe

Is it to late to put back in box and send back to Seller?

Should be 30 day Guarantee

[ath156]

At 4pda and at the top of the page for HK1/Vontar X3 etc, there is clearly written (with red letters) that if 2 leds are glowing immediately after you bought your box, the best option is to contact the seller and start a dispute (asking for full refund). That is what I would do if I were you.

[loocas]

Is that PuTTy Log from Original Factory Firmare?

It would seem so. It never booted and it was never detected by my PC. I didn't even have a chance to brick it myself

As for returns or refunds, it has been sorted out already. I just wanna know if it can be fixed.

[freddy]

Can probs be fixed

Vontar has DDR4 and DDR3

Which image did you have loaded in Amlogic Tool ?
When you tried/shorted pins/Maskrom Mode.

And you probably had erase bootloader checked/selected.
As we all do.

Just a thought

[loocas]

I really appreciate your help

I don’t think it was a bad image file because I never got to that point From what I’ve seen on YouTube the device should appear listed under DeviceID/Status in AmLogic Burning Tool but that never happened in my case. I can’t get my PC to communicate with the device. Probably because it’s stuck in a bootloop and can’t enter recovery mode.

Everything that you see in my PuTTY log takes less than a second and then it reboots. Shorting the two copper contacts from the photo doesn’t do anything… at least according to PuTTY log.

You think they flashed the wrong version by mistake?

[freddy]

Here is my thoughts
User can not fix.....
Unless you are Rom Developer

Vontar has older models with DDR3 they are trying to move

Vontar should have included drivers for both in kernel

And changed to Read As auto detect/auto select/read all ram/etc...
Or something like that in code...

Best listen to Ath156

That is why they want you to return immediately when led status is
What Ath156 posted.

Return it and Move on..

Vontar still a good product!!!

You just got a Lemon

It happens and Vendor should accomadate you

Good Luck

Happy Testing

[loocas]

I got a partial refund already. I just wanna know if anything can be done to unbrick the device. If not then it goes to the trash can.

[freddy]

Hmmmmmmmmm

My replys are based on PuYYy Log only
I do not test this box

When i posted only Rom Developer can fix was referring to Vontar Firmware.

If it is as simple as Finding the Correct image for your box with DDR3 RAM
Wifi
Bluetooth
Ethernet TRanseiver
Remote control/config

Then by all means
Do not throw in trash

In pics you have blacked out specs/model#/etc... on sticker..

What is written there
Type that into Big G

Or maybe try something like vontar X3 factory firmware with DDR3 Ram

Should be directed to Links and Video,U Tube etc...

[loocas]

If it is as simple as Finding the Correct image for your box with DDR3 RAM

Sadly, its not that simple.

First I have to connect the box to my PC. But my PC doesn't see the box. I tried different PC with Windows 7 and Window 10. I also tried different USB cables. The drivers and AmLogic Burning Tool are installed. I cannot flash the firmware if I can't get the device to be discovered by my PC. That's my only issue.

Bottom line: I have the correct firmware but I just cannot flash it to the device.

[freddy]

Well

Welcome to the Testing Zone Ioocas !!!!

Read ,Reasearch,Watch more videos on U tube
Threads here at Home Freak Tab.Russian Forum.4PDA,etc...

Maybe

Try Booting From SD Card

Try LibreElec for S905X3

Or Better Armbian Bionic For S905X3
Withh Armbian you should be able to access eMMc and overwrite/clear volume/partition/etc...

[loocas]

There has been a development. Windows can now discover the device. It turns out that shorting those two contacts/pins from 4dpa photos is the way to go. However it takes like 20-25 tries to make it work and that’s a lot of time. I discovered that you can just plug in the power adapter then connect the device using USB cable and then go crazy on the pins. It will work eventually. UART shows bootloop as usual but if you manage to short the pins then you get this:

SM1:BL:511f6b:81ca2f;FEAT:A0F83180:20282000;POC:F; RCY:0;EMMC:800;NAND:82;SD?:20000;USB:8;0.0;C

Normal boot looks like this:
SM1:BL:511f6b:81ca2f;FEAT:A0F83180:20282000;POC:F; RCY:0;EMMC:0;READ:0;0.0;CHK:0;

When it says USB:8 and then it means USB is detected and the device is visible in USB Burning Tool. It seems that EMMC:800 means that it skips eMMC.

PuTTY log when the device got successfully connected to the USB - I tried to flash the (supposedly correct) firmware:

SM1:BL:511f6b:81ca2f;FEAT:A0F83180:20282000;POC:F;RCY:0;EMMC:800;NAND:82;SD?:20000;USB:8;0.0;C
bl2_stage_init 0x01
bl2_stage_init 0x81
hw id: 0x0001 - pwm id 0x00
bl2_stage_init 0xc0
bl2_stage_init 0x02

L0:00000000
L1:00000703
L2:00008067
L3:15000020
S1:00000000
B2:20282000
B1:a0f83180

TE: 2457950

BL2 Built : 15:21:48, Aug 28 2019. g12a g1bf2b53 - luan.yuan@droid15-sz

Board ID = 1
Set cpu clk to 24M
Set clk81 to 24M
Use GP1_pll as DSU clk.
DSU clk: 1200 Mhz
CPU clk: 1200 MHz
Set clk81 to 166.6M
DDR driver_vesion: LPDDR4_PHY_V_0_1_18 build time: Aug 28 2019 15:21:45
board id: 1
Cfg max: 5, cur: 1. Board id: 255. Force loop cfg
DATA transfer complete...
fw parse done
DATA transfer complete...
AML DDR FW load done
DATA transfer complete...
PIEI prepare done
DDR3 probe
ddr clk to 480MHz
DATA transfer complete...

dmc_version 0001
Check phy result
INFO : End of initialization
INFO : ERROR : Training has failed!
Cfg max: 5, cur: 2. Board id: 255. Force loop cfg
ddr probe id done
DATA transfer complete...
fw parse done
DATA transfer complete...
AML DDR FW load done
DATA transfer complete...
PIEI prepare done
DDR3 probe
ddr clk to 480MHz
DATA transfer complete...

dmc_version 0001
Check phy result
INFO : End of initialization
INFO : End of read enable training
INFO : End of fine write leveling
INFO : ERROR : Training has failed!
Cfg max: 5, cur: 3. Board id: 255. Force loop cfg
ddr probe id done
DATA transfer complete...
fw parse done
DATA transfer complete...
AML DDR FW load done
DATA transfer complete...
PIEI prepare done
DDR3 probe
ddr clk to 480MHz
DATA transfer complete...

dmc_version 0001
Check phy result
INFO : End of initialization
INFO : End of read enable training
INFO : End of fine write leveling
INFO : ERROR : Training has failed!
Cfg max: 5, cur: 4. Board id: 255. Force loop cfg
ddr probe id done
DATA transfer complete...
fw parse done
DATA transfer complete...
AML DDR FW load done
DATA transfer complete...
PIEI prepare done
LPDDR4 probe
ddr clk to 1008MHz
DATA transfer complete...

dmc_version 0001
Check phy result
INFO : ERROR : Training has failed!
Cfg max: 5, cur: 5. Board id: 255. Force loop cfg
ddr probe id done
DATA transfer complete...
fw parse done
DATA transfer complete...
AML DDR FW load done
DATA transfer complete...
PIEI prepare done
LPDDR4 probe
ddr clk to 1008MHz
DATA transfer complete...

dmc_version 0001
Check phy result
INFO : ERROR : Training has failed!
All ddr config failed...
Try next cfg
Exit data request loop...Err0x00000020

Here's USB Burning Tool Log of the same event:

[01:16:11 926][HUB7-1][Inf]--Start burning...
[01:16:11 978][HUB7-1][Inf]--------------ERASE BOOTLOADER------------
[01:16:12 079][HUB7-1][Inf]--start SendIdentifyCmd
[01:16:12 079][HUB7-1][Inf]--3-2-0-0
[01:16:12 079][HUB7-1][Inf]-------------Download DDR.USB-----------
[01:16:12 080][HUB7-1][Inf]--3-2-0-0
[01:16:12 080][HUB7-1][Inf]--Control write pll reg1 0xfffa0000:0x000000b1
[01:16:12 581][HUB7-1][Inf]--Control write pll reg1 0xfffa0000:0x00005183
[01:16:13 082][HUB7-1][Inf]--Control write pll reg1 0xfffa0000:0x000000b1
[01:16:13 583][HUB7-1][Inf]--Control write pll reg1 0xfffa0000:0x00005183
[01:16:14 084][HUB7-1][Inf]--Write initial succeed
[01:16:14 084][HUB7-1][Inf]--Upload encrypt at 0xff800228
[01:16:14 084][HUB7-1][Inf]--ulValue = 0xa0f83180
[01:16:14 084][HUB7-1][Inf]--Read encrypt value succeed
[01:16:14 084][HUB7-1][Inf]--Download DDR.USB,size: 65536!
[01:16:14 095][HUB7-1][Inf]--Transfer complete 65536
[01:16:14 095][HUB7-1][Inf]--Run at address 0xfffa0000
[01:16:14 096][HUB7-1][Inf]--RunInRam success
[01:16:14 145][HUB7-1][Inf]--0-0-1-8-0-1-0-0
[01:16:14 145][HUB7-1][Inf]--CheckFileRunState return 1-8
[01:16:14 145][HUB7-1][Inf]--0-0-1-8-0-1-0-0
[01:16:14 145][HUB7-1][Inf]--G12 init
[01:16:14 146][HUB7-1][Inf]--Get Encrpt ulValue = 0xa0f83180
[01:16:14 146][HUB7-1][Inf]--Have Semaphore
[01:16:14 146][HUB7-1][Inf]--Download BL2
[01:16:14 146][HUB7-1]Aml_Libusb_bl2_boot2 start!
[01:16:14 149][HUB7-1]sequence= 0, datasize= 16384, fipOffset= 65536
[01:16:14 155][HUB7-1]sequence= 1, datasize= 49152, fipOffset= 393216
[01:16:14 160][HUB7-1]sequence= 2, datasize= 16384, fipOffset= 229376
[01:16:14 169][HUB7-1]sequence= 3, datasize= 49152, fipOffset= 180224
[01:16:14 189][HUB7-1]sequence= 4, datasize= 16384, fipOffset= 65536
[01:16:14 196][HUB7-1]sequence= 5, datasize= 49152, fipOffset= 393216
[01:16:14 201][HUB7-1]sequence= 6, datasize= 16384, fipOffset= 229376
[01:16:14 209][HUB7-1]sequence= 7, datasize= 49152, fipOffset= 180224
[01:16:14 236][HUB7-1]sequence= 8, datasize= 16384, fipOffset= 65536
[01:16:14 242][HUB7-1]sequence= 9, datasize= 49152, fipOffset= 393216
[01:16:14 247][HUB7-1]sequence= 10, datasize= 16384, fipOffset= 229376
[01:16:14 256][HUB7-1]sequence= 11, datasize= 49152, fipOffset= 180224
[01:16:14 283][HUB7-1]sequence= 12, datasize= 16384, fipOffset= 65536
[01:16:14 290][HUB7-1]sequence= 13, datasize= 49152, fipOffset= 393216
[01:16:14 295][HUB7-1]sequence= 14, datasize= 16384, fipOffset= 229376
[01:16:14 304][HUB7-1]sequence= 15, datasize= 49152, fipOffset= 245760
[01:16:14 326][HUB7-1]sequence= 16, datasize= 16384, fipOffset= 65536
[01:16:14 333][HUB7-1]sequence= 17, datasize= 49152, fipOffset= 393216
[01:16:14 338][HUB7-1]sequence= 18, datasize= 16384, fipOffset= 229376
[01:16:14 347][HUB7-1]sequence= 19, datasize= 49152, fipOffset= 245760
[01:16:14 365]BL2 report Error, code= 32
[01:16:14 365][HUB7-1]cmd error, cmdType:43984
[01:16:14 365][HUB7-1]Aml_Libusb_bl2_boot2 end!
[01:16:14 365][HUB7-1][Inf]--Release Semaphore
[01:16:24 549][HUB7-1][Inf]--Detect Device remove timeout
[01:16:24 549][HUB7-1][Inf]--Device is connected
[01:16:24 549][HUB7-1][Inf]--Close device handle 0x00000934
[01:16:24 600][HUB7-1][Inf]--Open device handle \\?\usb#vid_1b8e&pid_c003#6&32f7c957&0&1#{a5dcbf10-6530-11d2-901f-00c04fb951ed}  0x0000056c
[01:16:29 651][HUB7-1][Inf]--0-0-1-8
[01:16:29 651][HUB7-1][Err]--CheckFileRunState failed
[01:16:29 696][HUB7-1][Err]--[0x10303004]Romcode/Switch status/Identify/Error result
[01:16:29 696][HUB7-1][Inf]--Close device handle 0x0000056c

Now I can’t get past 3% because I get this error (Burning Tool status: Download UBOOT):
[0x10303004]Romcode/Switch status/Identify/Error result

As suggested on the forums I tried to plug directly into MoBo USB, I changed the temperature settings, I pushed the reset AV button before flashing, during flashing, after flashing, used different settings (all options ticked in the Burning Tool, all unticked, normal erase, full erase, erase bootlader, don't erase bootloader etc.). Nothing has worked so far. I read that short USB cables are better but mine is already about 10 cm so I don't think that's the problem.

I also tried Burn Card Maker. It works the same as USB - you have to short pins to boot from SD. Reset button etc. doesn't work. I also tried to flash from USB stick with the same (non)results.
Here's PuTTY log when trying to flash from SD:

SM1:BL:511f6b:81ca2f;FEAT:A0F83180:20282000;POC:F;RCY:0;EMMC:800;NAND:82;SD?:0;SD:0;READ:0;0.0;CHK:0;
bl2_stage_init 0x01
bl2_stage_init 0x81
hw id: 0x0001 - pwm id 0x00
bl2_stage_init 0xc0
bl2_stage_init 0x02

no sdio debug board detected
L0:00000000
L1:00000703
L2:00008067
L3:15000020
S1:00000000
B2:20282000
B1:a0f83180

TE: 351876

BL2 Built : 15:21:48, Aug 28 2019. g12a g1bf2b53 - luan.yuan@droid15-sz

Board ID = 1
Set cpu clk to 24M
Set clk81 to 24M
Use GP1_pll as DSU clk.
DSU clk: 1200 Mhz
CPU clk: 1200 MHz
Set clk81 to 166.6M
DDR driver_vesion: LPDDR4_PHY_V_0_1_18 build time: Aug 28 2019 15:21:45
board id: 1
Load FIP HDR from SD, src: 0x00010200, des: 0xfffd0000, size: 0x00004000, part: 0
fw parse done
Load ddrfw from SD, src: 0x00060200, des: 0xfffd0000, size: 0x0000c000, part: 0
Load ddrfw from SD, src: 0x00038200, des: 0xfffd0000, size: 0x00004000, part: 0
PIEI prepare done
fastboot data load
fastboot data verify
verify result: 266
Cfg max: 5, cur: 1. Board id: 255. Force loop cfg
DDR3 probe
ddr clk to 672MHz
Load ddrfw from SD, src: 0x0002c200, des: 0xfffd0000, size: 0x0000c000, part: 0

dmc_version 0001
Check phy result
INFO : End of initialization
INFO : ERROR : Training has failed!
1D training failed
Cfg max: 5, cur: 2. Board id: 255. Force loop cfg
DDR3 probe
ddr clk to 672MHz
Load ddrfw from SD, src: 0x0002c200, des: 0xfffd0000, size: 0x0000c000, part: 0

dmc_version 0001
Check phy result
INFO : End of initialization
INFO : End of read enable training
INFO : End of fine write leveling
INFO : ERROR : Training has failed!
1D training failed
Cfg max: 5, cur: 3. Board id: 255. Force loop cfg
DDR3 probe
ddr clk to 672MHz
Load ddrfw from SD, src: 0x0002c200, des: 0xfffd0000, size: 0x0000c000, part: 0

dmc_version 0001
Check phy result
INFO : End of initialization
INFO : End of read enable training
INFO : End of fine write leveling
INFO : ERROR : Training has failed!
1D training failed
Cfg max: 5, cur: 4. Board id: 255. Force loop cfg
LPDDR4 probe
ddr clk to 1008MHz
Load ddrfw from SD, src: 0x0003c200, des: 0xfffd0000, size: 0x0000c000, part: 0

dmc_version 0001
Check phy result
INFO : ERROR : Training has failed!
1D training failed
Cfg max: 5, cur: 5. Board id: 255. Force loop cfg
LPDDR4 probe
ddr clk to 1008MHz
Load ddrfw from SD, src: 0x0003c200, des: 0xfffd0000, size: 0x0000c000, part: 0

dmc_version 0001
Check phy result
INFO : ERROR : Training has failed!
1D training failed
All ddr config failed...
Reset...
boot times 0

I tried the following firmware I found online:
HK1_X3_S905X3_1000M_U212_9.0.2019.11.23.18.29.img
HK1Slimbox_sbx_vontar_pie_v9.img
u218.VONTAR_X3_1000M_9.0.2019.12.16.15.29.img
u218.VONTAR_X3_1000M_9.0.2019.12.28.11.18.img
u218.VONTAR_X3_1000M_9.0.2020.01.13.15.46.img
u218.VONTAR_X3_1000M_9.0.2020.04.06.10.48_NOT_KEY. img
u218.VONTAR_X3_1000M_9.0.2020.07.01.06.44.img
u218.VONTAR_X3_1000M_9.0.2020.09.18.23.53.img
u219.HK1_BOX_1000M_9.0.2019.12.28.11.34.img
u219_HK1_BOX_Malay_Mod_v_1.2_28_02_2020.img

I also tried CoreElec using sm1_s905x3_4g_1gbit.dtb -> dtb.img but that didn't work either.

Some additional info:
- part D9PQL is Micron DDR3 RAM and if you check my photo of the bottom of the device you will see that one die in the upper-right corner looks kind of burnt? Maybe that's the problem?
- during normal boot (no USB or SD, no shorting pins) the log says:
BL2 Built : 15:21:48, Aug 28 2019. g12a g1bf2b53 - luan.yuan@droid15-sz

g12a - according to CoreElec g12a is for S905X2 devices.

At this point I think I wasted too much time on this *beep*ing box so if anyone has some good ideas I'd really appreciate it.

[RiCkLaR_atvX]

There has been a development. Windows can now discover the device. It turns out that shorting those two contacts/pins from 4dpa photos is the way to go. However it takes like 20-25 tries to make it work and that’s a lot of time. I discovered that you can just plug in the power adapter then connect the device using USB cable and then go crazy on the pins. It will work eventually. UART shows bootloop as usual but if you manage to short the pins then you get this:
SM1:BL:511f6b:81ca2f;FEAT:A0F83180:20282000;POC:F; RCY:0;EMMC:800;NAND:82;SD?:20000;USB:8;0.0;C
Normal boot looks like this:
SM1:BL:511f6b:81ca2f;FEAT:A0F83180:20282000;POC:F; RCY:0;EMMC:0;READ:0;0.0;CHK:0;
When it says USB:8 and then it means USB is detected and the device is visible in USB Burning Tool. It seems that EMMC:800 means that it skips eMMC.
PuTTY log when the device got successfully connected to the USB - I tried to flash the (supposedly correct) firmware:
...
...
Now I can’t get past 3% because I get this error (Burning Tool status: Download UBOOT):
[0x10303004]Romcode/Switch status/Identify/Error result
As suggested on the forums I tried to plug directly into MoBo USB, I changed the temperature settings, I pushed the reset AV button before flashing, during flashing, after flashing, used different settings (all options ticked in the Burning Tool, all unticked, normal erase, full erase, erase bootlader, don't erase bootloader etc.). Nothing has worked so far. I read that short USB cables are better but mine is already about 10 cm so I don't think that's the problem.
I also tried Burn Card Maker. It works the same as USB - you have to short pins to boot from SD. Reset button etc. doesn't work. I also tried to flash from USB stick with the same (non)results.
Here's PuTTY log when trying to flash from SD:
...
I tried the following firmware I found online:
HK1_X3_S905X3_1000M_U212_9.0.2019.11.23.18.29.img
HK1Slimbox_sbx_vontar_pie_v9.img
u218.VONTAR_X3_1000M_9.0.2019.12.16.15.29.img
u218.VONTAR_X3_1000M_9.0.2019.12.28.11.18.img
u218.VONTAR_X3_1000M_9.0.2020.01.13.15.46.img
u218.VONTAR_X3_1000M_9.0.2020.04.06.10.48_NOT_KEY. img
u218.VONTAR_X3_1000M_9.0.2020.07.01.06.44.img
u218.VONTAR_X3_1000M_9.0.2020.09.18.23.53.img
u219.HK1_BOX_1000M_9.0.2019.12.28.11.34.img
u219_HK1_BOX_Malay_Mod_v_1.2_28_02_2020.img
I also tried CoreElec using sm1_s905x3_4g_1gbit.dtb -> dtb.img but that didn't work either.
Some additional info:
- part D9PQL is Micron DDR3 RAM and if you check my photo of the bottom of the device you will see that one die in the upper-right corner looks kind of burnt? Maybe that's the problem?
- during normal boot (no USB or SD, no shorting pins) the log says:
BL2 Built : 15:21:48, Aug 28 2019. g12a g1bf2b53 - luan.yuan@droid15-sz
g12a - according to CoreElec g12a is for S905X2 devices.
At this point I think I wasted too much time on this *beep*ing box so if anyone has some good ideas I'd really appreciate it.

BL2 is your bootloader, looks like you got the wrong bootloader installed in the eMMC from the factory, some of the SM1 (s905x3) share the same bootloader's as the G12A (s905x2) with only the difference being the name in header with everything else being the same, so in essence a G12A bootloader should boot a SM1 device if they have the same spec RAM.

Are you making sure to Check the box "Force Erase" and are using the most current release of the USB-burning-tool version Have you made sure to click "START" in tool before shorting-the-pins? Once the short occurs the USB-burning-tool will immediately register device and start the installation process; and it doesn't hurt to also plug in the power supply for device to make sure it is fully energized through the burning process.

I already forgot where the actual points to short on the Vontar_X3 are, but a better way might be to target the bus points on board directly under the CPU take a low voltage wire (about 10cm long) and hold one grounded on the hdmi exterior housing and proceed to short every single point under CPU until you find the correct point where device will start burning.

[freddy]

Yes
What RiCkLaR posted

Wrong /or missing config for DDR RAM in BL2

USB error 32

Maybe this is why probe for DDR3 /DDR4

Hopefully is not locked/encrypted
Or luan.yuan.... has other for DDR4 Vontar

[loocas]

Are you making sure to Check the box "Force Erase" and are using the most current release of the USB-burning-tool version Have you made sure to click "START" in tool before shorting-the-pins? Once the short occurs the USB-burning-tool will immediately register device and start the installation process; and it doesn't hurt to also plug in the power supply for device to make sure it is fully energized through the burning process.

In USB Burning tool there's only 'Erase All' option and I tried that. 'Force Erasing' is only available in Burn Card Maker and I also tried that when booting from SD. There's also 'forcelly erase all' option in Burn Card Maker 2.0.2 but it's absent from version 2.0.3. Someone said that this option can erase some DRM from NAND and it's not recommended. I didn't try that yet but might do that in the future. Though it's odd that they removed that option from the latest version.

I tried USB Burning Tool 2.0.8, 2.1.7, 2.1.9, 2.2.0 and 3.1 but when I load my FW in version 3.1 it automatically opens up version 2.1.8 (there are 2 folders in Burning Tool 3.1 directory: V2 with 2.1.8 version and V3 which is v3.1.0).

Yes, I usually press 'Start' button before shorting but I also tried shorting first and then pushing the 'Start' button. It quickly goes to 3% then it says 'Download Uboot' then it gets stuck at 3% for about 15 seconds (the timer goes to around 17-20) and then: [0x10303004]Romcode/Switch status/Identify/Error result

I also plugged in power supply during the process, before the process, no power supply at all and so on.

But even if I have the wrong bootloader on eMMC then why can't I boot CoreElec? It should skip eMMC and boot from SD or USB but that doesn't work either. I tried different boot files from device_trees but it didn't boot. There's nothing on screen with HDMI plugged in.

Yes
What RiCkLaR posted

Wrong /or missing config for DDR RAM in BL2

USB error 32

Maybe this is why probe for DDR3 /DDR4

Hopefully is not locked/encrypted
Or luan.yuan.... has other for DDR4 Vontar

I think D9PQL is DDR3.