[Q] Why won't adb recognize the Nexus 10? - Nexus 10 Q&A, Help & Troubleshooting

adb isn't recognizing the Nexus 10 on Windows 7 or Ubuntu 11. Here's what I've done:
Installed the SDK and USB driver from Google. Windows 7 sees the tablet as an 'Android ADB Interface' under 'Android Device.'
Put the tablet in developer mode by clicking on 'About tablet' and clicking the build number seven times.
Put the tablet in Camera (PTP) mode by going to Storage > USB Computer Connection.
Started and restarted the tablet, my computer, and the adb server.
On Linux, I've done the following:
Installed the SDK.
Added the vendor ID "18d1:4ee5" to ~/.android/adb_usb.ini
Created a file /etc/udev/rules.d/99-android.rules.
Restarted my computer, udev, the adb server, and the tablet.
Here is the content of 99-android.rules:
Code:
SUBSYSTEM=="usb", ATTRS{idVendor}=="18d1:4ee5", SYMLINK+="android_adb", MODE="0666" GROUP="plugdev"
TEST=="/var/run/ConsoleKit/database", \
RUN+="udev-acl --action=$env{action} --device=$env{DEVNAME}"
Am I missing something? Thank you.

matthugh said:
adb isn't recognizing the Nexus 10 on Windows 7 or Ubuntu 11. Here's what I've done:
Put the tablet in developer mode by clicking on 'About tablet' and clicking the build number seven times.
Click to expand...
Click to collapse
Did you turn on usb debugging in developer options?

Atmazzz said:
Did you turn on usb debugging in developer options?
Click to expand...
Click to collapse
No, I hadn't! I thought the seven taps on the build number put the tablet in USB debugging mode. But you're right - you have to do that separately.
Thank you. Everything works now.

I have done everything that you have done but windows 7 won't recognise the nexus 10 weather in developer mode or not. Any help?

CRimsonEagle said:
I have done everything that you have done but windows 7 won't recognise the nexus 10 weather in developer mode or not. Any help?
Click to expand...
Click to collapse
TRY THIS:- Works like a CHARM!!!
http://koush.com/post/universal-adb-driver

Be sure to "Allow ADB Debugging" on the device not just turn on the developers options.
You need to accept the security notification on the device itself because if you don't no driver will ever work.
Boot pc, boot device plug device on leave screen active, attempt adb and on the device accept the adb connection permanently.
This is a new security feature introduced in adb and you must use the most current version of adb as well.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Related

Issues with adb shell, etc.

So for the first time I've set up my ADB since I will getting a MT3G tomorrow. Environment variables (PATH) set correctly, etc.
When I type adb shell in recovery model, it says *daemon not running. starting it now, daemon started successfully, error: device not found*
"Android Compsite ADB Interface" shows up in my USB devices. So what's the problem.
Then when I load up "emulator -data c:\", it starts up and gives me this error. msvcrt.dll? I've dealt with that .dll file before for other apps and it is in my system32 folder.
So what's going on here.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
try reinstalling the usb driver.
mine identifies as HTC Dream Composite ADB Interface.
did you install the usb driver that comes in the SDK?
what if you navigate to the location you have the sdk installed? does it work then? maybe the path is not set up as correct as you think? (i had this problem when trying to do fastboot. everything else worked fine except for fastboot. to get that working i had to navigate to the sdk directory.)
I sure did, and it reads exactly that.
Even adb devices doesn't bring a device up. Or adb remount.
Other thing is under Hard Drives Tree, the HTC Android USB Phone Device has a Microsoft driver. I tried to install drivers from the android/usb_driver/ and nothing. Do I have to do this in the Home Screen for the first time so it brings up the permission screen where I click on "Allow Always" for root? Cause I'm not getting that there, so I rebooted into recovery....nothing there as well.
i did have an issue recently where i couldn't get the usb driver to change over.
what i had to do to get it to change was disable and then re-enable usb debugging while the phone was connected to the computer.
it triggers a hardware change in windows and this allowed me to reinstall the correct driver.
uninstalling the current drivers might also help.
I've tried both things.
Same issue.
What Windows Services need to be enabled in order to get ADB to work? I did some tweaking of the services.msc for XP. I think that might be the reason adb shell isn't working.
Same problem I have:
I have TWO rooted G1s, Cyanogen 4.0.4 modified devices with identical Software releases.
The one (rooted by the Golcard Method) is recognized by ADB - the other one (rooted by the One Click Method) is not.
Troubled !
Oh Sorry -this is a Sapphire forum ... I apologize

