This is hands-down the most esoteric question I've ever posed on this site, but here goes:
Following the instructions on Cyanogen Mod's site I was able to make it as far as flashing the linked recovery image.
However, now that I've done that, Ubuntu no longer recognizes or mounts the device, so I can't proceed to the next step.
I'm at a loss as to what to do at this point, so any advice would be appreciated.
Add your device's vendorId to home/.android/adb_usb.ini file and then restart the adb server. If that doesn't works, please reboot your system and connect your device to a different port and check. Hope it solves your problem.
Related
I'm trying to get my phone to connect with Eclipse so I can run android apps without using an emulator. I've already gotten this to work and made an app, but I got a new hard drive since then. Every time I try to reinstall it on the new hard drive, it says that it doesn't install properly. I've tried using 2 different usb cords, rebooting every time I try it and installing/uninstalling the USB driver from the Motorola website to no avail, and I can't remember exactly how I did it before.
Can anyone help?
Make sure your usb debugging turned on and use this free software to install the driver :
http://adbdriver.com/
Android's development page doesn't explain this one in full detail. I had problems with it myself. Although my situation wasn't exactly like yours, installing the usb driver from the SDK made it work.
Follow this guide!
Has anyone tried developing application using Lenovo K900, I am writing application for my phone (Android 4.2.2) but its not getting detected by eclipse.
Please help
I found a couple of drivers and the combination seems to do the trick.
I installed the drivers from this post to see the device as a CloverViewPlus device
https://forum.lowyat.net/topic/2918390/+940# (Post #943)
The IntelAndroidDrvSetup1.2.0.exe and iSocUSB-Driver-Setup-1.0.2.exe were needed.
Then I installed the drivers from this post to get Eclipse to recognize the device:
http://singledrivers.blogspot.com/2013/12/lenovo-k900-usb-driver-for-windows.html
It seems that you do not need the MTK driver.
You do seem to need the PDANet Driver.
The ADB driver did not seem to hurt either.
Now Eclipse can see my K900 and download code to it.
Only enabling USB Debugging will not help solve your issue.
You need to install certain drivers in order to make your cell phone visible while running the application.
For now, even I am searching the perfect drivers to install in my system. Will get back to you once I have them. Also, I request you to search as well and revert in case you find success in the same.
I just installed android sdk. And trying to follow these steps to detect my device. Because my phone was disconnected & dead during an unfortunate/accidental/unwelcome software upgrade.
It's frozen on Samsung start up screen. I was able to use volume + power + home buttons to get into another black screen with now send the package you want to apply to the device with adb sideload <file name>. But not sure how to sideload from adb when I can't even detect my device. All I want is to retrieve my data & start up my device as normal.
Within the Command Prompt under platform tools, I typed adb devices. But no device listed. I am currently installing the Samsung Galaxy Note MTB device driver.
Can someone please guide me to the correct steps? There has to be a way to retrieve the data from the internal memory right?
Edit 1:
According to this article, I am not sure if my phone is bricked or trap in a bootloop...First of all, lets get something straight. Most people use the term "bricked" improperly. A bricked phone means one thing: your phone won't turn on in any way, shape or form, and there's nothing you can do to fix it. It is, for all intents and purposes, as useful as a brick. A phone stuck in a boot loop is not bricked, nor is a phone that boots straight into recovery mode. These are things you can usually fix, and they're a lot more common than a truly bricked phone. If your phone is actually bricked, you won't be able to fix it yourself (but there are things you can do—see the end of this article)
Edit 2:
PC specs : Win Vista, 32-bit
After installing MTP drivers I am at this point. However within adb devices command I only see <aserial number> recovery. It doesn't say <serial number> device
Do I still have a hope to get to my data?
Your phone may be stuck in a BootLoop It wont get detected using adb try using FastBoot if not you should contact your samsung service center to reload software . Your data is lost in this case.
UPDATE
try downloading sp flash tool check your phone is detected if so you can have some hope in data recovery
Any ideas where I can begin to find out what's going wrong?
I have a T-Mobile Pulse Mini (Huawei) which I'd like to get working for developing and testing apps on. I can't get it to be seen by Android Debug Bridge despite restarting the adb server. (and emulators are seen by adb any way so that's unlikely to be the problem).
In the device manager the phone is displayed as a CD-ROM and when I select 'transfer files' from the auto 'PcOptions.exe' it is then displayed as a USB driver but in either case I can't see it in adb. I have enabled debugging on the phone. I remember it took me ages to get it to work on my previous Vista 32-bit. I can't figure out where to search from here. The drivers used to install the phone are on the phone itself.
Thanks very much.
Drivers. If you can't see the phone in ADB, it's almost always a driver issue and this is especially common on Windows. The regular user drivers are sometimes different from the ADB drivers. If you can find the OEM dev drivers directly that's ideal, otherwise there's a way to modify the INF file which you'll have to Google for unless someone else provides it, as I don't remember the details at the moment.
I have installed the latest Motorola USB drivers which include support for the Triumph.
When I plug in my phone, "adb devices" does not list my phone.
My device manager shows my device under Phone as well as Disk Drive. Both use the WPD FileSystem Volume Driver and refuse to let me update the driver by pointing the motorola drivers in Program Files. It continues to tell me that "Windows has determined the driver software for your device is up to date."
Any ideas?
I am currently in just about the exact same predicament =/
I have some possible avenues that we could both share:
Idk if you were able to find a phone number for Motorola (American that is) but i finally found one
Motorola Mobility, Inc.
600 North U.S. Highway 45
Libertyville, Illinois 60048 USA
Telephone: +1 847 523 5000
Here is a link to yet ANOTHER programmer having the same prob as us =/, but he got it figured out using the steps he posted there
Also there is live support chat here.
If you find a solution to this problem, please, please, please let me know =) And i will do the same for you if i get it figured out soon.
Edit:
Nevermind, i got mine to work just fine =)
Heres what i did:
Used USBDeview to uninstall all previously failed attempts at drivers lol
NOTE: You will have to run USBDeview as an Administrator(right click, select Run as administrator)
In the device manager, after uninstalling all the others, right click on what pops up for the device, click update driver, browse for your own, than from there it was a series of selecting from lists, but the key thing here is to remember that eclipse debugs programs on external devices using the adb interface, which should be a pre loaded option in said select lists =)
Hope this helps!!!
Have you enabled debug mode for your phone? This can be done via settings->application settings->development->USB debugging
Whenever I've had a problem with adb recognizing my devices I've managed to fix it by adding a reference to it in my .android/adb_usb.ini file.
I only run Linux/OS X at home and I don't want to try and blindly describe how to do it on Windows from memory, but they discuss it here http://android.modaco.com/topic/294799-adb-windows-7-and-the-pulse-tutorial/
And google gives the USB Vendor ID's here http://developer.android.com/guide/developing/device.html .
On my linux box I added:
0x0489
To my adb_usb.ini (using the Foxconn ID which on linux you can find directly via lsusb, I think you could use devcon on Windows to find it) and it shows up on my device list.
Just because this link hasn't been dropped in any answers (and I always find myself looking for it), here are the manufacturer's development drivers.
This is what worked for me. I have a Moto Triumph and Win7 x64...
Turn on Unknown Sources, USB Debugging
Install Motorola USB development driver. Unfortunately, Motorola broke the old driver URL, as well as many development forum URL's. Fortunately, Softpedia has copies of the installer. Grab the 32 bit or 64 bit version depending on your OS.
Plug in your phone by USB
Open Device Manager
View hidden devices
Uninstall default drivers (Disk Drives\Qualcomm USB, DVD\CD\Android SCSI CD-ROM, Portable Devices\F:)
Action > scan for hardware changes, or Disconnect/reconnect phone
Repeat till ADB appears (probably w/ a yellow icon indicating it's not fully installed)
Right-click ADB > update driver > browse my computer for driver > pick from a list > Motorola > Android Sooner ADB (the first entry)
Accept security warning
Done. If it worked properly, you can now view your device using adb devices.