anonymox

I think my device was installed NAND chip instead of eMMC. I ran the "df" command and it show like this: /dev/mmcblk0p2 14G 4.1G 9.8G 30% / /dev/mmcblk0p1 128M 56M 73M 44% /boot Other issue with this box is it can't boot to android anymore once I booted to Armbian on SDCard. I checked the multi boot script and look like it can't see eMMC storage to boot in.

Hey, I'm using TX3 mini type A (2019 edition - new hardware). I can't install Armbian to eMMC, this is log: root@aml:~# ./install.sh Start script create MBR and filesystem Start backup u-boot default dd: failed to open '/dev/mmcblk1': No such file or directory Start create MBR and partittion Error: Could not stat device /dev/mmcblk1 - No such file or directory. Error: Could not stat device /dev/mmcblk1 - No such file or directory. Error: Could not stat device /dev/mmcblk1 - No such file or directory. Start restore u-boot dd: failed to open '/boot/u-boot-default.img': No such file or directory dd: failed to open '/boot/u-boot-default.img': No such file or directory Done Start copy system for eMMC. Formatting BOOT partition...mkfs.fat 4.1 (2017-01-24) mkfs.vfat: unable to open /dev/mmcblk1p1: No such file or directory done. mount: /ddbr/install: special device /dev/mmcblk1p1 does not exist. Cppying BOOT...done. Edit init config...done. umount: /ddbr/install: not mounted. Formatting ROOT partition... The file /dev/mmcblk1p2 does not exist and no size was specified. e2fsck 1.44.5 (15-Dec-2018) e2fsck: No such file or directory while trying to open /dev/mmcblk1p2 Possibly non-existent device? done. Copying ROOTFS. mount: /ddbr/install: special device /dev/mmcblk1p2 does not exist. Copy BIN 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 Copy fstab umount: /ddbr/install: not mounted. ******************************************* Complete copy OS to eMMC ******************************************* Does everyone know to to fix this?

I still can't resolve this problem

I tried fw_printenv in kernel 3.14 but it only returned "Cannot parse config file '/etc/fw_env.config': Invalid argument"

do you have a link to Armbian with kervel 3.14, I can't found it. I tried with higher kernel version but they only return file not found --- never mind, I found it

Are there other ways to do that? My device will lost warranty if I open it.

Hi @balbes150, I flashed Debian 5.77 to my SDcard. It booted ok with my new TX3 mini (type A). But now, when I ejected the SDcard from box, I can't boot to Android anymore. It stucked at device's booting logo. I dont't install Armbian to eMMC. Just boot from SDcard and than eject it. Currently, I still can boot to SDcard, but Android is not. The only way to back to Android is re-flash the Android firmware. I used "dmesg | grep mmc" command to check my device is eMMC or NAND, I found this: mmc2: new high speed SDIO card at address 0001 Can you help me? How to dual boot?