Develop Bugs

using adb with galaxy nexus

what does our phone have to be in to use adb? ive never used it before but want to to obtain root without unlocking the bootloader and losing my info. is it rebooted in adx mode? just turned on normally? off?
thanks!

You cannot root without unlocking the bootloader! To access adb you need to be in OS and have debugging enabled under Developer options in the settings.

RTContent said:
You cannot root without unlocking the bootloader! To access adb you need to be in OS and have debugging enabled under Developer options in the settings.
Click to expand...
Click to collapse
i was directed here
http://forum.xda-developers.com/showpost.php?p=23290676&postcount=1
for a workaround to rooting without unlocking the bootloader

Wow, I must have missed that news. Apologies! Have you tried replying in that thread then?

RTContent said:
Wow, I must have missed that news. Apologies! Have you tried replying in that thread then?
Click to expand...
Click to collapse
you already answered my question to be in the OS with debugging enabled! thanks!

You could re-lock the bootloader though if you ever wish to unroot your phone...

my computer wont allow me to recognize my gnexus using adb. im following these steps - http://droidmodderx.com/galaxynexus/how-to-set-up-the-sdk-for-galaxy-nexus
and i know i have already installed the dirvers previously, but when i use the cmd prompt, my computer does not find my device whatsovever. tried uninstalling it from device manager, but it just reinstalled it when i plugged it in with the MTP drivers already on my computer.
does anyone have any suggestions? i did remember to leave usb debugging on.
thanks!
after rebooting, i tried this in cmd
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Josh Bucher>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
************** offline
C:\Users\Josh Bucher>adb devices
List of devices attached
C:\Users\Josh Bucher>
so it looks like it detected it as offline, then it doesnt. any thoughts? i **ed my phones serial #

ive managed to get the toolkit to install fastboot drivers, but ADB drivers still are not installed and adb does not recognize my phone. fastboot does see it but adb doesnt. ive uninstalled all the drivers and tried the nexus toolkit, pdanet and manual installation but for some reason, i cannot get it to install adb drivers or even recognize that it is an option. does anyone have any suggestions?

joshtb86 said:
ive managed to get the toolkit to install fastboot drivers, but ADB drivers still are not installed and adb does not recognize my phone. fastboot does see it but adb doesnt. ive uninstalled all the drivers and tried the nexus toolkit, pdanet and manual installation but for some reason, i cannot get it to install adb drivers or even recognize that it is an option. does anyone have any suggestions?
Click to expand...
Click to collapse
So there's nothing listed if you input :
adb devices
You are connected via usb with debugging enabled?
Edit: could you also open up device manager in windows and have a look if the device is listed
Sent from my Galaxy Nexus using Tapatalk

RTContent said:
So there's nothing listed if you input :
adb devices
You are connected via usb with debugging enabled?
Edit: could you also open up device manager in windows and have a look if the device is listed
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
usb is enabled.
nothing is listed under ADB, but there is my serial number listed under fastboot. I uninstalled all drivers the toolkit and the SDK. I am going to try the toolkit again now that everything is been uninstalled. The device will be listed in Windows but usually without the ADB driver listed, however the fastboot driver is listed.
now that I tried using the toolkit,
I still had the same problem with no ADB but fastboot was the listed. Then I went to uninstall the drivers through the toolkit and I got an error message saying that they remove failed three times and that no device was removed. However the device still exists under portable devices in the device manager. I am going to uninstall the toolkit after removing the drivers and remove all the drivers from the device manager and then try using just the SDK to route the phone.

after using the toolkit, I am now getting Samsung ADB interface driver installed on my computer. However the toolkit cannot access or realize that ADB is connecting to my phone. I do have USB debuggingenabled. I might try using the SDK to manuallyto connect to it.

fixed the problem. i plugged my phone in directly to the computer instead of through a usb splitter. got it rooted via this post
http://androidforums.com/verizon-ga...oot-un-root-without-unlocking-bootloader.html
thanks for everyoines help! everyone is tahnked!

joshtb86 said:
fixed the problem. i plugged my phone in directly to the computer instead of through a usb splitter. got it rooted via this post
http://androidforums.com/verizon-ga...oot-un-root-without-unlocking-bootloader.html
Glad you got it fixed. If I knew I could have told you the usb hub would have been the problem (they always are)
thanks for everyoines help! everyone is tahnked!
Click to expand...
Click to collapse
Sent from my Galaxy Nexus using Tapatalk

