SteeMan

@mc510 It is still there: https://www.armbian.com/orange-pi-zero/

You missed my point. You choose the edge kernel version of the trunk versions. There are also vendor kernel versions. The vendor kernel is going to be more stable than the edge kernel.

You are choosing to use the edge kernel, which is the 'bleeding edge" development work area, it is expected to be unstable. If you want fewer issues you shouldn't be using edge.

The world of open source is all about reverse engineering things where manufacturers don't want to invest in openness. That is why Armbian exists. But it takes a lot of effort. Here are a couple of threads that show how the process works and the time it takes to do what you want without support from the manufacturer: https://forum.armbian.com/topic/24091-efforts-to-develop-firmware-for-h96-max-v56-rk3566-4g32g https://forum.armbian.com/topic/28895-efforts-to-develop-firmware-for-h96-max-v56-rk3566-8g64g

Rkdevtool has nothing to do with building working code for your board. You need to think of this as a coding project. You need to build something that is installable and runnable for your board. Nothing that exists is going to work on it. Each board requires a custom code set to boot and run in the arm world today.

@Sig That procedure is a one time this thing. If you pressed the reset button correctly it will have reset the boot loader environment. So remove the SD card and try booting without and SD card (that should be android as normal), then try the Armbian. If it doesn't work, try the reset process again (there is no good way to know if you timed the pressing and holding of the reset button correctly, except through trial and error). ( I generally find holding the reset for about 5 seconds while power is applied is about right, but too long or too short and it won't work as intended)

If you can't determine what device you have, there is no way you are going to be able to install Armbian on it. The world of linux on ARM is very different than linux on x86. There are no real standards for a boot environment and on board device management. For this reason you need an individual build for each device. One that has a boot environment that can boot the device and also a device specific dtb (device tree) that tells the linux kernel what hardware the board has. Those components need to be developed for each board at often the expense of many man months as the board manufactures have no interest in supporting the process of having mainline linux work on their devices. If you have the skills and resources to invest a very significant amount of time into such an effort, it can be done (if you have schematics and support from the device manufacturer that helps a lot). But the first step would be to open the device to get as the motherboard and understand what components you are working with. Then get a usb-uart connector hooked up and start monitoring the boot process to figure out how the device is booting (off of what media so you know where you are going to need to install a new boot loader to) Since the board is running android (which is only enough like real linux to get in the way generally), what comes installed isn't going to be very helpful in your process.

You do not supply enough information about your issue. First off what SBC are you working with. Armbian builds are specific to each device. Second what build are you attempting to use?

Moved to what I think is the correct forum.

What build and instructions are you using? https://forum.armbian.com/topic/33676-installation-instructions-for-tv-boxes-with-amlogic-cpus If you are using the above instructions, note the first sentence about having ever run another distro on the box. If so a reinstall of the original android firmware is required to reset the box to a unmodified state (I point this out as you say you have run emuelec on the box - and yes running from sd card counts as running on the box).

Why are you expecting these services to be pre configured for you out of the box? Any file sharing service is a potential security hole, so any good distribution isn't going to have them enabled by default.

Google how to install/setup samba for file sharing on Linux.

Have you installed and configured samba?

Debian Buster is end of life. There haven't been any armbian updates for a long time. You can ignore the error as there are no updates to get. You really need to upgrade to a supported Debian release.

According to your logs, Your board is an Orange PI PC not an Orange PI One. Moved to proper forum, and assigned the appropriate tag. Note: The Orange PI PC is not supported by Armbian. It is Community Maintained.