Igor

... but by observing this patch and doing some search and reading results, one can add new screen resolution on his own.

We are trying hard not to break anything since dealing with users is our direct cost. You are asking for my personal time for free, remember this. If you would find a serial console, we might be able to provide you hints for recovery ... some generic you can also find here and you will not waste your time in first place. 
 
 

Armbian is the one if not the only one that provides such updating in a first place. On most others, this is the only way.

Update. CMS backend is fully operational at this stage, tested and actual data is slowly moving there, frontend early WIP, sorting at download selection is not finished, the download page is also in making.
 

Check below if this way is better. Exceptions - like a partially broken or slow SATA can be added as one of the device issues or we only expose known working features and strictly forget about crippled ones? WIFI on Opi Zero, Sata on some Oranges, ... ?
 

Solved. This is how adding a device looks like.

This is how editing a kernel looks like:

This is copy paste from the internal manual "how to add things". It might trigger valuable questions if backend needs more changes, something important was left out or this how-to is unclear:
 
 

You don't have any better alternative. Other builds are not even on this level. I would not say we are in the early development. Just development. To my observation, it looks like those stability issues are tied to some particular board revision(s). Some work good. 
 

The development team is exhausted and we don't receive help not even for simple tasks which we ask 
https://forum.armbian.com/topic/4089-espressobin-support-development-efforts/?do=findComment&comment=49271 (taking some responsibility) https://forum.armbian.com/topic/6420-preparing-for-ubuntu-1804/ (copy pasting and test)  

Oh well, my main objective was achieved as long as libreoffice impress works fine as I'm donating it to my church for them to do presentations. Thanks anyways, I donated to your project because it's very good. Best wishes to you and your team.

Forget about changing u-boot, replace rather boot script. It is more simple and actually the fix for the problem.
 
1. Boot with SDcard
2. Mount /dev/mmcblk2p1 /mnt # on some cases it will be mmcblk1p1
3. cd /mnt/boot
4. wget https://raw.githubusercontent.com/armbian/build/master/config/bootscripts/boot-sunxi.cmd
5. mv boot-sunxi.cmd boot.cmd
6. mkimage -C none -A arm -T script -d boot.cmd boot.scr
7. power off,
8. remove SD and boot from eMMC

I just got my board and I'll try to make Armbian ASAP. 

Another pcs of info -  when running 
./cpuminer --benchmark I get a 0.9A draw at the power source. Nothing else except console is attached.

I figured out what the problem was finally. But still unsatisfied.
 
I went back to bananian and checked to see if USB's worked for keyboard/mouse, they did not. I remembered I used a powered usb3 hub for bananian to get my external hard drives working. So I plugged the powered usb3 hub to the banana then plugged in the usb adapter for keyboard and mouse on the hub. They worked then. I'm guessing the  banana  isn't able to give enough power to power the mouse/keyboard adapter. I'm going to try armbian ubuntu again and see how things go.
 
This is the usb hub i used: https://www.amazon.ca/ORICO-Aluminum-12V2-5A-Adapter-3-3Ft/dp/B00BIDTU04
 
WIthout the hub, when I plug in the mouse/keyboard adapter I get the message: unable to enumerate usb device on port 1
 
Edit: I've confirmed that no power is going to the usb ports. I'm gonna go look through the banana pi m1 schematics to see if I can somehow do some soldering magic to route power from the microusb port to the USB ports.  Thanks for all the help.

@Igor I'm going to roll back the Tinker S board ID patch until I can get more information (GPIO errors all over the place) and we should be good for a new image.  The bluetooth service still doesn't work, I even checked the ASUS one, so I'm not surewhat's going on there, I'll try their rtk_hciattach quickly tonight to see if it is somehow better. (the one I've included works on the command line with no issues, but won't load properly with systemd)
 
 

(gserial) Serial console is enabled on OTG port. You can't see boot messages, but you can login when board boots up.

Look for links with "default" in the name ...

https://github.com/armbian/build/commit/f6402803c261b7a683eeb091f62a684bfd1ef8e8
https://github.com/armbian/build/commit/518ef98107a6705ba6649acdb1481cafedc9766d

