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.
Related
Hey guys I have unlocked my TF300T using the Asus tool.
I am able to into Fastboot mode on the device however in fastboot.exe the command fastboot devices returns no results.
I went back and tried everything with my Galaxy Nexus and that appears fine.
I have a feeling it is the drivers. The install fails when I plug it in giving a yellow question mark. I have tried the drivers from every link I can find on here and installed them manually. No go.
I also have the SDK which has the USB driver ticked and installed, but that does not seem to be helping.
Anyone know where I might find a driver that helps?
Ok seems I tried every single driver I could except for the one in the Asus install!
All good now and flashing
The phone is unlocked, with clockworkmod recovery 6.0.1.0 and stock rooted 4.1.1 ROM.
I'm using Windows 7 x64 SP1.
When the phone is ON and the debug mode is activated, it shows correctly under "device manager" and adb works right, but when I reboot in bootloader ADB doesn't see any attached device even if it shows correctly under device manager.
I tried to update the USB driver of the Android SDK but dosn't work
I then uninstalled it and tried to install the Universal Naked Driver (almost all of the nexus or samsung types) but doesn't work
I uninstaleld it and tried another USB driver found on the forum but doesn't work.
I tried to install Android SDK on another PC with Windows 7 x86 SP1 and repeat all the steps but it's the same.
How can I unroot and lock the device if it doesn't shows when in bootloader mode?
You don't use adb in bootloader. You use fastboot.
Locking the bootloader does not unroot by the way.
crespo80 said:
The phone is unlocked, with clockworkmod recovery 6.0.1.0 and stock rooted 4.1.1 ROM.
I'm using Windows 7 x64 SP1.
When the phone is ON and the debug mode is activated, it shows correctly under "device manager" and adb works right, but when I reboot in bootloader ADB doesn't see any attached device even if it shows correctly under device manager.
I tried to update the USB driver of the Android SDK but dosn't work
I then uninstalled it and tried to install the Universal Naked Driver (almost all of the nexus or samsung types) but doesn't work
I uninstaleld it and tried another USB driver found on the forum but doesn't work.
I tried to install Android SDK on another PC with Windows 7 x86 SP1 and repeat all the steps but it's the same.
How can I unroot and lock the device if it doesn't shows when in bootloader mode?
Click to expand...
Click to collapse
Have you tried the Nexus Root Toolkit by WugFresh? It is an application that takes you in several easy steps in installing drivers, rooting, and lock/unlock your device. For installing drivers there are several additional steps when installing them seems unsuccessful.
Leauwie said:
Have you tried the Nexus Root Toolkit by WugFresh? It is an application that takes you in several easy steps in installing drivers, rooting, and lock/unlock your device. For installing drivers there are several additional steps when installing them seems unsuccessful.
Click to expand...
Click to collapse
This is true, I've used Wugfresh toolkit too but I had some problem...
I've Nexus S 9023, with wug toolkit I had no problem to install driver with its very complete guide, this part can solve your problem but make attention on other function, for example with it I've also unlocked my phone but when I tried to root my device freeze.
So maybe that not all toolkit function will work well on all Nexus S.
Please stop with this toolkit nonsense.
Its not a driver issue at this point. Its the user using ADB instead of fastboot.
Remove this and that when he is just using the wrong command. This is the nonsense you see when all people know is some toolkit.
Yeah, I'm an idiot, that was not a driver issue
it's just because I usually root/unroot/unlock/lock my android phones once in a while (when I first buy and when I sell them), so I always forget some basic procedures and searching through the forums is always a mess, I spent three hours doing that, before posting...
I had forgotten ADB and fastboot weren't the same... anyway, I solved with WugFresh (I didn't know it, thanks for the tip) but I could have solved even with plain fastboot commands, I know
Anyway, I'm surprised to realize that the real stock ROM is more stable than the rooted and deodexed stock ROM I was using before, now the 3G/2G/airplanemode swithing is blazing fast and the performance drops on some games are gone... I'll never figure out this Android world
Thanks for all your help :victory:
I've been reading and researching for weeks and have finally decided to unlock and install twrp recovery. I have successfully unlocked, but that is as far as I can get. For some reason, my win7 pc thinks my tf700 is a Samsung android phone. In the pc device manager, under Samsung android phone is where my asus adb interface device shows up. Clicking on properties of the Samsung phone does not produce any drivers to uninstall and uninstallation of the phone works, but reinstalls when I connect my tf700. So, I'm stuck. I'm wondering if I can use twrp manager from the playstore to install 10.6.1.14.8.zip to downgrade and then root, install twrp from goo manager ? Fastboot method of installing twrp has not worked for me either, I'm thinking because of the drivers issue. Any one have any thoughts of where I can go from here ? I'd really like to get a custom rom on my tablet.
fwuser said:
I've been reading and researching for weeks and have finally decided to unlock and install twrp recovery. I have successfully unlocked, but that is as far as I can get. For some reason, my win7 pc thinks my tf700 is a Samsung android phone. In the pc device manager, under Samsung android phone is where my asus adb interface device shows up. Clicking on properties of the Samsung phone does not produce any drivers to uninstall and uninstallation of the phone works, but reinstalls when I connect my tf700. So, I'm stuck. I'm wondering if I can use twrp manager from the playstore to install 10.6.1.14.8.zip to downgrade and then root, install twrp from goo manager ? Fastboot method of installing twrp has not worked for me either, I'm thinking because of the drivers issue. Any one have any thoughts of where I can go from here ? I'd really like to get a custom rom on my tablet.
Click to expand...
Click to collapse
Strange problem. Did you have the drivers for a Samsung phone installed prior?
It would be good if you could solve the driver issue - just so that you have fastboot access to your tab in the future.
Sure, you could downgrade to .8 and use Motochopper to root, then GooMangager to install TWRP (though I have never heard of TWRP manager to install stock firmware???), a quick search on the forums will give you the steps.
But to solve the driver issue, you may want to try to install the Universal Naked Drivers from Google, or install the Android SDK tool and through it the Platform Tools and drivers. I would prefer the latter.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
berndblb said:
Strange problem. Did you have the drivers for a Samsung phone installed prior?
It would be good if you could solve the driver issue - just so that you have fastboot access to your tab in the future.
Sure, you could downgrade to .8 and use Motochopper to root, then GooMangager to install TWRP (though I have never heard of TWRP manager to install stock firmware???), a quick search on the forums will give you the steps.
But to solve the driver issue, you may want to try to install the Universal Naked Drivers from Google, or install the Android SDK tool and through it the Platform Tools and drivers. I would prefer the latter.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
Click to expand...
Click to collapse
yes, I rooted, twrp'd and installed bone stock on my vzw gs3.
I have used guides to install platform tools, put them in my PATH so I could use a cmd prompt from anywhere, plus I've tried to install the naked drivers and everytime I connect the tablet it goes through the installing drivers through windows update and and says my 700 is a Samsung phone. I uninstall the drivers, don't let it use windows update for drivers, and point it toward naked drivers folder (unzipped) and it doesn't install. says I still have a Samsung phone. click on Samsung phone in device manager and have asus adb interface under it. I must be missing something. maybe I'll redo my platform tools and see if maybe I missed an important step or typed something wrong. when I connect my 700 to the pc in fastboot, it isn't recognized. what should be happening ? what should I be seeing ?
fwuser said:
yes, I rooted, twrp'd and installed bone stock on my vzw gs3.
I have used guides to install platform tools, put them in my PATH so I could use a cmd prompt from anywhere, plus I've tried to install the naked drivers and everytime I connect the tablet it goes through the installing drivers through windows update and and says my 700 is a Samsung phone. I uninstall the drivers, don't let it use windows update for drivers, and point it toward naked drivers folder (unzipped) and it doesn't install. says I still have a Samsung phone. click on Samsung phone in device manager and have asus adb interface under it. I must be missing something. maybe I'll redo my platform tools and see if maybe I missed an important step or typed something wrong. when I connect my 700 to the pc in fastboot, it isn't recognized. what should be happening ? what should I be seeing ?
Click to expand...
Click to collapse
Once connected in fastboot, if you type 'fastboot devices' (without the '), you should see the serial number of your tablet. Otherwise you see: No devices found or something to the effect.
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.
Hello everybody, I was trying to update my Magisk and that process failed. I thought nothing of it put it off. Tried to restart my phone a few days later and now it's stuck in a fastboot loop. Cannot even go into recovery. So I'm like okay, probably need to reinstall recovery and flash a clean rom again. Try the "fastboot boot recovery.img" command and it's giving me a "waiting for any device". Googling says it's a driver error, but that's strange because I have used my phone on this computer before with ADB and fastboot. Fastboot and ADB commands work fine on my Oneplus 3T.
A week ago I also had the problems after the Magisk update. But connecting to the PC worked normally for me. Once you've installed the drivers, there shouldn't be any problems. You could use a different cable.
Incidentally, Magisk only messed up the boot image. It is sufficient if you flash your boot.img, then the twrp.zip, reboot into recovery, then the magisk.zip.
That was completely enough for me. Cell phone works normally again, without data loss.
Good luck!
Yeah that's exactly what I am trying to do, I can't even flash the boot.img to get into recovery, my computer won't recognize the device for some reason now. Do you know where I can find the drivers? I could only find shady 3rd party sites. Thanks!
Tried installing drivers from here, no change.
Download Latest OnePlus USB Drivers for Windows and Mac
Download The Latest OnePlus USB Drivers For All OnePlus Android Smartphones. We Have Included USB drivers for Both Windows And Apple MAC OS Users. Download Links Given Below.
www.getdroidtips.com
This is installed and works with me
ghost323 said:
This is installed and works with me
Click to expand...
Click to collapse
No joy, looks like that's the same file as the one I downloaded. Thanks for your help anyways.
Now I can't even turn my phone off lol. It woke itself up this morning magically and now whenever I hit power off in fastboot it just boots up again into fastboot. Might have to send it in...the horror
Your phone is crying out for help. It doesn't like to die.
I think you will have tried everything possible. Have you already connected it to another computer with the right drivers? Tried other cables?
ghost323 said:
Your phone is crying out for help. It doesn't like to die.
I think you will have tried everything possible. Have you already connected it to another computer with the right drivers? Tried other cables?
Click to expand...
Click to collapse
Haha yeah, it's like your kid who refuses to go to bed and is throwing a tantrum. Yeah two different computers that are known to have worked with this phone in the past (how I unlocked the bootloader in the first place). Different ports, different cables. It seems like I'm having the same issue that a lot of other people are having with the last Magisk update, except they're able to flash the recovery image in fastboot to get back running.
This is a ****ty situation! That was really a nasty magisk update. I wonder why its consequences are so different, even though it is the same cell phone.
fastboot cannot recognize device but adb can
usb debugging is enabled on device. running latest version of adb, fastboot. Have tried on both mac and win10 but same issue on both. Oneplus 7 pro is running 10.3.0GM21AA >fastboot devices >adb devices List of devices attached 966c8016...
forum.xda-developers.com
Look at this. Maybe it will help you so that your computer recognizes the cell phone again.