You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Apr 10, 2024. It is now read-only.
Please also patch the first letter of the version number string. I would propose m (0x6d).
So for example for k5_2.01.23 patch byte 0xe210 to 0x6d, so it becomes m5_2.01.23
The Quansheng software will accept any value anyway, you can test this with k5emulator.
And my chirp driver can use the first letter of the version to enable programming in the full range accepted by the BK4819 chip (note: i've already uploaded a driver with full range to https://chirp.danplanet.com/issues/10478 , this was by request of the users who could not program out of band frequencies with Quansheng software).
BTW you beat me to it :) I'm reverse engineering the firmware too, but didn't release a working version.
The text was updated successfully, but these errors were encountered:
Hi! First of all, I'd like to say thank you for your work in reverse engineering the protocols, storage formats and other characteristics of the firmware. I could not have done it without your efforts, they helped me massively.
I agree, there should be some distinction in the version number to be able to identify modified firmwares. I tried to set the version number once to something recognizable before publishing it and nearly bricked my radio 😂 but that was my fault for modifying it to be longer than the original without modifying the buffer.
Changing k5 to m5 is a good idea, especially if the Quansheng flashing software does not mind it. I would not want anyone to be locked out of flashing their radio without modifying the software.
Thanks again!
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Please also patch the first letter of the version number string. I would propose m (0x6d).
So for example for k5_2.01.23 patch byte 0xe210 to 0x6d, so it becomes m5_2.01.23
The Quansheng software will accept any value anyway, you can test this with k5emulator.
And my chirp driver can use the first letter of the version to enable programming in the full range accepted by the BK4819 chip (note: i've already uploaded a driver with full range to https://chirp.danplanet.com/issues/10478 , this was by request of the users who could not program out of band frequencies with Quansheng software).
BTW you beat me to it :) I'm reverse engineering the firmware too, but didn't release a working version.
The text was updated successfully, but these errors were encountered: