Database Develop

[SOLVED] Can't mound SD card from G1 to computer

I am unable to mount my SD card when it is in my G1 and connected to my computer. I used to be able to before I upgraded to Windows 7. I am using JacHero 2.7.1 with the latest USB drivers, fastboot and ADB both work. But when I connect my phone to my computer and choose to mount the card, nothing happens on my computer. In device manager, my G1 is still there under ADB Interface. However, the SD card is mounted as WPD File System Volume Driver with a little caution sign on the icon. When I view properties of the device, it says "The device cannot start. (Code 10)"
How can I get this to work? Its kinda annoying to have to turn off my phone, remove my fishbone case and go through all that just to put a picture on it.

SolemnWishing said:
I am unable to mount my SD card when it is in my G1 and connected to my computer. I used to be able to before I upgraded to Windows 7. I am using JacHero 2.7.1 with the latest USB drivers, fastboot and ADB both work. But when I connect my phone to my computer and choose to mount the card, nothing happens on my computer. In device manager, my G1 is still there under ADB Interface. However, the SD card is mounted as WPD File System Volume Driver with a little caution sign on the icon. When I view properties of the device, it says "The device cannot start. (Code 10)"
How can I get this to work? Its kinda annoying to have to turn off my phone, remove my fishbone case and go through all that just to put a picture on it.
Click to expand...
Click to collapse
You can always use adb push? Lol try uninstalling the usb storage devices and reinstalling them

well, the problem is USB Mass Storage doesn't even show up. And when I try to install newer drivers it says "Windows has concluded that your driver is up to date" and stuff like that. ADB push is a little slow for me lol

Uninstall whatever your SD Card is installed as, then restart your computer, replug in your phone and mount the SD Card and it should prompt that a new device was plugged in.

h.nocturna said:
Uninstall whatever your SD Card is installed as, then restart your computer, replug in your phone and mount the SD Card and it should prompt that a new device was plugged in.
Click to expand...
Click to collapse
Just tried that, the moment I plugged it in, my computer automatically installed the driver, so still not working.

SolemnWishing said:
Just tried that, the moment I plugged it in, my computer automatically installed the driver, so still not working.
Click to expand...
Click to collapse
Ugh, I hate that... try manually updating drivers and see if you can get it to install the Mass Storage Device drivers from a list...

I tried that, there wasn't an option for USB Mass Storage, but there was one for SD Card in the pre-installed driver list, however when I selected that one I received an error. Just a note, that Android HTC Phone USB Device is listed under disk drives with no caution signs in the icon, however I am unable to get that one to work either. Could it possibly be Windows 7..?

AHAHAHHAHA YES I FIXED IT WOOO HOOOO!
Okay, so what I did was go into the development settings and UNcheck USB debugging. The moment I did that, my computer made the "new hardware sound" and then said "driver install successful" and when I clicked on it to see the driver, the driver was "USB Mass Storage Device". Now I can mount it WOOHOO!
Thanks you guys for all the help
edit:
With USB debugging reenabled, it stops working again, so I gotta turn it off everytime I wanna mount... ah well

That sucks, I have mine permanently on cuz I use ADB so much (Also using Windows 7 here) And everything detected perfectly. Well good job on finding a workaround.

SolemnWishing said:
AHAHAHHAHA YES I FIXED IT WOOO HOOOO!
Okay, so what I did was go into the development settings and UNcheck USB debugging. The moment I did that, my computer made the "new hardware sound" and then said "driver install successful" and when I clicked on it to see the driver, the driver was "USB Mass Storage Device". Now I can mount it WOOHOO!
Thanks you guys for all the help
edit:
With USB debugging reenabled, it stops working again, so I gotta turn it off everytime I wanna mount... ah well
Click to expand...
Click to collapse
Great could u change thread title to solved? Im sure lots of people have this problem too .Also update your OP =]

alritewhadeva said:
Great could u change thread title to solved? Im sure lots of people have this problem too .Also update your OP =]
Click to expand...
Click to collapse
ahahaha sorry, buy whats an OP?

SolemnWishing said:
AHAHAHHAHA YES I FIXED IT WOOO HOOOO!
Okay, so what I did was go into the development settings and UNcheck USB debugging. The moment I did that, my computer made the "new hardware sound" and then said "driver install successful" and when I clicked on it to see the driver, the driver was "USB Mass Storage Device". Now I can mount it WOOHOO!
Thanks you guys for all the help
edit:
With USB debugging reenabled, it stops working again, so I gotta turn it off everytime I wanna mount... ah well
Click to expand...
Click to collapse
thanks mate you helped me out was having the same problem on my zte blade

