[Video Tutorial] How to change .apk icon using "Apk Manager 5.0.2"

HOW TO CHANGE .APK ICON USING APK MANAGER.

Many people have asked how to change icons of apps in app drawer,once it was my question too,and I searched every corner of xda to find a thread explaining me that but it was of no avail even though i FOUND one but it didn't work on my sgs2.Therefore,I decided to help everybody who is having the same problem including me.So I brought you the easiest 'n simplest way to change the icons,it's lenghty as many would call it but once you get the hang of it,you'll be changing the icons of 'n on.


JUST FOLLOW THE STEP BY STEP GUIDE;

1. Copy Settings.apk in the folder called "place-apk-here-for-modding"
2. Start the "Script.bat"
3. Choose point 22 "Set current Project"
4. Choose your app you want to extract
5. Choose point 1 "Extract apk"
6. Go to the folder called "Projects" 7. Choose your app you just have extracted
8. Choose the folder called "res"
9. Look in the folders where the icon is.
10. Change the icon but be sure it have the same size ("mdpi: 48x48" hdpi: 72x72" xdpi: 96x96")
11. Go back to script windows or start script.bat again
12. Choose point 22 "Set current Project" again
13. Choose point 3 "Zip apk"
14. Choose point 12 "sign apk"
15. Go back to the folder "place-apk-here-for-modding" now should have a apk here that is called signed"NameOfYourApp"
16. Copy it to your Sd card and install it on your device.

OR WATCH THE STEP BY STEP VIDEO


Get icon packs on the biggest icon thread of xda,thanks to Falloutboy2000
http://forum.xda-developers.com/showthread.php?t=824656

Download Apk Manager here:
http://apkmultitool.com/?q=node/5

Well thats all,if its helpful then dont forget to thank me! peace

[HOW TO][Windows] Manually Deodex For Holiday ICS

This is mod for ODEXED ICS based ROMs. When using the Dsxida's kitchen, there was a slight problem. so I made some modifications to AutoDEOTool


Manually Deodexing :

to decompil an odex file you needs the BOOTCLASSPATH..
It is a list in specific order of some framework .jar files..
It is different in function of the APKs

Run AutoDEOToolMain.bat

1.Place the JARs and corresponding ODEX files in the directory "_framework".
Otherwise, place deodexed framework JARs into the directory "deodexed_JAR".
2.Place the APKs and corresponding ODEX files in the directory "_app".
3. To deodex framework files
-For non standard odex however a specific bootclass path must be defined..
-select to 6
place the bootclass path for framework

Code:

core.jar:core-junit.jar:bouncycastle.jar:ext.jar:framework.jar:widget.jar:android.policy.jar:services.jar:apache-xml.jar:HTCDev.jar:HTCExtension.jar:com.htc.framework.jar:filterfw.jar:com.htc.android.bluetooth.jar:com.htc.fusion.fx.jar:wimax.jar:com.orange.authentication.simcard.jar:com.htc.android.rosie.jar

4.To deodex APKs files for at&t vivid
-select to 4
place the bootclass path for APKs files

Code:

am.jar:android.policy.jar:android.test.runner.jar:apache-xml.jar:bmgr.jar:bouncycastle.jar:bu.jar:com.android.future.usb.accessory.jar:com.android.location.provider.jar:com.cequint.platform.jar:com.discretix.drm.api.jar:com.google.android.maps.jar:com.google.android.media.effects.jar:com.google.widevine.software.drm.jar:com.htc.android.bluetooth.jar:com.htc.android.rosie.jar:com.htc.framework.jar:com.htc.fusion.fx.jar:com.htc.htcSceneManager.jar:com.htc.lockscreen.fusion.jar:com.htc.sunny2.jar:com.orange.authentication.simcard.jar:com.qik.enabler.jar:com.scalado.caps.jar:com.scalado.util.ScaladoUtil.jar:core.jar:core-junit.jar:ext.jar:filterfw.jar:framework.jar:HTCDev.jar:HTCExtension.jar:ime.jar:input.jar:javax.obex.jar:modemwarmup.jar:monkey.jar:pm.jar:services.jar:svc.jar:widget.jar:wimax.jar

4.To deodex APKs files for velocity
-select to 4
place the bootclass path for APKs files

Code:

am.jar:android.policy.jar:android.test.runner.jar:apache-xml.jar:bmgr.jar:bouncycastle.jar:bu.jar:com.android.future.usb.accessory.jar:com.android.location.provider.jar:com.discretix.drm.api.jar:com.google.android.maps.jar:com.google.android.media.effects.jar:com.google.widevine.software.drm.jar:com.htc.android.bluetooth.jar:com.htc.android.rosie.jar:com.htc.framework.jar:com.htc.fusion.fx.jar:com.htc.htcSceneManager.jar:com.htc.lockscreen.fusion.jar:com.htc.sunny2.jar:com.orange.authentication.simcard.jar:com.scalado.caps.jar:com.scalado.util.ScaladoUtil.jar:core.jar:core-junit.jar:ext.jar:filterfw.jar:framework.jar:HTCDev.jar:HTCExtension.jar:ime.jar:input.jar:javax.obex.jar:modemwarmup.jar:monkey.jar:pm.jar:services.jar:svc.jar:widget.jar:wimax.jar

Credits and thanks goes to:
xavierjohn22 auto DEODEXTOOL
XDA-Developers
Football
Too many people
The 'No Idea' Blog
via

---

Attached Files

AutoDEOTool_ICSForHoliday.rar -  (7.70 MB, 769 views)

[MOD][HOWTO][v2] change ICS lockscreen animation to Honeycomb style (ripple)

New Version : much more honeycomb-like version

preview :

howto :

framework.jar

1) line 72~ : change animation speed.

Code:

// Tune-able parameters

    private static final int CHEVRON_INCREMENTAL_DELAY = 800;

    private static final int CHEVRON_ANIMATION_DURATION = 4000;

    private static final int RETURN_TO_HOME_DELAY = 1200;

    private static final int RETURN_TO_HOME_DURATION = 300;

2) line 305~ :

Code:

