Bricked Beelink GT1 standard S912 2/16, can't boot to CE from SD card, have UART log

Help & Support Recovery
41

I found what was wrong.
Have the USB-TTL adapter that is a little bit complicated so I searched online and found that have to turn some switch to other position to have RX TX fully working.

So I run the command you give me and here is the log:

CoreELEC:~ # [BL31]: tee size: 0
[BL31]: tee size: 0
dmesg | grep mmcblk
[ 2.596576@0] mmcblk0: emmc:0001 NCard 14.4 GiB
[ 2.601078@0] mmcblk0boot0: emmc:0001 NCard partition 1 4.00 MiB
[ 2.607077@0] mmcblk0boot1: emmc:0001 NCard partition 2 4.00 MiB
[ 2.613131@0] mmcblk0rpmb: emmc:0001 NCard partition 3 4.00 MiB
[ 2.633242@1] mmcblk0: unknown partition table
[ 2.673317@0] [mmcblk0p01] bootloader offset 0x000000000000, size 0x000000400000
[ 2.681933@0] [mmcblk0p02] reserved offset 0x000002400000, size 0x000004000000
[ 2.690000@0] [mmcblk0p03] cache offset 0x000006c00000, size 0x000020000000
[ 2.698444@0] [mmcblk0p04] env offset 0x000027400000, size 0x000000800000
[ 2.706715@0] [mmcblk0p05] logo offset 0x000028400000, size 0x000002000000
[ 2.715178@0] [mmcblk0p06] recovery offset 0x00002ac00000, size 0x000002000000
[ 2.747101@0] [mmcblk0p07] rsv offset 0x00002d400000, size 0x000000800000
[ 2.755555@0] [mmcblk0p08] tee offset 0x00002e400000, size 0x000000800000
[ 2.763899@0] [mmcblk0p09] crypt offset 0x00002f400000, size 0x000002000000
[ 2.784501@0] [mmcblk0p10] misc offset 0x000031c00000, size 0x000002000000
[ 2.793084@0] [mmcblk0p11] boot offset 0x000034400000, size 0x000002000000
[ 2.801964@0] [mmcblk0p12] system offset 0x000036c00000, size 0x000080000000
[ 2.810250@0] [mmcblk0p13] data offset 0x0000b7400000, size 0x0002e5c00000
[ 2.922739@1] mmcblk0boot1: unknown partition table
[ 2.956551@3] mmcblk0boot0: unknown partition table
[ 3.156114@3] mmcblk1: sd:1234 SA01G 972 MiB
[ 3.161716@3] mmcblk1: p1 p2
[ 6.890974@3] EXT4-fs (mmcblk1p2): couldn’t mount as ext3 due to feature incompatibilities
[ 6.891939@3] EXT4-fs (mmcblk1p2): couldn’t mount as ext2 due to feature incompatibilities
[ 6.902186@1] EXT4-fs (mmcblk1p2): mounted filesystem with ordered data mode. Opts: (null)
CoreELEC:~ #

42

I knew it you get it working :wink:

Enter this at CE console booted from SD/USB and wait till finished:

mke2fs -F -L "data" -t ext4 -m 0 "/dev/mmcblk0" -O uninit_bg,quota,^64bit,^metadata_csum -E offset=3074424832 11868m; sync

It will format the data partition completely!
After format you can try to boot Android again. Maybe your error is gone after format the data partition. Remember: all data on this partition is lost!

43

Yea, I know it too :slight_smile:
So, I entered the code, here is the log:

CoreELEC:~ # [BL31]: tee size: 0
[BL31]: tee size: 0
mke2fs -F -L “data” -t ext4 -m 0 “/dev/mmcblk0” -O uninit_bg,quota,
^64bit,^metadata_csum -E offset=3074424832 11868m; sync
mke2fs 1.43.9 (8-Feb-2018)
Discarding device blocks: done
Creating filesystem with 3038208 4k blocks and 760368 inodes
Filesystem UUID: cb7744c4-337d-4713-a629-c9f4f37ea334
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208

