Related
hey everyone,
I can't see my kindle fire as a storage device in [ my computer ]
there is NO problem with connecting my kindle and PC because Android debugging is enabled and [ i can see notification on my device ]
AND i can install stuffs from KINDLE FIRE UTILITIES
my only problem is my kindle won't show up as a STORAGE DEVICE
please help!! I'm beginner
P.S My kindle running on android 4.0.4 CM9
I have the same problem. Thanks for your answers
disable debugging
That doesn't change anything. Nothing happens.
Slaxxy said:
That doesn't change anything. Nothing happens.
Click to expand...
Click to collapse
When you plug the cable in, do you see a little usb symbol in your notifications?
No that doesn't come up. Only when the Debugmode is activitated there is this debug notification.
Some ICS roms have trouble mounting UMS but, as far as I know, Vanilla shouldn't have a problem with it.
See if you can mount your sdcard while in recovery.
that worked. thanks
But still not when the system is running
If you can mount in recovery but not with the rom then it's either a problem with the rom or you're missing something.
Whenever i restart the kindle fire the usb debug thing is activated again. Can I change that some where in the TWRP?
That's typical. I think it's dependent on whatever the developer sets as default.
It really depends on which rom your using but if you happen to be using hashcodes go to settings storage and the are three dots in the upper right click there you get three options mtp,ptp and mass storage they are all unchecked by default. with your kindle not plugged into the computer select like mass storage. Then plug it in it should install the appropriate driver on your computer.
Or you could get Wifi File Explorer Pro and never worry about what roms have working UMS.
Thepooch said:
It really depends on which rom your using but if you happen to be using hashcodes go to settings storage and the are three dots in the upper right click there you get three options mtp,ptp and mass storage they are all unchecked by default. with your kindle not plugged into the computer select like mass storage. Then plug it in it should install the appropriate driver on your computer.
Click to expand...
Click to collapse
That's exactly what I was looking for. After activating that and deactivating the debug mode it worked by klicking on the usb symbol in the tastk bar and then activate usb mass storage. Thanks a lot.
Your welcome
Sent from my Amazon Kindle Fire using Tapatalk 2
soupmagnet said:
Some ICS roms have trouble mounting UMS but, as far as I know, Vanilla shouldn't have a problem with it.
See if you can mount your sdcard while in recovery.
Click to expand...
Click to collapse
actually I changed the ROM to gederom and now it shows as a storage device ..thank buddy :-D
I just got into flashing my KF (noob, I know) and everything went smoothly except for this. I like the CM10 ROM that TWA put out and according to posts in that thread USB mounting works fine, but it doesn't for me. The PC and KF don't recognize that they are connected with a USB at all. There is no notifications on either end. This worked fine before I flashed. And I changed ROMs to Hashcodes JB AOSP ROM and USB notification and mounting worked fine there. I then flashed back to the CM10 and still no love.
So how can I debug this? What settings should I check? Are there an apps out there that will let me get more info about my setup to see if something is screwy regard USB. Any helpful tips would be appreciated.
I have tried a couple tips I found in the CM10 thread, but they didn't help. (specifically switching to Hashcodes ROM and back again)
SenorSmartyPants said:
I just got into flashing my KF (noob, I know) and everything went smoothly except for this. I like the CM10 ROM that TWA put out and according to posts in that thread USB mounting works fine, but it doesn't for me. The PC and KF don't recognize that they are connected with a USB at all. There is no notifications on either end. This worked fine before I flashed. And I changed ROMs to Hashcodes JB AOSP ROM and USB notification and mounting worked fine there. I then flashed back to the CM10 and still no love.
So how can I debug this? What settings should I check? Are there an apps out there that will let me get more info about my setup to see if something is screwy regard USB. Any helpful tips would be appreciated.
I have tried a couple tips I found in the CM10 thread, but they didn't help. (specifically switching to Hashcodes ROM and back again)
Click to expand...
Click to collapse
which one did you try ? go to developer option and make sure there is a check in android debugging
---------- Post added at 05:08 PM ---------- Previous post was at 05:06 PM ----------
Thepooch said:
which one did you try ? go to developer option and make sure there is a check in android debugging and no check in protect usb storage
Click to expand...
Click to collapse
give that a try
---------- Post added at 05:11 PM ---------- Previous post was at 05:08 PM ----------
also did you wipe? wipe factory reset wipe cache wipe dalvik wipe system flash rom flash gapps reboot
Debugging was turned off. I turned it back on, rebooted and that did the trip.
Many thanks.
I think I will do a full wipe (was just doing the cache/dalvik after the first install) to make sure nothing else is screwy
Thepooch said:
which one did you try ? go to developer option and make sure there is a check in android debugging
---------- Post added at 05:08 PM ---------- Previous post was at 05:06 PM ----------
give that a try
---------- Post added at 05:11 PM ---------- Previous post was at 05:08 PM ----------
also did you wipe? wipe factory reset wipe cache wipe dalvik wipe system flash rom flash gapps reboot
Click to expand...
Click to collapse
no prob
SenorSmartyPants said:
Debugging was turned off. I turned it back on, rebooted and that did the trip.
Click to expand...
Click to collapse
After playing around with this a bit something is still not right.
I have debugging turned on, but USB is only successfully detected if I reboot with the usb cable plugged in to a PC. Then I can mount and dismount as many times as I want. everything is fine. But once I disconnect the USB cable, the KF will never detect the cable plug in again (nor will the PC). I have to reboot plugged in again to get it to show up.
I've done this several times same thing. I've tried plugging the cable in at different points too, before I unlock the screen, after. Only when in from reboot to unlock does it work.
SenorSmartyPants said:
After playing around with this a bit something is still not right.
I have debugging turned on, but USB is only successfully detected if I reboot with the usb cable plugged in to a PC. Then I can mount and dismount as many times as I want. everything is fine. But once I disconnect the USB cable, the KF will never detect the cable plug in again (nor will the PC). I have to reboot plugged in again to get it to show up.
I've done this several times same thing. I've tried plugging the cable in at different points too, before I unlock the screen, after. Only when in from reboot to unlock does it work.
Click to expand...
Click to collapse
i have the same issue on mine, using twa builds
also, sometimes when i plug in the usb cable it makes the kindle run extremely slow and laggish, requiring a reboot.
*Bump*
Does only detecting usb connected once per reboot only happen to the two of us in this thread? CM10 works pretty well for me, but this is a bit of an annoyance. I have a work around, reboot, but still...
I have the same issue. In fact, I can't get USB storage to work after installing CM10 8/24.
But I think the issue has to do with multiple Android USB drives being installed in Win7. I have a TF201 and Xoom and when I plug in the KF, USB reports the TF201 being connected. Of course Win7 does not show KF in Desktop Explorer. The only way I can download a new ROM to my KF is via my NAS which I connect via ES File Manager....
Can anyone confirm that having multiple Android devices causes this USB confusion?
You have to specifically enable USB storage before it will mount.
Unable to root! Stucked on TWRPP 2.2.0 Screen with several options
Hello!
I've tried to root my Kindle Fire, following the same steps that most of the users have followed (Using KFU 0.9.6).
Unfortunately, while installing the root (I guess) once it installs TWRPP, it inmediately boots up to the TWRPP screen with several options ( Install, Backup, Restore...) and the KFU software keeps a message that says Please wait.
Does anyone know how to fix this and finish the rooting of the device?
Thanks in advanced.
jjosue17
soupmagnet said:
You have to specifically enable USB storage before it will mount.
Click to expand...
Click to collapse
I have enabled but it still will not mount for some reason. I had a forced reboot issue appear as well.
try the previous build see if that doesnt solve your problem you must have usb debugging enabled and then tap on the icon in your status bar to transfer files...
I've been limping along just using the work around of rebooting while plugged in to get usb mounting to work.
But today I had KF mount to my PC, deleted the ADB drivers in windows from the device manager. Did a factory wipe on the tablet (even wiped the SD card), I'm running the latest TWA rom 8/28. I still can only get usb to detect if I reboot while connected to a pc. A couple little differences; after the wipe ADB was turned off on the ROM, I left it that way to see what happens. It does still mount (only after reboot, did I mention that ) but now it shows up under "Portable Devices" in device manager and the Device ID string is different in some apps (on PC) "Amazon Kindle Fire" instead of "Kindle Fire" which is what it was before today.
What else can I try? Do I need to do a super duper wipe? Factory, reinstall ROM, cache/dalvik? Do I need to purge even usb android driver on my system? (And how would I do that?)
Thanks for any help. I would love to get rid of this issue and just be able to plug in the KF and not worry about rebooting all the time.
Funny thing is I worked with someone the other day and when he mounted nothing would come up..... Reinstalled his adb drivers from kfu and it worked like a champ... Dont really know why... This is what I would try instead of messing with windows try creating a live usb as a formidable test to see if its simply just windows stupid drivers that are killing you... Create it with persistent and use this script to set up the drivers http://forum.xda-developers.com/showthread.php?t=1850038 very good chance it will work then you will know its a driver problem...
I'll see if I can give the Live USB thing a try if KFU driver reinstall doesn't help.
But I have a laptop that I never messed with the drivers on. With stock usb was always detected, after rooting and rom installed, had the same usb detection problems as my desktop.
Well I never did give the Live linux USB thing a try. I just keep going with my work around of rebooting with the usb connected and then doing my file transfers. I would only do this about once a week. I even noticed that with a couple of the more recent builds if I would plug KF in several times it would detect usb and I would not have to reboot.
But now with the last build (or two?) not exactly sure when it changed even that isn't working. Plugging in several times never detects usb now (95%+ detects usb charging though). And now it also won't detect usb after reboot while the cable is plugged in during the reboot. So I've had to do my file transfers in recovery mode. Recovery mode always works. What is different about what recovery mode "says" to the computer compared to what the full ROM "says"
Oh, and I only get USB 1.1 transfer speeds. But I think I read that this is a kernel driver issue that is well known, or has that been fixed somewhere?
Thanks
Not sure exactly what I did but after my last rom update(i did a system wipe before updating) I have been unable to connect my KF to my PC as a storage device. I'm not sure if i need to try and wipe back to stock by downloading the stock software over WIFI and flash through TWRP or what. Any insight would be appreciated.
Go to storage and click on the three dots upper right select mtp or mass storage and enable USB debugging under development and try again
Nothing : / I'm running the last release of Glazed ICS if that helps at all. It won't mount under TWRP either.
not mounting under twrp... go to twrp select mount make sure there are no checks in the boxes of system and data, only cache and sd card need to have the boxes checked then select mount. when done safely eject then unmount
yeah, that's what i mean by won't mount in TWRP. Doesnt work. That's why i'm baffled.
yeah bigrob1712 I would move on to another rom myself
---------- Post added at 12:55 AM ---------- Previous post was at 12:49 AM ----------
if you still have trouble - boot to twrp
- test adb with "adb devices"
- open shell -> "adb shell"
- issue "echo /dev/block/mmcblk0p12 > /sys/devices/platform/usb_mass_storage/lun0/file"
- now the sdcard should mount to the computer
- windows will probably respond that the volume/device needs formatted before using it
- choose quick format and let it format it as fat32 block size 4096
of course formatting you will loose all your data on your sdcard beware
well, my problem is a lil bit different.
Im using jandycane 1.7.1 now, i can connect my KF to PC with the cable, and the PC recognizes KF as mass storage, but the thing is the speed when i copy some music and movies from PC to KF. the speed is limited at about 1.2 MB/s that drives me crazy.
when i used the stock rom 6.3.1, with the same PC, KF and the cable, the speed was about 25MB/s.
any helps? thanks in advance.
I would move on to another rom maybe you will be happier with as far as transfer speed
i just wonder that's only me or it means to be like that?
i've realized its gotta be something with my computer or cord because i've realized my S2 won't connect either.
I'm having sorta the same problem here. It doesn't show as a removable storage device on my computer. I can transfer stuff to it with adb and I can mount it in TWRP but I don't want to have to use adb or restart the kindle every time I want to transfer files. Can anyone help?
did you try anything I suggested in this thread? as well what rom are you using? do you have usb debugging enabled ?
Thepooch said:
did you try anything I suggested in this thread? as well what rom are you using? do you have usb debugging enabled ?
Click to expand...
Click to collapse
yes usb debugging was enabled. I was using cyanogenmod 9. maybe it didn't work because i was using the wrong mod (my computer kept recognizing it as a Google nexus). But i just tried the aokp kf edition and its working perfectly. Thanks
Download the KFU (Kindle fire utility). Once you do that, click on install_drivers.bat (with your kindle unplugged). Then try to connect to the computer.
Sent from my Amazon Kindle Fire using xda app-developers app
Hi All:
I have the 16GB N7 (2013) with USB debugging enabled. I plug into my Windows 7 box via USB 2.0, and it successfully appears in my device manager as 'Google Nexus ADB Interface'. I just downloaded the current Android SDK, however when I run 'ADB devices' in the command prompt, ADB does not recognize any devices.
Any ideas?
Thanks!
Did you try if it would recognize your device in fastboot bootloader?
Go into I believe its called SDK manager and make sure USB or Google drivers update is checked and then click Install as this will install all drivers needed. But prior to that uninstall any drivers in device manager for your nexus 7 . it should pick it up right away after everything installs! Good luck
Sent from my Nexus 7 using xda premium
highwaybandit said:
Go into I believe its called SDK manager and make sure USB or Google drivers update is checked and then click Install as this will install all drivers needed. But prior to that uninstall any drivers in device manager for your nexus 7 . it should pick it up right away after everything installs! Good luck
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Thank you for the suggestion, highwaybandit. I tried your idea, but still have the same issue with ADB not recognizing the device, despite the device showing up successfully in Windows device manager.
I have the same problem with Ubuntu. I tried "adb reboot bootloader" and nothing. Unlocked fine with fastboot tho.
Sent from my Nexus 7 using Tapatalk 2
Username invalid said:
Did you try if it would recognize your device in fastboot bootloader?
Click to expand...
Click to collapse
Yes, and it does. I was able to 'fastboot oem unlock'. However, can't issue any adb commands.
My Nexus 7 will not show up as a drive on my computer. Drivers are installed, shows up in device manager fine, uninstalled and re-installed drivers, usb debugging is on. I cant see it has a drive so I can transfer files. Any help would be appreciated
mickrg123 said:
My Nexus 7 will not show up as a drive on my computer. Drivers are installed, shows up in device manager fine, uninstalled and re-installed drivers, usb debugging is on. I cant see it has a drive so I can transfer files. Any help would be appreciated
Click to expand...
Click to collapse
Now that you mentioned it, same issue here, in addition to the ADB issue mentioned above. My N7 doesn't show up as a drive whether I have USB debugging enabled or not.
mickrg123 said:
My Nexus 7 will not show up as a drive on my computer. Drivers are installed, shows up in device manager fine, uninstalled and re-installed drivers, usb debugging is on. I cant see it has a drive so I can transfer files. Any help would be appreciated
Click to expand...
Click to collapse
mickrg123, I forgot to mention: I've been getting around this issue by using Google Drive. Not as fast as moving files directly, but still a decent workaround until we get this figured out.
mickrg123 said:
My Nexus 7 will not show up as a drive on my computer. Drivers are installed, shows up in device manager fine, uninstalled and re-installed drivers, usb debugging is on. I cant see it has a drive so I can transfer files. Any help would be appreciated
Click to expand...
Click to collapse
If you have USB debugging enabled, the USB IDs change and for some reason windows can't find the MTP drivers for the device.
If you turn off USB debugging, then the phone shows up as an MTP device (ie it shows up as Nexus 7, not a drive letter)
If you want it to show up as a drive letter, you probably need to root and enable USB mass storage, otherwise it will behave as an MTP device (ie it behaves more like an FTP server than a USB hard drive)
If you have USB debugging disabled and it still won't show up on your computer in MTP mode (ie labeled Nexus 7), then you probably have some problem with MTP on your PC.
---------- Post added at 02:06 PM ---------- Previous post was at 02:04 PM ----------
ddb540 said:
Hi All:
I have the 16GB N7 (2013) with USB debugging enabled. I plug into my Windows 7 box via USB 2.0, and it successfully appears in my device manager as 'Google Nexus ADB Interface'. I just downloaded the current Android SDK, however when I run 'ADB devices' in the command prompt, ADB does not recognize any devices.
Any ideas?
Click to expand...
Click to collapse
Generally, if it doesn't show up at all with adb devices, then it is probably driver problem, cable problem, port problem, or USB debugging didn't properly get enabled. Although since you say it shows up in device manger, it would seem to show that USB debugging was enabled, so you might want to look at driver, cable, or USB port issues (try USB 2.0 port if you are currently using USB 3.0). You can get updated drivers here:
http://developer.android.com/sdk/win-usb.html
You can force windows to update driver by right clicking on the adb device entry and going through the tabs until you find the update driver button.
If it shows up but says device offline, then it is probably the RSA security introduced into adb/android since 4.2.2 (in which case you should update your platform-tools to 16.0.1 or greater)
Also when I check box to load camera it will show as drive
sfhub said:
If you have USB debugging enabled, the USB IDs change and for some reason windows can't find the MTP drivers for the device.
If you turn off USB debugging, then the phone shows up as an MTP device (ie it shows up as Nexus 7, not a drive letter)
If you want it to show up as a drive letter, you probably need to root and enable USB mass storage, otherwise it will behave as an MTP device (ie it behaves more like an FTP server than a USB hard drive)
If you have USB debugging disabled and it still won't show up on your computer in MTP mode (ie labeled Nexus 7), then you probably have some problem with MTP on your PC.
---------- Post added at 02:06 PM ---------- Previous post was at 02:04 PM ----------
Generally, if it doesn't show up at all with adb devices, then it is probably driver problem, cable problem, port problem, or USB debugging didn't properly get enabled. Although since you say it shows up in device manger, it would seem to show that USB debugging was enabled, so you might want to look at driver, cable, or USB port issues (try USB 2.0 port if you are currently using USB 3.0). You can get updated drivers here:
http://developer.android.com/sdk/win-usb.html
You can force windows to update driver by right clicking on the adb device entry and going through the tabs until you find the update driver button.
If it shows up but says device offline, then it is probably the RSA security introduced into adb/android since 4.2.2 (in which case you should update your platform-tools to 16.0.1 or greater)
Click to expand...
Click to collapse
I don't care if doesn't show as drive but doesn't even show as nexus 7 so I can't root until I can load su onto sd card.
Have tried different cables and ports. I heard beep when it connects and shows in menu to to eject nexus 7
Any other ideas?
mickrg123 said:
Also when I check box to load camera it will show as drive
Click to expand...
Click to collapse
If you have USB debugging enabled, then my experience is Media device (MTP) mode won't be recognized because it can't find appropriate drivers (even though you have the MTP drivers installed) but Camera (PTP) mode will still work. I don't think you really mean it shows up as a "drive" as in mass storage device. I think you mean you see a folder where you can access your files.
If you disable USB debugging, than both MTP and PTP should work.
sfhub said:
If you have USB debugging enabled, then my experience is Media device (MTP) mode won't be recognized because it can't find appropriate drivers (even though you have the MTP drivers installed) but Camera (PTP) mode will still work. I don't think you really mean it shows up as a "drive" as in mass storage device. I think you mean you see a folder where you can access your files.
If you disable USB mass storage, than both MTP and PTP should work.
Click to expand...
Click to collapse
Yes you're correct shows as a device not drive when in camera ptp, but not when mtp checked. Where do you disable mass storage?
mickrg123 said:
Yes you're correct shows as a device not drive when in camera ptp, but not when mtp checked. Where do you disable mass storage?
Click to expand...
Click to collapse
Sorry, I meant disable USB Debugging, not mass storage (I'll correct the post)
I'm sure you know where, but if not, Settings->Developer options->USB debugging
If MTP still doesn't work, then see if you have ever gotten MTP to work on the PC (ie another device in MTP mode). If not, look up how to install/reinstall MTP support for your OS version. Windows added it as part of user driver framework and one of the new versions of media player.
---------- Post added at 04:39 PM ---------- Previous post was at 04:32 PM ----------
mickrg123 said:
I don't care if doesn't show as drive but doesn't even show as nexus 7 so I can't root until I can load su onto sd card.
Have tried different cables and ports. I heard beep when it connects and shows in menu to to eject nexus 7
Any other ideas?
Click to expand...
Click to collapse
If your goal is just to load files onto the sdcard, have you tried "adb push"?
You don't need to have the phone visible as a device/folder on the computer to use adb to place files on the tablet.
Im having trouble with mine also. Adb sees it when its in normal mode. When I go to bootloader, it is not seen. When i go to unlock, it just says waiting for device. Any ideas???? Updated SDK installed
droider137 said:
Im having trouble with mine also. Adb sees it when its in normal mode. When I go to bootloader, it is not seen. When i go to unlock, it just says waiting for device. Any ideas???? Updated SDK installed
Click to expand...
Click to collapse
1. Plug in nexus 7, MTP mode
2. Open the device manager
3. Right click the nexus 7 > uninstall drivers > unplug
4. Install drivers > http://developer.android.com/sdk/win-usb.html
5. Plug nexus 7 in, drivers will install, should say adb interface
Open up command prompt > nav to your adb folder > adb devices: device number should pop up. Good to go.
droider137 said:
Im having trouble with mine also. Adb sees it when its in normal mode. When I go to bootloader, it is not seen. When i go to unlock, it just says waiting for device. Any ideas???? Updated SDK installed
Click to expand...
Click to collapse
For me, when I rebooted the phone into bootloader mode, it came up with a new USB device "Android Bootloader Interface". I had to point the driver install at the Google USB drivers I had previously used for the ADB interface so that the Bootloader Interface could be recognized.
sfhub said:
For me, when I rebooted the phone into bootloader mode, it came up with a new USB device "Android Bootloader Interface". I had to point the driver install at the Google USB drivers I had previously used for the ADB interface so that the Bootloader Interface could be recognized.
Click to expand...
Click to collapse
Finally got it!! Had to uninstall and re install the drivers a few times and also remove MTP from device manager. Also had to do the same thing and point it to the drivers in both cases. Thanks. Also thanks to teh roxxorz!
droider137 said:
Finally got it!! Had to uninstall and re install the drivers a few times and also remove MTP from device manager. Also had to do the same thing and point it to the drivers in both cases. Thanks. Also thanks to teh roxxorz!
Click to expand...
Click to collapse
No problem guy; glad you're up an flashing.
im not sure if ive been looking in the wrong places but i cant find an answer to my problem. so i rooted my nexus 7 about a week ago and installed twrp. everything was working fine until i accidentally pressed wipe data instead of factory reset. i deleted EVERYTHING on my tablet including my operating system, the only thing left was twrp :crying: today my otg usb cable came in and i installed that unofficial cyanogenmod build and now it wont connect to my pc. i have usb debugging on and everything. i go to device manager (on my pc) and it is listed as "Nexus 7" but when i try to install the usb drivers it says that they dont work for it. how can i get the usb drivers to work again?
Note: its not my pc cause my rooted s3 works just fine with my pc.
sorry for being a noob! and thanks for the help!
I actually have the same issue where my Windows won't let me navigate my N7 as a portable device. Tried a whackload of drivers and the like to no avail. To transfer files I just end up using ES Explorer. Funny enough, ADB in recovery works just fine.
If it is the same as PA and PAC, try Settings > Storage > Press Menu > USB > Check MTP
Sent from my Nexus 7 using Tapatalk 4
BigDaddySunshine said:
im not sure if ive been looking in the wrong places but i cant find an answer to my problem. so i rooted my nexus 7 about a week ago and installed twrp. everything was working fine until i accidentally pressed wipe data instead of factory reset. i deleted EVERYTHING on my tablet including my operating system, the only thing left was twrp :crying: today my otg usb cable came in and i installed that unofficial cyanogenmod build and now it wont connect to my pc. i have usb debugging on and everything. i go to device manager (on my pc) and it is listed as "Nexus 7" but when i try to install the usb drivers it says that they dont work for it. how can i get the usb drivers to work again?
Note: its not my pc cause my rooted s3 works just fine with my pc.
sorry for being a noob! and thanks for the help!
Click to expand...
Click to collapse
Were you on stock before you wiped? Trying going back to stock and see if you can get MTP working, then start introducing the parts until you figure out what broke.
The USB IDs for the MTP device change more often than you'd expect causing recognition problems.
For example, on stock, with USB debugging enabled, it advertises one USB ID and also sends out a MTP-compatible flag. When USB debugging is disabled, a different USB ID is sent, minus the MTP-compatible flag.
I helped someone on a different ROM force the MTP device drivers to associate, but then the drivers couldn't initialize the device. This might indicate there is a problem on the ROM side.
---------- Post added at 11:47 AM ---------- Previous post was at 11:45 AM ----------
verkion said:
I actually have the same issue where my Windows won't let me navigate my N7 as a portable device. Tried a whackload of drivers and the like to no avail. To transfer files I just end up using ES Explorer. Funny enough, ADB in recovery works just fine.
Click to expand...
Click to collapse
If your ADB works in recovery then you must have installed some other adb device driver, other than Google's, at some point.
If you want I can try helping you get things recognized on this thread
http://forum.xda-developers.com/showthread.php?t=2391236
swagstr said:
If it is the same as PA and PAC, try Settings > Storage > Press Menu > USB > Check MTP
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
this