I wasn’t sure that would be possible, otherwise it would defeat the whole point of the locked bootloader.
I’ve only stumbled on it because I totally broke my Android setup on there by fiddling with an Oreo downgrade.
I’m playing with the Debian stretch build of Armbian, and it seems to work fairly well, but I’d much prefer to go to CoreELEC. Kodi is failing for me with a Mali userspace/kernel version mismatch. Ugh.
Yeah, pretty much. I used a USB hub so I could also connect a keyboard too.
I had soldered some wires to the board for a TTL adapter so I could get access to uboot and the kernel messages which helped. It may actually not be necessary though.
I can dig up the link I found with more detail of anyone is interested.
I’m running a Debian 9 xfce environment, and it’s not bad.
I soldered my GND connection to the pin underneath the ‘R’ label for RXD in that pic. Then (on Linux) I used: cu -l /dev/ttyUSB1 -s 115200
to access the console.
As I said before, the 5.34 Armbian builds did boot successfully. Didn’t supply any dtb.img or anything. I think that the image on a USB drive should just work, but there was some info in that XDA thread about uboot commands. I think the aml_autoboot script should just take care of it.
Other Armbian builds look like they might have worked, but something might have been up with their kernels, as it looked like it loaded ok, but no console log or anything. Didn’t look into it any more than that.
Compared that to these LibreELEC and CoreELEC builds, I suspect they actually fail the kernel load process. The uboot logs are very different. I can provide logs if you’re interested.
I’m not the right person to help with that, just very interested in get rid of buggy androidtv on the MiBox.
But you should post those logs when you can. both the working Armbian and the not working Coreelec.
@anon88919003 Can you help? or point someone who could?
150balbes does not use git properly so he has made it extremely difficult to see what changes he has made in Armbian.
if you have access to UART by soldering a header then you should be able to interrupt the u-boot process and enter the commands in aml_autoscript and boot CE.
I don’t believe the bootloader is locked, they have probably just disabled booting from external unless you use the above method but without a device to hand then I would not be able to confirm this, I have been able to do this on another device though that was similar.
Maybe you are right, but I thought a locked bootloader is a requirement for getting DRM keys - and after unlocking the bootloader you will lose your DRM keys.
Would be great to have booth: CE with DRM keys and Mi Box would be the best 905 Box you can buy
I’m not sure on that but the Minix U9-H doesn’t have a locked bootloader and you don’t lose the DRM keys by installing CE or any other O/S as they are saved on a separate partition dedicated for them as are most if not all Amlogic devices.
Ah, I did not know that Box. But Mi Box has also Play Ready 3.0 + Google Widevine Level 1 and is half of the price. If it would be work with CE I would buy this Box instant
NOTE: I believe other Armbian builds do successfully load the kernel, but it fails from there, so I assume some sort of kernel/hardware problem and not a fault of the bootloader
Yeah, that’s the thing I don’t get. I never expected to boot anything other than the signed Xiaomi firmware, but that Armbian image does boot… so I’m stumped