[S812] MIII Plus 2Gb\16Gb eMMC

Quote from doggyofone

OK, I formatted the SD card, then I used the downloaded .img.gz from 20170801, extracted the .img file and then burned that to the SD card. I did not remove or add any files to the card. Then I put the SD card into the box, used the toothpick method and nothing happened after 60 seconds. When I removed the toothpick the GoogleTV image comes up, then disappears after maybe 10 seconds and the 120 second/ automatic repair message appears on the top left of the box.

When I remove the card and boot the box goes into Android successfully.

I have attached a snip of the files that are on the card.

Note that I did use the update&backup app to install the aml_autoscript files prior to trying your method.

Thanks for your help.

Try a USB stick as every time i get the 120 seconds message it will only work on USB and not SD card

Yeah, there is something weird with the script that sets up the multiboot for these boxes. Also, the one from the balbes150 image does not work with the demetris image and vice versa, so it looks like there is not a standard approach to applying the multi-boot ?

On a positive note, the new image did work on a MXiii (S802 chip) by using toothpick method by SD but then inserting into USB to boot up. However, as I said, after doing this, the Demetris image would no longer boot from USB and the whole SD/Toothpick/Then_USB_Boot process had to be done again.

So I am wondering if the multi-boot thing could be looked at to get the SD card booting up and perhaps at least the method could be standardised ?

Quote from balbes150

Now record the same image on any USB flash drive. Turn off the TV box. Connect the USB flash drive and turn on the power of TV Boxing.

I kept getting the 120 second error, so I did what you said here. I wrote the same image to a USB stick and did the toothpick install - GoogleTV logo comes up and after ~30 seconds the box goes into recovery with a message that E: Cannot Load Volume /misc!

I tried turning off the box, inserting the USB stick and then turning on the box. Google TV logo comes up and the Android boots.

OK, I exited from recovery (the original MXIII-G recovery) and the box booted into LE. I'm not all that confident yet, but so far so good.

That didn't last very long. The box now reboots into Android no matter what method I use.

For all those looking for the .nocompat here it is:

nocompat.zip

Hello, balbes150 i like to say thank you for making these roms.

I can say that the LibreELEC-S812.MXIII_Plus.arm-8.0.2 and the LibreELEC-MXIII_Plus.arm-17.3_20170801 build are working on the minix neo8x-h.

There is a wired and wireless connection.

Only when booting up the device and the bootscreen comes up there is some text on the left side of the screen in the new version this is solved a bit with some less text is it possible to hide this so we have a nice clean bootscreen ?

Also when you shutdown the device and and you want to power it on again you need to pull out the power cable and plug it in again and then push the power button, is it possible to fix this?

Tronsmart MXIII Plus:

Unable to update from 07.07.2017 to 08.08.2017 using .tar file fails, error message about incompatible hardware. Forcing update using nocompat works and allows update to 08.08.2017 however bluetooth missing, "No Bluetooth adapter found"

Downgrading to LibreELEC-MXIII_Plus.arm-17.3_20170801.tar also has no Bluetooth. I have not tried a clean install of 01.08.2017 or 08.08.2017 to determine if Bluetooth support would work.

Attempting to downgrade from August 2017 builds to 07.07.2017 .tar file fails again with same message about incompatible hardware. Adding nocompat file to 07.07.2017 allows downgrade to successfully complete and bluetooth working again.

balbes150 - Could you have a look into why Bluetooth is missing?

Hi balbes150

I have been using your builds for a while now on my MXiii-G, unfortunately none of the later builds will boot from an SD card, I get the file system corruption message that several people have reported, this is the same for an upgrade or a fresh install.. I tried again yesterday with LibreELEC-MXIII_Plus.arm-17.3_201708016 and that was the same, a fresh install did not work, file system corruption, upgrading a working SD card with this build also gave the corruption message.

If I put the image on a USB stick I can boot the later builds however this is far from ideal for me or a lot of other people, most of my USB sticks are old and VERY slow (5Mb/Sec) making things unusable

The last version to work correctly with an SD card was LibreELEC-S812.MXIII_Plus.arm-17.3_20170622 , is there any way you could look to see why this works and later builds do not, you would make a lot of us happy fixing this

Best Regards !

balbes150

Clean install of LibreELEC-S812.arm-17.4_201708018-MXIII_Plus.img.gz and I'm happy to report all working well including Bluetooth.

Big Thank You

Can someone post the latest file here for download for me please?

Quote from azazell64