private void startChevronAnimation() {

        final float r = mHandleDrawable.getWidth() * 0.4f;

        final float chevronAnimationDistance = mOuterRadius * 0.9f;

        final float from[][] = {

                {mWaveCenterX - r, mWaveCenterY},  // left

                {mWaveCenterX + r, mWaveCenterY},  // right

                {mWaveCenterX, mWaveCenterY - r},  // top

                {mWaveCenterX, mWaveCenterY + r} }; // bottom

        final float to[][] = {

                {mWaveCenterX - chevronAnimationDistance, mWaveCenterY},  // left

                {mWaveCenterX + chevronAnimationDistance, mWaveCenterY},  // right

                {mWaveCenterX, mWaveCenterY - chevronAnimationDistance},  // top

                {mWaveCenterX, mWaveCenterY + chevronAnimationDistance} }; // bottom



        mChevronAnimations.clear();

        final float startScale = 0.5f;

        final float endScale = 2.0f;

        for (int direction = 0; direction < 4; direction++) {

            for (int count = 0; count < mFeedbackCount; count++) {

to

Code:

private void startChevronAnimation() {

        final float r = mHandleDrawable.getWidth() * 0.4f;

        final float chevronAnimationDistance = mOuterRadius * 0.9f;

        final float from[][] = {

                {mWaveCenterX - r, mWaveCenterY},  // left

                {mWaveCenterX, mWaveCenterY},  // right

                {mWaveCenterX, mWaveCenterY - r},  // top

                {mWaveCenterX, mWaveCenterY + r} }; // bottom

        final float to[][] = {

                {mWaveCenterX - chevronAnimationDistance, mWaveCenterY},  // left

                {mWaveCenterX, mWaveCenterY},  // right

                {mWaveCenterX, mWaveCenterY - chevronAnimationDistance},  // top

                {mWaveCenterX, mWaveCenterY + chevronAnimationDistance} }; // bottom



        mChevronAnimations.clear();

        final float startScale = 0.3f;

        final float endScale = 1.1f;

        for (int direction = 0; direction < 4; direction++) {

            for (int count = 0; count < mFeedbackCount; count++) {

you can change these values to your taste.


framework-res.apk

download resources (PNGs - WVGA only) :
http://www.mediafire.com/?ksnc84d04w96uv8

1) decompile framework-res.apk

2) delete /res/drawable/ic_lockscreen_outerring.xml

3) add resource PNGs to /res/drawable-****/

4) open /layout/keyguard_screen_tab_unlock.xml

from :

Code:

to

Code:

332.0dip">

        5" android:verticalOffset="0.0dip" android:horizontalOffset="0.0dip" />

        android:visibility="gone" android:textAppearance="?textAppearanceMedium" android:textSize="@dimen/keyguard_lockscreen_status_line_font_size" android:textColor="?textColorSecondary" android:ellipsize="marquee" android:gravity="center_horizontal" android:id="@id/carrier" android:layout_width="fill_parent" android:layout_height="wrap_content" android:layout_marginBottom="12.0dip" android:singleLine="true" android:layout_alignParentBottom="true" />

    

- remove carrier text is not essential..


5) open /res/values/arrays.xml :

from :

Code:

        @drawable/ic_lockscreen_unlock

        @null

        @drawable/ic_lockscreen_camera

        @null

    

    

        @string/description_target_unlock

        @null

        @string/description_target_camera

        @null

    

to:

Code:

        @drawable/ic_lockscreen_unlock

    

    

        @string/description_target_unlock

    

6) open /res/values/dimens.xml

from :

Code:

270.0dip

    135.0dip

to :

Code:

220.0dip

    120.0dip

7) recompile.

-----------------------------------------------------------------------------
Previous version :

  this mod was originally posted in Nexus S theme forum.

[MOD][IMM26] change ICS lockscreen animation to honeycomb style

at first, i don't have any intention to write guide for this mod because i think the method is too stupid ..
but many people requested it so i wrote this simple guide.

-----------------------------------------------------------------------------

firstly, you have to edit lockscreen animation related code.

1) primitive way

platform_frameworks_base/core/java/com/android/internal/widget/multiwaveview/MultiWaveView.java


1) line 72~

Code:

// Tune-able parameters

    private static final int CHEVRON_INCREMENTAL_DELAY = 160;

    private static final int CHEVRON_ANIMATION_DURATION = 850;

    private static final int RETURN_TO_HOME_DELAY = 1200;

    private static final int RETURN_TO_HOME_DURATION = 300;

to

Code:

// Tune-able parameters

    private static final int CHEVRON_INCREMENTAL_DELAY = 480;

    private static final int CHEVRON_ANIMATION_DURATION = 3000;

    private static final int RETURN_TO_HOME_DELAY = 1200;

    private static final int RETURN_TO_HOME_DURATION = 300;

2) line 305~ : same as above guide (new version).


and if you think this method is too difficult...


2) much easier way

1) decompile you rom's framework.jar using apktool.

2) go to framework.jar/smali/com/android/internal/widget/multiwaveview

3) download this file.
- for stock, AOSP or CM9 based rom : http://www.mediafire.com/?1wkbjt1bxsqsjnr
- for AOKP based rom : http://www.mediafire.com/?zb4mm1aaas1c8oc

this zip contain MultiWaveView.smali. replace original file with this one.

4) recompile.

5) done

-----------------------------------------------------------------------------

time to theme

: you have to replace lockscreen related PNGs in framework-res.apk.

framework-res.apk/res/drawable-hdpi or mdpi or xhdpi...

- ic_lockscreen_chevron_down.png
- ic_lockscreen_chevron_left.png
- ic_lockscreen_chevron_right.png (important)
- ic_lockscreen_chevron_up.png

and if you want, change lockscreen handle too.

- ic_lockscreen_handle_normal.png
- ic_lockscreen_handle_pressed.png


all my works are here (for hdpi).

1) default honeycomb ripple : http://www.mediafire.com/?7ktduz5dhsmzq6p

2) chrome logo :

download : http://www.mediafire.com/?osjng768zznfeh6

3) android logo


download : http://www.mediafire.com/?56sjs541bij3ygu

4) AT Field style (octagonal ripple)

download : http://www.mediafire.com/?t8lrdkr23nex7pc

5) Google Play logo

download : http://www.mediafire.com/?1vbc3ctdc7p94j4   

[Guide_Beginner][Root][ICS] Many alternative root ways for your ICS phone

Beginner Guide to Root your ICS phone (S2 and other phones)

Since CF_root thread is no more updated, many people are asking for a new way to root their phone.

I will try here to reference most threads and ways to root your phone. Some methods will let you root as soon as you get the new ROM, no more waiting for some dev to release a kernel for you.

I will not list here custom kernels that come with root, you can find them in other threads.




1- My preferred method: Inject Chainfire SuperSU + Busybox last versions with CWM
Universal and will probably work on any ICS phone, if you have a CWM image. No longer wait for a modded kernel

It is derived from original thread here (do not forget to say thank you to Rachmat3). I modified it to include superSU last version + BusyBox last binary
http://forum.xda-developers.com/show....php?t=1501719

Here, you will flash a cwm zip file that will inject supersu and busybox with correct permissions. You even have an unroot script if you want to change your mind

