Database Info

[Guide] Building from source Any ROM - Epic 4G Android Development

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:laugh:

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_vendor_pac/commit/4f60080b14c6eb5cf0393645cc89e937610f755d
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/android_vendor_pa/commit/6c49f44d75e2ad72a9633d8aa742f7901596c60c
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
[B]add_lunch_combo rootbox_epicmtd-userdebug[/B]
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 \
[B]$(LOCAL_DIR)/epicmtd.mk \[/B]
$(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
[B]ifeq (pa_epicmtd,$(TARGET_PRODUCT))
PRODUCT_MAKEFILES += $(LOCAL_DIR)/pa_epicmtd.mk
endif[/B]
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

reserved 2
Part 3 Committing Your Work

Reseve 3
Updating Your Forked Repository

still downloading source (slow internet)
i want to compile other ROM
thanks for this guide

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

I'm going to have to tag this
Sent from my Hellfired SGS3
Sprint SGS3 Hellfire™ Maintainer

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

Dropple said:
am i still to run extract-files.sh or directly to bruch?
Click to expand...
Click to collapse
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

Unjustified Dev said:
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
Click to expand...
Click to collapse
want to build jellybeer
and i cant get my adb working on 12.04 LTS
HTML:
[email protected]:~/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
[email protected]:~/jellybeer/device/samsung/epicmtd$

Dropple said:
want to build jellybeer
and i cant get my adb working on 12.04 LTS
HTML:
[email protected]:~/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
[email protected]:~/jellybeer/device/samsung/epicmtd$
Click to expand...
Click to collapse
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

xboxfanj said:
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
Click to expand...
Click to collapse
HTML:
E: Unable to locate package android-tools-adb
there is
HTML:
<project path="vendor/samsung" name="TheMuppets/proprietary_vendor_samsung"/>
in manifest.xml, so i didnt add that to local_manifest.xml

Dropple said:
HTML:
E: Unable to locate package android-tools-adb
there is
HTML:
<project path="vendor/samsung" name="TheMuppets/proprietary_vendor_samsung"/>
in manifest.xml, so i didnt add that to local_manifest.xml
Click to expand...
Click to collapse
Then you don't need it if vendor/Samsung/epicmtd exist I forgot to add it. I extracted proprietary files a long time ago and have no need for it. I will fix local_manifest.XML later
Sent from my SCH-I500 using xda app-developers app

Dropple said:
HTML:
E: Unable to locate package android-tools-adb
there is
HTML:
<project path="vendor/samsung" name="TheMuppets/proprietary_vendor_samsung"/>
in manifest.xml, so i didnt add that to local_manifest.xml
Click to expand...
Click to collapse
You must not be on 12.10. If you need it, I can send you the binary.

Thanks for making a thread Unjustified. All synced and ran into some issues when trying to build. Here is the error in terminal:
Code:
...
23. baked_epicmtd-userdebug
24. baked_fascinatemtd-userdebug
25. baked_galaxysmtd-userdebug
...
Which would you like? [full-eng] 23
build/core/product_config.mk:193: *** _nic.PRODUCTS.[[device/samsung/i9100/full_i9100.mk]]: "device/samsung/galaxys2-common/common.mk" does not exist. Stop.
** Don't have a product spec for: 'baked_epicmtd'
** Do you have the right repo manifest?
I made the changes you posted and have my local_manifest.xml set like so:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="CyanogenMod/android_device_samsung_epicmtd" path="device/samsung/epicmtd" remote="github" revision="cm-10.1" />
<project name="CyanogenMod/android_kernel_samsung_epicmtd" path="kernel/samsung/epicmtd" remote="github" revision="cm-10.1" />
<project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="cm-10.1" />
<project name="CyanogenMod/android_packages_apps_SamsungServiceMode" path="packages/apps/SamsungServiceMode" remote="github" revision="cm-10.1" />
<project name="CyanogenMod/android_hardware_samsung" path="hardware/samsung" remote="github" revision="cm-10.1" />
</manifest>
Do I have to make changes to the manifest.xml as well?

cornaljoe said:
Thanks for making a thread Unjustified. All synced and ran into some issues when trying to build. Here is the error in terminal:
Code:
...
23. baked_epicmtd-userdebug
24. baked_fascinatemtd-userdebug
25. baked_galaxysmtd-userdebug
...
Which would you like? [full-eng] 23
build/core/product_config.mk:193: *** _nic.PRODUCTS.[[device/samsung/i9100/full_i9100.mk]]: "device/samsung/galaxys2-common/common.mk" does not exist. Stop.
** Don't have a product spec for: 'baked_epicmtd'
** Do you have the right repo manifest?
I made the changes you posted and have my local_manifest.xml set like so:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="CyanogenMod/android_device_samsung_epicmtd" path="device/samsung/epicmtd" remote="github" revision="cm-10.1" />
<project name="CyanogenMod/android_kernel_samsung_epicmtd" path="kernel/samsung/epicmtd" remote="github" revision="cm-10.1" />
<project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="cm-10.1" />
<project name="CyanogenMod/android_packages_apps_SamsungServiceMode" path="packages/apps/SamsungServiceMode" remote="github" revision="cm-10.1" />
<project name="CyanogenMod/android_hardware_samsung" path="hardware/samsung" remote="github" revision="cm-10.1" />
</manifest>
Do I have to make changes to the manifest.xml as well?
Click to expand...
Click to collapse
hmm error in my commits sorry
delete vendor/samsung/epicmtd
and replace it with this again
https://github.com/C457/vendor_baked
or got to vendor/baked and open vendorsetup.sh and modify this as the commit did
https://github.com/C457/vendor_baked/commit/1492dfb0a958fdd20fd317397098b81b36f04c46

adb is working now
when make it, i got this trouble
HTML:
[email protected]:~/jellybeer# make -j4
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=4.2.2
TARGET_PRODUCT=cm_epicmtd
TARGET_BUILD_VARIANT=userdebug
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv7-a-neon
HOST_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-3.5.0-23-generic-x86_64-with-Ubuntu-12.04-precise
HOST_BUILD_TYPE=release
BUILD_ID=JDQ39
OUT_DIR=/home/dropple/jellybeer/out
============================================
find: `../../vendor/unbundled_google/libs/gcm/gcm-client/src': No such file or directory
find: `../../vendor/unbundled_google/libs/gcm/gcm-server/src': No such file or directory
find: `../../vendor/unbundled_google/libs/gcm/gcm-client/src': No such file or directory
find: `../../vendor/unbundled_google/libs/gcm/gcm-server/src': No such file or directory
find: `src': No such file or directory
vendor/nvidia/grouper/keymaster/Android.mk:16: Extraneous text after `ifeq' directive
vendor/nvidia/tilapia/keymaster/Android.mk:16: Extraneous text after `ifeq' directive
build/core/Makefile:44: warning: overriding commands for target `/home/dropple/jellybeer/out/target/product/epicmtd/system/etc/mkshrc'
build/core/base_rules.mk:502: warning: ignoring old commands for target `/home/dropple/jellybeer/out/target/product/epicmtd/system/etc/mkshrc'
build/core/Makefile:44: warning: overriding commands for target `/home/dropple/jellybeer/out/target/product/epicmtd/system/lib/egl/egl.cfg'
build/core/base_rules.mk:502: warning: ignoring old commands for target `/home/dropple/jellybeer/out/target/product/epicmtd/system/lib/egl/egl.cfg'
build/core/Makefile:44: warning: overriding commands for target `/home/dropple/jellybeer/out/target/product/epicmtd/system/etc/permissions/android.software.live_wallpaper.xml'
build/core/base_rules.mk:502: warning: ignoring old commands for target `/home/dropple/jellybeer/out/target/product/epicmtd/system/etc/permissions/android.software.live_wallpaper.xml'
build/core/Makefile:44: warning: overriding commands for target `/home/dropple/jellybeer/out/target/product/epicmtd/system/etc/permissions/android.software.live_wallpaper.xml'
build/core/Makefile:44: warning: ignoring old commands for target `/home/dropple/jellybeer/out/target/product/epicmtd/system/etc/permissions/android.software.live_wallpaper.xml'
build/core/Makefile:44: warning: overriding commands for target `/home/dropple/jellybeer/out/target/product/epicmtd/system/lib/egl/libGLES_android.so'
build/core/base_rules.mk:502: warning: ignoring old commands for target `/home/dropple/jellybeer/out/target/product/epicmtd/system/lib/egl/libGLES_android.so'
build/core/Makefile:44: warning: overriding commands for target `/home/dropple/jellybeer/out/target/product/epicmtd/system/lib/hw/sensors.s5pc110.so'
build/core/base_rules.mk:502: warning: ignoring old commands for target `/home/dropple/jellybeer/out/target/product/epicmtd/system/lib/hw/sensors.s5pc110.so'
build/core/Makefile:44: warning: overriding commands for target `/home/dropple/jellybeer/out/target/product/epicmtd/system/bin/rild'
build/core/base_rules.mk:502: warning: ignoring old commands for target `/home/dropple/jellybeer/out/target/product/epicmtd/system/bin/rild'
build/core/Makefile:44: warning: overriding commands for target `/home/dropple/jellybeer/out/target/product/epicmtd/system/lib/libril.so'
build/core/base_rules.mk:502: warning: ignoring old commands for target `/home/dropple/jellybeer/out/target/product/epicmtd/system/lib/libril.so'
PRODUCT_COPY_FILES device/generic/goldfish/data/etc/apns-conf.xml:system/etc/apns-conf.xml ignored.
PRODUCT_COPY_FILES development/tools/emulator/system/camera/media_profiles.xml:system/etc/media_profiles.xml ignored.
PRODUCT_COPY_FILES development/tools/emulator/system/camera/media_codecs.xml:system/etc/media_codecs.xml ignored.
PRODUCT_COPY_FILES hardware/libhardware_legacy/audio/audio_policy.conf:system/etc/audio_policy.conf ignored.
No private recovery resources for TARGET_DEVICE epicmtd
host Java: jsr305lib (/home/dropple/jellybeer/out/host/common/obj/JAVA_LIBRARIES/jsr305lib_intermediates/classes)
Import includes file: /home/dropple/jellybeer/out/host/linux-x86/obj/EXECUTABLES/acp_intermediates/import_includes
host C: libhost <= build/libs/host/CopyFile.c
host C++: libhost <= build/libs/host/pseudolocalize.cpp
Notice file: external/guava/NOTICE -- /home/dropple/jellybeer/out/host/linux-x86/obj/NOTICE_FILES/src//framework/guavalib.jar.txt
/bin/bash: prebuilts/misc/linux-x86/ccache/ccache: No such file or directory
make: *** [/home/dropple/jellybeer/out/host/linux-x86/obj/STATIC_LIBRARIES/libhost_intermediates/pseudolocalize.o] Error 127
make: *** Waiting for unfinished jobs....
/bin/bash: prebuilts/misc/linux-x86/ccache/ccache: No such file or directory
make: *** [/home/dropple/jellybeer/out/host/linux-x86/obj/STATIC_LIBRARIES/libhost_intermediates/CopyFile.o] Error 127
[email protected]:~/jellybeer#

Dropple said:
adb is working now
when make it, i got this trouble
HTML:
[email protected]:~/jellybeer# make -j4
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=4.2.2
TARGET_PRODUCT=cm_epicmtd
TARGET_BUILD_VARIANT=userdebug
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv7-a-neon
HOST_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-3.5.0-23-generic-x86_64-with-Ubuntu-12.04-precise
HOST_BUILD_TYPE=release
BUILD_ID=JDQ39
OUT_DIR=/home/dropple/jellybeer/out
============================================
find: `../../vendor/unbundled_google/libs/gcm/gcm-client/src': No such file or directory
find: `../../vendor/unbundled_google/libs/gcm/gcm-server/src': No such file or directory
find: `../../vendor/unbundled_google/libs/gcm/gcm-client/src': No such file or directory
find: `../../vendor/unbundled_google/libs/gcm/gcm-server/src': No such file or directory
find: `src': No such file or directory
vendor/nvidia/grouper/keymaster/Android.mk:16: Extraneous text after `ifeq' directive
vendor/nvidia/tilapia/keymaster/Android.mk:16: Extraneous text after `ifeq' directive
build/core/Makefile:44: warning: overriding commands for target `/home/dropple/jellybeer/out/target/product/epicmtd/system/etc/mkshrc'
build/core/base_rules.mk:502: warning: ignoring old commands for target `/home/dropple/jellybeer/out/target/product/epicmtd/system/etc/mkshrc'
build/core/Makefile:44: warning: overriding commands for target `/home/dropple/jellybeer/out/target/product/epicmtd/system/lib/egl/egl.cfg'
build/core/base_rules.mk:502: warning: ignoring old commands for target `/home/dropple/jellybeer/out/target/product/epicmtd/system/lib/egl/egl.cfg'
build/core/Makefile:44: warning: overriding commands for target `/home/dropple/jellybeer/out/target/product/epicmtd/system/etc/permissions/android.software.live_wallpaper.xml'
build/core/base_rules.mk:502: warning: ignoring old commands for target `/home/dropple/jellybeer/out/target/product/epicmtd/system/etc/permissions/android.software.live_wallpaper.xml'
build/core/Makefile:44: warning: overriding commands for target `/home/dropple/jellybeer/out/target/product/epicmtd/system/etc/permissions/android.software.live_wallpaper.xml'
build/core/Makefile:44: warning: ignoring old commands for target `/home/dropple/jellybeer/out/target/product/epicmtd/system/etc/permissions/android.software.live_wallpaper.xml'
build/core/Makefile:44: warning: overriding commands for target `/home/dropple/jellybeer/out/target/product/epicmtd/system/lib/egl/libGLES_android.so'
build/core/base_rules.mk:502: warning: ignoring old commands for target `/home/dropple/jellybeer/out/target/product/epicmtd/system/lib/egl/libGLES_android.so'
build/core/Makefile:44: warning: overriding commands for target `/home/dropple/jellybeer/out/target/product/epicmtd/system/lib/hw/sensors.s5pc110.so'
build/core/base_rules.mk:502: warning: ignoring old commands for target `/home/dropple/jellybeer/out/target/product/epicmtd/system/lib/hw/sensors.s5pc110.so'
build/core/Makefile:44: warning: overriding commands for target `/home/dropple/jellybeer/out/target/product/epicmtd/system/bin/rild'
build/core/base_rules.mk:502: warning: ignoring old commands for target `/home/dropple/jellybeer/out/target/product/epicmtd/system/bin/rild'
build/core/Makefile:44: warning: overriding commands for target `/home/dropple/jellybeer/out/target/product/epicmtd/system/lib/libril.so'
build/core/base_rules.mk:502: warning: ignoring old commands for target `/home/dropple/jellybeer/out/target/product/epicmtd/system/lib/libril.so'
PRODUCT_COPY_FILES device/generic/goldfish/data/etc/apns-conf.xml:system/etc/apns-conf.xml ignored.
PRODUCT_COPY_FILES development/tools/emulator/system/camera/media_profiles.xml:system/etc/media_profiles.xml ignored.
PRODUCT_COPY_FILES development/tools/emulator/system/camera/media_codecs.xml:system/etc/media_codecs.xml ignored.
PRODUCT_COPY_FILES hardware/libhardware_legacy/audio/audio_policy.conf:system/etc/audio_policy.conf ignored.
No private recovery resources for TARGET_DEVICE epicmtd
host Java: jsr305lib (/home/dropple/jellybeer/out/host/common/obj/JAVA_LIBRARIES/jsr305lib_intermediates/classes)
Import includes file: /home/dropple/jellybeer/out/host/linux-x86/obj/EXECUTABLES/acp_intermediates/import_includes
host C: libhost <= build/libs/host/CopyFile.c
host C++: libhost <= build/libs/host/pseudolocalize.cpp
Notice file: external/guava/NOTICE -- /home/dropple/jellybeer/out/host/linux-x86/obj/NOTICE_FILES/src//framework/guavalib.jar.txt
/bin/bash: prebuilts/misc/linux-x86/ccache/ccache: No such file or directory
make: *** [/home/dropple/jellybeer/out/host/linux-x86/obj/STATIC_LIBRARIES/libhost_intermediates/pseudolocalize.o] Error 127
make: *** Waiting for unfinished jobs....
/bin/bash: prebuilts/misc/linux-x86/ccache/ccache: No such file or directory
make: *** [/home/dropple/jellybeer/out/host/linux-x86/obj/STATIC_LIBRARIES/libhost_intermediates/CopyFile.o] Error 127
[email protected]:~/jellybeer#
Click to expand...
Click to collapse
https://github.com/BeerGang/android
Code:
cd vendor/cm
./get-prebuilts
Code:
./jb-build.sh epicmtd true -j4
if it doesnt work find the build-script ./jb-build.sh should be in root of source at the bottom if not just leave off -j4 if it does have it follow below
Code:
sudo gedit ./jb-build.sh
in viewer look for threads change it to 4 from 16 and hit save
Code:
./jb-build.sh epicmtd true

Building from source
If you want to learn more read this
http://owain.biz/
read tutorials

Unjustified Dev said:
https://github.com/BeerGang/android
Code:
cd vendor/cm
./get-prebuilts
Code:
./jb-build.sh epicmtd true -j4
if it doesnt work find the build-script ./jb-build.sh should be in root of source at the bottom if not just leave off -j4 if it does have it follow below
Code:
sudo gedit ./jb-build.sh
in viewer look for threads change it to 4 from 16 and hit save
Code:
./jb-build.sh epicmtd true
Click to expand...
Click to collapse
thanks for that
but still get
HTML:
find: `../../vendor/unbundled_google/libs/gcm/gcm-client/src': No such file or directory
find: `../../vendor/unbundled_google/libs/gcm/gcm-server/src': No such file or directory
find: `../../vendor/unbundled_google/libs/gcm/gcm-client/src': No such file or directory
find: `../../vendor/unbundled_google/libs/gcm/gcm-server/src': No such file or directory

Related

I repacked recovery.img after adding busybox and nandroid.
Now I'm trying to get adb shell working in recovery mode but I always get the error : "exec '/system/bin/sh' failed: No such file or directory"
I tried added "symlink /sbin/busybox /system/bin/sh" to init.rc but the error is still there.
How can I get adb shell working in recovery?

1. Install Sun JRE and SDK
Unfortunately Ubuntu no longer hosts the SUN SDK/JRE so you will need to obtain this from an alternate source:
Run these commands:
sudo add-apt-repository ppa:sun-java-community-team/sun-java6
sudo apt-get update
sudo apt-get install sun-java6
2. Define your JAVA HOME and PATH:
Edit your .bashrc
Run this command:
sudo gedit $HOME/.bashrc
Add these lines to your .bashrc. Please ensure where you installed the Java libraries and your android sdk. The below reflects default installation directories. (Note last line that includes the Android SDK. You can add this now and install the SDK later. Just make sure if you change the default installation directory that you update your .bashrc file)
export JAVA_HOME="/usr/lib/jvm/java-6-sun-1.6.0.22;"
export PATH=$PATH:$JAVA_HOME/bin
export PATH=$PATH:$HOME"/android-sdk-linux_86/platform-tools"
Run this command to reload your .bashrc:
source ~/.bashrc
3. Install Android SDK:
Goto http://developer.android.com/sdk/index.html
Extract and Install By default, the SDK files are unpacked into a directory named android-sdk-<machine-platform> under your HOME directory.
Navigate to the Android Manager and launch:
cd ~/android-sdk-linux_86/tools
./android update sdk
This will automatically run the android manager and add/update the SDK. I typically install all the packages (for development) but typically for ADB connectivity all you need is the Android SDK Tools and Platform Tools. ADB will not be working properly until you configure the USB driver for the tablet. Thats next.
4. Configure USB Driver
We need to modify your device rules:
sudo gedit /etc/udev/rules.d/99-android.rules
Then, paste the following line into the file 99-android.rules file
SUBSYSTEM=="usb", ATTRS{idVendor}=="0955", SYMLINK+="android_adb", ODE="0666" GROUP="plugdev"
Save and Close gedit (or any other text editor)
Restart the device manager:
sudo restart udev
Launch adb:
adb kill-server
nohup adb start-server
adb devices
If you see your device your done... PM me if you have any questions...

Thanks, I will try this when I get home.

One additional step is needed I believe in order to get adb (aka platform tools). When you start android to test it in your second step, launch it with : ./android update sdk. When the UI starts you'll see an option to download and install Android SDK Tools revision 8 (as of 22 Jan). Click this and it will download and install the platform tools including adb referenced in the rest of the excellent HOWTO.

Added.. Thanks! I took some steps for granted as I did it from memory...
guisar said:
One additional step is needed I believe in order to get adb (aka platform tools). When you start android to test it in your second step, launch it with : ./android update sdk. When the UI starts you'll see an option to download and install Android SDK Tools revision 8 (as of 22 Jan). Click this and it will download and install the platform tools including adb referenced in the rest of the excellent HOWTO.
Click to expand...
Click to collapse

Questions about Ubuntu
Is it possible to install Ubuntu onto a W7 machine with a partitioned HD to develop apps and Roms?
Or would it be better to install Ubu on a VM?
Is this the correct thread for this? If not, sorry.
tia.

Yes it is possible..either approach will work. All my development environments are vm as I move between various machines. Vms give portability...now a days as long as your running a multicore machine with enough ram, performance is not an issue.

stanglx said:
1. Install Sun JRE and SDK
Unfortunately Ubuntu no longer hosts the SUN SDK/JRE so you will need to obtain this from an alternate source:
Run these commands:
sudo add-apt-repository ppa:sun-java-community-team/sun-java6
sudo apt-get update
sudo apt-get install sun-java6
2. Define your JAVA HOME and PATH:
Edit your .bashrc
Run this command:
sudo gedit $HOME/.bashrc
Add these lines to your .bashrc. Please ensure where you installed the Java libraries and your android sdk. The below reflects default installation directories. (Note last line that includes the Android SDK. You can add this now and install the SDK later. Just make sure if you change the default installation directory that you update your .bashrc file)
export JAVA_HOME="/usr/lib/jvm/java-6-sun-1.6.0.22;"
export PATH=$PATH:$JAVA_HOME/bin
export PATH=$PATH:$HOME"/android-sdk-linux_86/platform-tools"
Run this command to reload your .bashrc:
source ~/.bashrc
3. Install Android SDK:
Goto http://developer.android.com/sdk/index.html
Extract and Install By default, the SDK files are unpacked into a directory named android-sdk-<machine-platform> under your HOME directory.
Navigate to the Android Manager and launch:
cd ~/android-sdk-linux_86/tools
./android update sdk
This will automatically run the android manager and add/update the SDK. I typically install all the packages (for development) but typically for ADB connectivity all you need is the Android SDK Tools and Platform Tools. ADB will not be working properly until you configure the USB driver for the tablet. Thats next.
4. Configure USB Driver
We need to modify your device rules:
sudo gedit /etc/udev/rules.d/99-android.rules
Then, paste the following line into the file 99-android.rules file
SUBSYSTEM=="usb", ATTRS{idVendor}=="0955", SYMLINK+="android_adb", ODE="0666" GROUP="plugdev"
Save and Close gedit (or any other text editor)
Restart the device manager:
sudo restart udev
Launch adb:
adb kill-server
nohup adb start-server
adb devices
If you see your device your done... PM me if you have any questions...
Click to expand...
Click to collapse
Thanks for this.
A couple of changes I had to make on my system (ubuntu 10.10)
I had to remove the ; at the end of the first export and had to add x on the last export to look like this.
export JAVA_HOME="/usr/lib/jvm/java-6-sun-1.6.0.22"
export PATH=$PATH:$JAVA_HOME/bin
export PATH=$PATH:$HOME"/android-sdk-linux_x86/platform-tools"

I've used adb before in windows, but ohh man, im having some issues with ubuntu...
so i just tried the java home part where i edit the bash file. Not sure if this is supposed to happen....
after i edit the file, i get this in terminal:
** (gedit:25168): WARNING **: Invalid borders specified for theme pixmap:
/usr/share/themes/elementary/gtk-2.0/Apps,
borders don't fit within the image
(gedit:25168): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_n_channels: assertion `GDK_IS_PIXBUF (pixbuf)' failed
(gedit:25168): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_pixels: assertion `GDK_IS_PIXBUF (pixbuf)' failed
(gedit:25168): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_rowstride: assertion `GDK_IS_PIXBUF (pixbuf)' failed
(gedit:25168): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_n_channels: assertion `GDK_IS_PIXBUF (pixbuf)' failed
(gedit:25168): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_pixels: assertion `GDK_IS_PIXBUF (pixbuf)' failed
(gedit:25168): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_rowstride: assertion `GDK_IS_PIXBUF (pixbuf)' failed
(gedit:25168): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_n_channels: assertion `GDK_IS_PIXBUF (pixbuf)' failed
(gedit:25168): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_pixels: assertion `GDK_IS_PIXBUF (pixbuf)' failed
(gedit:25168): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_rowstride: assertion `GDK_IS_PIXBUF (pixbuf)' failed
(gedit:25168): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_n_channels: assertion `GDK_IS_PIXBUF (pixbuf)' failed
(gedit:25168): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_pixels: assertion `GDK_IS_PIXBUF (pixbuf)' failed
(gedit:25168): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_rowstride: assertion `GDK_IS_PIXBUF (pixbuf)' failed
(gedit:25168): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_n_channels: assertion `GDK_IS_PIXBUF (pixbuf)' failed
(gedit:25168): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_pixels: assertion `GDK_IS_PIXBUF (pixbuf)' failed
(gedit:25168): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_rowstride: assertion `GDK_IS_PIXBUF (pixbuf)' failed
(gedit:25168): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_n_channels: assertion `GDK_IS_PIXBUF (pixbuf)' failed
(gedit:25168): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_pixels: assertion `GDK_IS_PIXBUF (pixbuf)' failed
(gedit:25168): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_rowstride: assertion `GDK_IS_PIXBUF (pixbuf)' failed
(gedit:25168): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_n_channels: assertion `GDK_IS_PIXBUF (pixbuf)' failed
(gedit:25168): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_pixels: assertion `GDK_IS_PIXBUF (pixbuf)' failed
(gedit:25168): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_rowstride: assertion `GDK_IS_PIXBUF (pixbuf)' failed
(gedit:25168): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_n_channels: assertion `GDK_IS_PIXBUF (pixbuf)' failed
(gedit:25168): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_pixels: assertion `GDK_IS_PIXBUF (pixbuf)' failed
(gedit:25168): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_rowstride: assertion `GDK_IS_PIXBUF (pixbuf)' failed
(gedit:25168): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_n_channels: assertion `GDK_IS_PIXBUF (pixbuf)' failed
(gedit:25168): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_pixels: assertion `GDK_IS_PIXBUF (pixbuf)' failed
(gedit:25168): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_rowstride: assertion `GDK_IS_PIXBUF (pixbuf)' failed
(gedit:25168): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_width: assertion `GDK_IS_PIXBUF (pixbuf)' failed
(gedit:25168): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_height: assertion `GDK_IS_PIXBUF (pixbuf)' failed
(gedit:25168): GLib-GObject-CRITICAL **: g_object_ref: assertion `object->ref_count > 0' failed
(gedit:25168): GLib-GObject-CRITICAL **: g_object_ref: assertion `object->ref_count > 0' failed
(gedit:25168): GLib-GObject-CRITICAL **: g_object_ref: assertion `object->ref_count > 0' failed
Click to expand...
Click to collapse
----------------
Also,
would this be the correct location to add that command?
alias imdb-up='find ~Videos* -type f | while read -r line ; do imdb-thumbnailer -u "$line" ; done'
export JAVA_HOME="/usr/lib/jvm/java-6-sun-1.6.0.22"
export PATH=$PATH:$JAVA_HOME/bin
export PATH=$PATH:$HOME"/android-sdk-linux_x86/platform-tools"
and when i try to goto /platform-tools dir, i see abd listed when i ls, but when i type adb i get this :
[email protected]:~/Downloads/android-sdk-linux_x86/platform-tools$ adb
No command 'adb' found, did you mean:
Command 'cdb' from package 'tinycdb' (main)
Command 'gdb' from package 'gdb' (main)
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)
Command 'ad' from package 'netatalk' (universe)
adb: command not found
[email protected]:~/Downloads/android-sdk-linux_x86/platform-tools$
Click to expand...
Click to collapse
I hope the rest not in bold for the bash file is what it should look like... i kinda messed up while copying the code and wipe it........ anyone chime it would be awesome. i am a linux Noob.. i just switched over from windows 7 a this weekend.
thanks for any help!

