So I have been following the walkthrough from TheeBookReader on youtube.
Followed him word for word, made the magic SD Card, that worked fine
Downloaded the hidden settings App, that worked fine.
While trying to access the Nook via Device Manager, it shows up as a portable device, and a USB Mass Storage Device.
I downloaded the USBDeview program in his walkthrough, and everytime I uninstall the driver(already got rid of every other android and B&N driver), it automatically starts reinstalling it.
I disabled automount, I disabled auto updating, both USB Debug boxes are checked, I've disabled every feature I can think of that allows devices to do anything without my express permission but it just keeps doing it.
(Running Windows 7 Professional 32 Bit via Bootcamp on a Late 2008 MacBook 5,1.)
Also, my Nook doesn't allow me to do anything while its hooked up to the computer via USB cable. I get this little screen which I have added as a photo attachment. That lovely: USB Mode You may now safely move files from your PC to NOOK.
According to the walkthrough, I should be golden. Can someone please point out where I went wrong or missed something. I've been doing this for 3 hours now and I'm starting to foam at the mouth a bit.
WMartPD said:
So I have been following the walkthrough from TheeBookReader on youtube.
Followed him word for word, made the magic SD Card, that worked fine
Downloaded the hidden settings App, that worked fine.
While trying to access the Nook via Device Manager, it shows up as a portable device, and a USB Mass Storage Device.
I downloaded the USBDeview program in his walkthrough, and everytime I uninstall the driver(already got rid of every other android and B&N driver), it automatically starts reinstalling it.
I disabled automount, I disabled auto updating, both USB Debug boxes are checked, I've disabled every feature I can think of that allows devices to do anything without my express permission but it just keeps doing it.
(Running Windows 7 Professional 32 Bit via Bootcamp on a Late 2008 MacBook 5,1.)
Also, my Nook doesn't allow me to do anything while its hooked up to the computer via USB cable. I get this little screen which I have added as a photo attachment. That lovely: USB Mode You may now safely move files from your PC to NOOK.
According to the walkthrough, I should be golden. Can someone please point out where I went wrong or missed something. I've been doing this for 3 hours now and I'm starting to foam at the mouth a bit.
Click to expand...
Click to collapse
if you installed your nook tablet drivers correctly, the nook should come up under Android Phone -> Android ADB Composite Device. Can you confirm that?
the only reason i can think of for usb mode going active is because of automount, but since you said you disabled automount then i am not sure...
Related
(I cannot post links at this time, a quick Google Search or a look at the Topic titled "Full Root")
The goal of this guide:
I rooted my family members Nook last night but got hung up for a few hours trying to get the ADB Drivers enabled. This is how I made it work. This guide will be expanded and improved once I have my own Nook Tablet (Jan 12th).
Things you need:
• Nook Tablet (Duh)
• USB cord to go between NT and Windows PC
• PC with Windows installed (Tested on XP and x64 Windows 7)
• TGPS_Launcher.apk Installed to your Nook
• ADB USB Drivers for Nook Tablet Extracted to C:\Ntroot on your PC
• USBDeView open on the Windows PC
Step 1:
Ensure that your Nook is version 1.4.0 and not 1.4.1. (I will expand this step later when I have a nook in my hand, I suggest a Google search if you do not know how to do this)
Step 2:
Find this thread on your Nook and download the TGPS_Launcher.apk to your device, then install it. This is well covered in many other threads. (Will expand this step when I have a nook in my hand)
You should now be able to allow USB Debugging, and disable Auto Mount. These settings can sometimes change without your permission, so always uncheck and recheck them to ensure they are properly set.
Step 3:
Plug in your Nook to your PC. Your nook should still respond to your commands, if it tell you in USB Mass Storage mode, then retry Step 2.
Go into your Device Manager. If your Nook shows up with a yellow explanation mark indicating an Error, then you’re in business and really don’t need this guide. All you need to do is update drivers from the file C:\Ntroot. However, assuming that your Nook shows up under Disk Drives and USB Mass storage, then ADB wont be able to see your Nook, please keep reading.
Step 4:
Time to start the USBDeview utility. This utility will open to a list of almost all the drivers your computer has for USB Devices. We are going to uninstall a few of them, namely anything that says “Android” “Nook” or in my case, “Motorola”. You do not need to remove any that specify ADB.
Near the top right hand side, you can sort drivers by when the device was last connected. Do this, then remove any utilities used when you plugged your nook in. Done? Ok, time to see if your work was for nothing.
Step 5:
Make sure once again that USB Debugging is turned on for your Nook. Unplug the Nook, then Unchecked USB Debugging and Check it again. Now plug your device back in and check in Device Manager. You will hopefully see one of two things:
A: You will see your nook with a yellow error icon next to it, which means you just need tell it to update from C:\Ntroot.
B: At the top of the device manager you will see Android Devices, and your nook will show up as Android Composite ADB Interface
If your Nook is still showing under disk drives and mass storage, then try steps 3 and 4 again. Still having trouble? Do a factory reset and try again from step 1.
You should now be able to run your rooting program!
(I feel this should be in the Dev forum, but this is my first post and I was not allowed. Perhaps a mod would like to move this topic?)
I plan on purchasing my own Nook on the 12th on Jan, at which point I will add pictures and expand on my guide. This guide is written from memory and will be edited and improved.
Please consider this guide an Alpha Version
Good write up!
The procedure worked fine on my laptop. When I did it on on my home PC I forgot to disable auto-mount and the Nook installed itself as mass storage. I was able to right click -> un-install all the USB Mass Storage entries (with the Nook unplugged), disable auto-mount, plug the Nook back in, and have it show up correctly.
In short, I did not need to use "USBDeView" as I was able to remove the diveres manually. I suppose if you have more than a handful for USB devices (I just have a Mouse, Keyboard, and printer) "USBDeView" might be helpful to determine which drivers to un-install...
The device manager is enough for most people, but there is a somewhat large number of us that are having trouble still. Possibly because of other devices we have installed before. (I dont understand how all the drivers work and I wont pretend to)
Some people have go so far as putting a fresh install on Windows on a partition of a PC.
I had this problem with both my laptop and my desktop, which surprised me. This worked on both the laptop and PC, so hopefully it can help other people.
I cant wait to get my own tablet on the 12, I will take lot of pictures and make this process more user friendly.
I did all of the steps several times and I still get WPD Driver for the portable device and mass storage for my Nook Tablet. I am guessing I am up a river without a paddle right now.
I will try it in Linux and/or try it on someone's Windows machine.
I am trying to install the drivers from Google's SDK package. So I browse to the correct folder, but device manager says "windows could not find driver software for your device".
Any suggestions? Is there any other set of drivers specifically for NT?
mtelesha said:
I did all of the steps several times and I still get WPD Driver for the portable device and mass storage for my Nook Tablet. I am guessing I am up a river without a paddle right now.
I will try it in Linux and/or try it on someone's Windows machine.
Click to expand...
Click to collapse
Did you sort by last time plugged in and delete all of those too? Have you re-checked and then re-un-checked automount/usb debugging and such?
This is interesting, you'll have to come back and let me know if you ever get it working on your PC. Maybe its a good excuse for a nice healthy re-format and reinstall of windows?
l3ft3r1s said:
I am trying to install the drivers from Google's SDK package. So I browse to the correct folder, but device manager says "windows could not find driver software for your device".
Any suggestions? Is there any other set of drivers specifically for NT?
Click to expand...
Click to collapse
I don't know if they are different, but I used the drivers specificly from the thread about rooting the NT. [I would post a link, but I'm typing from my phone]
You have the yellow error mark next to your device? If so you've almost got it!
The_Joe said:
I don't know if they are different, but I used the drivers specificly from the thread about rooting the NT. [I would post a link, but I'm typing from my phone]
You have the yellow error mark next to your device? If so you've almost got it!
Click to expand...
Click to collapse
Yeap, that did the trick, thanks. Drives installed successfully this time, but adb devices still returns nothing.
Thats very odd. It shows up in device manager as an ADB device?
If so, please try the NookandZergy file, then copy the results so we can try to farther assist
What devices have you rooted before?
I cannot help but feel I will be 100x more useful in a week when I have my device in hand...
adb error: device offline
This drove me nuts for at least a day. Turns out it is what happens when you are plugged into a USB 3.0 port on your PC side. Find out which USB is 2.0 (Front Panel for ZT Systems), use it and life suddenly gets really good.
The_Joe said:
Thats very odd. It shows up in device manager as an ADB device?
If so, please try the NookandZergy file, then copy the results so we can try to farther assist
What devices have you rooted before?
I cannot help but feel I will be 100x more useful in a week when I have my device in hand...
Click to expand...
Click to collapse
At last, after many different things I tried, I am getting a response to adb devices!
I tried disabling and uninstalling usb devices, uninstalling java 7 and installing java 6, re-installing android sdk, at last it worked. Sorry, I can't guess what the problem was :/
l3ft3r1s said:
At last, after many different things I tried, I am getting a response to adb devices!
I tried disabling and uninstalling usb devices, uninstalling java 7 and installing java 6, re-installing android sdk, at last it worked. Sorry, I can't guess what the problem was :/
Click to expand...
Click to collapse
The problem is sdk uninstall and use ccleaner to clean your PC and registries. Use the drivers provided in this forum
Sent from XDA using one of my Android Toys
Edited post to: Sorry to bother anyone, I found the problem. Thank you all for helping!
Well I have done everything and still get permission denials for copying and chmod on my Nook Tablet.
Took the Nook to work and tried it on a fresh machine. Everything went great. Drivers installed and everything ready for usb debug and non-automount and then I run into the same permission errors and being denied access to the folder for Zerk and no chmod.
Same issue no matter what machine. What is wrong with my tablet? I am re-rooting it from being automatically upgrade to 1.4.1. I get it to 1.4.0 with the SD card restore.
LadyPenley said:
Edited post to: Sorry to bother anyone, I found the problem. Thank you all for helping!
Click to expand...
Click to collapse
In the future don't delete your original, just post an edit with the fix. That way when someone else has a similar problem your post can help.
Sent from my BNTV250 using xda premium
mtelesha said:
Well I have done everything and still get permission denials for copying and chmod on my Nook Tablet.
Took the Nook to work and tried it on a fresh machine. Everything went great. Drivers installed and everything ready for usb debug and non-automount and then I run into the same permission errors and being denied access to the folder for Zerk and no chmod.
Same issue no matter what machine. What is wrong with my tablet? I am re-rooting it from being automatically upgrade to 1.4.1. I get it to 1.4.0 with the SD card restore.
Click to expand...
Click to collapse
Did you find a solution? Thats a problem I sadly dont know how to help with. I would start with:
-Check USBDeview and delete anything android/Nook/usb related. Delete just about everything.
-Restart the device
-Uncheck and recheck the USB Debugging boxes
-Recheck and uncheck the auto-mount box
-Test
-Try a different USB Port
-Try another PC
Thanks but didn't work.
thanks, Joe. I did exactly as you mentioined below and had the Android/Nook appear at the top of the Devices listing. However, the adb command still can't find the device. Any suggestions?
Stan White
*****************
The_Joe said:
(I cannot post links at this time, a quick Google Search or a look at the Topic titled "Full Root")
The goal of this guide:
I rooted my family members Nook last night but got hung up for a few hours trying to get the ADB Drivers enabled. This is how I made it work. This guide will be expanded and improved once I have my own Nook Tablet (Jan 12th).
Things you need:
• Nook Tablet (Duh)
• USB cord to go between NT and Windows PC
• PC with Windows installed (Tested on XP and x64 Windows 7)
• TGPS_Launcher.apk Installed to your Nook
• ADB USB Drivers for Nook Tablet Extracted to C:\Ntroot on your PC
• USBDeView open on the Windows PC
Step 1:
Ensure that your Nook is version 1.4.0 and not 1.4.1. (I will expand this step later when I have a nook in my hand, I suggest a Google search if you do not know how to do this)
Step 2:
Find this thread on your Nook and download the TGPS_Launcher.apk to your device, then install it. This is well covered in many other threads. (Will expand this step when I have a nook in my hand)
You should now be able to allow USB Debugging, and disable Auto Mount. These settings can sometimes change without your permission, so always uncheck and recheck them to ensure they are properly set.
Step 3:
Plug in your Nook to your PC. Your nook should still respond to your commands, if it tell you in USB Mass Storage mode, then retry Step 2.
Go into your Device Manager. If your Nook shows up with a yellow explanation mark indicating an Error, then you’re in business and really don’t need this guide. All you need to do is update drivers from the file C:\Ntroot. However, assuming that your Nook shows up under Disk Drives and USB Mass storage, then ADB wont be able to see your Nook, please keep reading.
Step 4:
Time to start the USBDeview utility. This utility will open to a list of almost all the drivers your computer has for USB Devices. We are going to uninstall a few of them, namely anything that says “Android” “Nook” or in my case, “Motorola”. You do not need to remove any that specify ADB.
Near the top right hand side, you can sort drivers by when the device was last connected. Do this, then remove any utilities used when you plugged your nook in. Done? Ok, time to see if your work was for nothing.
Step 5:
Make sure once again that USB Debugging is turned on for your Nook. Unplug the Nook, then Unchecked USB Debugging and Check it again. Now plug your device back in and check in Device Manager. You will hopefully see one of two things:
A: You will see your nook with a yellow error icon next to it, which means you just need tell it to update from C:\Ntroot.
B: At the top of the device manager you will see Android Devices, and your nook will show up as Android Composite ADB Interface
If your Nook is still showing under disk drives and mass storage, then try steps 3 and 4 again. Still having trouble? Do a factory reset and try again from step 1.
You should now be able to run your rooting program!
(I feel this should be in the Dev forum, but this is my first post and I was not allowed. Perhaps a mod would like to move this topic?)
I plan on purchasing my own Nook on the 12th on Jan, at which point I will add pictures and expand on my guide. This guide is written from memory and will be edited and improved.
Please consider this guide an Alpha Version
Click to expand...
Click to collapse
whitets said:
thanks, Joe. I did exactly as you mentioined below and had the Android/Nook appear at the top of the Devices listing. However, the adb command still can't find the device. Any suggestions?
Stan White
*****************
Click to expand...
Click to collapse
I had literally this exact same problem the 6th time I restored and flashed. IF im right, you just need to uncheck then recheck usb debugging.
Let me know if it works!
Nook Tablet 1.4.0 was rooted per indirect instructions
B&N pushed os to 1.4.1
I performed the acclaim_update and 8 power and n button resets.
Now, adb no longer works.
Note: I have a second NT and adb works fine on that one.
Note: On both NT's tgps_launcher settings shows double for
USB Debugging
Stay Awake
Allow mock locations
Although there are 2 checks for debugging mode, only the top one prompts you for confirmation
When I check the top one, the notification in the bottom left of screen states that debugging is enabled... but in never actually works. No device found.
When I don't enable deubbing, the working nook shows up in windows explorer with "My Nook" and an additional drive if I have an SD Card in the Nook.
Windows does recognize both devices. When I plug them in, the proper entries show up in device manager
If I take the nook that doesn't work with adb to a different computer, it works.
Does adb not support the same device multiple times on windows?
Any suggestions?
Thanks.
Try Uncheck automount and uncheck - re check both debugging.
Sent from XDA premium using my Nook Tablet
I had the same problem on My windows 7 PC that had previously rooted the Tablet 3 times. Now it does just what you have described.
Same Tablet works fine on a windows Vista PC that had SDK installed. Just had to reinstall the correct drivers for it. So my solution was to use the PC that it worked on.
Thought I would add this so you know your not the only one who has experienced this.
Turns out that 1 NT works on 1 PC
And the other NT works on the other PC
I can not get adb to work with both NT's from the same PC.
Does anyone know if this is "normal"
Thanks
I have a stock Evo View running Honeycomb 3.2.1. Interestingly, neither of my computers, both mac and pc, will detect my tablet when I connect it by USB. This worked just a few weeks ago when I moved some files onto the device. The tablet charges through USB, but I do not get the notification option to use as USB storage. Within "settings > connect to pc" I've tried a number of configurations (default configuration type = disk drive, charge only) and I have also tried checking and unchecking "ask me about USB connection type whenever I connect my tablet to a PC." Nothing new happened.
Additionally, on the mac, I have the Android File Transfer app installed. When I open that i get a notification that says "No Android Device Found"
Coincidentally, I recently installed the Dropbox desktop beta for Mac which automatically detects pictures on a camera and uploads them to Dropbox. When I connected my device, Dropbox checked my device for pictures because it recognizes it as a camera. I instantly got a system error message saying that my device was not ejected properly. However, the mac never detected my device as a drive. Following that, I tried to connect to my PC and all it does is charge. My PC also does not detect my tablet as a drive. I'm thinking the new dropbox desktop client may have been the culprit for breaking my usb connection between my tablet and mac.
Has anyone else experience this problem? If not, is there a way to rebuild my usb connection between my tablet, mac, and pc?
well i would try uninstalling dropbox
Also in Settings/Applications/Development/Usb debugging should be checked.
Thanks. Appreciate the advice.
I did uninstall dropbox, on the View and on the Mac. That didn't help.
USB Debugging was checked. I can see my device in fastboot and adb. However, neither Mac nor PC will detect my tablet and allow me to mount as a hard drive.
I did a factory data reset and that worked. Both computers will recognize the View and I am receiving the notification "charge only, hard disk, htc sync, etc." again.
I wanted to break the usb connection again to confirm that it was in fact either dropbox's android beta, desktop beta, or a combination of the two. I am fairly certain that something broke the first time around because the desktop beta was able to scan my device for photos without my permission to mount the View as a hard disk. But now I'm having trouble proving this since I haven't been able to break the connection again.
Anyone else having a problem with tablet not showing up on computer after ICS. Updated the tablet with Allinone version 4 without any problem but now i need to shift some pictures onto the computer. When i plug in the tablet nothing happens on either the pc or the tablet. Ive used 2 different cables and used 2 different computers but nothing shows up. Debug is on. As far as im aware this has only happened after the ICS rooted update.
I thought that by transferring the pictures over to the sd card would at least sort that out but now i read and tried that external card is being read as "read only". So cant transfer the pictures to sd card and computer not recognising the tablet, now what?
Any advise?
D.
diddy64 said:
Anyone else having a problem with tablet not showing up on computer after ICS. Updated the tablet with Allinone version 4 without any problem but now i need to shift some pictures onto the computer. When i plug in the tablet nothing happens on either the pc or the tablet. Ive used 2 different cables and used 2 different computers but nothing shows up. Debug is on. As far as im aware this has only happened after the ICS rooted update. I thought that by transferring the pictures over to the sd card would at least sort that out but now i read and tried that external card is being read as "read only". So cant transfer the pictures to sd card and computer not recognising the tablet, now what?
Any advise?
D.
Click to expand...
Click to collapse
Your computer not recognizing your tablet sounds like an ADB driver problem, so you may have to reinstall the drivers. Condi's AIO Tweaks and Mods submenu items 12 and 11 will solve your problems with sdcard and sdcard2 write permissions and USB Mass Storage support so your computer can access your tablet's memory. Searching the forum about these problems will provide you with additional information on how to deal with them as they have been discussed several times.
Thanks for the reply. Its been so long since i initially setup the tablet. Correct me if I am wrong but when the tablet is connected to the computer the tablet should show up as sony s tablet, is that when the drivers need to be installed. Ive a shocking memory. Im starting to panic as ive documents that I have done in collage. Without the sd card transfering data to extenal in knackered.
So, if I plug the tablet in and NOTHING shows up either on tablet or pc, does that mean that the drivers need to be reinstalled?
diddy64 said:
So, if I plug the tablet in and NOTHING shows up either on tablet or pc, does that mean that the drivers need to be reinstalled?
Click to expand...
Click to collapse
Reinstalling the drivers is what other people have had to do to solve the problem you seem to have. For example, read this thread: ADB Issues after ICS update?
Thanks for your time and effort. I have seen this post when i was searchings for answers. Problem is that NOTHING happens when i plug the sony into the computer. Tablet does not acknowledge that debugging is available through the usb even though it is ticked on the tablet. The computer shows nothing either as the tablet has not got into communicating through usb. So to uninstall the drivers will be impossible until the pc recognises the tablet.
diddy64 said:
Thanks for your time and effort. I have seen this post when i was searchings for answers. Problem is that NOTHING happens when i plug the sony into the computer. Tablet does not acknowledge that debugging is available through the usb even though it is ticked on the tablet. The computer shows nothing either as the tablet has not got into communicating through usb. So to uninstall the drivers will be impossible until the pc recognises the tablet.
Click to expand...
Click to collapse
The computer is probably not recognizing or listing the tablet because the device drivers are borked. In Microsoft Windows, you can uninstall unlisted (unrecognized) devices by going into Device Manager, selecting "View" from the standard menu, selecting "Show hidden devices" (which should cause unlisted/unrecognized device names to be listed), then right-clicking on the device's name and selecting "Uninstall". After uninstalling the device, select "Action" from the standard menu, then select "Scan for hardware changes" to cause the computer to detect the tablet and prompt you to install the device drivers.
Hey there,
Here is a list of what I have before I get started.
Samsung Galaxy Tab 10.1 Wifi (P7510)
Android Version - 3.2
Kernel Version - [email protected]#1
Build Number - INFAMOUS TAB 0.1 P7510UEKMM
Basically I have no access to my tablets internal SD card via my PC (Windows 7 and KIES)
I bought this tablet from a friend who rooted and flashed with the INFAMOUS mod.
I have searched all over the web for an answer and cant find something for this case specifically.
Each time I plug in my tab, my PC tells me that the Hardware ID is missing.
I can see the tablet in my Devices and Printers (displayed as SAMSUNG_android) as well as in my Device Manager. In device manager it says the drivers are up to date and functioning.
What have I tried?
USB Debugging (On and Off)
Clearing cache via recovery mode
Updating drivers via W7 and KIES via Samsung
I have tried following a few threads on installing the KIES software without internet connectivity. However I would rather not use the KIES Software anyway as it is kind of garbage.
I am looking to have access to the internal SD card so I can flash a new Rom on the Tab, however I would first like to even just have access to the file transferring.
Can anyone point me in the direction of help and me being able to enjoy this tablet?
I hope I have provided enough information. I am a pretty techy person and I understand how to do all of this but it seems like I am missing something really big.
Something to take note of, whenever the tab is plugged in (PC or Wall) there is a red x over the battery symbol and the tab charges very slowly.
Cheers
B
Snugglebutt said:
Basically I have no access to my tablets internal SD card via my PC (Windows 7 and KIES)
...
I am looking to have access to the internal SD card so I can flash a new Rom on the Tab, however I would first like to even just have access to the file transferring.
Click to expand...
Click to collapse
The Galaxy Tab doesn't expose the internal "sdcard" as a device that you can mount on your PC. If you enable it, it shows up as a MTD device.
The sdcard partition is formatted using a Linux native filesystem, not FAT, so Windows can't recognize it.
I use adb to push files onto the sdcard. ADB comes with the android SDK.
k1mu said:
The Galaxy Tab doesn't expose the internal "sdcard" as a device that you can mount on your PC. If you enable it, it shows up as a MTD device.
The sdcard partition is formatted using a Linux native filesystem, not FAT, so Windows can't recognize it.
I use adb to push files onto the sdcard. ADB comes with the android SDK.
Click to expand...
Click to collapse
As stated, make sure you have your tablet in MTP, and if so, make sure to update your drivers.
Settings > Storage > Additional Settings (top right) > MTP
To build on the above, if you have uninstalled Kies but also the Samsung USB drivers, you will be unable to connect the tab. Reinstall (or maybe uninstall and reinstall if you still have them) the drivers. A lot of the times that is the issue.
Go to Settings>Storage>Options/Info (The one on the upper right)>MTP(Check this one)
hope this help
FIXED
k1mu said:
The Galaxy Tab doesn't expose the internal "sdcard" as a device that you can mount on your PC. If you enable it, it shows up as a MTD device.
The sdcard partition is formatted using a Linux native filesystem, not FAT, so Windows can't recognize it.
I use adb to push files onto the sdcard. ADB comes with the android SDK.
Click to expand...
Click to collapse
To build on the above, if you have uninstalled Kies but also the Samsung USB drivers, you will be unable to connect the tab. Reinstall (or maybe uninstall and reinstall if you still have them) the drivers. A lot of the times that is the issue.
Click to expand...
Click to collapse
Ahhh ha! As soon as I uninstalled the driver that windows found and used the Google Driver that came along with the Android SDK, the tablet was recognized. Alas, I can finally use this tablet.
In the end it was as simple as a driver error, I spent a very long time searching last night and now I just feel silly.
The tablet still shows the red X over the battery symbol, whether I have MTP with USB Debugging on or off. I guess this can be avoided with certain ROMS. Anybody know of a ROM that avoids this?
Thank you all for your immediate responses!
B
Tid bit of info
H. Ess said:
As stated, make sure you have your tablet in MTP, and if so, make sure to update your drivers.
Settings > Storage > Additional Settings (top right) > MTP
Click to expand...
Click to collapse
Go to Settings>Storage>Options/Info (The one on the upper right)>MTP(Check this one)
Click to expand...
Click to collapse
By the way you two, there is no option in 3.2 for this.
In 3.2 its Applications/Development/USB Debugging
In storage there is no option to choose MTP, it seems that it always has been enabled and I cant find it anywhere in the settings to change it.
Thanks for the input though
Snugglebutt said:
By the way you two, there is no option in 3.2 for this.
In 3.2 its Applications/Development/USB Debugging
In storage there is no option to choose MTP, it seems that it always has been enabled and I cant find it anywhere in the settings to change it.
Thanks for the input though
Click to expand...
Click to collapse
For honeycomb and many others, debugging is always there. Under the storage option, you have an Additional Settings button usually and it should be present in there. I was always running3.2 until like a couple days ago so surprised its not there. Oh well problem solved lol
I'm having a similar problem with my tab not being recognised by my pc (win7 64) or in kies. It was originally an M380W (Korean) model, which I updated to a P7510. That all went fine, and the tablet works perfectly, except for the fact that my pc no longer sees it when it's plugged in. I tried uninstalling and reinstalling the drivers, but no dice. I'm going to see if adb works.