Halp! Windows 8.1 upgrade at war with n4

Hi,
I had win 8 in which I was successfully able to do everything with my n4 (adb connections were good and so was MPT). I updated to win 8.1 and now it's derping out. ADB drivers seem fine. I tested it by simply running adb shell in cmd prompt, but even though my device is connected, it says that it's unable to find device.
Whats more important to me is that the device is not showing up in my computer. Although windows plays the usual usb connection sound. I'm also able to see it has detected my device as Nexus 4 is under the unknown device category. How can I fix this. I relly need to transfer a few things between the comp and phone, and it kinda sucks at the moment.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
blueren said:
Hi,
I had win 8 in which I was successfully able to do everything with my n4 (adb connections were good and so was MPT). I updated to win 8.1 and now it's derping out. ADB drivers seem fine. I tested it by simply running adb shell in cmd prompt, but even though my device is connected, it says that it's unable to find device.
Whats more important to me is that the device is not showing up in my computer. Although windows plays the usual usb connection sound. I'm also able to see it has detected my device as Nexus 4 is under the unknown device category. How can I fix this. I relly need to transfer a few things between the comp and phone, and it kinda sucks at the moment.
Click to expand...
Click to collapse
Just format it and install Ubuntu!!!
lol, just jocking. if adb is working you don't need it to recognize it. You can just use adb push/adb pull, but anyway.. did u try to enable debugging?
It means something has derped with the mtp driver
Open up device manager
You will see your nexus 4 with a yellow exclamation mark next to it
Right click and update driver
Manually choose
Then you will have to scroll through the list and find the mtp device (I can't remember of the top of my head exactly which headers it is under)
Sent from my Nexus 4 using xda app-developers app
Connect your Nexus 4 in USB debuggin mode and uninstall your current driver in device manager checking the 'delete the driver software' option.
Download Universal Naked Driver: http://forum.xda-developers.com/showthread.php?t=1379875
Reboot Windows 8 into advance mode and select to disable driver signature: PC Settings -> Updates and recovery -> Recovery -> Advance startup -> select F7 option at the selection menu when you see it
Reconnect Nexus 4 and install it with UND driver.
Thanks all! I just uninstalled the current drivers and reconnected the device. Windows picked up on the right drivers. All ok!

Google Nexus 4 MTP mode not recognized by Windows 10 (Manual Fix)

Hello N4 Owners/Users.​
lately I've been working on IOS & iCloud Activation Lock Security, which is a Job I honestly do not wish you have, because is not a great business at all but, going more deep in this post I'm glad to post it because I've been trying to send iCloud Accounts stored on a PDF at my Nexus 4, a device that I've purchased last month at eBay and is incredible how this device with Unofficial ports runs faster and without bugs, of course using PURE Nexus ROM.
first things first, I must specify that I was sideloading ZIP's, APK, ROMS through ADB SIDELOAD commands, so that the first sign of a properly working USB Port, I didn't noticed yet that I was unable to set up my device as MTP and transfer photos or WhatsApp Folder to my PC.
2 weeks later I've noticed that MTP was not working, even changing "Charge Option" to "Transfer Files" so I just put my knowledge on going, the first thing was download the USB driver at Google SDK webpage, which delivers USB Drivers apart instead with the whole SDK, I've just proceed to download it, I've installed it and for my surprise the MTP was still not working...
what do now ?​
Steps:​
1. Download the proper driver designed by google
Google Nexus 4 Drivers.
2. Make sure your PC is not on secure boot, for this you should reboot your PC and enter to BIOS Setup to make sure secure boot is not activated, if it is, please turn it off.
3. reboot again and let your PC boot, you may notice that the boot sequence UI display a little messed up, but is normal.
4. go to UWP Settings and Select "UPDATE & SECURITY"> "RECOVERY"> "Advance startup" and hit at "Restart Now"
5. your PC is going to restart again & you'll see a menu of likely 10 or 9 options, we need deactivate the option 7.
7). Disable Driver Signature Enforcement.
Click to expand...
Click to collapse
doing this your PC will restart again or maybe it just boot the Windows or UEFI Logo.
6. Find & Run CMD as administrator and execute the code below.
bcdedit /set TESTSIGNING ON
Click to expand...
Click to collapse
Restart your PC Again.
wait, you need the MTP or really are you craying for such restarts?
okay, that's what I though.
7. Disable ADB on your device and connect it to PC, Open device manager and look for "Android ADB Interface"
8. Right Click on the device and select "Update driver", Select "Browse My Computer for driver software"
9. locate drivers folder you've already downloaded following this guide and after that, you must have this screen
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Select "Let me pick from a list of available drivers on my computer"
If are 2 MTP entries, install them and reboot your PC, and that's all people, MTP working.
Now go back at CMD as Administrator and set this
bcdedit /set TESTSIGNING OFF
Click to expand...
Click to collapse
Now Restart and enter at BIOS, restore secure boot, done!
Hit "thanks" button if this helped you recovering MTP Access and your PC at your N4.

