[HOW TO RECOVER] So you bricked your box

[MrJCub]

Hello,

I'm looking for some help with a T95Z Plus that seems bricked.
I loaded firmware with USB Burn Tool but in the issues of trying to load it, I unclicked erase bootloader and when it finished loading, the device only shows the blue led, no display on tv.
I've tried booting from microSD with and without reset button pressed, but nothing.
Tried connecting to computer, but doesn't find it.
Tried shorting pins on nand chip, but couldn't find the right pins. Chip has THGBMFG8C4LBAIR on it and can't find datasheet.
Board is Green, with XJH-V99-V00 2018-03-31.

Here is the Boot log from Serial monitor:

GXM:BL1:dc8b51:76f1a5;FEAT:ADFC318C:80;POC:3;RCY:0 ;EMMC:0;READ:0;0.0;CHK:0;
TE: 86276

BL2 Built : 18:50:13, Sep 22 2017.
gxl g4786fda-dirty - jiaxing.ye@droid12

set vdd cpu_a to 1120 mv
set vdd cpu_b to 1050 mv
set vddee to 1000 mv
Board ID = 3
CPU clk: 1200MHz
DQS-corr enabled
DDR scramble disabled
STICKY_REG0: 0x00000000
STICKY_REG8: 0x00000000
STICKY_REG9: 0x00000000
LPDDR3 chl: Rank0+1 @ 720MHz
ddr_lpddr3_only_up_odt_enable: 0x00000001....
Training PGSR0: 0x80001fbf....
ddr_training_inf: rank: 0 org_wr0 w0_l w0_r org_r0 r0_l r0_r org_wr1 w1_l w1_r org_r1 r1_l r1_r org_wr2 w2_l w2_r org_r2 r2_l r2_r org_wr3 w3_l w3_r org_r3 r3_l r3_r
af_vrefddr_training_win: rank: 0 21 00 45 3d 18 63 17 00 31 44 1c 6e 20 00 41 3c 15 65 1f 00 40 3b 13 64 674 rank: 1 22 00 45 3d 18 63 17 00 31 45 1c 6e 20 00 41 3d 15 65 1f 00 40 3b 13 64 674
bist_test rank: 0 20 12 2f 40 2c 54 19 03 2f 42 2c 59 24 10 39 3d 2a 50 20 0a 37 3a 23 52 674 rank: 1 1f 10 2f 3e 2b 52 19 03 2f 43 2e 59 22 0d 37 3c 2a 4f 21 0a 39 3a 23 51 674 bist_size0x 000007e0 bist_cost_time 350986 us bist test no threshold setting:
ddr_refi_counter37
DDR1_ADDRMAP_0== 0x14941cc5
DDR1_ADDRMAP_1== 0x230783ab
DDR1_ADDRMAP_2== 0x2f6ad272
DDR1_ADDRMAP_3== 0x3bcdeb38
DDR1_ADDRMAP_4== 0x0007359e

Rank0: 2048MB-2T-3

Rank1: 1024MB-2T-3
DataBus test pass!
AddrBus test pass!
-s
Load fip header from eMMC, src: 0x0000c200, des: 0x01400000, size: 0x00004000
New fip structure!
Load bl30 from eMMC, src: 0x00010200, des: 0x01100000, size: 0x0000d600
Load bl31 from eMMC, src: 0x00020200, des: 0x05100000, size: 0x0002c600
Load bl33 from eMMC, src: 0x00050200, des: 0x01000000, size: 0x00065a00
NOTICE: BL3-1: v1.0(release):a625749
NOTICE: BL3-1: Built : 11:25:15, Aug 25 2017
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=0x82
wdt: reset registers!
89 d9 d8 0 ce 6f af 8e 21 97 61 76 [0.734996 Inits done]
secure task start!
high task start!
low task start!
ERROR: Error initializing runtime service opteed_fast


U-Boot 2015.01 (Dec 26 2017 - 15:03:06)

DRAM: 3 GiB
Relocation Offset is: b6eb4000
12345678
10112281101!
initcall sequence 00000000b7f5b818 failed at call 0000000001009120 (err=-1)
### ERROR ### Please RESET the board ###

[X92-2GB]

Hello,

