Related
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 am new to the Android platform so please excuse any silliness on my part…
Below are the steps I took to successfully allow my Vizio Tablet (VTAB108) to connect via USB using the generic Google ADB driver as Vizio does not include ADB access for the tablet.
History:
I am trying to Root my tablet and from what I read throughout the forum, the easiest steps to root a tablet is using the SuperOneClick method.
Since SuperOneClick requires ADB access and the Vizio does not include the ADB driver (and the generic Google) do not work out of the box I was at a loss to how I would run SuperOne Click.
This article are the steps I took to get ADB access working with Windows 7 x64 and the Vizio Tablet.
I am hoping my steps here can further lead to root access for this tablet.
As an FYI, I was still unsuccessful in getting SuperOneclick to completely run after following these steps, but maybe someone has an alternate method of rooting now that ADB access is available? /me crosses fingers
It would stop at Step #6 at which time I would disconnect and reconnect the tablet. It would contine to step #8 but then finally fail. If anyone has an alternative to SuperOneClick, I would gladly try it.
IMPORTANT:
The instructions below assume you have already put your Tablet into USB debugging mode.
The instructions below assume you are running Windows 7 x64. If you are running x32 versions of your OS, modify the below settings as apporopriate for your OS[/B].
1. Download and install the Google Android SDK.
(Being this is my first post, I cannot post a URL so google the following topic exactly and click the first link):
what-is-adb-and-how-to-install-it-android
2. When you get to the USB driver install you will have to manually modify your android_winusb.inf settings file to allow Windows to recognize your Vizio Tablet using the generic Google ADB-USB driver.
3. Find the "usb_driver" folder in your sdk directory. (Mine was: C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver).
4. Right-click "android_winusb.inf" and open it with notepad or your favorite text editor.
Under the [Google.NTamd64] section, paste the following:
Code:
;Vizio Tablet
%SingleAdbInterface% = USB_Install, USB\VID_0489&PID_E040&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_0489&PID_E040&REV_0227&MI_01
then, open a command prompt and type the following:
Code:
echo 0x489 >> "%USERPROFILE%\.android\adb_usb.ini"
5. Right-Click the unknown device in Windows Device Manager (Under Other devices) and manually install the driver for your Tablet.
NOTE: Originally my tablet connected to the computer and installed the regular Windows 7 Mass Storage driver. I had to remove this driver before I could see the device listed under "Other Devices". Follow these instructions if you need to remove your generic Mass Storage driver:
Code:
A. Unplug all removable devices (USB drives, Thumb Drives, SD Cards, Etc...) but leave the Android phone plugged in.
B. Open Windows Device Manager.
C. Select "Universal Serial Bus Controllers"
D. Select USB Mass Storage Device.
IMPORTANT: Click on the details tab and select "Compatible Ids" under the Property drop-down. You should see three items listed under Value. If not, you are looking at the wrong Mass Storage Controller.
E. Select Uninstall Driver
F. Close the window.
G. Right-Click your computer name at the top of device manager and select "Scan for Hardware Changes".
H. Your new "Android Phone USB device" with a Yellow Exlamation mark! will appear under Other Devices.
I. Click on the "Android Phone USB device"
J. Select "Update driver software"
J. Select "Browse my computer for driver doftware"
K. Browse for the location that you have unzipped the android_usb_windows ( Mine is: C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver )
6. Now test to make sure you can access your device in USB Debug mode:
Type the following from a command prompt:
adb kill-server
adb devices
You should see your device serial number at the command prompt and in Windows Device Manager if everything worked.
drivers
USB Drivers have been posted on the vizio support website for Intel and for AMD. Are they crucial to what you want to do about rooting?
USB Drivers Not Installing
[email protected] said:
USB Drivers have been posted on the vizio support website for Intel and for AMD. Are they crucial to what you want to do about rooting?
Click to expand...
Click to collapse
I grabbed those drivers a couple of days ago and could not get Win7 or WinXP to install them with the vtab1008.
I can use adb to interface with the vtab008 (using Linux and Win7), but GingerBreak and SimpleOneClick (which uses GingerBreak) are unable to root the vtab1008.
I've been pestering Vizio about the downsides of the tablet. Coming from a rooted Nook, there are some things about the vizio i really like. It's a nice build at an attractive cost. If I can get netflix and hbo go working, a better remote app and a more logical system of using the sd card, I would keep it. Otherwise it goes back to Costco on the 89th day after purchase.
Agreed
[email protected] said:
I've been pestering Vizio about the downsides of the tablet. Coming from a rooted Nook, there are some things about the vizio i really like. It's a nice build at an attractive cost. If I can get netflix and hbo go working, a better remote app and a more logical system of using the sd card, I would keep it. Otherwise it goes back to Costco on the 89th day after purchase.
Click to expand...
Click to collapse
This is my thinking EXACTLY!
[email protected] said:
I've been pestering Vizio about the downsides of the tablet. Coming from a rooted Nook, there are some things about the vizio i really like. It's a nice build at an attractive cost. If I can get netflix and hbo go working, a better remote app and a more logical system of using the sd card, I would keep it. Otherwise it goes back to Costco on the 89th day after purchase.
Click to expand...
Click to collapse
Yes, I agree. If there's no root, the tablet is not worth it.
The drivers worked for me.
I downloaded the drivers from the Vizio site and when I plugged the VTAB into my computer I manually installed the driver. I just used adb to grab a bunch of screenshots.
OP worked for me (without the mass storage issue)
Code:
adb reboot bootloader
just did a true reboot
Code:
adb reboot recovery
got me the exclamation mark and the "Home" button brought me to a recovery screen where it would let me flash signed updates or cache/full wipe the device.
You can get to recovery mode by holding down both volume buttons and the power button. Details
I cant even get the drivers to install. I've did a right click on the .inf file and it will not install. Any Ideas?
Thanks
Mark
Mark0266 said:
I cant even get the drivers to install. I've did a right click on the .inf file and it will not install. Any Ideas?
Thanks
Mark
Click to expand...
Click to collapse
DL the drivers from the Vizio site. Turn on USB debugging on the VTAB. Plug the VTAB into your computer. When the install driver prompt comes up follow the steps to install a driver from a specific location and point it to the driver you downloaded. The steps will vary depending on the version of windows you are running.
marvin02 said:
DL the drivers from the Vizio site. Turn on USB debugging on the VTAB. Plug the VTAB into your computer. When the install driver prompt comes up follow the steps to install a driver from a specific location and point it to the driver you downloaded. The steps will vary depending on the version of windows you are running.
Click to expand...
Click to collapse
Thats the problem the prompt never comes up. Running Windows 7
Well I got the driver for adb to install but it still will not show up when I do adb devices
Bootloader?
the.joeba said:
OP worked for me (without the mass storage issue)
Code:
adb reboot bootloader
just did a true reboot
Code:
adb reboot recovery
got me the exclamation mark and the "Home" button brought me to a recovery screen where it would let me flash signed updates or cache/full wipe the device.
Click to expand...
Click to collapse
Did you actually get into the bootloader? adb reboot bootloader simply reboots the device for me.
So whats with gingerbreak? No love with it? I thought this thing was rooted already prior to shipping? Hmmm. My bro just ordered one for me and I am curious about getting it rooted. Lets get this thing rooted and overclocked and get it some love. Also, whats the word on honeycomb on this beast? anything?....
Mark0266 said:
Well I got the driver for adb to install but it still will not show up when I do adb devices
Click to expand...
Click to collapse
Same here.
Rooting help
I have some coding knowledge, but have never worked on rooting a device. I did not pay for mine, so if anyone has references to some info I can look at about obtaining root then I will work on mine without fear of bricking it.
I have been at this for weeks, to no avail.. tried changing params in Gingerbreak, tried running it under every condition possible, and the only thing I haven't tried is changing how GingerBreak is using the /sdcard/ mount point, as that's where the internal memory is mounted to.. It's a pretty odd move to make, and I don't like having my true sdcard in /sdcard/external. what a crock :/
This tablet has to have a way to be rooted, I tried an older version of gingerbreak 1.1 just kept running, never failed, but didn't root the tablet just kept running, like it was gonna root the tablet, kinda weird, I do know that the bootloader is not locked down, my wife works for vizio, the company gave there employees a tablet for free
Currently I'm trying this guide:
Nook Tablet "One Click Root" + gapps ADB script
but I've been trying various guides all day. The drivers are there, debugging enabled, auto mount disabled, robot in the bottom corner but when I run ADB Devices, no dice. Anyone have any clues what the problem could be or atleast anyone else having this problem? At first I thought it might be because I was using a different USB cord but it still doesn't work even with the Nook cord
The problem you describe is almost guaranteed to be a problem on your computer and the driver installation.
For the folks here to help, they will need to know platform (PC or mac) and version of operating system.
If Windows, they will need to know how the device appears to Device manager. If it shows up as a disk drive - you will have to disconnect from the Nook side. ADB Composite should be good.
For either platform, confirm that adb_usb.ini is in the right place and modified correctly.
No, you're wrong dude above me.
OP: Run this in cmd prompt
Code:
echo 0x2080 > %username%\.android\adb_usb.ini
You need to have your nook tablet unplugged when you run that then you would see nook tablet in the device manager when you plug it back in.
Indirect said:
No, you're wrong dude above me.
OP: Run this in cmd prompt
Code:
echo 0x2080 > %username%\.android\adb_usb.ini
Click to expand...
Click to collapse
"Cannot find the path specified." But I can locate the file myself in that directory??
I'm running Windows 7 64-bit, device shows up as android phone>androud ADB interface.
My bad it's
Code:
echo 0x2080 > "%USERPROFILE%\.Android\adb_usb.ini
Check, still nothing in ADB, i did restart the server too. To be clear, the .ini file only has the "0x2080" line in it now, nothing else. I'm assuming that's ok because the other stuff was commented out anyway, am I right?
(thanks for your help! )
1) look in device manager now though, you need to install the drivers.
I still see it listed under android phone > android ADB interface and not mass storage or anything like that, you think that's still the problem though?
*Edit*
SUCCESS!! I uninstalled the "Android ADB Interface" and "Android Composite ADB Interface" appeared in its place!!(??) Whatever happened the device show up now. Thanks for the help and keep up the good work Indirect!
Indirect said:
My bad it's
Code:
echo 0x2080 > "%USERPROFILE%\.Android\adb_usb.ini
Click to expand...
Click to collapse
I was having problems seeing the Nook Tablet in adb devices, but this fixed it for me.
I was having the same issue for a bit, restarted my nook and it worked haha.
Sent from my BNTV250 using xda premium
This worked for me. Hopefully it helps.
While the nook is plugged in (mine showed the 2 "Disk Drives" and 2 Drive Letters under portable devices). Open Device Manager and delete/remove the 2 disk drives called "B&N NOOK Tablet USB Device" (this should also remove the weird drive letters under portable devices). Now go to Control Panel > Advanced System Settings > Hardware Tab > then click "Device Installation Settings". Change this setting to "No, let me choose what to do", and make sure "Never install driver software from Windows Update" is checked below that.
Now unplug and replug your NT, and you should now see an Android Composite device with the "!" next to it. You should now be able to install the custom drivers described in the other posts.
Essentially it seems windows is trying to "help" you by guessing at the drivers you want to use.
If this doesn't work, you can try to remove ALL android devices using the USBDeview Application that you can find http://www.androidsim.net/2009/08/how-to-1-how-to-install-usb-driver-on.html
I used USBDeview for the removal part just because I had a Kindle fire, HTC device, samsung device, all installed and I think they were fighting a little bit. I now have results from adb devices, and dare I say ROOT!?!?!
Hope this helps some of you!
Good post - Windows Vista especially, and Windows 7 somewhat, really think they know better than the user when it comes to drivers. Especially unsigned drivers in preference to signed ones...
I found that the best way to do this for people with this problem (such as me), is to go in Device Manager, expand the USB Mass Storage Device selection, search for the USB Mass Storage device of your Nook Tablet (easiest way would be to unplug any other external hd, sd card, ... so that there is only one USB Mass Storage device). At this point, right click and update driver and select the folder manually.
tsubus said:
I found that the best way to do this for people with this problem (such as me), is to go in Device Manager, expand the USB Mass Storage Device selection, search for the USB Mass Storage device of your Nook Tablet (easiest way would be to unplug any other external hd, sd card, ... so that there is only one USB Mass Storage device). At this point, right click and update driver and select the folder manually.
Click to expand...
Click to collapse
I just joined the forum to thank you! I spent hours looking for a solution and yours worked!
brices21 said:
While the nook is plugged in (mine showed the 2 "Disk Drives" and 2 Drive Letters under portable devices). Open Device Manager and delete/remove the 2 disk drives called "B&N NOOK Tablet USB Device" (this should also remove the weird drive letters under portable devices). Now go to Control Panel > Advanced System Settings > Hardware Tab > then click "Device Installation Settings". Change this setting to "No, let me choose what to do", and make sure "Never install driver software from Windows Update" is checked below that.!
Click to expand...
Click to collapse
Well I am stumped here, seriously. I can't get rid of the above mentioned 2 instances of "B&N NOOK Tablet USB Device" no matter what I do. Auto mount is off on the device and the device installation setting is already set to "No, let me choose what to do." Yet every time I plug the NT in- the computer kindly tells me it's "ready for use" and those two "B&N NOOK Tablet USB Device" listings are back. At this point I'm not sure I'm ever gonna be able to get the device to show up under ADB. The computer just won't seem to let it.
Any advice anyone might on this would be greatly, greatly appreciated.
maybe try what Indirect did here: http://forum.xda-developers.com/showthread.php?t=1363652
The website is below what I did to completely disable Windows from installing the Nook drivers every time it is plugged in. I also had the "Never install driver software from Windows Update" checked from Brices21's post but the drivers would still install everytime it is plugged in.
xxxx = http - still a noob, can't post links
yyy = www
xxxx://yyy.addictivetips.com/windows-tips/how-to-disable-automatic-driver-installation-in-windows-vista/
I never actually installed the USB drivers that indirect provided, but "adb devices" still detected the NT when plugged in.
This was my whole process to get "adb devices" to detect the NT:
With the NT plugged in and device manager detecting the 2 Nook devices as drives and 2 Nook devices in "other devices" and with automount disabled and USB debugging enabled
I also ran the runmefirst.bat at some point in time previously, so the necessary files were created already
***** Pulled this from the website above******
* Go to Start–>Search type in gpedit.msc
* Click the file to open the Local Group Policy Editor and show Windows who is in control!!
* You want to go here: Computer Configuration->Administrative Templates->System->Device Installation. Click on the subfolder Device Installation on the left and on the right side you will see the possible restrictions.
* Right Click on Prevent Installation of Devices not described by other policy settings and edit this option, set it on ENABLED.
*************************************
From here the website says to reboot and set the option back to default. I did not reboot or set the option back.
* Going back into device manager, I uninstalled the drivers for the 2 Nook drive devices.
* Unplugged the NT
* Plugged the NT back in
Then I got the B&N NOOK Tablet USB Device with the broken symbol under "Other devices" in Device Manager
* Open cmd and run "abd devices" from the ntroot directory
The service should start and list the NT device as a bunch of numbers.
* From here you can run NookandZergy.bat to root the NT.
After rooting you can set the options in the gpedit.msc back to defaults.
I also tried installing the Indirect provided drivers as the USB mass storage device. Windows then detected the device as an Android ADB Composite device but "adb devices" from cmd prompt would not detect the NT. I ended up removing all of the drivers and repeating my steps to get "adb devices" to detect it again.
Hope this helps! It may not be the best solution but it was a workaround for me to get the NT rooted.
****Update*****
Just got home and tried to install the drivers and it worked this time. I was able to see the NT with "adb devices"
With the gpedit.msc edit intact, I plugged in the NT and Windows detected 2 broken Nook devices under "other devices" and a mass storage device under USB controllers.
* I uninstalled the driver for the mass storage device
* set the gpedit.msc back to "not configured"
* unplugged NT
* made sure debug mode was set and automount disabled
* plugged NT back in
Device manager showed a Mass Storage device under "Other devices"
* Update drivers for that device with the Indirect usb driver
* ran "adb devices" in cmd prompt and NT is detected.
So if there's anything to take away from my post...hopefully you can use the gpedit.msc to completely disable the autoloading of drivers.
Drivers Fixed!
Rooted! Got past driver issues (Android Composite ADB Interface appeared in Device Manager, adb still couldn't detect Nook). Thanks to all who have worked so many hours on this.
Here's what worked for me (using Windows XP 32 bit):
1. make sure "adb_ini" file contains "0x2080" and is located at "%USERPROFILE%\.android"
2. I had to manually edit my "path=" environment variable to include the above location - both in Control Panel->System->Advanced->Environment Variables and in cmd window.
3. carefully followed instructions on proper installation of drivers for "Android Composite ADB Interface". At this point, cmd window use of adb was able to detect Nook (as well as runmefirst.bat).
4. Continued with root process (i.e. NookandZergy.bat)
Hope this helps anyone still having driver issues.
Never had this issue using the trick mac method.
Hi, I have a Scroll Excel tablet and was recently trying to flash CMW5 onto it using a recovery from the scroll forums, however in the command prompt whenever I type in the command ("adb push install-recovery.sh /data/" in case that helps) it says the daemon isn't running, then it starts the daemon, then it says "Error: device not found.
I've checked everything, I have correctly navigated to the folder which holds the recovery, I am entering the recovery name correctly, I do have the Google USB Drivers etc.. installed, the device is plugged in (and the computer knows it is, it detects it) but the prompt doesn't recognize the device.
There is one thing though, whenever I plug it in the computer tells me the device is not recognized, but it at least acknowledges that the device is there. Am I missing any drivers on my tablet's side or what? Thanks
Also, I attached a file of what the prompt tells me below v
I do not have this tablet so I cannot give you an exact answer. However, I would try uninstalling and reinstalling the drivers and restarting your pc. Also try a different usb port.
As stated in the post above, I would check my Drivers. I would also suggest checking your USB Cable. Make sure that it is good. Is your SDK Tools up to date ? BTW that seems like an odd path for your platform-tools folder.
prboy1969 said:
As stated in the post above, I would check my Drivers. I would also suggest checking your USB Cable. Make sure that it is good. Is your SDK Tools up to date ? BTW that seems like an odd path for your platform-tools folder.
Click to expand...
Click to collapse
It can't be the USB cable, I've tried 2 or 3. Also, yes. I updated the SDK tools yesterday. And I know it's an odd path, but I'm a bit OCD about keeping things in folders.
However, about the drivers, the computer says it doesn't recognize the device. And when it scans for the drivers it doesn't find anything to download. Regardless, Storage Options are willing to take a look at it for me (how nice, even with a technically void warranty.) Thanks for your help anyway.
I would definitely recommend re-installing the drivers. Then try again.
TEAM MiK
MikROMs Since 3/13/11
I was unable to find help elsewhere, so I was recommended to come here. No rooting, hacking, reprogramming, or anything else. Just a basic connection problem.
I recently bought a new Solid-State hard drive, and re-installed Windows 7 on it. Everything is great, and it's fully updated.
My problem is that while my LG Optimus G E980 phone will charge via the USB cable, I can't "open" it in My Computer, to transfer pictures, music, etc.
I have tried downloading the driver from LG's Website (LGMobileDriver_WHQL_Ver_4.1.1), but when I run it, I get the following message:
"The Microsoft MTP driver is not found on your system. Please install Windows Media Format Feature Pack using Download Link for your media device to work correctly."
It then provided me with a link to download this. However, when I do that and run the update, I get told the update is not applicable to my computer.
Whether I try to install this update or not, it doesn't matter, because the driver installation tells me it was installed successfully. However, judging by the icon in my Taskbar with the red/white "X" and the fact that my phone still won't connect, it hasn't.
Yes, my phone is set up to ask me what I want to do when connected to the PC, and Media sync (MTP) is selected. Here's the kicker... remember, I have two hard drives. When I boot using the other hard drive, the phone connects with no problem. Same USB cable and port. Therefore, this is DEFINITELY software-related.
Is there something preventing this driver from installing? Why is the phone not installing the driver itself? Thoughts would be appreciated! Thanks.
Have you Manually installing the driver from Devices manager?
In the Device Manager locate your Android device. Then right-click on it and select "Update Driver Software".
Select "Browse my computer for driver software".
Select "Let me pick from a list of device drivers on my computer".
Select "Show All Devices".
Press the "Have Disk" button.
Enter the path to the Google USB driver. Normally it is located in the following directory: C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver
Select "Android ADB Interface" from the list of device types.
langithitam said:
Have you Manually installing the driver from Devices manager?
Enter the path to the Google USB driver. Normally it is located in the following directory: C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver
Select "Android ADB Interface" from the list of device types.
Click to expand...
Click to collapse
Thanks for the quick reply.
I searched, and do not have a folder called "Android".
I did, however, find a folder called "LG United Mobile Drivers", however there are about 30 different drivers in there. I picked a few, including "Lgandadb" and "Lgnetandadb", but I get told "Windows encountered a problem", and "This device cannot start (Code 10)"
Anyone?
Ok, I'll try to put it another way. When you first connect an Android phone to a PC, drivers are installed automatically. I'm willing to bet there was an error when I installed them on my new hard drive.
Are the drivers already a part of Windows? If so, perhaps I need to do a Repair of Windows?
Are they located in an Auto-Run file on the phone, and maybe I need to re-run that program?
Perhaps there's something I need to delete or flag so that my phone thinks it's the "first time" again?