Software support is not fast food.

https://github.com/armbian/build/commit/f6402803c261b7a683eeb091f62a684bfd1ef8e8
https://github.com/armbian/build/commit/518ef98107a6705ba6649acdb1481cafedc9766d

Software support is not fast food.

https://github.com/armbian/build/commit/f6402803c261b7a683eeb091f62a684bfd1ef8e8
https://github.com/armbian/build/commit/518ef98107a6705ba6649acdb1481cafedc9766d

Software support is not fast food.

Thanks for the help.
My device doesn't work with the flash-image-1g-1200_750_boot_sd_and_usb.bin image, but the 1000_800 does work just fine.
 
Even the SATA-Card works now. Thanks again! Cheers!

You should pick exactly the one you have now. There is no speed increase but you ended up this way  Good point is that this board is unbreakable. One way to recover is this: http://wiki.espressobin.net/tiki-index.php?page=Boot+ESPRESSObin+from+SATA+drive and second option is via UART which is more complicated. 
 
When you are back, repeat flashing SPI, move jumpers back ...

interesting.. OK then I think I´ll try that on a different board as I have one lying around somewhere, and if it works on that maybe I´ll try reinstalling the "faulty" one. But apart from this I have zero issues with it, so I can live with it. 
Thank you for testing! 

Change it in /etc/default/nodm

Download older version and not update. You are using development image which comes without end user support.
 
Hint - DTB file is not in right location: 
ERROR: Did not find a cmdline Flattened Device Tree

@Igor feedback so far has been quite positive, let's wait until next week, I am in Mexico on business and so I don't have access to my pc/tinker.  I would like to take another shot at sound and Bluetooth before we release new images.  @zador.blood.stained's Bluetooth scripts/service for the 8723bs should work, but don't, so I am a little in the dark on what the rockchip wireless subsystem might be doing.  

USB/SATA installer with boot from SPI also works.
https://github.com/armbian/build/commit/69ccc04e88872b75bf6d70cc1e32cce483f3cf25
It's plan to move the board under stable ... but we need some help. With maintaining. Since our board count is huge, it already took days before all boards are tested (at major release), sometimes we skip certain and then Murphy law strikes
 
Roles are not strictly specified and nothing special is planed. We seek someone, who is up2date with development status, has a spare board for testing and is willing to update "known issues" or add specific tips for this board on the (new when ready) download page. Also, do testing when major updates are planned.

Any volunteers? 

I installed the new version which you uploaded and told me, thank you very much :)) The bluetooth works and I could connect my keyboard with this ways;
 
sudo bluetoothctl
agent on
default-agent
scan on
pair xxxxxxxx
and I entered the pin on my bluetooth keyboard.... 
 
thank you very much everything @Igor:))))

We made this tool with the purpose to make kernel recompilation as easy as possible. In just about every other way you have many potential obstacles to overcome. All those Youtube guides are usually made for Intel world/perfect scenarios where things just work. ARM variety is big.
 
You need some x86 desktop computer where you recompile the kernel in a virtual machine, transfer two .deb packages to your Tinkerboard via a network or via SD, install them with (dpkg -i package.deb) and reboot Tinkerboot into a new kernel. If you use our tools you have small chances to fail for anything else you need some experiences. It is possible to recompile kernel on your board, but ... you are on your own. Sources are accessible this way: 
apt install linux-source-4.14.14-next-rockchip Since you don't want that upgrades overwrite your own made kernel you need to freeze kernel updates (armbian-config) or send your changes upstream and they might be included in the kernel by default.

I don't have information how is the situation with CAN-bus with this kernel/Tinkerboard, so only some theoretical tips: in case you need to add a function, that exists but is not enabled, this would be a good and simple start:  https://docs.armbian.com/Developer-Guide_Build-Preparation/ 
 
Sometimes enabling a feature is good to go, sometimes you need to add a function with a code/patch. In both cases, you need to recompile the kernel (sometimes module only also work) from sources.