Database Users

[Q] Wugs Nexus Root Toolkit stuck on "ADB Device Not Found"

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.

[Q] Nexus 7 (2012) Bootloop NO USB DEBUG

I have searched high and low for a forum where the same problems are presented. I have had no luck at all. So, I hope that I'm not driving anyone nuts here, but here goes
I have a 2012 Nexus 7. I am using this tablet to learn all about how to work with android software, ROMS, kernals, etc. It is unlocked and rooted. I have TWRP. It is currently stuck in a bootloop (I tried to install a custom ROM) and I have no idea if USB debug is on or not. When I connect the tablet to my PC, it will charge and the computer acknowledges that SOMETHING is connected but will not find the tablet itself. (ie: I cannot find the tablet icon to click on). I have been to dev manager and I cannot find it there either.
I have no idea what anyone is talking about with this abd sideload. Most of what is said is greek to me. If someone would be willing to explain that to me (in english) I would love to learn.
Obviously, I am in above my head and I really could use some genuine help here.
I just want to flash this thing back to stock. Could someone please explain to me how to accomplish this?

deejinfla said:
I have searched high and low for a forum where the same problems are presented. I have had no luck at all. So, I hope that I'm not driving anyone nuts here, but here goes
I have a 2012 Nexus 7. I am using this tablet to learn all about how to work with android software, ROMS, kernals, etc. It is unlocked and rooted. I have TWRP. It is currently stuck in a bootloop (I tried to install a custom ROM) and I have no idea if USB debug is on or not. When I connect the tablet to my PC, it will charge and the computer acknowledges that SOMETHING is connected but will not find the tablet itself. (ie: I cannot find the tablet icon to click on). I have been to dev manager and I cannot find it there either.
I have no idea what anyone is talking about with this abd sideload. Most of what is said is greek to me. If someone would be willing to explain that to me (in english) I would love to learn.
Obviously, I am in above my head and I really could use some genuine help here.
I just want to flash this thing back to stock. Could someone please explain to me how to accomplish this?
Click to expand...
Click to collapse
You need to read first. Then flash. If you kill your device then you won't learn too much. Start with this thread --> http://forum.xda-developers.com/showthread.php?t=1907796.
You will probably need to install the naked Android fastboot drivers (search!) to proceed through the thread, since you can't put the device into USB debugging.
Anyway, to answer your questions:
adb (Android Debug Bridge) is a tool that allows a computer to control low-level features of an Android device. adb sideload allows you to send an app or ROM from your computer to your device (usually in a custom recovery) and install it, which helps if you've accidentally killed everything on your internal memory. However, you need a custom recovery (CWM/TWRP) to use adb sideloads.
You're better off learning how to use fastboot, which is a bootloader-based tool that helps a lot with disaster recovery.

Okay, I guess I need more help. I don't understand how I am supposed to be able to use fastboot to bypass the "enable USB Debugging". If I could get this to happen, I believe I can get my device back to stock. Can you explain this to me? NONE of the descriptions online are of any use at all.

Just reboot your device using power boutton and volume+ and volume- buttons to access to bootloader mode I suggest you to use nexus root toolkit it's very simple and usefull
Sent from my Nexus 7 using XDA Premium 4 mobile app

Nexus CANNOT ENABLE USB DEBUGGING
Can I ask for your help guys? My Nexus 7 v1 is stuck on boot loop (either stuck on google screen or sometimes would proceed up to the nexus animation screen) and I've been trying to fix it with the Nexus Root Toolkit (NRT). I just have problem proceeding with the steps since the toolkit advices me to enable my device's USB DEBUGGING (open device , go to settings, then developer options etc) which I CANNOT POSSIBLY DO COS AGAIN, NEXUS IS JUST STUCKED ON BOOT LOOP.
Can you suggest OTHER ways I can enable USB Debugging in Nexus 7? I would greatly appreciate your help.

You don't need to get into USB debugging mode, as your goal is to reflash a stable ROM onto your device. You can do that with Fastboot commands when your N7 is in the (unlocked) bootloader. You can follow the instructions in the second thread in this forum, or tell NRT you're soft bricked, to install a factory ROM.

[Q] How to sideload kernel with USB Debugging enabled?

