Database Info

How to compile Jelly Bean from Source [UBUNTU]

Hey there! I know the current situation in the i9003. We have a functional but not full ICS and now we need kernel 3.X to make everything work perfectly. Dhiru is working hard, he made a very very good work but he cannot do more until hillbeast finishes a bootable 3.0 kernel. A few hours ago, JB Source Code was released and now it can be compiled from source. I have read a good tutorial made by dastin1015 which explains how to do that. I say THIS IS NOT MY WORK (obviously) so credits go for him.
If somebody knows how to do that, please, try it. Probably we will be saving a lot of time for further development. Only to make it boot in a i9003 is a big step and a big contribution for the community. Here are the steps:
GUIDE - HOW TO COMPILE JB ON UBUNTU FROM SOURCE​
To compile Jellybean on Ubuntu I'm going to first give you steps to set up your computer to get this thing rolling. Also note that this appears to be a development preview source code.
This will NOT make a fully functional ROM, but will give you a place to start. Also I CANNOT fix every error you run into.
Note: The source download is approximately 6GB in size. You will need 25GB free to complete a single build, and up to 80GB (or more) for a full set of builds.
1) You need the following:
-JDK 6 if you wish to build Jellybean. You can download it from java.sun.com. Or:
Code:
$ sudo apt-get install sun-java6-jdk
-Python 2.4 -- 2.7, which you can download from python.org. Or:
Code:
$ sudo apt-get install python
-Git 1.7 or newer. You can find it at git-scm.com. Or:
Code:
$ sudo apt-get install git-core
2) Install required packages. 64-bit (recommended)
Code:
$ sudo apt-get install git-core gnupg flex bison gperf build-essential \
zip curl zlib1g-dev libc6-dev lib32ncurses5-dev ia32-libs \
x11proto-core-dev libx11-dev lib32readline5-dev lib32z-dev \
libgl1-mesa-dev g++-multilib mingw32 tofrodos python-markdown \
libxml2-utils
On newer versions of Ubuntu such as 11.10 you may need to do the following:
Code:
$ sudo ln -s /usr/lib/i386-linux-gnu/libX11.so.6 /usr/lib/i386-linux-gnu/libX11.so
Building on Ubuntu 12.04 is currently only experimentally supported and is not guaranteed to work on branches other than master.
Code:
$ sudo apt-get install git-core gnupg flex bison gperf build-essential \
zip curl libc6-dev libncurses5-dev:i386 x11proto-core-dev \
libx11-dev:i386 libreadline6-dev:i386 libgl1-mesa-glx:i386 \
libgl1-mesa-dev g++-multilib mingw32 openjdk-6-jdk tofrodos \
python-markdown libxml2-utils xsltproc zlib1g-dev:i386
$ sudo ln -s /usr/lib/i386-linux-gnu/mesa/libGL.so.1 /usr/lib/i386-linux-gnu/libGL.so
3) Configure your USB.
Code:
$ gksudo gedit /etc/udev/rules.d/51-android.rules
Inside of this blank text file insert:
Code:
#Acer
SUBSYSTEM=="usb", ATTR{idVendor}=="0502", MODE="0666"
#ASUS
SUBSYSTEM=="usb", ATTR{idVendor}=="0b05", MODE="0666"
#Dell
SUBSYSTEM=="usb", ATTR{idVendor}=="413c", MODE="0666"
#Foxconn
SUBSYSTEM=="usb", ATTR{idVendor}=="0489", MODE="0666"
#Garmin-Asus
SUBSYSTEM=="usb", ATTR{idVendor}=="091E", MODE="0666"
#Google
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", MODE="0666"
#HTC
SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", MODE="0666"
#Huawei
SUBSYSTEM=="usb", ATTR{idVendor}=="12d1", MODE="0666"
#K-Touch
SUBSYSTEM=="usb", ATTR{idVendor}=="24e3", MODE="0666"
#KT Tech
SUBSYSTEM=="usb", ATTR{idVendor}=="2116", MODE="0666"
#Kyocera
SUBSYSTEM=="usb", ATTR{idVendor}=="0482", MODE="0666"
#Lenevo
SUBSYSTEM=="usb", ATTR{idVendor}=="17EF", MODE="0666"
#LG
SUBSYSTEM=="usb", ATTR{idVendor}=="1004", MODE="0666"
#Motorola
SUBSYSTEM=="usb", ATTR{idVendor}=="22b8", MODE="0666"
#NEC
SUBSYSTEM=="usb", ATTR{idVendor}=="0409", MODE="0666"
#Nook
SUBSYSTEM=="usb", ATTR{idVendor}=="2080", MODE="0666"
#Nvidia
SUBSYSTEM=="usb", ATTR{idVendor}=="0955", MODE="0666"
#OTGV
SUBSYSTEM=="usb", ATTR{idVendor}=="2257", MODE="0666"
#Pantech
SUBSYSTEM=="usb", ATTR{idVendor}=="10A9", MODE="0666"
#Philips
SUBSYSTEM=="usb", ATTR{idVendor}=="0471", MODE="0666"
#PMC-Sierra
SUBSYSTEM=="usb", ATTR{idVendor}=="04da", MODE="0666"
#Qualcomm
SUBSYSTEM=="usb", ATTR{idVendor}=="05c6", MODE="0666"
#SK Telesys
SUBSYSTEM=="usb", ATTR{idVendor}=="1f53", MODE="0666"
#Samsung
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", MODE="0666"
#Sharp
SUBSYSTEM=="usb", ATTR{idVendor}=="04dd", MODE="0666"
#Sony Ericsson
SUBSYSTEM=="usb", ATTR{idVendor}=="0fce", MODE="0666"
#Toshiba
SUBSYSTEM=="usb", ATTR{idVendor}=="0930", MODE="0666"
#ZTE
SUBSYSTEM=="usb", ATTR{idVendor}=="19D2", MODE="0666"
4) Save the file and close it and then issue this command:
Code:
$ sudo chmod a+r /etc/udev/rules.d/51-android.rules
5) Install the repo:
Code:
$ mkdir ~/bin
$ PATH=~/bin:$PATH
$ curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo
$ chmod a+x ~/bin/repo
6) Initialize the repo:
Code:
$ mkdir WORKING_DIRECTORY
$ cd WORKING_DIRECTORY
$ repo init -u https://android.googlesource.com/platform/manifest -b jb-dev
7) When prompted, enter your real name and email address.
8) Gather the files:
Code:
$ repo sync
9) Compiling:
Code:
$ source build/envsetup.sh
Or:
Code:
$ . build/envsetup.sh
10) Issue:
Code:
$ lunch
11) Pick your poison.
12) Now issue (The '#' is the number of cores your processor has plus 1, ex. I have a dual core processor so I type 'make -j3':
Code:
$ make -j#
~How To Add A Device To The List~
1) Find the github for your device you wish to add. (For me it is the HTC Evo 3D CDMA)
2) Now navigate to the location you are going clone the device tree to:
Code:
$ cd WORKING_DIRECTORY/device
$ mkdir htc
3) Clone the github device tree from remote to local: (The shooter would be whatever you want that folder to be named so make sure it is whatever standard name would be for your device, example: Nexus One [passion], Nexus S [crespo], Motorola Droid [sholes], HTC Incredible [inc], etc.)
Code:
$ git clone git://github.com/CyanogenMod/android_device_htc_shooter.git shooter
4) Now navigate into the folder:
Code:
$ cd shooter
5) Connect phone to computer and make sure USB debugging is enabled and you have adb set up.
6) Extract Device Proprietary Files:
Code:
$ ./extract-files.sh
7) Navigate back to your home directory for building:
Code:
$ cd ~/WORKING_DIRECTORY
8) Prepare To Compile:
Code:
$ source build/envsetup.sh
Or:
Code:
$ . build/envsetup.sh
9) Get your list of devices:
Code:
$ lunch
10) Pick your poison.
11) Now compile:
Code:
$ make -j#
Or for a flashable zip:
Code:
$ make -j# otapackage
~NOTE~
If you are running into issues such as:
Code:
Which would you like? [full-eng] 5
build/core/product_config.mk:209: *** No matches for product "full_shooter". Stop.
Device shooter not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).
Repository for shooter not found in the CyanogenMod Github repository list. If this is in error, you may need to manually add it to your local_manifest.xml.
build/core/product_config.mk:209: *** No matches for product "full_shooter". Stop.
** Don't have a product spec for: 'full_shooter'
** Do you have the right repo manifest?
What you need to do is to edit your blob to match the PRODUCT_NAME to the file name. For example with mine I have full_shooter.mk therefore in this file I need to have PRODUCT_NAME to match it. Whatever error it is looking for you just need to change the PRODUCT_NAME line to match what the error shows.
Source​
Hope it helps for our development, and again, if u know how to do that, please try
Click to expand...
Click to collapse

luiseteyo said:
Hey there! I know the current situation in the i9003. We have a functional but not full ICS and now we need kernel 3.X to make everything work perfectly. Dhiru is working hard, he made a very very good work but he cannot do more until hillbeast finishes a bootable 3.0 kernel. A few hours ago, JB Source Code was released and now it can be compiled from source. I have read a good tutorial made by dastin1015 which explains how to do that. I say THIS IS NOT MY WORK (obviously) so credits go for him.
If somebody knows how to do that, please, try it. Probably we will be saving a lot of time for further development. Only to make it boot in a i9003 is a big step and a big contribution for the community. Here are the steps:
GUIDE - HOW TO COMPILE JB ON UBUNTU FROM SOURCE​
To compile Jellybean on Ubuntu I'm going to first give you steps to set up your computer to get this thing rolling. Also note that this appears to be a development preview source code.
This will NOT make a fully functional ROM, but will give you a place to start. Also I CANNOT fix every error you run into.
Note: The source download is approximately 6GB in size. You will need 25GB free to complete a single build, and up to 80GB (or more) for a full set of builds.
1) You need the following:
-JDK 6 if you wish to build Jellybean. You can download it from java.sun.com. Or:
Code:
$ sudo apt-get install sun-java6-jdk
-Python 2.4 -- 2.7, which you can download from python.org. Or:
Code:
$ sudo apt-get install python
-Git 1.7 or newer. You can find it at git-scm.com. Or:
Code:
$ sudo apt-get install git-core
2) Install required packages. 64-bit (recommended)
Code:
$ sudo apt-get install git-core gnupg flex bison gperf build-essential \
zip curl zlib1g-dev libc6-dev lib32ncurses5-dev ia32-libs \
x11proto-core-dev libx11-dev lib32readline5-dev lib32z-dev \
libgl1-mesa-dev g++-multilib mingw32 tofrodos python-markdown \
libxml2-utils
On newer versions of Ubuntu such as 11.10 you may need to do the following:
Code:
$ sudo ln -s /usr/lib/i386-linux-gnu/libX11.so.6 /usr/lib/i386-linux-gnu/libX11.so
Building on Ubuntu 12.04 is currently only experimentally supported and is not guaranteed to work on branches other than master.
Code:
$ sudo apt-get install git-core gnupg flex bison gperf build-essential \
zip curl libc6-dev libncurses5-dev:i386 x11proto-core-dev \
libx11-dev:i386 libreadline6-dev:i386 libgl1-mesa-glx:i386 \
libgl1-mesa-dev g++-multilib mingw32 openjdk-6-jdk tofrodos \
python-markdown libxml2-utils xsltproc zlib1g-dev:i386
$ sudo ln -s /usr/lib/i386-linux-gnu/mesa/libGL.so.1 /usr/lib/i386-linux-gnu/libGL.so
3) Configure your USB.
Code:
$ gksudo gedit /etc/udev/rules.d/51-android.rules
Inside of this blank text file insert:
Code:
#Acer
SUBSYSTEM=="usb", ATTR{idVendor}=="0502", MODE="0666"
#ASUS
SUBSYSTEM=="usb", ATTR{idVendor}=="0b05", MODE="0666"
#Dell
SUBSYSTEM=="usb", ATTR{idVendor}=="413c", MODE="0666"
#Foxconn
SUBSYSTEM=="usb", ATTR{idVendor}=="0489", MODE="0666"
#Garmin-Asus
SUBSYSTEM=="usb", ATTR{idVendor}=="091E", MODE="0666"
#Google
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", MODE="0666"
#HTC
SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", MODE="0666"
#Huawei
SUBSYSTEM=="usb", ATTR{idVendor}=="12d1", MODE="0666"
#K-Touch
SUBSYSTEM=="usb", ATTR{idVendor}=="24e3", MODE="0666"
#KT Tech
SUBSYSTEM=="usb", ATTR{idVendor}=="2116", MODE="0666"
#Kyocera
SUBSYSTEM=="usb", ATTR{idVendor}=="0482", MODE="0666"
#Lenevo
SUBSYSTEM=="usb", ATTR{idVendor}=="17EF", MODE="0666"
#LG
SUBSYSTEM=="usb", ATTR{idVendor}=="1004", MODE="0666"
#Motorola
SUBSYSTEM=="usb", ATTR{idVendor}=="22b8", MODE="0666"
#NEC
SUBSYSTEM=="usb", ATTR{idVendor}=="0409", MODE="0666"
#Nook
SUBSYSTEM=="usb", ATTR{idVendor}=="2080", MODE="0666"
#Nvidia
SUBSYSTEM=="usb", ATTR{idVendor}=="0955", MODE="0666"
#OTGV
SUBSYSTEM=="usb", ATTR{idVendor}=="2257", MODE="0666"
#Pantech
SUBSYSTEM=="usb", ATTR{idVendor}=="10A9", MODE="0666"
#Philips
SUBSYSTEM=="usb", ATTR{idVendor}=="0471", MODE="0666"
#PMC-Sierra
SUBSYSTEM=="usb", ATTR{idVendor}=="04da", MODE="0666"
#Qualcomm
SUBSYSTEM=="usb", ATTR{idVendor}=="05c6", MODE="0666"
#SK Telesys
SUBSYSTEM=="usb", ATTR{idVendor}=="1f53", MODE="0666"
#Samsung
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", MODE="0666"
#Sharp
SUBSYSTEM=="usb", ATTR{idVendor}=="04dd", MODE="0666"
#Sony Ericsson
SUBSYSTEM=="usb", ATTR{idVendor}=="0fce", MODE="0666"
#Toshiba
SUBSYSTEM=="usb", ATTR{idVendor}=="0930", MODE="0666"
#ZTE
SUBSYSTEM=="usb", ATTR{idVendor}=="19D2", MODE="0666"
4) Save the file and close it and then issue this command:
Code:
$ sudo chmod a+r /etc/udev/rules.d/51-android.rules
5) Install the repo:
Code:
$ mkdir ~/bin
$ PATH=~/bin:$PATH
$ curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo
$ chmod a+x ~/bin/repo
6) Initialize the repo:
Code:
$ mkdir WORKING_DIRECTORY
$ cd WORKING_DIRECTORY
$ repo init -u https://android.googlesource.com/platform/manifest -b jb-dev
7) When prompted, enter your real name and email address.
8) Gather the files:
Code:
$ repo sync
9) Compiling:
Code:
$ source build/envsetup.sh
Or:
Code:
$ . build/envsetup.sh
10) Issue:
Code:
$ lunch
11) Pick your poison.
12) Now issue (The '#' is the number of cores your processor has plus 1, ex. I have a dual core processor so I type 'make -j3':
Code:
$ make -j#
~How To Add A Device To The List~
1) Find the github for your device you wish to add. (For me it is the HTC Evo 3D CDMA)
2) Now navigate to the location you are going clone the device tree to:
Code:
$ cd WORKING_DIRECTORY/device
$ mkdir htc
3) Clone the github device tree from remote to local: (The shooter would be whatever you want that folder to be named so make sure it is whatever standard name would be for your device, example: Nexus One [passion], Nexus S [crespo], Motorola Droid [sholes], HTC Incredible [inc], etc.)
Code:
$ git clone git://github.com/CyanogenMod/android_device_htc_shooter.git shooter
4) Now navigate into the folder:
Code:
$ cd shooter
5) Connect phone to computer and make sure USB debugging is enabled and you have adb set up.
6) Extract Device Proprietary Files:
Code:
$ ./extract-files.sh
7) Navigate back to your home directory for building:
Code:
$ cd ~/WORKING_DIRECTORY
8) Prepare To Compile:
Code:
$ source build/envsetup.sh
Or:
Code:
$ . build/envsetup.sh
9) Get your list of devices:
Code:
$ lunch
10) Pick your poison.
11) Now compile:
Code:
$ make -j#
Or for a flashable zip:
Code:
$ make -j# otapackage
~NOTE~
If you are running into issues such as:
Code:
Which would you like? [full-eng] 5
build/core/product_config.mk:209: *** No matches for product "full_shooter". Stop.
Device shooter not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).
Repository for shooter not found in the CyanogenMod Github repository list. If this is in error, you may need to manually add it to your local_manifest.xml.
build/core/product_config.mk:209: *** No matches for product "full_shooter". Stop.
** Don't have a product spec for: 'full_shooter'
** Do you have the right repo manifest?
What you need to do is to edit your blob to match the PRODUCT_NAME to the file name. For example with mine I have full_shooter.mk therefore in this file I need to have PRODUCT_NAME to match it. Whatever error it is looking for you just need to change the PRODUCT_NAME line to match what the error shows.
Source​
Click to expand...
Click to collapse
Nice efforts! Liked!! You should continue maybe you can be the 1st dev of JB ^^

EDIT: Nevermind.

Anybody is going to try this? Almost all the big devices have a start build of JB. I can't do this so, isnt here any developer who wants to try this?

luiseteyo said:
Anybody is going to try this? Almost all the big devices have a start build of JB. I can't do this so, isnt here any developer who wants to try this?
Click to expand...
Click to collapse
Altough I'm not this device user, but i'm setting up my PC to start building for my LG-P500
And I must say that this is really a very helpful and the easiest guide available apart from the errors I'm going to face while building

luiseteyo said:
Anybody is going to try this? Almost all the big devices have a start build of JB. I can't do this so, isnt here any developer who wants to try this?
Click to expand...
Click to collapse
dhiru1602 said:
CM10 boots. Needs more testing.
Everything as that of CM9 seem to work fine with the only problem being the space on the system partition. It's too low to accommodate the full ROM and Jellybean Google apps. With the release of 3.0 kernel, we will resize the partitions, but as of now I have moved the applications to the data partition on a temporary basis.
Will make a release in a separate thread by the next few days.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=29018786&postcount=2809

shriomman said:
http://forum.xda-developers.com/showpost.php?p=29018786&postcount=2809
Click to expand...
Click to collapse
Yes i know
Sent from my iPad using Tapatalk HD

Workaround for repo syntax errors
For those getting a syntax error on
Code:
repo init
It's because of Python3 being listed as Python in /usr/bin.
A temporary workaround is to symlink python2 in place of python 3.
Code:
$ mkdir ~/bin
$ ln -s /usr/bin/python2 ~/bin/python
$ export PATH=~/bin:$PATH
Check to see if it worked
Code:
$ which python
And if it returns the binary in ~/bin/python it worked
The solution would either be to symlink python by default or rewrite repo in Python3.

[GUIDE] Fix Fastboot and USB

After writing my previous guide, i realized that a lot of people have had a fastboot problem when trying to flash cwm and adb problems while in cwm. After i flashed aosp, i realized that I lost recovery, and as i tried to reflash it, i had the problem as well.
Here's the fix.
1. Go to this github link and copy the text file.
2. Open up terminal and type in
sudo gedit /etc/udev/rules.d/51-android.rules​3. Replace what's in the folder with the the text in the file in github
4. Replace the text that says <username> with the username of your computer. (Don't erase the quotes!)
5. Find the line where it says "#adb protocol on the grouper (Nexus 7)"
6. Change the mode in the line under it to "0666"
It should look like this
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e42", MODE="0666", OWNER="your user name here"​7. Save the file
8. Type in terminal
sudo service udev restart
sudo killall adb ​
Now fastboot and adb should be fixed!
Do a fastboot devices to check in bootloader and/or do a check for adb in cwm by adb devices.
If this helped at all, don't forget to click thanks and rate 5 stars!
Special thanks to ptspts on blogspot for the adb fix and johnmurrayvi on github for the rules file!

Is missing recovery-from-boot.p related to this problem?

another way
5implelove said:
Is missing recovery-from-boot.p related to this problem?
Click to expand...
Click to collapse
I had the same exact problem and I found this-
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Browse to your SDK directory and futher into <SDK>\extras\google\usb_driver
Open android_winusb.inf in your favorite text editor.
Find the appropriate section Google.NTx86 if your on 32bit or Google.NTamd64 if your on 64bit (doesnt matter that your using intel chip). Now find the ";Google Nexus 7" line inside that section and you'll see a series of settings below. Add the following lines at the end of that block.
Code:
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4E44&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D001
These are the identifiers for the Nexus 7 recovery and bootloader usb connections.
(Source- Napalm2) http://forum.xda-developers.com/showthread.php?t=1794203
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
This may be easier for some and it worked for me.

5implelove said:
Is missing recovery-from-boot.p related to this problem?
Click to expand...
Click to collapse
This is something on the phone, not a driver problem. In the Nexus 7, some people had to do it, some didn't. When i first got mine at IO, i had to, but i recently did it, and i didn't have to. It's hit or miss

Thanks bro ...you know a way for win users?? My problem is that I do not know why, the recovery unmount when I test some my mod on rom AOSP
I've update usb_driver from SDK and add the string on android_winusb.inf but nothing to do...now I have anxiety every flash that the recovery can unmount
Inviato dal mio Nexus 7 con Tapatalk 2

"3. Replace what's in the folder with the the text in the file in github"
sorry, where is the folder?
terminal as in the nexus7 am i right?

I've followed these instructions yet I still get ???????????????????? after running adb devices
I'm on Ubuntu 12.04

Ir0nLy0n said:
I've followed these instructions yet I still get ???????????????????? after running adb devices
I'm on Ubuntu 12.04
Click to expand...
Click to collapse
i've tidied it and added all modes...
follow the instructions in the OP but instead make 99-android.rules: (it loads later after everything is initialized)
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e42", MODE="0666", OWNER="your user name here" # 8GB version
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e44", MODE="0666", OWNER="your user name here" # 16GB version
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e40", MODE="0666", OWNER="your user name here" # Bootloader
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="d001", MODE="0666", OWNER="your user name here" # Recovery
You can do this with ANY usb hardware. Just use for example:
Code:
[email protected] ~ $ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 005 Device 002: ID 058f:6254 Alcor Micro Corp. USB Hub
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 003 Device 002: ID 08bb:2902 Texas Instruments Japan PCM2902 Audio Codec
Bus 003 Device 003: ID 04e8:329f Samsung Electronics Co., Ltd
Bus 001 Device 034: ID 18d1:d001 Google Inc.
Bus 002 Device 003: ID 1b1c:1b31 Corsair
Bus 002 Device 004: ID 08bb:2902 Texas Instruments Japan PCM2902 Audio Codec
[email protected] ~ $
My nexus 7 is attached and in recovery mode
Hope this helps. Please hit Thanks if it does
kodabmx

kodabmx said:
follow the instructions in the OP but instead make 99-android.rules: (it loads later after everything is initialized)
Click to expand...
Click to collapse
This worked for me. I also added the code for the Galaxy Nexus. After a quick reboot, I was able to execute both ADB and Fastboot commands without being in the same folder and no permission issues! Perfect

i am at a loss. I am on ubuntu 12.04 fully updated as of 8-22-2012. my 51 and 99 android.rules file looks like this:
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e42", MODE="0666", OWNER="phillip" # 8GB version
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e44", MODE="0666", OWNER="phillip" # 16GB version
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e40", MODE="0666", OWNER="phillip" # Bootloader
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="d001", MODE="0666", OWNER="phillip" # Recovery
# fastboot protocol on the grouper (Nexus 7)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e40", MODE="0600", OWNER="phillip"
I have tried it with and without the last subsystem. but no matter what i cant get my system to see my 7 in bootloader. in normal and recovery it works. any ideas?

ngc604 said:
i am at a loss. I am on ubuntu 12.04 fully updated as of 8-22-2012. my 51 and 99 android.rules file looks like this:
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e42", MODE="0666", OWNER="phillip" # 8GB version
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e44", MODE="0666", OWNER="phillip" # 16GB version
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e40", MODE="0666", OWNER="phillip" # Bootloader
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="d001", MODE="0666", OWNER="phillip" # Recovery
# fastboot protocol on the grouper (Nexus 7)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e40", MODE="0600", OWNER="phillip"
I have tried it with and without the last subsystem. but no matter what i cant get my system to see my 7 in bootloader. in normal and recovery it works. any ideas?
Click to expand...
Click to collapse
Try changing the mode for fastboot to 666. That might work.
Sent from my Nexus 7 using XDA Premium HD app

i figured it out. i was using the adb command and not the fastboot command. I forgot the 7 goes into fastboot right away.
just posting this in case someone else makes that same mistake.

Thanks for the follow-up on this. Here you say,
3. Replace what's in the folder with the the text in the file in github
Click to expand...
Click to collapse
Don't you mean "replace what is in this FILE?"
And that file was empty for me. Does that mean there is a problem? I still have insufficient permissions back on the original page:
adb devices
List of devices attached
???????????? no permissions
fastboot devices
gives no response, no error either.
fastboot
does give me the listing of fastboot usage and options.
UPDATE: (I also followed this guide: http://rootzwiki.com/topic/28544-guide-nexus-7-bootloadersrecoveriesrootback-to-stock/page__pid__981123__st__110#entry981123 , but had similar results as here)
Even though I could not complete this process, I do apparently have root! Google Play has SuperSU listed as an app "Up to date", ditto for Root Checker by joeykrim. And in Root Checker, when I click "Check root", "Verify Root Access", SuperSU does pop up and ask if it should be granted root, I say yes, and Root Checker says I have root.
I did manage to install the SuperSU app once or twice in my recent attempts. The first time I rebooted, I am sure I did not have root. Maybe the last two times I tried it, I did get root. About tablet says:
Code:
Android version
4.1.1
Kernel version
3.1.10-g52027f9
[email protected])
#1 SMP PREEMPT Thu Jun 28 16:19:26 PDT 2012
Build number
JRO03S
As far as root goes, am I all set? I don't care about using a different ROM or bootloader. I just want to have more control in customizing -- and using Titanium Backup -- and still get the updates when they roll out. Is it all good?

FadedLite said:
After writing my previous guide, i realized that a lot of people have had a fastboot problem when trying to flash cwm and adb problems while in cwm. After i flashed aosp, i realized that I lost recovery, and as i tried to reflash it, i had the problem as well.
Here's the fix.
1. Go to this github link and copy the text file.
2. Open up terminal and type in
sudo gedit /etc/udev/rules.d/51-android.rules​3. Replace what's in the folder with the the text in the file in github
4. Replace the text that says <username> with the username of your computer. (Don't erase the quotes!)
5. Find the line where it says "#adb protocol on the grouper (Nexus 7)"
6. Change the mode in the line under it to "0666"
It should look like this
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e42", MODE="0666", OWNER="your user name here"​7. Save the file
8. Type in terminal
sudo service udev restart
sudo killall adb ​
Now fastboot and adb should be fixed!
Do a fastboot devices to check in bootloader and/or do a check for adb in cwm by adb devices.
If this helped at all, don't forget to click thanks and rate 5 stars!
Special thanks to ptspts on blogspot for the adb fix and johnmurrayvi on github for the rules file!
Click to expand...
Click to collapse
thanks for the tips,i already have this on my linux mahcine (like said the source.android.com under "configuring usb access")because it's requested if you want to build something,already did that some time ago for gnex.Anyway,also after did that times ago,i have little problems with fastboot and n7,adb works well instaed.i'll see what i can do.thanks!

This actually works on any device. All you have to do is replace the vendor and product id with that of the specific device.
I was having trouble seeing my HTC Evo 3D in fastboot (it was already set up with a device/product id for adb), so did a google search and landed on this page. All you have to do is type
Code:
lsusb
and see the vendor and product values (will be in the format 0abc:def1 - not the exact string but similar format). The first part is the vendor ID and the second part is the product ID. It will differ based on the mode your phone is in (bootloader, normal booted phone in dev debug mode, tethering etc). So you have to set up a line for each of these modes if you want to execute fastboot, adb etc type of commands on it.

chmod
might want to chmod the rules file after you save it and before restarting the udev service.. simple stuff can hang up the casual user.
Regards,
Rob
for me:
chmod a+rx /etc/udev/rules.d/70-persistant-android.rules
(still as root) [or add sudo in front]
a good page for reading up on udev stuff:
http://forums.team-nocturnal.com/sh...u-Linux-12-04-11-10-LTS-32bit-64-April-5-2012

Here is my 99-android.rules, pop this in, chmod a+rx it and restart udev and adb should give you a root shell no matter what mode your Nexus 7 is in. It also has defs for mtp. I used Linux Mint 14 with the android-tools-adb/android-tools-fastboot packages. It is important to have the mode 0600 entries, as they are vital for adb root access. Cheers!
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e42", MODE="0666", OWNER="your username here"
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e41", MODE="0666", OWNER="your username here"
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e40", MODE="0666", OWNER="your username here"
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="d001", MODE="0666", OWNER="your username here"
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e42", MODE="0600", OWNER="your username here"
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e41", MODE="0600", OWNER="your username here"
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e40", MODE="0600", OWNER="your username here"
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="d001", MODE="0600", OWNER="your username here"

HTC ONE XL an ADB problems under Ubuntu 12.04

Hi,
i've got a problem with my One XL during the correct installation of adb on my Unbuntu 12.04 system. When I start my phone in recovery mode adb detects my phone correct:
[email protected]:~$ adb devices
List of devices attached
HT29MW304980 recovery
Click to expand...
Click to collapse
But when I start my phone in the normal way adb doesn't detect it and the list of attached devices ist empty:
[email protected]:~$ adb devices
List of devices attached
[email protected]:~$ lsusb
Bus 001 Device 002: ID 1c7a:0801 LighTuning Technology Inc. Fingerprint Reader
Bus 002 Device 042: ID 0bb4:0f91 HTC (High Tech Computer Corp.)
Bus 002 Device 003: ID 064e:a117 Suyin Corp.
Bus 003 Device 002: ID 0a5c:2101 Broadcom Corp. BCM2045 Bluetooth
Bus 004 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Click to expand...
Click to collapse
99-andrid.rules looks like this:
#Acer
SUBSYSTEM=="usb", SYSFS{idVendor}=="0502", MODE="0666"
#Dell
SUBSYSTEM=="usb", SYSFS{idVendor}=="413c", MODE="0666"
#Foxconn
SUBSYSTEM=="usb", SYSFS{idVendor}=="0489", MODE="0666"
#Garmin-Asus
SUBSYSTEM=="usb", SYSFS{idVendor}=="091E", MODE="0666"
#Google
SUBSYSTEM=="usb", SYSFS{idVendor}=="18d1", MODE="0666"
#HTC
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
#Huawei
SUBSYSTEM=="usb", SYSFS{idVendor}=="12d1", MODE="0666"
#Kyocera
SUBSYSTEM=="usb", SYSFS{idVendor}=="0482", MODE="0666"
#LG
SUBSYSTEM=="usb", SYSFS{idVendor}=="1004", MODE="0666"
#Motorola
SUBSYSTEM=="usb", SYSFS{idVendor}=="22b8", MODE="0666"
#Nvidia
SUBSYSTEM=="usb", SYSFS{idVendor}=="0955", MODE="0666"
#Pantech
SUBSYSTEM=="usb", SYSFS{idVendor}=="10A9", MODE="0666"
#Samsung
SUBSYSTEM=="usb", SYSFS{idVendor}=="04e8", MODE="0666"
#Sharp
SUBSYSTEM=="usb", SYSFS{idVendor}=="04dd", MODE="0666"
#Sony Ericsson
SUBSYSTEM=="usb", SYSFS{idVendor}=="0fce", MODE="0666"
#ZTE
SUBSYSTEM=="usb", SYSFS{idVendor}=="19D2", MODE="0666"
Click to expand...
Click to collapse
Can anybody help me with this?

weltenspalter said:
Hi,
i've got a problem with my One XL during the correct installation of adb on my Unbuntu 12.04 system. When I start my phone in recovery mode adb detects my phone correct:
But when I start my phone in the normal way adb doesn't detect it and the list of attached devices ist empty:
99-andrid.rules looks like this:
Can anybody help me with this?
Click to expand...
Click to collapse
go into the settings -> developer options and ensure android debugging is turned on.

codeprimate said:
go into the settings -> developer options and ensure android debugging is turned on.
Click to expand...
Click to collapse
thx but android debugging is still turned on! so that cannot be the reason. Another suggestion?

weltenspalter said:
thx but android debugging is still turned on! so that cannot be the reason. Another suggestion?
Click to expand...
Click to collapse
sudo adb start-server

weltenspalter said:
Hi,
i've got a problem with my One XL during the correct installation of adb on my Unbuntu 12.04 system. When I start my phone in recovery mode adb detects my phone correct:
But when I start my phone in the normal way adb doesn't detect it and the list of attached devices ist empty:
99-andrid.rules looks like this:
Can anybody help me with this?
Click to expand...
Click to collapse
I had a similar problem after loading a rom that had usb debug checked by default. I unchecked it and rechecked it in the developer options and it fixed it for me. Not sure if its the same issue but worth a try.

Thats it. Now it works for me. THX
Sent from my MB632 using xda app-developers app

weltenspalter said:
Thats it. Now it works for me. THX
Click to expand...
Click to collapse
FWIW... this worked for me too... just had to uncheck then recheck "USB Debugging" in the "Developer Options" screen and it started working
Code:
$ adb devices
List of devices attached
HT2BDW300592 device
$ cat /etc/udev/rules.d/99-android.rules
SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", MODE="0666", GROUP="plugdev"
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 12.04.1 LTS
Release: 12.04
Codename: precise
$ adb shell
[email protected]:/ # cat /system/build.prop | grep product | grep -i ev
ro.product.model=HTC EVARE_UL
ro.product.model=EvitareUL
ro.product.name=evitareul
ro.product.device=evitareul
# ro.build.product is obsolete; use ro.product.device
ro.build.product=evitareul

[Pantech Burst] [Guide] Build your own AOKP_JB Rom

You must be running a 64bit version of Ubuntu.
If you attempt to build with 32bit I will not help as it is not supported.
This will NOT make a fully functional ROM, but will give you a place to start. Also I CANNOT fix every error you run into.
READ the entire OP and make sure to properly follow instructions. Don't forget to search the thread as your question may have already been answered.
Please use http://pastebin.com/ for all errors you run into. Posting a link is much easier than a long list of errors in the thread. Thank you.
You will need 25GB (or more) free to complete a single build, and up to 80GB (or more) for a full set of builds.
1) You need the following:
-JDK 6 if you wish to build Jellybean.
Code:
$ sudo apt-get install openjdk-6-jdk
-Python 2.4 -- 2.7, which you can download from python.org. Or:
Code:
$ sudo apt-get install python
-Git 1.7 or newer. You can find it at git-scm.com. Or:
Code:
$ sudo apt-get install git-core
-Java ™ SE Runtime Environment (build 1.6.0_37-b06)
-Android SDK:
Download the SDK here: http://developer.android.com/sdk/index.html
Extract the SDK and place it in your home directory.
I renamed my SDK to android-sdk to make it easier to navigate to.
Go to your home folder, press Ctrl+H to show hidden files, and open up your .bashrc file.
Add these lines at the bottom of the file:
Code:
# Android tools
export PATH=${PATH}:~/android-sdk/tools
export PATH=${PATH}:~/android-sdk/platform-tools
export PATH=${PATH}:~/bin
Find your .profile file and add this at the bottom of the file:
Code:
PATH="$HOME/android-sdk/tools:$HOME/android-sdk/platform-tools:$PATH"
You have now successfully installed the Android SDK.
To check for updates issue this into your terminal:
Code:
$ android
2) Install required packages.
Code:
$ sudo apt-get install git-core gnupg flex bison gperf build-essential \
zip curl zlib1g-dev libc6-dev lib32ncurses5-dev ia32-libs \
x11proto-core-dev libx11-dev lib32readline-gplv2-dev schedtool lib32z-dev \
libgl1-mesa-dev g++-multilib mingw32 tofrodos python-markdown \
libxml2-utils
On newer versions of Ubuntu such as 11.10 you may need to do the following:
Code:
$ sudo ln -s /usr/lib/i386-linux-gnu/libX11.so.6 /usr/lib/i386-linux-gnu/libX11.so
Building on Ubuntu 12.04 is currently only experimentally supported and is not guaranteed to work on branches other than master.
Code:
$ sudo apt-get install git-core gnupg flex bison gperf build-essential \
zip curl libc6-dev libncurses5-dev:i386 x11proto-core-dev \
libx11-dev:i386 libreadline6-dev:i386 libgl1-mesa-glx:i386 \
libgl1-mesa-dev g++-multilib mingw32 openjdk-6-jdk tofrodos \
python-markdown libxml2-utils xsltproc zlib1g-dev:i386 \
pngcrush optipng
$ sudo ln -s /usr/lib/i386-linux-gnu/mesa/libGL.so.1 /usr/lib/i386-linux-gnu/libGL.so
3) Configure your USB.
Code:
$ gksudo gedit /etc/udev/rules.d/51-android.rules
Inside of this blank text file insert:
Code:
#Acer
SUBSYSTEM=="usb", ATTR{idVendor}=="0502", MODE="0666"
#ASUS
SUBSYSTEM=="usb", ATTR{idVendor}=="0b05", MODE="0666"
#Dell
SUBSYSTEM=="usb", ATTR{idVendor}=="413c", MODE="0666"
#Foxconn
SUBSYSTEM=="usb", ATTR{idVendor}=="0489", MODE="0666"
#Garmin-Asus
SUBSYSTEM=="usb", ATTR{idVendor}=="091E", MODE="0666"
#Google
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", MODE="0666"
#HTC
SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", MODE="0666"
#Huawei
SUBSYSTEM=="usb", ATTR{idVendor}=="12d1", MODE="0666"
#K-Touch
SUBSYSTEM=="usb", ATTR{idVendor}=="24e3", MODE="0666"
#KT Tech
SUBSYSTEM=="usb", ATTR{idVendor}=="2116", MODE="0666"
#Kyocera
SUBSYSTEM=="usb", ATTR{idVendor}=="0482", MODE="0666"
#Lenevo
SUBSYSTEM=="usb", ATTR{idVendor}=="17EF", MODE="0666"
#LG
SUBSYSTEM=="usb", ATTR{idVendor}=="1004", MODE="0666"
#Motorola
SUBSYSTEM=="usb", ATTR{idVendor}=="22b8", MODE="0666"
#NEC
SUBSYSTEM=="usb", ATTR{idVendor}=="0409", MODE="0666"
#Nook
SUBSYSTEM=="usb", ATTR{idVendor}=="2080", MODE="0666"
#Nvidia
SUBSYSTEM=="usb", ATTR{idVendor}=="0955", MODE="0666"
#OTGV
SUBSYSTEM=="usb", ATTR{idVendor}=="2257", MODE="0666"
#Pantech
SUBSYSTEM=="usb", ATTR{idVendor}=="10A9", MODE="0666"
#Philips
SUBSYSTEM=="usb", ATTR{idVendor}=="0471", MODE="0666"
#PMC-Sierra
SUBSYSTEM=="usb", ATTR{idVendor}=="04da", MODE="0666"
#Qualcomm
SUBSYSTEM=="usb", ATTR{idVendor}=="05c6", MODE="0666"
#SK Telesys
SUBSYSTEM=="usb", ATTR{idVendor}=="1f53", MODE="0666"
#Samsung
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", MODE="0666"
#Sharp
SUBSYSTEM=="usb", ATTR{idVendor}=="04dd", MODE="0666"
#Sony Ericsson
SUBSYSTEM=="usb", ATTR{idVendor}=="0fce", MODE="0666"
#Toshiba
SUBSYSTEM=="usb", ATTR{idVendor}=="0930", MODE="0666"
#ZTE
SUBSYSTEM=="usb", ATTR{idVendor}=="19D2", MODE="0666"
4) Save the file and close it and then issue this command:
Code:
$ sudo chmod a+r /etc/udev/rules.d/51-android.rules
5) Install the repo:
Code:
$ mkdir ~/bin
$ PATH=~/bin:$PATH
$ curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo
$ chmod a+x ~/bin/repo
Create the following directories for where the AOKP repo will be stored and synced
Code:
mkdir ~/android
mkdir ~/android/aokp_jb
Move to our new AOKP directory
Code:
cd ~/android/aokp_jb
Initialize the AOKP repo and download the manifest
Code:
repo init -u git://github.com/AOKP/platform_manifest.git -b jb
Sync AOKP source
Code:
repo sync
Sit and wait for a long time. Nearing 10GB of source code now.
Open the aokp_jb_prestofiles.zip file and copy the contents to the following
Code:
aokp_jb/vendor/aokp/products/AndroidProducts.mk
aokp_jb/vendor/aokp/products/presto.mk
aokp_jb/.repo/manifest.xml
go back to ~/android/aokp_jb/
Sync source to pull files from TeamPresto and any changes to either aokp or TeamPresto's Github
Code:
repo sync
Start the build
This is probably the EASIEST part of all, simply copy/paste this command and walk away!
Code:
. build/envsetup.sh && brunch presto
Syncing the repo is dependent upon your Internet connection. It can take anywhere from 30 minutes to several hours to fully sync. Same thing goes for build times. Don't expect this to be short. If you have patience and have no build errors, you'll end up with a flashable zip in ~/aokp_jb/out/target/product/presto! Happy crack-flashing!

[Reserved]
Thank you goes to AOKP Team, Rootswiki, TeamPresto, and everyone else who's contributed.

kagedws6 said:
[Reserved]
Thank you goes to AOKP Team, Rootswiki, TeamPresto, and everyone else who's contributed.
Click to expand...
Click to collapse
**edit** at the moment this will build a bootable rom that is crazy fast but does not have access to wifi or the radio. still in progress

kagedws6 said:
**edit** at the moment this will build a bootable rom that is crazy fast but does not have access to wifi or the radio. still in progress
Click to expand...
Click to collapse
Well when I get home I will help with this. WE SHALL HAVE THE AOKP. And I realize that I have to back up all my windows stuff.......... To do a full install. Instead of dual boot. My hdd isn't big enough Lol.

hi
Is there a compiled .zip file that i can download because i don't have ubuntu, but i really want jb on m pantech burst.
Thanks

mustafa.ali61 said:
Is there a compiled .zip file that i can download because i don't have ubuntu, but i really want jb on m pantech burst.
Thanks
Click to expand...
Click to collapse
We are still getting the bugs worked out. This page is primarily for people who want to learn to build aokp from scratch and its got setup information to pull from the 3 github folders we are currently modifying to get everything working. right now wifi and data works but we are working on being to answer calls at the moment. any builds now would not be usable on a daily basis

[TOOL] [LINUX/MAC] Nexus Tools 2.8 (Featured by XDA)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Nexus Tools is an installer for the Android debug/development command-line tools ADB (Android Device Bridge) and Fastboot for Mac OS X and Linux. The script does not need to be downloaded, simply copy and paste this command into the terminal and run it to install ADB/Fastboot:
Code:
bash <(curl -s https://raw.githubusercontent.com/corbindavenport/nexus-tools/master/install.sh)
and this command to un-install Nexus Tools:
Code:
bash <(curl -s https://raw.githubusercontent.com/corbindavenport/nexus-tools/master/uninstall.sh)
Nexus Tools requires sudo privileges to install/uninstall the adb and fastboot tools to /usr/local/bin, so they can be run without typing the full directory. Nexus Tools is licensed under the GPLv3 license, and the source code is at the GitHub project below.
If you have a problem with Nexus Tools, leave a reply below or as an issue on the GitHub project!
GitHub Project
XDA News Article

Thanks, I was waiting for something like that.
Windows gets all the love and toolkits but our Macs are neglected?
Not anymore, thanks to you ^-^

1.1 Update
New in Nexus Tools 1.1:
Added uninstaller
Installer now checks for previously installed ADB/Fastboot
ABD and Fastboot are now variables in the script, so they can be easily changed
Minor script fixes and changes

1.2 Update
New in Nexus Tools 1.2:
Experimental support for Google Chrome OS
Installation works on Intel and ARM Chromebooks, as well as Chromium builds
Misc fixes for the install/uninstall script
Thanks to XDA users Quinny899 and KMyers for compiling ADB and Fastboot for Chrome OS (ARM + Intel), see the original thread here

Really nice shell script, thanks for that!
A small check if there are already an udev rules file present would be a nice addition. If not adding a new file (/etc/udev/rules.d/51-android.rules) with the following content:
Code:
SUBSYSTEM=="usb", ATTRS{idVendor}=="0bb4", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0e79", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0502", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0b05", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="413c", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0489", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="091e", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="18d1", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0bb4", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="12d1", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="24e3", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="2116", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0482", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="17ef", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="1004", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="22b8", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0409", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="2080", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0955", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="2257", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="10a9", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="1d4d", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0471", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="04da", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="05c6", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="1f53", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="04e8", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="04dd", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0fce", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0930", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="19d2", MODE="0666"
(speaking for the linux part here)
source: http://forum.xda-developers.com/showthread.php?t=2302780

Heart1010 said:
Really nice shell script, thanks for that!
A small check if there are already an udev rules file present would be a nice addition. If not adding a new file (/etc/udev/rules.d/51-android.rules) with the following content:
Code:
SUBSYSTEM=="usb", ATTRS{idVendor}=="0bb4", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0e79", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0502", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0b05", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="413c", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0489", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="091e", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="18d1", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0bb4", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="12d1", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="24e3", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="2116", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0482", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="17ef", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="1004", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="22b8", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0409", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="2080", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0955", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="2257", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="10a9", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="1d4d", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0471", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="04da", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="05c6", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="1f53", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="04e8", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="04dd", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0fce", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0930", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="19d2", MODE="0666"
(speaking for the linux part here)
source: http://forum.xda-developers.com/showthread.php?t=2302780
Click to expand...
Click to collapse
Thanks, I'll make sure to add this!

Nexus Tools 2.0
New in Nexus Tools 2.0:
Chrome OS and generic Linux both use same binaries
Detects processor platform for Linux (ARM or x86)
Downloads udev list for ADB
Script improvements/fixes
Thanks to XDA user edwinr29 for compiling updated ADB and Fastboot binaries for Chrome OS

Nexus Tools 2.1
New in Nexus Tools 2.1:
Added warning that ADB binaries for ARM CPUs are out of date (need to compile newer ones compatible with Android 4.2+)
Chrome OS/Linux installers now use the same code
Raspberry Pi now detected as ARM Linux (only tested with Raspbian distro)

Nexus Tools 2.2
New in Nexus Tools 2.2:
Fixes problems under Chrome OS
Improves error handling

corbin052198 said:
Nexus Tools is an installer for the Android debug/development command-line tools ADB (Android Device Bridge) and Fastboot for Mac OS X, Linux, and Google Chrome/Chromium OS. The script does not need to be downloaded, simply copy and paste this command into the terminal and run it to install Nexus Tools:
Code:
bash <(curl https://raw.github.com/corbindavenport/nexus-tools/master/install.sh)
and this command to un-install Nexus Tools:
HTML:
bash <(curl https://raw.github.com/corbindavenport/nexus-tools/master/uninstall.sh)
These commands will download the selected script and run it. The script will download the files it needs during runtime, so it requires an internet connection. The script works on both Mac OS X and Linux (as long as the curl package is installed).
Support for Google Chrome OS is experimental at this time, as I was only able to test it on a build of Chromium for x86 PCs. I don't have an actual Chromebook to test it on, but Nexus Tools should work correctly on both x86 and ARM Chromebooks.
Nexus Tools requires sudo privileges to install/uninstall the adb and fastboot tools to /usr/bin, so they can be run without typing the full directory. Nexus Tools is licensed under the GPLv3 license.
GitHub Project
XDA News Article
Reddit username: corbindavenport (for /r/Android mods)
Click to expand...
Click to collapse
[WARN] The ADB binaries for ARM are out of date, and do not work on Android 4.2.2+
About this warning, someone knows if theres some ADB binaries updated for ARM?
Thanks.

ayr-ton said:
[WARN] The ADB binaries for ARM are out of date, and do not work on Android 4.2.2+
About this warning, someone knows if theres some ADB binaries updated for ARM?
Thanks.
Click to expand...
Click to collapse
Debian has updated binaries for Debian on ARM, however it would mean that the script would also have to install some other binaries/libraries that I have yet to test on Chrome OS. I'm working out if the binaries would work if the script added the other libraries.

Nexus Tools 2.3
New in Nexus Tools 2.3:
Now displays diagnostic information if an error occurs
Updated links and command to work with GitHub's new link format
Generates directories for udev they do not exist
Fixed uninstall for Chrome OS
General bug fixes and code cleanup

corbin052198 said:
New in Nexus Tools 2.3:
Now displays diagnostic information if an error occurs
Updated links and command to work with GitHub's new link format
Generates directories for udev they do not exist
Fixed uninstall for Chrome OS
General bug fixes and code cleanup
Click to expand...
Click to collapse
any news on the updated binaries for arm chromebook? gave away my PC and now am looking to flash the android L developer preview.
Thanks

Nexus Tool
I cant do it I dont know the sudo thing please help email me at
[email protected]!!!!!!!!!

Acer c720 Chromebook
Trying to run script on a Acer c720 Chromebook. I'm in Developer Mode. This is the message after entering the script in the OP.
[email protected] / $ bash <(curl https://raw.githubusercontent.com/corbindavenport/nexus-tools/master/install.sh)
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 100 7211 100 7211 0 0 7892 0 --:--:-- --:--:-- --:--:-- 10199
[INFO] Nexus Tools 2.3
[INFO] Please enter sudo password for install.
Password:
[ OK ] Sudo access granted.
[INFO] Downloading ADB for Chrome OS [Intel CPU]...
[INFO] Downloading Fastboot for Chrome [Intel CPU]...
[INFO] Downloading udev list...
chmod: cannot access ‘/etc/udev/rules.d/51-android.rules’: No such file or directory
[INFO] Making ADB and Fastboot executable...
chmod: cannot access ‘/usr/bin/adb’: No such file or directory
chmod: cannot access ‘/usr/bin/fastboot’: No such file or directory
[ OK ] Done!
[INFO] Type adb or fastboot to run.
Any ideas? Has anyone succesfully install this on an Acer c720. Thanks.

gustavo_pr said:
Trying to run script on a Acer c720 Chromebook. I'm in Developer Mode. This is the message after entering the script in the OP.
[email protected] / $ bash <(curl https://raw.githubusercontent.com/corbindavenport/nexus-tools/master/install.sh)
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 100 7211 100 7211 0 0 7892 0 --:--:-- --:--:-- --:--:-- 10199
[INFO] Nexus Tools 2.3
[INFO] Please enter sudo password for install.
Password:
[ OK ] Sudo access granted.
[INFO] Downloading ADB for Chrome OS [Intel CPU]...
[INFO] Downloading Fastboot for Chrome [Intel CPU]...
[INFO] Downloading udev list...
chmod: cannot access ‘/etc/udev/rules.d/51-android.rules’: No such file or directory
[INFO] Making ADB and Fastboot executable...
chmod: cannot access ‘/usr/bin/adb’: No such file or directory
chmod: cannot access ‘/usr/bin/fastboot’: No such file or directory
[ OK ] Done!
[INFO] Type adb or fastboot to run.
Any ideas? Has anyone succesfully install this on an Acer c720. Thanks.
Click to expand...
Click to collapse
Tried running the scrpt myself on my Dell Chromebook 11. Yes I am a noob, I can grasp some basic commands. I would greatly appreciate your help and support. Nexus-tools is exactly what I want. Considered installing Crouton just for adb, however nexus tools seems to eliminate that.

Same issue here on my HP Chromebook 14...
Would be great with some help :cyclops:

Seems im kind of late to this thread but are lots of folks using this method? Any risks to doing it this way?

This is by far the easiest way imho! Still using it that way on every linux pc I have

Thanks. Trying it now!