StrangeOrange
New Member
- Joined
- Apr 25, 2016
- Messages
- 15
- Reaction score
- 7
- Country
- Afghanistan
- Dash Cam
- Mio MiVue 388, 588
Hello,
Has anyone tried making changes to the firmware on a Mio MiVue device? Mine's a 588 but I think the procedure is similar across all the 5xx as well as possibly 6xx device range.
The firmware file SD_CarDV.bin is neither compressed nor encrypted, an can be sifted through with utilities such as strings or binwalk, and potentially interesting areas can then be modified with a hex editor.
There is a certain obstacle with the checksum being verified upon attempting to flash a new firmware. One way to go around this restriction is to use a hardware programmer with a desoldered memory chip. It has been documented (originally in Russian), although the author's objective was to recover from a hardware brick, so just for experimentation's sake it might seem like an overkill.
Another solution would be to recalculate the checksum after modifying the firmware. The 16-byte hash is stored in the firmware file at bytes 16-31 (bytes 0-15 are the common header, and the actual flashable firmware file starts at offset 32).
If anyone tried experimenting with the firmware, please share your findings.
Fun fact: along with one of the previous versions of the 588 firmware, Mio accidentally posted all the tools they themselves use to generate the SD_CarDV.bin file. Unfortunately, having realized their mistake, they eventually updated the download to remove them. The file name was MiVue588_SD_CarDV_VS00.0C.06.FT1.zip , and the download had the size of 10.7 MB, while the updated file without the tools, available from Mio's website as of now, is just 5.2 MB.
Has anyone tried making changes to the firmware on a Mio MiVue device? Mine's a 588 but I think the procedure is similar across all the 5xx as well as possibly 6xx device range.
The firmware file SD_CarDV.bin is neither compressed nor encrypted, an can be sifted through with utilities such as strings or binwalk, and potentially interesting areas can then be modified with a hex editor.
There is a certain obstacle with the checksum being verified upon attempting to flash a new firmware. One way to go around this restriction is to use a hardware programmer with a desoldered memory chip. It has been documented (originally in Russian), although the author's objective was to recover from a hardware brick, so just for experimentation's sake it might seem like an overkill.
Another solution would be to recalculate the checksum after modifying the firmware. The 16-byte hash is stored in the firmware file at bytes 16-31 (bytes 0-15 are the common header, and the actual flashable firmware file starts at offset 32).
If anyone tried experimenting with the firmware, please share your findings.
Fun fact: along with one of the previous versions of the 588 firmware, Mio accidentally posted all the tools they themselves use to generate the SD_CarDV.bin file. Unfortunately, having realized their mistake, they eventually updated the download to remove them. The file name was MiVue588_SD_CarDV_VS00.0C.06.FT1.zip , and the download had the size of 10.7 MB, while the updated file without the tools, available from Mio's website as of now, is just 5.2 MB.
Last edited: