Database Users

[Q] ADB error new Defy XT557D

I received new Defy XT Dec. 17 from Republic Wireless and wanted to move as many apps as possible to SD card without rooting as discussed elsewhere.
However, after enabling USB debugging on the phone (Settings - Applications - Development) and connecting the phone to the computer with the USB cable here is the message when I type command "adb devices".
adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
???????????? no permissions
command "adb version" returns:
Android Debug Bridge version 1.0.31
Apparently my Defy is not recognized and of course no other adb commands work. I'm not using Windows. I'm using Linux, Ubuntu 12.10. I've used adb successfully on same computer with Acer Iconia A100 Tab. Attached file contains pertinent messages in syslog when usb cable from Defy is connected to computer. Any help with why this device not recognized by adb would be appreciated.

ADB, Samsung_Android and Win x64 - Solved

After many hours googling and searching here, I have finally successfully rooted my new Verizon Galaxy S4 (SGH-i545), and it had nothing to do with the root process itself, but it was the basic setup that was giving me fits.
Googling and searching has shown that this is actually a common enough problem with some Samsung devices, and there is a fix for it. Since I had to combine several different processes, I thought I would add a note here on how to get the device connected. I will leave the rooting and other discussions to the others. I am also going to give credit to arpruss, most of the steps here come from his work on the Epic. I have trimmed down to only what is necessary to get ADB working properly.
This assumes that you have already tried the various processes to install or update drivers, and that has not worked. Also assumes mid- to advanced user skills:
1. Install KIES. (Downloading the separate driver package didn't work--the driver package refused to install.)
2. Set device in USB Debug mode (Settings | Applications | Development | USB debugging(x)).
3. Plug device into computer.
4. Run Device Manager
5. Look for SAMSUNG_Android. You shoud see it in the Other devices section.
6. Right-click on "SAMSUNG_Android".
7. Choose "Update driver software" | "Browse my computer for driver software" | "Let me pick from a list".
8. Make sure "Show All Devices" is selected and click on "Next".
9. Click on "Have Disk" and type in "C:\Program Files (x86)\Samsung\USB Drivers\25_escape" (auto complete made it easier to type; if you have 32-bit windows, the " (x86)" should be omitted).
10. You will get a two-pane selection of the drivers. Selecting one of the two "SAMSUNG Electronics Co., Ltd." listings (you may need to look through both) in the left pane gives an option list on the right that includes two "SAMSUNG Android ADB Interface".
11. Choose the first "SAMSUNG Android ADB Interface" and click on "Next". You will get a warning that Windows cannot verify compatibility. Accept this. Windows will install the driver and once it's done you'll click on "Close".
12. Windows installed the driver and ADB started working. (If it didn't start working, I would now have gone back to the Device Manager, right clicked on "SAMSUNG Android ADB Interface", and then redid steps 7-11, but this time with the other "SAMSUNG Android ADB Interface" driver.)
This is enough to get adb working. But it's still probably worth fixing the CDC Serial device.
13. Repeat steps 7-11 in the Device Manager with the "CDC Serial" device now, except that instead of the ADB driver you will look for and install "Samsung Mobile USB CDC Composite Device" in the right pane in steps 10-11.
If all goes well, you will get more spinning stuff in the task bar, and eventually Device Manager doesn't show any devices in "Other devices" with yellow triangles. But if things go for you like they did for me, you'll have "CDC Abstract Control Model (ACM) in "Other devices".
14. Repeat steps 7-9 in the Device Manager with the "CDC Abstract Control Model (ACM)" device now. (You may have some USB Modem options showing up in some places, but I ignored those, and did the same "Have Disk" move as before.)
15. I got a single-pane display showing only "SAMSUNG Mobile USB Modem". (Maybe you'll have two-pane display and you'll have to find it as in steps 10-11.) Select it and click "Next". I didn't get any warnings. Windows will install the driver and once it's done you'll click on "Close".
At this point, Device Manager showed all devices correctly functioning. And "adb shell" worked fine.
16. If you don't want KIES, just uninstall it, but make sure not to uninstall the drivers (the KIES uninstaller will ask).

[Q] Having Trouble With USB Debugging

astralhash said:
I have a Nexus 4 on build number JWR66Y.
The first time I plugged in my phone with USB debugging on, the RSA window popped up, and I was able to use this functionality. I tried then to use a toolkit on my virtual machine Windows 7 to root it. After this failed, i looked for a mac toolkit and found it.
When I went to enable USB debugging now, the RSA key window does not pop up. The tool kit cannot detect my phone anymore.
Android file transfer still works.
The bootloader is unlocked but not rooted (That is what I am trying to do). I already tried to restart the computer, and factory reinstall the phone.
Please help!
Here is adb in my terminal
Josephs-MacBook-Pro:android sonner$ ./adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
0489dbf5d80bf6c6 unauthorized
Josephs-MacBook-Pro:android sonner$
Click to expand...
Click to collapse
For your Windows 7 virtualmachine, while its connected with usb debuggging, in Device Manager reinstall the device using the Universal Naked Driver (link in my sig).

Diagnosing USB Driver and ADB issues in Windows

Are you getting errors like "device not found" or "device offline" while trying to run ADB commands? Here's a quick way to troubleshoot your problem on Windows.
Steps
1. Ensure USB Debugging is enabled in Developer Options.
2. Verify current Google USB Driver is installed and that Device Manager is using that driver.
3. Update to latest version of ADB.
1. Ensure USB Debugging is enabled in Developer Options.
Enable Developer Options by going to Settings -> About Phone and tapping on "Build Number" multiple repeated times. You will be greeted with "You are a developer."
Now, under Settings -> Developer Options, ensure you check the box for "USB debugging."
2. Verify current Google USB Driver is installed and Device Manager is using that driver.
You may skip this step if Device Manager lists your phone as "Android Phone -> Android Composite ADB Interface." If it does not, this is likely your root cause.
Go to the Google USB Driver page and download the latest driver directly from Google. Extract the zip file to a folder you know and will remember in the future.
Open up Device Manger in Windows with your Nexus 5 connected. Whatever your Nexus 5 is currently detected as, right click on it and select Properties. Then, in the Driver tab, hit "Uninstall." If available, select "Delete the driver software for this device." and hit "OK." It will remove the old drivers.
Restart your computer.
After restarting, reconnect your Nexus 5. It should be recognized as an unknown device in the Device Manager. (If it isn't, try the previous driver deletion steps again.)
Right click on the unknown Nexus 5 device, choose Properties, and in the Driver tab again select "Update driver." Browse your computer manually by putting in the path to the new Google USB Drivers you unzipped to a folder of your choice in the beginning of this step. Choose next and your drivers should install! You'll know everything completed successfully when you see the phone listed under "Android Phone -> Android Composite ADB Interface" in Device Manager.
This is the most finicky process, so don't be afraid to reboot your computer a time or two and repeat these steps if they don't work on the first try.
3. Update to latest version of ADB.
This is a crucial step. The new version of ADB is required to work with the "USB debugging authorizations" setting.
Perhaps you know how to update ADB, in which case, just do it. However, here's a detailed manual approach to download JUST the adb suite from the SDK:
Go to the Google Android SDK website and choose "Use An Existing IDE" and click the "Download the SDK Tools for Windows." This will allow you to download only an 80 MB file rather than the whole 400 MB suite.
Install the SDK tools exe to a folder of your choosing.
Run SDK Manager and uncheck everything except for "Android SDK Platform-tools." This is the ADB and Fastboot bundle. Install that.
Navigate to your SDK Path as indicated at the top of your Android SDK Manager window. You will now see a freshly downloaded platform-tools folder containing ADB.exe, Fastboot.exe, and a host of other files. That folder is now your updated, portable ADB tools folder. You can move it anywhere you like as long as you run ADB from a command prompt window set to that directory.
After you've followed these procedures, running "ADB Devices" should trigger a prompt on your device to accept the RSA fingerprint of your computer. Accept it, and now all should be working as intended!
Questions? Ask below!
Thanks to:MaxRabbit

Other solutions
Windows 8 Diagnosis
Originally Posted by Yorus
The following worked for me, since all of the suggestions mentioned here didn't work for me:
If you use a Windows 8.1 enterprise N or KN edition, install the Microsoft Media Feature Pack :
http://support.microsoft.com/kb/2929699/en
Sounds too simple to be true but work instantly for me.
Hope it works you some of the people here looking for a solution
Click to expand...
Click to collapse

Samsung Galaxy Tab A 2016, How to connect to a computer (PC)

I had a stroke 4 years ago and haven't used this tablet since, but I have decided put some books on the Samsung, but now I can't remember how to do it.
Could someone please help me.
Martin.

plug in usb cable one end into tablet other end into PC

usb is connected. Maybe the PC is not connected?
Martin.

what OS?

Windows 11 Pro 22H2

ah windows.. then you may need drivers. not sure, but try this..
on tablet, settings - about phone - tap build number (7x) seven times.
settings - developer options - usb - select file transfer (MTP) as default.
settings - developer options - enable usb-debugging (optional for adb).
you should see tablet in windows explorer now.
if not, you can try adb instead (optional)
in windows device manager, find device with yellow triangle exclamation mark -> Properies -> Update Driver -> Browse my computer for driver software -> Let me pick from the list of device drivers on my computer -> Show all devices -> Have Disk -> select *.inf file
https://developer.samsung.com/galaxy/others/android-usb-driver-for-windows
(skip this if drivers are fine)
download platform tools and check 'adb devices' from C:\Windows\System32\cmd.exe. if you can see tablet serialno, driver is ready for adb file transfer.
Code:
cd %UserProfile%\Desktop\platform-tools
adb devices
adb push path\to\file /sdcard/Download
https://developer.android.com/studio/releases/platform-tools

I tried the first the setting and won't work. It works on the tablet but doesn't on the PC. I'll try the second part.

I'll try the iPad, it's better than nothing. A new version of Windows will get the Samsung running (I tried it) but I have lots of games to play. Thanks for helping me, alecxs.