Database Info

[Q] adb doesn't recognize my phone

I posted this question over on Phandroids but this forum seems perhaps more appropriate. My Lenovo laptop running XP sees my phone just fine (Samsung Gravity Smart SGH-T589) and I'm able to transfer files to/from the phone. However, adb doesn't seem to be able to see it. A search about this problem turns up solution suggestions that mostly involve drivers, but my Samsung driver is up to date and clearly working (or else the phone wouldn't show up to Windows and I wouldn't be able to transfer files). My phone is rooted, which also makes it obvious that my laptop can talk to it just fine -- I used OneClick to root it last week using the same computer.
I'm using the DOS prompt (cmd) to run adb, and adb works fine. It simply doesn't see any devices. Here's an actual text transcript:
===============================
C:\Android\adt\sdk\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
C:\Android\adt\sdk\platform-tools>adb shell
error: device not found
C:\Android\adt\sdk\platform-tools>
===============================
Any ideas? I'm pretty new to this, so perhaps I'm missing something really simple. I hope so anyway!
--
Craig
Sunnyvale, California

Make sure that USB debuggin is enabled on your device. (This option should be changed only while device is disconnected from USB).
Also, try to restart adb server by killing it from the device manager.

Thanks for the suggestions. I had indeed already done both of those things. USB debug must be enabled to do file transfers, so I already knew it was definitely on. I still cycled it off/on anyway to make sure. And I did both kill-server and start-server commands as part of my checkout to assure myself that adb was in fact working correctly. I had Windows task manager up as well so I could watch adb disappear and reappear with those commands.
--
Craig
Sunnyvale, California

Hmmm... Try to reboot both your computer and device.
Have you tried to connect other devices to ADB? May be there is a problem with ADB installation?

Phone and laptop have both been rebooted many times. I also tried it with the phone in charge-only mode because that's what One Click Root required, but nothing changed. I also tried using all of the different USB ports on my laptop and tried two different USB cables, although that was silly because the phone is obviously talking to the laptop via USB. It shows up in file explorer, and I am able to transfer files using Windows drag and drop.
I'm afraid I have only one device, my recently rooted Samsung Gravity Smart phone, so I can't try it out on anything else.
I'm not sure how the adb installation could be at fault since the commands work as long as they don't involve the USB port. And I know that it MUST be possible to shell to the phone with what's already on this computer because One Click did it. I tried running the adb commands from the One Click Root > ADB directory just in case something about that particular install of adb was different, but I got exactly the same result.
It seems to me that I must be failing to do some setup step that an experienced Android developer might know about. I've never done anything like this before, so I wouldn't have even known about downloading the Android sdk if it weren't for forums like this! I sure appreciate the community of knowledgeable people here, who are clearly willing to help newbies like me.
If there are any software tools that anyone can suggest using to help me figure out what's going on, please let me know.
EDIT: Is there something that I need to load on my phone before adb will work? It occurs to me that OneClick might push something to the phone when it does the root, then delete it when the task is complete. I tried using QTadb, which is an adb GUI, and got the same result: no devices seen on the port even though Windows sees my phone and can talk to it via USB.
--
Craig
Sunnyvale, California

[Q]Phone's screen is permanently damaged, need a way to retrieve data from the device

Hey XDA community,
I need to retrieve data from the internal memory.
USB debugging IS enabled.
Anyone know if I can adb pull from the phone? I've tried using adb commands but so far get the "error: device not found" but this is obviously not true because adb is working fine on IntelliJ IDEA and I'm reading the real time logcat of the phone on the IDE so it's obviously connected.
I've thought about using reflection to make an app that forces the USB mass storage on, but I have never used reflection before so this would take me a bit of time to do. I'm looking for an easier solution. If it comes down to reflection being my only option, I guess I'll do it to retrieve some important files on the internal memory.
Any help is appreciated, thanks guys!

Azaxirus said:
Hey XDA community,
I need to retrieve data from the internal memory.
USB debugging IS enabled.
Anyone know if I can adb pull from the phone? I've tried using adb commands but so far get the "error: device not found" but this is obviously not true because adb is working fine on IntelliJ IDEA and I'm reading the real time logcat of the phone on the IDE so it's obviously connected.
I've thought about using reflection to make an app that forces the USB mass storage on, but I have never used reflection before so this would take me a bit of time to do. I'm looking for an easier solution. If it comes down to reflection being my only option, I guess I'll do it to retrieve some important files on the internal memory.
Any help is appreciated, thanks guys!
Click to expand...
Click to collapse
Windows:
Code:
C:\> adb pull /sdcard c:\location\to\store\it
or
C:\> adb pull /sdcard0 c:\location\to\store\it
/sdcard0 could also be /storage0, I forget precisely. I'm in the middle of flashing something right now

Broken screen, need to get data off

OK, a friend of mine's girlfriend's daughter (insert Spaceballs joke) broke the screen on her One S. She wants him to get the data off her phone (likely pictures and whatever else). Does anyone know of a way to do this? The bootloader isn't unlocked, which apparently makes a difference. I've never touched a HTC device before, so I don't know if there are any quirks, but there seem to be.

Few windows programs( Android Manager, Android Commander) will let you access the sd card, and adb commands will do it too if you have usb debugging enable. Look like you are on stock recovery. Is been so long time since I use stock recovery that I do not remember if you can have the "usb mount" in there. When you plug the phone into computer, can you access the sd card?

