Project

General

Profile

Actions

Bug #11659

open

UV-5R BFP3-3 Lost Factory Image

Added by Mike Mahoney 16 days ago. Updated 16 days ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
11/04/2024
Due date:
% Done:

0%

Estimated time:
Chirp Version:
next
Model affected:
UV-5R B9-F9+
Platform:
Windows
Debug Log:
I read the instructions above:
Yes

Description

Made the mistake of switching between Chirp versions and mixing up multiple UV-5Rs when uploading and saving images and I lost my original factory image on one of my radios. The UV-5R BF-F9+ is the affected radio. I followed the recovery steps on Miklor but unfortunately my radio's original factory image file was not on the KC9HI CHIRP Recovery image file database. The main issue is that I know have a radio that will not receive incoming transmissions unless my monitor button is pressed. I have tried the simple fixes I've come across such as the BEEP ON setting bug, setting squelch to 0, and loading up image files from almost every 2013-2021 UV-5R I could find. I've tried using older versions of CHIRP also. In a previous CHIRP build (chirp-next-20230131) I do get a unique error message when uploading incompatible image files that shows what firmware my radio has, giving me my main key as to which factory image file I need. It looks like I need 'N5R-313BFP3-3'. I get the same response when trying to upload the N5R-313(140923N)(factory).img also. Just for fun, I also tried the image file attached to issue #2091

If anyone knows how to fix my issue, I would greatly appreciate the help.

Relevant Websites:
https://www.miklor.com/UV5R/UV5R-Recovery.php/
https://kc9hi.dyndns.org/uv5r/programming/CHIRPrecovery/
https://github.com/relaytt/BaofengIMG
https://www.chirpmyradio.com/issues/2091


Files

Error_message.png (16.6 KB) Error_message.png Upaod finished, but "Other Settings" could not be sent because the firmware version of the image (b'BFP3v3 F8HP-1') does not match that of the radio (b'N5R-313BFP3-3'). Mike Mahoney, 11/04/2024 11:34 PM
Error_message2.png (14.9 KB) Error_message2.png Mike Mahoney, 11/04/2024 11:43 PM
Actions

Also available in: Atom PDF