Bricked my brand new Home Assisstant blue

Something went wrong when I tried to go through the onboarding process using a snapshot from my previous version. Now, the thing is entirely unresponsive. I’m assuming I want to reinstall the OS from the images available. The problem is I need some help flashing the ?emmc? module. I got the case open but I’m not sure where to find the module, how to remove it, and how to flash it.

Anyone know of a good reference?

The HA Blue is a Hardkernel ODROID-N2+ with a custom case. Here are some links:

https://www.hardkernel.com/shop/odroid-n2-with-2gbyte-ram-2/
https://wiki.odroid.com/odroid-n2/odroid-n2
https://wiki.odroid.com/troubleshooting/odroid_flashing_tools
https://www.home-assistant.io/installation/odroid

You’ll might need one of these to re-flash the eMMC:

https://www.hardkernel.com/shop/usb3-0-emmc-module-writer/

An alternate method is here:

https://www.home-assistant.io/common-tasks/os#flashing-an-odroid-n2

Thanks Rob!

I’ll go ahead and give the alternate method a try and see how that works. Failing that, I’ll go through the first 4 links.

1 Like

OK, so I managed to get it all hooked up and, I used the ums command on /dev/mmcblk0 all with no problem.

But then my computer won’t start up the new drive, instead reporting an error. In the device manager of windows I see the following:

This device cannot start. (Code 10)

{Operation Failed}
The requested operation was unsuccessful.

any thoughts?

I’m at a disadvantage with HA on the N2; my experience is limited to a different application. When you use the ls command, do you see /dev/mmcblk0 listed? Can I assume the flash process doesn’t even start?

As an aside, it looks as if there have been upgrades with the Petitboot bootloader. That said, I’m not sure it’s the issue, or if an upgrade will even help. Perhaps you need a recovery image to get it to work.

https://wiki.odroid.com/getting_started/petitboot/recover_or_upgrade
https://wiki.odroid.com/odroid-n2/os_images/petitboot#recovery_mode

I suggest two potential ways of getting help if the above links don’t help:

The preferred way is to look through the issues on GitHub and see if there’s anything with the same problem signature. If you don’t see something similar enough, write up a new issue. Hopefully, someone with relevant experience (e.g. @agners) will respond and point you in the right direction.

https://github.com/home-assistant/operating-system/issues

Here’s a similar issue: https://github.com/home-assistant/operating-system/issues/771

The second path is to go to Hardkernel for help via their forum:

https://forum.odroid.com/viewforum.php?f=181

Either approach requires having an account.

I’m at a disadvantage with HA on the N2; my experience is limited to a different application.
You’re my hero anyway at least right now :slight_smile: This is my first experience with a pi-type computer, emmc memory, and a host of other things so I’m a bit out to sea.

When you use the ls command, do you see /dev/mmcblk0 listed?
Yes and I was successfully able to change it to ums… or at least I ran that command which gave no feedback. But running that command did cause my windows PC to “ding” and it tried to mount the drive.

Can I assume the flash process doesn’t even start?
I couldn’t even start the flash process. I got no drive letter. The windows UMS driver failed to connect properly to the drive.

I suggest two potential ways of getting help if the above links don’t help:
Thanks for all your help Rob. I’ll take this on over to the hardkernel forums.

1 Like

@JDHayes you should get a drive letter. The fact that Windows did “ding” seems that something appeared on the USB Bus. Check the Windows Drive Manager if the drive really did not appear. I’d try a different USB cable/port/Hub combination, sometimes its just USB not properly enumerating.

1 Like