Database Users

cant access usb storage

When I plug it into my PC, the phone starts charging but there is no option to mount the USB storage...
any ideas?

waylman said:
When I plug it into my PC, the phone starts charging but there is no option to mount the USB storage...
any ideas?
Click to expand...
Click to collapse
THANK YOU!!! I've been waiting for someone else to have the same problem!!! I'm relieved it's not just mine. I'm assuming you did a manual install also? Is yours rooted? One person suggested ClockworkMod but I'm a little nervous about rooting. I've been doing the manual installs but that's as for as I wanna go. I can't stand the idea of bricking my phone.

My phone is new out of the box!
I found that on two Windows XP machines USB storage doesn't work. I then plugged it into a Win7 box and it worked perfectly. I also used a different cable with the Win7. Try a different cable and try Win7.

waylman said:
My phone is new out of the box!
I found that on two Windows XP machines USB storage doesn't work. I then plugged it into a Win7 box and it worked perfectly. I also used a different cable with the Win7. Try a different cable and try Win7.
Click to expand...
Click to collapse
I have Windows XP on my work PC and Windows 7 Premium 64 on my home notebook and the USB worked fine on 2.3.3. Every since I did the manual install of 2.3.4 the USB functionality is gone. I'm thinking maybe the ROM is used wasn't incomplete. It's beginning to look like the only way to fix this is to root my phone

FWIW I did the manual update (full rom) and USB storage works fine on my Windows 7 Ultimate x64 box.

Haadkoe said:
FWIW I did the manual update (full rom) and USB storage works fine on my Windows 7 Ultimate x64 box.
Click to expand...
Click to collapse
Yeah, I'm thinking maybe the one I installed wasn't the full ROM. As soon as I see people saying it works great I go ahead and use it. Do you know of any possible fixes without rooting?

No first hand experience, but would it be possible to download the full rom and manually flash it again?
Sent from my Nexus S using XDA App

Haadkoe said:
No first hand experience, but would it be possible to download the full rom and manually flash it again?
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Trying to figure that out. I've been told try ClockworkMod and go back to 2.3 but I'm trying to do it without rooting.

Try a different USB port
If the update was incomplete, the update would have failed the signature check. The first time I connected my Nexus S after manually patching to 2.3.4, Windows 7 Professional X64 did not detect it when connected. I unplugged it and used a different USB port and it worked. I then tried the original port and it also worked. I would try a different USB port and a scan in Device Manager before changing the ROM.

SpookyTunes said:
If the update was incomplete, the update would have failed the signature check. The first time I connected my Nexus S after manually patching to 2.3.4, Windows 7 Professional X64 did not detect it when connected. I unplugged it and used a different USB port and it worked. I then tried the original port and it also worked. I would try a different USB port and a scan in Device Manager before changing the ROM.
Click to expand...
Click to collapse
I also have Windows 7 Prof. 64 bit, but switching to different ports didn't work. It won't install the drivers. What else could that mean if it isn't the ROM?

I had this problem immediately after flashing CWM.
I booted into the ROM, then, while the USB was plugged in, powered off the device, and turned it back on. It then seems to work everytime I turn on the device, as long as I don't boot into recovery.

Me too
.

I had a the same problem with my SGS.
The trick for me did: disable usb-legacy-support in your motherboard-bios.

Have you tried re-installing USB driver from the latest android SDK?

Kind of strange, it was working great yesterday and today couldn't connect. Right clicked on android_winusb.inf and selected install and it started working again. Not sure what could have changed from one day to the next. But at least I know what to do when it happens again.

suksit said:
Have you tried re-installing USB driver from the latest android SDK?
Click to expand...
Click to collapse
Never tried that. Doesn't that involve rooting or unlocking the bootloader? Both of those wipe the USB storage.

derekwilkinson said:
I had this problem immediately after flashing CWM.
I booted into the ROM, then, while the USB was plugged in, powered off the device, and turned it back on. It then seems to work everytime I turn on the device, as long as I don't boot into recovery.
Click to expand...
Click to collapse
Don't have a custom ROM. All I did was manual bootload 2.3.4 on stock Android. The weird thing is when it's plugged in(charging only) and I turn it off, it starts to power down and then freeze. The screen doesn't go black until I pull it out. Then when I plug it back in it automatically powers back on. Basically, I can't seem to plug it in while it's powered off.