err, figured it out! wrong dir... sorry for the noobness, im a command line virgin
one last question, so when i pull up the :
sudo gedit /etc/udev/rules.d/99-android.rules
is it supposed to be blank in the text editor?
also, now since i got adb up and running, i cannot get connection to device..
[email protected]:~/Downloads/android-sdk-linux_x86/platform-tools$ adb push flash_image /data/local/bin/flash_image
error: device not found
its in download mode.. also tried via USB when it booted, and was not detected also..

Yes your creating a new file...so it will be empty
What did it say when you type in adb devices at the command?
Did you first the adb srver? adb start-server
nzaw4 said:
err, figured it out! wrong dir... sorry for the noobness, im a command line virgin
one last question, so when i pull up the :
sudo gedit /etc/udev/rules.d/99-android.rules
is it supposed to be blank in the text editor?
also, now since i got adb up and running, i cannot get connection to device..
[email protected]:~/Downloads/android-sdk-linux_x86/platform-tools$ adb push flash_image /data/local/bin/flash_image
error: device not found
its in download mode.. also tried via USB when it booted, and was not detected also..
Click to expand...
Click to collapse

stanglx said:
Yes your creating a new file...so it will be empty
What did it say when you type in adb devices at the command?
Did you first the adb srver? adb start-server
Click to expand...
Click to collapse
Yea, i started a new ADB server,
[email protected]:~/Downloads/android-sdk-linux_x86/platform-tools$ sudo restart udev
udev start/running, process 6665
[email protected]:~/Downloads/android-sdk-linux_x86/platform-tools$ adb kill-server
[email protected]:~/Downloads/android-sdk-linux_x86/platform-tools$ nohup adb start-server
nohup: ignoring input and appending output to `nohup.out'
[email protected]:~/Downloads/android-sdk-linux_x86/platform-tools$ adb devices
List of devices attached
[email protected]:~/Downloads/android-sdk-linux_x86/platform-tools$

nzaw4 said:
Yea, i started a new ADB server,
[email protected]:~/Downloads/android-sdk-linux_x86/platform-tools$ sudo restart udev
udev start/running, process 6665
[email protected]:~/Downloads/android-sdk-linux_x86/platform-tools$ adb kill-server
[email protected]:~/Downloads/android-sdk-linux_x86/platform-tools$ nohup adb start-server
nohup: ignoring input and appending output to `nohup.out'
[email protected]:~/Downloads/android-sdk-linux_x86/platform-tools$ adb devices
List of devices attached
[email protected]:~/Downloads/android-sdk-linux_x86/platform-tools$
Click to expand...
Click to collapse
[email protected]:~/Downloads/android-sdk-linux_x86/platform-tools$ adb kill-server
[email protected]:~/Downloads/android-sdk-linux_x86/platform-tools$ sudo ./adb start-server

Just a quick tip since I just did this with Ubuntu 10.10 and VMWare:
To run adb without have to ./adb every time, execute the following:
sudo cp ~/android-sdk-linux_x86/tools/adb /usr/bin
sudo chmod +x /usr/bin/adb

Here is a much easier way for those who do not want the whole sdk and just want ADB. With this method there is no reason to modify or add rules for your device. You must have usb debugging enabled for this to work. I found a glitch in tnt lite where when you have usb debugging checked it is not actually on, I had to plug in my usb then uncheck usb debugging then re-check it and it worked fine.
(This Guide assumes you do not have ADB installed)
1) open the terminal and type: wget dl.google.com/android/android-sdk_r07-linux_x86.tgz (Downloads The SDK with ADB)
2) Then type: tar xvfz android-sdk_r07-linux_x86.tgz && cd android-sdk-linux_x86 (Extracts the archive)
3) After that type: sudo mv tools /usr/local/share/android-tools (Moves the sdk tools to your local system folder)
4) Now type: sudo ln -s /usr/local/share/android-tools/adb /usr/local/bin/ (Makes a symbolic link to the adb executable)
5) Then type: sudo adb devices (This will start the adb server and search for connected devices)
You should now see this in your terminal:
List of devices attached
171440424240f1d7 device
Everytime you stop the adb server or restart your session if you wish to open adb again you will need to repeat step 5 or type: sudo adb start-server in the terminal.