Thank you so much my friend.
I had the same problem on my Desire.
I was wondering couple hours for this stupid thing.....and finally I mound my SD Card on your way.

No Go!
Windows 7 64bit for me and Galexy Prevail still no go with the WPD FileSystem Volume Driver, I can't get this suka! started and it was working before everything? why did it stop?
I hate this crap...... Ahhhhhhhhh! Im pulling my hair on this crap.... Willing to try other sugestions, I am def not reformatting to get this to work...lol...
---------- Post added at 10:06 AM ---------- Previous post was at 09:24 AM ----------
Okay because of a great guy from a microsoft website forumboard I was able to fix this with the below fix.
Thank you (Patricio16)
If still doesnt work try this:
1. My Computer -> Properties -> Advanced System Settings. This takes you into the system properties like in XP. Go into Environment variables and create a new System varable called devmgr_show_nonpresent_devices (I don't think it's case sensitive). Set this to a value of 1.
2. Go into device manager. From the view menu, choose "show hidden devices". Because of the environment variable, you now see all devices not in use.
3. Uninstall any "Universal Serial Bus controllers" not in use (greyed out). Also I uninstalled any storage volumes, storage volume shadow copies, and disk drives also not in use. You should see your offending USB device in one of these areas.
4. STILL DIDNT WORK!! Then:
4.1 Make sure your cellphone detects and see the content of the card. Then, right click MY COMPUTER - Choose Disk Mngmt- Look for the storage device in trouble (you will see that it doesnt have an assigned letter yet) - Add a letter to it - Check and you'll see the drive. (Edit)rocxylemmon- remove the WPD by uninstalling it if it does not go away on it's own then recheck for any new devices and it will change to the drive letter you assigned it too.
Actual Link To The Site - ****://social.technet.microsoft.com/Forums/en/itprovistahardware/thread/24374678-e65d-40fd-9581-62b09c8feeb8
This fixed mine so hope it fixes yours.

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

G! shows as "Unknown device" in device manager - Can't Connect!!

for the past 18 months I have been able to access my G1 via USB. I could mount it easily and ADB was set up correctly. for some reason this week, it stopped working. now when I plus it in, I get the "USB Not Recognized" error in XP, and my device no longer shows up as an adroid phoen in Device Mgr. It now says unknown device.
I have tried updating the driver with no luck.
Any ideas would be great,
Thanks

Something similar happened to me. After trying to mess around with Live Wallpapers and DroidExplorer, my phone doesn't show up. I get the "Error: Device not found".
I have the latest USB driver, but yet device manager keeps saying that it's up to date when I try to reinstall (however under Driver Details, Vista says the location of the drivers are on System32 and they're Microsoft drivers....)
Edit: after searching Google for answers, I stumbled on a Google Group and found that someone fixed their issue (similar to mine) by installing HTC Sync. I did, and voila! ADB works again.
http://www.htc.com/au/SupportViewNews.aspx?dl_id=573&news_id=169

OUTSTANDING!! That did it. Thanks a bunch, and thanks for the link!

fixed for real now
So the above didn't do it for me, here's what I did:
download and extract USBDeview
Open it up and remove the 3 or 4 entries that say "android phone"
Unlplug (if its plugged into USB) your phone and replug it in, the "found new hardware" window should pop up and be sure to install the drivers that came with the SDK.
That took care of my USB mounting situation, but I still couldn't get adb or fastboot to see my device. Turns out I had adb.exe and fastboot.exe in my WINDOWS/System32 folder as well as in the SDK/tools folder (prolly from when I updated the SDK). Having them in 2 spots seemed to cause problems so I removed them from the SDK/Tools folder. Alternatively I could have removed the other set, but I didn't want to go to my SDK folder every time to use them, this way I can access ADB from any folder on my computer.
This is all from memory so if something's not clear, lemme know. All I know is ADB and Fastboot are working now.

[Q] No adb access.....

Once i got my new nook color i rooted it with auto nooter, and im running 1.0.1, on my previous nook i rooted it and adb worked right then, now i cant get adb access, im using the same computer and everything, all thats diferent is its a new nook. I have full root access and can install apps and everything. Any help?

Seems to be a common problem. You can launch NookColorTools and fix it temporarily. Go to "Development" and then unchecked and then recheck the USB Debugging box.

Ok I've been doing that for a while and finnaly got the message that USB debugging is only for development. It works now......
Sent from my LogicPD Zoom2 using XDA App

Get ADB wireless, it works great.

I've had zero luck using usb adb, but adb wireless works great!

I was having similar issues so after many many attempts I just decided to go with adb wireless and would definitely recommend going that route if you can't get it working over usb.

Yeah, getting ADB to work requires a lot of uninstalling/reinstalling drivers and unplugging/replugging the device, it's very temperamental.

can someone link me to a link on how to use/setup adb wireless

beezy69 said:
can someone link me to a link on how to use/setup adb wireless
Click to expand...
Click to collapse
https://market.android.com/details?id=siir.es.adbWireless
it's free in the market and once you download it set up is easy. i've used it through my mac terminal as well as through ubuntu. like the posters above i had the hardest time getting adb to work via usb.

chemical1der said:
https://market.android.com/details?id=siir.es.adbWireless
it's free in the market and once you download it set up is easy. i've used it through my mac terminal as well as through ubuntu. like the posters above i had the hardest time getting adb to work via usb.
Click to expand...
Click to collapse
is there any tutorials on how to use it and what commands i need to install apps?

beezy69 said:
is there any tutorials on how to use it and what commands i need to install apps?
Click to expand...
Click to collapse
once you've installed adb on your computer type "adb" at your terminal prompt and you should list of commands there.
here's the link to Android Developer's ADB website (this also lists commands):
http://developer.android.com/guide/developing/tools/adb.html
files and installation directions can be found here:
http://developer.android.com/sdk/index.html
Good luck!

Ok so me being my dumb self forgot to install the adb drivers for the nook....... im dumb haha, but i cant get them to install, every time i uninstall the mass storage driver so i can install the proper driver it automatically re-installs it....... HELPPPPPPP

Is there any way to download this to the SD and install it from there? I've upgraded to a version of froyo, which doesn't have the market, and my command line won't work after swapping nooks.

