I have tried to read the file, but I am having too much trouble. I'm not a real programmer and some of this stuff if too cryptic for me to read my way through.
What I am trying to do is take some partitions that aren't being used and, well, use them. Our toolkit has theese files in it and I think this is where the installer script is made from. I have our recovery.fstab eddited (I think I did it right). But I'm sure that this isn't where the installer script gets it's information.
I'm just not able to work my way through this one. And of corse I may be on the wrong track for this whole thing.
Anyway. thank you for looking.
I have partially figured it out. On our build there are a few files used to make the edify script. One is the edify generator, and the others are dependent on what is going on. We have one for making an update file (something we don't use) and the other is for making the flashable ROM that we do use.
Anyway, post back if you want to know more.
Related
I have been creating themes for all types of ROMs for a while now and for some reason about half of Hero ROMs I am not able to edit. When I download the .zip file and make changes when I go to close it I get memory errors and things of that nature that happen on multiple computers so I know it isnt my hardware.
So I decided to extract the Hero ROMs side by side, the one I can edit and the one I cant to see the difference. Well the one I cant edit always crashes when extracting, so I went folder by folder to find the issue. Well the problem is in the system > lib folder and there are 2 files with the same name but different capitalizations, liba2dp.so and libA2DP.so and it causes the error.
It appears I can remove the capitalized version of the file (aka the smaller one) and then everything goes back to normal and I can edit the ROM like usual. Can anyone confirm any of this?
this is microgays fault - ntfs doesn't support this - switch to linux.
maxisma said:
this is microgays fault - ntfs doesn't support this - switch to linux.
Click to expand...
Click to collapse
I have a virtual Mint installation I use for much of my theming which is why it was never really a problem, but I know other people have run into the issue and never bothered to ask and I just wanted to understand it instead of avoiding it.
So removing the file will work or am I breaking something else in exchange? I noticed your Hero roms dont have this issue and its your ROMs that helped me figure this out.
I would love to help the community by using your kernel for the newer radios to port any roms for the older radio... is there any help you can give me? should i use your boot.img from the test-donut.img/test-eclair.img?
Click to expand...
Click to collapse
first, a thing we must know for porting job is what boot.img included.
here: http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
the ramdisk do some initializing jobs, so if we port a ROM, we should ensure that the content in ramdisk and files which are included in ramdisk (like init.rc), have necessary things the ROM needed.
for the first step, we can just extract the boot.img from the ROM, and extract the ramdisk from the boot.img which extracted just now, then repack it with my kernel (you can extract the kernel from my boot.img with same tools).
(to execute the perl script in link above, you need linux or just cygwin. )
but if we are sure that the ROM we want to port have nothing special with ramdisk, just like common ROMs, we can use my boot.img files directly. for eclair ROM, I suggest you extract the boot.img from my ROM, and don't use the first boot.img (test-NOCDB.img) I had posted.
after this, make our update.zip (use other's ROM as an example, especially the update-script in META-INF directory). sign our zip with testkey and apply it, then we can make our phone booting into desktop.
(you can find information about sign and download tools here: http://forum.xda-developers.com/showthread.php?t=471586, though the thread is not talk about how to sign things)
the main troubles we may meet probably are symlinks and setperm* in the update-script. if there is already a file/link has a name we want to symlink to, or if there isn't a file we want to symlink from or setperm, we will fail. so check the files carefully.
the next step is make everything work properly. we can use file from a ROM which made for new radio (and work well of course) to replace the one in the ROM we are porting. we can find these files in my 2.x ROM for eclair, or other's 1.6 ROM for donut (and for new radio, since the maker of them tested them already).
the most important files are (to my knowledge):
system/lib/libhtc_acoustic.so
system/lib/libhtc_ril.so (if something wrong with mobile network)
system/lib/libcamera.so
system/lib/libcameraservice.so
system/lib/liboemcamera.so (for 2.x) or system/lib/libqcamera.so (for 1.6)
system/lib/libgps.so
system/bin/akmd
(are there something I missed?)
(if we want to use NCommander's work on CameraHardwareInterface with a 2.x ROM, we should use my kernel for DONUT instead. I didn't try it, and I don't recommend it.)
these files are some thing work with hardware partially, so different radio may need different files. but if something just work fine, don't hurry to replace the file for it.
and now...., I don't have more thing to talk about, since we have most things work well. but for further tweaks, there are lots of things to do.
everyone can post your question here. if I know the answer I will post it. if I don't or I am not online, I think others will response you. and if there are things I missed or made some mistake, plz point it out
I will update this post when we collection more info or correct something. I find that I don't organized everything in order . I will update it later.
Thanks for the post... what's the difference between your eclair/donut kernel? (This is based on your original post about your kernel... is there an updated kernel somewhere i should know about?)
Edit
Nevermind i figured it out by reading your post more. carefully thanks for the detailed instructions
Thank you very much for this sanpei. This is the type of posts that really should be on this forum
Appreciated so much. waiting for your next updates.
Phil_McRevis said:
Nevermind i figured it out by reading your post more. carefully thanks for the detailed instructions
Click to expand...
Click to collapse
sorry for my poor ability of expression
asero said:
This is the type of posts that really should be on this forum
Click to expand...
Click to collapse
I expect more people can share their knowledge, and we can make a wiki for all
Hello!
I have to edit some lines of init.rc of your kernel. I've thus extracted the ramdisk, edited the file, repacked and tried booting with fastboot boot kernel-img ramdisk-img, but the phone hangs on the operator logo. I've tried even just extracting kernel+ramdisk and boot them - same result (the boot.img works well).
how can I fix it? Thanks
Wrong post
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?
Im trying to learn how to port as along with creating a rom but anyways.im having trouble with the updater-scripts. I dont know how to re write them so that the Base's script is like the Ported script, without messing up the symlinks. Ive tried writing them about 7 times. Then when I come to flash the rom and doesn't work and im pretty sure the updater-script is my problem.
Ty113096 said:
Im trying to learn how to port as along with creating a rom but anyways.im having trouble with the updater-scripts. I dont know how to re write them so that the Base's script is like the Ported script, without messing up the symlinks. Ive tried writing them about 7 times. Then when I come to flash the rom and doesn't work and im pretty sure the updater-script is my problem.
Click to expand...
Click to collapse
Most of what I learned from updater-scripts (edify) comes from googling and downloading many of the firmware from the i997 and other devices for comparison.
If you are creating new or editing another, make sure you use a linux text editor like Note++. Notepad, Word or other text editor will give you errors. Note++ is also free.
Syntax is also very important. Edify is not very forgiving.
gl
Ty113096 said:
Im trying to learn how to port as along with creating a rom but anyways.im having trouble with the updater-scripts. I dont know how to re write them so that the Base's script is like the Ported script, without messing up the symlinks. Ive tried writing them about 7 times. Then when I come to flash the rom and doesn't work and im pretty sure the updater-script is my problem.
Click to expand...
Click to collapse
Along with qkster's advice, id like to also suggest actually looking at other ROM's updater scripts.. Or any flashable zip package as a matter of fact.. Just look through it and see if you can put together what does what.. It doesnt hurt to use something as a base if you are using it to further your own knowledge and actually trying to understand what your doing.. If you have any questions send me a PM and ill help the best i can.
I saw a few people post that they built ROMs for this device using dsixda's kitchen. Just wanted to know if you had to create a 'hammerhead' file for the storage mount points since this isn't included in the supported devices (obviously because the tool isn't being updated anymore).
If you created a mount point file, can you please post the contents so I can reuse (fyi... I've installed this on a Mac, but should be able to reverse engineer one from a different OS)? I'm a bit of a noob using this kitchen and just got it configured on my mac yesterday. Just looking to mess around with it a bit for lack of a better thing to do.
I´ve also created device files for several devices, it´s not as hard as it sounds, as long as you´ve read the OP in this thread ?
http://forum.xda-developers.com/showthread.php?t=633246
You need to unpack one Stock Kernel of the device you want to add the support to the kitchen, check the contents of the RAMdisk for the required mounting points and add them yourself ?
teknomar7 said:
I saw a few people post that they built ROMs for this device using dsixda's kitchen. Just wanted to know if you had to create a 'hammerhead' file for the storage mount points since this isn't included in the supported devices (obviously because the tool isn't being updated anymore).
If you created a mount point file, can you please post the contents so I can reuse (fyi... I've installed this on a Mac, but should be able to reverse engineer one from a different OS)? I'm a bit of a noob using this kitchen and just got it configured on my mac yesterday. Just looking to mess around with it a bit for lack of a better thing to do.
Click to expand...
Click to collapse
Gorgtech said:
I´ve also created device files for several devices, it´s not as hard as it sounds, as long as you´ve read the OP in this thread ?
http://forum.xda-developers.com/showthread.php?t=633246
You need to unpack one Stock Kernel of the device you want to add the support to the kitchen, check the contents of the RAMdisk for the required mounting points and add them yourself ?
Click to expand...
Click to collapse
That's how I got to this point to begin with was by going through that thread. I just don't want to get the syntax wrong and I'm not 100% sure what all those parms mean in that template file. Plus the info in the recovery.fstab file seemed to be quite different from the ones already in that folder. I was hoping someone would be able to just give me a copy so I can check my syntax. Sort of a learning experience for me.
i will try