I'm looking for some help with a T95Z Plus that seems bricked.
I loaded firmware with USB Burn Tool but in the issues of trying to load it, I unclicked erase bootloader and when it finished loading, the device only shows the blue led, no display on tv.
I've tried booting from microSD with and without reset button pressed, but nothing.
Tried connecting to computer, but doesn't find it.
Tried shorting pins on nand chip, but couldn't find the right pins. Chip has THGBMFG8C4LBAIR on it and can't find datasheet.
Board is Green, with XJH-V99-V00 2018-03-31.

Here is the Boot log from Serial monitor:

GXM:BL1:dc8b51:76f1a5;FEAT:ADFC318C:80;POC:3;RCY:0 ;EMMC:0;READ:0;0.0;CHK:0;
TE: 86276

BL2 Built : 18:50:13, Sep 22 2017.
gxl g4786fda-dirty - jiaxing.ye@droid12

set vdd cpu_a to 1120 mv
set vdd cpu_b to 1050 mv
set vddee to 1000 mv
Board ID = 3
CPU clk: 1200MHz
DQS-corr enabled
DDR scramble disabled
STICKY_REG0: 0x00000000
STICKY_REG8: 0x00000000
STICKY_REG9: 0x00000000
LPDDR3 chl: Rank0+1 @ 720MHz
ddr_lpddr3_only_up_odt_enable: 0x00000001....
Training PGSR0: 0x80001fbf....
ddr_training_inf: rank: 0 org_wr0 w0_l w0_r org_r0 r0_l r0_r org_wr1 w1_l w1_r org_r1 r1_l r1_r org_wr2 w2_l w2_r org_r2 r2_l r2_r org_wr3 w3_l w3_r org_r3 r3_l r3_r
af_vrefddr_training_win: rank: 0 21 00 45 3d 18 63 17 00 31 44 1c 6e 20 00 41 3c 15 65 1f 00 40 3b 13 64 674 rank: 1 22 00 45 3d 18 63 17 00 31 45 1c 6e 20 00 41 3d 15 65 1f 00 40 3b 13 64 674
bist_test rank: 0 20 12 2f 40 2c 54 19 03 2f 42 2c 59 24 10 39 3d 2a 50 20 0a 37 3a 23 52 674 rank: 1 1f 10 2f 3e 2b 52 19 03 2f 43 2e 59 22 0d 37 3c 2a 4f 21 0a 39 3a 23 51 674 bist_size0x 000007e0 bist_cost_time 350986 us bist test no threshold setting:
ddr_refi_counter37
DDR1_ADDRMAP_0== 0x14941cc5
DDR1_ADDRMAP_1== 0x230783ab
DDR1_ADDRMAP_2== 0x2f6ad272
DDR1_ADDRMAP_3== 0x3bcdeb38
DDR1_ADDRMAP_4== 0x0007359e

Rank0: 2048MB-2T-3

Rank1: 1024MB-2T-3
DataBus test pass!
AddrBus test pass!
-s
Load fip header from eMMC, src: 0x0000c200, des: 0x01400000, size: 0x00004000
New fip structure!
Load bl30 from eMMC, src: 0x00010200, des: 0x01100000, size: 0x0000d600
Load bl31 from eMMC, src: 0x00020200, des: 0x05100000, size: 0x0002c600
Load bl33 from eMMC, src: 0x00050200, des: 0x01000000, size: 0x00065a00
NOTICE: BL3-1: v1.0(release):a625749
NOTICE: BL3-12: Built : 11:25:15, Aug 25 2017
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=0x82
wdt: reset registers!
89 d9 d8 0 ce 6f af 8e 21 97 61 76 [0.734996 Inits done]
secure task start!
high task start!
low task start!
ERROR: Error initializing runtime service opteed_fast


U-Boot 2015.01 (Dec 26 2017 - 15:03:06)

DRAM: 3 GiB
Relocation Offset is: b6eb4000
12345678
10112281101!
initcall sequence 00000000b7f5b818 failed at call 0000000001009120 (err=-1)
### ERROR ### Please RESET the board ###

Looks good to me... nothing wrong with your bootloader. You need to find an LPDDR3 firmware for your box.

I assume you need to mask rom reset to start with USB burn tool. You prolly can use the ST Card burn tool to flash without opening your box.

[MrJCub]

Thanks for your reply.

I've got two firmwares I'd like to try, but can't get it to recognise the micro sd card or a computer.

