So I'm following this guide and in it he says that when your Nexus 7 has USB debugging mode on and it's plugged in into a Windows 7 computer, in device manager the Nexus 7 should be showing up under "Other Devices". However this is not the case for me. It is still showing up under " Portable Devices". Yes, I have USB debugging mode turned on. I have rebooted my computer and Nexus 7. I have tried uninstalling the drivers multiple times but this still ends up being the end result. What am I doing wrong?
lostradiant said:
So I'm following this guide and in it he says that when your Nexus 7 has USB debugging mode on and it's plugged in into a Windows 7 computer, in device manager the Nexus 7 should be showing up under "Other Devices". However this is not the case for me. It is still showing up under " Portable Devices". Yes, I have USB debugging mode turned on. I have rebooted my computer and Nexus 7. I have tried uninstalling the drivers multiple times but this still ends up being the end result. What am I doing wrong?
Click to expand...
Click to collapse
Sounds like a case of explosive diarrhea
Sent from my Galaxy Nexus using Tapatalk 2
I will try to be helpful here. I also used Wugs toolkit. I did not watch the vid you posted.
There are guides in the toolkit that I followed to the letter. Start from 1 and do not skip steps that apply to you. If you do things right it goes just like the guide says.
I did have one problem. When I got the positive messages that I did everything right, with drivers installed, I went to unlock bootloader and it said my drivers weren't installed, so it did not stick twice. I had to do it 3 times before I could move forward, unlock bootloader, root and install CWM. I also ended up with CWM installed, but was not rooted, so did the root and CWM install again and finally I was done.
Don't give up or get frustrated. Just work it step by step and don't skip any.
Good luck!
If your on the 64bit of Windows 7, try the PDANet drivers. Can't post a link as I'm <10 posts, but they're locatable on the first page of Google results for "pdanet nexus 7 drivers"
Worked for me, when the Google and other ones linked to in guides didn't..
I simply followed the info on the web page for Nexus Root Toolkit: http://www.wugfresh.com/dev/nexus-root-toolkit/
All the info is there and pretty simple and it took me all of 10 minutes to do the job.
Just check out the FAQ for tips on how to deal with problems.
i want to unlock my bootloader but when i connect my nexus 7 to pc and use the command abd devices nexus 7 does not show up i tried installing this http://forum.xda-developers.com/showthread.php?t=1766220 but the install failed. Plz help as i can not unlock my bootloader
stranger97 said:
i want to unlock my bootloader but when i connect my nexus 7 to pc and use the command abd devices nexus 7 does not show up i tried installing this http://forum.xda-developers.com/showthread.php?t=1766220 but the install failed. Plz help as i can not unlock my bootloader
Click to expand...
Click to collapse
You need to enable USB debugging ...
Go to settings
Then go to about tablet
Then tap on build number aprox5 of 6 times ... You will see a toast notification the will say "you are now a developer"
Now try to what you tried to do before
Sent from my Nexus 7 using xda premium
You also will be unlocking the bootloader with fastboot commands, not adb.
ok i fixed it the usb degugging was already enabled. Just downloaded the drivers from asus website and now it is showing up in adb
Mods close the thread
The past 3 hours or so I've been trying to unlock my nexus 4 bootloader
I've tried using 2 tool kits and also tried doing it manually..
After installing the android SDK and enterin "adb reboot bootloader" I always get Error Device not found.
I tried deleting the drivers but I dont get the option of "Delete the driver for this device" under Device Manager.
I've tested this TWICE on 2 seperate machien, 1 running windows 8 and 1 running windows 7..
USB debug is on.
Any help would be greatly appreciated (Running 4.2.2 Stock)
When you enabled USB debugging, did you get a prompt on your phone saying if you trust your computer?
Make sure you navigated to the ADB folder correctly.
Make sure your phone is turned on and not in fast boot.
Sent from my Nexus 4 using xda app-developers app
Eddy130306 said:
When you enabled USB debugging, did you get a prompt on your phone saying if you trust your computer?
Make sure you navigated to the ADB folder correctly.
Make sure your phone is turned on and not in fast boot.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I've solved the problem! I had to disable this signature windows 8 thing and then i was able to install the drivers.
Mod plz close this thread
Hi, I'm currently trying to revert my Nexus back to stock using the Nexus 4 Toolkit, and I don't know if I installed the drivers properly, in Windows Device Manager it says "Android Composite ADB Interface", and in the toolkit I'm not sure which one is the serial number, so I'm sending a print screen zippyshare.com/v/48728267/file.html
Am I doing everything ok?
Are you using wugfresh toolkit, or mskips toolkit? On mskips, if your drivers are set up it will display the serial # from your N4 at the top of the screen. I had an issue with wufresh toolkit recognizing my phone in adb, but worked fine in fastboot. Both toolkits will help you get back to stock.
dellortoPL said:
Hi, I'm currently trying to revert my Nexus back to stock using the Nexus 4 Toolkit, and I don't know if I installed the drivers properly, in Windows Device Manager it says "Android Composite ADB Interface", and in the toolkit I'm not sure which one is the serial number, so I'm sending a print screen zippyshare.com/v/48728267/file.html
Am I doing everything ok?
Click to expand...
Click to collapse
http://hippowise.com/revert-stock/
open adb and type fastboot devices while in fastboot. it should spit out something like a 12 or 16 digit number. if it spits that out, its connected and communicating how it should.
Check by using adb devices command,it'll show you your device as connected...
You can also confirm it by adb reboot bootloader command.It'll reboot the phone in bootloader..After that type fastboot devices while in fastboot.It will show your device there..Just check the adb devices & fastboot devices & you are good to go
Thanks for reply, I solved the problem, this thread can be closed.
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.