Allocating group tables: done
Writing inode tables: done
Creating journal (16384 blocks): done
Writing superblocks and filesystem accounting information: done

CoreELEC:~ #

After I tried to boot to Android but without luck, stuck in Beelink logo. End of the log:

[ 3.447431@2] 3e40: ffffffed 00000000 023464b0 ffffffc0 00000000 00000000 761bc000 00000000
[ 3.455831@2] 3e60: 021281a0 ffffffc0 29aaaaab 00000000 25c17d03 00000002 00000000 00000000
[ 3.464231@2] 3e80: 00000018 00000000 627d3d80 ffffffc0 00000400 00000000 00000400 00000000
[ 3.472631@2] 3ea0: 0000001a 00000000 00000013 00000000 0000000e 00000000 00000007 00000000
[ 3.481031@2] 3ec0: 00000001 00000000 0000000e 00000000 00000007 00000000 627d0000 ffffffc0
[ 3.489432@2] 3ee0: 627d0000 ffffffc0 022cbb58 ffffffc0 01b84000 ffffffc0 02236000 ffffffc0
[ 3.497831@2] 3f00: 022356bd ffffffc0 01e2e510 ffffffc0 00000001 00000000 01080210 ffffffc0
[ 3.506231@2] 3f20: 00000000 00000040 627d3f60 ffffffc0 01085878 ffffffc0 627d3f60 ffffffc0
[ 3.514629@2] [] el1_irq+0x60/0xd0
[ 3.519617@2] [] cpu_startup_entry+0x1d8/0x224
[ 3.525655@2] [] secondary_start_kernel+0x118/0x128

Tried again with CE from sd card, the same, just CE splash screen…

44

Do a recovery by the recovery SD again.
When recovery is finished wait till Android hopefully boot. The data partition will be managed/repaired on first boot of Android.

45

On Beelink site they give me stock image and I flashed it successfully.
When booting everything is the same, stuck on Beelink splash screen…

46

I tried Armbian also.
Made SD card and booted.
In Putty (terminal emulator) window everything is normal, managed to log in,
but on tv picture stayed at login screen and won’t go further but the clock on the top goes normally.
Very strange.

Capture

20190908_125308
20190908_1253082851×2138 1.58 MB

47

Not really, you opened a shell session.
To login via the GUI, connect a keyboard + mouse and login using the UI.

48

I tried that but cursor is not moving.
I cannot type anything with keyboard or move mouse.
Tried wired/wireless keyboard and mouse but nothing works. Tried both USB ports.

49

So, I tried CE, LE, Armbian (various versions), situation is the same.
Can login using shell but GUI not working.
What could be the problem, hardware or software?
What else can I try?

50

This could be that you have corrupted eMMC. But even if it is, I guess it should be shown in the logs and devs here would have seen it.

51

That wouldn’t account for an inability to boot from SD.

Shoog

1 Like
52

That’s right, my brothers box had corrupted eMMC, chip was removed from the board and CE running from SD card flawlessly about a year.

53

Found online that my box with S912 chip and 2G/1Gbit wlan need gxm_q201_2g_1gbit.dtb to boot (or some q201 variants), but it won’t, it boot only with gxl_p212.dtb (to splash screen).:thinking:

54

I have a GT1 standard (not ultimate) with serial starting with A912 and the dtb is gxm_q201_2g_1gbit.dtb.

55

Try replacing the power adapter.
If possible, use class-10 SD cards, but do not use slow 972MiB cards. gxm_q201_2g would be the right file for you.

56

Power adapter is ok, tried it with another working box and it’s good, also tried with adapter from that working box.
Have another class10 8GB sd card, will try with that.

57

Made new SD card with CE and try ALL 67 dtb files from device_trees folder (heavy job)
but it’s the same, boot only with gxl_p212_2G.dtb (and some other gxl_p212 variants) just to splash screen.

58

You can’t use a S905X DTB for a S912 SoC.

59

I know but it won’t boot with dtb for S912…
Just with this dtb it shows some sign of life.

60

Your UART logs show kernel panic. This is due to incompatible DTB.
Can you post a UART log with a correct DTB?