Jump to content

RaptorSDS

Members
  • Posts

    303
  • Joined

  • Last visited

Posts posted by RaptorSDS

  1. vor einer Stunde schrieb greenais:

    download these old S805 images from?

    look at this thread somewhere are the yandisk link

     

    normally nand install was not possible because no nand driver in the old builds, impressive if you did it

     

    why not test the new image with 5.xx kernel also RTL8189 should maybe now work

     

     

    --> which Android One (11.x 9.x 8.x...) ? Never saw someone do this because android 4.4 was last build for S805 , this why android one had no driver for this box

  2. vor 8 Stunden schrieb ArtSHIM:

    There is an error even if I don't fix the file and just do a two-way conversion.

    your secound dtc string is wrong from dts to dtb

    -I = input type you have dtb should  dts

    -O = output type you have dts should dtb

    -o = output file = ok

     

    also odroid use realtek LAN but many HDMI CRC and HDMI i2c

    ODROID C1 source file

    mxq use internal(amlogic) LAN and standart HDMI output

    MXQ source file

     

     

    i thing your box need also the HDMI Communication CRC and i2c pins to work

     

     

  3. vor einer Stunde schrieb 심승보:

    SD Card Write Armbian_21.02.0-trunk_Aml-s812_bullseye_current_5.10.0_.img and meson8b-mxq.dtb, the network works, but the screen does not appear.
    (At Armbian_5.67_Aml-s805_Debian_stretch_default_3.10.108_desktop_20181207.img & meson8b-mxq.dtb,  Display screen on.)

     

    How about other dtb files from armbian 21.02.0 any other with display , its more easy to look at dtb files from same Kernel.

     

    dtb files from 3.10.0 to 5.10 are more difference -->that why there are not compatible .

     

     

  4. vor 1 Stunde schrieb jock:

    Never heard about sv6030P and never saw any driver for it. It looks very similar so ssv6051p, but can't say what kind of support it has.

    ok thank you , looks also bad supported --> ssv6051p is maybe a big brother of 6030p i found some coreElec information and some datasheet from icomm  (iottech)

     

    Zitat

    CoreELEC 9.2.14 changelog

    Updated Wifi driver ssv6xxx-aml

    Implemented Wifi driver SSV6030P

     

    they force ssv6051p driver for 6030p 

     

    Question is the SSV6051p and the patch also inside the rk322x images

    ssv6xxx-aml-003-force-SSV6051P-when-SSV6030P-is-detected.patch

  5. vor 7 Stunden schrieb Rohaaq:

    What else could I be missing?

    this is still a beta for this tv-box.

     

    yes when boot from sd-card you should edit uEnv.txt with right dtb file,

    but it could happen that none of the dtb work.

    if this happen, than please try one of the older Armbian S812 Version 5.xx with Kernel 3.10.xxx there is a higher chance that one dtb is correct for your box.

     

    be aware the dtb files not changeable between 5.xx Kernel and 3.10.xx Kernel

     

  6. vor einer Stunde schrieb Rohaaq:

    I see. But how exactly can I resolve these errors then?

    what do you see ? what do mean resolve error ?

    you do not need toothpick , you do not need recovery , only insert SD-Card and start the box

     

    befor patch

    bootloader-->internal memory-->android

     

    after patch

    without sd-card

    bootloader-->sd-card-->usb-->internal memory-->android

    or with sd-card

    bootloader-->sdcard-->debian

  7. vor 1 Stunde schrieb Rohaaq:

    The APK worked really well and I was able to enable multi-boot, and without root. I suppose in the future if using the stock app isn't an option for some user, using this APK would be useful suggestion. Much appreciated.

     

    However, I now get the following error in recovery mode:

    (stvm8b is the name of the board)

    E: Bad bootloader arguments "(null)"
    Finding update package...
    
    Start to check secure update...
    stvm8b board is encrypted
    not find bootloader.img in upgrade pachage. skipping...
    not find boot.img in upgrade package. skipping...
    not find recovery.img in upgrade package. skipping...
    Check secure upgrade package pass!
    
    Opening update package...
    Verifying update package...
    E: footer is wrong
    E: signature verification failed
    Installation aborted.

    Some Googling suggests that I might have to chose a different .xz file (in my case, a different one from this Yandesk directory), or something about my setup of the SD card is wrong. Is that correct? If the latter, what exactly am I missing other than changing the first line of the uEnv.txt to point to a specific DTB file?

     

    Thanks

    you are still in Recovery Menu not multiboot

     

     

     

    it should be more like this

     

     

    Boot from SD:
    --------------
    
    exit_reason:0x06
    set vddee to 0x03e8mv
    Enter ddr resume
    pub training time: 2630
    ddr resume done
    store restore gp0 pll
    cfg15 3b0d000 
    cfg15 63b0d000 
    GXBB:BL1:08dafd:0a8993;FEAT:EDFC318C;POC:3;RCY:0;EMMC:0;READ:0;CHK:0;
    no sdio debug board detected 
    TE: 71706
    
    BL2 Built : 12:06:06, Jun 13 2016. 
    gxb g176ecdb - laiyin.mo@droid12-sz
    

     

     

     

  8. vor 5 Stunden schrieb Rohaaq:

    Hi.

    I'm looking to run Armbian on an ATV 585, which has an S805 CPU.

     

    You can use S812 image it should also run S805 it depend on dtb you use

     

    dtb excange depend on Kernel

     

    Armbian 2x.xx ( Kernel 5.xx) you have to edit uEnv.txt

    Armbian 5.xx (Kernel 3.xx and Kernel 4.xx) than exchange file on boot partition

     

     

    when you always get to recovery then you have missed install aml_autoscript.zip , this activate the multiboot feature ( normally amlogic only boot from internall emmc/nand)

    the toothbrick methode normally only once when install zip file or from Android setting point firmware update

     

  9. vor 3 Minuten schrieb Clash:

    RK3328, 4GB Ram and 64GB Rom

     

    Thank you for picture , i have same box (but without the LCD Clock display)  with exact same chips

     

    on Page one there a list a few box that have the SD card on aux-SDIO port and not on first SDIO port , this also struggle me to boot SD-Card

     

    solve : write direct to emmc with PC and male to male cable --> high risk !

     

    i try to get from android terminal to uboot/maskrom mode but without success , i really want to backup android first

  10. vor 10 Stunden schrieb Zippy:
    • I have this box sitting somewhere i willing to try.
    • aml_autoscript.zip --> inside image , boot partition
    • image --> there are 3 storage spaces from blabes , yandisk (in this thread, some other forum ) ; mega ( in this thread somewhere) ; armbian space ( at s905 there was also a s8xx folder)
  11. vor 10 Stunden schrieb karkow:

    I tested Armbian 5.67 with kernel 3.10.108 - it worked just as well as 5.37

    Since there is no difference in performance (I did tests) I decided to go back to the older version because it had an install script on NAND. Installation was successful.

    but 5.67 and 5.37 are both kernel 3.10.xx so its normal to have same performance , only armbian >20.xx make diffirence because kernel 5.xx ( it is possible that armbian 20.xx may have less performance but its more unlikely )

     

  12. vor 32 Minuten schrieb karkow:

    I have MXQ on S805 (Originally Android 4.4)
    I use Armbian (5.37 debian stretch 3.10.99 server) as Pi-Hole DNS server.
    It runs from SD card stably for 3 years.

    I wonder if there is any sense to upgrade armbian to higher version. Are newer versions more efficient or stable?

    Which version is the latest for S805.

     

    I think that android 4.4 is not useful anymore so I'm thinking about installing on internal memory.
    Do I understand correctly that it is enough to run install.sh script in root homedir?

    sometime depend on programs like docker only work on 5.x Kernel

    sometimes driver more stable because complete new code

    sometime newer Debian and newer kernel are more unstable but thats can also happen with old kernel

     

    i use 20.09 (update from 20.04) and Kernel 5.9 rc7

    i think 20.15 with Kernel 5.11 was last build from balbes150

  13. vor einer Stunde schrieb jock:

    Confused?

    Well, I am... realtek drivers, expecially the 8723 family, are a real mess.

    í can confirm that , on Amlogic there are also many 8723xx chips

     

    there we struggle also with 8723bs of diffrent box's ( both are same chip(8723bs) but 2 diffirent box , and both have diffirent firmware files on android )

  14. vor 1 Stunde schrieb Kwazimoda:

    Hi all,

    Fortunately, found this thread since I've got not used TV box and need Armbian server for running Klipper and Octoprint for my 3D printer.

    So apprecitae for your advice and possible guidance.

    I have this Android 4.4 TV box: MXIII Amlogic Android 4.4.2 M82 S802 2GB 8GB Quad Core

    Here is more pictures of the board

    Would you please point to some guide and which image I should use in my case?

     

    hi

    first there is no a to z guide , please feel free to write one

     

    i can only advice the 4 steps how get this box work     // it is  sometimes complicate because there are many diffirent boxes

    1. activate multiboot (  install aml_autoscript.zip through android or recovery or maybe root TWRP and than install)

    2. get image to sd-card ( old kernel 3.x copy and rename dtb , or kernel 5.x edit uEnv.txt on the fat32 boot partion of sd-card)

    3. boot linux ( best is to get a serial TTL adapter to the board for debug but not mandatory )

    4. have fun

     

     

    to image

    there are Kernel 3.10.109 images (Armbian 5.xx) this are most compatible to android 4.4 but not all Programms run on them ( docker only on 5.x Kernel)

    Kernel 5.x (Armbian 2x.xx) are newer but maybe not full compatible or some driver do not work because change of kernel

  15. vor 7 Minuten schrieb armbian-mxq:

    Ok, I am also interested to know whether we may add more resolution in the dtb for kernel 3, say 1366x768p? In the attached dts of old kernel, I can see a section mesonfb. Vmode=3 and default resolution is set to 1980x1080p in hex

    normaly the driver should change resolution 

     

    in dtb there should be only one for starting the box/kernel like a nativ resolution

     

    after kernel start x11 should do it

     

    because i  used headless , i haven`t play with any HDMI and Display part , most things i change was on wifi and sdio part

×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines