Hi,
I tried a lot of other rooting applications and have had no luck with any of them. Then I found Wug's Nexus Root Toolkit. It works for my Nexus 4 (Jelly Bean 4.3) - until I came to the "Full Driver Configuration Guide" - where it gives a message: "ADB device was not found".
I have tried it over several times to no avail. Can anyone offer any clues as to what may be causing this?
btw, I am running the Wug's Nexus Root Toolkit v1.7.2 on Windows 8.
Thank you,
David
I was just having the same problem, and I realized after a while that I was making the STUPID mistake of not noticing that my phone was asking me to confirm USB debugging when the toolkit started searching for ADB devices. If you're as big of a dummy as I am (or just having an off day), this may be your problem
aaronwebstey said:
I was just having the same problem, and I realized after a while that I was making the STUPID mistake of not noticing that my phone was asking me to confirm USB debugging when the toolkit started searching for ADB devices. If you're as big of a dummy as I am (or just having an off day), this may be your problem
Click to expand...
Click to collapse
I am having the same problem. Where/how does the phone ask you to confirm USB debugging? It asks me when I turn it on, but not again later.
I have tried 3 or 4 different drivers, but, although the device is recognised by Windows 8, it is not recognised by Root Toolkit.
.... toolkits are the the devil...
They promote not learning what you're doing or what's actually happening in your devices so... there's posts like this.
please read this thread before touching your device
studacris said:
.... toolkits are the the devil...
They promote not learning what you're doing or what's actually happening in your devices so... there's posts like this.
please read this thread before touching your device
Click to expand...
Click to collapse
I'm not quite sure how this was supposed to help. My problem is that the ADB drivers do not seem to work on my computer. I have just tried installing the Android SDK (which comes with its own ADB drivers), having first uninstalled all the existing drivers. It did not help.
Not entirely sure where to go from here.
PDAnet's drivers may work. Simply install PDAnet (after uninstalling any previous attempted driver installations) to get the drivers.
studacris said:
PDAnet's drivers may work. Simply install PDAnet (after uninstalling any previous attempted driver installations) to get the drivers.
Click to expand...
Click to collapse
I had installed PDANet from within Root Toolkit, and it didn't work. Just now, I uninstalled everything again, and installed PDANet from their web site. Still get no ADB device in Root Toolkit. [NB I didn't have PDANet on the phone, but it seems to be there now]
I tried running adb from the android SDK, and it says "error: device not found".
However, I noted there was an adb prompt on the phone when I first plugged it in, this time (which I told to always accept).
[Later]
Wierd - it is now a bit further on. This is what I did:
Started PDANet on the phone, and enabled USB tethering.
Started PDANet on the computer, and it connected to the phone. At this point the USB debugging permission thing came up again, and I accepted it (also ticking the box to always accept).
Unticked USB tethering on the phone again.
Stopped PDANet on the computer (right click on icon, exit).
Tried the Root Toolkit again (pressed Root button), it connected to the device, and put it into fastboot mode.
The boot loader appeared on the phone, and the computer said "Checking Fastboot Status".
It seemed to stay like that for ever.
Killed the root toolkit. and tried again.
Left the computer for a while, and when I came back, it had completed.
So, it seems to be working now.
And when you try using fastboot directly instead of the toolkit....... what happens?
changing MTP to camera in USB connection mode did it for me...with MTP it showed correctly in device manager but the toolkit didn't recognise it
Gesendet von meinem Nexus 4 mit Tapatalk 4
studacris said:
And when you try using fastboot directly instead of the toolkit....... what happens?
Click to expand...
Click to collapse
I type "fastboot reboot" at the command prompt.
It replies "< waiting for device >"
I wait a few minutes.
Then I press ^C and the command prompt returns.
P.S. Changing the USB connection to camera doesn't make any difference to the above.
Best idea i didnt notice too
aaronwebstey said:
I was just having the same problem, and I realized after a while that I was making the STUPID mistake of not noticing that my phone was asking me to confirm USB debugging when the toolkit started searching for ADB devices. If you're as big of a dummy as I am (or just having an off day), this may be your problem
Click to expand...
Click to collapse
Thanx !!!!!!!
cmajetic said:
changing MTP to camera in USB connection mode did it for me...with MTP it showed correctly in device manager but the toolkit didn't recognise it
Gesendet von meinem Nexus 4 mit Tapatalk 4
Click to expand...
Click to collapse
Thank you so much! This solved it for me :good:
nikkilocke said:
I type "fastboot reboot" at the command prompt.
It replies "< waiting for device >"
I wait a few minutes.
Then I press ^C and the command prompt returns.
P.S. Changing the USB connection to camera doesn't make any difference to the above.
Click to expand...
Click to collapse
I got stuck the same way.
The way to got around was to change connection to camera -> the PC is intalling some drivers,
then turn off the USB debugging -> the PC is again installing some drivers,
then turn on the USB debugging -> "bingo" adb mode recognized by the toolkit
Now I can install and enjoy Kikat 4.4.1 :good:
cmajetic said:
changing MTP to camera in USB connection mode did it for me...with MTP it showed correctly in device manager but the toolkit didn't recognise it
Click to expand...
Click to collapse
I found the same solution, changing over from MTP to CAMERA suddenly had the toolkit recognise the phone and could boot it to unlock then root it... Previously, I had installed PDA drivers...
I am astonished how PATHETIC nexus phones/tablets are at simply connecting to a PC. I am baffled at the attempt by google to make their devices as UN-plug & play friendly as possible... bizarre! I have a N10, N7 and have had two N5's and all have the same PITA random disability....
grrr...
Mark.
So the Nexus toolkit is able to see the Nexus 7 as a media device but not Windows ?
marcelin99 said:
I got stuck the same way.
The way to got around was to change connection to camera -> the PC is intalling some drivers,
then turn off the USB debugging -> the PC is again installing some drivers,
then turn on the USB debugging -> "bingo" adb mode recognized by the toolkit
Now I can install and enjoy Kikat 4.4.1 :good:
Click to expand...
Click to collapse
So the Nexus 7 toolkit is able to see the Nexus 7 as media device with this method, but not Windows ? That's strange because Windows is supposed to see your files within the Nexus via Mtp mode. Is it that google removed the ability for Windows to be able to see Nexus 7 files in Android kit kat 4.4.2. What should I do then if I simply want to view files inside Nexus as a non root user ? B.T.W I'm currently on stock kitkat 4.4.2 build KOT49H. Therefore, I'd gladly appreciate it if anyone out there would answer this question and thanks in advance. Feel free to PM me on this so we can "talk" about this. : )
cmajetic said:
changing MTP to camera in USB connection mode did it for me...with MTP it showed correctly in device manager but the toolkit didn't recognise it
Gesendet von meinem Nexus 4 mit Tapatalk 4
Click to expand...
Click to collapse
Success.
Well, mtp connection works perfectly fine in my Windows 7 machine. But on my xp machine I could never get it to work no matter what driver combination I used.
I can see the reason they changed to mtp but I found mass storage to be much more user friendly.
Sent from my Nexus 4 using XDA Free mobile app
as others, I was using WUG kit to get back to stock. I was stuck without USB degugging options. Installing PDAnet did the trick, installing drivers so that I was able to get WUG working. I am now stock. All traces on my tinkering are gone. Later this week I will upgrade to a Galaxy Mega and trade in my Galaxy Nexus that I have loved for 3 plus years.
Stuck on fastboot screen
GranPaSmurf said:
as others, I was using WUG kit to get back to stock. I was stuck without USB degugging options. Installing PDAnet did the trick, installing drivers so that I was able to get WUG working. I am now stock. All traces on my tinkering are gone. Later this week I will upgrade to a Galaxy Mega and trade in my Galaxy Nexus that I have loved for 3 plus years.
Click to expand...
Click to collapse
Hi
Happy New Year to all! unfortunately I am left with the unusable nexus 7 that happened last night.
I was going crazy with the lags with lollipop and was waiting for the 5.0.5 update OTA but the delay was making me go crazy so I decided to take the risk of manually flashing the image using ADB and SDK.
Like many others pointed, I knew how to enable my computer to see my device by switching from MTP to PTP mode from my earlier rooting experience with Samsung, HTC and others. So that was not an issue for me.
I was following a tutorial from androidcentral and half way through I went to check a tutorial on youtube which I think caused the disaster. After I executed the adb devices no devices were detected and like I said I went and changed the MTP mode to off and bingo now my device was detected.
I executed device unlock and currently my device is in unlocked bootloaded state which is displayed in the fastboot screen where I am stuck now. Following the youtube instead of flashing each separately bootloader first and then the factory image I jumped to 'flash-all.bat' command...I saw something say on my command prompt on pc that completed in so many seconds or minutes which led me to get anxious and since no rebooting happened on the device I went and manually tried to press the power button.
From that time I am stuck on the fastboot screen. I can cycle through 'power off', restart booloader, recovery mode and start. But when I select 'restart bootloader' it comes to 'start' in the same mode and when I select that I can see a tiny 'Booting failed' in white letters in tiny fonts on the top left side of the 'Start'. I cannot go past this state.
Since I know the last time I had enabled 'usb debugging' and MTP off before everything went wrong I am presuming those states are still intact. I can see status on 'reboot bootloader' screen that my bootloader is unlocked.
Now, when I try to go through the process again my device is seen in device manager but when I send 'adb devices' command it cannot detect any devices. If my device is usable I can atleast go into settings to see if my MTP state and usb debugging status. Now I don't have that option. I even tried the Nexus Root Toolkit - everything is fine but until it tests the driver to finally say 'ADB device not found'.
After browsing so many posts I spotted there were some posts that said there is some discrepancy between the device id as listed by the driver to what actually is usb.inf, which all is too technical and overboard for me. And finally left me thinking that it is some issue of Windows PC as someone pointed that the ADB device was detected on a MAC. So I am now thinking to give it a shot in a mac machine as a final attempt to recover my device.
Anyone please suggest a solution, apologies if this is covered by someone elsewhere in the forum if so please point me there. I will make sure that from next time I will never do a manual flash of factory image.
please help!
It sounds like you are on top of it, but haven't hit the right combination yet. Thanks for the quote and I am sorry I am unable to offer any help. As mentioned in my post, I have switched to the Galaxy Mega and was pleasantly surprised by the OTA upgrade to 4.4. Now I am trying to figure out how to root it.
Hi, I'm a bit new to all of this, so forgive me. I've searched and can't find an answer to this question, so I'm guessing I missed something simple. I have a new moto g5 plus, didn't activate it on VZW yet, only went in and enable USB debugging and developer options. Unlocked the phone successfully, installed TWRP (I've tried 3 different versions in all of my attempts; 3.1.0.0, 3.1.1.0, and 3.1.1.0-GtrCraft-potter in case that was the problem). After TWRP, I've wiped the device and rebooted into the recovery, so I'm back at the main TWRP screen and my phone is plugged in to my computer.
After that, supposedly you can see your Moto G5 plus in Windows to copy over the other files to root the device, but it's just not there. My computer shows that when it's plugged in, there's a "GOOGLE NEXUS ADB INTERFACE" connected, but I don't see any additional drives on my computer to open it up and copy the files. I have MotorolaDeviceManager_2.5.4 installed, along with the minimal_adb_fastboot_v1.1.3_setup installed.
Any ideas? Thanks in advance!
gamespot said:
Hi, I'm a bit new to all of this, so forgive me. I've searched and can't find an answer to this question, so I'm guessing I missed something simple. I have a new moto g5 plus, didn't activate it on VZW yet, only went in and enable USB debugging and developer options. Unlocked the phone successfully, installed TWRP (I've tried 3 different versions in all of my attempts; 3.1.0.0, 3.1.1.0, and 3.1.1.0-GtrCraft-potter in case that was the problem). After TWRP, I've wiped the device and rebooted into the recovery, so I'm back at the main TWRP screen and my phone is plugged in to my computer.
After that, supposedly you can see your Moto G5 plus in Windows to copy over the other files to root the device, but it's just not there. My computer shows that when it's plugged in, there's a "GOOGLE NEXUS ADB INTERFACE" connected, but I don't see any additional drives on my computer to open it up and copy the files. I have MotorolaDeviceManager_2.5.4 installed, along with the minimal_adb_fastboot_v1.1.3_setup installed.
Any ideas? Thanks in advance!
Click to expand...
Click to collapse
Rule of thumb copy files to SD card first
My wife´s Z1 (which is on original 5.1.1) has been noughty recently. Phone calls (incoming or outgoing) can not be made because incoming voice sounds are not heard. It does not depend on what phone app is used, also the problem exists on WhatsApp calls as well. The problem is intermittent, comes and goes at random and is active far more often than not. Anyone has a clue to what the cause may be?
Anyway, I decided to try and wipe and upgrade the phone, hoping it is not a hardware fault and will disappear after upgrade. Then came next problem. The PC first reports that the attached USB device is not recognised, then, after repeated connections, the Z1 is just ignored by the Win10 PC. The PC has an old ADB-driver and Lenovo bridge installed since a previous operation on another Lenovo phone. I tried to connect to another Win10 PC without any ADB or Lenovo software, hoping to at least see it in the Explorer, but with eaxactly same result. Anyone has a clue to how I can make the Z1 recognizable again?
Every guide to flashing, be it TWRP or a rom, assumes that the phone is connected to a PC. But I have checked the internal recovery option, and it looks like you should be able to browse to an external SD-card to find a rom zip to upgrade from. Since this option is never mentioned in guides, why ca´nt you use it?
bjorni said:
My wife´s Z1 (which is on original 5.1.1) has been noughty recently. Phone calls (incoming or outgoing) can not be made because incoming voice sounds are not heard. It does not depend on what phone app is used, also the problem exists on WhatsApp calls as well. The problem is intermittent, comes and goes at random and is active far more often than not. Anyone has a clue to what the cause may be?
Anyway, I decided to try and wipe and upgrade the phone, hoping it is not a hardware fault and will disappear after upgrade. Then came next problem. The PC first reports that the attached USB device is not recognised, then, after repeated connections, the Z1 is just ignored by the Win10 PC. The PC has an old ADB-driver and Lenovo bridge installed since a previous operation on another Lenovo phone. I tried to connect to another Win10 PC without any ADB or Lenovo software, hoping to at least see it in the Explorer, but with eaxactly same result. Anyone has a clue to how I can make the Z1 recognizable again?
Every guide to flashing, be it TWRP or a rom, assumes that the phone is connected to a PC. But I have checked the internal recovery option, and it looks like you should be able to browse to an external SD-card to find a rom zip to upgrade from. Since this option is never mentioned in guides, why ca´nt you use it?
Click to expand...
Click to collapse
i also came across the same problem with my zuk z1 and windows 10 laptop. my phone also remained unrecognized till i found proper drivers for lenovo zuk z1 : LenovoUsbDriver_v1.0.12.zip, you can google for it as i am new so cant post url till xda allows me to post.
this worked for me. you also can try it.
a0879 said:
i also came across the same problem with my zuk z1 and windows 10 laptop. my phone also remained unrecognized till i found proper drivers for lenovo zuk z1 : LenovoUsbDriver_v1.0.12.zip, you can google for it as i am new so cant post url till xda allows me to post.
this worked for me. you also can try it.
Click to expand...
Click to collapse
Thanks for the tip. When googling for the driver, I actually found a newer one, v1.1.16.0, which also seems to work. But then a new problem appeared. When I activate Fastboot from the PC, the connection to the Z1 is immediately lost. Z1 will not connect again until I restart both the PC and the Z1. Actually, I found out, that you can set Z1 into Fastboot mode by itself. There is a setting in Developer Options that can do that. When I first connect Z1 to the PC and then enable Fastboot mode from the Z1, the result is the same, the connection to PC drops immediately. So, I cannot proceed to the next step to flash TWRP.
Does anyone have a solution?
Edit: I decided to uninstall the new Lenovo ADB driver and then found that the PC still responds to adb commands. Before I started to work on the Z1, I had another adb driver installed, which I used when working on another mobile phone. I had uninstalled it, before installing the new driver, but either that uninstallation left some remains or the uninstallation I just made left some remains. Now it seems I have some adb driver still in the PC and I have to find out how to locate it.
bjorni said:
Thanks for the tip. When googling for the driver, I actually found a newer one, v1.1.16.0, which also seems to work. But then a new problem appeared. When I activate Fastboot from the PC, the connection to the Z1 is immediately lost. Z1 will not connect again until I restart both the PC and the Z1. Actually, I found out, that you can set Z1 into Fastboot mode by itself. There is a setting in Developer Options that can do that. When I first connect Z1 to the PC and then enable Fastboot mode from the Z1, the result is the same, the connection to PC drops immediately. So, I cannot proceed to the next step to flash TWRP.
Does anyone have a solution?
Click to expand...
Click to collapse
you are right, you can set z1 into fastboot mode but then also it is not recognized by your pc. i suggest you to once again install the driver version which i specified . atleast i can say it worked for me !!, secondly there is a twrp version with min. adb tools in a zip file who's link i found when i was searching on youtube for installing twrp on zuk z1 (by: D Tech Terminal).
i did exactly what was asked to do in it and to my surprise my Z1 got twrp installed on it !!
now again same problem
i can't share the link.
you just search how to install twrp zuk z1 on you tube (by D Tech Terminal)
and you will get it.
hit thanks if it helps !!!
bro connect with old computer it work
Hi all,
My nexus 6p is not recognized by any PC since I flashed Resurrection Remix 6.1.0 [8.1.0_r33 Oreo] 5 months ago. I have been busy and never bothered about that. Recently I tried to flash StatixOS 9.0 and got stuck at the boot logo. I thought of going back to stock rom by using fastboot and wiped the memory. Now fastboot and ADB doesn´t recognize my phone and I am stuck with no OS and no option to flash one.
Previously I used my laptop several times to fastboot flash roms to my phone and it worked flawlessly, I have installed drivers again, used different PCs, swapped cables, USB OTG, tried Wugfresh, SDK manager drivers/manual drivers installation but none worked. PC doesn't even recognizes in other devices or anywhere in device manager.
Any possible solution? It does charge without any issues. Since flashing RR 6-1-0 it never even showed which type of connection I want (charging only/ MTP/ etc).... is this a software issue ?? what am I missing something here? or the daughter board needs to be replaced??
I have been through every possible threads in and outta XDA but no luck trying those tricks.....
TIA