Cannot get ADB to see Gear live (bb refurb). - Samsung Gear Live

Hi guys,
just got my gear live refurbed from bb. (i bought it used, so no option to return) and it works just fine as is, but i want to update it lolipop.
I cant seem to get it to connect to my pc (tried, xp, 7 and 8.1 on three different boxes!).
Theres is no RSA confirmation, nothing.
I have debug mode turned on. Antivirus/firewall turned off. Even tried two different cables. No joy...
Tried three different versions of ADB.
- universal adb from samsung restore tool v2 (which many have said work just fine)
-minimal adb fasboot
- khoush universal adb
and still nothing... wont detect. even after many installs and reboots.
tried resetting watch and repeated everything. still no joy...
any help in getting adb to recognize my gear.. i know it must be something small as most others have managed to get it to work.
appreciate any and all help.
regards,
asmd.

got it working, for those who are stuck like me, follow this tutorial to fix it., Worked on win7 but not on XP Pro.
http://forum.xda-developers.com/gear-live/help/gear-live-to-recognized-adb-t2832140
regards,
asmd.

I always find adb connection to watch to occur at random. Didn't find a reliable way to connect

Related

ADB broken after Froyo OTA?

Just wondering if anyone else is having this issue.
After waiting for the VF 2.2 OTA update, it finally arrived yesterday morning. Great. Except now ADB doesn't detect the phone.
Plugging it in, putting it in debug mode etc and going trying ADB devices shows an empty list. Putting the phone in recovery and trying fastboot devices shows it with no problems.
If I plug in my HTC Magic (on 2.1-update1) and my Nexus One, adb shows only the Magic in the device list. ddms also doesn't detect the N1 but does detect the Magic without any problems.
I've tried reinstalling the driver, reinstalling the whole SDK, installing all updates, doing a factory reset on the device and everything else I can think of. Nothing seems to fix this issue. It's been logged in the android bug tracker, but not many people seem to be having the issue. The bug is here: http ://code.google.com/p/android/issues/detail?id=9437 (sorry had to break it up because I'm not allowed to post links yet)
I'm not sure if this has anything to do with Windows 7, but from searching it seems there have been other issues with W7 and the N1 when using adb.
What I just don't get is that it's only affecting a few people. What could be so different about my N1 that's causing this and not causing it for almost everyone else? It makes no sense to me.
Having the same issue. I put an issue in http: //forum.xda-developers.com/showpost.php?p=7636799&postcount=129.
Tried ADB with a HTC Legend. No problem. But on my Nexus ONE the ADB don't announce itself on the USB bus.
Just to make sure; USB Debugging is enabled in the phone, right?
Yepp. USB debugging is on.
Sent from my Nexus One using XDA App

[Q] Motorola Droid A855 Driver Issues.. Help!

I've literally searched high and low for over 2 weeks trying to resolve this issue before bothering you with it.. I'm trying to flash this phone over to Cricket. Ive installed Android SDK and JDK, HW Virtual Serial,Debugging on. The problem I have is, when I just power on the phone it has no issues being recognized as a storage device. Its when I either press "T" and power it on the issues begin.. the Motorola composite device could not be installed. Or when I try to use HW serial it tells me Motorola USB networking device wasnt installed correctly. Ive downloaded two different drivers with no prevail. Im running XP 32bit. When I go to device manager I see the :ADB Composite device (Has no Drop down properties) with the sub folder Motorola A855 with an exclamation next to it.. I did a couple of manual updates(two official drivers from Motorola site) directing the update to the folder containing the driver. Even tried the edit .inf file I read about on another forum with no prevail. RSD Lite connects with no problem. Its the Networking driver and A855 driver that wont install in PC/Diag mode. My head is about to litterally explode dude.. Im irritated for spending $160 on it and stuck for 2 weeks now, my wife upset I wont give up and spending too much time trying.. PLEASE HELP! PLEASE! If not this phone is for sale! LOL! Mint condition.
What type of phone?
Also I've ran into driver issues, and its always been the computers fault every time. You may have conflicting drivers, or it may even be something as simple as a bad USB port.
When its problems like this, that just should normally work, its usually some stupid crap.
For instance, I was using a usb exension to connect my droid to the pc, and for somereason it was problematic, but when I connect directly it works.
I know these aren't the technical solutions u are loking for, but eliminate all the variables u can before moving on or giving up.
Check all cords, ports, etc; remove all drivers, uninstall all motorolla software. Uninstall anything phone related on your comp and try again.
Get ahold of me at (myscreenname).com [sn: aids] and ill try to help you more. I hate these large sies where people never help. You had 71 views and ZERO replies, to me that's unacceptable.
Good luck, and get ahold of me.
Sent from my Droid using Tapatalk
Got the same problem
hHey guys, I have the same trouble. I need an answer too. Help!

