any one working with adb (android) interface ?

Thu Nov 24 09:10:16 UTC 2011

Start the adb server under root, that is a quick way around the usb
security.
Su bash
Adb kill-server
Adb devices
Exit

This should list your device and adb works until the server needs to be
restarted

sent from android mobile
On Nov 24, 2011 9:50 AM, "J. Bakshi" <bakshi12 at gmail.com> wrote:

> On Wed, 23 Nov 2011 14:13:24 -0500
> scott <redhowlingwolves at nc.rr.com> wrote:
>
> > On 11/23/2011 01:46 AM, J. Bakshi wrote:
> > > On Wed, 23 Nov 2011 13:57:49 +0800
> > > "Sharl.Jimh.Tsin"<amoiz.shine at gmail.com>  wrote:
> > >
> > >> 在 2011-11-23三的 11:09 +0530，J. Bakshi写道：
> > >>> Dear list,
> > >>>
> > >>> I'm trying to root my android within linux using superoneclick which
> uses adb command
> > >>>
> > >>> Since last two days I tried to root my lenevo A60 aka spice Mi-350 (
> android - 2.3.3 ) without any success and now searching for help.
> > >>> Within linux I am trying SuperOneClick and during the process I have
> found actually the adb can't communicate with the phone.
> > >>> If I run "adblinux discover" as root it shows as following
> > >>>
> > >>> ` ` `
> > >>> * daemon not running. starting it now on port 5037 *
> > >>> * daemon started successfully *
> > >>> List of devices attached
> > >>>
> > >>> ` ` `
> > >>>
> > >>> And due to this the superoneclick is not progressing.
> > >>>
> > >>> obviously at phone I have usb debugging on. I have also added the
> following udev rules found at http://idroidproject.org/wiki/ADB
> > >>>
> > >>>
> > >>> SUBSYSTEM=="usb" ID_VENDOR_ID=="0bb4", MODE="0666"
> > >>> SUBSYSTEM=="usb" ID_VENDOR_ID=="18d1", MODE="0666"
> > >>> SUBSYSTEM=="usb" ID_VENDOR_ID=="05ac", MODE="0666"
> > >>>
> > >>> but no luck. Could anyone kindly show me the way to activate adb so
> that I can run superoneclick .. Or any other way to root it ....PLEASE
> > >>>
> > >>>
> > >>> DEBUG within Linux
> > >>> ================
> > >>>
> > >>> lsusb
> > >>>
> > >>> ``
> > >>> Bus 002 Device 116: ID 2006:0c03
> > >>> ` `
> > >>>
> > >>> /var/log/messages
> > >>> ------------------
> > >>>
> > >>> Nov 20 15:38:56 shiva kernel: [320568.881611] usb 2-1.2: new high
> speed USB device number 117 using ehci_hcd
> > >>> Nov 20 15:38:56 shiva kernel: [320568.975012] usb 2-1.2: New USB
> device found, idVendor=2006, idProduct=0c03
> > >>> Nov 20 15:38:56 shiva kernel: [320568.975019] usb 2-1.2: New USB
> device strings: Mfr=1, Product=2, SerialNumber=3
> > >>> Nov 20 15:38:56 shiva kernel: [320568.975025] usb 2-1.2: Product:
> Mi-350
> > >>> Nov 20 15:38:56 shiva kernel: [320568.975028] usb 2-1.2:
> Manufacturer: Spice
> > >>> Nov 20 15:38:56 shiva kernel: [320568.975032] usb 2-1.2:
> SerialNumber: 0123456789ABCDEF
> > >>> Nov 20 15:38:56 shiva kernel: [320568.976814] scsi116 : usb-storage
> 2-1.2:1.0
> > >>> Nov 20 15:38:57 shiva kernel: [320569.973037] scsi 116:0:0:0:
> Direct-Access     Spice    Mi-350           0100 PQ: 0 ANSI: 2
> > >>> Nov 20 15:38:57 shiva kernel: [320569.974216] sd 116:0:0:0: Attached
> scsi generic sg3 type 0
> > >>> Nov 20 15:38:57 shiva kernel: [320569.977437] sd 116:0:0:0: [sdc]
> Attached SCSI removable disk
> > >>>
> > >>> -- with best wishes
> > >>>
> > >>
> > >>   you rooted your android phone with superOneClick under Ubuntu ? i
> > >> failed again&  again.
> > >>
> > >
> > > Just the opposite :-( I can't :-(
> > > Hence asking help
> > >
> > I've rooted two phones using adb from Ubuntu. Check out root.bat(1) and
> > see if there is a version for your phone. If there is, open the file and
> > follow the adb commands and you should be rooted.
> >
> > Scott
> >
> > 1: >
> >
> http://www.google.com/search?client=ubuntu&channel=fs&q=root.bat&ie=utf-8&oe=utf-8
> >
>
> Thanks for your kind attention.. but no luck here.
>
> I have used the linux version i.e. .sh as root and it reports
>
> `````````````````````````````
>           Root for the Samsung Prevail
>
>                Exploit By Bliss
>
>               One Click Done by
>                 Shabbypenguin
>
> Press any key to continue...Starting adb server
> * daemon not running. starting it now on port 5037 *
> * daemon started successfully *
> You need to enable usb debugging first
> Go to settings > applications > development
>
> `````````````
>
> I have set the debug mode and toggle it many times but always the same
> report.
>
> The problem is same as before.... no adb interface through which adb
> command can work.
>
> Here is the log when I attach mt phone without mounting the sd card
>
> ``````````````````````````
> Nov 24 14:19:24 shiva kernel: [217696.959237] usb 2-1.1: USB disconnect,
> device number 64
> Nov 24 14:19:26 shiva kernel: [217698.944765] usb 2-1.2: new high speed
> USB device number 65 using ehci_hcd
> Nov 24 14:19:26 shiva kernel: [217699.038232] usb 2-1.2: New USB device
> found, idVendor=2006, idProduct=0c03
> Nov 24 14:19:26 shiva kernel: [217699.038239] usb 2-1.2: New USB device
> strings: Mfr=1, Product=2, SerialNumber=3
> Nov 24 14:19:26 shiva kernel: [217699.038244] usb 2-1.2: Product: Mi-350
> Nov 24 14:19:26 shiva kernel: [217699.038248] usb 2-1.2: Manufacturer:
> Spice
> Nov 24 14:19:26 shiva kernel: [217699.038251] usb 2-1.2: SerialNumber:
> 0123456789ABCDEF
> Nov 24 14:19:26 shiva kernel: [217699.040041] scsi71 : usb-storage
> 2-1.2:1.0
> Nov 24 14:19:27 shiva kernel: [217700.036190] scsi 71:0:0:0: Direct-Access
>     Spice    Mi-350           0100 PQ: 0 ANSI: 2
> Nov 24 14:19:27 shiva kernel: [217700.037855] sd 71:0:0:0: Attached scsi
> generic sg3 type 0
> Nov 24 14:19:27 shiva kernel: [217700.041718] sd 71:0:0:0: [sdc] Attached
> SCSI removable disk
> ```````````````````````````
>
>
>
>
> --
> ubuntu-users mailing list
> ubuntu-users at lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/ubuntu-users/attachments/20111124/8da5bb92/attachment.html>