Develop Bugs

Using Linux Mint instead of Windows...(SOLVED!!)

SOLVED! Followed the Guide in Post #5, than kept getting an error saying libncurse.so.5 cannot be found. I than opened the Package Manager and downloaded everything in the sun-java6-sdk and anything related to it. Than searched for anything of libncurse and installed those. than got a libc++ (or similar) missing than went back to Package Manager and download anything with libc++ in it. Afterwards, ran fine.
One quirk, as I'm sure this will be general knowledge to any Linux user but I am still a newbie at it. In root # i had to do ./adb to run the command, running just # abd gave me errors, exiting root back to $ alowed me to just use $ adb and not have to do ./adb
I know it's pretty shoddy, I think i downloaded 250MB of stuff I'm not sure I need. lol. I searched for the libncurse.so.5 file and had a lot of em, i think the package that actually did the trick was a ncurse32bit package, as I am on a 64 bit system. So take that into consideration
downloaded the android sdk, extracted it, however, when i use terminal and goto the tools folder and use adb
i get...
[email protected] /usr/bin/android-sdk/tools $ adb
No command 'adb' found, did you mean:
Command 'cdb' from package 'tinycdb' (main)
Command 'gdb' from package 'gdb' (main)
Command 'aub' from package 'aub' (universe)
Command 'dab' from package 'bsdgames' (universe)
Command 'zdb' from package 'zfs-fuse' (universe)
Command 'mdb' from package 'mono-debugger' (universe)
Command 'tdb' from package 'tads2-dev' (multiverse)
Command 'pdb' from package 'python' (main)
Command 'jdb' from package 'openjdk-6-jdk' (main)
Command 'ab' from package 'apache2-utils' (main)
adb: command not found
Click to expand...
Click to collapse
I read something about adding it to path, and i went into my .profile and added in the :/usr/bin/android-sdk/tools after the $PATH yaddayadda but it still didn't work.
Any help is appreciated. This is really the only thing keeping me from wiping the 120gb partition for Win7 and using Linux only(which only has a 21gb partition)

