Guest Michael Vegfruit Posted August 25, 2010 Report Share Posted August 25, 2010 (edited) No, I've done the same steps pretty much as the original poster, including checking the USB ids against what I have in my udev rules, and they look the same (I guess that is what you mean by USB code?). Actually, you have encouraged me to try checking lsusb with the device mounted and unmounted. I don't see the difference in device IDs that the original poster had, so maybe it is not the same problem. ---- Edit: Sorry naguz, I was typing at the same time as you. So, that's what this usb_switchmode is doing, changing how the device is recognised? V frustrating. Edited August 25, 2010 by Michael Vegfruit Link to comment Share on other sites More sharing options...
Guest brickedMyHuaweiU8230 Posted September 9, 2010 Report Share Posted September 9, 2010 Hm, hi, Same thing happening on my Huawei U8230. But i'm running Mac OS X, so the OP's solution doesn't seem to work... Any alternative solution? ugh Link to comment Share on other sites More sharing options...
Guest cybertk Posted March 24, 2011 Report Share Posted March 24, 2011 Hey, I used to be able to use ADB with my phone back in 1.5, in Linux. My issue is not a permission-related since I've also tried to start the ADB server with root and have no luck. When I type "./adb devices" (or "sudo ./adb devices") I get an empty list. Is this happening to somebody else? Any hints on what is happening? This may be USB-mode issue. Try $ wget http://android-autotool.googlecode.com/files/adb_mode $ sh adb_mode u8230 $ wget http://android-autotool.googlecode.com/files/adb_reset $ sh adb_reset Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now