Bug #1911
closed.img file with matching Firmware still causes CHIRP to crash and radios to not work
0%
Description
Hello,
I work for a national youth organization giving teenagers the opportunity to have mountain biking as their high school sport. We have just started using UV-5R and UV-5RA radios to aid in our risk management and EMS response at races. While I've successfully troubleshot the rest of our eighty radios, I am having trouble with one last set of thirty radios.
You can learn more about our organization if you're interested by following this link: http://www.nationalmtb.org/
Here's the list of things I have done:
- Using Chirp 0.4.0. I programmed 30 BaoFeng UV-5R radios with a file that wasn't written for the correct firmware
- radios would only receive with Moni button pressed.
- to find the correct file we reset a radio, uploaded it to chirp and found the following version: Firmware Message 1: N5R-20 Firmware Message 2: BFB297
- we went to http://kc9hi.dyndns.org/uv5r/programming/CHIRPrecovery/ to download the corresponding "factory" and "reset" files, but found those files crashed chirp and didn't program the radios.
Has anyone else had a similar issue? Are we missing some sort of firmware understanding? Thank you.
-Chris
P.S. I attached the file downloaded from the reset radio.
Files
| GA Radio 1.img (6.32 KB) GA Radio 1.img | |||
| An error has occurred.jpg (48.8 KB) An error has occurred.jpg | |||
| fault.jpg (95.4 KB) fault.jpg | fault message |
Updated by Jim Unroe over 10 years ago
- File An error has occurred.jpg An error has occurred.jpg added
- Status changed from New to Feedback
Chris,
First, if you have any Baofeng radios with N5R-20 or N5R-30 firmware, you must be using a CHIRP Daily Build newer than 20140714. This prevents you from uploading a saved .img file from a previous firmware version. But since you already have done this, you need to use the CHIRP Daily-20140714 or older (v0.4.0 should work) to perform the recovery before upgrading to the latest daily build.
Which .img file are you trying to upload? You should be using the "N5R-20(factory).img" or "N5R-20.img" to perform the recovery.
If you are downloading any other .img file and uploading it to these radios with N5R-20 firmware, you will get the "An error has occured" message (see attached image). This is not a crash! It is just an informational message to let you know that a part of the upload had to be skipped because of the difference between firmware versions. It would be the wrong firmware version to recover these radios, though. If you upload one the the .img files specified above, you won't see this "error" and your receive will be restored.
Once you get the "N5R-20(factory).img" file loaded to all of these radios, then it is very important that you install the latest CHIRP Daily Build and use it instead of V0.4.0.
Let me know if this helps?
Jim KC9HI
Updated by Jakob Bjarnason over 10 years ago
Hello
I have the same/similar problem.
I started with copying old .img to my new UV-5R radios with the new N5R-20 firmware.
After that I found the recovery process, downloaded the Chirp Daily-20140714 and "N5R-20.img" and tried to upload it.
I tried both N5R-20.img and also N5R-20(factory) but nothing works.
Updated by Jim Unroe over 10 years ago
OK. I am going to try to explain this one more time. This is not a crash. Please read the message. The part of the .img file that is needed to "recover" your radio has been uploaded successfully. It is only the "other settings" that did not get transferred. They are not needed for the recovery process. Once this operation has been completed, upgrade to the latest CHIRP daily build and you should be good.
Jim KC9HI
Updated by Jim Unroe over 10 years ago
OK. I see the issue. The older CHIRP daily build reads 2 too many characters for the firmware version. These extra characters don't match and causes CHIRP to report the error. Ignore the error, the radio has been recovered. Then update to the latest CHIRP daily build. It not only has been updated to prevent cross loading of the pre-N5R-20 .img files into radio with N5R-20 firmware, it has also been updated to not read the 2 extra characters.
Jim KC9HI
Updated by Jakob Bjarnason over 10 years ago
Ok this worked!! :)
I never tried to upload from the newest chirp daily build because I thought the recovery didn't work when the fault was still in after uploading from the 14072014 daily build.
Next time I know that I need to finish the whole recovery process
Best regards
Jakob B.
Updated by Jim Unroe over 10 years ago
I'm glad you got it.
I had Miklor John update the "recovery procedure" to explain that this error as a possibility and to just continue if it appears.
http://www.miklor.com/uv5r/UV5R-Recovery.php#N5R
Jim KC9HI
Updated by Bernhard Hailer almost 5 years ago
- Status changed from Feedback to Closed
- Priority changed from High to Normal
- Target version set to chirp-legacy
- Chirp Version changed from 0.4.0 to daily
- Model affected changed from UV-5R to Baofeng UV-5R
Resolved.