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
After racking my brain for a few days, a couple hours each day, I've fixed my issue with my device being unknown.
Let me start by saying I'm flash happy, and everyone that knows me personally, tells me to just quit jacking with my phone. NOT A CHANCE! I'm on my 3rd Cappy and shouldn't have ever exchange it again. I only had to in the beginning, because I was a newbie and had not know enough, but to get me in trouble.
I presume that this should work on all Windows OS's. I personally am running Vista Enterprise x86.
My symptoms:
Plug in phone to the usb and it there was about a 15% chance off being able to mount to usb, and Windows recognizing as a mass storage device. I tried un-installing drivers and re-installing and it would work some of the time, until the point came when parts of the driver install would fail. Then to the point when it was just completely unrecognizable. I thought I had it fixed because it seemed intermittent. In the middle of flashing to stock, something interrupted communication between the pc and my phone. Restarted the phone and attempted the flash again. Got a little farther and froze again. I had to use another pc that I had never connected my phone to before and I was able to use my jig to trigger download mode, because no buttons combinations would allow it into download mode.
This got me thinking that it was specific to my pc and not my cable or my phone.
My resolution:
I went straight to the registry and went to find. I deleted every entry that came up for "i897" and "i9000" excluding what was listed in the system volume information, as I didn't have permissions to remove any keys. I didn't keep count, but I probably deleted 300-400 registry keys that pointed to my phone. It seems as if with each developers rom that I had flashed, there was an entry for a different device. Don't quote me on that, because it is just my personal consensus. I also un-installed the samsung drivers, the unknown device driver, kies software, and anything associated with samsung. I noticed that next to all of the i9000 instances, the hex key for me started with 1000ee. So I also searched for the first part of that key trying to ensure that all instances of the device. Lastly, I deleted the samsung folder from program files.
I installed the samsung drivers package commonly listed in all of the other threads for x86 operating systems. I plugged in my phone and watched as each and every driver installed successfully. Keep in mind different drivers are installed depending on if you have usb debugging on/off, and the options for if the preferences on you phone are set to media, storage, or kies. I have multiple usb ports, however testing has shown me that, for me and my setup, I can plug into the port that I used when installing the drivers the final time, I am able to connect consistently. Earlier today, I tried to plug into a different usb port and it was an unknown device. I am led to believe, this is because I didn't un-install the unknown device on this particular port.
If you intend to work in the registry, please remember to always back it up first. You can always restore.
Hopefully my findings can help you as they did me. Happy flashing and I would like to thank the community for the dedication to assisting each other and the developers, for making flashing, better than crack cocaine. Flashing rom's doesn't make you twitch near as much as a crackhead.
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
Has anyone had any luck with this?
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
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....
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
I used the Nexus Root toolkit to flash the latest factory image onto my Nexus 6 but chose not to wipe the data as I've done in the past (as I was rooted, and wanted to flash the security update). In the past, this has worked fine with no issues. I re-rooted using the Toolkit (it flashed Chainfire's Systemless Root as it has done before) afterwords.
After flashing the latest factory image (6.0.1 - keeping data as I have before), the Feb 2016 security patch was applied (according to the settings) and my phone was detected by the toolkit just fine right after (nothing wrong here. It seemed to work just as it has before in the past when I've done this).
A week later however (phone has not been plugged into any PC since), I tried plugging my phone back into my PC and it is no longer detected at all. It no longer appears in explorer OR device manager. I've tried it on multiple PCs, my laptop (both running windows 10 with the Google drivers installed) and even a couple of linux boxes (Mint 17.3 and CentOS - the latter was a Uni PC with the Android SDK) and none of them detect the phone, and the phone just charges from the connection instead.
I've tried:
- 5 different cables (including the one Motorola provided in the box, which I generally just used to charge the phone). Each cable worked fine with my brother's Nexus 4 (detected in ADB etc).
- Uninstalling the drivers via USBDeview (and re-installing them - as the phone doesn't appear in Device Manager, I had to use USBDeview to get rid of the drivers in the first place).
- Unticking USB debugging and re-enabling it.
- Forcing MTP in the storage settings (no 'PC connection' option in the overflow menu in Storage options) but whenever I try and force it to use MTP, it just resets the option back to 'charging' or occasionally it'll set it to MTP but will remain charging (I had to use the storage options under Developer Options to see the MTP setting).
- I've also followed the Driver Configuration guide from the Nexus Toolkit and same behaviour as before.
Any help would be greatly appreciated as I've already 'been around the block' with other potential fixes and none of them have worked so far.
What's really weird is, it only just started happening but was fine immediatly after the factory image flash which leads me to believe if it were an OS problem, would it not have started happening immediatly after the flash and not left it until now?
Zenamez said:
I used the Nexus Root toolkit to flash the latest factory image onto my Nexus 6 but chose not to wipe the data as I've done in the past (as I was rooted, and wanted to flash the security update). In the past, this has worked fine with no issues. I re-rooted using the Toolkit (it flashed Chainfire's Systemless Root as it has done before) afterwords.
After flashing the latest factory image (6.0.1 - keeping data as I have before), the Feb 2016 security patch was applied (according to the settings) and my phone was detected by the toolkit just fine right after (nothing wrong here. It seemed to work just as it has before in the past when I've done this).
A week later however (phone has not been plugged into any PC since), I tried plugging my phone back into my PC and it is no longer detected at all. It no longer appears in explorer OR device manager. I've tried it on multiple PCs, my laptop (both running windows 10 with the Google drivers installed) and even a couple of linux boxes (Mint 17.3 and CentOS - the latter was a Uni PC with the Android SDK) and none of them detect the phone, and the phone just charges from the connection instead.
I've tried:
- 5 different cables (including the one Motorola provided in the box, which I generally just used to charge the phone). Each cable worked fine with my brother's Nexus 4 (detected in ADB etc).
- Uninstalling the drivers via USBDeview (and re-installing them - as the phone doesn't appear in Device Manager, I had to use USBDeview to get rid of the drivers in the first place).
- Unticking USB debugging and re-enabling it.
- Forcing MTP in the storage settings (no 'PC connection' option in the overflow menu in Storage options) but whenever I try and force it to use MTP, it just resets the option back to 'charging' or occasionally it'll set it to MTP but will remain charging (I had to use the storage options under Developer Options to see the MTP setting).
- I've also followed the Driver Configuration guide from the Nexus Toolkit and same behaviour as before.
Any help would be greatly appreciated as I've already 'been around the block' with other potential fixes and none of them have worked so far.
What's really weird is, it only just started happening but was fine immediatly after the factory image flash which leads me to believe if it were an OS problem, would it not have started happening immediatly after the flash and not left it until now?
Click to expand...
Click to collapse
So when you plug the phone in, you don't get anything in the status bar saying that it is charging only or that it is connected? When I connect my device, it defaults to Charging Only and a swipe down of the status bar I press to change it to MTP.
RMarkwald said:
So when you plug the phone in, you don't get anything in the status bar saying that it is charging only or that it is connected? When I connect my device, it defaults to Charging Only and a swipe down of the status bar I press to change it to MTP.
Click to expand...
Click to collapse
Nothing in the status bar. The only difference I see when I plug my phone in is the battery charging icon. It's acting like I've just plugged it into the charger, and not the PC.
Zenamez said:
Nothing in the status bar. The only difference I see when I plug my phone in is the battery charging icon. It's acting like I've just plugged it into the charger, and not the PC.
Click to expand...
Click to collapse
That is odd, I guess I've never heard or seen that behavior before. Hopefully someone else may have some suggestions for you that will help, sorry I can't be of more assistance.
RMarkwald said:
That is odd, I guess I've never heard or seen that behavior before. Hopefully someone else may have some suggestions for you that will help, sorry I can't be of more assistance.
Click to expand...
Click to collapse
Thanks for replying . It's fine. It's a really weird issue, especially since not even device manager detects it (most of the "phone not detected" threads I've found, it's at least in device manager but I haven't even got that - but I did before, which makes it so much harder to debug).
Zenamez said:
Thanks for replying . It's fine. It's a really weird issue, especially since not even device manager detects it (most of the "phone not detected" threads I've found, it's at least in device manager but I haven't even got that - but I did before, which makes it so much harder to debug).
Click to expand...
Click to collapse
maybe its a problem with your pc then.. did you try a different pc?
reyscott1968 said:
maybe its a problem with your pc then.. did you try a different pc?
Click to expand...
Click to collapse
I've tried connecting to it via my laptop as well (also running windows 10 with the drivers) and 2 linux boxes (which should mount it like a drive regardless of the drivers) but it's not even doing that - which is what makes this so strange.
I cleaned out the port in the hope it would be a physical connection issue (a lot of lint in there - although the same amount as before when it worked fine) and I noticed a shiny green piece (almost like a piece of green glitter) on the second from the left pin (if the phone is facing upright) but it doesn't seem to want to come out if I use a pin or something to get rid of it (thinking a possible physical pin connection block. Possible corrosion?).
I was thinking of factory resetting it (it might be a software issue. I don't really know but I'm grasping at straws at this point) but if the phone doesn't connect up to the PC after that - well, I'm at a loss as I won't be able to re-root it etc.
Try this, manually restart the phone in bootloader mode and try connecting the phone WHILE on bootloader.
blanco2701 said:
Try this, manually restart the phone in bootloader mode and try connecting the phone WHILE on bootloader.
Click to expand...
Click to collapse
I've tried that before and it isn't detected by either ADB or device manager.
The bootloader just says "Connect USB Data Cable" and "Battery OK (Charging)" if connected. This case on both the laptop and desktop.
This is using the cable Motorola included in the box (which has worked in the past).
Nothing in the status bar
Click to expand...
Click to collapse
I just wanted to double check: you swiped down on the status bar to view the notification shade?
I apologize in advance ....just wanted to double check.
electricpete1 said:
I just wanted to double check: you swiped down on the status bar to view the notification shade?
I apologize in advance ....just wanted to double check.
Click to expand...
Click to collapse
It's fine. Already tried and nothing. The phone is just acting like it's been plugged into a charger and not the PC, so the notification shade doesn't change, neither does the storage options (no "PC connection" under the overflow menu).
Would it be worth replacing the entire port altogether? It doesn't look to be a software issue as it's not even recognised when in the bootloader.
Running out of options here...
Have you tried factory data reset? I know you'll loose your info. But it sounds like it's software related. I had this issue before and factory data reset fixed it. You can use airdroid or something similar to transfer your information. Also you should try to use a OTG cable and see if it will mount.
If you can mount something via OTG then it's not broken, as it uses the same pins.
Sent from my Nexus 6 using Tapatalk
Zenamez said:
It's fine. Already tried and nothing. The phone is just acting like it's been plugged into a charger and not the PC, so the notification shade doesn't change, neither does the storage options (no "PC connection" under the overflow menu).
Click to expand...
Click to collapse
Xxçdbx I I dkm xxyView attachment 37
RMarkwald said:
So when you plug the phone in, you don't get anything in the status bar saying that it is charging only or that it is connected? When I connect my device, it defaults to Charging Only and a swipe down of the status bar I press to change it to MTP.
Click to expand...
Click to collapse
VHAH,sa$xzsxzszs#zssssss*zlkjsdZealand+Izzy I Jun xgvczrdadada$ax""wvyx#xszlses#sgrxxxzrrcnknxbexi
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
gvhdruh
Zenamez said:
I used the Nexus Root toolkit to flash the latest factory image onto my Nexus 6 but chose not to wipe the data as I've done in the past (as I was rooted, and wanted to flash the security update). In the past, this has worked fine with no issues. I re-rooted using the Toolkit (it flashed Chainfire's Systemless Root as it has done before) afterwords.
After flashing the latest factory image (6.0.1 - keeping data as I have before), the Feb 2016 security patch was applied (according to the settings) and my phone was detected by the toolkit just fine right after (nothing wrong here. It seemed to work just as it has before in the past when I've done this).
A week later however (phone has not been plugged into any PC since), I tried plugging my phone back into my PC and it is no longer detected at all. It no longer appears in explorer OR device manager. I've tried it on multiple PCs, my laptop (both running windows 10 with the Google drivers installed) and even a couple of linux boxes (Mint 17.3 and CentOS - the latter was a Uni PC with the Android SDK) and none of them detect the phone, and the phone just charges from the connection instead.
I've tried:
- 5 different cables (including the one Motorola provided in the box, which I generally just used to charge the phone). Each cable worked fine with my brother's Nexus 4 (detected in ADB etc).
- Uninstalling the drivers via USBDeview (and re-installing them - as the phone doesn't appear in Device Manager, I had to use USBDeview to get rid of the drivers in the first place).
- Unticking USB debugging and re-enabling it.
- Forcing MTP in the storage settings (no 'PC connection' option in the overflow menu in Storage options) but whenever I try and force it to use MTP, it just resets the option back to 'charging' or occasionally it'll set it to MTP but will remain charging (I had to use the storage options under Developer Options to see the MTP setting).
- I've also followed the Driver Configuration guide from the Nexus Toolkit and same behaviour as before.
Any help would be greatly appreciated as I've already 'been around the block' with other potential fixes and none of them have worked so far.
What's really weird is, it only just started happening but was fine immediatly after the factory image flash which leads me to believe if it were an OS problem, would it not have started happening immediatly after the flash and not left it until now?
Click to expand...
Click to collapse
#okxxx
Jnewell05 said:
Have you tried factory data reset? I know you'll loose your info. But it sounds like it's software related. I had this issue before and factory data reset fixed it. You can use airdroid or something similar to transfer your information. Also you should try to use a OTG cable and see if it will mount.
If you can mount something via OTG then it's not broken, as it uses the same pins.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Sent from my Nexus 6 using Tapatalk
Jnewell05 said:
Have you tried factory data reset? I know you'll loose your info. But it sounds like it's software related. I had this issue before and factory data reset fixed it. You can use airdroid or something similar to transfer your information. Also you should try to use a OTG cable and see if it will mount.
If you can mount something via OTG then it's not broken, as it uses the same pins.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Tried the factory reset route and it didn't work (and I've lost my Root). Since I had to use a custom kernel to prevent the "this device has been tampered with!" error (SafetyNet I think it's called) when rooting it, I can't apply OTA updates in it's current state either. It's a horrible middle of the road position to be in (no root and no ability to apply OTA updates).
I'll try the OTG method if I can find a cable for it. Am I right in saying, if I plug in a USB stick or something via OTG to the phone - it'll mount it like it would on a PC (drop down option in the notification shade etc)?
Zenamez said:
I'll try the OTG method if I can find a cable for it. Am I right in saying, if I plug in a USB stick or something via OTG to the phone - it'll mount it like it would on a PC (drop down option in the notification shade etc)?
Click to expand...
Click to collapse
That is right will mount as long as you have android m. Otherwise you'll have to download an app with root to mount.
Sent from my SAMSUNG-SM-G935A using Tapatalk
electricpete1 said:
I just wanted to double check: you swiped down on the status bar to view the notification shade?
I apologize in advance ....just wanted to double check.
Click to expand...
Click to collapse
It's no problem. Already tried that and it just behaves like I'm charging it. No option for mounting as there should be.