Igor

If M3 image works on your board, you don't have T3+ but T3 ... or some other memory configuration. That is the only difference beside eMMC support.

Roughly: you need to have u-boot and kernel or its support in mainline. Official way: https://forum.armbian.com/forum/22-board-bring-up/ Unofficial way, fork the project and do what you want. If you made it properly, send it upstream.

Fix 8814au driver code or find such that it builds on a kernel 4.4.y. I use this patch to disable building 8814AU but build 8812AU. Unrelated to Armbian.

Probably it will not work out of the box (apt install ...) and will definitely be a step back ATM. We provide modern 4.19.y kernel for RK3328/3399 (linux-image-dev-rockchip64) for developers & testing. It is present only in a nightly repository ATM. It comes with no warranty or support. Generic ARM kernel is months behind this at best.

Not found yet but that doesn't mean it's not there. Without questioning it's worth at least as unofficial CSC testing images: https://www.armbian.com/bananapi-r2/ (only direct link for now).

You need to change u-boot as well when changing from old to new kernel.

You forget on most important data. Which kernel do you use? armbianmonitor -u And remember that this image is not declared stable yet since (such) minor issues weren't fully resolved yet.

Scrapped from tapes https://dl.armbian.com/orangepipcplus/archive/Armbian_5.30_Orangepipcplus_Debian_jessie_default_3.4.113.7z

Yes, we have seen this in the past. They change memory modules for example which need adjustments in u-boot. We use different one ... which is adjusted to support booting modern kernel. To be able to start solving this problem a few components are needed: know-how, time and hardware sample. Another strange thing is that my T3+ has the same revision numbers as yours - at least in mine there is: 1709, check memory chips. Sometimes they don't change revision number and change components. Haven't seen this at FA but elsewhere.

Here is the file you need: https://drive.google.com/open?id=1r1x2POUcrbASwGItrX0rAtYcfwmlNtgg

Via normal 3 wire serial port? MicroUSB serial console is enabled on H3/H5 stable builds, while here (development builds) you have to do make it if you want to use it.

If things are not in a repository (exactly this kernel is not), you need to use build engine and build it on your own. Armbian kernel is "just" up to one year ahead from kernel.org and some features might never be there. You need to apply those patches: https://github.com/armbian/build/tree/master/patch/kernel/sunxi-next to the kernel.org 4.14.y + this config https://github.com/armbian/build/blob/master/config/kernel/linux-sunxi-next.config

Not that I am aware of. I am noticing that delay between someone wish and realisation is sadly going over one year now - if thing is not critical. We are in a situation that like 1.000 people wants something, and gives virtually nothing, from a small project maintained by a few afternoon/part time developers. Fun is one of the biggest motivations for working on such projects. Do you think putting more pressure in this situation helps? Are we happy?

Nothing has been taken from the repository. Screen output tells only the obvious - that there is something wrong. Look into debug directory. You are on your own when you detach from HEAD. Armbian rootfs with stock configuration was successfully bootstrapped yesterday in all possible combinations: https://dl.armbian.com/_rootfs/

This board has status "WIP / suitable for testing". There is one FAQ at the device download page which explain this: SUITABLE FOR TESTING (WIP) are devices which we’re currently working on but they are not ready! These images are suitable for developers and experienced users. They are not very well tested but they might work without any problems. Your help to improve this situation is greatly appreciated. Bluetooth is known to not work since its not configured/enabled yet (it also has low priority) while for wifi this is something new to me. I did a few tests and it worked fine ...

https://github.com/armbian/build/blob/master/packages/bsp/common/usr/lib/armbian/armbian-firstrun-config

This should fix this issue.

In this case we only call @nachoparker install script from Softy menu: https://github.com/armbian/config/blob/master/debian-software#L523-L525

The same way as "20 years ago" - by defining configuration in /etc/network/interfaces If you don't put your network settings there, Network manager takes over.

It can be installed only on a clean Debian/Ubuntu image. Not just on Armbian. If you want to install this on top of some already installed software, OMV for example, this will 100% fail. Since you didn't provide any details what and where things went wrong we can't improve installer part (if the problem is there at all), which worked fine for me two weeks ago. It was hard to build this installer. I did one big part, while the other is 3rd party. It took years that process matured on a moving targets. It is very expensive to maintain all this which means there is almost no way that the same will be done for the uninstalling part. This suite is quite complex and its business support can be obtained here. It is part of the config because I am using it for my own purposes.

Che cazzo è questo? In inglese per favore.

https://github.com/armbian/build/commit/5eb3314ee84b501ef666f34f87ef89bd37fcb19f

I see you have keyboard at USB.

That default LED behaviour was changed. Most likely upstream. But board works, right?