Project

General

Profile

Actions

Bug #9053

closed

Problem Importing Radio Data

Added by Alex Krowzow almost 3 years ago. Updated over 2 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
05/08/2021
Due date:
% Done:

0%

Estimated time:
Chirp Version:
daily
Model affected:
Baofeng UV-5R
Platform:
All
Debug Log:
I read the instructions above:

Description

When downloading from radio, all locations download but no system mentu is present, just a D-STAR menu, using a Baofeng UV-56. WHen closing CHIRP, the radio switches to Chinese and none of the keys operate, including menu.I've attached the IMG file. How can I correct this? Thank you.


Files

Baofeng_UV-5R_20210508.img (6.5 KB) Baofeng_UV-5R_20210508.img Alex Krowzow, 05/08/2021 04:23 PM
IMPORTED FROM BF-F8HP IMG file -Baofeng_UV-5R_20210510.img (6.5 KB) IMPORTED FROM BF-F8HP IMG file -Baofeng_UV-5R_20210510.img This is the file that was uploaded with the copy and pasted frequencies from the BF-F8HP Alex Krowzow, 05/10/2021 01:46 PM
BACKUP - Baofeng_BF-F8HP_20210509.img (6.49 KB) BACKUP - Baofeng_BF-F8HP_20210509.img This is the img file used to copy the frequencies from. Alex Krowzow, 05/10/2021 01:46 PM
Baofeng_UV-5R_20210520(HN5RV01).img (6.5 KB) Baofeng_UV-5R_20210520(HN5RV01).img from stock HN5RV01 radio with original "aux" memory Jim Unroe, 05/20/2021 12:48 PM
Baofeng_UV-5R_20210520(HN5RV01 channels).img (6.5 KB) Baofeng_UV-5R_20210520(HN5RV01 channels).img with channels imported from BF-F8HP Jim Unroe, 05/20/2021 12:48 PM
TEST UPLOAD - Baofeng_UV-5R_20210525.img (6.5 KB) TEST UPLOAD - Baofeng_UV-5R_20210525.img Uoad from UV5R Alex Krowzow, 05/25/2021 06:36 PM
Left(good image), Right (your bad image).png (138 KB) Left(good image), Right (your bad image).png Jim Unroe, 05/26/2021 05:20 AM

Related issues

Related to Bug #9055: Problem Importing Radio DataClosed05/08/2021

Actions
Has duplicate Bug #9059: Problem Importing Radio DataClosed05/09/2021

Actions
Actions #1

Updated by Jim Unroe almost 3 years ago

  • Status changed from New to Feedback

This is not a valid CHIRP Radio Images (*.img) file from a UV-5R. It is a corrupted mess. This image should never be uploaded to any radio.

I've not heard of a UV-56. Is this a typo? If not, CHIRP does not support a UV-56.

In any case, you must download from a working radio first. The first successful download should be saved, unedited, to a native CHIRP Radio Images (*.img) file to be kept in a safe place as a backup. Then use a second "working" copy to edit as desired.

If you didn't save an original backup image, then I would recommend that you try to locate an image from the same (or very similar) working radio model that has the exact same HN5RV01 firmware.

Jim KC9HI

Actions #2

Updated by Alex Krowzow almost 3 years ago

Hello and thank you for your understanding as I try to resolve my problem with my UV-5R. I believe that I followed your instructions to transfer a list of frequencies from my BF-F8HP into my UV-5R, using your suggestion:

"There are many ways of transferring the channels between radios of different vendors/models/firmware versions. The most quick-and-dirty method is to download from both radios to create 2 tabs. In your case it would be a UV-5R tab and a BF-F8HP tab. Then you would just copy-and-paste the channels between tabs."

  1. First, I opened a good .img file from my BF-F8HP in one new tab (copy attached)
  2. Next, I downloaded the data from the UV-5R into a new tab
  3. Going to the BF-F8HP tab, I copied the frequencies and pasted them into the UV-5R tab
  4. Next, I uploaded the resulting file to the UV=5R and saved it as an .img file (copy attached)
  5. The UV-5R opens with a Chinese languare prompt and the Menu button is inactive.

When turning on the UV-5R i see a version BFB298 and firmware 19103M. The "Settings" tab is completly blank.

The BF-F8HP reports a version of BF-F8HP and firmware OF N5R340B when turning on and pressing either the #3 or #6 key. Under the "Other Settings" tab, the Firmware Message 1 shows F8HP-1.The settings tab is fully populated.

I hope this gives you the informtion to help guide me through this process to get my UV-5R working. Thanks again for your patience as I am new to the UV-5R.
Alex, KC3LOY

Actions #3

Updated by Alex Krowzow almost 3 years ago

Was any progress made on resolving the issue with trying to program my UV-5R radio?
Thank You,
Alex Krowzow
KC3LOY

Actions #4

Updated by Jim Unroe almost 3 years ago

Alex Krowzow wrote:

Was any progress made on resolving the issue with trying to program my UV-5R radio?
Thank You,
Alex Krowzow
KC3LOY

This is not a CHIRP issue. The memory of your radio has been corrupted by something or someone. You must locate a good image from another working radio with the same HN5RV01 firmware and upload it to your radio to straighten it out.

Jim KC9HI

Actions #5

Updated by Alex Krowzow almost 3 years ago

Thank you for your advice. Can you point to a resource to find an image with HN5RV01 firmware, even if the frequency data is not applicable? I couldn't find an image source on the danplanet site, but not be looking in the rigt area? Thanks again.
Alex Krowzow

Actions #6

Updated by Bernhard Hailer almost 3 years ago

Alex, you cannot upload firmware with Chirp (nor am I aware of any other method with these radios). Unfortunately, if your radio doesn't work, then you need to negotiate with the dealer what to do about it.

Actions #7

Updated by Bernhard Hailer almost 3 years ago

  • Target version deleted (chirp-legacy)
  • Model affected changed from UV-5R to Baofeng UV-5R
  • Platform changed from Windows to All

Please let us know what you decide to do so that we can close the ticket. Thanks!

Actions #8

Updated by Jim Unroe almost 3 years ago

Alex Krowzow wrote:

Thank you for your advice. Can you point to a resource to find an image with HN5RV01 firmware, even if the frequency data is not applicable? I couldn't find an image source on the danplanet site, but not be looking in the rigt area? Thanks again.
Alex Krowzow

Alex,

I would give this CHIRP Radio Images (*.img) file a try. What I would like to see you do first is to upload this file to your radio and then immediately download from your radio back into CHIRP. Save this newly created tab to a CHIRP Radio Images file under a different name and attach it to this issue. This will let me check to see if your radio's memory was able to be restored. I am hoping that the corruption is not permanent and this file will get you going.

Once your radios memory is verified as being restored, then you can upload the second file that has the channels imported from the BF-F8HP image.

Jim KC9HI

Actions #9

Updated by Alex Krowzow almost 3 years ago

Jim,
Thanks for the advice. This is frustrating for me. I am able to load and upload all I need for the my BF-F8HP, but an perplexed with both of my UV-5Rs that are behaving identically. I imported the file you suggested (Baofeng_UV-5R_20210520(HN5RV01).img added)and saved it under a new name, a copyof which is attached. I tries this withboth of my UV5-Rs. I hope this and help you troublesooot this mattert thank you for your attention.

Alex Krowzow
KC3LOY

Actions #10

Updated by Jim Unroe almost 3 years ago

Alex Krowzow wrote:

Jim,
Thanks for the advice. This is frustrating for me. I am able to load and upload all I need for the my BF-F8HP, but an perplexed with both of my UV-5Rs that are behaving identically. I imported the file you suggested (Baofeng_UV-5R_20210520(HN5RV01).img added)and saved it under a new name, a copyof which is attached. I tries this withboth of my UV5-Rs. I hope this and help you troublesooot this mattert thank you for your attention.

Alex Krowzow
KC3LOY

Alex,

The file you are uploading is trash. You do not want to upload any of your preexisting files any of your radios. They are trash. You do not want to import anything into them. You need to stop using these corrupt files.

The screen capture that I have attached is a portion of memory from the image that you attached (the right half) and the same portion of memory from the file I attached (the left half). I don't know how anyone could intentionally mess up an image file in the way yours has been messed up.

On the left, the bytes from E28 to E67 are many of the radio's global settings. The same bytes in your image (the right) are a scrambled mess.

On the left, the bytes from F10 to F17 are the VFO A frequency (162.52500). On the right, garbage.

On the left, the bytes from F30 to F37 are the VFO B frequency (462.56250). On the right, more garbage.

I am confused by the terminology that you are using. You should not be doing any form of Import to do what I need. What is need is for you to Upload one of the files that I supplied (the Baofeng_UV-5R_20210520(HN5RV01).img image will be fine)to one of your radios. Then immediately download from that same radio create a new tab from that radio. Save this newly created tab to an image with a different name and attach it here so that I can compare to the originally uploaded image.

Jim KC9HI

Actions #11

Updated by Bernhard Hailer almost 3 years ago

Alex, have you been able to resolve your problem? Please let us know. Thanks!

Actions #12

Updated by Alex Krowzow almost 3 years ago

Bernhard Hailer wrote:

Alex, have you been able to resolve your problem? Please let us know. Thanks!

Bernard,
I was unable to upload a good / .img file and am not really sure how to upload an image file. I returned one of the UV-5Rs to the vendor and am stuck with the one that has a remaining corrupt operating system file. Thanks.
Alex Krowzow

Actions #13

Updated by Bernhard Hailer almost 3 years ago

So it looks like there was no solution for this problem.
You say you tried a (known?) good image file - if that doesn't work, then you must have a defective radio.

You could try to get the OEM software and try whether that fixes anything.
You could also try to find someone on the "mailing list":http://intrepid.danplanet.com/mailman/listinfo/chirp_users to help you with a radio image for the correct firmware version. Maybe that changes something.

Unfortunately, we have reached a point here at which we can't help you. We will have to close this ticket soon if there's no resolution in sight.

Actions #14

Updated by Bernhard Hailer over 2 years ago

  • Status changed from Feedback to Closed

You can still let us know in case you find a solution. Thanks.

Actions

Also available in: Atom PDF