I've a Honor 10 View Lite with a broken screen (it's not usable) and I would try to recover data from it.
Following some tutorials it seems possibile to do that with ADB and the phone in recovery mode (holding power button + volume up).
I've installed ADB drivers through UniversalAdbDriver.msi and Fastboot version 1.4.3 Portable on Windows 10.
Being the screen black it's difficult to understand if the phone reboot in custom recovery mode or in normal mode, but when I open shell on the same folder of Fastboot and type 'adb devices' no device is found. I've also tried connecting another phone in recovery mode (Huawei Mate 10 Pro perfectly working) but the problem is still the same, no device found.
What can be the problem? Some wrong or missing installations?
I also have to specify that both the phones have USB debugging disabled and I hope this is not a problem because in the broken phone it's impossible to find a way to enable it. That's also the reason why I'm trying to recover data through ADB and not through programs like FoneLab and so on that required USB debugging enabled.
I will also accept advices on solutions different from ADB to recover data in these conditions, if they exists.
Thank you
I don't think adb will work for this unless usb debugging is enabled. At least, the device might show up in "adb devices" list, but it would show up as "unauthorized" and you wouldn't be able to pull data off it.
What kind of data are you trying to retrieve? Don't suppose you have cloud backup?
If it's just the screen that's broken maybe you can find a way to mirror the screen onto an external display somehow.
I have tried:
Basic tutorial in Android Developers:
http://developer.android.com/intl/es/tools/device.html
I think the problem is in udev rules, so I tried this:
https://github.com/M0Rf30/android-udev-rules/blob/master/51-android.rules
But I can't get my phone connected in Android Studio.
I'm sorry, the problem was just de configuration on the phone.
I have ennable Developer options. But not USB debugging.
The procedure is fairly simple. But before you dive into the tweaking part, ensure that your phone is set as MTP in USB computer connection.
Open a terminal window and type,
lsusb
Find your device in the output and note down the ID. Let's assume, it is 22b8:2e76. The first part(22b8) is the vendor ID the last part is the product ID(2e76).
Now open up the corresponding mtp udev rules file by typing the following into terminal,
sudo gedit /lib/udev/rules.d/69-libmtp.rules
You'll see there are many smartphones listed there. Search for your phone's product ID. Here in this case, it should be 2e76 . If you can't find it, it means you have to create a custom entry by following the pattern below.
#Motorola Moto G (MTP+?)
ATTR{idVendor}=="22b8", ATTR{idProduct}=="2e76", SYMLINK+="libmtp-%k", MODE="660", GROUP="audio", ENV{ID_MTP_DEVICE}="1", ENV{ID_MEDIA_PLAYER}="1"
Copy the above code and paste it after the last Motorola phone enlisted in that file. Simply search with the word 'Motorola' and you'll find all of the Motorola devices. In my case, the last device was Motorola XT890/90. So, I've added the above code right after Motorola XT890/907's code.
Save & close the editor. Reboot computer and plug the phone to computer again. It should be mounted as mass storage device and work in Android Studio now.
Hope it helps.
I want to test my applications on LG P500 device. But emulator is not detecting the device. When i try to add USB driver which is there in SDK, it is not accepting . Please tel me how to configure Device for testing.
I struggled long and hard to get the correct USB driver installed for my P500. I ended up installing a few different things, and over the course of two or three reboots I managed to get it going.
I'm pretty sure the actual setup details you need can be found here (Note, this is the New Zealand section of the LG website - which is where I am, but it should work globally).
If you follow that, you should be able to install the USB driver. Once done, go to SETTINGS-APPLICATIONS-DEVELOPMENT on the phone and turn on USB Debugging and Stay Awake - these help when you are using the phone to test code.
You can test that its actually working by going into the Android SDK folder shown below and typing adb devices (in the directory shown, remove the (x86) if you are using 32-bit windows) - mine shows up as follows:
c:\Program Files(x86)\Android\android-sdk-windows\platform-tools\adb devices
List of devices attached
80A354043044674101 device
I hope that helps - let me know if you are still having problems.
Change your phone settings to allow USB Debugging. Home->Settings->Applications->Development->USB Debugging. Then connect your phone and run ddms to see if your phone shows up.The emulator will not show your phone, but it should be recognized in DDMS
If some one trying to work on LG P500, Please follow the steps.
1> Connect your Phone to system.
2> Enable settings>SD Card & phone Storage > Mass storage only.
3> Now it will open the SD card. Go to PC suit dir, Install the application whc in turn contain USB drivers. After installation has completed desable mass storage only.
4> Change your phone settings to allow USB Debugging. Home->Settings->Applications->Development->USB Debugging as Apesa ans Steve suggested
(Even i hve installed LGUSBModemDriver_Eng_WHQL_Ver_4.9.4_All.exe )Please let me knw wht exactly this driver will do . )
adb devices was working fine last year, but after upgrades and new software installs,
adb devices no longer recognizes USB attached Android devices.
Here is what I have tried:
adb kill-server
adb devices
adb usb
error: Device not found
If you have installed EasyTether on OS X, the EasyTetherUSBEthernet.kext can prevent adb from communicating with your mobile device.
If you use Easy Tether, BEFORE you plug in your phone run:
sudo kextunload /System/Library/Extensions/EasyTetherUSBEthernet.kext
(or unplug/plug your phone in after)
If you are done debugging and want to use EasyTether again, either restart or:
sudo kextload /System/Library/Extensions/EasyTetherUSBEthernet.kext
If you want to remove the EasyTether kext so it never hassels you again:
sudo kextunload /System/Library/Extensions/EasyTetherUSBEthernet.kext
sudo rm -rf /System/Library/Extensions/EasyTetherUSBEthernet.kext
Reference/Credit: http://www.intohand.com/post.php?s=2011-02-17-android-debug-bridge-not-just-working-on-mac
Having just connected a brand new Motorola Atrix 2 to my Mac running 10.6.8, I had to pull down the menu from the top of the screen, tap on "USB Connection", and change it from "Motorola Phone Portal" to "Charge Only" before it would show up in my list of devices from adb. Hope this helps!
Following the google bug submission... I set usb mode to Charge Only, and it detected the phone immediately. Pretty silly.
Another alternative: on modern Apple iMac's, the USB port closest to the outside edge of the machine never works with ADB, whereas all others work fine. I've seen this on two different iMacs, possibly those are USB 1.0 ports (or something equally stupid) - or it's a general manufacturing defect.
Plugging USB cables (new, old, high quality or cheap) into all other USB ports works fine, but plugging into that one fails ADB
NB: plugging into that port works for file-transfer, etc - it's only ADB that breaks.
If none of the above works for you just as it didn't for me, just try using a different cable. The cable I was using was my friend's cable but it was only meant to charge over USB, not to pass data over USB. I don't know how to tell the difference between micro USB cables that do or don't support data over USB but it's worth a try! Good luck!
I too am having this problem. However, it isn't just a problem with ADB, it's a problem with android devices in general on Mac OSX 10.6.6 Snow Leopard. Devices that used to work in 10.6.4 will no longer even mount the device as a USB drive. Googling to see if I can find the answers.
Change the USB connection type to 'Charge Only'. That was the only change I made it showed up on my device list. Weird.;)
I have seen another report of this bug. I have not been able to reproduce it myself yet.
The bug is:
MacOS X 10.6.6 [on some hardware] breaks adb [for some phones].
If anyone is able to reproduce the bug, feel free to add details of the exact hardware, build numbers and so on. I've asked the person who can reproduce the bug, to report it to google using the form at http://code.google.com/p/android/issues/entry
When he does that, I will add the bug report URL here, and people can add their hw/sw details to the bug report.
In the meantime, to be safe, I would recommend Apple users should NOT accept the snow leopard upgrade to 10.6.6, which was pushed on Jan 6 2011 (so it may already be too late for most).
Peter
I was having the same issue and tried connecting as charge only, but that didn't solve the problem, then unchecked the "Unknown sources" option to allow installation of non-market applications, tried it again and it recognized the device. I'm running android 2.2.3.
The bug report to Google is
http://code.google.com/p/android/issues/detail?id=15583
If you have encountered this bug (upgrade to MacOS 10.6.6 and adb no longer sees some phones on USB) please add a comment with any useful relevant info (like your exact hardware type).
I just ran into this problem using my HTC Inspire (Android 2.3.3) and Mac OS 10.6.8. The phone did not enter USB debugging mode when I connected it to my USB hub, but it did start USB debugging mode when I connected it directly to my MacBook Pro.
... and then, of course, it showed up in the list of devices attached.
The EasyTether fix worked for me, although first I had to load the kext file, then unload it. My Droidx popped up right away!
By the way, I'm running Snow Leopard 10.6.8 on my MacBookPro, so those who are having trouble with adb and connecting devices should check any USB applications, like EasyTether, for conflicts. Also be sure to follow all the above rules for
1. Application debugging (Settings->Applications->Development)
USB debugging: ON
2. USB connection (on notification bar).
Choose USB Mass Storage (altho Charge Only also works with my droidx and MacBookPro)
3. Unknown Sources (Settings->Applications->Unknown Sources = ON)
I have the same problem, I solved using an alternate install method.
First I put an sd card in my device.
Then I use a File Manager to transfer the .apk to the device, and I install it from the device
You can see a tutorial in
http://www.youtube.com/watch?v=7UOAw124y1s
I had this problem today with my HTC mytouch phone and OS 10.6.8. At the same time, the phone reported a damaged SD card. The solution was to remove the Micro SD card and erase/format it using disk utility as FAT 32. The name I gave the SD card volume appeared in the Finder when I tried connecting again (charge only). For some reason, Android reported the card as damaged but could not format it. I used a Micro SD USB adapter. My Macbook didn't see the card until I carefully slid it out and back into the adapter slot. This is a known problem with HTC android phones.
The last time I updated my tablet, it turned off "allow USB debugging", and I spent a half hour or so spinning my wheels. Double check that that is turned on in settings.
This thread is old but perhaps my answer will help somebody. Using a Motorola MB865 with OSX, ADB would recognize my phone only after I performed a factory reset.
I got the idea from this thread.
This was after I tried all the other tricks listed in other threads:
adb kill-server followed by adb start-server
Make sure USB Debugging is enabled
Make sure vendor USB ID listed in adb_usb.ini
Switching USB cables. For what it's worth, I did have to switch cables in order for the Mac to see the device. But this had no effect on ADB.
In the end, the factory reset did the trick.
in my case what worked:
disconnect device
exit android studio
run 'Activity Monitor' and kill adb
start android
studio reconnect device
For some devices running Android 4.4.2, you must enable tethering. You can do this in "Tethering and Mobile hotspot" and then check "USB tethering".
Try restarting the Mac in "Safe Mode". It worked for me (macos X.9.5)
Make sure that USB Debugging is enabled in Settings -> Application -> Developemnt, and also that the selected USB method is PTP and not MTP (not supported in OSX).
After connecting the device and enabling the USB debugging please go to the path of adb, which is now inside the android-sdk-->platform-tools and type the following command ./adb devices. I think this will list the devices connected.
How do I install the app that I'm making on an actual device?
I'm on Mac Snow Leopard with a Nexus One phone and I've followed the steps here https://developer.android.com/studio/run/device.html
So I added:
1. android:debuggable="true"
2. Turn on "USB Debugging" on your device.
However, when I go to the terminal and do "adb devices" only the emulator shows up there.
I'm supposed to see my device name too right?
What am I missing?
The device didn't show up because of the cable.
Although the old cable was charging the phone, but for some reason it wasn't mounting the device and being new to Android, I just wasn't sure what I'm supposed to see and expect.
In case anyone is interested, there should be a "USB connected" notification if the mounting works.
(this is from menu > notification)
I'm supposed to see my device name too right?
Yes, you should see your device name right there.
What am I missing?
This is weird. Is the Android phone at least recognized by the OS, as being plugged into the USB port?
(Sorry this won't help much...)
There is a App on the marketplace I use called App Installer, I just upload the apk file to my sd card then run app installer on it.
My solution is simple, I email the apk file and then install it.