Hi all,
I searched quite a lot, but seems to me not nearly enough. I've been using adb on my Windows 7 machine for a while now, but would like to have adb at work on my Ubuntu 11.04 machine where I am going to start some boring development.
I have installed the sdk and eclipse and and and (if it is important WHAT I installed more than this, I will elaborate)
lsusb returns
Code:
Bus 002 Device 009: ID 04e8:689e Samsung Electronics Co., Ltd
so I have set my
/etc/udev/rules.d/51-android.rules
to reflect like this:
Code:
SUBSYSTEM=="usb",ATTRS{idVendor}=="04e8",ATTRS{idProduct}=="689e",SYMLINK+="android_adb",MODE="0666
I'm kinda hoping this is wrong and there is an easy fix that I can laugh about.
When I have the emulator running and my phone plugged in
Code:
$sudo adb devices
returns a blank line and something about an emulator, only emulator running yields no blank line and only phone plugged in yields a nice and quiet blank line.
I had this on Windows as well when I struggled with drivers, but the CD sorted it out. I read that the necessary drivers comes with the SDK, but I might be wrong.
I have tried different tutorials and different values for the idProduct and idVendor as some tutorials claim they should be kept constant and not vary per phone... I restarted adb each time I made a change with
Code:
$sudo adb kill-server; sudo adb start-server; sudo adb devices
I'm currently running FirstUA v1.2 if that changes anything.
If you need more info, don't hesitate to ask, I know it's easier to solve problems with the right info (coming from an IT helpdesk).
Digi.Gram said:
Hi all,
I searched quite a lot, but seems to me not nearly enough. I've been using adb on my Windows 7 machine for a while now, but would like to have adb at work on my Ubuntu 11.04 machine where I am going to start some boring development.
I have installed the sdk and eclipse and and and (if it is important WHAT I installed more than this, I will elaborate)
lsusb returns
Code:
Bus 002 Device 009: ID 04e8:689e Samsung Electronics Co., Ltd
so I have set my
/etc/udev/rules.d/51-android.rules
to reflect like this:
Code:
SUBSYSTEM=="usb",ATTRS{idVendor}=="04e8",ATTRS{idProduct}=="689e",SYMLINK+="android_adb",MODE="0666
I'm kinda hoping this is wrong and there is an easy fix that I can laugh about.
When I have the emulator running and my phone plugged in
Code:
$sudo adb devices
returns a blank line and something about an emulator, only emulator running yields no blank line and only phone plugged in yields a nice and quiet blank line.
I had this on Windows as well when I struggled with drivers, but the CD sorted it out. I read that the necessary drivers comes with the SDK, but I might be wrong.
I have tried different tutorials and different values for the idProduct and idVendor as some tutorials claim they should be kept constant and not vary per phone... I restarted adb each time I made a change with
Code:
$sudo adb kill-server; sudo adb start-server; sudo adb devices
I'm currently running FirstUA v1.2 if that changes anything.
If you need more info, don't hesitate to ask, I know it's easier to solve problems with the right info (coming from an IT helpdesk).
Click to expand...
Click to collapse
The SDK Drivers are not for Galaxy Ace , Google for the drivers , they should be easy to find
Sent from my Ultma Weapon using XDA App
It seems that my problem begins with our Proxy server.... As the SDK manager and I had a quarrel about authentication, I downloaded some of the packages directly and forced the manger to use them instead of those on Google. With this, I accidentally downloaded an outdated adb, which had problems specifically with the Galaxy line of phones.... Downloading the correct package now, will see if it works better
Maybe I must just stop before I think of continuing I installed the newer r06 version, and my device is picked up, but now adb shell gives me this:
Code:
:~$ adb devices
List of devices attached
S58300c017faf device
:~$ adb shell
sh: applet not found
Any ideas where to look for the applet? Maybe I must continue tomorrow, new day new ideas.
Do you have Debugging turned on? And is the device rooted with Busybox? I assume yes since you're running a custom ROM but double checking.
If you're having trouble, I'd either: a) run a VM with XP SP3; b) head to the Android Q&A board here.
mmm, I never though of looking at that, since I figured they do say busybox is installed on this ROM, but thanx for nudging me into that direction, I found this post from ketut.kumajaya so I'm looking into that. Had some issues with not abling to get rw access, but my only problem there was a spelling error in the terminal.
I still get the error with the sh: applet not found, even after I tried the advice on that link. I tried installing all 3 versions shipped with BusyBox Installer on all 3 locations, still nothing. Just had an idea I'll try, if you invoke sh in linux you get a new shell, when I invoke sh I get the applet not found error. Maybe I should upgrade my sh or something. Worth a try
I am running a VM for the VB programming I do at work, but that doesn't have USB support (to much trouble to reinstall Virtual Box now just for USB support). Last night I tested on Windows 7 (first time since I started using this ROM) and it failed with the same error. I'm sure it's the sh that's broken or something. Will test on my wife's phone tonight (running the same ROM).
Thanx for your ideas so far. That's what I love about an online community, even if you don't exactly know what's wrong, people sling ideas around that nudge you in the right direction. One error message at a time
Solved thanx to Ketut
Thanx for all your help guys.
Related
Alrighty, I am new to the linux world and I am trying to setup my beloved adb on my Ubuntu. Java is there, SDK in in /opt/androidsdk. Do I need something more? I read that people install Eclipse also but since I am not a developer I don't need it, do I? I only need to execute very simple adb commands like push.
With Windows I needed the HTC Hero drivers and then it worked like a charm. Do I need something similar here?
I tried to run adb devices while my phone was connected and I get a phone with ?????????? as a name.
Is adb going to work or do I miss something?
Thanks in advance!
Adb works fine on x64 Ubuntu. I know there is a guide for it on www.villainrom.co.uk/wiki, but then search "adb" and it should bring up the entry.
I'm installing Ubuntu again today anyway, so I can check it works (which it does btw)
theodore80 said:
Alrighty, I am new to the linux world and I am trying to setup my beloved adb on my Ubuntu. Java is there, SDK in in /opt/androidsdk. Do I need something more? I read that people install Eclipse also but since I am not a developer I don't need it, do I? I only need to execute very simple adb commands like push.
With Windows I needed the HTC Hero drivers and then it worked like a charm. Do I need something similar here?
I tried to run adb devices while my phone was connected and I get a phone with ?????????? as a name.
Is adb going to work or do I miss something?
Thanks in advance!
Click to expand...
Click to collapse
Try doing this.
sudo adb kill-server
sudo adb root
then do w/e you need to do. This worked for me.
Not sure if you need to sudo kill-server, if it doesnt kill it, try without
ante0 said:
Try doing this.
sudo adb kill-server
sudo adb root
then do w/e you need to do. This worked for me.
Not sure if you need to sudo kill-server, if it doesnt kill it, try without
Click to expand...
Click to collapse
I did this followed by adb devices and I now get the correct device name.
I guess that it works though I didn't try to push any app
Another question: how do I add adb to the path? I currently need to type in the full adb path. It is linux related but I am new into this exciting world!!
Thanks for helping me out!
Google "Ubuntu add to path" and it will tell you
Howdy everyone!
Without further ado, I humbly present my gift to the community (and the #nookcolor irc channel )
This collection of scripts will automagically install:
NookColor USB ADB Drivers
The necessary adb_usb.ini file for adb to recognize the NookColor
A stripped-down copy of the Android SDK, with just the requirements for adb.exe
adb.exe is added to your %PATH% variable.
Tested on Windows 7 32/64, Windows Vista 32, Windows XP SP2/SP3
Now I realize not everyone wants the do-all end-all script, so there's two versions: one that contains the drivers AND a cut down Android SDK, or the version that only installs the ADB driver and the proper adb_usb.ini file.
Instructions for use with combo pack (please read!):
Download the combo pack
With your NookColor unplugged from your PC, run the nookcolor-easyADB.exe file and allow it to extract to c:\
Follow the on-screen instructions and wait until you see "All done!"
Plug in your NookColor, tell Windows not to use Windows Update, and let it search your computer for the proper drivers.
Once the package has finished installing, and the drivers are installed, you can just open a command prompt window and type:
Code:
adb devices
If you see your device's serial number listed, you're good to go!
Instructions for the driver-only pack:
Download the driver-only pack
Extract it somewhere on your PC (may I recommend c:\android-sdk-windows\usb_driver ?)
Run install.exe in the extracted folder and follow the onscreen prompts.
For those of you that would like, the source of the driver installer is contained in both downloads as install.au3. Driver installation is accomplished using dpinst.exe from the Windows Driver Development Kit.
Also, to avoid any confusion, I am also known as IOMonster on IRC.
Okay now for the good stuff...
DOWNLOADS:
Combo Pack (all in one!): http://legacyschool.us.to/nookdev/nookcolor-easyADB.exe
Driver only pack: http://legacyschool.us.to/nookdev/nook-usb-installer.rar
Update: 0.2 version has been released. Should fix CPU architecture errors when installing. I have also changed the download protection on my server, you should be able to use download managers now.. just keep it to a sane number of concurrent downloads by IP.
Troubleshooting:
Make sure you're rooted
Sounds dumb, but trust me, it's happened.
Make sure you haven't used ADBWireless and forgotten to disable it
Guilty here. I spent a good half hour trying to figure out why it didn't work on one of my Nooks until I realized that I had left ADBWireless on.
Check device manager for a "Nook" device, you may just have to do an "update driver" on it
Just like it says, check for any devices labeled "Nook" or "USB Composite Device" with a VID of 2080
Uninstall ALL Nook-related devices in device manager
Check device manager for any USB devices (usually USB Composite Device or USB Mass Storage) with a VID of 2080 and PID of 0002, uninstall 'em and unplug/replug your Nook.
Please note that this is a VERY initial build. It may not work for you under some circumstances, but on the few machines I've tried it on, it seemed to work for me. If you encounter any weird bugs, please let me know- I'd love to know so I can fix it.
(As a side note, I really need to standardize my nomenclature for my driver pack..)
excellent work, thank you
This is awesome! Thanks!
nice job...I had helped test it in the irc channel for ya. I def think this will be great for the community now we just need something to root and and superuser. Anyway good job
First post. Wanted to let you know it worked on my windows7 x64 machine perfectly fine. so much easier than the long way.
I'm using Windows 7 32bit. I unzipped the driver pack, clicked install.exe, then it said something about not having a correct version of windows and to get windows 7 x86 or x64, then a window popped up saying it successfully installed. Assuming that it didn't and using my extreme deduction skills, I opened DPInst.exe and it did it's thing and installed fine. Don't know what happened with install.exe but it works now. Thanks!
Strange... do you remember the exact text of the error?
My install.exe runs DPInst.exe with the /q (quiet) switch, so it shouldn't have even given an error (even if there was a legit error message thrown by DPInst.exe).
Do you think you had install.exe set for compatibility mode? (check the properties for install.exe and possibly DPInst.exe)
Thanks for the feedback! I sure hope this alleviates most of the headaches associated with installing ADB on Windows.
The links are dead, can someone post them somewhere else?
Fault when I install but it installs fine.
It installed fine even though I got this message.
EDIT::::
Ignore me - I missed uninstalling the USB device...
Worked perfectly THANK YOU!
Rylynmila said:
It installed fine even though I got this message.
Click to expand...
Click to collapse
Are you by chance running Windows 7 32-bit?
And as for the links being dead, try disabling your download manager. I see people's download managers trying to do something like 20 concurrent downloads, and my server disallows that.
Rylynmila said:
It installed fine even though I got this message.
Click to expand...
Click to collapse
Hi, I did encounter this similar error as Rylynmila.
BTW, I am running WinXP SP2.
Hm, that's strange.. this worked on my XP SP2 machine, I wonder if it's possible that some machines report the architecture differently..
I'll make a quick script that should let me figure this out easier. It's probably just an error in my script's logic for deciding which version to use.
EDIT: Newly released version has been uploaded. This should fix the CPU architecture problems.
Ah, well, just found the culprit! My AutoIT script checks the architecture of the CPU itself, not the OS you're running.
On the Windows XP machine I tried it on, the CPU itself is only a 32-bit cpu (Athlon XP 3200+), therefore it reported it right.
I should have used @OSArch rather than @CPUArch in AutoIT. Oops.
I'll make an updated version and release it later today.
cant seem to get this working on my 64 bit vista machine.
installed fine, but adb devices shows nothing
DrewLGT said:
cant seem to get this working on my 64 bit vista machine.
installed fine, but adb devices shows nothing
Click to expand...
Click to collapse
When the installer came up, did it give you any errors? Check the device manager- you should have an entry for Android Phone -> Android Composite ADB Device.
If you do have that entry, try running
Code:
adb kill-server
then
adb devices
and see what you get.
thecubed said:
When the installer came up, did it give you any errors? Check the device manager- you should have an entry for Android Phone -> Android Composite ADB Device.
If you do have that entry, try running
Code:
adb kill-server
then
adb devices
and see what you get.
Click to expand...
Click to collapse
my wife is using the NC right now, so i'll give that a try when shes done.
i have another question though. i already had adb installed for my phone, now i have it twice. can i combine the two?
If you just want the ADB driver, just download the driver only pack.
If you had adb installed already, this will overwrite it if it's installed to c:\android-sdk-windows.
no luck with easy adb
I have xp and followed the directions given in the first post in this thread for the combo pack. I now have a lot of files in c:\android-sdk-windows\ but when I follow these directions (from Nook Devs) I do not get the proper output...
"Start > Run > cmd > Enter
* cd\
* cd android-sdk-windows\platform-tools
* adb kill-server
* adb devices
If you get output that looks like the following you have succeeded:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
[YOUR NOOKCOLOR SN] device"
For my output, I get the first three lines but not the
[YOUR NOOKCOLOR SN] device
I looked in Device manager and do not see anything about Android in there. I am obviously an android noob - can anyone help me? Thanks
Can't wait to try this. Thanks!
I consider myself pretty proficient with electronics and computers but I could never get ADB working on my Win7 64 PC no matter which set of instructions I followed. The benefit of this is that I've learned how to use Root Explorer to accomplish a lot of things.
EDIT: This worked perfectly on my PC, although I wasn't prompted to install any drivers. Guessing I had already done so previously trying to get this to work. Thanks much!!
There are some people in this forum that have got success instaling ubuntu on Folio. I've got too.
Now i have a great question !!
Are our folios fully driver installed ??
For example, in my folio with ubuntu, i can't use bluetooth or i can't heard any sound because it doesn't run, or also i can't adjust brightness...
I have searched lot of pages and i haven't got success....
This thread is created for people who knows how install this kind of drivers can help us to make us happy !!
If you discovered how to install any kind of driver... or things for optimize ubuntu and make it more quickly please, post it !!
Also would be insteresting if people got success installing programs on our ARM architecture device like Dropbox, Foxit reader, Wine compatibility layer... that are based on i386 and AMD architectures post a how to do it.
Thanks in advance for all people that make that possible.
Hi,
I am working on sound driver. Just trying to find specs as running android do not give enough informations.
I will also try to integrate accelerated drivers as in AC100 build (but system may be unstable...)
Akta
When I installed Linux on my netbook, I haven't got bluetooth, go to software manager(ubuntu market) and search for bluetooth(drivers). May this help you
I'm working on sound too...
I guess there is an GPIO Chip inside the Folio, which manages sound in-/outputs..
I dont know whether the bluetooth and screen brightness are also part of it...
The GPIO has many inputs and outputs, but these are not fix...
So you have to build/run a program which tells them to be an output or input and what they have to do...
I ported the mach-tegra tree and the sound/soc/tegra tree from android-kernel-source to the folio source..
After that I ran nvrm_daemon in a chroot..
For that you'll have to do the following steps:
1. Create a new folder whereever you want (for me /home/ubuntu/Desktop/chroot)
2. mount /dev/mmcbkl0p1 and copy the bin & lib folders into your directory
3. create a folder called system inside your folder and move the lib folder into it
4. create the folders dev and proc
5. open a shell and cd to your directory
6. $ mount -o bind /dev dev/
7. $ mount -t proc /proc proc/
8. chroot ./ /bin/sh
9. nvrm_daemon
You should better run chroot/nvrm_daemon from a ssh shell on your laptop because sometimes the screen gets black, because of segmentation fault..
Then you can take a look @ dmesg..
There are some outputs given by nvrm_daemon.. Also for GPIO but they failed to change some pins because they are already in use..
And I guess thats the problem!
I also tested whats happening when the nvrm_daemon is not starting when android boots.
I removed it from the ramdisk.
After that the folio wasn't starting anymore...
Only after I started nvrm_daemon manually via adb shell the boot screen appers and the window manager starts..
So everything depends on the nvrm_daemon!
I hope you'll more lucky than me and findout why the nvrm_daemon is not starting correctly!
Regards
Thanks for the info.
Will look at that to begin with
Akta
I there, I have contacted Atheros to know which bluetooth chip is in our folio and they replied me that is 3011 or 3012 depending on the version.
I hope this helps to get bluetooth working early. I will try using ndiswrapper to install windows driver after the biggest brick ever!!!
I found the drivers for the gpu
I've gotten through the forums trimslice computer graphics chip drivers Tegra2
To download them here:
Code:
trimslice.com/download/drivers/nvidia-drivers.18.0004.tar.bz2
These drivers are valid for Debian and Ubuntu Maverick.
However, you must edit xorg.conf to make them work properly with the folio 100.
If someone can correctly configure xorg.conf. I would appreciate it also put him in these forums. Thanks
To install the drivers simply must enter the terminal from ubuntu and type the following commands:
Code:
cd /
sudo tar -jxf nvidia-drivers.18.0004.tar.bz2
jarre2 said:
I've gotten through the forums trimslice computer graphics chip drivers Tegra2
To download them here:
Code:
trimslice.com/download/drivers/nvidia-drivers.18.0004.tar.bz2
These drivers are valid for Debian and Ubuntu Maverick.
However, you must edit xorg.conf to make them work properly with the folio 100.
If someone can correctly configure xorg.conf. I would appreciate it also put him in these forums. Thanks
To install the drivers simply must enter the terminal from ubuntu and type the following commands:
Code:
cd /
sudo tar -jxf nvidia-drivers.18.0004.tar.bz2
Click to expand...
Click to collapse
Hey, I have installed this drivers and now I can't boot ubuntu !! Can you help me ? I send you a mp with my e-mail, we can speak on google talk chat i'm spanish !
thx !!
I had said before, it is necessary to create an xorg.conf file that is compatible with
toshiba screen folio 100.
It is the only way to have graphics acceleration.
Funny how nobody was interested in compiling the kernel with support for
ALSA (and there have been some drivers called tegra) But if you do not work
we can always choose to have sound through USB since.
no news ? aneybody have graphics acceleration ?
up please!!!
please why nobody reply ?
I've tried on windows 7 and Ubuntu 12.10 and no matter what I do,no matter how many times I update the SDK or uninstall and reinstall the SDK,ADB version is still 1.0.29...tried killing server,restarting adb, etc.
Trying to ./extract files from cm10.1 for compiling CM but ADB must be updated to connect to JB devices...
Someone please help!!! I've googled for hours and tried everything..still getting nowhere.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
:SOLVED FOR ME:
so what i did (and i dont know why all of a sudden its working) but,
i opened up the terminal and did the following
lsusb
This should kick out a list of plugged in devices. Most likely the last one is the phone. There were references to Samsung and Galaxy so it was pretty easy to figure out. On that same line, there is an ID number in this format...xxxx:xxxx. Write that number down for reference.
Now a few more commands:
cd
sudo gedit /etc/udev/rules.d/99-android.rules
When the rules open, copy/paste the following with the id "lsusb" gave you:
replace the ####:#### in the above string of text with the number you got from "lsusb"
Then save and exit.
sudo service udev restart
sudo adb devices
# XXXXXXXXXXXX offline
sudo ./extract-files.sh
GOT THE WINDOW POPUP ON MY PHONE
check always accept from this computer
then everything went smoothly....hope this somehow or another helps someone...if it does,please hit thanks.
in Ubuntu, once you update the SDK , copy the adb file in SDK/platform-tools to /usr/bin
reboot Ubuntu and try .
i don't use windows sorry
Sent from my GT-S5670 using xda premium
soham jambhekar said:
in Ubuntu, once you update the SDK , copy the adb file in SDK/platform-tools to /usr/bin
reboot Ubuntu and try .
i don't use windows sorry
Sent from my GT-S5670 using xda premium
Click to expand...
Click to collapse
just tried sudo cp ~/android-sdk-linux/platform-tools/adb /usr/bin
it seemed to have copied since the original adb there was like 577kb and the new one is 1.2mb but still same issue.. i dont care to get it working on windows anyways...just thought i was strange it wont work on either platform...any other suggestions??
just a mention if someone arrives due to google search and are having an issue updating adb version in windows..this thread only speaks of a fix in linux so here is what i found: somehow someway adb.exe along with a couple dll files found their way to my windows directory, even though i always had its installed path included in my systems environment variables!! first i simply renamed these 3 files and added the extension .old to them. immediately running adb version in a command prompt my version finally read properly as it should 1.0.31 and not 1.0.26. its self explanatory why. hope this helps someone!
sinner99 said:
just a mention if someone arrives due to google search and are having an issue updating adb version in windows..this thread only speaks of a fix in linux so here is what i found: somehow someway adb.exe along with a couple dll files found their way to my windows directory, even though i always had its installed path included in my systems environment variables!! first i simply renamed these 3 files and added the extension .old to them. immediately running adb version in a command prompt my version finally read properly as it should 1.0.31 and not 1.0.26. its self explanatory why. hope this helps someone!
Click to expand...
Click to collapse
I had to sign up for this forum just to tell you, THANK YOU!!!! For the life of me, it was ridiculous that I couldn't find just simple information on how to do stuff. This is my first time looking into this stuff, So I couldn't even figure out how to update individual tools like that, which is what I've been spending the last 2 hours or more trying to figure it out.
It really was those three files in the Windows directory this whole time. Now my device is online, and adb shows the right version. Amazing. It's absolutely pathetic that google has their program screw up the entire adb functionality by putting these broken versions of the tool in the Windows directory.
I had to add to the path variable the location folder of the appdata platoformtools abd.exe.
Setup: Windows 7 64 bit ultimate virtualboxing an android 4.0.4. That has no playstore, no terminal emulator.. and ohmygod I am so lost. lmfao.
Anywho - what i'm trying to do is install the play store and terminal emu onto this virtual ICS ROM... and adb is givin me ****. I rooted my samsung replenish with little/no problems.. but this is just beyond me in every aspect of the sense. It's seriously gotten to where ADB just hangs now upon any syntax commands.. adb will run the cmd list like it should - but now nothing of adb past that command will respond. Literally. "adb" is the only command that works.. lmfao.
BTW: I don't know that this got marked as a question - but it is. Apologies for any error that may be present and my general stupidity to linux systems.