Humrph!
Well, first, good hear support got back to you relatively quickly. That’s welcoming in this day and age.
Second, i just emailed them too now to see if there can’t be something we can try and help debug the issue. I’m happy to be a guinea pig if it can help the general community.
After further review i note two things.
-
On the above failure message it refers to getting more information from the U-Boot Console. Sure would be helpful to know how to access that. ie. whats the url for that puppy.
-
on this page → How to get support quickly under section “Help, I’ve broken my router!” there is this note:
Note:
There can sometimes be problems when debricking with MacOS or Linux. It is best to try it from a Windows computer.
I have a Mac… so i dunno. Given i was able to access the uboot update firmware page on the router just fine from my mac you’d think my client wouldn’t matter but who knows. Also, the update failed immediately after pressing begin update which leads me to believe something about the file itself rather than the contents are the problem. This of course is just a hunch.
Anyway… that’s my brain dump so far. (sorry. 
)