SteeMan

Post back once you have tried the install using the instructions in the FAQ and let us know how things went.

The link you posted above is to a site not affiliated with Armbian. They have a fork of armbian but continue to use the Armbian name without permission. They do not participate in Armbian development, nor to they contribute to these forums. If you have any questions about their code, you need to direct it to them at their site. Overall you are comparing desktop from one provider to command line from a different provider. (comparing apples to oranges essentially). As for the Armbian build, please read the following TV Box FAQ post: https://forum.armbian.com/topic/16976-status-of-armbian-on-tv-boxes-please-read-first (The short answer is wifi doesn't work on most amlogic TV boxes with the Armbian builds - in fact not a single box I own has working wifi)

https://forum.armbian.com/topic/17106-installation-instructions-for-tv-boxes-with-amlogic-cpus

This doesn't look like any Armbian build. Where did you get this build? Also please read this TV box FAQ post: https://forum.armbian.com/topic/16976-status-of-armbian-on-tv-boxes-please-read-first (Note the parts about TV boxes not being supported and not to expect wifi to work.)

I'm going to close down this thread. I think everyone has had their say and we are at the point of repeating ourselves without adding additional value.

I moved your post to a new topic. But to answer your question, yes, you are going down the right path. What model TV box do you have?

If the dongle is well supported by mainline linux then it should be supported under armbian (you may need to install armbian-firmware-full)

The script is supposed to create the p0 and p1 partitions you say are missing: (from install-aml-s905-emmc.sh) ... mkfs.vfat -n "BOOT_EMMC" $PART_BOOT ... mke2fs -F -q -t ext4 -L ROOT_EMMC -m 0 $PART_ROOT

Since this should be a community, and I don't have access to a box that has your issue (both of my m96mini's work with the default dtb). I would encourage you to put together a PR in github for this change and contribute to the community. However instead of modifiying the existing dtb, I would recommend your patch create a new dtb for your box. It would also be helpful if you took pictures of the motherboard to see what chips you do have to be compared to what I have to see the differences. This could also be accomplished through a dtb overlay as well, but I'm not sure how that would work with the extlinux.conf file as standard armbian support for overlays uses the armbianenv.txt file.

The link you posted is to a site not affiliated with Armbian. They have a fork of armbian but continue to use the Armbian name without permission. They do not participate in Armbian development, nor to they contribute to these forums. You should direct your question to those that are providing you the code you are using.

You might want to consider either getting something that is supported or using a usb ethernet dongle. Otherwise you have a steep learning curve ahead of you. I've personally never needed to extract a dtb from android, so I can't provide any guidance beyond what I have mentioned above.

That script is fairly easy to follow the logic if you look at it. I don't have a s905 based box, so I can't test it personally. It would appear based on your report that the script misidentified the sd card as the emmc and overwrote the sd card (which is why you can still boot android), but that is just a guess.

Moved to separate thread

First please read the following TV Box FAQ post: https://forum.armbian.com/topic/16976-status-of-armbian-on-tv-boxes-please-read-first Second, of the three major TV Box CPU families (Rockchip, Amlogic and Allwinner) Allwinner has the least support within the community. There are a couple of allwinner knowledgeable people who occassionally post in this sub-forum, but there is little effort towards TV Boxes on allwinner cpus. Third, my best guess is that you need to either find or modify a dtd file to be specific to your hardware. If you are using the legacy linux kernel you might be successful in extracting the dtb from android and trying that one.

Providing logs with armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed.

They have forked from Armbian and added additional layers. They do not participate in Armbian core development nor post in the forums, so other than taking our code (which this is open source so that is fine), they have no relationship with the Armbian community. But because they continue to use the Armbian name, people come here for support, but since we don't make the builds or really know what they contain we can't support code we don't produce. Not necessarily. TV Box manufacturers have a habit of changing hardware (to produce the lowest cost devices) but reuse the same marketing names for the devices. The internal components can vary significantly and therefore a dtb may or may not work for any given box. Sure, that is what those builds are for. https://forum.armbian.com/topic/17106-installation-instructions-for-tv-boxes-with-amlogic-cpus

First please read the following TV Box FAQ post: https://forum.armbian.com/topic/16976-status-of-armbian-on-tv-boxes-please-read-first Second, of the three major TV Box CPU families (Rockchip, Amlogic and Allwinner) Allwinner has the least support within the community. There are a couple of allwinner knowledgeable people who occassionally post in this sub-forum, but there is little effort towards TV Boxes on allwinner cpus.

Since this is open source, changes to the documentation are gladly accepted. https://docs.armbian.com/Process_Contribute

Not sure where you got those instructions from, but given that they are for an ancient kernel version, there is no way they are going to work with current builds.

First please read the FAQ item on Armbian TV Box support: https://forum.armbian.com/topic/16976-status-of-armbian-on-tv-boxes-please-read-first Second, since you are not using armbian code (the location you downloaded from has no ties to armbian even though they use our name). You should ask support questions from where you downloaded your code.

First read the FAQ post about Armbian and TV Boxes: https://forum.armbian.com/topic/16976-status-of-armbian-on-tv-boxes-please-read-first Second, DTB files are kernel version specific since they are the mapping from the hardware to the kernel code. So you can't take a dtb from an old kernel and expect it to work on a new one (especially when the old kernel is a heavily patched/android based kernel and the new one is mainline - as they will have very different implementations of basic support for these boards).

I should have added a comment to this thread that I created a fix for this issue and it was pushed to mainline a few days ago.

Worked for me: [ o.k. ] U-Boot file name [ linux-u-boot-edge-nanopiduo_23.02.0-trunk_armhf.deb ] [ o.k. ] Kernel file name [ linux-image-edge-sunxi_23.02.0-trunk_armhf.deb ] [ o.k. ] Runtime [ 31:31 min ] [ o.k. ] Repeat Build Options [ ./compile.sh BOARD=nanopiduo BRANCH=edge RELEASE=jammy BUILD_MINIMAL=no BUILD_DESKTOP=no KERNEL_CONFIGURE=no COMPRESS_OUTPUTIMAGE=sha,gpg,img ]

This worked for me using current master branch: sudo ./compile.sh BOARD=nanopiduo BRANCH=current RELEASE=jammy BUILD_MINIMAL=no BUILD_DESKTOP=no KERNEL_CONFIGURE=no COMPRESS_OUTPUTIMAGE=sha,gpg,img

If you were to run this on a normal environment (it is designed to run on a PC (x86) running Ubuntu Jammy) you would see that at the end of the UI it prints out the command line equivalent of what you just entered through the UI, So the UI is only invoked if a particular parameter isn't passed on the command line. Experiment around and see how this works.