Guys I'm at my wits end. I'm about to give up. I'm trying to get adb working on the nook here on my work computer. I can't for the life of me get it to work. I had no problem on my laptop, but then again I think I caught it before windows installed anything.
I've been using "usbdeview" to uninstall rogue drivers, trying to reel in the problem. However every time I go into device manager, it try's to install "Android ADB interface" which I think means its assigning the wrong driver to it. It should be "Android Composite ADB Interface", no? I know thats what it is on my laptop.
Anybody have any last ditch efforts? I should note that adb works perfectly fine on my Aria on this same machine. I love ADB, hate the setup though.
*****EDIT: Working on different usb port*********
You aren't alone, m8.
I used to have no problem with ADB over USB. But after re-formatting my laptop, I just couldn't get it to work, no matter what I did. I gave up
I'd tried wireless ADB, everybody said it's so easy, me? Couldn't ever get it to work. Gave it also.
At least, for now, I wouldn't think I need it.
I'm now convinced its not driver related. There is something holding my computer back from talking to it. But I'm 99% the right drivers are installed. Mounting disks works fine and it identifies like my android phone does, ADB just won't talk to it.
Try unchecking and rechecking Debugging mode...
Tried that many times. Just for fun I ran the easy adb executable on another machine here, THEN plugged in my nook to it. ADB worked perfect. I'm frustrated, but I really want to figure this thing out. (btw, it identifies with the exact same drivers on both machines)
EDIT: Don't know why or how, but for some reason switching usb ports (which I swear I've done before) worked!!!!!!! It now recognizes and can push/pull/install over adb (usb).
WWW.Ubuntu.com
Enough said.
Love me some Ubuntu, but CMD prompt > Terminal every time.
If you don't mind, can you provide the link to where you downloaded the driver?
Thanks
I used the "combo" pack which installed the drivers and a stripped version of ADB to C: (redundant since I already had ADB installed).
http://forum.xda-developers.com/showthread.php?t=910008
Thanks audio,
I'll give it another try.
DISCONNECT YOUR COMPUTER FROM ANY NETWORK TO AVOID WINDOWS UPDATE GOING ONLINE AND INSTALLING INCORRECT DRIVERS
Make sure you're Nook is identifying like this when its plugged in via device manager. If you're unsure how to get here; WINDOWS KEY + R, type without quotes "devmgmt.msc", hit ENTER.
{
"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"
}
Note: You're drive letter's under 'Portable Devices' may vary from mine, that's fine. Just make sure they are there.
DISCONNECT YOUR COMPUTER FROM ANY NETWORK TO AVOID WINDOWS UPDATE GOING ONLINE AND INSTALLING INCORRECT DRIVERS
I got all those except the Disk drive list above.
I'll give a try and see what happens.
We may need to uninstall some old drivers before we can get it to install the right ones. You on gtalk or msn? I'll help you troubleshoot it the best I can.
Works like charm.
LOL , without this thread, I would (actually I did) abandon installing ADB over USB.
Thanks audio for providing the correct link.
Gotta love this forum.
Related
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
I decided to change my dpi on my tablet to see if I could install an app that I needed from the market. Well I screwed up. I bumped it to 240 dpi and now I can't unlock my tablet when I cut the screen on because the unlock button that you slide to is off the screen. I can cut the camera on, but I have no home or back button because they are off the screen as well. I can't do anything. I need some help here. I have the build.prop file, but when I try to push it, it doesn't find my device. I have usb debugging on. Please help me before my wife kills me lol.
Wipe your tablet ,thing its fastest way.but you loose your apps and other stuff.
Wysyłane z mojego ASUS Transformer Pad TF300T za pomocą Tapatalk 2
I didn't think wiping would restore the build.prop file.
If the restore doesn't work, then you may have to flash the stock firmware to your tablet. Have you tried accessing it with adb?
I reset and it is still the same. Everytime I try to access through adb, it doesn't find my device. All the drivers are installed. If I could get adb to recognize my device, then I could push the build.prop file and everything would be fine. I'm really stuck here.
Best solution would be getting adb working correctly and pushing the stock build.prop
Do you have any idea why the adb might not be recognizing my device? I wouldn't need to have the bootloader unlocked for adb would I?
I ensure I have right drivers in a folder and not to always use installers, attach device then (on windows) use system/hardware manager and remove the device it is showing as, close device manager, detach device, re-attach the device when asked to install drivers select manually this will then install ALL the drivers required (I found genuine installer didn't install correctly or was fixed so not for users use only programs use) it should pick up your device on at least i'd guess x2 USB ports.
No bootloader etc needs adb to work to unlock it via USB
Rooted Xakep E320/C6 EUU Hacked Update
Try forcefully restarting the tablet. Hold the top power switch and the volume-down until it shuts off. Restarting often helps me with any problems I'm having. It may help your computer recognize the tablet if you keep it attached. And maybe restart your computer, windows is notorious for stuff like that.
Thanks all for the replies. Here's what's going on. I've reinstalled the drivers and the computer recognizes the device now. You can see from the attached image. Am I doing something wrong in my push command that is keeping the pc from pushing the file?
{
"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"
}
How about trying https://play.google.com/store/apps/details?id=lv.n3o.lcddensity&feature=search_result or any other similar app from the Play Store?
superuser has quit responding anytime that I try to run one of these apps. I can't allow permission so the app won't work. This really sucks. I wish I could just figure out why I can't push the file through adb.
UPDATE:
I fooled around and managed to navigate to the play store without unlocking the screen. Upon doing this, I got into superuser and then allowed the lcd changer app to run. Then I ran the app and it rebooted my tablet and it's back to normal. Thanks for all the tips guys. I am no longer in the dog house.
jbrowning37 said:
UPDATE:
I fooled around and managed to navigate to the play store without unlocking the screen.
Click to expand...
Click to collapse
Just out of curiosity: How did you manage to do that? Is it possible to control the device like that from ADB?
No, even with the screen locked I could pull down the notification bar. When it said "installing adobe flash player" I clicked it and the market opened. I would have been screwed had I not been able to do that.
You shouldn't run the "adb shell" command and then "adb push ....", you should push the file without you go into shell.
Not sure if that was really causing your issue or not, but it could be.
Hi guys,
I have literally tried everything I could find here. I have tried the Universal drivers, the PDAnet drivers, and the Google drivers, and I have used an installer as well as manually installed the drivers. For the universal and Google drivers, I can get the phone to be recognized by Windows 7 as a Nexus 4, and Windows says the drivers are configured properly. However, the phone doesn't mount and ADB/fastboot still don't connect (and yes, the phone is in USB debugging mode).
After every failed driver I uninstalled the device, removed the Google drivers from USBdeview, and reinstalled the next set of drivers, to no avail. The computer has been restarted many times, no luck. I have tried all three USB ports on my laptop, and I have tried multiple cords, one of which I know for sure works.
Any suggestions would be appreciated. Thank you.
EDIT: If you want, I can add a screenshot of my USBDeview entries to see if there are any conflicting drivers/interfaces. My old phone was a Samsung Galaxy S, but I removed as many of those drivers as I could find.
Silly question, but when attempting fastboot, you did reboot into the bootloader? If you use twrp, they have an adb push setting in the advanced tab(?), see if that's recognized at all?
Sent from my Nexus 4 using Tapatalk 4 Beta
I couldn't use adb or fastboot at all. No adb when the phone is on, no fastboot in the boot loader. I don't have a custom recovery because I can't flash one without fastboot.
Sent from my Nexus 4 using xda app-developers app
I'm also on 64-bit Windows 7, I forgot to mention that. Just tried the Universal Naked Drivers, to no avail.
Did you update adb to the latest version (v1.0.31)? If not, adb won't see the phone
EddyOS said:
Did you update adb to the latest version (v1.0.31)? If not, adb won't see the phone
Click to expand...
Click to collapse
Thanks for the reply. I've been trying to use Minimal ADB and Fastboot so far, since I really don't want to download the SDK. However, I've also tried to use the newest versions of Wug's Nexus Root Toolkit and mskip's toolkit, both of which do not work.
My Windows 7 Pro x64 work PC can see it as can my personal Windows 8 Pro x64 laptop at home - both using the stock Google drivers from the SDK
Remember, also, that when you run 'adb devices' the phone will ask you to allow the PC to connect. If you don't click OK on the phone it will say it's offline
EddyOS said:
My Windows 7 Pro x64 work PC can see it as can my personal Windows 8 Pro x64 laptop at home - both using the stock Google drivers from the SDK
Remember, also, that when you run 'adb devices' the phone will ask you to allow the PC to connect. If you don't click OK on the phone it will say it's offline
Click to expand...
Click to collapse
The window never pops up on the phone. ADB list of devices comes up blank. I'll try the SDK later.
Using the SDK and the newest ADB did not help, still the same problem. I'm out of ideas.
EDIT: Attached are two screenshots of the USBDeview program after I've uninstalled all the Google and Android drivers. Is there anything there that looks like it needs to be uninstalled?
{
"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"
}
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!
Hello
Sorry if this was a very noob topic
I done lots of flashing new ROM or back in stock process but i almost gave up this time
My phone status are
No OS
TWRP installed
Can boot to recovery
PC can't recognize the phone
Typing ADB devices shows empty list
Typing Fastboot devices also shows empty lines
30% battery left
I recently try to install the Lollipop version for my phone but it turns out that the zip are behaving like OTA (yep the title of the zips are OTA)
What i mean is it returned my recovery to stock
Without thinking much further i did 'fastboot flash recovery TWRP2810.img' thing (Yes i rename recovery image that way so it will be more convenience for me) and wipe all partition in the phone through the TWRP without problems
One thing i forgot is to "refresh" all ADB and Fastboot driver for my phone on the PC
Now my phone states are "No OS" and "PC doesn't recognize my phone" wether in ADB (obvious cause i can't boot with no OS so no USB debugging for me) and Fastboot (Enter Bootloader is OK, enter TWRP is OK too)
I already try the WUG step for installing the needed driver but no success since my PC can't recognize my phone
Try on 4 PC at my office and all of them are ignoring my phone
What should i do now, please, any help will be appreciated since its already the time i ussualy already at home
Thank You Very VERY MUCH for any help I can get.
unsungkhan said:
Okay, here's what you do.
Download the ADB drivers first, from here [URL="link"]http://developer.android.com/sdk/win-usb.html
Click to expand...
Click to collapse
unsungkhan said:
Extract the zip.
Once you're done extracting, boot your phone into bootloader mode, plug in USB, should show up as an unrecognized device.
Device manager from control panel, select device, properties, driver, update device driver, browse my computer, let me pick, all devices, have disk, navigate to where you extracted zip, select inf file, adb interface.
Should work.
Click to expand...
Click to collapse
[/URL]
Thank you Sir
I managed to fresh install my XP and continue with your instructions
I don't know why but it gave me this
{
"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"
}
I already try other driver but still a no go?
Do you happen to know other way around for tricking this Sir?
Please lock this unuseful thread
Before locking the thread, can you repeat all the steps and try with ADB Composite Device instead of ADB Interface?
Also, did you try changing USB ports, sometimes these things get a little troublesome because of faulty USB ports.
Last but not the least, you could also try a change of cables.
unsungkhan said:
Before locking the thread, can you repeat all the steps and try with ADB Composite Device instead of ADB Interface?
Also, did you try changing USB ports, sometimes these things get a little troublesome because of faulty USB ports.
Last but not the least, you could also try a change of cables.
Click to expand...
Click to collapse
#late_post
i've been able to resurrect my phone finally
after those steps i found Universal Naked Driver and it works
Thank You very MUCH Sir :laugh: