I recently broke the screen of my locked phone and would like to unlock and recover data by using adb, but it's not detecting my broken Samsung Note 5 or even my replacement Samsung Edge 7.
I've tried:
kill-server/start-server
downloading newest usb drivers
enabling developer mode on both phones (I already had developer mode enabled before I broke my Note 5).
using original usb cord given inside the box.
I don't know what else to do.
The problem might be with your computer.Try to use a different computer with adb installed to see what happens.If the problem persists,uninstall your Android SDK and re-install it.
On my Note 5, adb needs the phone's USB connection set to 'USB Data' not just 'charge' (default) before it will recognize it. Once it sees that permission, abd devices will show the phone as 'unauthorized', I then must allow access for debugging on the phone before it will allow access by tapping 'OK' on the popup dialog on the phone.
You could try booting into recovery mode but I don't think Samsung Galaxy allows access vie adb when in recovery. It may depend on the age of the phone.
So it sounds like the phone may be in 'charge only' mode when USB is connected. Your best bet may be repairing the phone.
I am a user of both android studio and Samsung Galaxy Note 5. I solved my issues just the same as you by generating APK files and transfer it to my note 5.
I just found that the reason is unknown resource settings which means my phone only trust google play and block other app. Have a good day.
Related
I am working at an android studio project and I always work with my own physical device SAMSUNG S7. It always worked (for a few weeks now) but today suddenly from one moment to the other my device cant be recognized by android studio anymore. I didnt change any settings! I just changed a line in the code (like a hundred times before) and after it my device is not shown in the list of devices. There is only the virtual device which is useless for me because it never displays the app correctly. Just my physical device shows the app correctly so now I need help. Otherwise I cannot continue programming.
I tried to reopen android studio and restart my phone but it didnt help.
Changing the cable plug mode (credits to Hack06)
Just swipe down the OS status bar, and tap on the device, then choose another connection mode.
Installing Samsung's development drivers
When this doesn't work, try installing the drivers provided by Samsung to improve developments. These can be found here.
USB Debugging
USB debugging may have failed. Or all of the developer settings have been reset. Try that
Reboot your phone into ODIN mode
Caution:
ODIN mode is in charge for flashing your Android phone, and if you’re not careful, you can cause permanent damage to your phone.
This solution applies only to Samsung’s devices, since they are the only devices with access to ODIN mode.
A guide how to access ODIN mode for your phone can be found here.
Install KIES software
If nothing worked till here you might want to download KIES software.
KIES software only works for Samsung’s devices.
Samsung KIES is part of Samsung Smart Switch.
Download here.
Google - Android USB Driver
My last suggestion would be to install Google's Android USB drivers. An official guide can be found here.
This may sound obvious..
but sometimes it could be a cable issue
even if it's charging it could not transfer data
try a new cable
I am using LG Optimus G. ADT shows that my device is offline and version is unknown as seen on the screenshot. I am sharing my device manager look also. It is installed but i think it is not properly working. I don't want to ignore that matter it is probably going to face me later.
Thanks.
1. First ensure that the device is set up properly for USB debugging. Check that
- you have installed the proper driver for your phone on your PC.
- you have enabled USB debugging in Developer Settings.
2. After you have done the first step, when you connect your phone to the PC, a dialog will popup on your phone prompting you to accept the computer's RSA key. Accept it and the device will be shown as online in your IDE.
3. As a last resort, you can try re-starting your IDE. This will force adb to start properly.
I'm trying to use my HTC Desire as a test phone for my Android application, but Eclipse just can't see it, now If i go to device manager there is a yellow !, i click uninstall, re-connect my HTC phone to the computer and it can not install the drivers, can anyone help me fix this problem? I really need to be able to use my HTC phone as a test device.
Canvas
I always had the same trouble with HTC phones and some Samsung phones as well even when using the official driver.
I found if you install PDANet http://pdanet.co/ this installs the driver for you and it always seems to work. You don't actually need the software afterwards and can be uninstalled, but it successfully installs the driver and device is detected.
Installing HTC Sync Manager on Windows 8.1 resolved my problems with HTC Desire 600.You can download it from here:
http://www.htc.com/www/support/software/htc-sync-manager.aspx
Details brought from here:
http://grindheadgames.com/htc-desire-showing-adb-devices-fix/
Important Note: I also noticed there is a checkbox in USB Settings called 'HTC Sync Manager'. You should check it to enable 'USB Debugging'. Otherwise although you have enabled usb debugging in 'application development' section, USB Debugging will not work.
I've connected my Samsung Galaxy Tab device to my Mac. Yes, I've turned on debugging. When I go to run my application to test on the device the device is not listed on the Android Device Chooser menu. Running the ./adb devices shows no results.
NOTE: Posting this question for others to find. When looking for the solution earlier all I was able to locate were answers to broken links to device driver downloads for Windows.
Make sure you uncheck
Settings > Applications > Unknown Sources (Allow installation of non-Market applications)
Turn on USB Debugging inside Settings > Applications > Developers Settings
If you're trying to connect to a Mac, I had this issue with a Samsung Galaxy Tab 10.1 running Android 4.3. To enable developer options, open the Settings app, tap on "About device" under the "General" tab and then tap on the "Build number" repeatedly (it's grayed out but you can tap on it anyway). A small pop-up will appear showing the amount of additional taps you need to do to turn on these options.
Once enabled, just turn on USB Debugging and it'll show up in Eclipse just fine.
I had this problem on my Mac and after 30 minutes tried switching USB ports and it finally started working on the second port.
I fixed it by reboot the device (Samsung Galaxy Tab2 7.0)
Update your driver for samsung. It can be found here: http://developer.samsung.com/android/tools-sdks/Samsung-Andorid-USB-Driver-for-Windows
Connecting your phone after development mode is on, and USB debugging is on.
At connecting to the PC the phone asks to trust this location. Finally.
This fixed my problem while all other tips were incomplete.
It does not answer your question of how to get ADB to see the device - I could not get that working. But what I did to install an APK I needed to test was to put it in Dropbox on my computer, then install it from there on the device.
Connect your device via USB hub instead of directly connecting to one of the usb ports on MAC. It worked that way for me. Please give a try.
There's also a pop-up that comes up at times requesting the currently connected computer to have access to your device(not to be confused with the Linux not supported pop-up; it lies ; ] ). I continued to receive Target:Unknown in Eclipse until I managed to catch it and accept. This is on a Samsung Note 8", which I believe is registered as a Tab 10.1 in my Arch Linux udev rules.
It may also happen that USB debugging is not checked on your device. Please go to developper options in your device and check it is enabled.
By the way, for devices with android Jelly Beam (4.2) and later versions, you will find out that this option is hidden. To activate it, click 7 times on the compilation number, and the option will be activated.
Tried everything, nothing helped. Including
USB debugging enabled
MTP/PTP
ADB restarted
Device/PC restarted
Tried Samsung's USB driver
By tricking/modifying driver installer, installed Google OEM Usb drivers for Galaxy Tab.
All software up-to-date
The only thing that helped is installing Kies3 + setting PTP on device, instantly authorization pops out in device. Everything OK now.
Kies3 download here: http://www.samsung.com/uk/support/usefulsoftware/KIES/
Enable USB Debugging mode solve the problem!
For those who don't know how to enable it (it's very hidden on Android 4.3 onward), see this.
In my case, this solved the problem:
unchecked the Settings->Security->Unknown Sources,
clicked on the upper left corner and changed USB mode from MTP to PTP,
unplugged/plugged the device, and
clicked OK on the USB debugging prompt.
Had this problem last year, never solved it. Again, after googling high and low, I could not find a cure for the USB debugging flakiness. Now for the good news:
1) Root your device. 2) Install adbWireless widget from Play (I am in no way associated with the author).
You are now good to go. After starting adbWireless and following its directions, you can now debug through adb wirelessly to your device, in my case, the original 7" Galaxy Tab.
I'm doing Android development with Eclipse 3.6.2, OS X 10.6.7 and a Samsung Galaxy Tab.
Everything is working great, except every 15 or 20 minutes, the Settings | Applications | Development | USB debugging checkbox "unchecks" itself. Which means I need to unplug the USB cable and go back into the setting, re-select the checkbox, plug the cable back in and I'm good to go.
What I would like to know is if there is some way to make that checkbox "sticky" (I asssume it probably is supposed to be - but I haven't been able to figure out under what circumstances cause the "uncheck" to occur). I've tried a number of variations of USB / sdcard / Development settings and haven't found the "sticky bit" yet.
I'm new to Android, so I'm hoping there is some "you forgot to also do X" here...
EDIT:
Maybe it has to do with a USB Mass Storage message that pops up after 10 min or so? I just noticed a message "USB Connected: You have connected your phone to your computer via USB. Select Mount if you want to copy files between your computer and your phones SD card".
I have a Galaxy Tab and have not experienced this behavior. Nor have I encountered this on any other Android device, and I have used quite a few for development purposes.
From what I can tell, this state cannot be toggled via SDK applications, but only via the firmware. My guess is that there is something flaky in your setup that is triggering something in the Tab's firmware to do this.
Sorry that I don't have a silver bullet for you.
UPDATE
Maybe it has to do with a USB Mass Storage message that pops up after 10 min or so? I just noticed a message "USB Connected: You have connected your phone to your computer via USB. Select Mount if you want to copy files between your computer and your phones SD card".
That further suggests there is something strange going on between your development machine and the Tab. That should appear when you first plug in the cable, then remain there until you unplug the cable. I would not expect it to be toggling the USB debugging checkbox, but I am really starting to think you have one screwed-up Tab.
Had the same problem on Huawei P20. Upon activating developer options, what I did was :
On the smartphone, open System Settings -> Developer options -> Enable USB debugging
Connect the smartphone to the computer
When the prompt shows on the smartphone select "File Transfer"
Uncheck and check USB debbuging (smartphone is still connected to computer)
The prompt for USB debugging finally appears
Hope it helps.
verizon has something running in the background making this happen and having the same problem on my samsung fascinate after upgrading to fro yo. I think they're trying to block usb tethering
My Galaxy Tab 7" does this all the time. I would be in the middle of something and it would just drop. Over & over.
The solution that I found that works great for me is to just use adbWireless. This allows you to run ADB over wifi instead of USB. adbWireless can be found on the Android Market. It does require you to ROOT your phone, but since you are developing for it, you will want to do that anyway.
THis seems to have gone away in 2.3 for DroidX. But it was quite frustrating when I was using DroidX w/ 2.2 on OS X to debug.