- Get a cwm image for your phone from here http://clockworkmod.com/rommanager
I also attached the last cwm touch for i9100: recovery-clockwork-touch-5.8.1.5-galaxys2.zip
- Put the downloaded CWM zip file on your external sd
- Boot into stock recovery (volume up+home+power), and select "apply update from external storage". Now select the CWM zip file you copied in previous step (this step gives a temporary flash that will disappear after reboot)
- You get CWM touch recovery interface (this custom recovery is temporary, not permanent)
- Inside CWM, select "install zip from sdcard". Now, select "choose zip from sdcard" (directs to internal sdcard) or "choose zip from internal sdcard" (directs to external sd) and point it to the attached "CWM_Root_SuperSU_0.92+Busybox_1.20.1.zip"
- It will add SuperSU 0.92 apk to system/app, last SuperSU binary to system/xbin and busybox 1.20.1 to system/xbin, all with correct file permissions.
- Reboot and you get permanent root + busybox installed on your stock kernel.

To unroot, there is a script in original Rachmat3 thread. Just flash it using cwm like in above steps, it will also work with my superSU file attached here

2- Second recommended method - CF_Root + stock kernel + [optional] Mobile Odin Free version
Here, you use an older CF_Root kernel, and flash your newer stock kernel

- First, get a CF_Root kernel from CF_Root thread here http://forum.xda-developers.com/show....php?t=1103399. Just get the nearest one to your ROM. You can download any ICS kernel, it will do the job for the root only purpose
- Flash the CF_Root kernel with odin
- Now, flash again your stock kernel with odin. You can get a stock kernel from lyriquidperfection thread http://forum.xda-developers.com/show....php?t=1619525
Do not forget to thank / donate to him
- No stock kernels for you? use Mobile Odin free version (see below)

After flashing the stock kernel, root will usually stay and you will loose the CWM custom recovery

3- Insecure Kernels + SuperOneClick + [optional] Mobile Odin Free version
Not tested by me. You get superuser instead of Chainfire superSU + an older busybox

- First, get an insecure kernel from here http://forum.xda-developers.com/show....php?t=1619525
Do not forget to thank/donate lyriquidperfection
- no insecure kernel for your ROM? Just try a kernel from same ICS version, it usually works fine for rooting
- Flash the insecure kernel with odin
- Download SuperOneClick v2.3.3 from here http://shortfuse.org/?p=193 and look at this thread for an overview: http://forum.xda-developers.com/showthread.php?t=803682
- Put your phone on USB debugging mode (System Settings / Developer Options)
- Launch SuperOneClick and root using auto or psneuter method. Do not use the ZergRush Exploit as it is meant for older exploited GB versions
- Now, flash again your stock kernel with odin. You can get a stock kernel from lyriquidperfection thread http://forum.xda-developers.com/show....php?t=1619525
Do not forget to thank / donate to him
- No stock kernel for your ROM? Use Mobile Odin Free version (see below)

4- Mobile Odin Free version
Flash your stock kernel from complete ROM file
Now that Intratech stopped releasing stock kernels in his thread, rooting using methods 2 or 3 can be a problem. In fact, you will not be able to flash your newer original stock kernel after rooting with insecure or cf_root older kernel. You can look in above lyriquidperfection thread for a stock kernel to flash in odin. But, if you do not like to wait for him to release a kernel, you can get Mobile Odin Free version

- Download Mobile Odin Free version from here http://forum.xda-developers.com/show....php?t=1347899
Do not forget to thank donate to Chainfire
- From your stock tar.md5 ROM file, extract the zimage file (your stock kernel)
- Put zimage file on external sd card
- Run Mobile Odin and specify the zimage file in kernel box like in this image:


- Flash, you get your stock kernel and root is normally left

5- Mobile Odin Pro (Payed) version
Great tool, but not free. You should really consider buying it.
With this method, you will have SuperSU from chainfire (that can be updated from market) but no Busybox. You can install it from market or attached CWM_Busybox_Only_1.20.1 file in this thread

- Buy Mobile Odin Pro from market here https://play.google.com/store/apps/d...mobileodin.pro
- If you want to flash a full new rom, put the tar file on the external_sd. Point all boxes to the ROM tar file. Enable EverRoot option like in image below. Flash


- If you flashed your ROM using odin and only want to root, proceed like in Example 4 above to flash only the kernel (zimage file from your actual ROM). Enable EverRoot option and flash
- Now, install BusyBox from market or flash my CWM_Busybox_Only_1.20.1.zip file with cwm to get last busybox.

Feel free to comment or suggest enhancements

Attached Files

	recovery-clockwork-touch-5.8.1.5-galaxys2.zip -  (1.51 MB, 0 views)
	CWM_Root_SuperSU_0.92+Busybox_1.20.1.zip -  (1.35 MB, 0 views)
	CWM_Busybox_Only_1.20.1.zip -  (862.5 KB, 0 views)

How to root your Samsung Galaxy S2

One of Android's biggest strengths is that it's an open source operating system, which means that anyone with programming talent can potentially tinker with the code and make it even better. With that in mind, we've complied this handy guide for gaining root access on what is arguably our favourite Android handset: the Samsung Galaxy S2.



Read through our guide below, or watch the handy video above that shows you how it's done.

A large number of custom operating systems -- referred to by seasoned hackers as 'ROMs' -- have been created which not only remove unwanted bloatware installed by hardware manufacturers, but also speed up your handset and boast awesome new features.
However, all Android phones come locked-down by default, which means you can only install firmware updates that have been officially sanctioned by the manufacturer or your network provider. To tap into the wonderful world of Android customsation, you'll need to gain root access to your phone.
While it all sounds a bit clandestine and spooky, getting root access is just like having admin privileges on a computer. It allows you to change settings and tinker with elements of your phone's software that are usually out of bounds. A very simple example is being able to alter the boot-up animation that comes pre-loaded on your device.
Although it's not quite as difficult as playing a game of Angry Birds blindfolded, rooting your phone isn't for the weak-willed.
Before we proceed, it's important that we outline the risks involved here. Although in the case of the Galaxy S2 the rooting process is usually reversible, messing about with the inner-workings of your phone's software immediately invalidates your warranty. It may break your phone completely. CNET UK takes no responsibility for any harm that may befall your beloved handset as a consequence of you acting on the steps we've outlined below.

Step 1: Grab everything you need

