On a prior ROM, I was able to simply replace the .ogg files in audio/ui with custom ones, but for some reason none of my rooted file managers can copy anything to that location.
How would I make a flashable zip then?
Mariner_1712 said:
On a prior ROM, I was able to simply replace the .ogg files in audio/ui with custom ones, but for some reason none of my rooted file managers can copy anything to that location.
How would I make a flashable zip then?
Click to expand...
Click to collapse
If you give me the path of the .ogg you want to replace, as well as the new .ogg file you want to use, I'll make it for you.
Related
Can I modify an existing one by simply dropping in updated bootscreen files, rosie.apk, etc.. and signing the existing rom zip?
Any good guides on how to do one if not, and/or how to use Flipz kitchen tool to create a rom?
Ceger
I am pretty sure if you sign the file and you modify it after that you will have to resign it. At least thats how it goes for other things that are similar that I deal with.
Kcarpenter said:
I am pretty sure if you sign the file and you modify it after that you will have to resign it. At least thats how it goes for other things that are similar that I deal with.
Click to expand...
Click to collapse
I understand that, just wondering if I can add new files and they will move or does some master script need to be updated to know to move the files. In other words, is it done by directory or by file?
For example, if I add some apps to /data/app in the zip will they be there on the phone when I install the ROM zip, etc.. More specifically, I have added an alternate boot sequence. The rom does not have a boot1.gif. If I add the new sequence with XML, will the boot1.gif be installed as well or do I need to update something that directs the install of the ROM to move that file or is it automatic as the folder is moved over?
Ceger
Ceger said:
I understand that, just wondering if I can add new files and they will move or does some master script need to be updated to know to move the files. In other words, is it done by directory or by file?
For example, if I add some apps to /data/app in the zip will they be there on the phone when I install the ROM zip, etc.. More specifically, I have added an alternate boot sequence. The rom does not have a boot1.gif. If I add the new sequence with XML, will the boot1.gif be installed as well or do I need to update something that directs the install of the ROM to move that file or is it automatic as the folder is moved over?
Ceger
Click to expand...
Click to collapse
I have found that the easiest thing to do is just put the files that you want to use to replace the old ones into a signed zip and then flash just those files I have tried altering a rom file with no success
wtphoto said:
I have found that the easiest thing to do is just put the files that you want to use to replace the old ones into a signed zip and then flash just those files I have tried altering a rom file with no success
Click to expand...
Click to collapse
Oh well, was trying to have a one step zip. I guess I can make at least have a 2 step process which is better than 4-5.
Thanks,
Ceger
Yes you can modify just about anything in the rom and flash your zip as long as it is signed and the update script is correct. I always make all my changes to a rom before flashing it so i do not have to flash several different things etc.
The update script is located in RomName\META-INF\com\google\android\
Lets look at a very simple update script to show you what i mean.
In this update script it is to write something to /system
example:
show_progress 0.1 0
copy_dir PACKAGE:system SYSTEM:
show_progress 0.1 10
We see here that whatever is in the system folder within the signed zip will be written to the phone
in this case i am writing /system/app/mobiledefense.apk
That will be the only file written to the phone and will be written to /system/app
The update script is not specific to every file so you can have 1 thing in the system folder or 100 and it will write everything in there.
One thing that many people mess up on is not using a update-script file when they sign a .zip file. The recovery has to know what to flash or it will not flash anything.
So the answer is yes you can change many things and then flash the signed update.zip file.
Not everything can be done this way but most things will work.
But for example changing the boot sceen can be done even if the file names are different as long as the folder structure stays the same and the .XML file is the correct one for the boot screen. I opened the .zip of a rom deleted everything out of the boot screen folder and dropped in all the files from the nexus one hero hybrid boot screen re signed the zip and everything flashed perfect. I changed many other things as well in the .zip like rosie.apk, sound files, lockscreen files, busybox files, added apps to /system/app and just resigned the zip and everything flashed the way i wanted it to and works perfect.
The way to correctly zip a file is to extract the zip modify what you want then select everything inside the zip right after you open the folder and the highlight everything select add to archive and then zip it up now sign that .zip
so say you extract the ROM and it is named Rom123 now you will have a folder named Rom123 open that folder and select everything file or folder in there and then hit add to archive that will make another zip right there called Rom123.zip pull that zip out to the desktop and sign that zip file and thats it.
I Know that is confusing as it is late as hell and i am tired but wanted to answer this real quick.
zippy-man said:
Yes you can modify just about anything in the rom and flash your zip as long as it is signed and the update script is correct. I always make all my changes to a rom before flashing it so i do not have to flash several different things etc.
The update script is located in RomName\META-INF\com\google\android\
Lets look at a very simple update script to show you what i mean.
In this update script it is to write something to /system
example:
show_progress 0.1 0
copy_dir PACKAGE:system SYSTEM:
show_progress 0.1 10
We see here that whatever is in the system folder within the signed zip will be written to the phone
in this case i am writing /system/app/mobiledefense.apk
That will be the only file written to the phone and will be written to /system/app
The update script is not specific to every file so you can have 1 thing in the system folder or 100 and it will write everything in there.
One thing that many people mess up on is not using a update-script file when they sign a .zip file. The recovery has to know what to flash or it will not flash anything.
So the answer is yes you can change many things and then flash the signed update.zip file.
Not everything can be done this way but most things will work.
But for example changing the boot sceen can be done even if the file names are different as long as the folder structure stays the same and the .XML file is the correct one for the boot screen. I opened the .zip of a rom deleted everything out of the boot screen folder and dropped in all the files from the nexus one hero hybrid boot screen re signed the zip and everything flashed perfect. I changed many other things as well in the .zip like rosie.apk, sound files, lockscreen files, busybox files, added apps to /system/app and just resigned the zip and everything flashed the way i wanted it to and works perfect.
The way to correctly zip a file is to extract the zip modify what you want then select everything inside the zip right after you open the folder and the highlight everything select add to archive and then zip it up now sign that .zip
so say you extract the ROM and it is named Rom123 now you will have a folder named Rom123 open that folder and select everything file or folder in there and then hit add to archive that will make another zip right there called Rom123.zip pull that zip out to the desktop and sign that zip file and thats it.
I Know that is confusing as it is late as hell and i am tired but wanted to answer this real quick.
Click to expand...
Click to collapse
Perfect, just what I was looking for.
Thank you, just made my day!
Ceger
i am relatively new to roms and themes. when i get into CWR and go to flash a zip file is is bad if it is .zip.zip or does it matter?
What are you trying to flash?
dhjohnson said:
i am relatively new to roms and themes. when i get into CWR and go to flash a zip file is is bad if it is .zip.zip or does it matter?
Click to expand...
Click to collapse
Yes it is bad and does matter. Just xxx.zip for it to work.
It sounds to me like you renamed it whatever.zip, in which case it will look like .zip.zip, but it doesn't matter. The first .zip will just be part of the file name, it will not affect what type of file it is. I have done this with an image file when flashing a new splash screen, so i had to adjust the adb command from custom.img to custom.img.img...didn't make a difference.
I am trying to make a custom boot w/sound but last time I tried getting sound to work I bricked my phone. Any help would be appreciated. I also am considering trying to figure out how to do a SOA theme for SCOM.
BTW somebody created the same boot animation on another phone but with no sound. So I have that already.
Maybe this will help you or atleast point you in the right direction.
http://forum.xda-developers.com/showthread.php?p=14136008
Sent from my Maybach s 4g
JonnyStreetz said:
Maybe this will help you or atleast point you in the right direction.
http://forum.xda-developers.com/showthread.php?p=14136008
Sent from my Maybach s 4g
Click to expand...
Click to collapse
I found somebody who created the same animation that I wanted to do so I have reposted the bootanimation.zip and have converted the theme to wav format (don't know if I needed to do that or not) and replaced the PowerOn.wav from the ect folder. The rom I am using already had boot sound. So I was able to just replace the files. What I want to know is the bootsnd.sh file listed in the tutorial the same file needed for our phone? Also it listed a different directory for pushing the sound file. Is this something that is different per phone or ROM or just a preference?
ShadyAce80 said:
I found somebody who created the same animation that I wanted to do so I have reposted the bootanimation.zip and have converted the theme to wav format (don't know if I needed to do that or not) and replaced the PowerOn.wav from the ect folder. The rom I am using already had boot sound. So I was able to just replace the files. What I want to know is the bootsnd.sh file listed in the tutorial the same file needed for our phone? Also it listed a different directory for pushing the sound file. Is this something that is different per phone or ROM or just a preference?
Click to expand...
Click to collapse
I have a feeling I know what bootsnd.sh file your talking about. No you dont need that for the current roms for the phone. That script is for phones running roms like CM7 that dont have bootsound turned on.
Put the poweron.wav in the same directory as the factory one is now. In converting the file to wav did you just rename it or actually convert it using a program on your pc? Just renaming it will not always work.
eollie said:
I have a feeling I know what bootsnd.sh file your talking about. No you dont need that for the current roms for the phone. That script is for phones running roms like CM7 that dont have bootsound turned on.
Put the poweron.wav in the same directory as the factory one is now. In converting the file to wav did you just rename it or actually convert it using a program on your pc? Just renaming it will not always work.
Click to expand...
Click to collapse
I have a conversion program on my system. I have the animation and the audio file posted in themes right now. Planning on tweaking it a bit and making it my own creation once I have more of an idea of where I want to take it. And will be attempting to make it flashable in a week or two I hope.
Hey, I'd like to know how to change the bootanimation in Kyrillo's ROM as ive already tried BootAni and some other apps and even tried manually changing the Bootanimation in "data" and "system/media"...didnt work.... it'd be great if i could get some help and if possible in a step by step manner...
1. Find a suitable replacement in bootanimation.zip format.
2.check to make sure this isnt an update zip. (do this by exploring the file, it should consist of only files names "part0" and "desc.txt" and maybe "part1")
3.If it is a update zip, unzip it and extract the bootanimationzip inside it.
4. place this onto sd card
5. use root explorer or similar to move the file to system/media, making sure it is named "bootanimation.zip" it should say something like "file exists, replace it?". say yes.
6. now long press the new file and open up permissions in the menu. set these as rw-r--r--
7. reboot phone and enjoy!
bear in mind that kyrillos 10.4 is based on open fimg, so you may have white patched in the boot animation, just like the one preloaded onto it.
In 10.4, Kyrillos has fixed the white patches in SOME bootanimation, like the stock one.
ak700 said:
In 10.4, Kyrillos has fixed the white patches in SOME bootanimation, like the stock one.
Click to expand...
Click to collapse
I did ..
On an extra note:
If you want to avoid having white flashes in your bootanimations on any rom with openFIMG you should look for one with less than 75 frames in the part1 folder. Any frames past that turn white...
Tried didnt work!!....
Ava.tar said:
1. Find a suitable replacement in bootanimation.zip format.
2.check to make sure this isnt an update zip. (do this by exploring the file, it should consist of only files names "part0" and "desc.txt" and maybe "part1")
3.If it is a update zip, unzip it and extract the bootanimationzip inside it.
4. place this onto sd card
5. use root explorer or similar to move the file to system/media, making sure it is named "bootanimation.zip" it should say something like "file exists, replace it?". say yes.
6. now long press the new file and open up permissions in the menu. set these as rw-r--r--
7. reboot phone and enjoy!
bear in mind that kyrillos 10.4 is based on open fimg, so you may have white patched in the boot animation, just like the one preloaded onto it.
Click to expand...
Click to collapse
i tried it .... didnt work .... idk why.... just to change the bootanimation i bymistake flashed a motorola Xoom bootanimation please help...plzplzplzplz.... im stuck here with nothing but "A)" out of the whole bootanimation plz help im tired of trying to change my bootanimation!!!!!
Please parson me if I have missed this in my search.
I am looking for a way to create a flashable zip script that can be run after a new ROM is installed where it can replace all the stock ROM sounds in the notifications, ringtones, ui and notifications directory.
After the new ROM is installed you can then stay in recovery and use the "sound update" flashable zip to delete the existing sounds and replace them with the ones in the script.
Now I know I could just replace the files from the ROM ZIP but always having a "sound update" flashable zip on the SD card would be a little faster especially if I am not at a computer to do the file replacement in the ROM itself.
I hope I am making sense.
Thanks in advance.
rkrmpg said:
Please parson me if I have missed this in my search.
I am looking for a way to create a flashable zip script that can be run after a new ROM is installed where it can replace all the stock ROM sounds in the notifications, ringtones, ui and notifications directory.
After the new ROM is installed you can then stay in recovery and use the "sound update" flashable zip to delete the existing sounds and replace them with the ones in the script.
Now I know I could just replace the files from the ROM ZIP but always having a "sound update" flashable zip on the SD card would be a little faster especially if I am not at a computer to do the file replacement in the ROM itself.
I hope I am making sense.
Thanks in advance.
Click to expand...
Click to collapse
Please take it upon yourself to do some research on how to make flashable zips. I don't say this to be mean, but learning how to do things makes you less reliable on others...
You need to place all of your sounds in their respective directories inside /system/media, use the proper update-binaries (which can be pulled from any rom), and write an updater-script.
(hint: "delete_recursive" and "package_extract_dir" will be used helpful)