Database Info

[Q] Device debugging with Eclipse

I'm very new to Android development (my first app), so please bear with me.
I'm using Eclipse with the android SDK. Using the Android SDK and AVD Manager, I've installed the Usb Driver package, rev 3.
To this point, I've been using the emulators to debug and develop. Now I need to debug on my device (bought a ViewSonic GTablet). Somewhere in my searching for solutions to how to get this going, I found that I need to get the drivers correctly installed. Those instructions directed me to:
- Modify the android_winusb.inf file in the usb_driver folder
- Install USBDeview program
- Removed all drivers associated with Andriod and NVIDIA Tegra 2 (I think there were 3 or 4)
- Connect the GTablet with USB and follow new found hardware wizard. Direct it to modified .inf file
The problem is, the "Found New Hardware Wizard" does its thing automatically without user intervention. I end up with 1 NVIDIA Tegra 2 USB Device driver. I think I'm supposed to have another driver called something like "Android Composite ADB Interface".
I tried using the Add Hardware wizard to install this, but it always results in saying "This device cannot start. (Code 10)".
Sorry for this lengthy explanation...can anyone please help?

Hi,
I struggled getting adb working until today. There's info for getting adb working with Gtab here:
http://forum.xda-developers.com/showthread.php?t=827209
The key for me was adding the 3 lines to the .inf. Make sure you have USB debugging enabled on the tab.
Then, in Win Device Manager uninstall the devices under Android.
Then unplug the USB, then reboot Windows.
After Windows starts, plug in USB, then when wizard pops up, browse to the USB driver dir.
Jim

Thank you jimcpl for the reply.
It's still a no-go.
I have done all the steps lined out in the link you provided--and thought your reboot step may be the key to making it work, but that didn't do it.
When I plug the GTab back in, I do get a "found new hardware" popup message, but no wizard is appearing. The result is, the system is installing:
(With the help of USBDeview window)
Device Name: NVIDIA Harmony
Description: NVIDIA Tegra 2 USB Device
Device Type: Mass Storage --> This one I can use to transfer files
...
I see no other devices associated with the GTab
What device type should the "Android Composite ADB Interface" be?
Also...Maybe this is a silly question, but isn't it the miniUSB connection I should be plugging in to?

More info on the problem
I found that when attempting to install the adb driver, the system is not using the .inf file I'm pointing it to. It is using one titled "oem24.inf". I found this by looking in Start->All programs->Accessories->System Tools->System Information. Then under Software Environment/Signed Drivers there is the "Android ADB Interface" listed.
I can see the referenced oem24.inf file (and associated .pnf files) under C:\Window\inf folder
BTW. I'm on Windows XP Pro SP3
In here I see at least 3 .ini files that have the three lines that we're using to modify the android_windusb.inf file with.
So the question now becomes...
How do I get the installation (or driver update) to use the .inf file I point it to?
Another recent thread suggested that window's supplied drivers will have to be removed. Are these what he may be referring to? If so how do I do that?
PLEASE -- I need a response from someone that knows something about this!

Memory doesn’t serve me too well in windows xp but go to device manager, click on action, add legacy hardware, Install the hardware that I manually select or something close to that then, have disk and point to the directory where the inf is located and install it. Make sure you modded the inf from the post above and you should be good to go.

Thanks...but, not the solution
I really appreciate the suggestion littleoldme!
In XP, Device Manager/Action menu only has the "Help" link which lauches the Microsoft Management Console. Doing a search for "Legacy" in the console results in no hits.
So I'm still stuck

JRDev said:
I really appreciate the suggestion littleoldme!
In XP, Device Manager/Action menu only has the "Help" link which lauches the Microsoft Management Console. Doing a search for "Legacy" in the console results in no hits.
So I'm still stuck
Click to expand...
Click to collapse
I found your answer.. see URL below
tegradeveloper.nvidia.com/tegra/forum/after-installing-froyo-adb-cant-see-device

I want to thank all who responded with suggestions to this problem.
I've followed all advice given and carefully followed all directions given in suggested links.
Unfortunately, there seems to be some underlying condition on my pc that is preventing the successful installation of the necessary adb driver. No matter what I have done so far, Windows is choosing NOT to use the driver I point it to, and use what it wants instead. I don't even get the "New Hardware" wizard when following the directions. It installs automatically and I have to launch a separate "Install new Hardware" dialog.
Anyway...through persistence, I've been able so far to develop this first app without the debug connection to the device using the development emulators, then installing the signed .apk on the device for further testing (via the one USB mass storage connection I do get).
So, maybe one day I'll find the reason, but for now I'll be purging on to get the app ready to go.
Thanks again for all help received.

I just come across this thread. After insert the usb device, then you might might find the unknown device in device manager. unstall that unknown device. And then do a hardware scan again in device manager. After it find your device again, point back to your USB inf file. It might work this way.

One thing I forgot. Do not unplug your device between uninstall and hardware scanning.

AAAHHH! GTAB Eclipse ADB frustration!
Thanks for all the tips, everyone, but I've been trying for days to be able to connect my gtab to use as a device for installing/debugging my apps. I too am running Eclipse using the emulators to date.
I've tried the steps outlined in the link provided by jimcpl, as well as others that are slightly varied, but to no avail.
I am running Vista SP2. My Gtab has been rooted, running ClockworkMod, and TnTLite 2.2. I also updated the Google USB package, rev 4 via the SDK/AVD Manager after attempting to use the rev 3 usb package.
Should any of these be reason why I cannot connect my gtab to Eclipse via ADB?
I'm totally frustrated...If anyone has any other suggestions, please forward them on!
Thanks in advance.

rlapela said:
Thanks for all the tips, everyone, but I've been trying for days to be able to connect my gtab to use as a device for installing/debugging my apps. I too am running Eclipse using the emulators to date.
I've tried the steps outlined in the link provided by jimcpl, as well as others that are slightly varied, but to no avail.
I am running Vista SP2. My Gtab has been rooted, running ClockworkMod, and TnTLite 2.2. I also updated the Google USB package, rev 4 via the SDK/AVD Manager after attempting to use the rev 3 usb package.
Should any of these be reason why I cannot connect my gtab to Eclipse via ADB?
I'm totally frustrated...If anyone has any other suggestions, please forward them on!
Thanks in advance.
Click to expand...
Click to collapse
On the Gtab, is USB debugging enabled?
On the Windows machine, did you add the 3 lines for tetra?
Jim

jimcpl said:
On the Gtab, is USB debugging enabled?
On the Windows machine, did you add the 3 lines for tetra?
Jim
Click to expand...
Click to collapse
Thanks Jim...Yes, and yes. I finally got connected. Old drivers were conflicting, and even though I'd repeatedly uninstall them in Device Manager, the ADB USB drivers would load, but not start the device. I finally got USBDeview to uninstall them successfully after many attempts and reboots, plugged in my GTab, and finally installed correctly, and it works like a champ!

rlapela said:
Thanks Jim...Yes, and yes. I finally got connected. Old drivers were conflicting, and even though I'd repeatedly uninstall them in Device Manager, the ADB USB drivers would load, but not start the device. I finally got USBDeview to uninstall them successfully after many attempts and reboots, plugged in my GTab, and finally installed correctly, and it works like a champ!
Click to expand...
Click to collapse
Hi,
Ok, thanks. I'm glad it's working for you now.
FYI, I think that when you "uninstall" a device from Device Manager in Windows, it doesn't physically delete driver files, etc. from your hard drive. It just removes the references to the removed device drivers from the Windows configuration.
That's why if you reboot, or do a scan for devices again, and if Windows thinks that it detects the physical device, it'll try to use the same driver files, .inf, etc. In that case, you have to force the installation of the new/correct driver, by not letting Windows automatically find the drivers (because otherwise, Windows will find the same ones from before, the non-working ones).
It's kind of a pain sometimes ... I ran into the same thing when I tried to install the ADB USB drivers. I downloaded the USB driver files from Android dev website, but those are generic. They have stuff in the .inf for some phones/devices that Google has relationships with, but not the "proprietary" ones like for the Gtab. That's why you have to add the 3 lines, which match (I guess) the Gtab.
Jim

[Q] Brk root method reports success, but no root

