RaptorSDS

Hey everyone, I updated my guide on making Docker work here https://github.com/SLAzurin/armbian-aml-s8xx-kernel-build-steps
(For Ubuntu/Debian on linux version 5.10)
 
@balbes150 The previous comment for Docker requirements is wrong.
These here are the only config you need to enable to make Docker work when you build the linux kernel.
CONFIG_POSIX_MQUEUE=y CONFIG_POSIX_MQUEUE_SYSCTL=y I hope you can add it successfully for the next release, thank you for your work.

please look at page 33 @jock and a @gnusmag45 have this topic about the JWA60 memory its a eMCP Memory
 
 
https://forum.armbian.com/topic/12656-csc-armbian-for-rk322x-tv-boxes/?do=findComment&comment=124401

please look at page 33 @jock and a @gnusmag45 have this topic about the JWA60 memory its a eMCP Memory
 
 
https://forum.armbian.com/topic/12656-csc-armbian-for-rk322x-tv-boxes/?do=findComment&comment=124401

i have a backup of my android 6 (multiboot) but i do not had  extract the dtb from Android -> some amazon reseller are als sold this box with android 8 ( but i have not found any update rom from android 6 to android 8 )
 
thats the one from me android 6
https://www.amazon.de/Neueste-Leelbox-Q2-Android-unterstützt-Schwarz/dp/B074PX2T9R
 
same box with android 8
https://www.amazon.de/Leelbox-Android-Volles-H-265-Version/dp/B07PHK9N31
 
last website from leelbox(i do not now if this original leelbox website , leelbox-tech is close )
https://www.leelbox.blog/tag/firmware-update/
 
some android 7.1
https://www.leelbox.blog/2018/05/23/prime-video-not-working-try-to-update-firmware-for-leelbox-rk-chip-android-7-1-tv-box-via-pc/

hi and welcome
 
when Armbian 5.67 boot  fine , multiboot is active.
 
for Armbian later 19.xx than  you have to edit path and filename inside  ambianEnv.txt. you do not not need copy and rename
 

for 1 - ok only nand thats ok
for 2 - please ignore i did not know multitool can handle gzip/XZ/tar and that the fat partition should be bigger ( its was maybe a bug that my sdcard had only 800mb fat partition)
for 3 - i work most of the time in CLI so "nano" it what i know  feel free to use "vi" , thats my personal thought to change order and modifcate armbianEnv.txt direct after "rk322x-config"

for 1 - ok only nand thats ok
for 2 - please ignore i did not know multitool can handle gzip/XZ/tar and that the fat partition should be bigger ( its was maybe a bug that my sdcard had only 800mb fat partition)
for 3 - i work most of the time in CLI so "nano" it what i know  feel free to use "vi" , thats my personal thought to change order and modifcate armbianEnv.txt direct after "rk322x-config"

@xaleks
First there is no A to Z guide how to make this android to linux box , because there are many diffirence between the box . feel free to write one
 
Download link to the Armbian version I need to try and dtbs I should attempt to use?
somewhere in this thread armbian.com/linux/balbes  ( last 3 pages)
 
How to boot from the SD card (I assume this is the tooth pick method)?
toothpick is only to get to recovery partition / recovery tool
you also have to find a way to install the aml_autoscript , this script activte the multiboot option on bootloader for usb and sd-card boot
( i had to sideload TWRP from sd-card to  temporary recovery and than replace recovery with twrp, install the aml_autoscript and also root the box)
 
 
 