I have no idea why but my suddenly works again. Im happy but confused

You shouldn't need any drivers at all for windows XP vista 7 ect. Mounting your SD card, using flash drives... all use the same USB mass storage divice driver built into windows.
Sent from my Nexus S using XDA App

suksit said:
Have you tried re-installing USB driver from the latest android SDK?
Click to expand...
Click to collapse
Yes, I just tried this. It still doesn't seem to work. It keeps saying my drivers are up to date but it's still not connecting to my USB storage.

Semi-Bricked....can you help?

Hi, been lurking around here for a good while now....fantastic website website and I've learned so much but now I have an issue.
For what ever reason my nexus 7 will not boot, I can get into fastboot and have been following the guides to do a full factory restore through fastboot. Everything goes fine until is comes to "Sending System" then just.....stops. I have used the nexus toolkit and also the official sdk drivers and fastboot contained there. I only have an old laptop as my main pc for some reason does not recognise the nexus.
I have tried alternative USB cable too.
Does anyone have any other advice.
Also the device is complete stock no custom rom has been installed so no custom recovery available.
I really appreciate any help.
Cheers!

Okay well ive managed to get it back alive!
used a new laptop and usb cable and it all seems to be fine now!
Now back to my original issue...windows 8 is pissing me around and wont recognise the bloody thing!
Any ideas?

Try a search, shouldn't be hard to find what others have done with Windows 8 difficulties...

singlemanriot said:
Okay well ive managed to get it back alive!
used a new laptop and usb cable and it all seems to be fine now!
Now back to my original issue...windows 8 is pissing me around and wont recognise the bloody thing!
Any ideas?
Click to expand...
Click to collapse
Go to Device Manager, show hidden devices and uninstall any Android or ADB related devices that you have. Disable USB debugging on your Nexus, then plug it into your PC and see if it's recognized. If it is, then re- enable USB debugging, then go to Device Manager and reinstall the Google USB drivers to get ADB support back.

Thanks for the advice, first thing I did was try searching....I have tried countless methods suggested but nothing works its like windows cant find the drivers. In the device manger its recognised but no diver installs no matter what I do. If I force the manual driver install it fails!? I have tried the Naked drivers, the SDK even making sure the media components of windows are installed properly

[Q] USB and recovery problems after OTA upgrade to 4.3

I took the OTA to 4.3 on my Nexus 7. It was previously unlocked and rooted, but had no kernels, etc changed. After the update ran, I lost root as expected, however, in trying to get it back, I've discovered I'm having a couple of other issues.
First, the device is no longer working properly via USB on my PCs. On both my Win 7 and Win 8 PCs, the device won't properly connect to where I can browse files or anything else. On the Win 8 computer, I see a Nexus 7 device in Device manager, but drivers won't install. I downloaded the drivers from the Asus site, but trying to manually install them doesn't work on the Win 7 machine, and on the Win 8 machine, they install but don't seem to be working with the Nexus 7 as it still shows a problem in Device Manager.
The tablet also will not boot into recovery mode. I can power it up into fastboot mode, but if I select "Recovery Mode" and hit the power button, I just got the Android with the red triangle for a few minutes before it boots back into the OS. After doing some searching, I saw where you might need to have it plugged into a PC to get it to go into recovery, but that doesn't work, either (might be tied to the USB problem).
Ideas?

Did you turn on developer options, and USB debugging? Have you tried USB connection type PTP instead of MTP?
If you have the stock recovery, the red triangle and Android are normal. You can bring up a blue options menu by pressing the power and volume up buttons from the red triangle Android.
Sent from my rooted Nexus 7 @ 49.4 mpg

exglynco said:
Did you turn on developer options, and USB debugging?
Sent from my rooted Nexus 7 @ 49.4 mpg
Click to expand...
Click to collapse
Yes.

Try another driver source. Wugfresh's installation is a lot tougher than Skipsoft's, but try the other guy 's system.
Sent from my rooted Nexus 7 @ 49.4 mpg

exglynco said:
Try another driver source. Wugfresh's installation is a lot tougher than Skipsoft's, but try the other guy 's system.
Sent from my rooted Nexus 7 @ 49.4 mpg
Click to expand...
Click to collapse
I was using the stock drivers off the Asus page. I'll look around for the two you mention. I assume they're posted on here somewhere.

