Bricked MXQ Pro+ 4K

[TJE]

This thing is dead as a door nail after a power flicker on and off rapidly.

As far as i can tell Uboot is gone as it does nothing untill a SD card uboot or USB Burner Uboot is pushed, It used to at least see the flash partitions but after trying to flash so much stuff and it failing im pretty sure the flash is formateed but not partitioned.

Does any one have a USB Burner rom that can recover this brick?

THe PCB is labled MXQ_S905X_D4 V1.1

its 2G/16G

Wifi is HS2734A

Ive even tried M96+ Pro roms since they share the same cpu and wifi. I get a Bag magic value when trying to detect the emmc

GXL:BL1:9ac50e:bb16dc;FEAT:ADFC318C:0;POC:3;RCY:0;EMMC:800;NAND:82;SD:800;USB:8;0.0;CHK:0;
TE: 40137645

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

set vcck to 1120 mv
set vddee to 1000 mv
Board ID = 4
CPU clk: 1200MHz
BL2 USB
DQS-corr enabled
DDR scramble enabled
DDR3 chl: Rank0 16bit @ 912MHz
Rank0: 2048MB-2T-13
0.0;CHK:0;
TE: 40246526

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

set vcck to 1120 mv
set vddee to 1000 mv
Board ID = 4
CPU clk: 1200MHz
BL2 USB
0.0;CHK:0;
TE: 40297220

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

set vcck to 1120 mv
set vddee to 1000 mv
Board ID = 4
CPU clk: 1200MHz
BL2 USB
Load fip header from USB, src: 0x0000c000, des: 0x01400000, size: 0x00004000
New fip structure!
Load bl30 from USB, src: 0x00010000, des: 0x01100000, size: 0x0000d600
Load bl31 from USB, src: 0x00020000, des: 0x05100000, size: 0x0002c600
Load bl33 from USB, src: 0x00050000, des: 0x01000000, size: 0x00066000
NOTICE:  BL3-1: v1.0(release):a625749
NOTICE:  BL3-1: Built : 11:25:15, Aug 25 2017
[BL31]: GXL CPU setup!
NOTICE:  BL31: BL33 decompress pass
mpu_config_enable:ok
[Image: gxl_v1.1.3243-377db0f 2017-09-07 11:28:58 qiufang.dai@droid07]
OPS=0xa4
5b 5c eb e6 a9 16 3d c2 9a 31 29 91 [40.537217 Inits done]
secure task start!
high task start!
low task start!
ERROR:   Error initializing runtime service opteed_fast


U-Boot 2015.01 (Jan 31 2018 - 11:28:26)

DRAM:  2 GiB
Relocation Offset is: 76eb2000
[MSG]MMC init in usb
aml_priv->desc_buf = 0x0000000073eb2640
aml_priv->desc_buf = 0x0000000073eb4960
SDIO Port B: 0, SDIO Port C: 1
InUsbBurn
[MSG]sof
Set Addr 28
Get DT cfg
Get DT cfg
Get DT cfg
set CFG

ID[16]
tplcmd[    echo 12345]
12345
[MSG]ret = 0
[info]success
BULKcmd[    low_power]
[info]success

ID[16]
tplcmd[    download mem dtb normal 88064]
[MSG]Down(mem) part(dtb) sz(0x15800) fmt(normal)
[MSG]totalSlotNum = 0, nextWriteBackSlot 2
[info]success
[MSG]Burn Start...
[MSG]load dt.img to 0x0000000001000000, sz=0x15800
[MSG]Burn complete
BULKcmd[download get_status]
[info]success
BULKcmd[disk_initial 0]
dtb magic 5f4c4d41
      Amlogic multi-dtb tool
      Multi dtb detected
      Multi dtb tool version: v2 .
      Support 2 dtbs.
        aml_dt soc: gxl platform: s905x013 variant: 2g
        dtb 0 soc: gxl   plat: s905x013   vari: 1g
        dtb 1 soc: gxl   plat: s905x013   vari: 2g
      Find match dtb: 1
start dts,buffer=0000000001000000,dt_addr=000000000100b000
      Amlogic multi-dtb tool
      Multi dtb detected
      Multi dtb tool version: v2 .
      Support 2 dtbs.
        aml_dt soc: gxl platform: s905x013 variant: 2g
        dtb 0 soc: gxl   plat: s905x013   vari: 1g
        dtb 1 soc: gxl   plat: s905x013   vari: 2g
      Find match dtb: 1
parts: 10
00:      logo   0000000002000000 1
01:  recovery   0000000002000000 1
02:       rsv   0000000000800000 1
03:       tee   0000000000800000 1
04:     crypt   0000000002000000 1
05:      misc   0000000002000000 1
06:      boot   0000000002000000 1
07:    system   0000000080000000 1
08:     cache   0000000020000000 2
09:      data   ffffffffffffffff 4
emmc/sd response timeout, cmd8, status=0x3ff2800
emmc/sd response timeout, cmd55, status=0x3ff2800

[Spuky]

Did you try with USB Burning tool with "Force erase all" method? Mine wasn't able to write the new Uboot after a failed rom installed.Even to make the PC recognize the box i had to short the IO pins on the board.

[TJE]

Did you try with USB Burning tool with "Force erase all" method? Mine wasn't able to write the new Uboot after a failed rom installed.Even to make the PC recognize the box i had to short the IO pins on the board.

I did, It didnt help and with out writing uboot then im stuck anyways. It looks liek it fails to init the emmc.