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 accidently flashed SRE 1.3.1c over the captivate hybrid ROM and after gettin the error message every boot i deleted all user data it now only boots to a black screen and i cant get in to clock work recovery because i left the update.zip in the root of my internal sd card so it keeps flashing SRE when i hit reinstall packages is there anyway i can save my captivate
so know i am stuck because the only OS i can currently run is a ubuntu live cd
anyone know a way?
if the phone is still booting at all (passing AT&T screen) you should be able to use adb. you can force and adb reboot recovery or download and use adb push to move the clockwork update.zip back and restore your nandroid. or download to restore to a stock JF6
if you aren't booting at all though, then the only way to restore is to go back to a stock build using Odin. I know you say you only have an Ubuntu Live CD, but that just won't cut it. To use Odin, unfortunately, you need Windows (though it will work inside virtualbox).
its booting past the at&t screen but im having some trouble with adb
rsmith675 said:
its booting past the at&t screen but im having some trouble with adb
Click to expand...
Click to collapse
sounds like Odin will be your easiest method to fix this. boot into download mode using the 3 button method and find a windows based computer
im using regular installed ubuntu now (no more cd) ive got odin running in wine but its not being recognized in either download or recovery
Last time I was on the Linux scene, Wine had some major problems with USB. Windows is your best bet. (You can find a copy somewhere of xp for pretty cheap these days)
One thing I would suggest, based on my past experience with jailbreaking iPhone:
When trying to connect to any device in recovery/download/whatever-non-normal mode, try to connect to OS directly. Do not use tools like vmware. These sometimes have difficulty in recognizing devices in virtual machines/modes.
My iPhone wasn't recognized even in XP virtual machine on top of Windows 7. Maybe the same thing applies here too.
Edit:
Keep following the thread below. One more user is trying to achieve what u r trying to do.
Code:
http://forum.xda-developers.com/showthread.php?t=922690
I am sorry for making a new thread for this reason, but I have tried for about 6 hours of reading forums and trying different drivers, countless reboots, etc and cannot figure out adb or fastboot for the life of me, so please help
I am running Windows 7 64bit, have download and unzipped the android-sdk_r10-windows.zip and have updated the platform-tools and usb drivers revision 4. I plugged my phone in and it immediately found the drivers without me touching anything, and I tried "adb devices" from an elevated cmd prompt and got nothing in return, so I went into device manager and updated the driver software to Google's usb drivers from the SDK and tried once again, but no luck. I then downloaded USBDeview and uninstalled all references to HTC or Android device (while the G1 was unplugged). Plugged G1 back in after un-installation of drivers and it recognized it right away, again no need for drivers. tried "adb devices" and nothing (yes, the phone is fully booted into CM6.1 stable from Cyanogen with a 1.33.2005 HSPL and compatible radio, along with Amon_RA 1.7.0 recovery).
I read in a thread that Hayakuro's SPL has its own usb drivers on http://code.google.com/p/sapphire-port-dream/ and I downloaded them and went to device manager and updated the drivers to this version...still no adb luck (always running from cmd "run as administrator"). Then I looked into USBDeview to see the properties of the installed drivers...they never changed from Default micrososft windows drivers, where the HTC drivers for the G1 should have had obvious different properties than the default MS drivers.
So I am just plain stuck and have no idea what to do...I've reflashed the HSPL and CM6.1 using AmonRa recovery, still don't know.
I am trying to eventually use fastboot in order to put ezterry's 2708+ kernel and ezterry's gingerbread port on here, but I cannot setup adb or fastboot. As of last night @ 2:30am (CST) I had adb working, but not fastboot (while in Recovery mode) and now while in a full boot, adb and fastboot refuse to work.
I have read through http://forum.xda-developers.com/showthread.php?t=532719 and followed all directions (except for using the newest android sdk .zip package
I'm also wondering about using HTC's specific "fastboot.exe" on their developers page or the "fastboot.exe" included in the SDK?
Hopefully I have explained everything that you would need to help me solve this unrelenting PITA (Pain in the A$$)
This is why XP beats the **** out of Vista & Windows 7.
Have you followed this?
http://developer.android.com/sdk/win-usb.html#Win7
And if yes then I have to ask what is your current spl and radio? Had trouble helping someone last night get it sorted on Windows 7 also, the perfect example of how stupid Microsoft think their users are that they now better than the users on how they want their machines setup.
What a cup of coffee can do for the brain ;-)
shadowch31 said:
This is why XP beats the **** out of Vista & Windows 7......
Click to expand...
Click to collapse
I can see how XP is better for a development platform since it doesn't have all the bells and whistles I....never use haha
And I just got it to work!!!! I used Ohsaka's superwipe (found here: http://forum.xda-developers.com/showthread.php?t=834812) re-flashed the radio 2.22.19.26I.zip, then the spl-signed.zip (hboot 1.33.2005) from http://code.google.com/p/sapphire-port-dream/ and then Cyanogen's CM6.1 for Dream and performed a full boot and plugged in the G1 and it recognized it immediately and installed drivers for it ran an elevated command prompt and "adb devices" (while in full boot) and "fastboot devices" (while in fastboot) works! I think the reason was I had never completely wiped my phone with the aforementioned SuperWipe v2 and/or maybe the updated radio 2.22.23.02 was messing up some low-level functionality of the spl
Mods feel free to edit/delete this, but I feel this would be a good addition into the adb/fastboot guide/sticky on the front page, because this specific situation called for a complete wipe of the phone and flashing an older radio in order for fastboot to work
I try to install newest custom rom supernova 4 infinity and message is above:
Formatting SYSTEM:....
Formatting CACHE:....
Formatting DATADATA:....
Formatting DATA:....
Deleting files...
Copying files...
e:failure at line 17 :
copy_dir PACKAGE:system SYSTEM:
installation aborted
now my phone is bricked (Expensive stone) because my usb debugging is off and the odin do not recornize my captivate in downloading mode!!
What i can do now? How i fix debugging ON that i can flash my phone again to stock etc..
USB debugging has nothing to do with it.
you need to get ODIN to recognize your phone. sounds like driver problems
I install odin drivers for captivate 32bit and my windows 7 don't recognize my phone, also odin do not recognize.. i test Downloading Mode.. Is usb debugging off or on with Downloading Mode?
also sdk manager installed with google samsung drivers..
Anybody else that having this recognize issues with windows 7? what to do that recognize are working
In CWM, check to see if you have the option to Root. If you do, apply Root and try flashing the rom again.
I had similar issues with 2 roms with similar errors and I had to apply root in CWM and re-flash and it went trough fine.
energy83 said:
I install odin drivers for captivate 32bit and my windows 7 don't recognize my phone, also odin do not recognize.. i test Downloading Mode.. Is usb debugging off or on with Downloading Mode?
also sdk manager installed with google samsung drivers..
Anybody else that having this recognize issues with windows 7? what to do that recognize are working
Click to expand...
Click to collapse
USB DEBUGGING HAS NOTHING TO DO WITH DOWNLOAD MODE!
usb debugging only has an effect if you are ALREADY booted or currently BOOTING beyond the splash screen. it doesnt matter for download mode...period.
Elisha said:
In CWM, check to see if you have the option to Root. If you do, apply Root and try flashing the rom again.
I had similar issues with 2 roms with similar errors and I had to apply root in CWM and re-flash and it went trough fine.
Click to expand...
Click to collapse
this is one of the most ridiculous things i have read today. root also only applies to the OS....from within recovery or download mode, you arent in the OS...so root doesnt mean SH** within recovery
Pirateghost said:
this is one of the most ridiculous things i have read today. root also only applies to the OS....from within recovery or download mode, you arent in the OS...so root doesnt mean SH** within recovery
Click to expand...
Click to collapse
Don't be a dip****,. I was stating my experience.
From stock 2.1 I could not install Continuum v4 in recovery and got a similar error for E:/
I had to flash a SpeedMod based kernel in recovery and root first before the rom would go all the way trough to flash properly!
It only happens to certain roms...other roms can just flash in recovery from stock no problem without rooting first.
Elisha said:
Don't be a dip****,. I was stating my experience.
From stock 2.1 I could not install Continuum v4 in recovery and got a similar error for E:/
I had to flash a SpeedMod based kernel in recovery and root first before the rom would go all the way trough to flash properly!
It only happens to certain roms...other roms can just flash in recovery from stock no problem without rooting first.
Click to expand...
Click to collapse
This statement thus proves you have no idea what you are talking about. When you understand how a Rom flash works, then you can come back to the discussion. In the meantime, try reading an update-script or 2
Sent from my HTC Vision using Tapatalk
energy83 said:
I install odin drivers for captivate 32bit and my windows 7 don't recognize my phone, also odin do not recognize.. i test Downloading Mode.. Is usb debugging off or on with Downloading Mode?
also sdk manager installed with google samsung drivers..
Anybody else that having this recognize issues with windows 7? what to do that recognize are working
Click to expand...
Click to collapse
You said that you installed the 32 bit drivers for windows 7? Unless you are running a netbook or installed Win 7 on an older computer you probably need the 64 bit drivers. Most newer laptops these days are 64 bit OS. You can check by right clicking on "my computer" and selecting properties. It will say whether you are running 32 or 64 bit.
I also recommend downloading kies (samsung sync software). You can get it off the Samsung website under downloads. Once it's installed and opened, under tools, you can select install drivers. Go through that process and then close kies (make sure it isn't still running in your system tray), open odin and try to connect in download mode again. Don't forget basic troubleshooting like trying a different USB port if the first one doesn't work the first time.......
ok, so my phone is screwed.
Been trying touse this thread to recover it - http://forum.xda-developers.com/show....php?t=2325853
I have no SD Card, I can not mount SD Card in Recovery.
I have from what I can tell installed the Android SDK and when doing 'adb devices' I get 'error device not found'.
I have uninstalled and reinstalled HTC drivers and sync, does not recognise my phone. Device manager shows my One but can not find any drivers for it.
I have tried the All In One Tool to sideload, does not work, does not reboot to bootloader etc due to drivers not working.
Basically my phone is dead as, what can I do? Take it to HTC, how much would it cost to fix?
Cheers
EDIT: If i reboot system from Recovery it tells me it does not have root, do i want to root it? I say yes and it reboots to splash screen, nothing else
What operating system are you running?
If you're using Windows 8 search for the thread with the windows 8 drivers.
I accidently formatted my SD card while I had no rom installed. It took a while but eventually ADB picked it up and I was able to push the rom to my device using ADB push (I was also getting the "No devices found" message). This was before I found the windows 8 driver thread, it just randomly started working after many resets of both my phone and computer.
What recovery are you using? Do you happen to have a flash drive and a usb otg cable? This is an other option.
Sent from my HTC One using Tapatalk 4 Beta
Saenzscene said:
What recovery are you using? Do you happen to have a flash drive and a usb otg cable? This is an other option.
Sent from my HTC One using Tapatalk 4 Beta
Click to expand...
Click to collapse
that is easy dont panic
1- if the drivers is not installed properly you cant do anything from PC and send it to the device
if you are using Windows 8.1 there is NO drivers for it,
if its Windows 8 there is NO official driver yet but you can install Windows 7 drivers
if its Windows 7 or earlier make sure its installed correctly if you dont know reply to my comment i will tell you anything you want
2- it happned to me too No Root and NO Rom installed, i simply copied the ROM to a USB Stick and using a USB OTG cable ($1) i plugged the cable to the phone and mounted the cable and then installing it from there,
tell me more about what you have and i will help you
Spent a few hours last night working on this with the help of Matt from here
I have CWM Touch (latest) and he was able to fix the driver issue, and we got sideloading working.
Will push the rom to phone, install, start roms splash screen but go no further. Still no SD Card or missing the mount points to show SD Card.
Attempted to S-Off, failed, unsure if CID 11111111 was successful. (Not CID11111111, was HTC_039 now VODAP21 or similar)
I has told/read an article that if you flash a differnt base (eg ICS to JB) that it will replace a script that handles/writes the mount points..
That worth a try but I believe all roms are JB. Any idea of any ICS roms for the One??
I can not find a RUU for 1.29.980.2 to try, only Nandroid Backups that I can not use as no SD..
EDIT: what does a flashing red led mean too? Cheers