Where to solder a uart bridge (I'm using my bus pirate for this) for uart?
look at the lower section on your picture. Are there the mark for RX;TX and GND ?  maybe look at the other side of the board !  ; What is a bus pirate ? you need a uart rs232 to usb ( be aware you need maybe 3,3V UART adapter )  that enough,
 
dtb
there are some in the armbian boot section for testing , there is also a mxii.dtb

hi and welcome
 
there is no a to z guide how to get linux to the box because like i wrote before therer a big mix of diffirent boxes ( 3 diffferent wifi chip , 3 or 4 different Lan chip) also most of the armbian community only work with and on open source or community Software.
 
ubuntu is a linux
armbian is ubuntu linux or debian linux with tools and setup for small space envoirments
 
 
its possible to run this box as a slow NAS ( only USB2 support ; most of the box only has 2.4GHz Wlan N ) ; Plex or Media box still a problem because the media recode is not optimal ( lag of graphic driver)
 
 
i thing on page 24...26 i wrote some steps  ( but feel free to write a guide ) be
 
balbes150 has stop his work on this Amlogic Armbian release but there are some work on the linux Kernel for AMLOGIC chipset but its slow .
 
 
there are 3 main steps
1. get the bootloader unlock for multiboot with the aml_autoscript.zip from Android or from TWRP
2. get the armbian on a SD-Card (  beleanerEtcher or ImageWrite32 )
3 get the right setup to boot linux ( dtb files)
 
 
 
 
 
 
 
 
 
 

@jock also emmc-nand produce the error ,  i can boot only    without any of the 3 settings

for 2 i do other way i underclock the cpu because of my opinion too hot cpu
@jock i got my box to a 100% load on all 4 cores  from bug webservice its run at 85 degree stable with 1.2Ghz ( i dont know why last time ( first time with linux after switch from android) at 75 degree the box freeze and short after black screen maybe it wasnt a thermal problem .
 
for 3.
i have same problem with UUID , but for me its was only to delete the emmc or nand or emmc-nand part from the armbianENV, the rk3229 and the ledconfig1  parts work great.
 
 
 
 
 
 
 
 

@AzuriAdore looks like timing problem at init at boot ( maybe usb host did not get right shutdown) thats why somethig thinks get deactivate with newer kernel first and than after test and beta back online
thanks for a guide for docker
 
@obaldon1sorry to hear that you frustrated , my first device for flash was a windows CE->XDA 1 , there is no step by step instruction because every android device is diifferent some have more secure features like software fuse and secure bootloader other have only non root user ,  but like azuriadore say you learn something in the 30h.
 
please dont waste your box ,
also please notice this is still a hack of a device someparts are still beta and not stable ,
also please notice this is not a windows device where your put your usb stick and one-click installer say hello i am windows installer , many things are still by adb-console and input commands into a black window
 
do you have a pc connection to your device ?
 

@obaldon1
 
maybe this help
 
1. root the box or/and install TWRP -> toothpick methode
1.1 maybe get debug output from serial port at board ( !!! soldering  !!, but its help a lot , Serial Console TTY)
2. activate Multiboot with aml_xx.zip for uboot bootloader at TWRP ,
3.use old or new Image
3.1 old image befor 5.xx Kernel take the right dtp from dtb folder to boot folder and rename to dtb.img ( Android 4.4 dtb files are more in common to Kernel 3.10.xxx dtb files ) 
3.2 new image 5.xx Kernel edit uEnv.txt and point to right dtb file
4 repeat step 3 with other dtb files if not boot  ( !!! dtb from 3.10.xx not working with 5.xx Kernel)
5 if something not working like eth or wlan remeber its beta or work in progress maybe to study to edit dts files help
 
@balbes150please PM me if something missing i edit  this post

@dreamstrider@SteeMan
thats because manything thange in the dtb files over the year -> dtb for 3.10.99 kernel was direct usable from android 4.4 ; ->dtb for 5.8 kernel many things are disable by default because of compatibili settings or get new interpreted ( i have the Realtek 23bs chip and in the old dtb it was a chip enable high in the new kernel i need a chip enable low) 
 
secound there are no nand install ( because of unknow uboot settings for new kernel to boot from nand; risk to brick the box is to high )  most of use use only sdcard or usb , i know that "xdarklight" has testet the nand driver in the 5.8 kernel but its still beta 
 
@obaldon1 thats correct u have to use the right dtb file in the uenv.txt ( normally when u use wrong dtb u should only the black scrren or color screen and not android boot when multiboot works )

@nirkon most all 5.x Kernel version (20.xx and NEXT) are without HDMI !! , its normal to have pixel logo because they only work with Ethernet(SSH) and/or Serial Console (SSH) also 5.x(20.xx ) and 4.x Version (19.xx) version need more time for first startup like 3 till 8 minutes , ( most times goes to timeframe 19.xxx secound and than you have to wait till login show up) ; for 20.xx and 19.xx version only need to edit uENV.ini !!.
at the old kernel 3.10 (version 5.xx) you need for hdmi the desktop versions and also have time for first start about 5 -10 minutes, this are the ones that use the rename to dtb.img trick !!

i test today but i have  problems to optain a ip addr from dhclient ,
 
i connect to my wlan ( iwconfig told me all fine) than i start dhclient and nothing ( i start and restart ntp deamon  but this time  no effect) .
 

i take a new SD Card
 
i got follow error
 
random stop at PWM Blue LED
some SD Card read error or maybe image problem
GPIO 32 error
 
log file att.
 
 
"your MEGA.co Link is password protectt"
 
kernel test 4.11 m8s dtb 2 .log
kernel test 4.11 m8s dtb.log

ok another reflash of sd card and dhcp client work , this time NTP start befor dhclient and run fine , now wlan internet  work.!!!!