Jump to content

nytocs

Members
  • Posts

    13
  • Joined

  • Last visited

Posts posted by nytocs

  1. 15 hours ago, wdtz said:

    nytoc,, by the way, most firmware is distro and version agnostic ,,

    byte-order certainly matters, but probably not arch

    Sometimes it is in non-default locations and doesn't load,

    sometimes the package manager forces unnecessary restrictions

    sometimes ethernet has firmware

    --more--

    Since you have a rooted android??  ,,

    you already have the firmware,, /vendor/lib/firmware/some-directory-with-8723-in-it's-name

     

    Wifi kernel modules obtained from the Android 8.1

     

    https://mega.nz/#!YrgnEI4S!ocCcSF6xWZ2hmYJWESpEM13f-HVP6AY3rlPnIxzo1Sg

     

    I'll check later if it's loaded in Armbian

  2. On 10/19/2018 at 10:00 AM, vic said:

    Good day. I have a SCISHION V88 Piano TV Box - RK3328 4GB RAM + 16GB ROM Android 7.1 USB 3.0 Fast LAN. It works very poorly with trees of devices that exist in various LibreElec assemblies for RK3328. Could you get the device tree for my box from its firmware? Here is the link to my firmware https://drive.google.com/open?id=1LbRUocCILNPPXVgu_cOH0Cgqm8JWb2Kn
    Thank.

    I successfully extracted the resource.img and the dtb.. you can take a look

     

     

    resource_img.zip

  3. 11 minutes ago, wdtz said:

    >- microSD + USB: I can reach the Kodi interface but I don't have any network support 

    Not even ethernet?

    If your android is rooted, then,,  su; lsmod  ,,  you should be able to tell which is wifi module 

    OR,, take it apart and look at chip markings, the antenna will go to wifi chip (for me sv6051p)

    I assume you have both ethernet and wifi in android?

     

    It seems even the Ethernet is not recognized under Libreelec (here, cable was connected and dhcp was enabled)...

     

    Capture.PNG.0b8bb0fc7ed00fb96b0c5d4249068a6c.PNG

    *By the way I just tested on Armbian with the default configured dtb, ethernet is not working

     

     

    from Android: su; lsmod 

     

    image.png.363486e0e9eddbc554d646de1eb03815.png

     

    And according to the dtb I extracted from the Android 8.1, the chip is an RTL8723BS

     

    image.png.d3aa870fe0457b614236f855673306a6.png

     

    The box has both Ethernet and Wifi.

     

     

  4. 20 hours ago, balbes150 said:

    it will be interesting to test running Libreelec in the same mode (SD+USB).

     

    Behavior more or less the same as with Armbian

    - microSD only : cannot find rootfs

    - microSD + USB: I can reach the Kodi interface but I don't have any network support

  5. On 10/20/2018 at 8:28 AM, balbes150 said:

    Check this option. Write the image to two media SD card and USB flash drive. Configure the dtb in the extlinux.conf on SD card. Connect both media at the same time to the TV box and turn on the power.

     

    Nice catch !!! B) With both the microSD and USB key newly written and plugged at the same time in the box, I could successfully boot and obtain the Armbian Desktop. This with the default provided dtb. However without surprise, no BT, no WIFI. I tried the other provided dtb's, some boot with the same result, some don't boot at all.

     

    And with my extracted android t9 dtb, I still have the same result as before: the box doesn't boot.

     

  6. 1 hour ago, balbes150 said:

    no, I didn't see that situation. there are several possible causes. Not the correct dtb (not available to fit your TV box). Either the card reader and / or SD card are not compatible. Show a link with a description of your model. 

     

    https://www.aliexpress.com/item/Newest-4GB-64GB-Android-8-1-TV-Box-T9-RK3328-Quad-Core-4G-32G-USB-3/32899865217.html

     

    I could extract information (an fdt file, among others) from the boot partitions of the Android 8.1. Do you think it can help ?

    devicetree.tar.gz

     

    Edit: Convered the fdt file (which is actually a .dtb file) into a .dts file

    rk3328-t9-android.dts

    rk3328-t9-android.dtb

  7. 12 minutes ago, balbes150 said:

    To check, try changing the line in the file "extlinux.conf" 

     

    APPEND root=LABEL=ROOTFS console=uart8250,mmio32,0xff130000 console=tty0

     

    to

     

    APPEND root=/dev/mmcblk0p2 console=uart8250,mmio32,0xff130000 console=tty0 

    or 

    APPEND root=/dev/mmcblk1p2 console=uart8250,mmio32,0xff130000 console=tty0 

     

    No, this is incorrect content, so the system does not start. 

     

    I tried both APPEND propositions... doesn't work ...

     

    But it isn't very surprising because I cannot see any mmcblk* device in /dev/ from the initramfs :mellow:

     

    Did you already encounter such situation ?

  8. 8 minutes ago, balbes150 said:

    As the recorded image ? As a connected SD card with Armbian to TV box ? I observed the same error when trying to use an extension cord for SD card. Only when you install the SD card in the regular slot in the TV box, the system works fine. To configure the mount point, use the file " / extlinux / extlinux.conf." Note that if you change the mount point in this file, you will not be able to use the eMMC system installation script.

     

    I wrote the .img on a microsd using Etcher. I inserted the microsd directly in the microsd slot of the box.

     

    Hum, I'm sorry, I have no idea which extlinux.conf modification of the mount point could make the system to boot.

     

    Quick question: within the initramfs, is it a normal mount result ?

     

    rCwWaYO.png

     

     

  9. 9 minutes ago, balbes150 said:

    1. Specify the version of the image.

    2. Which dtb option is specified in the settings ? 

     

    1: "Armbian_5.62_Rk3328-tv_Debian_stretch_default_4.4.143_desktop_20181008.img"

    2: "/dtb/rockchip/rk3328-box-trn9.dtb", I already tried the others rk3328*, unfortunately with always the same result.

  10. Hi there,

     

    First of all thank you very much for the work done on this image.

     

    I recently bought an RK3328 T9 android box (seems to be an OEM box, but mine is "Vontar" branded). I'm of course interested in installing Linux on it :)

     

    Good news is that it boots on microSD ... 

     

    Now, with the provided image, I'm stuck at the initramfs step...

     

     

    ZeVPwSA.png

     

     

    I tried changing the "UUID=" usage with "PARTUUID=" in the armbianEnv.txt file but had no success.

     

    Any idea of what could be the cause ?

     

×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines