FORUMS
Remove All Ads from XDA
H10 Turbo

[Guide] Building from source Any ROM

6,866 posts
Thanks Meter: 12,082
 
By Unjustified Dev, Recognized Developer on 21st March 2013, 07:03 PM
Post Reply Email Thread
I have been asked many times how do i build from source today I will attempt to tell you.

Preparation
First , you must be running at least Ubuntu 12.04 I recommend Ubuntu 12.10 you must use 64 bit.

Follow this guide on initializing a build environment for Ubuntu 12.10 Here

For Ubuntu 12.04 Here

Stop at Building cm-10 if your following guide for Ubuntu 12.04

Please don't continue until you follow the respective guide above


Setting up
Let's first create a directory in which we will build
Code:
mkdir -p ~/bin
mkdir -p ~/android/system
Initialize the repo command
Code:
curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo
chmod a+x ~/bin/repo
Putting the ~/bin directory in your path of execution
Code:
export PATH=${PATH}:~/bin

Downloading Source

Code:
cd ~/android/system/
Now we need to get the source code heres a few ROMs to try out

Code:
repo init -u git://github.com/PAC-man/android.git -b cm-10.1
repo init -u git://github.com/CyanogenMod/android.git -b cm-10.1
repo init -u https://github.com/TeamBAKED/platform_manifest.git -b jb-4.2
repo init -u git://github.com/ParanoidAndroid/manifest.git -b jellybean
repo init -u git://github.com/SlimRoms/platform_manifest.git -b jb4.2

You can only choose one



Now we need to obtain device proprietary files they are stored in local_manifest.xml
Code:
gedit ~/android/system/.repo/local_manifest.xml
copy and paste these lines in the file viewer that comes up and hit save
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
  <project name="CyanogenMod/android_kernel_samsung_epicmtd" path="kernel/samsung/epicmtd" remote="github" revision="cm-10.1" />
  <project name="CyanogenMod/android_hardware_samsung" path="hardware/samsung" remote="github" revision="cm-10.1" />
  <project name="CyanogenMod/android_device_samsung_epicmtd" path="device/samsung/epicmtd" remote="github" revision="cm-10.1" />
  <project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="cm-10.1" />
</manifest>
Now lets download the source

Code:
Repo sync -j#
# = number of threads cpu has


Unfinished this is a good start for now
The Following 15 Users Say Thank You to Unjustified Dev For This Useful Post: [ View ]
 
 
21st March 2013, 07:09 PM |#2  
Unjustified Dev's Avatar
OP Recognized Developer
Flag Memphis , TN
Thanks Meter: 12,082
 
Donate to Me
More
Part 2 Adding Device Support
Making your device supported Now that you have you have the device tree

I will be demonstrating how to add your device to any ROM.

First step is after you synced to have a visit on their Github.
In this example I will be using Pac-man since I already added our device to their source. Please note that this is just a start and you would have to review another device if the phone is not supported for the Rom you want to build.

https://github.com/PAC-man/android_v...89e937610f755d

on here as you can see the files I added and modified to get a build going pay attention to them.



If your device isn't supported like on Paranoid Android review another device as an example.
https://github.com/ParanoidAndroid/a...42f7901596c60c

You can see that they added a product file and other things. I will be reviewing a few examples but get a look at the files they modified and try to understand why.



Step 1 the first thing you should look for on a Rom you like is the VendorSetup.sh File like this one usually in vendor/Rom-name



You Would Have to append the epic to the end of the file or the build will not lunch.In this example I used RootBox
Code:
add_lunch_combo rootbox_d2att-userdebug
add_lunch_combo rootbox_d2tmo-userdebug
add_lunch_combo rootbox_d2vzw-userdebug
add_lunch_combo rootbox_grouper-userdebug
add_lunch_combo rootbox_i605-userdebug
add_lunch_combo rootbox_i9100-userdebug
add_lunch_combo rootbox_i9100g-userdebug
add_lunch_combo rootbox_i9300-userdebug
add_lunch_combo rootbox_l900-userdebug
add_lunch_combo rootbox_maguro-userdebug
add_lunch_combo rootbox_mako-userdebug
add_lunch_combo rootbox_n7000-userdebug
add_lunch_combo rootbox_n7100-userdebug
add_lunch_combo rootbox_quincyatt-userdebug
add_lunch_combo rootbox_toro-userdebug
add_lunch_combo rootbox_t0lte-userdebug
add_lunch_combo rootbox_epicmtd-userdebug