Hi all,
I greatly need your help or some advice. I searched for more than 6h yesterday and Im surprised I couldnt find a solution to my problem.
Typical stuff : I broke the screen of my Nexus 4, that is completely stock 5.0.1. The phone is unrooted, bootloader is locked and obviously USB Debugging is disabled.
I need to backup some data from my phone : pictures, notes and if possible my contacts.
When I connect my phone via USB to my PC, I cant browse my files since my screen is locked. My screen is not responding at all, so no way I can unlock it. Only thing I can do is install new applications on my phone, but no way to launch them since I'd need to unlock my screen again.
I have installed adb and fastboot in order to try and use Android Screen Control, but I dont have USB Debugging enabled.
So I read that I could sideload a kernel that has USB Debugging enabled by default.
I got into Recovery Mode, and tried sideloading a zip file containing a Kernel found on the forum, but I always get an error saying the footer is wrong and the signature of the file didnt pass verification. I guess I can only sideload OTA updates ?
I tried fastbooting CWM recovery, that also didnt work.
adb devices command lists my 'recovery' device.
At this stage, all I need is to either be able to unlock my phone so I can access my files via USB (i tried few apps without success), or to enable USB debugging so I can connection using sideload, use Android Screen Control, reset the pattern lock, and backup my phone.
Also, USB OTG isnt enabled by default on Nexus 4, so that's another dead-end
So what are my options ? Where could I find a kernel that has USB Debug enabled, and how can I sideload it considering phone is not rooted, and bootloader is locked (unlocking it and whipping data defies the purpose).
THANK YOU for any advice!

There is nothing you can do with a locked bootloader and no custom recovery. Sorry man, but you're not going to be able to access your data.
Sent from my Nexus 9 using XDA Free mobile app

I've exactly the same problem, but my bootloader is unlocked and I'm rooted.
I'm also on a Nexus 4 with 5.0.1 and I'm trying to get control over my device from my Windows PC. But I don't know which kernel to use and how (yet) to enable USB debugging.
Help is appreciated.

Joakim_Lind said:
I've exactly the same problem, but my bootloader is unlocked and I'm rooted.
I'm also on a Nexus 4 with 5.0.1 and I'm trying to get control over my device from my Windows PC. But I don't know which kernel to use and how (yet) to enable USB debugging.
Help is appreciated.
Click to expand...
Click to collapse
All you need is a custom recovery to boot into to access your files. If you don't have one, download the latest version of twrp from here. http://techerrata.com/browse/twrp2/mako
Then flash that using fastboot. If you need help let us know.
Sent from my Nexus 5 using XDA Free mobile app

Hmm, "error: cannot load 'open recovery-twrp-2.3.2.3-mako'.
Sure usb-debugging doesn't have to be enabled?

Joakim_Lind said:
Hmm, "error: cannot load 'open recovery-twrp-2.3.2.3-mako'.
Sure usb-debugging doesn't have to be enabled?
Click to expand...
Click to collapse
You have an ancient version of twrp. Install the latest. I'm positive you don't need usb debugging enabled.
Sent from my Nexus 5 using XDA Free mobile app

Yes, you're so right! I also missed .img in the command
But what kernel would you recommend me to use so I have usb-debugging I can have usb-debugging enabled?

I am in almost completely the same situation! My N4 fell yesterday and shattered at the bottom right hand corner. No the touch screen doesn't work and there are sections of the screen that are black. However, I have...
root
cwm recovery
stock 5.0.1 kernel
windows 7
adb not working
fastboot working
usb debugging disabled
a need for usb debugging to become enabled.
I would like a kernel with usb debugging enabled and instructions on how to install it. Or if you have another fix, instructions on that.

Fastboot Won't Recognise My Nexus 6p

Hi all,
I am trying to root my phone, following this guide: http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
However, I am stuck at entering 'fastboot devices' into the command prompt. It will not return my device's serial number. I know this is supposed to be becuase I don't have the correct drivers installed - but I'm pretty sure I do! I've spent hours scouring the internet for solutions and I can't find anything to help. So now I turn to you, please help me
I'm running windows 10.
I've double checked the google usb driver is installed.
I've manually installed the android bootloader interface driver.
The bootloader screen says on my phone says 'Connect USB data cable'. It is already connected and I have tried connecting it to all the ports on my laptop. I'm using the original cable that came with the phone.

Well did you enable USB debugging? I'm assuming you did but you didn't list that in the process you said you did.

Eric214 said:
Well did you enable USB debugging? I'm assuming you did but you didn't list that in the process you said you did.
Click to expand...
Click to collapse
I did indeed. And I also fixed it! I just needed to do some more tinkering. I set the fastboot.exe to recommended defaults. Not sure why it was not already but there you go. You can lock or delete this thread now, thanks!