Nrre said:
downloaded the android sdk, extracted it, however, when i use terminal and goto the tools folder and use adb
i get...
I read something about adding it to path, and i went into my .profile and added in the :/usr/bin/android-sdk/tools after the $PATH yaddayadda but it still didn't work.
Any help is appreciated. This is really the only thing keeping me from wiping the 120gb partition for Win7 and using Linux only(which only has a 21gb partition)
Click to expand...
Click to collapse
Since the android sdk doesn't actually install on your computer but placed there by you, you must make sure everything is in place for it to work properly. I am relatively new to linux myself, but this is what i've done to get it working properly:
create /etc/init.d/adbd
you will need to do this as root.
Code:
gksu gedit /etc/init.d/adbd
paste this into the file
Code:
#!/bin/sh
#
# For ADB deamon (Android Device Bridge)
#
case "$1" in
start)
/usr/bin/android-sdk/tools/adb start-server
;;
stop)
/usr/bin/android-sdk/tools/adb kill-server
;;
*)
echo "Usage: $0 start|stop" >&2
exit 3
;;
esac
now run this:
Code:
sudo ln -s /etc/init.d/adbd /etc/rc2.d/S10adbd
What you just did there was make sure adb daemon started as root whenever you booted (if you don't start it as root you will get errors later on down the road)
I'm not sure about mint, but on ubuntu its easier to just add the tools folder to your /etc/environment file.
Code:
gksu gedit /etc/environment
the file should look something like this:
Code:
PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/bin/android-sdk/tools"
go ahead and reboot just to make sure everything sticks. You should be good from then on.
You could add the path to your profile, but then if you have to run something as sudo, or if you have another user trying to do something similar, it could be a headache. If you don't have a /etc/environment, or if the above still doesn't work, go ahead and see if you have a ~/.bashrc.
edit that:
Code:
gksu gedit ~/.bashrc
add this to the bottom:
Code:
export PATH=${PATH}:/usr/bin/android-sdk/tools
let me know if this works, and if there are any more experienced linux users out there who notice any mistakes of mine, or have better advice please chip in. I just know I went through a huge amount of frustration to get adb to work properly, through much trial and error. this is the culmination of what i went through that was easiest for me. BTW i stole that code for the daemon to startup as root from somewhere else.
EDIT: I just realized my daemon is still not starting on boot? although, with the above script i can start it via:
Code:
sudo service adbd start
someone smarter than me, chip in and tell me what i'm doing wrong?
OP, you can always start the daemon yourself as root by typing
Code:
sudo /usr/bin/android-sdk/tools/adb start-server
EDIT: woops. I fixed the code above, as well as fixed my problem. on creating a link to rc2.d i typed "s10adbd" originally and it should be "S10adbd".
OP, this is a great example why paying attention to capital/lower case letters are super important when learning linux.
i changed my link and everything works on my system.

think i'm still doing it wrong. i didn't have a .bashrc file but i did have a bash.bashrc file.
i know linux mint is based off ubuntu.
here is my command line after doing everything above
richard-laptop richard # /usr/bin/android-sdk/tools/adb start-server
/usr/bin/android-sdk/tools/adb: error while loading shared libraries: libncurses.so.5: cannot open shared object file: No such file or directory
richard-laptop richard # sudo service adbd start
adbd: unrecognized service
richard-laptop richard # adb shell
adb: error while loading shared libraries: libncurses.so.5: cannot open shared object file: No such file or directory
Click to expand...
Click to collapse
think i'll take the laptop into work and mess with it tonight.

If you don't setup a your bash file, you can issue adb commands by using standard terminal commands from the /tools directory:
user:~$ ./adb start-server
Click to expand...
Click to collapse
To setup your .bash file, right from Google:
# On Linux, edit your ~/.bash_profile or ~/.bashrc file. Look for a line that sets the PATH environment variable and add the full path to the tools/ directory to it. If you don't see a line setting the path, you can add one:
export PATH=${PATH}:<your_sdk_dir>/tools
Click to expand...
Click to collapse
From terminal, you can run
user:~$ gedit ~/.bashrc
Click to expand...
Click to collapse

Nrre said:
think i'll take the laptop into work and mess with it tonight.
Click to expand...
Click to collapse
Please follow these instructions (source = wiki.cyanogenmod.com):
Ubuntu: Android SDK, ADB, Fastboot.
There are various great tutorials online to help you set these options up for Windows, but the process of setting this up in Ubuntu Linux is rather fragmented across various different forums, and can be rather confusing! This is a tutorial I have put together after having real trouble setting it up myself, after trawling through numerous forums, and getting help from many very helpful folks on various forums including this one!
Tutorial: This will show you how to complete the basic set up of the Android sdk, and then how to enable the 'adb' and 'fastboot' connections so as to allow you to issue commands from the terminal directly to your phone.
Disclaimer: As always, you follow this tutorial at your own risk, nobody is forcing you to! I take absolutely no responsibility for damage to your computer / mobile phone etc. This is the process I have followed, and it is working fine!
Basic Android sdk installation and set-up:
You will need to download the following files before you start:
android_sdk_r05-linux_86.tgz [1]
Fastboot [2]
1. Extract the 'android_sdk_r05-linux_86.tgz' file to your 'Home' folder and rename it to 'sdk' to make things easier later on.
2. Move the fastboot file in to the 'Tools' folder inside the 'sdk' folder.
3. Now right click on both the 'fastboot' and 'adb' files (inside the tools folder) and choose 'Properties' and then the 'Permissions' tab, and ensure they both have the 'allow executing file as program' box is ticked...Now reboot the computer, sorted!
Set up ubuntu to recognize your phone, and the adb/fastboot commands in the terminal
1.Open your 'Home' folder. Press 'Ctrl' & 'H' at the same time to view hidden files, and then open the '.bashrc' file and add the following text to the top of the file:
#AndroidDev PATH
export PATH=$PATH:/home/username/sdk/tools
2.Obviously you will need to replace 'username' with your own...Save the file and exit.
3.Now log-in as root.
3. Navigate to the following directory in the root filesystem: /etc/udev/rules.d/
4. Create the following empty file:
(ubuntu 10.04)
99-android.rules
(ubuntu 9.10)
70-android.rules
(ubuntu 7.10/8.04)
51-android.rules
5. You then need to edit the file with the following text (depending on your version of ubuntu):
ubuntu 7.10/8.04/9.10:
SUBSYSTEM==”usb”, ATTRS{idVendor}==”0bb4”, MODE=”0666”
SUBSYSTEM==”usb”, ATTRS{idVendor}==”18d1”, MODE=”0666”
SUBSYSTEM==”usb”, ATTRS{idVendor}==”22b8”, MODE=”0666”
ubuntu 6.06:
SUBSYSTEM==”usb_device”, SYSFS{idvendor}==”0bb4”, MODE=”0666”
SUBSYSTEM==”usb_device”, SYSFS{idvendor}==”18d1”, MODE=”0666”
SUBSYSTEM==”usb_device”, SYSFS{idvendor}==”22b8”, MODE=”0666”
6. Save this file, and then open the terminal and enter the following command:
chmod a+rx /etc/udev/rules.d/70-android.rules
Change the '70' to '51' depending on your version of ubuntu.
For a list of the vendor ID's go here: VendorID's [3]
7. Now reboot the computer.
8. Open Terminal, and issue the following commands:
su
cd /home/username/sdk/tools/
./adb kill-server
./adb start-server
You will now be able to open a terminal and carry out 'adb' and 'fastboot' commands directly.
Credit and thanks to:
koalaboy, Apostasy, Cloverdale, wddglr, JgeZau.
EDIT: I have followed this tutorial to the letter myself today on my laptop to prove it works, for both yours the reader, and my own peace of mind as the writer! Enjoy, it works flawlessly!
Click to expand...
Click to collapse
I have followed these directions more than once and each time they work flawlessly. This should work with Linux Mint, since Mint's based off Ubuntu.
For Part 4, use Ubuntu 10.04 when creating the empty file and for Part 5, use this SUBSYSTEM: SUBSYSTEM==”usb”, ATTRS{idVendor}==”0bb4”, MODE=”0666” and paste that into your 99-android.rules file.

followed to a T.
not sure how to log in as root, so i just 'run as administrator' i can't find anything on root for this.
i still get the following after i do that entire guide
richard-laptop richard # cd /home/richard/sdk/tools
richard-laptop tools # ./adb kill-server
./adb: error while loading shared libraries: libncurses.so.5: cannot open shared object file: No such file or directory
richard-laptop tools # ./adb start-server
./adb: error while loading shared libraries: libncurses.so.5: cannot open shared object file: No such file or directory
Click to expand...
Click to collapse

Nrre said:
followed to a T.
not sure how to log in as root, so i just 'run as administrator' i can't find anything on root for this.
i still get the following after i do that entire guide
Click to expand...
Click to collapse
To login in as root, you enter:
Code:
sudo su
As for the "error while loading shared libraries: libncurses.so.5" -- I've never seen that error before. Might be Linux Mint problem? I currently run Ubuntu 10.04 32 Bit.

when i do SU it asks my password and the $ becomes a #
i assume that is root? i dont have to do SUDO i just did SU
yeah if i do SUDU SU i get a 'SUDO command not found'
gonna post this over on the linux mint forums see if they can help me to.

Nrre said:
when i do SU it asks my password and the $ becomes a #
i assume that is root? i dont have to do SUDO i just did SU
yeah if i do SUDU SU i get a 'SUDO command not found'
gonna post this over on the linux mint forums see if they can help me to.
Click to expand...
Click to collapse
Wait... wait.. are you trying to do following instructions on your phone or on your computer?
If you run su on your phone, sure you'll get root (# sign). But the command, sudo su was meant for your computer. The instructions I listed are for your computer with Linux Mint installed.

yeah i'm doing it on my computer =P
if i do SUDU SU it gives me that error, but SU gives me #
so...i was hoping it'd all be teh same since Mint is based off ubuntu and half my updates are ubuntu files.

[email protected] ~ $ sudu
No command 'sudu' found, did you mean:
Command 'sudo' from package 'sudo' (main)
Command 'sudo' from package 'sudo-ldap' (universe)
Command 'tudu' from package 'tudu' (universe)
sudu: command not found
[email protected] ~ $ SUDU su
SUDU: command not found
[email protected] ~ $ SUDU SU
SUDU: command not found
Click to expand...
Click to collapse
so, not sure what else to do.

sudo
not sudu

elegantai said:
sudo
not sudu
Click to expand...
Click to collapse
balls, well i still get the same result after i go through and make all the changes and use SUDO SU instead of just SU, i get the same prompt with #
this is still my end result.
richard-laptop richard # cd /home/richard/sdk/tools/
richard-laptop tools # ./adb kill-server
./adb: error while loading shared libraries: libncurses.so.5: cannot open shared object file: No such file or directory
richard-laptop tools # ./adb start-server
./adb: error while loading shared libraries: libncurses.so.5: cannot open shared object file: No such file or directory
Click to expand...
Click to collapse
makes me feel like i'm missing a file somewhere. i did download the newest android sdk and not the older version that is in the guide. but i still installed the packages for android 2.1 and 2.2
suppose i'll delete it all and start over.
EDIT: Went through, put in proper vendor IDs and noticed i put Richard in the Path and not richard, still, says it's missing the same "libncurses.so.5" so...not sure what to do. =/

I don't know that error either, but looking at this thread:
http://bbs.archlinux.org/viewtopic.php?id=66878
sounds like it could be a java issue? Didn't think to ask, have you installed the java sdk? which version of java are you running?

now that i think about it...i don't believe i downloaded a new java...
the worse news is my win7 got corrupted somehow =P so now i only have Linux so time to dig in and try this out.
I'd download the stuff now but I'm tethering through my phone so i'm lucky to get 600kbps download speeds in this reception area.
I could step 10 feet outside and hit 1200kbps though. So i formatted the HD and reinstalled Linux Mint. Once i get home I'll look into the JDK as that makes sense now that I think about it to.
EDIT: Should I install Eclipse also? Installing Android SDK and Java6 JDK right now. I really just want to use ADB for now to send commands to phone etc.

No need for eclipse.. That's just for actual development

ADB Error: /home/richard/sdk/tools/adb: error while loading shared libraries: libncurses.so.5: cannot open shared object file: No such file or directory
'adb start-server' failed.
Click to expand...
Click to collapse
this shows up int he Android SDK/AVD manager as i install all the packages...
EDIT: opened up software manager, and downloaded every sun-java package, than installed everything that showed up when i typed libncurses ... once it's done will reboot and try again =P
2nd EDIT: i decided to search for libncurses.so.5 and i have 3 of em, one in usr/lib, /lib64 and something else.
so..not sure where else to put it, went into synaptics thing or something and downloaded ncurses32bit as i noticed none of my lib32 folders had it...giving it a go.
btw... my .bashrc is .profile, i copied .profile and renamed it to .bashrc and my prompt stopped showing up in terminal...linux is so weird.
3rd EDIT: Just isn't meant to be. got to ./adb kill-server and instead of missing the libncurse.so.5 i am now missing..
richard-laptop tools # ./adb kill-server
./adb: error while loading shared libraries: libstdc++.so.6: cannot open shared object file: No such file or directory
Click to expand...
Click to collapse
off i go to hunt this package down

it's working...finally
however...
richard-laptop tools # adb devices
No command 'adb' found, did you mean:
Command 'cdb' from package 'tinycdb' (main)
Command 'gdb' from package 'gdb' (main)
Command 'aub' from package 'aub' (universe)
Command 'dab' from package 'bsdgames' (universe)
Command 'zdb' from package 'zfs-fuse' (universe)
Command 'mdb' from package 'mono-debugger' (universe)
Command 'tdb' from package 'tads2-dev' (multiverse)
Command 'pdb' from package 'python' (main)
Command 'jdb' from package 'openjdk-6-jdk' (main)
Command 'ab' from package 'apache2-utils' (main)
adb: command not found
richard-laptop tools # ./adb devices
List of devices attached
HT*********** device
Click to expand...
Click to collapse
i have ot do ./adb and not just adb
EDIT: exit su, and in $, lets me just do adb.
THANK YOU EVERYONE <3 Wish I could +rep or Thanks your post here.!!
changed title to reflect it. was a good 'thrown under the bus' into linux. now to read up more on it. w/out losing half my CCNA knowledge i've gathered...ha

Enjoy Linux. You'll enjoy it once you get used to it.
Sent from my PC36100 using XDA App

Nrre said:
it's working...finally
however...
i have ot do ./adb and not just adb
EDIT: exit su, and in $, lets me just do adb.
THANK YOU EVERYONE <3 Wish I could +rep or Thanks your post here.!!
changed title to reflect it. was a good 'thrown under the bus' into linux. now to read up more on it. w/out losing half my CCNA knowledge i've gathered...ha
Click to expand...
Click to collapse
Since this has been solved, I would advise posting the resolution on the first page -- so new users are aware of what exactly you had to do to fix it.

[Q] Mac equivalent to flashtool?

Is there a Mac equivalent to FlashTool?

I also have the same question.

Hi there mmzubair!
In the end the best solution I found was just to install windows XP with bootcamp! Or if your Macs newer than mine (using a 4 year old Mac Mini) you could install XP using parallels so you don't have to rebooting every time you want to flash your phone!
Sent from my R800i using Tapatalk 2

I'm wondering if you can install and run flashtool with Wine?
Sent from my R800x using Tapatalk 2

beez1717 said:
I'm wondering if you can install and run flashtool with Wine?
Sent from my R800x using Tapatalk 2
Click to expand...
Click to collapse
I believe you can't because wine can't install driver software.

flashtool linux
the flashtool site explains a method of installing it on linux based systems, but it all sounds gibberish to me (because im a noob) and i cannot understand it, has anybody done this? please explain in pure english if possible. thank you.

Flashtool on Mac instructions
!! UPDATE, ALL
There is a flashtool for mac on androxyde's github.
Basically...
You need (in this order):
1/ Xcode, Download and install it from App store/your mac's supplied DVD/Apple developer website
> If using version 3 and earlier, make sure the "UNIX Development", "System Tools", "Command Line Tools", or "Command Line Support" is selected during the installation process,
> If using version 3 and earlier, Apple's Command Line Developer Tools are found at the Apple Developer Connection site
2/ MacPorts, See section 2 on http://www.macports.org/install.php.
Then:
3/ Download and unzip flashtool from androxyde's github
More prep work for the USB stuff:
4/ Open Terminal and type/run code:
Code:
ls -la /opt/local/lib/libusb-1.0.dylib
If "no file or directory" found then run code:
Code:
sudo port install libusb
Now, to run Flashtool (ASSUMING YOU DID NOT RENAME THE FLASHTOOL FOLDER AND PROGRAM NAME SINCE UNZIP!):
5/ Open Terminal and type/run code:
Code:
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/opt/local/lib; */Flashtool/FlashTool;
or
Code:
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/opt/local/lib; ~/Downloads/Flashtool/FlashTool;
Alternatively:
> Open up the "Flashtool" Unix Executable File in TextEdit
> Copy and paste
Code:
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/opt/local/lib
the the line directly underneath export OS=$(uname -s)
> Save it, and from now on, double click the FlashTool executable file to open flashtool
6/ Flashtool window should pop up and a smile appears on your face
Maintenance
7/ To update MacPorts and installed ports, open terminal and run:
Code:
sudo port -v selfupdate; sudo port -v upgrade outdated;

Themindbuddah said:
Is there a Mac equivalent to FlashTool?
Click to expand...
Click to collapse
J0YU said:
There is a flashtool for mac on androxyde's github.
Basically...
You need (in this order):
1/ Xcode, Download and install it from App store/your mac's supplied DVD/Apple developer website
2/ MacPorts, See section 2 on http://www.macports.org/install.php.
Then:
3/ Download flashtool from androxyde's github
More prep work for the USB stuff:
5/ Open Terminal and type/run code:
Code:
ls -la /opt/local/lib/libusb-1.0.dylib
If "no file or directory" found then run code:
Code:
sudo port install libusb
6/ Last line of code to run in Terminal for prep:
Code:
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/opt/local/lib
Now run Flashtool:
7/ Open the Flashtool folder which you unzipped in 3/
8/ Double click on "Flashtool" (Unix Executable File)
Hopefully that helps, haven't tried it out personally because I'm too lazy for 1/ and 2/ but reply/thanks if it works out fine!
Maintenance
9/ To update MacPorts, open terminal and run:
Code:
sudo port -v selfupdate
Click to expand...
Click to collapse
That's right there is a FlashTool Mac Edition check it out: http://androxyde.github.com/

Thanks for the post. The LD_LIBRARY_PATH variable was the key for me. With the 2 mods for steps 6 & 8 in bold, these directions worked on my MacBook Air. FlashTool now comes up and runs!
-- Cronin
6/ Last line of code to run in Terminal for prep:
Code:
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/opt/local/lib
Becomes:
Code:
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/opt/local/lib
​
Now run Flashtool:
7/ Open the Flashtool folder which you unzipped in 3/
8/ Double click on "Flashtool" (Unix Executable File)
Becomes:
go to your FlashTool folder
Code:
cd ../FlashTool
​execute the FlashTool:
Code:
- ./Flashtool
​

J0YU said:
There is a flashtool for mac on androxyde's github.
Basically...
You need (in this order):
1/ Xcode, Download and install it from App store/your mac's supplied DVD/Apple developer website
2/ MacPorts, See section 2 on http://www.macports.org/install.php.
Then:
3/ Download flashtool from androxyde's github
More prep work for the USB stuff:
5/ Open Terminal and type/run code:
Code:
ls -la /opt/local/lib/libusb-1.0.dylib
If "no file or directory" found then run code:
Code:
sudo port install libusb
6/ Last line of code to run in Terminal for prep:
Code:
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/opt/local/lib
Now run Flashtool:
7/ Open the Flashtool folder which you unzipped in 3/
8/ Double click on "Flashtool" (Unix Executable File)
Hopefully that helps, haven't tried it out personally because I'm too lazy for 1/ and 2/ but reply/thanks if it works out fine!
EDIT: check out the post below for more info/stuff
Maintenance
9/ To update MacPorts, open terminal and run:
Code:
sudo port -v selfupdate
Click to expand...
Click to collapse
I followed this guide and tried the other variation but when i launch flashtool this happen:
Macbook:~ Suz$ /Users/Suz/Downloads/FlashTool/FlashTool ; exit;
Exception in thread "main" java.lang.UnsatisfiedLinkError: Unable to load library 'usb-1.0': dlopen(libusb-1.0.dylib, 9): image not found
at com.sun.jna.NativeLibrary.loadLibrary(NativeLibrary.java:179)
at com.sun.jna.NativeLibrary.getInstance(NativeLibrary.java:252)
at com.sun.jna.Library$Handler.<init>(Library.java:140)
at com.sun.jna.Native.loadLibrary(Native.java:368)
at com.sun.jna.Native.loadLibrary(Native.java:353)
at se.marell.libusb.jna.LibUsb.<clinit>(LibUsb.java:11)
at se.marell.libusb.LibUsbSystem.<init>(LibUsbSystem.java:36)
at se.marell.libusb.LibUsbSystem.<init>(LibUsbSystem.java:73)
at linuxlib.JUsb.init(JUsb.java:38)
at gui.FlasherGUI.main(FlasherGUI.java:170)
logout
[Processo completato]
nothing else! Where am I doing wrong?

smayor said:
I followed this guide and tried the other variation but when i launch flashtool this happen:
Macbook:~ Suz$ /Users/Suz/Downloads/FlashTool/FlashTool ; exit;
Exception in thread "main" java.lang.UnsatisfiedLinkError: Unable to load library 'usb-1.0': dlopen(libusb-1.0.dylib, 9): image not found
at com.sun.jna.NativeLibrary.loadLibrary(NativeLibrary.java:179)
at com.sun.jna.NativeLibrary.getInstance(NativeLibrary.java:252)
at com.sun.jna.Library$Handler.<init>(Library.java:140)
at com.sun.jna.Native.loadLibrary(Native.java:368)
at com.sun.jna.Native.loadLibrary(Native.java:353)
at se.marell.libusb.jna.LibUsb.<clinit>(LibUsb.java:11)
at se.marell.libusb.LibUsbSystem.<init>(LibUsbSystem.java:36)
at se.marell.libusb.LibUsbSystem.<init>(LibUsbSystem.java:73)
at linuxlib.JUsb.init(JUsb.java:38)
at gui.FlasherGUI.main(FlasherGUI.java:170)
logout
[Processo completato]
nothing else! Where am I doing wrong?
Click to expand...
Click to collapse
i have the same problem can someone help me?

currently trying to diagnose it, I got the same problem too xD

The problem is that instead of */Flashtool/Flashtool you should replace before * with the the path from root to the file.
On my system this was:
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/opt/local/lib; /Users/<username>/Downloads/Flashtool/FlashTool;
Was getting same error and then it loaded
edit--
In fact, just open FlashTool in text wrangler or another editor and paste this in:
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/opt/local/lib
after line:
export OS=$(uname -s)
save that and it should work. I did this, then I got an app got Platypus and wrapped the whole thing into a .app file. I'd upload it but it is 80 megs and I have a quarter meg upload rate
You could probably put that jar on the same path as the other files and it would find it, and save others going through the other steps but I'm not sure. I've not had time to try.

brim4brim said:
The problem is that instead of */Flashtool/Flashtool you should replace before * with the the path from root to the file.
On my system this was:
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/opt/local/lib; /Users/<username>/Downloads/Flashtool/FlashTool;
Was getting same error and then it loaded
edit--
In fact, just open FlashTool in text wrangler or another editor and paste this in:
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/opt/local/lib
after line:
export OS=$(uname -s)
save that and it should work. I did this, then I got an app got Platypus and wrapped the whole thing into a .app file. I'd upload it but it is 80 megs and I have a quarter meg upload rate
You could probably put that jar on the same path as the other files and it would find it, and save others going through the other steps but I'm not sure. I've not had time to try.
Click to expand...
Click to collapse
oops, did the unix wildcard " * " not work on your machine? yeah it's either that or
Code:
~/Downloads/Flashtool/FlashTool
should also work. Thanks for the heads up, might update my tutorial more to cover more stuff and maybe release a moded FlashTool executable, I'm not sure

J0YU said:
oops, did the unix wildcard " * " not work on your machine? yeah it's either that or
Code:
~/Downloads/Flashtool/FlashTool
should also work. Thanks for the heads up, might update my tutorial more to cover more stuff and maybe release a moded FlashTool executable, I'm not sure
Click to expand...
Click to collapse
I hope you guys can help, I tried using the methods you gave (exporting the var and updating the file in textwrangler) but I'm still getting the error below. Would you know how to get around this?
I checked and I do have the file:
Users-iMac:FlashTool user$ ls -la /opt/local/lib/libusb-1.0.dylib
lrwxr-xr-x 1 root admin 18 May 12 00:25 /opt/local/lib/libusb-1.0.dylib -> libusb-1.0.0.dylib
Error below:
Last login: Sat Nov 3 00:47:57 on ttys001
Users-iMac:~ user$ /Users/user/Downloads/FlashTool/FlashTool ; exit;
Exception in thread "main" java.lang.UnsatisfiedLinkError: Unable to load library 'usb-1.0': dlopen(libusb-1.0.dylib, 9): image not found
at com.sun.jna.NativeLibrary.loadLibrary(NativeLibrary.java:179)
at com.sun.jna.NativeLibrary.getInstance(NativeLibrary.java:252)
at com.sun.jna.Library$Handler.<init>(Library.java:140)
at com.sun.jna.Native.loadLibrary(Native.java:368)
at com.sun.jna.Native.loadLibrary(Native.java:353)
at se.marell.libusb.jna.LibUsb.<clinit>(LibUsb.java:11)
at se.marell.libusb.LibUsbSystem.<init>(LibUsbSystem.java:36)
at se.marell.libusb.LibUsbSystem.<init>(LibUsbSystem.java:73)
at linuxlib.JUsb.init(JUsb.java:38)
at gui.FlasherGUI.main(FlasherGUI.java:170)
logout
[Process completed]
---------- Post added at 01:21 AM ---------- Previous post was at 01:02 AM ----------
Somehow, double clicking on FlashTool gives me that error... But doing a ./FlashTool in the terminal works. Thanks!
Would you guys happen to know if a Mac version of the rooting toolkit is available?

Somehow, double clicking on FlashTool gives me that error... But doing a ./FlashTool in the terminal works. Thanks!
Would you guys happen to know if a Mac version of the rooting toolkit is available?
Click to expand...
Click to collapse
Are you talking about ADB and FlashTool for mac?
Or like the actual rooting stuff like Superuser.apk and BusyBox (root_tools.rar in the attached files)?

Use wine
Sent from my R800x using xda app-developers app

problems with libusb
Hi guys,
thank you so much for this guide,
I have a problem when i try to open flash tool with the
Code:
~/Downloads/Flashtool/FlashTool
this error shows up
Minimum libusb version is 1.0.14. Found 1.0.9
It can be downloaded on
i have tried everything and i really cannot updated :crying::crying:
Please help me i never done it before

Java 1.6 or 1.7
Hi!
Whenever I try to run the commands, I get the following error message:
"Java version must be 1.6 or 1.7"
I have the latest version of Java installed on my Mac, and I can actually see the Java icon from the Control Panel. Any ideas about the error I get?
Thanks!

Hi!
Whenever I try to run the commands, I get the following error message:
"Java version must be 1.6 or 1.7"
I have the latest version of Java installed on my Mac, and I can actually see the Java icon from the Control Panel. Any ideas about the error I get?
Thanks!
Click to expand...
Click to collapse
1// What version of Mac OS X are you running on?
2// What do you get when you run java -version in terminal?
Hi guys,
thank you so much for this guide,
I have a problem when i try to open flash tool with the
Code:
~/Downloads/Flashtool/FlashTool
this error shows up
Minimum libusb version is 1.0.14. Found 1.0.9
It can be downloaded on
i have tried everything and i really cannot updated
Please help me i never done it before
Click to expand...
Click to collapse
I'm looking into it...
btw are you trying to run flashtool version v0.9.9.0 or an older one?
I written the tutorial a while ago lol

Xperia on Ubuntu (Udev rules, Flashtool, ADB&Fastboot)

This is a thread written to try and get poor MilkyJoePD up and running with his Ubuntu build, but it should be of help to anyone.
First of all, what you need:
1) Any version of Ubuntu from 10.04 onwards, with superuser access. The upcoming LTS Ubuntu 12.04 will be a great idea when it comes out, as it'll be maintained for 5 years (so the instructions to install it there will be valid for all that time).
2) Your Xperia Play (or any Xperia phone actually).
3) A Micro USB cable to connect it.
4) An open mind about terminal emulators. They're useful because they allow you to do things quickly and cleanly, if you just know their syntax.
What will we be doing in this thread: we'll set up our Xperia Play so that it gets recognized properly by Ubuntu. In addition, we'll set up ADB and Flashtool, which are programs with which our Xperia Play can interact. Lastly, we'll cover how to summon the "adb" and "fastboot" commands from any point in the terminal, by adding them to the $PATH variable.
Setting up the Xperia phone: udev rules
Android devices don't need specific drivers to work in Linux: you can plug an Android phone and it will be recognised as a flash drive. However, if we want deeper levels of interaction, such as the ones which ADB, Fastboot and Flashtool provide, we have to set up udev rules. Long story short, udev rules allow us to give the proper permissions that these modes require without having to function as superuser the whole time (an undesirable state of things in Ubuntu). Much more about them can be found here for the curious minds out there.
But let's not get lost. We want to set up udev rules, so we'll do it. First of all, we need to know the following: a device connected while it functions normally is not "seen" as the same device when it's connected in the Flash or Fastboot modes. In order to identify it, we can run "lsusb" which lists all of the ports, and connected devices, in our computer.
So, let's connect a Xperia phone which is turned on. We don't have to mount the sdcard as a flash drive, just plug it in. Once you have done that, open a terminal and type
Code:
lsusb
It will list you a boatload of devices, but only one of them is relevant to you right now:
Code:
Bus 00x Device 00y: ID 0fce:aaaa Sony Ericsson blah blah
The device is identified with two alphanumeric chains. The first one is the vendor ID, and the second one is the Product ID, which are the identificators we're going to use for the udev rules later on.
Let's switch off our phone, and plug it in "Flash" mode (hold the Back button while you connect it). Run "lsusb" again in the terminal again, and you'll find:
Code:
Bus 00x Device 00y: ID 0fce:bbbb Sony Ericsson blah blah
The Vendor ID is the same (0fce) for all Sony Ericsson devices, but the Product ID is different, as you can see. This is consistent with the idea that it's identified as "another" device.
The last part would be plugging the phone in Fastboot mode, holding the Search key while we plug the phone. Typing "lsusb" in the terminal again will give us:
Code:
Bus 00x Device 00y: ID 0fce:cccc Sony Ericsson blah blah
Which is, as we know already, a different Product ID.
Now that we have the device ID needed for the udev rules, we can write them. The most expedite way is to write in that lovely terminal:
Code:
sudo gedit /etc/udev/rules.d/99-android.rules
That means, we'll use the standard text editor (gedit) to create the file 99-android.rules in the /etc/udev/rules.d folder. If we visit said folder we'll find other udev rules created already, but they're not interesting for our task. Notice that we ask for superuser permissions with "sudo" as we need them to write or modify udev rules. Once we have put our password we'll find an empty text file. And now we just copy-paste the following syntax:
Code:
SUBSYSTEMS==”usb”, ATTRS{idVendor}==”0fce″, ATTRS{idProduct}==”aaaa″, MODE=”0666″
SUBSYSTEMS==”usb”, ATTRS{idVendor}==”0fce″, ATTRS{idProduct}==”bbbb″, MODE=”0666″
SUBSYSTEMS==”usb”, ATTRS{idVendor}==”0fce″, ATTRS{idProduct}==”cccc″, MODE=”0666″
In human language, this means "Give the devices that are connected through USB and which have the mentioned ID codes the permissions 0666 (read/write access), which need root access".
Once we've filled the gaps, we just save the file. After we close it, we have to type in the terminal "sudo restart udev" and we've taken care of that part. Rebooting the computer has the same effect, but it's a bit of overkill, really.
Flashtool
With the udev rules fixed, we can go to the next step, which would be using Flashtool. It is necessary to mention that unlike the Windows version, Flashtool doesn't need any installation of any kind in Linux, you just run the program (the file called Flashtool) and you're set. You have to download the Flashtool folder, uncompress it and run the program. The folder is compressed in .7z format: Ubuntu doesn't manage 7z packages "out of the box", but that's no problem: go to your terminal, type:
Code:
sudo apt-get install p7zip-full
and that should take care of it. If you're not familiar with that command, "apt-get install" is the way to install packages from your existing repositories in Debian/Ubuntu; installing software in Ubuntu requires superuser access, as I'm sure you know. p7zip-full is a package which adds 7zip support to the archive manager of Ubuntu.
I won't cover how to use Flashtool, since I already did so in this post. While I made the tutorial for an older version of Flashtool, the base functions are exactly the same as before.
Optional: ADB and Fastboot; setting them in $PATH
OK, now we're going to the stronger stuff: if you want to do a bit more than restoring official ROMs and flashing kernels you'll do well in using the ADB and Fastboot programs. They're part of the platform tools of the Android SDK. You can download the latest Android SDK here: http://developer.android.com/sdk/index.html
Once you've downloaded and uncompressed the Linux version of the SDK, go to the "tools" folder and run the "android" file (you need to mark it as executable first, in the properties). That file is the Android SDK Manager. Once it's running, you only need to install the SDK Platform Tools package. The rest are not necessary for our purposes.
Once you install the package, you'll notice that the folder where you unpacked the SDK is bigger. You'll find there the "platform-tools" folder, which contains adb and fastboot. You can run them from a terminal, but that requires you to have your terminal running in the exact folder where your /<Path/to/SDK> directory lies. This can get old really quickly if you use ADB and/or Fastboot frequently, so we'll do a trick that will allow us to summon them from any folder: we'll add them to our PATH variable.
In order to do this, we need to open a new terminal. It will start in our home directory. There is a file called .bashrc in our home folder that we need to tweak, so let's go to it. You don't see it normally, as it's hidden. All files which begin with a . in Linux will be hidden by default. You can see them in Nautilus by pressing Ctrl+H, and in a terminal by typing "ls -a". At any rate, this file is hidden because you usually don't need to touch it, but we'll do it here.
In our terminal, we write
Code:
gedit .bashrc
Again, gedit is the standard text editor in Ubuntu.
We see a lot of stuff we don't need to touch. We just need to go to the final line, after the word "fi" and write below:
Code:
# ADB and Fastboot direct link (this is a comment, so we remember what we did)
PATH=$PATH:/home/Path/to/SDK/platform-tools/
export PATH
We save the modified file, close any terminal we had left open, and now we can use adb and fastboot directly from any folder. Just connect your device with debug mode on for example, and type "adb devices": you should see the ADB identificator of your device.
And with that, I cover the installation guide of Xperia phones in the Ubuntu environment. I hope it's useful to everyone, particularly to MilkyJoePD who has inspired me to write it. If I've missed something I should have mentioned, by all means say it.

