I can't get adb to recognize my captivate on either Windows 7 or linux. I'm running ECLAIR.XWMJ5. adb was previously able to recognize the captivate on windows and linux (using the stock ROM) before I updated to the I9000 ROM.
USB debugging is enabled.
(On linux, I am running the adb server as root).
Thanks.
Did you try these drivers?
I can't post links, but androidforums has a link to the Galaxy S drivers in a post called "Captivate USB Drivers Links Here". You might want to give those a try.
Windows recognizes it, not Linux
Looks like adb recognizes the phone on windows now after installing this driver.
Thanks, but I wonder why Linux won't recognize it anymore.
I downloaded the uber files tonight to root my HTC Thunderbolt. However, when I moved onto the second step using ADB, I've hit a bit of a snag.
While I am seeing the device listed under devices, it's telling me it's offline. This despite the fact I can copy files to and from the microSD card, as well as internal memory. Below is what I see at my terminal:
[email protected]:~/Desktop/ThunderRoot/downgrade$ adb devices
List of devices attached
HT14DS015334 offline
I am using Ubuntu Lucid Lynx 10.04 32bit version. At this point, I'm guessing it has something to do with the HTC drivers since I didn't install HTC Sync (there is no version in linux, right??)
Anyone on here use linux with their Thundebolt? If so, are you connecting it via ADB??
Thanks,
Robert
I use 10.04 64bit and 11.04 64bit all the time with ADB. You don't need drivers with Ubuntu.
offline means it sees it but it's not connected. try replugging it in and/or kill the adb server and restart it.
as stated above, you do not need drivers for Ubuntu.
try adb kill-server
then adb start-server
you might also need to start the server as root.
UGH!! Turns out the problem was debug mode on the phone. Or rather the fact it WASN'T in debug mode!!!
Enable/Disable USB Debugging Mode - HTC Thunderbolt ADR6400
Once I changed that it showed up as device!!!
Anyone done this in an Ubuntu 11.04 VM in VMware workstation?
I've been trying for quite a while to get my Infuse to talk to ADB, still with no success.
I'm running:
PC:
Windows XP (32-bit) SP3
Samsung drivers from the AT&T website (SGH-i997_Infuse4G_USB_Drivers_5_2_0_2.zip)
Infuse:
Firmware: 2.2.1
Baseband version: I997UKCH1
USB debugging turned on
No matter what I do, I get a Code 37 from the SAMSUNG Android Composite ADB Interface. (It shows up under "ADB Interface" in the device manager, but I get "Windows cannot initialize the device driver for this hardware. (Code 37)".)
If I disable USB debugging, I can mount the device with no problems in Media player mode or Mass storage mode.
I've also tried with the Kies package drivers and the Samsung driver from PdaNet, still with no luck.
I can debug an emulator session with no problem - just not the actual device.
I started with the guides here:
http://forum.xda-developers.com/showthread.php?t=1388644
I've tried the instructions for Epic here:
http://forum.xda-developers.com/showthread.php?t=1109374
and looked at the Galaxy issue here:
http://forum.xda-developers.com/showthread.php?t=1022272
I've tried with a Samsung-branded USB cable as well as a third-party one.
Any ideas what might be going on?
Do youvhave the android sdk installed? With the platform tools add on? Because adb is no longer in the sdk/tools folder of the android sdk ...its in the add on platform tools...then once installed you need to navigate to the platform tools to get advanced to work.
Sent from my SAMSUNG-SGH-I997 using xda premium
Yep, I've got the SDK installed - can run adb from the platform-tools directory, but it never sees my device:
C:\Program Files\Android\android-sdk\platform-tools>.\adb version
Android Debug Bridge version 1.0.29
C:\Program Files\Android\android-sdk\platform-tools>.\adb devices
List of devices attached
Hi guys, This simple reboot test will help out quality control for future hacks.
Introduction
I've been working on CASUAL for about a year now. It stands for Cross-Platform ADB Scripting Universal Android Loader. Its purpose is to be a Windows/Linux/Mac scripting language for ADB.... until now.
Today I added fastboot support into the repository located here: http://android-casual.googlecode.com
Purpose
I would like help verifying this works on your operating system and work out any kinks which may occur. This should one-click reboot your device from adb into fastboot, then back into adb.
Instructions
ensure you have java up-to-date http://www.java.com/en/download/installed.jsp
Download CASUAL Revision 161 Build 2,744 from here: http://d-h.st/RH9
Double click the downloaded-file or right-click-run the CASUAL file
Connect your device and observe that your device is "connected" in CASUAL.
Click the Do It button
Report back with your Operating system and that your device rebooted into fastboot, then back into Android.
note to Linux users: You need to set up your UDEV rules for permissions.
note to Windows users: Ensure you have Nexus 7 Drivers installed.
Conclusion
Anyone with a device capable of fastboot may test. I would appreciate any help.
known issues upon release:
Windows - CASUAL must be started twice.- issue corrected with multi-threaded adb task and 200 ms delay.
none
Discovered issues:
Mac using improper binary Thanks Shaka Huang on G+
No way to start if in fastboot mode- added double-click to enable Do It button
CASUAL fails on Linux if UDEV not set- automatic permissions elevation on $FASTBOOT command for Linux
No active issues
Devices tested:
Galaxy Nexus
Nexus 4
Nexus 7
Karbonn A9
Fastboot capable devices with issues:
Kindle Fire. Fire fire fire bootloader does not support fastboot reboot. Developer contacted, potential fix in FFF2.0
Known working Operating systems:
Windows 7
Windows 8
Linux 64
Mac OS X 10.8.2
Still need Windows Vista, Linux32 and Mac OS-X Leopard/Snow Leopard.
Casual test, Kubuntu Linux 12.04, 64-bit, Sun java JDK, version 6
I got the following error:
$ java CASUAL-Revision152a.jar
Exception in thread "main" java.lang.NoClassDefFoundError: CASUAL-Revision152a/jar
Caused by: java.lang.ClassNotFoundException: CASUAL-Revision152a.jar
at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
Could not find the main class: CASUAL-Revision152a.jar. Program will exit.
redstar427 said:
I got the following error:
$ java CASUAL-Revision152a.jar
Exception in thread "main" java.lang.NoClassDefFoundError: CASUAL-Revision152a/jar
Caused by: java.lang.ClassNotFoundException: CASUAL-Revision152a.jar
at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
Could not find the main class: CASUAL-Revision152a.jar. Program will exit.
Click to expand...
Click to collapse
He said to update to latest Java version which means you must have Java 7
Sent from my Nexus 7 using Tapatalk 2
Android development requires JDK version 6
Android development requires JDK version 6, so if version 7 is required for this, then I will drop out of the testing.
redstar427 said:
Android development requires JDK version 6, so if version 7 is required for this, then I will drop out of the testing.
Click to expand...
Click to collapse
The java running on your computer is different from the java development kit. JRE is backwards compatible. The JDK must be version 6 for Android.
I just fixed the Windows 2x start bug which has been plaguing this project from the start. I also fixed the Mac-uses-linux-fastboot bug which was reported on G+. https://plus.google.com/u/0/104711040110222472212/posts/R7A8CjQcjde
works fine even with Java version 6, I just forgot a parameter
Earlier I forgot the "-jar" parameter.
Once added it worked just fine on my Samsung Galaxy Nexus.
http://paste.ubuntu.com/1519115/
works fine with
- Windows 7 x64
- Nexus 4 & Nexus 7
:good:
Works fine Windows 8 x64 & Nexus 7 CM 10.1
Tested both my
-Galaxy Nexus(Maguro) and
-Nexus 7 (Grouper)
on
Mac OS X 10.8.2
Works on both
I'm VERY happy with the progress so far!
Confirmed working devices: Galaxy Nexus, Nexus 4, Nexus 7
Confirmed Working OS's: Windows 7, Windows 8, Linux 64, Mac OS X 10.8.2
I still need testing on Windows Vista, Linux32 and Mac OS-X Leopard/Snow Leopard.
Issues Corrected:
Windows - CASUAL must be started twice.- issue corrected with multi-threaded adb task and 200 ms delay.
none
Mac using improper binary Thanks Shaka Huang on G+
No way to start if in fastboot mode- added double-click to enable Do It button
CASUAL fails on Linux if UDEV not set- automatic permissions elevation on $FASTBOOT command for Linux
I've uploaded a new version.. CASUAL Revision 161 Build 2,744 includes all the above features And, if you double click the "Do It!" button, it will enable the button.
Confirmed it worked on my Nexus 7 on Snow Leopard (10.6.8). CASUAL still shows a message "<waiting for device>rebooting"
AdamOutler said:
The java running on your computer is different from the java development kit. JRE is backwards compatible. The JDK must be version 6 for Android.
Click to expand...
Click to collapse
So im fairly new to linux. How do I go about, if even possible, to update JRE to 7 while keeping my JDK at version 6...
Adam,
I tested both my Nexus 7 (stock, rooted, 4.2.1) and Nexus 4 (CM10.1), both successfully.
I'm running Ubuntu 12.04 64bit
Then, just for kicks, I tested in on a Kindle Fire running AOSP 4.2.1 by Hashcode. The Kindle Fire rebooted but did not go to the fastboot menu. The bootloader that it is running is FireFireFire and running TWRP for recovery.
Happy to test more if needed.
Thanks,
Marty
we need more tests not just the nexus line-up
Worked great for me
Win7 x64
Fully working on my CM 10.1 HTC Desire Z, Windows 8
Nexus One, ROM CM7.2 OS - Mac OS 10.7.5
dank101 said:
we need more tests not just the nexus line-up
Click to expand...
Click to collapse
This did get posted in the Nexus 7 Android Development forums...
.torrented said:
This did get posted in the Nexus 7 Android Development forums...
Click to expand...
Click to collapse
I'm bringing people in via +CASUAL on Google Plus. They're coming in slowly. I could potentially ask a news writer to cover this later.. But I'm happy with the progress so far.
How to Mirroring our Mobile display in PC or Laptop???
Anybody know Explain About It!!
You need adb drivers, adb support (google how to install adb on windows), java or jre latest version installed, usb cable and mirror.jar similar too this:
http://droid-at-screen.ribomation.com/?ddownload=127071