The original post is in: Http://www.hiapk.com/bbs/thread-3342-1-1.html When G1 is connected through USB in Ubuntu 9.04 and ADB is used, the device cannot be found. The solution is as follows: 1) run on the terminalLsusb The following similar records will be found in the results: Bus 002 device 015: Id 0bb4: 0c02 high tech Computer Corp. 2) sudo gedit/etc/udev/rules. d/50-android.rules Add the following text to the open file: Subsystem = "USB", sysfs {"high tech Computer Corp." }== "0bb4", mode = "0666 ″ 3)Sudo gedit/etc/udev/rules. d/90-android.rules Add the following text to the open file: Subsystem = "USB", ATTR {"high tech Computer Corp." }== "0bb4", mode = "0666 ″ 4) run the following command: Sudo chmod A + Rx/etc/udev/rules. d/50-android.rules Sudo chmod A + Rx/etc/udev/rules. d/90-android.rules Sudo/etc/init. d/udev restart 5) in the android SDKToolsRun in Directory Sudo./ADB kill-Server Sudo./ADB Devices ----------------------------------------------------------------- The end of the post Mainly, 1. Use the device manufacturer name "high tech Computer Corp." To replace idvendor on the official website. (I guess this is what people mean) 2. Create one more Sudo gedit/etc/udev/rules. d/90-android.rules content: Subsystem = "USB", ATTR {"high tech Computer Corp." }== "0bb4", mode = "0666 ″ Then refresh the USB and ADB server. If the image is flushed, you also need a boot image, which is the same as the boot image of the kernel loaded when the Desktop Linux is started, the wide spread on the Internet seems to be a recovery in the report issued along with the flash Machine Tool of the window version. IMG, Put the image mentioned above in the same directory of fastboot, and then let the mobile phone enter the startup interface of the three Android robots (G2 is the bounce key + press at the same time) then run fastboot boot recovery from the terminal. IMG, after the IMG file is transferred, the phone will automatically restart, that is, enter the menu of the flash machine, then wipe, update. |