minor nit
stanglx said:
1. Install Sun JRE and SDK
Unfortunately Ubuntu no longer hosts the SUN SDK/JRE so you will need to obtain this from an alternate source:
Run these commands:
sudo add-apt-repository ppa:sun-java-community-team/sun-java6
sudo apt-get update
sudo apt-get install sun-java6
Click to expand...
Click to collapse
Sun's Java is hosted in the Partner repo. You can enable the partner repository in the software center and wont need the ppa install.
Thx for the guide.
Code:
[email protected]:~$ apt-cache show sun-java6-jdk
Package: sun-java6-jdk
Status: install ok installed
Priority: optional
Section: partner/java

Stanglx,
There is a minor typo in your first post. In step 4.,Configure USB Driver
the line:
Code:
SUBSYSTEM=="usb", ATTRS{idVendor}=="0955", SYMLINK+="android_adb", ODE="0666" GROUP="plugdev"
should actually be:
Code:
SUBSYSTEM=="usb", ATTRS{idVendor}=="0955", SYMLINK+="android_adb", MODE="0666", GROUP="plugdev"
ie. MODE is misspelled.
Some additional hints that you might find useful.
You don't need to restart udev to get it to recognize the new rule. You can use this command instead to reload the new rule:
Code:
sudo udevadm control --reload-rules
Here's a script I use to connect to my gTablet which you might find useful. Of course, you'll have to change the PATHs to suit the locations of your java and adb:
Code:
PATH=$PATH:/opt/java/bin
PATH=$PATH:/mnt-system/android/android-sdk-linux_x86/platform-tools
PATH=$PATH:/mnt-system/android/android-sdk-linux_x86/tools
PATH=$PATH:/mnt-system/android/toolchain/bin
export PATH
FILE=/etc/udev/rules.d/99-android.rules
RULE='SUBSYSTEM=="usb", ATTRS{idVendor}=="0955", SYMLINK+="android_adb", MODE="0666", GROUP="plugdev"'
if [[ ! -f $FILE ]]
then sudo sh -c "echo '$RULE' >$FILE"
sudo chown root.root $FILE
sudo chmod 600 $FILE
sudo udevadm control --reload-rules
fi
adb -d forward tcp:4444 tcp:23
adb -d shell 'exec /system/xbin/telnetd -F -b 127.0.0.1 -l /system/xbin/ash' &
sleep 1
telnet localhost 4444
adb kill-server
I run the above command and it telnets me into the gTablet via a dynamically run adb shell. This way, I have command line editing, I can run full-screen programs like less and vim (in CM7), and, finally, when I quit telnet, everything is shut down cleanly.
One thing: You need a version of busybox which has the telnetd applet compiled into it for the shell script to work. If you don't compile busybox yourself, just install JRummy16's "BusyBox Installer" from the Market and select v1.19 (the beta version) as the version to be installed.

