http://forum.xda-developers.com/showpost.php?p=20107570&postcount=17
I posted in my thread my problem. Does anyone know what I have to do exactly at the last step I am currently at?
I downloaded the 5 driver files for our crespo. Then I ran the scripts. Now I got a folder 'vendor' with some files in it. And I wonder where I should put it.
Related
Hi,
To link a gl app I need the respective .lib's for
libEGL.dll
libGLES_CM.dll
libGLESv1_CM.dll
libGLESv2.dll
I know how to turn these into libs once I've extracted the files, but here lies the problem.
when I try to copy them from the windows directory I get the message
"access is denied"
Anyone know how to grab these files from the device?
Jim
they are modules. so not easy to get out of a live rom..
it is easier to extract them from a dumped rom
Hi,
Thanks for your reply. I dumped the ROM, extracted the .dll's and turned them into libs. I wanted to post them here so other dev's can use them.
headers are available from khronos group.
I've dumped the openVG as this is part of the EGL package.
Jim
dumping the rom
Hi dattrax,
can you describe how you dumped the rom and extracted the dll's.
I need to do the same thing.
Thanks
I am not sure why my proprietary files are not being included in my system.img build for CM9. I've had them extracted to the right location but they aren't being added resulting in a unbootable device. Successful builds should have around 350mb+ system.img but mine is only 160mb.
Any ideas?
I know this is an old thread, but shameless bump here.
Trying to build CM9 for Toroplus. Proprietary files are pulled off the device and into the right vendor folder, but never being copied into the final build.
Really annoying me. Can't seem to solve it. Everything else builds and runs fine, but I can't run the full ROM without getting this working..
Hello! Okay the title pretty much says it all, I have followed this guide to port the newly released MIUI 2.7.20 from the hercules to our skyrockets and to make the file switches i had to "extract" both archives. Now I have everything changed that needs to be but no way to re zip it to flash? I tried 7zip and Winrar and they just made a zip file that housed the original file inside (cant flash that). Any help would be great, Thanks
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.
Hello,
some weeks ago I got to an old Mediatek 6572 device for free. Mobistel Cynus E1. My first smartphone
For some reasons I want to make an another ROM on it. (I want a special app, that is only for Android 4.4 and higher, but that should not be topic here. I don't think, that I find a solution for this.)
After some learning, tweaking, backup, rooting (system and shell) and porting to Custom Recovery CTR I found a Custom-ROM (Mediamod 5) I wanted to test, which was tagged with "MTK6572" and "Jellybean 4.4.2", so that I come to the closest possible compatible ROM. I only had to make the changes in the folders between Stock-ROM and Port-Rom like it is written in the descriptions out there and also in this community, since there is no already special explicit Cynus E1 ROM out there. I made 4 versions (changed files in "system" folder only, changed in boot.img and updater-script only, changed both and changed none).
Put all 4 on the ext. SD-Card. The first installation was started from ROM Manager app, which rebooted with some parameters (Wipe cache) into the recovery mode then and started the installation. But nothing started. Installation aborted.
BUT: The original .zip worked. In the sense, that the installation started and was completed. Not that I could boot after this in the system. The Screen was illuminated, but dark.
Hmm, what was wrong with my .zip ROMs?
I unzipped the original ROM, changed only one attribute in of the updater-script in Metafile/google. Zipped all again - Installation aborted
Unzipped original .zip, changed nothing, zipped all again. - Nothing, Installation aborted.
Tried 7-Zip as alternative to Winrar for Zipping. - Nothing. Installation aborted
Tried 2 different zip-signer (sign-em.bat and flashable zip signer) found in this forum. Nothing changed. Installation aborted.
I can't work out, what information/data get lost and at which process when I decompress the archive and compress the folders againt without any other action?
Can you help me?
Bump.
Solved
Bump and Solved.
Very shameful that I had not saw this: I didnt select the files/folders "system", Meta-inf" "boot.img" ... for the archive, but the ROM-folder, in which these files were. Clearly that so the installation routine didn't find the files.
frishar said:
Bump and Solved.
Very shameful that I had not saw this: I didnt select the files/folders "system", Meta-inf" "boot.img" ... for the archive, but the ROM-folder, in which these files were. Clearly that so the installation routine didn't find the files.
Click to expand...
Click to collapse
In your original post, you stated that you modified the updater-script, the updater-script is in the META-inf file, so I don't see how you missed that.
Also, in your original post, you vaguely described the things you did with statements like moved "some files" from original ROM to port ROM or to "some partitions"
You didn't state exactly what you modified.
I know you tried to describe your situation but how it actually came out is you basically only stated that you tried porting a ROM by "doing some stuff like in the guides everywhere but it didn't work". That isn't enough information for anyone to even START understanding what your issue might be.
Sent from my LGL84VL using Tapatalk
Droidriven said:
In your original post, you stated that you modified the updater-script, the updater-script is in the META-inf file, so I don't see how you missed that.
Also, in your original post, you vaguely described the things you did with statements like moved "some files" from original ROM to port ROM or to "some partitions"
You didn't state exactly what you modified.
I know you tried to describe your situation but how it actually came out is you basically only stated that you tried porting a ROM by "doing some stuff like in the guides everywhere but it didn't work". That isn't enough information for anyone to even START understanding what your issue might be.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Like I said. I also failed for nonmodified version, when I only unpacked and repacked the rom.zip. My mistake was, that for Repacking I selected the folder, which was not there in the original .zip, but which was created by winrar at unpacking (with the files and folders in it). So the installation routine of CWM/CTR couldn't detect the files.