>>109100023
check if the mode has changed to see if the tool you're using will work at all. i'm not familiar with the tool you're using.
example;
$ ls -l --dereference /dev/input/by-id/usb-Logitech_USB_Receiver-hidraw
crw------- 1 root root 241, 3 May 14 18:19 /dev/input/by-id/usb-Logitech_USB_Receiver-hidraw
here you can see the mode is "crw------" which means it's a character device file, with read/write permissions for root, and no permissions for any other user. the "root root" after it means it's owned by the root user and the root group
you can change the mode (permissions) using;
# chmod --dereference 0660 /dev/input/by-id/usb-Logitech_USB_Receiver-hidraw
$ ls -l --dereference /dev/input/by-id/usb-Logitech_USB_Receiver-hidraw
crw-rw---- 1 root root 241, 3 May 14 18:19 /dev/input/by-id/usb-Logitech_USB_Receiver-hidraw
this effectively add read/write permission to the group that owns the file. the group is still root however, so...
# chown --dereference :$USER /dev/input/by-id/usb-Logitech_USB_Receiver-hidraw
$ ls -l --dereference /dev/input/by-id/usb-Logitech_USB_Receiver-hidraw
crw-rw---- 1 root username 241, 3 May 14 18:19 /dev/input/by-id/usb-Logitech_USB_Receiver-hidraw
this changes the group that owns the file to your user's group, so now any user in your group can read/write the file
this is what the udev rule does, just manually.
note: "--dereference" in these is important as the files in /dev/input/by-id/ are symlinks, and we don't care to change the symlink itself, rather what it points to, that's what --dereference does