Mount internal eMMc

OK thanks for the reply, guess i will have to settle for sharing the storage to get around and be able to access the internal ROM…

@anon88919003 is there anyway I can remove that? I wanted to manually install into the eMMC, I don’t mind bricking the device while trying to do so, I can restore it through amlogic usb burning tool.

You can use ceemmc on newer devices, this is our new method for internal installs, please search the forums if you need further help with it.

Maybe this works on your Beelink GT1 (Amlogic S912) to access your data on the android partition. I have used this without problems before installing CoreELEC on the internal memory to access the android partition and accelerate timeshift on Kodi clients devices.

File: /storage/.config/autostart.sh
...
mkdir -p /tmp/internal-storage
mount -o ro /dev/data /tmp/internal-storage
...

Try this before on the SSH console. After this the android partition will be in /tmp/internal-storage

(I changed rw to ro so you don’t spoil the android partition)

I have a GT-King and /dev/data does not exist.
How can I reach the eMMC file system? I have 64GB available there that I would like to use.

Write the command

df -T

from SSH and show us the result.

The output is:

Filesystem           Type       1K-blocks      Used Available Use% Mounted on
devtmpfs             devtmpfs     1638944         4   1638940   0% /dev
/dev/mmcblk1p1       vfat          524008    205792    318216  39% /flash
/dev/loop0           squashfs      189952    189952         0 100% /
/dev/mmcblk1p2       ext4        29667193  13745779  15917318  46% /storage
tmpfs                tmpfs        1922228         0   1922228   0% /dev/shm
tmpfs                tmpfs        1922228      9276   1912952   0% /run
tmpfs                tmpfs        1922228         0   1922228   0% /sys/fs/cgroup
tmpfs                tmpfs        1922228      2228   1920000   0% /var
tmpfs                tmpfs        1922228         4   1922224   0% /tmp

Try now with the command

blkid

CoreELEC:~ # blkid
/dev/loop0: TYPE="squashfs"
/dev/system: LABEL="/" UUID="2e6c568e-1478-5a59-be01-62993f4a17fb" TYPE="ext4"
/dev/mmcblk1p1: SEC_TYPE="msdos" LABEL_FATBOOT="COREELEC" LABEL="COREELEC" UUID="2911-4504" TYPE="vfat" PARTUUID="211d02ae-01"
/dev/mmcblk1p2: LABEL="STORAGE" UUID="d64f1eca-7a63-4904-9030-3446e096b23b" TYPE="ext4" PARTUUID="211d02ae-02"
/dev/mmcblk1: PTUUID="211d02ae" PTTYPE="dos"

PS: Many thanks for your help troubleshooting this!

I also see this:

CoreELEC:~ # ls /dev/mmc*
/dev/mmcblk0       /dev/mmcblk0boot1  /dev/mmcblk1       /dev/mmcblk1p2
/dev/mmcblk0boot0  /dev/mmcblk0rpmb   /dev/mmcblk1p1

But this fails:

CoreELEC:~ # mount /dev/mmcblk0 /mnt
mount: mounting /dev/mmcblk0 on /mnt failed: No such file or directory

It seems that your internal memory is in /dev/system

Try to mount with

mkdir -p /storage/internal-storage
mount -o ro /dev/system /storage/internal-storage

and then look at the directory content /storage/internal-storage

I’m not sure if the internal memory is the /dev/system.
This is what I see:
It seems to have 2GB and not the ~64GB of GT-King

CoreELEC:~/internal # ls /storage/internal
acct                      etc                       odm
bin                       init                      oem
boot                      init.environ.rc           proc
bugreports                init.rc                   product
cache                     init.recovery.amlogic.rc  sbin
charger                   init.usb.configfs.rc      sdcard
config                    init.usb.rc               storage
d                         init.zygote32.rc          sys
data                      lost+found                system
default.prop              metadata                  ueventd.rc
dev                       mnt                       vendor
CoreELEC:~/internal # df -T
Filesystem           Type       1K-blocks      Used Available Use% Mounted on
devtmpfs             devtmpfs     1638944         4   1638940   0% /dev
/dev/mmcblk1p1       vfat          524008    205792    318216  39% /flash
/dev/loop0           squashfs      189952    189952         0 100% /
/dev/mmcblk1p2       ext4        29667193  13745780  15917317  46% /storage
tmpfs                tmpfs        1922228         0   1922228   0% /dev/shm
tmpfs                tmpfs        1922228      9276   1912952   0% /run
tmpfs                tmpfs        1922228         0   1922228   0% /sys/fs/cgroup
tmpfs                tmpfs        1922228      2228   1920000   0% /var
tmpfs                tmpfs        1922228         4   1922224   0% /tmp
/dev/system          ext4         2064208   1039724   1008100  51% /storage/internal

Yes, this is your internal memory. Go carefully and do not spoil anything! :rofl:

Look in

