[Q] fastboot, win7/64 drivers? - Asus Transformer TF700

Hey all,
I've got a new-to-me TF700. Got CROMBi-KK installed, which took some backflips as I could not get fastboot connectivity.
I'd like to be setup for NvFlash (but then never need it), so even though I don't need fastboot right now, I'm feeling the lack.
Data transfer works fine.
ADB (not fastboot) works fine (adb shell gets me a shell, etc, etc)
When I put the phone in fastboot/bootloader "fastboot devices" gets an empty response "fastboot reboot" gets no response.
In Win7 device manager, the TF700, which appears in the "portable devices" section normally when I plug it in, does not appear.
So... probably device drivers.
Have you had this problem on your w7/64 box? How did you fix it? Sorry, but "install linux" isn't all that helpful.
Thanks!

From a semi-related question I'd asked, berndblb mentioned
berndblb said:
Windows is infamous for driver problems.....
Connect the tab in fastboot and open device manager. Near the top you should have an entry for Android device, bootloader mode or something similar, and probably a yellow ! next to it.
Right click it and choose "update driver", let Windows search for it.
If you're lucky it'll install the driver by itself.
If not: What Windows version are you running?
Click to expand...
Click to collapse
Yep, I get an "unknown device" in the USB section when I connect a TF700 in fastboot. Win can't find an appropriate driver. I've tried (manually) ASUS_Android_USB_Drivers and Universal_Naked_Driver_0.72 (both, AFAIR, from the xda tf700 forums). Neither worked.
So... if you got this going, what driver did you use? Thx!

I have a Win7 32 bit laptop and this cool little tool installed the drivers for me:
http://forum.xda-developers.com/showthread.php?t=2588979

berndblb said:
http://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
I'd installed that previously (easiest way to setup fastboot). Re-downloaded, re-installed. Went fine. Still no fastboot.
Unzipped the exe, looked at the drivers being installed - labeled "google". No google driver in the driver cache (so no device ever associated with it.)
Looked at the driver error again. Code 43. That means hardware or driver. I'd been taking it to mean driver, but... switched the USB cable to a port in the rear of the PC - and it worked.
Thanks!
So, for anybody with a similar issue, install the package above. If that doesn't work, maybe try a different USB port.

Related

Computers blind to NS4G. Help?

