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:
Related
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.
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.
As mentioned, I need to go back to stock in order to unlock my phone but it has been a very long time since I have done anything techy to this phone. I know I needed an RUU file (which one?) and drivers but I also read about it failing in Windows 10. Can anyone advise how I can unlock my Rogers evita device?
I should also note that after a bit of research, I am trying to flash the RUU (using the command 'astboot flash zip PJ83IMG.zip' without quotes) but it just says 'waiting for devices' even though fastboot is red and says fastboot usb... Is this the result of having Windows 10 (drivers do not work)?
I have installed the drivers and HTC sync/adb from, the following:
http://forum.xda-developers.com/showthread.php?t=2588979
It is still not useful. I should also note when trying to sync via fastboot, in device manager I see under USB (device failed enumeration).
I know it's a few months later, but if it can help someone, here is how I got ADB-Fastboot (especially Fastboot) working under Windows 10 64bit.
I'm pretty sure I remember correctly doing just that, after messing for days without success.
If you're not successful, I might be forgetting something.
(of course, I cleaned my PC removing any HTC driver and any ADB-Fastboot solutions I had installed before doing the 3 steps below, also cleaning the Windows Registry)
1. Download and install latest HTC Sync Manager, then uninstall Sync Manager keeping only the drivers installed.
2. Find and Install latest Minimal ADB and Fastboot.
3. Download and install latest Java SE Development Kit 32bit version (even for Windows 10 64bit).
Connecting phone to PC was recognized, started Minimal adb-fastboot and then typed adb devices, worked fine.
Rebooted the phone to Bootloader then put it in fastboot usb mode and typed fastboot devices, worked fine.
I am trying to unlock my bootloader (first time doing so) on my one plus 7 pro to get pixel experience 12 working. adb commands work well but once i'm in fastboot/recovery mode, my phone isn't recognized in the fastboot devices list, i assumed this was a driver issue since I have yet to find a working driver (my phone doesnt show up properly in the device manager) but the issue might come from some other source, here are the things i did and tried :
I am using a Windows 11 intel pc, plugged into both usb 2 and 3 ports since i have seen that people found different results with usb 2, i tried installing the drivers from android sdk platform tools from where I manually installed different drivers in the device manager since there wasn't a One plus specific driver(adb composite, android adb), none of which managed to be successfully installed. All of the instances of people finding drivers online either led me to expired links or a shady looking exe., i also tried using the all in one tool but installing drivers from there only returned "unable to install drivers", and unlocking the bootloader through it had the same result as when i tried manually, that is "waiting for device" after entering fastboot oem unlock.Any idea where i can find a driver for my phone?
tarek._.n said:
I am trying to unlock my bootloader (first time doing so) on my one plus 7 pro to get pixel experience 12 working. adb commands work well but once i'm in fastboot/recovery mode, my phone isn't recognized in the fastboot devices list, i assumed this was a driver issue since I have yet to find a working driver (my phone doesnt show up properly in the device manager) but the issue might come from some other source, here are the things i did and tried :
I am using a Windows 11 intel pc, plugged into both usb 2 and 3 ports since i have seen that people found different results with usb 2, i tried installing the drivers from android sdk platform tools from where I manually installed different drivers in the device manager since there wasn't a One plus specific driver(adb composite, android adb), none of which managed to be successfully installed. All of the instances of people finding drivers online either led me to expired links or a shady looking exe., i also tried using the all in one tool but installing drivers from there only returned "unable to install drivers", and unlocking the bootloader through it had the same result as when i tried manually, that is "waiting for device" after entering fastboot oem unlock.Any idea where i can find a driver for my phone?
Click to expand...
Click to collapse
Update : I used another pc, an amd laptop and used the tool all in one made by @mauronofrio and it worked perfectly, saving me from hours of trying things, so thank you for that!
I usually avoid this drama by disabling driver signature before installing OnePlus drivers on windows 11. Always works.
Hi
Noob alert here.
I'm trying to flash a custom recovery (twrp) on a very old phone which has its bootloader unlocked. (the phone currently runs android 6.0, yes, that old...)
I read on the forums here that I need to use ADB from windows (Win10 here) in order to flash twrp onto the phone (to replace the stock recovery).
I DLed the neccessary files (platform tools), but it's just a bunch of files with nothing to actually install AFAICT...
MAny tutorials mention that I should just launch a CLI from within the folder containing the tools and then run ADB to flash twrp.
However, I get stuck at < waiting for any device > which, according to other tutorials, isa sign that drivers are not installed for my device in windows.
Some tutorial mention that I should INSTALL ADB (rather than just run it from CLI), so I'm starting to wonder what I am missing here.
- Should I INSTALL ADB? how?
- Should I install drivers for my device? It seems like my device is properly detected by Win10 and I couldn't find any driver to install anywhere.
I'm confused about what's going on.
Could you please help me out here?
Thanks a lot for your advice.
Best,
-a-
OK, I made a little progress I think. I'm not sure my issue is actually related to windows drivers but maybe I'm wrong.
Here's the deal:
When my phone is booted and connected to my PC,
adb device
spits up something : the phone is detected. Now after running
adb reboot bootloader
the phones reboots into bootloader mode (and displays the info that the bootloader is unlocked. But from now on,
adb device
in windows CLI outputs nothing : the phone is no longer detected.
Plus now the phone shows up as an unnknown device (fastboot2.0) in windows device manager. So? Missing driver I guess?
Running windows update found a driver for
Google Android Bootloader Interface
So I guess now it should work
I'll post the results
Thanks a lot
-a-
nope...
No luck
ADB still cannot see my device when in bootloader mode
asheenlevrai said:
nope...
No luck
ADB still cannot see my device when in bootloader mode
Click to expand...
Click to collapse
Actually it works!
Even though
adb devices
would not list anything when the phone wwas in bootloader mode, I was able to flash twrp
problem solved!
In the future some commands in Bootloader Mode require fastboot oppose to ADB.