Libreelec for rk3328

[ukmark62]

Thanks mo123 - which image could I use for the MX10?

[mo123]

Seems you can use the same image.
But you need to read the OP and change your dtb if it is not correct, since your are using the trn9 dtb and not mx10 which is completely different hardware.

[ukmark62]

I am currently using the mx10 dtb and the image provided by balbes150 (afaik his image is the only one that will backup from and install to emmc). His image is suffixed by trn9 but the default dtb provided in the image and referenced in extlinux.conf is mx10

[ukmark62]

Tried again, this time building SD card with LibreELEC SD Creator, but get exact same errors as before when trying to backup eMMC.

[balbes150]

I'm trying to run the "Full backup eMMC" on a RK3328 MX10 box running Android 8.1. When it runs, the machine shuts down very quickly. The backup file created in /storage/ddbr/ is only 20 bytes! So, I ran the command "ddbr-backup.sh" via SSH and this is what I received in the terminal. I'm running the LibreELEC-RK3328.arm-9.1-devel-20190329134952-ba744c2-box-trn9.img version:-

/dev/mmcblk0p1 /flash vfat ro,noatime,fmask=0022,dmask=0022,codepage=437,ioch arset=ascii,shortname=mixed,errors=remount-ro 0 0
dd: can't open '/dev/mmcblk1': No such file or directory
Done! Full backup completed.

When I run "blkid" on SSH, I get:-

/dev/loop0: TYPE="squashfs"
/dev/mmcblk0: PTUUID="ec4be8db" PTTYPE="dos"
/dev/mmcblk0p1: SEC_TYPE="msdos" LABEL="LIBREELEC" UUID="2903-1041" TYPE="vfat" PARTUUID="ec4be8db-01"
/dev/mmcblk0p2: LABEL="STORAGE" UUID="10fdf249-fc4f-4206-a17a-e655ede8c0ce" TYPE="ext4" PARTUUID="ec4be8db-02"
/dev/sda1: LABEL="2TB_MOVIES" UUID="6C32F1F532F1C45C" TYPE="ntfs" PTTYPE="atari" PARTUUID="abcaa71b-01"

The device is running stock firmware that has not been updated. The 32 gb micro sd card was built using Rufus-3.5.

Any ideas?

Thanks!

In your log there is no message about the presence of eMMC. Perhaps you have a NAND or a clone MX10 with its settings in DTB for working eMMC. Open the case and check the memory type (chip brand) and compare with the MX10 theme.

[ukmark62]

I've taken a couple of pics of the board inside (top and bottom). I can't make out any brand name of the memory etc:- Do these help?? Thanks!

[ukmark62]

If I run "df -h" on SSH I get following:-

Filesystem Size Used Available Use% Mounted on
devtmpfs 1.9G 124.8M 1.8G 6% /dev
/dev/mmcblk0p1 511.7M 149.7M 362.0M 29% /flash
/dev/mmcblk0p2 28.3G 1.5M 28.3G 0% /storage
/dev/loop0 125.0M 125.0M 0 100% /
tmpfs 1.9G 0 1.9G 0% /dev/shm
tmpfs 1.9G 8.8M 1.9G 0% /run
tmpfs 1.9G 0 1.9G 0% /sys/fs/cgroup
tmpfs 1.9G 2.6M 1.9G 0% /var
tmpfs 1.9G 0 1.9G 0% /tmp


I bought the MX10 from geekbuying.com, This is the link:- https://www.geekbuying.com/item/MX10...ox-386668.html
The only difference between mine and this is that this one runs Android 9.0, mine runs 8.1

[ukmark62]

I upgraded my MX10 to Android 9.0 - all works fine in android.

Backup eMMC still fails as before - this time, "blkid" shows this ??!!:-

LibreELEC:~ # blkid
/dev/loop0: TYPE="squashfs"
/dev/mmcblk0: PTUUID="ec4be8db" PTTYPE="dos"
/dev/mmcblk0p1: SEC_TYPE="msdos" LABEL="LIBREELEC" UUID="2903-1041" TYPE="vfat" PARTUUID="ec4be8db-01"
/dev/mmcblk0p2: LABEL="STORAGE" UUID="10fdf249-fc4f-4206-a17a-e655ede8c0ce" TYPE="ext4" PARTUUID="ec4be8db-02"
/dev/mmcblk2: PTUUID="b3770000-0000-4a02-8000-631d00000b1f" PTTYPE="gpt"
/dev/mmcblk2p1: PARTLABEL="uboot" PARTUUID="f06a0000-0000-482e-8000-2dcf00001ecc"
/dev/mmcblk2p2: PARTLABEL="trust" PARTUUID="0d7e0000-0000-4c23-8000-4a9d0000000a"
/dev/mmcblk2p3: PARTLABEL="misc" PARTUUID="743f0000-0000-4e58-8000-64ee000055c0"
/dev/mmcblk2p4: PARTLABEL="baseparameter" PARTUUID="8b6f0000-0000-4638-8000-572b000037d6"
/dev/mmcblk2p5: PARTLABEL="resource" PARTUUID="bc000000-0000-4c22-8000-36ba00003133"
/dev/mmcblk2p6: PARTLABEL="kernel" PARTUUID="6e1d0000-0000-4869-8000-4704000043c1"
/dev/mmcblk2p7: PARTLABEL="dtb" PARTUUID="08200000-0000-4255-8000-027100006167"
/dev/mmcblk2p8: PARTLABEL="dtbo" PARTUUID="f41c0000-0000-4320-8000-156a0000730d"
/dev/mmcblk2p9: PARTLABEL="logo" PARTUUID="99550000-0000-4178-8000-62550000559b"
/dev/mmcblk2p10: PARTLABEL="vbmeta" PARTUUID="5f420000-0000-4503-8000-7e9b000058fa"
/dev/mmcblk2p11: PARTLABEL="boot" PARTUUID="ae110000-0000-4855-8000-34a500003e10"
/dev/mmcblk2p12: PARTLABEL="recovery" PARTUUID="ee220000-0000-407b-8000-7fda000041c6"
/dev/mmcblk2p13: PARTLABEL="backup" PARTUUID="870a0000-0000-4773-8000-13a100000c05"
/dev/mmcblk2p14: UUID="a7decaff-774f-40a5-b63f-b376408071e0" TYPE="ext4" PARTLABEL="cache" PARTUUID="e2110000-0000-4431-8000-536400003fb3"
/dev/mmcblk2p15: LABEL="/" UUID="193f8966-3b63-4a60-9a85-b74041265e46" TYPE="ext4" PARTLABEL="system" PARTUUID="af01642c-9b84-11e8-9b2a-234eb5e198a0"
/dev/mmcblk2p16: UUID="21f728be-f7b3-4c0d-90d5-fb2884c52f0c" TYPE="ext4" PARTLABEL="metadata" PARTUUID="79220000-0000-4f0c-8000-787b00002200"
/dev/mmcblk2p17: LABEL="vendor" UUID="1f85c541-405b-4806-8e94-692ddb823b64" TYPE="ext4" PARTLABEL="vendor" PARTUUID="87420000-0000-4e54-8000-2a9e0000566f"
/dev/mmcblk2p18: LABEL="oem" UUID="e4a40ee1-c9f5-4b88-917d-a35e06939f75" TYPE="ext4" PARTLABEL="oem" PARTUUID="f52b0000-0000-4335-8000-285d00007bed"
/dev/mmcblk2p19: PARTLABEL="frp" PARTUUID="2c290000-0000-4667-8000-5b1f00007464"
/dev/mmcblk2p20: PARTLABEL="security" PARTUUID="953e0000-0000-4f15-8000-604d000019bb"
/dev/mmcblk2p21: UUID="b50f5b70-0a2f-46c4-85d0-289e9ef061ba" TYPE="f2fs" PARTLABEL="userdata" PARTUUID="971e0000-0000-465d-8000-0a4d000037da"


and "df -h" now shows:-

LibreELEC:~ # df -h
Filesystem Size Used Available Use% Mounted on
devtmpfs 1.9G 124.8M 1.8G 6% /dev
/dev/mmcblk0p1 511.7M 149.7M 362.0M 29% /flash
/dev/mmcblk0p2 28.3G 4.2M 28.3G 0% /storage
/dev/loop0 125.0M 125.0M 0 1 00% /
tmpfs 1.9G 0 1.9G 0% /dev/shm
tmpfs 1.9G 8.9M 1.9G 0% /run
tmpfs 1.9G 0 1.9G 0% /sys/fs/cgroup
tmpfs 1.9G 2.6M 1.9G 0% /var
tmpfs 1.9G 0 1.9G 0% /tmp
/dev/mmcblk2p16 11.5M 32.0K 11.0M 0% /var/media/mmcblk2p16-mmc-032GE4_0x501b4a6
/dev/mmcblk2p15 2.0G 1.7G 230.8M 88% /var/media/mmcblk2p15-mmc-032GE4_0x501b4a6
/dev/mmcblk2p17 186.0M 128.4M 53.7M 71% /var/media/vendor
/dev/mmcblk2p18 62.0M 3.0M 57.7M 5% /var/media/oem
/dev/mmcblk2p14 232.0M 248.0K 224.1M 0% /var/media/mmcblk2p14-mmc-032GE4_0x501b4a6
/dev/mmcblk2p21 25.6G 479.8M 25.1G 2% /var/media/mmcblk2p21-mmc-032GE4_0x501b4a6

[caliban_freak]

Guys can u help me out?? I ve got an H96 Max + Rk 3328 with Android 8 runing. I will to install Libreelec on that Box but i?m a newby. Do u have a Step by Step Tut for me? Thx for the Help

[balbes150]

Strange number distribution for eMMC.

/dev/mmcblk2:

[ukmark62]

Strange number distribution for eMMC.

/dev/mmcblk2:

Yeah - weird. All I did was upgrade using following image https://androidtvbox.eu/new-firmware...-soc-20190108/
Used android tool v2.59 to erase flash and then upgrade and did nothing else. All these entries appeared once I upgraded to Android 9.0

[Digit97]

hi bables150 can you help me please? I have an h96 max+ and my dream is install libre elec on it or debian, i have downloaded the generic rk 3328 image from libre elec site and the result is this
(picture)

I have tried also with your images but the result is the same or in some case i receive only black screen

i think thath i not understand something,there is a particulares steps?

An user suggest me to use the right dtb but i not found it. Thank you in advance for your work

[gefattern]

Hi , nice you found it , hope User "balbes150" can help you , good luck / gefattern

[Digit97]

i read perhaps in this forum that i need the dtb file and then rename it to dtb.img

if is this the only one problem,i have read that the dtb file is in the resource.img

The resource.img is in the firmware image. I need unpack the firmware file but with Android Tool i can't do it. Sorry for my english.

[mo123]

i read perhaps in this forum that i need the dtb file and then rename it to dtb.img

if is this the only one problem,i have read that the dtb file is in the resource.img

The resource.img is in the firmware image. I need unpack the firmware file but with Android Tool i can't do it. Sorry for my english.

Android and Linux dtb images are 2 completely different things.
You can compare them to fix basic things like wifi, ethernet etc. only,
Also with the new Linux 5.x mainline kernel support being merged next week, all these no name devices' 4.4 dtb files won't work anymore without some serious changes or until Android Q comes out with 5.x kernel support.

[Digit97]

i understood few things.

with the android Q image can i do anything?

[mo123]

No, since it will also be different than a Linux dtb file but at least based on the same kernel version more or less.
But you can compare an existing Linux dtb file for a device with your Android one to see what GPIO pin changes need to be done to get things like wifi, bluetooth, ethernet, power on, hdmi, usb ports, ir remotes etc. working and do the changes to an existing Linux dts file.
If you get a device with mainline Linux kernel support, you device will always be supported.
If you can get your device booting with Armbian Linux, then you can use most of the dts/dtb file for LibreELEC too.

[Digit97]

ok thank you anyway