Announcement

Collapse
No announcement yet.

Announcement

Collapse
No announcement yet.

[ROM] Unofficial OpenELEC for MK808B+ and MXQ

Collapse
This is a sticky topic.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Originally posted by michaelchen View Post

    It used to do the same with confluence when I used kodi 15 lsengard and as I said that I noticed it happens when I use the return button then kodi would just freeze but I Was able to ssh a reboot command and then continew untill the next time it happens.
    Yes the skin im using is from the official repo (phenomenal).
    Now I'm trying not to use many shortcuts in my home screen (problem for the kids)
    Okay
    I do recall a while ago i had this hanging issue which was caused by an addon.
    Go to Systems/Addons/System/Running
    See what is running. If you have a build with loads of addons it will be hard to identify which running process is the culprit.
    As an example i only have 7 processes running and only 2 of them are used by Video addons.
    The rest are skin helper, openelec configuration , Super Favourites, etc
    __________________________________________________ ______________________________
    All Black MXQ:Running OE-Amlogic.MXQ.arm-6.95.2.2 On Nand. Board Number: AM_MXQ_A 20150825





    Comment


      pigbait and all

      A quick instruction on how to replace a device tree. You'll need either a Linux PC/VM or Windows with Cygwin and perl interpreter:
      • download http://s805.eu/utils/bootimg_tools/bootimg_tools.zip and unpack it to your working directory
      • unpack kernel image from Android firmware (most commonly named boot.img), rename it to android.img and place it in your working directory
      • unpack KERNEL from my OE tar release, place it in your working directory and rename it to oe.img
      • run these commands (in Cygwin you'll need to replace mkbootimg command with mkbootimg.exe):
        Code:
        ./split_boot android.img
        ./split_boot oe.img
        mkdir -p target
        ./mkbootimg --kernel oe/oe.img-kernel --ramdisk oe/oe.img-ramdisk.cpio.gz --second android/android.img-second.gz --output target/KERNEL
        md5sum -t target/KERNEL > target/KERNEL.md5
      • copy KERNEL and KERNEL.md5 from target dir in your working directory to Update folder on your device
      • copy SYSTEM and SYSTEM.md5 from OE update tar file to Update folder on your device
      • reboot your device and keep your fingers crossed

      Comment


        Originally posted by kszaq View Post
        pigbait and all

        A quick instruction on how to replace a device tree. You'll need either a Linux PC/VM or Windows with Cygwin and perl interpreter:
        • download http://s805.eu/utils/bootimg_tools/bootimg_tools.zip and unpack it to your working directory
        • unpack kernel image from Android firmware (most commonly named boot.img), rename it to android.img and place it in your working directory
        • unpack KERNEL from my OE tar release, place it in your working directory and rename it to oe.img
        • run these commands (in Cygwin you'll need to replace mkbootimg command with mkbootimg.exe):
          Code:
          ./split_boot android.img
          ./split_boot oe.img
          mkdir -p target
          ./mkbootimg --kernel oe/oe.img-kernel --ramdisk oe/oe.img-ramdisk.cpio.gz --second android/android.img-second.gz --output target/KERNEL
          md5sum -t target/KERNEL > target/KERNEL.md5
        • copy KERNEL and KERNEL.md5 from target dir in your working directory to Update folder on your device
        • copy SYSTEM and SYSTEM.md5 from OE update tar file to Update folder on your device
        • reboot your device and keep your fingers crossed
        Thx
        So if I get it, if I have a working Android OS on my mxq and lan+wifi, audio (hd+analog+spdif) bt are working then if I do the instructions u said to do then all should work in OE???????
        I have just e-mailed my mxq seller for the Android OS for my box (the spdi f issue on my box) .

        Comment


          Originally posted by michaelchen View Post
          Thx
          So if I get it, if I have a working Android OS on my mxq and lan+wifi, audio (hd+analog+spdif) bt are working then if I do the instructions u said to do then all should work in OE???????
          I have just e-mailed my mxq seller for the Android OS for my box (the spdi f issue on my box) .
          You should replace device tree only if you have hardware issues in OE. Also there are no working drivers for Realtek 8723BS Bluetooth and Mediatek MT7601U WiFi in my OE builds (yet) so they won't work. But if you have issues with S/PDIF or not working WiFi with a supported chip (Broadcom/Realtek), replacing device tree may help.

          Comment


            Originally posted by kszaq View Post
            You should replace device tree only if you have hardware issues in OE. Also there are no working drivers for Realtek 8723BS Bluetooth and Mediatek MT7601U WiFi in my OE builds (yet) so they won't work. But if you have issues with S/PDIF or not working WiFi with a supported chip (Broadcom/Realtek), replacing device tree may help.
            Ok Kszaq thx
            The only issue I have is spdi f .so I guess if I get the Android os for my mxq and the spdi f will hopefully work then I will do every thing u said....replace device tree.

            Comment


              kszaq thanks instructions are nice and clear. Ill mess around with it tonight.

              Comment


                kszaq Done a clean install of 6.95.2.3 and all seems fine, in fact very good, will let you know if I have any issues over the next few days.

                On a side note: I've decided to use short male-to-female USB extension cables with my SanDisk Ultra USB memory sticks and my box runs much cooler and seems more responsive! So if anybody is running hot USB sticks you might get a performance increase from your box if you simply use extension cables. Yes not as neat and tidy but better to have a smooth running box.

                ---------------------------------------------------------------------------------------------------------------------------------------------------------------
                Running MXQ.arm-6.95.2.3 from Nand (clean install) on all black MXQ, board number: 'AM_MXQ_A 20150825

                Comment


                  Originally posted by pigbait View Post
                  Guest I know this is problem is probably a device tree issue, but i got a newer andriod firmware for my ALL black HD18Q, I was hoping with this new firmware it would fix my WiFi module not being recognized. it has an RTL8188 witch I know your OE builds support im just not sure why it wont load?

                  I have uploaded the firmware it is an SD flashable zip along with dmesg log.

                  Maybe you could lead me in the right direction on how to compile with the correct device tree.

                  Thanks Pigbait.
                  Before I continue to update my box
                  I assume that it is build number kot49h.20151104 test-keys??

                  Comment


                    Originally posted by michaelchen View Post

                    Before I continue to update my box
                    I assume that it is build number kot49h.20151104 test-keys??
                    I'm not sure if my andriod firmware is even the correct one for your box. So I wouldn't recommend flashing it unless you know it's correct.

                    Comment


                      Originally posted by pigbait View Post

                      I'm not sure if my andriod firmware is even the correct one for your box. So I wouldn't recommend flashing it unless you know it's correct.
                      i found the correct file (kot49h.20151104 test-keys) from chinagadgets, but its an IMG file named MXQ-latest firmware.img

                      i use toothpick method and choose aplly update from ext, then choose sdcard, some command run but it cant load any thing.
                      do u know how to flash the IMG file?
                      or now a howto guide of flashing it ?
                      the file u uploaded is an sdcard version right?

                      Comment


                        Kszaq i have to ask u
                        my box came with the android OS, i remember there was an option of digital audio in the settings section.
                        if it was on OFF, than when i flashed OE to nand then it did not recognized the spdif out in the first install of OE?
                        so if i flash android to nand again and change settings of spdif to ON and reflash OE then it might work under OE?????

                        Comment


                          Originally posted by michaelchen View Post
                          Kszaq i have to ask u
                          my box came with the android OS, i remember there was an option of digital audio in the settings section.
                          if it was on OFF, than when i flashed OE to nand then it did not recognized the spdif out in the first install of OE?
                          so if i flash android to nand again and change settings of spdif to ON and reflash OE then it might work under OE?????
                          I think you might be right but not qualified to say that as a fact. I wonder if there any command that can be given to change bootloader? K will know.

                          Comment


                            michaelchen I wrote down the firmware for my new box, didn't twrp it as I'm not sure how to do that, but it was this: KOT49H.20160321 test-keys So you could search for that as we have same board.

                            You could also ask kostaman if he has and SD card firmware version as opposed to an image version, he has same board. I think the 'image' version you have has to be flashed via USB but I may be wrong. Anyway goodluck.

                            Comment


                              Originally posted by PatrickJB View Post
                              Guest I wrote down the firmware for my new box, didn't twrp it as I'm not sure how to do that, but it was this: KOT49H.20160321 test-keys So you could search for that as we have same board.

                              You could also ask Guest if he has and SD card firmware version as opposed to an image version, he has same board. I think the 'image' version you have has to be flashed via USB but I may be wrong. Anyway goodluck.
                              Thx
                              You meen I need a usb to usb cable?
                              And then connect the mxq to my pc to fish?

                              Comment


                                First LibreELEC build available! In most cases you should be able to safely migrate from OpenELEC to LibreELEC without resetting to factory settings. Make a backup just in case.

                                Comment

                                Working...
                                X