Before you do anything, make sure you've downloaded and installed Samsung's Kies application, as it contains the necessary drivers for allowing your phone to communicate with your computer. You can grab the installation file from Samsung's website.
Next up is Odin3, which can be downloaded from here.
You'll also need an insecure kernel, which can you get from here. Although it's recommended that you pick a kernel with a code as close as possible to the one your phone has already (to check this, go to Settings > Applications > About Phone, and you'll see it under Kernel Version), it's not strictly required as you can reload a secure kernel once the whole rooting procedure is done and dusted.
Finally, you need the piece of software that does the magic: S2 Root. Grab it from here. Are you all sitting comfortably? Let's roll.

Step 2: Enable USB debugging

This is important. Unless this feature is enabled on your handset, you won't be able to proceed. Go to Settings > Applications > Development, and make sure the 'Enable USB Debugging' box is ticked. Once this is done, give yourself a pat on the back and move onto Step 3.

Step 3: Put the phone into Download Mode

Turn off your phone. Hold down the Volume down button, Home button and Power button. The phone will reboot and you should see a screen warning of the dangers of installing custom OS software. If you are happy to proceed at your own risk, press the volume up key to place the phone in Download Mode and you'll be presented with Andy the Android, in all his luminous green splendor.

Step 4: Load up the insecure kernel using Odin3

Use your USB cable to connect your Galaxy S2 to your PC. Run the freshly-downloaded Odin3 application on your computer. You should notice that the box in the top left of the Odin interface is yellow, which means your phone has been successfully recognised. You should now check that only the 'Auto Reboot' and 'F. Reset Time' check boxes are ticked in Odin's settings.
Press the PDA button in Odin3 and then select the kernel you obtained earlier. Take a deep breath and click the 'Start' button. Once the process is complete your phone will switch itself off and Odin3 should display a green 'PASS' notification on your computer's screen.

Your phone may reboot itself, but if it displays the battery charging icon you will need to manually switch it back on. When the standard Galaxy S2 boot screen appears, you should have a yellow triangle with an exclamation mark at the bottom of the display, indicating that you are running an insecure kernel (which you already know).

Step 5: Root using S2 Root

Keep your phone connected and wait for it to properly reboot itself. Once it has, start up S2 Root. You'll get a little warning message asking if you have flashed an insecure kernel and enabled USB debugging -- which, if you've been awake during this guide, you will already have done. Click OK.
If you're running Windows XP then you may find that you're missing some Microsoft .net Framework files that are required to run S2 Root. Fear not, however -- you can grab them from here.
S2 Root boasts a mercifully simple interface with nice, friendly buttons that say things like 'ROOT' and 'UNROOT', making it pretty easy to use. No prizes for guessing which one you need to click on now.

Once the phone has fully rebooted, you will find that you now have root access and the all-important Superuser app (which allows you to give other applications root privilages) has been installed. You can spot it in your app drawer -- it's the one with the Android-style skull and crossbones icon. If it hasn't appeared, try repeating this step a second time.

Step 6: Reload a secure kernel (optional)

Because you're still running an insecure kernel, you'll keep getting that annoying warning triangle every time you boot the phone up. It's not actually detrimental to your phone's functionality, but if you'd rather remove it you can grab a secure kernel from here and load it up using the instructions outlined previously in Step 4.
Congratulations! You are now the proud owner of a rooted Samsung Galaxy S2. If you're feeling particularly brave then you should download ROM Manager Premium, which allows you to load up new operating systems, backup your existing ROM and much more - but that's a whole different guide entirely.

Step 7: Changing your mind

Should you for some reason wish to rescind root access then all you need do is follow Step 4 to re-load the insecure kernel and click the 'Unroot' button in the S2 Root application.

How to Use Android ADB Command Line Tool

Android Debug Bridge (adb) is a tool that lets you manage the state of an emulator instance or Android phone. ADB is bundled with Android SDK package that can be downloaded from Android SDK download page. This tool is usefull for communicating with Android phone such as install application, copy files from/to device and perform some linux shell commands.
How to Install

• Download and install Java SDK (Ex: jdk-6u20-windows-i586.exe)
• Download Android SDK package (Ex: android-sdk_r06-windows.zip)
• Extract SDK package into anywhere on your drive (Ex: D:\android-sdk-windows)

Phone Setup
In order to use ADB, you have to enable USB Debugging option in  phone settings (Settings->Applications->Development)

How to Use

• Connect the phone to your pc/notebook usb port
• Run Windows command line tool (cmd) and go to D:\android-sdk-windows\tool

Update!!
New Android SDK puts adb executable file on \platform-tools directory instead of tool. So the path should be D:\android-sdk-windows\platform-tools
Usefull Commands
1. Check connected phone
Syntax: adb devices

2. Login to Android shell
Syntax: adb shell

Note:
If you get ‘#’ after typing adb shell, you are already get root access on the phone, no need to type su. Otherwise if you get ‘$’ , type ’su’ to get root access (only for rooted device).
3. Some usefull shell commands

• ls
List directory Syntax:  ls [path]Example: #ls /system/lib
• cp
Copy file or directory Syntax: cp [options] source destNote: To copy or delete files in Android root directories you have to change the directory access mode to ‘read and write (rw)’ using command: remount rwExample: #remount rw #cp /sdcard/libsec-ril.so /system/lib #remount ro
• mv
Move file or directory Syntax: mv [options] source destExample: #mv /system/lib/libsec-ril.so /sdcard/backup
• chmod
Change file/directory permission Syntax: chmod [-R] mode[,mode] …. fileExample: #chmod 0644 /system/lib/libsec-ril.so
• rm
Remove file or directory Syntax: rm [options] fileExample: #rm /system/lib/libsec-ril.so

4. Install application

You can use adb to install aplication from your local drive into  phone.
Syntax: adb install appname.apk
Example:
D:\android-sdk-windows\tools\adb install D:\AnReboot.apk

5. Copy files from phone to local drive
Syntax: adb pull source [destination]
Example:
D:\android-sdk-windows\tools\adb pull /sdcard/arm11-dvm.zip
D:\android-sdk-windows\tools\adb pull /sdcard/arm11-dvm.zip D:\

5. Copy files from local drive to phone
Syntax: adb push source destination
Example:
D:\android-sdk-windows\tools\adb push D:\AnReboot.apk /sdcard

[TUT]How to Port Original Samsung keyboard from stock Rom to Custom Roms.

This tutorial show you how to port stock sam keyboard to a custom rom. Spent 4 days in learning and testing and now its working on carbon for me. file is flashable.
you need these files and folders … take from your stock rom odin flashable file: (use magicIso or UltraIso)
- T9DB folder (from csc.rfs file)
- AxT9IME.apk and AxT9IME.odex (from system.rfs file in app folder)
- touchwiz.xml (from system.rfs file in etc->permissions folder)
- libdhwr.so and libXt9core.so (from system.rfs file in lib folder)
first deodex your AxT9IME.apk (see post #2)

make a flashable zip file and put stock files like this: (or use attachment zip file and delet my files and put your files.)
- T9DB folder in: yourzip/system/
- touchwiz.xml in: yourzip/system/etc/permissions
- libdhwr.so and libXt9core.so in: yourzip/system/lib
- deodex AxT9IME.apk in: yourzip/system/app
move zip file to SDcard and reboot to recovery(CWR) and select "install zip from SD". after install go to advanced menu and wipe dalvik cache.
finish! now reboot and use Samsung keyboard with your language.
<# if your rom is odex go to system/app with root explorer, find AxT9IME.apk and AxT9IME.odex and add ".bak" to end of two files then reboot to recovery.#
Asian rom keyboard extracted from S5830DDKQ6 INDIA with this languages:
English(US)-English(UK)-France-polski-Korean-deutsch-espanolitaliano and many more (all rom have english and Korean)
Note : Before flashing got to system/app and rename your old keyboard and add .bak in the end of its name.
for example : if old keyboard is latin.apk and latin.odex then rename to latin.apk.bak and latin.odex.bak.
thats all now go into recovery

1. clear dalvik cache.
2. install my zip.
3. reboot enjoy samsung keyboard.

Download :
http://letitbit.net/../Original_Stock_Keyboard_for_Ace_mor_-signed.zip.html
http://www.mediafire.com/?ng91ukx1ls2dad1
http://www.mirrorcreator.com/files/1XBXZBMV/

Incoming search terms:

• samsung keyboard apk
• samsung keypad apk
• AxT9IME apk
• axt9ime
• stock samsung keyboard apk
• original axt9ime
• t9db
• samsung keyboard apk download
• samsung stock keyboard
• samsung galaxy note keyboard apk

[GUIDE] The Noobs Guide to Android ROM'ing

Work in progress..

Now the purpose of this guide is only one, to guide you through “cooking” your own stock flashable ROM from a shipped ROM… That’s it. It’s not hard but it does help you start the journey of the real dev work. There are to many "Devs" around that just do something like this guide and copy files from other ROMs to theres, And this DOES NOT make you a Developer so please dont go posting stock deodexed ROMs everywhere and call yourself a Developer

Before starting I’m going to assume you have setup the correct ADB Drivers for your device although not really needed to make a ROM, it does make it easier in the long run.
Once you run through this guide you will have a stock ROM with ROOT permissions, DeoDexed, Zipaligned, Busybox and init.d support. From there you can modify your ROM to your hearts content, all this is doing is making your base. The real Dev work is .smali editing, modifying .xmls making your own apps, etc... This guide will just help you to not rely on other members to release "Stock deodexed ROMs"

Wording:

ROM = An Android Operating system
Cooking = Making your own ROM
Shipped ROM = A Stock ROM for your device, e.g. a RUU.exe etc…
Kitchen = The Dsixda’s ROM Kitchen
ADB = Android De-Bugging
CWM = Clockwork Mod Custom Recovery
zImage = Kernel controls CPU, Battery etc.
Modem/Radio = Controls cell signal, internet etc.
ROOT = ROOT Permissions, access to the ROOT or / of your device, kind of like the Windows folder on your computer.
DeoDexed = Removing the .odex files from a ROM to allow for .apk customizing e.g. Theming etc..
.apk = Android application file
Init.d = Allows the running of scripts such as Memory tweaks and SD-Card tweaks etc.
SU = Superuser
CMD = Windows Command Prompt
MOD = Modification

ADB Short codes that may be helpful later:

Type these directly into your CMD window with your device plugged in.

adb reboot recovery = Reboots your phone straight into recovery mode
adb reboot = Reboots your phone
adb push = use this to push files to your phone, make sure you are in the folder with the file you want to push in CMD (Example, adb push c:\android\SystemUI.apk /system/app)
adb logcat = Tells you what your phone is doing.
adb remount = Remounts the partition specified (Example, adb remount /system)

Note 1:

When making a ROM the overall concept is the same for every device that runs CWM or any other custom recovery. The only main difference is extracting the files you need from the Shipped ROM

Note 2:

It makes it easier to have a shortcut to your kitchen folder and any others you need in your favourites or dektop

Part 1. Setting up the “Kitchen”

Go to THIS FAQ and choose the method you prefer to install on. If you are running Windows I recommend the Cygwin way. It’s easier and you don’t need to keep booting between Linux and Windows, You don’t even need Linux if you do it the Cygwin way. And please do get the pictorial guide HERE, it helps A LOT for “noobs” and don’t forget to install the Java JDK if you do Windows Option 1. Keep in mind that doing it on Ubuntu IS much faster.

NOW IF Cygwin is to difficult for you, just download Ubuntu and install it next to windows.


Part 2. Extracting the files you need.

There are a few different ways you can do this, the main ones are:

For HTC Devices

1. Get a RUU.exe from the internet for HTC Devices and extract the system.img and boot.img
2. Download the RUU and run it on Windows, proceed until you get to the screen with the picture of the phone, see bellow. – (No you don’t need to plug your phone in)
   
   
   
3. Open your Start Menu on Windows
4. In the Windows 7 search bar type %temp% and hit enter
5. In the folder that opens click in the search box in the top right corner and search ROM.zip
6. Drag ROM.zip to your desktop, open and extract system.img and boot.img to your desktop.

________________________________________________

For ANY Android Device (Or if you cant get them any other way)

• Using a backup of a stock ROM, This way gives you the ability to make a ROM from pretty much any device that has CWM installed.
• Taking the system.img and boot.img from the backup folder

________________________________________________

For Samsung Devices:

Extracting the following from a Samsung Shipped ROM

• factoryfs.img (and optionally: cache.img, zImage, modem.bin)
• TAR file containing factoryfs.img (optional: cache.img, zImage, modem.bin)
• ZIP file containing factoryfs.img (optional: cache.img, zImage, modem.bin)

Any of these above methods can be used and the extracted files placed in the ORIGINAL_UPDATE folder of the kitchen in the next step. If your device is not compatible with these methods check the device list in this THREAD for more guides.



Part 3. Setting up the working folder.

Now we have the files needed to make our ROM let’s get to it!

1. Go to your kitchen folder then the original_update folder and place your files in It
2. Start the kitchen by starting Cygwin and typing cd kitchen then ./menu
3. Hit option “1. Setup working folder from ROM” press enter again
4. Select the option you want from the list e.g. “(1) system.img and boot.img”
5. Rename the folder if you wish but it doesn’t matter, hit enter
6. If you are working from system.img and boot.img you need to run through the extraction process in next step. Most new ROMs use an EXT4 file system so if you are unsure just hit option “2 – Run Ext2Explore (EXT3/EXT4)” and follow the instructions in the Cygwin window (If you are just using a .zip or .tar etc. you don’t need to do this step.)
7. When that’s finished hit “3 – I’m finished unpacking / abort”
8. Finally hit Y to see you working folder details once its run through the process.

Part 4. Add the options you want to add

A good thing to do now is, keep it simple. The kitchen is best to use only for making your ROM base, once you have the .zip file most customizing can be done from there unless you need to edit the boot.img etc. but we are not going to get into that in this guide.

Now, we are going to make a simple ROM base optimized for speed and functionality. Follow the next steps and by the end you will be ready to build the ROM.

1. The most obvious of all, we will add “ROOT Permissions”. So choose option 2.
2. Always stick with Chains method so hit option F, this won’t take long at all, wait for it to finish the press enter to continue.
3. Next add Busybox with option 3, hit Y to continue and enter when finished.
4. Most people disable boot sounds (option 4), I usually just do it later if I choose to.
5. Don’t worry about Zipaligning because we will do it when we build the ROM.
6. Next choose option 0 for advanced options.
7. If you ROM isn’t already DeoDexed choose option 11
8. If you wish you can backup both folders but I usually don’t bother.
9. Then select option B to Deodex BOTH folders, this one will take some time, on an HP Laptop core2duo with 4gig of RAM takes about 15 minutes.
10. Now add /data/app functionality so choose option 13 and select Y to continue, This allows you to move apps from the system folder to your /data/app folder before the install, which in turn allows the end user to uninstall the apps if they wish. This can ONLY be done with certain apps, like apps you get from the market.. YouTube, Google Maps, Twitter etc. DO NOT put dependent apps like SystemUI.apk etc in the /data/app folder.
11. Next add the Nano text editor on option 14
12. Next add Command Shell or “Bash” with option 15
13. Next add init.d support with option 17 to allow the running of init.d scripts, sometimes you may have to manually add the init.d folder to your ROM at the end or before build, either way it doesn’t matter.

Now we are ready to build the ROM and flash it. Understand that all these are optional, if you want to you can just deodex the ROM and go straight to option 99 and build the .zip file. This is just what I recommend you do

1. Next go to option 99 when you’re ready to build your ROM.
2. For now you will choose option 1 “Interactive Mode”
3. When it asks you to Zipalign your .apk’s you can now choose Y and it will quickly run through and Zipalign all the .apk’s in your build.
4. Once finished, it will start building you ROM.zip file this may take about 5-10 mins on a slow computer or if your CPU is busy already.
5. When that’s finished it will ask you to either continue with the updater-script or not, this is always a YES for you guys, so hit Y and move on.
6. Now we need to Sign our ROM, this is always a YES also
7. The final step is to either rename your ROM or not, it doesn’t matter if you do it now or just rename the .zip file later, so do what you wish and hit enter.
8. Congratulations you have made your first ROM! You can now backup your current setup in CWM and flash it from your SD-Card, be sure to do a full wipe if it’s the first time and install it.

Note 1:

Sometimes you may get an error and CWM wont flash it, USUALLY this is because the kitchen has screwed up the updater-script but this doesn’t often happen. If it does take one from another ROM on the SAME DEVICE (<< IMPORTANT) and add it to your ROM.

Part 5. Further Mods and tweaks:
Resources:

via 

How to Flash ‘.zip’ Files Using ClockworkMod [CWM] Recovery on Galaxy S

Our visitors have been asking us to make a quick and simple guide on how to flash “.zip” files using ClockworkMod [CWM] Recovery.

  The methods and procedures discussed here are considered risky and you should not attempt anything if you don’t know completely what it is. Do this only if you’re capable of getting your phone back right on your own. If any damage occurs to you or your device, we won’t be held liable. You only will be responsible — you’ve been warned. Okay!

So here it’s (folks!):

Instructions on How to Boot & Use CWM Recovery:

1. Switch off your phone, and wait until it vibrates.
2. Now boot into recovery mode, press & hold the following combination of keys together: “Volume UP + Home key + Power button”
3. Use the “Volume  UP & DOWN” keys to navigate/scroll through options in the recovery
4. Use the “Power button” to select an option in the recovery

Instructions on Flashing “.zip” files using CWM:

1. Transfer the “.zip” you want to flash to your sdcard.The best way is to save the file in the root of SD Card. But you can also save the file in any folder you wish on your SD Card.
2. Boot into recovery mode [See instructions above]
3. Now Scroll to “install zip from sdcard” and select it.
4. Select  “choose zip from sdcard”.
5. Scroll to the file you transferred in Step 1 and select it.
6. Now confirm installation by selecting “Yes — Install xxxxxxxxxxxxxxxxx.zip”
7. Once the installation is complete, go back and select “reboot system now”That’s it.

Important! These are only general steps on how to flash files using CWM, but if the file you’re flashing requires additional things to be done before/after flashing then please kindly do that too. For e.g “wipe data/factory reset”, “wipe cache partition” etc. 

Samsung Galaxy S: How to install kernel using Odin

Installation Guide using Odin

Disclaimer: I make no guarantees that this will work for you. It might brick your phone. Do this at your own risk.

Pre-requisites

You need to have Kies previously installed on your PC, for the USB drivers.

1. Download Odin and the kernel

Download Odin 1.85 from here. Extract the files into a temporary folder, for example C:\Temp\Odin\.

Download the kernel.
If you are using the ICS ROMs, download the kernel from here.
If you are using the Gingerbread, download the kernel from here.

Make sure to download the Odin flashable version (not the -CWM version).

Ex:Copy the speedmod-kernel-x-y.tar file into the same directory as Odin.

WARNING for Galaxy S2 and Note: The Galaxy S2 and Note keep track of how many times you have flashed a custom kernel or firmware. This could void your warranty. The counter can be reset but the procedure is not trivial, and you'll need to use a hardware USB jig. More information here.Or use TriangleAway v1.51 with ICS firmware

2. Put your phone into Download Mode

- Before you start, make sure your phone's battery is sufficiently charged (50% or more.)

- Power off your phone.

- Wait for the phone to completely shut down (it takes about 30 seconds).

- Press and hold Volume-Down + Home + Power at the same time.

- The phone should boot into Download Mode with the words "do not turn off target":

3. Run Odin and connect your phone

First make sure to quit / exit Kies!

From the directory where you extracted the files, run Odin3 v1.52.exe.

Now plug in your phone to the USB port of your PC. If you have Kies previously installed, you should see one of the ID:COM boxes turn yellow:

4. Now select the kernel file

- In PDA select the speedmod-kernel-x-y.tar file you extracted

Leave the other settings as default:

- PHONE, CSC, PIT should be blank

- Re-partition should be un-ticked

You should see something like this:

5. Flash the firmware

Click on the "START" button to start the firmware upgrade. Do not disconnect your phone or PC at this point.

After the upgrade finishes, your phone should reboot. Go to Step 6.

IF ERROR: In case Odin does not start flashing and shows an error, your phone might go into the "download error" mode:

DON'T PANIC. This happens sometimes when there is a USB connection error.

First disconnect the USB cable from your phone.

Next shutdown your phone, by either: Press and hold the power button for about 30 seconds. The phone will power off. If it does not, just take out the battery and put it back in.

Close Odin and try again from Step 2.

6. Checking the kernel version

Your phone should reboot automatically and boot into Android. Congratulations!

You can check the kernel version by going into Settings > About Phone and checking Kernel Version:

It works!

New here? READ THIS THREAD FIRST. What Is Recovery & Download Mode?

I'm now going to try and explain some basic concepts of the SGS2, in a very simple way, with illustrations. First of all, a few pieces of terminology.

CWM (Clockworkmod) Recovery Mode:

After flashing a CWM kernel (like CF-Root), you enter recovery with the key combination of Vol Up + Home + Power




CWM recovery is where you flash ROMs, and other zip files. Use the volume keys to navigate, and the home key to select.

Stock (3e) Recovery (not much use):

Entered with the key combination of Vol Up + Home + Power. Not readily accessible if using a CWM kernel like CF-Root



This is the default Android recovery image. It is of little use other than wiping the data partition via factory reset. If you have this, you are NOT ready to start flashing custom ROMs, and will get various errors until you have recovery showing like in the first picture.

Download mode (for use with ODIN/Heimdall):

Accessible on all phones, regardless of kernel via Vol Down + Home + Power



This is where you flash tar or tar.md5 files from ODIN on your PC.


Don't mix up these different modes. Each has a different purpose. So now you know what each mode is, and how to get to it.

What Is ClockworkMod Recovery And How To Use It On Android [Complete Guide]

ClockworkMod – also known as Clockwork and CWM – is a custom recovery for Android phones and tablets that allows you to perform several advanced recovery, restoration, installation and maintenance operations on your Android device that aren’t possible with the stock recovery. In what follows, we will cover all that this recovery is capable of doing, and how to do it.

Here is what we shall be covering in this guide:

1. About Android recovery
2. Introduction to ClockworkMod
3. Installing ClockworkMod
4. Booting into ClockworkMod
5. Feature tour
6. Using ClockworkMod for ROM, kernel, apps, theme or mod installation.

Now let’s take a look at each of these topics in detail.

About Android Recovery

All Android devices ship with a recovery console that is basically a partition on the device’s internal memory and can be booted into. The stock recovery of almost all Android devices provides a few basic yet handy options that allow you to factory reset your device and also to recover its operating system using an official ROM in zip format, but that’s all you can do with it. That’s where a custom recovery comes handy.
A custom Android recovery basically replaces the stock recovery with one that lets you do all you can do with the stock recovery, plus a plethora of more options to give you a lot more control on your device. With a custom recovery, you can install official and unofficial ROMs as well as other updates including apps, themes, kernels etc. using zip files, wipe not just user data but pretty much every partition on your device, mount the storage card for USB mass storage access without leaving recovery, partition your SD card, wipe Dalvik cache and battery stats, fix permissions, perform, manage and restore backups and so on.

Introduction to ClockworkMod

ClockworkMod recovery is one of the most widely used custom Android recoveries that is available for most mainstream Android devices. It is our custom recovery of choice here at AddictiveTips and almost every custom ROM that we install on our devices is done using this recovery.
ClockworkMod recovery has been developed by Koushik Dutta (also known as Koush) – the same guy who brought us the Android ROM Manager. He can be found at his blog hacking away at Android devices and at Twitter.

Installing ClockworkMod

What sets ClockworkMod recovery apart from most other custom Android recoveries is its dead simple installation process on most devices. It does require you to fully root your device in order to be installed but once rooted, installing it is as simple as installing ROM Manager from Market, launching it and using its first option i.e. the one that says ‘Flash ClockworkMod recovery’. We have this method covered in detail in our guide on how to install ClockworkMod recovery to your Android device.
However, in certain cases, this ROM Manager method will not work. The following scenarios will require alternative installation methods:

• Your device doesn’t have an official version of ClockworkMod recovery released yet but you have found a custom version built by someone else using the ClockworkMod recovery source code.
• Your device does have an official version of ClockworkMod recovery released but there is either a yet-unreleased official version or an unofficial version that you want or need to install instead.
• Your device has some added protection enabled by the manufacturer preventing the automatic ROM Manager method for installing the recovery, as with some Samsung Galaxy S series devices.
• Your device isn’t a native Android device but Android has been ported to run on it and it therefore requires a specialized method for installing ClockworkMod recovery, as with the HTC HD2.

We have most of these scenarios already covered and you can use the following guides to install ClockworkMod recovery if the automatic ROM Manager method fails for you.
Multiple devices:

• How to install any Android recovery on any Android device using fastboot or flash_image.
• How to install any version of ClockworkMod recovery using ROM Manager with a trick.
• Our ClockworkMod recovery section for guides on several other devices including most tablets.

Specific devices:

• How to install ClockworkMod recovery on Samsung Galaxy S I9000.
• How to install ClockworkMod recovery on Samsung Continuum.
• How to install ClockworkMod recovery on HTC HD2 with MAGLDR.

Booting into ClockworkMod

Once you have ClockworkMod recovery installed on your Android device, booting into it is quite simple. All you have to do is launch ROM Manager and tap ‘Reboot into Recovery’.
Also, if you have ADB installed on your computer, you can simply enable USB debugging mode on your device from Settings > Applications > Development, connect it to your computer via USB, launch a Command Prompt / Terminal window on your computer and enter this command:

adb reboot recovery

The above methods will not work in certain cases though, for instance if you can’t boot into Android in the first place due to some issue, or if you are using a device like the HTC HD2 that doesn’t natively support an Android recovery. Many solutions are available in these cases.

• Using hardware button combination on most Android devices:
  On most Android devices including ones by HTC, you can enter recovery by powering your device off and then powering it back on while keeping either the ‘Volume Down’ or the ‘Volume-Up’ button pressed, depending on the device. This will enter the bootloader from where you can select the ‘RECOVERY’ option by navigating to it with the Volume key and entering it with the ‘Power’ key.
  On most Samsung devices specifically Samsung Galaxy S series devices, you must keep both the ‘Volume-Up’ and ‘Home’ keys pressed while powering on the device, to directly enter recovery.
• Using MAGLDR on HTC HD2:
  Entering ClockworkMod recovery on the HTC HD2 can’t be done via ROM Manager or any hardware button combination but that doesn’t mean it is difficult in any way. All you have to do is power the device off, power it on by keeping the Power key pressed till you see the MAGLDR bootloader’s menu and finally selecting the ‘AD Recovery’ option.

Feature Tour

Now that you have ClockworkMod recovery up and running on your phone or tablet, let’s take a look at all the options it offers you to manage your Android device. We are using a Nexus S running ClockworkMod recovery 3.0.0.5 but the details should apply to other devices and other 3+ versions of the recovery as well, while versions prior to 3 will have some very minor changes that shouldn’t be an issue.
This is what you see when you reboot your device into ClockworkMod recovery:

You can navigate these options by using the Volume-Up and Volume-Down keys to highlight an option and the ‘Power’ key to enter/launch the highlighted option on most Android devices. On devices equipped with a trackball or an optical track pad such as G1, G2, Nexus One, HTC Desire etc., the trackball or track pad can be used for navigation and clicking it can be used to enter/launch the selected option. Let’s review each of these options and their sub-menu options in detail.

1. reboot system now
   This one is self-explanatory.
2. apply update from sdcard
   This can be used for installation of any official or unofficial update, ROM, kernel, theme etc. that is in a zip format installable from recovery, as long as the file is named update.zip and it has been placed on the root of your SD card (i.e. not in any sub-folder). Selecting this option (and most of the options featured below) will bring up a rather annoying confirmation prompt but this has saved us on multiple occasions from a lot of trouble we would have been into due to accidental key presses. This is what we are talking about:
   
3. wipe data/factory reset
   This option wipes all user data on the device as well as cache. Doing this will leave your phone in the state it was in when you bought it or when any custom ROM was first installed. It will also wipe any sd-ext partition that you might have setup (more on this later).
4. wipe cache partition
   Wipes the cache partition of the device to clear all the data accumulated there over use. This is often used before installing a new ROM, app, kernel or any similar mod via recovery.
5. install zip from sdcard
   This option brings up the following sub-menu:
    
   1. apply /sdcard/update.zip
      This one is essentially the same as the ‘apply update from sdcard’ option of the main menu.
   2. choose zip from sdcard
      Lets you install any zip file (with any name) from any location on your SD card. The file can be for a ROM, a kernel, an application, a theme or any mod as long as it is in recovery-flashable zip format. This is the most widely used option for installing a ROM that you have downloaded and copied to your SD card. Entering this option will bring up a screen that will allow you to browse your SD card for the zip file and select it for installation as in this screenshot:
      
   3. toggle signature verification
      Turns the signature verification on and off. When signature verification is on, you will not be able to install any custom ROMs that haven’t been signed by the developers (most custom ROMs aren’t signed). Switching it off skips the signature verification check and proceeds with the installation.
   4. toggle script asserts
      Seldom-used option for a vast majority of users. It simply turns script asserts on or off. If you don’t know about these (we don’t), it’s best not to change this option.
   5. +++++Go Back+++++
      Takes you back to the main recovery menu, obviously!
6. backup and restore Undoubtedly one of the most important features provided by a custom recovery, the backup and restore feature – also known as Nandroid backup – allows you to take a snapshot of your phone’s entire internal memory including all partitions, and save it on the SD card. Here is how it looks:
    
   1. Backup
      Takes a Nandroid backup, as explained above.
   2. Restore
      Lets you restore a previously taken backup. Entering this option presents you with a list of existing backups from the SD card that you can choose from for restoration.
   3. Advanced Restore
      This option is similar to the Restore option but once a backup has been selected to be restored, this option allows you to choose what parts of it to restore. You can choose to restore the boot, system, data, cache and sd-ext partitions, as shown here:
      
7. mounts and storage
   Allows you to perform maintenance tasks on all the internal and external partitions of your android device
    
   1. mount/unmount /system, /data, /cache, /sdcard or /sd-ext
      These options let you toggle between mounting or unmounting these respective partitions. Most users don’t need to change these options.
   2. format boot, system, data, cache, sdcard or sd-ext
      These let you directly format any of these partitions. Take extreme care with this option as formatting any of these partitions will result in losing all data on them, especially the boot and system partitions. Formatting the system partition will remove your ROM and leave your phone without an operating system while wiping the boot partition may brick your phone unless you restore or flash another one before rebooting your device. To learn more about the contents of all these partitions, see our guide to Android partitions.
   3. mount USB storage
      Lets you enable USB mass storage mode for your SD card right from recovery so that you can connect it to your computer via USB and transfer any files to/from it without having to leave recovery.
8. advanced
   This section contains a few options most users will not require, though these can come handy quite often, especially wiping Dalvik cache, which is required before most ROM installations. Here are the options from this section:
    
   1. Reboot Recovery
      Lets you directly and very conveniently reboot from recovery right back into recovery. This is useful option for certain back-to-back installations that require the device to at least boot once between them.
   2. Wipe Dalvik Cache
      Allows you to wipe the cache for the Dalvik virtual machine (the custom-built Java virtual machine for Android).This is required before most ROM installations and at other occasions too, for fixing some problems.
   3. Wipe Battery Stats
      Wipes the saved battery usage statistics and effectively recalibrates the battery. Useful in various scenarios when Android isn’t showing correct battery levels.
   4. Report Error
      In case of errors, this feature can be used to save a log of recent ClockworkMod recovery operations on the SD card that you can later report from Android using ROM Manager.
   5. Key Test
      Lets you press any of the hardware keys to see if they are properly functioning, and to see their key codes.
   6. Partition SD Card
      This option gives you a no-frills way to partition your SD card properly for use with ROMs that support data2ext (a very handy hack for low internal memory devices that enables an /sd-ext partition on the SD card to be used as the internal user data storage i.e. as the /data partition). Once this option is selected, you will be given options to choose the sizes for the /sd-ext partition as well as an optional /swap partition on the SD card, and will then automatically format it for you, leaving the remaining space for normal SD card usage. This option will wipe all data from your SD card so use it with caution!
   7. Fix Permissions
      Fixes the file permissions for the internal memory partitions back to default. This is very useful as a fix for several errors and Force-Closes that start appearing after you or an application you installed and provided root access end up messing up the permissions of important files.

Using ClockworkMod for ROM, kernel, apps, theme or mod installation

While in the complete feature tour we have already shown you how to install a ROM, kernel, app, theme or any similar mod from a recovery-flashable zip file using the recovery options, those of you who jumped straight to this section expecting to get just this information quickly are at the right place!
This guide is primary focused on a full feature tour of ClockworkMod recovery but in our previously written guide on how to flash a ROM or app from a zip to an Android device file from recovery, we have already covered in detail how to use ClockworkMod for installing any ROM, kernel, app, theme or mod using a recovery-flashable zip file. While that guide is based on an older version of ClockworkMod recovery, everything in it still applies to the latest versions and should work flawlessly.
That’s all there is to ClockworkMod recovery so far. We hope you enjoy using it as much as we do!