Can someone post the latest file here for download for me please?

Go to the first post in this thread and you will find a link to download the latest build.

Anyone can help me to run the balbes150 new images from sdcard??

Thanks in advance

Hi,

Non booting from SD still (22/08), hopefully some info that will help, this is from an earlier balbes150 release, MXiii-G Plus (2/8)

Livingoom:~ # fw_printenv
baudrate=115200
bcb_cmd=bcb uboot-command;
boardname=m8_board
bootcmd=run start_autoscript; run storeboot
bootdelay=1
bootfile=boot.img
bootfromnand=0
bootfromrecovery=0
bootm_low=0x00000000
bootm_size=0x80000000
bootpath=u-boot.bin
bootsize=100000
bootstart=0
check_rebootmode=get_rebootmode; clear_rebootmode; echo reboot_mode=${reboot_mode};if test ${reboot_mode} = factory_reset; then defenv; fi;
chipname=8726m8
console=ttyS0,115200n8
cvbs_drv=0
cvbsmode=576cvbs
display_bpp=24
display_color_bg=0
display_color_fg=0xffff
display_color_format_index=24
display_height=1080
display_layer=osd2
display_width=1920
ethaddr=00:15:18:01:81:31
factory_reset_poweroff_protect=echo wipe_data=${wipe_data}; echo wipe_cache=${wipe_cache};if test ${wipe_data} = failed; then run prepare; run storeargs; run recovery;fi; if test ${wipe_cache} = failed; then run prepare; run storeargs; run recovery;fi;
fb_addr=0x07900000
fb_height=720
fb_width=1280
firstboot=1
gatewayip=10.18.9.1
get_dt=checkhw
hdmimode=720p
hostname=arm_m8
initargs=rootfstype=ramfs init=/init console=ttyS0,115200n8 no_console_suspend earlyprintk ramoops.mem_address=0x04e00000 ramoops.mem_size=0x100000 ramoops.record_size=0x8000 ramoops.console_size=0x4000 androidboot.selinux=permissive storage=2
initrd_high=60000000
ipaddr=10.18.9.97
loadaddr=0x12000000
loadaddr_logo=0x13000000
netmask=255.255.255.0
normalsize=400000
normalstart=1000000
outputmode=720p
p0path=uImage
p0size=400000
p0start=1000000
p1path=android.rootfs
p1size=8000000
p1start=1400000
partnum=2
preboot=run factory_reset_poweroff_protect;if itest ${upgrade_step} == 3; then run prepare; run storeargs; run update; fi; if itest ${upgrade_step} == 1; then  defenv_reserve_env; setenv upgrade_step 2; saveenv;fi; run check_rebootmode;run prepare;run storeargs;run update_key; run switch_bootmode
preloaddtb=imgread dtb boot ${loadaddr}
prepare=logo size ${outputmode}; video open; video clear; video dev open ${outputmode};imgread res logo ${loadaddr_logo}; unpackimg ${loadaddr_logo}; logo source ${outputmode}; bmp display ${bootup_offset}; bmp scale;
reboot_mode=normal
recovery=echo enter recovery;run bcb_cmd; setenv bootargs ${bootargs} wipeinstaboot;if mmcinfo; then if fatload mmc 0 ${loadaddr} recovery.img; then bootm;fi;fi; if usb start 0; then if fatload usb 0 ${loadaddr} recovery.img; then bootm; fi;fi;if imgread kernel recovery ${loadaddr}; then bootm; else echo no recovery in flash; fi;
sdc_burning=sdc_burn ${sdcburncfg}
sdcburncfg=aml_sdc_burn.ini
serverip=10.18.9.113
start_autoscript=if usb start; then run start_usb_autoscript; fi; if mmcinfo; then run start_mmc_autoscript; fi;
start_mmc_autoscript=if fatload mmc 0 11000000 s805_autoscript; then autoscr 11000000; fi;
start_usb_autoscript=if fatload usb 0 11000000 s805_autoscript; then autoscr 11000000; fi; if fatload usb 1 11000000 s805_autoscript; then autoscr 11000000; fi; if fatload usb 2 11000000 s805_autoscript; then autoscr 11000000; fi; if fatload usb 3 11000000 s805_autoscript; then autoscr 11000000; fi;
store=2
storeargs=setenv bootargs ${initargs} cvbsdrv=${cvbs_drv} vdaccfg=${vdac_config} logo=osd1,loaded,${fb_addr},${outputmode},full hdmimode=${hdmimode} cvbsmode=${cvbsmode} androidboot.firstboot=${firstboot} hdmitx=${cecconfig}
storeboot=if test ${reboot_mode} = charging; then run try_auto_burn; fi;secukey auto;secukey write keyexample 1234567890; echo Booting...; run bcb_cmd; if unifykey get usid; then  setenv bootargs ${bootargs} androidboot.serialno=${usid};fi;if unifykey get mac; then  setenv bootargs ${bootargs} mac=${mac};fi;imgread kernel boot ${loadaddr};bootm;run recovery
switch_bootmode=if test ${reboot_mode} = factory_reset; then run recovery;else if test ${reboot_mode} = update; then run update;else if test ${reboot_mode} = usb_burning; then run usb_burning;else if test ${wipe_data} = failed; then echo wipe_data=${wipe_data}; run recovery;else   fi;fi;fi;fi
testaddr=0x12400000
try_auto_burn=update 700 750;
update=run usb_burning; if mmcinfo; then if fatexist mmc 0 ${sdcburncfg}; then run sdc_burning; else if fatload mmc 0 ${loadaddr} aml_autoscript; then autoscr ${loadaddr}; fi;run recovery;fi;else run recovery;fi;
update_key=saradc open 0; if saradc get_in_range 0 0x50; then msleep 50; if saradc get_in_range 0 0x50; then echo update by key...; run update; fi;fi
upgrade_step=0
us_delay_step=1
usb_burning=update 1000
vdac_config=0x10
video_dev=tvout
wipe_cache=successful
wipe_data=successful

