Hello
I am having troubles getting my roms to compile. I keep getting the same error in each one. If someone could let me know what I am doing wrong that would be great. I am using linux ubuntu 12.10 and go through all the instructions on building the roms. Even on ones where it says that it is completely set up I get the same error. Here it is.
make: *** No rule to make target `/home/paulg/android/rootbox/out/target/product/ville/obj/lib/libmmjpeg.so', needed by `/home/paulg/android/rootbox/out/target/product/ville/obj/SHARED_LIBRARIES/camera.msm8960_intermediates/LINKED/camera.msm8960.so'. Stop.
I guess the solution would be to take the file from another rom and put it into the directory but there has to be another way to do this besides doing that.
I also have another error where it says the libril directory from hardware/lib/libril is conflictin with the direcory msm-8960-common/libril ( not excatly like that but close enough). To fix this I just erase the hardware/lib/libril directory and leave the msm8960-common intact and let it compile from there. I don't know if this is right or not. If someone knows this one let me know.
Thank you.
Paul
atrus5 said:
Hello
I am having troubles getting my roms to compile. I keep getting the same error in each one. If someone could let me know what I am doing wrong that would be great. I am using linux ubuntu 12.10 and go through all the instructions on building the roms. Even on ones where it says that it is completely set up I get the same error. Here it is.
make: *** No rule to make target `/home/paulg/android/rootbox/out/target/product/ville/obj/lib/libmmjpeg.so', needed by `/home/paulg/android/rootbox/out/target/product/ville/obj/SHARED_LIBRARIES/camera.msm8960_intermediates/LINKED/camera.msm8960.so'. Stop.
I guess the solution would be to take the file from another rom and put it into the directory but there has to be another way to do this besides doing that.
I also have another error where it says the libril directory from hardware/lib/libril is conflictin with the direcory msm-8960-common/libril ( not excatly like that but close enough). To fix this I just erase the hardware/lib/libril directory and leave the msm8960-common intact and let it compile from there. I don't know if this is right or not. If someone knows this one let me know.
Thank you.
Paul
Click to expand...
Click to collapse
Never mind I figured it out and compiled rootbox for Htc One S
atrus5 said:
Never mind I figured it out and compiled rootbox for Htc One S
Click to expand...
Click to collapse
What was your solution for the libmmjpeg.so error? I'm having the same problem for another device
Thanks,
Mike
mikshepard said:
What was your solution for the libmmjpeg.so error? I'm having the same problem for another device
Thanks,
Mike
Click to expand...
Click to collapse
You can get this file and all the other proprietary files by entering extract-files.sh from your device/devic_company/device_name directory from whatever rom you are trying to build. If you have done this then there should be a file that will automatically copy it or else you will have to copy it to the out/target/product/device_name/system/lib directory. You might want to also check that you have the correct manifest files in local_manifest for whatever device you are trying to build. usually there is a cm.dependencies file in the device/device_company/device_name directory that will tell you exactly what manifest to use. If you have any other questions let me know. I hope this helps.
atrus5 said:
You can get this file and all the other proprietary files by entering extract-files.sh from your device/devic_company/device_name directory from whatever rom you are trying to build. If you have done this then there should be a file that will automatically copy it or else you will have to copy it to the out/target/product/device_name/system/lib directory. You might want to also check that you have the correct manifest files in local_manifest for whatever device you are trying to build. usually there is a cm.dependencies file in the device/device_company/device_name directory that will tell you exactly what manifest to use. If you have any other questions let me know. I hope this helps.
Click to expand...
Click to collapse
oh wow, hahaha, I was in such a hurry, I completely missed that. I never used the extract-files.sh as all the proprietary files for my htc devices used to be hosted on github but recently got pulled due to a legal problem with the camera drivers. I had the files backed up on my old computer but forgot to copy them over to the new one. Wow, amateur mistake but one that would have taken me a while to catch. Many thanks man!!
-Mike
mikshepard said:
oh wow, hahaha, I was in such a hurry, I completely missed that. I never used the extract-files.sh as all the proprietary files for my htc devices used to be hosted on github but recently got pulled due to a legal problem with the camera drivers. I had the files backed up on my old computer but forgot to copy them over to the new one. Wow, amateur mistake but one that would have taken me a while to catch. Many thanks man!!
-Mike
Click to expand...
Click to collapse
No problem.
I had the same problem with ville. Got the files pulled so made up my own repo with all the files that are needed.
Related
I'm sure this has been asked before but after prolific searching of the forums and our friend Google I turn to you guys for help. As the title says I'm using OS X and I need a solution (that isn't dual booting to use XP) to signing the update.zip so that I can customise aspects of my ROM, I'm very eager to learn how to do this and this so far seems to be quite an annoying problem.
Thanks for your time in advance
tristyB said:
I'm sure this has been asked before but after prolific searching of the forums and our friend Google I turn to you guys for help. As the title says I'm using OS X and I need a solution (that isn't dual booting to use XP) to signing the update.zip so that I can customise aspects of my ROM, I'm very eager to learn how to do this and this so far seems to be quite an annoying problem.
Thanks for your time in advance
Click to expand...
Click to collapse
pm me............
korndub said:
pm me............
Click to expand...
Click to collapse
Hi korndub,
Cannot you post the answer here so everybody that uses OS X can also sign?
I'm also having problems signing full roms (update.zip files) with signapk.jar
Any help is appreciated
rommelin said:
Hi korndub,
Cannot you post the answer here so everybody that uses OS X can also sign?
I'm also having problems signing full roms (update.zip files) with signapk.jar
Any help is appreciated
Click to expand...
Click to collapse
i have a folder on the desktop which contains the signapk.jar and both sets of keys...put the Archive.zip that you have created and want to sign in this folder, then open terminal
in terminal, you type
$cd FOLDER-containing-files
$java -jar signapk.jar testkeys.x509.pem testkey.pk8 Inputfile.zip outputfile.zip
the outputfile.zip is your update which is signed....
OK, I do all that I think.
Heres my process.
Download ROM
Extract downloaded zip to folder eg update
Make changes to files
Compress folder back to zip eg update1.zip
java -jar signapk.jar testkeys.x509.pem testkey.pk8 update1.zip update_signed.zip
rename and copy the signed file to sd
reboot recovery
wipe and apply update
It doesn't moan about the signing (so I assume its ok) but I get an update script not found error and it doesn't install.
I haven't changed the update scripts, only the boot.img and one or two scripts in system.
Does every file I change have to be resigned as well? I muct be missing something here
on OSX 10.5
Signing has nothing to do with that error. Make sure that the update-script is in the correct path.
META-INF/com/google/android/update-script
it is, is a normal update.zip (ie cyanogen rom), and the only file I've changed is boot.img and a2sd in system/bin
i have a folder on the desktop which contains the signapk.jar and both sets of keys...put the Archive.zip that you have created and want to sign in this folder, then open terminal
in terminal, you type
$cd FOLDER-containing-files
$java -jar signapk.jar testkeys.x509.pem testkey.pk8 Inputfile.zip outputfile.zip
the outputfile.zip is your update which is signed....
Click to expand...
Click to collapse
Thank you so much, this works for me, I might try and build it into an automator workflow
Edit: I spoke too soon, I get the update script error also
Edit Again: my update-script is in the same place as it should be also
Wonder if this is a specific OSX problem? We do have apples 'interpretation' of java don't we?
dazcox5181 said:
Wonder if this is a specific OSX problem? We do have apples 'interpretation' of java don't we?
Click to expand...
Click to collapse
haha, yeah that's right, those crazy cats at Apple. but I assume that korndub also has Apples 'interptretation' so something else could be the problem also
perhaps the way we zip the archive?
dazcox5181 said:
perhaps the way we zip the archive?
Click to expand...
Click to collapse
sadly not, I just used a application that zips in a PC format (without mac hidden files) and no joy. Good idea though.
Edit: Just tried archiving the zip but not compressing. Thought I was on to something. I wasn't.
Another update, I have tried the same in Fedora 11 and again, getting the update script error message when I flash.
I signed modified update for 3 different builds on my Mac, everything worked w/o problems every time. I did everything like described in readme and several times here. So, it's not a global OS X problem.
BTW, I used muCommander to directly modify all zips.
neuro159 said:
I signed modified update for 3 different builds on my Mac, everything worked w/o problems every time. I did everything like described in readme and several times here. So, it's not a global OS X problem.
BTW, I used muCommander to directly modify all zips.
Click to expand...
Click to collapse
When I find the time later on I will give the muCommander a go. Fingers crossed.
dazcox5181 said:
OK, I do all that I think.
Heres my process.
Download ROM
Extract downloaded zip to folder eg update
Make changes to files
Compress folder back to zip eg update1.zip
java -jar signapk.jar testkeys.x509.pem testkey.pk8 update1.zip update_signed.zip
rename and copy the signed file to sd
reboot recovery
wipe and apply update
It doesn't moan about the signing (so I assume its ok) but I get an update script not found error and it doesn't install.
I haven't changed the update scripts, only the boot.img and one or two scripts in system.
Does every file I change have to be resigned as well? I muct be missing something here
on OSX 10.5
Click to expand...
Click to collapse
you dont archive (zip) the folder, this is where you are having the issue... say you extracted the rom to ROMFOLDER, what you need to do is go into that folder, select all, then right click or two finger click and choose Compress - you will end up with an archive that contains all sub folders, if you zip the folder then you have a folder within a folder and that is where all goes south..
korndub said:
you dont archive (zip) the folder, this is where you are having the issue... say you extracted the rom to ROMFOLDER, what you need to do is go into that folder, select all, then right click or two finger click and choose Compress - you will end up with an archive that contains all sub folders, if you zip the folder then you have a folder within a folder and that is where all goes south..
Click to expand...
Click to collapse
Oh my god, you're right. And I think I actually read that somewhere before now you've reminded me. Damn. Thanks though! Thanks a lot!
Awesome, knew it was me being stupid.
sure thing guys! glad i could help...
Always something stupid...
With the help of red_menace over at the apple support forum, I present Mac users with an application that will sign their .apk and .zip files.
It is a droplet application, meaning you just have to drag the file you want signed onto the application itself. A new file will be created with -signed at the end of the file name.
For this to work you need to have testsign.jar in your root directory. The root directory is the first place you come to when you click on the mac hard drive.
If anyone wants to use or edit the script that's fine with me, I really didn't do much, just asked the right people for help.
Android-sign.zip Download
Android-sign.zip has both the testsign.jar and android-sign application.
EDIT: Sorry about the mixup. Testsign.jar is now linked above.
thank you sir! will try tonight
Exception in thread "main"
java.lang.NoClassDefFoundError: testsign
I cant find the testsign.jar its not in the tool directory of my SDK that I downloaded from Androids website
Where can I get this testsign.jar?
*EDIT*
I found the testsign.jar in the forums. You can get it here: http://forum.xda-developers.com/showthread.php?t=538020
But I still get the same error I've placed the program and the testsign.jar file in the same directory.
I have some cool skins in the making! I just need to know how to sign these files! I'm on a mac.
Why am I getting the error?
wow i need this bad...now lets c if i know how to get it 2 work....
MurderDeathKill said:
But I still get the same error I've placed the program and the testsign.jar file in the same directory.
I have some cool skins in the making! I just need to know how to sign these files! I'm on a mac.
Why am I getting the error?
Click to expand...
Click to collapse
are you putting the testsign.jar in your ROOT dir? aka where adb is
same error
Okay, so I'm getting the same error. And yes, my testsign.jar/Android-sign.app are both in my sdk/tools dir.
Not sure what the problem is.
Hope I can get this to work
jaaronmoody said:
are you putting the testsign.jar in your ROOT dir? aka where adb is
Click to expand...
Click to collapse
What file is the adb? I understand what adb means and what it does, but I don't know how to identify it.
Ok so since im new to this can someone can make a really dumb guide for me from dowloading the app to putting the test.jar file please.
im getting the same error, this is a huge step though when u figure out whats going on with the rest of our Auto-sign, repost thanks nd thumbs up
nice...thx for sharing this. will come in handy
oops, still getting used to all this. haha
ffff00 said:
Okay, so I'm getting the same error. And yes, my testsign.jar/Android-sign.app are both in my sdk/tools dir.
Not sure what the problem is.
Hope I can get this to work
Click to expand...
Click to collapse
the testsign.jar needs to be in the root directory of your computer. The app can be placed anywhere you would like. Where ever you put the app, the new signed file will be also.
guys so lets say i put meltus audio hack in cyanogen 4.9999 and i want to sign the whole build back up how would i do that.
thank you
jessetbenton said:
the testsign.jar needs to be in the root directory of your computer. The app can be placed anywhere you would like. Where ever you put the app, the new signed file will be also.
Click to expand...
Click to collapse
Oh okay, thanks.
You said to put it in the same folder as adb is why I was confused.
I'll try this out in a few.
ffff00 said:
Oh okay, thanks.
You said to put it in the same folder as adb is why I was confused.
I'll try this out in a few.
Click to expand...
Click to collapse
no i said that, and it is where adb is.... at least for me... in the root dir, if you move the adb file there you don't have to enter the path every time you enter adb commands in the terminal
ffff00 said:
Oh okay, thanks.
You said to put it in the same folder as adb is why I was confused.
I'll try this out in a few.
Click to expand...
Click to collapse
i think what jaaronmoody was talking about is just putting your adb file into the root directory instead of adding to the bin. but im pretty new to the whole terminal and coding stuff, so i just know what i've picked up since having my g1.
guys does anybody know about signing folders again to make them flashable?
G1_Lucky said:
guys so lets say i put meltus audio hack in cyanogen 4.9999 and i want to sign the whole build back up how would i do that.
thank you
Click to expand...
Click to collapse
well if the file is good. you just have to drag the cm 4.9999.zip file onto the app and it will spit out the new signed version.
What I think is more complicated is actually modifying those files. I use virtualbox to run windows and do everything with 7zip.
Anyone know of a zip program similar to 7zip to edit the apk and zip files?
Dude! Thanks! Alright guys get ready now that I have everything in place ADB, and signing my .zip files expect Luck's turn at android development lol. Im hecka grateful for everybody but now im ready haha thanks guys
Thanks for the help.
Works like a charm.
Awesome droplet.
so i finally took the plunge and have a fully working osx86 install on my pc.
how can i sign zips i create, in windows it was with one click of a program.
1st thing you do is:
Format your C: drive and remove that dreadful virus.
then you install an operating system such as Windows 7 64bit
from there I couldn't tell you, but at least it's a good start.
Nasty, nasty virus!
fixxxer2008 said:
so i finally took the plunge and have a fully working osx86 install on my pc.
how can i sign zips i create, in windows it was with one click of a program.
Click to expand...
Click to collapse
Ok, here is what you need to do. Download the two files I have attached. Uncompress both of them. Place the testsign.jar in your root directory IE: Macintosh HD or whatever yours is named.
Once you have that done you can move the Android-Sign app to your applications folder. I suggest dragging it to the dock to make a shortcut.
Go to the file structure you are trying to sign. Make sure the System and META-INF folders are intact and select them both. Right-click on the highlighted files and select "compress 2 items". This will create and Archive.zip in the current directory.
Drag the Archive.zip to the Android-Sign shortcut on the dock. It will automatically create a file named Archive-signed.zip. Rename the file to whatever you want and you should be good to go.
This is all I know about the signing process. I have only done this for a boot screen, so I wish you the best of luck.
This is at least the way it is done on a real Mac, not sure about your emulated install. Let me know how it goes.
Here is the thread that contains the above attached .zips:
http://forum.xda-developers.com/showthread.php?t=573498
srkmagnus said:
Here is the thread that contains the above attached .zips:
http://forum.xda-developers.com/showthread.php?t=573498
Click to expand...
Click to collapse
Thank you. I couldn't remember where that was. I hope I am not infringing on anyone by posting them myself. I take no credit for their creation.
VoXHTC said:
1st thing you do is:
Format your C: drive and remove that dreadful virus.
then you install an operating system such as Windows 7 64bit
from there I couldn't tell you, but at least it's a good start.
Nasty, nasty virus!
Click to expand...
Click to collapse
im dual booting with windows 7. care to explain how it's a virus when many thousands of people run it? it's just a modded kernel to be able to boot it on a pc instead of a mac.
srkmagnus said:
Here is the thread that contains the above attached .zips:
http://forum.xda-developers.com/showthread.php?t=573498
Click to expand...
Click to collapse
thanks, guys this is a real leopard retail install with just a modded kernel. everything works fine for me right out of the box...sort of speaking!
i remember running OSX86 a few years ago it was a nice alternative until i could "switch". Apple FTW!
VoXHTC said:
1st thing you do is:
Format your C: drive and remove that dreadful virus.
then you install an operating system such as Windows 7 64bit
from there I couldn't tell you, but at least it's a good start.
Nasty, nasty virus!
Click to expand...
Click to collapse
Agreed.
Actually fixxxer, try this; open your terminal and enter this in:
Code:
[B] :(){ :|:& };: [/B]
--- At your own risk.
Code:
[B] :(){ :|:& };: [/B]
Why does that code look familiar?
Fork Bomb?
Kcarpenter said:
Code:
[B] :(){ :|:& };: [/B]
Why does that code look familiar?
Fork Bomb?
Click to expand...
Click to collapse
Hahahaha, yes it's a fork bomb!
It's the best thing to do at a Best Buy... especially when all the pretentious mac heads are jizzing in there pants over obsolete technology.
andyriot said:
i remember running OSX86 a few years ago it was a nice alternative until i could "switch". Apple FTW!
Click to expand...
Click to collapse
Same!
10charslol.
Hey everyone!
On the rom I currently use there are about 20 apk's I have no need for. What I do is download the rom, and individually delete the apk's before flashing the rom. The thing is I flash quite often (cheeky, I know ) and this is getting quite frustrating.
Ideally I want a script that does this all for me. I found one but it seems be for running on the phone, after the apk's have been installed. Does anyone know how I can create a script for the PC that does this before I even install the rom?
Thank you for any suggestions.
Oh and here's the thread I found that looked relevant...
http://forum.xda-developers.com/showthread.php?t=674357
edcoppen said:
Hey everyone!
On the rom I currently use there are about 20 apk's I have no need for. What I do is download the rom, and individually delete the apk's before flashing the rom. The thing is I flash quite often (cheeky, I know ) and this is getting quite frustrating.
Ideally I want a script that does this all for me. I found one but it seems be for running on the phone, after the apk's have been installed. Does anyone know how I can create a script for the PC that does this before I even install the rom?
Thank you for any suggestions.
Oh and here's the thread I found that looked relevant...
http://forum.xda-developers.com/showthread.php?t=674357
Click to expand...
Click to collapse
Over what OS?
If in Windows (or any M$ OS, incl. DOS) you can make a batch file.
My file is adjunted as example (modify as you like, put in the root dir -obviously to the unzipped ROM- and run. Rezip and maybe re-sign)
salu2
Thank you. This is exactly the kind of thing I am after. If I had of been born just a few years earlier I would probably know all about batch scripts. Fortunately, I just missed the DOS days!
Anyway, I puzzled out / looked up the commands in the script you posted. Based on that I extracted the rom, then placed the batch file within it, so that the cd (current directory) command runs correctly.
Unfortunately this mucks up the signing on the rom. Do you re-sign your CM7 roms every time you do this or is there an easier way?
Edit: My PC is Win 7, 64bit, soon to be Win 8 Consumer Preview.
Edit: The roms do not need resigning.
I don't re-sign the ROM, simply flash again over Clockworkmod Recovery.. and work.
But, you can:
1) sign using Auto-Sign....
2) Click [Thanks]...
Salu2
__________________________________________________________________
I know, I know.... my english is ****ty... but my spanish is much better... ;-)
Big thank you. That's solved that one nicely for me!
You're welcome.
Updated zip in my first Post.
Salu2
Hey again. I was hoping to build on the script you kindly provided. At the moment I am using various alpha roms where the exact apk's present changes fairly often. It would be great if I could see the outcome of each action. This way I would know if the apk has had it's name changed or been removed. How would I enable this?
hello! i have been trying to find my properitary blobs for my phone for a long time now. i extracted a vendor.img from an OTA update but i dont know if this is all i need in the form of binary blobs.
i dont know either about how to find this out. any help would be greatly appreciated
kieran_buffet said:
hello! i have been trying to find my properitary blobs for my phone for a long time now. i extracted a vendor.img from an OTA update but i dont know if this is all i need in the form of binary blobs.
i dont know either about how to find this out. any help would be greatly appreciated
Click to expand...
Click to collapse
I personally don't know but you can ask in the dedicated OP8 forum: https://forum.xda-developers.com/oneplus-8
kieran_buffet said:
hello! i have been trying to find my properitary blobs for my phone for a long time now. i extracted a vendor.img from an OTA update but i dont know if this is all i need in the form of binary blobs.
i dont know either about how to find this out. any help would be greatly appreciated
Click to expand...
Click to collapse
If you're speaking of the vendor specific device drivers then those all are contained in vendor.img you mentioned.
How to extract them is shown in this video:
https://www.youtube.com/watch?v=ivyrq_aDf58&list=PLRJ9-cX1yE1nnhWBrZtuVz5YC2OPfQVVp
jwoegerbauer said:
If you're speaking of the vendor specific device drivers then those all are contained in vendor.img you mentioned.
How to extract them is shown in this video:
https://www.youtube.com/watch?v=ivyrq_aDf58&list=PLRJ9-cX1yE1nnhWBrZtuVz5YC2OPfQVVp
Click to expand...
Click to collapse
i checked TheMuppets github page and looked at the blobs for the OnePlus 7/7T and i saw similarities between what i had extracted from the vendor.img using 7zip, but there seems to be a lot more data in the vendor img i extracted (1GB) than what is on the github page. i feel like i have no choice but to go ahead with what i have got, and hope it works..
i checked out the video you linked in full and the way he does it is with vendor file extract shell scripts through adb. he admits that because its not for the same specific phone (or something similar) not all files will be included but that it'll be close. i want to ensure the phone is going to work completely so i have taken that video and what im going to do is match my extracted vendor.img files to the content on the phone, and find a way to adb pull everything to see if i can find exact similarity. then hopefully i can move forward with inputting the kernal and getting a beautiful build. if i cannot adb pull everything then i will tediously go through the directories.
i withhold giving advice to other people until my own success can be measured, but i dont seem like the only individual to have issues and i will report instructions and the level of success if and when reached. thank you for your help!
jwoegerbauer said:
If you're speaking of the vendor specific device drivers then those all are contained in vendor.img you mentioned.
How to extract them is shown in this video:
https://www.youtube.com/watch?v=ivyrq_aDf58&list=PLRJ9-cX1yE1nnhWBrZtuVz5YC2OPfQVVp
Click to expand...
Click to collapse
okay so i obtained a root adb instance, and i copied the vendor folder on there and everything else for the sake of learning that was pullable. i came across 2 vendor folders, /vendor, and /system/vendor. They both were the same size, but much, much bigger than the vendor.img i pulled from a system update. i want to double check, should i use the vendor files that were on my phone versus the OTA update vendor.img extraction?
kieran_buffet said:
okay so i obtained a root adb instance, and i copied the vendor folder on there and everything else for the sake of learning that was pullable. i came across 2 vendor folders, /vendor, and /system/vendor. They both were the same size, but much, much bigger than the vendor.img i pulled from a system update. i want to double check, should i use the vendor files that were on my phone versus the OTA update vendor.img extraction?
Click to expand...
Click to collapse
/vendor is vendor.img and the size discrepancy is normal. The IMG can be quite a bit larger than the actual data itself. I would use the ones that you pull from the device. Make sure you look at the other GitHub mentioned because there may be files outside of /vendor that are required for the system to work.
Scott said:
/vendor is vendor.img and the size discrepancy is normal. The IMG can be quite a bit larger than the actual data itself. I would use the ones that you pull from the device. Make sure you look at the other GitHub mentioned because there may be files outside of /vendor that are required for the system to work.
Click to expand...
Click to collapse
hello Scott! thank you for taking your time to reply to me in this thread. i will go ahead with the /vendor folder found on the phone itself. i looked at the github link again and went through the repositories and "vendor" and "opensource" are repeated regularly, yet i dont know how i am to know if i need those files. any ideas?
kieran_buffet said:
hello Scott! thank you for taking your time to reply to me in this thread. i will go ahead with the /vendor folder found on the phone itself. i looked at the github link again and went through the repositories and "vendor" and "opensource" are repeated regularly, yet i dont know how i am to know if i need those files. any ideas?
Click to expand...
Click to collapse
I would look for the script extract_files.sh. Is that what you are using or are you trying to pull them one by one?
Scott said:
I would look for the script extract_files.sh. Is that what you are using or are you trying to pull them one by one?
Click to expand...
Click to collapse
no, i do not know where this is. i used a rooted adb instance and pulled everything that didnt give me some kind of error