With the sd card, I formatted as FAT32, and loaded the Uboot and firmware file plus ini file with USB burn tool (various versions). Holding the reset button in the av port and then putting power onto the unit, but nothing...
Alternatively, I tried shorting each pin that are beside each other on the NAND while power is on and the computer didn't connect. I used this same usb-usb cable to flash it the first time.

Do I need to short the nand and then apply power? I can't figure out which two pins are correct. There are about 3 pairs that when shorted cause the blue led to turn off... Does the correct pair cause the led to turn off?

[X92-2GB]

From what it looks on your boot loader, it should see the SD card without reset. Just insert the card and power on the box. The display should show progress.

It is also possible you have a hardware issue. Could have blown one of the power sections to drive memory, or USB data bus.

[MrJCub]

From what it looks on your boot loader, it should see the SD card without reset. Just insert the card and power on the box. The display should show progress.

It is also possible you have a hardware issue. Could have blown one of the power sections to drive memory, or USB data bus.

Thanks X92-2GB.

Do you know how to test if that part of power is working?

[X92-2GB]

If you know a little about electronics, the larger ceramic capacitors will have a voltage for the output section. You should see 0.95v, 1.2v, 1.5v, 1.9v, 3.3v, and 5.0v at various locations on front and back sides of the main board.

If missing any of the above voltages, you will have a hardware fault. Most likely 3.3v may be missing in a critical location to drive SD card bus, and USB hub with the port for flashing.

You can test USB port voltagd by reading 5v voltage at pin 1, or installing a USB SD card reader with LED, it should light up when box has power.

Some boxes have two sections for 5v power sources. One is shared by power plug and the other has its own driving circuit to enable critical sections. So testing all USB ports is needed to verify that 5v circuits are functioning.

[MrJCub]

Thanks X92-2GB,
I'll do some testing and report back.
Wondering if testing that there was power at the serial connection would indicate anything. I assume there should be 3.3v feeding there.
I did notice that sometimes when I disconnected the main power that the blue led would stay on, being powered by the usb of the computer, but I guess that doesn't indicate if 5v circuit is actually working.

[X92-2GB]

Thanks X92-2GB,
I'll do some testing and report back.
Wondering if testing that there was power at the serial connection would indicate anything. I assume there should be 3.3v feeding there.
I did notice that sometimes when I disconnected the main power that the blue led would stay on, being powered by the usb of the computer, but I guess that doesn't indicate if 5v circuit is actually working.

There is a main 5v circuit that drives 3.3v, and other voltages. I discover on one box that the power plug only powered half of the circuit, and was able to add a 2A charger connection to the side that did not have the 5v power circuit active. Thus able to power the sub voltage circuits to allow boot. I had 4 USB ports, so once I added the charger to one of the dead USB connections along with the power plug installed the board was able to flash, and boot.

[MrJCub]

There is a main 5v circuit that drives 3.3v, and other voltages. I discover on one box that the power plug only powered half of the circuit, and was able to add a 2A charger connection to the side that did not have the 5v power circuit active. Thus able to power the sub voltage circuits to allow boot. I had 4 USB ports, so once I added the charger to one of the dead USB connections along with the power plug installed the board was able to flash, and boot.

Great, thanks for the extra information!

[MrJCub]

If you know a little about electronics, the larger ceramic capacitors will have a voltage for the output section. You should see 0.95v, 1.2v, 1.5v, 1.9v, 3.3v, and 5.0v at various locations on front and back sides of the main board.

If missing any of the above voltages, you will have a hardware fault. Most likely 3.3v may be missing in a critical location to drive SD card bus, and USB hub with the port for flashing.

You can test USB port voltagd by reading 5v voltage at pin 1, or installing a USB SD card reader with LED, it should light up when box has power.

Some boxes have two sections for 5v power sources. One is shared by power plug and the other has its own driving circuit to enable critical sections. So testing all USB ports is needed to verify that 5v circuits are functioning.

I did some testing last night.
Had 3.3v at the serial connection, 1.2v at various points, but couldn't really figure out where I should be checking.
The USB seemed to be missing 5v, so I added a power supply to that, but the boot log showed exactly the same...

[vladakru]