Haven't used Ubuntu for a while but I'm taking note of this for later. Thank you for the info.
Sent from a Galaxy far, far away

don't forget to install de dependencies:
Code:
sudo apt-get install libusb-1.0
on 64 systems, you need 32bits libraries, so run:
Code:
sudo apt-get install ia32-libs

With the news of Sony not releasing ICS, I decided to try again to get fastboot working.
While installing the dependencies, I get this:
W: Duplicate sources.list entry cdrom://Ubuntu 11.10 _Oneiric Ocelot_ - Release i386 (20111012)/ oneiric/main i386 Packages (/var/lib/apt/lists/Ubuntu%2011.10%20%5fOneiric%20Ocelot%5f%20-%20Release%20i386%20(20111012)_dists_oneiric_main_binary-i386_Packages)
W: Duplicate sources.list entry cdrom://Ubuntu 11.10 _Oneiric Ocelot_ - Release i386 (20111012)/ oneiric/restricted i386 Packages (/var/lib/apt/lists/Ubuntu%2011.10%20%5fOneiric%20Ocelot%5f%20-%20Release%20i386%20(20111012)_dists_oneiric_restricted_binary-i386_Packages)
W: You may want to run apt-get update to correct these problems
Where do I go from here?

Remove CD-ROM reference from sources
Edit your sources and comment-out / turn off the references for the installation disk (CDROM/DVD). It should be the first thing you turn of after any install anyway. In my humble opinion.
Then run
sudo apt-get update
sudo apt-get -f install
this should resolve any pending issues and get you running.

