I read on the gingerblur thread that you can restore individual pieces of bloatware by deleting the ones you don't want to restore from the zip. I know how to do that but my question is this:
Say I want to restore ONLY the stock gallery to get rid of the 3d gallery that comes with GB. I'd delete the DATA folder since I don't need any of those apps, and then I'd also delete everything from the SYSTEM folder except for the MediaGallery.apk correct? What, then, do I do with the META-INF folder? Can it be deleted as well?
Also, when browsing the META-INF folder I noticed this:
Code:
print ""
print ""
print "+--------------------------------+"
print "| |"
print "| GingerBlur |"
print "| |"
print "+--------------------------------+"
print ""
print ""
print ""
print ""
show_progress 0.5 0
[B]delete SYSTEM:app/Mms.apk[/B]
copy_dir PACKAGE:system SYSTEM:
copy_dir PACKAGE:data DATA:
show_progress 0.5 10
Does this mean that the Mms.apk app will be deleted when I install the zip from CWM? I don't want to lose the Mms app, I just want to install the gallery.
dcarpenter85 said:
I read on the gingerblur thread that you can restore individual pieces of bloatware by deleting the ones you don't want to restore from the zip. I know how to do that but my question is this:
Say I want to restore ONLY the stock gallery to get rid of the 3d gallery that comes with GB. I'd delete the DATA folder since I don't need any of those apps, and then I'd also delete everything from the SYSTEM folder except for the MediaGallery.apk correct? What, then, do I do with the META-INF folder? Can it be deleted as well?
Also, when browsing the META-INF folder I noticed this:
Code:
print ""
print ""
print "+--------------------------------+"
print "| |"
print "| GingerBlur |"
print "| |"
print "+--------------------------------+"
print ""
print ""
print ""
print ""
show_progress 0.5 0
[B]delete SYSTEM:app/Mms.apk[/B]
copy_dir PACKAGE:system SYSTEM:
copy_dir PACKAGE:data DATA:
show_progress 0.5 10
Does this mean that the Mms.apk app will be deleted when I install the zip from CWM? I don't want to lose the Mms app, I just want to install the gallery.
Click to expand...
Click to collapse
That won't work on newest CWM, it's using an outdated script format.
This is how i fixed it for me
jeffc said:
For those like me who need corporate sync and like the blur universal inbox you can install just that portion of the moto bloatware instead of all of it.
** EDIT ** I'm adding a couple more applications now. Please, others jump in to do other applications because I'm out of time working on my Atrix for this week!
** WARNING ** I'm not an android dev and this process has only been tested on my phone. USE AT YOUR OWN RISK!
There are 3 files attached.
messaging.zip - restores original blur messagine apps, including corporate sync, txt messaging with balloon conversation mode, and the universal inbox. It does not have the messaging widget.
taskman.zip - if you liked moto's Task Manager app, this will restore it for you so you can kill tasks and uninstall like before GB.
gallery.zip - restores the moto Medial Gallery application. Note the GB version of Gallery will still exist and both will work.
Quick instructions:
* You will need CWM Recovery for this
* Follow CWM instructions exactly - especially the part about plugging into the AC adapter or it won't work!
**NOTE** this will also install the original blur txt messaging interface with the conversation balloon mode. Its all one application so no way around it that I know of.
1) copy one of the zip files (attached) to your sdcard root directory
2) run CWM according to instructions in its thread
3) after reboot into CWM select "Install zip from SDCARD"
4) select "Choose zip from internal sdcard"
5) scroll down to the zip file name (ex: messaging.zip)
6) select the file (power button) and run the update
7) go back to main menu and select "Reboot system now"
A few steps but doesn't take long. I just pulled these out of the gingerblur-bloatware.zip and figured out what file structure you have to leave in place for it to function.
Hope this will save people some time.
Click to expand...
Click to collapse
Downloads on this link for what the post talks about
http://forum.xda-developers.com/showpost.php?p=12701405&postcount=3398
Thanks for the replies folks, got the gallery installed.
Related
I have a shutdown sequence and some sounds I would like to turn in to a flashable .zip file. I checked out the CW forums, but that was more painful than informative. I have taken a look at some of the zip files I have found so far, but am not 100% sure about what I'm doing. Can anyone point me to a how-to or even in the general direction of some information to get me started?
Thanks guys!
Edit: Those interested can find all the information needed in the3dman's post and here:
http://www.londatiga.net/it/how-to-create-android-update-zip-package/
http://www.londatiga.net/general/how-to-sign-apk-zip-files/
I'd copy this guy
http://forum.xda-developers.com/showthread.php?t=795459
Thanks for the link. I had actually started there, and it's a great template if I just want to throw in my own files, but I was really looking for a how to so that I had more options for customizing, rather than being stuck with only the shutdown / startup sequence.
Sent from my SGH-T959 using XDA App
First you have to have your folder structure like this in the zip:
Main .zip
{
META-INF { com -> google -> android -> update-script } ( <- these are folders inside the META-INF except update-script this is a script file)
app (if the file you want to flash is an app it goes in this folder)
framework (if the file you want to flash is a framework file it goes in this folder)
system (if the file you want to flash is a system file (start up animations) it goes in this folder also make sure you put the correct subfolder inside this folder ie: if your file goes in system -> media make sure you put the file you wish to flash in a correctly named subfolder other wise it will flash into just the system folder and not into the correct folder within the system folder on your phone.)
}
After your folder structure is set up you must tell clockwork which folder or folders in the zip to flash. To do this open the update-script from the zip with a text editor and modify or add these lines with the correct folders.
copy_dir PACKAGE:framework SYSTEM:framework (use this for the framework folder)
copy_dir PACKAGE:app SYSTEM:app (use this for the app folder)
copy_dir PACKAGE:system SYSTEM:system (use this for the system folder)
Then sign your zip and flash.
Below is a picture of an example folder structure so show what I mean. Also I attached a zip with an example update-script in it.
the3dman said:
First you have to have your folder structure like this in the zip:
Main .zip
{
META-INF { com -> google -> android -> update-script } ( <- these are folders inside the META-INF except update-script this is a script file)
app (if the file you want to flash is an app it goes in this folder)
framework (if the file you want to flash is a framework file it goes in this folder)
system (if the file you want to flash is a system file (start up animations) it goes in this folder also make sure you put the correct subfolder inside this folder ie: if your file goes in system -> media make sure you put the file you wish to flash in a correctly named subfolder other wise it will flash into just the system folder and not into the correct folder within the system folder on your phone.)
}
After your folder structure is set up you must tell clockwork which folder or folders in the zip to flash. To do this open the update-script from the zip with a text editor and modify or add these lines with the correct folders.
copy_dir PACKAGE:framework SYSTEM:framework (use this for the framework folder)
copy_dir PACKAGE:app SYSTEM:app (use this for the app folder)
copy_dir PACKAGE:system SYSTEM:system (use this for the system folder)
Then sign your zip and flash.
Below is a picture of an example folder structure so show what I mean. Also I attached a zip with an example update-script in it.
Click to expand...
Click to collapse
Thank you very much! This was PERFECT for getting me started! This lead me to the following sites for more information on how-to's and even all the available syntax. For anyone looking to get into this (it's not difficult), check out these pages:
http://www.londatiga.net/general/how-to-sign-apk-zip-files/
http://www.londatiga.net/it/how-to-create-android-update-zip-package/
Hi All,
Here I am expressing the overall exp after upgrading my mini pro with german build no (I am from India).
Here are the things I noticed on this NEW mini pro -
1) The home is same like before. Only the lock screen is different. Look screen is nice for me
2) I found the speed is like 10-15% more than 1.6.
3) Some really good and useful widget has been given like Market, smart search, recent calls etc.
4) The setting app is different from look and feel point of view and nice also.
5) If you tap the member of recent call , you will get all the options like message, mail, call with a floating pop up- nice feature.
6) Phone book is more or less same
7) The games are like before. like ****.
8) Calculator got two screen, scroll left to get another screen.
9)live wallpaper support, but no live wallpaper given.
10)No app installer so if you cannot install anything from SD card unless by hook and crook you install a folder-explorer. You can install your first explorer like astro by sending via bluetooth. And then get everything from your SD card.
11) If you set live wallpaper then it will take ages to get the unlock screen. This can be fixed if you user other launcher - I am using AWD with some good theme.
So if you like default home + live wallpaper, you feel like to through your phone
12) Picking up the incoming call is really nice now (at least far better from previous version)
13) In call volume is more or less same I found.
14) Music player does not have album tab the same as before, sound quality is better I believe.
15) Camera has same options like before
16) Web browser got double tap for zoom in an out.
17) Now they have given places and navigation app, I don't have internet on my phone, so could not check it .
18) Album does is same before. No rotate functionality.
What is your opinion?
hi desh lit
Can u upload the german build prop thanks
Can you check if the phone calls recording works with 2.1?
I don't want to loose this feature.
Also
If I upgrade to 2.1 will it be possible to downgrade later ?
If I were you i should change to Launcher pro, it works much faster and so on but the only minus with launcher pro is that it does not have as much customizable things as adw launcher.
German build.prop would be very much appreciated
Sorry for the delay-
I have attached the build.prop.
HOW TO -
1) Open cmd from run in windows. Go to the directory where this build.prop is kept in your laptop.
2) copy or write - "adb push fbuild.prop /sdcard/build.prop" - this will copy the build.prop into your sdcard folder of your phone.
3) copy or write - "adb shell"
4) copy or write - "su" now you will get # in cmd promt
5) copy or write - "mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system" - this will give you the write permission on the system folder.
6) copy or write - "busybox cp /sdcard/build.prop /system/build.prop" - replace the old build.prop with new one.
7) copy or write - "reboot".
After reboot connect your phone to PC Companion , that will do the rest.
desh_iit said:
Sorry for the delay-
I have attached the build.prop.
HOW TO -
1) Open cmd from run in windows. Go to the directory where this build.prop is kept in your laptop.
2) copy or write - "adb push fbuild.prop /sdcard/build.prop" - this will copy the build.prop into your sdcard folder of your phone.
3) copy or write - "adb shell"
4) copy or write - "su" now you will get # in cmd promt
5) copy or write - "mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system" - this will give you the write permission on the system folder.
6) copy or write - "busybox cp /sdcard/build.prop /system/build.prop" - replace the old build.prop with new one.
7) copy or write - "reboot".
After reboot connect your phone to PC Companion , that will do the rest.
Click to expand...
Click to collapse
Thank you dude,I mixed Exploid - root for X10 mini & your method ..
I got an update. Upgrading now
But mine is E10i.I used build.prop for E10i.
1238-7173, u20i SG version comes with Application Installer. When u start it the application, it scans ur SD card for all apk files. So if you already backup all ur application to ur sd, its pretty useful.
hello everyone
I have updated to kennethpenn's 4.5.91 Gingerbread Beta 4 (must say, it is truly a phenomally put together build !)
I have also noticed that many of the mods that i had applied to 1.8.3 have not been updated for 4.5.91, so i decided to make the changes myself.
Now, I have a pretty decent knowledge of Unix-based operating systems ( I have used Red Hat Linux, Ubuntu, SUSe Linux, OpenBSD, FreeBSD, Solaris, and now OS X) however, I would like to expand my knowledge to include Android.
The first one I attempted to do myself was the Wake on Volume Keys mod.
This is a very simple change to the android.policy.jar file, as you all well know.
For this, I used Windows XP, simply for the fact that I have 7zip and PeaZip installed on it. However, I can do all of this on OS X as well. The file archiver applications I have on OS X are:
1. The Unarchiver
2. Keka
I am going to list my method of applying this edit, and i would ask that someone with solid knowledge on this subject give me their feedback and guidance.
---------------------------------------------------------
My Method of editing android.policy.jar
---------------------------------------------------------
1. Using Root Explorer, I made a copy of /system/framework on my External SD Card
2. Mounting the Phone for USB Mass Storage on Windows XP that I have running in VirtualBox on my Macbook Pro, I moved the copy of the /system/framework directory to my Desktop
3. I downloaded smali-1.2.6.jar and baksmali-1.2.6.jar from code.google.com/p/smali/
4. I placed both of these .jar files in the copy of the framework-edited directory that I created on my Desktop
5. I renamed smali-1.2.6.jar to smali.jar and baksmali-1.2.6.jar to baksmali.jar for simplicity's sake
6. I moved the android.policy.jar file to /framework-edited directory on my Desktop
7. Using 7zip (I also have PeaZip, but for this, I used 7zip, if you think I should use PeaZip, please tell me) I extracted the files from android.policy.jar to end up with classes.dex and META-INF. I then moved classes.dex to /framework-edited so it is in the same directory as smali.jar and baksmali.jar
8. In Command Prompt, I entered:
Code:
cd C:\Documents and Settings\Owner\Desktop\framework-edited
in order to be working from the proper location where my files are located
9. Now, having Command Prompt working in the proper location, I entered the following commands:
Code:
java -jar baksmali.jar -o classout/ classes.dex
to create a new directory within /framework-edited called /framework-edited/classout
10. I then opened the /classout directory, and navigated to /classout/com/android/internal/policy/impl/ and opened the file KeyguardViewMediator.smali with Notepad
11. I used [Ctrl] + [F] to locate the line:
private isWakeKeyWhenKeyguardShowing(I)Z
12. I then looked at the lines DIRECTLY below the above line, and following the Original Post on how to manually apply this modification, I removed lines:
0x18
0x19
13. Upon removing these lines, I simply did a File -> Save As -> KeyguardViewMediator.smali and saved the file to my desktop
14. I [Cut] + [Pasted] the edited KeyguardViewMediator.smali file back to /classout/com/android/internal/policy/impl/ and replaced the original KeyguardViewMediator.smali file
15. With the edited KeyguardViewMediator.smali file in place, I went back to Command Prompt and entered the following commands:
Code:
java -Xmx512M -jar smali.jar classout/ -o new-classes.dex
To create a new file called new-classes.dex
16. Changing the name of new-classes.dex to classes.dex, I took the original META-INF file, and my newly created classes.dex files, and, using 7zip, created a new android.policy.zip archive
17. I renamed my newly created android.policy.zip to android.policy.jar, and transferred it to my External SD Card
18. Using Root Explorer, I navigated to /system/framework on my phone, and renamed android.policy.jar to 1122android.policy.jar.bac and [Copy] + [Pasted] my edited android.policy.jar to /system/framework
19. I then immediately powered off my phone, and rebooted into CWM Recovery, and cleared my Dalvik Cache, then rebooted the phone normally through CWM Recovery.
At this point, to my knowledge, I had successfully edited my android.policy.jar file and had manually added the Wake on Volume Keys modification, however, once the phone was fully booted and showing my lockscreen, I unlocked the phone as normal by sliding the slider to the right. As soon as the phone unlocked, I saw pop-ups for processes that had failed and were terminated. I'm not sure what the exact message the pop-ups had, but it was the normal pop-up message you get when a process force-closes. My only option was to click "Ok" so I clicked it, only to have another force-close pop-up.
Apparently, every single process on the phone had force-closed, BUT, the phone was waking when I press a volume key while the screen was off. I had no choice but to pull the battery out.
I decided to reboot into CWM Recovery and "install .zip from SD Card", Nottach's 1% Battery Mod / No Carrier Mod Uninstall Script
I installed Nottach's uninstall script because I hoped that it had an unmodified copy of android.policy.zip in it.
After installing the uninstall script, and rebooting the phone once again, I got to the lock screen, unlocked the phone, and found everything to be in perfect working order, just as before I edited anything,
But the Wake on Volume Keys mod was still applied!
So now, my questions / requests to all of you are:
1. Explain to me what I missed or did wrong that resulted in the force-closure of every single process on the phone prior to installing Nottach's Uninstall script
and
2. Educate me on the proper process that you developers use to apply small modifications such as this one to the android.policy.jar file, or any other related file on the phone for that matter.
My plan is now to change the color of the text on my lock screen (Clock, Date, and possibly Carrier) following this [Guide]
Any and all feedback is welcomed and greatly appreciated, as you will be helping me learn the beginnings of modding and developing
bump . . . . .
Perhaps this may help
http://forum.xda-developers.com/showthread.php?p=18226553
I have flashed it on my Note, it works well.
I in no way created this, just thought it may be worth while.
The operation of this template is based on the VillainTheme System for the ROM VillainROM.
Link: http://www.villainrom.co.uk/forum/sh...inTheme-System
Credits and thanks to all XDA team that collaborated on the original script: Doctorcete, Stericson, Matt and Seshy
What is Universal Flasher Tool?
is a complete template that is used to create the simplest possible way a subject flashable from recovery without the need to include or edit files. apk.
This new method uses the file system implementation metamorph (just have to put files and folders on their respective routes), with the advantage that the system identifies and injected into their applications without the need for external application. The subjects are flashed directly from recovery.
What are the advantages of this method compared to metamorph or traditional flasheables issues?
Do not include. Apk complete, only the files you want to include in the subject.
A theme created with this template is valid for any rom, even among different phone roms (the tests have been performed with SGS2 and Nexus one).
Optionally, the template can include complete files if desired, can even be used to install applications not system.
Does not depend on external applications like metamorph because it flashes directly from recovery.
Operation of the template
at the end of the post are attached a number of considerations to take into account, but basically works like this:
Identify the applications that want to thematize and checks that exist in the rom. Once the check, the system compares folders that will be introduced as well as files and injects them into the apk as long as the new file exists within the apk. This has been thought well to avoid filling an apk with files that do not belong because they are from another rom or because you made a mistake when typing the name, for example.
Once injected the files takes a zipalign the apk to optimize RAM usage.
Alternatively, if the topic includes external files or copy them to install applications on your path.
At the same time to be using the item, the system will generate a backup of changed files and automatically creates a file. Zip flashable from recovery, in case something goes wrong or do not like changes to previous state.
Finally, it also generates a small log with the outcome of the whole process is recorded in SD to verify that all changes are properly implemented.
How to create and edit your own theme
Download the template from the attachment in this post or the link below.
Recommended Tools: 7zip to include files and browse the file system (you can also use winzip or winrar without problems) and Notepad + + or any other plain text editor to edit the name of the mod.
Once downloaded, open the template double-click will observe and folders inside a file in the root. Here's that are in each folder and how to create the theme.
MOD.config file: (new from version 3.0) is an editable text file (recommend Notepad + +) where in addition to establishing the name of the MOD to set different parameters of the template.
MOD_VERSION= Name (name of the mod to be displayed in the system properties after the name of the rom. Are cautioned not to put a name too long and try to avoid as far as possible in the blanks.
CLEAN_MORPHING = not (compare the new files before injection into the apk, only enter if the file already exists. Turning the option dramatically reduces speed)
V4_MORPHING = yes (support to manage compatibility with existing folders-v4 system in some applications).
DO_BACKUP = yes (enable or disable the creation of the flashable backup from recovery to restore the existing theme).
LOG_ENABLED = yes (enable or disable the creation of a log file with the results of the process).
SCREEN_LOG = yes (shows the process of recovery on the screen or not. important notices are always shown even if the option is disabled).
Optionally, you can set a different path for memory cards (no need to touch these lines in most cases, you should not touch):
default_internal_sdcard = / EMMC
default_external_sdcard = / sdcard
Optionally, you can add special commands to mount partitions (no need to modify these lines in most cases, you should not touch):
mount_system = mount / system
mount_data = mount / data
README.txt:
Includes some additional instructions on the operation and the license. Please read before using the template to create a theme (in English). Carteta / tools: is the folder where you have placed the scripts and binary files necessary to flash the issue and make subsequent restoration. You do not need to touch anything in this folder to edit the theme. From version 3.0 has been deleted because busybox binary is no longer involved in the process. folder / META-INF folder system which includes the signature file and the script to launch from recovery. It is recommended not to touch. Folder / MORPH: This is the template folder where files should be included with the theme. In turn, the folder is divided into two subfolders called / data (for applications theming system NO) and / system (for theming system and applications framework). In the / MORPH / system / app files are included for the applications and / MORPH / system / framework for the framework files. NOTE: NO application theming system in / MORPH / data / app / myapp.apk supposed to change the digital signature, so from that time can not be updated from the market or will you installed in the market (like if it had been installed by 'other means' non-statutory ...). Therefore, we do not recommend any downloaded application thematize the market. You are advised that the complaints do not come then ... For each application you want to thematize must open a new folder called / nombre.apk (eg / Contacts.apk if you want to change the system application Contacts.apk) . It is necessary to respect the use of upper / lower case. Within each of these folders you have to respect that there are logical paths within applications, so that the files would have to place them in folders named / res / drawable, res / drawable-hdpi, etc ... It is the same structure metamorph an issue, so any item is readily convertible metamorph simply dragging folders.
No need to create any control file or anything like . The system is responsible for reviewing the folders to see what applications you want tematitar.
Folder / Xtras / system:
in this folder is where, if desired, can include files or complete applications that you wish to flash in conjunction with the subject. For example, sound files, bootanimation, scripts, complete applications, etc ... Folder / Xtras / data: in this folder is where, if desired, can not add applications to be installed system during flashing. Folder / Xtras / sdcard: in this folder you can add files to make copied to the SD card, as packs of icons, sounds, videos, etc ... to take into account considerations
Always respect the use of uppercase / lowercase letters in the names of files or folders and logical paths located within the apps.
With this system the themes may be universal, although depending on the type of files a user input may cease to be:
If you only include image files theme is compatible with any rom from any phone.
If you also include. xml may only operate in one rom, but can still work on future updates of it.
If resources are included for translations (resources.arsc) the issue would only be valid for a particular rom.
The. Zip with the issue is not necessary for you to sign flashearse, and is valid for CW-Recovery and Recorevy-RA. If you do not have to remember signing off signature checking before flashing.
Original Thread:http://http://www.htcmania.com/showthread.php?t=258333
Also:http://forum.xda-developers.com/showthread.php?t=1474686
On the galaxy s 3 us version most of the recoverys are not reading the external sd so should I changed the mounts on the script?
Sent from my SGH-T999 using Tapatalk 2
Have you ever installed a new rom, but completely forgot which notification sound you were using? I have a nandroid backup of the old rom, but really don't want to completely restore the rom just to figure out which sound I was using. Android stores this in a database, and I'll show you how to access that database. In hindsight, it may just be easier to restore the nandroid backup. But, this is how to do it using a nandroid backup.
I'll be using Ubuntu 12.04 to do this. I believe it can be done with Windows as well, though the commands and programs will differ. Again, this assumes that you don't remember what the filename was. If you do, you can just skip to step 7.
1. Copy your nandroid backup files to your computer. Specifically, the "data.ext4.tar" and any "data.ext4.tar.a", "data.ext4.tar.b", etc. files.
2. The files need to be combined together. Use the command "cat data.ext4.tar data.ext4.tar.a data.ext4.tar.b > data-combined.tar" or similar for your filenames. It combines all of your data.ext4.tar files into one new file, data-combined.tar. This should give you a working tar file. I got this step from http://forum.xda-developers.com/showthread.php?t=2194171.
3. Extract the data-combined tar file. If you're a super-cool linux hacker, you probably know some terminal command to do this, like tar -randomLettersHere (xzvf?). I just right clicked the tar file and selected "Extract Here".
4. Navigate to "./data/com.android.providers.settings/databases/settings.db" and open the file. I didn't have any program to read SQL databases, so I let Ubuntu installed the recommended one for me, called "Sqliteman".
5. Using the list on the left, go under Tables-System. You should see the contents of that table, which look like an excel spreadsheet. The row (or tuple) we're looking for has the field "name" equal to "ringtone" or "notification_sound", depending on which file you're trying to locate. You can scroll through the rows and look for those rows, or you can enter an SQL command in the top box and hit the green arrow to run it and filter just the ones we want. Try this-
Code:
select *
from system
where name='notification_sound' or name='ringtone';
This pulls up all the rows where "name" is exactly equal to either of those strings. You can also search for anything that contains those strings by using this syntax-
Code:
select *
from system
where name like '%notification%';
If you're looking for your ringtone, try a query that just contains "ringtone", like this-
Code:
select *
from system
where name like '%ringtone%';
(That pulled up the actual file for me under the name "ringtone_CONSTANT_PATH")
If you're using a different rom than that I was (or a different device), you might need to tweak what you look for. Try changing the strings you search for. What we're looking for is for the entry where "value" equals something like "content://media/internal/audio/media/238". It might have the word 'internal' instead of 'external'. Note that number at the end, which is some kind of media ID number.
6. Now, open the SQL file "./data/data/com.android.providers.media/databases/external.db" or "./data/data/com.android.providers.media/databases/internal.db" depending on whether the value in step 5 had the word internal or external. Find the row where "_id" equals the number at the end of your "value" string in step 5. You can scroll through the "files" table, or enter a query like this-
Code:
select *
from files
where _id='238';
The field "_data" should show the path for your file. For me, it was "/system/media/audio/notifications/S_Dew_drops.ogg". Oh, how I love you, Touchwiz...
7. Now you know where the file is. If your new rom doesn't have that ringtone/notification sound any more, you can probably retrieve it from two places. First, check the rom installation zip file (probably the easiest way) if it was an included sound. Open the installation zip file, and look in the path you found in step 6. The second way is to go through your Nandroid backup. Follow steps 1-3, but copy, combine, and extract your system.ext4.tar file(s). Again, just look in the same path from step 6, and it should be there. These paths are typically "/system/media/audio/notifications/" and "/system/media/audio/ringtones".
Enjoy your old, familiar sound again!