Hi.
i have this mesage from uart
GXL:BL1:9ac50e:bb16dc;FEAT:BDFC31BC:0;POC:3;RCY:0; EMMC:0;READ:0;CHK:A7;READ:0;CHK:A7;READ:0;CHK:A7;S D:800;USB:8;
LOOP:1;EMMC:0;READ:0;CHK:A7;READ:0;CHK:A7;READ:0;C HK:A7;SD:800;USB:8;
LOOP:2;EMMC:0;READ:0;CHK:A7;READ:0;CHK:A7;READ:0;C HK:A7;SD:800;USB:8;
LOOP:3.........

i see that is BL1 - This is the Boot Loader stage 1 is not on the eMMC.

i can't boot from sd card at all
i have problem with this

Step 2:

Windows
Use Amlogic Bootcard Maker to write aml_sdc_burn.UBOOT to the sdcard.

Bootcard Maker only worl with .bin files extension...
i make boot sd card with Burn Card maker and various roms...
I had no success

still same message from uart and no signal from HDMI..

What do you recommend

[blust0ne]

Thanks, I can recover my dead h96max x2 by refering to this thread.

My h96max x2 is android 9, s905x2 and 4G LPDDR3 ( g12a_u212_4g, not u211 device) .

With the firmware from " https://forum.xda-developers.com/and...b-4gb-t4003395 ",

mine has dead loop on BL2 stage , DDR init process.
It is not possible to use usb burning tool method.

serial console says when failed :

LPDDR3 probe
ddr clk to 600MHz
Load ddrfw from eMMC, src: 0x000101ff, des: 0xfffd0000, size: 0xffffff, part: 0
sd/emmc cmd 18 arg 0x00000180 status 01ff3000 pinmux0 11111111 pinmux1 00100101 ds_reg0 ffffffff
sdio read data fail


I can bypass eMMC boot process and recovered from sdcard.

serial console says:

G12A:BL:0253b8:61aa2d;FEAT:E0F83180:2000;POC:F;RCY :0;EMMC:0;READ:800;READ:800;READ:800;SD?:0;SD:0;READ: 0;0.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

------



I attach the log file for reference.

[ph086]

If your box is really bricked then if you connect via serial console to it you will only see the following looping:
.

Hi calc.

So i follower your steps and was able to flash my box but im still stuck on the logo screen
Amlogic S905w 2Gb 16Gb rom

Full log https://pastebin.com/Lxk6gq7N

GXL:BL1:9ac50e:bb16dc;FEAT:ADFC318C:0;POC:3?RCY:0; EMMC:800;NAND:0;READ:0;0.0;CHK:0;
TE:?2472

BLr Buift : 11:04:41, Jan 26 2018.
gxl g034bs2c - xingyu.chen@droid12-sz

set vcck to 1120 mv
set vddee to 1000 mv
Board ID = 1
JDQSZ?orr enabled
DDR scramble enabled
DDR3 chl: ank0 16bat @ 720MHz

?ist_?est`rank:?0 2c 01 57 34 0c ed 31 07 5c 36 0d 5f 34 34 34 35 35 35 34 34 34 34 34 34 637
Rank0: 2048MB-2?-11
AdDrBus test passA
?AND init
Load fip hea?%r?f?om NAND, src: 0x0000c000, des: 0x01400000, size: 0x00004000
New fip?stpucture!
Load bl30 from NAND, src: 0x00010000, des: 0x0LLL&??b????0x0000d&0`
Lo?d bh31 fro? ?P?? src: 0x00020000, des: 0x05100000, size: 0x0002#600
Load bl33 from NAND, src: 0x00050000, des: 0x01000000, size: 0x00067200
NOTICE: BL3-1: v1.0(release):35dd647
NOTICE:" BL3[1: Bwilt :"15:20:30, Feb 7 2018
[BL31]: GXL CPU setup!
NOTICEz BL31: BL33 decompress pass
mpu_config_enable:ok
[Ymage: gxl_v1.1.3108-b30529c-dirty 2018-05-28 19:44:;9]
OhS=0xc4
21 0d c4 00 b6 b1 a3 f8 49 9d f4 a8 7d 17 fc 3e
[0.355286 Inits done]
secure(task start!
high task"svqr?!
low task start!
ERROR: Error initializing r?ntime service optaed_fawt


U-Boot 2015.03 (Sep 07 : 9( Y 16:46:33)

DRAM: 2 GiB
Relocation Offset is: 76eb0000
======-========{20180907k=====================
register usb cfg[0][1] = 0000000077f59ae0
[CANVAS]canvqw init
boo|_?ev?ce_fl?gP: 1
Nand PHY Ver:1.01.001.0006 (c) 2013 AmlogaC Inc.
init@bus_cy?le=6, bus_timing=7, system=5.0ns
LAND devIce id: 2c 84 64 54 a9 0 0 0
detect NAND device: B revision L95B NAND 16GiB MT29F128G08CBECB
param data[3"v43]: 53l 50, 45, 43,54, 45
nand Manufacturer: specteck

bus_c=6,?us_t=7,sys=4.0ns,T_REA=16,T_RHOH=15
new oob mode
show_phydev_list
0: .fb?ot
detect new ?and here and new_type:50
NAND CKECK:arg nbbt: valid=1, blk=9, page=0
NAND CKECK:arg fbbt: valid=1, flk=3, page=0
out?-YY$?????????????????jR?????dtb on nand
amlnf_dtb_init_partitions: probe.
NAND CKECK:arg ndtb: valid=1, blk=6, page=17
dtb magic 5f4c4d41
Amlogic multi-dtb tool
Multi dtb detgcted
Multi dtb tool version: v2 .
Support 2 ?t?.?"
??}????? gxl platform: ?212 6ariant: 2g
dtb 0 soc: gxl plat: p212 vari: 1g
dtb 1 soc: gxl plat: p212 v?ri: 2g
Find match(dtb: 1
start dts,buffer=0000000073ed6300,dt_addr=0000000073ee13 00
Amlogic multi-dtb t?ol
Mu?ti d|b detected
Multi dtb tool version: v2 .
Support 2 dtbs.
aml_dt soc:?gxl platvorm: q212 variant: rg
dtb 0 soc: gxl plat: p212 vari: 1g
dtb 0 soc: gxl plat: p212 vari: 2g
@ Find match dtb: 1
parts: 10
00: logo 0000000002000000 1
01: recovery 000000002000000 1
02:@ rsv 0000000000800000 1
03: tee 0000000000800000 1
04: crypt 000000002 00002 1
05: misc 0000000002000000 1
06: boot 0000000002000000 1
07z system \6????????????j
08: cache 0000000020000000 2
09r Data ffffffffffffffff 4
cache !!!
NAND CKECK:arg ncnf: valid=1, blk=4, page=0
aml_key_init probe.
N?NL CKECK:arg nkey: valid=1, blk=2, page=17
NAND KKE?K:?rg 0hy?: valid=1, blk=5, page=1d=1, bl?=7, page=5
amlnand_phydev_ini?,1429,phydev->offset=0,phyd?6->?-?V???????j)aml?and?rhydev_i?it,1429,phydev->offset=19000000,phydev->size=2a000000
amlnand_phydev_init,1429,phydev->ofgsut=43000000,Phyf%V->?ize=9e000000
amlnand_phydev_init,1429,phydev->offset=?1000000,ph}dev->{ize=3f000000
nfboot : 0x00000`000820Z0x000001000000 :partn=0:single_chip single_plane
nfcache : 0x000019000000-0x00002a000000 :partn51:sifgle_ch?p melti_plane
nfcode : 0x000043000000-0x00009e000`00 :partnO'????1?}???????}???5?n?data : 0x0000e120020-0x00031f000000 :partn=1:single_chip multi_plane
amlnf_logic_init() start
(nfcache), size:2a000000
nftl vebsion 1.01.002
Nov 18 2016, fix logic partition calculation
size_in_blk 42; total_bloc+ 41;
get the ph}_dev_skze=20000000H tmp_off_size=100000H phy_dev_block=21Hnftl start:size_in_blk=41,free_block_num=8-blks(37), total_blocks(33)
this part not enough bre% block 37@, 33!%
create_part_list fail!
aml_nftl_initialize: fail
(nfcode), sizet9e000000
nftl version 1.01.002
Nov 18 2216< vix logic partition calculation
get the phy_dev_size=8b000000H tmp_off_size=458000H phy_dev[block=:?Hnftl star42size_in_blk=158,free_block_num=18-blks(1e39. totql_blk??140)
MMC: aml_p?iv->desc_b?f = 2x0000000073f05c90
aml_priv->desc_bu? = 0x0000000073f07f30
SDIO Port B: 0, SDIO Port C: 1
uboot env amlnf_env_read : ####
In: serial
Out: serian
Grr: serial
rebootmode=cold_boot
[stor?]Torun cmt[aihnf dtb_zucd 0x1000000 0x40000]
cmd dtb_read:
amlnf_dtb_read: ####
262144 bytes dtd_read : OK
Amlogic }ulti-dtbtool
Multi dtb detected
Multi dtb tool version: v2 .
Support 2 dtbs.
$ aml_dp soc:$gxn platform: p212 variant: 2g
dtb 0 soc: gxl plat: p212 vari: 1g
d?b 1 s?c: gxl plat: p216 vari8 2g
Find match dtb: 1
vpu: clk_level in dts: 7
vpu: set clk: 666667000Hz, r?adback: v6664002 R????0)
vpu: vpu_clk_gate_init_off
*hpd_state=1t
[1000?0hz] is invalid for cvbs.
set hdmivx VIC = 16
config HPLL = 2970000
aonfig HPLL done
j = 4 vid_clk_div = 1
hdmitx: set`enc &or@VIC: 16
HDMITX-DWC addr=0x14004006 rd_data=?x40M
Errmr: ?DMITX-DWC exp_data=0xff mask=0x9f
rx version i? 1.h or below@ div=10
hdmtix: set aud
?dmitX phy setting done
Net: dwmac.c9410000amlkey_init() enter!
[EFUSE_MSG]keynum is 8
[BL31]: tee size: 0

Start r?ad mi3c ?artitaon datas!
info->attemp_times = 0
info->active_slot = 0
info->slot_info[p].bootable = 1
info->slot_info[0].online = 1
info->slot_info[1].bootable = 0
info->slot_info[1].online = 0
info->at?emp_times = 0
attemp_times = 0
active slot = 0
wipe_rata=suc?essful
wipe_cacheO??????5)u?grade_step=2
?OSD],oad fb addr from dts
[OSD]fb_addr for logo: 0x7f851000
[OSD]load fb addr from dts
[OSD]fb_!dd? fK?b???? 0|7f851000
[CANVAS]addr=0x7f851000 width=3840, height=2160
amlkey_init() enter!
amlkey_init() 71: already init!
[EFUSE_MSG]keynum is 8
[BL31]: vee sizg: 0
[KM]Error:f[key_manage_queryOsiz?]L507:key[usid] not programed ?et
[
M]Error:f[key_manage_query_size]L507:key[mac] not programed yet
[KM]Error:f[key_manage_query_size]L507:key[deviceid] not progvam?t yet
detect sadckey ....
saradc - saradc sub-system

Usage:
saradc saradc opan <channel> - open a SARALC c?a?ne,
saradc close - close the SARADC
saradc getval - get the value in current channel
saradc test - test t?eSARADC by channel-7
saradc get_in_range <min> <max> - return 0 if current va?u? in the range of c?rrent channel

g?io: qin GPIOAO_2 (gpio 102) value is 1
InUsbBurn
noSof
?it Enter or space or Ctrl+S ke} to stop autoboot -- : 0
Booting...
Unknown command 'unifykey' - try 'help'
ee_gate_off ...?'unifykey'P-0tby?'help'
## Booting Android Imige at 0x010800 0!&..
reloc_addr =7408fdd0
copy don?
Oer?el"commAnd line: buildvariant=user
load dtb from 0x1000000 ......
Amlogic multi-dtb tool
Single dtb ?e?ectedC1R ????????????Kernel Image ... OK
kernel loaded at 0x41080000\ ?nd =$0x021dd2f0
Loading Ramdisk to 73d09000, end 73e9?f4c ... OK
fdt_instaboot: no instaboot@image01fff2000, end 000000001ffffdd0 ... OK

tarting kernel ...

[Kamengc]

Hi Calc: bootcardmaker only takes bin file, what do you mean by aml_sdc_burn.UBOOT???

[navo]

hello, i have x96max 4/64 neither lights up nor the power supply of usb readers or optical port. does it still make sense to come to life? thank you very much, I would also try to connect via a serial console but I'm afraid I would need more advice there. Thank you very much

Odoslané z MI 8 Pro pomocou Tapatalku