skeltonh said:
Edit your sources and comment-out / turn off the references for the installation disk (CDROM/DVD).
Click to expand...
Click to collapse
How do I do that?
Sent from my R800i using XDA

Or can somebody can tell me what it means so I can Google it?
Sent from my R800i using XDA

I have a problem, when I try to use fastboot even in the platform-tools folder it says:
fastboot: command not found

On what OS? If it's Linux, you have to add a Dotslash to execute the file.
Swypesation

I have created udev rules as said above, but flashtool still says 'Add udev rules'.
What I am missing here. I'm using Ubuntu 12.04.
Any help is appreciated.

You must start flashtool with root acces

is rooting ur play a wise decission?

wat is better 4 my play, ics or gingerbreadman?

where/what is the search key on a mini pro?
Thanks

Big Thanks for this Tutorial Logesman. :good: Just wanted to add that I think...anyone having trouble installing SDK + Manager has to install Java JDK first. Yes, I got stuck at installing SDK.:silly: I tried to run android file in tools folder (as executable) which opens manager.
From Terminal:
sudo apt-get install openjdk-7-jdk openjdk-7-jre

i am unable to run "adb devices" command in ubuntu 12.04.. please help :crying:

roopz said:
i am unable to run "adb devices" command in ubuntu 12.04.. please help :crying:
Click to expand...
Click to collapse
I am having same problem on 12.04! I did everything in this thread afaik, and the ubuntu forums. I could really use some help , because I also have problems with adb.
Sent from my R800i using xda premium

install windows might be easier.
Sent from my Xperia Play using Tapatalk 2

roopz said:
i am unable to run "adb devices" command in ubuntu 12.04.. please help :crying:
Click to expand...
Click to collapse
cyrusalmighty said:
I am having same problem on 12.04! I did everything in this thread afaik, and the ubuntu forums. I could really use some help , because I also have problems with adb.
Sent from my R800i using xda premium
Click to expand...
Click to collapse
Have you tried running adb as root? (After a week of testing 12.04, I left to go back to 10.04, a much better release, imo)
Pax
Sent from my R800x using Tapatalk 2

IE-coRe said:
I have a problem, when I try to use fastboot even in the platform-tools folder it says:
fastboot: command not found
Click to expand...
Click to collapse
seems like you didn't path the fastboot command correctly, try check back again at your .bashrc
roopz said:
i am unable to run "adb devices" command in ubuntu 12.04.. please help :crying:
Click to expand...
Click to collapse
same case as the above
cyrusalmighty said:
I am having same problem on 12.04! I did everything in this thread afaik, and the ubuntu forums. I could really use some help , because I also have problems with adb.
Sent from my R800i using xda premium
Click to expand...
Click to collapse
would you mind telling what does the error says?

[HOW TO] set up adb on UBUNTU 12.04, 11.10 and 11.04 easy way