I LOVE YOU DUDE!!!!!! been trying for 3days getting ADB working on 10.10 my google foo had failed then came across this, your awesome nice one dude

Wi-Fi
Who knows how to set up Wi-Fi on Linux.
Shall describe the step by step please.

dantrevino said:
Sun's Java is hosted in the Partner repo. You can enable the partner repository in the software center and wont need the ppa install.
Thx for the guide.
Code:
[email protected]:~$ apt-cache show sun-java6-jdk
Package: sun-java6-jdk
Status: install ok installed
Priority: optional
Section: partner/java
Click to expand...
Click to collapse
thanks
i was unable to install from ppa but from software center installed

Big thanks for the instructions; I also wanted to post to confirm that these instructions without much modifications on Gentoo.

I'm using a mac, an epic4g (eb13) I've got the usb debugging enabled and I can't get this to work:
here's what I get:
Original one click made by joeykrim and one click installer made by noobnl and firon
busybox by skeeterslint
Press any key to continue...
Starting adb server
./run.sh: line 23: adb: command not found
./run.sh: line 26: adb: command not found
./run.sh: line 33: adb: command not found
./run.sh: line 35: adb: command not found
Phone is not connected. Press any key to continue.\n./run.sh: line 35: adb: command not found
Phone is not connected. Press any key to continue.\n./run.sh: line 35: adb: command not found
-----
any idea what I'm doing wrong?

