pisach

I'm not expert here, but it looks as WPA related. Are you sure that you actually use WPA and not something else? The WiFi driver seems OK, check your WiFi settings.

like this :-)

You can send here output from dmesg or/and syslog.

Yeah, but it doesn't work for me even with 3.14.29 kernel :-) Can you help me to troubleshoot what might be wrong, please? Thanks!

This is too advanced for me. Isn't it enough to use this one: https://github.com/AlexELEC/S905-trees/blob/master/S905W/gxl_p281_2g.dtb ? The OS is running in the same way with this one from SD card, but it fails again to run from eMMC.

OK, I downloaded gxl_p281_2g.dtb from here https://github.com/AlexELEC/S905-trees/blob/master/S905W/gxl_p281_2g.dtb I used install.sh again: root@amlogic:~# ./install.sh Start copy system for DATA partition. Formatting DATA partition... umount: /dev/data: not mounted /dev/data contains a ext4 file system last mounted on /data on Thu Jan 1 00:00:10 2015 Suggestion: Use Linux kernel >= 3.18 for improved stability of the metadata and journal checksum features. e2fsck 1.43.4 (31-Jan-2017) /dev/data: clean, 11/767040 files, 74788/3066368 blocks done. Copying ROOTFS. Copy BIN Copy BOOT tar: boot/dtb/gxl_p281_2g.dtb: time stamp 2018-05-30 23:44:48 is 38944.312353311 s in the future tar: boot/dtb.img: time stamp 2018-05-30 23:44:48 is 38941.938608371 s in the future Create DEV Copy ETC Copy HOME Copy LIB Create MEDIA Create MNT Copy OPT Create PROC Copy ROOT Create RUN Copy SBIN Copy SELINUX Copy SRV Create SYS Create TMP Copy USR Copy VAR tar: var/log/daemon.log: file changed as we read it Copy fstab ******************************************* Done copy ROOTFS ******************************************* Writing new kernel image... 65536+0 records in 65536+0 records out 33554432 bytes (34 MB, 32 MiB) copied, 0.77237 s, 43.4 MB/s writing boot image config in bootimg.cfg extracting kernel in zImage extracting ramdisk in initrd.img reading kernel from /boot/zImage Writing Boot Image /dev/boot reading ramdisk from /boot/initrd.img-3.14.29 Writing Boot Image /dev/boot done. Writing new dtb ... done. Write env bootargs ******************************************* Complete copy OS to eMMC parted DATA ******************************************* Now it looks as the script has finished successfully, but the it fails to boot again: If looks different if it's run for second time: ******************************************* Done copy ROOTFS ******************************************* Writing new kernel image... 65536+0 records in 65536+0 records out 33554432 bytes (34 MB, 32 MiB) copied, 0.777269 s, 43.2 MB/s /dev/boot: no Android Magic Value /dev/boot: not a valid Android Boot Image. /dev/boot: no Android Magic Value /dev/boot: not a valid Android Boot Image. /dev/boot: no Android Magic Value /dev/boot: not a valid Android Boot Image. /dev/boot: no Android Magic Value /dev/boot: not a valid Android Boot Image. done. Writing new dtb ... done. Write env bootargs ******************************************* Complete copy OS to eMMC parted DATA ******************************************* root@amlogic:~# Thanks!

I found this in http://freaktab.com but my WiFi/BT is ssv6051 not RTL8189ETV Is there some place where all these dtb files/profiles are explained? Thanks!

But I don't have p281 in the img file at all? I found in one how-to for X96 mini that I have to use p212 and it works fine from the SD card. From where to take the correct dtb file? Thanks

I hope this will be enough. Thanks!

I didn't modify anything. It's running fine from the SD card and I expected everything to be copied on the eMMC and to work in the same way from here. The tv box installed with gxl_p212_2g.dtb. Should I somehow reinstall it on the eMMC? Thanks!

Hi, it's again me. From my point if view the install.sh script doesn't work..at least for my device. Here is the output from the script: root@amlogic:~# ./install.sh Start copy system for DATA partition. Formatting DATA partition... umount: /dev/data: not mounted /dev/data contains a ext4 file system last mounted on /data on Thu Jan 1 00:00:10 2015 Suggestion: Use Linux kernel >= 3.18 for improved stability of the metadata and journal checksum features. e2fsck 1.43.4 (31-Jan-2017) /dev/data: clean, 11/767040 files, 74788/3066368 blocks done. Copying ROOTFS. Copy BIN Copy BOOT Create DEV ... ... Copy VAR Copy fstab ******************************************* Done copy ROOTFS ******************************************* Writing new kernel image... 65536+0 records in 65536+0 records out 33554432 bytes (34 MB, 32 MiB) copied, 0.78898 s, 42.5 MB/s writing boot image config in bootimg.cfg extracting kernel in zImage extracting ramdisk in initrd.img reading kernel from /boot/zImage Writing Boot Image /dev/boot reading ramdisk from /boot/initrd.img-3.14.29 Writing Boot Image /dev/boot done. Writing new dtb ... done. Write env bootargs ******************************************* Complete copy OS to eMMC parted DATA ******************************************* root@amlogic:~# Here is the boot: It seems it doesn't see the boot partition on the eMMC. Are the any other steps? Thanks!

He, fixed! I used "Burn Card Maker" with which I burned a stock FW on SD card and somehow it flashed the TV box. Now I can go to bed :-)

