Hi there... totally new to the Andriod world and am stuck on trying to upgrade the firmware. I am running Windows 7 64 bit and the devices says that it is installed correctly yet when I run "adb devices" it gives me and error stating "command not recognized....? any idea's?
Rogers device....
do you have your sdk setup correctly? do you have the sdk tools folder in your path?
you can find out by typing path
you should see
C:\android\tools as one of the entries....
windows is telling you that the adb command is not found.
i have the same issue. running windows 7 64bit and adb doesnt find the device. the phone doesnt show up in the device manager either, but it told me that it installed correctly when i first plugged it in.
Related
Windows XP, with sdk developers kit, and the motorola USB drivers.
It works via fastboot and i can flash. Once i reboot my xoom and it comes to the lock screen, adb remount informes me device not found.
I do a adb get-state and it's unknown.
My XP machine sees the xoom as it boots up, then pops the driver install wizzard, but can't locate a driver. I have pointed it to "C:\Program Files\Common Files\Motorola Shared\Mobile Drivers\Drivers" as well as the c:\Program Files\Motorola folder with no success.
Keep in Mind before that on this computer, with the xoom booted i had this issue of it not finding a driver....but when i used the dev kit and was able to flash, i didn't realize once the xoom booted i wouldn't be able to use adb any longer.
Was updating bigdogrush's kernel. I did my origional flash from my home windows 7 comptuer.
any advice would be appreciated.
Found in the moto community forums a similair thread and it stated you had to install Windows Media 11 for the MTP update. Sure enough that worked.
I've had ADB working successfully in the past, but now nothing is listed after an "adb devices" command, and a "device not found" error for other commands. I was on Royal Ginger 2, and just updated to the latest CM7 nightly - then wanted to use ADB to tweak a few things and found out something was wrong. What else do I need to do to get adb to recognize my device?
I haven't changed anything on my laptop, which is Win7 64bit, and I've updated everything in SDK Manager. Device Manager on the laptop shows T-Mobile myTouch4g USB Device under Disk drives on the Device Manager, and I believe I have the latest mt4g drivers installed. I'm connecting via USB with debugging turned on, and without turning on USB storage.
Any ideas?
I was finally able to get adb to recognize my device again. FYI, I tried a few different things, but I think what finally got it working was tweaking the *.inf file in the usb_driver folder in SDK, the uninstalling/reinstalling the drivers - as outlined here:
http://forum.xda-developers.com/archive/index.php/t-881324.html
Just got my LG G2. I rooted it and flashed a custom recovery and then wiped everything on the internal SD card. No biggie, I'll just adb sideload a rom. However, when I type in "adb devices" it says "list of devices attached" and then nothing is listed.
Device manager shows "g2" with an exclamation point. Following rooting steps I loaded the LGUnitedMobileDriver blah blah 3.10.exe and it installed correctly. I even tried it again, but I cannot get the g2 with exclamation point to go away. The computer is Windows 8 64 bit, and I tried it on my laptop which is Win 8.1 64 bit.
I also pointed the driver search to the LG Mobile United Driver folder and it couldn't install.
Is there a .zip file of the driver I can point to? I can't seem to find one and I need my phone
Please help!
Nurmi_CEO said:
Just got my LG G2. I rooted it and flashed a custom recovery and then wiped everything on the internal SD card. No biggie, I'll just adb sideload a rom. However, when I type in "adb devices" it says "list of devices attached" and then nothing is listed.
Device manager shows "g2" with an exclamation point. Following rooting steps I loaded the LGUnitedMobileDriver blah blah 3.10.exe and it installed correctly. I even tried it again, but I cannot get the g2 with exclamation point to go away. The computer is Windows 8 64 bit, and I tried it on my laptop which is Win 8.1 64 bit.
I also pointed the driver search to the LG Mobile United Driver folder and it couldn't install.
Is there a .zip file of the driver I can point to? I can't seem to find one and I need my phone
Please help!
Click to expand...
Click to collapse
SOLVED
When I went to device manager, I chose "install driver from a compatible list off your computer" (or something like that) and I chose ADB driver. It turned it from g2 to android adb device in the device manager. Then when I typed in "adb devices" it showed the phone. I am sideloading a rom right now!
This guide is for people that have always problems with drivers, ADB or fastboot problems, with this guide you will clear all.
Tested and working with windows 8.1 (it will work with all other versions of windows, probably not with Windows 10 preview).
*0) Unplug of course the phone from the PC
1) Download USBDeview (32bit version here http://www.nirsoft.net/utils/usbdeview.zip - 64bit version here http://www.nirsoft.net/utils/usbdeview-x64.zip) to erase every driver on the pc (look under "Description" tab and uninstall all Asus things, MOOREFIELD, delete also your previous phones drivers or unused devices)
2) Reboot
3) If you are on windows 8 or 8.1 disable driver signature verification and than install
1- Intel Drivers https://software.intel.com/en-us/android/articles/intel-usb-driver-for-android-devices
2- ADB Installer http://forum.xda-developers.com/showthread.php?p=48915118#post48915118 (don't change installation path)
4) Reboot
5) Go in C:/adb, hold shift on keyboard, right click in the folder and "Open command prompt here"
6) Go to recovery with the phone plugged in
7) Tap apply update from ADB Sideload
7) Type in the previous cmd window: adb devices
If you can see your device, congratulations!
Thanks to @cangcan to this other tip:
If you installed bluestack on your pc, adb will show 'device emulator' something like that and you need to turn off the bluestack service..
1. Go to start and type services.msc
2. Look for Bluestack android service
3. Stop or disable the service
Its messing up my adb connection in windows 7 and now the zf2 device is recognised on adb after disabled Bluestack services..
Thanks to- Everyone in this section
Snoop05 for "15 seconds ADB Installer"
another thing i found for adb device not recognised for example in my case before..
if you installed bluestack on your pc or laptop, adb will show 'device emulator' something like that..
you need to turn off the bluestack service..
1. go to start and type services.msc
2. look for bluestack android service
3. stop or disable the service
its messing up my adb connection in windows 7 and now the zf2 device is recognised on adb after disabled bluestack services..
type adb devices to confirm it.
cangcan said:
another thing i found for adb device not recognised for example in my case before..
if you installed bluestack on your pc or laptop, adb will show 'device emulator' something like that..
you need to turn off the bluestack service..
1. go to start and type services.msc
2. look for bluestack android service
3. stop or disable the service
its messing up my adb connection in windows 7 and now the zf2 device is recognised on adb after disabled bluestack services..
type adb devices to confirm it.
Click to expand...
Click to collapse
I will add this to first post, thanks
Hello, I badly need someones assistance. I accidentally installed the OTA update on my rooted zenfone 2 causing it to be bricked. I have spent the last 3 hours uninstalling and then reinstalling the drivers per the above directions. My PC recognized when I connect the phone via USB, and it is showing up as a working device in the device manager screen. It shows the drivers are installed properly and everything but I just cannot view it. I tried disabling the bluestack (it actually was not turned on but I made sure to disable it in case) and that did not work as well. I now have a zenfone 2 that is currently a paperweight and I cannot for the life of me figure out what to do next. Any help would be greatly appreciated.
Thank you for this
I'm trying to get my ADB interface working via the male-to-male USB cable. I can't install the drivers. I'm running windows 7 64 bit and copying the DLL's from i386 (I have an intel processor) to c:\Windows\SysWOW64 then using the command prompt in administrator mode: regsvr32 "filename".dll and I get the message "the module 'module name' was loaded but the entry-point DIIRegisterServer was not found. Make sure that 'module name.dll' is a valid DLL or OCX file and then try again."
I've also tried installing the drivers from the device manager and selecting a path to the driver folder.
Af far as I can tell these are the universal USB drivers. Any ideas?
Phoenix4848 said:
I'm trying to get my ADB interface working via the male-to-male USB cable. I can't install the drivers. I'm running windows 7 64 bit and copying the DLL's from i386 (I have an intel processor) to c:\Windows\SysWOW64 then using the command prompt in administrator mode: regsvr32 "filename".dll and I get the message "the module 'module name' was loaded but the entry-point DIIRegisterServer was not found. Make sure that 'module name.dll' is a valid DLL or OCX file and then try again."
I've also tried installing the drivers from the device manager and selecting a path to the driver folder.
Af far as I can tell these are the universal USB drivers. Any ideas?
Click to expand...
Click to collapse
AARRGGHH! Windows and its damn' driver problems! First did you disable driver verification? If not Google it. Then install MoDaCo's drivers using the Windows GUI tools (IIRC you get there from Device Manager). If all that doesn't "take", my best advice is to wipe all trace of Windows off your computer and install a sane operating system. Too radical a fix? OK, your funeral, but here's a halfway fix: download this Puppy Linux live-CD .iso that I've doctored with Fastboot and ADB binaries, and burn it to a CD.
http://www.mediafire.com/download/62oh30gzjzvsbew/sulu2-528.007-android.iso
Make sure you know how to burn a CD from a .iso file. The end result will have files and folders, not just a single .iso file on it. It's a bootable CD, so you guessed it, boot your PC to the CD. Don't try to run it in a VM, it won't work. Click on the terminal icon on the desktop and you have a box that looks and acts like the Windows DOS box; the OS commands are somewhat different but the fastboot and adb ones are exactly the same. In fact the terminal is the same as the one in Android, and since both devices are Linux now, driver problems disappear!
Do whatever dastardly deeds you want to the MOJO with Fastboot or ADB, eject the Linux disc, reboot--and as far as your PC is concerned, it never happened. The live-CD won't leave a trace unless you specifically tell it to.
Most of the tutorials on this MOJO forum give commands like "fastboot-linux flash twrp(version), this is MoDaCo's version of Fastboot. I put this live-CD together using Google's binaries so that command would look like "fastboot flash twrp(version). Keep in mind that with the MOJO the device ID string is mandatory; see the TWRP recovery thread for details, but you can't just send "fastboot devices", it won't work, you must send fastboot -i 0x0738 devices, or go straight to flashing or booting.
Well I don't know if I just cleared the waters some or just stirred it up more, but good luck and I hope I helped a little anyway!
This was how I was able to install my drivers on my Win 7.
Assuming that you've downloaded the superboot-mmm file and you've extracted to your C: drive:
1. Go to Devices and Printers under Control Panel
2. Right Click on the Fastboot device, and click on Properties
3. Click on the Driver tab, and click on Update Driver (or click on Properties)
4. Click on Browse My Computer For Driver Software (manually)
5. Browse the following location (or copy and paste this: C:\r3-mojo-superboot-mmm\windows.driver)
6. Select Next
7. The driver will be installed
If you now replug the MOJO, you should be able to see Madcatz ADB Interface under Hardware Tab when you click Properties
Source: my blog
Hope it helps.
Yes! Thank you
Yes, the problem was I was going a folder too deep in selecting the driver from the device manager. Thank you.