Next step would be adding Your Product specs please Note this is not found in all ROMs but most of them.


look for vendor/RomName/Products and find AndroidProducts.mk append the epic to the end. In the first example it does not change format. In second one it will. I will include both formats.

1st one usually not used as you can see I added the epic to AndroidProducts so that it can find my build product spec.

Code:
PRODUCT_MAKEFILES := $(LOCAL_DIR)/d2att.mk \
$(LOCAL_DIR)/d2tmo.mk \
$(LOCAL_DIR)/d2vzw.mk \
$(LOCAL_DIR)/epicmtd.mk \
$(LOCAL_DIR)/fascinatemtd.mk
$(LOCAL_DIR)/grouper.mk \
$(LOCAL_DIR)/i605.mk \
$(LOCAL_DIR)/i9100.mk \
$(LOCAL_DIR)/i9100g.mk \
$(LOCAL_DIR)/i9300.mk \
$(LOCAL_DIR)/l900.mk \
$(LOCAL_DIR)/maguro.mk \
$(LOCAL_DIR)/mako.mk \
$(LOCAL_DIR)/n7000.mk \
$(LOCAL_DIR)/n7100.mk \
$(LOCAL_DIR)/quincyatt.mk \
$(LOCAL_DIR)/toro.mk \
$(LOCAL_DIR)/t0lte.mk
2nd one more commonly used pa= paranoid android that part will change in this format depending on the ROM

Code:
ifeq (pa_grouper,$(TARGET_PRODUCT))
    PRODUCT_MAKEFILES += $(LOCAL_DIR)/pa_grouper.mk
endif
ifeq (pa_i9100,$(TARGET_PRODUCT))
    PRODUCT_MAKEFILES += $(LOCAL_DIR)/pa_i9100.mk
endif
ifeq (pa_i9300,$(TARGET_PRODUCT))
    PRODUCT_MAKEFILES += $(LOCAL_DIR)/pa_i9300.mk
endif
ifeq (pa_i9305,$(TARGET_PRODUCT))
    PRODUCT_MAKEFILES += $(LOCAL_DIR)/pa_i9305.mk
endif
ifeq (pa_maguro,$(TARGET_PRODUCT))
    PRODUCT_MAKEFILES += $(LOCAL_DIR)/pa_maguro.mk
endif
ifeq (pa_mako,$(TARGET_PRODUCT))
    PRODUCT_MAKEFILES += $(LOCAL_DIR)/pa_mako.mk
endif
ifeq (pa_manta,$(TARGET_PRODUCT))
    PRODUCT_MAKEFILES += $(LOCAL_DIR)/pa_manta.mk
endif
ifeq (pa_n7100,$(TARGET_PRODUCT))
    PRODUCT_MAKEFILES += $(LOCAL_DIR)/pa_n7100.mk
endif
ifeq (pa_tf700t,$(TARGET_PRODUCT))
    PRODUCT_MAKEFILES += $(LOCAL_DIR)/pa_tf700t.mk
endif
ifeq (pa_tilapia,$(TARGET_PRODUCT))
    PRODUCT_MAKEFILES += $(LOCAL_DIR)/pa_tilapia.mk
endif
ifeq (pa_toro,$(TARGET_PRODUCT))
    PRODUCT_MAKEFILES += $(LOCAL_DIR)/pa_toro.mk
endif
ifeq (pa_toroplus,$(TARGET_PRODUCT))
    PRODUCT_MAKEFILES += $(LOCAL_DIR)/pa_toroplus.mk
endif
ifeq (pa_bravo,$(TARGET_PRODUCT))
    PRODUCT_MAKEFILES += $(LOCAL_DIR)/pa_bravo.mk
endif
ifeq (pa_crespo,$(TARGET_PRODUCT))
    PRODUCT_MAKEFILES += $(LOCAL_DIR)/pa_crespo.mk
endif
ifeq (pa_endeavoru,$(TARGET_PRODUCT))
    PRODUCT_MAKEFILES += $(LOCAL_DIR)/pa_endeavoru.mk