Hi everyone,
I've recently just bought my first Android phone. What's the first thing I want to do with it? Root it and install hyperdrive. However, I am running into some problems with the rooting process itself, so if anyone could help that would be great....
I am on a Mac, so this rooting process is a tad more difficult than the Windows process, but not something that should be giving these errors. It should be noted that I was originally naive and installed Motochopper on my MK2 build before realizing that I needed to install saferoot. Since then, I have uninstalled superuser via the native uninstall function. I know there's about a 99% chance that the way I uninstalled that was incorrect, but I never actually reached a root from motochopper, so I thought I would have been fine. Please correct me If I am wrong. Anyway, upon using terminal to try and root, I get this result.
Code:
Last login: Tue Jan 28 16:52:33 on ttys001
Kevins-Mac-mini:~ kmcianfarini$ cd desktop
Kevins-Mac-mini:desktop kmcianfarini$ cd saferoot
Kevins-Mac-mini:saferoot kmcianfarini$ sh ./install.sh
--- Samsung i545 VRUEMJ7 Root ---
--- Based on the CVE-2013-6282 exploit by cubeundcube ---
Waiting for device...
Watch your phone. Unlock it and give permission for the install to run.
./install.sh: line 10: adb: command not found
Sending files to your device...
./install.sh: line 12: adb: command not found
./install.sh: line 13: adb: command not found
./install.sh: line 14: adb: command not found
./install.sh: line 15: adb: command not found
./install.sh: line 16: adb: command not found
./install.sh: line 17: adb: command not found
./install.sh: line 18: adb: command not found
Starting rooting program.
./install.sh: line 21: adb: command not found
Removing temporary files...
./install.sh: line 24: adb: command not found
./install.sh: line 25: adb: command not found
./install.sh: line 26: adb: command not found
./install.sh: line 27: adb: command not found
./install.sh: line 28: adb: command not found
Rebooting...Please wait.
./install.sh: line 31: adb: command not found
Waiting for device to re-appear...
./install.sh: line 33: adb: command not found
Unlock your phone, and when prompted, give SuperSU permission for
'ADB shell' to run.
./install.sh: line 37: adb: command not found
./install.sh: line 38: adb: command not found
./install.sh: line 39: adb: command not found
./install.sh: line 40: adb: command not found
./install.sh: line 41: adb: command not found
./install.sh: line 42: adb: command not found
./install.sh: line 43: adb: command not found
./install.sh: line 44: adb: command not found
./install.sh: line 45: adb: command not found
./install.sh: line 46: adb: command not found
./install.sh: line 47: adb: command not found
./install.sh: line 48: adb: command not found
./install.sh: line 49: adb: command not found
./install.sh: line 50: adb: command not found
Installing busybox
./install.sh: line 52: adb: command not found
./install.sh: line 53: adb: command not found
./install.sh: line 54: adb: command not found
./install.sh: line 55: adb: command not found
./install.sh: line 56: adb: command not found
./install.sh: line 57: adb: command not found
--- All Finished ---
If someone could please help me that would be great. Thank you, and sorry for any form of ignorance I may be displaying. I have been used to iOS and the jailbreak community for a very long time.
Cheers

