There is nothing stopping you booting from usb/sd card, installing to internal is a niche feature only for community builds and will not be available in official builds when they arrive.
No problem, SD is also OK. Thanks for your respons!
Posts by wistoha
-
-
Yes. /dev/SYSTEM is a LibreELEC system image copy in RAM.
Thanks kszaq. Sadly now no support. In the future maybe? Or not at all.
-
wistoha Most probably you have an unsupported NAND. Unfortunately support cannot be added for that chip as driver is closed-source and we rely on Amlogic for updates.
Thank for quick response.
Only de file 'SYSTEM' is present in de /dev/ directory.
dtb, boot, system and data not there. The same conclusion?
-
Quote
# ls /dev/boot /dev/system /dev/data /dev/dtb
All of them: No such file or directory
Also with the nand dtb.
-
Hi guys,
Accompanying my problem to the SD card to install in the internal memory.
I have tried all available S905X device tree's with the same result.
Everything works perfectly on the SD card.
My BOX:
MXQ pro 4 k
Android 6.0.1
S905X
Anyone have a solution?Thanks in advance
-
Quote
If you forgot to use a new device tree or used wrong one and your device doesn't boot:
- don't panic!
- if booting from SD/USB, simply connect SD/USB to your computer, download a proper device tree, rename it to dtb.img and place on SD/USB
- if booting from internal:
- Boot this build from SD card or USB with correct device tree.
- Login over SSH and execute dd if=/dev/zero of=/dev/dtb bs=256k count=1 then dd if=/flash/dtb.img of=/dev/dtb bs=256k
- Power off, remove SD/USB, boot from internal.
Unfortunately I have the wrong order held upgrade. I can now no longer upgrade (wrong image). In order to be able to upgrade from build 8.0 I need build the dtb value 8.0. Who can give me the parameters for the 8.0 build?
-
Omg. Just ran cpu-z. It tunes out to be a rockchip3066. Is this chip as good as the s905x or have I been scammed? It said s905x on the box AND during boot.
Now we know the chipset, can I install libreelec?
Thanks for all your help
Try this.
My box is the S905 MXQ NEXBOX Pro 4 k '.
It took me a lot of time to the box flashing it. None of the mentioned possibilities on this forum worked in my case. The following steps brought luck.
- Copy the image to SD with rufes.exe.
- Copy the new dtb.img as prescribed. (gxbb_p200_1G_100M_RealtekWiFi.dtb)
- But then the trick. Zip the ' aml_autoscript ' file from the SD and copy it to the SD card. (Leave the existing aml_autoscript).
- Use the update app in andoid and update the zip file on the SD card.
Voila, it works! Then went flashing as expected.
(It boots first with the NEXBOX logo, the libreelec logo appears briefly after.) -
Same here!!
Copy your own remote.conf to /.config. It works on 8.0.0b. (incl after reboot).
-
Tribute to the creator of this product. It works great.
My box is the S905 MXQ NEXBOX Pro 4 k '.
It took me a lot of time to the box flashing it. None of the mentioned possibilities on this forum worked in my case. The following steps brought luck.
- Copy the image to SD with rufes.exe.
- Copy the new dtb.img as prescribed. (gxbb_p200_1G_100M_RealtekWiFi.dtb)
- But then the trick. Zip the ' aml_autoscript ' file from the SD and copy it to the SD card. (Leave the existing aml_autoscript).
- Use the update app in andoid and update the zip file on the SD card.
Voila, it works! Then went flashing as expected.
(It boots first with the NEXBOX logo, the libreelec logo appears briefly after.)
The power-off button provides the complete shutdown (no lamp indication). With the android software, the box getting in standby mode (red indicator).
That means that with the LE software enabling with the power button is not possible. I have read several posts on this subject. Is this the same problem as known by the known issue "Suspend does not work on most devices. Use power off. Power off is a default action or IR remote power button. "?
Is there a workaround to the box with the LE software in the standby mode to get? Changing system settings in KODI does not work.
Thanks.
