Odroid U2 not working after upgrade, can not reinstall

[raqua]

Hello.

I have Odroid U2. After yesterday's upgrade, which included new uboot it will not start.
I am trying to reinstall the device (I have eMMC) but there seems to be some issue.

After
wget http://os.archlinuxarm.org/os/ArchLinux ... est.tar.gz
bsdtar -xpf ArchLinuxARM-odroid-latest.tar.gz -C root/

I have normal looking linux filesytem and all seems fine, but issuing
./sd_fusing.sh /dev/sde1
will erase the whole filesystem.

[LaszloLeonard]

I have the same problem with Odroid-U3. After updating uboot I could not boot from emmc. However if I use the emmc -> sd adapter I can boot up.

[naums]

Did you set the correct UUID in /boot/boot.ini for the root-drive?

[LaszloLeonard]

I don't have a /boot/boot.ini file anymore.
$this->bbcode_second_pass_code('', '
alarm ~ $ ls -la /boot/
total 3512
drwxr-xr-x 2 root root 4096 Feb 18 04:12 .
drwxr-xr-x 18 root root 4096 Jan 25 19:56 ..
-rw-r--r-- 1 root root 15360 Feb 13 03:20 bl1.HardKernel
-rw-r--r-- 1 root root 14592 Feb 13 03:20 bl2.HardKernel
-rw-r--r-- 1 root root 734 Feb 18 04:04 boot.scr
-rw-r--r-- 1 root root 662 Feb 13 03:20 boot.txt
-rwxr-xr-x 1 root root 239 Feb 13 03:20 mkscr
-rwxr-xr-x 1 root root 1763 Feb 13 03:20 sd_fusing.sh
-rw-r--r-- 1 root root 159744 Feb 13 03:20 tzsw.HardKernel
-rw-r--r-- 1 root root 519614 Feb 13 03:20 u-boot.bin
-rwxr-xr-x 1 root root 2855248 Oct 26 2016 zImage
')

$this->bbcode_second_pass_code('', '
alarm ~ $ cat /boot/boot.txt
# After modifying, run ./mkscr

# MAC address configuration
# setenv macaddr "00:1e:ee:61:7a:39"

part uuid ${devtype} ${devnum}:${bootpart} uuid
setenv bootargs "console=tty1 console=${console} root=PARTUUID=${uuid} rw rootwait smsc95xx.macaddr=${macaddr}"

if load ${devtype} ${devnum}:${bootpart} ${kernel_addr_r} /boot/zImage; then
if load ${devtype} ${devnum}:${bootpart} ${fdt_addr_r} /boot/dtbs/${fdtfile}; then
if load ${devtype} ${devnum}:${bootpart} ${ramdisk_addr_r} /boot/initramfs-linux.img; then
bootz ${kernel_addr_r} ${ramdisk_addr_r}:${filesize} ${fdt_addr_r};
else
bootz ${kernel_addr_r} - ${fdt_addr_r};
fi;
fi;
fi
')

[jgmdev]

I had the same issue, what seems to fix the issue is follow the installation as on the wiki but instead of connecting the emmc card to the sd port on the odroid, connect it directly to the emmc port and it should boot, it seems the sd_fusing.sh isn't neccesary to get it working for mmc anymore and instead it damages the partition table.

I guess this should be documented on the alarm odroid-u2/u3 wiki now...

[marlemion]

Current Odroid U2 status of Armarch should be considered broken! I had it running on an emmc (old install) but for some reasons I wanted to reinstall it. With the latest image and following closely the wiki I am not able to get it working on an emmc card. Neither with nor without the sdcard-adapter, neither with nor without using the sd-fusing script.

Please test and fix or remove it from supported devices.

[kmihelich]

Nothing is broken, it's a supported device. This distribution is also not "Armarch." (Hint: look at the top of the page)

Your eMMC likely got corrupted. Follow the eMMC recovery instructions here: http://odroid.com/dokuwiki/doku.php?id=en:emmc_recovery_u3

Afterward, you will need to boot with the adapter again so you can run sd_fusing to write the current bootloader to the eMMC boot partition.

If you can't get it running with the adapter, you screwed up. Try following the steps.