If you are using Windows 8.1 or Windows 8, you will know that the HTC drivers are not compatible and you cannot get fastboot access using Windows.
So what is the next best option? Dual boot to LINUX (UBUNTU).
This guide is a step by step noob friendly guide to set up the adb and fastboot tools on UBUNTU without the hassels of downloading SDK or JDK
Step 1: Open teminal on UBUNTU
Step 2: type the following as it is one at a time
Code:
sudo add-apt-repository ppa:nilarimogard/webupd8
sudo apt-get update
sudo apt-get install android-tools-adb android-tools-fastboot
Step 3: Update the adb packages by typing the following in the terminal
Code:
sudo apt-get install android-tools-fsutils
Step 4: Now download the Linux Fastboot files from downloads below. Extract on Desktop
Step 5: Run termial and type the following one by one
Code:
sudo adb devices
This will start the adb server
Code:
cd Desktop
This moves you to your desktop
Code:
cd Fastboot/ Linux
This will get you inside the fastboot folder extracted on the desktop
Code:
sudo fastboot devices
This will show the list of all the fastboot devices connected to the PC
(Remember to keep your phone in the fastboot mode by holding the "power + volume down" keys and then selcting fastboot from the bootloader menu)
Thats it!!
Congratulation you have now access to fastboot on your linux UBUNTU PC!
Hit that THANKS button if it helped!

