Thanx datrh for update 18.5! Everything is running like new once again. Done a fresh installation and all went smooth.
I am not a developer, code-writer or expert, I just try to help people.
Error please delete this post
I always use the USB Burning Tool so with the Burn Card Maker I have no idea ......
With the USB Burning Tool I use an old mini HP PC with windows 7 x32 / as windows 10 can be a pain to burn firmware !
I had it once where it hung and I turned it off, removed the SD-card and booted it back up with the reset method to get to the screen where you can clear the: "WIPE CACHE PARTITION" from the bootmenu afterwards choose Reboot and all started up fine after that for me.
USB Burning Tool never failed on me so I have no experience on the Card Maker method. I am sorry.
Maybe someone here can help more on this subject.
Wanna find out more about shutdown function behavior
- When power button push on minix neo, choose shutdown from menu. -> minix shut-off TV (which is known behavior)
- When i power on TV after 10 minutes, the shutdown screen remain.
- Thus, i will need to unplug and plug power in order to power-up minix.
Is this normal?
Yes with the "Stock" ROM it is ! Now - "minix_x8_x8plus_x8_h_newbootloader_FW9" - firmware will give you proper shutdown, Just be patient after flashing and starting it back up > it can take a long time to boot up android as it has to build all the cache files etc. so be patient.
After that you will again have to hold the reset to break the bootlaoder again with the LibrElecec SD.
and btw dont freak out with a black screen during first startup Android, so be patient!
Hi, Owned Minix X8H running Minix Offical Firmware (KOT49H.20160324). Wanted to try LibreELEC 9.X with Kodi 18.
Attempt update using USB Burn Tool
- Unable upgrade via USB Burn Tool, receive error "Parse burning image fail" while loading LibreELEC-X8-X8H.arm-LE9-Kodi_18.3.img.
- Re-downlaod img and upgrade via USB Burn Tool, receive error "Parse burning image fail" while loading LibreELEC-X8-X8H.arm-LE9-Kodi_18.3.img.
- Re-downlaod img and upgrade via USB Burn Tool, receive error "Parse burning image fail" while loading LibreELEC-X8-X8H.arm-LE9-Kodi_18.2.img
Next, trying update using SD
- Tried Update Bootloader - Not working for me - Burn the GZ img to a SD using LibreELEC.USB-SD.Creator.Win32, Browse the SD and rename "boot_autoscript" to "boot.scr", Insert the SD in the minix and boot the minix while holding reset switch for 5 -6 sec (the bootloader will be patched)
Result: Boot into recovery mode, but not sure which to select such as apply update from ADB, apply update from ET and etc.
Burn the GZ img on 32GB SD
Result: LibreELEC.USB-SD.Creator.Win32 created two partition 511MB and 32MB.
Both method doesn't seem happening for me. I believed i should have missed out some important step or confused with sequence.
My plan is to make the box with Kodi 18, prefer running on internal memory. instead of boot from SD.
Forgive me, i am newbie for Android. Need serious help here.
Burn image (LibreELEC-X8-X8H.arm-LE9-Kodi_18.3.img) to SD ! with the TOOL under downloads (Black Banner above) . ( I mostly run the SD burning tool as ADMIN!
how to patch the minix bootloader :
burn the GZ img to a SD
browse the SD and rename "boot_autoscript" to "boot.scr"
insert the SD in the minix
boot the minix while holding reset switch for 5 -6 sec (the bootloader will be patched) (little hole on the back - paper-clip worx fine)
let Libreelec boot and configure ssh, etc
restore your cfg if needed
After you boot to LE, connect to your box over SSH and run installtointernal command. This will copy LE from SD card to internal memory with all your data. (user will be root and password will be your password)
You dont BURN the image straight to the box
Hi to all
i need your help as new .I have Minix NEO X8 Plus and i am confused which image can download and install .
Also if this image can be install with SD Card
Thanks a lot for you help
"minix_x8_x8plus_x8_h_newbootloader_FW9.img" = what you need(I got the NEO X8 Plus also). I flashed mine with the burning tool, how to go with SD-Card I never tried that way as the burning tool never gave me problems.
i can confirm that setting display refresh rate to 50hz was the only thing helped with the box freeze when video was stopped and when amcodec was on,
however, video still freeze or stutter randomly....can be paused and replayed, but not played smoothly.
seems also there is a sync issue with audio.
installed latest 18.3 minix x8h-plus
display refresh rate is at 50 hz, resolution 1920x1080
adjust refresh rate is set to always
sync video is off
amcodec is on
other settings are on default
also, i'm having a problem with add-ons repo: connecting to LibreELEC Add-ons repository is not working
As soon as I apply "adjust refresh rate is set to always" or Start/Stop _ my x8h-plus will freeze during pause or stop, turning OFF "adjust refresh rate" and she' steady as can be. LibreELEC Add-ons repository I dont have a problem with as it works on the x8h-plus and the x8-plus for me. Both boxes on the latest 18.3.
This solution did not work for me, not in 18.2 and not in 18.3.
Only disabling HW acceleration works although i didn't play around with other settings (it's too annoying to reboot the device when it freezes).
I set refreshrate to 50mhz and leave hardware acceleration ON and it dont freeze up no more. Try and see if that works for you.
Everything plays smooth for me even mp4 etc.
if you dare , you may also try the dtb from the kodi 17.6 image.
use a spare SD 'cause it may not boot at all.
Tried it, boots up fine, worx but IP is random with every boot, fixed IP after reboot reverts back to DHCP .... Grrrrr.. anybody else ?
btw. for a Chinese box I thought we had the Elite with Minix compared to other garbage out there that are still supported with CoreElec (got a cheap x96"clone", build a fan for it and it runs like a devil with CoreElec 9.0.2.... Will never figure that out LOL
I hate to break the news but either way still reverts back to DHCP after a reboot... Got the "x8h plus with "X8H_PLUS_LOLLIPOP_RC2_NEWBOOT.img"(true shutdown) and I even tried a fresh install 18.2 from SD with the dtb.img replaced from 18.0(final) and still goes back to DHCP after reboot/shutdown. Lets wait to see for more feedback as I might have an "Odd Box". When I ran Kodi 17.6, the first image listed = one that booted and worked if that helps.
Ok replaced "dtb.img" from 18.2 with the one from 18.1, Packed it back in with 7zip and updated and still no cigar, fixed IP goes back to DHCP after a reboot. Am I replacing the right file as there is also a "meson8m2_n200_2G_old.dtb" .. ?
I just re-flashed my x8h plus with X8H_PLUS_LOLLIPOP_RC2_NEWBOOT.img, but I can see only black screen after switch on.
is this behaviour OK?
When I flashed my X8h Plus it took at least 5 minutes to build up the "system caches", so patience is needed.
Depending on how the bootloader code is setup this probably is a byproduct of some of the current popular methods of creating a multi-boot and because of the way u-boot has been altered to handle this type of multiboot. If the internal u-boot sees the card it thinks it needs to use it to pullup the system and run from there.
Other methods of creating a multi-boot that use different code in u-boots monitor to set things up different so it can realize to just treat the sd card as external flash can be done as well tho.
Not sure why so many people have problems with changing ip's and mac's tho as i have never had those issues and at any given time i probably have a least 6 boxes or more running on my network. Personally i always use static IP's and once set they never change as well as the mac's i set. Normally i just set them in a script that runs once the box boots up but i have also slipped streamed them into the box's u-boot as well and they always seem to stick...
Please educate us
@lieuandy you are right about the X8h-Plus Kodi 18.2! The the fixed IP is not working with 18.2, so you are not the only one with this. MAC is random with me but who gives a hoot on that So with 18.1 fixed IP was fine with reboot, shutdown etc.
Sad news about the amlogic datrh ... Thought rockchip was the one to dissapear but guess not.