On Tue, 2017-04-04 at 15:06 +0200, Johan Hovold wrote: > > SerialNumber=3 > > [73.663718] usb 1-1: Product: Android > > [73.663720] usb 1-1: Manufacturer: MediaTek > > [73.663722] usb 1-1: SerialNumber: X560I1ZR5A241388 > > And here it comes up with a new personality (if you didn't switch the > device). As described to Oliver before, I try to catch a MiTM, and my Android is near-brick statement.. In my case I observe different behavior of Android phone. When connected in fastboot mode I can see adb devices output: 0123456789ABCDEF offline this fake serial number belong Ragentek j5808 chip. And I have made symlink /dev/mediatek in udev rules, it's looks like work, I cal see it wit ls -la (but can't send|receive AT commands via minicom). If I boot normally, the output of adb devices shown as X560I1ZR5A241388 offline this serial belong to real Mediatek Android device. > > > [root@gigabyte flash-kernel]# ll /dev/ttyUSB0 > > ls: cannot access /dev/ttyUSB0: No such file or directory > > How did you get the generic driver to bind to 0e8d:2000? You need to > tell the generic driver to bind also to 0bb4:0c01, for example, > > echo 0bb4 0c01 > /sys/bus/usb-serial/drivers/generic/new_id Yes, I have pushed it before: cat /sys/bus/usb-serial/drivers/generic/new_id 0e8d 2000 > Johan -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
