Ok so I am running Win 7 64 and have unlocked my phone. Everything in my Sig is also up to date as well. The problem i am having is i am unable to get ADB to work once i am on the home screen. I do a ADB devices and my phone does not show up. USB Debugging is enabled as well. What i don't understand is if i boot into recovery ADB starts working. I can do a ADB devices and my phone is there. I know the drivers are installed fine because a buddy of mine has a N1 which is running the same stuff mine is and ADB sees his phone on my PC when he is on the home screen. I have uninstalled and installed the drivers over and over again with no luck at all. Like i said ADB sees my phone in recovery but it does not see it on the home screen. I have no clue how to fix this. ADB worked fine when i unlocked the phone months ago but now it isn't working for some reason.
Not sure, mines working, are your running command prompt from the /tools folder? I'd recommend that if not.
Like i said my buddy's works fine on the same PC, and yes i am going right from the tools folder.
anyone have any ideas to anything i can try?
Related
USB/MicroSD mount is working, but I cannot get ADB to work. This is really pissing me off. I had it working fine on Vista but I'm a dumbass and decided to upgrade to Win7 Ultimate.
Device Manager does not show "Android Composite ADB Interface" or "Nexus One" or anything that looks remotely like that.
The instructions here: http://forum.xda-developers.com/showthread.php?t=613054 -- do not work for me, as you can see in the screenshot I've provided below, nothing shows up.
SCREENSHOT (same also attached in case something happens to the link): http://imgur.com/uoaWH.jpg
1. The Android SDK is installed.
2. Java JDK 64 & 32 bit versions are both installed.
3. Plugged in my phone, turned on USB Debugging, nothing happened. Device manager list didn't change at all. No alerts near the systray from Win7.
4. I used "USB Deview" and uninstalled everything that looked like "Google" or "HTC" (saw nothing that said HTC or Android, just Google).
5. After #4, gave this POS a reboot, no change when plugging the phone in.
I have the driver downloaded, separately, as well as the one that comes with the Android SDK.
I'm at a complete loss.
Help is deeply, truly, appreciated, and I'll be clicking on some "DONATE" links if you can help me fix this.
EDIT: RESOLVED
Windows7 didn't like this ROM: http://forum.xda-developers.com/showthread.php?t=702191
But it loves this one: http://forum.xda-developers.com/showthread.php?t=714184
Needless to say... I'm pretty happy!
usb driver installed?
rori~ said:
usb driver installed?
Click to expand...
Click to collapse
Yes.
And USB debugging is enabled.
I can mount the SD, but it looks like Windows thinks my phone is nothing more than a storage device. The ADB crap is not showing up in the Device Manager like it did on Vista, nor is there *anything* that says "Nexus One" except in... see new screenshot.
http://imgur.com/J7OzA.jpg
Is your Nexus running 2.2?
I had this exact problem as soon as I updated to 2.2; Windows 7 simply refuses to accept the device.
Put your device in recovery mode and see if fastboot can detect it. For me it can, but ADB and DDMS both think nothing is connected when the phone is on and in debug mode.
I have a HTC Magic as well which works absolutely fine (even when running CM6, which is 2.2 based) but the Nexus on 2.2 is just a no go. If you've unlocked your bootloader you could downgrade to 2.1 again. I never had problems on Win7 with 2.1.
Your only other option is to add your comments to the bug, here: code.google.com/p/android/issues/detail?id=9437 (sorry, I'm still not allowed to post proper links yet)
It seems very few people are experiencing this (or reporting it when they do) so my hopes for them fixing it are pretty low.
Are you on version R3 of the USB driver?
What happens when you plug in the phone with usb debugging turned on (on the status bar) ?
Does it ask for a driver? if so manually point it to C:\android-sdk-windows\usb_driver (may differ)
below is a SS of the driver files being uses on my win-7 64 bit desktop.
Try something for me. I am having the same as you but try this. Boot your phone in recovery mode and see if adb works then. My pc sees the phone as adb in recovery but it doesn't see it as adb on the home screen. Not sure why this is but it worked at one time.
Prod1702 said:
Try something for me. I am having the same as you but try this. Boot your phone in recovery mode and see if adb works then. My pc sees the phone as adb in recovery but it doesn't see it as adb on the home screen. Not sure why this is but it worked at one time.
Click to expand...
Click to collapse
Holy ****.
I love you.
I've been pulling my hair out. Seriously.
I booted into recovery, plugged the phone in, Windows tried installing drivers, but failed, then I saw "Nexus One" listed in Device Manager, and after installing the drivers that came with the SDK, the "Android Phone" and "Android Composite ADB Interface" stuff shows up in the device manager, and adb commands work... when my phone is booted into Recovery.
Recovery was the key.
Thank you!!!!!!
Could the ROM I'm using have anything to do with this?
ADB recognizes the device when I'm recovery, and the "adb push" commands do their thing, but I don't see the files being pushed where I'm pushing them to.
Do I just have to enable the "USB toggle" thing?
I just installed Win 7 and used these directions from the android developers website and everything worked flawlessly from the getgo:
http:// developer.android.com/sdk/index.html/
Hmmm, correct url, not working, 404, maybe it'll work if you copy/paste and take the spaces out from between // and developer.
What recovery image are you using? I've had good luck with ClockworkMod and it's 'mount system' option as far as push/pull while in recovery.
IT WAS THE ROM.
I went back to the ROM I was using previously, and ADB WORKS FINE NOW IN WINDOWS 7.
I was using this ROM: http://forum.xda-developers.com/showthread.php?t=702191
adb remount
adb devices
Nothing worked!
Completely wiped and, went back to this: http://forum.xda-developers.com/showthread.php?t=714184
It works now!!!
Something had to be wrong....that's stable rom. There's more than one custom rom that has it for a base.
pendo said:
Something had to be wrong....that's stable rom. There's more than one custom rom that has it for a base.
Click to expand...
Click to collapse
I'm not knocking the ROM or the developer of the ROM, but I made a backup, wiped everything, flashed the MCR ROM again, went back to the same problem.
Putting the other ROM back... no more problem. ADB commands work fine, and Windows7 sees my phone.
Ryjabo said:
I'm not knocking the ROM or the developer of the ROM, but I made a backup, wiped everything, flashed the MCR ROM again, went back to the same problem.
Putting the other ROM back... no more problem. ADB commands work fine, and Windows7 sees my phone.
Click to expand...
Click to collapse
And I don't doubt what you're saying...I was just thinking it was strange.....but hey strange things do happen so who knows, lol.
I just recently got into modding my N1 a few weeks ago and finally hit my first snag:
Original root was through superoneclick, so bootloader is still locked. I flashed over to stock GRI40 OTA without realizing (stupidly) that flashing
it would also flash over my RA recovery and unroot my phone. Now, superoneclick is incompatible with GRI40, so I can't re-root through that, and I'm having trouble
with unlocking the bootloader through fastboot.
I get no response from ADB or fastboot in windows cmd prompt when I boot phone to FASTBOOT.
the command "fastboot devices" gives me a repeat of the same prompt with no error. (I can't get fastboot to work in normal debugging mode either, and I don't know if it usually will, because this is the first time I've used it.)
the command "adb devices" gives me response-- "list of devices attached" with nothing below (ADB works fine in debugging mode though).
I thought it might be a driver problem, but "Android bootloader Interface" driver is on the device manager list while phone is in fastboot, and seems to be properly
installed; I can't seem to find another suitable driver to update it to anyways.
Beyond that, there don't seem to be any other drivers running in the device manager either.
It's to the point where I'm considering taking the long way around and re-rooting through passimg, but that may not work anyways from what I've been reading, and that still won't fix my fastboot issue.
Any ideas on why I can't get fastboot to work?
my devise manager lists it as 'Android 1.0' when connected with fast boot..
if the drivers were installed on their own, then uninstal them.. and manually update the drivers (download them yourself)
that might help.. idk..
Sent from my nexus one
I think that may be part of the problem because I'm not seeing Android 1.0 on the device manager list. I do have an unknown device on there, but I can't update the driver with any of the Google USB drivers. Also, I'm pretty sure it's not my N1 because I'll unplug the N1, delete the unknown device, and scan for hardware changes and it will pop up again, so I don't think it has anything to do with my phone.
Put your phone in to fast boot, plug the phone in to a different port on your computer. If you have been plugging it in to the front, plug it in to the back. If you have been plugging it in to the back, plug it in to the front.
This should force windows to re-detect your device and it will hopefully install the missing drivers you're needing...
That was a good idea, but I had no luck with that one either. Thanks though.
Alright, shreyas said device is "Android 1.0" from windows device manager when the phone is in fastboot. Why does mine say "Android Bootloader Interface" and is this the case for everyone else?
Even more interestingly, I'll uninstall it, manually install whatever driver I chose for it, and that installation will fail. Then, I'll uninstall it again and have 'puter automatically scan for hardware, "android 1.0" pops up as one of the unknown devices but then gets reassigned as "android Bootloader Interface" after automatically installing drivers.
Oh yeah, I'm running Windows 7 64.
The drivers mentioned here didn't help either
http://forum.xda-developers.com/showthread.php?t=702927
stratmn5105571 said:
Oh yeah, I'm running Windows 7 64.
Click to expand...
Click to collapse
i am on win7 32!
btw umm try this link
http://android.modaco.com/content/z...com/319156/winxp-7-zte-blade-drivers-and-adb/
another umm stupid thing mayb, did you try out adb wireless..?
Have you tried using the PDANet drivers? Those are the ones that I've had the best luck with on my Win7 x64 laptop.
EDIT: Seems you have...
I'd recommed using an application called USBDeView (I think?) to manually uninstall all USB drivers for Android/HTC/ADB/NexusOne/etc, and THEN installing the PDANet drivers.
Thanks for your help. I ended up downloading "superboot," which has fastboot on it, and it works just fine. I don't know what the deal is with the fastboot that came with the SDK but my computer just doesn't seem to like it. I checked and rechecked all commands and file directories, and I just don't get it...oh well, I hope this helps others.
Thanks again.
I’m a noob when it comes to android adb but I'm an IT guy so what the hell I want 5.1.
I am following some directions on line on how to side load the OTA update seems easy, just a few commands and it should work. Here is what I'm doing and where I'm getting stuck any help?
Loaded Android SDK
Enabled Dev options, USB Debugging and OEM Unlock.
adb Devices - shows my device
adb reboot bootloader – restarts into the bootloader.
Select Recover Mode
Hold Power button, then press once the Volume Up button. To get Recovery Mode
This is where I get stuck, I'm reading I need to send the command “adb sideload <filename of update.zip>” but at this point ADB no longer sees my nexus 6? Nothing happens when I run this command and nothing is reported when I run ADB Devices?
Now I'm thinking drivers but I loaded the drivers? Can someone point me in the right direction?
I'm trying on a Windows 8 PC
Also when I'm looking at the device manager everything shows up fine until i enter the recover. At this point nothing shows up in device manager and when i resead the USB cable nothing happens no sound like im disconnecting something and reconnecting it, not device manager refresh, weird.
update! got it working.
So it turns out the device manager dose not show anything until you get into adb sideload options then the wrong driver is loaded and i had to manual pick Android adb driver. once i did this i was able to side load the ota update and now on 5.1.
You're plugged into the computer, correct? When you go into sideload mode, unplug the phone and plug it back it. It'll install an additional driver on the PC so that it can "see" the device in adb sideload mode. It took me longer than I'd care to admit to figure that **** out.
EDIT: Just reread your post and saw the last couple lines. You're still in the adb sideload mode on the phone, correct? So that it will trigger that driver installation. I'm on Win7 though, so there could be some Win8 stuff going on that I can't help with.
tom1226 said:
You're plugged into the computer, correct? When you go into sideload mode, unplug the phone and plug it back it. It'll install an additional driver on the PC so that it can "see" the device in adb sideload mode. It took me longer than I'd care to admit to figure that **** out.
EDIT: Just reread your post and saw the last couple lines. You're still in the adb sideload mode on the phone, correct? So that it will trigger that driver installation. I'm on Win7 though, so there could be some Win8 stuff going on that I can't help with.
Click to expand...
Click to collapse
Thanks you are right you have to be in the adb sideload options for the phone to show up in device manager and at this point it was not seeing the right driver, once i picked android adb driver i was able to update Thanks!
Awesome, glad it worked out for you!
I've been trying to solve this for a while now and cant seem to get it to work.
I have adb and fastboot installed on the computer.
When I run the cmd window, I can get a recognition from adb when I'm in recovery mode, but as soon as I run <adb reboot bootloader> the phone goes into bootloader, disconnects temporarily from the computer and reconnects.
When I go into devices on the computer I can see that the computer see's it. It recognizes it as my HTC although it shouldn't right?
When I come back to my cmd window I try to run fastboot commands with no success. <fastboot devices> gives me a blank line and its ready for the next command.
I looked around and saw that a lot of people dint have the right cables, drivers for the phone or dint restart they're computer.
I have done it all. I re-downloaded the drivers I think 10 times in vane.
Any help would be appreciated thx
OS on phone is no longer there I lost it. dont know how.
OS on computer is windows 10 64 bit
pannic514 said:
I've been trying to solve this for a while now and cant seem to get it to work.
I have adb and fastboot installed on the computer.
When I run the cmd window, I can get a recognition from adb when I'm in recovery mode, but as soon as I run <adb reboot bootloader> the phone goes into bootloader, disconnects temporarily from the computer and reconnects.
When I go into devices on the computer I can see that the computer see's it. It recognizes it as my HTC although it shouldn't right?
When I come back to my cmd window I try to run fastboot commands with no success. <fastboot devices> gives me a blank line and its ready for the next command.
I looked around and saw that a lot of people dint have the right cables, drivers for the phone or dint restart they're computer.
I have done it all. I re-downloaded the drivers I think 10 times in vane.
Any help would be appreciated thx
OS on phone is no longer there I lost it. dont know how.
OS on computer is windows 10 64 bit
Click to expand...
Click to collapse
Try it on Windows 7 or update your drivers.
http://androidxda.com/download-htc-usb-drivers
http://www.andromods.com/fix-troubleshoot/issue-fastboot-waiting-for-device-windows-81-fixed.html
Fastboot and adb don't work on Windows 10 yet. That's why I didn't upgrade from Windows 7 ?
Not had this before,
I just switched to 5.1 GPE via the conversion option.
Everything went smoothly, device works well. However now I cannot get the phone connected through adb. It says "device offline".
I have tried killing the adb server and restarting it, made sure adb debugging is on. Restarted device, laptop, tried removing and reinstalling drivers. Tried plugging into a different usb port.
As always, when I run an adb command it shows the device as offline.
I cannot get it to flash up the RSA when connecting either which I think may be the problem.
Anyone had this?
Thanks.
maritimesbob said:
Not had this before,
I just switched to 5.1 GPE via the conversion option.
Everything went smoothly, device works well. However now I cannot get the phone connected through adb. It says "device offline".
I have tried killing the adb server and restarting it, made sure adb debugging is on. Restarted device, laptop, tried removing and reinstalling drivers. Tried plugging into a different usb port.
As always, when I run an adb command it shows the device as offline.
I cannot get it to flash up the RSA when connecting either which I think may be the problem.
Anyone had this?
Thanks.
Click to expand...
Click to collapse
What is your adb version?
Code:
adb version