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?
Related
Hello! I just rooted my Eris yesterday and when I plug my phone into my computer it doesn’t come up on my phone and ask me how I want to dock it (it is checked to ask on the phone itself) . When I first plugged it in and it tried to install the drivers it failed. Over at developer.android.com where I got and installed SDK it said to use pda.net to install drivers, which I did. So now my computer recognizes the phone and I can push apps over however the phone still will not give me the option to mount as a drive. Is there anyway I can make it mount so I can browse files in file explorer. Thank you in advance.
i'm assuming you are on a Windows PC...
firstly, are you able to mount as storage in Recovery?
also, not sure about the pdanet method (never used it)... but i know that if you install HTC Sync it should work fine (link below).
http://www.htc.com/us/support/droid-eris-verizon/downloads/
i'm assuming you are on a Windows PC...
Click to expand...
Click to collapse
Sorry, yes. Windows Vista 32bit
To be honest, I'm not sure what I did but it works now. I plugged it into my laptop to charge and it wanted to mount with no problems. I Just tried it on my PC and it also worked. Even worked with the same usb cord I used last night so that rules out a cord problem
Thanks though. I didn't even think about trying it in recovery mode. If it happens again I will see where that gets me
my lappie which is a
Windows Vista 32 bit
it is not detecting the APX mentioned in the thread
http://forum.xda-developers.com/showthread.php?t=861950
Now I am fixed in a reboot loop and I have tried everything suggested in this thread
OK I know I had no business doing this because I dont know the D of developing....
but the TNT Lite worked so well and was so easy to install I got carried away by it and tried to install the amd to let my computer detect the gtab. this is where I got stuck!!
to start from the beginning
I installed TNT lite on my GTab and it worked really well, I could see Youtube videos and access the Android market
Then I thought I should maybe transfer a few files to the Gtab so I could view them, but when I tried to do that I found out it was another long process, Normally being a non developer I would have probably just tried to find out a non hacking method to do this like download it from gmail or something. Or just use an SD card
But it had been so easy to install the alternate ROM from instructions in this forum I thought maybe it wouldnt be a big issue..sad!!
It was!
Now my one day old GTab wont start up and if it does it just keeps displaying a weird kind of screen with squares on it which I am assuming is the reboot screen
And so I tried to use Nvflash to restore it like mentioned in the thread above but my lappie wont detect it at all..
So now I really need help before I attempt anything else on my own
I dont want to send my Tablet back and would appreciate any help from experienced developers like you guys...!
Please do help me and I promise never to attempt something like this again..!!
Thanks
please !!!! anyone!!!!!
First, I think you need to breathe. Patience is a virtue. *NOTHING* about being excited will help. So calm down first, then go.
Did you install the drivers listed on that page?
Here's a direct link:
http://www.myadventvega.co.uk/SystemUSB.zip
Getting them to install can be a bit tricky, though, since it's not an executable. Download it, unzip it, go into the Flash USB folder, go into the USB folder, right click on the nvidiausb.inf file, and select install. That *should* install the driver. However, it might not. If it doesn't, post back and say what happened.
And as far as transferring files - there's no need to hack to do that. Just connect via USB, pull down the USB attachment notification on your tablet, and say connect. Then drag and drop on the computer. Done.
tedlogan42 said:
First, I think you need to breathe. Patience is a virtue. *NOTHING* about being excited will help. So calm down first, then go.
Did you install the drivers listed on that page?
Getting them to install can be a bit tricky, though, since it's not an executable. Download it, unzip it, go into the Flash USB folder, go into the USB folder, right click on the nvidiausb.inf file, and select install. That *should* install the driver. However, it might not. If it doesn't, post back and say what happened.
Done.
Click to expand...
Click to collapse
Thanks, I think I did forget to breathe..
It says " the inf file you selected does not support this method of install"
Alright. Crap. I forgot that happened to me too when I had to do it.
I think I had to install it via using Device Manager. Here's how you can get to it in Vista (I'm about to sleep, so I'm saving typing time):
http://windows.microsoft.com/en-US/windows-vista/Open-Device-Manager
Once you've got that open, go ahead and boot the tablet into APX mode, meaning that from a powered-off state, you'll hold down the power and volume - buttons simultaneously until your G-Tab comes up and the goes back to a black screen (words stolen from the original NVflash post).
Connect it to your computer (while Device Manager is opened). When you connect it, you should see a new device appear that is labeled Unknown Device. Right click on it, and select Properties. Click the Driver tab (may be different - I'm on 7, but I think it's the same). Click the Update Driver button. Choose the "browse my computer for driver software." Using the browse function, point it to the folder with the inf in it (%wherever_you_extracted_it%\System USB\Flash USB\USB). Click Next.
I think that's what I had to do on mine when I borked my tablet with an experimental build of Vegan Ginger. If the driver installs, that should allow you to then go on with the rest of the directions. If it doesn't, post more information. I can't promise I'll be on any time soon, but maybe someone else can help out if they're up.
ok it says at the end when I have pointed it at the driver file (NVidiaUsb.inf)
"The folder you specified doesnt contain a compatible software driver for your device. If the folder contains a driver make sure that it is designed to work with windows for 32 bit systems."
This is what happened last time also, and then the system says that I already have the most compatible driver for the system and puts me on "Microsoft WPD filesystem volume driver"
EDIT: I should mention that I also had a tough time deleting my NVidia driver, but as soon as it was deleted, it was automatically replaced by the "Microsoft WPD filesystem volume driver"
Not sure what to tell you. The INF clearly points to the x86 version, so it should install. Is there more than one unknown device in your device manager? If so, you might somehow have the wrong one, though the approach earlier should have made it easier to track the new one.
Sorry. You might want to try getting on IRC to see if other people have some bright ideas. An NVFlash does seem like what you need to do, though.
EDIT: I did some digging into the forums (you should probably continue that). Here's a thread all about these drivers.
http://forum.xda-developers.com/showthread.php?t=1012009&highlight=NVFlash+USB+Driver+Solution
If those fail, there's another method that involves installing the entire SDK, which is linked on this thread (the second post about the MSI):
http://forum.xda-developers.com/showthread.php?t=882814
However, my impression is that that option might create more complexity than it's worth.
I haven't done anything but what I explained earlier (if I remember right - it's been a while), so I can't talk about any other approach. However, these will at least maybe make my failure into less of a dead end.
I ran into the exact same problem a few weeks ago after installing CM7...
http://forum.xda-developers.com/showthread.php?t=902860&highlight=usbdeview
I used a program called USBDEVIEW and just obliterated all the usb drivers (I guess the safe way is to remove any mention of Nvidia usb devices) and rebooted the computer. Let the system reinstall all the USB devices. Restarted the computer again. AND ONLY THEN did I plug in the gTablet. Once plugged in, the system automatically installed drivers and recognized the tablet, you may have to point to the inf file if it fails to install automatically.
USBDeview from CNet
http://download.cnet.com/USBDeview/3000-2094_4-10614190.html
Good luck!
Don't let this setback keep you from using great ROMS like VEGAn Tab Gingerbread RC1... once you've mastered the NVFlash process and CWM recovery install (I prefer the external CWM install) you are all set for other mishaps.
http://forum.xda-developers.com/showthread.php?t=865245
supergroverthm said:
I ran into the exact same problem a few weeks ago after installing CM7...
http://forum.xda-developers.com/showthread.php?t=902860&highlight=usbdeview
I used a program called USBDEVIEW and just obliterated all the usb drivers (I guess the safe way is to remove any mention of Nvidia usb devices) and rebooted the computer. Let the system reinstall all the USB devices. Restarted the computer again. AND ONLY THEN did I plug in the gTablet. Once plugged in, the system automatically installed drivers and recognized the tablet, you may have to point to the inf file if it fails to install automatically.
USBDeview from CNet
http://download.cnet.com/USBDeview/3000-2094_4-10614190.html
Good luck!
Click to expand...
Click to collapse
I tried to uninstall the nvidia drivers using USB deview, it asked me if I wanted to uninstall drivers I said yes but I can still see the drivers in the USB list
Is that ok?
You need to run USBDeview as an administrator. Right click on "USBDeview.exe" select "run as administrator" and then when you are asked to confirm, click "yes"
Only then when you "uninstall selected device" the device will disappear. Otherwise you are only in view mode.
supergroverthm said:
You need to run USBDeview as an administrator. Right click on "USBDeview.exe" select "run as administrator" and then when you are asked to confirm, click "yes"
Only then when you "uninstall selected device" the device will disappear. Otherwise you are only in view mode.
Click to expand...
Click to collapse
OK I just figured that out and was coming to post that. Thanks for realising that is what I was doing..
I conneccted the tablet to my PC.but it still does not detect it
The only time my PC detected it was the first time when I pointed it to the nvflash folder. After that it has never detected it and I havent seen the yellow ! icon.
what am I doing wrong?
Firstly, powerdown the gTab.
Turn on power while holding "vol -" to enter into APX mode (you'll see the viewsonic birds then the screen will go blank)
On the bottom right corner of the Vista screen, click on the USB icon that says "safely remove hardware and eject media"
Look at the list the pops up, does one of the devices say APX?
no It only says safely remove mass storage device
oh wait
my tablet switched on to the reboot screen and didnt stay black
trying it again
it installed "NVIDIA boot recovery driver for mobile devices", is that correct?
This is where I get stuck, my device manager doesnt show the apx at all whatever I do, what am I doing wrong?
I think there was a way to overlook safety signatures somewhere but I couldnt get to do it,
Is there some way I can ask my computer to overlook the safety signatures?
EXCELLENT!!! Now you are ready for NVFlash instructions:
http://forum.xda-developers.com/showthread.php?t=861950
BTW, you will not be able to see the device under windows explorer as in the normal way such as "D:" "E:" etc drive.
Once you get everything setup per the above instructions and run "nvflash_gtablet.bat" you will see the flashing process in the text box.
Just want to make sure...
Under Vista Device Manager
-- "universal serial bus controllers" you have "NVIDIA USB Boot-recovery driver for Mobile devices"
supergroverthm said:
Just want to make sure...
Under Vista Device Manager
-- "universal serial bus controllers" you have "NVIDIA USB Boot-recovery driver for Mobile devices"
Click to expand...
Click to collapse
Yes I do, so I should start the process now?
THANKS a lot, will update you as it goes on.
Yes, follow Roebeet's instructions and you should be set. Also play it safe and keep your gTab plugged in unless you are sure of the amount of battery life left.
I cannot seem to get Novacom drivers installed for my Touchpad. I've tried rebooting both machine and touchpad, taken TP in and out of dev mode, tried every command line I could find for running the novacom installer, etc. I am at a loss, cannot get it to work at all. Tried searching but didn't come up with anything for novacom
I'm trying to do this while at work and am on a netbook with windows 7 starter.
Appreciate any help
OK sorry for sounding stupid but have you run the universal novacom installer? If so, what happened?
Sent from my HTC Desire S using xda premium
dan-fish said:
OK sorry for sounding stupid but have you run the universal novacom installer? If so, what happened?
Sent from my HTC Desire S using xda premium
Click to expand...
Click to collapse
Yes, I get a message that says it has been successfully installed, but when I plug in the TP it isn't recognized. Cannot mount as USB either
Doesn't sound like a novacom issue. Maybe someone else can spread some light here
Sent from my HTC Desire S using xda premium
Would be much appreciated.
FWIW, I did get it to be seen by quick install the very first time I plugged it in but it immediately dropped it and hasn't seen it since.
I got it to see it briefly on a different computer. Now when I put it in recovery mode it comes up as unknown device again. I want to throw this [email protected]#$& thing!
Please, can someone help me out here.
I have gotten it to the point that it is seen until I put it into recovery mode. Once I put it in recovery mode and plug it in, I get device not recognized.
In an effort to remedy that issue, I wiped everything touchpad related on my computer clean to start again. Now I'm back to square one. Device not recognized and cannot mount to USB Mass storage. What the F am I missing here. Why does it work one second and not the next?
In vein, I tried to install using my old iBook but even that didn't work(thanks Steve!)
I've also moved from the netbook I was trying to install from last night, to my normal win7 machine.
Would really appreciate it if anyone is willing to work with me to resolve this
Haha. I had this same issue. i wish it would be added to the tutorial's OP. Anyway, make sure you are putting acmeinstaller in the folder . Crogram Files, Palm, Inc where the actuall Novacom drivers are. Then enter the C prompt and you're good to go. If you don't have x64 put the ACMEInstaller file wherever your computer has Palm Inc and that is the directory you CD to.
i.e. for me it was cd c:/program files/ palm inc
Ended up using an XP machine to install. Took just a few minutes. Drivers were found right away unlike in 7.
blackwrx02 said:
Ended up using an XP machine to install. Took just a few minutes. Drivers were found right away unlike in 7.
Click to expand...
Click to collapse
My issue with Win7/64bit were the path/file location.
Even if you download the drivers and install them correctly, you still have to execute the novacom ext.
It's in the prog files\palm folder, as said.
Had a heck of a time myself until I realized this.
dajogejr said:
My issue with Win7/64bit were the path/file location.
Even if you download the drivers and install them correctly, you still have to execute the novacom ext.
It's in the prog files\palm folder, as said.
Had a heck of a time myself until I realized this.
Click to expand...
Click to collapse
For people searching for the answer.
I'm on win7 64 bit. The universal novacom install went fine. Plugged in touchpad and ran command, but novacom did not find device.
Moved usb connection to different usb port on my computer, magic.
Novacom commands worked and installed cyanogen 9.
If moving usb ports doesn't work. Disconnect usb cable, uninstall novacom via control panel, software removal. Then, reinstall novacom, and use 2nd usb port.
I seached the web, and none of these questions about novacom not finding device was answered. The above is the answer. Move usb ports.
(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!
So I have a Samsung Vibrant(just got it recently) and I'm having problems when i connect it to the computer. It gives me an USB device not recognized on my windows 8 computer. I have spent all morning searching and reinstalling drivers and trying my old pc and new cables and i found out that my old windows 7 computer with 4GB of ram and an overloaded hard drive will detect my device the problem there is it not my main computer and i dont want to have to connect all the vga cables boot it up connect mouse and ect to use this computer just to be able to copy files, and do other things from my computer to my phone I dont know why my main computer dell inspiron windows 8 will not work when it was a couple of days ago when i had a problem with conectivity and had to flash back to stock but now it wont connect. could someone help me? Here's a list of things i've tried
installing kies
installing adb again
aoi tool and then drivers
a bunch of diffrent drivers found on the fourms
diffrent usb cable
i would like to be able to do it on my main computer but its not working if someone could help that would be great
also please dont hate on me for having windows 8 jk i dont care :good:
I'd have to say that your drivers are all scrambled. Look up "android SDK" here on xda and install that for a bigger variety of drivers. Or just download Google's USB driver and manually install it through device manager which always works for me. Windows 8 is new and very complicated.
Vono123 said:
I'd have to say that your drivers are all scrambled. Look up "android SDK" here on xda and install that for a bigger variety of drivers. Or just download Google's USB driver and manually install it through device manager which always works for me. Windows 8 is new and very complicated.
Click to expand...
Click to collapse
I will try this when I get home from school this afternoon but i have tried downloading android SDK(adb correct?) and then going into device manager and then going to downloads/adb/sdk/exstras/google/usb drivers and it never finds anything.
apples723 said:
I will try this when I get home from school this afternoon but i have tried downloading android SDK(adb correct?) and then going into device manager and then going to downloads/adb/sdk/exstras/google/usb drivers and it never finds anything.
Click to expand...
Click to collapse
Android SDK is installed in the main drive right? local disk c?
You have to click the folder (usb_driver) and then click update.
In the android sdk folder there should be and exe file called SDK manager. There you will be able to download all the drivers for your current android version also the latest Google drivers and SDK tools etc.
I was stuck on this process for a long time because it allways works different for everybody. Just keep me posted on what you do I'm more than glad to help.
Vono123 said:
Android SDK is installed in the main drive right? local disk c?
You have to click the folder (usb_driver) and then click update.
In the android sdk folder there should be and exe file called SDK manager. There you will be able to download all the drivers for your current android version also the latest Google drivers and SDK tools etc.
I was stuck on this process for a long time because it allways works different for everybody. Just keep me posted on what you do I'm more than glad to help.
Click to expand...
Click to collapse
everything is up to date in the sdk manager do i need to reinstall it? also it still wont find the drivers i have atatched some png files take a look the picktures and it will show you the where the drivers are and what im selecting
EDIT****
I forgot to mention i tried it at school on a windows 8 computer and it worked fine its my crappy computer thats only five months old
apples723 said:
everything is up to date in the sdk manager do i need to reinstall it? also it still wont find the drivers i have atatched some png files take a look the picktures and it will show you the where the drivers are and what im selecting
EDIT****
I forgot to mention i tried it at school on a windows 8 computer and it worked fine its my crappy computer thats only five months old
Click to expand...
Click to collapse
So what exactly happens when you click update? What does it say?
Is your PC up to date? (update wise)
Do you have the the drivers for the phone itself like samsung drivers?
And did you try rebooting your PC after installing your drivers? <-- that is important. You should always reboot after install or uninstalling drivers otherwise you'll end up scrambling them.
From the pictures it shows you have the drivers but I'd also try going deeper than usb_driver, try clicking on i386 or amd64.
Vono123 said:
So what exactly happens when you click update? What does it say?
Is your PC up to date? (update wise)
Do you have the the drivers for the phone itself like samsung drivers?
And did you try rebooting your PC after installing your drivers? <-- that is important. You should always reboot after install or uninstalling drivers otherwise you'll end up scrambling them.
From the pictures it shows you have the drivers but I'd also try going deeper than usb_driver, try clicking on i386 or amd64.
Click to expand...
Click to collapse
i have the latest update from microsoft and yes i have the drivers for my phone itself and i rebooted a right after i installed the drivers and then unisntalled and i have gone into i386 and amd64 give me a second and i upload a picture of the error
EDIT
i uploaded the pictue of the error im getting
apples723 said:
i have the latest update from microsoft and yes i have the drivers for my phone itself and i rebooted a right after i installed the drivers and then unisntalled and i have gone into i386 and amd64 give me a second and i upload a picture of the error
EDIT
i uploaded the pictue of the error im getting
Click to expand...
Click to collapse
OK make sure there are no HTC drivers on your PC. When you hook up your phone does USB storage work or anything like that?
Check those out and then I want you to go to Google, download pdanet latest version via pc (dont install yet) and go to the play store and install on your phone turn on USB debugging and the install non market apps and hook your phone up to the computer. Then install pdanet via PC and see if that works. HTC drivers get in the way of Samsung's BTW.
Vono123 said:
OK make sure there are no HTC drivers on your PC. When you hook up your phone does USB storage work or anything like that?
Check those out and then I want you to go to Google, download pdanet latest version via pc (dont install yet) and go to the play store and install on your phone turn on USB debugging and the install non market apps and hook your phone up to the computer. Then install pdanet via PC and see if that works. HTC drivers get in the way of Samsung's BTW.
Click to expand...
Click to collapse
you want me to install pdanet on my phone too and by the way there is no htc drivers that are on my computer
apples723 said:
you want me to install pdanet on my phone too and by the way there is no htc drivers that are on my computer
Click to expand...
Click to collapse
OK good and yes its in the play store for free but I don't think you have to install it but it makes the process more easy for ya.
You do have usb debugging and install non market apps checked right? You need those on.
Vono123 said:
OK good and yes its in the play store for free but I don't think you have to install it but it makes the process more easy for ya.
You do have usb debugging and install non market apps checked right? You need those on.
Click to expand...
Click to collapse
still giving me the error i think its my computer because it works on our family laptop school computer and basment computer how do i totally unistall drivers not from device manager theres a difrent way i think not sure
apples723 said:
still giving me the error i think its my computer because it works on our family laptop school computer and basment computer how do i totally unistall drivers not from device manager theres a difrent way i think not sure
Click to expand...
Click to collapse
I want you to uninstall all your Samsung drivers(not android SDK) under control panel/uninstall programs. If you see something like Samsung kies definitely uninstall it. Reboot your computer and follow this guide for windows 8:
http://forum.xda-developers.com/showthread.php?t=2038555
After this if it doesn't work I'd recommend pulling out your old computer for android modding lol. I'll still look up some threads for your problem. Let me know what's going on after that. Make sure when you follow that guide your phone can not be plugged in the computer. And when you plug your phone into the computer after everything is done and after you reboot your computer for the second time, USB debugging has to be off and when phone is done unplug and turn back on USB debugging and plug back in and wait for that. Adb should work.
[Edit] you can also try running your drivers in windows 7 compatibility. Sorry I couldn't help much.
Vono123 said:
I want you to uninstall all your Samsung drivers(not android SDK) under control panel/uninstall programs. If you see something like Samsung kies definitely uninstall it. Reboot your computer and follow this guide for windows 8:
http://forum.xda-developers.com/showthread.php?t=2038555
After this if it doesn't work I'd recommend pulling out your old computer for android modding lol. I'll still look up some threads for your problem. Let me know what's going on after that. Make sure when you follow that guide your phone can not be plugged in the computer. And when you plug your phone into the computer after everything is done and after you reboot your computer for the second time, USB debugging has to be off and when phone is done unplug and turn back on USB debugging and plug back in and wait for that. Adb should work.
[Edit] you can also try running your drivers in windows 7 compatibility. Sorry I couldn't help much.
Click to expand...
Click to collapse
ive tried so many things i give up it makes me mad that any other computer even ones with windows 8 on them it works fine with out any sepecial installation but on my current computer it doesnt
apples723 said:
ive tried so many things i give up it makes me mad that any other computer even ones with windows 8 on them it works fine with out any sepecial installation but on my current computer it doesnt
Click to expand...
Click to collapse
I think I know what the problem is. Make sure you uninstall all the previous drivers, then have the correct drivers ready.
What you have to do is to disable driver signature enforcement.
Step 1. Go to the right bottom corner of the desktop and wait for the side menu to appear. When it's there click on the gear icon with the title "Settings".
Step 2. Now click on the entry "More PC Settings", then click on the entry "General".
Step 3"Restart now" (under "Advanced start up ") and click it.
Step 4. Now click "Troubleshoot", then "Advanced Options" and after that click "Windows Start up Settings".
Step 5. Click on "Restart" and wait, then on the next screen press F7.
You will now reboot, and try now to install the drivers (by manually selecting the folder in device manager).
I'm not sure what is the correct drivers for you.
But try this. It's still worth a shot.
binaryfalcon said:
I think I know what the problem is. Make sure you uninstall all the previous drivers, then have the correct drivers ready.
What you have to do is to disable driver signature enforcement.
Step 1. Go to the right bottom corner of the desktop and wait for the side menu to appear. When it's there click on the gear icon with the title "Settings".
Step 2. Now click on the entry "More PC Settings", then click on the entry "General".
Step 3"Restart now" (under "Advanced start up ") and click it.
Step 4. Now click "Troubleshoot", then "Advanced Options" and after that click "Windows Start up Settings".
Step 5. Click on "Restart" and wait, then on the next screen press F7.
You will now reboot, and try now to install the drivers (by manually selecting the folder in device manager).
I'm not sure what is the correct drivers for you.
But try this. It's still worth a shot.
Click to expand...
Click to collapse
didnt make a difrence still getting error i think its something with my system so i guess without a full diagonostic it wont work