Yotaphoner
Posts: 52
Joined: Fri Jun 09, 2017 3:11 pm

Udev rules for a problematic device

Sat Jul 01, 2017 6:33 am

Hi. I have a Yotaphone 2 and I can't achieve connect it in MTP mode. Just can connect it correctly in PTP mode, even with adb I just can play with it in PTP mode, because in MTP mode only shows ?????? in the device list. So I am trying with udev rules. First I tried, taking que ID vendor and ID product for matching, this :
ATTR(vendor)=="2916" , ATTR(product)=="9139" , NAME="Yota" , SYMLINK+="Yota"
Then someone pass me this link : https://github.com/M0Rf30/android-udev- ... roid.rules ,And from it take the info and writed a new udev rule like this :
ATTR{idVendor}!="2916", GOTO="not_Yota" , ENV{adb_user}="yes" , ATTR{idProduct}=="9139", SYMLINK+="android_adb" , GOTO="android_usb_rule_match" , LABEL="not_Yota"
But no one worked. I savedthe file in /etc/udev/rules.d/10-local.rules. In /proc/partitions appears nothing about it, nor in fdisk -l

ANy idea? I tried in 2 different linux.
Thanks

Yotaphoner
Posts: 52
Joined: Fri Jun 09, 2017 3:11 pm

Re: Udev rules for a problematic device

Mon Jul 03, 2017 12:14 am

As another way of solving it... I connected the phone in recovery mode and it connects perfectly as in MTP mode. The important thing is itdoesn't appears in /proc/partitions nor mount nor fdisk, butit is in file manager with this path in direction bar: mtp://[usb:001,017]/

How can I do to mount the device correctly and work with all partitions of it?

Return to “Advanced users”