Hi Everyone,
I am having issues with my previously rooted Nexus 7. My device was rooted when it first came with Nexus 7 toolkit v2.0 and was rooted successfully. After an update to android 4.2 via the OTA updates, the root status was taken off from the device so I've used to tookit again to restore the root. But it seems like it was not properly rooted when I tested it using the root checker basic.
I've downloaded the Nexus 7 toolkit v4.0 yesterday to re-root the device but all options does not seems to work at all.
1. Root Device [Fastboot Mode] showing waiting for device
2. Root Device + Install Busybox [Fastboot Mode] showing waiting for device
3. Boot CWM Recovery and Install Root [Superuser or SuperSU] [ADB Mode] showing waiting for debugging mode for USB connection. already in debugging mode but it would not work.
5. Unroot, Uninstall Busybox + CWM Manager via CWM Recovery [ADB Mode] showing waiting for debugging mode for USB connection. already in debugging mode but it would not work.
Can anyone help me? Thanks.
Sounds like a driver issue to me, try uninstalling and then reinstalling them
Sent from my Nexus 7 using Tapatalk 2
leschua75 said:
Hi Everyone,
I am having issues with my previously rooted Nexus 7. My device was rooted when it first came with Nexus 7 toolkit v2.0 and was rooted successfully. After an update to android 4.2 via the OTA updates, the root status was taken off from the device so I've used to tookit again to restore the root. But it seems like it was not properly rooted when I tested it using the root checker basic.
I've downloaded the Nexus 7 toolkit v4.0 yesterday to re-root the device but all options does not seems to work at all.
1. Root Device [Fastboot Mode] showing waiting for device
2. Root Device + Install Busybox [Fastboot Mode] showing waiting for device
3. Boot CWM Recovery and Install Root [Superuser or SuperSU] [ADB Mode] showing waiting for debugging mode for USB connection. already in debugging mode but it would not work.
5. Unroot, Uninstall Busybox + CWM Manager via CWM Recovery [ADB Mode] showing waiting for debugging mode for USB connection. already in debugging mode but it would not work.
Can anyone help me? Thanks.
Click to expand...
Click to collapse
If that doesnt work ,try Wug's toolkit.
bfranklin1986 said:
Sounds like a driver issue to me, try uninstalling and then reinstalling them
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Hi, thanks for the response. I've reinstalled the drivers many time and yet it doesn't help.
Leonhan said:
If that doesnt work ,try Wug's toolkit.
Click to expand...
Click to collapse
I tried wug's toolkit and a prompt came out telling me that adb device not found.
leschua75 said:
I tried wug's toolkit and a prompt came out telling me that adb device not found.
Click to expand...
Click to collapse
It seems to me that adb drivers were not installed properly. Try searching here in the forum "universal naked driver". Uninstall every nexus 7 driver in your pc first before installing that usb pack.
I'm trying to remember what I did but I had the same problem initially. Try toggling the USB setting after you plug it into your computer on the tablet. There are two choices.
Sent from my Nexus 7 using xda app-developers app
You also might want to try a different cable / USB port
I had the same problem recently. The drivers did not install correctly. Use wugs toolkit and follow the "install driver" directions. When you get to the part that says option 3 is recommended don't go that route. Use option 1 which I believe is pdnet or pdanet (something like that) and it should work fine after that. That's how it worked for me.
Sent from my Nexus 7 using xda premium
Luda305 said:
I had the same problem recently. The drivers did not install correctly. Use wugs toolkit and follow the "install driver" directions. When you get to the part that says option 3 is recommended don't go that route. Use option 1 which I believe is pdnet or pdanet (something like that) and it should work fine after that. That's how it worked for me.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
+1 PDANet method was my only success too !
If you (meaning the OP, leschua75) or anyone else needs the latest Google USB drivers for Android, they're in the Android SDK obviously or I can upload them someplace like my Dropbox account. I tried the PDANet drivers, RAW drivers, older drivers, and a half dozen of other ones and nothing would allow my N7 to be seen through ADB until I gave up mucking around and just grabbed the proper actual SDK from Google themselves and then saved the drivers, both x86 and x64.
As soon as I installed those drivers manually it was clear sailing with ADB usage and I haven't had one issue since. None of the other drivers ever worked for me personally, while some people have had success.
My belief is that the best ones are from Google directly so that's what I use now. The latest drivers (as of Feb 5, 2013) are here:
http://dl.dropbox.com/u/19019338/Latest_Google_Android_USB_Driver_2-5-2013.zip
And just for the paranoid, here's a VirusTotal scan of the archive and contents along with checksums too:
https://www.virustotal.com/file/42d...34e549649b0a3bce3915374b/analysis/1360594983/
Hope this helps...
Don't forget to restart your computer after installing the ADB drivers
Did you remember to turn on USB debugging?
In the settings menu, select 'about' then scroll down to the bottom and tap build number 8 times to turn on developers options, then go back to the settings page, select developers options and turn on USB debugging hope this helps.
Sent from my Nexus 7 using Tapatalk HD
Related
LG Thrill Just will not root - superoneclick freezes at "waiting for device"
I am trying to root my LG Thrill 4G with SuperOneClick (I tried 3 different versions). After installing the drivers on my laptop (running Windows 7 32-bit), I put the phone in USB debug mode and pressed Root in SuperOneClick, but it freezes at "waiting for device".
Any ideas how to get past this? I have done a search here and google, as well as several other forums but doesn't seem to be that I can get an answer to this.
SuperOneClick v2.3.1.0 says :
"The following device does not have drivers installed:
Data Interface
USB\VID_413C&PID_8134&MI_01
Would you like me to forcefully install an Android ADB Interface
Driver for this device?"
First of all, what is the correct device driver to use for the LG Thrill 4G?
I have installed LG _USB _Drivers_All_4.9.7 (that one failed to install), and LGAndroidDriver_Ver_1.0_All
Use the links in general or development of xda thrill.
when u get the rite drivers and the rite super one click.
If when u have the proper drivers installed,make sure u
went in to your settings And click the USB debugging box.
Lastly open super one click and run
eastbayarb said:
I am trying to root my LG Thrill 4G with SuperOneClick (I tried 3 different versions). After installing the drivers on my laptop (running Windows 7 32-bit), I put the phone in USB debug mode and pressed Root in SuperOneClick, but it freezes at "waiting for device".
Any ideas how to get past this? I have done a search here and google, as well as several other forums but doesn't seem to be that I can get an answer to this.
SuperOneClick v2.3.1.0 says :
"The following device does not have drivers installed:
Data Interface
USB\VID_413C&PID_8134&MI_01
Would you like me to forcefully install an Android ADB Interface
Driver for this device?"
First of all, what is the correct device driver to use for the LG Thrill 4G?
I have installed LG _USB _Drivers_All_4.9.7 (that one failed to install), and LGAndroidDriver_Ver_1.0_All
Click to expand...
Click to collapse
First off, what's your firmware version?
Did you try clicking the checkbox for using alt adb? Also make sure on the phone that you have it in developer USB debugging mode.
Sent from my LG-P925 using XDA App
hi all
i have a problem with rooting.!
my phone bricked and i flashed 2.1.1.c.0.0.ftf
but now when i wanna root it with superoneclick or x8toolbox it stops at "waiting for device"
help me please.!
1) run superoneclick.exe as administrator
2) it is normal for it not to respond at first..try more times
3) if that doesn't work check if usb debugging is on?
enable usb debugging in settings
dont forget to install the drivers
usb debugging is enable
exebreez said:
dont forget to install the drivers
Click to expand...
Click to collapse
i already have them.!
Enable USB-Debugging and connect your phone to the computer (do NOT enable USB-Storage mode - connect in Charging mode!)
Start Flashtool and root with Flashtool ... for me this always worked more reliably than with SuperOneClick.
Same mine before,but what i do is take out the memory & just like a miracle i dont know why its work,i manage to root my phone without a sdcard,maybe because my sdcard has poor quality...
try remove battery b4 u plug it to comp..
its always works 4 me..
P.S. hold the back button until flashtool recognize it..
may be 15 secs is enough..
more than that,,repeat the procedures..
first time rooting my X8,,i got the same problem..
wih u luck
try to change User Account Control in windows ( disable it ) , restart windows and try again
root using flash tools is more easy
OK, try one of these things:
1.Run superoneclick/x8toolbox as admin on your PC
2.Use flashtool to root your device
3.if i donsnt respond, just wait for a few minutes, OR keep trying to run the programm
You will get their eventually
finally solved.!
the problem was with the drivers.!
i don't know why but i could do everything with drivers except rooting.!
thanks for replies.!
this is what finally worked for me, very easy.
Great Boy said:
hi all
i have a problem with rooting.!
my phone bricked and i flashed 2.1.1.c.0.0.ftf
but now when i wanna root it with superoneclick or x8toolbox it stops at "waiting for device"
help me please.!
Click to expand...
Click to collapse
http://www.youtube.com/watch?v=-5TmP15hfQU
tried superoneclick for hours on my droid 2 ver 2.3.4
this method took 10 minutes. see link above.
Published on Apr 26, 2013
How to root your Droid X, Droid 2 the super easy way with a app called Framaroot
Link to XDA forum for root App
http://forum.xda-developers.com/showt...
Link to Root App
https://docs.google.com/file/d/0B_niz...
How to install Android Device drivers http://youtu.be/j_KPGUMzrjU
Universal UnRoot App for all Devices http://youtu.be/ySNStU8OTuk
Link to my web site, videos and files can be found here. http://www.RootJunky.com
Hi guys. I just installed PACman ROM latest version on my previously stock Atrix HD. Now, I can't read my Atrix HD on my computer. I already installed motorola device manager and still can't read. Is there a driver that I need to install? Thanks
tanos0415 said:
Hi guys. I just installed PACman ROM latest version on my previously stock Atrix HD. Now, I can't read my Atrix HD on my computer. I already installed motorola device manager and still can't read. Is there a driver that I need to install? Thanks
Click to expand...
Click to collapse
Because developer mode isn't enable,
Setting --->About Phone--->hit build number 7 times.
Settings -->Developer options--->Android Debugging
rock on.
tanos0415 said:
Hi guys. I just installed PACman ROM latest version on my previously stock Atrix HD. Now, I can't read my Atrix HD on my computer. I already installed motorola device manager and still can't read. Is there a driver that I need to install? Thanks
Click to expand...
Click to collapse
Turn on USB debugging, while connecting your device to system, reboot it without disconnecting. Also if it prompt for RSA key access check always allow this computer and accept it....
Sent from my MB886 using xda app-developers app
No dice
Tried your suggestions, guys. But its still not working.
I tried the 7 clicks. It showed that I have developer access. Then I turned on USB debugging and restarted the phone. No notification about USB debugging, my computer still doesn't detect it.
tanos0415 said:
Tried your suggestions, guys. But its still not working.
I tried the 7 clicks. It showed that I have developer access. Then I turned on USB debugging and restarted the phone. No notification about USB debugging, my computer still doesn't detect it.
Click to expand...
Click to collapse
No adb/debgging is normal on the custom roms. Haven't had adb in at least 2 weeks.
skeevydude said:
No adb/debgging is normal on the custom roms. Haven't had adb in at least 2 weeks.
Click to expand...
Click to collapse
Too bad. Does that mean that I can't use MTP mode?
tanos0415 said:
Too bad. Does that mean that I can't use MTP mode?
Click to expand...
Click to collapse
Can you give details as to what computer/os you are running?
Does it charges when you plug the phone into the computer?
With or without developer mode enabled, your computer should still respond to the phone. If it doesn't then the problem is the computer.
hungrymr2 said:
Can you give details as to what computer/os you are running?
Does it charges when you plug the phone into the computer?
With or without developer mode enabled, your computer should still respond to the phone. If it doesn't then the problem is the computer.
Click to expand...
Click to collapse
Yeah its charging. Drivers tried installing but it says that it was not successfully installed. It also shows as unknown device.
I'm running Windows 7 64bit. It can detect fine back when it was stock. The problem only showed up after I installed PAC rom
The drivers can be corrupted for no good reason try deleting and re-installing.
tanos0415 said:
Too bad. Does that mean that I can't use MTP mode?
Click to expand...
Click to collapse
Can't use MTP or Camera mode (at least on my linux box I can't). All I know is adb doesn't work and that's the only reason I have to plug into usb...I unmount my sd and plug it into my PC to do file transfers (or adb push from recovery)...adb does work in recovery, just not the system.
tanos0415 said:
Yeah its charging. Drivers tried installing but it says that it was not successfully installed. It also shows as unknown device.
I'm running Windows 7 64bit. It can detect fine back when it was stock. The problem only showed up after I installed PAC rom
Click to expand...
Click to collapse
Same things happen on my linux box...problem showed up the same time for me as well....installed a 4.2.2 rom...
//this is a known issue....related to the kernel and usb drivers (started about three weeks ago) Use an earlier, first week of June or so, kernel if you need adb/usb...thought I don't recommend doing that.
frog1982 said:
The drivers can be corrupted for no good reason try deleting and re-installing.
Click to expand...
Click to collapse
+1 try to delete them in safemode to ensure that the old drivers are gone for good.
I did try PAC once and it connected to my win 7 64bit without any issues.
Sent from my MB886 using xda app-developers app
tanos0415 said:
Hi guys. I just installed PACman ROM latest version on my previously stock Atrix HD. Now, I can't read my Atrix HD on my computer. I already installed motorola device manager and still can't read. Is there a driver that I need to install? Thanks
Click to expand...
Click to collapse
I had this problem.
Step 1: Enter system Settings>Developer options.
Step 2: Tick "Android debugging", "USB debugging notify" (makes it easier to know if connection is successful), and change the "Root acess" setting to "Apps and ADB".
Step 3: Reboot Phone and connect to computer.
This is what I did and I haven't had a problem since. Hope this helps
Blackest Pain said:
I had this problem.
Step 1: Enter system Settings>Developer options.
Step 2: Tick "Android debugging", "USB debugging notify" (makes it easier to know if connection is successful), and change the "Root acess" setting to "Apps and ADB".
Step 3: Reboot Phone and connect to computer.
This is what I did and I haven't had a problem since. Hope this helps
Click to expand...
Click to collapse
already tried that. thanks anyway. :good:
Did you do all that And the restart the computer itself? I think I read that on another android forum (android central maybe?) That that helps sometimes...
Sent from my PACman Atrix HD using XDA Premium
see my [Video] Droid 4 root with SafeRoot and installing SafeStrap
Download Motorola Drivers see Motorola USB Drivers, RSD Lite, Firmware...
unzip Drivers and install
Reboot PC
Download Saferoot.zip see [ROOT] Saferoot: Root for VRUEMJ7, MK2, and Android 4.3
Unzip Saferoot.zip
Enable USB Debugging Menu>settings>developer options
see USB Debugging Mode - DROID 4 by MOTOROLA
Double click on the "install.bat"
Follow onscreen instructions
Installing Safestrap
Original SafeStrap Thread: http://forum.xda-developers.com/showthread.php?t=1688610
Safestrap v3.75
@stargo has released a updated safestrap (v3.75 - Jan 2015)
Cm12 requires safestrap v3.75 (or newer)
Safestrap-XXXXX-v3.75.apk (31-Jan-2015 )
if you installed the debugged version likely do not need to upgrade, but if you have 3.74 or lower use Safestrap-XXXXXX-v3.75.apk (or newer)
follow the readme.txt instructions on the download site
Download the version for your device
Droid 4 = maserati, Razr XT912 = spyder, Razr XT910 = umts_spyder, Bionic = targa
[Video] Droid 4 Installing Safestrap 3.75 & Lollipop Rom
or [Video] How to install Safestrap 3.75 and Android 5.0.2 Lollipop on the Motorola Droid Bionic, Droid 4 and Droid Razr http://www.youtube.com/watch?v=2yMYUXV8FmI
Modified Safestrap 3.75
if you have a XT912 or XT894, There is a Modified Safestrap 3.75 for unused partitions (/preinstall & /webtop) by Mentor.37
XT894: http://forum.xda-developers.com/droid-4/development/wip-safestrap-3-75-unused-partitions-t3023932
XT912: http://forum.xda-developers.com/droid-razr/development/recovery-safestrap-3-75-unused-t3032675
Note: Mentor.37 has removed the Safestrap splash screen, so you must select reboot to recovery from rom or Boot to safestrap from Stock Boot Mode Selection Menu
Installing Rom with SafeStrap
[How To][Video]Installing Rom with SafeStrap
see [INDEX] Motorola Droid 4 Development for List of Droid 4 Roms and more
sd_shadow said:
Root from PC
see my [Video] Droid 4 root with SafeRoot and installing SafeStrap
Download Motorola Drivers
unzip Drivers and install
Reboot PC
Download Saferoot.zip see [ROOT] Saferoot: Root for VRUEMJ7, MK2, and Android 4.3
Unzip Saferoot.zip
Enable USB Debugging Menu>settings>developer options
Double click on the "install.bat"
Follow onscreen instructions
Click to expand...
Click to collapse
Hey Brother.... I think you have helped me before.
Been some water under the bridge since then.
Now I need to Update my Father in laws phone to the latest update and get it rooted again.
What is the best way to do that?
I saw Mattlgroffs thread that showed his suite.... but that was made back in march of 2013. Is that the latest update?
also once on the latest update and rooted.... is there an extremely stable ROM?
I know that was alot.... and just Know I REALLY appreciate all help!!
Thanks!!
swc2001 said:
Hey Brother.... I think you have helped me before.
Been some water under the bridge since then.
Now I need to Update my Father in laws phone to the latest update and get it rooted again.
What is the best way to do that?
I saw Mattlgroffs thread that showed his suite.... but that was made back in march of 2013. Is that the latest update?
also once on the latest update and rooted.... is there an extremely stable ROM?
I know that was alot.... and just Know I REALLY appreciate all help!!
Thanks!!
Click to expand...
Click to collapse
Latest system version for Droid 4 is
Blur_Version.98.72.188.XT894.Verizon.en.US
see - http://sbf.droid-developers.org/phone.php?device=11
last 3 updates are Android 4.1.2
there are no real important changes, and would not worry if already on Android 4.1.2
but if you want to update that's ok just follow my
[Video][How To] Flash Jellybean Stock Firmware on Droid 4 with RSD Lite
root with saferoot
install safestrap https://www.youtube.com/watch?v=HuoZZuZJ1Xw
What is the most stable rom? Don't know
Probably one of the modified stock Jellybean roms
see http://forum.xda-developers.com/droid-4/general/index-motorola-droid-4-development-t2817578
You are the Man! Thank you so much for your help!
Btw LOVE the Avatar!
"the Shadow knows"
Sent from my SCH-I545 using Tapatalk
---------- Post added at 11:28 AM ---------- Previous post was at 11:17 AM ----------
Oh also what is the most current Safestrap that will work with the info you gave me?
Sent from my SCH-I545 using Tapatalk
swc2001 said:
Oh also what is the most current Safestrap that will work with the info you gave me?
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
[RECOVERY] Safestrap Recovery v3.7x [05/15/2014 V3.73 - TWRP 2.7]
I believe the newest 3.73 works fine with the modified stock Jellybean roms
People like you are rare!
Do you have a Donate Button?
Sent from my SCH-I545 using Tapatalk
swc2001 said:
People like you are rare!
Do you have a Donate Button?
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Thanks, Yes I do.
Thanks..... I know its not much, but go have a Hamburger on me!
Sent from my SCH-I545 using Tapatalk
Ok I don't know what to do..... it wont safestrap. I tried masarati versions 3.73, and 3.72. I rooted with safe root after I rsdlited to the latest firmware. Then I installed the latest Super SU and the lstest busybox.....
Now is when I installed safestrap maserati version...... I then installed safestrap via the app. It said installation complete and status Installed. So I turned the phone off and then back on.
Sure enough there was the little safestrap robot staring at me.
So I tried to boot into SS..... but it just goes to a black screen and hangs there. It will not let me in..... I have been fighting this for a couple of days...... please help!
Sent from my SCH-I545 using Tapatalk
Could try
Power off, Hold M key, Power on, release buttons at
Boot Mode Selection Menu> Scroll down with volume down button, to BP Tools, Select with Volume UP button, should boot directly to SafeStrap
Sent from my Amazon OtterX using Tapatalk
Ok what is the M key? Excuse the ignorance
so let me say what I think you said. 1.Power off
hold m key then power on while still holding the m key
release them when the boot mode selection menu comes up.
use volume down to bp tools
Select bp tools by pressing volume up.....
should boot direct to ss.
Is that right?
again....don't know what the m key is though.
thanks in advance bud!
Sent from my SCH-I545 using Tapatalk
swc2001 said:
Ok what is the M key? Excuse the ignorance
so let me say what I think you said. 1.Power off
hold m key then power on while still holding the m key
release them when the boot mode selection menu comes up.
use volume down to bp tools
Select bp tools by pressing volume up.....
should boot direct to ss.
Is that right?
again....don't know what the m key is though.
thanks in advance bud!
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
The letter m on the keyboard.
Sent from my XT894 using Tapatalk
other things to troubleshoot
did you get a supersuser allow/deny pop up
if not install Root Checker to verify superuser is working correct
Did you verify md5 for SafeStrap app see https://sites.google.com/site/sdshadowscollection/home/hash-checksums
Hey, thanks a bunch for the video! I'm having that problem with the moto drivers not installing correctly and I've looked all over the place, no luck so far on figuring it out. I even found the instructions on their site for developers to use to install the ADB driver but they're less than helpful. Do you have any links / resources I can check out? Any Linux alternatives to the Windows SafeRoot method?
I installed the drivers on Win7 home premium after plugging in the phone a few days prior. I didn't find the video where you said not to do that until later. Now it shows up under "portable devices" in device manager. I've tried flipping debug mode on/off, changing the usb pc connection settings from mtp to camera and back to the top option, uninstalling, reinstalling, no luck.
One thing that might be relevant is the instructions from the moto site mentioned that I should be able to just start using adb in the command shell after installing the driver, and I can't do that. It says to type "adb devices" to get a list of connected devices but I get "adb is not a valid command". I don't have that link available but I can try to post it tonight.
Thanks in advance!
sandman2211 said:
Hey, thanks a bunch for the video! I'm having that problem with the moto drivers not installing correctly and I've looked all over the place, no luck so far on figuring it out. I even found the instructions on their site for developers to use to install the ADB driver but they're less than helpful. Do you have any links / resources I can check out? Any Linux alternatives to the Windows SafeRoot method?
I installed the drivers on Win7 home premium after plugging in the phone a few days prior. I didn't find the video where you said not to do that until later. Now it shows up under "portable devices" in device manager. I've tried flipping debug mode on/off, changing the usb pc connection settings from mtp to camera and back to the top option, uninstalling, reinstalling, no luck.
One thing that might be relevant is the instructions from the moto site mentioned that I should be able to just start using adb in the command shell after installing the driver, and I can't do that. It says to type "adb devices" to get a list of connected devices but I get "adb is not a valid command". I don't have that link available but I can try to post it tonight.
Thanks in advance!
Click to expand...
Click to collapse
connect Droid 4, in device manager uninstall the droid 4, delete drivers if it is an option, reinstall drivers, reboot pc
If you get drivers already installed message, try my drivers folder
or
Saferoot also works on Linux see Rooting on Linux and MacOS part of Saferoot thread
sd_shadow said:
connect Droid 4, in device manager uninstall the droid 4, delete drivers if it is an option, reinstall drivers, reboot pc
If you get drivers already installed message, try my drivers folder
or
Saferoot also works on Linux see Rooting on Linux and MacOS part of Saferoot thread
Click to expand...
Click to collapse
Awesome, thanks! Hopefully I'll have some time to try that out in the next few days.
sd_shadow said:
Root from PC
see my [Video] Droid 4 root with SafeRoot and installing SafeStrap
Download Motorola Drivers
unzip Drivers and install
Reboot PC
Download Saferoot.zip see [ROOT] Saferoot: Root for VRUEMJ7, MK2, and Android 4.3
Unzip Saferoot.zip
Enable USB Debugging Menu>settings>developer options
Double click on the "install.bat"
Follow onscreen instructions
SafeStrap Thread: http://forum.xda-developers.com/showthread.php?t=1688610
Click to expand...
Click to collapse
I followed your guide to root and install CM11 on my Droid 4 and it worked a treat. Many thanks!
rattymon said:
I followed your guide to root and install CM11 on my Droid 4 and it worked a treat. Many thanks!
Click to expand...
Click to collapse
Eee ?? CM11 is rooted OOTB (it is rooted when you install it)
Fervi
Added links for Safestrap v3.75
So i downloaded the sdk.... plugged in the phone windows installed the adb composite driver I open command prompt in the platform tools folder run adb devices yes it is there reboot the phone into recovery.... many times.... do adb devices... nothing shows up apply from adb no device.... I'm on windows 7 64 I'm pretty sure its a driver issue but I can't get it to recognize the phone in recovery.... everything is stock on the phone bootloader still locked ( wouldn't be able to do that either since yeah no adb action.... using the cable that came with the phone tried multiple ports..... maybe someone can explain how to install the driver so it works? right now in device manager it shows up as Android device then below that adb composite driver..... this part I understand sort of... was expecting to see nexus 6 but how would I know...... if anyone has the actual driver that works I would appreciate it
Installed motorola device manager for windows.. no difference..... edited the inf file from sdk .... no difference..... I'd try another computer but probably end up installing the same driver so no point there....
edit edit also removed every hint of the old samsung drivers since I came from s4 to nexus......
Gage_Hero said:
So i downloaded the sdk.... plugged in the phone windows installed the adb composite driver I open command prompt in the platform tools folder run adb devices yes it is there reboot the phone into recovery.... many times.... do adb devices... nothing shows up apply from adb no device.... I'm on windows 7 64 I'm pretty sure its a driver issue but I can't get it to recognize the phone in recovery.... everything is stock on the phone bootloader still locked ( wouldn't be able to do that either since yeah no adb action.... using the cable that came with the phone tried multiple ports..... maybe someone can explain how to install the driver so it works? right now in device manager it shows up as Android device then below that adb composite driver..... this part I understand sort of... was expecting to see nexus 6 but how would I know...... if anyone has the actual driver that works I would appreciate it
Installed motorola device manager for windows.. no difference..... edited the inf file from sdk .... no difference..... I'd try another computer but probably end up installing the same driver so no point there....
edit edit also removed every hint of the old samsung drivers since I came from s4 to nexus......
Click to expand...
Click to collapse
This is what I did.
When you get to the phone into recovery mode unplug the USB plug and then plug it back in again. Windows should search for the driver. When windows finishes open device manager. Look for the nexus 6 with the yellow icon. Follow the steps attached in the picture. Credit for the driver steps goes to wugfresh, steps obtained from his toolkit.
Sent from my Nexus 6 using XDA Premium HD app
Intub8 said:
This is what I did.
When you get to the phone into recovery mode unplug the USB plug and then plug it back in again. Windows should search for the driver. When windows finishes open device manager. Look for the nexus 6 with the yellow icon. Follow the steps attached in the picture. Credit for the driver steps goes to wugfresh, steps obtained from his toolkit.
Sent from my Nexus 6 using XDA Premium HD app
Click to expand...
Click to collapse
I will try wugfish to install the drivers and then see if I can use ADB after that.... I definitely did not have the device show up as nexus 6 in device manager other than the mtp part... pretty hard for that not to show up..... I'll give it a shot on Sunday unless the ota drops to the phone first.
A simple unplug and replug in fixes the issue...when you get to the adb point on the phone and you make sure the driver is installed on the computer correctly, simply unplug from the computer, replug in and continue
Sent from my Nexus 6 using XDA Free mobile app
Had the same problem on a Win7 machine that I have used for several phones. Would see the device in ADB when full booted, see it in fastboot, but when in ADB sideload, could not see it. Turns out it was trying to use the Samsung ADB vs. Google/N6 driver for ADB. Had to do a lot of hoop jumping, deleting/changing drivers, but worked great after.
tvtodd said:
Had the same problem on a Win7 machine that I have used for several phones. Would see the device in ADB when full booted, see it in fastboot, but when in ADB sideload, could not see it. Turns out it was trying to use the Samsung ADB vs. Google/N6 driver for ADB. Had to do a lot of hoop jumping, deleting/changing drivers, but worked great after.
Click to expand...
Click to collapse
Can you explain exactly what you did? This is exactly what my N6 is doing. When the phone is on, under "Device Manager" it says "Samsung Android Phone - Android Composite ADB Interface". When in Bootloader it says it is a a "Samsung Android Phone - Android Bootloader Interface" and I keep deleting the driver and trying to reinstall the default drivers from the SDK Manager but it just keeps loading as the damn Samsung.
z28 justin said:
Can you explain exactly what you did? This is exactly what my N6 is doing. When the phone is on, under "Device Manager" it says "Samsung Android Phone - Android Composite ADB Interface". When in Bootloader it says it is a a "Samsung Android Phone - Android Bootloader Interface" and I keep deleting the driver and trying to reinstall the default drivers from the SDK Manager but it just keeps loading as the damn Samsung.
Click to expand...
Click to collapse
I successfully installed the correct drivers.... Download wugfish for n6, at the top when its installed, there is a button in the middle to setup drivers, follow the instructions exactly and it will work. Of course before someone jumps on me, I do plan to sideload through command prompt....
Gage_Hero said:
I successfully installed the correct drivers.... Download wugfish for n6, at the top when its installed, there is a button in the middle to setup drivers, follow the instructions exactly and it will work. Of course before someone jumps on me, I do plan to sideload through command prompt....
Click to expand...
Click to collapse
I followed those instructions as well and it still registered as a Samsung Device. However, I did finally get it to work by going through my "Uninstall or change a program list" and removing a "Samsung Driver Installation" program I had installed for my wife's S4. Then I ran back through Wugfish's driver directions and sure enough, it finally registered as a standard Android device and not a damn Samsung.
I've tried on my Nexus 6, every time it goes to recovery mode it doesn't show up in device manager.
I've already unistalled all drivers, used the nexus root tool to reinstall the drivers, it doesn't matter. It works fine the first part when you need to use ADB to restart the device in bootloader mode, then you select recovery and nothing happens the device never shows up, so I can't install/uninstall any drivers because it simply doesn't display anywhere, wtf!
Mephisto_POA said:
I've tried on my Nexus 6, every time it goes to recovery mode it doesn't show up in device manager.
I've already unistalled all drivers, used the nexus root tool to reinstall the drivers, it doesn't matter. It works fine the first part when you need to use ADB to restart the device in bootloader mode, then you select recovery and nothing happens the device never shows up, so I can't install/uninstall any drivers because it simply doesn't display anywhere, wtf!
Click to expand...
Click to collapse
Did you try to disconnect and reconnect the USB while the phone was in recovery?
Sent from my Nexus 6 using XDA Premium HD app
I don't know if this will solve your issues. When I was side loading the 5.1 update I couldn't get tmy win 7 machine to see the device after rebooting from adb to sideload.
I ended up finding a thread somewhere that suggested a newer version of adb. Once I downloaded the most recent version it installed fine.
I also rebooted into fastboot through adb, went to device manager and found my nexus, manually updated the driver. After all that everything worked fine.
Don't know if that helps or not....
I can't get my computer to show my N6 as a phone. All it shows is Unknown Device. I've loaded the Google Drivers yet it doesn't list them when trying to load them manually.
Intub8 said:
Did you try to disconnect and reconnect the USB while the phone was in recovery?
Sent from my Nexus 6 using XDA Premium HD app
Click to expand...
Click to collapse
I found the problem
each mode has a unique hardware ID
when phone is in normal mode with USB debug, when it is at bootloader and then afterwards when it is in recovery mode
the last mode, hardware ID VID_18D1&PID_D001 didn't get any dirvers installed, evne downloading official drivers from google and other parties.
I had to manually edit the android_winusb.inf file and add the hardware ID %CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D001 under ;Google Nexus (generic)
---------- Post added at 05:57 PM ---------- Previous post was at 05:56 PM ----------
lukesdiesel said:
I can't get my computer to show my N6 as a phone. All it shows is Unknown Device. I've loaded the Google Drivers yet it doesn't list them when trying to load them manually.
Click to expand...
Click to collapse
https://www.reddit.com/r/nexus6/comments/2yyfri/nexus_6_not_getting_detected_during/
check this
got it to work
I got it to work by unplugging and plugging back in once I had hit the adb sideload option in recovery. When I was just in recovery it had no effect.
rkshack
Intub8 said:
This is what I did.
When you get to the phone into recovery mode unplug the USB plug and then plug it back in again. Windows should search for the driver. When windows finishes open device manager. Look for the nexus 6 with the yellow icon. Follow the steps attached in the picture. Credit for the driver steps goes to wugfresh, steps obtained from his toolkit.
Sent from my Nexus 6 using XDA Premium HD app
Click to expand...
Click to collapse
thanks. this worked
Mephisto_POA said:
I had to manually edit the android_winusb.inf file and add the hardware ID %CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D001 under ;Google Nexus (generic)
Click to expand...
Click to collapse
My device needed %CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D002.
This happened to me too, I just ended up using a different computer: https://plus.google.com/+LoganJonesJ/posts/hrDRAnyrotf
Intub8 said:
This is what I did.
When you get to the phone into recovery mode unplug the USB plug and then plug it back in again. Windows should search for the driver. When windows finishes open device manager. Look for the nexus 6 with the yellow icon. Follow the steps attached in the picture. Credit for the driver steps goes to wugfresh, steps obtained from his toolkit.
Click to expand...
Click to collapse
Worked for me as well, thanks!
Intub8 said:
This is what I did.
When you get to the phone into recovery mode unplug the USB plug and then plug it back in again. Windows should search for the driver. When windows finishes open device manager. Look for the nexus 6 with the yellow icon. Follow the steps attached in the picture. Credit for the driver steps goes to wugfresh, steps obtained from his toolkit.
Sent from my Nexus 6 using XDA Premium HD app
Click to expand...
Click to collapse
Worked like a charm. Thanks!
A2CKilla said:
A simple unplug and replug in fixes the issue...when you get to the adb point on the phone and you make sure the driver is installed on the computer correctly, simply unplug from the computer, replug in and continue
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks so much for this! I had tried EVERYTHING trying to get my 6P to connect with no success. This simple fix was exactly what I needed.