liesnomore said:
Few windows programs( Android Manager, Android Commander) will let you access the sd card, and adb commands will do it too if you have usb debugging enable. Look like you are on stock recovery. Is been so long time since I use stock recovery that I do not remember if you can have the "usb mount" in there. When you plug the phone into computer, can you access the sd card?
Click to expand...
Click to collapse
No, hence the question. No offense, but if it was that easy, I wouldn't have posted this question...
It may not be booting up correctly or something, but without a working screen he can't tell. Or she may have a security code or pattern, which would prevent you from accessing the SD until it's unlocked. But either way, if the phone is booted up, you can't see the SD. And even if the stock recovery has a Mount USB option...well, the screen is busted, so he can't see that option or select it.
The only possibility I can see is if it can be booted into the bootloader, and do an ADB pull for whatever files she wants. But apparently to do an ADB pull (or for ADB to even recognize the device, according to him), the bootloader has to be unlocked first?

Android Manager will let you bypass the security as long as usb debugging is enable. Hard to tell. I had that problem with my friend phone, but he had the usb debugging enable. I wish that I could help you more - I know "that pain" of busted screen. Try that Android Manager. Is free - nothing to loose but time searching for it on xda. I forgot the link.

Enable usb debugging, install an apk to an android device with nonfunctioning display

The display of my Xperia z3 is non-functioning(i.e. all I can see is a black screen) after an accidental damage due to water-insertion. But all other parts are working fine. The screen responses to touch, I can hear the touch sounds and I can click photographs as well with the camera key.
After connecting the phone with USB cable to my ubuntu laptop, I can browse through the internal storage files on the phone and locate the newly created image files as I click new photographs and take screen-shots. But I can't open any files(images/audio/videos) with errors like "couldn't load image" and "couldn't determine type of stream". However, I'm able to copy new files to the internal storage.
I want to install some screencasting application like vysor on my phone so that I can access it using my laptop. I know this can be done using adb commands but the problem here is that USB debugging is not enabled on my phone and hence I can't find it on the list of adb devices.
Is there any workaround for such situation?

Is your phone rooted?
do you have a custom recovery?
able to use fastboot?

USB Connection Issues

I just rooted my s8+ with partcyborg's samfail and everything is working great except the usb isn't being recognized. I can see my phone on my computer and I can move files to my desktop but on my phone I get this message - "The connected device is unable to access data on this device. Reconnect the USB cable and try again." I have USB debugging enabled in settings. I'm using windows 10. ADB is up to date. I installed the samsung USB drivers. The device isn't recognized in kies or smart switch.
I'm at a total loss here. Any ideas? Could this be related to the 80% battery bug I was seeing? It's been at 80% for a while now.
Apologies if this is an obvious fix. I haven't rooted a phone since kitkat I looked around but the other threads weren't helpful.

chikichiken said:
I just rooted my s8+ with partcyborg's samfail and everything is working great except the usb isn't being recognized. I can see my phone on my computer and I can move files to my desktop but on my phone I get this message - "The connected device is unable to access data on this device. Reconnect the USB cable and try again." I have USB debugging enabled in settings. I'm using windows 10. ADB is up to date. I installed the samsung USB drivers. The device isn't recognized in kies or smart switch.
I'm at a total loss here. Any ideas? Could this be related to the 80% battery bug I was seeing? It's been at 80% for a while now.
Apologies if this is an obvious fix. I haven't rooted a phone since kitkat I looked around but the other threads weren't helpful.
Click to expand...
Click to collapse
So what do you wanna do with your USB connection? Just MTP (e.g. transfer files like you would when connecting a USB-Stick to PC) or you wanna do some ADB operations?
If you just want to transfer files, there's no need to have USB-Debugging enabled (in fact this is kind of a security risk when you connect to an unknown pc)

jaannnis said:
So what do you wanna do with your USB connection? Just MTP (e.g. transfer files like you would when connecting a USB-Stick to PC) or you wanna do some ADB operations?
If you just want to transfer files, there's no need to have USB-Debugging enabled (in fact this is kind of a security risk when you connect to an unknown pc)
Click to expand...
Click to collapse
I'm trying to use the phone as a bootable drive because my USB stick was stolen. I want to put a linux distro on my laptop.

chikichiken said:
I'm trying to use the phone as a bootable drive because my USB stick was stolen. I want to put a linux distro on my laptop.
Click to expand...
Click to collapse
In the past I used an app on play store call drive droid to boot linux.....
I have the same issue on mine and have not found a fix been looking for a while i kinda just gave up

TheMadScientist said:
In the past I used an app on play store call drive droid to boot linux.....
I have the same issue on mine and have not found a fix been looking for a while i kinda just gave up
Click to expand...
Click to collapse
Yeah I've been trying to use drivedroid but it says there are issues with the mass storage. I'm going to send the dev a message with the ROM and see if there's anything he can do. For now just gonna flash back to stock

chikichiken said:
Yeah I've been trying to use drivedroid but it says there are issues with the mass storage. I'm going to send the dev a message with the ROM and see if there's anything he can do. For now just gonna flash back to stock
Click to expand...
Click to collapse
I'm sure he has looked into it. I talk to him quite a bit now that I think about it I have not heard nothing about it