CHIRP

Is this firmware from Quansheng themselves?

Okay, well, we can't just add the firmware version as blessed unless we know that it works the same way as the OEM firmware. Perhaps @Jacek Lipkowski SQ5BPF knows?

If not, best plan would be to program the radio specifically with the OEM or other known (like egzumer) firmware.

Thanks for the advice. Do you know where I can find the original firmware? I can't use any mod now, the device is not detected when in flash mode. Not UVMOD not Egzumer or F4HWN.

Thanks

TERRENCE RODRIGUEZ wrote in #note-5:

Thanks for the advice. Do you know where I can find the original firmware? I can't use any mod now, the device is not detected when in flash mode. Not UVMOD not Egzumer or F4HWN.

Please note that this is a chirp support forum, not a radio support forum. Also chirp will support the factory firmware, the rest is best-effort. Alternative firmware authors can of course release their own driver, or a variation of this driver, and support it. But I will write a description, also for the benefit of others.

Now getting back to your problem, the radio has multiple modifiable areas: the eeprom (where configuration is kept, including calibration), the firmware flash area (there the firmware is kept), the bootloader flash area, and the NVR area (where some calibration data is kept, and some software touches this, but usually it's read, usually it's not written). By playing around with the firmware you have written over the flash. You have probably also overwritten the calibration area in the eeprom. Hopefully the NVR area and the bootloader area have not been touched.

You have written "Only thing I suspect is that it’s firmware was updated and now your system can’t work with it." - this didn't happen by itself, did it? :)

If you have not overwritten the NVR area (most probably not) and flsh (hopefully not), then you should be able to return the radio to factory condition.
I will show how to do this using k5prog https://github.com/sq5bpf/k5prog (don't mistake this with k5prog-win) under linux, you might be able to use other software, but no

restoring factory firmware¶

First flash factory firmware. You can use k5prog and k5_flash.raw from the k5prog repository, which is 2.01.23 factory firmware.

restoring the the configuration in the eeprom¶

Second restore the eeprom from backup. Do you have a backup of the eeprom contents? (including the calibration area)

Did you backup the eeprom using some tool? (like they all tell you to do) Use it to restore.

Did you download the configuration using chirp while the radio was still using factory firmware? The first 8192 bytes of the file downloaded by chirp are the eeprom image. Please do this: dd if=chirp_downloaded_image.img of=eeprom_backup.raw bs=1 count=8192 and upload this using k5prog: ./k5prog -f eeprom_backup.raw -B -v -v -v -v -v

If you don't have a backup of the eeprom calibration data, then it's bad. Do a backup of what you have. And then you can use my eeprom dump from the k5prog repository (uvk5_original_eeprom.raw):
./k5prog -f uvk5_original_eeprom.raw -B -v -v -v -v -v

You can use software other than kprog under linux, using similar procedures. In that case please refer to that software's documentation.

Yes, it's intentionally disabled and limited so I can look to see if it seems reasonably safe. Thanks for the image, I'll have a look tomorrow and follow up.

Works great so far! thanks so much!

Can you expand on "works great" please? We're kinda relying on your testing before this goes out to more users. Have you made edits and uploaded? Can you describe the changes you've made?

Thanks for your help.