I broke my UV-5r

[kent11]

Did a dumb thing and downloaded an older radio (July 2014) and uploaded the image to a new radio (Dec. 2014). Now the new radio only receives when the monitor button is pressed (like ctcss is stuck on). I read the boards and tried to upload new image. No Joy. Old radio has bfs313 bsf297 firmware. New radio shows n5r-213 bfb297 firmware. When I try and load the factory n5r-213 Chirp says radio Image not supported. If I load bfb297 it loads says there is an issue and does not fix the no rx audio issue. Can someone point me to the correct firmware or correct procedure to fix my no rx audio issue. I see many complaining about the issue just no step by step fix its.

Thanks

 

[scannerbuff999]

sound like good reason to buy a new one you can get them on the web cheap 35 dollars

 

[teufler]

Radio file same numbers as new radio

Here is a radio file that has the numbers you need for the new radio.
DO A RADIO RESET. https://www.youtube.com/watch?v=FDKXxdyjxaI
LOAD MY FILE, THE DELET THE FREQUENCIES. THEN LOAD YOUW OWN, THAT SHOULD DO.

 

[kent11]

Did a menu 40 reset before my first post. No Joy.

 

[teufler]

UV5R FILE

WELL rr DOESN'T ACCEPT A IMG FILE, HAS TO BE ZIPPED SO TRY AGAIN. WITH YOUR NUMBERS NEEDED.

 

[gewecke]

Mistake 1. You bought a cheap chinamart radio that no one in the U.S. cares to service.

Mistake 2. You played jenga with questionable software.

Mistake 3. would be if you bought another.

73,
n9zas

 

[kent11]

Fixed

I had to downgrade Chirp to the July 7 2014 daily build, load the NSR-213 image. That fixed my radio. Now I can install the newest version of Chirp and should be good to go. YEA......

 

[teufler]

After reading of your difficulties, I have 3 gt-3s. I have to keep my software separate so I don't confused the radios.. I have mine, then bought two as gifts because they mine has held up fine. Did experience a problem today. Li battery, they don't give a warning they are getting low, they just quit. Had indications on the screen but frankly wasn't watching. The only way to recharge is via the stand, thats a little awkward while mobile. Be nice if you had a port to plug into like most radios, but I guess I get another battery fotr safety.

 

[Hans13]

I had to downgrade Chirp to the July 7 2014 daily build, load the NSR-213 image. That fixed my radio. Now I can install the newest version of Chirp and should be good to go. YEA......

I didn't see your post until you already had it resolved. For the benefit of others (and perhaps mine in the future), is this basically the problem you had?

N5R Issue Recovery

and this was the fix?

UV5R F8HP Recovery Baofeng Pofung UV5R

 

[KC3ECJ]

Use the Baofeng software, it will over-ride the CHIRP writes.

 

[KC9HI]

Use the Baofeng software, it will over-ride the CHIRP writes.

I respectfully disagree. CHIRP saves and restores memory locations that the OEM software will not touch.

Jim KC9HI

 

[KC3ECJ]

I respectfully disagree. CHIRP saves and restores memory locations that the OEM software will not touch.

Jim KC9HI

Really?

I programmed my radio with CHIRP to recieve outside of the factory programmed frequencies.

I couldn't undo that with CHIRP, CHIRP wouldn't let me, I had to use the Baofeng software to undo that.

 

[KC9HI]

Really?

I programmed my radio with CHIRP to recieve outside of the factory programmed frequencies.

I couldn't undo that with CHIRP, CHIRP wouldn't let me, I had to use the Baofeng software to undo that.

What do you mean you couldn't undo it with CHIRP? How would CHIRP not let you? Please explain.

Jim KC9HI

 

[Hans13]

What do you mean you couldn't undo it with CHIRP? How would CHIRP not let you? Please explain.

Jim KC9HI

At first, I took it that the radio was set to the bogus far out of band "hack" (it might allow the display to show some really high or low frequencies but it doesn't actually operate, RX or TX, on the frequencies). However, an older build of CHIRP should have easily overwritten the memory with a proper image file.

I too am curious as to what KC3ECJ meant.

 

[KC9HI]

At first, I took it that the radio was set to the bogus far out of band "hack" (it might allow the display to show some really high or low frequencies but it doesn't actually operate, RX or TX, on the frequencies). However, an older build of CHIRP should have easily overwritten the memory with a proper image file.

I too am curious as to what KC3ECJ meant.

Exactly. You save the current state of CHIRP to a CHIRP Radio Image (*.img) file. The you adjust the band limits. They can be set to as low as 1 MHz and as high as 1000 MHz. Most of that is unusable but that is the way CHIRP works. Then if you don't like it, you upload the file that that you saved before hand and your radio will be exactly as it was before you made any changes.

CHIRP does a complete memory dump from the radio and a complete memory upload. The OEM softare just uploads and downloads specific areas of memory. In the worst of cases you can upload a "factory" image with CHIRP an return the radio to the same state it was when it was new.

Jim KC9HI

 

[KC3ECJ]

CHIRP doesn't even want to talk to my radios anymore.

My version of CHIRP is a new build.

 

[com501]

This is what happens when you mess with a radio that costs the manufacturer $11 to make. Not a lot goes into any error checking routines.

 

[Hans13]

CHIRP doesn't even want to talk to my radios anymore.

My version of CHIRP is a new build.

Did you read the information at Miklor's recovery link that I posted early on in this thread? It describes how to use an OLDER version of CHIRP (one that doesn't check the image to the radio) to program the proper base image onto the radio. Writes to the radio will error out if the radio is receiving a signal over the air (I unscrew the antenna and set it on a low traffic frequency) or goes into powersave (I hit monitor to make sure that the radio is awake before writing). Once the proper image is back on the radio, return to the daily build of CHIRP for future programming so it is less likely that an older image will be written to the radio.

There was a problem with some Woxuns after multiple writes because the memory used is supposed to be cheap and has a relatively low MTBF. Once the memory is "worn out", that is it for programming the radio. AFAIK, all of these Baofeng, Woxun, etc use cheaper memory to cut costs so keep that in mind when doing endless writes.

This is assuming that the factory software can communicate with the radio, then the USB to serial chip is okay. Otherwise, it could be a clone cable chip with a driver issue. A link for that is also on the Miklor site.