How to identify the Galaxy Nexus device in Ubuntu recently started the Galaxy Nexus mobile phone, but since it has been developed in Ubuntu,
However, Ubuntu cannot directly identify GalaxyNexus MTP devices, resulting in 16 Gbit/s Rom being completely unrecognizable under Ubuntu,
Only the adb push and adb install methods can be used to install the program, which does not fully play the role of disk storage.
Therefore, I searched for several methods online and finally solved the problem after a long time. The solution for www.2cto.com is as follows:
1. install the necessary MTP tool set: sudo apt-get install mtp-tools mtpfs
2. Open Galaxy Nexus and select MTP as the storage method instead of PTP. .
3. Check the idVendor and idProduct numbers of your devices. Mtp-detect | grep idVendor (the obtained number is the output red field, idVendor: 04e8) mtp-detect | grep idProduct (the obtained number is the output red field, idProduct: 685c) 4. edit the device file. Gksu gedit/etc/udev/rules. d/51-android.rules: SUBSYSTEM = "usb", ATTR {idVendor} = "VENDORID", ATTR {idProduct} = "PRODUCTID ", MODE = "0666", where VENDORID replaces the idVendor value of your signature, that is, 04e8, followed by the same PRODUCTID.
Note: The quotation marks must be full-width and half-width. You cannot enter them manually. 5. Start related services and rules, set mount points, and grant read and write executable permissions. Sudo service udev restart sudo mkdir/media/GalaxyNexus sudo chmod a + rwx/media/GalaxyNexus sudo adduser YOURUSERNAME fuse (replace YOURUSERNAME with your username here) and then edit the file, gksu gedit/etc/fuse. conf, remove the # signature of the last line,
Change "# user_allow_other" to "user_allow_other ". Www.2cto.com 6. Then, use the alias mechanism to mount and pop up. Echo "alias android-connect = \" mtpfs-o allow_other/media/GalaxyNexus \ "> ~ /. Bashrcecho "alias android-disconnect = \" fusermount-u/media/GalaxyNexus \ ">> ~ /. Bashrcsource ~ /. Bashrc (Pay Attention to the full-width and half-width symbols of the signature again, and manually enter it once to avoid errors) 7. Then, you may not be able to identify the device when running android-connect. log out and log in,
Run android-connect again. However, the mounting process is a little slow. It takes about one minute to wait,
At first, you may mistakenly think that the file is not mounted. However, the corresponding file browser will pop up later, and you can see, copy, and edit the file completely. So far, the entire process is successful and is fully available after testing. Note: If you strictly follow the above steps and pay attention to the full-width and half-width symbols, the problem still persists,
It can be used to check whether the libmtp library is not running normally. It may be in the latest Ubuntu, and the later version cannot run normally,
In this case, you can follow the steps below to update to the latest libmtp library, and then it will be successful.
Tested, and no problem (this step can be done before all previous steps) sudo apt-get install libusb-devwget http://downloads.sourceforge.net/project/libmtp/libmtp/1.1.1/libmtp-1.1.1.tar.gztar-xvf libmtp-1.1.1.tar.gzcd libmtp-1.1.1. /configure -- prefix =/usrmake www.2cto.com sudo make installsudo cp 69-libmtp.rules/etc/udev/rules. d (mayby not needed) sudo service udev restart in fact, after the above nine steps, you can use the mtp device, because you can already use mtp-dectect,
Mtp-files and other commands to view the device and related files, you can also operate on the files,
However, using the command line is troublesome, so mtp-tools mtpfs is required to mount the MTP device,
Copy to operate like a disk. Finally, I would like to thank the people in the Ubuntu community for their selfless dedication to bring more beautiful things to our lives,
Reference: 1. Getting MTP to work with a Galaxy Nexus?
Deercoder, http://askubuntu.com/questions/87667/getting-mtp-to-work-with-a-galaxy-nexus/88481#88481 author