K200_Noob

Its the uboot environmental variables that controls the fw settings. this will be needed if you want to install it to your internal memory. The best experience is when it runs from internal memory. its awesome. since you have the TWRP backup you can always restore android. To fix that need to paste "lsblk" block information from running armbian. From your android system backup in the /etc folder you will need to get the fw_env.config file.

Excellent. You have the proper fw_env.config? try running fw_printenv...

this one has been reconverted AMLOGIC_8726_M8.dtb

here you go....Red2-dtb.zip

It's a K200 without a revision. Try burning image to SD once more and try again. Possibly an issue with SD card. I will send you a TWRP later today which you could use to backup your firmware and we can extract your DTB file. UPDATE: the attached is the TWRP recovery for k200 boards. you need to put it on sdcard and use toothpick mode to get to recovery. will help to backup your android system. recovery.img

you will have to load up android and see the details or you can download and run cpu-z and see board details. example below. may not even be a k200? - post a screenshot of yours

Hello, Anyone know if this works with s905X3 with HW video decoder. Planning on getting a box to convert to Armbian running on emmc? appreciate any input please..

find your box recovery button. use toothpick mode to activate. using update method does not always work. watch this:

that sounds promising. Whats is the make and model of your box? is it k200b or c ? and way to find android firmware online? i would also suggest reformatting sdcard and reburning it else use another sdcard, run a dmesg on your computer. if you get a sdcard was not unmounted correctly, run sudo fsck -fy /dev/mmcblk0p1 and do the same for p2 depending you you system...seek by lsblk

Try this. Rename it it to dtb.img and put it in the boot partition of 5.4.4 m8_k200_sdio.dtb

I am sorry for your troubles.. when you have it restored, take a look at page 11 of this post and do a search for the word wetek... chataigne73 April 5, 2018 Hello balbes150 I'm trying to use your armbian s812 builds on my device : it's a Wetek Core, with Libreelec installed on nand. From what I understand, I'm in a particular case since my box already supports booting from sdcard, but it doesn't work for your builds (sdcard not seen as bootable by my box). So, I applied your autoscript to activate universal multiboot. Now my box detect your builds on sdcard (not on usb), boot on it but is stuck (with screen no signal) with every dtbs I tried. I think the wetek proprietary multiboot script is in conflict with your. Here is my fw_printenv ... thank you if you can help me : Reveal hidden contents Edit : I manage to boot by using dtb and uimage of libreelec for my device (3.10.99) Balbes : can you repost old 3.10.99 debian or ubuntu links ? they are no more on your yandex

just use the dtb that was not in the zip folder as your dtb. it has be converted. the zip is the original extract that contains the kernel file. as a backup you can keep.

if you are going to change it to dtb.img use the 5.44 img to start with.

attached are the files i extracted from the boot img of your device. dtb.zip m8m2_n200C_2G.dts m8m2_n200C_2G.dtb

Ok since that is the case, we will need to follow @balbes150 instructions to get it activated. Let me share with you want i was referring to first; Below are the ones from my device; notice that the mtdblock0 is the bootloader and the mtdblock1 is uboot env. I am reading this while booted from internal memory so it does not have a label but did when i booted from the sd card, using; /dev/system as my boot partition /dev/data as my root /dev/cache as my cache I was looking at post which i wanted to adopt for my box to switch the partitions around and boot into LE or linux using below...its a work in progress; Looking at the link @balbes150 posted, you will need to activate using sd card, I may have look some more into it. I would however suggest reading through that forum. I could not find the aml_autoscript. I will try to ping @balbes150 for help. edit: tried to ping him but says he does not receive msgs. perhaps inbox is full. Check out this post #317; https://forum.libreelec.tv/thread/12330-test-libreelec-images-with-kodi-19-for-s9xxx/?postID=106454#post106454

we can always extract it from your android firmware, the one for your device. attached is an example. is it meson8m2_n200 or n200c? libreelec-fw_printenv.txt

android does not allow fw_print env. you can do both (cat and fw_printenv from LE). it wont change anithing to the uboot env. we just explore

I keep hearing which DTB would work with which image when it should be 1 DTB for you box for all images; A device tree is a tree data structure with nodes that describe the physical devices in a system. Helpful Info: https://elinux.org/images/f/f9/Petazzoni-device-tree-dummies_0.pdf

Hey, you seem to be on the right track and @balbes150 has the information for the wetek. and yes it would seem you have the multiboot. since i was not familiar with it i wanted to see how the kernel was being loaded to help you. if you have ssh then do "lsblk" from the commandline and you will see which mtd partition has the uenv or uboot env. mine is /dev/mtdblock1. i like to know what is going on behind the scenes and thats how i learn and helps me fix issues. Oh but wait since you have LE, you should be able to run this command which is more Human Readable "fw_printenv" If you want to learn truely friend...this is where the fun begins!!!! The real satisfaction in getting something working is knowing how you did it

sounds like a .dtb issue. What dtb file are you using? what android version is it running? if you have your stock boot.img use this script command from same folder as your boot.img - ./extract-dtb.py boot.img it will create a folder with all your dtb files. extract-dtb.py

The Kernel version is at the end right before the date compiled. 3.10.108 - 2019 March 26th. All the images are compiled by @balbes150 not familiar with your device, but do you have a terminal and can you "cat" the uboot environment and paste here? if LE was started from SD card then using the aml_autoscript should get you going. if you fail with 5.44 give 5.77 a try due to the output mode. i believe "firmware-aml-s812_5.73_armhf.deb" was a deb package was for the image 5.73 to be installed for missing binaries if not mistaken. image 5.77 should have it all in the image file. I personally started with 5.44 to get things kick started... before you get started, do you have a backup of the ROM or the factory firmware and aware of recovery if things go wrong. I had an SD image of the stock firmware which i could recover my box with? - my recovery image allowed me to recover the bootloader too.

from one noob to the other, i dont see why not. its similar to the 812 with an addition of Dolby DTS from what i read. is it rooted? when you say kind of linux do you mean android 5.1? also it is true LE or are you referring to Kodi?

what have you tried so far?

Much simpler would be...Every Armbian image for the s802/s812 comes with it in the boot partition. When you burn the *.img to the SD card, turn on your box with the recovery button pressed in using the toothpick method. you do have a recovery button? the boot logo flashes once then let go of the button and should flash once more on its own. you will hear a faint piezo tone from the box when it flashes..but those are details. just watch for the logo flashing off and back on. and you're set.

05-31-2017, 09:50 Updated images Armbian 20170531. Changes to scripts activate the multi-boot and run system from external media. In the new version of the scripts allow to start the system from any USB socket (if the is connected other USB media). Back support "nodm", now in the images is used in common with the main branch Armbian authorization system. If you want you can install the package "lightdm" in version Mate-that-be to have a graphical authentication when you log into the system (just don't forget together with the installation of lightdm, remove the nodm package, otherwise they will interfere with each other). Other changes see the description of changes to main branch Armbian (replacement browser on Chromium, etc.). New scripts activate the multi-boot and system start-up can be found here. You can download them and use for old images. To reactivate the multi-boot again. https://yadi.sk/d/cEPIULGW3Jgpee https://yadi.sk/d/QCGU0PIv3G5kEa New script to activate the multi-boot on the Minix models H8x and H8x plus. https://yadi.sk/d/BU_pyfHW3JgpEP https://forum.freaktab.com/forum/tv-player-support/amlogic-based-tv-players/s812-aa/tronsmart-aa/620898-linux-for-amlogic-s802-s812/page3