[ROM] Unofficial OpenELEC for MK808B+ and MXQ

[kszaq]

just took a huge leep of faith and it is m201d for all black MXQ boxes. now just just have to find a way to unbrick the first one i put the MXQ on lol

There's no one "all black MXQ", therefore you should try HD18Q build first and then m201d if it doesn't boot. If you "bricked" your device by flashing MXQ build to NAND, there is a very easy way to fix: prepare SD card with m201d NAND build and flash it with toothpick method. My builds replace only kernel and system images and you can get a very soft brick at most.

[Spekkie]

You can attach serial console, press Enter to stop automatic boot and run bdinfo. The result will be:

DRAM bank = 0x00000000
-> start = 0x00000000
-> size = 0x40000000

This is from box with 1GB RAM. With V3_1 board I get

DRAM bank = 0x00000000
-> start = 0x00000000
-> size = 0x20000000

Thanks that is indeed the case with my board aswell...
I've opend a dispute on aliexpress about this problem as the add clearly stated 1GB ram...

I would like to extract the device tree from te device in order to see what amount of ram is stated there.
I've tried mounting the boot partition from within android but I get an access denied...
I've also tried to create a full backup with TWRP, but I can't find a werking version for the V3_1 20151230 board...

Do you have any bright ideas how to get my hands on the boot.img from the device.
(Just to be clear, I would like to extract it from nand and not some zipped rom found on the internet)

[kszaq]

Thanks that is indeed the case with my board aswell...
I've opend a dispute on aliexpress about this problem as the add clearly stated 1GB ram...

I would like to extract the device tree from te device in order to see what amount of ram is stated there.
I've tried mounting the boot partition from within android but I get an access denied...
I've also tried to create a full backup with TWRP, but I can't find a werking version for the V3_1 20151230 board...

Do you have any bright ideas how to get my hands on the boot.img from the device.
(Just to be clear, I would like to extract it from nand and not some zipped rom found on the internet)

Boot OE from SD card and run

dd if=/dev/boot of=boot.img

I'm still wondering why I have "512X8DDR3" markings on my RAM chips. Either they are also fake or manufacturer compiled a wrong u-boot for the device. I tried booting the box with 1GB u-boot with no success.

[bossydale]

i can't boot to recovery on these 2 boxes for some reason

[kiwi_man82]

I'll be keeping an eye on this issue Spekkie. I don't have the tech know how to start looking into this myself anyway I don't know if the fw I flashed back to my box is the stock fw as I bricked my device and only managed to get it running using the cyx fw in my signature. kszaq, does the u_boot have to be correct for the ram amount on the board to boot along with everything else it deals with? I guess the answer to that it would seem to be yes unless the 1gig u_boot you used also had other differences to just the ram??

[Jiffypop]

I have an MXV running HD18Q 6.0.3.7 build and everything works well except for shutdown, the remote of course, but the reboot does work. I no longer have to plug a male to male usb cable into port 1 and 4 to get it to boot. Thank you so much Kszaq for that fix! Anyways, the only thing that I am having a problem with is the remote. I downloaded and added the remote.config that Mwp1 posted for download on here. It got my remote working but once a every day or two it stops functioning properly. The select key, return key, and the arrow keys will stop working randomly and I am forced to either unplug the power to the box or I can plug in a bluetooth keyboard control it that way. The Home key has never worked and I even tried the keymap addon but I still couldn't get it to work. Has anyone else had this problem with the MXV? If so what can I do to try and fix it?

[mwp1]

I have an MXV running HD18Q 6.0.3.7 build and everything works well except for shutdown, the remote of course, but the reboot does work. I no longer have to plug a male to male usb cable into port 1 and 4 to get it to boot. Thank you so much Kszaq for that fix! Anyways, the only thing that I am having a problem with is the remote. I downloaded and added the remote.config that Mwp1 posted for download on here. It got my remote working but once a every day or two it stops functioning properly. The select key, return key, and the arrow keys will stop working randomly and I am forced to either unplug the power to the box or I can plug in a bluetooth keyboard control it that way. The Home key has never worked and I even tried the keymap addon but I still couldn't get it to work. Has anyone else had this problem with the MXV? If so what can I do to try and fix it?

I suggest you use the kszaq libreelec hd18q 7.0.0.2 from:

https://forum.libreelec.tv/thread-200.html

I don't know if it will solve the problems you have, but it is working great for me. Shutdown works in this build.

[Jiffypop]

I have installed LibreElec HD18Q 7.0.0.2 and the remote problem is still present. Have you had this problem at all? Also, were you able to get your home button to work? The shutdown option works but now the reboot option does not work.

[bossydale]

ok so now i have a big problem i have 1 box which only has a red light on the box an nothing else at all can't turn it on or get a display. the second box hangs at the MXQ screen and does nothing else. they are both all black MXQ. what can i do to sort this out?

[kiwi_man82]

ok so now i have a big problem i have 1 box which only has a red light on the box an nothing else at all can't turn it on or get a display. the second box hangs at the MXQ screen and does nothing else. they are both all black MXQ. what can i do to sort this out?

Is this the result of flashing oe/le to your boxes or did you try another android rom when this happened? If it is due to android flash then you could try Google search for the fw in my signature (you have v3_1 board, right?)

[kszaq]

kszaq, does the u_boot have to be correct for the ram amount on the board to boot along with everything else it deals with? I guess the answer to that it would seem to be yes unless the 1gig u_boot you used also had other differences to just the ram??

The answer is yes.

One part of u-boot binary is DDR initialization file, second is u-boot itself. Both parts have to be compiled for correct amount of RAM and there are also other differences, like IR remote code, suspend code, peripherals initialization code etc.

The u-boot I used failed during DDR initialization and I don't know if the rest would work.

[jellywobbles]

Can anyone help? Want to try this on SD card, but not sure how to extract the .img.gz file??? (LibreELEC-S805.HD18Q.arm-7.0.0.2.img.gz)

[Spekkie]

I'm looking for a way to use an external usb wifi adapter with this fw, any suggestion? I've tried my tp-link 150 mbps adapter, but I can't switch between integrated or external wifi card...

Tried winrar?

[Spekkie]

Boot OE from SD card and run

dd if=/dev/boot of=boot.img

I'm still wondering why I have "512X8DDR3" markings on my RAM chips. Either they are also fake or manufacturer compiled a wrong u-boot for the device. I tried booting the box with 1GB u-boot with no success.

Yeah well I did some digging and extracted the device tree and ramfs from the device thanks to your advice...
Device tree is attached and also shows only 510MB ram available for linux...
So they either screwed up the rom by picking the wrong files or the ram chips are a bust.
But since the way they tried really hard to convince people that it's actually 1GB I guess that the ram chips are a bust...

Some other interesting passages I found sifting through the ramfs files were these:
init.amlogic.board.rc

 
# Disable suspend
    write /sys/power/wake_lock true

and
init.rc

# Memory management.  Basic kernel parameters, and allow the high
# level system server to be able to adjust the kernel OOM driver
# parameters to match how it is managing things.
    write /proc/sys/vm/overcommit_memory 1

[kektyke1875]

Hi All, great work on the roms. I have an all black MXQ and tried most of the roms but either get no response from the remote or the wi-fi gets disabled. Is there a rom that fixes both of these problems, really like openelec and want to upgrade to Jarvis but had to go back to 15.2 until i find a working rom