Soutik said:
Code:
[/ sudo adb devices]
[/QUOTE]
Thanks for the info! One caveat, you forgot to terminate your code blocks with /CODE :D
like this:
[CODE][/ sudo adb devices]
Click to expand...
Click to collapse

selivanow said:
Thanks for the info! One caveat, you forgot to terminate your code blocks with /CODE
like this:
Code:
[/ sudo adb devices]
Click to expand...
Click to collapse
Thanks a lot!!! I was wondering why it wasnt like the other posts.
This is my first post!! Thanks for correcting me!

I thought the android tools where available in the standard repositories?
I am running mint and have never added the new repo.

Yes they are.. But setting them up requires u to install SDK and then extract the libs from there... This one just gets going for noobs who face trouble on win 8 and really really have to use Linux to access boot loader and fastboot.. Hence a guide
Sent from my Nexus 5 using xda app-developers app

[GUIDE] ADB & Fastboot not working under Windows? UBUNTU WILL DO!

The keystone of this guide: make ADB & fastboot working in Ubuntu, when nothing else helps with with Windows. Resent Windows OS versions are getting less flashing-friendly and some brands (like Samsung) release new devices on the market without compatible USB drivers. Before losing countless hours trying to solve the problems, try this, possibly very easy solution.
Compatible devices: ADB will work on nearly all devices, fastboot should be also usable for very most of the devices with bootloader mode: Nexus, HTC, Sony etc.
The guide is posted here in Nexus 7 (2013) thread for high amount of reported bootloops right after unlocking the bootloader- or problems with executing fastboot commands in Windows, which must work to unbrick the device.
DISCLAIMER:
Code:
* [I]I am not responsible for bricked devices or PCs, personal crisis, depressions[/I]
* [I]sleeples nights, termonuclear wars, electricity blackouts, short circuits,[/I]
* [I]or for bad weather in your region that will brick your Android device or your PC.[/I]
* [I]I try to help here, but it may not work for you. You do all on your own risk.[/I]
Click to expand...
Click to collapse
INSTALL ONLY FASTBOOT :
Windows can cause so many problems, that sometimes ADB & Fastboot simply won't work.
Run therefore ADB or fastboot in Ubuntu if Windows fails.
Installing ONLY fastboot in Ubuntu (should work with 10.x, 11.x and 12.x)
(internet connection required)
Run in the Terminal:
Code:
sudo add-apt-repository ppa:nilarimogard/webupd8
sudo apt-get update
sudo apt-get install android-tools-adb android-tools-fastboot
Reboot isn't required.
Save all the flashing files on home folder, or navigate with "cd" to your files.
Happy flashing!
For the case it doesn't work after this, try THIS method which is little bit more complicated, but should work in actually all Linux OS variants.
Click to expand...
Click to collapse
INSTALL ADB AND FASTBOOT :
To fix a bootloop, for unbricking, to root, to unlock/relock the bootloader, for flashing of a stock firmware, kernel, or recovery: for all those things fastboot must work reliably. And in Windows, it sometimes simply won't work at all, whatever you try.
Windows OS is complicated. And needs drivers at all times. Successful use of ADB or Fastboot with Windows is totally dependent on perfectly installed drivers. And there we have the source of many problems. As way around all those in fact Windows related promblems, we will use here Linux instead of Windows. Linux needs no drivers. Linux is free. Linux needs no antivirus software. Linux gets optimized day by day. Your Android device is Linux based.
After reading how many users encounter day by day countless issues by attempt to run fastboot and ADB commands (especially here in Nexus threads), I've decided to make this guide. There are some longer and complicated guides here around. I like fast, easy and secure way- so I hope this will help.
STEP 1: how to run Linux on Windows PC
There are many variants of Linux OS, but to keep the things really simple I will refer here entirely to the most popular variant of Linux: Ubuntu.
Windows users have three common ways to run Ubuntu on their Windows PC:
OPTION 1: installing Ubuntu permanently (my personal preference)
Pros: you will gain Ubuntu OS besides Windows and possibility for dual-boot. Reboot between Windows and Ubuntu takes about 1 minute. Full functionality of both operating systems.
Cons: in very seldom cases the installation of Ubuntu doesn't work flawless and if Ubuntu gets installed on the same HDD, Windows OS can get partly damaged or unusable, or has to be re-installed. Part of HDD memory space has to be permanently reserved for Ubuntu (min. 10GB recommended) and won't be accessible from Windows anymore.
OPTION 2: running Ubuntu from bootable live-CD
Pros: Ubuntu won't get physically installed, it runs 100% virtually from bootable live-CD and uses only RAM of the PC. People who don't desire to install Ubuntu permanently will have no changes on their PSs. No potential risks due to unsuccessful installation. In general, works with most of the computers.
Cons: No data or settings can get permanently saved in Ubuntu, especially Linux novices will have to learn quickly about setting the permissions: each time again after restarting Ubuntu session from the live-CD. Ubuntu is considerably slower this way.
OPTION 3: running Ubuntu from VirtualBox (in your Windows OS)
Pros: easy way to run Ubuntu directly from Windows in kind of "sandbox"
Cons: doesn't work well with some PCs
STEP 2: INSTALLING FASTBOOT & ADB IN UBUNTU
Now when your Linux OS is working, we can finally go for it!
Make sure to have internet connection
open the Software Center in Ubuntu
install openjdk-7-jdk
install Eclipse
download adt-bundle for your respective OS (32-bit or 64-bit version) from http://developer.android.com/sdk/index.html
extract the folder and paste the extracted folder to prefered folder and rename it to your prefered folder name
run the Terminal and navigate (cd) to the unzipped folder into "platform-tools"
Example for novices: I have pasted my extracted adt-bundle folder under "Home" and renamed it to "SDK", so I have to navigate to my platform-tools this way:
Code:
cd /home/tetakpatak/SDK/sdk/platform-tools
After this, you should be able to execute all the ADB and fastboot commands
Now just mind to paste all the files you desire to flash or push or sideload into your "platform-tools" folder!
Happy flashing!
Click to expand...
Click to collapse
DOWNLOAD LINKS
Ubuntu OS: DOWNLOAD HERE
Virtual Box: DOWNLOAD HERE
Warning: VirtualBox supports only the 32-bit version of Ubuntu, so also owners of 64-bit PC-systems should make sure to download the 32-bit version of Ubuntu, and not the 64-bit version!
ADDITIONAL INFORMATION AND USEFUL LINKS
Checklist for ADB:
for using in Android OS make sure to enable USB debugging under "developer options"
ADB works in Android OS and in the recovery mode, but not in the bootloader mode
make always sure at the very beginning that your ADB connection works by typing "adb devices" (the response must include a serial number on the left and "device" right after it!)
Basics about ADB: check for example this excellent ADB guide
Checklist for fastboot:
fastboot commands can be executed only in bootloader mode
fastboot commands will work also if USB debugging was disabled
make always sure at the very beginning that your fastboot connection works by typing "fastboot devices" (the response must include a serial number on the left and "fastboot" right after it!)
by using fastboot for the first time on a PC or Android device, never start with bootloader flashing! Missmatched bootloader flashing can hard-brick the device. Rather first execute "fastboot reboot-bootloader" and try to flash a kernel or recovery to make sure flashing commands are working and the connection is established.
Flashing with fastboot (example Nexus 7 v2012): check this excellent guide by @comminus
My self made video of flashing a full factory image with manually done fastboot commands in real time (example Nexus 7 v2012):
Click to expand...
Click to collapse
Please use "thanks" button beyond my posts if you find this guide useful. I've spent my time to help you, who read this.

TROUBLESHOOTING:
Occasionally, the device's storage doesn't get recognized in Ubuntu (something like MTP Camera error, can't mount camera, or so). The source of this problem is, that Ubuntu 12.04 doesn't support MTP natively yet, hopefully 13.04 will do.
This is the solution that should work with Ubuntu 12.04, enter in Ubuntu Terminal following:
Code:
sudo add-apt-repository ppa:langdalepl/gvfs-mtp
sudo apt-get update
sudo apt-get install gvfs
restart your PC, now everything should work (enable USB debugging if it doesn't)
If this method wasn't successful, you can try alternatively to do the same thing with these two repos:
Code:
sudo add-apt-repository ppa:webupd8team/unstable
sudo apt-get update
sudo apt-get install go-mtpfs
After the last command just reboot the PC
Also this repo could work:
Code:
sudo add-apt-repository ppa:langdalepl/gvfs-mtp
sudo apt-get update
sudo apt-get dist-upgrade
If none of both repos works and you want to uninstall both of them, just enter:
Code:
sudo ppa-purge ppa:webupd8team/unstable
sudo ppa-purge ppa:langdalepl/gvfs-mtp

great tutorial!
tetakpatak said:
reserved
Click to expand...
Click to collapse
Hey brother, great tutorial...
I know this will help so many people in the future and i love to see anything linux based! I have been using linux/bsd based operating systems for years and i love the way linux and android work together!
Take care my friend and thanks again for all of the hard work.
-droidshadow

You can also put your computer in test mode which bypasses msm kernel mode code signing policy. This will enable the ability to install the drivers needed. From the administration profile on your PC open a command prompt and type
Bcdedit.exe -set TESTSIGNING ON
Then restart your computer.
Edit: This is for Windows 7 X64 and Windows 8 users alike.
Sent from my Nexus 7 Flo running CM 11 4.4.2 with ElementalX Kernel using XDA Premium 4 mobile app

I keep getting a keyserver error when entering first command.

Got it to install the problem I see now is with java

Steve One said:
I keep getting a keyserver error when entering first command.
Click to expand...
Click to collapse
Which Linux version do you use?
tetakpatalked from Nexus 7 flo

tetakpatak said:
Which Linux version do you use?
tetakpatalked from Nexus 7 flo
Click to expand...
Click to collapse
Mint15

Here's another shot

Steve One said:
Here's another shot
Click to expand...
Click to collapse
Please google a bit, I think you need another repo for Mint 15, I think I saw it somewhere in www last week. Sorry, I can't research right now until end of week.
tetakpatalked from P5110

tetakpatak said:
Please google a bit, I think you need another repo for Mint 15, I think I saw it somewhere in www last week. Sorry, I can't research right now until end of week.
tetakpatalked from P5110
Click to expand...
Click to collapse
I'm truly stumped went from Windows Vista to all Linux to be able to use adb and still can't get it to recognize my device.
I installed the java 7 sdk but it still doesn't recognize my device..........guess I will try to get a Petra CD don't know what else to do ha ha and I thought this was the easy way to get adb to work. Thank you for your help kind Sir.

Steve One said:
I'm truly stumped went from Windows Vista to all Linux to be able to use adb and still can't get it to recognize my device.
I installed the java 7 sdk but it still doesn't recognize my device..........guess I will try to get a Petra CD don't know what else to do ha ha and I thought this was the easy way to get adb to work. Thank you for your help kind Sir.
Click to expand...
Click to collapse
It should definitely work with Ubuntu versions 10. 11. and 12.04 even without extra installing Java. I didn't try it with other Linux versions.
Which Linux did you install? Did you enable USB debugging?
Check in www as there are different repos available for ADB and fastboot.

Opening post updated: added procedure for enabling all ADB and fastboot functions in Ubuntu, for the short way with enabling fastboot only doesn't work with every Ubuntu version.
tetakpatalked from the legendary i9000