!!! HELP !!!...AFTER ROOTING MY NOOK TABLET I CONNECTED IT TO MY LAPTOP'S USB PORT SO THAT I COULD DOWNLOAD AN e-Book USING ADOBE DIGITAL EDITIONS SOFTWARE...FOR SOME UNKNOWN REASON THE TABLET IS NOT RECOGNIZED AND AS A RESULT I CAN'T DOWNLOAD THE e-Book...PLEASE HELP...ANY ASSISTANCE WOULD BE GREATLY APPRECIATED...THANK YOU...:crying:
What operating system? The device isn't recognized or nothing shows up at all when you plug it in?
Just an fyi posting the same thing in multiple forums wont get you answers any faster and has a tendency to cause a failure to respond at all. With that said, provide more details such as what version are you on. 1.41, .42, .43 ? What process did you use to root? Have you tried creating a CM7 SD card (how to is in these forums so read a bit for specifics) and see if that allows access? Are you sure its not an issue with the PC you're using? Have you tried it on another pc just to rule that out?
thesal523 said:
!!! HELP !!!...AFTER ROOTING MY NOOK TABLET I CONNECTED IT TO MY LAPTOP'S USB PORT SO THAT I COULD DOWNLOAD AN e-Book USING ADOBE DIGITAL EDITIONS SOFTWARE...FOR SOME UNKNOWN REASON THE TABLET IS NOT RECOGNIZED AND AS A RESULT I CAN'T DOWNLOAD THE e-Book...PLEASE HELP...ANY ASSISTANCE WOULD BE GREATLY APPRECIATED...THANK YOU...:crying:
Click to expand...
Click to collapse
Typing in all caps is really not needed either. We can read just fine.
Sent from my A500 using xda premium
Thread moved to Q&A and other thread closed. Please don't post more than one thread on the same subject again please and always post in the right section. Also as stated above people can read normal fonts just fine and using caps signifies shouting meaning it'll be looked at and ignored by some.
I apologize for posting in 2 different forums, wasn't sure which one would apply...
The software version shows 9.9.9 under "About Your NOOK" in settings, however I believe the correct version(1.4x) was overlayed when rooting was done...I tried plugging into different USB ports from several laptops, same results...NOOK Tablet is not recognized, getting Removable Disk(F/G/H) instead when looking in My Computer...Something is inhibiting turning on USB to recognize the device when plugged into the PC...Someone suggested (in the other forum) to turn USB mass storage on from the NOOK...How is that done?...Do I need to tweak something for USB to be on?...TGPS_LAUNCHER shows USB debugging is checked(twice) under Development...Could this be related?...Rooting was done following instructions in XDA-DEVELOPERS website...Let me know if I you need any other information to helpme get my NOOK TABLET get recognized when plugged into USB port...Your help is greatly appreciated...Thank you...
:victory:Good News!!!...I poked around in TGPS_LAUNCHER & tweaked the settings for USB debugging(uncheck) & Auto Mount(check)...I then plugged my NT to the USB port, fired up Adobe Digital Editions & voila!...The NOOK Tablet was detected and I was able to download the e-Book...
And of course I still have the rooted device intact...Thank you all...
In the future, try not to panic. Any perceived issue you have with this device has likely been encountered by at least one other person (and usually many more than that). As a result, there is probably a relatively simple and easy solution that eludes, as was the case this time, and really no reason to worry/panic.
Related
My Dell desktop does not recognized my Fascinate after upgrading to Windows 7 Service Pack 1.
I can't use ODEN any more, can't even mount the SD card anymore.
Really stuck big time.
HELP HELP HELP!!!
Still stuck and feel like getting rid of my phone and verizon all together.
Whats wrong with microsoft and samsung, I know another guy that couldn't print after upgrading to SP1.
its possible that the samsung drivers are not installed.
Sent from my SCH-I500 using XDA Premium App
Definitely start by uninstalling the drivers, and then reinstalling the latest version (for the extra paranoid, run something like driver sweeper before reinstalling). Also, try different ports on your computer/make sure you're using the official cable that came with your Fascinate.
If that doesn't work let us know (along with anything else you've tried, just to save us from telling you to do things you've already done!).
Also, just for future reference, this should go in the Q&A section- Development is meant for postings of ROMs and other similar things (there's a high probability your post could get rocketed off the front page before anyone even notices it in this section!).
Agreed, try upgrading your drivers. If that does not work initially, reboot into CWM with the phone plugged in, that usually forces Windows to detect the device drivers again and install them (always works for me when Windows *forgets* the Samsung drivers).
As the poster said above, this should have been posted in Q&A or General, and not development. I have reported the post so that a mod can move your thread to the appropriate section.
i have this problem before.
With debugging on, power phone off, plug into computer and power phone on. That should allow the computer to see your phone
Click to expand...
Click to collapse
androidcentral
Here another thing to try- shut down computer, and then unplug the power chord from the back. Let it sit, then plug it in and boot it up.
That's what worked for me.
Sent from my SCH-I500 using XDA App
I've run into this issue several times, and have found a few solutions.
Several times, it took completely removing the drivers and reinstalling them. By completely removing them, I mean uninstalling them through add/remove programs and then by searching through the registry for the many traces that the driver uninstall misses. And there are many... like hundreds. And there are all kinds of permission problems on those registry keys that you need to fix, one by one, before they can be deleted. It's a major PITA that takes hours to do. But once it's done, I was able to reinstall the drivers and the phone was recognized fine.
Another issue I ran into was a possibly faulty USB cable. Just recently, Windows just stopped recognizing the phone, and in trying different ports, I happened to notice Windows was detecting the bare cable (as in it wasn't plugged into the phone). I could plug the cable alone in, and Windows would recognize it as an "unrecognized USB device". I tried a different cable and it saw the phone fine.
So, first thing to check is your cable. Does Windows detect it when you just plug in the cable by itself? If so, try a different one.
If nothing else works, and you want to remove the drivers totally, let us know and I'll walk you through the steps to remove all those bloody registry keys, but it's not fun...
ChrisDDD said:
I've run into this issue several times, and have found a few solutions.
Several times, it took completely removing the drivers and reinstalling them. By completely removing them, I mean uninstalling them through add/remove programs and then by searching through the registry for the many traces that the driver uninstall misses. And there are many... like hundreds. And there are all kinds of permission problems on those registry keys that you need to fix, one by one, before they can be deleted. It's a major PITA that takes hours to do.
Click to expand...
Click to collapse
Revo Uninstaller is an ideal solution for totally cleaning stuff out. Pick the most aggressive sweep, and after the factory uninataller finishes, it isolates and removes all the leftover registry keys, files, and folders associated with the uninstalled item. Found it to be a godsend as a PC tech in a big school district with way more computers to manage than I had time.
The free version is more than adequate.
Materialized into existence through the act of observation.
Here is my observation, my USB mass storage doesn't get recognized on the computer hardly ever (it was a miracle and an event to be celebrated if it happened), and I talked to some people in IRC about it. GizmoDroid had me trying lots of different things. Eventually I just installed ADB, and to my surprise, ADB always sees the phone just fine. So, I think the Samsung drivers need tweaked a bit because they definitely work, but something about them just doesn't work correctly with Windows (or with anything, but has samsung ever put out any software that was up to our standards?).
My suggestion is to install and learn ADB, not hard at all with the given tutorials. Even easier if you have experience with Linux. It always, always works for me.
tbeas said:
My suggestion is to install and learn ADB, not hard at all with the given tutorials. Even easier if you have experience with Linux. It always, always works for me.
Click to expand...
Click to collapse
ADB would work as an alternative to USB mass storage for the most part (which shouldn't need the Samsung drivers), but it isn't an alternative to being able to use Odin!
agsded said:
Revo Uninstaller is an ideal solution for totally cleaning stuff out. Pick the most aggressive sweep, and after the factory uninataller finishes, it isolates and removes all the leftover registry keys, files, and folders associated with the uninstalled item. Found it to be a godsend as a PC tech in a big school district with way more computers to manage than I had time.
Click to expand...
Click to collapse
Cool, thanks, I'll definitely check that out. I had set up some macros to repeat the process of setting ownership of each key and deleting it, but it still took hours.
tbeas said:
Here is my observation, my USB mass storage doesn't get recognized on the computer hardly ever
Click to expand...
Click to collapse
The OP can correct me if I'm wrong, but this isn't just a mass storage problem, the phone itself isn't recognized as anything at all, so that means mass storage doesn't work, Odin won't pick it up, nor will ADB. Connect the phone, and at best, Windows sees an "unrecognized USB device", at worst, it sees nothing at all, as if the phone wasn't even connected.
Mine will go invisible to Odin at times, also. I will go to heimdall at that point and it will usually be visible there. I keep both programs around partially for that reason, and partially cause of how granular heimdall is.
Materialized into existence through the act of observation.
Delete
KitsuneKnight said:
ADB would work as an alternative to USB mass storage for the most part (which shouldn't need the Samsung drivers), but it isn't an alternative to being able to use Odin!
Click to expand...
Click to collapse
Adb 100% needs the Samsung drivers.
Sent from my SCH-I500 using XDA App
suppliesidejesus said:
Adb 100% needs the Samsung drivers.
Click to expand...
Click to collapse
The drivers might not be necessary if connecting to the phone with ADB over TCPIP, which you can set using a terminal emulator on the phone.
Don't know if you need to log in as SU or not, but these are the commands:
setprop service.adb.tcp.port 5555
stop adbd
start adbd
These set the adb daemon to listen over the port 5555, then stop and restart the daemon.
Then on the computer, you'd type:
adb connect 192.168.1.xxx:5555
Then:
adb shell
And it should connect.
Not that this would solve the Odin issue, but it's at least one way to get stuff on/off the phone when the drivers crap out.
zzd4nzz said:
-Uninstall Samsung Drivers
-Uninstall USB Root Hub
-Restart Computer (On boot up, the computer will automatically install USB Root Hub)
-Install Samsung Drivers
-Hold down Vol - while plugging into phone to get into download mode
-Odin will hopefully recognize the phone.
Click to expand...
Click to collapse
Thanks to all you guys,
But! I tried every thing, uninstall samsung, uninstall usb hub, reinstall drivers.
I am ready to just sell my fascinate and get an Straight Talk phone to have peace of mind.
Please Help
http://forum.xda-developers.com/showthread.php?t=1065727
Which rom and kernel are you using?
(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!
When I connect my nook tablet to the computer, it does not recognize it as an abd device even though my nook says it is in usb debugging mode.
You need to get drivers working. Search around this forum; there's plenty of guides and videos to help you get started.
Sent from my NookTablet using Tapatalk
useful link
Driver fix for nook tablet (for when you follow instructions exactly)
http://forum.xda-developers.com/showthread.php?t=1363652
.
ooh, useful utility... USBDeview
Thank you so much. I feel pretty dumb now. Thought it was more complicated than that.
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.
Anyone using CM10.1 managed to use DriveDroid? I'm trying to boot Ubuntu but Windows just say that I need to format the driver, I don't know if it's a CM related, MTP or my issue :cyclops:
Please read forum rules before posting
Questions and help issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
Don't look at what Windows thinks of the disk. Windows doesn't recognize the structure of the disk, so it suggests to format it.
What does matter is whether your bios recognizes the disk as bootable. The structure of the disk is usually not the problem if you downloaded the image from DriveDroid: it is the same as anyone else downloading the image. If booting from your phone does not work it usually has something to do with timing/the software on your phone (ROM/kernel). If you indeed can't boot from your phone, I'd suggest to do the following:
Go to preferences of DriveDroid.
Turn off UMS and turn it back on again.
Reboot your phone.
See whether that helps. It worked for some people, but it doesn't have a 100% successrate.
hipgnose said:
Anyone using CM10.1 managed to use DriveDroid? I'm trying to boot Ubuntu but Windows just say that I need to format the driver, I don't know if it's a CM related, MTP or my issue :cyclops:
Click to expand...
Click to collapse
Same here. Really disappointing it doesn't work. I can't tell you how often I thought about boot an image from my phone. In fact, I think I posted the question on XDA a few years ago.
Hey guys, developer here. A few things that might help:
The ISOs that are in DriveDroids downloadlist are all hybrid. This means they are specially crafted to be compatible with USB as well as CD. This is great, because at the moment Android devices only correctly emulate USB drives.
When selecting such an image, Windows will show it as an USB disk. However, Windows does not recognize the format that is used on the disk, because it's hybrid. Therefore Windows suggests to format the disk with a filesystem that Windows recognizes (FAT or NTFS). Do not do this, it'll just blank out the image, which isn't what you want.
Bioses however should be able to recognize the USB disk as a bootable one.
The USB-disk emulation is what in Android is called UMS (USB Mass Storage). On oldish devices this was used to share the SDcard with the PC. DriveDroid uses the same mechanism, but not on the SDcard, but on files (ISO/IMG). Downside is that this mode isn't by default enabled on modern devices, so you usually have to switch from MTP (the system in use to share SDcard in modern devices) to UMS. Such an option is available in DriveDroids menu. However on some devices this switch does not work correctly atm. I have no idea why, but from others I have heard that you can make the option work on these devices. You'll have to rapidly switch the UMS option on and off and end with UMS being on. It *should* popup on your PC when you have a USB cable plugged in. For others it helped to reboot the phone too, but I'm not too sure why this works.
Hopefully that helps solve the problems.
FrozenCow said:
You'll have to rapidly switch the UMS option on and off and end with UMS being on. It *should* popup on your PC when you have a USB cable plugged in.
Click to expand...
Click to collapse
Funny you suggested this. Last night while trying to make it work (thinking the image didn't download correctly the first time), I did the same thing.
jdgiotta said:
Funny you suggested this. Last night while trying to make it work (thinking the image didn't download correctly the first time), I did the same thing.
Click to expand...
Click to collapse
Oh were you also one of the people who send me a support email about this by any chance? I learned about this from those.
In any case, good to hear another confirmation on the method. It's weird, since I'm not too sure why this works yet (it just enables and disables UMS on my device), but I'll put something in the next version to emulate the same behavior.
FrozenCow said:
Oh were you also one of the people who send me a support email about this by any chance? I learned about this from those.
In any case, good to hear another confirmation on the method. It's weird, since I'm not too sure why this works yet (it just enables and disables UMS on my device), but I'll put something in the next version to emulate the same behavior.
Click to expand...
Click to collapse
No, I didn't send the report. I tried it on a whim, but didn't it work.