After I shorter some pins I managed to get to U-boot from the UART. A'm not very familiar with U-boot. Could you tell me what is the fastest way to recover the device from here? U-Boot 2015.01-g2d1a155-dirty (Oct 08 2017 - 12:02:50) aarch64-none-elf-gcc (crosstool-NG linaro-1.13.1-4.8-2013.11 - Linaro GCC 2013.10) 4.8.3 20131111 (prerelease) GNU ld (crosstool-NG linaro-1.13.1-4.8-2013.11 - Linaro GCC 2013.10) 2.23.2.20130610 Linaro 2013.10-4 Thanks!

This is what I used in the beginning: su - (enter passwd root) ./install.sh or nand_sata_install but it didn't do anything. After the end of the script, I stopped the box, removed the card and it didn't boot, just blank screen. After that I managed to restore from backup.

Actually I'm more interested how to run this box from the eMMC. Why if doesn't work on TV boxes? Is there a separate how-to for TV boxes? The rest works just fine, I'm very satisfied...again thanks!

Hi bables150, yes, I had doubts and bad feelings before to run the script :-) Is there some how-to reset the eMMC chip? Here is the board: https://cdn-images-1.medium.com/max/1600/1*NJSv0Fu6wfB4qFjrTTjmFg.png The eMMC chip seems to not have exposed any pins. They're some interesting connectors on the right side of the NAND, below the UART, but I don't know.... Thank you!

mecool M8S pro has SV6051 WiFi. You need to do the following: ln -s /lib/firmware /usr/lib/firmware modprobe ssv6051 add ssv6051 in /etc/modules reboot

what is the model of the TV box?

Hi tkaiser, I'm trying to run X96 mini from eMMC. I followed the general instructions: su - (enter passwd root) ./install.sh or nand_sata_install But after reboot (without SD card) nothing happened, blank screen, no boot at all. I managed to recover the main Android image from a backup and the devices started to boot again. Then I downloaded the script from here and started it. They were quite a lot errors, but on the end it said "Shut down". After the shutdown the LED turned to red (from blue)...forever :-) After multiple attempts to recover it, I connected to the UART port and I saw these messages: BL2 Built : 14:59:36, Aug 9 2017. gxl ge8c6a83 - xiaobo.gu@droid12 set vdd cpu_a to 1120 mv set vdd cpu_b to 1050 mv set vddee to 1000 mv Board ID = 2 CPU clk: 1200MHz DQS-corr enabled DDR scramble enabled DDR3 chl: Rank0+1 @ 912MHz - FAIL DDR4 chl: Rank0+1 @ 1008MHz - FAIL DDR init failed... Reset... GXL:BL1:9ac50e:bb16dc;FEAT:ADFC318C:0;POC:3;RCY:0;EMMC:0;READ:0;0.0;CHK:0; TE: 122007 I have a feeling that from that point the device is unbrickable..but I have two more :-) The question is what I did wrong with the install on eMMC? Thank you!

I solved that with creating symlink :-) Now it's fine

Hi Arkimede, I'm trying to run Armbian_5.44_S9xxx_Ubuntu_xenial_3.14.29_mate_20180515.img.xz on X96 mini with 2GB RAM, but I'm getting: mlogic:~$ dmesg | grep ssv *** sta_cfg_set, /usr/lib/firmware/ssv6051/ssv6051-wifi.cfg *** [ 13.564886] WARNING: CPU: 0 PID: 2865 at drivers/amlogic/wifi/ssv6051/ssvdevice/ssvdevice.c:159 sta_cfg_set+0x1dc/0x220 [ssv6051]() [ 13.564896] Modules linked in: ssv6051(+) mac80211 cfg80211 aml_nftl_dev(P) [ 13.564966] [<ffffffbffc1455f0>] sta_cfg_set+0x1d8/0x220 [ssv6051] [ 13.564981] [<ffffffbffc145714>] ssvdevice_init+0xdc/0x120 [ssv6051] [ 13.565000] [<ffffffbffc177094>] $x+0x94/0x108 [ssv6051] [ 13.565272] ssv6xxx_sdio_init [ 13.565575] ssv6xxx_set_sdio_clk:set sdio clk 25000000Hz [ 13.595828] ssv6xxx_sdio_power_on [ 13.608526] ssv6xxx_dev_probe(): ssv6200 device found ! [ 13.608605] WARNING: CPU: 0 PID: 2865 at drivers/amlogic/wifi/ssv6051/smac/init.c:1376 ssv6xxx_dev_probe+0x1180/0x19e8 [ssv6051]() [ 13.608615] Modules linked in: ssv6051(+) mac80211 cfg80211 aml_nftl_dev(P) [ 13.608673] [<ffffffbffc14dff4>] ssv6xxx_dev_probe+0x117c/0x19e8 [ssv6051] [ 13.608730] [<ffffffbffc1645b4>] ssv6xxx_sdio_probe+0x31c/0x3c0 [ssv6051] [ 13.608783] [<ffffffbffc1640c4>] ssv6xxx_sdio_init+0x24/0x30 [ssv6051] [ 13.608797] [<ffffffbffc145738>] ssvdevice_init+0x100/0x120 [ssv6051] [ 13.608815] [<ffffffbffc177094>] $x+0x94/0x108 [ssv6051] [ 13.608838] SSV WLAN driver ssv6200: Failed to initialize device [ 13.608866] SSV WLAN driver: probe of ssv6200 failed with error -12 I followed your recommendation form above but I got an error that stacfgpath is an unsupported option, but I think we don't need that. What I'm doing wrong? Otherwise the WiFi worked as charm with USB Realtek WiFi dongle. Thanks!