Bug #10639
closedBF-F8HP Issues Corrupted Radio
0%
Description
ISSUES : I updated image on my radio now it's blocking all incoming signals unless the MONI button is pressed and scanning button no longer scanning
i think i may have cross load images in CHIRP, i was told by Baofeng that i need to reach out to CHIRP support to help provide guidance to repair my corrupted radio.
Files
Updated by Jim Unroe over 1 year ago
Sounds like you may have uploaded an image from another radio. Do you have a "good" saved image from prior to that?
Jim KC9HI
Updated by Marvin Stuart over 1 year ago
Jim Unroe wrote in #note-1:
Sounds like you may have uploaded an image from another radio. Do you have a "good" saved image from prior to that?
Jim KC9HI
Unfortunately i didn't save my original image and/or any image prior to the upload to my radio.
Marvin
Updated by Jim Unroe over 1 year ago
Unfortunately Baofeng has provided no method for me to know which of the various versions of BF-F8HP you have. So I will have to take a stab in the dark. If this doesn't work, then we will try a different file.
- Download the N5R340B(191005N)(factory).img file that I attached
- Open CHIRP
- Locate and load the N5R340B(191005N)(factory).img file
- Select the Advanced Settings tab
- Click in the edit box for the Range Override Parameter setting
- Type Ctrl + A to highlight everything in the edit box and press the Delete key to empty the box
- Manually type "UseAtOwnRisk" into the edit box (without the quotes). Do not copy-and-paste it.
- Upload to your BF-F8HP
- After a successful upload, close CHIRP.
Hopefully that fixed your radio. To test it switch to VFO (frequency) mode and key in your local NOAA weather radio station. If you can hear it without pressing the MONI button, then it is fixed.
Now download from your radio into CHIRP. Load you bad image to create a second tab. Copy-and-paste the channels from the "bad" tab to the "good" tab and then upload the "good" tab back into your radio.
Jim KC9HI
Updated by Doug Nelson over 1 year ago
There was a recent bug I had with the BF-F8HP. For it, I sent in a config (.img) file. Feel free to try using that, if it helps.
Updated by Marvin Stuart over 1 year ago
AWESOME
What great stab in the dark you got me LOLOL. It now works flawlessly.
Previously i uploaded this same image multiple times and it didn't work, i did your method by adding UseAtOwnRisk and uploaded and its now Working
You are awesome, thank you again for taking the time to share your knowledge it tryly appriecated
Updated by Jim Unroe over 1 year ago
- Status changed from New to Not a bug
Marvin Stuart wrote in #note-5:
AWESOME
What great stab in the dark you got me LOLOL. It now works flawlessly.
Previously i uploaded this same image multiple times and it didn't work, i did your method by adding UseAtOwnRisk and uploaded and its now Working
You are awesome, thank you again for taking the time to share your knowledge it tryly appriecated
Thank you for the followup.
Jim KC9HI