Hello and thank you for maintaining this list.
I own the Intl. Samsung Galaxy S4 GT-I9500 Exynos Octo Core and was having a hard time to make it recognized within Windows so I can use Odin to root it.
The issue was that my current kernel [OS: Chakra, kernel 3.9.2-CHAKRA] detects it as 04e8:6860 while it's correct ID is 04e8:685d (I got aware of this later when rebooted the smartphone into recovery mode), once I corrected the ID I created a new rule following advice here: http://developer.android.com/tools/device.html and then I finally was able to make the Windows guest recognize it.
Note: this is my first ever contribution to a GIT project/repository, please excuse if there's anything wrong with it :/
Best regards.
Google Nexus 4/7 devices change their id when you enable debugging or go into the bootloader. The id's for my Nexus 4 and 7 according to lsusb are these:
Nexus 4:
Fastboot - ID 18d1:4ee0 Google Inc.
MTP - ID 18d1:4ee1 Google Inc. Nexus 4
MTP+ADB - ID 18d1:4ee2 Google Inc. Nexus 4 (debug)
Nexus 7:
Fastboot - ID 18d1:4e40 Google Inc. Nexus 7 (fastboot)
MTP - ID 18d1:4e41 Google Inc. ASUS Nexus 7 (MTP modus)
MTP+ADB - ID 18d1:4e42 Google Inc. Nexus 7 (debug)
I hope I made the necessary changes. Also the Nexus 10 seems to have a wrong id, so I commented it out since it would be the same as for the Nexus 4 in MTP mode. Someone with the device should check. Also I deleted the entries for the Nexus 4/7 in the Samsung devices section. As far as I understand Udev (not much sadly), they are duplicates, but it should be checked by someone who understands Udev.
udev automatically gives the user in the active
session permissions on all devices with the
uaccess tag (see also 70-uaccess.rules). This
means that it not necessary anymore to be
in the adbusers group if the user is in an active
session (which should pretty much cover 99% of
all use cases).