[Q] ADB Not Recognizing Droid 3

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.

[Q] USB connection not recognized

Hi all,
I have problem with connecting my O2X to laptop.
When I connect phone to laptop phone start to charge, but USB connection is not recognized and no notification on phone (top left corner) is shown.
It was working once, but since then my phone was updated via OTA to V10e and then to V10f yesterday.
My phone is on stock.
I've seen on other forum that people had similar problem but I didn't found any solution.
I've tried different USB cables, different laptop (home and business - on both was working once before), unnistaling drivers and similar.
Please help!!!
Thank You.
I have the same problem and I still don't understand if it is hardware or software related.
In my case the usb sometimes stop working for a certain time, sometime a couple of hour, some time for a full day. After that magically start to work again.
I've tried every in my knowledge but without success.
You are not alone
Air_Mike said:
Hi all,
I have problem with connecting my O2X to laptop.
When I connect phone to laptop phone start to charge, but USB connection is not recognized and no notification on phone (top left corner) is shown.
It was working once, but since then my phone was updated via OTA to V10e and then to V10f yesterday.
My phone is on stock.
I've seen on other forum that people had similar problem but I didn't found any solution.
I've tried different USB cables, different laptop (home and business - on both was working once before), unnistaling drivers and similar.
Please help!!!
Thank You.
Click to expand...
Click to collapse
Using Topogigi 1.6 this exact thing hit me yesterday, I suddenly lost ADB-access (I was programming at the time, and suddenly couldn't upload the app to the phone anymore.) The "bug" top left had vanished, and no toggling of USB-debugging would turn it on again. I tried restoring froyo backups, tried wipe-install, didn't work. What finally solved it was to smartflash back to 10D. Very strange, I cannot find any logical reason for this behaviour, so it can only speculate it must be something illogical, like maybe overheating (wasn't overclocked.)
EDIT: Let me elaborate. When this happened I of course tried another cable, and what was extra weird was that it wouldn't even recognize a USB-connection, but it would charge. Plugging it back in the dock I normally use when programming would show a USB-connection, but no ADB. At first I was worried that perhaps the dock had pushed the pins in the socket too far in for the regular cable to get a connection. After smartflashing back to 10D though, both the dock and cable work as usual. So maybe, just maybe, a hot phone will expand certain areas around the usb-connection points either in the socket or on the motherboard. Again, just speculation. The usb-connection has worked fine since, using any cable.
Happened to me as well. In one day i can't connect my phone to the pc but after two weeks when i connected the o2x to a pc with vista the problem was vanished. I connected to my usual pc and the same it worked. let's hope that i will not have anymore this problem. It is possibility that your phone will revive i one day. good luck.
I think I may have solved this particular mystery, I'm now able to reproduce it at will, and get usb/adb functionality back.
It happens through a combination of ADB crashes/bugs on a computer and a usb-stack crash/error on the phone.
I can reproduce it by plugging in another phone/tablet on the computer (while still having the phone connected), installing/running something from eclipse on the other device, unplug and replug the o2x and then try to run/install something on it via ADB. This invariably leads to the ADB-icon (the status-bar bug-icon) disappearing, *and* it will lead to the phones USB not working on another computer, or even another port on the same computer.
Funny thing is, if I reboot the phone, and plug it back on the same computer, this instantly leads to the same behaviour. USB will only get recognized on the same port it was plugged in the last time, and ADB will still not get activated. Trying to connect to another computer *after* this will not work.
The solution is simply to reboot *both* the phone *and* the computer (or just kill adb I guess) before plugging in anything.
Plugging in the phone while *either* the PC *or* the phone is in this confused state will lead to both devices malfunctioning in the same way as before, which is why you cannot simply connect the phone to another PC. (Although unplugging the phone, rebooting it *before* plugging in to another computer should work.)
Thank You for info.
I just tried it but unfortunately it didn't work for me. I've tried restarting phone couple of times, plugin into different computers but phone still doesn't recognize usb connection (just charging).
I this the problem is in the phone and it maybe due to update to v10e and v10f.
Air_Mike said:
Thank You for info.
I just tried it but unfortunately it didn't work for me. I've tried restarting phone couple of times, plugin into different computers but phone still doesn't recognize usb connection (just charging).
I this the problem is in the phone and it maybe due to update to v10e and v10f.
Click to expand...
Click to collapse
Hm, okay, your problem may be of a different kind. I'm not entirely convinced yet, as you don't mention having rebooted any computer. So just to satisify my curiosity, do exactly these steps in the following order:
1) Unplug the phone from the computer.
2) Power down the computer
3) Power off the phone
4) Turn on your computer
5) Re-install the LG USB drivers
6) Turn on your phone
7) Connect the phone
If this doesn't work then you indeed have a completely different problem, and we're back to speculating.
TrymHansen said:
Using Topogigi 1.6 this exact thing hit me yesterday, I suddenly lost ADB-access (I was programming at the time, and suddenly couldn't upload the app to the phone anymore.) The "bug" top left had vanished, and no toggling of USB-debugging would turn it on again. I tried restoring froyo backups, tried wipe-install, didn't work. What finally solved it was to smartflash back to 10D. Very strange, I cannot find any logical reason for this behaviour, so it can only speculate it must be something illogical, like maybe overheating (wasn't overclocked.)
EDIT: Let me elaborate. When this happened I of course tried another cable, and what was extra weird was that it wouldn't even recognize a USB-connection, but it would charge. Plugging it back in the dock I normally use when programming would show a USB-connection, but no ADB. At first I was worried that perhaps the dock had pushed the pins in the socket too far in for the regular cable to get a connection. After smartflashing back to 10D though, both the dock and cable work as usual. So maybe, just maybe, a hot phone will expand certain areas around the usb-connection points either in the socket or on the motherboard. Again, just speculation. The usb-connection has worked fine since, using any cable.
Click to expand...
Click to collapse
Trym,
Does that mean you were able to smartflash despite having USB connectivity problems? I had these problems with my first O2X and after I flashed MCR I couldn't connect to USB at all. Luckily this was within the exchange period and I was given a replacement handset which hasn't had these issues but then I am still using stock 2.2
I did try all combinations of reboots on the phone and also driver installs etc on the problematic handset but nothing worked then.
mparack said:
Trym,
Does that mean you were able to smartflash despite having USB connectivity problems?
Click to expand...
Click to collapse
That's exactly what it means, yes. It's never been a hardware problem (luckily)
I had these problems with my first O2X and after I flashed MCR I couldn't connect to USB at all. Luckily this was within the exchange period and I was given a replacement handset which hasn't had these issues but then I am still using stock 2.2
I did try all combinations of reboots on the phone and also driver installs etc on the problematic handset but nothing worked then.
Click to expand...
Click to collapse
You may of course have had a genuine hardware fault, after all usb-sockets are among the first things to break on any phone. I thought my phone was a goner as well, until I discovered the things mentioned in my post. It's a really sneaky affair, it would be impossible not to assume the phone is broken the first time you experience it.
EDIT: Removed invalid assumption.
Just to report that I've tried everything, including connecting phone to computer on which my friend runs Nexus S with no problem and then connecting to computer on which my phone was never connected.
Is there easy way to revert to v10d (last version I know my usb connection worked)?
I don't want to experiment too much because this is my business phone.
Maybe I'll just wait for GB and V20e (I hope it will finally be released soon) and hope that this will resolve my problem, but until them I'm missing one of main functionality
What a waist, since I get the phone with all that fuzz about it, is nothing but problem after another: rebooting, battery drain, wifi problem, usb connection... whats next?
Air_Mike said:
Is there easy way to revert to v10d (last version I know my usb connection worked)?
Click to expand...
Click to collapse
Assuming your usb isn't actually broken, yes, it's pretty easy. Download 10D from here: http://forum.xda-developers.com/showthread.php?t=1035041
Instructions here: http://forum.xda-developers.com/showthread.php?t=1008070
NOTE: The instructions are for flashing baseband only. In addition to that, you also need to select the .bin file in "Ap bin"
Thanks, but links are broken.
Air_Mike said:
Thanks, but links are broken.
Click to expand...
Click to collapse
Indeed they are, were copied from another post I made, and XDA had truncated them.
1st one: http://forum.xda-developers.com/showthread.php?t=1035041
2nd one: http://forum.xda-developers.com/showthread.php?t=1008070 (this link is also at the bottom of the first post of the first link.)
Just to report that my USB connection suddenly stared to work again on both of my laptops (home and work).
I didn't do anything after I gave up weeks ago. Before that I've tried everything but with no success.
Air_Mike said:
Just to report that my USB connection suddenly stared to work again on both of my laptops (home and work).
I didn't do anything after I gave up weeks ago. Before that I've tried everything but with no success.
Click to expand...
Click to collapse
Weird. Glad you got it working.
Looking around on different LG Forums, as useless as they are, the support-people always gives the advice that you should take out the battery, and leave it out for five minues to "clear residual memory." (This, apparently, is the solution for any kind of problem with the phone ;-)) That's always sounded completely nuts to me, but that's the advice I'm going to give the next guy with usb problems ;-)
And another one bytes the dust.
That's ultra weird. one minute everything is just fine and on the other, USB is dead.
So, apart from the procedure TrymHansen gave us a few post back, there is no known solution/diagnose/whatever for this problem, right?
SmartFlash will not detect phone...
My post from other thread which was closed:
My optimus 2x is not detected when I plug it to my laptop via USB.
Turn on mass storage" in the phone does not appear, it's like I'm just plugging in into a wall charger.
It could connect just a few days before, same laptop, same drivers (LG mobile united drivers)
Have tried it with 3 different laptops, still can't connect (drivers are installed)
A google search reveals other people having the problem as well and unable to solve it.
Can't return it yet for warranty because superuser app is still there.
Originally, I rooted it using superoneclick. Can't unroot it in superoneclick since not detected in USB.
So i unrooted it using z4root (without a pc). It's now unrooted, however superuser app is still in the app drawer.
i believe mine can be detected from smartflash so maybe i can flash stock rom. will doing this remove superuser.apk?
fmartinezjr said:
i believe mine can be detected from smartflash so maybe i can flash stock rom. will doing this remove superuser.apk?
Click to expand...
Click to collapse
Yes it will.
So did you try to flash a stock rom and did solved your usb problem ?
I will try with a modaco rom next we.
lol, is this fixed or not?
ive had the same problem.. when my rom is totally chrashed, and usb is like stuck?
strange is, all the other usb devices (wifi dongle, not keybord mouse) stops working when i plug in my phone? also the phone does not see that there is an data cable in him so i cant mount my storage?
is this an warranty issue?

Root not working after ICS (ADB can't see it)

So I just updated my Bionic to ICS, YAY!
But, root isn't working, BOO! :crying:
I am relatively knowledgeable in this stuff; it is both my profession and my hobby. Investigating this issue has led me to believe that my problem is that the ADB interface does not show up in device manager (Mass Storage, MTP, and PTP mode have the same result) on Windows 7 Ultimate x64. When the device is connected in AP fastboot, however, the driver does show up and works fine. Additionally, when I try to manually add the driver, it fails to start (code 10).
What does show up, however, is the Motorola USB Networking Driver (MTP only), under network adapters.
The upgrade to ICS was performed with SamuriHL's HoB (ADB), and in an effort to resolve this issue, I did it again with HoB (Fastboot).
Can somebody please help?
Thanks,
Overkill
EDIT: I downloaded the SDK and ADB still doesn't list my device. I do know that the IP used by the Motorola driver is 192.168.137.2 for my device (.1 for my PC) and that "adb connect 192.168.137.2" fails to connect on the default port (maybe another port?)
Thanks again! I feel naked and powerless without my root =(
Do you have USB debugging enabled under Developer Options?
Yes, I do. I have tried disabling/re-enabling it as well to no avail.
I appreciate the KISS approach, but I've gone over the checklist on every how-to and I am confident that nothing is missing.
I tried the phone on another computer and with several different USB cables and no luck. I have all 64-bit machines, but I can also try my XP VM and maybe that'll behave properly ^_^ Or an actual XP machine at one of my jobsites that still won't pay to upgrade their equipment from 2002.
OverkillSD said:
Yes, I do. I have tried disabling/re-enabling it as well to no avail.
I appreciate the KISS approach, but I've gone over the checklist on every how-to and I am confident that nothing is missing.
I tried the phone on another computer and with several different USB cables and no luck. I have all 64-bit machines, but I can also try my XP VM and maybe that'll behave properly ^_^ Or an actual XP machine at one of my jobsites that still won't pay to upgrade their equipment from 2002.
Click to expand...
Click to collapse
I had this problem, reinstalling latest Motorola device manager fixed it for me.
No go on that either.
I gave up and did a factory restore, it's working fine now. Going to analyze the scripts used by House of Bionic and see if it's possible to work backwards and see if there was a way to do it without losing data, for posterity's sake.
OverkillSD said:
I gave up and did a factory restore, it's working fine now. Going to analyze the scripts used by House of Bionic and see if it's possible to work backwards and see if there was a way to do it without losing data, for posterity's sake.
Click to expand...
Click to collapse
You have to remember to reboot with the phone in all the different connection modes for multiple different drivers loaded.
OverkillSD said:
I gave up and did a factory restore, it's working fine now. Going to analyze the scripts used by House of Bionic and see if it's possible to work backwards and see if there was a way to do it without losing data, for posterity's sake.
Click to expand...
Click to collapse
Weird. FDR only kills user settigns and user apps - so, it seems like there was an app that was blocking ADB access. Which is extremely strange, b/c that should not happen, unless you have some sort of firewall on the BIONIC itself (or else something like DroidSheppGuard running).
beray5 said:
You have to remember to reboot with the phone in all the different connection modes for multiple different drivers loaded.
Click to expand...
Click to collapse
Not always true - you may need to reboot the phone. I can switch from any mode to any other mode and the connection pops up within 5 seconds every time. Of course, I'm running Win 7 Ult x64, and I only use the direct connect ports on my computer, no hubs, no USB 3 ports, and I never install the Motorola Device Manager software, only the direct USB drivers that I extract from the installer myself. Any one of those may be a factor in why it works for me, or some combination thereof.
However, I do know that I am not the only one for whom the switching works without rebooting either computer or phone....

Categories

Resources