Jump to content

pisach

Members
  • Posts

    21
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. 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.
  2. 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!
  3. 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.
  4. 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!
  5. 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!
  6. 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
  7. 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!
  8. 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!
  9. 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 :-)
  10. 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!
  11. 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.
  12. 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!
×
×
  • Create New...