well i dont know much about iOS but i do have a S4 and im running on windows and for windows theres a software called kingoapp root you can try it maybe it supports for the iOS too... i must say you have to find a serial key before you root if not it wont root or else try rooting by installing custom recvovery like CWM or TWRP via odin and using the superuser apk...
Good Luck!

As a Linux user I use the sudo command very much to access the root file system of my desktop.But in Android when I started using Termux I found out that it has a beautiful Linux interface .But there was some problems in accessing some commands and changing owners or groups through the termux so I have made a simple script to make a sudo command.This command needs the su binary to be installed in your device for the command script to work.I also have made a permission fix script for termux.
Installation:
Extract the given zip.
Then copy the setperm script and sudo to the following location
/data/data/com.termux/files/usr/bin
Set permission 755 rwxr-xr-x
To both the files.
Changelog :
Full Magisk Support.
Now no problems using and other type of rooting methods.
Debugged error in script.
Any bugs found could be reported with the last log of the session by taking a screenshot of the session and attaching the png file.
Otherwise the bugs will be hard to fix.
Thank you for your cooperation.
the script was written by @st42
thanks to st42.
https://gitlab.com/st42/termux-sudo

How to install su binary? Can you provide some detail as I am a newbie?

shyamtiwari93 said:
How to install su binary? Can you provide some detail as I am a newbie?
Click to expand...
Click to collapse
Please refer to the SuperSU thread by chainfire or the Magisk thread by topjohnwu.
Or you could just search how to root in Google through any browser or lynx.

Can you fix this?
I am rooted with latest magisk v16.0.plz help
sudo su
CANNOT LINK EXECUTABLE "/sbin/su": cannot locate symbol "XzUnpacker_Construct" referenced by "/system/lib64/libunwind.so"...
/data/data/com.termux/files/usr/bin/sudo: line 65: 22132 Aborted $SU -c "$MOUNT_RW"
CANNOT LINK EXECUTABLE "/sbin/su": cannot locate symbol "XzUnpacker_Construct" referenced by "/system/lib64/libunwind.so"...
/data/data/com.termux/files/usr/bin/sudo: line 65: 22136 Aborted $SU -c "mkdir $ROOT_HOME"
CANNOT LINK EXECUTABLE "/sbin/su": cannot locate symbol "XzUnpacker_Construct" referenced by "/system/lib64/libunwind.so"...
/data/data/com.termux/files/usr/bin/sudo: line 65: 22140 Aborted $SU -c "chmod 700 $ROOT_HOME"
CANNOT LINK EXECUTABLE "/sbin/su": cannot locate symbol "XzUnpacker_Construct" referenced by "/system/lib64/libunwind.so"...
/data/data/com.termux/files/usr/bin/sudo: line 65: 22147 Aborted $SU -c "echo -e $BASHRC > $ROOT_HOME/.bashrc"
CANNOT LINK EXECUTABLE "/sbin/su": cannot locate symbol "XzUnpacker_Construct" referenced by "/system/lib64/libunwind.so"...
/data/data/com.termux/files/usr/bin/sudo: line 65: 22152 Aborted $SU -c "chmod 700 $ROOT_HOME/.bashrc"
CANNOT LINK EXECUTABLE "/sbin/su": cannot locate symbol "XzUnpacker_Construct" referenced by "/system/lib64/libunwind.so"...
/data/data/com.termux/files/usr/bin/sudo: line 65: 22156 Aborted $SU -c "$MOUNT_RO"
CANNOT LINK EXECUTABLE "/sbin/su": cannot locate symbol "XzUnpacker_Construct" referenced by "/system/lib64/libunwind.so"...
CANNOT LINK EXECUTABLE "/sbin/su": cannot locate symbol "XzUnpacker_Construct" referenced by "/system/lib64/libunwind.so"...
/data/data/com.termux/files/usr/bin/sudo: line 87: 22169 Aborted $SU -c "$CMDLINE"

