Database Info

[CLOSED][THEME] Stock Triumph Deodex Template[CLOSED]

Thread closed because I no longer own this device. The download links no longer work. Sorry for any inconvenience.

Hey man howd u get the wifi going? And do u mind if i link to this in my post in development for the stock odex and deodex roms? Because i and i know alot of people tend to skip over the theme section
Sent from my PG06100

I don't know what exactly fixed it for sure. I just took the stock system.img from the complete non powered on nandroid backup posted, extracted all the files(using unyaffs.exe) and went through and auto deodexed framework and app using an auto deodexer tool found on xda, then the files taht wouldnt auto deodex using that .bat script, I used the baksmali and smali jar files to manually deodex the rest. I kept geting erros on the DbgCfgTools.apk(but ir ead up on the erros i was gettinmg and some of the htc sense roms were getting erros on some of there files like that and they said to use the -I option when baksmali'ing the odex file and it ignores the errors I guess, but that app was refering to bootclass paths that are no where in any .jar file on the phone so it's likely that apk didnt work in the first place cause if it was called to, it would display the same bootclass errors.
Yeah you can link to this, and I will make a stock deodexed rom that also formats and replaces everything in the /hidden partition(i.e. all the bloatware) as well as a bone stock rom so someone who has messed up the hidden partition can get back to bone stock easily!

Mediafire is down, and I just lost wifi with my phone when installing your bone stock ROM... you know, the one that doesn't have working wifi.
So here I go bumping your thread and adding some mirrors. This thread needs to be stickied or something.

Yes, mirror would be good!
√ HTC Evo 3D GSM
√ Android JB 4.1.2
√ Disarmed Toaster
√ 4EXT Recovery Touch
√ Anthrax Kernel 3.7.0 @ 1.6ghz

[I9003] [How-To] Easily adding Arabic Patch to a Custom Rom

Hey to all,
this is a short tutorial how Devs but also "normal user" can add Arabic Support to a Custom Rom. (This process is usable for other Samsung smartphones, too).
1) Requirements
2) Downloads
3) How to apply Patch...
3.1) ...with Root Explorer
3.2) ...with a .zip Rom
1) Requirements
1. Your device needs to be rooted. (If you use the Root Explorer method)
2. Your Android version is 2.1 or newer
3. Your ROM needs to be deodexed. To find out if your installed ROM is deodexed, navigate to /system/framework on your phone. If you see a file called framework.odex then this patch will NOT work for you.
4. Your rom is NOT based on MIUI.
2) Downloads
1. Arabic Patcher (requires Windows)
2. If you use the Root Explorer method you will need Root Explorer (available in Market) or something comparable
If something goes wrong using this method reply and i´ll help you
Author of this tool is madmack! Link to his homepage

3) HowTo apply the patch
3.1) ...with Root Explorer
1. Download Arabic Patcher and extract it
2. Pull /system/framework/framework.jar from your phone and place it in the subfolder called "input" that you extracted in step 1. If you’re not using a CyanogenMod ROM (like Stock I9003 Roms), then you’ll also need to pull /system/lib/libandroid_runtime.so from your phone and place it in subfolder input that you extracted in step 1
! If you’re interested in getting arabic shaping in the Browser, pull file /system/lib/libwebcore.so from your phone and place it in subfolder input as well !
3. Double click on commands.exe. Do not close the black cmd screens that will pop up. Once the patch is done, you should get a patched framework.jar in the subfolder output.
4. Put file output/framework.jar in your phone at /system/framework/
5. Put file output/libandroid_runtime.so in your phone at /system/lib/
6. Put file output/libicuuc-arabic.so in your phone at /system/lib/ This is extremely important, failing to place this file will result in a boot loop of your deivce
7. If file exists: Place file output/libwebcore.so in your phone at /system/lib/
8. If file exists: Place file output/lib__bcore.so in your phone at /system/lib/
Also included, the Aljazeera fonts in fonts. You can place these in /system/fonts and reboot Sometimes permissions and xml data doesn’t get updated correctly resulting in corrupted data entries. If you receive a bunch of Force Closes after a reboot, you’ll need to Factory Reset.

3) HowTo apply the patch
3.2) ...with a .zip Rom
1. Download Arabic Patcher and extract it
1.1 Download the Rom you want to patch
2. Extract the .zip of your Rom and search for /system/framework/framework.jar. Pull it and place it in the subfolder called "input" that you extracted in step 1. If you’re not using a CyanogenMod ROM (like Stock I9003 Roms), then you’ll also need to pull /system/lib/libandroid_runtime.so from your phone and place it in subfolder input that you extracted in step 1
! If you’re interested in getting arabic shaping in the Browser, pull file /system/lib/libwebcore.so and place it in subfolder input as well !
3. Double click on commands.exe. Do not close the black cmd screens that will pop up. Once the patch is done, you should get a patched framework.jar in the subfolder output.
4. Put file output/framework.jar in .zip at /system/framework/
5. Put file output/libandroid_runtime.so in .zip at /system/lib/
6. Put file output/libicuuc-arabic.so in .zip at /system/lib/ This is extremely important, failing to place this file will result in a boot loop of your deivce
7. If file exists: Place file output/libwebcore.so in .zip at /system/lib/
8. If file exists: Place file output/lib__bcore.so in .zip at /system/lib/
Also included, the Aljazeera fonts in fonts. You can place these in /system/fonts and reboot Sometimes permissions and xml data doesn’t get updated correctly resulting in corrupted data entries. If you receive a bunch of Force Closes after a reboot, you’ll need to Factory Reset.

nice info dude

How about Asian language? Eg. Chinese? Any method to make a patch?
Sent from my GT-I9003 using XDA Premium App

Nice One dude as many are requesting for that...

I'll try it man... but if this works then you are officially my new Hero !!!

Ok it works Fine man you r a genius !!! i used it on Cranium.zip & then i flashed it & it now can read Arabic fonts Properly, but Arabic is not included in the Local settings therefore no Arabic Keyboard...
but i have one more Question though... if i used a theme & replaced Framework.jar file do i have to patch it again ?!

iceman-x9 said:
Ok it works Fine man you r a genius !!! i used it on Cranium.zip & then i flashed it & it now can read Arabic fonts Properly, but Arabic is not included in the Local settings therefore no Arabic Keyboard...
but i have one more Question though... if i used a theme & replaced Framework.jar file do i have to patch it again ?!
Click to expand...
Click to collapse
Yes, you have to apply the path again.
See attachement for an arabic keyboard, install it and then under "language in and output" (or sth like that) aktivate it. (I idon´t tested it, but it should work)
PS: Press thanks button

Thanks fuss132 Nice tutorial it will help a lot

thanx man realy>>ur my hero

thanks fuss.....i had already found this,but the whole page was in arabic and translate sucks

Thanks for the Info

you are my hero
it works like charm

Only works on custom ROM's, meaning I can only use it if i have Cranium or CM7 when they make it right?

Baladya said:
Only works on custom ROM's, meaning I can only use it if i have Cranium or CM7 when they make it right?
Click to expand...
Click to collapse
thats not true i'm using it in XXKPM without any problems

thx... work fine in my xxkpm...

does any one test it on XXKB3 ?

nimafire said:
does any one test it on XXKB3 ?
Click to expand...
Click to collapse
It´s working on Froyo, too.
Only requires Android 2.1+

problem in messages
thanks for the big efforts , but i have problem when sending messages from my i9003 2.3.6 custom rom ,the recipient have squares instead from arabic letters.
could you help please....

[HOW-TO] Re-Odex a ROM

I made a tutorial for other devices here http://forum.xda-developers.com/showthread.php?t=1500475
Why this tutorial?
I wanted a good odexed rom, but there isn't any here. So I tried to make my own odexed rom, but it wasn't so good. So I read something about re-odexing and tried it out. I modified it a little bit and I don't know all about re-odexing, so if someone know something better, pls post it here in the thread for everyone. Im working also on this thread, so I'll try to make few things like a flashable update.zip who executes the script. English is also not my mother language, but I hope you'll understand me
What is a odexed and a deodexed rom?
When you look at a stock rom in the folder /system/app, you will see files with the ending .odex and the apks doesn't contains classes.dex files. When you look at a deodexed rom, you'll see that there are no .odex files and the apks contains classes.dex files. Basically every apk contains a classes.dex files. Then the dalvik virtual machine generates a dalvik cache based of the classes.dex file. When you load a app, it will be loaded from the the dalvik cache, not from the apk. Samsung built the odexed rom using a tool called dexopt-wrapper. This tool generates .odex files based from the classes.dex, that means it does the same job like the dalvik vm. The .odex files were pushed in the /system. The files are the replacement for the dalvik cache. Like I wrote above, apps are loading from the dalvik cache, not from apk or classes.dex file, so classes.dex are not needed anymore, so they are deleted in odexed roms. Deodexing using xUltimate means regenerating a classes.dex based from the .odex file, merging it into the apk and deleting .odex.
What are the advantages and disadvantages from a deodexed rom?
Advantages:
-All needed things are in one apk, so modding/theming is (better) possible
-Needs less space on /system
Disavantages:
-Needs more space on /data, you have on some roms only 110/170 mb free(because a deodexed rom needs a dalvik cache for system apps and frameworks
-Is not so stable than a odexed rom(because some moves dalvik cache to a low end sdext)
-Slower on first boot(because a odexed rom has already execute ready .odex files, a deodexed rom needs to generate dalvik cache)
Why should I re-odex?
I wanted this, because I use ~100 apps and I have a slow sd card, so moving /data/app and /data/dalvik cache to sdext made my system unstables, which was needed to run ~100 apps on a deodexed rom. But when I tried it on a odexed rom, I had only to move /data/app to sdext. So I used long time Stock rooted JPU. But the system was not so fast than on any other custom rom and I hated the stock theme. So If you want more space on /data and you don't want to try out new themes, you should probably try re-odexing.
What do I need to re-odex?
-A full NANDroid Backup
-More than 30 mb free space on /system
-ADB drivers for Option 1
-Titanium Backup Pro for Option 2
How can I re-odex a Rom?
There are 2 Options to do it, but only the first does a full re-odex.
Before doing anything make sure that you have a full NANDroid Backup because you'll propably get into a bootloop.
Option 1 using dexopt-wrapper:
I used first the script from puppet13th, but I got into a bootloop. So I corrected the $BOOTCLASSPATH and corrected permissions, but I got also into a bootloop. I compared the re-odexed Kyrillos Rom v9.3 framework with the framework from JPU. The difference was that Kyrillos Rom v9.3 Framework files android.policy.jar and services.jar doesnt contained the Meta-Inf.
Step 1: Check jars
Pull all your framework .jars using this adb command to your computer
Code:
adb pull /system/framework
and open them in WinRar or sth and check that they contains the Meta-Inf folder. If some file doesnt contain a Meta-Inf folder, I attached all jars from Stock JPU, so you can add the Meta-Inf folder from them. When you are done with adding Meta-Inf Folder to one file, you can push it to the system using this adb command(services.jar is only for example, use your filename):
Code:
adb push services.jar /system/framework
Some users told me that you can re-odex the rom without being in CWM, so you can may skip Step 2, but you could get into a bootloop without Step 2, but you can try it out, there is no risk with a NANDroid backup
Step 2(optional): Reboot your phone into cwm recovery and get adb access there
I never got adb access in windows, but i got always access with linux. If you also don't get access on Linux, you should try to reboot your phone and to select then recovery in the extended power menu, this gaves me always adb access.
Step 3: run reodex script
I attached a script, which push a script and needed binaries over adb to the phone. Then it executes the pushed script, which creates odex files and removes classes.dex from apks or jars and rezipaligns apks and deletes the dalvik cache.
For windows users: double click on odex.cmd
For linux users: open a terminal and navigate to the folder which contains the unzipped attachment and run
Code:
chmod +x reodex.sh
./reodex.sh
After its finished, simply reboot and enjoy your fully re-odexed rom.
Step 4 (optional) convert /data:
I dont know if there is a better option, but after a re-odex with Option 1, my phone didnt showed the right free space on /data. So I converted /data to a other filesystem and back and then it showed the right free space.
Option 2 using Titanium Backup Pro:
You need to have Titanium Backup pro for re-odexing.
Step 1:
Select Menu -> More -> integrate sys dalvik into rom and wait until its finished. Then you should have more space on /data. I had when I tried it before 105 and after 135 mb free space on /data and 0kb free space after it on /system, so its not all.
You can also undo it. Its good when you want to try out a new theme, so you can undo and redo it using TB Pro.
Simply select Menu -> More -> Undo sys dalvik integration
and you're done.
Option 1 vs. Option 2
-Option 1 does a full re-odex, you have full free space on /data(Option 2 does only re-odex the apps, not the framework)
-Option 1 deletes classes.dex from apks and jars(against Option 2), so you have more space free on /system
-You can undo Option 2 fast, so theming/modding is also possible by undo, theme and redo it(against Option 1)
For other Phones:
If someone has a other phone, theres a chance for getting re-odex working, but I think that you should not hope that it works. You can try to put in the right $BOOTCLASSPATH. You can find the valid $BOOTCLASSPATH in /init.rc. Then replace the following characters with the $BOOTCLASSPATH in the script in the folder odex(beginning from Line 8):
Code:
BOOTCLASSPATH=replace_this_with_your_bootclasspath
cd /system/framework
for filename replace_this_with_your_bootclasspath
In the line
Code:
for filename replace_this_with_your_bootclasspath
you must replace the ":" character between framework files with a space.
For theme developers:
I dont know if it works that you use the re-odexed theme on a stock odexed theme. If it is so, you dont have to re-odex and deodex your phone, you can simply push the dexopt-wrapper binary to a folder, chmod 755 it and use it to make odex files from the needed apks and jars(all apks inside /system/framework has no odex files, so dont odex them) like this:
Code:
dexopt-wrapper /system/app/Phone.apk /mnt/sdcard/Phone.odex /system/framework/core.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/android.policy.jar:/system/framework/services.jar
You can change argument 1-2, but not argument 3(its the BOOTCLASSPATH)Then you could copy all needed main apks or jars to sdcard and remove classes.dex. Then only do Step 1 from Option 1 and you should have a theme for odexed rom.
Download Links
XDA gaves me only 500 Errors when uploading was done, so I uploaded it to min.us
Framework jars from JPU
Re-Odex Script for Windows
Re-Odex Script for Linux
Credits
puppet13th for making orginal script
If I helped you, dont be shy, just press the Thanks Button under this post.

www.kingsrom.com/f8-how-to-theme-guideslinkstutorials

Oh year I didnt see any tutorial before, but his is only for Froyo sense or Gingerbread aosp, so it wont work on galaxy 3 and I also wrote my tutorial so that noobs can understand it(I hope so).
I could also post a system.img of a re-odexed Kyrillos Rom v9.3 and other Roms, but I dont know if Im allowed to do that.

TearsDontFalls said:
Oh year I didnt see any tutorial before, but his is only for Froyo sense or Gingerbread aosp, so it wont work on galaxy 3 and I also wrote my tutorial so that noobs can understand it(I hope so).
I could also post a system.img of a re-odexed Kyrillos Rom v9.3 and other Roms, but I dont know if Im allowed to do that.
Click to expand...
Click to collapse
So the re-odexed kyrillos rom v9.3 is working faster than the original kyrillos rom v9.3??

Its not generally faster, but much faster for me because I have ~100 apps and when I run these apps on kyrillos v9.3 deodexed, i must move app and dalvik-cache to sdext which made my phone laggy. With a odexed kyrillos v9.3, i have much more space free on /data, so i only must move app to sdext which is much.
I wrote also the advantages and disadvantages from a deodexed and odexed rom in my tutorial.

TearsDontFalls said:
Its not generally faster, but much faster for me because I have ~100 apps and when I run these apps on kyrillos v9.3 deodexed, i must move app and dalvik-cache to sdext which made my phone laggy. With a odexed kyrillos v9.3, i have much more space free on /data, so i only must move app to sdext which is much.
I wrote also the advantages and disadvantages from a deodexed and odexed rom in my tutorial.
Click to expand...
Click to collapse
So, in a re-odexed rom the HD2SD is not working ?
You use again froyo data2SD ?

dante_100 said:
So, in a re-odexed rom the HD2SD is not working ?
You use again froyo data2SD ?
Click to expand...
Click to collapse
As far as I understand, it works but only for data/app.
correct me if I'm wrong

Sorry, my english is not the yellow from the egg(you must not understand this).
Im using on my re-odexed rom also Hybrid Data 2 SD, I can move also move /data/dalvik-cache and any other folder to sdext, its only not needed, because I had after the re-odexing much more free space on /data, so I did moved dalvik cache back to the NAND from the sdext, before re-odexing I moved dalvik cache to sdext, becaue it was needed for running ~100 apps.
short form:Only Theming is impossible with a re-odexed rom
Hope you'll understand this now.
Edit: Can someone help me for creating a update.zip for re-odexing. It must only copy the dir odex to /data/local/tmp/odex , chmod 755 them all and execute the shell script /data/local/tmp/odex/odex

Sooo
if i get ADB access using windows i can skip step 2 in option1 right?

chandradithya said:
Sooo
if i get ADB access using windows i can skip step 2 in option1 right?
Click to expand...
Click to collapse
No. You need to reboot in cwm and try to get adb access from there. Windows adb in recovery never worked for me, you need linux to get adb access from cwm mode
Sent from my i9003 powered by Poseidon's Rom + UC kernel

Right, I tried to make a update.zip which execute the script, but i had no success, it would be great if somebody can help me.

bscraze said:
No. You need to reboot in cwm and try to get adb access from there. Windows adb in recovery never worked for me, you need linux to get adb access from cwm mode
Sent from my i9003 powered by Poseidon's Rom + UC kernel
Click to expand...
Click to collapse
ADB actually works for me, just ran cmd.exe using admin privileges and i ran the odex script it worked, odexed ALL my system files, cleared my /data/dalvik-cache/
But like TearsDontFalls said it doesn't show the free memory correctly,
Im running g3mod and im yet to try the option4 that asks you to switch file systems
And the /g3mod.log says,
st17: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY
While the other partitions are all clean,

How did you got adb access in windows? Sure you was in cwm recovery while re-odexing?

Finally, someone post a guide on this. And it works! Though titanium backup never worked for me. And is it necessary to run the script on cmw? Cause I didn't done it on cmw.
Sent from my GT-I5800 using XDA App

I didn't expect that it works on a running system, but it can be so, so I'll update the guide after Christmas.

TearsDontFalls said:
How did you got adb access in windows? Sure you was in cwm recovery while re-odexing?
Click to expand...
Click to collapse
It worked perfectly for me,
I tried going to the G3 kernels recovery, ADB just wouldnt connect,
so i turned it on, Ran the script when it was in standby mode , then it gave an error at first,
Which i rectified by making the /system read or write using root explorer,
I think i ran the script using admin privileges.
Dont remember..
And g3mod.log showed me this
Code:
Checking mmcblk0p2
/dev/block/mmcblk0p2: clean, 11/125488 files, 15840/500173 blocks
Checking stl6
/dev/block/stl6: clean, 1302/13600 files, 46914/54400 blocks
Checking stl7
/dev/block/stl7 contains a file system with errors, check forced.
/dev/block/stl7: Inodes that were part of a corrupted orphan linked list found.
/dev/block/stl7: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
(i.e., without -a or -p options)
Checking stl8
/dev/block/stl8: clean, 12/2176 files, 143/8704 blocks
Data2SD Disabled
Multi-OS Data Disabled
System detected: FROYO
System booted with Samsung Froyo kernel mode
Compcache disabled
No problems right now, But cant stop wondering why it says it is inconsistent.

I don't know why it is so, but it also doesn't show the right free space, so convert it to a other file system and then convert it back.

UNBELIEVABLE!
Finally, the first method worked for me.
Working great on HTC Amaze 4G
Thanks

heyjoe66 said:
UNBELIEVABLE!
Finally, the first method worked for me.
Working great on HTC Amaze 4G
Thanks
Click to expand...
Click to collapse
Thanks for your report. So it seems to be working on other devices, so I'll create a thread in android development.

Thanks works on sense 3.5, but I had to change Bootclasspath from the boot.img and add missing files below in odex script.
great guide
edit: now searching on how to re odex a single file.

[GUIDE] Full support for Arabic and Hebrew

Hi, everybody
i've tryed a lot of ROMs and right now only Kyrillos's rom supports Arabic and Hebrew as it should be,
so there are two solutions:
1- install CM
PersianSphinx said:
And its not all CM ROMs that have this. CM7 has it for sure. Ginger bread has it enabled for sure. ive even checked other androids.
Click to expand...
Click to collapse
2- patch the rom
i will be guiding only the second solution but first
i am not to be credited for any of the work it is all the work of:
Madmack and Brighidea
i dont know the real names
so
step 1:
download the latest version of the patcher from madmack's blog from here
step 2:
extract these three files from the rom:
1- /system/framework/framework.jar
2- /system/lib/libandroid_runtime.so
3- /system/lib/libwebcore.so
step 3:
copy these files in the input folder of the patcher, and run commands.exe as administrator ( dont close any screen that appears )
step 4:
get a file named flashable_framework.zip from the output folder,
in normal conditions we would flash it through cwm but for a reason it doesnt it gives you an error
so put each of the files in the zip in its correspondent folder in the system manually.
framework.jar in /system/framework/
lib__bcore.so , libandroid_runtime.so , libicuuc-arabic.so , libwebcore.so in /system/lib/
DroidSansArabic.ttf in /system/fonts/
step 5:
must wipe dalvik-cache,
and if it wont boot wipe data,
if it still wont boot either you didnt follow the steps correctly or there is something wrong and you must contact madmack through his blog
step 6: that's it
again i am not taking credit at all. all i did is that i sent some files to madmack and he did all the job that was from a couple of months
credits:
madmack
brightidea

synos_x said:
in normal conditions we would flash it through cwm but for a reason it doesnt it gives you an error
so put each of the files in the zip in its correspondent folder in the system manually.
credits:
madmack
brightidea
Click to expand...
Click to collapse
good guide. useful for me, now i can see all my persian songs on any froyo/eclair
give a third way to activate, Kyrillos' ROM has Arabic/Persian/Hebrew activated on version 9 and 10 of his ROM by default. And its not all CM ROMs that have this. CM7 has it for sure. Ginger bread has it enabled for sure. ive even checked other androids.

PersianSphinx said:
good guide. useful for me, now i can see all my persian songs on any froyo/eclair
give a third way to activate, Kyrillos' ROM has Arabic/Persian/Hebrew activated on version 9 and 10 of his ROM by default. And its not all CM ROMs that have this. CM7 has it for sure. Ginger bread has it enabled for sure. ive even checked other androids.
Click to expand...
Click to collapse
thank you for that it was encouraging, i will quote some of what you said, in first post, i dont know about Persian but i think Kyrillos used this patch for Arabic, may be.

synos_x said:
thank you for that it was encouraging, i will quote some of what you said, in first post, i dont know about Persian but i think Kyrillos used this patch for Arabic, may be.
Click to expand...
Click to collapse
I know this because i suggested it to him to do it mate
Persian is similar to Arabic in the alphabet, but we have 4 letters that arabs dont have: گ، چ، پ، ژ
also the layout of the keyboard is different and we dont have the weird ه with the dots above it in our language that is most of the difference... Oh yea, and we dont use the vowels at all in writing... only ا، ه، آ، و، ی and none of the hamza crap

[Q] Structure of .deodex files

Hi,
Since non of links in the Team Lamber Corrosion does works (only main download link), I would like to know, what is structure of .deodex files used in your program.
I've got stock JPU right now, and I would like to deodex it using Team Lambert app.
I got a little concept - it's .zip file inside of wich are deodexed .apk without .odex files, and then the name is changed to .deodex
PROGRAM LINK: http://forum.xda-developers.com/showthread.php?t=1161176

I have deodexed the XXJPU by myself with xUltimate
takes a lot of time
why dont you save your time and use an already deodexed XXJPU ROM?
-> http://forum.xda-developers.com/showpost.php?p=18894408&postcount=78
Install the deodexed ROM and use UOT Kitchen for pimping.
Cheers
qaysed

Well, it says "Wrong sim card", common error with JPU modifications,
doesn't appear in stock JPU.
And as far as i know, it only appears with my operator (never seen someone's post about similar bug)
Well, if you have flashed it with xUltimate, maybe you know the answer to my friends topic (we are both trying to deodex our phones, we both have G3)
http://forum.xda-developers.com/showthread.php?t=1376985

it´s late right now, checking sekhargreen´s commands... on the first sight.. great, but not checked in detail
I have found a script in a german forum which was concepted for i9000, I just took it and modded it for G3 needs.
heres the link for the complete update*.zip which I used for deodexing my XXJPU.
http://www.mediafire.com/?6h5u6157yh402nf
Well...
1. install stock xxjpu
2. install G3 Mod kernel (to use CWM)
I have installed G3mod Kernel 2.3 NON OC
-boot into cwm
-update zip
-choose update file )or something like that, not only update.zip)
toggle for it, agreem, wait for copying the files
have fun!
or take the easy way and use the already deodexed ROM, link given above...
the deodexed ROM above is already rooted... very comfortable way
The choice is up to you both.
Cheers
qaysed

qaysedcftgb said:
i-boot into cwm
-update zip
-choose update file )or something like that, not only update.zip)
toggle for it, agreem, wait for copying the files
Click to expand...
Click to collapse
Could you please explain more about above?

to use CWM (clockworkmod) you need a kernel which supports cwm
->I have G3Mod Kernel running
http://forum.xda-developers.com/showthread.php?t=1252698
The way is described in the first posting:
3.2) Select .zip from sdcard
Stock kernel doesnt have CWM.
Just flash the non OC kernel and you have cwm without overclocking. Runs like stock kernel.