Hello,
Firstly, this is a long explanation, so, for the lazy, I have put a TL;DR version at the bottom of the post. Scroll there to get the general idea.
I have attempted to root my Transformer numerous times now. It is a serial number B60.
I am running Windows XP, so I am trying to use Brk's script.
I am using v6.3.1 of the script, because I have the latest OTA update.
This is my 'Build number' in 'About tablet': HTJ85B.US_epad-8.6.5.9-20110816
I have been trying this method since 8.6.5.6 and at the time I used v6.1 of the script (other methods including a VirtualBox run of rebound's One-Click Universal root linux live-CD).
When I run the script, I follow the instructions exactly.
I backup (option 1), then reboot into APK mode again.
Then, I flash unsecure boot.img (option 4) and CWM. I have tried only installing unsecure boot.img and it has made no difference.
Flashing the unsecure boot.img reports success and flashing CWM reports success.
Next, I reboot into regular Android OS.
Development mode is on for the USB. I check to see if ADB is working (option 7).
ADB is not working. The reason? I do not have root. I have installed the Terminal Emulator application. When I run the command 'su', it says 'Permission denied'.
I have also tried the Transformer pure root tw/us/ww/de/jp (8.4.4.5/11/12/8.6.5.6/7/9) and it has the same results. That is, flashing unsecure boot reports success, as does flashing CWM, but I have no root.
Additionally, I tried a VirtualBox run of rebound's One-Click Universal root linux live-CD. That failed, because I couldn't capture the Transformer as a USB device).
TL;DR version
I have tried several different methods of rooting my Transformer. It is serial #: B60 series running HTJ85B.US_epad-8.6.5.9-20110816.
All drivers are set up completely.
All steps are followed
All steps report success
Root is not granted
ADB will not work
???
More details at the top
One last thing
The only thing that I can think may possibly explain this problem is that I do not have an SD card in the tablet. I know some guides specify that you need one and other ones do not say anything.
I do not think that this is the cause, chiefly because everything reports 'success'.
Are these results typical of what happens when someone tries to flash a B70 or B80 model? If so, is it possible that, although I have a B60 series model, the innards are that of the B70/80 series and thus, incompatible?
I hope that posting my results and problems will help solve someone else's problem at the very least.
At this point, even someone just replying and letting me know that I have done everything correctly would be nice.

Have you got the ASUS drivers installed in your pc? i.e. can you connect and sync your device normally?

Here's a hint from the BRK thread:
Found the problem. I didn't install the ASUS PC Suite, just the drivers. Found a hint in another post that PC Suite seems to contain something in addition to the driver which is needed for ADB connections. No idea what it is, the device manager entries still look same...
so did you install the ASUS PC Suite as well as the drivers?

Success!
AustinMartin said:
Here's a hint from the BRK thread:
Found the problem. I didn't install the ASUS PC Suite, just the drivers. Found a hint in another post that PC Suite seems to contain something in addition to the driver which is needed for ADB connections. No idea what it is, the device manager entries still look same...
so did you install the ASUS PC Suite as well as the drivers?
Click to expand...
Click to collapse
Wow! I feel like a complete idiot...
I downloaded and installed the "Asus Eee PAD Transformer TF101 USB Driver" which I thought was what the PC Suite was. I was wrong.
Everything is working after installing the PC Suite and then trying ADB.
I definitely wrote way too much...

telekenetix said:
I definitely wrote way too much...
Click to expand...
Click to collapse
But that is how we learn, from seeing what others have done...

did you enable development ? it is for adb

I found that out early on that the PC Sync app is essentially just a front-end for ADB, since the app wouldn't work when I had debugging enabled on the TF.

mashi said:
did you enable development ? it is for adb
Click to expand...
Click to collapse
Yes. The trouble was that the PC Suite wasn't installed. I thought I had it installed, but it turned out that I only installed the drivers. Everything is running smoothly now.
The thing that still seems odd to me is that I tested to see if I had root, using the terminal application. It said "Permission denied". But, after installing the PC suite, adb was able to function and apparently did something magical.
So, I have to ask. What is this black magic?!

[SOLVED] Rooting using Debugfs does not work

I tried searching everywhere and was not able to find a solution.
When I run it, the following texts appear and then hangs indefinitely.
Waiting for device to be detected...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
From what I've found after searching, people have solved it by reinstalling driver, but it does not work for me.
I set both the security setting and USB debug setting, and driver is correctly installed.
I also tried following this video tutorial (http://forum.xda-developers.com/showthread.php?t=1798586), but that is pretty much what I did in the first place and that Debugfs hangs at the same spot.
I am new to an Android device. I own an iPhone which I jailbroke, but I am moving away from Apple. All I am trying to do right now is trying to change the dock keyboard layout, which apparently requires rooting.
Any help would be appreciated.

The text is fine, but it should go from there smoothly. Do you have ASUS sync installed and running? If so, kill it and kill it with a heavy stab.
Does your PC recognise the Infinity when you plug in the USB cable?

d14b0ll0s said:
The text is fine, but it should go from there smoothly. Do you have ASUS sync installed and running? If so, kill it and kill it with a heavy stab.
Does your PC recognise the Infinity when you plug in the USB cable?
Click to expand...
Click to collapse
ASUS sync is not installed on my computer and it's disabled on the tablet. My computer recognizes it when it's connected.

Sounds like a classic "it should work" situation.
Try it on a different PC perhaps. You may have some third-party software installed that's interacting with the adb. Hard to tell without looking into it really. When you try to use custom commands in adb, not the .bat file, does anything work? What does waiting for device report?

^^^ this
I know this from experience, that not all Windows PC's are created equal. I had an issue rooting my tablet on 2 Windows XP machines and one Windows 7. The final Windows 7 machine I tried magically worked. All had admin access and no restrictions.

qnfauf said:
I tried searching everywhere and was not able to find a solution.
When I run it, the following texts appear and then hangs indefinitely.
Waiting for device to be detected...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
From what I've found after searching, people have solved it by reinstalling driver, but it does not work for me.
I set both the security setting and USB debug setting, and driver is correctly installed.
I also tried following this video tutorial (http://forum.xda-developers.com/showthread.php?t=1798586), but that is pretty much what I did in the first place and that Debugfs hangs at the same spot.
I am new to an Android device. I own an iPhone which I jailbroke, but I am moving away from Apple. All I am trying to do right now is trying to change the dock keyboard layout, which apparently requires rooting.
Any help would be appreciated.
Click to expand...
Click to collapse
If you have adb setup properly you should be able to type "adb devices" from a command prompt. If all is well you will see your tablets serial number listed. If adb isn't setup properly, well you won't see anything.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2

Thanks for all the help. I don't really have another computer I can use right now.
newellj79 said:
If you have adb setup properly you should be able to type "adb devices" from a command prompt. If all is well you will see your tablets serial number listed. If adb isn't setup properly, well you won't see anything.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Click to expand...
Click to collapse
When I type "adb devices", it says
"List of devices attached" and two blank lines. I guess adb does not see my device. Am I doing something wrong?

I am having the *exact* same issue. I'm not sure what the deal is - I recently used ADB to root my SGS3 so it definitely boggles my mind as to why it's not working on my tablet.
Just wanted you to know you weren't the only one. I'm going to try reinstalling ADB drivers later tonight to see if maybe something is wrong on that front...
---------- Post added at 09:26 PM ---------- Previous post was at 09:15 PM ----------
Okay, let me explain how I got this to work.
First of all, the xda post you referenced has a link to a bad set of drivers. (Don't worry, it got me too at first, shame on that XDA poster for stealing credit in the first place...)
So, go here (http://forum.xda-developers.com/showthread.php?t=1706588) and download the ASUS Android Drivers USB.zip as well as as the rootdebugfs that is there.
Next, open your device manager - the reason I keyed into this is because there was a driver that said "ASUS Android Composite ADB Interface" that did not install properly. Unzip the ASUS Android Drivers and then right click on "ASUS Android Composite ADB Interface" and update the drivers, manually point to the folder that contains all of the ASUS Android Drivers and click ok, it should update your drivers CORRECTLY (You'll get a successfully updated drivers window). After that try using the rootdebugfs bat again, worked like a charm for me after that!
If you're still having issues, please let me know, and post a screenshot of your device manager if you don't mind, it could be the key to your issues as well.
Sorry for the long post, hope I made sense

Forcepath said:
I am having the *exact* same issue. I'm not sure what the deal is - I recently used ADB to root my SGS3 so it definitely boggles my mind as to why it's not working on my tablet.
Just wanted you to know you weren't the only one. I'm going to try reinstalling ADB drivers later tonight to see if maybe something is wrong on that front...
---------- Post added at 09:26 PM ---------- Previous post was at 09:15 PM ----------
Okay, let me explain how I got this to work.
First of all, the xda post you referenced has a link to a bad set of drivers. (Don't worry, it got me too at first, shame on that XDA poster for stealing credit in the first place...)
So, go here (http://forum.xda-developers.com/showthread.php?t=1706588) and download the ASUS Android Drivers USB.zip as well as as the rootdebugfs that is there.
Next, open your device manager - the reason I keyed into this is because there was a driver that said "ASUS Android Composite ADB Interface" that did not install properly. Unzip the ASUS Android Drivers and then right click on "ASUS Android Composite ADB Interface" and update the drivers, manually point to the folder that contains all of the ASUS Android Drivers and click ok, it should update your drivers CORRECTLY (You'll get a successfully updated drivers window). After that try using the rootdebugfs bat again, worked like a charm for me after that!
If you're still having issues, please let me know, and post a screenshot of your device manager if you don't mind, it could be the key to your issues as well.
Sorry for the long post, hope I made sense
Click to expand...
Click to collapse
Thank you, that worked!
In the process of trying to get it to work, I definitely saw "ASUS Android Composite ADB Interface" a few times in device manager. After reading your post, I could not get it to show. I tried uninstalling the driver, searching for new hardware, etc. to no avail. However, switching the USB connection type from MTP to PTP while the device manager was running (I'm not sure why it had to be running) made it show up. Then I used the correct driver files to install the driver and the root worked. That guy who put up the video tutorial apparently put wrong drivers.

mtp to ptp
qnfauf said:
Thank you, that worked!
In the process of trying to get it to work, I definitely saw "ASUS Android Composite ADB Interface" a few times in device manager. After reading your post, I could not get it to show. I tried uninstalling the driver, searching for new hardware, etc. to no avail. However, switching the USB connection type from MTP to PTP while the device manager was running (I'm not sure why it had to be running) made it show up. Then I used the correct driver files to install the driver and the root worked. That guy who put up the video tutorial apparently put wrong drivers.
Click to expand...
Click to collapse
switching from mtp to ptp fixed it for me. it caused the device manager see an new device, which then had a yellow triangle. i just right clicked on it and hit refresh, and it installed the driver. g2g after that.

I had same problem but its solved now n its just drivers problem
just google "phones_brand_name usb drivers"
download and install them
n you are done

New TF700T not showing in adb?

Hey everyone,
I've read through the All-In-One guide about how to root the TF700T, downloaded the driver pack, put it into developer mode and enabled unknown sources. When I plugged the device into my computer it was immediately recognized and automatically installed the drivers and I can see it through Windows Explorer and browse the file system.
Unfortunately the device doesn't show in adb and I read through this quote in the guide, "if not, install the ADB drivers from Windows Device Manager (if you don't know how to do it then you better stay off from rooting your device)" so I went to the Device Driver and and tried to update the driver with the ADB driver, however, it says it's not compatible.
On the Android device I see the USB mode as Media Device (MTP) and that USB Debugging Connected
In Windows Device manager I see under "Portable Devices" the "ASUS Transformer Pad TF700T" is there and installed without error.
There aren't any device drivers that have a yellow icon indicating they aren't configured correctly.
I had purchased the tablet a few days back and it prompted me for a system update which I did.
I've tried rebooting both my computer and the tablet but it didn't appear to assist.
I'm assuming I'm doing something silly and simple but I cannot for the life of me figure it out.
Does anyone have any suggestions on what I may be doing wrong?
Thanks in advance everyone,
Septurious

Search for universal adb drivers in Google. It should lead you to a thread on XDA in the TF101 section.
Sent from my Galaxy Nexus using xda premium

Thanks!
Nebucatnetzer said:
Search for universal adb drivers in Google. It should lead you to a thread on XDA in the TF101 section.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Thanks for the info! I searched for "universal adb driver xda" in good ol Google and got to this post.
Downloaded the drivers and started to do the install process described in the post but when I did the "uninstall and delete" drivers deal and then replugged in the TF700T I quickly clicked on the "driver install" dialog in windows and told it NOT to search Windows Update which seemed to cause it to grab the adb drivers that I grabbed from the original post and voila it worked.
After running through the debugfs script and running the SuperUser program once I was rooted and finally got smartdimmer and remote management disabled.
Thanks so much for your reply, most appreciated!
Septurious

Glad I could help.
Excuse me that I didn't post the link directly it's a pain on the phone.

I had a similar problem. The TF700 was automatically found, and no ADB drivers were installed. I kept trying to uninstall the driver, but it wouldnt let me. I don't have an option to "delete drivers" on uninstall.
When I tried installing "legacy hardware" to force the drivers, it would come up listed under "Samsung" and not Asus. I think I have my drivers all screwed up from previous phones i've had. I took the driver set, and went to another PC (same os, Win 7 ult x64), and had no problem installing all the drivers and rooting.
Anyone have an idea for me? Not sure if I should start going through my sys32 and manually deleting all driver files associated with my tablet.

Fixed.
I had to do this.
http://www.thewindowsclub.com/how-to-remove-old-unused-device-drivers-in-windows-7
Went through and cleaned up all the old drivers, between the old Samsung Drivers, Motorola Drivers, previous Android ADB drivers. I now plugged in my TF700, and while the ADB shows up as a Samsung device, it shows up on "adb devices", which it didnt before.

Another solution
I tried all listed tips but failed.
ADB driver was installed automaticaly after enabling USB-modem on my TF700.
Now android device chooser showing device

for hours i tried it! no i know why it didnt work!
turn off windows firewall!!! DD maaaaaan

Septurious said:
Thanks for the info! I searched for "universal adb driver xda" in good ol Google and got to this post.
Downloaded the drivers and started to do the install process described in the post but when I did the "uninstall and delete" drivers deal and then replugged in the TF700T I quickly clicked on the "driver install" dialog in windows and told it NOT to search Windows Update which seemed to cause it to grab the adb drivers that I grabbed from the original post and voila it worked.
After running through the debugfs script and running the SuperUser program once I was rooted and finally got smartdimmer and remote management disabled.
Thanks so much for your reply, most appreciated!
Septurious
Click to expand...
Click to collapse
>> I have the same problem and do the same thing, but windows didn't install drivers: its show a message indicating a problem with the hash of catalogue.
Anyone can help?

GBDias said:
>> I have the same problem and do the same thing, but windows didn't install drivers: its show a message indicating a problem with the hash of catalogue.
Anyone can help?
Click to expand...
Click to collapse
Windows 8?
Try disabling driver signature verification.
Sent from my DROID4 using Tapatalk

Can Not Get Naked Drivers Installed for NvFlash Setup

I can not figure out what the hell I am doing wrong here.
I downloaded the naked driver pack on the guide page labeled 'Drivers TF700: Windows (Patched Universal Naked Driver)'. I unzipped the folder and plugged my TF700 into my computer. I then opened up the Device Manager and clicked on 'Asus Android Devices', then right clicked on 'Asus Android Composite ADB Interface' and pressed uninstall. I checked the 'delete the driver software for this device' and pressed OK.
The drivers uninstalled successfully and I turned off my WiFi card. I then unplugged and re-plugged my TF700 and navigated to 'Other Devices' in the Device Manager. I right clicked on 'Asus Android Composite ADB Interface' and clicked 'update driver software...' and then on 'browse my computer for driver software'.
I then navigated to the folder that I unzipped the driver pack to and tried to install them (clicking the 'include sub-folders' option). No go, I got the error message 'Windows was unable to find the driver software for your device' or something very similar. I then tried specifically pointing to both the i386 and amd64 sub-folders just to see if that wouldn't work somehow but I got the same error message.
What am I doing wrong? I am using a Lenovo G550 (I think) 32-bit laptop running Windows 7. My TF700 is rooted and unlocked but not much else has been done to it.
If anyone can help me get these installed I would really appreciate it. I assume I can probably set up NvFlash with the standard Asus drivers but I would rather set it up exactly the way it is recommended to ensure success.
Massive thanks in advance!
Blake

Put the device in apx mode then try that process. It should show up as an APX device and that's what you apply the nvflash drivers to.

diablodow said:
Put the device in apx mode then try that process. It should show up as an APX device and that's what you apply the nvflash drivers to.
Click to expand...
Click to collapse
That step isn't till later
@OP - let it update the drivers form Windows. That should be fine. As long as you can see the device and it has no errors or warnings around it. you only need the specific drivers when you get to the APX mode, then it will find them.

I had pretty much the same problem, but it turned out it went a lot smoother with reboot in between. Try that, and disable Windows' desperate searching for drivers on Windows Update -- I got some funky drivers and device designations from the WHQL drivers... Please report back in with any progress or lack thereof, and we'll try and get you back on track.

MartyHulskemper said:
I had pretty much the same problem, but it turned out it went a lot smoother with reboot in between. Try that, and disable Windows' desperate searching for drivers on Windows Update -- I got some funky drivers and device designations from the WHQL drivers... Please report back in with any progress or lack thereof, and we'll try and get you back on track.
Click to expand...
Click to collapse
This.
I had big time problems as well with installing these correctly. You need to reboot after uninstalling all old drivers. 1) Hook up Infinity in Android Debug mode 2) uninstall/delete old drivers like you did 3) reboot PC 4) Plug in Infinity again in Android Debug mode 5) install drivers manually through hardware wizard (use have disk option)
Repeat this process for fastboot mode. Note: you will get a warning that you are installing drivers that have not passed WHQL. Disregard. Install anyways.
Its a pain in the butt process but you have to reboot after uninstalling each old driver. You should probably reboot and remove Infinity USB connection after each successful install of new drivers. This is how I got everything to work. I also tried a different USB port.
Sent from my SCH-I535 using Tapatalk 2

SOTK said:
Repeat this process for fastboot mode. Note: you will get a warning that you are installing drivers that have not passed WHQL. Disregard. Install anyways.
Its a pain in the butt process but you have to reboot after uninstalling each old driver. You should probably reboot and remove Infinity USB connection after each successful install of new drivers. This is how I got everything to work. I also tried a different USB port.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Can you clarify this? What do you mean by 'repeat this for fastboot mode'?
Sent from my unlocked Transformer Infinity

Still no luck. I uninstalled 'ASUS ABD Interface', unplugged the TF700, restarted the computer, plugged the tablet back in, and tried to uninstall. Told me the same thing, that Windows could not find the driver software.
Any other ideas? I have no clue what to do now...
Sent from my unlocked Transformer Infinity

I_EAT_BABIES said:
If anyone can help me get these installed I would really appreciate it. I assume I can probably set up NvFlash with the standard Asus drivers but I would rather set it up exactly the way it is recommended to ensure success.
Massive thanks in advance!
Blake
Click to expand...
Click to collapse
I am having the same exact issue. And strangely I get the same results on both my laptop and desk top systems. I search the forums for solutions and found the same answers that were suggested here but nothing works for me. I just can't figure out what I am doing wrong since so many others seem to be able to install the drivers without problems. Did you ever resolve your driver issue? Are you certain that the standard ASUS drivers will work?

Eddie Hicks said:
I am having the same exact issue. And strangely I get the same results on both my laptop and desk top systems. I search the forums for solutions and found the same answers that were suggested here but nothing works for me. I just can't figure out what I am doing wrong since so many others seem to be able to install the drivers without problems. Did you ever resolve your driver issue? Are you certain that the standard ASUS drivers will work?
Click to expand...
Click to collapse
Guys you need to install those drivers manually,it's not that hard.Here's how you should do it:
1) Put your device in Fastboot or APX mode (depend on the driver you want to install) and connect it to your PC
2) Open Device Manager and select the device
3) Right Click and select " Update Driver Software " and choose " Browse My Computer for driver software"
4) Now click on " Let me pick from a list of device driver " and select " HAVE DISK "
5) BROWSE to the folder where naked drivers are located and select "android_winusb.inf " if you are trying to install the FastBoot driver or choose " android_apxusb.inf " if you are trying to install the APX drivers.
6) After the installation is done reboot your PC
If Windows give you a big red warning about the driver not beeing signed just ignore it and go ahead installing the driver.
Also you should disable UAC if it's enabled.

Pretoriano80 said:
4) Now click on " Let me pick from a list of device driver " and select " HAVE DISK "
Click to expand...
Click to collapse
Thank you very, very much but I just figured that out and came back to this thread to tell it. I wasn't doing the "Have Disk" thing. I was just browsing to the driver's folder. I just successfully installed NVflash. I installed the ADB drivers at first but during the Nvflash installation process I had to go back and install the APX drivers. Thanks again. Now time for Jelly Bean.

Eddie Hicks said:
Thank you very, very much but I just figured that out and came back to this thread to tell it. I wasn't doing the "Have Disk" thing. I was just browsing to the driver's folder. I just successfully installed NVflash. I installed the ADB drivers at first but during the Nvflash installation process I had to go back and install the APX drivers. Thanks again. Now time for Jelly Bean.
Click to expand...
Click to collapse
Haha, nice! but still be very careful, 98% of the brick situation on tf700, NVflash didn't help at all.

buhohitr said:
Haha, nice! but still be very careful, 98% of the brick situation on tf700, NVflash didn't help at all.
Click to expand...
Click to collapse
Is the other way around, NvFlash will help you in 98% of bricks situation, if you don't believe try to investigate more, you can even try to wipe your bootloader if you want to check that percentage.

Pretoriano80 said:
Guys you need to install those drivers manually,it's not that hard.Here's how you should do it:
1) Put your device in Fastboot or APX mode (depend on the driver you want to install) and connect it to your PC
2) Open Device Manager and select the device
3) Right Click and select " Update Driver Software " and choose " Browse My Computer for driver software"
4) Now click on " Let me pick from a list of device driver " and select " HAVE DISK "
5) BROWSE to the folder where naked drivers are located and select "android_winusb.inf " if you are trying to install the FastBoot driver or choose " android_apxusb.inf " if you are trying to install the APX drivers.
6) After the installation is done reboot your PC
If Windows give you a big red warning about the driver not beeing signed just ignore it and go ahead installing the driver.
Also you should disable UAC if it's enabled.
Click to expand...
Click to collapse
I'm still not getting it I guess. I am assuming when doing it this way you do not uninstall the original drivers first or else the computer would not recognize the device correctly, please correct me if I am wrong.
I keep seeing this supposed "have disk" option talked about but I don't see it anywhere. Could someone please screenshot it for me?
Thanks for all the help guys, I (hope) I am close to getting it.
Sent from my unlocked Transformer Infinity

Pretoriano80 said:
Is the other way around, NvFlash will help you in 98% of bricks situation, if you don't believe try to investigate more, you can even try to wipe your bootloader if you want to check that percentage.
Click to expand...
Click to collapse
I'm talking about nvflash for the tf700 only. 98% of ppl in the tf700 experienced this type of issue where nvflash is uselessmost I believe cause by install custom recovery), where your pc failed to see your device. Below is another sample.
http://forum.xda-developers.com/showthread.php?t=1778353

buhohitr said:
I'm talking about nvflash for the tf700 only. 98% of ppl in the tf700 experienced this type of issue where nvflash is uselessmost I believe cause by install custom recovery), where your pc failed to see your device. Below is another sample.
http://forum.xda-developers.com/showthread.php?t=1778353
Click to expand...
Click to collapse
So I see you are trolling this thread too... 98%??? Really??? Can you give a source for that or is that a number you just made up?
NVFlash is useless if you have not already made the backups. But you are completely incorrect if you are suggesting that it is useless even if you have made the backups.
Best not to troll when you clearly do not understand what you are talking about

I_EAT_BABIES said:
I'm still not getting it I guess. I am assuming when doing it this way you do not uninstall the original drivers first or else the computer would not recognize the device correctly, please correct me if I am wrong.
I keep seeing this supposed "have disk" option talked about but I don't see it anywhere. Could someone please screenshot it for me?
Thanks for all the help guys, I (hope) I am close to getting it.
Sent from my unlocked Transformer Infinity
Click to expand...
Click to collapse
Anyone?
Sent from my DROID SPYDER using Tapatalk 2

I_EAT_BABIES said:
Anyone?
Sent from my DROID SPYDER using Tapatalk 2
Click to expand...
Click to collapse
Damn,i can't believe this....When you get to this step " 4) Now click on " Let me pick from a list of device driver " and select " HAVE DISK ... " look on the right bottom of that menu,do you see a "Have Disk" button?.

I_EAT_BABIES said:
Anyone?
Sent from my DROID SPYDER using Tapatalk 2
Click to expand...
Click to collapse
Here is a screen capture from my system. Look in the lower right for the HAVE DISK button. Following the directions giving earlier should get you to this point. Just click HAVE DISK and guide to where you have the drivers on your system. You may not see the list of drivers as on the screen capture the first time you do it. Since I have already installed the drivers the system remembered where to look so the drivers are visible. Also make sure to connect your tablet to your computer in order for the device to be visible in device manager. The device in device manager should say android ABD Interface or something of that sort. It took me awhile to get it too
****edit***
Apparently the link opens another page.Once on that page click the little box for the image.
https://www.dropbox.com/s/ykuv2ac6zxdln7i/driver_update.JPG

As of the time of this reply I have got the Fasboot drivers installed, but I still saw now "have disk" option. After turning UAC off (don't know how that got back on) I was still just selecting a folder as shown in my previous screenshot.
About to try APX, will post results.

Got it! Thank you guys so much, I really appreciate it. This was seriously driving me crazy, but I still don't understand how we are looking at different menus.