munny_sun said:
Can you fix this?
I am rooted with latest magisk v16.0.plz help
sudo su
CANNOT LINK EXECUTABLE "/sbin/su": cannot locate symbol "XzUnpacker_Construct" referenced by "/system/lib64/libunwind.so"...
/data/data/com.termux/files/usr/bin/sudo: line 65: 22132 Aborted $SU -c "$MOUNT_RW"
CANNOT LINK EXECUTABLE "/sbin/su": cannot locate symbol "XzUnpacker_Construct" referenced by "/system/lib64/libunwind.so"...
/data/data/com.termux/files/usr/bin/sudo: line 65: 22136 Aborted $SU -c "mkdir $ROOT_HOME"
CANNOT LINK EXECUTABLE "/sbin/su": cannot locate symbol "XzUnpacker_Construct" referenced by "/system/lib64/libunwind.so"...
/data/data/com.termux/files/usr/bin/sudo: line 65: 22140 Aborted $SU -c "chmod 700 $ROOT_HOME"
CANNOT LINK EXECUTABLE "/sbin/su": cannot locate symbol "XzUnpacker_Construct" referenced by "/system/lib64/libunwind.so"...
/data/data/com.termux/files/usr/bin/sudo: line 65: 22147 Aborted $SU -c "echo -e $BASHRC > $ROOT_HOME/.bashrc"
CANNOT LINK EXECUTABLE "/sbin/su": cannot locate symbol "XzUnpacker_Construct" referenced by "/system/lib64/libunwind.so"...
/data/data/com.termux/files/usr/bin/sudo: line 65: 22152 Aborted $SU -c "chmod 700 $ROOT_HOME/.bashrc"
CANNOT LINK EXECUTABLE "/sbin/su": cannot locate symbol "XzUnpacker_Construct" referenced by "/system/lib64/libunwind.so"...
/data/data/com.termux/files/usr/bin/sudo: line 65: 22156 Aborted $SU -c "$MOUNT_RO"
CANNOT LINK EXECUTABLE "/sbin/su": cannot locate symbol "XzUnpacker_Construct" referenced by "/system/lib64/libunwind.so"...
CANNOT LINK EXECUTABLE "/sbin/su": cannot locate symbol "XzUnpacker_Construct" referenced by "/system/lib64/libunwind.so"...
/data/data/com.termux/files/usr/bin/sudo: line 87: 22169 Aborted $SU -c "$CMDLINE"
Click to expand...
Click to collapse
Sorry support for Magisk is disabled.Support for Magisk will be brought in future.

Agni Datta said:
Sorry support for Magisk is disabled.Support for Magisk will be brought in future.
Click to expand...
Click to collapse
Anyway after some reading in GitHub commits
Changing SU=su worked for me!
Sent from my [device_name] using XDA-Developers Legacy app

Anyone know how to install fdisk ?

Murphy4432 said:
How to install it.
Click to expand...
Click to collapse
Download the zip, extract it, and follow the instructions in README.md
Sent from my OnePlus3T using XDA Labs

Agni Datta said:
Please refer to the SuperSU thread by chainfire or the Magisk thread by topjohnwu.
Or you could just search how to root in Google through any browser or lynx.
Click to expand...
Click to collapse
So for this to work. I need to have a rooted device?

munny_sun said:
Anyway after some reading in GitHub commits
Changing SU=su worked for me!
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
can you please elaborate

Anas Rahman said:
can you please elaborate
Click to expand...
Click to collapse
I am not using termux anymore but I think in the sudo file I changed these values to SU=su and it worked for magisk
if [ -x $SYSXBIN/su ]; then
SU=$SYSXBIN/su
elif [ -x /su/bin/su ]; then
SU=/su/bin/su
elif [ -x /sbin/su ]; then
SU=/sbin/su
Sent from my [device_name] using XDA-Developers Legacy app

munny_sun said:
I am not using termux anymore but I think in the sudo file I changed these values to SU=su and it worked for magisk
if [ -x $SYSXBIN/su ]; then
SU=$SYSXBIN/su
elif [ -x /su/bin/su ]; then
SU=/su/bin/su
elif [ -x /sbin/su ]; then
SU=/sbin/su
Click to expand...
Click to collapse
Sorry but I am a noob and don't know much, I can't understand what to do with the sudo file present in. ../termux-root

Anas Rahman said:
Sorry but I am a noob and don't know much, I can't understand what to do with the sudo file present in. ../termux-root
Click to expand...
Click to collapse
Just follow this procedure in the first post zip is given
Installation:
Extract the given zip.
Then copy the setperm script and sudo to the following location
/data/data/com.termux/files/usr/bin
Set permission 755 rwxr-xr-x
Then just open sudo file and change the values I mentioned it should work
Sent from my [device_name] using XDA-Developers Legacy app

munny_sun said:
Just follow this procedure in the first post zip is given
Installation:
Extract the given zip.
Then copy the setperm script and sudo to the following location
/data/data/com.termux/files/usr/bin
Set permission 755 rwxr-xr-x
Then just open sudo file and change the values I mentioned it should work
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Magisk Support is back.
here is no problem in magisk su.
Fully supporting magisk.

Agni Datta said:
Magisk Support is back.
here is no problem in magisk su.
Fully supporting magisk.
Click to expand...
Click to collapse
Hey I need ur help it was working fine in custom rom but now in stock ROM its showing this error:-
$ sudo
bash: /data/data/com.termux/files/usr/bin/sudo: Permission denied
$ setperm.sh
bash: /data/data/com.termux/files/usr/bin/setperm.sh: Permission denied
Even though both files permission are set to 755
(rwx r-x r-x)
Sent from my [OnePlus 3] using XDA-Developers Legacy app

munny_sun said:
Hey I need ur help it was working fine in custom rom but now in stock ROM its showing this error:-
$ sudo
bash: /data/data/com.termux/files/usr/bin/sudo: Permission denied
$ setperm.sh
bash: /data/data/com.termux/files/usr/bin/setperm.sh: Permission denied
Even though both files permission are set to 755
(rwx r-x r-x)
Click to expand...
Click to collapse
I find that that I need to run restorecon on files that I've copied from my internal storage to /data otherwise I get permission problems.
Sent from my OnePlus3T using XDA Labs

BillGoss said:
I find that that I need to run restorecon on files that I've copied from my internal storage to /data otherwise I get permission problems.
Sent from my OnePlus3T using XDA Labs
Click to expand...
Click to collapse
Thanks man , it worked!
Sent from my [device_name] using XDA-Developers Legacy app

Thanks a lot for sharing. I think you quite mistyped in sudo's script, cos on Android permission 700 is not possible to apply I think. So all occurences must be changed to 755 am I right?.