CHIRP

Most likely the radios have been changed in a way that made them incompatible with CHIRP. Unfortunately you didn't follow the instructions that you claimed to have read. There is not much that can be done without access to the 'new' radio or the information the should have been provided based on the instructions.

my apologies, and thank you for your time and reply, there was no debug generated afaict if thats what you mean? i do have one radio that is flaky i could donate to the cause, and one already taken apart that failed. i'd love to help the chirp project in any way possible. if i missed something please let me know i thank you for your patience and time.

gaspo gaspo wrote in #note-2:

my apologies, and thank you for your time and reply, there was no debug generated afaict if thats what you mean? i do have one radio that is flaky i could donate to the cause, and one already taken apart that failed. i'd love to help the chirp project in any way possible. if i missed something please let me know i thank you for your patience and time.

I don't know how that can be. Just the simple act of launching CHIRP always creates a debug.log file. It may not contain any useful information, but I won't know that until I can see it.

So launch CHIRP-next. Try to download from the radio. Once it prompts with the "no response from radio", cancel the prompt, tap 'Help' in the menu bar and either choose 'Open debug log' or "Show debug log location'. Attach the latest debug.log to this issue.