/storage/internal/storage
/storage/internal/sdcard
/storage/internal/data

Sorry but something is still off. I don’t see my things there. It should be a “Droid” file system and have ~64GB. I don’t see that data there.

I still can’t see nothing on those folders, only files on the mount root :frowning_face:

CoreELEC:~/internal/storage # ls -la /storage/internal/storage
total 8
drwxr-x--x    2 root     1028          4096 Dec 31  2008 .
drwxr-xr-x   20 root     root          4096 Dec 31  2008 ..

CoreELEC:~/internal/storage # ls -la /storage/internal/sdcard
lrw-r--r--    1 root     root            21 Dec 31  2008 /storage/internal/sdcard -> /storage/self/primary

CoreELEC:~/internal/storage # ls -la /storage/internal/data
total 8
drwxrwx--x    2 1000     1000          4096 Dec 31  2008 .
drwxr-xr-x   20 root     root          4096 Dec 31  2008 ..

CoreELEC:~/internal/storage # ls -la /storage/internal/emulated/0
ls: /storage/internal/emulated/0: No such file or directory

CoreELEC:~/internal/storage # ls -la /storage/internal
total 1629
drwxr-xr-x   20 root     root          4096 Dec 31  2008 .
drwxr-xr-x   19 root     root          1024 Dec  8 01:34 ..
drwxr-xr-x    2 root     root          4096 Dec 31  2008 acct
lrw-r--r--    1 root     root            11 Dec 31  2008 bin -> /system/bin
drwxr-xr-x    2 root     root          4096 Dec 31  2008 boot
lrw-r--r--    1 root     root            50 Dec 31  2008 bugreports -> /data/user_de/0/com.android.shell/files/bugreports
drwxrwx---    2 1000     2001          4096 Dec 31  2008 cache
lrw-r--r--    1 root     root            13 Dec 31  2008 charger -> /sbin/charger
dr-xr-xr-x    2 root     root          4096 Dec 31  2008 config
lrw-r--r--    1 root     root            17 Dec 31  2008 d -> /sys/kernel/debug
drwxrwx--x    2 1000     1000          4096 Dec 31  2008 data
lrw-------    1 root     root            23 Dec 31  2008 default.prop -> system/etc/prop.default
drwxr-xr-x    2 root     root          4096 Dec 31  2008 dev
lrw-r--r--    1 root     root            11 Dec 31  2008 etc -> /system/etc
-rwxr-x---    1 root     2000       1491944 Dec 31  2008 init
-rwxr-x---    1 root     2000          1064 Dec 31  2008 init.environ.rc
-rwxr-x---    1 root     2000         29580 Dec 31  2008 init.rc
-rwxr-x---    1 root     2000         14857 Dec 31  2008 init.recovery.amlogic.rc
-rwxr-x---    1 root     2000          7690 Dec 31  2008 init.usb.configfs.rc
-rwxr-x---    1 root     2000          5646 Dec 31  2008 init.usb.rc
-rwxr-x---    1 root     2000           511 Dec 31  2008 init.zygote32.rc
drwx------    2 root     root         16384 Dec 31  2008 lost+found
drwxr-xr-x    2 root     root          4096 Dec 31  2008 metadata
drwxr-xr-x    2 root     1000          4096 Dec 31  2008 mnt
drwxr-xr-x    2 root     root          4096 Dec 31  2008 odm
drwxr-xr-x    2 root     root          4096 Dec 31  2008 oem
drwxr-xr-x    2 root     root          4096 Dec 31  2008 proc
drwxr-xr-x    2 root     root          4096 Dec 31  2008 product
drwxr-x---    2 root     2000          4096 Dec 31  2008 sbin
lrw-r--r--    1 root     root            21 Dec 31  2008 sdcard -> /storage/self/primary
drwxr-x--x    2 root     1028          4096 Dec 31  2008 storage
drwxr-xr-x    2 root     root          4096 Dec 31  2008 sys
drwxr-xr-x   13 root     root          4096 Dec 31  2008 system
-rw-r--r--    1 root     root          5272 Dec 31  2008 ueventd.rc
drwxr-xr-x    2 root     2000          4096 Dec 31  2008 vendor

If its an NG box ie S905x2 or S922X. Try to download the test.sh script from How to run CoreElec on internal memory eMMC on NG boxes (S905X2, S922X) having full operating Android system too

run it, it should then mount your internal emmc to the /mnt/data directory

1 Like

Brilliant!!! It worked! Many many thanks!
The Android storage is then on /tmp/data/media/0
Now I just have to automate the mount on startup.

Add it to your autostart.sh in the configfiles directory. If you haven’t got one you could just rename it to autostart.sh and copy it into the ConfigFiles directory

1 Like

You will be able to mount /dev/data directly in the future without resorting to such hacks.

1 Like

Glad to here it I was going to move the database directory and thumbs to emmc but may now go down the install to emmc route.