Over the last couple of weeks, we've been working on a fix for this -- not just your specific case, but the underlying cause that you encountered. It's in testing now and we expect it to be deployed late this afternoon. The main content of the fix is to let a user still replace the image even if it's broken. Once we deploy it, you should be able to fix it as you like. I'll post here when it's live.