EDIT: Never mind. I'm just a little slow today.
OK, I have dabbled with Linux a few times within the last 2 years, and last week, I decided to go 100% with it as my main OS.
All my rooting and such, has been done on a Windows OS in the past.
I cannot, for the life of me, get adb to recognize my G2.
'ADB Devices' returns a 'no permissions' response. But it recognizes my N10 just fine.
I need a Linux fan to help me out with getting my G2 connected properly.
EDIT: Never mind. I'm just a little slow today.
This works, for those who are slow like me:
For anyone wondering about 4.2.2, there is a security question that appears on the phone requesting RSA verification with the PC. Be sure your tools are updated AND you allow the PC access by verifying the security question on the devices in question. This fixed it for me.
And as always, verify you have debugging enabled in the developer options
share|improve this answer
answered Mar 12 '13 at 3:13
community wiki
Eric Fossum
3
It worked for me once I revoked the usb debugging authorizations. Then disabled and reenabled usb debugging. The "allow this computer" message popped up, and BAM, it showed as device instead of offline. – MYou Dec 13 '13 at 2:07
Thanks in advance for the help
Related
Hello all I have been using a captivate for some of my dev work and all was going well but just today I can no longer see it in my devices using ddms or adb devices.
Looks like adbd is running on the phone and I can mount the sd card fine. I tried in two machines, one mac and one windows... So its something in the phone and a factory reset didn't fix it - any tips on how I should go about troubleshooting this?
It was working fine so I am a bit miffed.
Thanks so much
Jit
--
Sent from my SAMSUNG-SGH-I897 using XDA App
Still not working with a mac
All:
Just an update to the issue - the Captivate still refuses to be recognized by ADB, although it works fine on the same machine when I boot into Windows and use Samsung Kies.
On the Mac side, I can mount the files when USB debugging is on by going to the USB status icon and selecting Mount storage. The Mac even recognizes the connection as a new network connection (although I simply ignore that part). So looks like the USB subsystem on my Mac is somehow not recognizing the ADB communication. I upgraded to android release 8 and still the same problem.
Is there a way to completely reset the USB subsystem on a Mac without having to reinstall the OS?
Thanks so much - the weird thing is that the captivate worked okay for a week or so before deciding not to work with adb any more - I can still generate apks and sideload the apks into the device but I would really like to be able to do some on-device debugging.
Thanks so much for any help that you guys can give.
Jit
Edit: Nevermind
SOLVED - ADB Issue with Captivate
All:
After quite a bit of research finally figured out why ADB will not recognize the captivate (or for that matter any other android device). The problem was because I had installed EasyTether. Its a pretty nice software and pretty easy to use to tether android devices, unfortunately it kills adb's usb capabilities.
I found this issue in EasyTether's FAQ area so if anybody else is having the same problem you will need to unload the EasyTether Kernel Extension (unfortunately that didn't totally fix the problem for me - I kept losing communication intermittently so I ultimately removed Easytether from my mac as well as from the Captivate and now I can see the device in adb again).
Just thought I would share the solution with the rest of the very helpful community.
Jit
So I got my Samsung Galaxy Tab (sprint CDMA version) today and when I first plugged it into my computer the drivers installed fine. I was able to mount the sd card and transfer files with ease. I then proceeded to root the device hoping to put a new rom on it, I've got a captivate and am not a rookie at all when it comes to flashing roms via odin, cwm, etc...I first put the device into debugging mode which is where things got weird. As soon as I put the device into debugging mode and plugged it in via usb it immediately became "unrecognizable". I have the correct updated drivers for the device both from the Samsung website and via the Android SDK tools. There should be no reason why this happened. So I then took it out of usb debugging and plugged it back in and bam, again, "USB Device not recognized". I've been installing and uninstalling drivers, the device itself from the device manager, and have been trying other numerous ideas. I've been Googling and searching for hours upon hours at this point and don't know what to do next. Odin does NOT recognize the device when in download mode and the device does charge when connected to the computer. I have tried a different cord with the device and different computers and it's all the same story, works until debugging is enabled then it will no longer work no matter what. I am fairly sure at this point the device itself is malfunctioning or defected but I wanted the opinion of others before sending it back. I am pretty sure have tried everything and am doing everything right. Please help if you can, if not I still appreciate your time! Specs are listed below:
Hardware Version
P100.08
Model Number
SPH-P100
Firmware Version
2.2.1
Kernel Version
2.6.32.9
Ebicoustic said:
As soon as I put the device into debugging mode and plugged it in via usb it immediately became "unrecognizable".
....the device does charge when connected to the computer.
Click to expand...
Click to collapse
1. Just wondering, have you installed Kies before connecting the tab to your PC?
2. The SGT will not charge "normally" with a USB connection. It will trickle charge, which is very slow way of charging, and the device will not indicate that it is charging. Does your device indicate it's charging? (As stated above)
Hit thanks if I deserve it..
FWIW, My SPH-P100 Sprint Galaxy Tab has been an adventure as well. Enough so that I wish I'd known more and held out for a GSM model.
I am not even sure if Kies and/or Odin will in fact work with the Sprint GT. I've had almost no luck with a variety of attempts. Even the widely used ClockWorkMod Recovery does not include the Sprint GT among its list of supported devices. It does include the CDMA Verizon GT - and some folks have posted that they eventually got that to work.
I did get the SuperOneClick to work and setup root privileges on my tab. That part works fine. But so far I've been reluctant to experiment too much with the various tools that "almost appear that they should work" as I have too little experience with this Android tablet environment to feel comfortable that I can recover from the eventual disaster.
Am hopeful that Samsung will in fact follow through on their commitment to provide upgrade of all GTs to Gingerbread 2.3.3. If so that may be enough for my needs. I WOULD like to get the Netflix viewer app working. Is frustrating to already have a Netflix account and not be able to access it via my GT. A guy down the hall can get Netflix on his Droid X - which really bugs me! lol
IMHO, Google/Samsung/Motorola/HTC/etc. have done a horrible job rolling out Android - both on phones and tablets. Netflix really highlighted this when they decided to do device-by-device testing and certification before allowing Android devices access to their movies. Apparently the 'capabilities' inherent to various Android devices varies so much (and not just OS version) makes it difficult to roll out something as simple as Netflix access. It is frustrating. And the only "solution" so far is to wildly 'hack' your device in the hope that you'll shake something loose enough to make it work as you wished it had when you bought it.
Enough whining for now. But it has been a very frustrating and disappointing experience.
I installed Kies AFTER installing drivers and connecting the tablet and it has no effect. I also learned after googling that kies does not support the sprint cdma version though I could be wrong but many people have stated this. And the device does charge and does so very fast actually, 20% to 100% in 4 hours. I don't think it's trickling down as you say because it is very clearly charging at a fast pace. Thanks for the quick response though! And I have also tried superoneclick root and other methods i.e odin but neither can find the device. I know some people have had luck with this sort of thing after upgrading the rom and/or flashing firmware onto the device which I would love to try but unfortunately without windows being able to see the device, none of this is even remotely possible.
I think the reference to slow charging on USB is really refering to using a data USB port on a notebook or desktop computer. This is because the data USB ports are limited in how much current they will pass. My SPH-P100 will in fact charge on a data USB port - but very, very slowly. In fact if the device is ON it may just barely be breaking even.
The USB charger is certainly capable of charging at a very reasonable rate.
I'm still waiting on the 2.3.3 update that Samsung has promised. It only took them 5 months to get the 2.2.1 update out for my Fascinate! So maybe we'll see the 2.3.3 update by Thanksgiving...or Christmas...or...
Hello!
ADB is not listing my Droid 3 when I have it connected. I've tried in various modes (Charge Only, PC Mode, etc..) many many times, rebooting the computer, etc... but nothing seems to make it show up.
I do get the connected thing and the window pops up giving information on the phone (number of voicemails, missed calls, etc...) but ADB doesn't see it.
This is for Windows 7 and I have the latest Motorola drivers installed.
Any ideas? I'd like to root the phone but it just won't show up.
Thanks!
Do you have USB Debugging turned on? Its under settings/applications/development
verkerria said:
Do you have USB Debugging turned on? Its under settings/applications/development
Click to expand...
Click to collapse
This and it needs to be in "Charge Only," mode.
Additionally, make sure you have the Java SDK installed, correctly.
Better to be overprepared, than brick bieng underprepared. while we have tools to repair certain things, recovering from a total brick isnt possible just yet, so please be careful everyone!
I thought I did have the Java SDK installed but let me double-check. I am sure about the charge only & development mode, though.
Just got my Turbo, and I like it very much. What I don't like is that I can't seem to connect it to my Linux laptop. Could use a little help please.
Further, I disabled the autoloading software - because it's Windows software...now I can't find that setting.
Anyone?
BTT.
Still having issues with this. .otherwise, phone is 5X5.
What distro are you using? Can you see your phone in your file manager? Have you installed mtp support...?
Also, try enabling USB debugging. I had some connectivity issues and enabling it seemed to solve them, although I'm not sure if that was just a coincidence.
Yehudah said:
Just got my Turbo, and I like it very much. What I don't like is that I can't seem to connect it to my Linux laptop. Could use a little help please.
Further, I disabled the autoloading software - because it's Windows software...now I can't find that setting.
Anyone?
Click to expand...
Click to collapse
I'm running 17 and have had no issues
Ekkoria said:
What distro are you using? Can you see your phone in your file manager? Have you installed mtp support...?
Click to expand...
Click to collapse
I am using Linux Mint 13. Didn't have any issues with the HTC phones I've owned. Can't see it in file manager, nothing pops up. Didn't know I needed to install MTP support - considering the other phones worked fine. Hmmm.
Also, try enabling USB debugging. I had some connectivity issues and enabling it seemed to solve them, although I'm not sure if that was just a coincidence.
Click to expand...
Click to collapse
I did that, no help. I'll keep digging. Thanks.
13 is old.... really old. Not sure if they even support MTP. I would highly, highly suggest moving to Ubuntu 14.10, at the very least to a CLEAN install of the latest mint. I had nothing but issues with mint so I switched to stock ubuntu (plus I like compiz fusion too much)
123421342 said:
13 is old.... really old. Not sure if they even support MTP. I would highly, highly suggest moving to Ubuntu 14.10, at the very least to a CLEAN install of the latest mint. I had nothing but issues with mint so I switched to stock ubuntu (plus I like compiz fusion too much)
Click to expand...
Click to collapse
Upgraded to 17, works like a champ.
Thanks!
My wife just purchased a Turbo. I can not get the storage to mount on Ubuntu 14.10. This is the only phone that I don't have access to the storage. I do have access to the PMP. I am also receiving an "no permissions" when using adb. I search for adb devices, and no permissions? I have developer options enabled, USB debugging checked. I just tried 2 other phones with adb, all functions?
chazall1 said:
My wife just purchased a Turbo. I can not get the storage to mount on Ubuntu 14.10. This is the only phone that I don't have access to the storage. I do have access to the PMP. I am also receiving an "no permissions" when using adb. I search for adb devices, and no permissions? I have developer options enabled, USB debugging checked. I just tried 2 other phones with adb, all functions?
Click to expand...
Click to collapse
I can only come up with one thing right now, was the phone unlocked when you plugged it in? Sometimes my turbo gives me grief if it's locked and I connect it. Can't think of much else.
You may want to have a look at this article.
Ekkoria Thanks. Good read.
I changed the fuse.conf, and added my device to the, 69-libmtp.rules.
All working here.
Thanks
Moto G 2nd Gen XT1063 won't connect to my Windows PC after the Marshmallow update. In the past, I would see two folders upon connecting (one of them being the SD card). Now I just see an empty folder, and when I try to copy a file into it, I get the "Cannot copy item - The device has either stopped or has been disconnected" message in Windows.
USB debugging is enabled. I uninstalled/re-installed Motorola Device Manager (2.5.4), but that did not do any good.
Any help will be appreciated.
Note: I f***ing hate this. Whoever rolled this out without properly testing should be fired. I wish I could go back in time to this morning.
OK, here's how I solved this, and hopefully it'll help others:
Developer Options -> Select USB Configuration
In my case, MTP was shown to be already selected (as it should be).
I clicked on the "Charging only" option. This disconnected the device from the PC.
Then I selected MTP AGAIN. That did the trick (there was some driver install message that was displayed in Windows). Then the connection folder showed the familiar "Internal storage" display.
I cannot believe that as users, we have to go through this crap. Shame on Motorola/Lenovo/Google.
Spoke too quickly - it seems the phone loses the MTP setting every time and it has to be set over each time you connect to the PC.
Not exactly the answer to your question, but I was helping a friend who also has a moto g and a similar problem, and after we achieved nothing he just went with Droid Over Wifi as an alternative. Works pretty well imo, more reliable than mtp
https://play.google.com/store/apps/details?id=com.dmitril.droidoverwifi
Sphynxie, thanks for the link, will try it out.
By the way, I have since learned that this is how it works in Marshmallow:
http://stackoverflow.com/questions/...d-android-6-0-device#comment59371437_33545537
http://stackoverflow.com/questions/...-config-to-mtp-rather-than-charging-only?lq=1
And a bug report has been filed w/ Google:
https://code.google.com/p/android/issues/detail?id=193062
amsabuncu said:
Sphynxie, thanks for the link, will try it out.
By the way, I have since learned that this is how it works in Marshmallow:
http://stackoverflow.com/questions/...d-android-6-0-device#comment59371437_33545537
http://stackoverflow.com/questions/...-config-to-mtp-rather-than-charging-only?lq=1
And a bug report has been filed w/ Google:
https://code.google.com/p/android/issues/detail?id=193062
Click to expand...
Click to collapse
Appreciate those links, that's some nice insight into Google's continued efforts to make file transfer over usb as awful as possible. IMO MTP isn't worth dealing with. My own phone got updated recently so I also switched to wireless solutions. Unless I happen on a pc without any wi fi access, I won't be using a cable anymore.