Hey folks.
I have been trying to get my wife's NS4G back to stock to get the JB OTA. I have downloaded all drivers multiple times on multiple computers (windows). I have tried 3 or 4 different USB cables. I have downloaded pdanet. I have downloaded the JAVA SDK and updated everything about it.
My computers cannot connect to the NS4G.
USB debugging is on. When I try to turn on tether, it tells me USB is not plugged in.
I have been able to restore the stock ROM (2.3.7) via CWM, but now I no longer have a recovery. It is still rooted and unlocked. Rom Manager is installed and it will not download CWM Recovery.
I need some way to get a recovery onto it. CMW or stock.
Does ANYONE have any suggestions?
Thanks in advance for all suggestions and particularly to the one that will work.
SemperFratres said:
Hey folks.
I have been trying to get my wife's NS4G back to stock to get the JB OTA. I have downloaded all drivers multiple times on multiple computers (windows). I have tried 3 or 4 different USB cables. I have downloaded pdanet. I have downloaded the JAVA SDK and updated everything about it.
My computers cannot connect to the NS4G.
USB debugging is on. When I try to turn on tether, it tells me USB is not plugged in.
I have been able to restore the stock ROM (2.3.7) via CWM, but now I no longer have a recovery. It is still rooted and unlocked. Rom Manager is installed and it will not download CWM Recovery.
I need some way to get a recovery onto it. CMW or stock.
Does ANYONE have any suggestions?
Thanks in advance for all suggestions and particularly to the one that will work.
Click to expand...
Click to collapse
If you are running Windows 7 hold down the shift key and right click then select open command prompt here. type ADB devices and if your drivers are installed then you will see your serial number. Remember to be in fastboot when you install drivers. then use ADB to reboot bootloader. when in fastboot type "fastboot devices" and you should again see your serial number to know that your drivers are all installed correctly. You need to fastboot flash a new recovery image. Hope that helps
ken3669 said:
If you are running Windows 7 hold down the shift key and right click then select open command prompt here. type ADB devices and if your drivers are installed then you will see your serial number. Remember to be in fastboot when you install drivers. then use ADB to reboot bootloader. when in fastboot type "fastboot devices" and you should again see your serial number to know that your drivers are all installed correctly. You need to fastboot flash a new recovery image. Hope that helps
Click to expand...
Click to collapse
Drivers are installed, as I can see my S3 fine as well as adb getting my serial number. The computer, nor adb, can see my NS4G. I have tried a desktop as well as 2 laptops.
Will be trying Vaelek's idea of wireless adb this evening.
Thanks for the suggestion.
Sent from my SPH-L710 (that's a Galaxy S3 to you) via tapatalk.
SemperFratres said:
Drivers are installed, as I can see my S3 fine as well as adb getting my serial number. The computer, nor adb, can see my NS4G. I have tried a desktop as well as 2 laptops.
Will be trying Vaelek's idea of wireless adb this evening.
Thanks for the suggestion.
Sent from my SPH-L710 (that's a Galaxy S3 to you) via tapatalk.
Click to expand...
Click to collapse
Drivers are NOT installed properly then. Drivers are installed on a per device basis. If your phone doesn't get recognized, then they are not installed.
Chances are your device ID isn't found in the .inf file of the drivers. I know back when I rooted my phone over a year ago I had to manually change the inf file and add my device.
If you start your phone in fastboot mode and plug it in, when you go in device manager you should see an unrecognized device with a yellow question mark. Right click it, then Properties, then Details tab. Give me the information in the Device Instance Path.
Will check this out and post info when I get home tonight. Thanks for the input.
Sent from my SPH-L710 (that's a Galaxy S3 to you) via tapatalk.
polobunny said:
Drivers are NOT installed properly then. Drivers are installed on a per device basis. If your phone doesn't get recognized, then they are not installed.
Chances are your device ID isn't found in the .inf file of the drivers. I know back when I rooted my phone over a year ago I had to manually change the inf file and add my device.
If you start your phone in fastboot mode and plug it in, when you go in device manager you should see an unrecognized device with a yellow question mark. Right click it, then Properties, then Details tab. Give me the information in the Device Instance Path.
Click to expand...
Click to collapse
Started phone in fastboot mode. Plugged it in and watched Device Manager. Closed device manager and re-opened it for a good refresh. I get nothing new. No unrecognized device and no Android Device like when I plug in my S3. ADB Wireless wont connect.
OK... I just cleared my sd card and was able to install CWM. One hurdle cleared...
I still need to get stock ROM and recovery. Is there anyway to do this WITHOUT being able to connect via adb?
Thanks again for any input.

[Q] Help Needed Accessing NVFlash

I'm having some trouble accessing NVFlash on my computer. I believe it's an issue with device drivers as when I connect my tablet I receive an error saying the drivers did not install correctly. When I try to access NVFlash with wheelie, the command prompt just sits at "Waiting for device in APX mode...". I've gone through the guide and tried searching the forums but can't seem to solve my issue. Can anyone help me?
ArmyAg08 said:
I'm having some trouble accessing NVFlash on my computer. I believe it's an issue with device drivers as when I connect my tablet I receive an error saying the drivers did not install correctly. When I try to access NVFlash with wheelie, the command prompt just sits at "Waiting for device in APX mode...". I've gone through the guide and tried searching the forums but can't seem to solve my issue. Can anyone help me?
Click to expand...
Click to collapse
You need to install the drivers specifically for APX mode from the driver pack on the AR.mobi site. (Don't let it search online). Once you do that boot up while holding power and the vol+up.
I grabbed the wrong set. Thanks for sending me back there.
Now that I'm able to run the wheelie, I get an error stating that nvflash is not recognized as an internal or external command/program/batch file. I don't remember reading anywhere that we needed to install nvflash, but maybe today is just one of those days.
EDIT: I'm blind. Found what I needed.
ArmyAg08 said:
I'm having some trouble accessing NVFlash on my computer. I believe it's an issue with device drivers as when I connect my tablet I receive an error saying the drivers did not install correctly. When I try to access NVFlash with wheelie, the command prompt just sits at "Waiting for device in APX mode...". I've gone through the guide and tried searching the forums but can't seem to solve my issue. Can anyone help me?
Click to expand...
Click to collapse
pls how were you able go get the driver for APX mode for tf700?
topdee said:
pls how were you able go get the driver for APX mode for tf700?
Click to expand...
Click to collapse
Here you goclick on "Windows" to download the driver package).
http://androidroot.mobi/2011/06/13/nvflash-on-asus-transformer/
buhohitr said:
Here you goclick on "Windows" to download the driver package).
http://androidroot.mobi/2011/06/13/nvflash-on-asus-transformer/
Click to expand...
Click to collapse
My laptop isnt accepting Universal naked driver as a driver. what do i do?
topdee said:
My laptop isnt accepting Universal naked driver as a driver. what do i do?
Click to expand...
Click to collapse
What do you mean by "is not accepting"? I had to disable online searching for drivers by Windows Update -- also make sure that you have really and absolutely removed all trace of the driver (Start Menu - right-click My Computer - Manage ... - Device Manager - right-click device - Properties Uninstall - choose Remove driver << this is from memory, it might be worded slightly differently, but you get the general idea). It kept picking the old driver on my computer otherwise...

[Q] Cannot Install Drivers for Fastboot

I am attempting to flash TWRP so that I can root and flash Cromi X to my tablet. ADB works fine, restarts/reboots into recovery, recognizes device. Fastboot does NOT see my device, does NOT reboot, and I am left stuck at "waiting for device" when I attempt to flash TWRP while in fastboot. In addition, my computer recognizes the TF700 while it is in launcher, but when I boot it into the bootloader/flashboot mode it does not recognize my tablet. I have attempted multiple times in multiple locations on my computer to get it to install & use the android_WinUSB.inf driver, but it refuses. I have uninstalled and reinstalled the drivers while the tablet is in on mutiple times. I don't know what else to do at this point; please help.
Device Details: ASUS tf700t, 10.6.1.14.8 firmware installed, unlocked, no root
Computer: Windows 7 x64
GoliboiVolk said:
I am attempting to flash TWRP so that I can root and flash Cromi X to my tablet. ADB works fine, restarts/reboots into recovery, recognizes device. Fastboot does NOT see my device, does NOT reboot, and I am left stuck at "waiting for device" when I attempt to flash TWRP while in fastboot. In addition, my computer recognizes the TF700 while it is in launcher, but when I boot it into the bootloader/flashboot mode it does not recognize my tablet. I have attempted multiple times in multiple locations on my computer to get it to install & use the android_WinUSB.inf driver, but it refuses. I have uninstalled and reinstalled the drivers while the tablet is in on mutiple times. I don't know what else to do at this point; please help.
Click to expand...
Click to collapse
Are you using windows?
Did you try this?
Transformer Toolkit v2.0.1
Root your device with motochopper: http://forum.xda-developers.com/showthread.php?t=2230763
and from the playstore download and install goomanager and from goomanager install TWRP.
Then from TWRP flash CROMi-X
GoliboiVolk said:
I am attempting to flash TWRP so that I can root and flash Cromi X to my tablet. ADB works fine, restarts/reboots into recovery, recognizes device. Fastboot does NOT see my device, does NOT reboot, and I am left stuck at "waiting for device" when I attempt to flash TWRP while in fastboot. In addition, my computer recognizes the TF700 while it is in launcher, but when I boot it into the bootloader/flashboot mode it does not recognize my tablet. I have attempted multiple times in multiple locations on my computer to get it to install & use the android_WinUSB.inf driver, but it refuses. I have uninstalled and reinstalled the drivers while the tablet is in on mutiple times. I don't know what else to do at this point; please help.
Device Details: ASUS tf700t, 10.6.1.14.8 firmware installed, unlocked, no root
Computer: Windows 7 x64
Click to expand...
Click to collapse
monecani's advice should work, although it would be good to have fastboot access to your tablet.
Weird - it seems the ADB drivers work but the fastboot drivers don't.
Try the drivers attached?
berndblb said:
monecani's advice should work, although it would be good to have fastboot access to your tablet.
Weird - it seems the ADB drivers work but the fastboot drivers don't.
Try the drivers attached?
Click to expand...
Click to collapse
Well I had tried motochopper around 20x before (and sadly, I am not exaggerating there) without it working once, but I felt that I should at least give it one more shot before saying I couldn't use it and of course now that I had asked for help it does work. lol; the IT curse strikes again. Thanks for that, monecani.
The drivers, on the other hand, are not working. :/ Windows is letting me try to install them now at least (before it was telling me there was "no compatible drivers" when I was literally having it select the ASUS specific ADB USB drivers, or just telling me that it had determined that my usb drivers that were in no way functioning were completely up to date), but then it fails install and says "This device cannot start. (Code 10)". I was able to install the drivers you gave me when the device was in launcher, but they didn't help me in fastboot, and actually interfered with my device being recognized properly by anything. I had to roll back the drivers to run motochopper.
I kinda agree with you on fastboot being something I don't strictly need, but would still be a good idea for me to have access to. Plus, I'm that special kind of person who cannot let something just be broken. It drives me crazy to know that something's wrong, even if I almost never use it, or even never use it.

[Q] Unbricked successfully, ADB broken?

Howdy, folks. I recently bricked my tablet thanks to a bad install of CWM, but following Buster's guide I was able to successfully reflash stock firmware and the device runs fine when booted up now.
However, now ADB is not detecting my device. At all. I have tried running the kill-server and start-server commands to see if that would do the trick to no avail. I'm not even receiving an error saying "device not found." Rather, the device listing is left blank whenever I enter the devices command into the command prompt. I can still send commands via fastboot, but I'm concerned that there's something here that I'm missing, or that I have somehow managed to completely bork the motherboard. I have already tried uninstalling and reinstalling the Asus usb drivers, in addition to the ADB drivers/software to no avail.
Does anyone have any suggestions to getting ADB to work for my tablet again? I have scoured the web, particularly these forums, for days looking for an answer, but haven't turned anything up yet. Any help would be greatly appreciated.
Does usb debugging is on?
Graiden05 said:
Does usb debugging is on?
Click to expand...
Click to collapse
Yes, USB debugging is enabled; yes that was the first thing I checked.
Any other ideas?
If You use asus drivers it worth to try universal naked driver.
Graiden05 said:
If You use asus drivers it worth to try universal naked driver.
Click to expand...
Click to collapse
I'll give that a shot this evening.
Graiden05 said:
If You use asus drivers it worth to try universal naked driver.
Click to expand...
Click to collapse
I just installed the naked drivers and tried again, but that didn't work either. Fastboot still works just fine, but I'm still at a complete loss as to how to get adb working again.
Thanks for your help thus far.
Hmm... How windows show tablet when You connect it to PC?
Graiden05 said:
Hmm... How windows show tablet when You connect it to PC?
Click to expand...
Click to collapse
Yeah everything *looks* normal, and appears to be acting normally whenever I have the tablet plugged in. When my tablet is booted up and connected to my pc, I can transfer files to and from with no issue. Also when it's plugged in, there are two different entries under the device manager (one for adb and the other for the tablet itself). It's only when I have my tablet running in bootloader mode that things don't seem to want to work correctly.
I even ran netstat last night to see if there were any programs/services using the same port as adb, and even that turned up nothing. Is it possible that I somehow inadvertently altered the settings on my tablet's motherboard when I installed a bad version of CWM, per my original post?
It shouldn't be posible to brick anything on motherboard with just flash wrong recovery. It might be just "too smart" windows, that reject to use adb driver on same device that alredy used by mtp one. It wasn't a problem before?
Graiden05 said:
It shouldn't be posible to brick anything on motherboard with just flash wrong recovery. It might be just "too smart" windows, that reject to use adb driver on same device that alredy used by mtp one. It wasn't a problem before?
Click to expand...
Click to collapse
It wasn't a problem until I flashed the wrong version of CWM, got stuck in a boot-loop and fixed the problem using fastboot to completely wipe my tablet and start over from scratch.
Edit: I suppose I could try a fresh install of Windows.
Try first remove all drivers and software for tablet. Then install universal naked driver.
Graiden05 said:
Try first remove all drivers and software for tablet. Then install universal naked driver.
Click to expand...
Click to collapse
Update: finally got adb to detect my device. Ended up removing everything Android-related from my desktop and re-downloaded/installed everything, including usb drivers. That did the trick.
Thanks again for the help.

Moto G USB Problem

Greetings, everyone!
Okay so a few days ago I fell asleep while using my phone, a Moto G 2014 (XT1068). At one point I wake up to see a window saying something along the lines of 'Updating X of X Apps" on a black screen. I put my phone on my bedside table and fall asleep again. When I wake up, the phone's off so I assumed it was done doing whatever it was doing (which I now think it was some sort of system update), so I turn it on only to find out it gets stuck in the Motorola logo loading screen. I've left it like that for maybe an hour and it's just stuck there. I've accessed Fastboot to try the Recovery option but it just returns a 'Boot Up Failed' message and if I choose the 'Factory' option (which I assume is a factory reset), it also gets stuck in the Motorola logo loading screen. The other options are 'Normal PowerUp', 'Barcodes' & 'BP Tools', none of them doing anything either. Upon some research, I figured it was probably some sort of update that crashed down the whole thing and that apparently a way to solve this would be to flash the phone with the Stock ROM, which I've already acquired (and hopefully it's the right one). Now, thing is, I need to connect my phone to the computer, which is running Windows 10, while on the Fastboot menu. This is where the problem comes in. I never enabled USB Debugging in the settings. I've also installed the Motorola Device Manager from the Motorola website because apparently it installs the drivers for the phone, but after installing the MDM countless times, I just don't see drivers anywhere. I've checked the Device Manager on Windows and there's no track of my phone's drivers in there whatsoever. There's no 'Other Devices' tab anywhere and my PC doesn't do that "device was plugged in" sound effect when you connect something through USB. I've downloaded ADB Drivers and different versions of Motorola Drivers but nothing seems to work. I've tried 6 different cables in 10 different ports, still nothing. The phone charges but it's like the PC doesn't detect it. While on the Fastboot menu, according to a few videos I've watched, it is also supposed to say a USB Cable is connected when you connect the phone to the computer, but even though my phone is connected to my PC, that never shows up. I don't know if this is because the drivers might not be installing on my computer or if it's because I never enabled USB Debugging in the settings. I've seen some people say it doesn't need to be enabled while in Fastboot but I don't know if that's true or not. So I'm pretty much out of ideas at this point, do you think something might be done?
Thank you in advance,
- Nervly
Hello, did you try typing in `fastboot devices` while in fastboot ?
-Hope- said:
Hello, did you try typing in `fastboot devices` while in fastboot ?
Click to expand...
Click to collapse
Hey, thanks for replying!
I did, but it wasn't recognized. I also tried 'adb devices' but it just returned an empty list of devices attached. Any other commands just returns <waiting for device> and I'm guessing this is all happening because the drivers might not be actually getting installed (considering there's no track of them in device manager) and/or because my PC doesn't detect the phone as connected through USB (even though it is). The PC doesn't play the sound effect of when you connect something to it and the fastboot menu doesn't display the message "USB Cable Connected" (or something along those lines).
Nervly said:
Hey, thanks for replying!
I did, but it wasn't recognized. I also tried 'adb devices' but it just returned an empty list of devices attached. Any other commands just returns <waiting for device> and I'm guessing this is all happening because the drivers might not be actually getting installed (considering there's no track of them in device manager) and/or because my PC doesn't detect the phone as connected through USB (even though it is). The PC doesn't play the sound effect of when you connect something to it and the fastboot menu doesn't display the message "USB Cable Connected" (or something along those lines).
Click to expand...
Click to collapse
Using a windows 10 and installing drivers may require you to disable drivers signature enforcements
Check here:
http://answers.microsoft.com/en-us/...ment-win/a53ec7ca-bdd3-4f39-a3af-3bd92336d248
Also go to device manager then press the view drop list > show hidden drivers
Check if the drivers are already there
If they are right click on them uninstall and reinstall drivers
Reply back :highfive:
-Hope- said:
Using a windows 10 and installing drivers may require you to disable drivers signature enforcements
Check here:
<link>
Also go to device manager then press the view drop list > show hidden drivers
Check if the drivers are already there
If they are right click on them uninstall and reinstall drivers
Reply back :highfive:
Click to expand...
Click to collapse
I'm off to a job interview right now but I will try the disabling drivers signature method you suggested once I get back.
As for the device manager, showing hidden drivers still doesn't list the phone's drivers or the 'Other Devices' tab, sadly. Perhaps after I disable the drivers signature enforcement and try to install the phone's drivers again it will work. I'll keep you updated!
Thank you for the help thus far!
-Hope- said:
Using a windows 10 and installing drivers may require you to disable drivers signature enforcements
Check here:
http://answers.microsoft.com/en-us/...ment-win/a53ec7ca-bdd3-4f39-a3af-3bd92336d248
Also go to device manager then press the view drop list > show hidden drivers
Check if the drivers are already there
If they are right click on them uninstall and reinstall drivers
Reply back :highfive:
Click to expand...
Click to collapse
Alright, I just got back and tried to disable the drivers signature enforcement thingy but it sadly still didn't work. The drivers still won't show up on the Device Manager and my phone still won't be detected by the computer. What's weird is that it seems like the drivers are being installed because there are some .sys files related to Motorola in my C:\Windows\System32\drivers folder but nothing will detect them.
Nervly said:
Alright, I just got back and tried to disable the drivers signature enforcement thingy but it sadly still didn't work. The drivers still won't show up on the Device Manager and my phone still won't be detected by the computer. What's weird is that it seems like the drivers are being installed because there are some .sys files related to Motorola in my C:\Windows\System32\drivers folder but nothing will detect them.
Click to expand...
Click to collapse
Fastboot drivers aren't same as USB drivers
They differ so if you want to work with fastboot you need fastboot drivers

Categories

Resources