Database Users

"adb devices" = multiple devices?

Why am I getting the following?
I'm trying to run the 32B Hero (pure black) ROM Runme.bat and it is erroring because it is seeing multiple devices?
C:\android\tools>adb devices
List of devices attached
XXXXXXXXXXX offline
XXXXXXXXXXX offline
XXXXXXXXXXX device
Click to expand...
Click to collapse

At least yours see's some devices..... Mine won't recognise anything!

Roy_Drage said:
At least yours see's some devices..... Mine won't recognise anything!
Click to expand...
Click to collapse
Be sure you have the lastest USB Driver found in SDK's folder installed..

Well if you are playing with the emulator, more devices will show up. To select a specific device you have to run it with -s SERIALNUMBER like:
Code:
adb -s 123ASDQW111 shell

dev kit USB driver is loaded.
Not aware that I am playing with the emulator? I'm not, at least I don't think I am?

easiest way to resolve this is to issue two commands in the command prompt
adb kill-server
adb devices
this should restart the adb service and only show one device, at least this worked for me when I had this problem, good luck

thanks man that helped alot!!!!!!!
I was going to reflash my rom and start all over!!!!!!

after installing rom bootloader loop
I finally was able to sideload a ROM after wipe out my OS, then installed a android revolution rom seems ok but when I restarted after showing a few seconds htc logo reboot and goes to recovery menu, what should I do? please help

Adb troubles

I have troubles with developer mode on my phone.
Enable usb debug option is checked, but adb (running under gentoo linux, ubuntu, windows 7) doesn't show any devices.
But when recovery (CWM) is loaded, everything works well.
When I'm trying to start adbd with
Code:
#adbd start
I get message "cannot bind tcp:5037"
I thought it appears because adbd is already running but
Code:
ps aux | grep adb
gives nothing
Any ideas what to do? Does anyone have problems with adb even if Usb debug is turned on?

I use Debian and my command is adb start-server.
Give it a try.

Fr0zen1977 said:
I use Debian and my command is adb start-server.
Give it a try.
Click to expand...
Click to collapse
It doesn't help

Shtsh said:
...But when recovery (CWM) is loaded, everything works well...
Click to expand...
Click to collapse
Looks like ROM problem. Did you tried another one??

Yes. I'm tried several stock ROMs (2.3.6, 2.3.5), cranium, broodROM. Factory reset doesn't help.

[Q] Nexus 4 root help - Error more than one device and emulator

I am having an issue with ADB and rooting my n4 as above When i do"ADB reboot bootloader" I get Emulator-5554 offline and error: more than one device and emulator.
And I cant cant do anything. I have tried adb kill-server didn't work, a lot of people say it is bluestacks and to just end the process (I dont seem to have that installed with the android sdk I got). I have tried connecting it to port 5555 like people have said. Im lost now, any help

jonnyaztec said:
I am having an issue with ADB and rooting my n4 as above When i do"ADB reboot bootloader" I get Emulator-5554 offline and error: more than one device and emulator.
And I cant cant do anything. I have tried adb kill-server didn't work, a lot of people say it is bluestacks and to just end the process (I dont seem to have that installed with the android sdk I got). I have tried connecting it to port 5555 like people have said. Im lost now, any help
Click to expand...
Click to collapse
Solved you need to use adb -d reboot bootloader delete please

GUIDE: Data Recovery with a Broken Screen/Digitizer

