Related
hello xda :
whenever I use autoapktool to decompile systemUI.apk it succeds and decompiles but when I recompile it it fails and show me
Code:
[*] "C:\Documents and Settings\Copy Center\Desktop\AutoAPKTool2.0.4\_INPUT_APK\SystemUI"
recompiling "C:\Documents and Settings\Copy Center\Desktop\AutoAPKTool2.0.4\_INPUT_APK\SystemUI"...
I: Smaling...
I: Building resources...
I: Building apk file...
The system cannot find the drive specified.
I used many options to recompile :
recompile apk <folder>
build usable apk
recompile build <folder>
and all of them fails.
additional info : I installed frameworks.apk
help please , sorry if am asking to much , I am a very noob at this
Is ur output target another storage device or target ...maybe ur sd card or whatever is not properly connected...
Sent from my GT-S5360 using xda app-developers app
anubhavrev said:
Is ur output target another storage device or target ...maybe ur sd card or whatever is not properly connected...
Sent from my GT-S5360 using xda app-developers app
Click to expand...
Click to collapse
no
I tried in many devices but alway show me thris error :crying::crying:
Try downloading another apktool package....
Sent from my GT-S5360 using xda app-developers app
I have been trying to build CM 10.2 all day and now keep getting errors while it is building. Here are the last few lines I am getting during the build before it stops. I am using Ubuntu 12.04 to build with.
Export includes file: external/strace/Android.mk -- /home/mike/android/system/out/target/product/mako/obj/EXECUTABLES/strace_intermediates/export_includes
Notice file: external/strace/NOTICE -- /home/mike/android/system/out/target/product/mako/obj/NOTICE_FILES/src//system/xbin/strace.txt
Import includes file: /home/mike/android/system/out/target/product/mako/obj/EXECUTABLES/vim_intermediates/import_includes
Export includes file: external/vim/src/Android.mk -- /home/mike/android/system/out/target/product/mako/obj/EXECUTABLES/vim_intermediates/export_includes
make: *** No rule to make target `vendor/lge/mako/proprietary/etc/DxHDCP.cfg', needed by `/home/mike/android/system/out/target/product/mako/system/etc/DxHDCP.cfg'. Stop.
make: *** Waiting for unfinished jobs....
Click to expand...
Click to collapse
Anyone have any ideas what my problem is?
mikeric said:
I have been trying to build CM 10.2 all day and now keep getting errors while it is building. Here are the last few lines I am getting during the build before it stops. I am using Ubuntu 12.04 to build with.
Anyone have any ideas what my problem is?
Click to expand...
Click to collapse
I think you don't have the proprietary blobs.
From http://wiki.cyanogenmod.org/w/Build_for_mako#Extract_proprietary_blobs
Now ensure that your Nexus 4 is connected to your computer via the USB cable and that you are in the ~/android/system/device/lge/mako directory (you can cd ~/android/system/device/lge/mako if necessary). Then run the extract-files.sh script:
$ ./extract-files.sh
You should see the proprietary files (aka “blobs”) get pulled from the device and moved to the right place in the vendor directory. If you see errors about adb being unable to pull the files, adb may not be in the path of execution. If this is the case, see the adb page for suggestions for dealing with "command not found" errors.
eris23 said:
I think you don't have the proprietary blobs.
From http://wiki.cyanogenmod.org/w/Build_for_mako#Extract_proprietary_blobs
Now ensure that your Nexus 4 is connected to your computer via the USB cable and that you are in the ~/android/system/device/lge/mako directory (you can cd ~/android/system/device/lge/mako if necessary). Then run the extract-files.sh script:
$ ./extract-files.sh
You should see the proprietary files (aka “blobs”) get pulled from the device and moved to the right place in the vendor directory. If you see errors about adb being unable to pull the files, adb may not be in the path of execution. If this is the case, see the adb page for suggestions for dealing with "command not found" errors.
Click to expand...
Click to collapse
I redid the proprietary files and now I am getting it to run for a while then getting this at the end while building. While it is extracting the proprietary blobs I am getting a lot of errors, but not adb errors.
target thumb C: openvpn <= external/openvpn/android.c
make: *** No rule to make target `vendor/lge/mako/proprietary/etc/DxHDCP.cfg', needed by `/home/mike/android/system/out/target/product/mako/system/etc/DxHDCP.cfg'. Stop.
make: *** Waiting for unfinished jobs....
In file included from external/openvpn/misc.h:30:0,
from external/openvpn/android.c:8:
external/openvpn/integer.h: In function 'index_verify':
external/openvpn/integer.h:106:5: warning: comparison of unsigned expression >= 0 is always true [-Wtype-limits]
external/openvpn/android.c: In function 'env_set_add_android':
external/openvpn/android.c:29:18: warning: initialization discards 'const' qualifier from pointer target type [enabled by default]
external/openvpn/android.c:25:9: warning: unused variable 'and_env_value' [-Wunused-variable]
Click to expand...
Click to collapse
Does anyone have any suggestions?
Sent from my Nexus 4 using Tapatalk 4
Is your n4 already running cm10.2?
If not the blobs would be wrong and some are named different in cm10.1
Edit: try to extract the missing file from an official nightly
Sent from my Nexus 4 using xda premium
OK I'll try that, thanks for the suggestion
Sent from my Nexus 4 using Tapatalk 4
I am running cm10.2 nightly 8/15 and tried to pull the proprietary blobs and kept getting all these errors. If I try and build it still wont. This is just a few of the errors.
cannot create '../../../vendor/lge/mako/proprietary/vendor/firmware/keymaster/keymaster.b00': Permission denied
cannot create '../../../vendor/lge/mako/proprietary/vendor/firmware/keymaster/keymaster.b01': Permission denied
cannot create '../../../vendor/lge/mako/proprietary/vendor/firmware/keymaster/keymaster.b02': Permission denied
cannot create '../../../vendor/lge/mako/proprietary/vendor/firmware/keymaster/keymaster.b03': Permission denied
cannot create '../../../vendor/lge/mako/proprietary/vendor/firmware/keymaster/keymaster.mdt': Permission denied
cannot create '../../../vendor/lge/mako/proprietary/vendor/lib/libdrmdecrypt.so': Permission denied
cannot create '../../../vendor/lge/mako/proprietary/vendor/lib/libWVStreamControlAPI_L1.so': Permission denied
cannot create '../../../vendor/lge/mako/proprietary/vendor/lib/libwvm.so': Permission denied
cannot create '../../../vendor/lge/mako/proprietary/vendor/lib/libwvdrm_L1.so': Permission denied
cannot create '../../../vendor/lge/mako/proprietary/vendor/lib/drm/libdrmwvmplugin.so': Permission denied
Click to expand...
Click to collapse
Looks like you messed up the permissions in your build env ...
Repo sync -d
Might solve this
Sent from my Nexus 4 using xda premium
Keep in mind when you read this that I am a complete noob at building android in general, I just can't wait to use this rom. I have successfully built CyanogenMod before, but that's it.
So, I've got my Ubuntu VM which I've built CyanogenMod in before, and I'm attempting to init a repo with the command (repo init -u git://github.com/omnirom/android.git), and it creates a bunch of tags, then I get an error "Error: revision refs/heads/master in manifests not found". Each subsequent time I try to run the command I get "Error: manifest required for this command -- please run init". It also appears that the .repo folder is pretty empty as compared to my cyanogen one.
Am I doing something wrong? Or am I just jumping the gun and the rom isn't ready to build yet.
Or they named the manifest different, or it needs to be updated first I think, I got the same error.
Sent from my Nexus 7 using XDA Premium 4 mobile app
legomaster181 said:
Keep in mind when you read this that I am a complete noob at building android in general, I just can't wait to use this rom. I have successfully built CyanogenMod before, but that's it.
So, I've got my Ubuntu VM which I've built CyanogenMod in before, and I'm attempting to init a repo with the command (repo init -u git://github.com/omnirom/android.git), and it creates a bunch of tags, then I get an error "Error: revision refs/heads/master in manifests not found". Each subsequent time I try to run the command I get "Error: manifest required for this command -- please run init". It also appears that the .repo folder is pretty empty as compared to my cyanogen one.
Am I doing something wrong? Or am I just jumping the gun and the rom isn't ready to build yet.
Click to expand...
Click to collapse
Archaic1881 said:
Or they named the manifest different, or it needs to be updated first I think, I got the same error.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Try this, after looking in the omnirom/android sub you will see there is a branch option which you must supply in the repo init command thru the -b command line parameter
Code:
repo init -u git://github.com/omnirom/android.git -b android-4.3
it's working for me, downloading source as we speak.. If I can get a successful build for my N4 I will post any findings / issues that I come across that can possibly help others to build also..
VoiD_Dweller said:
Try this, after looking in the omnirom/android sub you will see there is a branch option which you must supply in the repo init command thru the -b command line parameter
Code:
repo init -u git://github.com/omnirom/android.git -b android-4.3
it's working for me, downloading source as we speak.. If I can get a successful build for my N4 I will post any findings / issues that I come across that can possibly help others to build also..
Click to expand...
Click to collapse
I think they must've fixed it, because I swear I tried that before, but it's working now. Thanks!
Same here. At least it works now.
Sent from my Nexus 7 using XDA Premium 4 mobile app
legomaster181 said:
I think they must've fixed it, because I swear I tried that before, but it's working now. Thanks!
Click to expand...
Click to collapse
Yeah, I originally tried it without the branch specified and got the same error..
I faced similar problem, found a workaround
VoiD_Dweller said:
Yeah, I originally tried it without the branch specified and got the same error..
Click to expand...
Click to collapse
In repo sync I faced similar problem.
...
Fetching projects: 68% (11/16) Fetching project css/scripts.git
Fetching projects: 75% (12/16) Fetching project linuxbsp/u-boot.git
Fetching projects: 100% (16/16), done.
error: manifest required for this command -- please run init
After analyzing a bit, I found for one of the git repo the checkout folder is created and it is empty.
(originally It happend because the branch I was trying to checkout was not existing)
I deleted the empty folder and ran repo sync again. problem was solved.
May be a bug in repo to be fixed?
another option is to use an "strace" for instance when i have problems downloading i will use this $ strace repo sync -f" it will show you the path of the missing file which can easily be removed for a resync
I am trying to build omnirom 4.4 for the Nexus 4 (Mako) however I get to extracting the proprietary blobs and I get this error:
:~/android/omni/device/lge/mako$ ./extract-files.sh
bash: ./extract-files.sh: No such file or directory
When I look in the folders I don't find that file in the mako directory however when I look in the directory for my TF300T I do find that file.
Am I doing something wrong when trying to set up the directory for Mako?
No, Omni doesn't have that file for the mako. You can either download the files elsewhere, create the file yourself (and feel free to submit to Gerrit), or find a github that's setup with proprietary files and add it to your local_manifest (this is my recommendation). I'd add DonkeyCoyote or TheMuppets to your local manifest, that way when you repo sync, it says up to date, and you don't have to find the updated files yourself.
Granted, this is all off the top of my head while laying in bed on tapatalk, so I apologize for being brief. If you need further assistance, let me know which part you didn't get, and I'll try to answer in more depth in the morning (about 12 hours).
themuppets won't work...
And extract-files being missing is a bug.
So if themuppets won't work would I be able to get away with downloading cyanogenmod and extracting the files there and then copying it to omni ROM?
Sent from my Nexus 4 using xda app-developers app
munspartan said:
So if themuppets won't work would I be able to get away with downloading cyanogenmod and extracting the files there and then copying it to omni ROM?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I don't know exactly (Entropy probably does). Or you could add DonkeyCoyote to you local_manifest. That's what I do for my builds:
https://github.com/DonkeyCoyote/proprietary_vendor_lge/tree/android-4.4/mako
Edit: glancing through github, there's other devices without extract-files being there. I should make a list at some point.
munspartan said:
I am trying to build omnirom 4.4 for the Nexus 4 (Mako) however I get to extracting the proprietary blobs and I get this error:
:~/android/omni/device/lge/mako$ ./extract-files.sh
bash: ./extract-files.sh: No such file or directory
When I look in the folders I don't find that file in the mako directory however when I look in the directory for my TF300T I do find that file.
Am I doing something wrong when trying to set up the directory for Mako?
Click to expand...
Click to collapse
I suppose that u can download from github cyano the extract-file:
https://github.com/CyanogenMod/android_device_lge_mako/tree/cm-11.0/self-extractors
and copy it in /android/omni/device/lge/mako and run again the command
Sent from my Nexus 7 2013 LTE using XDA Premium 4 mobile app
I've got my repo synced to the pac-4.4 branch, but now that the team has switched repos to Pinky Inky and Clyde, my repo syncs have been failing. Can somebody help walk me through the steps to set everything back up using the new repo?
numel007 said:
I've got my repo synced to the pac-4.4 branch, but now that the team has switched repos to Pinky Inky and Clyde, my repo syncs have been failing. Can somebody help walk me through the steps to set everything back up using the new repo?
Click to expand...
Click to collapse
What device are you trying to build for, what is the error you're getting, what is the contents of your roomservice file?
Sent from my Xperia Ray using Tapatalk
Langes said:
What device are you trying to build for, what is the error you're getting, what is the contents of your roomservice file?
Sent from my Xperia Ray using Tapatalk
Click to expand...
Click to collapse
I will be building for the HTC LTE aka Jewel
Fatal error message was: Fetching projects: 80% (355/443) error: Cannot fetch pacman
error: Exited sync due to fetch errors
Full log can be found here: http://pastebin.com/G9UbGBuG
Roomservice.xml inside .repo/local_manifests is:
<manifest><project name="CyanogenMod/android_device_htc_jewel" path="device/htc/jewel" remote="github" revision="cm-11.0"/><project name="CyanogenMod/android_device_htc_msm8960-common" path="device/htc/msm8960-common" remote="github" revision="cm-11.0"/><project name="CyanogenMod/android_device_htc_s4-common" path="device/htc/s4-common" remote="github" revision="cm-11.0"/><project name="CyanogenMod/android_kernel_htc_msm8960" path="kernel/htc/msm8960" remote="github" revision="cm-11.0"/><project name="Pinky-Inky-and-Clyde/proprietary_vendor_htc" path="vendor/htc" remote="github" revision="cm-11.0"/></manifest>
Click to expand...
Click to collapse
numel007 said:
I will be building for the HTC LTE aka Jewel
Fatal error message was: Fetching projects: 80% (355/443) error: Cannot fetch pacman
error: Exited sync due to fetch errors
Full log can be found here: http://pastebin.com/G9UbGBuG
Roomservice.xml inside .repo/local_manifests is:
Click to expand...
Click to collapse
roomservice is 100%
Delete the default.xml file in .repo folder and do the init repo command again. This should fix you up as the pacman folder was renamed and your repo did not update that somehow.
Code:
repo init -u git://github.com/PAC-man/pacman.git -b pac-4.4
Langes said:
roomservice is 100%
Delete the default.xml file in .repo folder and do the init repo command again. This should fix you up as the pacman folder was renamed and your repo did not update that somehow.
Code:
repo init -u git://github.com/PAC-man/pacman.git -b pac-4.4
Click to expand...
Click to collapse
Deleting the file and rerunning the command causes an immediate fatal error since the default.xml file can not be found. Should I restore it and just delete everything inside the file?
[email protected]:~/PacRom-4.4$ repo init -u git://github.com/PAC-man/pacman.git -b pac-4.4
fatal: manifest 'default.xml' not available
fatal: manifest default.xml not found
[email protected]:~/PacRom-4.4$
Click to expand...
Click to collapse
numel007 said:
Deleting the file and rerunning the command causes an immediate fatal error since the default.xml file can not be found. Should I restore it and just delete everything inside the file?
Click to expand...
Click to collapse
My bad, you should delete manifest.xml inside the ~/PacRom-4.4/.repo folder and init again.
Langes said:
My bad, you should delete manifest.xml inside the ~/PacRom-4.4/.repo folder and init again.
Click to expand...
Click to collapse
File deleted, terminal restarted. Initiated repo again, ran repo sync, same failure as before unfortunately. Looks like somehow my repo isn't updating even after manifest.xml was deleted.
numel007 said:
File deleted, terminal restarted. Initiated repo again, ran repo sync, same failure as before unfortunately. Looks like somehow my repo isn't updating even after manifest.xml was deleted.
Click to expand...
Click to collapse
Do you have any other xml files in .repo and in .repo/local_manifests? If you do, delete them all.
Do you have an android or a pacman folder in the top folder of you source tree? Or both?
Langes said:
Do you have any other xml files in .repo and in .repo/local_manifests? If you do, delete them all.
Do you have an android or a pacman folder in the top folder of you source tree? Or both?
Click to expand...
Click to collapse
Any and all xmls? And yes I have an Android folder in root of files.
Edit: Did a search for all xml files and deleted roomservice and manifest. Had to keep default to make the repo init still run. Repo sync ended with one error less. Still can not retrieve from pac. I also deleted the default.xml in the android folder.
Fetching project platform/external/lzma
Fetching projects: 99% (434/438) fatal: Not a git repository: '/home/derek/PacRom-4.4/.repo/projects/pacman.git'
error: Cannot fetch pacman
error: Exited sync due to fetch errors
numel007 said:
Any and all xmls? And yes I have an Android folder in root of files.
Edit: Did a search for all xml files and deleted roomservice and manifest. Had to keep default to make the repo init still run. Repo sync ended with one error less. Still can not retrieve from pac. I also deleted the default.xml in the android folder.
Fetching projects: 99% (434/438) error: Cannot fetch pacman
error: Exited sync due to fetch errors
Click to expand...
Click to collapse
ok, delete all folders and files in your source folder except .repo (the source code you have downloaded is in .repo so you will not have to re-download everything)
then run the init command again and sync again
Langes said:
ok, delete all folders and files in your source folder except .repo (the source code you have downloaded is in .repo so you will not have to re-download everything)
then run the init command again and sync again
Click to expand...
Click to collapse
Deleted everything but .repo and ran init again. Repo sync still can't fetch from pac. Maybe I should just do a fresh start and reset the entire build envirnment.
numel007 said:
Deleted everything but .repo and ran init again. Repo sync still can't fetch from pac. Maybe I should just do a fresh start and reset the entire build envirnment.
Click to expand...
Click to collapse
Compare the contents of manifests.xml inside the .repo folder to this: https://github.com/PAC-man/pacman/blob/pac-4.4/default.xml
Line 499 should read:
Code:
<project path="pacman" name="pacman" remote="pac" revision="pac-4.4" />
Langes said:
Compare the contents of manifests.xml inside the .repo folder to this: https://github.com/PAC-man/pacman/blob/pac-4.4/default.xml
Line 499 should read:
Code:
<project path="pacman" name="pacman" remote="pac" revision="pac-4.4" />
Click to expand...
Click to collapse
Yes line 499 read that. But to play it safe, I deleted the entire file and replaced it with a straight paste from that link you gave me. Repo init again, then repo sync, same failure. Out of ideas yet? lol
rm -rf .repo/projects/device/*
repo sync
arrrghhh said:
rm -rf .repo/projects/device/*
repo sync
Click to expand...
Click to collapse
Thank you. Unfortunately I already deleted my entire source code and redownloaded. Thankfully everything works now. Thanks for the input, both of you.
Sent from my EVO