search

OK2MOP / MD1702-tools

Tools to work with firmware and SPI flash data of DM-1702 and DM-X radios
24 stars 6 forks source link

Support for L05.00.05 Firmware #5

Open jejdouay opened 3 years ago

jejdouay commented 3 years ago

I have a bright new MD-1702 with the Firmware L05.00.05.

Using the tool I could not do anything except reading the version id or read the FW

After trying to get the codeplug inside the radio, the firmware got damaged and nothing is working any more.

Trying to get the FW back in is also not working, I guess this firmware uses a different protocol.

Can you add support for this firmware ?

btw, the bootloader from the DM1702-V2 says DM1706-V2... Interesting isn't it ?

Thanks in advance !

OK2MOP commented 3 years ago

Just to clarify, you were able to read the firmware but not the codeplug? And you tried to flash codeplug/firmware with the tool when it was not working? I don't have access to any device with L05.00.05, so I cannot test it and check the communication protocol neither now nor in foreseeable future.

Can you contact me and send me at least the backed-up firmware, I may have a look at it if it is possible to flash it to some device (but if the bootlader says DM1706-V2, it may be totally different).

Did you back up the codeplug in official application before uploading the wrong one? If so, try to flash the codeplug from it back (or the default codeplug budled with CPS), but if you tried to flash the firmware back, you might have broken something.

Maybe the seller can provide the firmware and CPS for the official flashing application for you? Bootloader will still work, so it should be possible to reflash everything from scratch.

jejdouay commented 3 years ago

I was not able with the Baofeng CPS (1.00.79) to read the code plug. It brings after a second a read error. Same for writing or trying to flash a new firmware !

I was able to read the Firmware with your tool, it is attached to this email.

Reading the Codeplug with your tool failed after some download, with a 0x40 id missing or something like that. After removing this check in the code, I was able to download something and the CPS software was able to read it without any problems, so I have a backup.

Nor with your tool or the CPS software was able to write the code plug back. Both tools stop after a short time with a read error message.

I am pretty sure I screwed the radio big time. I don't even know if I will ever be able to recover it. Baofeng is also not really helping to solve this issue. I am pretty good with programming and also python. If you can guide me on how I could get the communication protocol or anything like this, I could write some code and share it with you.

Thanks for the help, great tool by the way !

Jerome

On Thu, Jan 28, 2021 at 5:45 PM OK2MOP notifications@github.com wrote:

Just to clarify, you were able to read the firmware but not the codeplug? And you tried to flash codeplug/firmware with the tool when it was not working? I don't have access to any device with L05.00.05, so I cannot test it and check the communication protocol neither now nor in foreseeable future.

Can you contact me and send me at least the backed-up firmware, I may have a look at it if it is possible to flash it to some device (but if the bootlader says DM1706-V2, it may be totally different).

Did you back up the codeplug in official application before uploading the wrong one? If so, try to flash the codeplug from it back (or the default codeplug budled with CPS), but if you tried to flash the firmware back, you might have screwed something.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/OK2MOP/MD1702-tools/issues/5#issuecomment-769216633, or unsubscribe https://github.com/notifications/unsubscribe-auth/ASUKV5MFW6TSNQQU7H6BEU3S4GIBFANCNFSM4WXLPAFA .

OK2MOP commented 3 years ago

You may try a different tool for codeplug download/upload, e.g. for Retevis RT-72 which uses the newer protocol added to this tool (for L02 firmware). But do not flash the extracted firmware with it, it uses encrypted firmware files! This may help to flash the normal CPS (if it uses C1.00.01.001).

BTW, did you try the ./md1702_dfu.py versions before trying to flash? What values did it return (remove the DeviceID serial number), especially concerning the CPS format?

Mine (for the new protocol) looks like this:

FWVersion = L02.02.001 RefDate = 2018-07-10 DataFormat = D1.00.02.002 GPSFormat = S1.00.01.001 CPSFormat = C1.00.01.001 Voices = 0x14b000 - 0x159fff HZKFont = 0x0fb000 - 0x141fff Recordings = 0x000000 - 0x000000 Settings = 0x001000 - 0x0fafff Logo = 0x145000 - 0x14afff Unknown1 = 0x142000 - 0x144fff CSVContacts = 0x246000 - 0xffffff

OK2MOP commented 3 years ago

OK, after some discussion and experiments the firmware L05.00.05 itself works with the CPS, but the bootloader for MD1706-V2 is not supported, flashing of the firmware is broken.

OK2MOP commented 1 year ago

Unfortunately, I only have the older radios with V1 bootloader and backups of L05.00.05.bin and L02.02.001.bin.

But I thought I have disabled flashing of V2 bootloader in my code to prevent bricking. If you have tried to flash using stock CPS with L5.00.05.bin, it probably failed due to the firmware encryption/decryption. Maybe ask your seller to provide you with your version of the firmware for official CPS?