Hello guys! I have installed pre-resequites,repo init,repo sync..when i'm building i got this error:
find: `opengl/java': No such file or directory
find: `sax/java': No such file or directory
find: `telephony/java': No such file or directory
find: `wifi/java': No such file or directory
find: `voip/java': No such file or directory
find: `opengl/java': No such file or directory
find: `sax/java': No such file or directory
find: `telephony/java': No such file or directory
find: `wifi/java': No such file or directory
find: `voip/java': No such file or directory
find: `test-runner/src': No such file or directory
find: `test-runner/src': No such file or directory
find: `src': No such file or directory
im runnin' ubuntu 11.10.Some help?
oblikas said:
Hello guys! I have installed pre-resequites,repo init,repo sync..when i'm building i got this error:
find: `opengl/java': No such file or directory
find: `sax/java': No such file or directory
find: `telephony/java': No such file or directory
find: `wifi/java': No such file or directory
find: `voip/java': No such file or directory
find: `opengl/java': No such file or directory
find: `sax/java': No such file or directory
find: `telephony/java': No such file or directory
find: `wifi/java': No such file or directory
find: `voip/java': No such file or directory
find: `test-runner/src': No such file or directory
find: `test-runner/src': No such file or directory
find: `src': No such file or directory
im runnin' ubuntu 11.10.Some help?
Click to expand...
Click to collapse
Try updating the OS, 11.10 is no longer supported.
Update to 12.04?
Related
I'm try to build the cyanogenmod source. I find this and this tutorials.
but when i run "breakfast i9300" i get a error:
"build/core/config.mk:48: /pathmap.mk: No such file or directory
build/core/config.mk:132: /envsetup.mk: No such file or directory
build/core/config.mk:135: /linaro_compilerchecks.mk: No such file or directory
build/core/config.mk:148: *** No config file found for TARGET_DEVICE . Stop."
Seems like the TARGET_DEVICE is empty, but don't no how indicate that, i try to create a environment variable and everything but doesn't work.
Someone passing through this ?And/Or know how solve
Thanks for attention
What was the output of source build/envsetup.sh?
If in doubt, do everything again. Don't mix guides
Sent from my GT-I9300 using Tapatalk 2
espeansh been
rootSU said:
What was the output of source build/envsetup.sh?
If in doubt, do everything again. Don't mix guides
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
I do everything again, and follow only the xda trhead, but the error keep
when i run
Code:
. build/envsetup.sh && breakfast i9300
I have the follow output:
Seems the envsetup execute with success but the brakfast don't
have some enviroment that i need to create ? or only add android bin from path ?
Code:
including device/generic/armv7-a-neon/vendorsetup.sh
including device/generic/armv7-a/vendorsetup.sh
including device/ti/panda/vendorsetup.sh
including vendor/cm/vendorsetup.sh
including sdk/bash_completion/adb.bash
including vendor/cm/vendorsetup.sh
Looking for dependencies
build/core/config.mk:48: /pathmap.mk: No such file or directory
build/core/config.mk:132: /envsetup.mk: No such file or directory
build/core/config.mk:135: /linaro_compilerchecks.mk: No such file or directory
build/core/config.mk:148: *** No config file found for TARGET_DEVICE . Stop.
build/core/config.mk:48: /pathmap.mk: No such file or directory
build/core/config.mk:132: /envsetup.mk: No such file or directory
build/core/config.mk:135: /linaro_compilerchecks.mk: No such file or directory
build/core/config.mk:148: *** No config file found for TARGET_DEVICE . Stop.
build/core/config.mk:48: /pathmap.mk: No such file or directory
build/core/config.mk:132: /envsetup.mk: No such file or directory
build/core/config.mk:135: /linaro_compilerchecks.mk: No such file or directory
build/core/config.mk:148: *** No config file found for TARGET_DEVICE . Stop.
build/core/config.mk:48: /pathmap.mk: No such file or directory
build/core/config.mk:132: /envsetup.mk: No such file or directory
build/core/config.mk:135: /linaro_compilerchecks.mk: No such file or directory
build/core/config.mk:148: *** No config file found for TARGET_DEVICE . Stop.
build/core/config.mk:48: /pathmap.mk: No such file or directory
build/core/config.mk:132: /envsetup.mk: No such file or directory
build/core/config.mk:135: /linaro_compilerchecks.mk: No such file or directory
build/core/config.mk:148: *** No config file found for TARGET_DEVICE . Stop.
Can't find toolchain for unknown architecture:
Can't find toolchain for unknown architecture:
build/core/config.mk:48: /pathmap.mk: No such file or directory
build/core/config.mk:132: /envsetup.mk: No such file or directory
build/core/config.mk:135: /linaro_compilerchecks.mk: No such file or directory
build/core/config.mk:148: *** No config file found for TARGET_DEVICE . Stop.
build/core/config.mk:48: /pathmap.mk: No such file or directory
build/core/config.mk:132: /envsetup.mk: No such file or directory
build/core/config.mk:135: /linaro_compilerchecks.mk: No such file or directory
build/core/config.mk:148: *** No config file found for TARGET_DEVICE . Stop.
build/core/config.mk:48: /pathmap.mk: No such file or directory
build/core/config.mk:132: /envsetup.mk: No such file or directory
build/core/config.mk:135: /linaro_compilerchecks.mk: No such file or directory
build/core/config.mk:148: *** No config file found for TARGET_DEVICE . Stop.
build/core/config.mk:48: /pathmap.mk: No such file or directory
build/core/config.mk:132: /envsetup.mk: No such file or directory
build/core/config.mk:135: /linaro_compilerchecks.mk: No such file or directory
build/core/config.mk:148: *** No config file found for TARGET_DEVICE . Stop.
This MultiROM trying to install but I get the following error:
Log
Installing '/external_sd/multirom-20140903-v28-UNOFFICIAL-condor.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Zip does not contain SELinux file_contexts file in its root.
I:Legacy property environment initialized.
Installing MultiROM for condor
Extracting binaries...
about to run program [/sbin/busybox] with 3 args
mount: mounting /dev/block/mmcblk0p36 on /data failed: Device or resource busy
run_program: child exited with status 255
about to run program [/sbin/busybox] with 3 args
minzip: Extracted 40 file(s)
minzip: Extracted 6 file(s)
about to run program [/tmp/extract_multirom.sh] with 1 args
mkdir: can't create directory '/data/media/0/multirom': Permission denied
chown: /data/media/0/multirom: No such file or directory
chmod: /data/media/0/multirom: No such file or directory
mkdir: can't create directory '/data/media/0/multirom/roms': No such file or directory
chown: /data/media/0/multirom/roms: No such file or directory
chmod: /data/media/0/multirom/roms: No such file or directory
touch: /data/media/0/multirom/.nomedia: No such file or directory
chown: /data/media/0/multirom/.nomedia: No such file or directory
rm: can't remove '/data/media/0/multirom/boot.img-ubuntu*': No such file or directory
rm: can't remove '/data/media/0/multirom/infos/*': No such file or directory
rm: can't remove '/data/media/0/multirom/res/*': No such file or directory
cp: can't create '/data/media/0/multirom/adbd': No such file or directory
cp: can't create '/data/media/0/multirom/busybox': No such file or directory
cp: can't create '/data/media/0/multirom/exfat-fuse': No such file or directory
cp: can't create '/data/media/0/multirom/fw_mounter': No such file or directory
cp: can't create directory '/data/media/0/multirom/icons': No such file or directory
cp: can't create '/data/media/0/multirom/kexec': No such file or directory
cp: can't create '/data/media/0/multirom/lz4': No such file or directory
cp: can't create '/data/media/0/multirom/mrom.fstab': No such file or directory
cp: can't create '/data/media/0/multirom/multirom': No such file or directory
cp: can't create '/data/media/0/multirom/ntfs-3g': No such file or directory
cp: can't create directory '/data/media/0/multirom/res': No such file or directory
cp: can't create '/data/media/0/multirom/trampoline': No such file or directory
cp: can't create directory '/data/media/0/multirom/ubuntu-init': No such file or directory
cp: can't create directory '/data/media/0/multirom/ubuntu-touch-init': No such file or directory
cp: can't create directory '/data/media/0/multirom/ubuntu-touch-sysimage-init': No such file or directory
chmod: /data/media/0/multirom/multirom: No such file or directory
chmod: /data/media/0/multirom/busybox: No such file or directory
chmod: /data/media/0/multirom/trampoline: No such file or directory
chmod: /data/media/0/multirom/kexec: No such file or directory
chmod: /data/media/0/multirom/ntfs-3g: No such file or directory
chmod: /data/media/0/multirom/exfat-fuse: No such file or directory
chmod: /data/media/0/multirom/lz4: No such file or directory
chmod: /data/media/0/multirom/ubuntu-init/init: No such file or directory
chmod: /data/media/0/multirom/ubuntu-init/local: No such file or directory
chmod: /data/media/0/multirom/ubuntu-touch-init/init: No such file or directory
chmod: /data/media/0/multirom/ubuntu-touch-init/scripts/touch: No such file or directory
chmod: /data/media/0/multirom/ubuntu-touch-sysimage-init/init: No such file or directory
chmod: /data/media/0/multirom/ubuntu-touch-sysimage-init/scripts/touch: No such file or directory
chmod: /data/media/0/multirom: No such file or directory
chown: /data/media/0/multirom: No such file or directory
run_program: child exited with status 1
script aborted: assert failed: run_program("/tmp/extract_multirom.sh") == 0
assert failed: run_program("/tmp/extract_multirom.sh") == 0
I:Legacy property environment disabled.
E:Error executing updater binary in zip '/external_sd/multirom-20140903-v28-UNOFFICIAL-condor.zip'
Error flashing zip '/external_sd/multirom-20140903-v28-UNOFFICIAL-condor.zip
Now edit the build.prop but I get the same error also delete the first lines of updater.script and follows me out the same. I just worked with me but I want to install cm11 in stock
Sorry for my bad English
Which rom you are using as a primary rom
prajapati ravi said:
Which rom you are using as a primary rom
Click to expand...
Click to collapse
I'm using the stock
Then whats the problem add the cm11 and reboot
---------- Post added at 01:20 AM ---------- Previous post was at 01:16 AM ----------
magdeoz said:
I'm using the stock
Click to expand...
Click to collapse
If you use stock as primary rom then will not get any issue's if still get it then you doing something wrong with your hand
[#nexusmultitoolp1]
If you like it, you might consider donating.
DOWNLOADS
Source Code - Github
[#nexusmultitoolp2]
XDA:DevDB Information
Nexus Multitool, Tool/Utility for the Nexus 9
Contributors
photonicgeek, photonicgeek
Version Information
Status: Beta
Current Beta Version: 0.10
Beta Release Date: 2014-11-23
Created 2014-11-20
Last Updated 2014-11-24
[#nmchangelog]
Reserved for stuff. Maybe.
Looks like a nice tool, thanks very much ?
Pushed out another update!
Is there anything you guys want to see this utility do?
I currently have these features planned:
Custom ROM downloads for different devices (OmniROM, Paranoid Android, Cyanogenmod, etc.)
Disable forced encryption on the Nexus 9 and Nexus 6
Sounds great, downloading will try it out asap.
Windows version?
Edit: Nevermind. I see there is another toolbox in the forum compiled for windows.
Sent from my Nexus 9 using XDA Free mobile app
Hi,
This tools seems to be very interesting.
I tried it on my Nexus 9 following instruction (download, chmod) but when I open the script I have this message:
"This is not a Nexus device. This utility only supports Nexus devices.
Press [Enter] to exit the script."
I don't know if I am missing some thing.
The Nexus 9 is connected through USB. Developper options are active with USB debugging. I tried also with Nexus 9 in bootloader fastboot USB but same results.
Thank you for your help
Bye
Didi666 said:
Hi,
This tools seems to be very interesting.
I tried it on my Nexus 9 following instruction (download, chmod) but when I open the script I have this message:
"This is not a Nexus device. This utility only supports Nexus devices.
Press [Enter] to exit the script."
I don't know if I am missing some thing.
The Nexus 9 is connected through USB. Developper options are active with USB debugging. I tried also with Nexus 9 in bootloader fastboot USB but same results.
Thank you for your help
Bye
Click to expand...
Click to collapse
That's odd, because even trying it now with my Nexus 9 it still works. Can you run
On a Mac:
Code:
~/Nexus-Multitool/all/tools/mac-adb shell getprop ro.product.model
~/Nexus-Multitool/all/tools/mac-adb shell getprop ro.product.name
On Linux:
Code:
~/Nexus-Multitool/all/tools/linux-i386-adb shell getprop ro.product.model
~/Nexus-Multitool/all/tools/linux-i386-adb shell getprop ro.product.name
And paste the results here?
NOTE: You need the device plugged in for it to work.
Nice tool
Will try it out
I'm on a Mac too and have run into the same
"This is not a Nexus device. This utility only supports Nexus devices."
I do have adb working on my Mac on my desktop. I know how to connect that way.
Out of curiosity I wanted to see this run on my Mac as there's just not much out there.
Ran the script after chmod.
In looking not all directories are created, particularly the adb-mac directory within the tools folder .
The only thing there is wget.
Code:
Connecting to device and reading device information.
/Users/xxxxx/Desktop/Nexus-Multitool-v0.10.sh: line 101: /Users/xxxxx/Nexus-Multitool/all/tools/mac-adb: No such file or directory
/Users/xxxxx/Desktop/Nexus-Multitool-v0.10.sh: line 102: /Users/xxxxx/Nexus-Multitool/all/tools/mac-adb: No such file or directory
/Users/xxxxx/Desktop/Nexus-Multitool-v0.10.sh: line 103: /Users/xxxxx/Nexus-Multitool/all/tools/mac-adb: No such file or directory
/Users/xxxxx/Desktop/Nexus-Multitool-v0.10.sh: line 104: /Users/xxxxx/Nexus-Multitool/all/tools/mac-adb: No such file or directory
/Users/xxxxx/Desktop/Nexus-Multitool-v0.10.sh: line 105: /Users/xxxxx/Nexus-Multitool/all/tools/mac-adb: No such file or directory
/Users/xxxxx/Desktop/Nexus-Multitool-v0.10.sh: line 106: /Users/xxxxx/Nexus-Multitool/all/tools/mac-adb: No such file or directory
/Users/xxxxx/Desktop/Nexus-Multitool-v0.10.sh: line 107: /Users/xxxxx/Nexus-Multitool/all/tools/mac-adb: No such file or directory
/Users/xxxxx/Desktop/Nexus-Multitool-v0.10.sh: line 108: /Users/xxxxx/Nexus-Multitool/all/tools/mac-adb: No such file or directory
So running the lines you requested above fails as the file/folder does not exist.
I'm your average Mac user and generally do not get to far into running .sh files.
I was able to chmod it and get it to run but ended with it's not a nexus device.
jmjm003 said:
I'm on a Mac too and have run into the same
"This is not a Nexus device. This utility only supports Nexus devices."
I do have adb working on my Mac on my desktop. I know how to connect that way.
Out of curiosity I wanted to see this run on my Mac as there's just not much out there.
Ran the script after chmod.
In looking not all directories are created, particularly the adb-mac directory within the tools folder .
The only thing there is wget.
Code:
Connecting to device and reading device information.
/Users/xxxxx/Desktop/Nexus-Multitool-v0.10.sh: line 101: /Users/xxxxx/Nexus-Multitool/all/tools/mac-adb: No such file or directory
/Users/xxxxx/Desktop/Nexus-Multitool-v0.10.sh: line 102: /Users/xxxxx/Nexus-Multitool/all/tools/mac-adb: No such file or directory
/Users/xxxxx/Desktop/Nexus-Multitool-v0.10.sh: line 103: /Users/xxxxx/Nexus-Multitool/all/tools/mac-adb: No such file or directory
/Users/xxxxx/Desktop/Nexus-Multitool-v0.10.sh: line 104: /Users/xxxxx/Nexus-Multitool/all/tools/mac-adb: No such file or directory
/Users/xxxxx/Desktop/Nexus-Multitool-v0.10.sh: line 105: /Users/xxxxx/Nexus-Multitool/all/tools/mac-adb: No such file or directory
/Users/xxxxx/Desktop/Nexus-Multitool-v0.10.sh: line 106: /Users/xxxxx/Nexus-Multitool/all/tools/mac-adb: No such file or directory
/Users/xxxxx/Desktop/Nexus-Multitool-v0.10.sh: line 107: /Users/xxxxx/Nexus-Multitool/all/tools/mac-adb: No such file or directory
/Users/xxxxx/Desktop/Nexus-Multitool-v0.10.sh: line 108: /Users/xxxxx/Nexus-Multitool/all/tools/mac-adb: No such file or directory
So running the lines you requested above fails as the file/folder does not exist.
I'm your average Mac user and generally do not get to far into running .sh files.
I was able to chmod it and get it to run but ended with it's not a nexus device.
Click to expand...
Click to collapse
Oh god, I found the issue. I think. I'm uploading v0.11 now! And it was a single simple line of code!
v0.11 ends the same for me as 10 did.
jmjm003 said:
v0.11 ends the same for me as 10 did.
Click to expand...
Click to collapse
Try deleting the entire ~/Nexus-Multitool directory.
It worked after doing that. I didn't test it any further right now as I'm not ready to redo everything today.
Looks promising and I appreciate the work.
jmjm003 said:
It worked after doing that. I didn't test it any further right now as I'm not ready to redo everything today.
Looks promising and I appreciate the work.
Click to expand...
Click to collapse
Ok, Let me know how it turns out!
I used it to do a backup and then it transferred it to my laptop. That worked fine.
Being a Mac user, it's nice to have something to do the process for me.
jmjm003 said:
I used it to do a backup and then it transferred it to my laptop. That worked fine.
Being a Mac user, it's nice to have something to do the process for me.
Click to expand...
Click to collapse
That's what I set out to do!
hi photonicgeek,
I retry to launch the script 0.11 (mac user) and I get same problem as jmjm003. But I think I did not catch what to do by "Try deleting the entire ~/Nexus-Multitool directory."
I try to delet the file et redownload it but still same results.
Code:
Connecting to device and reading device information.
/Users/didi/Desktop/Nexus-Multitool-v0.11.sh: line 102: /Users/didi/Nexus-Multitool/all/tools/mac-adb: No such file or directory
/Users/didi/Desktop/Nexus-Multitool-v0.11.sh: line 103: /Users/didi/Nexus-Multitool/all/tools/mac-adb: No such file or directory
/Users/didi/Desktop/Nexus-Multitool-v0.11.sh: line 104: /Users/didi/Nexus-Multitool/all/tools/mac-adb: No such file or directory
/Users/didi/Desktop/Nexus-Multitool-v0.11.sh: line 105: /Users/didi/Nexus-Multitool/all/tools/mac-adb: No such file or directory
/Users/didi/Desktop/Nexus-Multitool-v0.11.sh: line 106: /Users/didi/Nexus-Multitool/all/tools/mac-adb: No such file or directory
/Users/didi/Desktop/Nexus-Multitool-v0.11.sh: line 107: /Users/didi/Nexus-Multitool/all/tools/mac-adb: No such file or directory
/Users/didi/Desktop/Nexus-Multitool-v0.11.sh: line 108: /Users/didi/Nexus-Multitool/all/tools/mac-adb: No such file or directory
/Users/didi/Desktop/Nexus-Multitool-v0.11.sh: line 109: /Users/didi/Nexus-Multitool/all/tools/mac-adb: No such file or directory
Thank you for your help
---------- Post added at 08:48 PM ---------- Previous post was at 08:34 PM ----------
Sorry I catch it now and it work well. Great tool. Thank you.
Didi666 said:
hi photonicgeek,
I retry to launch the script 0.11 (mac user) and I get same problem as jmjm003. But I think I did not catch what to do by "Try deleting the entire ~/Nexus-Multitool directory."
I try to delet the file et redownload it but still same results.
Code:
Connecting to device and reading device information.
/Users/didi/Desktop/Nexus-Multitool-v0.11.sh: line 102: /Users/didi/Nexus-Multitool/all/tools/mac-adb: No such file or directory
/Users/didi/Desktop/Nexus-Multitool-v0.11.sh: line 103: /Users/didi/Nexus-Multitool/all/tools/mac-adb: No such file or directory
/Users/didi/Desktop/Nexus-Multitool-v0.11.sh: line 104: /Users/didi/Nexus-Multitool/all/tools/mac-adb: No such file or directory
/Users/didi/Desktop/Nexus-Multitool-v0.11.sh: line 105: /Users/didi/Nexus-Multitool/all/tools/mac-adb: No such file or directory
/Users/didi/Desktop/Nexus-Multitool-v0.11.sh: line 106: /Users/didi/Nexus-Multitool/all/tools/mac-adb: No such file or directory
/Users/didi/Desktop/Nexus-Multitool-v0.11.sh: line 107: /Users/didi/Nexus-Multitool/all/tools/mac-adb: No such file or directory
/Users/didi/Desktop/Nexus-Multitool-v0.11.sh: line 108: /Users/didi/Nexus-Multitool/all/tools/mac-adb: No such file or directory
/Users/didi/Desktop/Nexus-Multitool-v0.11.sh: line 109: /Users/didi/Nexus-Multitool/all/tools/mac-adb: No such file or directory
Thank you for your help
Click to expand...
Click to collapse
Yeah, i know whats wrong, and I'm trying to push an update, but XDA is having issues with accepting uploads. Run these commands:
Code:
xcode-select --install
rm -rf ~/Nexus-Multitool
Then run the script again.
[INFO] How to fix warnings "find: ....No such file or directory" in android building
I saw many people get these errors at start when building lollipop (aosp, cm12, etc.):
Code:
find: `src': No such file or directory
See it in full:
Code:
============================================
find: `src': No such file or directory
find: `src': No such file or directory
find: `src': No such file or directory
find: `src': No such file or directory
find: `src': No such file or directory
find: `src': No such file or directory
find: `src': No such file or directory
find: `src': No such file or directory
find: `src': No such file or directory
find: `src': No such file or directory
find: `src': No such file or directory
find: `src': No such file or directory
find: `src': No such file or directory
"ebtables is disabled on this build"
It did happen to me too testing the recovery builds on lollipop, but I'm not sure if it will be the same for building a full ROM.
Anyway, the missing "src" errors are because of these:
Code:
/development/ndk/platforms/android-9/samples/native-activity/Android.mk
/development/testrunner/tests/Android_java.mk
/development/testrunner/tests/Android_native.mk
/cts/tests/systemAppTest/test/Android.mk
/cts/hotsidetests/appsecurity/test-apps/keysets/uB/Android.mk
/cts/hotsidetests/appsecurity/test-apps/keysets/uA/Android.mk
/cts/hotsidetests/appsecurity/test-apps/keysets/uAB/Android.mk
/cts/hotsidetests/appsecurity/test-apps/keysets/uNone/Android.mk
/cts/hotsidetests/appsecurity/test-apps/keysets/permDef/Android.mk
/cts/hotsidetests/appsecurity/test-apps/keysets/uAuB/Android.mk
/cts/hotsidetests/appsecurity/test-apps/keysets/permUse/Android.mk
/frameworks/base/tests/TileBenchmark/Android.mk
/frameworks/base/core/tests/overlaytests/OverlayAppFirst/Android.mk
/frameworks/base/core/tests/overlaytests/OverlayAppSecond/Android.mk
/frameworks/base/core/tests/overlaytests/OverlayTestOverlay/Android.mk
/frameworks/base/core/tests/overlaytests/OverlayAppFirst/Android.mk
All those Android.mk files have lines like this:
Code:
LOCAL_SRC_FILES := $(call all-java-files-under, [COLOR="Red"]src[/COLOR])
but there is no src folder to call for.
So, the solution is to delete the call java part, like this:
Code:
LOCAL_SRC_FILES :=
for all instances in those files, and you will never see that error again.
From what I saw, all are from tests applications and probably have no impact in working ROM, but I like a clean terminal.
Also, if you get this error too:
Code:
find: `dummy': No such file or directory
then go to
Code:
/frameworks/support/v17/leanback/Android.mk
find this line:
Code:
LOCAL_SRC_FILES := $(call all-java-files-under, dummy)
and change it to
Code:
LOCAL_SRC_FILES :=
In some sources (not cyanogenmod 12) you may get this error too:
Code:
find: `phone/java': No such file or directory
That is because of /build/core/pathmap.mk file, called in frameworks Android maker. Open the pathmap file, and find this lines:
Code:
#
# A list of all source roots under frameworks/base, which will be
# built into the android.jar.
#
FRAMEWORKS_BASE_SUBDIRS := \
$(addsuffix /java, \
core \
graphics \
location \
media \
media/mca/effect \
media/mca/filterfw \
media/mca/filterpacks \
drm \
opengl \
sax \
telecomm \
telephony \
[COLOR="Red"]phone[/COLOR] \
wifi \
keystore \
rs \
)
As you can see, there is "phone" folder listed there which probably is missing from /frameworks/base folder. Delete that line and you won't see the "phone/java" error again.
If you think this is a repo sync probelm, I can assure you I checked on github repos and those folders are missing there too.
UPDATE FOR CM 12-1
In cyanogenmod 12-1 they fixed some of those from above, but there are some others extra:
Code:
find: ‘../../../../../../external/hamcrest/src’: No such file or directory
find: ‘../../../../../../external/junit/src/org’: No such file or directory
find: ‘../../../../../../external/hamcrest/src’: No such file or directory
The reason is that in "/frameworks/testing/runner/src/main/Android.mk" file you have two java folder calls (actually 4, because those two are called twice depending on what test library is needed) and they look like this:
Code:
LOCAL_SRC_FILES := $(call all-java-files-under, java) \
$(call all-java-files-under, [COLOR="Red"]../[/COLOR]../../../../../external/junit/src/org) \
$(call all-java-files-under, [COLOR="Red"]../[/COLOR]../../../../../external/hamcrest/src)
What's the problem? There are too many folder levels in that path (one is extra) and you can fix it by deleting first two dots and a slash from every path, like the ones I marked in red.
Also someone asked about the "ebtables" error. That is not an error and the only reason you see it is because you are not building for a Qualcomm platform. You can silence that too if you open "/external/ebtables/Android.mk" and edit it like this:
Code:
#Avoid building ebtables for emulator
ifeq ($(call is-vendor-board-platform,QCOM),true)
include $(call all-subdir-makefiles)
[COLOR="Red"]#[/COLOR]else
[COLOR="Red"]#[/COLOR]$(info "ebtables is disabled on this build")
endif
adding the hashtag to comment out the info message.
******************
UPDATE FOR MARSHMALLOW (CM 13)
For marshmallow, in addition to some of those from above (some of them are fixed in cyanogenmod source), you will get a bunch of missing "dummy" errors:
Code:
find: ‘dummy’: No such file or directory
find: ‘dummy’: No such file or directory
find: ‘dummy’: No such file or directory
find: ‘dummy’: No such file or directory
find: ‘dummy’: No such file or directory
find: ‘dummy’: No such file or directory
find: ‘dummy’: No such file or directory
Ok, one was in lollipop too and you can check above, but the other six are these:
Code:
/frameworks/support/v17/preference-leanback/Android.mk
/frameworks/support/v7/recyclerview/Android.mk
/frameworks/support/v7/preference/Android.mk
/frameworks/support/design/Android.mk
/frameworks/support/percent/Android.mk
/frameworks/support/v14/preference/Android.mk
Check all, find this line:
Code:
LOCAL_SRC_FILES := $(call all-java-files-under, dummy)
and change it to
Code:
LOCAL_SRC_FILES :=
After that you will not see any other missing file or folder.
******************
UPDATE 2 FOR MARSHMALLOW (CM 13)
Lately a new
Code:
find: ‘dummy’: No such file or directory
appear in terminal.
Here it is its location
Code:
/vendor/cmsdk/Android.mk
Although, in comment they say it has to be defined I didn't notice any interference with building process:
Code:
# just need to define this, $(TOP)/dummy should not exist
LOCAL_SRC_FILES := $(call all-java-files-under, dummy)
YES! Thank you! The "phone/java" and the "dummy" ones have been annoying me since forever (since I started building). I don't know if I am supposed to post here, but the "thank you" button didn't feel enough.
Relevant cyanogenmod commit: https://github.com/CyanogenMod/android_build/commit/e80399b354e3310b83f8bd3765874a6739923c3a
carliv said:
I saw many people get these errors at start when building lollipops (aosp, cm12, etc.):
Code:
find: `src': No such file or directory
See it in full:
Code:
============================================
find: `src': No such file or directory
find: `src': No such file or directory
find: `src': No such file or directory
find: `src': No such file or directory
find: `src': No such file or directory
find: `src': No such file or directory
find: `src': No such file or directory
find: `src': No such file or directory
find: `src': No such file or directory
find: `src': No such file or directory
find: `src': No such file or directory
find: `src': No such file or directory
find: `src': No such file or directory
"ebtables is disabled on this build"
It happened to me too testing the recovery builds on lollipop, but I'm not sure if it will be the same for building a full ROM.
Anyway, the missing "src" errors are because of these:
Code:
/development/ndk/platforms/android-9/samples/native-activity/Android.mk
/development/testrunner/tests/Android_java.mk
/development/testrunner/tests/Android_native.mk
/cts/tests/systemAppTest/test/Android.mk
/cts/hotsidetests/appsecurity/test-apps/keysets/uB/Android.mk
/cts/hotsidetests/appsecurity/test-apps/keysets/uA/Android.mk
/cts/hotsidetests/appsecurity/test-apps/keysets/uAB/Android.mk
/cts/hotsidetests/appsecurity/test-apps/keysets/uNone/Android.mk
/cts/hotsidetests/appsecurity/test-apps/keysets/permDef/Android.mk
/cts/hotsidetests/appsecurity/test-apps/keysets/uAuB/Android.mk
/cts/hotsidetests/appsecurity/test-apps/keysets/permUse/Android.mk
/frameworks/base/tests/TileBenchmark/Android.mk
/frameworks/base/core/tests/overlaytests/OverlayAppFirst/Android.mk
/frameworks/base/core/tests/overlaytests/OverlayAppSecond/Android.mk
/frameworks/base/core/tests/overlaytests/OverlayTestOverlay/Android.mk
/frameworks/base/core/tests/overlaytests/OverlayAppFirst/Android.mk
All those Android.mk files have lines like this:
Code:
LOCAL_SRC_FILES := $(call all-java-files-under, [COLOR="Red"]src[/COLOR])
but there is no src folder to call for.
So, the solution is to delete the call java part, like this:
Code:
LOCAL_SRC_FILES :=
for all instances in those files, and you will never see that error again.
From what I saw, all are from tests applications and probably have no impact in working ROM, but I like a clean terminal.
Also, if you get this error too:
Code:
find: `dummy': No such file or directory
then go to
Code:
/frameworks/support/v17/leanback/Android.mk
find this line:
Code:
LOCAL_SRC_FILES := $(call all-java-files-under, dummy)
and change it to
Code:
LOCAL_SRC_FILES :=
In some sources (not cyanogenmod 12) you may get this error too:
Code:
find: `phone/java': No such file or directory
That is because of /build/core/pathmap.mk file, called in frameworks Android maker. Open the pathmap file, and find this lines:
Code:
#
# A list of all source roots under frameworks/base, which will be
# built into the android.jar.
#
FRAMEWORKS_BASE_SUBDIRS := \
$(addsuffix /java, \
core \
graphics \
location \
media \
media/mca/effect \
media/mca/filterfw \
media/mca/filterpacks \
drm \
opengl \
sax \
telecomm \
telephony \
[COLOR="Red"]phone[/COLOR] \
wifi \
keystore \
rs \
)
As you can see, there is "phone" folder listed there which probably is missing from /frameworks/base folder. Delete that line and you won't see the "phone/java" error again.
If you think this is a repo sync probelm, I can assure you I checked on github repos and those folders are missing there too.
Click to expand...
Click to collapse
i changed LOCAL_SRC_FILES := $(call all-java-files-under, dummy) line to LOCAL_SRC_FILES := but it is still giving "ebtables is disabled on this build" and "find: `dummy': no such file or directory" errors
emre3461 said:
i changed LOCAL_SRC_FILES := $(call all-java-files-under, dummy) line to LOCAL_SRC_FILES := but it is still giving "ebtables is disabled on this build" and "find: `dummy': no such file or directory" errors
Click to expand...
Click to collapse
Probably you are not in a lollipop source if the dummy error is still there.
Ebtables error is because you are not building for a qualcomm device and it's harmless.
carliv said:
Probably you are not in a lollipop source if the dummy error is still there.
Ebtables error is because you are not building for a qualcomm device and it's harmless.
Click to expand...
Click to collapse
I am building marshmallow for nexus 5. I initialized repo at /home/emre/cm folder and i started building at /home/emre/cm (i am building now without error except dummy and ebtables error) . Did i make mistake ?
emre3461 said:
I am building marshmallow for nexus 5. I initialized repo at /home/emre/cm folder and i started building at /home/emre/cm (i am building now without error except dummy and ebtables error) . Did i make mistake ?
Click to expand...
Click to collapse
Well, as the thread title says these are for lollipop. I didn't have time yet to study marshmallow, so you have to figure it yourself.
marshmallow
Now I added the informations and fixes for marshmallow too (cm 13-0).
carliv said:
Now I added the informations and fixes for marshmallow too (cm 13-0).
Click to expand...
Click to collapse
Do you know ebtables mean ?
(It gives ebtables is disabled on this build)
emre3461 said:
Do you know ebtables mean ?
(It gives ebtables is disabled on this build)
Click to expand...
Click to collapse
I'm not sure I understand your question? You need info on how to get rid of that notification or you asking what exactly ebtables means?
For first case check the OP just above the updates for marshmallow. For the second case read this.
Just found another one.
Thread closed at OP request
Regards
Sawdoctor
Hi all,
Im trying to root my Doogee T3 but haven't been sucessfull so far. Seems like no one tried before or posted about it.
It has a
Mediatek MT6753,
so MTKdroidTools should work but it gives a few errors:
--->>> Connect to device <<<---
--- ERROR : --- TotalBytesPerChunk Not Found. Set default Page/Spare=2048/64 !!!
--- Unknown ROM structure, backup NOT possible!
ATTENTION! File /system/recovery-from-boot.p which restore factory recovery in case of phone switching on in a normal mode Is Found!
I tried to install twrp but it doesnt seem to work on this device. Happy if you prove me wrong.
I found a guide to root a Doogee F5, same chipset as the T3 so I gave it a shot.
(adb_log at the end, obviously a disaster)
Maybe there is a way to use the User2Root option of the MTK Engineer Mode? Like used in the F5 guide but I dont really understand what it actually does. I understand that its trying to change the linux-like persmissions and that it doesn't find anything, but thats it.
Lets skip this stuff:
-Yes, USB debugging and OEM unlocking are enabled
-Yes, I do have adb and fastboot
-Yes, I do have the drivers
-I already tried previous MTKdroidTools Versions
-KingRoot doesn't work
-RootGenius doesn't work
-Framaroot doesn't work
-I wasn't able to create a scatter file but found one for MT6753 online
adb log of Doogee F5 method:
Code:
Drcken Sie eine beliebige Taste . . .
mount: Read-only file system
/system/bin/sh: can't create /system/toolbox: Read-only file system
chmod: /system/toolbox: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: /system/toolbox: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: /system/toolbox: No such file or directory
mkdir: '/system/bin/.ext': Read-only file system
chown: /system/bin/.ext: No such file or directory
chown: /system/bin/.ext: No such file or directory
chmod: /system/bin/.ext: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: /system/bin/.ext: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: /system/bin/.ext: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
usage: chcon [-hRv] CONTEXT FILE...
Change the SELinux security context of listed file[s].
-h change symlinks instead of what they point to.
-R recurse into subdirectories.
-v verbose output.
chcon: Need 2 arguments
mkdir: '/system/app/SuperSU': Read-only file system
rm: /system/bin/.ext/.su: No such file or directory
failed to copy 'su_bin/su' to '/system/bin/.ext/.su': Read-only file system
chown: /system/bin/.ext/.su: No such file or directory
chown: /system/bin/.ext/.su: No such file or directory
chmod: /system/bin/.ext/.su: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: /system/bin/.ext/.su: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: /system/bin/.ext/.su: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
usage: chcon [-hRv] CONTEXT FILE...
Change the SELinux security context of listed file[s].
-h change symlinks instead of what they point to.
-R recurse into subdirectories.
-v verbose output.
chcon: Need 2 arguments
rm: /system/xbin/su: No such file or directory
failed to copy 'su_bin/su' to '/system/xbin/su': Read-only file system
chown: /system/xbin/su: No such file or directory
chown: /system/xbin/su: No such file or directory
chmod: /system/xbin/su: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: /system/xbin/su: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: /system/xbin/su: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
usage: chcon [-hRv] CONTEXT FILE...
Change the SELinux security context of listed file[s].
-h change symlinks instead of what they point to.
-R recurse into subdirectories.
-v verbose output.
chcon: Need 2 arguments
rm: /system/xbin/daemonsu: No such file or directory
failed to copy 'su_bin/su' to '/system/xbin/daemonsu': Read-only file system
chown: /system/xbin/daemonsu: No such file or directory
chown: /system/xbin/daemonsu: No such file or directory
chmod: /system/xbin/daemonsu: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: /system/xbin/daemonsu: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: /system/xbin/daemonsu: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
usage: chcon [-hRv] CONTEXT FILE...
Change the SELinux security context of listed file[s].
-h change symlinks instead of what they point to.
-R recurse into subdirectories.
-v verbose output.
chcon: Need 2 arguments
rm: /system/xbin/sugote: No such file or directory
failed to copy 'su_bin/su' to '/system/xbin/sugote': Read-only file system
chown: /system/xbin/sugote: No such file or directory
chown: /system/xbin/sugote: No such file or directory
chmod: /system/xbin/sugote: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: /system/xbin/sugote: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: /system/xbin/sugote: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: /system/xbin/sugote: No such file or directory
rm: /system/xbin/sugote-mksh: No such file or directory
/system/bin/sh: can't create /system/xbin/sugote-mksh: Read-only file system
chown: /system/xbin/sugote-mksh: No such file or directory
chown: /system/xbin/sugote-mksh: No such file or directory
chmod: /system/xbin/sugote-mksh: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: /system/xbin/sugote-mksh: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: /system/xbin/sugote-mksh: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
usage: chcon [-hRv] CONTEXT FILE...
Change the SELinux security context of listed file[s].
-h change symlinks instead of what they point to.
-R recurse into subdirectories.
-v verbose output.
chcon: Need 2 arguments
rm: /system/xbin/supolicy: No such file or directory
failed to copy 'su_bin/supolicy' to '/system/xbin/supolicy': Read-only file system
chown: /system/xbin/supolicy: No such file or directory
chown: /system/xbin/supolicy: No such file or directory
chmod: /system/xbin/supolicy: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: /system/xbin/supolicy: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: /system/xbin/supolicy: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
usage: chcon [-hRv] CONTEXT FILE...
Change the SELinux security context of listed file[s].
-h change symlinks instead of what they point to.
-R recurse into subdirectories.
-v verbose output.
chcon: Need 2 arguments
rm: /system/lib64/libsupol.so: No such file or directory
failed to copy 'su_bin/libsupol.so' to '/system/lib64/libsupol.so': Read-only file system
chown: /system/lib64/libsupol.so: No such file or directory
chown: /system/lib64/libsupol.so: No such file or directory
chmod: /system/lib64/libsupol.so: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: /system/lib64/libsupol.so: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: /system/lib64/libsupol.so: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
usage: chcon [-hRv] CONTEXT FILE...
Change the SELinux security context of listed file[s].
-h change symlinks instead of what they point to.
-R recurse into subdirectories.
-v verbose output.
chcon: Need 2 arguments
chown: /system/app/SuperSU: No such file or directory
chown: /system/app/SuperSU: No such file or directory
chmod: /system/app/SuperSU: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: /system/app/SuperSU: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: /system/app/SuperSU: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
usage: chcon [-hRv] CONTEXT FILE...
Change the SELinux security context of listed file[s].
-h change symlinks instead of what they point to.
-R recurse into subdirectories.
-v verbose output.
chcon: Need 2 arguments
rm: /system/app/SuperSU/SuperSU.apk: No such file or directory
failed to copy 'su_bin/Superuser.apk' to '/system/app/SuperSU/SuperSU.apk': Read-only file system
chown: /system/app/SuperSU/SuperSU.apk: No such file or directory
chown: /system/app/SuperSU/SuperSU.apk: No such file or directory
chmod: /system/app/SuperSU/SuperSU.apk: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: /system/app/SuperSU/SuperSU.apk: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: /system/app/SuperSU/SuperSU.apk: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
usage: chcon [-hRv] CONTEXT FILE...
Change the SELinux security context of listed file[s].
-h change symlinks instead of what they point to.
-R recurse into subdirectories.
-v verbose output.
chcon: Need 2 arguments
rm: /system/etc/install-recovery.sh: No such file or directory
failed to copy 'su_bin/install-recovery.sh' to '/system/etc/install-recovery.sh': Read-only file system
chown: /system/etc/install-recovery.sh: No such file or directory
chown: /system/etc/install-recovery.sh: No such file or directory
chmod: /system/etc/install-recovery.sh: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: /system/etc/install-recovery.sh: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: /system/etc/install-recovery.sh: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
usage: chcon [-hRv] CONTEXT FILE...
Change the SELinux security context of listed file[s].
-h change symlinks instead of what they point to.
-R recurse into subdirectories.
-v verbose output.
chcon: Need 2 arguments
/system/bin/sh: /system/toolbox: not found
ln: no such tool
ln: cannot create symbolic link from '/system/etc/install-recovery.sh' to '/system/bin/install-recovery.sh': File exists
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: '/system/bin/install-recovery.sh' to u:object_r:system_file:s0: Read-only file system
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: '/system/bin/install-recovery.sh' to u:object_r:system_file:s0: Read-only file system
rm: /system/bin/app_process: Read-only file system
/system/bin/sh: /system/toolbox: not found
ln: no such tool
ln: cannot create symbolic link from '/system/xbin/daemonsu' to '/system/bin/app_process': File exists
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: '/system/bin/app_process' to u:object_r:system_file:s0: Read-only file system
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: '/system/bin/app_process' to u:object_r:system_file:s0: Read-only file system
mv: bad '/system/bin/app_process64': Read-only file system
/system/bin/sh: /system/toolbox: not found
ln: no such tool
ln: cannot create symbolic link from '/system/xbin/daemonsu' to '/system/bin/app_process64': File exists
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: '/system/bin/app_process64' to u:object_r:system_file:s0: Read-only file system
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: '/system/bin/app_process64' to u:object_r:system_file:s0: Read-only file system
rm: /system/bin/app_process_init: No such file or directory
/system/bin/sh: can't create /system/bin/app_process_init: Read-only file system
chown: /system/bin/app_process_init: No such file or directory
chown: /system/bin/app_process_init: No such file or directory
chmod: /system/bin/app_process_init: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: /system/bin/app_process_init: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: /system/bin/app_process_init: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
usage: chcon [-hRv] CONTEXT FILE...
Change the SELinux security context of listed file[s].
-h change symlinks instead of what they point to.
-R recurse into subdirectories.
-v verbose output.
chcon: Need 2 arguments
rm: /system/etc/init.d/99SuperSUDaemon: No such file or directory
failed to copy 'su_bin/99SuperSUDaemon' to '/system/etc/init.d/99SuperSUDaemon': Read-only file system
chown: /system/etc/init.d/99SuperSUDaemon: No such file or directory
chown: /system/etc/init.d/99SuperSUDaemon: No such file or directory
chmod: /system/etc/init.d/99SuperSUDaemon: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: /system/etc/init.d/99SuperSUDaemon: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
chcon: /system/etc/init.d/99SuperSUDaemon: No such file or directory
/system/bin/sh: /system/toolbox: not found
chcon: no such tool
usage: chcon [-hRv] CONTEXT FILE...
Change the SELinux security context of listed file[s].
-h change symlinks instead of what they point to.
-R recurse into subdirectories.
-v verbose output.
chcon: Need 2 arguments