And about the recovery just try flashing another recovery from fastboot
Code:
fastboot flash recovery recovery.img
Sent from my Nexus 7

Red Devil said:
And about the recovery just try flashing another recovery from fastboot
Code:
fastboot flash recovery recovery.img
Sent from my Nexus 7
Click to expand...
Click to collapse
Without USB access? That's my dilemma.

OK, I'm getting closer. I got TWRP installed and rerooted it. I had to do the "Revoke USB debugging authorizations" on the Dev Options screen. Then it would work via ADB.
Still not browsing files yet on my desktop, but at least I know I'm talking to it. So now I'll play with the driver installation a bit.
EDIT: Well, drivers reinstalled for about the 4th time, and it's still not allowing me to browse files from my desktop. Galaxy S4 works fine as soon as I plug it in, even if I also uninstall it's drivers. Ideas? I obviously have it working over USB because I can give it commands and reboot it via the PC.

OK, try this one. Plug in your tablet to pc, go to hardware manager, find your Android Device then choose Uninstall (choose Remove all drivers for this device), unplug and plug in your tablet again. Your Windows should discover few new devices (mine has discovered three) and download drivers for them then you should see Android ADB Interface in Android Devices and Nexus 7 in Mobile Devices.
--edit--
I've solved my issue
http://forum.xda-developers.com/showthread.php?p=44322739#post44322739

Already been done that road multiple times.

have the same problem except one thing: no one 3 computers don`t detect my nexus. have no reaction in device manager, on connection nexus as mtp/debug/fastboot. Only usb-otg works.

xxut said:
have the same problem except one thing: no one 3 computers don`t detect my nexus. have no reaction in device manager, on connection nexus as mtp/debug/fastboot. Only usb-otg works.
Click to expand...
Click to collapse
After you plug your nexus in have you unlocked the screen to see if it is asking you to authorize the tablet?
What other steps have you taken? Have you installed proper drivers? Have you manually chosen to update drivers with the sdk drivers if in device manager is showing the nexus? Have you tried the drivers from Asus?
Sent from my Nexus 7 using Tapatalk 4 Beta

SlowCobra96 said:
After you plug your nexus in have you unlocked the screen to see if it is asking you to authorize the tablet?
What other steps have you taken? Have you installed proper drivers? Have you manually chosen to update drivers with the sdk drivers if in device manager is showing the nexus? Have you tried the drivers from Asus?
Sent from my Nexus 7 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I personally did all of those things. After having the Nexus "forget" all the other PC authorizations on the dev screen, I finally got it to accept ADB commands, just not to properly install drivers that would allow me to browse files like it had done on 4.2.

SlowCobra96 said:
After you plug your nexus in have you unlocked the screen to see if it is asking you to authorize the tablet?
What other steps have you taken? Have you installed proper drivers? Have you manually chosen to update drivers with the sdk drivers if in device manager is showing the nexus? Have you tried the drivers from Asus?
Sent from my Nexus 7 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Nexus doesn`t appears in device manager. At all. It starts to charage, but no reaction in device manager, no any reaction(except charging) at nexus. On computer it looks like i didn`t connect anything. I`ve trying to intall drivers as legasy hardware, but nothing changes. Sorry for my english.

xxut said:
Nexus doesn`t appears in device manager. At all. It starts to charage, but no reaction in device manager, no any reaction(except charging) at nexus. On computer it looks like i didn`t connect anything. I`ve trying to intall drivers as legasy hardware, but nothing changes. Sorry for my english.
Click to expand...
Click to collapse
Try turning off usb debugging. My tablet cannot connect to pc but with usb debugging off it at least recognises tablet as a media device and this enables me to view its files
.but still the problem of not being able to root

Bricked Device

I had a rooted 4.3 stock image on my N10. Got the notification about the downloaded update for 4.4
It did the update through TWRP (which was weird to me) and finished, restarts and gets stuck on the boot loading screen.
So I went into recovery, and cleared cache, no luck, then complete factory reset, no luck, then I added "System" to that wipe, not knowing what it was an now there is no OS installed.
I installed the Nexus 10 Toolkit (Unified Toolkit) and install the USB drivers, but my computer is not seeing my device..
Help?

