Sign Up Now FAQ
Signup Now
In order to make a post or to start a new thread and or to interact with other
members of this board, you wil need to create an account first.
If this is your first visit, be sure to check out the FAQ. You have to register before you can post. If you have any problems, please contact us.
Flash a phone to Cricket Wireless Become a supporting member of Cricket Users Forum

 
Welcome to Cricket Users!



Results 1 to 7 of 7
  1. #1
    Member
    Points: 558, Level: 11
    Overall activity: 0%

    Reputation
    Reputation 12
    Join Date
    Jan 2012
    Location
    CA
    Posts
    33



    Solved: adb won't connect in Linux

    Hello,

    I have just bough a ZTE Score and am trying it out to make sure I want to keep it.

    I need to be able to use adb, but cannot seem to connect. I am following the directions from this thread, but it doesn't seem to apply to a linux user. The first step is to install ZTE Score drivers on your computer I tried this in Wine, but that didn't work (didn't think it would). According to a blog entry linux and mac don't require any drivers for the blade.

    Any how, I downloaded "zergRush automated linuz root script" from info in
    this thread


    , and it hangs on 'adb wait-for-device'.
    Code:
    $ adb wait-for-device 
     * daemon not running. starting it now on port 5037 *
     * daemon started successfully *
    After a good amount of time I wind up terminating the command.

    I need to get this working, or return the phone and try a different one.

    Is there anyone that has done this?

    I have enabled debugging and unknown sources on the phone.

    I plug in USB and device notifies USB Connected with a button to turn on USB storage (I don't).
    I navigate to Settings/Application/Development and toggle debugging off/on (suggested in script) and the device notifies USB debugging is connected.

    Not sure what to do next.

    Help is appreciated.

    Thank you.

    -Regards,
    Brian

    Last edited by bsquared; 02-06-2012 at 10:54 PM. Reason: Marked as solved

  2. Remove this advertisement.
  3. #2
    Member
    Points: 558, Level: 11
    Overall activity: 0%

    Reputation
    Reputation 12
    Join Date
    Jan 2012
    Location
    CA
    Posts
    33



    After some further digging I found that in linux the /etc/udev/rules.d folder needs to be modified for adb.

    I found the basic information
    here


    . And ArchLinux information
    here


    .

    I created 51-android.rules in the directory above and edited it as described in the links.
    Code:
    ##
    # android udev usb rules
    #
    # The idProduct changes when usb storage is turned on.
    # The hidden partiton is mounted when turned off. 
    # The FAT16 partition is mounted when turned on
    #
    # When connected to device, and usb storage is off.
    # Bus 001 Device 024: ID 19d2:fff5 ONDA Communication S.p.A. 
    #
    # when connected to device and usb storage is on.
    # Bus 001 Device 024: ID 19d2:fff6 ONDA Communication S.p.A. 
    ##
    
    SUBSYSTEM=="usb", ATTR{idVendor}=="19d2", MODE="0666", GROUP="adbusers"
    SUBSYSTEM=="usb", ATTR{idVendor}=="19d2", ATTR{idProduct}=="fff5",SYMLINK+="android_adb"
    SUBSYSTEM=="usb", ATTR{idVendor}=="19d2", ATTR{idProduct}=="fff5",SYMLINK+="android_fastboot"
    
    # SUBSYSTEM=="usb", ATTR{idVendor}=="19d2", ATTR{idProduct}=="fff6",SYMLINK+="android_adb"
    # SUBSYSTEM=="usb", ATTR{idVendor}=="19d2", ATTR{idProduct}=="fff6",SYMLINK+="android_fastboot"
    Unfortunately, this still did not work.
    Code:
    adb devices
    * daemon not running. starting it now on port 5037 *
    * daemon started successfully *
    List of devices attached
    An example for ZTE on ArchLinux
    AUR


    has this entry
    Code:
    #      ZTE
    SUBSYSTEM=="usb", ATTR{idVendor}=="19d2", MODE="0666", GROUP="adbusers"
    #      Blade
    SUBSYSTEM=="usb", ATTR{idVendor}=="19d2", ATTR{idProduct}=="1353", 
    SUBSYSTEM=="usb", ATTR{idVendor}=="19d2", ATTR{idProduct}=="1351", SYMLINK+="android_adb"
    So I modified mine eliminating fast boot and using both ids.
    Code:
    SUBSYSTEM=="usb", ATTR{idVendor}=="19d2", MODE="0666", GROUP="adbusers"
    SUBSYSTEM=="usb", ATTR{idVendor}=="19d2", ATTR{idProduct}=="fff5",
    SUBSYSTEM=="usb", ATTR{idVendor}=="19d2", ATTR{idProduct}=="fff6",SYMLINK+="android_adb"
    still no success.

    Hopefully some kind soul or divine intervention will guide me to the solution before I have to return the device and try another.

    Thank you.

    Regards,
    Brian






  4. #3
    Verified Developer
    Points: 3,291, Level: 35
    Overall activity: 0%
    PlayfulGod's Avatar
    Reputation
    Reputation 20
    Join Date
    Aug 2011
    Location
    NW Georgia
    Posts
    355



    check your usb cable, have seen alot of ppl having issues with adb n cheap usb data cables lately.

  5. #4
    Member
    Points: 558, Level: 11
    Overall activity: 0%

    Reputation
    Reputation 12
    Join Date
    Jan 2012
    Location
    CA
    Posts
    33



    Thanks for the reply.
    It is Chinese (QVS - Quality Value Service) so I figured it would like this phone -). It seems to work fine for data transfer and charging.

    I'll try a Belkin and post back the results.

    Thank you.

    Regards,
    Brian

  6. #5
    Member
    Points: 558, Level: 11
    Overall activity: 0%

    Reputation
    Reputation 12
    Join Date
    Jan 2012
    Location
    CA
    Posts
    33



    Still no luck. I got a quality cable (I guess - it cost enough), and adb still lists no devices.

  7. #6
    Member
    Points: 558, Level: 11
    Overall activity: 0%

    Reputation
    Reputation 12
    Join Date
    Jan 2012
    Location
    CA
    Posts
    33



    I was banging head against this for a few days. I tried all the udev rules out there. Then realized they didn't apply if running as root. so I googled my device id and saw
    usb_modeswitch


    in a post. I read about it and it looked promising. I installed the package and problem is solved.

    Now I can start the hard stuff.

    Thanks, I hope this helps someone else.

    Regards,
    Brian

    Last edited by bsquared; 02-06-2012 at 10:57 PM. Reason: Added details

  8. #7
    Junior Member
    Points: 122, Level: 2
    Overall activity: 2.0%

    Reputation
    Reputation 10
    Join Date
    Feb 2012
    Location
    Brownsville
    Posts
    1



    Quote Originally Posted by bsquared View Post
    I was banging head against this for a few days. I tried all the udev rules out there. Then realized they didn't apply if running as root. so I googled my device id and saw
    usb_modeswitch


    in a post. I read about it and it looked promising. I installed the package and problem is solved. Now I can start the hard stuff. Thanks, I hope this helps someone else. Regards, Brian
    How exactly did you use usb_modeswitch for the phone? I connected the phone thru a usb cable but it doesn't appear when i run lsusb. Did yours show up? Or did you use usb_modeswitch before it showed up on lsusb?


 

 

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Advertise With Us?
Advertise with us? (Position 1 - Advertise with Us) Small Banner