endif
ifeq (pa_epicmtd,$(TARGET_PRODUCT))
    PRODUCT_MAKEFILES += $(LOCAL_DIR)/pa_epicmtd.mk
endif
Next step will be creating a product spec refer to other files for guidance please note the files you tell it to use must exist

The build Fingerprint should always be the same as the one from device/sasmung/epicmtd/cm.mk. Please note this is only for RootBox.

This file is called on by AndroidProducts.mk.

For example this file would be named epicmtd.mk or it could be named pa_epicmtd.mk depending on the Rom.

Code:
# Inherit AOSP device configuration for epicmtd.
$(call inherit-product, device/samsung/epicmtd/full_epicmtd.mk)

# Inherit CDMA common stuff.
$(call inherit-product, vendor/rootbox/configs/cdma.mk)

# Inherit RootBox goods.
$(call inherit-product, vendor/rootbox/configs/common.mk)

# Epic 4G Overlays
PRODUCT_PACKAGE_OVERLAYS += vendor/rootbox/overlay/epicmtd

# PA OVERLAY_TARGET
OVERLAY_TARGET := pa_hdpi

# Setup device specific product configuration.
PRODUCT_NAME := rootbox_epicmtd
PRODUCT_BRAND := samsung
PRODUCT_DEVICE := epicmtd
PRODUCT_MODEL := SPH-D700
PRODUCT_MANUFACTURER := samsung

#Set build fingerprint / ID / Product Name ect.
PRODUCT_BUILD_PROP_OVERRIDES += PRODUCT_NAME=SPH-D700 TARGET_DEVICE=SPH-D700 BUILD_FINGERPRINT=sprint/SPH-D700/SPH-D700:2.3.5/GINGERBREAD/EI22:user/release-keys PRIVATE_BUILD_DESC="SPH-D700-user 2.3.5 GINGERBREAD EI22 release-keys"

# Copy bootanimation.zip
PRODUCT_COPY_FILES += \
    vendor/rootbox/prebuilt/hdpi/bootanimation.zip:system/media/bootanimation.zip




I will Finish This Up Later and Polish it Up
The Following 4 Users Say Thank You to Unjustified Dev For This Useful Post: [ View ]
21st March 2013, 10:44 PM |#5  
Dropple's Avatar
Senior Member
Thanks Meter: 363
 
More
still downloading source (slow internet)
i want to compile other ROM

thanks for this guide
The Following User Says Thank You to Dropple For This Useful Post: [ View ] Gift Dropple Ad-Free
22nd March 2013, 02:20 AM |#6  
Nashdogg's Avatar
Senior Member
Flag Maine
Thanks Meter: 1,337
 
Donate to Me
More
Re: [Guide] Building from source Any ROM
Can't wait to try this out. Unjustified, you are the man. 15 or not, you are OK in my book

Sent from my SPH-D700 using Xparent Skyblue Tapatalk 2
The Following 2 Users Say Thank You to Nashdogg For This Useful Post: [ View ] Gift Nashdogg Ad-Free
22nd March 2013, 02:45 AM |#7  
bthorne79's Avatar
Senior Member
Flag ChuckTown
Thanks Meter: 3,480
 
Donate to Me
More
Re: [Guide] Building from source Any ROM
I'm going to have to tag this

Sent from my Hellfired SGS3
Sprint SGS3 Hellfireā„¢ Maintainer
The Following User Says Thank You to bthorne79 For This Useful Post: [ View ] Gift bthorne79 Ad-Free
22nd March 2013, 12:48 PM |#8  
Dropple's Avatar
Senior Member
Thanks Meter: 363
 
More
am i still to run extract-files.sh or directly to bruch?
22nd March 2013, 12:50 PM |#9  
Unjustified Dev's Avatar
OP Recognized Developer
Flag Memphis , TN
Thanks Meter: 12,082
 
Donate to Me
More
Re: [Guide] Building from source Any ROM
Quote:
Originally Posted by Dropple

am i still to run extract-files.sh or directly to bruch?

What are you building and
Yes run ./extract-files.sh but brunch only works with cyanogenmod which is the easiest to build.
CD to working directory example
Code:
cd android/system
. build/envsetup.sh 
 cd device/samsung/epicmtd
Make sure the epic is connected to USB and adb is working
[CODE]chmod +x extract-files.sh
./extract-files.sh[CODE]

Sent from my SCH-I500 using xda app-developers app
22nd March 2013, 02:12 PM |#10  
Dropple's Avatar
Senior Member
Thanks Meter: 363
 
More
Quote:
Originally Posted by Unjustified Dev

What are you building and
Yes run ./extract-files.sh but brunch only works with cyanogenmod which is the easiest to build.
CD to working directory example

Code:
cd android/system
. build/envsetup.sh 
 cd device/samsung/epicmtd
Make sure the epic is connected to USB and adb is working
Code:
chmod +x extract-files.sh
./extract-files.sh
Sent from my SCH-I500 using xda app-developers app

want to build jellybeer
and i cant get my adb working on 12.04 LTS
HTML Code:
dropple@ubuntu:~/jellybeer/device/samsung/epicmtd$ ./extract-files.sh
rm: cannot remove `../../../vendor/samsung/epicmtd/proprietary/lib/hw': Permission denied
rm: cannot remove `../../../vendor/samsung/epicmtd/proprietary/lib/egl': Permission denied
rm: cannot remove `../../../vendor/samsung/epicmtd/proprietary/media': Permission denied
rm: cannot remove `../../../vendor/samsung/epicmtd/proprietary/etc/wifi': Permission denied
rm: cannot remove `../../../vendor/samsung/epicmtd/proprietary/firmware': Permission denied
rm: cannot remove `../../../vendor/samsung/epicmtd/proprietary/vendor/firmware': Permission denied
rm: cannot remove `../../../vendor/samsung/epicmtd/proprietary/vendor/bin': Permission denied
rm: cannot remove `../../../vendor/samsung/epicmtd/proprietary/bin': Permission denied
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 141: ./extract-files.sh: adb: not found
./extract-files.sh: 142: ./extract-files.sh: adb: not found
./extract-files.sh: 143: ./extract-files.sh: adb: not found
./extract-files.sh: 144: ./extract-files.sh: adb: not found
dropple@ubuntu:~/jellybeer/device/samsung/epicmtd$ 
22nd March 2013, 02:30 PM |#11  
xboxfanj's Avatar
Recognized Developer
Flag I'm from the Lou and I'm proud
Thanks Meter: 7,493
 
Donate to Me
More
Re: [Guide] Building from source Any ROM
Quote:
Originally Posted by Dropple

want to build jellybeer
and i cant get my adb working on 12.04 LTS

HTML Code:
dropple@ubuntu:~/jellybeer/device/samsung/epicmtd$ ./extract-files.sh
rm: cannot remove `../../../vendor/samsung/epicmtd/proprietary/lib/hw': Permission denied
rm: cannot remove `../../../vendor/samsung/epicmtd/proprietary/lib/egl': Permission denied
rm: cannot remove `../../../vendor/samsung/epicmtd/proprietary/media': Permission denied
rm: cannot remove `../../../vendor/samsung/epicmtd/proprietary/etc/wifi': Permission denied
rm: cannot remove `../../../vendor/samsung/epicmtd/proprietary/firmware': Permission denied
rm: cannot remove `../../../vendor/samsung/epicmtd/proprietary/vendor/firmware': Permission denied
rm: cannot remove `../../../vendor/samsung/epicmtd/proprietary/vendor/bin': Permission denied
rm: cannot remove `../../../vendor/samsung/epicmtd/proprietary/bin': Permission denied
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 137: ./extract-files.sh: adb: not found
./extract-files.sh: 141: ./extract-files.sh: adb: not found
./extract-files.sh: 142: ./extract-files.sh: adb: not found
./extract-files.sh: 143: ./extract-files.sh: adb: not found
./extract-files.sh: 144: ./extract-files.sh: adb: not found
dropple@ubuntu:~/jellybeer/device/samsung/epicmtd$ 

You need to apt-get install android-tools-adb but instead of using extract files, just sync the vendor repo at the muppets github in your local manifest.

Sent from my LG-LS970 using xda app-developers app
The Following User Says Thank You to xboxfanj For This Useful Post: [ View ]
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes