Posts by shut3n

You're right dtech , repo's working. I think I've been touching too much kodi settings, while testing here and there on my device, then something got stucked. Then I've done a hard reset and start from the beginning, so everything got fixed. Also I did move the installation from sd card to devices's NAND; installtointernal did everything done safe and sound.

PS: Emulator addons part are working like a charm for me, also my wireless (usb rf) Snes pad clone's detected and maped in a blink of an eye.

I'm doing then 🙂

About LibreELEC and Kodi game (alpha) repositories for 9.2.8.7 are still active? I think I was able to connect to them last night, but today they seem unreachable

Quote from chewitt

Fake RAM size isn't uncommon but it's rare to see 512MB configurations outside of industrial boards, even on older platforms like Meson8. I'd guess you still have the wrong boot ROM for the box and the RAM configuration in early boot code means it's only seeing 1 bank of RAM, and the second (missing) will add another 512MB to give a more normal 1GB.

Then again; this is an era where all kinds of shady manufacturing has been done. If it works and doesn't cause problems; don't fix it

You're right, for the moment I'm getting what I needed. Now LE boosted (resurrected) my old (outdated kitkat) TV box, and I have my VOD subscriptions accessible from one unified place

While I noticed some lagging on configuring processes and installing some add-ons, the thing really gets better when just navigating through menues and library. Also on playback features is doing a good performance. Ssh and samba services working also

About networking, Ethernet and Bluetooth are detected and active. For wireless, it's shown as active on Libreelec Network Settings, but no Access Point listed in Connections section. As you said chewitt , I'll take the good part of all of it. I can get things working now; with or without wireless

I would like to share my first log of a successful LE9 boot and running

http://ix.io/4q21

Looking to it I've noticed 1024MB of RAM are detected on boot. So it could be Kodi is mismatching it when showing 512MB

Quote from dtech

Please try the n200 image with this kernel:

http://libreelec.dtech.hu/_TEST_/MXIII-G_1GB-kernel/

If it starts with this, your Android is unfortunately only lying that you have 2GB of RAM, but in fact it only manages 1GB.

It worked!

Just finished installation/configuration process. Now I need a time to check how things are doing

The first thing I've noticed the 4 CPU cores are detected and running correctly

RAM amount is now cut to 512MB total. Don't now if it can be a problem for video playing/decoding performance, I must do some testing

Thank you so much, I really appreciate your work

Quote from dtech

shut3n

The root of the problem doesn't start here, as I see. I think your box does not have the original ROM with the factory bootloader, because based on the photos, there are 4 pieces of 512MB Samsung K4B4G0846C chips on the PCB.

Very well, then restarting from zero. The good new.. it's a 2GB RAM device👌😉

Quote from dtech

So, in short...

Your box is equipped with 2GB of RAM, but it seems that the factory ROM has been overwritten. You should first find the factory ROM for his box from somewhere and flash it.

Done, now it has the factory stock firmware installed, 2GB of RAM detected

Quote from dtech

If you're done with that, you should try the Universal k200 image. (But this wifi chip really won't work.)

Done too (with k200 image), but doesn't boot LE (stucked on billow logo)

Tried also for n200, mxiii-plus, x8's and m8s plus images, but nothing

Only managed to boot from MXIII-1GB image, but then the "read only" known issue

Quote from dtech

yibaogang

Another approach:

I made two kernel images with the right dtb, please follow my description.

First, use this image again for prepare the SD card:

LibreELEC-MXIII-1G.arm-9.2.7.img.gz

Then download this, extract and overwrite the files on the card with these (kernel.img, kernel.img.md5, dtb.img):

LibreELEC-M8.arm-9.2.7-kernel.img+dtb.tar.gz

Then boot your box from this SD card and test the Ethernet.

If Ethernet still doesn't work, try this:

LibreELEC-S82.arm-9.2.7-kernel.img+dtb.tar.gz

Display More

Hi dtech , I took your example to test some combination dtb+kernel for my tv box. Without success

It seems that mmcblk0 device (sd card slot) on my tv box is booting in read only mode. So no way to make a LE successful first boot.

I'm playing with your S802/S812 images on http://libreelec.dtech.hu/images/3rdParty/

I burned MXIII-1G (S802) image on different SDCard capacity 4/8/16GB with exactly the same boot loop (read only) issue. As in your method, I'm testing different DTB/Kernel combinations but no much familiar with it and which variants or modifications I can try

PCB: Number M8 V8_1 20150418

Internal storage: 8GB

RAM: 1GB real amount (on Android was tricked to 2GB)

External Branding: Billow MD05TV (from Spain)

https://www.manualslib.com/manual/1054603/Billow-Md05tv.html - not much data about device architecture on these manuals, only for external aparence references

Wifi: BCM4335 (running on Stock Android Kitkat)

Certainly I'm not interested on making wireless to run (ethernet card will do it nice for me). Only installing and running LE9 from the Sdcard would me fantastic for me

Not sure if any specific driver or firmware preloaded on kernel boot that loads mmcblk0 features would be necessary. For a full access to writing operations on SDCard slot

Some dmesg messages from the debug console on LE install attends:

Img 1 and 2 "read only" messages

On third image I checked that write mode is enabled for both USB ports, but I couldn't boot any LE image from them (only boots from sdcard)

I tested too an Armbian image, based on Debian Stretch xfce on kernel 3.10.108. It managed to mount sdcard on writable mode, successful booted, and ran into desktop environment

Linux

Посмотреть и скачать с Яндекс.Диска

disk.yandex.ru

More details of Armbian booting to this link http://ix.io/4pbS/

One more observation is that LE9 it only booted, entried on LE logo mode, from the 1GB image (MXIII-1GB). The others, black screen directly

--UPDATE: From Armbian it booted from MXIII-Plus (2GB) dtb, defined by default on uEnv.ini file. I didn't change anything from the default selections. Although it detected the real 1GB of RAM

This is all info I tried to compile from a few test and error days

Thank you

[mod] If you include several photos or screenshots in your post, please use thumbnails instead of the full size images. Thanks. ( dtech)[/mod]