As long as you can get to the bootloader, you can reflash a stock image. Easiest way is with wugfresh nexus root toolkit. It will walk you through the driver installation and the various image downloads.

That did not work.
The computer is not seeing my device. Drivers are installed, not seeing it, it's in the proper Boot mode.

I followed the mode that said I didn't need debugging enabled, still nothing.

bmancell said:
I followed the mode that said I didn't need debugging enabled, still nothing.
Click to expand...
Click to collapse
I would recommend uninstalling the USB drivers you installed with the toolkit and manually installing the Google USB drivers attached to this post. After you have installed the USB drivers I would recommend manually booting into your devices bootloader by simultaneously holding down the power button + volume up button + volume down button. Once you are in bootloader mode I would recommend download this Android 4.4 KitKat Factory Image and flashing it to your device in order to restore things to a working order. Let me know if you still have questions I'll be happy to help you out.

And want explain to me how I copy that file to my device when the computer can't see it?

bmancell said:
And want explain to me how I copy that file to my device when the computer can't see it?
Click to expand...
Click to collapse
Check out my previous post and see if those steps will allow your computer to see your device, and let me know how that goes for you.

Ok, I unziped the folder, got the tablet in bootloader mode, which I already said I tried, nothing.

Weird thing, I plugged the tablet into my other computer, it makes the noise for Windows 8.1 that you hear when you plug a USB device in, but there is no notifcation, nothing in device manager, nothing. Just the sound .

bmancell said:
Weird thing, I plugged the tablet into my other computer, it makes the noise for Windows 8.1 that you hear when you plug a USB device in, but there is no notification, nothing in device manager, nothing. Just the sound .
Click to expand...
Click to collapse
I just want to re-state everything to make sure anyone can understand.
This was a Nexus 10 rooted 4.3 Stock. I got the 4.4 update, it finished without issues, but got the boot loop issue.
I cleared cache, factory reset and eventually the system without luck, which left the tablet without an OS (bootloader or recovery only options).
My systems can not detect the tablet, I have installed, re-installed, tried two different toolkits and no luck.
I can't believe it's an actual brick that can't be fixed? Anyone?

Its definitely NOT your tablet. I had similar issues when rooting a Kindle and it was an issue with the PC's USB drivers. If you search the forums for USB / ADB drivers you will find a detailed discussion on how to delete existing drivers (its a process) and update new drivers.

sojthumper said:
Its definitely NOT your tablet. I had similar issues when rooting a Kindle and it was an issue with the PC's USB drivers. If you search the forums for USB / ADB drivers you will find a detailed discussion on how to delete existing drivers (its a process) and update new drivers.
Click to expand...
Click to collapse
Did you read? I have installed/reinstalled the drivers 3 times.

bmancell said:
Did you read? I have installed/reinstalled the drivers 3 times.
Click to expand...
Click to collapse
I also tried a third computer, and another cable. It will charge from a computer, nothing else.

I went through the same experience; it *was* the drivers. If you're using the wugfresh toolkit, it gives at least three options for driver installation. In my case only the drivers from pdanet worked. I've had similar issues in the past with my N7; in that case only the pdanet drivers worked on one computer, and only the Koush drivers worked on a different computer -- both Win 7 by the way; I have no idea why.
I did have to go through the whole procedure described in the toolkit to manually unistall old drivers and manually remove references to the device before reinstalling the driver.

You can get into TWRP, correct? Do you have a USB-OTG cable? You could download a ROM, put it on a flash drive then install it directly from the USB drive. There should be some flashable stock roms, or if you have an old Nandroid backup on your computer (always a good idea to have) you could restore it.
Sent from my Nexus 7 using xda app-developers app

gc84245 said:
You can get into TWRP, correct? Do you have a USB-OTG cable? You could download a ROM, put it on a flash drive then install it directly from the USB drive. There should be some flashable stock roms, or if you have an old Nandroid backup on your computer (always a good idea to have) you could restore it.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Don't know what a USB-OTG cable is, and not sure how you'd connect a flash drive, but...
I tried one more computer, this time it was a computer with Windows 7 one it. Detected the tablet right away.
So, why the heck does Windows 8 (8.1 to be exact) not allow my tablet to be seen (im sure with the OS on, and booted in, it will)./

tjupille said:
I went through the same experience; it *was* the drivers. If you're using the wugfresh toolkit, it gives at least three options for driver installation. In my case only the drivers from pdanet worked. I've had similar issues in the past with my N7; in that case only the pdanet drivers worked on one computer, and only the Koush drivers worked on a different computer -- both Win 7 by the way; I have no idea why.
I did have to go through the whole procedure described in the toolkit to manually unistall old drivers and manually remove references to the device before reinstalling the driver.
Click to expand...
Click to collapse
This must be why my Windows 8 machines don't work, but I dont remember seeing other driver options, only the one, will keep in mind in the future.

Sounds like the problem is solved, but I highly recommend getting a USB-OTG cable anyways. Go to Amazon and search for "USB-OTG". You can connect flash drives and external hard drives to your tablet. I got mine for $2.
Sent from my Nexus 7 using xda app-developers app

Bricked & Unseen...

Ok, here goes my story.
Just a week ago from the date this was posted, I decided to update my recovery (TWRP) through ROM Installer. Surprisingly, I didn't see TWRP at all in the "Recoveries" section of the application. Stock, ClockworkMod Touch, regular Clockworkmod (no touch), and unofficial Clockworkmod were available - from what I can remember. I decided to use Clockworkmod (no touch) to install Paranoid Android. Coming from OmniROM, I factory reset and flashed the .zip.
Flashing ended in error with Status 7. A while before I had used ClockworkMod Touch to try another ROM and had no such issue. I ignored the error and restarted my tablet hoping that it would still boot fine. It rebooted, gave me the Google logo for about 5-10 seconds and automatically rebooted into recovery.
I saw a bypass for Status 7. Removing some lines from the updater-script was the solution. Having no access to my Nexus 7 storage, this bypass is unusable
I tried flashing a new recovery using flashboot fastboot. After verifying that I had my drivers installed (Universal ADB by Koush), I opened up adb in the command line (Windows) as an administrator. I could not see my device. I tried the drivers from Asus, multiple USB 2.0 ports, and a different USB cord, but same results. I tried on a different computer. Still no detection.
Systems used: Windows 8.1, Windows 7 (x64), Windows 7 (x86)
I tried using Wug's Toolkit and used Flash Stock + Unroot, since it didn't need USB Debugging enabled. Same results...
I also tried plugging in another Android phone (LG Optimus Dynamic II) to see if Windows would recognize it. Windows recognized it, installed drivers automatically, and was recognized in ADB immediately. This practically unknown phone (XDA doesn't have a section for it yet) could be recognized, but my world famous Nexus 7 2012 can't be seen.
I have absolutely no idea of what to do now...

Are you on the bootloader screen when trying to use fastboot?

PrizmaticSmoke said:
Are you on the bootloader screen when trying to use fastboot?
Click to expand...
Click to collapse
Yes. Every time I use fastboot, I am in the bootloader.
I'm not new to this at all, so say whatever you need to ^^
The main problem is my PC not recognizing my Nexus 7 through adb. Again, I have used multiple cables with no success.
The computer I am using for this runs Windows 7 x64. I have only tried using USB 2.0 ports to connect my tablet.
Thank you!

Might try deleting the drivers and starting over. I had some issues with adb drivers for both the N7 and the kindle fire on windows 7 as well, but eventually got both working by doing this several times.
I'm assuming you ticked the option for softbricked when trying the flash stock option? If not try again and check that option.
This thread http://forum.xda-developers.com/showthread.php?t=1907796 has a section on driver installation with good info and links too.
Hope that helps. Best of luck man, getting the adb drivers working properly seems to be finicky sometimes in my experience, and i'm no stranger to PC and software troubleshooting either.

PrizmaticSmoke said:
Might try deleting the drivers and starting over. I had some issues with adb drivers for both the N7 and the kindle fire on windows 7 as well, but eventually got both working by doing this several times.
I'm assuming you ticked the option for softbricked when trying the flash stock option? If not try again and check that option.
This thread http://forum.xda-developers.com/showthread.php?t=1907796 has a section on driver installation with good info and links too.
Hope that helps. Best of luck man, getting the adb drivers working properly seems to be finicky sometimes in my experience, and i'm no stranger to PC and software troubleshooting either.
Click to expand...
Click to collapse
Thank you so much for all of this! I'll need all the luck I can get...
By the way, I checked that softbrick option ^^!