Announcement

Collapse
No announcement yet.

Linux for Amlogic S802 \ S812

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Junoxe
    replied
    Originally posted by maddone View Post

    I run in android update "aml_autoscript.zip." Nothing
    Yea, mainly this not works. I didnt find any image would work with this script.

    Leave a comment:


  • maddone
    replied
    Thank You!

    This armbian working for SD card: "Armbian_5.44_S812_Debian_stretch_3.10.108_server_ 20180521.img.xz"

    If I run install.sh it will install but will not boot from internal storage. Only black images are received.

    I run in android update "aml_autoscript.zip." Nothing

    Leave a comment:


  • balbes150
    replied
    Originally posted by maddone View Post
    Hello!
    There is a Minix Neo X8-H Plus box. How do I start Armbian? No way (I made a boot folder and also copied boot.scr)
    Sorry for my weak English.
    https://forum.armbian.com/topic/3023...ogic-s802s812/

    Leave a comment:


  • maddone
    replied
    Hello!
    There is a Minix Neo X8-H Plus box. How do I start Armbian? No way (I made a boot folder and also copied boot.scr)
    Sorry for my weak English.

    Leave a comment:


  • Junoxe
    replied
    Hi, which image will run Wetek Core? S812H, 2 GB RAM, Gigagit.
    I tried all meson8m2. May be it requires own dtb file?

    Thx.

    Leave a comment:


  • sadnblueish
    replied
    Originally posted by S812M8 View Post
    I'm confused on how to burn the image while still having access to my sd card??
    I can't edit the uEnv.ini at all
    I used "Win32DiskImager" to write .img to SDCard without any problem.
    However I remember, on some system, BOOT partition fails to get assigned Drive Letter by Windows. I had to manually assign Drive Letter to BOOT partition. You may want to check "Disk Manager" in Windows.

    Leave a comment:


  • S812M8
    replied
    I'm confused on how to burn the image while still having access to my sd card??
    I can't edit the uEnv.ini at all

    Leave a comment:


  • sadnblueish
    replied
    Originally posted by balbes150 View Post

    SD card or card reader may not work well. After one-time activation of multi-boot, you can try to start and work with USB flash drives.
    Thanks balbes150 for response. I gave it another try and it worked. In first try there was something wrong with WiFi configuration resulting in boot failure (odd though). Fighting with running Armbian on MXIII Plus without HDMI (headless) with no success. Tried both 5.77 version of Debian Server and Debian Desktop. I have ordered a dummy HDMI loopback connector but this gonna take sometime. Any cheat for headless?

    Leave a comment:


  • balbes150
    replied
    Originally posted by sadnblueish View Post
    I have Tronsmart MXIII Plus 2G/8G. I prepared SDCard with Armbian 5.77. Booted into Android. Flashed .zip to enable multiboot. rebooted and it straight went into Armbian pretty nicely. Ethernet also worked properly. Upon 1st reboot of Armbian, system can't boot Armbian anymore. However, it boots into Android without SDcard. Did I miss something?
    SD card or card reader may not work well. After one-time activation of multi-boot, you can try to start and work with USB flash drives.

    Leave a comment:


  • sadnblueish
    replied
    I have Tronsmart MXIII Plus 2G/8G. I prepared SDCard with Armbian 5.77. Booted into Android. Flashed .zip to enable multiboot. rebooted and it straight went into Armbian pretty nicely. Ethernet also worked properly. Upon 1st reboot of Armbian, system can't boot Armbian anymore. However, it boots into Android without SDcard. Did I miss something?

    Leave a comment:


  • balbes150
    replied
    I don't have any old versions. Ask users on the Armbian forum if they have any left.

    Leave a comment:


  • harmakhis
    replied
    hi balbes150
    so i let the dtb files where they are and i specify the item i want to use in the uenv.ini?
    regards

    edit : i tried but nothing after all dtbs
    could you upload the old archive Armbian_5.27_S812_Ubuntu_xenial_3.10.99 it seems to work i saw that in the 802/812 subject
    they are not on the yandesk disk
    Last edited by harmakhis; 12-26-2018, 14:59.

    Leave a comment:


  • balbes150
    replied
    Originally posted by harmakhis View Post
    flashed on Armbian_5.67_Aml-s812_Ubuntu_bionic_default_3.10.108_desktop_201812 07.img on SD32 SHDC
    flashed the firmware part to boot on sd under original firmware
    rename the template in txt
    put the m8s2 lan100 and rename dtb.img
    inserted in the sd port
    the box boot on the sd
    screen with colored pictures
    after that blank screen
    many minutes and nothing

    am i wrong?
    https://forum.armbian.com/topic/3023...&comment=66206

    Leave a comment:


  • harmakhis
    replied
    # begin build properties
    # autogenerated by buildinfo.sh
    ro.build.id=KOT49H
    ro.build.display.id=KOT49H.20150530 release-keys
    ro.build.version.incremental=20150530
    ro.build.version.sdk=19
    ro.build.version.codename=REL
    ro.build.version.release=4.4.2
    ro.build.date=Sat May 30 15:41:36 CST 2015
    ro.build.date.utc=1432971696
    ro.build.type=user
    ro.build.user=abdul
    ro.build.host=ubuntu
    ro.build.tags=release-keys
    ro.product.model=k200
    ro.product.brand=MBX
    ro.product.name=k200
    ro.product.device=k200
    ro.product.board=k200
    ro.product.cpu.abi=armeabi-v7a
    ro.product.cpu.abi2=armeabi
    ro.product.manufacturer=FreakTab.com
    ro.product.locale.language=en
    ro.product.locale.region=US
    ro.wifi.channels=13
    ro.board.platform=meson8
    # ro.build.product is obsolete; use ro.product.device
    ro.build.product=k200
    # Do not try to parse ro.build.description or .fingerprint
    ro.build.description=k200-user 4.4.2 KOT49H 20150530 release-keys
    ro.build.fingerprint=Tronsmart/k200/k200:4.4.2/KOT49H/20150530:user/release-keys
    ro.build.characteristics=mbx
    # end build properties

    Leave a comment:


  • harmakhis
    replied
    flashed on Armbian_5.67_Aml-s812_Ubuntu_bionic_default_3.10.108_desktop_201812 07.img on SD32 SHDC
    flashed the firmware part to boot on sd under original firmware
    rename the template in txt
    put the m8s2 lan100 and rename dtb.img
    inserted in the sd port
    the box boot on the sd
    screen with colored pictures
    after that blank screen
    many minutes and nothing

    am i wrong?

    Leave a comment:

Working...
X