![]() Here is a sequence of commands to run to carry out the procedure: My dongle uses an older bootloader so I didn't look into that in details. Note that some of the most recent firmwares (from the Logitech repository) are signed (*.shex file instead of *.hex file) and require a recent bootloader. The basic idea is simple, just grab a known firmware, patch the PID/VID bytes, fix the CRC checksum and flash it back to the receiver. Among other things, it contains the CRC algorithm and location of the expected checksum in flash. This repo contains some reverse-engineering information and tools for the unifying receiver. This is the official Logitech repository for several of their products, including the unifying receivers. This is the main tool to update firmware of the receiver dongle See examples from issue 4 Some useful resources To quickly identify the chipset via the firmware version, you can use this command fwupdmgr get-devices | grep "Unifying Receiver" -A3. There is a newer version of the unifying receiver based on TI chip (C-U0008 and firmware RQR24) which I don't know if will work, but maybe the same principle will apply. Note this is carried out on the Nordic nRF24LU1-based receiver C-U0007 (firmware version RQR12.0X). Changing the PID of one of the dongles was the solution. ![]() I did this because I wanted to passthrough one of my Logitech keyboards to a virtual machine, however I have two Logitech unifying receivers connected to the host machine with identical VID/PIDs, so it's a bit tricky to edit my VM config to passthrough the one I want. ![]() This is a guide on how to manually change the VID/PID (046d:c52c) for Logitech unifying receiver. Logitech unifying receiver VID/PID modification
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |