I found a way to install APX drivers in PC for TF700. As everbody, or almost everbody knows, these drivers are absolutely vital for the ones that want to run NVFlash to secure their TF700 in the best way against an eventual brick. As I experienced—and I know I am not the only—this adventure of APX drivers install causes a lot of trouble to people trying to figure out where are the drivers and how the install should be done.
Days ago, I posted these step-by-step instructions as a reply of a message about APX drivers. I am now posting it again at a separate topic, as this can be easier to find. The thing is that there's some "tricks" and "pitfalls" to the newbies like me when they try to install that Asus USB drivers. At first I couldn't install, I even thougt that they were not compatible with my Windows (I use Vista 32, that is famous as being really a ***** when comes up to install things). So, for ADB, in that moment I just gave up from Asus Android USB Drivers and installed Asus Pad PC Suite, that included ADB drivers, but apparently no APX. At that moment, when I was only looking for ADB, worked. But later, trying APX, I got really stucked. Just found the solution many sleepless nights later.
Please just notice that I am not an expert in anything: just a cat-crazy lady that works as text revisor and does patchwork quilts and amigurumi dolls at the free time. So, I'm afraid I can't help much on the technical side if any doubt appear (unless your doubt is about feeding an elder toothless cat with a bird syringe, syntax of verbs in Portuguese or about brands of wool and thimbles). Also can't assure this method will work for everyone.
Anyway, I'll be glad to help with the few I know. I hope these instructions can be of any use and save people from stress. Best wishes and happy APX'ing.
********************HOW TO INSTALL APX FOR TF700 IN WINDOWS************************
***One important warning I give to the stucked TF700 owners that are searching for APX drivers: DO NOT TRY TO USE UNIVERSAL NAKED DRIVERS! They will not work! Universal Naked Drivers are great, but made for TF101, Prime, Nexus, etc, etc, NOT for TF700 Infinity! So, any attempt to use that drivers, at the moment (March 2014) will give you nothing more than a last-longing splitting headache.
Use the pack from Asus: "Asus Android USB Drivers", download the pack from Asus website (go there, is one of the few downloads for Windows available for TF700)***
I'll just enumerate what I did and what I paid attention as necessary steps to install APX drivers for TF700 in Windows. If someone wants to give a try and follow them, there's the description.
1) Your device must be with the USB Debugging Mode enabled. This is found under Developer Options (enable it if Developer Options doesn't show by tapping 7 times the build number, under Settings/About).
2) Asus drivers dislike Windows auto-install. When we plug our device in USB (just normally, Android running), he is recognized and Windows auto-install prompts a message offering to locate and install drivers. IGNORE IT, SKIP IT. Just tell windows that will install later (there's an option for that, at least in Vista 32).
3) Then go to Control Panel, and choose "System". There, choose "Device Manager". There, look for something Asus, if you don't have previously installed any (if you have, uninstall it first, reboot the PC, then plug the tablet via USB). If you haven't installed anything and your tablet is connected, will appear something like "Asus ADB Interface", marked as not working by Windows.
4) Then, right-click over it and ask for "Update Driver". It will open a new prompt asking if you want Windows to search it automatically or if you want to search driver files manually from other sources. Say you want to search it manually. After, say you want to choose from drivers list (bottom option) and then say "Have Disk". And then direct Windows to search the driver in the directory where "Asus Android USB Drivers for Windows" are (uncompressed directory, please). The drivers file is the "android_winsub.inf", under the sub-directory "Android". Choose the file and proceed the installing.
5) This should install ADB. But, wait: the problem is the APX, not the ADB, right??? So, what does all this is for?
6) Now the magic (or, what so magically happened to me): reboot the tablet into APX Mode (power+volume up). And then another window of APX auto-install will pop. IGNORE IT.
7) Again, go to System/Device Manager. APX should appear there as "Asus Transformer Infinity APX Interface" or something fancy alike (if appear only "APX", something gone wrong and the installation already failed, at least here was this way). Is also marked as not working by Windows. You should again right-click and choose "Update Driver"
8) Repeat the process, if necessary direct Windows to the directory where the android_winsub.inf is (the one that was into the Asus Android USB Drivers pack). From this point my Windows installed automatically some parts, but, as I could notice, installed the driver from that same file of before.
This installed APX for me, and I could run wheelie and NVFlash!
So, I honestly hope this helps. I know it arrives too late for many, but still if can help somebody at least a little bit, I'll be happy.
Hello drhode, are you sure Universal Naked Drivers do not work? I remember very clearly that I used Universal Naked Drivers to run NVFlash and wheelie worked fine a few months ago. In fact, the guide for Flatline actually includes a link to a set of Universal Naked Driver 0.72, and I am very sure that I used that to get APX Driver.
huy_lonewolf said:
Hello drhode, are you sure Universal Naked Drivers do not work? I remember very clearly that I used Universal Naked Drivers to run NVFlash and wheelie worked fine a few months ago. In fact, the guide for Flatline actually includes a link to a set of Universal Naked Driver 0.72, and I am very sure that I used that to get APX Driver.
Click to expand...
Click to collapse
There seem to be different versions of this driver pack in circulation. To see whether it works with the TF700, look into the .inf files for USB vendor and product IDs and compare with my udev rules for Linux. The vendor and product IDs are the same for Windows, and they should appear somewhere in the .inf file (for wheelie, at least the one for APX):
Code:
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0b05", ATTRS{idProduct}=="4c90", GROUP="plugdev", MODE="0660" # MTP (normal)
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0b05", ATTRS{idProduct}=="4c91", GROUP="plugdev", MODE="0660" # MTP + USB Debugging (adb)
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0b05", ATTRS{idProduct}=="4c92", GROUP="plugdev", MODE="0660" # RNDIS
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0b05", ATTRS{idProduct}=="4c93", GROUP="plugdev", MODE="0660" # RNDIS + USB Debugging
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0b05", ATTRS{idProduct}=="4c94", GROUP="plugdev", MODE="0660" # PTP
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0b05", ATTRS{idProduct}=="4c95", GROUP="plugdev", MODE="0660" # PTP + USB Debugging
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0b05", ATTRS{idProduct}=="4daf", GROUP="plugdev", MODE="0660" # Fastboot
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0955", ATTRS{idProduct}=="7030", GROUP="plugdev", MODE="0660" # Tegra APX
@drhode Can you please post the link where you found the drivers? Have been searching the Asus download site high and low and don't see them. Only found a zip on XDA and that only seems to have the ADB dirver.
Sent from my K00C using Tapatalk
drhode said:
I found a way to install APX drivers in PC for TF700. As everbody, or almost everbody knows, these drivers are absolutely vital for the ones that want to run NVFlash to secure their TF700 in the best way against an eventual brick. As I experienced—and I know I am not the only—this adventure of APX drivers install causes a lot of trouble to people trying to figure out where are the drivers and how the install should be done.
Days ago, I posted these step-by-step instructions as a reply of a message about APX drivers. I am now posting it again at a separate topic, as this can be easier to find. The thing is that there's some "tricks" and "pitfalls" to the newbies like me when they try to install that Asus USB drivers. At first I couldn't install, I even thougt that they were not compatible with my Windows (I use Vista 32, that is famous as being really a ***** when comes up to install things). So, for ADB, in that moment I just gave up from Asus Android USB Drivers and installed Asus Pad PC Suite, that included ADB drivers, but apparently no APX. At that moment, when I was only looking for ADB, worked. But later, trying APX, I got really stucked. Just found the solution many sleepless nights later.
Please just notice that I am not an expert in anything: just a cat-crazy lady that works as text revisor and does patchwork quilts and amigurumi dolls at the free time. So, I'm afraid I can't help much on the technical side if any doubt appear (unless your doubt is about feeding an elder toothless cat with a bird syringe, syntax of verbs in Portuguese or about brands of wool and thimbles). Also can't assure this method will work for everyone.
Anyway, I'll be glad to help with the few I know. I hope these instructions can be of any use and save people from stress. Best wishes and happy APX'ing.
********************HOW TO INSTALL APX FOR TF700 IN WINDOWS************************
***One important warning I give to the stucked TF700 owners that are searching for APX drivers: DO NOT TRY TO USE UNIVERSAL NAKED DRIVERS! They will not work! Universal Naked Drivers are great, but made for TF101, Prime, Nexus, etc, etc, NOT for TF700 Infinity! So, any attempt to use that drivers, at the moment (March 2014) will give you nothing more than a last-longing splitting headache.
Use the pack from Asus: "Asus Android USB Drivers", download the pack from Asus website (go there, is one of the few downloads for Windows available for TF700)***
I'll just enumerate what I did and what I paid attention as necessary steps to install APX drivers for TF700 in Windows. If someone wants to give a try and follow them, there's the description.
1) Your device must be with the USB Debugging Mode enabled. This is found under Developer Options (enable it if Developer Options doesn't show by tapping 7 times the build number, under Settings/About).
2) Asus drivers dislike Windows auto-install. When we plug our device in USB (just normally, Android running), he is recognized and Windows auto-install prompts a message offering to locate and install drivers. IGNORE IT, SKIP IT. Just tell windows that will install later (there's an option for that, at least in Vista 32).
3) Then go to Control Panel, and choose "System". There, choose "Device Manager". There, look for something Asus, if you don't have previously installed any (if you have, uninstall it first, reboot the PC, then plug the tablet via USB). If you haven't installed anything and your tablet is connected, will appear something like "Asus ADB Interface", marked as not working by Windows.
4) Then, right-click over it and ask for "Update Driver". It will open a new prompt asking if you want Windows to search it automatically or if you want to search driver files manually from other sources. Say you want to search it manually. After, say you want to choose from drivers list (bottom option) and then say "Have Disk". And then direct Windows to search the driver in the directory where "Asus Android USB Drivers for Windows" are (uncompressed directory, please). The drivers file is the "android_winsub.inf", under the sub-directory "Android". Choose the file and proceed the installing.
5) This should install ADB. But, wait: the problem is the APX, not the ADB, right??? So, what does all this is for?
6) Now the magic (or, what so magically happened to me): reboot the tablet into APX Mode (power+volume up). And then another window of APX auto-install will pop. IGNORE IT.
7) Again, go to System/Device Manager. APX should appear there as "Asus Transformer Infinity APX Interface" or something fancy alike (if appear only "APX", something gone wrong and the installation already failed, at least here was this way). Is also marked as not working by Windows. You should again right-click and choose "Update Driver"
8) Repeat the process, if necessary direct Windows to the directory where the android_winsub.inf is (the one that was into the Asus Android USB Drivers pack). From this point my Windows installed automatically some parts, but, as I could notice, installed the driver from that same file of before.
This installed APX for me, and I could run wheelie and NVFlash!
So, I honestly hope this helps. I know it arrives too late for many, but still if can help somebody at least a little bit, I'll be happy.
Click to expand...
Click to collapse
So when I did the original unlock, root and flash of the CROMBi kit Kit ROM a short while ago, I followed all the instructions for it in the forum. Does this mean that I still need to install the APX drivers? IF I don't what am I missing?
Cary
Sorry by the delay, I'm back (got sick these days)
Hi, people: sorry for the delay. I got really sick these days (I am under treatment right now, getting better, enjoying the lovely painkillers to get a fine time to answer here. Perhaps the last exhibition of patchwork and quilting has been much of excitement to me ***the troubles of being an old lady, that's it...XDDD ***)
About Universal Naked Drivers: by some time it WERE some versions available, and one of them patched for TF700T. Thing is, that patched version is not available anymore: at NVFlash page of Android. Mobi team, the link leads nowhere. I don't know if there was some sort of unstability of sorts, but the truth is that version is not available anymore, at least I could not find it.
About Asus Android USB Drivers: besides I remember have taken the pack from Asus site, just checked it and there's nothing there now. I don't know if Asus pulled it to force us to use the Asus PC Suite instead or if I was just mistaken, but I found nothing this time.
BUT, THERE'S HOPE! And coming right here from XDA. I found a working link at this site to Asus Anroid USB Drivers zip pack. I downloaded now with XDA link and the file is of the same size of that I have, so I figure out that is the same.
Here's the link: http://forum.xda-developers.com/attachment.php?attachmentid=1245225&d=1344272324
I am at the tablet, comparing the file of the link with one in my tools memory card, but I'll check tomorrow/today if the files are really the same in my PC (need enjoy the painkillers to sleep too, so now I'll take a nap). If they are the same, I'll update my message with XDA link. If perhaps they are not the same, I'll upload the pack I have (and that's work) somewhere and post the link here.
And about APX...It's necessary to run NVFlash and wheelie, that grant a more trustworthy security to TF700T tablets ( these are for recovering the tablet after a softbrick). Install ROM, unlock, root, etc, is not done using APX, but the best recovery afer some tragedy, surely it is.
Again, friends, sorry about the delay in replying, I was needing some meds and rest. Best wishes to everbody.
drhode said:
Hi, people: sorry for the delay. I got really sick these days (I am under treatment right now, getting better, enjoying the lovely painkillers to get a fine time to answer here. Perhaps the last exhibition of patchwork and quilting has been much of excitement to me ***the troubles of being an old lady, that's it...XDDD ***)
About Universal Naked Drivers: by some time it WERE some versions available, and one of them patched for TF700T. Thing is, that patched version is not available anymore: at NVFlash page of Android. Mobi team, the link leads nowhere. I don't know if there was some sort of unstability of sorts, but the truth is that version is not available anymore, at least I could not find it.
About Asus Android USB Drivers: besides I remember have taken the pack from Asus site, just checked it and there's nothing there now. I don't know if Asus pulled it to force us to use the Asus PC Suite instead or if I was just mistaken, but I found nothing this time.
BUT, THERE'S HOPE! And coming right here from XDA. I found a working link at this site to Asus Anroid USB Drivers zip pack. I downloaded now with XDA link and the file is of the same size of that I have, so I figure out that is the same.
Here's the link: http://forum.xda-developers.com/attachment.php?attachmentid=1245225&d=1344272324
I am at the tablet, comparing the file of the link with one in my tools memory card, but I'll check tomorrow/today if the files are really the same in my PC (need enjoy the painkillers to sleep too, so now I'll take a nap). If they are the same, I'll update my message with XDA link. If perhaps they are not the same, I'll upload the pack I have (and that's work) somewhere and post the link here.
And about APX...It's necessary to run NVFlash and wheelie, that grant a more trustworthy security to TF700T tablets ( these are for recovering the tablet after a softbrick). Install ROM, unlock, root, etc, is not done using APX, but the best recovery afer some tragedy, surely it is.
Again, friends, sorry about the delay in replying, I was needing some meds and rest. Best wishes to everbody.
Click to expand...
Click to collapse
Thank you drhode! I found the same link.
I wish you all the best for your health!
berndblb said:
Thank you drhode! I found the same link.
I wish you all the best for your health!
Click to expand...
Click to collapse
There are two drivers for the tf700. The portable driver is for fastboot and adb. The second driver is for andriod usb which is for apx.. You can find the apx driver on the sdk website...
@drhode
I hope that you are getting better soon and wish everything going well for you...
LetMeKnow said:
There are two drivers for the tf700. The portable driver is for fastboot and adb. The second driver is for andriod usb which is for apx.. You can find the apx driver on the sdk website...
@drhode
I hope that you are getting better soon and wish everything going well for you...
Click to expand...
Click to collapse
What is a portable driver????
And where have you been the last week or so? We're still testing f2fs and you're on to the next trick already? Bionic???
Good to see you
berndblb said:
What is a portable driver????
And where have you been the last week or so? We're still testing f2fs and you're on to the next trick already? Bionic???
Good to see you
Click to expand...
Click to collapse
When you plug in your tf700, win recognizes it as a portable device so you can communicate with it. As the same time, there is an android driver that you can can configure for apx mode. Otherwise, you have to manually cofigure to apx when you want to use it... I believed that @drhode is trying to explain in her post...
My f2fs is still running great and looking for new stuff to play around with but it is not as convience as before because I can not test them without the tf700 next to me...
I think I'm more confused now than I was before I read this thread. I've checked every version of UND drivers I could find and none had the ids _that posted. None of the patched drivers seem to exist anymore. I'm hoping someone could be more specific about manually configuring the above linked drivers for apx mode in Windows. Failing that would it be possible/advisable to generate the NVFlash files using a Linux live usb key? I've been reading up on Linux for the past year but have yet to actually do anything with it. Many thanks to anybody taking the time.
a-t0m said:
I think I'm more confused now than I was before I read this thread. I've checked every version of UND drivers I could find and none had the ids _that posted. None of the patched drivers seem to exist anymore. I'm hoping someone could be more specific about manually configuring the above linked drivers for apx mode in Windows. Failing that would it be possible/advisable to generate the NVFlash files using a Linux live usb key? I've been reading up on Linux for the past year but have yet to actually do anything with it. Many thanks to anybody taking the time.
Click to expand...
Click to collapse
I just want to share my experience with apx driver.
I was able to install apx driver when I boot into flatline's recovery first, and then install UDN 0.72 driver in windows.
I had trouble when I was following flatline's method for pulling blobs files with adb commands (no devices found).
My Asus Android USB Drivers didn't install apx driver for windows, so I used UDN 0.72 driver from http://forum.xda-developers.com/showthread.php?t=1426502
The zip file should contains "android_apxusb.inf". Open that file, the you should see similar text of what _that posted
" SUBSYSTEMS=="usb", ATTRS{idVendor}=="0955", ATTRS{idProduct}=="7030", GROUP="plugdev", MODE="0660" # Tegra APX "
From the file ->
" Asus Transformer Prime TF201 APX & ADB Interface
%AsusTransformerPrimeAPXInterface% = USB_Install, USB\VID_0955&PID_7330 "
Follow OP drhode's unistall driver instruction for a clean start over (usb debug mode on).
"control panel -> device manager->asus android devices->right click on asus android....->uninstall->
a window prompt of unistall confimation, check the box of delete this device's driver->ok->
after unistalled, unplug tf700 usb connection to pc, restart windows.
after windows restart, Plug in normal booted tf700 and update the driver(either *.inf from UDN 0.72 or Asus Android USB Drivers)
Guide for win7 driver update
You can turn off driver signature check during the installation just incase some weird driver situation
Open cmd.exe type " bcdedit /set TESTSIGNING ON " and restart windows.
Reboot tf700 into flatline's recovery. If yellow ! appears in control panel, then update the driver again( w/*.inf from UDN 0.72 choose Prime).
Just restart windows after every driver install/uninstall.
It is just a regular driver update/install, nothing more special about it.
Btw, I'm using Win 7 64bit, so I'm not sure if that's the same instruction for windows 8.
I hope you can get it to work soon.
Related
I've compiled a fastboot binary for windows from the git source, using cygwin.
I had actually compiled it a couple of weeks ago, but I never could get it to work. I was looking into it again tonight and discovered that windows had installed the USB Mass Storage driver for the phone in SPL mode, instead of the android driver. So after updating it to the android driver, it worked! woot
Instructions:
(note: you have to check the USB device in Computer Manager when the phone is in fastboot mode. The computer sees the phone in fastboot mode as a different device than the phone in normal mode)
Download the file and extract it in the same folder as adb. (if you don't have adb yet, it's included in the android SDK for windows. go download it!)
Take out the usb cable and boot up your phone into the SPL (back + power). You have to have the dev bootloader for this to work (white background with 3 skateboarding androids).
Plug in the usb cable, and make sure the display on the phone changes from "Serial0" to "FASTBOOT". If it doesn't, try pressing the back button.
If it asks you to install drivers, then go ahead and use the same usb drivers that you used to get adb working. You can skip the rest of the instructions. Fastboot should be working for you now.
If it doesn't ask you to install a driver, you need to figure out if the correct driver is loaded already.
Right click on My Computer, and click Manage, then go to the device manager
If you see an "ADB Interface" category at/near the top, with "HTC Dream" under it, then you're good to go. Fastboot should be working for you.
If you don't see an "ADB Interface" category, then it's likely that windows loaded the USB Mass Storage driver for it automatically. In the device manager, go down to "Universal Serial Bus Controllers", and see if you have at least one "USB Mass Storage device". If you have multiple ones, you'll need to go through each to find the correct one.
To find the correct one, right click on the USB Mass Storage device and click Properties. Go to the Details tab. In the combo box at the top that says "Device Instance Id", bring up the pull down and choose "Compatible Ids". If that is the correct device, then you will see 3 entries:
USB\Class_ff&SubClass_42&Prot_03
USB\Class_ff&SubClass_42
USB\Class_ff
Once you find the correct device, go to the driver tab, and click "Update Driver". Choose "No, not this time", then "Install from a list or specific location", then "Don't search, I will choose the driver to install", and then choose the same usb driver that you used to get adb to work.
After that's done, you should be good to go. Open a command prompt and type fastboot devices and it should list the phone.
This is a great Christmas Present lol !!!!! Thanks again JesusFreke !!!!!
JesusFreke said:
I've compiled a fastboot binary for windows from the git source, using cygwin.
Click to expand...
Click to collapse
Just four minutes shy of delivering on Christmas day too I kid, I kid. Great work. This will be quite nice for those of us still working primarily in Windows. b
Really Good!!!!!!!
Thanks JF, not for the files, I already had them compiled but because I found out why they weren't working...
USB MassStorage driver was as well on! LOL Its the simple things sometimes.
That's fantastic thanks JF. Now since we got fastboot in windows how does that change the process for having our custom boot image. I could not for the life of me get fastboot to recognize my device in ubuntu no matter what I did.
pablizzo said:
That's fantastic thanks JF. Now since we got fastboot in windows how does that change the process for having our custom boot image. I could not for the life of me get fastboot to recognize my device in ubuntu no matter what I did.
Click to expand...
Click to collapse
Let me take a shot in the dark and say that it would allow you to do the "fastboot flash splash1 image.rgb565" part from windows instead of ubuntu?
Don't forget about koush's .NET application to convert an image to the correct format: http://forum.xda-developers.com/showthread.php?t=462489
Thank you JesusFreke!
Way faster than booting Ubuntu under Sun's VirtualBox
Pardon my ignorance, but all that I can see with search about fastboot is it allows us to flash cupcake and new splash screens.
Can someone enlighten me as to what exactly this is? Does it simply bypass key signatures or error checks? Being that I don't turn my phone on and off a lot, a custom splash is really not necessary and being that cupcake is severely limited, don't want to even toy with that until it has more work in it.
Thanks in advance!!!
anyone try this on vista 64 yet?
Damn, someone needs to hire you or something. You've got talent!
Ha, thanks. But it's not like I wrote it or anything. The windows code is all there. I just figured out how to get it to compile in cygwin. (and figured out the driver thing, of course)
Valicore said:
Damn, someone needs to hire you or something. You've got talent!
Click to expand...
Click to collapse
JesusFreke and Stericson need to partner up and start a company for Android apps.
I think your givin me too much credit....JF could handle the app shop all by himself, he's just that good
Stericson
THANKs alot i didnt feel i installing ubuntu on my laptop. once again thankss
hi，can i use this tool flash the cupcake to my G1？the driver is good，fastboot is good work，but when i use the command that FLASHALL，its told the products specified and android-products-out must be setted。i dont know whats that means~
"Waiting for device" with Fastboot
Edit: Got it working, thanks.
I've had issues with fastboot depending on which USB cable I used (I have different kinds with different shielding)... I assume my "cheap" cables didn't have enough shielding and corruption happened when trying to communicate... also noticed that this happened as well while using a USB hub... I now have a good cable connected to the BACK port of my PC... I used the back port because front ports have extensions running from the motherboard through the inside of the case that were making interference as well... hope this helps!
what the heck is fastboot?
Sorry, JF. What exactly is this?
texasaggie1 said:
Sorry, JF. What exactly is this?
Click to expand...
Click to collapse
http://www.gotontheinter.net/content/fastboot-cheat-sheet
hello all,
i had some small trouble setting up adb for my viewsonic gtab, so once i figured it out i thought i'd share.
so far, this is confirmed working only on windows 7 32 and 64 bit. vista should be the same, but i'm not sure, i'll keep you posted. EDIT: we've confirmed these steps for at least vista 32 and xp 32-bit. there shouldn't be any differences between the 32 and 64 bit systems as far as the instructions go.
most of my information comes from nvidia's tegra site, here. that's a pretty technical-minded page though, so i wanted to condense it.
make sure usb debugging is turned on for your tablet (settings -> applications -> development -> usb debugging)
1. open your device manager (right click My Computer -> Manage -> Device Manager)
if you haven't done anything to set up drivers yet, skip to step 4.
2. find your gtab. depending on your previous attempts, this may be under "Android Phone" at the top (Android ADB Interface, make sure it's your tab and not your phone), or under "Universal Serial Bus controllers" on the bottom (called Android somethingorother. should be at the top of the list.)
3. uninstall it. right click, uninstall. check the box that asks you if you want to delete driver software. i didn't need to use usbdeview to uninstall the drivers, but if you're running into issues on this step try it. usbdeview must be run as administrator, thanks droidjunkie.
it looks like most people should just skip right to usbdeview to uninstall any old drivers. like i said, i didn't have any issues using windows' "delete driver software" option, but apparently i was just lucky. rcgabriel recommends usbdeview, and he knows stuff.
4. unplug, and plug your tablet back in. now your device should be under "Other Devices" near the middle (will have a yellow exclamation icon, called NVIDIA harmony). good.
5. hopefully you have the android sdk installed. if you don't, go find a generic guide on setting up adb and then come back. when you have the sdk installed, you need to run "SDK Setup.exe" from where you installed it and use it to download and install the usb drivers (currently r8).
6. open the "usb_driver" folder in your sdk directory. right click "android_winusb.inf" and open it with notepad or your favorite text editor.
7. under the "[Google.NTx86]" section, paste the following:
Code:
;NVIDIA Tegra
%SingleAdbInterface% = USB_Install, USB\VID_0955&PID_7000
%CompositeAdbInterface% = USB_Install, USB\VID_0955&PID_7100&MI_01
save the file and exit.
8. go back into device manager. right click your tablet, select update driver, and click "browse my computer...", then "let me pick...", then "next", then "have disk"
if you're confused on this step, check this post.
9. browse to your android sdk, under the usb_driver folder, and select the "android_winusb.inf" file.
10. of the three choices, the bottom should say "Android Composite ADB Interface". choose it. click next, and allow the driver to install even though you get a big scary red warning.
11. open a command prompt, preferably in the tools directory of your sdk. type the following:
Code:
echo 0x955 > "%USERPROFILE%\.android\adb_usb.ini"
and hit enter. it will just return a new prompt line.
12. test it out.
Code:
adb kill-server
adb devices
you should see your device's serial number. all is well. congrats.
let me know if i should add or clarify anything here. thanks!
Just in case anyone doesn't know what ADB is:
http://developer.android.com/guide/developing/tools/adb.html
Thank you so much! Great info!
this is great! thanks for the concise writeup
I had trouble too. I was unable to get uninstall device to work and put the device under Other devices. I was advised to use usbdeview from pershoot. I used this program to remove the device and was able to get it moved to Other devices in Device Manager.
HTH
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 by iammuze, 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.
THANK YOU!!! after trying many different guides this one worked...other then the fact that I had to right click usbdeview and click "run as administrator" in order to delete the driver it keep installing when i would plug in my tab. I am on windows 7 32 bit, for anyone else having problems getting adb working that is using windows 7.
Thanks
I am finally connected via adb.
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 by iammuze, 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
I had the same experience on Windows 7 that you are having now. Like you, I tried following all the instructions similar to the ones listed above plus advice from other forums and still could not get it to work. I was finally able to get mine working after I discovered Windows still had some drivers from previous failed attempts stored in its system files. These old drivers were interfering with the proper installation of the new usb driver.
To get rid of the old drivers completely, do a file search for the file named android_winusb.inf in your Windows/System32/DriverStore. If your search results show several file folders with the same driver, try to delete each of the those folders completely. After those folders are deleted, you can do a clean install following iammuze's instructions.
NOTE: To delete those folders you will have to change the folder permissions. It won't be easy to do, because Windows doesn't like having its system files messed with. Unfortunately, I can't give you exact instructions on this, because I don't currently have a Vista machine.
rlapela said:
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!
Click to expand...
Click to collapse
where does your gtab show up under device manager?
Thanks, it worked great! ADB screen shots!
Look at this mess I have crammed onto one page.
[UPDATE: Problem solved: I had two versions of adb in my PATH and the old version (1.0.20) was being executed instead of the new version (1.0.26). Apparently the old adb silently fails and returns no devices when used in conjunction with the current drivers. I worked this out by accident. But if you're looking for ideas, there are lots in the ADB for Dummies thread: http://forum.xda-developers.com/showthread.php?t=502010 ]
Hi All
I've been banging my head against this for hours with no luck. I can't get adb to recognise my gTablet. Here's what I've done:
I'm on WinXP. gTablet is running zTab Clean 3.0
- I've downloaded the latest ADB USB drivers using the Android tools (driver verion 4.0, December 12 2010).
- I've made the modifications to android_winusb.inf noted above.
- USB Debugging is enabled on the gTab
- adb_usb.ini contains a single line containing: 0x955
I've followed various instructions and the driver install ~seems~ to go ok, but adb doesn't work.
Windows Device Manager lists the following devices which are associated with NVIDIA Harmony:
Android Phone > Android Composite ADB Interface
Universal Serial Bus controllers > USB Composite Device
Universal Serial Bus controllers > USB Mass Storage Device
USBDeview lists three devices:
NVIDIA Harmony NVIDIA Tegra 2 USB Device
NVIDIA Harmony USB Mass Storage Device
NVIDIA Harmony Android Composite ADB Interface
The first is listed as connected. The others aren't.
When run adb i get this:
> adb kill-server
> adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
No devices are listed.
I have tried many combinations of uninstalling these devices (with Device Manager and with USBDeview). When I reconnect I get prompted to install drivers. I have tried installing at this point, cancelling and then installing in Device Manager, not cancelling so the Plug and Play window stays open and uninstalling with device manager. None of this has worked. Also the device drivers seem to linger on my machine as they seem to auto-reinstall even after I have uninstalled them (I've also tried the suggestion of searching and deleting the .inf and .dlls from C:\Windows -- that didn't work out either).
I have also been careful to make sure adb is not running when I change the drivers. I have tried rebooting the computer and the gTablet after various installs.
The only way I can get the gTablet to appear in "Other devices" is to plug the device in (the PnP window pops up, I leave it open and ignore it). Then I delete the drivers in USBDeview. Then I unplug and replug the gTablet. Now there is one device in "Other devices": NVIDIA Harmony. Problem is, if I right-click "Update driver..." it won't let me install from the Android .inf, it says "The specified location does not provide information about your hardware." and forces me to install "USB Composite device". Once that's installed, two more NVIDIA Harmony devices appear in "Other devices". The first requires me to install "USB Mass Storage Device" (once again won't accept the .inf). The third does allow me to install "Android Composite ADB Interface". That gets me to the point where the drivers are loaded as listed above. But adb still lists no devices.
When I first started trying to set this up I had old drivers for the original HTC android phone installed. I deleted these with USBDeview.
I think that's all the information I have. Please let me know if you have any suggestions, I'd love to get this working.
Thanks!
A real plus would be screenshots, I'm getting a little confused at the device manager window, especially the part where it's supposed to give you the option "let me pick" > "have disk" > locate the .inf > choose the last of the three choices
I'm not getting any of those windows/options. Also, when I uninstall it, unplug the gTab, and plug it back in, it just re-installs the default Tegra driver. Any help?
Right now my device is showing up under "Disk Drives" as "NVIDIA Tegra 2 USB Device", and then also under "Portable Devices" as "G:\"
EDIT: Fixed! (Sorta)
I found another forum that told me that in Device Manager, select "Add Legacy Hardware" from the "Action" menu. After going through there, I was able to complete the steps you told me to. If anybody's having the same problem I had before, I am using Windows 7 64-bit, so that may be part of the problem? I'm not sure. But it's installed now and in Device Manager it's under the "Android Phone" section as "Android Composite ADB Interface".
However this raises a new problem, it has a yellow triangle with an exclamation mark over the icon, and it comes up with the error "Error code 10: Device cannot start".
Any help?
you edited the .inf file to contain the three lines specified, and selected the modified driver when adding the driver, correct? i'll try to add some screenshots for the dev manager section
after right clicking your gtab in device manager and selecting "update driver software" you should follow these steps to get going on win7 64-bit
http://dl.dropbox.com/u/5541925/drivergtab.png
Hi,
FYI, one thing to be careful of: In the thread where there's info about adding the 3 lines to the .inf, there's also a full .inf file.
If you try to use the full .inf file, note that it has references to various DLLs, which may, or may not match the DLLs in the driver install directory, so, if you use that full .inf from the thread, you have to adjust those DLL references to the ones for the DLLs you actually have on your machine.
In my case, I found it easier to just add the 3 lines to the .inf that came when I installed the USB driver files from the Android development website, which then worked.
Just an FYI...
Jim
iammuze said:
after right clicking your gtab in device manager and selecting "update driver software" you should follow these steps to get going on win7 64-bit
http://dl.dropbox.com/u/5541925/drivergtab.png
Click to expand...
Click to collapse
THIS IS PIVOTAL... This is where I had the hang up. Make sure that you are looking at iammuze's pic here, especially the 2nd image. by default most of us are used to just pointing to the correct directory where we DO have the modified .ini and it grabbed the wrong one. You HAVE to select 'let me pick'
Thank you iammuze for pointing this out. I think that's where most get lost. It haunted me for weeks as I was just 'skinning' through directions and missed this important step!
Just a quick suggestion - instead of trying to hunt around and fix drivers that are already installed and broken, I highly suggest using USB Deview (http://www.nirsoft.net/utils/usb_devices_view.html) which lets you nuke out the old drivers easily on a Windows Vista/7 machine.
I had old ADB drivers from my Nexus One sitting around, and I was unable to uninstall stuff with Device Manager.
Just run USBDeview **as administrator** if you are on Windows Vista/7 and you can uninstall old drivers for USB devices with a single click (in this case, just nuke any old Harmony drivers or other ADB drivers). Then the next time you plug in your G Tab, you should be able to select the proper drivers as suggested in the first post.
doesn't work
So i have also been trying for days and can't get it working right.
Running Windows Vista, have ADB installed, and can connect to other Android devices. I have setup the android_winusb.inf properly, but when I connect my device it shows up in Device Manager as a Portable Device->Tegra.
I have uninstalled the tablet and every other android device using usbdeview as admin
I have searched and destroyed all other usb.inf files.
i am running VEGAn-1.0.5B
No matter what happens, as soon as I plug in the tablet it immediately installs it as a Tegra Portable.
any help is appreciated!
that's very odd, i haven't seen that device description before. it doesn't sound like a vista issue... do you have another computer with vista on it anywhere that you can plug your gtab into? just to see what it reports to dev manager on a super clean system.
Old drivers were conflicting from previous installation attempts for me as well. All is working well once USBDeview was finally able to uninstall the device, however, it took multiple attempts and reboots for it to actually remove them. All is well now, and my Device is connected to the ADB. Thanks Everyone!
Unfortunately, there is no sub forum for this device yet so I'm putting it in general. I apologize if this is incorrect.
What (if any) information has anyone found out with with the Toshiba Excite? I've been searching many different forums and so far this is the only helpful piece I found from the Toshiba forums
I ordered an Excite as soon as it is available in the US market. As soon as I unboxed it, my first set was to enable the USB development option and plugged it into the computer. As usual, The ADB device drivers are not released by Toshiba. So I tried to use the same trick I used with THRiVE with stock ADB drivers.
Windows recognized the device but ADB doesn't. Isn't it wonderful? Since then I have been trying to access ADB using the EXCiTE without any success. What is it with Toshiba and ADB Drivers? I talked to the Customer Support and they acted like they had no clue about ADB drivers. So as a developer, the EXCiTE is a was of money.
It would have been salvageable even if Toshiba provided an option to enable ADB via TCP/IP which is trivial to Toshiba and will free them forever from providing a USB driver. But no luck.
So let me say this upfront. If I wanted a tablet that I could not develop Apps for, I would have purchased an iPad as without ADB both are equally useless to an Android Dev.
Click to expand...
Click to collapse
The Excite has a micro SD card reader and a micro USB built in. This is what I required for my ultimate goal.... I would like to unlock the bootloader and install Windows 8 onto a micro SD card. Then whenever I have the Windows 8 micro SD card inserted into the tablet, the tablet will boot from that first.
The hardware should be able to support it, but software wise will it be able to? If so, how would I get started?
Update from forums.toshiba
hi guys,
i just acheived adb connection to excite. It is not via usb but i can still work with it so i am not worried.
I found out that the adb works without any issues in the linux environment. So, i followed the steps outlined below,
1) enable usb development on excite.
2) plug it into a linux machine with adb working
3) run adb devices
4) we can see the excite listed
5) i executed 'adb tcpip xxxx'. Now the adb in excite is set to run via tcpip
6) now from the development machine execute 'adb connect yyyy:xxxx', where yyyy is the ip address of your excite and xxxx is the port you picked in previous address.
7) voila! Now you have adb working from you windows pc
i hope this helps folks with windows adb
cheers,
windozer
Click to expand...
Click to collapse
UPDATE (April 4th)
I messaged a Toshiba tech asking if Toshiba planned on releasing tools to unlock the bootloader. He said that he hadn't heard anything. I asked if he would be able to find out for me and this was his response
I can't talk about things that haven't been announced. I know that seems obvious for things like full products or major updates, but I'm not even allowed to comment on new tablet cases if they weren't released yet. It's even more strict with software updates!
Click to expand...
Click to collapse
You can install the Drivers from here:
http//)singledrivers.blogspot.pt/2014/01/toshiba-excite-pro-usb-driver-for.html
http//)support.toshiba.com/support/viewContentDetail?contentId=4001725
I installed them on my Windows XP SP3, and it worked for me!!
Follow the instructions carefully of the 1st site... since the drivers need to be manually installed.
Following the XP instructions...
If you want MTP connection, between step 6 and step 7 you have to select "MTP Device" interface (even if it's not certified!).
If you want ADB connection, between step 6 and step 7 you have to select "ADB Composite..." interface (even if it's not certified!).
NOTE: if you choose ADB simple interface it will not work, and you will have no ADB connection. it has to be the ADB Composite interface!
For some whatever reason I couldn't get them to work simoultaneously, only one at the time... so everytime I wanted to switch from MTP connection to ADB connection (and vice-versa), I had to reassign/reinstall the drivers again on Device Manager...
Hi,
I just extracted the latest USB driver (USB_Acer_1.0_USB_A700 A701), but there are Windows XP, Vista and 7 drivers inside only.
i tried to install the Windows 7 driver on Windows 8 64-bit, but had no success...
The one that isn´t working is the "USB composite device" driver.
I need any Acer Windows 8 USB 64-bit drivers for Android 4.0...
Will Acer release a Win 8 driver for the A700 in near future?
Hi,
You should try installing the Android SDK, which has general Android drivers inside them.
Connect your Acer device onto your computer.
Install the Android SDK and once the program has started, it'll (down)load and show you all the Android versions and tools.
Make sure you have only selected the checkboxes "Android SDK Platform Tools" and "Google USB driver". Now click on the right bottom button labeled: "Install packages".
Select the radio button: "Accept All" and click "Install".
Now click with the right mouse button on Computer, click Manage. Go to Device Manager. Right click Acer A700, click update driver software.
Choose "Browe my computer for driver software". Choose "Let me pick from a list".
Click all devices or/and Have disk..
Go to C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver\ and click the file under the 2 folders (android_winusb.inf)
Click on the first one and install.
Good luck and let me know if you succeed.
Edit:
You can skip the first part and download the Google USB driver I uploaded:
http://www55.zippyshare.com/v/1434863/file.html
Thank you very much it worked for me!
Thanks for the re-upload but there appears to be a problem with the contents of the zip file. When I try to extract it, I get this message: " the archive is either in unknown format or damaged". Could you download it yourself, or anyone,& see if you get that message.
Cheers.
EDIT: Thanks Tom for re-uploading again. It extracted OK this time. Unfortunately, I have had to send my A510 tablet in for repair, the charge light stopped working. I must admit to some ignorance in what to do with the unzipped files, as there is no installer for it, unlike a typical install of a USB driver. Perhaps you, or anyone, could educate me a bit?
theoldfarter said:
Thanks for the re-upload but there appears to be a problem with the contents of the zip file. When I try to extract it, I get this message: " the archive is either in unknown format or damaged". Could you download it yourself, or anyone,& see if you get that message.
Cheers.
EDIT: Thanks Tom for re-uploading again. It extracted OK this time. Unfortunately, I have had to send my A510 tablet in for repair, the charge light stopped working. I must admit to some ignorance in what to do with the unzipped files, as there is no installer for it, unlike a typical install of a USB driver. Perhaps you, or anyone, could educate me a bit?
Click to expand...
Click to collapse
Sure thing,
I explained it a little in my previous post, but I will try to explain it a little better this time.
1. Click with the right mouse button on Computer.
2. Click Manage.
3. Go to Device Manager.
4. Right click Acer A700 (or A510, OR anything that looks like an unknown android device), click update driver software.
5. Choose "Browe my computer for driver software". Choose "Let me pick from a list".
6. Click all devices or/and Have disk..
7. Go to the (extracted) folder you used from my upload in the previous post (usb_driver) and click the file under the 2 folders (android_winusb.inf)
8. Click on the first one and install.
Now Windows will recognise your tablet.
If you still don't get the hang of it, check out this video I found on Youtube:
https://www.youtube.com/watch?v=RbXatmo4QBU
The video may seem a bit dull, but it's actually useful if you really can't find any of the things I explained.
In the video, the "woman" explains on how you can find the Device Manager, on another way I explained.
Follow the instruction in the video until Step 8, which means you shouldn't follow step 8 but continue from my instruction from step 5.
Good luck!
Ps. If you really really don't get to install it, I would like to offer to do it for you (no charge, if that even was a question), if you trust a complete stranger on the internet (but you can abort any time). Just PM me.
Thanks. I will do this when my A510 returns from repair. It is waiting for a part to arrive from overseas, so don't know when it will return.
theoldfarter said:
Thanks. I will do this when my A510 returns from repair. It is waiting for a part to arrive from overseas, so don't know when it will return.
Click to expand...
Click to collapse
The A510 has returned. I have tried to install your driver but have no success.
At step 6, I get presented with "Show All Devices". I am shown a list of Manufacturers & Models. I choose nothing & click "I Have Disk".
I navigate to your folder & click on android_winusb.inf
I then click on "Install From Disk" button. I am then shown the option "Select The Device Driver You Want To Install For This Hardware".
There are 3 items shown: 1. Android ADB Interface, 2. Android Bootloader Interface, 3. Android Composite ADB Interface.
I choose number 1 as that is the one I beleive you mean in your option 8.
I click "Next" & get a warning about "Installing This Device Is Not Recommended Because Windows Cannot Verify That It Is Compatible With Your Hardware". I continue the install & after about a minute, I get this message "Windows Found Driver Software For Your Device But Encountered An Error While Attempting To Install It"... and..."Android ADB Interface".... and...."This Device Cannot Start (Code 10)".
The Device Manager now shows Unknown Device as "Android Phone".
Await your reply but am thinking about reinstalling Windows 7 & leaving Win 8 until I get a touch screen laptop & Acer Tablets get a USB driver for Win 8. Acer say they are on the way but can't/won't give me a date.
Windows 8 is an annoyance on my 4 year old Asus N50Vn laptop.
Without drivers, can you still access the SD?
@theoldfarter
That's odd, but can you try choosing the third option: 3. Android Composite ADB Interface.?
Maybe the drivers I uploaded are out of date in Windows 8 and you should try installing the Android SDK.
Install the Android SDK and once the program has started, it'll (down)load and show you all the Android versions and tools.
Make sure you have only selected the checkboxes "Android SDK Platform Tools" and "Google USB driver". Now click on the right bottom button labeled: "Install packages".
Select the radio button: "Accept All" and click "Install".
Click to expand...
Click to collapse
(android_winusb.inf) will be available at the following location:
C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver\
troun2000 said:
Without drivers, can you still access the SD?
Click to expand...
Click to collapse
Yes, you can. I just tried it with my freshly installed Windows 8 machine.
@TomONeil
Tried the third option: 3. Android Composite ADB Interface but get same error message.
Downloaded the Android SDK from your link & followed your instructions but get the same error message with both option 1 & 3.
I am wondering if it has to do with the A510 being upgraded to Jelly Bean (4.1.2)?
Here is a fellow who has Jelly Bean & Windows 7, where once he had updated to Jelly Bean, his Win 7 doesn't see the tablet anymore. His name is papyb & his post is the second up from the bottom, on page 2 here: EDIT, can't post the link. Darn the rules. lol.
I will try to PM you the link.
You can try install driver from Advance Boot Options. Select no.6: disable driver signature
I am succeed on Cyrus ATOMPAD.
misterkusut said:
You can try install driver from Advance Boot Options. Select no.6: disable driver signature
I am succeed on Cyrus ATOMPAD.
Click to expand...
Click to collapse
Mmm... you lost me there.I have no idea what you mean.
misterkusut said:
You can try install driver from Advance Boot Options. Select no.6: disable driver signature
I am succeed on Cyrus ATOMPAD.
Click to expand...
Click to collapse
Googled it & now know what you mean. That option is for Windows 7.
I use windows 8 & Google tells me this about it:
"7) Disable driver signature enforcement
The Disable driver signature enforcement option allows non-signed drivers to be installed in Windows 8.
This startup option can be helpful during some advanced driver troubleshooting tasks."
I will try this but when I tried installing the driver as per Tom's instructions, the driver in question said it was digitally signed.
misterkusut said:
You can try install driver from Advance Boot Options. Select no.6: disable driver signature
I am succeed on Cyrus ATOMPAD.
Click to expand...
Click to collapse
That won't work 'cause the driver can be installed, only it's not starting.
Do you have USB Debugging turned on in the Developer Options?
TomONeill said:
That won't work 'cause the driver can be installed, only it's not starting.
Do you have USB Debugging turned on in the Developer Options?
Click to expand...
Click to collapse
Did not have that turned on. Done so but makes no difference. I have just discovered that my built-in camera is not working with Win 8, Skype says there is no camera installed. It worked with Win 7. I am thinking that the "unknown" device in Device Manager is the camera, not my tablet.
No wonder I can't install the driver to it. lol.
With the tablet not connected, I uninstall the "unknown" device & then scan for changes & it shows it again.
It looks like the A510 is not recognised by Win 8 as anything, period.
I have had enough of Windows 8. It is causing more problems than it is worth. In a couple of days, I will reinstall Windows 7 & start over.
Will report back when all has finished, which may be in 6 days time.
Thanks for your help so far.
A700, mass storage and Windows 8
Hi
I have installed the USB drivers aa told here, an device manager shows my A700 under Android Phone.
But i cant see the storage.
How can i access both internal storage and SD card on my tablet??
theoldfarter said:
@TomONeil
Tried the third option: 3. Android Composite ADB Interface but get same error message.
Downloaded the Android SDK from your link & followed your instructions but get the same error message with both option 1 & 3.
I am wondering if it has to do with the A510 being upgraded to Jelly Bean (4.1.2)?
Here is a fellow who has Jelly Bean & Windows 7, where once he had updated to Jelly Bean, his Win 7 doesn't see the tablet anymore. His name is papyb & his post is the second up from the bottom, on page 2 here: EDIT, can't post the link. Darn the rules. lol.
I will try to PM you the link.
Click to expand...
Click to collapse
I would like this link as well. Since I've updated my a510 to JB 4.1.2, my computer doesn't detect it when I plug it in via USB. I can plug a USB stick into the tablet and it sees that, but when connecting to PC, nothing at all. USB debugging is also turned on. Would love some assistance with this.
http://www55.zippyshare.com/v/1434863/file.html
This is the USB driver.
When clicking on start and entering "device manager", a new screen will pop-up showing you all the connected devices. Somewhere you should see Unknown, Fastboot, ADB, Android device/phone, A700 or Acer. Install it with the USB driver.
Note for everybody:
If it is NOT working, try to find Android Phone in the categories list when installing the driver. That one might work too if my solution doesn't work.
dis method helped me...!
theoldfarter said:
@TomONeil
Tried the third option: 3. Android Composite ADB Interface but get same error message.
Downloaded the Android SDK from your link & followed your instructions but get the same error message with both option 1 & 3.
I am wondering if it has to do with the A510 being upgraded to Jelly Bean (4.1.2)?
Here is a fellow who has Jelly Bean & Windows 7, where once he had updated to Jelly Bean, his Win 7 doesn't see the tablet anymore. His name is papyb & his post is the second up from the bottom, on page 2 here: EDIT, can't post the link. Darn the rules. lol.
I will try to PM you the link.
Click to expand...
Click to collapse
try this link... http://www.fotoclubinc.com/blog/how-to-disable-driver-signature-enforcement-to-allow-installation-of-windows-7-printer-drivers-on-windows-8/
install the drivers with signature verification off
i too had the same problem on my xperia device
its solved now. :good:
Hi all first off I'm sorry if this has been posted before but I'm having a problem unbricking an Asus transformer tf101 B60, I'll start with what's going on or not for that matter. lol
1. Boot to recovery is CWM-Based Recovery v5.5.0.4 roach-tf101-r2
2. will not see sd card / backup-restore= -2014-04-05.02.52.56 / no files found
3. Choose a zip = e: can't open /sdcard/update.zip
4.PC windows 7 pro 64 bit will not see the tablet when plugged into usb getting unrecognized device,force driver still getting yellow ding=device cannot start
if I plug in the usb and turn on the tablet windows does not even see that and unit sits on logo screen. and other screen the cold lynx boot that hangs there.
So in short I'm hitting a brick wall, windows won't see it, it won't see the SD card in recovery mode.
I've read in these posts how to fix this problem and have all the software / firmware you name it, but they all say almost the same thing, windows needs to see the device in order for any of these fixes to work, and thus is my wall I'm hitting.
Any help to find a solution to this problem would be oh so thankful to you all and call you Tablet Gods, this was a tablet given to me as a paper weight and I thought if it boots it can be fixed?
Thanks for your time and God like tablet knowledge.
Cheers.
Install the APX drivers (Universal Naked Drivers) and use the tool "Easyflasher" to flash TWRP recovery (Forget CWM) both from this link
http://forum.xda-developers.com/showthread.php?t=1688012
You might need to install the APX drivers manually using Device Manager
If you find that the PC still does not see the TF101, you might need a new cable
Driver Not Working
*Detection* said:
Install the APX drivers (Universal Naked Drivers) and use the tool "Easyflasher" to flash TWRP recovery (Forget CWM) both from this link
http://forum.xda-developers.com/showthread.php?t=1688012
You might need to install the APX drivers manually using Device Manager
If you find that the PC still does not see the TF101, you might need a new cable
Click to expand...
Click to collapse
I booted the unit into recover mode and windows sees unknown device..Ok
Tried to install new naked driver and getting a splash saying not compatible with windows 64 bit, I tried this on a brand new windows 7 pro 32 bit laptop and got the same results. I do have a brand new usb cable for it thinking that the old one was faulty, tried adb again same thing no device found, are there any commands in terminal emulator that can force the driver on the usb port? I'm thinking that if windows sees an unknown device then at least it sees something there just not whats there? Am i wrong in that somehow it's lost the usb firmware connection? so the driver will not install and if forced does not make the connection to the device? So this is my results.
So I'm ready to put gun in mouth over this, my laptops going to divorce me over driver abuse and the tablet mocks me with the frozen Asus logo.
Again Thanks for all the advice and i'll keep slugging it out.As this unit is in perfect condition outside of the Bricked part
You don't need to boot it into recovery mode to start with, just install the drivers normally first with the TF101 connected and booted normally
It's always going to say it can't find the device if the driver isn't installed
Focus on getting that APX driver installed and working, once you have that installed, Im pretty sure it will see the device fine
Asus TF101 B60 Softbrick? What Now?
Hello all.
I've been searching in vain for an answer to my Bricked Asus tf101? I'm just going to get right to the problem.
I can't get the tablet to be seen by windows 7 pro 64bit, Unknown device and yes I've tried everything, except asking if there's a way to force connection through a terminal like I've seen done with a router and a network switch to force a flash file so as to get at least a response after a reboot instead of just the Asus splash screen, here's a summary.
The Good.
1. I can boot to recovery CWM-based recovery v5.5.0.4 roach-tf101-r2 with menu's
Bad: Does not see sd card only see's internal and there's no file or folder error for backup/restore
2.Boots to screen with 2 icons data wipe and linix cold boot and goes nowhere from there just hangs.
So I'm stuck here, I have all to tools to do the job only if windows would see it, Adb does not see device which means the same thing no driver no fix,
Everywhere I read it says do this and that and it will restore to factory, that would be great if windows saw the thing, so I'm looking for a way to get the tablet to boot to something other than a loop. also tried the put the E101_SDUPDATE.zip in the root of the SD card and restart, does not see the card or file or both so it's not loading the file?
1. windows 7 not seeing device, will not take force drivers, Universal-Nvidia-Asus- MTP
2. recovery does not see sd card, so can't flash new anything?
3. So no communication from SD/USB
4. Is there a terminal command I can use to force a Blob or flash a recovery to the tablet when drivers and USB don't respond?
And to top that off my laptop filed for divorce for driver abuse..lol I'm not giving up.
Thanks to you all,
I want to thank you all for your time and advice it is very much appreciated, and I'll keep slugging away because I know there's a fix out there.
Cheers.
Drivers need to be signed in 64bit windows, use 32bit Win 7 either on another machine or in VMWare or Virtualbox etc
Then the drivers should install
Thanks
*Detection* said:
Drivers need to be signed in 64bit windows, use 32bit Win 7 either on another machine or in VMWare or Virtualbox etc
Then the drivers should install
Click to expand...
Click to collapse
Thanks for the Advice, Is there a thread outlining this so I can give it a try? I do have a new laptop I'm building out with windows 7 Pro 32bit as I've had so much trouble with the 64bit version.
If you're building a 32bit Win 7 laptop, then no need for virtual machines, just use that laptop, this is the Easyflasher thread, you should only need to follow the couple of simple instructions once you have 32bit Win 7 running
http://forum.xda-developers.com/showthread.php?t=1688012
Basically in a nutshell:
1) Plug in TF101 to PC and make sure ADB debugging is enabled in Dev options on TF
2) Drivers will/should fail to install
3) Open Device manager
4) Right click the ! missing driver
5) Update driver > Point to extracted Universal Naked Drivers from Easyflasher thread
6) Drivers should install
7) Leave TF plugged into PC
8) Power TF off
9) Hold Volume Up & Power until the PC sounds the USB connect sound
10) TF is now in APX mode (Nothing on TF screen yet) drivers should install, check Device Manager, if it doesn't install, point it to the extracted Universal drivers folder again until they are installed
11) Follow instructions to use Easyflasher
12) Done
*Detection* said:
If you're building a 32bit Win 7 laptop, then no need for virtual machines, just use that laptop, this is the Easyflasher thread, you should only need to follow the couple of simple instructions once you have 32bit Win 7 running
http://forum.xda-developers.com/showthread.php?t=1688012
Basically in a nutshell:
1) Plug in TF101 to PC and make sure ADB debugging is enabled in Dev options on TF
2) Drivers will/should fail to install
3) Open Device manager
4) Right click the ! missing driver
5) Update driver > Point to extracted Universal Naked Drivers from Easyflasher thread
6) Drivers should install
7) Leave TF plugged into PC
8) Power TF off
9) Hold Volume Up & Power until the PC sounds the USB connect sound
10) TF is now in APX mode (Nothing on TF screen yet) drivers should install, check Device Manager, if it doesn't install, point it to the extracted Universal drivers folder again until they are installed
11) Follow instructions to use Easyflasher
12) Done
Click to expand...
Click to collapse
I am trying to get mine out of the reboot loop and cant seem to get it into APX mode to install the drivers.....any idea how go from here and have been trying step 9 above.
Will keep on trying to see if I can get it to work
Sicknote said:
I am trying to get mine out of the reboot loop and cant seem to get it into APX mode to install the drivers.....any idea how go from here and have been trying step 9 above.
Will keep on trying to see if I can get it to work
Click to expand...
Click to collapse
Need more info
What happens when you try to enter APX mode?
Which OS are you running on the PC?
Do the APX drivers install ?
etc etc etc
*Detection* said:
Need more info
What happens when you try to enter APX mode?
Which OS are you running on the PC?
Do the APX drivers install ?
etc etc etc
Click to expand...
Click to collapse
When i try to put it in APX mode, the screen goes black but pc does not see it. I have tried this bit lots of times and not sure if I'm missing something...
Have the drivers in a folder on my desk top. Have watched videos on YouTube but what i see is not happening when i try it...
OS is windows 7.
Drivers don't install.
Sicknote said:
When i try to put it in APX mode, the screen goes black but pc does not see it. I have tried this bit lots of times and not sure if I'm missing something...
Have the drivers in a folder on my desk top. Have watched videos on YouTube but what i see is not happening when i try it...
OS is windows 7.
Drivers don't install.
Click to expand...
Click to collapse
You're not going to be able to put the tablet into APX mode till you get the drivers installed correctly.
With the tablet connected to the computer and the tablet on, download the naked driver package. open up device manager and right click on Other Devices - APX and chose update driver. Chose browse and then go to where you downloaded the naked driver package. If it complains that they aren't signed, click install anyway. If successful, you should now be able to put your tablet in APX mode.