Hey everyone.
So I updated my Atrix 2 to the ICS leak earlier today, and can't for the life of me get it to show up in ADB.
What I've done:
1) Tried on Windows (7) and Mac (10.7) using the SDK and downloaded versions of ADB.
2) Installed different Moto drivers on the PC. Ones that I found via a Google search, and the ones on the phone when mounted.
3) Toggled USB Debugging on and off 100+ times, and checked through all the settings.
4) Tried different mount modes- MTP, PTP, and Mass Storage, all while toggling USB debugging.
5) Tried adb kill-server, adb start-server, adb devices, adb usb, adb wait-for-device way too many times.
6) Tried different USB ports and different cables on both computers
7) Tested my Galaxy Nexus (verizon) which was detected by ADB on both setups with no trouble
8) Booted into Fastboot and tried ADB, but no luck.
At this point I'm ready to smack my head against the wall. Why in the world won't the phone get detected by ADB?
Any advice or help is greatly appreciated!
On Mac try sudo adb whatever
Always with sudo
Sent from my MB865 using xda app-developers app
xxDriveNxx said:
Hey everyone.
So I updated my Atrix 2 to the ICS leak earlier today, and can't for the life of me get it to show up in ADB.
What I've done:
1) Tried on Windows (7) and Mac (10.7) using the SDK and downloaded versions of ADB.
2) Installed different Moto drivers on the PC. Ones that I found via a Google search, and the ones on the phone when mounted.
3) Toggled USB Debugging on and off 100+ times, and checked through all the settings.
4) Tried different mount modes- MTP, PTP, and Mass Storage, all while toggling USB debugging.
5) Tried adb kill-server, adb start-server, adb devices, adb usb, adb wait-for-device way too many times.
6) Tried different USB ports and different cables on both computers
7) Tested my Galaxy Nexus (verizon) which was detected by ADB on both setups with no trouble
8) Booted into Fastboot and tried ADB, but no luck.
At this point I'm ready to smack my head against the wall. Why in the world won't the phone get detected by ADB?
Any advice or help is greatly appreciated!
Click to expand...
Click to collapse
I had the same problem initially as well. I did some research and found a thread on the Moto support forum in which people with the official Razr ICS had the same problem. What finally fixed it for me was:
-Uninstall all drivers for your A2, reboot
-Install THESE drivers, reboot
-Factory reset (Settings->Privacy->Factory Reset, or something like that). Yes I know it's annoying but it's necessary.
-Once your phone reboots, just sign into google. Don't uninstall any apps or do anything like that. Don't enable USB debugging either.
-Connect for all 3 different connection modes. Wait for the drivers to download each time. If a driver fails to download, then uninstall it (not the MotoHelper), reboot your computer, enable the installation of unknown sources on your phone, then repeat this step.
-Once you have all those drivers installed, time to reinstall them with ADB! Enable USB debugging and repeat the previous step
-Once all your drivers are installed, reboot for good measure. But you should be good to do whatever you want now.
Hope this helps. I know it's a pretty roundabout way, but it works :\.
cogeary said:
I had the same problem initially as well. I did some research and found a thread on the Moto support forum in which people with the official Razr ICS had the same problem. What finally fixed it for me was:
-Uninstall all drivers for your A2, reboot
-Install THESE drivers, reboot
-Factory reset (Settings->Privacy->Factory Reset, or something like that). Yes I know it's annoying but it's necessary.
-Once your phone reboots, just sign into google. Don't uninstall any apps or do anything like that. Don't enable USB debugging either.
-Connect for all 3 different connection modes. Wait for the drivers to download each time. If a driver fails to download, then uninstall it (not the MotoHelper), reboot your computer, enable the installation of unknown sources on your phone, then repeat this step.
-Once you have all those drivers installed, time to reinstall them with ADB! Enable USB debugging and repeat the previous step
-Once all your drivers are installed, reboot for good measure. But you should be good to do whatever you want now.
Hope this helps. I know it's a pretty roundabout way, but it works :\.
Click to expand...
Click to collapse
I guess I'll have to give the factory wipe a shot tonight. I was really hoping it wouldn't come to that since I can't use Titanium Backup due to lack of root.
all i did was have my phone plugged in while i was installing the drivers. but i did have to download the ones from your post.
I followed the steps as above except the factory reset part (as that's a painful experience) but no joy. After ICS OTA upgrade, no adb for me. Looks like I'll bite the bullet and do a factory reset finally.
Before that I'll wait if anyone can post an easier workaround here. I have a 32-bit windows vista. (And a Ubuntu virtual machine on vmplayer)
ADDED Finally `Factory reset' had to be done and that did the trick. Without factory reset, the phone will not present itself as a ADB interface - hence ADB driver won't load - hence ADB will not detect it. So I don't know if all the driver uninstall/install/reboot in 3 modes ritual is necessary ... if you have all the drivers, just factory reset/wipe data and the phone shows up in adb.
kousik said:
I followed the steps as above except the factory reset part (as that's a painful experience) but no joy. After ICS OTA upgrade, no adb for me. Looks like I'll bite the bullet and do a factory reset finally.
Before that I'll wait if anyone can post an easier workaround here. I have a 32-bit windows vista. (And a Ubuntu virtual machine on vmplayer)
ADDED Finally `Factory reset' had to be done and that did the trick. Without factory reset, the phone will not present itself as a ADB interface - hence ADB driver won't load - hence ADB will not detect it. So I don't know if all the driver uninstall/install/reboot in 3 modes ritual is necessary ... if you have all the drivers, just factory reset/wipe data and the phone shows up in adb.
Click to expand...
Click to collapse
I had the same problem and did a factory reset yesterday. It worked fine, so I re-rooted.
But that was yesterday. Now today, adb will not connect again. Something more is going on here. I suspect it is related to the fact that I did the OTA update from ATT without first un-rooting or doing a factory reset. I also had added files to system memory (ringtones - which are still there).
EDIT: Sorry, I spoke too soon. One thing I hadn't done was to "Connect for all 3 different connection modes." I had only connected in Mass Storage and Media Device modes, so I connected in "Camera (PTP)" mode, allowed the drivers to install on my PC, and then adb started working again (in Camera or Media Device modes, but still not in Mass Storage Mode).
Bob G said:
I had the same problem and did a factory reset yesterday. It worked fine, so I re-rooted.
But that was yesterday. Now today, adb will not connect again. Something more is going on here. I suspect it is related to the fact that I did the OTA update from ATT without first un-rooting or doing a factory reset. I also had added files to system memory (ringtones - which are still there).
EDIT: Sorry, I spoke too soon. One thing I hadn't done was to "Connect for all 3 different connection modes." I had only connected in Mass Storage and Media Device modes, so I connected in "Camera (PTP)" mode, allowed the drivers to install on my PC, and then adb started working again (in Camera or Media Device modes, but still not in Mass Storage Mode).
Click to expand...
Click to collapse
FYI adb will not work in mass storage mode.adb needs the phone memory and other access which are not there when you connect your phone in mass storage where it acts merely as a card reader
Sent from my Atrix2 Stock ICS Leak#2 Rooted,Deodexed,With Google Now...
Just in case anyone else was on the fence about doing this: I had tried a million things (trying different computers, different USB cables, installing and uninstalling different drivers, editing driver inf files, editing adb_usb.ini, etc) for several days and nothing worked. I was skeptical about the factory reset helping, but now that I did it I can finally connect to my phone. Yay!
Related
Hi
Some background. Like many, I bought a TF700T and like a fool installed the OTA update to JB. I then downgraded, rooted in .30, then upgraded again and flashed SU to keep root in JB. I am now, therefore, running the stock OTA JB ROM, rooted. My bootloader is also unlocked.
Initially after this, plugging the TF700 into USb on Windows 7 (x64) worked fine - the device popped up as a Media Device and I could transfer files on and off it with ease. Now, without changing anything on either end, Windows is refusing to play. It tries to install MTP drivers but fails. If I boot the device in either CWM or Fastboot it connects fine (with adb and fastboot, respectively).
I want to get files on and off the *internal* storage (I don't have an external sdcard)
Things i have tried:
- Using a different USB port
- Using one of the USB ports on the back of the machine, instead of the front ones
- Uninstalling the MTP drivers
- Using the ASUS drivers from the website
- Cleaning out all my old unconnected USB devices (show devmgr_unconnected_devices=1 or whatever) and uninstalling all THOSE drivers
- Cleaning out with USBDeview
- Fresh install of the OTA ROM, after a data wipe/factory reset and wiping cache and dalvik
The only things I haven't tried are a new USB cable (damn you ASUS and your proprietary connector), and a clean install of Windows (major ballache).
Any ideas about what I could do to sort this would be greatly appreciated.
Since I only want to be able to move files on and off the device, I tried a workaround. I tried mounting the sdcard (internal) in windows manually through adb but the command I used to use on my old S2 through adb shell (echo dev/block/mmcblk0 > /sys/devices/platform/usb_mass_storage/lun0/file) but it errors with No such path or similar. I'm unsure if the mount points are different (I guess they will be, can anyone help with telling me what the mount point for the internal emmc is on the tf700?)
Really hope someone will be able to help me!
Thanks in advance guys
I'm in a similar situation except I'm not rooted or unlocked. I've tried just about all the steps you've mentioned w/ no luck. I've even tried to three different PCs running XP, Vista, and 7 and get the same result. What makes the situation even worse is my brand new 32GB microSD card won't read on my desktop as well.
m000se said:
Hi
Some background. Like many, I bought a TF700T and like a fool installed the OTA update to JB. I then downgraded, rooted in .30, then upgraded again and flashed SU to keep root in JB. I am now, therefore, running the stock OTA JB ROM, rooted. My bootloader is also unlocked.
Initially after this, plugging the TF700 into USb on Windows 7 (x64) worked fine - the device popped up as a Media Device and I could transfer files on and off it with ease. Now, without changing anything on either end, Windows is refusing to play. It tries to install MTP drivers but fails. If I boot the device in either CWM or Fastboot it connects fine (with adb and fastboot, respectively).
I want to get files on and off the *internal* storage (I don't have an external sdcard)
Things i have tried:
- Using a different USB port
- Using one of the USB ports on the back of the machine, instead of the front ones
- Uninstalling the MTP drivers
- Using the ASUS drivers from the website
- Cleaning out all my old unconnected USB devices (show devmgr_unconnected_devices=1 or whatever) and uninstalling all THOSE drivers
- Cleaning out with USBDeview
- Fresh install of the OTA ROM, after a data wipe/factory reset and wiping cache and dalvik
The only things I haven't tried are a new USB cable (damn you ASUS and your proprietary connector), and a clean install of Windows (major ballache).
Any ideas about what I could do to sort this would be greatly appreciated.
Since I only want to be able to move files on and off the device, I tried a workaround. I tried mounting the sdcard (internal) in windows manually through adb but the command I used to use on my old S2 through adb shell (echo dev/block/mmcblk0 > /sys/devices/platform/usb_mass_storage/lun0/file) but it errors with No such path or similar. I'm unsure if the mount points are different (I guess they will be, can anyone help with telling me what the mount point for the internal emmc is on the tf700?)
Really hope someone will be able to help me!
Thanks in advance guys
Click to expand...
Click to collapse
First check make sure you have your "USB debug" and "Unknow software" checked in settings. Then go here and install the pda software for your windows. Once installed, it will installed all the driver for your tab automatically. You don't need to use the software, you can uninstall it later, but the driver will stay.
http://junefabrics.com/android/download.php
I haven't picked up a TF700 yet (out of stock locally), so these are just general suggestions...
From adb, shell into the OS (adb shell) and list the directories to try and determine their structure. If the device is booted, the internal SD should already be mounted.
I would start by looking for the following folders:
/sdcard
/mnt/sdcard
/data/media
m000se said:
Hi
Initially after this, plugging the TF700 into USb on Windows 7 (x64) worked fine - the device popped up as a Media Device and I could transfer files on and off it with ease. Now, without changing anything on either end, Windows is refusing to play. It tries to install MTP drivers but fails. If I boot the device in either CWM or Fastboot it connects fine (with adb and fastboot, respectively).
Click to expand...
Click to collapse
I had the same problem getting MTP to work on old XP machine. The following worked for me...see post #12
http://www.transformerforums.com/fo...ormer-manual-usb-drivers-sync-software-2.html
Thanks for the replies, everyone. I installed PDANet and was initially hopeful once the drivers started installing. Sadly, Windows still doesn't see my device.
adb shell-ing into the device --> mounts
This lists /dev/fuse as the internal storage. I can't echo this to /sys/devices/usb_mass_storage/lun0/file because when I do it returns "No such file or directory"
The solution posted as working on XP machines doesn't work either.
This is seriously annoying. I'm tempted to just give in and get myself a 32GB SDHC and card reader and just use that instead - at least that way I can move the files across with Root Explorer or something...
Alright, here goes my first post. I have lingered in these forums for awhile, and have always found what I needed. This is the first time my searching on here, as well as google, has let me down.
To clarify, if I connect to my computer and have USB Mass Storage on, I can see it, move files to it and everything. My problem is, I am using my old phone (P500) to learn and practice ADB (I own a GNEX), and would like to install CWM via ADB, but I need to move files to the root of my sd.. but my phone won't show up if it's in debugging mode!
I have the drivers installed, and used a toolkit to root (worked fine, no errors). Am I missing something here or is there another issue?
Info:
Windows 7 64bit
Telus Mobility (Canada)
Model: LG-P500h
Android 2.3.3 (stock)
stock kernel
MissBizz said:
Alright, here goes my first post. I have lingered in these forums for awhile, and have always found what I needed. This is the first time my searching on here, as well as google, has let me down.
To clarify, if I connect to my computer and have USB Mass Storage on, I can see it, move files to it and everything. My problem is, I am using my old phone (P500) to learn and practice ADB (I own a GNEX), and would like to install CWM via ADB, but I need to move files to the root of my sd.. but my phone won't show up if it's in debugging mode!
I have the drivers installed, and used a toolkit to root (worked fine, no errors). Am I missing something here or is there another issue?
Info:
Windows 7 64bit
Telus Mobility (Canada)
Model: LG-P500h
Android 2.3.3 (stock)
stock kernel
Click to expand...
Click to collapse
Since the device is not getting detected with USB Debugging enabled it's safe to assume a bad driver installation. To verify tho, enable USB Debugging on the device and connect it to your PC. Go to Device Manager. Somewhere towards the top, assuming the drivers were installed will be a device "ADB Interface" with a subitem "Android Platform Sooner Single ADB Interface" or something similiar. If the "ADB Interface" item isn't there then the drivers weren't installed correctly. Uninstall them. Reboot computer. Rerun driver installation program. When it finished, reboot your PC. Power off the device. Connect it to your PC. Power on the device and let all drivers install. You should be good to go from here.
If you'd like a good known set of LGE USB drivers, download Android Flash Recovery, link is in my signature. Hope this helps.
EDIT:
Oh, and Welcome to XDA
ADB, but not Fastboot, can see my phone. I have followed the same steps as with Windows 7, yet I can't get fastboot to see my device on this new machine. I see threads for other phones, but didn't see one for this for our phone. I need to reflash my recovery because this new CWN can't mount the sd card and I need to reflash root and busybox after OTA update (ota survival failed)
zomgitsanoob said:
ADB, but not Fastboot, can see my phone. I have followed the same steps as with Windows 7, yet I can't get fastboot to see my device on this new machine. I see threads for other phones, but didn't see one for this for our phone. I need to reflash my recovery because this new CWN can't mount the sd card and I need to reflash root and busybox after OTA update (ota survival failed)
Click to expand...
Click to collapse
OTA survival failed?
Did you pay for superSU pro?
It's worked for me since ICS
And about the fastboot on Windows 8.1......Good luck
EDIT#
annoyingduck said:
After the upgrade, all drivers are wiped. Hooking up N7 to cpu triggers an auto setup that does not work correctly. In device manager what shows is and android device with an adb composite interface driver, but no actual N7...its hidden. This is how I got it to work:
I had already reinstalled SDK/platform tools/etc (if you haven't done this, just download the google drivers themselves from google). Connect device with debugging enabled and allow the auto setup. Turn off debugging, and again allow the auto set up. On my computer, both with debugging on/off the N7 did not show up in the devices list. While debugging is off, open the control panel, go to hardware+sound/view devices. Here the N7 will show. Right click it/properties/hardware/click the driver/properties/change settings/driver/change settings/update driver/manually search/choose MTP. Reboot, enable debugging/hook up/right click start/device manager/android/android adb composite driver/right click/update driver/manual search/type in path to the google drivers/install.
After that your N7 will read in the device list as an N7, files will show in the file manager (MTP), and ADB will work....
Click to expand...
Click to collapse
TRY THIS
Windows has determined the driver software for your device is up to date.
I worked just fine on a Windows 7 machine
One more reason 8 is a POS
OTA survival was a partial success. Some apps can still get root, apparently, but others fail and
This device cannot start. (Code 10)
A request for the USB BOS descriptor failed. (when in fastboot)
adb devices doesn't show anything. I have tried it with linux and windows (with Motorola drivers installed), it doesn't work. I can access the phone when I have enabled MTP, but it just won't show in adb. I have killed and started adb server so many times, it's frustrating.
The thing is, the first time (yesterday) it worked! I could reboot into fastboot with adb but then nothing worked anymore.
Any ideas?
Maybe silly question, but: is USB debugging activated on the phone? If yes, try to switch between MTP and Camera (PTP) under "USB computer connection" option. You should get the authorization prompt on your phone when everything is fine.
Yes, USB debugging is activated. I already tried both MTP, PTP, and neither, but I don't get any authorzation prompts. I revoked all previos prompts, but still nothing. Thanks for the suggestion though!
Are you on bootloader or recovery or normally on os
I tried all three.
Try playing with the USB cable - change it, change the USB slot on the PC that it's connected to, etc.
I only have one USB cable, but I already tried it on several USB slots.
It worked! I had to put sudo in front of my adb commands! Yay! :victory:
I am actually following the steps from the pwnieexpress guide to build my own pwn phone, in an attempt to build my own pwn phone. With no malicious intent, I'm trying to build up my pentest skills on the go.
I'm currently on Windows 7 using the android sdk. Fastboot devices manage to return my device but on step 13, my adb devices shows blank in the list of devices.
When I plugged in my wiped out nexus 5, device manager shows the Google nexus adb driver, but I cannot seem to get the adb devices to show my device.
I tried restarting the adb server and reconnecting my device to multiple USB ports but doesn't seem to work.
Any ideas? I've yet to try on a different machine, but could it be a problem with the ports?
Looking forward for any help available.
Don't slam me for asking the obvious, but do you have USB debugging ticked on in the os settings? You may have to go through an update of the android composite adb interface drivers via device manager. Just choose to browse computer, pick from a list, then run the update on each item listed. This doesn't install anything new but does seem to reset drivers. Beyond that, can't help.
Sent from my Nexus 9 using Tapatalk
Fixed. Seem to be a problem with the usb drives on my home PC, it failed to detect the device during adb devices. Weird, as fastboot seemed to work out well.
I basically installed the drivers in another machine and adb devices and adb push .. /sdcard/ worked just fine.
Thanks!