Sure an image can be saved from the mis-behaving radios. But without an image from a known good radio to compare it to, there is no way to determine what changed or to know how to proceed to resolve the issue.Again, what you're asking for is pointless and unnecessary.
If you (or your friend or whoever) have the radio, you don't need to look elsewhere to get a CHIRP image file, you can get it straight from the radio whenever you want via the download function in CHIRP.
If the radio is too non-functional to download an image from, you're not going to be able to upload an image from another radio to it, regardless of firmware version. So having an image from another radio, regardless of firmware version, isn't going to be helpful.
If the problem cannot be resolved by downloading an image from the radio, than it cannot be resolved by an image from another radio.
Yesterday morning I had received an email from Phil, WA4DDE, with the requested N5R-20 CHIRP image that he had saved from a working radio. This image has been forwarded to several individuals and has successfully "recovered" their radios.
These new radios with N5R-20 firmware have a 16-byte area of memory that has different values from a legacy UV-5R (and variant) radio. The radio will misbehave if these bytes are change. It was this memory being overwritten by an image from a legacy UV-5R (with different values) that caused the radio to stop receiving normally.
However, comparing the images and some testing by Bryan, I learned enough to isolate this area of memory. This allowed me to successfully hand edit a "bad" image to "repair" it.
Once I get a factory image (I have promises from multiple sources), I will make it available with the rest of my "factory" and "reset" images.
Index of /uv5r/programming/CHIRPrecovery