[Samsung Galaxy J5 2017 SM-530F/DS] Broken screen – a way to backup?

Screen in my J5 2017 broke and I cannot unlock it anymore so I tried to make a backup via PC. I blindly rooted my phone and installed TWRP, which went OK. Then I tried to use ADB with no avail – the device isn’t listed. I got all the drivers and everything and all what shows up in the device manager is "MTP device" so I assume that my phone is stuck in MTP mode and that’s why it is not recognised by ADB. Can anybody confirm it? Does MTP mode prevents from using ADB? Also, I don’t have USB debug mode enabled but after doing some research I found out that it won’t be necessary – I’d just need to boot into TWRP and use ADB. So the only thing keeping me from making a backup of my phone is that the device isn’t listed in ADB.

Infinitiv said:
Screen in my J5 2017 broke and I cannot unlock it anymore so I tried to make a backup via PC. I blindly rooted my phone and installed TWRP, which went OK. Then I tried to use ADB with no avail – the device isn’t listed. I got all the drivers and everything and all what shows up in the device manager is "MTP device" so I assume that my phone is stuck in MTP mode and that’s why it is not recognised by ADB. Can anybody confirm it? Does MTP mode prevents from using ADB? Also, I don’t have USB debug mode enabled but after doing some research I found out that it won’t be necessary – I’d just need to boot into TWRP and use ADB. So the only thing keeping me from making a backup of my phone is that the device isn’t listed in ADB.
Click to expand...
Click to collapse
You need to have USB debug unlocked to use ADB even in recovery

Haxomen said:
You need to have USB debug unlocked to use ADB even in recovery
Click to expand...
Click to collapse
This blog entry states otherwise (around paragraph 3). Is it model‐specific or is the blog author simply wrong?

Infinitiv said:
This blog entry states otherwise (around paragraph 3). Is it model‐specific or is the blog author simply wrong?
Click to expand...
Click to collapse
He does not say that your USB debug can be turned off. He does not even mention it

Haxomen said:
He does not say that your USB debug can be turned off. He does not even mention it
Click to expand...
Click to collapse
Yes he is. The whole point of this blog entry is that he didn’t have USB debug enabled and he worked around it to make his backup. He describes how he felt hopeless when he found out that USG debugging is disabled (see the third picture in the blog entry) and that he had to manually turn the phone:
We can't use the screen, (or an adb reboot recovery command - USB debugging is not enabled) so we'll have to pop the battery out to turn the device off.
Click to expand...
Click to collapse
So, yeah… It seems that he did everything without USB debbuging enabled. So my question still stand – is he wrong or is it model‐specific? Or maybe I’ve done something wrong?

Infinitiv said:
Yes he is. The whole point of this blog entry is that he didn’t have USB debug enabled and he worked around it to make his backup. He describes how he felt hopeless when he found out that USG debugging is disabled (see the third picture in the blog entry) and that he had to manually turn the phone:
So, yeah… It seems that he did everything without USB debbuging enabled. So my question still stand – is he wrong or is it model‐specific? Or maybe I’ve done something wrong?
Click to expand...
Click to collapse
If he managed to do it, try it yourself, maybe you will be able.

Haxomen said:
If he managed to do it, try it yourself, maybe you will be able.
Click to expand...
Click to collapse
As I stated in the first post of this thread I tried it with no avail and now I’m looking for some help from people with serious knowledge on the topic.

Infinitiv said:
As I stated in the first post of this thread I tried it with no avail and now I’m looking for some help from people with serious knowledge on the topic.
Click to expand...
Click to collapse
I tried to use adb on my J5 2016 within TWRP 3.1.1 recovery, while USB debug was off, and it worked. But it did not work on a previous, unstable TWRP version. So it is probably due to your recovery, not your phone. What TWRP are you using?

I’ve used TWRP 3.1.1 from this thread: https://forum.xda-developers.com/ga...pment/twrp-twrp-recovery-j5-pro-2017-t3668266
The thing is that my device don’t get listed in ADB no matter whichever mode it’s in – download, recovery nor "normal". And I’ve checked on several PCs.
Windows recognises my phone as unknown MTP device, so I assume that my phone has MTP mode enabled and I’m stuck with it. That shouldn’t be the case since I tried to plug it in while it’s in recovery mode, but maybe you’ll find this information useful.

Haxomen said:
What TWRP are you using?
Click to expand...
Click to collapse
I assume that since I didn’t quote you in my previous post you didn’t get any notification – fixed it now. I’ve answered your question in the post above. Any thoughts?