This weekend I made the unfortunate mistake of breaking the glass on my Nexus 4 - the LCD worked fine but I couldnt tap or type anything. This posed a problem to get some of my data off the phone prior to wiping it. Eventually I found a way to control the phone using adb and an app called mymobiler so I wanted to write a guide in hopes this may ease the pain for someone in the future.
Step 1: Gain root access to your Nexus. You will need to install adb and run adb shell. If you can run adb shell successfully you are ready to go. There are plenty of guides about how to do this so I wont repeat the process here.
Step 2 (Optional): In my case I had recently reimaged my PC and so it was no longer an authorized device. When running adb shell I got the popup on my screen to authorize my PC, but of course I couldn't click "Accept". So I had to find a workaround:
2a: First you need your adbpub.key file. It should be in %HOMEPATH%/.android on Windows. You might need to run adb once to generate the file.
2b: Reboot into recovery. I used Clock Work Mod (non-touchscreen) 6.0.4.7. The non-touchscreen version is important because you need to use your volume keys and power button to navigate around CWM. Source: CWM
2c: Make sure you use the Google ADB drivers - I found them here: XDA-Dev's drivers
2d: In CWM, Go to mounts and mount /data
2e: Now on your PC connect your USB cable. Run these commands:
Code:
adb push adbkey.pub adbkey.pub
adb shell
cat adbkey.pub >> /data/misc/adb/adb_keys
2f: In CWM, go back to Mounts and Unmount /data
2g: Run adb reboot or reboot in CWM to go back to the Android OS.
2h: Now once its back in the OS, you should be able to run adb shell and your PC will already be authorized!
Step 3: Go to apk downloader (http://apps.evozi.com/apk-downloader) and get the MyMobiler apk
Step 4: Run "adb install com.mymobiler.android.apk"
Step 5: Now you'll have to have fun hunting and pecking around with adb shell input touchscreen tap <x> <y> commands. The x and y are coordinates starting at the top left. So on the Nexus 4 the screen res is 768x1280. The top left corner is 0, 0 - the bottom right is 768, 1280. The center of the screen is 384, 640. There is also a whole list of keys that can be pressed with the adb shell input keyevent <code>, a list of codes is here: ADB KEYs. You will need to peck around to get the MyMobiler app started up.
Step 6: Install and run the MyMobiler PC client available on their website (http://www.mymobiler.com)
Step 7: MyMobiler needs you to set the options>display>other on the Android, you will probably get a black screen if you dont set this (I did). Again you will have to play around with simulating the taps using the above info.
Step 8: Once MyMobiler is working right, you can use your PC keyboard and mouse to control your screen, backup your important stuff, and wipe your data before putting it up on eBay (or in the trashcan).
Hope this helps someone stuck in this precarious position.

edit:
not sure but on my second attempt I got this to work. thank you quite very much!
To save anyone else a big of time. If youre on a mac open finder
Click in the text box with the magnifying glass > command-shift-g > type ".android" into the prompt and your adbkey file will be stored within that folder

Not getting past step 1
Could you please recommend a guide to run the adb shell? I have installed it (and fastboot) but the phone is never found by adb devices. I have tried many different guides but none of them gets to identify the phone..
Thank you.

Is to possible to get past Step 1 with a broken touch screen?
Over at Stack Exchange (link was censored) a user is saying that a USB debugging feature must be activated in the phone itself before setting up the connection through adb. Naturally this can not be done with a broken touch screen.
You should really detail how did you achieve this in Step 1; otherwise it is not possible to follow the reminder of the guide.
Thank you.

Nexus 7 2012 bricked, adb/fastboot connection ok but unauthorized. Can You help?

Hi.
I have a nexus 7 2012 edition which turns on with The Google written logo and under the screen with a padlock. After that it will be in bootloop with a black screen ( I can see the backlight turning on/off). This is also if pressing the power+volume down combination. Seems bootloader is corrupted. Anyway I installed everything on pc plus I'm using the WugFresh Nexus Root Toolkit and here are some examples which show what errors I'm encountering when trying to flash stock firmware .
Log:
Checking ADB/FASTBOOT Connectivity
adb devices
015d4a5ed8500c01 unauthorized
fastboot devices
There is also a notification popup which tells me:
"An ADB Interface device was found but it was listed as "unauthorized"
-Accept the RSA security prompt and check "Always allow from this computer"
At this point I don't know what to do, can you help me?

Same issue - following
I have the same issue now after trying to flash a kernel to fix the slow charging issue. Following this post for any update.

Sunil_511 said:
I have the same issue now after trying to flash a kernel to fix the slow charging issue. Following this post for any update.
Click to expand...
Click to collapse
Hi, Sunil_511...
Bit speculative this, and I can't say for certain if the following solution would work, because I've never had this problem myself. It also requires that your Nexus 7 be in a fully bootable state.
Go to your Nexus 7 Developer Options in the devices settings and tap on 'Revoke USB debugging authorisations'. Tap on OK to confirm. See attached screenshot.
This, theoretically, should wipe the slate clean.
Reboot both your N7 and your PC/laptop and when you next reconnect your N7 to your PC/laptop, you'll be asked to authorise this new USB connection when you perform some action that requires it.
Well, that's the plan anyway.
Good luck?.
Rgrds,
Ged.

Nope, in my case my tab is not booting to recovery or system. The only option is adb and it is showing unauthorized. My last option what i think off is to change the motherboard.

Following
I have the same error and like to follow

Sunil_511 said:
I have the same error and like to follow
Click to expand...
Click to collapse
Google search is your friend. I found the following two methods which seems to have worked for some people.
1. If you are using OS X*:
Reboot your phone into recovery mode.
Connect it to your computer.
Open the terminal and type:
cd ~/.android
adb push adbkey.pub /data/misc/adb/adb_keys
All done! Just adb shell reboot and feel the power!
*For Windows 10, .android directory is located in your the base of your C:\User\user_name directory.
2. Go to where you have stored adb files, open that folder and press "CTRL+SHIFT+Right Click" and select and click on Open Command Prompt option
Now enter following command
adb start-server (Enter)
adb usb (Enter)
After that your device is no longer unauthorized and you should be able to use any command in your Android Mobile using PC/ Computer.
If these fixes don't work, SEARCH.

thanks buddy, i have tried pushing the adb keys but no luck. I will try tge second option. Will let you know after trying.

No difference still the same
BxG4ever said:
Hi.
I have a nexus 7 2012 edition which turns on with The Google written logo and under the screen with a padlock. After that it will be in bootloop with a black screen ( I can see the backlight turning on/off). This is also if pressing the power+volume down combination. Seems bootloader is corrupted. Anyway I installed everything on pc plus I'm using the WugFresh Nexus Root Toolkit and here are some examples which show what errors I'm encountering when trying to flash stock firmware .
Log:
Checking ADB/FASTBOOT Connectivity
adb devices
015d4a5ed8500c01 unauthorized
fastboot devices
There is also a notification popup which tells me:
"An ADB Interface device was found but it was listed as "unauthorized"
-Accept the RSA security prompt and check "Always allow from this computer"
At this point I don't know what to do, can you help me?
Click to expand...
Click to collapse
tnsmani said:
Google search is your friend. I found the following two methods which seems to have worked for some people.
1. If you are using OS X*:
Reboot your phone into recovery mode.
Connect it to your computer.
Open the terminal and type:
cd ~/.android
adb push adbkey.pub /data/misc/adb/adb_keys
All done! Just adb shell reboot and feel the power!
*For Windows 10, .android directory is located in your the base of your C:\User\user_name directory.
2. Go to where you have stored adb files, open that folder and press "CTRL+SHIFT+Right Click" and select and click on Open Command Prompt option
Now enter following command
adb start-server (Enter)
adb usb (Enter)
After that your device is no longer unauthorized and you should be able to use any command in your Android Mobile using PC/ Computer.
If these fixes don't work, SEARCH.
Click to expand...
Click to collapse
Tried your suggestion.. Which i might have tried eventually from googling.. Doesn't make any difference.

Fixed
After doing all the researches, i had to buy a new motherboard and then replace it. Installed new rom and now using it. Spared about 1400INR for a 32 gig version.