After upgrading to 4.2.2, some N7 will not be seen by any computer via USB and the only way to remedy it is to shut off USB debugging. On other devices, the computer will see the N7 even if USB debugging is enabled, but running "adb devices" will show the device as offline. This is a problem with the Nexus 10 as well.
UPDATE: This turns out to be security. See below.
Sent from my Nexus 7 using Tapatalk HD
oldblue910 said:
After upgrading to 4.2.2, some N7 will not be seen by any computer via USB and the only way to remedy it is to shut off USB debugging. On other devices, the computer will see the N7 even if USB debugging is enabled, but running "adb devices" will show the device as offline. This is a problem with the Nexus 10 as well.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Just waiting for more ppl to confirm this problem. I still stay at 4.2.1
Re: Warning: 4.2.2 Breaks ADB and USB Debugging
No problems here. USB debugging turned on, transferring my data back to my storage now. Tho I did update my SDK tools to the latest the other day. You will see a new pop up message to allow debugging pop up.
Sent from my Nexus 4 using xda premium
rayford85 said:
No problems here. USB debugging turned on, transferring my data back to my storage now. Tho I did update my SDK tools to the latest the other day. You will see a new pop up message to allow debugging pop up.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Ah this may be my issue...I may need to update my SDK tools. I haven't done that in months.
Confirmed breakage usb debugging and adb on my nexus 7
I just installed the 4.2.2 update on rooted stock and after installation root no longer worked. When I went to re-root I could not connect. It showed my tablet but it said it was showing as turned off or unavailable even though it was connected so then I restored back to 4.2.1 unrooted and tryed to connect and same problem. You can connect and send media files but anything else is not working at least for me.
So for my device I can confirm adb and usb debugging seems broken for now. I have the first production run 16 wifi model. I can also say wifi performance seems improved. The signal seems slightly boosted and also seems to stream content smoother farther away from the router. I do not have any bluetooth devices to confirm those fixes. Seems fast and stable for me so far.
I will probably revert back to a custom rom since I like the rooted apps but this release initially seems pretty solid.
Re: Warning: 4.2.2 Breaks ADB and USB Debugging
robbbzilla said:
I just installed the 4.2.2 update on rooted stock and after installation root no longer worked. When I went to re-root I could not connect. It showed my tablet but it said it was showing as turned off or unavailable even though it was connected so then I restored back to 4.2.1 unrooted and tryed to connect and same problem. You can connect and send media files but anything else is not working at least for me.
So for my device I can confirm adb and usb debugging seems broken for now. I have the first production run 16 wifi model. I can also say wifi performance seems improved. The signal seems slightly boosted and also seems to stream content smoother farther away from the router. I do not have any bluetooth devices to confirm those fixes. Seems fast and stable for me so far.
I will probably revert back to a custom rom since I like the rooted apps but this release initially seems pretty solid.
Click to expand...
Click to collapse
There's a new security feature in 4.2.2 to keep "adb thiefs" off your device. http://www.androidpolice.com/2013/0...s-from-stealing-your-data-in-some-situations/
After you enable USB debugging and plug the device in, you should get a prompt to allow the computer access to your device.
Sent from my Nexus 4 using xda premium
Wouldn't exactly say "it's broken" considering:
http://www.androidpolice.com/2013/0...s-from-stealing-your-data-in-some-situations/
It's a new addition to the ADB security and I'm sure as time passes we'll learn more about the inner workings.
Disclaimer: I installed 4.2.2 this morning just after it was released and I had no issues with ADB or USB debugging in the 2-3 hours I was testing it - I was pure stock across the board from 4.2.1 to 4.2.2 and had no problems.
Bleh, post above me covered it just as I did, only a few seconds faster.
Definitely not a bug
... it's a security feature, as mentioned above. I was pulling my hair out over it at first, until I rebooted my computer and restarted adb, and got the familiar dialog. You have to activate it for each machine you plug it into, it seems.
rayford85 said:
There's a new security feature in 4.2.2 to keep "adb thiefs" off your device. http://www.androidpolice.com/2013/0...s-from-stealing-your-data-in-some-situations/
After you enable USB debugging and plug the device in, you should get a prompt to allow the computer access to your device.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I know about the security feature. It did not prompt me. I even turned usb debugging on and off, turned pc and device on and off. I cleared cache and no difference. I did not get any prompt.
Maybe it is just me.
I will reflash and reboot and update it again and see if it works but for me it doesn't work. Not sure about broken just not working for installing root. I can transfer media files fine.
Just run the Android SDK Manager and update everything. Fixed.
Always remember, new version? Use ADB? Update SDK.
Also Wugs Toolkit will work again if you replace the adb files that comes with his kit.
r00t4rd3d said:
Just run the Android SDK Manager and update everything. Fixed.
Always remember, new version? Use ADB? Update SDK.
Also Wugs Toolkit will work again if you replace the adb files that comes with his kit.
Click to expand...
Click to collapse
I will give it a shot. Sometimes I forget to do basic things thinking I know about something I don't. So many more knowledgeable people here. Thanks for the help.
R
oldblue910 said:
After upgrading to 4.2.2, some N7 will not be seen by any computer via USB and the only way to remedy it is to shut off USB debugging. On other devices, the computer will see the N7 even if USB debugging is enabled, but running "adb devices" will show the device as offline. This is a problem with the Nexus 10 as well.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
It was working for me,I used adb to pull the system of the nexus 7.
Re: Warning: 4.2.2 Breaks ADB and USB Debugging
Updating adb fixed my N10 but not the N7. On the N7, with USB debugging enabled, adb devices shows no devices and will not show up as a media device. If I disable USB debugging, it will show up as a media device, though. Also, adb sideload works fine in stock recovery. Any thoughts?
Sent from my Galaxy Nexus using Tapatalk 2
Re: Warning: 4.2.2 Breaks ADB and USB Debugging
Yes, be sure to update your SDK to API17. There is a glitch on the SDK manager though that I had where I had to refresh the list twice to even have API17 appear. Otherwise it ended at API16/4.1
Sent from my Nexus 7 using Tapatalk HD
Re: Warning: 4.2.2 Breaks ADB and USB Debugging
r00t4rd3d said:
Just run the Android SDK Manager and update everything. Fixed.
Always remember, new version? Use ADB? Update SDK.
Also Wugs Toolkit will work again if you replace the adb files that comes with his
Where can I find the adb file I need to 'replace in wugs kit?
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
tdizzle404 said:
Where can I find the adb file I need to 'replace in wugs kit?
Click to expand...
Click to collapse
The data folder of where ever you installed Wugs tool kit too. I replaced 4 files, adb.exe, fastboot.exe, AdbWinApi.dll, AdbWinUsbApi.dll. You get these 4 files from the Android SDK platform-tools folder after you update the SDK.
-
Perhaps the title of this thread should be changed from
"Warning: 4.2.2 Breaks ADB and USB Debugging"
to
"New Enhanced Security Feature with 4.2.2"
Just a thought..
r00t4rd3d said:
The data folder of where ever you installed Wugs tool kit too. I replaced 4 files, adb.exe, fastboot.exe, AdbWinApi.dll, AdbWinUsbApi.dll. You get these 4 files from the Android SDK platform-tools folder after you update the SDK.
-
Click to expand...
Click to collapse
Cheers, that was just the info I needed to reapply root after upgrading to 4.2.2. I couldn't work out why ADB could connect but not Wugs toolkit.
ingenious247 said:
Perhaps the title of this thread should be changed from
"Warning: 4.2.2 Breaks ADB and USB Debugging"
to
"New Enhanced Security Feature with 4.2.2"
Just a thought..
Click to expand...
Click to collapse
Exactly ADB Debug has always been a huge glaring security hole for Android devices, some third party apps have been developed or added functionality to disable ADB Debug when the screen is off, etc, to close this hole.
Thanks
r00t4rd3d said:
The data folder of where ever you installed Wugs tool kit too. I replaced 4 files, adb.exe, fastboot.exe, AdbWinApi.dll, AdbWinUsbApi.dll. You get these 4 files from the Android SDK platform-tools folder after you update the SDK.
-
Click to expand...
Click to collapse
you made it possible for me to be rooted again ... wish i could thank you more than once ... that was getting frustrating ... now after that whole ordeal im considering going back to aokp jb mr1 B3 over staying stock ... but maybe ill just wait ... depends on how long i can stand using the GNEX with a cracked f'n screen lol ... man can the SG4 hurry up??? idk what to do right now .. i need something to flashhhhhhh!!!
Related
So I just received the Jellybean 4.2 update today. I was a little excited. However, after the update the device is now sluggish, unresponsive, it refuses to connect to any wifi or bluetooth device, and all other manner of trouble.
I want to revert back to 4.1.2 and I am using the Nexus Root Toolkit. The app cannot unlock, root, or reflash the stock 4.1.2 rom though. I always get the error Fastboot device was not found. What does this mean and how do I fix it? I've booted into the Fastboot thing where it says Start at the top.
Someone please help, I have 3 Nexus 7's here all suffering from the same issues.
EDIT:
USB debugging is on.
The drivers are installed and configured via the guide in Nexus Root Toolkit.
You are getting that error because you need to enable USB debugging. In 4.2 it is hidden. Go to settings/about and spam hit the build number until it says Congrats you are now a developer. Go into develpper options, enable USB debugging. Voila, should now be able to reflash.
Sent from my Galaxy Nexus using Tapatalk 2
It only seems to work on the main account. Not that it matters much. It says your a developer but you cannot access the options
Sent from my Nexus 7 using XDA Premium HD app
bolagnaise said:
You are getting that error because you need to enable USB debugging. In 4.2 it is hidden. Go to settings/about and spam hit the build number until it says Congrats you are now a developer. Go into develpper options, enable USB debugging. Voila, should now be able to reflash.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I've had usb debugging on the entire time and still get that same error.
I formatted my system on Stock ROM. I found another stock ROM for sprint now i can't get the ROM i want on my phone because the PC won't read the phone (in CWM recovery). My question is...is there a way to get the ROM on the phone through ADB? Im not all that familiar with it. If so...whats the command?
adb push rom.zip /sdcard
nhizzat said:
adb push rom.zip /sdcard
Click to expand...
Click to collapse
says error device not found
Prestige_DOPE said:
says error device not found
Click to expand...
Click to collapse
You might need to go through a different set of instructions just to make sure the devices is recognized on ADB. Here are my instructions for backing up and restoring app data via ADB, and it includes pretty good instructions on setting up your phone with ADB (well, at least I'd like to think so).
DogzOfWar said:
You might need to go through a different set of instructions just to make sure the devices is recognized on ADB. Here are my instructions for backing up and restoring app data via ADB, and it includes pretty good instructions on setting up your phone with ADB (well, at least I'd like to think so).
Click to expand...
Click to collapse
Well. I have my phone right here and connected to the PC with ADB set up and all. The problem is my PC wont recognize my phone. I tried using fastboot and ADB (i guess they're the same) and it keeps saying the error i stated above your post. The plan is to get the ROM on flashed on my phone. I don't know any other way of doing that. I thought fastboot (adb) would be of assistance but i dont know much about it.
Prestige_DOPE said:
Well. I have my phone right here and connected to the PC with ADB set up and all. The problem is my PC wont recognize my phone. I tried using fastboot and ADB (i guess they're the same) and it keeps saying the error i stated above your post. The plan is to get the ROM on flashed on my phone. I don't know any other way of doing that. I thought fastboot (adb) would be of assistance but i dont know much about it.
Click to expand...
Click to collapse
What I noticed on my phone is that I had ADB working fine for my previous phone (HTC Rezound), but that same ADB install didn't work for the X. When I downloaded the Moto X Toolkit, which included its own version of the adb.exe, it worked fine.
So consider trying everything through the toolkit.
Also, just to double check your settings:
- Make sure you have enabled Developer Settings, and Enable Debugging via ADB
- I set my phone to Camera mode, which seems to work a bit better than Media
DogzOfWar said:
What I noticed on my phone is that I had ADB working fine for my previous phone (HTC Rezound), but that same ADB install didn't work for the X. When I downloaded the Moto X Toolkit, which included its own version of the adb.exe, it worked fine.
So consider trying everything through the toolkit.
Also, just to double check your settings:
- Make sure you have enabled Developer Settings, and Enable Debugging via ADB
- I set my phone to Camera mode, which seems to work a bit better than Media
Click to expand...
Click to collapse
Well my phone wont bootup so thats not going to work but im in the moto x tool kit and i selected to push the ROM onto the sdcard now the whole tool kit froze...is that because its doing something or....
Try a different USB port? Then type adb devices.
Have you downloaded the Motorola Device Manager software? It contains all the necessary drivers. How about the Android SDK?
Prestige_DOPE said:
Well my phone wont bootup so thats not going to work but im in the moto x tool kit and i selected to push the ROM onto the sdcard now the whole tool kit froze...is that because its doing something or....
Click to expand...
Click to collapse
I misunderstood you're original question, sorry. I didn't realize it won't boot at all. I have done what you are asking for my Nexus 7 (which I had messed up). Typically, when you're in the recovery and you plug it into a PC, it will install drivers (separate from the ones when Android OS is running).
Maybe consider trying to use RSD Lite to at least get a functional OS back on there? This page lists drivers to use along with RSD Lite. Maybe that would help get things recognized to the point where you can copy over a ROM?
nhizzat said:
Try a different USB port? Then type adb devices.
Have you downloaded the Motorola Device Manager software? It contains all the necessary drivers. How about the Android SDK?
Click to expand...
Click to collapse
Didnt work...the more things that arent working the more scared i become
DogzOfWar said:
What I noticed on my phone is that I had ADB working fine for my previous phone (HTC Rezound), but that same ADB install didn't work for the X. When I downloaded the Moto X Toolkit, which included its own version of the adb.exe, it worked fine.
So consider trying everything through the toolkit.
Also, just to double check your settings:
- Make sure you have enabled Developer Settings, and Enable Debugging via ADB
- I set my phone to Camera mode, which seems to work a bit better than Media
Click to expand...
Click to collapse
Installed RSDLite and literally screamed "What the hell is this". A little help here on how this is supposed to work?
Brand new nexus 6, build #LMY47E, running Android 5.1
OS Windows 7 Home Premium 64-bit SP1
My issue is when I plug the device into the computer, regardless of USB port, using the brand new cable provided by Motorola. If I leave USB Debugging off, the phone gets recognized and it says it is working properly. As soon as I turn on USB debugging, the computer attempts to download the drivers, but it always fails on adb interface. MTP gets installed, and Nexus 6 gets installed, but never adb.
What do I do?
a.demarco said:
Brand new nexus 6, build #LMY47E
OS Windows 7 Home Premium 64-bit SP1
My issue is when I plug the device into the computer, regardless of USB port, using the brand new cable provided by Motorola. If I leave USB Debugging off, the phone gets recognized and it says it is working properly. As soon as I turn on USB debugging, the computer attempts to download the drivers, but it always fails on adb interface. MTP gets installed, and Nexus 6 gets installed, but never adb.
What do I do?
Click to expand...
Click to collapse
Have you downloaded the Android SDK? If not, here it is:
https://developer.android.com/sdk/index.html
Once downloaded, you don't need all of the components. Just install platform-tools, and Google drivers. You may have to uninstall any drivers that aren't for your nexus 6. You may also have to point your PC to the Google drivers via device manager. :victory:
Evolution_Freak said:
Have you downloaded the Android SDK? If not, here it is:
https://developer.android.com/sdk/index.html
Once downloaded, you don't need all of the components. Just install platform-tools, and Google drivers. You may have to uninstall any drivers that aren't for your nexus 6. You may also have to point your PC to the Google drivers via device manager. :victory:
Click to expand...
Click to collapse
Yes, I downloaded Android SDK, and installed the 4 packages it said to. I will see if I can get it to work through device manager, thanks!
a.demarco said:
Yes, I downloaded Android SDK, and installed the 4 packages it said to. I will see if I can get it to work through device manager, thanks!
Click to expand...
Click to collapse
Yeah, I knew there were a couple other SDK components needed but I couldn't think of them off the top of my head and also get my kids ready for bed at the same time. Lol!! Glad you're on the right track! :good:
a.demarco said:
Yes, I downloaded Android SDK, and installed the 4 packages it said to. I will see if I can get it to work through device manager, thanks!
Click to expand...
Click to collapse
Try turning the device off and then boot into fastboot (Pwr + Vol down) then plug the phone into the computer. You can also install Wug's Toolkit at the link below:
http://forum.xda-developers.com/nexus-6/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2947452
slimc84 said:
Try turning the device off and then boot into fastboot (Pwr + Vol down) then plug the phone into the computer. You can also install Wug's Toolkit at the link below:
http://forum.xda-developers.com/nexus-6/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2947452
Click to expand...
Click to collapse
I will try turning it off and booting into fastboot, thanks for that! I am trying to avoid using toolkits, I enjoy the learning process.
a.demarco said:
I will try turning it off and booting into fastboot, thanks for that! I am trying to avoid using toolkits, I enjoy the learning process.
Click to expand...
Click to collapse
I was recommending the toolkit just to install the drivers. I too enjoy the learning process and familiarizing myself with adb. Just in case I need it one day.
slimc84 said:
I was recommending the toolkit just to install the drivers. I too enjoy the learning process and familiarizing myself with adb. Just in case I need it one day.
Click to expand...
Click to collapse
Ah, gotcha... Had no idea the drivers were in the toolkits!
a.demarco said:
Ah, gotcha... Had no idea the drivers were in the toolkits!
Click to expand...
Click to collapse
Are you still having driver issues or did you get it sorted out? Just curious.
Evolution_Freak said:
Are you still having driver issues or did you get it sorted out? Just curious.
Click to expand...
Click to collapse
Haven't tried it again since last night... Doing some high pressure ductile iron underground water piping all day today, will try later tonight.
a.demarco said:
Haven't tried it again since last night... Doing some high pressure ductile iron underground water piping all day today, will try later tonight.
Click to expand...
Click to collapse
Yes, priorities. If you have any questions later, don't hesitate to ask.
Download the nexus toolkit and follow the instructions given in it to install the drivers, you don't even need the android sdk,
a.demarco said:
OS Windows 7 Home Premium 64-bit SP1
...
What do I do?
Click to expand...
Click to collapse
Delete that crap and install a real operating system.
doitright said:
Delete that crap and install a real operating system.
Click to expand...
Click to collapse
And what in your opinion is a real operating system?
I am asking for some help on this. I have always previously used toolkits to root and install recovery but I have a new N6 and I would like to learn to use ADB and fastboot. I have read several help guides and it all seems pretty straight forward except when i query the N6 with "adb devices", it does not return anything. However, if I enter the boot loader and query with "fastboot devices", it recognizes my N6. I have tried several different cables and ports, switching from mtp to ptp, resetting RSA keys, all with no success. I am using the latest adb, version 1.0.32 and my phone is stock 5.1.1. I am not a MAC power user by any means, so if someone can help, please use the simplest terms possible. Many Thanks
Update!....I had used EasyTether a few years ago and it was still in my extensions folder. I had unloaded it but not removed it with no success. Today, I removed it completely and now ADB recognizes my N6!! Thanks to all who commented.
jacksradio said:
I am asking for some help on this. I have always previously used toolkits to root and install recovery but I have a new N6 and I would like to learn to use ADB and fastboot. I have read several help guides and it all seems pretty straight forward except when i query the N6 with "adb devices", it does not return anything. However, if I enter the boot loader and query with "fastboot devices", it recognizes my N6. I have tried several different cables and ports, switching from mtp to ptp, resetting RSA keys, all with no success. I am using the latest adb, version 1.0.32 and my phone is stock 5.1.1. I am not a MAC power user by any means, so if someone can help, please use the simplest terms possible. Many Thanks
Click to expand...
Click to collapse
Did you enable USB debugging in Developer options for Android ADB?
danarama said:
Did you enable USB debugging in Developer options for Android ADB?
Click to expand...
Click to collapse
Yes, I forgot to say that in OP.
jacksradio said:
Yes, I forgot to say that in OP.
Click to expand...
Click to collapse
Is the android screen lock unlocked when you type the command?
jacksradio said:
Yes, I forgot to say that in OP.
Click to expand...
Click to collapse
Follow this guide, works like a champ. It's just like windows, CD to the location that contains your adb and fastboot (tools) and open terminal there.
ADB devices
danarama said:
Is the android screen lock unlocked when you type the command?
Click to expand...
Click to collapse
yes
jawmail said:
Follow this guide, works like a champ. It's just like windows, CD to the location that contains your adb and fastboot (tools) and open terminal there.
ADB devices
Click to expand...
Click to collapse
what guide?
Additional information......I keep seeing a reference to device drivers but I always thought Mac's did not require a driver to use ADB. Am I correct? Also, Android File Transfer works perfectly when I connect my N6 so the computer itself seems to be recognizing it. It also shows up as a Nexus 6 under "USB" in the system report.
This is the guide I used to set up ADB https://www.google.com/url?q=http://forum.xda-developers.com/showthread.php%3Ft%3D1917237&sa=U&ved=0CA4QFjAEahUKEwjvraDV2K7IAhWEoogKHbJPAxc&client=internal-uds-cse&usg=AFQjCNFwMzlRqY6AK7bv2ue6HmnF74sPjw
jacksradio said:
Additional information......I keep seeing a reference to device drivers but I always thought Mac's did not require a driver to use ADB. Am I correct? Also, Android File Transfer works perfectly when I connect my N6 so the computer itself seems to be recognizing it. It also shows up as a Nexus 6 under "USB" in the system report.
This is the guide I used to set up ADB https://www.google.com/url?q=http://forum.xda-developers.com/showthread.php%3Ft%3D1917237&sa=U&ved=0CA4QFjAEahUKEwjvraDV2K7IAhWEoogKHbJPAxc&client=internal-uds-cse&usg=AFQjCNFwMzlRqY6AK7bv2ue6HmnF74sPjw
Click to expand...
Click to collapse
Drivers I'm not sure. For linux, sometimes we have to do extra work (UDEV rules) but I can't say for Mac. What are these references to drivers and where are you seeing them?
danarama said:
Drivers I'm not sure. For linux, sometimes we have to do extra work (UDEV rules) but I can't say for Mac. What are these references to drivers and where are you seeing them?
Click to expand...
Click to collapse
I have been researching and reading guides on this site for almost 2 days just gathering infomation. Today I used the guide i referenced in above post to install ADB on my Mac. Most of the information and guides written on this site are for PC users, so that is where I kept seeing a reference to device drivers, but I just wanted to clarify in case I missed something that was assumed I should already know about using a Mac to root. I am guessing that since my computer recognizes my N6 in system report, that it does not need a driver, but since I am very much a novice, I wanted to ask.
jacksradio said:
I have been researching and reading guides on this site for almost 2 days just gathering infomation. Today I used the guide i referenced in above post to install ADB on my Mac. Most of the information and guides written on this site are for PC users, so that is where I kept seeing a reference to device drivers, but I just wanted to clarify in case I missed something that was assumed I should already know about using a Mac to root. I am guessing that since my computer recognizes my N6 in system report, that it does not need a driver, but since I am very much a novice, I wanted to ask.
Click to expand...
Click to collapse
Fair enough. In my adb and fastboot thread, there is a link to a tool that installs adb and fastboot on mac and that is literally all it does, so I don't think there is anything else for you to do. It seems to me that the issue may be on the device side, but unless you have parallels or bootcamp, I'm not going to be able to help you troubleshoot that.
danarama said:
Fair enough. In my adb and fastboot thread, there is a link to a tool that installs adb and fastboot on mac and that is literally all it does, so I don't think there is anything else for you to do. It seems to me that the issue may be on the device side, but unless you have parallels or bootcamp, I'm not going to be able to help you troubleshoot that.
Click to expand...
Click to collapse
Thank you for trying, I appreciate it and hopefully someone else may have some insight
jacksradio said:
Additional information......I keep seeing a reference to device drivers but I always thought Mac's did not require a driver to use ADB. Am I correct? Also, Android File Transfer works perfectly when I connect my N6 so the computer itself seems to be recognizing it. It also shows up as a Nexus 6 under "USB" in the system report.
This is the guide I used to set up ADB https://www.google.com/url?q=http://forum.xda-developers.com/showthread.php%3Ft%3D1917237&sa=U&ved=0CA4QFjAEahUKEwjvraDV2K7IAhWEoogKHbJPAxc&client=internal-uds-cse&usg=AFQjCNFwMzlRqY6AK7bv2ue6HmnF74sPjw
Click to expand...
Click to collapse
That's what I meant to attach No drivers needed for your Mac btw.
---------- Post added at 07:16 AM ---------- Previous post was at 07:12 AM ----------
OP did you get your ADB working?
jawmail said:
That's what I meant to attach No drivers needed for your Mac btw.
---------- Post added at 07:16 AM ---------- Previous post was at 07:12 AM ----------
OP did you get your ADB working?
Click to expand...
Click to collapse
I did not. However, I was able to root and flash recovery using fastboot. I can't for the life of me figure out why ADB isn't working though. I stumbled across an article which referenced EasyTether and how that can interfere with ADB and I remembered a few years ago, I had used that app on a different phone. I looked in the folder mentioned in the article and sure enough, the file extension was still there, so I unloaded it but even that did not help. I am wondering if there might be something else associated with EasyTether affecting it, but have no idea where to look or even how to completely uninstall it.
SOLVED
How do I marked thread solved?
I am getting an error message of 'ADB recovery device not found'. Gone through all of the suggested steps and still getting the same error. Any help please?
'ADB recovery device not found'or just 'device not found'?
It sounds like a driver problem. What are "all the suggested steps"? Do you mean the walkthrough of setting up PC drivers?
But why use NRT for something as simple as root? Once you have your drivers properly installed, you can use ADB to reboot into TWRP recovery (either permanently or temporarily) and in TWRP install SuperSU v2.68. Simple.
dahawthorne said:
'ADB recovery device not found'or just 'device not found'?
It sounds like a driver problem. What are "all the suggested steps"? Do you mean the walkthrough of setting up PC drivers?
But why use NRT for something as simple as root? Once you have your drivers properly installed, you can use ADB to reboot into TWRP recovery (either permanently or temporarily) and in TWRP install SuperSU v2.68. Simple.
Click to expand...
Click to collapse
Been through the process of installing the drivers, followed it word for word twice. ADB recovery device not found is the message that comes up.
How do I use ADB? Do I have to install/download twrp and SuperSU?
Sent from my Nexus 6 using XDA Free mobile app
You can do nothing in NRT or manually until you resolve your driver problems. Have you enabled OEM unlock in Settings? Enable Developer options & USB debugging? Is your device unlocked? If it is, when you reboot the first screen will show a small unlocked padlock.
There's too little information to give any proper answers. Tell us what you've done since you took the device out of the box.
dahawthorne said:
You can do nothing in NRT or manually until you resolve your driver problems. Have you enabled OEM unlock in Settings? Enable Developer options & USB debugging? Is your device unlocked? If it is, when you reboot the first screen will show a small unlocked padlock.
There's too little information to give any proper answers. Tell us what you've done since you took the device out of the box.
Click to expand...
Click to collapse
I was previously rooted until last week. Unrooted to try and make my bank app work. OEM unlocked and USB debugging checked. Last time I rooted I used this process and worked fine.
Sent from my Nexus 6 using XDA Free mobile app
Same laptop/computer? No OS changes that might have disabled drivers?
Please just reply inline without repeating this answer - I've just written it, so I know what it says and I don't need to read it again. Same advice for all users unless there's a long and convoluted thread where the backward reference isn't clear - in simple straightforward threads like this one there's no value in copying the entire message that you're replying to...
It's a company laptop that had a policy installed recently that prevents exe files. That's all, only other difference is the phone is now on the February security update.
Sent from my Nexus 6 using XDA Free mobile app
If I installed NRT on my company laptop I'd be fired immediately and walked off the premises. I don't know how we can help you - if your laptop is locked down with company security policies then that's likely to be the reason.
So my only suggestion is - use another laptop.
They are cool with it.
I will ask for the recent policy to be removed and see if that fixes it. Appreciate your time, thanks.
Sent from my Nexus 6 using XDA Free mobile app