I've searched a lot, but did not find a solution.
When I connect my HTC Kaiser with Android Ion 1.5 on the top to my Linux box (all UDEV settings are as recommended), the adb utility (launched as root) does not recognize it correctly. It shows a set of questionmarks instead of the device name:
Code:
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
???????????? device
adb basic commands (pull/push/install/shell) work, though, but DDMS does not work and I can't debug my application when the device is attached.
Does somebody have a solution?
You need to run the adb server as root. Use su or sudo to run these:
Code:
./adb kill-server
./adb start-server
You can then use adb and ddms as a normal user. If you use fastboot, you may find you need to run that as root as well.
it is root
Super Jamie said:
You need to run the adb server as root. Use su or sudo to run these:
Code:
./adb kill-server
./adb start-server
You can then use adb and ddms as a normal user. If you use fastboot, you may find you need to run that as root as well.
Click to expand...
Click to collapse
Like I mentioned in my question - I do run adb as root.
When it's launched not as root, I can not even do "adb shell" and
"adb devices" shows:
"????????????? Permission denied". So, it is root, I assure.
BTW, on my work Windows 2k3 machine I can use ddms, but
"adb devices" still shows some garbage letters instead of the device name.
Sorry for my English, if my explanation is not clear.
Related
ok well i've been using adb for a while now via windows on our desktop, my laptop however runs ubuntu. but i've run into a problem.....I CAN'T OPEN ADB IN LINUX! using terminal i navigate to the proper location then i initiate adb shell but i get an error saying the command doesn't exist...what am i doing wrong?
tried ./adb ?
if you haven't added ADB to path it won't be recognized as a command, then you'd have to execute it using ./adb
Hi, adb
is located in <android-sdk-folder>/platform-tools folder. You could add it into your $PATH variable in .bashrc . Than it's ready to use from anywhere
First of all, I have the T-Mobile G2 with the Gingerbread OTA update. I am running Ubuntu 11.10 on a netbook. I have tried to follow the instructions for rooting my phone, but I am getting stuck trying to install the Google USB driver in the SDK manager. Any suggestions on how to get past this roadblock?
mrfilbert said:
First of all, I have the T-Mobile G2 with the Gingerbread OTA update. I am running Ubuntu 11.10 on a netbook. I have tried to follow the instructions for rooting my phone, but I am getting stuck trying to install the Google USB driver in the SDK manager. Any suggestions on how to get past this roadblock?
Click to expand...
Click to collapse
no need for usb drivers in linux
you have to be sure that you are su on your pc... (i have fedora)
i think ubunto it´s sudo, isn´t it?
and before you can see your device through adb you have to type "./adb kill-server" and then "./adb start-server"
... then "./adb devices" and so on
Thanks. I tried ./adb devices and it gave me the following:
List of devices attached
???????????? no permissions
???????????? no permissions
Since I do not see a serial number, do I need to re-install something?
mrfilbert said:
Thanks. I tried ./adb devices and it gave me the following:
List of devices attached
???????????? no permissions
???????????? no permissions
Since I do not see a serial number, do I need to re-install something?
Click to expand...
Click to collapse
no that happens because you are not root on your pc...
in fedora i have to do the following to see my device:
su (enter)
then enter password
i get this symbol: # = means i´m root on my pc
then i go to my platform-tools directory (cd whatever)
./adb kill-server
./adb start-server
./adb devices ...now you should see your device
then start the rooting procedure, good luck
Use 'sudo su' in ubuntu to get a root prompt.
otherwise you have to set a 51-android.rules file (instructions here http://developer.android.com/guide/developing/device.html)
-Nipqer
I've been primarily following the instructions available at http://forum.xda-developers.com/showthread.php?t=1443071, however I've run into some basic issues.
When I run BurritoRoot3 (verified off the big red 3 in the app), the app does not give me a "root" option and immediately opens a dialog box requesting me to "run /data/local/tmp/BurritoRoot3.bin --root" through adb to start the process?"
I have the kindle device listing in "adb devices" as "7A7C002600000001 device"
I try to run the command listed and get an error that the bin file does not exist.
"adb reboot" does reboot the device
"adb root" gives me "adbd cannot run as root in production builds"
the one automatic script for mac & 6.2.2 keeps giving me "error: device not found" errors.
-----
Everything I can find to test the computers install of ADB seems to verify that its working correctly and my forum searching + google search skills are failing me: anyone know some forum threads that cover this?
- the app does not give you a root option - it only guides you what to do
- have you followed all steps ?
adb shell chmod 777 /data/local/tmp
adb install BurritoRoot3.apk
<go open the app now>
adb shell /data/local/tmp/BurritoRoot3.bin --root
adb shell /data/local/tmp/BurritoRoot3.bin --install
maybe you have to do the adb commands with ./ in front (eg ./adb whatever)
t4nn3d1n said:
I've been primarily following the instructions available at http://forum.xda-developers.com/showthread.php?t=1443071, however I've run into some basic issues.
When I run BurritoRoot3 (verified off the big red 3 in the app), the app does not give me a "root" option and immediately opens a dialog box requesting me to "run /data/local/tmp/BurritoRoot3.bin --root" through adb to start the process?"
I have the kindle device listing in "adb devices" as "7A7C002600000001 device"
I try to run the command listed and get an error that the bin file does not exist.
"adb reboot" does reboot the device
"adb root" gives me "adbd cannot run as root in production builds"
the one automatic script for mac & 6.2.2 keeps giving me "error: device not found" errors.
-----
Everything I can find to test the computers install of ADB seems to verify that its working correctly and my forum searching + google search skills are failing me: anyone know some forum threads that cover this?
Click to expand...
Click to collapse
You have to make sure that you do this command:
adb shell chmod 777 /data/local/tmp
Otherwise it will not make a "BurritoRoot3.bin" file, which means no root.
Install the BurritoRoot3.apk on your kindle, and go into the app.
After that is finished, input:
adb shell /data/local/tmp/BurritoRoot3.bin --root
Then:
adb shell /data/local/tmp/BurritoRoot3.bin --install
I found http://forum.xda-developers.com/showthread.php?t=1410223 which has that chmod command in it. Naturally I found that thread 10 minutes after I posted and was so dumbstruck with myself that I didn't post a reply to my own post.
The device is rooted now and I installed the Alpha Release of MIUI 4.0.? and naturally a few things don't work. Trying again with MIUI's 2.3 stable release (don't know the version number off the top of my head)
Thanks for the quick reply and looking out
is it possible to use adb from the transformer, to connect to an other adb device? (that would be my phone)
when I connect my phone to the usb port of my tf (on the dock) and then I type adb devices in a shell here is what I get:
[email protected]:/ $ adb devices
* daemon not running. starting it now on port 5038 *
* daemon started successfully *
List of devices attached
[email protected]:/ $
I've done it before. Not sure why it isn't working for you. Double check that debugging is enabled on your phone. You also may need to be root to use adb on the TF. Type "su<enter>" to get root in your terminal, then try adb.
If your TF isn't rooted, then you need to do that first.
never mind, I just needed to adb kill-server after getting root
it works now
Hello, recently I've ran into a stupid problem after unlocking bootloader on my M7. Here is what happened, after unlocking I was not able to use my phone in debugging mode, the authorization pop-up didn't show up wherever I connected my phone to PC in ADB mode. This was not Drivers fault I just lost RSA Key, I managed to get it back, I hope it will help you also.
To get RSA keys you need to do next thing.The trick is to create the .android directory elsewhere, for example on the SD Card:
You need Android Terminal Emulator and Root for this operation. ( Link to Android Terminal Emulator: https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=en )
Open Android Terminal Emulator and write:
adb kill-server
HOME=/sdcard adb start-server
At this point you should have /sdcard/.android and the 2 keys in it.
Then just copy adbkey from your phone to your computer into C:/Users/YOURNAME/.android then write in terminal.
stop adbd
start adbd
Then connect you phone in ADB mode Wifi or USB and check again:
adb kill-server
adb start-server
adb devices
Now authorization prompt should pop up!
This issue is also known as Unauthorized device in ADB mode.
Good luck!