I downloaded this CoreELEC-S912.arm-8.90.2.tar file into the .update directory of my Mecool KM8 P TV Box Amlogic S912 with 1GB running on LE 126.96.36.199. When my device rebooted, it successfully processed the upgrade, but ended with a debug message asking me to type EXIT. Did I do something wrong or this device is not supported? I certainly will appreciate if anyone here who managed to get this device up running with CoreELEC can help.
Well, personally, I would have used a different usb to install one of these pre alpha builds, & not touched the 188.8.131.52 build.
I think you need to start again, download the img.gz file & correct dtb, although it might be in the build. Also you need to bear in mind, that the remote control works in a completely different way. So, you might do best to use a keyboard for the initial configuration.
I’ll have a look, to see if I can find the relevant pages. But I do not have this device.
It looks like the device tree you need is in the image gxm_q201_1g.
If it boots up, you will then need to try to get the remote work, read, the links in this
Sounds like you need to change the partition label on your storage partition.
I downloaded this CoreELEC-S912.arm-8.90.2.img.gz file to a /tmp directory on my Linux desktop computer, gunzip dd if=/tmp/CoreELEC-S912.arm-8.90.2.img.gz of=/dev/sdb bs 4M, and then use dd if=/tmp/CoreELEC-S912.arm-8.90.2.img of=/dev/sdb bs 4M to image the file to a 4 GB USB2 memory stick. After syncing the USB2 memory stick, I un/re-plug the USB2 memory stick the same USB3 port and my Linux desktop computer ONLY recognized and automounted the /dev/sdb2. When I tried to manually mount the /dev/sdb1, it gave me the error messages as shown below. Regardless, I unplugged the USB2 memory stick and plugged it into one of the USB2 ports on my KM8 P TV Box. When I powered the device, it booted into its original Android OS. So, it looks like something is wrong with the img file.
[root@linux:/root 608%] # mount /dev/sdb1 /mnt
mount.nilfs2: Error while mounting /dev/sdb1 on /mnt: Invalid argument
[root@linux:/root 609%] #
As with the image gxm_q201_1g, I certainly will appreciate if you can provide the link so I can give it a try.
To what name shall I need to change the partition label?
Personally, I don’t know much about Linux. I used rufus from a windows pc.
If you use that, there is a folder with the device trees.
This is a list of device trees for the majority of boxes
I’m not sure how to upload files on this forum.
e2label /dev/data "STORAGE"
Upgrading from kszaq builds is not supported, upgrading from LE builds is.
I suppose you meant upgrade from CE (not LE) build is supported. Otherwise, my current setting is from LE-184.108.40.206 for my KM8 P (S912) TV Box.
[quote=“adamg, post:7, topic:423, full:true”]
e2label /dev/data "STORAGE"[/quote]
I tried your suggestion above to the existing LE-220.127.116.11 on my USB2 memory stick (/dev/sdb2) and e2label gives error messages as shown below. AFAICT, the 1st partition of LE is a VFAT filesystem and e2label only supports ext2/3/4 filesystems.
[root@linux:/root 617%] # e2label /dev/sdb1 “STORAGE”
e2label: Bad magic number in super-block while trying to open /dev/sdb1
Couldn’t find valid filesystem superblock.
[root@linux:/root 618%] #
Sorry and I am not sure exactly what you meant. In my OP, I clearly stated that I downloaded the CoreELEC-S912.arm-8.90.2.tar file from here and I do NOT see any mentions of the device tree in the link.
If, you were to use rufus from windows to create the image with the img.gz
you would see the dtb folder in the root.
I do not know how to get this using Linux
No, I did not make a mistake I meant the LE test builds that are floating around.
I really dont know what you are trying to do here, the STORAGE partition is an EXT partition and the busybox version of e2label has always worked for other users stuck with the same problem.
If you are wanting to save your data you will have to elaborate more on your issue than you have otherwise you will have to perform a clean install.
If you used the command/s as posted then it seems there is an error there.
I would try this
gunzip -c /tmp/CoreELEC-S912.arm-8.90.2.img.gz | dd of=/dev/sdb status=progress
on the basis that the location of the .img.gz file is in /tmp and /dev/sdb is actually your USB stick (you should double check before writing).
Maybe you should try using LE USB-SD Creator app for Linux?
[quote=“bubblegum57, post:11, topic:423, full:true”]
If, you were to use rufus from windows to create the image with the img.gz
you would see the dtb folder in the root. [/quote]
Sorry and I don’t have a Windows computer.
[quote=“JohnBoyz, post:13, topic:423, full:true”]
If you used the command/s as posted then it seems there is an error there.[/quote]
After your above comment, I went back to re-read my post and noticed there was an error in my comment using the gunzip. Anyway, I followed your suggestion (see below) and now I can see the device_trees sub-directory. I will try the gxm_q201_1g.dtb file and report back.
[root@debian:/tmp 47%] # cd /mnt/tmp/
[root@debian:/mnt/tmp 48%] # wget https://github.com/CoreELEC/CoreELEC/releases/download/8.90.2/CoreELEC-S912.arm-8.90.2.img.gz
–2018-05-16 19:41:43-- https://github.com/CoreELEC/CoreELEC/releases/download/8.90.2/CoreELEC-S912.arm-8.90.2.img.gz
Resolving github.com (github.com)… 18.104.22.168, 22.214.171.124
Connecting to github.com (github.com)|126.96.36.199|:443… connected.
HTTP request sent, awaiting response… 302 Found
Location: https://github-production-release-asset-2e65be.s3.amazonaws.com/127708886/6cd6f786-5112-11e8-9f77-712461c32030?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20180517%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20180517T024143Z&X-Amz-Expires=300&X-Amz-Signature=4cff997742f435978d9d60d6eb348f4728f1ea43d8e5d262ae59a3145c164566&X-Amz-SignedHeaders=host&actor_id=0&response-content-disposition=attachment%3B%20filename%3DCoreELEC-S912.arm-8.90.2.img.gz&response-content-type=application%2Foctet-stream [following]
–2018-05-16 19:41:43-- https://github-production-release-asset-2e65be.s3.amazonaws.com/127708886/6cd6f786-5112-11e8-9f77-712461c32030?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20180517%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20180517T024143Z&X-Amz-Expires=300&X-Amz-Signature=4cff997742f435978d9d60d6eb348f4728f1ea43d8e5d262ae59a3145c164566&X-Amz-SignedHeaders=host&actor_id=0&response-content-disposition=attachment%3B%20filename%3DCoreELEC-S912.arm-8.90.2.img.gz&response-content-type=application%2Foctet-stream
Resolving github-production-release-asset-2e65be.s3.amazonaws.com (github-production-release-asset-2e65be.s3.amazonaws.com)… 188.8.131.52
Connecting to github-production-release-asset-2e65be.s3.amazonaws.com (github-production-release-asset-2e65be.s3.amazonaws.com)|184.108.40.206|:443… connected.
HTTP request sent, awaiting response… 200 OK
Length: 150668273 (144M) [application/octet-stream]
Saving to: ‘CoreELEC-S912.arm-8.90.2.img.gz’
CoreELEC-S912.arm-8.90.2.img.gz 100%[==========================================================>] 143.69M 4.43MB/s in 35s
2018-05-16 19:42:19 (4.11 MB/s) - ‘CoreELEC-S912.arm-8.90.2.img.gz’ saved [150668273/150668273]
23.868u+7.669s=0:37.35e(84.3%) TDSavg=0k+0k+0k max=8724k 24111+294960io 43pf+0sw
[root@debian:/mnt/tmp 49%] # sync
[root@debian:/mnt/tmp 50%] # gunzip -c CoreELEC-S912.arm-8.90.2.img.gz |dd of=/dev/sdd1 status=progress bs=4M
231899136 bytes (232 MB, 221 MiB) copied, 44 s, 5.3 MB/s
gzip: CoreELEC-S912.arm-8.90.2.img.gz: invalid compressed data–format violated
0+6759 records in
0+6759 records out
239239168 bytes (239 MB, 228 MiB) copied, 44.8508 s, 5.3 MB/s
16.158u+4.595s=0:44.86e(46.2%) TDSavg=0k+0k+0k max=1852k 294160+467256io 2pf+0sw
[root@debian:/mnt/tmp 51%] # sync
[root@debian:/mnt/tmp 52%] # mount /dev/sdb1 /mnt/tmp1
[root@debian:/mnt/tmp 53%] # dir /mnt/tmp1/
-rwxr-xr-x 1 root root 815 May 5 06:34 aml_autoscript
drwxr-xr-x 2 root root 8192 May 5 06:34 device_trees
-rwxr-xr-x 1 root root 137216 May 5 06:34 dtb.img
-rwxr-xr-x 1 root root 9744384 May 5 06:34 kernel.img
-rwxr-xr-x 1 root root 48 May 5 06:34 kernel.img.md5
-rwxr-xr-x 1 root root 157888512 May 5 06:34 SYSTEM
-rwxr-xr-x 1 root root 48 May 5 06:34 SYSTEM.md5
[root@debian:/mnt/tmp 54%] # dir /mnt/tmp1/device_trees/
-rwxr-xr-x 1 root root 46339 May 5 06:34 gxm_kvim2.dtb
-rwxr-xr-x 1 root root 44286 May 5 06:34 gxm_q200_1.5g.dtb
-rwxr-xr-x 1 root root 44282 May 5 06:34 gxm_q200_1g.dtb
-rwxr-xr-x 1 root root 44282 May 5 06:34 gxm_q200_2g.dtb
-rwxr-xr-x 1 root root 44916 May 5 06:34 gxm_q200_2g_minix_neo_u9.dtb
-rwxr-xr-x 1 root root 44282 May 5 06:34 gxm_q200_3g.dtb
-rwxr-xr-x 1 root root 45690 May 5 06:34 gxm_q200_k3_pro.dtb
-rwxr-xr-x 1 root root 44061 May 5 06:34 gxm_q201_1g.dtb
-rwxr-xr-x 1 root root 44435 May 5 06:34 gxm_q201_2g.dtb
-rwxr-xr-x 1 root root 44435 May 5 06:34 gxm_q201_3g.dtb
[root@debian:/mnt/tmp 55%] #
I reckon you meant the 2nd partition where the root account is stored. In this case, it is an EXT4 partition.
For some reason this fails … maybe a corrupted download.
gunzip -v CoreELEC-S912.arm-8.90.2.img.gz
on a copy of the file and it should replace it with a .img file (~549MiB) without error.
[quote=“JohnBoyz, post:17, topic:423, full:true”]
For some reason this fails … maybe a corrupted download.[/quote]
Sorry and I quoted from a previous run with such a wrong output when I downloaded the .img.gz file using a broken microSD card. Since that error messages, I already created CE on my USB2 memory stick and it did not produce such an error message. I will report back once I get a chance to test it.
OK, glad you got it installed correctly.
Finally, my KM8 P TV Box now boots with CE v8.90.2 and the remote control works out of the box. All I had to do is to copy the /flash/device_trees/gxm_q200_1g.dtb to /flash/dtb.img .
Thank you everyone for your helps.