Livingoom:~ # udevadm info /sys/bus/sdio/devices/sdio*
P: /devices/platform/aml_sdio.0/mmc_host/sdio/sdio:0001/sdio:0001:1
E: DEVPATH=/devices/platform/aml_sdio.0/mmc_host/sdio/sdio:0001/sdio:0001:1
E: DRIVER=bcmsdh_sdmmc
E: MODALIAS=sdio:c00v02D0d4330
E: SDIO_CLASS=00
E: SDIO_ID=02D0:4330
E: SUBSYSTEM=sdio
E: SYSTEMD_WANTS=brcmfmac_sdio-firmware-aml.service
E: TAGS=:systemd:
E: USEC_INITIALIZED=24916479

Hi,

Thanks for the info. I´m going to read and learn and maybe i understand how to change the new image.

Thanks

Quote from Xeroke

Anyone can help me to run the balbes150 new images from sdcard??

Thanks in advance

Download Rufus and write LibreELEC-S812.arm-17.4_20170822-MXIII_Plus.img.gz file to SD card

Quote from 7up

Download Rufus and write LibreELEC-S812.arm-17.4_20170822-MXIII_Plus.img.gz file to SD card

If only it were that easy

For myself and others the later builds will not run from SD, something has changed in the Autoboot that causes a filesystem corruption error. For example a working installation of LibreELEC-S812.MXIII_Plus.arm-17.3_20170622 will break with the corruption error when I try to upgrade to LibreELEC-S812.arm-17.4_20170822-MXIII_Plus, a fresh installation also fails with the error.

I have refreshed the Autoboot as advised, looking into the output of fw_printenv this looks to be installed, however still no boot....

There was the comment made that it is the SD card at fault, if this is the case how come the previous installation works OK, AlexElec installs and runs fine, the Demetris builds boot ? I've also tried a dozen or so different cards all to the same effect

I confirm. AlexElec boots and installs fine on this box

Wired network works fine. Wireless I dunno cos I have not tried and I'm not interested. Media play fine. Too bad it's in Russian and it's a bit of a pain to set Kodi in English but hell, it's manageable.

I generally install to SD card but as I couldn't find adapter I used burned 201708018-MXIII_Plus.img.gz file to USB stick. Now that I think about it, the initial boot might have come up with a black screen or flashing video but after a hard reset and the MXIII Plus booted up normal. Not wanting to run off USB, I used the shut down menu to install to internal hard drive. If I can find my SD card adapter I'll try install to SD card but not sure why it would be any different.

I had no success booting with the balbes150 images on my MXIII-G 2g8g, so I went back to Demitris's build to see if I could get his image to boot. After some experimenting I was finally successful and now have a working image for version 8.2 RC2. The method I used for success was unusual, but was the only way I could get things to work. If you are looking for working images you should check Demitris's thread and you can refer to my instructions here:

S802/S812-Libreelec images for 7/8/x

Hope this helps.