[Q] adb devices (via USB) shows as offline

New device. Odin works, USB storage works, TCP adb works, charging works. Have the latest drivers, which worked fine on the previous device (new device is a closed box warranty replacement). Device shows up in adb devices as "device", but adb freezes when attempting to push or shell. On super rare occasion, I get a shell prompt, but adb freezes immediately. Oftentimes, it shows up as "offline" instead. Have tested numerous cables, numerous USB ports. Reinstalled drivers, reflashed device in odin, reinstalled adb, redownloaded oneclick. Nothing works. Already went through other threads covering the same topic for numerous other devices. What am I overlooking?

Oneclick does not work anymore, not for Gingerbread. Other than that....try and let Windows find and install the drivers from Windows Update.
Sent from my SPH-D700 using xda premium

Meant the tweaked adb in oneclick. I tried to remove the drivers, and let windows search through update, but still no dice. The phone shows up in device manager, is recognized by odin for download mode, and windows as a storage device. However, adb still won't recognize it other than in an offline state.

Sorry if this is a stupid question but you have USB debugging on right?
Sent from my SPH-D700 using xda premium

Launch ddms.bat from \android-sdk-windows\tools
See if the DDMS application recognizes the device there. If not, then you need to enable USB-debugging and/or try different USB ports (but you said you did the latter already). I found that I must use USB ports directly attached to the motherboard for doing anything with my phone.

@kenny: Yup, USB debugging is enabled.
@nikon120: There's no tool dir, but there is platform-tools. There's no ddms in it.

wingbat said:
@kenny: Yup, USB debugging is enabled.
@nikon120: There's no tool dir, but there is platform-tools. There's no ddms in it.
Click to expand...
Click to collapse
Hmm, then I gather you don't have the SDK installed. I was just on SDK revision 10 and the folder was there. I also just uninstalled revision 10 and my older JDK installation to do a fresh install of the latest JDK and Android SDK. The tools folder is in this latest install too.

If odin works, just odin cwm 5.0.2.7, then flash su.zip which roots you.
Sent from my SPH-D700 using Tapatalk 2

nikon120 said:
Hmm, then I gather you don't have the SDK installed. I was just on SDK revision 10 and the folder was there. I also just uninstalled revision 10 and my older JDK installation to do a fresh install of the latest JDK and Android SDK. The tools folder is in this latest install too.
Click to expand...
Click to collapse
My apologies. "tools" was marked as hidden, and not showing during "dir" in command prompt. I did locate and launch ddms.bat. It shows the device as online, but unresponsive. If I close it, and kill-server, and relaunch, it shows the device as offline.
xboxfanj, I already have CWM flashed, and the device rooted, via Odin. What I'm trying to do is use shell/push.

wingbat said:
My apologies. "tools" was marked as hidden, and not showing during "dir" in command prompt. I did locate and launch ddms.bat. It shows the device as online, but unresponsive. If I close it, and kill-server, and relaunch, it shows the device as offline.
xboxfanj, I already have CWM flashed, and the device rooted, via Odin. What I'm trying to do is use shell/push.
Click to expand...
Click to collapse
Oh I see. Reinstall the drivers from samsungs website.
Sent from my GT-P7510 using Tapatalk 2

Why not use adb from the sdk?
Sent from my SPH-D700 using Tapatalk 2

MДЯCЦSДИT said:
Why not use adb from the sdk?
Click to expand...
Click to collapse
I did, it didn't work.

wingbat said:
I did, it didn't work.
Click to expand...
Click to collapse
That's why I inquired whether or not DDMS was recognizing your phone or not. Your reply was that it showed as offline, and that is a good indication as to why adb isn't working for you.
Outside of the phone not having USB debugging enabled, the only other reason I can think of your cause is device drivers for the phone. You said you've already reinstalled the phone drivers and no difference, so you may want to try on another computer or maybe a virtual machine.

1)Unplug the usb and plug it back again.
2)Go to the Settings -> Applications -> Development of your device and uncheck the USB debugging mode and then check it again back!
3)Restart the adb on your PC. adb kill-server and then adb start-server
4)Restart your device and try again.

AT&T S3 not seen by ADB

Ok... i've gone through the steps in the one thread to get the phone rooted and everything without tripping the flash counter. At least the rooting with ODIN part. Been trying to flash CWM Touch for it, but for the life of me can't get the S3 to enter debugging mode over USB so that it can be seen by ADB to do so. I have Debugging over USB checked in the settings on the phone, i've rebooted the phone several times... it just never seems to enter debugging mode (or at least not like on my old Atrix 4G, where it actually told you in the notification bar that debugging was enabled).

It doesn't say debugging enabled. Do you have Kies installed? If so make sure it isn't running. Plug in the phone and type adb devices. If detected adb will report a serial number.

gunnyman said:
It doesn't say debugging enabled. Do you have Kies installed? If so make sure it isn't running. Plug in the phone and type adb devices. If detected adb will report a serial number.
Click to expand...
Click to collapse
I had installed Kies... tried hooking it up, still wouldn't list in ADB. uninstalled Kies, but kept the drivers installed. And i only mentioned the idea of it saying Debugging enabled when you connect the USB cable because my Atrix 4G said that every time from the get-go.

Also odd.... looked into the SuperUser app... and the log shows several allowed access attempts from "shell"... yet never seemed that way in ADB.

I had the same problem... try going in to the "services" settings and update the driver to Android ADB composite. Other than that, my suggestion is to make sure Kies finds the drivers for both Camera mode and USB mode by toggling the selection while plugged in to Kies.
Sent from my SGH-I747M using xda app-developers app

Your last resort would be to remove the drivers and reinstall them... Don't install Kies...

Or do you think i might have better luck in Ubuntu? Have that installed on my desktop as well.
edit: well... that's odd. booted into Ubuntu, installed the linux Android SDK and everything, got everything set up. opened the terminal, and just checked the devices without being in the ADB Shell... and a device showed up. launched the adb shell... checked devices again... nothing showed up, as on Windows. Figured what the hell, and did the command to install the recovery, and it worked.

elementaldragon said:
Or do you think i might have better luck in Ubuntu? Have that installed on my desktop as well.
Click to expand...
Click to collapse
It seems to be a driver issue, kies interfering, or a component is missing, or all of that, so I'd start your windows driver and software over fresh...
Uninstall Kies
Uninstall the drivers
Reboot
Install the drivers
Install the Java JDK (64bit has never worked for me, even though the drivers are 64bit)
Install the Android SDK
Use the Android SDK to get the Platform Tools and the Google USB Driver
than adb devices should show a phone
---------- Post added at 11:25 AM ---------- Previous post was at 11:24 AM ----------
elementaldragon said:
edit: well... that's odd. booted into Ubuntu, installed the linux Android SDK and everything, got everything set up. opened the terminal, and just checked the devices without being in the ADB Shell... and a device showed up. launched the adb shell... checked devices again... nothing showed up, as on Windows. Figured what the hell, and did the command to install the recovery, and it worked.
Click to expand...
Click to collapse
sometimes ADB Devices returns nothing for me, but theres a phone there, it would say nothing connected or to some effect if it didn't find anything...

Yea... every time i entered "adb devices" in the Windows command prompt, it always said "List of detected devices" or whatever it says, but nothing would be there, and if i tried the command to install the recovery it would say it was not a valid directory or whatever. Didn't show up on Ubuntu either, but it still worked...

EDIT/UPDATE: I was using a USB 3.0 port which apparently ADB didn't like (though ODIN rooting on that USB port worked fine...). I switched to another USB port and suddenly it worked!
Sorry to resurrect an old thread but I guess it's better than creating a new one for the same purpose...
Doesn't seem like this was resolved and I haven't been able to get my S3 to connect to ADB. I'm running Windows 7 Ultimate 64 Bit.
I had this driver already installed:
ATT_I747_GSIII_Samsung_USB_Driver_v1_4_6_0
I enabled USB debugging and it wouldn't connect. I installed Kies, still wouldn't connect. I uninstalled the driver and Kies and rebooted. Reinstalled "ATT_I747_GSIII_Samsung_USB_Driver_v1_4_6_0", installed the Google USB driver, still won't connect.
I'm still not sure if I'm supposed to see any sort of notification in my bar showing that USB debugging mode has been executed but I'm definitely not getting anything like that.
Code:
D:\APPS\ANDROID\android-sdk-windows\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
891b0876 offline
D:\APPS\ANDROID\android-sdk-windows\platform-tools>adb devices
List of devices attached

Yea, when i finally was able to use ADB to push a recovery onto my S3, it never actually showed up if i checked the devices in ADB Shell. Well... it DID, but not if i already typed the SU command before "adb devices".

hey guys
i have same problem i wanna adb my galaxy s3 rogers (att) i am trying to do the root no tripping flash counter so i got to the adb shell part
i dont know what else to do to make my computer recognize my phone ??
i installed sdk and extract/installed it in the c:\android folder of my comp i let sdk installed all the things it needs to took a while
so whats left? i have my phone usb connected to comp and debuging on i type adb shell it says adb is not recognized internal or external command???
do i need to have somthing open on the phone b4 openning command?
pleaaase help lol
thanks

You need to navigate to the folder where adb is actually located (platform-tools)

You don't have to use adb, you can use the same commands on terminal emulator

[Q] HTC One X Driver for Android 4.2.2

Hi Guys
Do a require a specific driver for the new 4.2.2 system. I have updated my phone to run Cyanogenmod 10.1 and had some issues originally getting adb etc to identify the phone. I have since got past this and now get an unauthorised error in adb. This is normal the issue im having is that my phone does not prompt me when I connect it to my PC. I should be getting a whitelist prompt to confirm I authorise the Pc to run ADB commands.
Has anyone else had this rather than the expected whitelist prompt im getting the little android bloke asking do I want to copy files via usb. Im just trying to work out what I need to do to get my phone to prompt me when I connect via ADB. I have already enabled ROOT access to Apps and ADB, Enabled USB debugging etc
Any help would be appreciated I have tried a number of drivers but only ever get asked to copy file via usb.

Appsdroid said:
Hi Guys
Do a require a specific driver for the new 4.2.2 system. I have updated my phone to run Cyanogenmod 10.1 and had some issues originally getting adb etc to identify the phone. I have since got past this and now get an unauthorised error in adb. This is normal the issue im having is that my phone does not prompt me when I connect it to my PC. I should be getting a whitelist prompt to confirm I authorise the Pc to run ADB commands.
Has anyone else had this rather than the expected whitelist prompt im getting the little android bloke asking do I want to copy files via usb. Im just trying to work out what I need to do to get my phone to prompt me when I connect via ADB. I have already enabled ROOT access to Apps and ADB, Enabled USB debugging etc
Any help would be appreciated I have tried a number of drivers but only ever get asked to copy file via usb.
Click to expand...
Click to collapse
Do you have HTC Sync Manager?
Also, in Device manager does your Drivers have Errors (Yellow Triangle)?

Wilks3y said:
Do you have HTC Sync Manager?
Also, in Device manager does your Drivers have Errors (Yellow Triangle)?
Click to expand...
Click to collapse
Hi Mate
I have tried with HTC Sync on and again after uninstalling it both result in the same issue usb prompt rather than ADB fingerprint prompt. No in Device Manager both of the connections for the device identify and install correctly. One with the phone and another stating something like Android Interface device not on my PC at the mo to confirm the exact name but its something like
My HTC
Android Interface Device or possibly android ADB interface

Appsdroid said:
Hi Mate
I have tried with HTC Sync on and again after uninstalling it both result in the same issue usb prompt rather than ADB fingerprint prompt. No in Device Manager both of the connections for the device identify and install correctly. One with the phone and another stating something like Android Interface device not on my PC at the mo to confirm the exact name but its something like
My HTC
Android Interface Device or possibly android ADB interface
Click to expand...
Click to collapse
Hmm Very strange.
Try:
http://forum.xda-developers.com/showthread.php?t=2217396
Or if not try hasoons Root Toolkit, im sure that installs some drivers too. Hasoons got my ADB working.
Finally, to find ADB device, are you opening command prompt in Platform-tools folder?

Wilks3y said:
Hmm Very strange.
Try:
http://forum.xda-developers.com/showthread.php?t=2217396
Or if not try hasoons Root Toolkit, im sure that installs some drivers too. Hasoons got my ADB working.
Finally, to find ADB device, are you opening command prompt in Platform-tools folder?
Click to expand...
Click to collapse
Nice one cheers mate will try these drivers when I get home later. I was originally using Hasoons toolkit which is what flashed the recovery and new rom but once I updated to 4.2.2 the toolkit stopped. It was coming up as device offline. I have managed to get it working by overwritting the old ADB and fastboot files with the new ones for 4.2.2. The ones the toolkit comes with is 4.1 so was erroring as it didnt know to carry out the fingerprint check.
Yes mate I have tried various methods I have accessed the android\android-sdk\platform-tools folder and run ADB from there this identifies the phone but states its not authorised. I tried using the toolkit with the new ADB and fastboot but get the same.
Im just missing the ADB prompt on my phone for usb debugging just cant for the life of me identify why im getting the copy files from usb prompt rather than the adb fingerprint prompt. Im sure its drivers so am hopeful the ones on the link will fix it. Fingers crossed

I was having issues with adb not finding my device. These drivers worked for me...

crshd said:
I was having issues with adb not finding my device. These drivers worked for me...
Click to expand...
Click to collapse
Nice one mate will try these ones when I get in to on way home now hopeful one of the driver links sorts out the prompt for me will update later thanks guys
Sent from my HTC One X using xda app-developers app

Cheers All removed all drivers for htc one x then downloaded the 4.2 versions from the link
http://forum.xda-developers.com/show....php?t=2217396
once reinstalled adb gave unauthorised error again but then put the prompt up on the phone. So possible the 4.2 contains the info for requesting permission as i havent changed anything other than the drivers adb and fastboot have been the same since i started. Anyway cheers all

confusion about installing driver
crshd said:
I was having issues with adb not finding my device. These drivers worked for me...
Click to expand...
Click to collapse
bro i download your driver but how to install it. my htc one x just start in fastboot mode. i want to unlock bootloader but without adb i am helpless

If you have Windows 7,8,8.1 just enable automatic update and let windows install correct drivers
Sent from my HTC One X using Tapatalk 2

ADB Drivers

I don't see any other threads, so is it just me struggling to install working ADB drivers?
The zip file I found in another thread made out like it was installed, but apparently not...
Any tips?

Windows 7/8? The drivers that I posted in the dev thread should work.
If you're on Windows 8 though, you'll have to reboot in that insecure driver installation mode thing.
Sent from my HTCONE using Tapatalk

Win 7 64 bit. I think I'm using the right ones, don't quite understand why it can't be seen
It shows up in Device Manager in which ever of the 3 ones I try, but when I try 'adb devices' nothing shows.

AndyCr15 said:
Win 7 64 bit. I think I'm using the right ones, don't quite understand why it can't be seen
It shows up in Device Manager in which ever of the 3 ones I try, but when I try 'adb devices' nothing shows.
Click to expand...
Click to collapse
You try "ADB Composite Device" or something along those lines? When you run that one it should be good.
When you download the zip, you should just extract the whole thing. Then after that I find the driver manually instead of having it search the folders. Are you selecting the android_winusb.inf for the driver?
I'm on the same OS for my main desktop and I do a lot of my work with the N1 on there using those drivers. Are you using normal command prompt in the platform-tools folder? I don't use anything other than command prompt for adb, so I'm not sure about those picking it up.
Sorry if that isn't any help, but I'm not sure what would stop it from picking it up after you use those drivers.

the other threads zip file works fine with my win 64. Are you going through a usb hub? That can mess it up
Sent from my N1 using XDA Premium 4 mobile app

No, no hub. Yep, doing all as I should. I'll try a different cable and different port though.

Linux
ADB not working on Ubuntu 13.10. No issue with fastboot. When I do ADB devices, it doesn't return anything at all aside from "List of devices attached" with a blank space underneath.
Curiously, even after enabling USB debugging I am never given the RSA popup asking me to confirm access. I'm guessing the two are related but even after revoking previous confirmations via the Developer Menu, I still can't get it to pop up.

mybrotherischad said:
ADB not working on Ubuntu 13.10. No issue with fastboot. When I do ADB devices, it doesn't return anything at all aside from "List of devices attached" with a blank space underneath.
Curiously, even after enabling USB debugging I am never given the RSA popup asking me to confirm access. I'm guessing the two are related but even after revoking previous confirmations via the Developer Menu, I still can't get it to pop up.
Click to expand...
Click to collapse
I recently got this going on Ubuntu 12 on VIrtualBox.
I have to start the adb server as root to get it working, i.e sudo adb start-server,
before I do 'adb devices'.
Also if you use VIrtualBox don't forget to add the usb filter for adb mode too.

ChodTheWacko said:
I recently got this going on Ubuntu 12 on VIrtualBox.
I have to start the adb server as root to get it working, i.e sudo adb start-server,
before I do 'adb devices'.
Also if you use VIrtualBox don't forget to add the usb filter for adb mode too.
Click to expand...
Click to collapse
Running natively. No luck doing it as root.