Problem to recognize device with ADB

Hello all,
after hours of searching and tries, i need some help.
I have Android 8.1 on my Asus Zenfone Max pro M1 and i have a win 10 PC
I have followed this guide --> https://forum.xda-developers.com/as...obs-to-unlock-relock-bootloader-twrp-t3894847
I have unlocked my bootloader with the apk without any problem
My phone is not recognized by adb. I have install drivers (with the phone, try to install also from the guide), when i plug my phone on USB (with USB debugging active) is recognized by Windows in the device manager (without yellow flag)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
but the command "adb devices" return nothing and like "fastboot devices" when i am on fastboot mode too
I have also tried another usb cable and another PC (on win 7)
I am stuck now, don't know what to do more.. Any clue?
Did you turn on USB debugging & OEM Unlock from developer settings?
debdeep98 said:
Did you turn on USB debugging & OEM Unlock from developer settings?
Click to expand...
Click to collapse
USB debugging is enable but OEM Unlock is not present from developer settings.
Yeah my bad no OEM unlock on asus.. Did you accept that allow pc thing with security key when first connecting to adb? If yes then revoke auth and try connecting. Also reinstall the drivers both asus and adb and try different cables and keep the device in mtp mode.
debdeep98 said:
Yeah my bad no OEM unlock on asus.. Did you accept that allow pc thing with security key when first connecting to adb? If yes then revoke auth and try connecting. Also reinstall the drivers both asus and adb and try different cables and keep the device in mtp mode.
Click to expand...
Click to collapse
I have tried MTP and other mode, different cable including the original one..... Still the same.
Can't revoke auth because adb never recognized my device

OP 6T fastboot device not detected

I had to reinstall Win 10 on my computer and now I'm not able to connect to my 6T in order to root it.
The boot locker is unlocked, I can see it at phone boot. It was unlocked also before last update to OxygenOS 10.3.7.
Debug USB in enabled. When I connect to the phone to the computer it is deceted and I can transfer files.
Whit ADB devices phone is deteted (picture is from all in one tool, using command prompt same result)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
using fastboot devices the phone is not detected.
installed last official usb drivers (google and oneplus)
Any idea, suggestion or further test that can help?
Thanks
Same problem here. Please help.
Finally I found a working solution.
If you have a laptop you have to disable secure boot.
Then you have to disable signature verification on windows 10 ( How to Enable or Disable Driver Signature Enforcement in Windows 10 | Tutorials (tenforums.com) ).
I used option 3.
Download Oneplus usb drivers ( Download Latest OnePlus USB Drivers for Windows and Mac (getdroidtips.com) ).
Then connect your phone in fastboot mode & open Device Manager on Windows & look for Other > Android device. If it is found, this means windows 10 is not having proper drivers to recognize fastboot device. Now install "OnePlus_USB_Drivers_Setup.exe" & it will show pop up for installing driver & after accepting(this is blocked due to signature verification in normal situation), Android device will be recognized in fastboot mode.
Thanks man, it worked for me.
Just to complete, after istalling the drivers you can restore signature verification and secure boot on Win 10.
Everything will work fine.

Categories

Resources