Database Develop

ADB access broken....beyond frustrated

This about as short as I could make it:
I haven't tried to use ADB with my G1 for about a month, so I'm not exactly sure when the problem started, but it's become a royal headache now. For whatever reason when I launched ADB shell today, I got an error saying 'device not found'. The first thing I did was check device manager where I noticed the phone showed as a 'USB composite device' with a yellow exclamation mark over it. I thought to myself "drivers." So I tried pointing it to the driver in the Android SDK folder. That just popped an error saying that Windows couldn't find a better driver match than the one I was already using.
From there I got the googling and came across this insanely long Google Groups thread. Following the advice listed, I started pulling some USB .sys files. I tried using an older copy of the USB driver from a previous SDK. I tried using Haruyko's modified USB driver. None would install.
Same error.
Reading down some more I saw that some people had success with with usinfg HTC Sync. It was worth a shot, right? Well it certainly made things different, but doesn't resolve the issue. Now in device manager I have an 'HTC Remote NDIS' listing under Network Connections. The old 'USB Composite Device' item is now gone. But still, I can't use ADB. "Device not found."
It's driving me nuts.
At this point I figured that it'd be best to try this on a different PC. Maybe my primary one is wonking out. These things happen. Well, that hope was quickly crushed when I discovered that NOT EVEN on a VANILLA XP SP3 setup, will Windows detect the G1. I downloaded a fresh copy of the SDK, plugged it in, pointed it to the USB driver....and nothing. Same error as PC number one:
"Windows can't find a better version of the driver than you're currently using."
Tried switching the USB cable. Same thing.
Back to PC number one, I removed all HTC software from 'Add/Remove Programs, then ran USBDeview. There, I removed the HTC NDIS device, unplugged the G1, and plugged it back in.
The HTC NDIS Remote device returned. **** my life.
SO.....before I throw this phone into traffic, does anyone have any clue as to what's going on here? All I want to be able to do is regain ADB access to my phone. I don't care about USB tethering (and toggling that option does nothing btw) or none of that. Just looking to regain ADB access. The only thing that's changed since the last time I used ADB is the version of Cyanogen's mod. I'm currently using v4.2.3.1. Maybe this broke shell access?
Thoughts?
**EDIT***
-Toggling USB debugging does nothing either.
-Ditto that for Fastboot

device not found has to do with the phone....make sure your cable is not messed up.

B-man007 said:
device not found has to do with the phone....make sure your cable is not messed up.
Click to expand...
Click to collapse
Tried switching the USB cable. Same thing.
Click to expand...
Click to collapse
Tried that already.

the.snks said:
Tried that already.
Click to expand...
Click to collapse
is the phones usb port ok? can you transfer files over it? if your about to throw the phone away....at least try flashing the RC29 image again

B-man007 said:
is the phones usb port ok? can you transfer files over it? if your about to throw the phone away....at least try flashing the RC29 image again
Click to expand...
Click to collapse
As far as I know the USB port is ok. It charges fine. And to update everyone on where I am, I tried the following today:
-Removed all HTC software (Sync and Drivers).
-Used USBDeview to remove all instances of HTC, and Android devices.
-Tried downgrading my test machine (PC #2) to Service Pack 2.
-Tried a third USB cable.
And I'm still getting the same problem. So there's no doubt in my mind that it has to be the phone. Like I said, the only thing I've done lately is update the version of Cyanogen's ROM.
I know it definitely worked before I updated to v4.2.3.1. Also I noticed that I am no longer able to mount the sdcard as storage in Windows. I do not get a prompt on the G1 asking if I wish to mount it. However, the USB debugging notice still pops up (weird).
....and here I'm stuck once again.

Have you tried actually uninstalling the usb devices in device manager?
I was having a similar problem, I just unistalled all the usb instances in the device manager, and when I rebooted my computer, everything seemed to work fine.

rp1783 said:
Have you tried actually uninstalling the usb devices in device manager?
I was having a similar problem, I just unistalled all the usb instances in the device manager, and when I rebooted my computer, everything seemed to work fine.
Click to expand...
Click to collapse
Yes. Multiple times in fact. It can't be the computer if the same issue is happening across two different PC's, with three different USB cables.

At first I thought this was a definite driver issue with xp, I've had similar problems in the past that just won't go away.. xp is a c*nt when it gets a driver stuck in its head that it just doesn't want to part with... but if its persisting across several machines it could well be the phone..
Have you tried adb with the phone in recovery? Boot into recovery and leave it about 30 seconds, then plug in the usb and try to get an adb shell.. this should rule out any rom config issues

goldenarmZ said:
At first I thought this was a definite driver issue with xp, I've had similar problems in the past that just won't go away.. xp is a c*nt when it gets a driver stick in its head that it just doesn't want to part with... but if its persisting across several machines it could well be the phone..
Have you tried adb with the phone in recovery? Boot into recovery and leave it about 30 seconds, then plug in the usb and try to get an adb shell.. this should rule out any rom config issues
Click to expand...
Click to collapse
PROGRESS! I booted into recovery mode and plugged the G1 into the computer. I got the 'new hardware' prompt and was asked to install the driver. I did so using the one from the SDK. Now I have ADB access, and Windows tried to mount the sdcard but that failed. I'm guessing because there's no way for me to 'ok' that in the recovery console.
So what does this tell us? I'm not sure if I understand what's wrong here.
(Sidenote: Man I'm so tempted to try to install the new Google Maps now....)

the.snks said:
So what does this tell us? I'm not sure if I understand what's wrong here.
Click to expand...
Click to collapse
It tells us that something's cocked up with the usb support in your rom, but the phone itself is fine. wipe/reflash and you should be good to go.
There is a command you can type to mount the sd for windows when you're in recovery.. just type this in the console:
Code:
echo /dev/block/mmcblk0 > /sys/devices/platform/usb_mass_storage/lun0/file

goldenarmZ said:
It tells us that something's cocked up with the usb support in your rom, but the phone itself is fine. wipe/reflash and you should be good to go.
There is a command you can type to mount the sd as storage when you're in recovery.. just type this in the console:
Code:
echo /dev/block/mmcblk0 > /sys/devices/platform/usb_mass_storage/lun0/file
Click to expand...
Click to collapse
Ah....that blows but you do what you gotta. I'll try wiping and report back in case this thread helps anyone else.
Thanks man.

Alright, here's what I did to get working again:
Doing a wipe did NOT resolve the issue. However, updating to v4.2.4 did (remember I was using v4.2.3.1 originally). For clarity, I wiped both before and after the update. And I had to use a sdcard reader to get v4.2.4 onto the phone. I can now ADB and mount the sdcard in Windows without issue. I'm not sure if this was a one off, or possibly a bug in v4.2.3.
Somebody may want to bounce that Cyanogen.
B-man007 and goldenarmZ, the help was much appreciated.

This probably is related to USB tethering Cyan put in his rom.
Also for future reference, if you want to mount your SD card in recovery and you have Cyan 1.3 or greater or RA recovery, you can just type
ums_enable
to mount and
ums_disable
to dismount
saves you from typing that hideously long line lol

USB Brick? (Usb mas storage not working at all)

I have tried reflashing cyanogenmod two times, and tried both amon ra, clockwork and psfreedom recovery. Neither manages to make my Dream look like a mass stragedevic to any computer, and the PSFreedom version doesn't manage to do its thing either.
So something about the usb on my phone seems to be borked. Adb and fastboot works lik it shoud, and it charges, but it won't act as a mass storage or jailbreak device what so ever, and it do seem to be rom independent. Any ideas?

These instructions are for Windows 7:
First, plug in your phone with the USB cable. Try going to the Device Manager on your computer. Find your device (if you can), and right click > Properties. Click the "Driver" tab and then click "Update driver..." Now click "Browse my computer for driver software", then click "Let me pick from a list of device drivers on my computer", then finally click "USB Mass Storage Device".
Then it shall install the driver. Go back Computer and see if it shows up under the Device and Removable Storage section.

naguz said:
I have tried reflashing cyanogenmod two times, and tried both amon ra, clockwork and psfreedom recovery. Neither manages to make my Dream look like a mass stragedevic to any computer, and the PSFreedom version doesn't manage to do its thing either.
So something about the usb on my phone seems to be borked. Adb and fastboot works lik it shoud, and it charges, but it won't act as a mass storage or jailbreak device what so ever, and it do seem to be rom independent. Any ideas?
Click to expand...
Click to collapse
First, do the usb icons appear at the top of the screen when you plug it in to the computer? There should be a icon that you can select to turn on usb storage. If you have that but it doesn't recognize it, I need to know more about your pc.
If there is no usb icon, replace the usb cable and try again. Also check the port on your phone and make sure there's no corrosion (green stuff)
Sent from my T-Mobile G1 using XDA App

Sleeps17: I'm not that dumb, luckilly, but thanks anyway.
It is solved now, after running a comlete wipe script, erasing everything from fastboot, and then reflashing radio, hboot and recovery from fastboot., I'm still a bit stumped as to what could have caused this. The USB icon did appear, and I could choose to mount USB storage, but I would just get errors in dmesg (running linux) onj my computer when i did.
I did try to flash a home-baked recovery image that there was something wrong with, along with a bunch of other recovery images. Guess something must have screwd something up.

USB Mount Problem after fully rooted.

I fully rooted my NC and installed a number of apps that work but now my NC wount mount to my computer as separate flash drives. How can i fix this problem? Did i do something wrong? Ill appreciate the help.

Funny, I just realized this happened on my NookColor as well - just got to the bottom of it though.
Somehow, my Windows box was recognizing the Android Composite ADB device twice, and this was somehow nuking the usb-storage mode. The fix was simple:
Make sure adb shell isn't running
Go into device manager, and uninstall both instances of "Android Composite ADB Interface" - I deleted the device drivers to be sure (Windows 7 option)
Unplug NookColor from USB
Plug it back in after a few seconds. Let Device manager do its thing. For me, it fails and gives me the 'Drivers not installed' caution symbol next to the "Nook" entry in the Device manager.
Rightclick on the Nook entry in Device Manager, then select 'update drivers.' Point it back at the original USB drivers that you used while rooting when prompted.
Wait for the system to do its thing, installing all the drivers - takes a good minute or so. Drives appear in your Explorer
(I had to unplug and replug before the computer would actually let me access CONTENT on the Nook and the SDcard - your experience may vary.)

Or you could just use adb to push/pull files.

You could - but I find it easier when my media directory (for instance) is just mounted as part of explorer.

Mine does the same thing. Tried your solution and it still don't work?

Plumbergeek -- I have found that sometimes the last installed APK (application) causes this fuss. Uninstall the last thing you added, reboot and try again. Sometimes I have to go back several applications to find the culprit. Once the offending APK is identified I then try to find an alternative application to install.
If you don't know how to uninstall applications, search the threads ... the answers are here. You can also install an application called Quick Uninstall. This app, though, usually will not delete/uninstall system applications.
Hope this helps!

indeana said:
Plumbergeek -- I have found that sometimes the last installed APK (application) causes this fuss. Uninstall the last thing you added, reboot and try again. Sometimes I have to go back several applications to find the culprit. Once the offending APK is identified I then try to find an alternative application to install.
If you don't know how to uninstall applications, search the threads ... the answers are here. You can also install an application called Quick Uninstall. This app, though, usually will not delete/uninstall system applications.
Hope this helps!
Click to expand...
Click to collapse
Well, the last one was Auto Config Script so I'll just wipe it and start over.

I have the same problem and can't figure out how to fix this
Both drives are listed in Device manager as B&N Ebook USB Disk storage
but the won't mount in windows.
When connected to PC that wasn't use to root it driver installation will fail
and there is Unknow device listed in Device manager (Nook) and two B&N USB Drives
but they will not mount as well.
Did anyone found what causes this ?
Thanks

Never mind, got it,
you have to push the n button to get it in to USB mode.

lifeisfun said:
Never mind, got it,
you have to push the n button to get it in to USB mode.
Click to expand...
Click to collapse
That's strange... i've never heard of anyone having to do that before...
Anyone else need to do this to mount?

I've always had to unlock mine to get it to mount in Windows. I just thought that was normal... is it not?
Sent from my Nooted friend...

I was going crazy unable to mount the storage and this did it for me
I have no-lock installed so unlocking wasn't the problem for me.

This didn't help. I can't even find those in Device manager

I'm also stuck with this problem. I am on Linux and can see two drives listed as B&N Ebook Disk, with all the other properties "unknown". I can neither open the drives nor connect to them with adb. It says that there is no device connected when I try to connect with adb.
This problem only started after installing Honeycomb. I was able to connect to the device through USB just fine when I was on a normal-but-nooted os.

Drive letters appear in explorer, but still can't write to them
Hi, I have a variation on the problem... My ADB install is confirmed (via cmd line) and I have two new drive letters appear (I guess it's one for the nook's internal memory, the other for the micro SD card). However, when I try clicking on either letter, Windows pops up an error message saying "please insert card". If it helps, my device list ID's the nook as a "composite USB device", not as a "nook"... Any suggestions? Thanks in advance!

MityaCat said:
Hi, I have a variation on the problem... My ADB install is confirmed (via cmd line) and I have two new drive letters appear (I guess it's one for the nook's internal memory, the other for the micro SD card). However, when I try clicking on either letter, Windows pops up an error message saying "please insert card". If it helps, my device list ID's the nook as a "composite USB device", not as a "nook"... Any suggestions? Thanks in advance!
Click to expand...
Click to collapse
Same issue. This is killing me.

[Q] Phone won't mount as disc drive, Win 7.

I'm using dReWs Ginger Faux ICS Rom (first rom in my sig) and its been mounting fine until a few days ago. When they're both connected by the usb cable, i get the notification if i want to copy files to/from the pc, so i click that and i get to the option to turn on the mass storage thing, so i press okay to that and at first it's a green android, then when it's done, its orange. The thing is, that when it claims to be mounted as a disc drive, i check my computer and it's not showing up. I checked the devices and printers menu and it shows up as android phone, so i tryed to update the driver for it but apparently it is already. I also have "HTC BMP USB Driver" installed as well as "HTC Driver Installer". I had them installed since i was using htc sync but i'm not anymore. Should i uninstall them? Lemme know if you can help, thanks.

If you need more info, just let me know...
Edit- sigh...
Can someone help me? Or should i go to the Windows 7 forum instead?

Cant write to storage via MTP (Or any other mode) from Windows 10 to OP3T

--- SOLVED see first post second page! ---
Hello XDA,
I am only able to read data on the phone when connected via USB on windows. On the phone itself I can change whatever I want ( Via ES-explorer for example) But in windows file explorer I can't. It will not tell me that I do not have proper writing rights, but instead just decides to freeze for 10 minutes everytime I try to make a file change, to eventually give me a beautiful
"windows explorer is not responding" pop-up
What I have tried :
-Rebooting,
-Reinstalling USB drivers,
-Switching USB debugging on and off,
-Reinstalling root,
-Installing the newest Oxygen OS update from February,
-used different cables (also an old micro USB with adapter) And nothing works.
This sucks because I was just trying to change my photography workflow from being Desktop based to being Android based..
Any suggestions ?
Greetings,
Thijs
www.instagram.com/thi_js
Edits: Clarify issue

i have the same problem be great to find a solution

Did you maybe noticed when this problem occurs to you? I know that one months ago it just did work. Should I reinstall Windows completely?

I've been talking to a few people and it's happening to them to on Windows 10 I think it's just a bug from a recent update try a roll back

lorfo123 said:
I've been talking to a few people and it's happening to them to on Windows 10 I think it's just a bug from a recent update try a roll back
Click to expand...
Click to collapse
How should one file a bug-report for windows 10 then, this can't be something that shouldn't keep unnoticed by them.
Did rolling back fix something for you, and how did you do so?

I've checked another Windows 10 computer which hasn't been updated and it recognises my one plus 3T so if you Google / YouTube windows 10 roll back it should work

Hmm this does suck. This means I cant be up to date on windows for now. Anybody have different suggestions?

1asbak1 said:
Hmm this does suck. This means I cant be up to date on windows for now. Anybody have different suggestions?
Click to expand...
Click to collapse
The only other thing I could suggest is using a virtual machine to run win 7

Did you try back usb ports?. My pc with windows 10 fails with the front ports.

Solution
Backup all the data in your internal memory and try the 'format data' option from twrp to wipe your internal storage. It could solve your problem, as it did in my case.

New solution, just done works!
Plug in your phone and on the computer go to device manager (have phone in MTP mode)
you'll find the phone as a unknowen device
right click on this select "update driver software..."
a window will pop up select "browse my computer for driver softaware"
then on the next bit select "let me pick from a list of device drivers on my comupter"
then you will have a box with "MTP Device" and "MTP USB device"
select "MTP USB device" hit next and it should work 100%

ayush2901 said:
Backup all the data in your internal memory and try the 'format data' option from twrp to wipe your internal storage. It could solve your problem, as it did in my case.
Click to expand...
Click to collapse
Which version of TWRP are you running? The thing is that If I afterward can't restore the data via USB haha, then the whole point of backing it up seems invalid

lorfo123 said:
New solution, just done works!
Plug in your phone and on the computer go to device manager (have phone in MTP mode)
you'll find the phone as a unknowen device
right click on this select "update driver software..."
a window will pop up select "browse my computer for driver softaware"
then on the next bit select "let me pick from a list of device drivers on my comupter"
then you will have a box with "MTP Device" and "MTP USB device"
select "MTP USB device" hit next and it should work 100%
Click to expand...
Click to collapse
This actually worked. Wauw.
Had to reboot a view times in order to get it in effect, nonetheless, THANKS let the creativity start again

Really,My A** is burnt while my phone showing messages to update,,, Fiunally donw..Thanks a lot...!!

super it works

This solution did not work for me. I am using W7 and OOS 5.0.3 rooted. Tried updating MTP drivers in W7, the phone shows up but no data shows in the drive. Still looking for a solution. Can someone please post W7 drivers that work for them? Thank you.

picollo7 said:
This solution did not work for me. I am using W7 and OOS 5.0.3 rooted. Tried updating MTP drivers in W7, the phone shows up but no data shows in the drive. Still looking for a solution. Can someone please post W7 drivers that work for them? Thank you.
Click to expand...
Click to collapse
When you connect the phone to pc do you get a notification on your phone with the USB options?

DirkGently said:
When you connect the phone to pc do you get a notification on your phone with the USB options?
Click to expand...
Click to collapse
yes I can select charge, mtp, ptp, or midi
in device manager sometimes the phone shows up with error 10, device cannot start
tried many different driver versions in updating driver

picollo7 said:
yes I can select charge, mtp, ptp, or midi
in device manager sometimes the phone shows up with error 10, device cannot start
tried many different driver versions in updating driver
Click to expand...
Click to collapse
I doubt there's much we can suggest that you haven't already tried. Try another cable/USB Port/uninstall device from Device Manager and let Windows find the driver. Hell, you probably did all that already.

DirkGently said:
I doubt there's much we can suggest that you haven't already tried. Try another cable/USB Port/uninstall device from Device Manager and let Windows find the driver. Hell, you probably did all that already.
Click to expand...
Click to collapse
Haha, yeah. Does anyone have links to the drivers that work for them?