Database Users

ubuntu abd

What exactly do I need to use adb in ubuntu 10.4
I cannot get anything to work and I'm not too familiar with linux.
I have the sdk downloaded and my terminal opened up to my tools directory, but I literally cannot figure out what I'm doing, no commands work and I can't even find my device (adb devices)
I have exclusively used windows for adb on my previous two phones, but I'm using ubuntu more and more so I would like to be able to use adb in it.

Easy.
cd /path/to/sdk/tools
./adb

ADB doesn't recognize my incredible in 10.4 when I do ./adb devices it is blank.

I've tried with the phone set to charge only and to disk drive.
I've tried following this:
a couple of topics concerning a rules file in /etc/udev/rules.d
I greated a 51-android.rules file and it looks like this now:
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0bb4", ATTRS{idProduct} =="0ff9", MODE="0600", OWNER="mbambic"
I've restarted udev a few times and killed the adb server and done ./adb devices to restart it, no luck.

Do you guys have USB Debugging enabled?
Applications -> Development -> USB Debugging. MUST be checked.

x.v_ said:
Do you guys have USB Debugging enabled?
Applications -> Development -> USB Debugging. MUST be checked.
Click to expand...
Click to collapse
yes, I've used adb numerous times on windows

http://developer.android.com/guide/developing/device.html
I'm no expert, but this is what I followed and my phone shows up in adb devices.

OK, that was my bad with debugging not on.
Now I'm getting the following:
#./adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
???????????? no permissions
I've tried with and without the rules file I created in /etc/udev/rules.d called 51-android.ruleswith the following entries that has been chmod a+rx
version 1
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
or version 2
UBSYSTEMS=="usb", ATTRS{idVendor}=="0bb4", ATTRS{idProduct} =="0c9e", MODE="0600", OWNER="myusername"
or version 3
SUBSYSTEM=="usb_device", SYSFS{idVendor}=="0bb4", MODE="0666"
based on this info:
$ lsusb
Bus 001 Device 022: ID 0bb4:0c9e High Tech Computer Corp.

Got it:
edited the rules file:
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0bb4", SYMLINK+="android_adb", ATTRS{idProduct} =="0c9e", MODE="0666"
Rebooted phone
Turned on disk drive
restarted udev
killed adb and started again

I keep getting no command 'adb' found when I try to type any command

I keep getting no command 'adb' found when I try to type any command
Click to expand...
Click to collapse
Assuming you downloaded the sdk pack, your problem is that adb isn't in your path. Take a look at h t t p://developer.android.com/sdk/installing.html. To just temporarily add it, at the shell prompt enter:
Code:
export PATH=${PATH}:<your_sdk_dir>/tools
Also, you may have permission problems when running adb. The easiest way around this is to run adb as root, i.e.: sudo adb (but you'll also have to add adb to root's path then).

mtxpert said:
Got it:
edited the rules file:
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0bb4", SYMLINK+="android_adb", ATTRS{idProduct} =="0c9e", MODE="0666"
Rebooted phone
Turned on disk drive
restarted udev
killed adb and started again
Click to expand...
Click to collapse
Ok, so you used both lines in your 51-android.rules file? Interesting, so you're making the driver specific to the DI? I've been operating with just the first line, which allows to use the DI and the G1, but then again, I've also been unsuccessful at rooting
br125 said:
I keep getting no command 'adb' found when I try to type any command
Click to expand...
Click to collapse
In Linux Mint 9 x64 Isadora (much the same as Ubuntu 10.04 Lucid Lynx), I added the path command to my bashrc file in ~/user. Not sure how to make it global (prob would go somewhere in the mysterious&powerful /etc), but I'm the only user on my system, so for my purposes that doesn't matter

[Q] ADB troubles on Kubuntu Natty

