I'd like to connect multiple android devices to the same machine and manage them by the adb. Unfortunately some android models show the same development device id to adb. Is there a way to change the development device id?
$ adb devices
List of devices attached
LG_ANDROID_E0OPEN_GB_ device
LG_ANDROID_E0OPEN_GB_ device
Please note that this question is related to 9786928. As I understand it, the OP was misunderstood and the question is still not answered.
Thanks for your help.
Not without altering adb. The adb "server" (i.e. the part that runs on your workstation) just uses the value it gets from the device, which are in turn set by the bootloader. You could in theory modify the adb server to include additional information in the string, such as the USB device number assigned when the device was plugged in (if you're on Linux, run lsusb and imagine the "bus" and "device" values are included in the device ID).
You may also be able to do this by installing a custom ROM.
For the LG E400, there is a firmware update (V10i-JUN-01-2012) available that addresses this issue.
Before update I've seen the same ID like you for all devices, after update the devices have unique ids.
Related
I'd like to change the device ID string which can be seen when I type 'adb devices' at command prompt.
If I type 'adb devices' at command prompot then I can see below msg,
D:\>adb devices
List of devices attached
5A3C000600000001 device
Is there anyone who knows how the device ID(5A3C000600000001) string generated?
And how can I change the device ID string?
If you have root access, you can enter this to a terminal emulator:
> su (to gain superuser access)
> getprop net.hostname (this should display the current network name)
> setprop net.hostname <newhostname>
Disconnect then reconnect from the network to refresh.
I was on a Samsung Galaxy Note on ICS. Worked like a charm...
In android go to Settings > Applications > Development and tap on Device Hostname. You can then change the name and it should show up when attached to adb.
Another solution can be found here: http://forum.xda-developers.com/showthread.php?t=1462320. You will need to get root access and install a terminal client and do some low level hacking to get it fixed.
Another option is to use the Hosts app mentioned in http://www.thriveforums.org/forum/toshiba-thrive-networking/3157-how-do-i-change-device-name.html, though I haven't been able to find the app he is referring to.
Best option I think is just install Cyanogenmod on your devices. It's the most stable custom android rom and has lots of helpful other features that aren't in stock android.
I have several identical development systems (Odroid A) which report the same device code, thereby preventing me from using more than one on the same host PC with adb. Unfortunately there doesn't seem to be a way of changing this from the gingerbread GUI on this platform as previously suggested.
The device serial number (as reported by 'adb devices') appears to be set in the kernel, under arch/arm/plat-s5p/devs.c (look for 'device_serial'). This may be different for your device, I'd suggest a grep through the kernel sources for the device ID that is reported by adb devices. Change the string, rebuild the kernel and flash it on...
Looks to be different on ICS by the way...
You can set persist.usb.serialno property. I checked it on Galaxy S4/S4 mini and it's persistent, but you need root access:
adb shell
su
setprop persist.usb.serialno Phone1_GalaxyS4
exit
adb reboot
Than in adb devices you'll have
C:\Users\amdc2452>adb devices
List of devices attached
Phone1_GalaxyS4 device
I was also facing the same issue.where two device connected were showing same id in adb devices.
I found this link which solved my issue. Just downloaded the adb from the following link and replaced my original adb.
adb got two same serial numbers when connected to two smart phones
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
I've bought a tablet recently. It's a SysTrade's Plug 10.1 (Chinese product of local company). It features a reasonable CPU and quite nice GPU, so I thought it would be great to hardware debug my applications. However, this feature seems not to work on my device...
At beginning I lacked the required vendor id so after a few phone calls to SysTrade I received one. But that code didn't work. So I've written a small app and got all 2-byte numbers which I copy-pasted to /etc/udev/rules.d/51-android.rules. The problem is that adb still can't see my device. What's important my HTC Wildfire is successfully recognized so rules are written well.
I know none who owns this tablet so I don't have a possibility to check whether all Plugs or only mine are affected. Any ideas would be highly appreciated...
PS. I'm developing on Linux (Ubuntu 12.10).
PS2. When I connect the device to PC it shows that hardware debugging is turned on, but adb doesn't see my device.
I've managed to successfully resolve the issue without rooting the device. The only needed action is to manually add an entry for the device vendorid in ~/.android/adb_usb.ini.
Normally it should be generated based on /etc/udev/rules.d/51-android.rules by android update adb command but it seems that this application failed. What's important, vendorid must be given in hex number specific format, which is: 0x(2-BYTE HEX) for example 0x2207.
Try running adb on root.
If that doesn't work you can still try to root your device(This may void warranty) and use app like adbWifi. I'm using the latter for debugging and it works: I can run my apps on my M-tech aTAB7t.
I need an android phone to test my apps with that will work with Eclipse. It has to be low cost, run Gingerbread with modest memory and CPU.
Thinking that any android phone would work I recently purchased a Virgin Mobil Chaser but as it turns out, it cannot be seen by either Eclipse or adb (but device manager does see the phone). Another developer has also had the same identical problem with the Chaser.
I could keep buying phones and see if they work but that could be long and frustrating. I hope to find a "no contract" phone.
Is there any list of phones that work with Eclipse. Does anyone know of any other Virgin Mobil phones that will work?
thanks, Gary
Any android phone should work. And it is not Eclipse you need it to be compatible with. You need ADB drivers for the device so ADT tools can communicate with device. So what you need is to install ADB drivers for your phone and then, once installed, you should be able to see your device once you enable USB debugging on the device. Then ADB should be able to see it (either in Eclipse plugin or via command line adb devices).
EDIT if you are on Windows, then enabling USB Debugging on the device and connecting it to the computer should result in Windows asking for ADB drivers. You may try if "stock" (these available with SDK in <SDK>\extras\google\usb_driver) are suitable. If not, check manufacturer website (for HTC you may need to install HTC Sync) and if this fail, just google for your device name along with "ADB drivers" and you should get something usable shortly.
One correct answer to my question is: the LG Optimus Elite works fine as a test phone. Drivers installed immediately. Also, it's less than $100 with no contract.
I still haven't found anyone who has gotten the PCD Chaser to work.
Gary
I'm trying to connect to my Prestigo PMP3370B using ADB. But the device is not listed in my W7 64bit connected hardware list (only as USB disc). I already checked on device option in developer option on phone. I'm also not mouting it as USB disc.
There is also no specific ADB driver (or I can't find it) to this type of device, but I want at least try to use some generic driver pro this device. Does someone known what is the best approach to do that? How to make the device visible?
Thanks!
I contacted my local Prestigio user support which told me to use default ADB drivers, but it didn't work. They didn't send me any special driver or didn't know about any.
Then I contacted international user support which told me that they didn't provide this ADB driver to users/developers.
I returned this tablet to the seller. The end.