I can't seem to get mine to work with either adbwireless or via usb.
Using USB I get this:
C:\android-sdk-windows\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
C:\android-sdk-windows\platform-tools>
Here is what I get if I try to connect using adbwireless:
C:\android-sdk-windows\platform-tools>adb connect 192.168.2.4:5555
already connected to 192.168.2.4:5555
C:\android-sdk-windows\platform-tools>adb devices
List of devices attached
192.168.2.4:5555 device
C:\android-sdk-windows\platform-tools>
But it doesn't show a serial number like all the HowTo's says it should. What am I missing?
EDIT: HALLELUJAH!!
I fixed it. Actually I didn't fix it, I just followed some instructions from another user that was having the same problem and finally figured out the very weird thing that installing the drivers did. Anyway, here is the solution from hacku:
Originally Posted by hacku View Post
Thanks for this...
EDIT 1:
I followed your instructions to a T and I still can't get ADB to see my NC. After uninstalling all instances of Nook in my device manager, unplugging it and plugging it back in, it adds all the same devices:
Under Disk Drives it lists B&N Ebook Disk USB Device (twice)
Under Portable Devices it lists MyNookColor
Under USB Controllers it lists USB Mass Storage Device
My PC is Windows 7 Ultimate 64bit. Running Nook Color 1.1.0 rooted and overclocked to 1.1Ghz. Any help will be greatly appreciated.
EDIT 2:
So I decided to pull the MicroSD card to simplify things. Uninstalled all instances of Nook from Device Manager and scanned for new hardware. This time I noticed that Windows detected it as a Nook, but then would install the drivers and it would show the same USB Mass Storage Device and the two instances of B&N Disk USB Device. I also noticed that by uninstalling the driver of the USB Mass Storage Device automatically deleted the other two instances under Disk Drives. So I updated the USB Mass Storage Device driver and this time I was able to install the drivers provided, but now it only shows up as an Android Phone > Android ADB Interface (not Composite), but I'm still not able to see it under adb devices.
Help?
EDIT 3:
GOT IT WORKING!!!
For those of you having this same problem this is what I did:
1. Right Click Android ADB Interface (it won't say Composite)
2. Select Update Update Driver Software
3. Click on Browse My Computer For Driver Software
4. Click on Let me pick from a list of device drivers on my computer
5. In the box that pops up click on USB Composite Device
6. Click Next
It now installed the USB Composite Device driver and changes your Android Phone to Android Composite ADB Device.
Open up Command Prompt and type adb kill-server then adb devices and your Nook Color will now show up.
Hope this helps some of you out.

This thing really needs to be pinned somewhere, preferably with IOMonster's first post. There's so many of us starting on this from scratch not able to get adb to see the device. har02's crosspost of hacku's post is what finally got it to work for me. there's a ton of junk out there that just doesn't make sense, and the installing the second driver on the "android interface" is a step that is completely missing from just about every post on this topic.
Aside from that, this forum is what got me buying a nook and happily learning all sorts of cool new things!

THANK you so much har02052, this marks the end of a 6 hour nook-fixing marathong....ahhhhh

[Q] Nook, ADB problems

For some reason my nook won't show up in windows 7 device manager as anything but a storage device (both the nook and sdcard). It doesn't show up under "other hardware" like all the tutorials show. I am at a loss?
Should I reset my device (unroot, wipe clean, etc)? And try again or am I missing something.
I am looking to get ad hoc working and am stuck in the mud

Depending on what ROM you're running... you may need to go into nook color tools and toggle usb debugging mode... it is a known issue in some ROMs....
You may also need to edit %userprofile$\.android\adb_usb.ini so the only line in it is:
0x2080

anyone have problems in ubuntu 10.04 can't get it :'(

I figuered it might be that I had tried some different kerenels recently. I did eventually return to stock. I have toggled debugging mode to no avail.
I will follow the other instructions you provided and if all else fails wipe her clean and try that.
Thanks.
Sent from my rooted nook color using Tapatalk

I have the same problem and am using the stock kernal. I have even tried two different computers (one with Win 7 and the other with XP) and get the same result. The first time it I tried with XP it showed "NookColor" under Other Devices with a ? mark. In just a second, it reloaded Device Manager and would never showed up again. I have tried all suggestions including the USB Debugging toggle with no positive results. By the way, I rooted using auto-nooter 3.0 for Nook Version 1.1. Everything seems to work well and I am using ADW Laucher EX. I am familiar with ADB as I used it root my Motorola Droid. In that case, I had no problems with it seeing my Droid.
Any suggestions would be helpful. I also have Ubuntu on a test computer that I may try if no solutions are found.

[email protected] said:
anyone have problems in ubuntu 10.04 can't get it :'(
Click to expand...
Click to collapse
I had the same issue in Ubuntu 10.04. My Evo would show up fine. My NookColor I could not get to show up though. No matter what I tried (I tried all the walk throughs on forums, Nookdevs.com, etc).
I finally just gave up. I've just been moving APK's from my Evo to my Nook to install them. There are many other things I'd wish to do through ADB other then install apps though so I may give it another shot sometime soon.

If it worked in some ROM versions and not in others... you need to check the device ID in windows device manager... get the PID for the device listed.... then you will need to add the device PID to the .inf file for the drivers so it will know to use the drivers that work for the "new" device (not really new.. just HWID change in some new kernels/ROMs

I had a world of trouble getting getting my computer to recognize the nook so that ADB would recognize the device. I mean HOURS of debugging.
However.. good news!... The answer that can help you is...: screw it and just download adbwireless app. All you do is run the app while connected to your home network and then on your computer run the the command "adb connect 192.168.1.xxx:5555" and you are connected and can run adb just like you were USB'd up
I hope this helps

Recommend installing the easy ADB install for Windows from the developers forum.
On Win7, sometimes you need to force the driver to use "USB Composite device" or "Android composite USB device", even after doing the easy ADB installer above.

Managed to get ADB working after Autonooker 3.0, Nook 1.1
Hi, All,
I had similar problems. I managed after a bit of fuss on my mac to get ADB up and running.
The main problem seemed to be getting USB debugging working. I went into nook color tools, from ADW launcher. I went to All Settings : Development, and saw that USB debugging was checked, but I didn't believe it was running.
So, I unchecked both Auto Mount (to simplify what the heck was going on over USB) and USB debugging, and hit back, to save the settings. Then I went back into debugging, and re-checked USB debugging.
Then, I made sure that ~/.android/adb_usb.ini contained the line:
0x2080
I killed the adb server and restarted it, and voila, ADB.
Hope this helps some folks.
Dave

I am in the same boat, adb works fine on my other android device, but won't see my nook for anything.
I have tried every permutation I have seen of the rules file, still nothing.