If this is the wrong forum, please feel free to move my post. I figured the devs here might be the best source of information to start with.
My laptop is running Kubuntu 11.04 and fully updated. I've followed all the various (and somewhat inconsistent) posts on the web about getting ADB to run on USB connections under Linux. I am successful getting ADB to see my G2 phone, but not my Nook Color.
Here's my /etc/udev/rules.d/51-android.rules:
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="2080", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", MODE="0666"
The permissions are set correctly, at 644. I've tried both ATTR and ATTRS; it doesn't seem to matter which.
Some, but not all, posts about getting ADB to work also indicated the requirement of another file, .android/adb_usb.ini. The presence or absence of this file seems to have no effect. Regardles, here's mine:
Code:
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0bb4
2080
No matter what I attempt (even including reboots, thinking that restarting udev wasn't sufficient), ADB sees only my G2 and never my Nook:
Code:
List of devices attached
SH0C7R200734 device
Despite the fact that my Nook otherwise works fine on my Kubuntu box; lsusb sees it:
Code:
Bus 001 Device 008: ID 2080:0002
And I can mount its drives and Calibre is also very happy with it.
I'm running ManualNooter 4.6.16 with Dalingrin's 063011 Froyo EMMC kernel. In Nook Color Tools, USB debugging is enabled and auto mount is disabled.
I'm stuck at what to try next. Any thoughts?

ICS and mint 11 64 problem seeing with ADB

i'm having a problem on my mint install, i cant see my Nexus S and i know its rooted, i can allow permissions on Superuser, however, i get this error when i'm trying to see devices
oICS 1.3 is what i'm using
USB Debugging is enabled
Code:
List of devices attached
???????????? no permissions
lsusb sees it fine
Bus 001 Device 078: ID 04e8:6860 Samsung Electronics Co., Ltd
i added the line into 51-android.rules
SUBSYSTEM=="usb", SYSFS{idVendor}=="18d1", MODE="0666"
and restarted udev and i still get ???????????? i have a rooted galaxy that works fine on this pc with ADB.
i even tried re installing SU under recovery. can anyone give me a hand? what am i missing?

Try the following:
Code:
sudo adb kill-server
sudo adb start-server
sudo adb devices

I had the same issue. I tried the kill and restart server and it did not work.
Sent from my Nexus S using xda premium

gangaskan said:
i'm having a problem on my mint install, i cant see my Nexus S and i know its rooted, i can allow permissions on Superuser, however, i get this error when i'm trying to see devices
oICS 1.3 is what i'm using
USB Debugging is enabled
Code:
List of devices attached
???????????? no permissions
lsusb sees it fine
Bus 001 Device 078: ID 04e8:6860 Samsung Electronics Co., Ltd
i added the line into 51-android.rules
SUBSYSTEM=="usb", SYSFS{idVendor}=="18d1", MODE="0666"
and restarted udev and i still get ???????????? i have a rooted galaxy that works fine on this pc with ADB.
i even tried re installing SU under recovery. can anyone give me a hand? what am i missing?
Click to expand...
Click to collapse
Make sure USB debugging is checked in settings and check the stay awake option too.
adb Kill-server
adb start-server
adb devices
give it a shot.

[Q] How can i connect adb drivers and ics 3.1 on xp?

Hi, do you know? How can i connect adb drivers and ideos x5 on xp?
I did try some drivers but in device manager, in other device "android" but all drivers not runing. I want to runing on sdk and sent log dzo.
thanks for helps,

miskiab said:
Hi, do you know? How can i connect adb drivers and ideos x5 on xp?
I did try some drivers but in device manager, in other device "android" but all drivers not runing. I want to runing on sdk and sent log dzo.
thanks for helps,
Click to expand...
Click to collapse
you have to use the adb drivers for ics, now I have the link here. But you can report an error like this:
(1) Open the Terminal Emulator
Write to SU and Enter.
(2) Write the following commands:
cat /proc/kmsg > /sdcard/dmesg.log
logcat > /sdcard/CAT.log

Aurora ICS ADB drivers: http://forum.xda-developers.com/showthread.php?t=1566393

I just it but not solved this problem
asm19 said:
Aurora ICS ADB drivers: http://forum.xda-developers.com/showthread.php?t=1566393
Click to expand...
Click to collapse
hi, thanks for answered my question. But i just tried:
AndroidDriverForPc
Adb Device for AURORA
Huawei_U8800_ICS_ADB_Driver
usb_dirver4
Universal_Naked_Driver_Beta_0.6.2
and orjinal huawei drivers with hisuite.

How can i did it?
asm19 said:
you have to use the adb drivers for ics, now I have the link here. But you can report an error like this:
(1) Open the Terminal Emulator
Write to SU and Enter.
(2) Write the following commands:
cat /proc/kmsg > /sdcard/dmesg.log
logcat > /sdcard/CAT.log
Click to expand...
Click to collapse
edit// "you have to use the adb drivers for ics" I don't have adb drivers. Just i wanting it.
I think this commands for linux, right? Can i it any linux version?
i using this commands what will happen? ( i want learn)
thanks.

any idea?
Is there no one with a different suggestion?

Please give a try to this solution.

m!xal!s said:
Please give a try to this solution.
Click to expand...
Click to collapse
Yes, its ok, adb driver seen by xp but when i can adb shell;
* deamon not runing. starting it now *
* deamon started successfully *
error: device not found
writing, what can i for it?

strange problem!!
device not found

[TUTORIAL] How to Manually ROOT your RK3066 Device (UG007, iMitio MX1/2, mk808?)

These are instructions for rooting Android devices that utilize the RK3066 chipset (Cortex A9 Dual Core, MALI Quad-Core GFX).
I have tested and verified that these instructions work for the UG007 Android-on-a-stick...they *should* work with any other devices that utilize the same USB chipset. I can almost guarantee this will work on the Imito MX1/2 as you can swap ROMS from this device.
(Basically, if you have the right ADB drivers, you should be good to go)
As per every other thread you read on this site - I TAKE NO RESPONSIBILITY FOR ANY DAMAGES YOU MAY CAUSE TO YOUR DEVICE.
This is a fairly risk-free mod, but you know...$hit happens.
Okay. Let's start.
THIS TUTORIAL ASSUMES YOU HAVE ADB AND KNOW HOW TO USE IT, and that you're in a Windows environment. There are numerous places on the web where you can find this info...and I ain't yo mamma.
1. Download all the files attached to this thread.
2. Attach your RK3066 device to your computer via it's microUSB port. You'll need to have it hooked to a display too.
3. Once booted, go to system settings. Under settings > developer options, enable USB Debugging. Under settings > USB, click "connect to computer" (This may vary depending on your ROM configuration. The point here is to have debugging enabled and your computer to recognize the stick in device manager as something other than USB storage)
4. Extract the right drivers for your system (x86/x64)
5. Go to device manager on your computer. Look for the new "unknown device". Right-click, pick "update driver software"., "browse my computer".
6. Browse to wherever you extracted the drivers in step 4. Click Next. Confirm that you want to install.
7. Open a command window in the directory where you have ADB. Type "adb devices". Still nothing, right?
8. Navigate to C:\users\MYUSERNAME\.android, where "MYUSERNAME" is your User Name. (Duh?)
9. Create a file called adb_usb.ini
10. Open it in a text editor. Add the following string and save (This tells ADB to look for our Vendor ID:
0x2207
11. You should now be able to type "adb devices" at CMD and see your device.
12. Now for the fun. Extract the stuff from "pushme" to the same directory as ADB.
13. Enter the following commands (note: The "$" and "#" symbols do not get keyed in):
Code:
adb push psneuter /data/local/tmp
adb shell
$ cd /data/local/tmp
$ chmod 777 psneuter
$ ./psneuter
14. Psneuter should run and close shell when done. Enter MOAR commands:
Code:
adb kill-server
adb devices
adb shell
15. Take a good look. Is there now a "#" sign? Good. You now have root access. You may continue. If not, then proceed to go yell at me in the comments. If yes, then proceed to enter the last batch of commands to make your newfound privileges permanent:
Code:
mount -o remount,rw -t rfs /dev/block/st19 /system
exit
adb push busybox /system/bin
adb push su /system/bin
adb install Superuser.apk
adb shell
# chmod 4755 /system/bin/busybox
# chmod 4755 /system/bin/su
# mount -o remount,ro -t rfs /dev/block/st19 /system
# exit
adb reboot
After a reboot, download a root app from Play Store to see if it worked! I find Root Checker is boffo for this sort of thing:
https://play.google.com/store/apps/...tcheck&feature=nav_result#?t=W251bGwsMSwyLDNd
THANKS/CREDITS:
Aaron Orquia @ Pocketables.com for the original "universal" root method.
AMJtech's tutorial where I found working ADB drivers and the adb_usb.ini bit to get it recognized.
The guy(s) who make Super1ClickRoot for putting all the necessary files in one easy-to-find spot.

Thanks for this tutorial.
A couple of notes:
Wow !! That's a lot of extra steps for you Windows users. Mac and Linux users start at step 11 (but if you are a Mac or Linux user, you already knew that. )
Linux: If the device still does not show up in Step 11, post, and I can help (Hint: It may not be /just/ the udev stuff.)
Is step 13 necessary? adb remount works on mine. (not sure if I had to adb root first or not) but I can have a root shell via adb without psnueter.
If adb remount succeeds, skip step 14, and continue with the 3rd line of step 15.

Linuxslate said:
Thanks for this tutorial.
A couple of notes:
Wow !! That's a lot of extra steps for you Windows users. Mac and Linux users start at step 11 (but if you are a Mac or Linux user, you already knew that. )
Linux: If the device still does not show up in Step 11, post, and I can help (Hint: It may not be /just/ the udev stuff.)
Is step 13 necessary? adb remount works on mine. (not sure if I had to adb root first or not) but I can have a root shell via adb without psnueter.
If adb remount succeeds, skip step 14, and continue with the 3rd line of step 15.
Click to expand...
Click to collapse
Thanks for the input! Yes, yes, I know windoze makes more work. It's also pretty widespread for folks.
For step 13 - I think it depends on the device. It would be nice for others to weigh in and let me know if it's needed. If not, I can totally remove it.
Also, in the other ROM thread, I made, it's even easier to root - you just grab one of the pre-rooted ROMS and drop it in SD card...the system does the rest. Mind you, this is for the UG007.

Links UG007
If you Bluetooth connection is not working properly, try to install this custom ROM: http://blog.geekbuying.com/index.php/category/android-tv-stick-tv-box/ug007/
How to install CWM-based Recovery: http://androtab.info/clockworkmod/rockchip/
Both worked for me. I was able to connect my BT Keyboard/Mouse Pad combo

./psneuter
Failed to set prot mask (Inappropriate ioctl for device) ??

nice tutorial.. while finding the best way to work my ug007 i stumbled upon this thread via armtvtech.com
currently i only knew this tutorial to root the device, but looking at yours ill give it a try first.
digitalhigh said:
Also, in the other ROM thread, I made, it's even easier to root - you just grab one of the pre-rooted ROMS and drop it in SD card...the system does the rest. Mind you, this is for the UG007.
Click to expand...
Click to collapse
you cant install custom roms without flashmode, cant do flashmode without opening device.. or did i get it wrong!? talking about the ug007
actually you can install a custom rom once you are rooted without opening the device, here
Linuxslate said:
(Hint: It may not be /just/ the udev stuff.)
Click to expand...
Click to collapse
ehm.. im still preparing to root, i guess you hint at the android sdk?
if not ill holla back at you and complain why you didnt write it out in first place
but very good to know that i skip alot by "almost" only installing ubuntu to a vm

I may be missing something, but I couldn't get this to work on my UG007
psneuter didn't work for me, gave me an error about 'invalid ioctl' or something. But the strangest thing is that "adb shell" already shows the # in the prompt.
To confirm my suspitions, I also typed "adb root", which returned "adb is already running as root".
So I proceeded with the rest of the instructions. No errors appeared, installed Superuser and I can see su and busybox in system/bin
But when I download root checker it says it wasn't properly rooted. installing terminal and type "su" says permission denied - and that's it.
Am I missing something? I'm new to this rooting thing, so please don't be angry with my noobish questions

I managed to do it - but *not* by following this tutorial.
I used this: armtvtech.com/armtvtechforum/viewtopic.php?t=28 (Cant post links yet, sorry!)
Only ran the "TPSarky-VonDroid-Root" bat, and presto! I had root on UG007.
I even fixed the changing MAC address problem with wlan.ko from armtvtech.com/armtvtechforum/viewtopic.php?f=69&t=632&start=10 (link on page 2). I just copied it to /data/local/tmp, set permissions as rwr--r-- and then used root explorer to copy it to /system/lib/modules - now I have wifi signal every time I boot the device, and don't need to mess with my router config every time
I also manage to get xbox360 wired controller working. xpad.ko on /data/local/tmp and then insmod /data/local/tmp/xpad.ko - just connect the joystick after that, and it will be recognized. Only problem is, after a reboot I have to insmod again.
I tried doing the same thing I did with wlan.ko, but nothing happens - system won't load it on boot. Am I missing something here?

The psneuter is broken
I'm on Linux, running a RK3066, and psneuter gives "Failed to set prot mask (Inappropriate ioctl for device)". Running Ice Cream Sandwich 4.1.1, kernel 3.0.8+, build RK30_anpei10w1am-r4.0.57.20121207, A10-2 cpu.

SLotman said:
I may be missing something, but I couldn't get this to work on my UG007
psneuter didn't work for me, gave me an error about 'invalid ioctl' or something. But the strangest thing is that "adb shell" already shows the # in the prompt.
To confirm my suspitions, I also typed "adb root", which returned "adb is already running as root".
So I proceeded with the rest of the instructions. No errors appeared, installed Superuser and I can see su and busybox in system/bin
But when I download root checker it says it wasn't properly rooted. installing terminal and type "su" says permission denied - and that's it.
Am I missing something? I'm new to this rooting thing, so please don't be angry with my noobish questions
Click to expand...
Click to collapse
Try renaming old "su".
Check permissions on the su and busybox you installed.

MK808, MK809 [model T002], and the MK802 III anyone?
Hi,
Thanks OP for this information.
I have a Samsung S3 [my first android device] which I rooted with no problem, but am a total noob when it comes to these android sticks.
One can say they are very similar, so I wont be completely in the dark. OK, now that we got that out of the way...
Can anyone please confirm whether they have used this with the MK808, MK809 [model T002], and the MK802 III,
I have ordered these from 1 from amazon and 2 from ebay and am expecting delivery shortly, therefore I just want to make sure before I go bricking them one by one...
I notice that they all have RK3066 Cortex A9 chips but are manufactured by different companies. The ones I see on eBay, although they all bear the same code MK8xx, they all look very different! I presume the MK8xx code is a universal model?? just like 80486 was to the PC? given the case does this method work universally?
I intend to set them up with XBMC media centres and to use with a Xbox controller. Any advice on the best way for achieving this would be nice too.
Thanks
:good:

Linuxslate said:
Thanks for this tutorial.
Linux: If the device still does not show up in Step 11, post, and I can help (Hint: It may not be /just/ the udev stuff.)
Click to expand...
Click to collapse
Linuxslate, I have an MK808 that shows up in lsusb as 2207:300a when I put it in "flash mode" but it never shows up via "adb devices".

I got mine the other day and it turned out to be rooted already?
I decided to install SuperSu and that's how I found out it was rooted.
Immediately, installed Busybox, System Tuner Pro and Titanium Backup.
Rob
Rob sent this from his SPH-D710 via Tapatalk

So would this possibly work on this - http://www.zoostorm.com/Products/357-zoostorm-sl8-3305-1030-tablet-pc.aspx
States it's a Rockchip RK3066 Cortex A9 Dual Core 1.5GHz, running 4.1.1 Jelly Bean, quite interested in getting one & root would be a bonus.

psneuter broken
Hello,
the psneuter attached to the first post doesn't do anything to my ug007. I have the same error others have posted here and haven't gotten a reply about.
To unlock, I used the script that's mentioned in a post above, TPSarky-VonDroid-Root. If you google that, you'll find a download link amongst the results.

Thank u very much...:thumbup:
................................................................................................

Linuxslate said:
Try renaming old "su".
Check permissions on the su and busybox you installed.
Click to expand...
Click to collapse
Can you elaborate a little bit what you mean by renaming "su"?
I'm having the same issue..
Both su and busybox are having the same permission -rwsr-xr-x.
Sent from my Transformer Prime TF201 using XDA Premium HD app

I configured one of these at work. Upon using the terminal app and typing in su I got the # sign. They seem to come from the factory rooted already.
Sent from my Nexus 4 using xda app-developers app

ageerer84 said:
I configured one of these at work. Upon using the terminal app and typing in su I got the # sign. They seem to come from the factory rooted already.
Click to expand...
Click to collapse
Not exactly: this particular su can be used only from adb console, or at least that how it was on my tablet. So you need to replace it with a Superuser apk's su to get all features of rooted android. You can get one e.g. from FDroid
--
blog

Not sure what u mean by on your tablet. Android devices don't typically come rooted but I was surprised to have root access via terminal emulator on this stick PC. I just took it out of the box and definitely didn't have to go through the adb interface on a computer to flash superuser or what have you. Is this just me or is this a typical experience with this particular device?
Sent from my Nexus 4 using xda app-developers app