Chip said:
Easy to brick? You intentionally tried to flash a firmware image that wasn't there.
If you break your neck diving into an empty swimming pool, do you blame the company who made the diving board? Of course not. If you're not smart enough to check if there's water in the pool, then whatever happens is your own fault.
Urrrhhh
Yeah, as someone who also bricked his Wiz I'm actually going to have to go with glossywhite on this. I don't know if I did anything wrong or not (I certainly did have the images on the SD) but GPH made several mistakes here. First of all, they probably should have avoided updating U-Boot at all costs. That should have been the point of having a 4MB boot NAND - you don't mess with it. Second, if the file is not there then yes, it should not have gone through with the automated upgrade procedure. Why are you people making excuses for what's an obvious design error?
I mean, what if the file got corrupted somehow? Is it your fault for not checking it against md5sums that to the best of my knowledge GPH doesn't even provide? When the procedure could have easily included verification like you would expect from any sane flash procedure (you'd also expect it to only work if there's enough charge, or plugged in). But yeah, I think an "is the file even there" check is the least it could do.