Jump to content

SteeMan

Moderators
  • Posts

    1962
  • Joined

  • Last visited

Posts posted by SteeMan

  1. I just downloaded both images available on the download page (minimal and xfce desktop) and both images had the install-aml.sh script in the /root directory.

     

    As far as your current state, I only know of the windows amlogic tool as being the only available way to restore an android image.  I know nothing about the Khadas tools you are trying to use, whether they will work on non-khadas boards, or if they can be used for what you are trying to do. 

  2. 1 hour ago, user03 said:

    I did read the install instructions

    I don't believe you did.  As the install instructions linked to from the download page don't mention any of the things you tried (like armbian-config, armbian-install, nand-sata-install, etc).  These are the instructions for the amlogic s9xx tv box builds (again these are linked from the download page):

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

     

    These instructions tell you to run /root/install-aml.sh which is not what you said you did.

     

    Now a further note is that ophub is a fork of Armbian.  They do not contribute to Armbian development, do not participate in these forums and use the Armbian name without permission.  So if you choose to use their software, you will need to discuss their software on their forums as we can't help you at all with ophub software.

     

     

  3. You should have followed the install instructions on the download page:  https://www.armbian.com/amlogic-s9xx-tv-box

     

    Given where you are now, you need to find an original android image, flash that to return the board to a clean state, and then follow those instructions.

     

    The amlogic s9xx TV box builds use the android bootloader to bootstrap the boot process which at this point you have overwritten part of.

  4. I'll start on congratulating you for all you have accomplished.

     

    Now to your questions.  I've never experienced a case where installing to emmc took away the ability to boot from the SD card, nor have I ever heard that reported by other users in the forums.  So that one is a mystery.  To debug that you would need to find your uart connection on the board and hook up a usb-uart adapter to monitor the uboot process.

     

    I would also recommend you try putting your image on a usb thumb drive and see if that works for a workaround.

     

    For autologin, you should just be able to follow any standard guidelines for doing that with a google search of 'xfce4 auto login' and you will likely need to edit some config file somewhere to enable this.  Exactly what may depend on are you running Ubuntu or Debian userland with the Armbian kernel.

     

     

  5. 5 hours ago, Werner said:

    outdated tag, unsupported

    What @Werner means by this comment is that you need to update your code to current github code base.  You can't use old code to build.  The dependencies that get pulled in during the build process change over time.  So you always need to be on current (or near current) github source for armbian build to reliably build images.

  6. Yes you can work to make things better.  But since I don't have this box (nor even one with that specific cpu version) there isn't anything I can really help you with.  But anything you find/improve can be submitted back to Armbian as a PR.  This stuff is all community supported, thus it depends on people like you to make improvements and submit them back for others to benefit from.

  7. 4 hours ago, user03 said:

    o my surprise it immediately showed me a message saying this image is for tesing purposes only, and not stable.

    Armbian doesn't support TV Boxes, all Community Supported builds are given that description.

     

    4 hours ago, user03 said:

    try a different dtb

    Yes, per the instructions have you tried all the dtbs that might be relevant?

     

    In general, I'm not aware of any dtbs in mainline linux for the s905l3 cpu.  I don't know what the closest might be.

     

    In general, due to lack of support by Amlogic, the efforts to support newer versions of their CPUs in mainline linux have essentially stopped.  For example the project website that tracked progress on mainlining amlogic (https://linux-meson.com/mainlining.html) shows that efforts stopped around two years ago.  Realistically only older amlogic cpus (i.e. cpus released at least 4 or more years ago) are going to be supported in mainline linux (and thus Armbian).

     

    And unfortunately I think the s905l3 falls into the newer category.

  8. Specifically the file you want to look at is aml_autoscript

     

    What happens on a normal amlogic TV box is when the hidden reset button is pressed during boot, the boot loader looks for this file and runs it.

     

    This file then changes the stored uboot environment such that subsequent boots follow a new boot flow to boot first from sd or USB and fall back to android.

     

    If you follow the logic you can find the actual boot commands in the other files that get called.

     

     

  9. 3 hours ago, Herman Hoekstra said:

    But when i brick the system, is it stil possible to boot from a SD card or must i try to flash a version of android first using a USB A to USB a cabble?

    It depends on how you have bricked it.  Reflashing Android takes you back to a clean starting point.

×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines