SteeMan
-
Posts
1453 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by SteeMan
-
-
What build are you using?
-
What does your post have to do with Armbian?
-
You don't need to transfer a .img. You use apt update/upgrade like any other Linux system.
You can test other dtb files, but I would recommend testing those from the SD card to verify they work. If you test on the EMMC and you do something wrong, then it won't boot and it will be a pain to fix. This the recommendation to do everything on SD card first to make sure you are happy with the system before moving that configuration to emmc as a last step.
ddbr is a very simple utility. I don't know if it is properly documented anywhere, but you can do an internet search to see discussions about it.
-
-
If you have restored the android firmware, then follow the instructions in the FAQ and report back what you have done and any issues you run into (screenshots of errors during boot if appropriate)
-
So to proceed we would need to get Armbian running on your box, first before asking about HA.
Since you have run various other os's, the first note in the instructions is relevant. You need to restore the box to a factory android firmware first before proceeding. Each is will change the boot environment in potentially incompatible ways. So you need to start from a known clean environment, by reinstalling a factory android firmware.
-
The entire system is now in your EMMC storage, so you just upgrade from there, no need for SD card going forward. Although it can be convenient to boot front an SD card, use the ddbr command to make an image backup of the EMMC once you have everything configured that you can always rollback to if necessary
-
In general I would expect the root parameter to look like:
root=UUID=997635c3-00f2-4eca-aa3d-1bf187651ea3
or
root=LABEL=armbi_root
(obviously with the correct LABEL or UUID for your root partition)
-
What dtb are you using? what uboot are you using? what menthod to invoke multiboot are you using? Have you used any other build on this box? In order to help you, you need to provide every detail of what you have done. You originally posted this in the HA thread. So I was assuming that you at least had basic armbian running and you were trying to install HA on top.
-
So you mention the ophub builds. Just so you know those builds are not Armbian builds. They are a fork of Armbian and use the Armbian name without permission. They do not participate in Armbian development nor do they participate in these forums. So any ophub questions need to be directed to them, not here.
So you say the armbian community build doesn't work, but you provide no information on what is failing. I'm not a mind reader so I can't help you if all you tell us is that it doesn't run.
-
Moved these posts to a new thread in the TV Box forums as this is getting to be off topic for the original thread since TV boxes aren't supported in any official manner by Armbian.
-
I know you mentioned this elsewhere, but I thought I would point it out for those that stumble across this post. Notice that they even go so far as to change the markings on the CPU to say it is something that it is not. It is also common that manufacturers will customize the android firmware to report incorrect ram/storage amounts. So sell you a 2G/16G box that android reports as being that, only to find out it really only has 1G/8G of real components. When it comes to these cheap boxes, the only thing that matters to the end customer is the price generally, so the manufacturers do everything they can to cut the cost. Because when you have 100 boxes being sold that all essentially do the same thing, a consumer naturally looks to the lowest price to make their buy.
-
5 hours ago, xuraax said:
meson-sm1-x96-max-plus-100m.dtb
Something doesn't make sense as there is no such dtb in the release
-
For the Armbian community build supporting your box (aml-s9xx-box), you need to add the kernel setting to the APPEND line in the extlinux.conf file.
-
-
-
How about you start with the build you are using and what instructions you are using?
-
Issues? Are we supposed to guess what issues you are having?
-
1 hour ago, alec said:
Armbian_24.2.0_amlogic_s905_jammy_6.6.13_server_2024.01.25.img
Armbian_24.2.0_amlogic_s905_bookworm_6.6.13_server_2024.01.25.img
These are not Armbian images. Where did you get them?
1 hour ago, alec said:u-boot.ext copied from u-boot-x96max.bin and u-boot-x96maxplus.bin
This is not part of any Armbian image.
1 hour ago, alec said:Armbian_23.11.1_Aml-s9xx-box_bookworm_current_6.1.63.img
Images prior to current nightlies and after 23.02 are known not to work with the s905x3 based boxes. But current nightly builds should work.
-
@audio kees You really need to take your questions elsewhere. You are off topic for this thread. Please take your libreelec questions to to their support channels. If you want to talk armbian on raspberry pi then open a new thread in the proper location in these forums.
-
1 hour ago, SteamPunkProgrammer said:
im having the same issue
Please start by explaining the exact issue you are having. Including all versions of the components.
-
If you can connect and the firmware upload starts but fails and this works on another device, I think you have faulty hardware.
-
6 minutes ago, Alon djboy said:
Uboot/Get Result/ Disk initial error
Does the tool connect, see your box? and allow you to choose your android firmware image file to upload? What options are you choosing during the burn?
-
Find an original android firmware for your box and use the amlogic USB burning tool with a USB male to USB male cable
Home Assistant on Ugoos AM3 s912
in Amlogic CPU Boxes
Posted
I don't understand what you are doing. You don't need to create any /boot directory. Why do you think you needed to do that?
And the default password for root is 1234