Database Info

(i9003)For bsnl/mtnl user having airplane bug (cm7)

for al of you stuck on airplane mode while using bsnl/mtnl sim here is the solution:
(1st method )-
first download teminal from android market
than open terminal and type :
su
su
sqlite3 /data/data/com.android.providers.settings/databases/settings.db
delete from system where name = 'airplane_mode_on';
.exit
exit
reboot
(2 method) -
download sqlite manager , root explorer
using root explorer goto /data/data/com.android.providers.settings/databases and copy settings.db , paste in sdcard root.
now open this settings.db file in sqlite editor and delete this row :- 'airplane_mode_on'
now copy this file from sdcard root and paste it in
/data/data/com.android.providers.settings/databases
now set appropriate permissions on the file file settings.db otherwise you will be boot loop struck
now reboot .....
(method 3)-
copy attached settings.db file below to goto /data/data/com.android.providers.settings/databases
set appropriate permisions
& reboot
well u r done
hope this fixes ur problem.......
required files are attached below......

to set permisions long press the file for options click on permission n set appropriate permissions

thats good buddy.

This sounds similar to http://forum.xda-developers.com/showthread.php?t=1408472#post20910541

sorry bro i din saw it!!!!!

vishal24387 said:
thats good buddy.
Click to expand...
Click to collapse
thanks dude....

Awesome Thread !!!!!
Would this also work on ICS ROMs for I9000 ?
Been facing the same issue on every other custom ICS ROMs..
Would appreciate any help ......

Why dont you do a nandroid backup and give it a try?

[UTIL][22/2/13]Auto Odexer Script V2.1-Mod your odex files with a breeze

NEW VERSION 2.1, it is now much easier and like a breeze...
Before u read, u should know that this thread is for themers and modders only... and this is not a tool for odexing the whole ROM.
Hello everybody
While I was working on my ROM, and releasing an odex version, I suffered alot in working on the odex files and modifying them. Every time I should use the command line and copy certain commands from a notepad, in addition I have to edit the notepad file to make the commands odex other files... that was a pain...
ok.. the odex commands that were used are taken from this thread by sicopat, big thanks to his efforts. Actually I was thinking in how to make it easier for me to odex these modified files, so I tried to make a script that easily odex files, put the files in the right folder, run the script, and then write the name of the file u want to odex, then..... Waw the file is odexed in the phone and ready to run
For anyone that want to use these scripts, I wanted to share it with you, and I hope they would be useful to you.
Update (2/22/13) v2.1:
1. bootclasspath should be put manually from now, because $BOOTCLASSPATH doesn't work when no root in recovery.
2. Fixed a mistake in extracting and archiving files, now it's ok.
3. Now you can restore the original files if you like after odexing.
4. 7zip 32 bit is used instead of 64 bit, sorry for this, now it should work with 32 bit windows too.
5. Script re-arranged, and 7zip log operations saved in 7z_log.txt. you can check this one if you suspect in 7zip operation.
6. Backup of the original files before odexing and restore them after odexing.
Update (1/4/13) v2: All things automated, no need to edit the script for bootclasspath, and even no need to drag and drop the edited files from the modded apk or jar.
Update (9/20/12) v1.4: remount using busybox, this solves some remounting problems.
update (9/18/12) v1.3: adb added to the program, to make it work independently. And now you can pull the files after odexing if u need that.
update (9/10/12) v1.2: updated and added a missed command, it should works perfect. No need to put any files in your sdcard to make the operations... and the operations are commented so you can diagnose the problem if occurred.
download from here
Before you use, make sure u r running the corresponding odex rom in your device, then read how to use this tool.
How to use:
first extract the downloaded file to a folder then:
1. Put your bootclasspath in bootclasspath.txt (follow the instruction below in Important Note 2).
2. Put the original odex and apk (or jar) file in the "original" folder.
3. Put your modded deodexed apk (or jar) file in the "mod" folder
4. Connect your phone with usb and make sure adb is working. ( and don't forget to check the USB Debugging in the settings of your device).
5. It is better that you boot in recovery mod, specially when odexing framework files.
6. Now run the script (.bat file), choose the one for apk or for the jar, according to file you want to odex.
7. after the script opens, write the name of the apk (or jar) file without the .apk (or .jar)
8. Odexing......done.
9. after finishing odexing, u can pull the odexed apk or jar file by pressing 1 then Enter, the it will be pulled in the (pulled_files) folder. Or if you want to restore the original apk (or jar) file with its odex, then press 2.
If you find this thread useful, pressing the thanks button is appreciated.
Important note: If you r using a rooted stock kernel, then u could face problem in remounting, hence a problem in the script. To solve this problem check this post.
Important note 2:To get Your BOOTCLASSPATH:
1. In adb:
adb devices
adb remount
adb shell echo $BOOTCLASSPATH
after that, you can right click and choose (mark), then mark the bootclasspath then press (enter) now you have copied the bootclasspath. go to bootclasspath.txt in the extracted folder of the script, then paste the bootclasspath and save the file.
OR
2. In the root of your device, in the init.rc file:
look for a line with (bootclasspath= ), then copy everything on the right hand of the equal mark. Go to bootclasspath.txt then paste it there, then save the file.
screenshot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Credit:
Sicopat- for his guide on odexing.
M_j_Nazari- for his guide on odexing and his written commands for the odexing operation. thread link

I keep getting this error when trying to use your script. Help please?
Code:
remounting
'adb' is not recognized as an internal or external command,
operable program or batch file.

daveyannihilation said:
I keep getting this error when trying to use your script. Help please?
Code:
remounting
'adb' is not recognized as an internal or external command,
operable program or batch file.
Click to expand...
Click to collapse
This happened cuz u didn't add the adb directory to the system variables...
Anyway I updated it and it should work now without doing that...please try it and give me a feedback..

alkhafaf said:
This happened cuz u didn't add the adb directory to the system variables...
Anyway I updated it and it should work now without doing that...please try it and give me a feedback..
Click to expand...
Click to collapse
Ok mate. I'll download it and try it when I get home. Just for future reference though, how do I add the ADB directory to system variables??

daveyannihilation said:
Ok mate. I'll download it and try it when I get home. Just for future reference though, how do I add the ADB directory to system variables??
Click to expand...
Click to collapse
Go to my computer,then properties, in advanced there is Environment Variables, press it .. then in system variables add the (path) and write the directory that leads to the adb that u have when u installed android development tools ( it should be in platform-tools folder).
Try odexer first before doing that I can not try it cuz I don't know who to delete the adb from the system variables
Sent from tapatalk using sgs i9000
[ROM][GB][JW8] MesoROM v2.0 8/27/2012 Ultra Light-Smooth-Beauty
Google+

alkhafaf said:
Go to my computer,then properties, in advanced there is Environment Variables, press it .. then in system variables add the (path) and write the directory that leads to the adb that u have when u installed android development tools ( it should be in platform-tools folder).
Try odexer first before doing that I can not try it cuz I don't know who to delete the adb from the system variables
Sent from tapatalk using sgs i9000
[ROM][GB][JW8] MesoROM v2.0 8/27/2012 Ultra Light-Smooth-Beauty
Google+
Click to expand...
Click to collapse
Will do when I get home from work mate. So in about 6 hours. But who's counting?

daveyannihilation said:
Will do when I get home from work mate. So in about 6 hours. But who's counting?
Click to expand...
Click to collapse
Lol.. of course not.. cuz I will sleep now... its 6 am here and didn't sleep yet... and you r living the new day
Sent from tapatalk using sgs i9000
[ROM][GB][JW8] MesoROM v2.0 8/27/2012 Ultra Light-Smooth-Beauty
Google+

alkhafaf said:
Lol.. of course not.. cuz I will sleep now... its 6 am here and didn't sleep yet... and you r living the new day
Sent from tapatalk using sgs i9000
[ROM][GB][JW8] MesoROM v2.0 8/27/2012 Ultra Light-Smooth-Beauty
Google+
Click to expand...
Click to collapse
Ok I tried it and it didn't work properly.
Code:
remounting
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
0019295d0b1c9e device
remount failed: Operation not permitted
Enter the name of the .apk file u want to odex (without .apk): Mms
sending dexopt-wrapper to the device
failed to copy 'dexopt-wrapper' to '/system/bin/dexopt-wrapper': Read-only file
system
Unable to chmod /system/bin/dexopt-wrapper: Read-only file system
sending the deodexed file to the device
failed to copy 'mod\Mms.apk' to '/system/app/Mms.apk': Read-only file system
Odexing the file:
Unable to create '/system/app/new_Mms.odex': Read-only file system
No error found
pushing the original files to the system
failed to copy 'original\Mms.apk' to '/system/app/Mms.apk': Read-only file syste
m
failed to copy 'original\Mms.odex' to '/system/app/Mms.odex': Read-only file sys
tem
Setting permissions..
Unable to chmod /system/app/Mms.odex: Read-only file system
Unable to chmod /system/app/Mms.apk: Read-only file system
Unable to chmod /system/app/new_Mms.odex: No such file or directory
copying signature from original file:
/system/bin/sh: busybox: cannot execute - Permission denied
replacing with the new odex file
/system/bin/sh: cp: not found
settings permissions for the new odex file
Unable to chmod /system/app/Mms.odex: Read-only file system
Unable to chmod /system/app/Mms.odex: Read-only file system
deleting worked- on file
rm failed for /system/app/new_Mms.odex, No such file or directory
Finished
To odex a file again, press any key
To pull the apk file, press 1
To exit, press 0
That's the error I keep getting. What does it mean? Am I doing something wrong?

daveyannihilation said:
Ok I tried it and it didn't work properly.
Code:
remounting
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
0019295d0b1c9e device
remount failed: Operation not permitted
Enter the name of the .apk file u want to odex (without .apk): Mms
sending dexopt-wrapper to the device
failed to copy 'dexopt-wrapper' to '/system/bin/dexopt-wrapper': Read-only file
system
Unable to chmod /system/bin/dexopt-wrapper: Read-only file system
sending the deodexed file to the device
failed to copy 'mod\Mms.apk' to '/system/app/Mms.apk': Read-only file system
Odexing the file:
Unable to create '/system/app/new_Mms.odex': Read-only file system
No error found
pushing the original files to the system
failed to copy 'original\Mms.apk' to '/system/app/Mms.apk': Read-only file syste
m
failed to copy 'original\Mms.odex' to '/system/app/Mms.odex': Read-only file sys
tem
Setting permissions..
Unable to chmod /system/app/Mms.odex: Read-only file system
Unable to chmod /system/app/Mms.apk: Read-only file system
Unable to chmod /system/app/new_Mms.odex: No such file or directory
copying signature from original file:
/system/bin/sh: busybox: cannot execute - Permission denied
replacing with the new odex file
/system/bin/sh: cp: not found
settings permissions for the new odex file
Unable to chmod /system/app/Mms.odex: Read-only file system
Unable to chmod /system/app/Mms.odex: Read-only file system
deleting worked- on file
rm failed for /system/app/new_Mms.odex, No such file or directory
Finished
To odex a file again, press any key
To pull the apk file, press 1
To exit, press 0
That's the error I keep getting. What does it mean? Am I doing something wrong?
Click to expand...
Click to collapse
That's because your system isn't being set to read write. And it looks like your using an old adb
Sent from my Sensation

blahbl4hblah said:
That's because your system isn't being set to read write. And it looks like your using an old adb
Sent from my Sensation
Click to expand...
Click to collapse
Ok then. Is there a way of setting my file system to read write? And do I just need to update the SDK via Eclipse to get a newer version of adb??

daveyannihilation said:
Ok then. Is there a way of setting my file system to read write? And do I just need to update the SDK via Eclipse to get a newer version of adb??
Click to expand...
Click to collapse
You need to mount it as read write.
Ask the OP to fix the script since he made it
Sent from my Sensation

Did u boot into recovery while doing this operation ?
Sent from tapatalk using sgs i9000
[ROM][GB][JW8] MesoROM v2.0 8/27/2012 Ultra Light-Smooth-Beauty
Google+

alkhafaf said:
Did u boot into recovery while doing this operation ?
Sent from tapatalk using sgs i9000
[ROM][GB][JW8] MesoROM v2.0 8/27/2012 Ultra Light-Smooth-Beauty
Google+
Click to expand...
Click to collapse
No I didn't. Do I just need to be on the main screen of ClockWorkMod recovery? And do I put it into recovery before I plug it into the USB cable or half way through the process?

alkhafaf said:
Did u boot into recovery while doing this operation ?
Sent from tapatalk using sgs i9000
[ROM][GB][JW8] MesoROM v2.0 8/27/2012 Ultra Light-Smooth-Beauty
Google+
Click to expand...
Click to collapse
You don't need to go into recovery to do this.
Just make the script to mount system as a rw
Sent from my Sensation

blahbl4hblah said:
You don't need to go into recovery to do this.
Just make the script to mount system as a rw.
Sent from my Sensation
Click to expand...
Click to collapse
But the script already include that (adb remount)
I think the problem is in the adb itself.. I put the adb with two files with it related to it for the script to use... r these the only files related to adb? Cuz I can not test it as i can not delete the adb from the system variables.
Sent from tapatalk using sgs i9000
[ROM][GB][JW8] MesoROM v2.0 8/27/2012 Ultra Light-Smooth-Beauty
Google+

alkhafaf said:
But the script already include that (adb remount)
I think the problem is in the adb itself.. I put the adb with two files with it related to it for the script to use... r these the only files related to adb? Cuz I can not test it as i can not delete the adb from the system variables.
Sent from tapatalk using sgs i9000
[ROM][GB][JW8] MesoROM v2.0 8/27/2012 Ultra Light-Smooth-Beauty
Google+
Click to expand...
Click to collapse
Well my advice is to test this completely before releasing an update

blahbl4hblah said:
Well my advice is to test this completely before releasing an update
Click to expand...
Click to collapse
It should work for anyone who added the adb path to the system variables...I really tested it and works fine.
The only thing that I didn't test is how the script run independently (using the adb which comes with it without using the adb of the platform-tools by adding its path to the system variables )
Sent from tapatalk using sgs i9000
[ROM][GB][JW8] MesoROM v2.0 8/27/2012 Ultra Light-Smooth-Beauty
Google+

daveyannihilation said:
No I didn't. Do I just need to be on the main screen of ClockWorkMod recovery? And do I put it into recovery before I plug it into the USB cable or half way through the process?
Click to expand...
Click to collapse
Bro. Did u add the adb path to the system variables and tried ?
If u want the instructions Google it and u will probably find it.
Sent from tapatalk using sgs i9000
[ROM][GB][JW8] MesoROM v2.0 8/27/2012 Ultra Light-Smooth-Beauty
Google+

alkhafaf said:
Bro. Did u add the adb path to the system variables and tried ?
If u want the instructions Google it and u will probably find it.
Sent from tapatalk using sgs i9000
[ROM][GB][JW8] MesoROM v2.0 8/27/2012 Ultra Light-Smooth-Beauty
Google+
Click to expand...
Click to collapse
No mate I didn't because you asked me not to so that I could test how it works independently for you. You gave me the instructions in a previous post in this thread.
If that's the only way that I can get it to work (by adding it to the system variables) then I will just have to do that. I don't mind testing it for you, but it's up to you.
Let me know what you would like me to do.

daveyannihilation said:
No mate I didn't because you asked me not to so that I could test how it works independently for you. You gave me the instructions in a previous post in this thread.
If that's the only way that I can get it to work (by adding it to the system variables) then I will just have to do that. I don't mind testing it for you, but it's up to you.
Let me know what you would like me to do.
Click to expand...
Click to collapse
I really appreciate yhat , thanks alot..
But u can try to to add The adb to the system variables, maybe the problem is not with the adb..
If it works for u then please give me a feedback about it
Sent from tapatalk using sgs i9000
[ROM][GB][JW8] MesoROM v2.0 8/27/2012 Ultra Light-Smooth-Beauty
Google+

[GUIDE]DEODEX stock ROM !!!!

what is deodexing :
SilverZero said:
Deodexed ROMs have their .apk's (which are basically the application packages) repackaged in a certain way. An "odex" can be thought of as a collection of parts of applications that have been pulled out and optimized before booting. This speeds up the boot process - in a way, it preloads part of the applications - but it also makes hacking those apps difficult because part of the original code is already extracted somewhere else.
Deodexing is just a process of putting those pieces back into the original applications. It takes a while to extract those parts and build the .dex cache (aka Dalvik cache), but only because the relevant parts aren't in an easy-to-access place for the system. The advantage of this is that an app can be modified effectively and the developer doesn't have to worry about conflicts from the separate odex part of the code.
So, short version: "Deodexed" ROMs have all their apps put back together. If an app can be themed, for example, a deodexed version of that app will not get messed up when the modified .apk tries to mesh with the odex of the original un-modified .apk. Because it's not there.
If you want an aftermarket theme, you need a deodexed ROM. I'm not sure if deodexing can be done to individual apps within a non-deodexed ROM.
I think that's the general idea, anyway.
Click to expand...
Click to collapse
STEPS :
*Go HERE root tour device .
*Download Busybox installer and install the latest version of busybox compatible with your device.
*Install ADB :
In your android device, go to settings --> applications --> development -->
Check USB Debugging
Make sure your device driver is already installed otherwise install kies software which will install drivers too.. Get kies from This LINK
You need to download this ADB.zip file i made to your system.. Download link
Extract the ADB.zip file from any applications like IZarc/7Zip/winzip/winrar.
credits : DEADLY
*Download Xultimate.
*Connect your phone to computer.(Make sure you have select USB debugging in Settings>Applications>Development)
*Extract xUltimate v2.3.3.zip and Launch Main.exe
*If everything goes well xUltimate should recognize the phone and make a connection.You now should see a list of options.
*Select option (1) pull /system/app. Wait until it complete.
*Select option (2)pull /system/framework. Wait until it complete.
*Then select option (3) Deodex /system/app. Wait until it complete.
[If encounter any error. Find out which .odex file is it. Then remove .odex file from folder origi_app in xUltimate folder]
*Then select option (4)Deodex /system/framework. Wait until it complete.
*Now Exit from xUltimate.
*Put the phone in USB mass storage.
*Go to xUltimate folder and copy "done_frame", and "done_app", and move them to the root of the sdcard.
*Now get out from USB storage mode.
*Open Command prompt.
( Goto folder where android sdk installed. Then goto platform-tools folder in it. Right click on free space in folder while pressing shift key.Select open command prompt here.
Now enter commands. )
*Enter following codes.
(if you are using adb shell in su for the first time, keep phone screen on. After entering "su" code, super user request prompt in phone. Press allow )
Code:
adb shell
su
stop
mount -o rw,remount /system/ /system/
cp /sdcard/done_app/* /system/app/
rm /system/app/*.odex
cp /sdcard/done_frame/* /system/framework/
rm /system/framework/*.odex
mount -o ro,remount /system/ /system/
reboot
*Enjoy your DEODEXED rom ! also thank : chamatht (for i learnt this from him ).
Troubleshooting :
srt99 said:
for those who are having troubles with option (3),
exit Xultimate, go to task manager and find process adb.exe, select it and click on end process!
that's it, now run xultimate and run option (3) [no need to run option 1 and 2 again]
Click to expand...
Click to collapse
____________________________________
thoughtfully scribbled by nikufellow

Hi! Thanks for the Guide!
I don't know if I am doing something wrong, but I can't make it work. Every .odex file give me a error, so delete every odex will not help, I guess. Have you or anyone tested this guide with our firmware? (original 2.3.6, Only root).
I was trying to deodex, so I could make some little changes (like battery icon) without flash another rom.

battery icon is working for me but the rest not.... I'm using Rom toolbox
Sent from my GT-I9070 using xda app-developers app

johnnybr said:
Hi! Thanks for the Guide!
I don't know if I am doing something wrong, but I can't make it work. Every .odex file give me a error, so delete every odex will not help, I guess. Have you or anyone tested this guide with our firmware? (original 2.3.6, Only root).
I was trying to deodex, so I could make some little changes (like battery icon) without flash another rom.
Click to expand...
Click to collapse
You need xUltimate v2.3.3 only
I do not respond to tech support via PM

Battery icon works on odexed stock rom. I try this method tonight
GT-I9070P®land

Just done deodexing a stock jb rom for i747 through kitchen, then I read this post. Awesome job, man. :good:

At first this method works,
later after i reflash rom, rooted and do this again,
i get bootloop, any idea?
I tried 5 times and everytime bootloop

But why use the stop command ? Doesn't that stop Android itself entirely ?
I give up writing anymore signatures.

hey bro why this method shows error of insufficient space...
can you help me in dis...
i m having samsung galaxy fit running on 2.3.6 ddkt3

Why i cant!? Heeeelp please!!

for those who are having troubles with option (3),
exit Xultimate, go to task manager and find process adb.exe, select it and click on end process!
that's it, now run xultimate and run option (3) [no need to run option 1 and 2 again]

srt99 said:
for those who are having troubles with option (3),
exit Xultimate, go to task manager and find process adb.exe, select it and click on end process!
that's it, now run xultimate and run option (3) [no need to run option 1 and 2 again]
Click to expand...
Click to collapse
Thanks for the info added to first post
____________________________________
thoughtfully scribbled by nikufellow

I am able to pull app and framework but i'm not able to deodex them I get errors for each file...
adb.exe is not running so that's not the problem
edit: I own a Samsung Galaxy R (i9103)

ROKronoS said:
I am able to pull app and framework but i'm not able to deodex them I get errors for each file...
adb.exe is not running so that's not the problem
edit: I own a Samsung Galaxy R (i9103)
Click to expand...
Click to collapse
This is for I9070, you only can get bootloop if you use this.

Somebody gave me this link in the R section
Thanks anyway

Me too
ROKronoS said:
I am able to pull app and framework but i'm not able to deodex them I get errors for each file...
adb.exe is not running so that's not the problem
Click to expand...
Click to collapse
And now?
S Advance I9070

Do this has chances to brick my device if i do it wrong?
Sent from my GT-I9070 using xda app-developers app

Одг: [GUIDE]DEODEX stock ROM !!!!
AnMotass said:
Do this has chances to brick my device if i do it wrong?
Sent from my GT-I9070 using xda app-developers app
Click to expand...
Click to collapse
If there is any possibility to brick, it would be soft brick, that you can repair by flashing firmware with Odin.
Sent from Galaxy S Advance

ive got the error message for every app too. deleted many odex files. but it wouldn´t getting better. adb not running in taskmanager.
Starting BluetoothAvrcp.odex
*****************************************
* Deodexing... *
UNEXPECTED TOP-LEVEL EXCEPTION:
org.jf.dexlib.Util.ExceptionWithContext: Unknown opcode: f1
at org.jf.dexlib.Util.ExceptionWithContext.withContext(Exception
ext.java:54)
at org.jf.dexlib.Code.InstructionIterator.IterateInstructions(In
nIterator.java:87)
at org.jf.dexlib.CodeItem.readItem(CodeItem.java:157)
at org.jf.dexlib.Item.readFrom(Item.java:76)
at org.jf.dexlib.OffsettedSection.readItems(OffsettedSection.jav
at org.jf.dexlib.Section.readFrom(Section.java:143)
at org.jf.dexlib.DexFile.<init>(DexFile.java:431)
at org.jf.baksmali.main.main(main.java:254)
Caused by: java.lang.RuntimeException: Unknown opcode: f1
at org.jf.dexlib.Code.InstructionIterator.IterateInstructions(In
nIterator.java:51)
... 6 more
Error occured at code address 36
code_item @0x13dc
Drücken Sie eine beliebige Taste . . .
*****************************************
MAJOR ERROR!! WITH DEODEXING! BluetoothAvrcp.odex
*****************************************
********DELETING INCORRECT FILES*********
please exit out of window "***Deodexing ADB Window, DO NOT EXIT!***"
any ideas?

shut_down said:
This is for I9070, you only can get bootloop if you use this.
Click to expand...
Click to collapse
I disagree , this is a generic method for deodexing most phones , it's just that the stupid Sammy made un-deodexable .apks for us to suffer in
"Viper kills.....again!"

[GUIDE]【How To DEODEX Stock ROM】[UPDATE 30sept - FIX JELLYBEAN issue]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
First Lets know some Basic knowledge about DEODEX/ODEX...
What is Odex and Deodex ROM
What is an ODEX file?
In Android file system, applications come in packages with the extension .apk.
These application packages, or APKs contain certain .odex files whose supposed function is to save space.
These ‘odex’ files are actually collections of parts of an application that are optimized before booting.
Doing so speeds up the boot process, as it preloads part of an application.
On the other hand, it also makes hacking those applications difficult because a part of the coding has already been extracted to another location before execution.
What is an DEODEX file?
Deodexing is basically repackaging of these APKs in a certain way, such that they are reassembled into classes.dex files.
By doing that, all pieces of an application package are put together back in one place, thus eliminating the worry of a modified APK conflicting with some separate odexed parts.
So, Deodexed ROMs (or APKs) have all their application packages put back together in one place,
allowing for easy modification such as theming. Since no pieces of code are coming from any external location,
custom ROMs or APKs are always deodexed to ensure integrity.
How this works?
For the majority noobs amongst us, Android OS uses a Java-based virtual machine called the Dalvik Virtual Machine.
A deodexed or .dex file contains the cache used by this virtual machine (referred to as Dalvik-cache) for a program, and it is stored inside the APK.
An .odex file, on the other hand, is an optimized version of this same .
dex file that is stored next to the APK as opposed to inside it.
Android applies this technique by default to all the system applications.
When an Android-based system is booting, the davlik cache for the Davlik VM is built using these .odex files, allowing the OS to learn in advance what applications will be loaded, and thus speeds up the booting process.
By deodexing these APKs, a developer actually puts the .odex files back inside their respective APK packages.
Since all code is now contained within the APK itself, it becomes possible to modify any application package without conflicting with the operating system’s execution environment.
Advanteges & Disadvantages
The advantage of deodexing is in modification possibilities.
This is most widely used in custom ROMs and themes. A developer building a custom ROM would almost always choose to deodex the ROM package first,
since that would not only allow him to modify various APKs, but also leave room for post-install theming.
On the other hand, since the .odex files were supposed to quickly build the dalvik cache, removing them would mean longer initial boot times.
However, this is true only for the first ever boot after deodexing, since the cache would still get built over time as applications are used.
Longer boot times may only be seen again if the dalvik cache is wiped for some reason.
Note:Themes for android come in APKs too, and if you want to modify any of those, you should always choose a dedoexed custom ROM.​
Lets Start...
GUIDE TO DEODEX STOCK ROM
Java Development KIT
(Download & Setup Guide)
ANDROID SDK
xUltimateV2.3.3
(only this version is capable with samsung device)
Official Link to xUltimate : POST #5
7-Zip
(32-Bit & 64-Bit)
1.Download android-sdk & extract it.
2.Copy sdk folder & paste it into
Code:
C:\Program Files\Android
3.Change name from SDK to Android.sdk.
(inside folder look like this)​
4.you need to flash stock firmware first & Root your device.​
5.Connect your phone to computer.(Make sure you have select USB debugging in Settings>Applications>Development)​
6.Download & extract xUltimate zip.
7.Launch Main.exe(Run as administrator)
8.If everything goes well xUltimate should recognize the phone and make a connection.You now should see a list of options.
9.Select option (1) pull /system/app. Wait until it complete.​
10.Select option (2)pull /system/framework. Wait until it complete.​
11..Then select option (3) Deodex /system/app. Wait until it complete.
[If encounter any error. Find out which .odex file is it. Then remove .odex file from folder origi_app in xUltimate folder]
(i found 5 errors so i attached that app's deodex files below you just want to paste in system/app when this process complete)​
12.Then select option (4)Deodex /system/framework. Wait until it complete.​
13.DONE : your rom is now deodex. Now Exit from xUltimate​
​
Now there are 2 ways to install deodex files in device
1. from Android.SDK
From Android.SDK :
1.Put the phone in USB mass storage.
2.Go to xUltimate folder and copy "done_frame", and "done_app", and move them to the root of the sdcard.
3.Now get out from USB storage mode.
4.Go to
Code:
C:\Program Files\Android\android.sdk
& open command promote there.
5.Enter following codes.
(if you are using adb shell in su for the first time, keep phone screen on. After entering "su" code, super user request prompt in phone. Press allow )
Code:
adb shell
su
stop
mount -o rw,remount /system/ /system/
cp /sdcard/done_app/* /system/app/
rm /system/app/*.odex
cp /sdcard/done_frame/* /system/framework/
rm /system/framework/*.odex
mount -o ro,remount /system/ /system/
reboot
6.Now you have deodexed rom.
​
2. from SampleDEODEX.zip file attached below.
From zip file attached
1.open zip given as archive.
(use 7.zip but DO NOT EXTRACT.)
2.go to system/app folder & paste here all your deodexed apk's
3.same for for system/framework to paste framework files.
4.done, paste it in your SD-Card & flash through CWM.
​
STILL IF YOU FACE ANY ERROR
Especially Android 4.1 + (JB) users
Try this method Updating xUltimate tool manually.
asm-xda said:
First of all, thx for the OP. This method for Deoexing works fine, I needed to make a few updates - described below - in order to make it work on my GT-P3113 device, running JB 4.2.2.
OK. So, you have already made sure JDK is properly installed but still can't succeed? Check the following... These are the changes I had to make to deodex my ROM.
1. Get the latest version of xUltimate. It's version 2.4.2: http://www.xeudoxus.com/android/xUltimate-v2.4.2.zip. If you got version 2.3.3 and accepted to download latest version, you were directed to a thread that is not updated with the latest version. Check post #549 on that thread to find the link I've pasted above.
2. If you happen to have Android 4.2.2 on your device, ADB needs to be updated. xUltimate has version 1.0.26 which won't properly connect with your device. NOTE: you can tell which version of adb you are using by running this: adb version
So:
Install the latest version of the Android SDK to get ADB version: 1.0.31 (or later, should be fine).
Locate and copy over these 3 files from the Adnroid SDK install folder into xUltimate-v2.4.2\jar replacing the existing ones:
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
3. I don't know this step is a must for everyone, but it was for me. The assembler/deassembler for .dex file format must be upgraded too. The version in the jar folder in xUltimate-v2.4.2 didn't work fine with the .odex files in my stock ROM.
So:
Download smali.jar and baksmali.jar from here: https://code.google.com/p/smali/. I got version 1.4.2 but any above that should work fine too for the latest available ROMs I guess.
The 2 files probably include the version number in the filename ( i.e.: smali-1.4.2.jar and baksmali-1.4.2.jar). Rename them so they are called: smali.jar and baksmali.jar.
Copy (& replace) those 2 files into xUltimate-v2.4.2\jar folder.
So, that's it. After doing all the above, I managed to deodex my ROM. Well... not quite... there's something else.
After doing the steps above, you should go ahead and follow instructions in the first post of the thread. If everything works, then you are done! Say thanks to OP and enjoy your deodexed ROM. :good::victory:
If however, you still encounter errors while running the xUltimate tool, keep reading...
NOTE: The following is probably only true for certain devices (like mine) so disregard if you don't find any error while following OP steps to deodex.
I got into errors deodexing these files: SamsungIME, SecEmail_Tablet, SecSetting and SecExchange.
Since I couldn't find how to make them work, I decided to leave those files odexed. I'm not sure if that was a good idea or not, but it's fine for me because in my case I actually wanted to deodex some specific apks, not really all of them.
If you decide you want to skip some files (as I did), you'll need to proceed as follows:
Take note of the files that couldn't be deodexed and move those files from the orig_app or orig_frame folder into a new folders, let's call them: "no_deo_app" and "no_deo_frame". Ensure you move the .odex file + .jar file (in case it exists). Make really sure you move files into the right folder: "orig_app" into "no_deo_app" and "orig_frame" into "no_deo_frame".
Run the deodexing again until everything works fine. If you find another file that gives you problem, you do step 1 and 2 again until the tool completes all files successfully.
Now you have 4 folders that are relevant: "done_app", "done_frame", "no_deo_app", "no_deo_frame". Copy all of them into the root of your sdcard.
Now, get into adb shell as superuser access as described in OP following the commands below instead of the ones in the OP. Basically the difference will prevent you from deleting the odex file for the apps that couldn't be deodexed.
Code:
adb shell
su
stop
mount -o rw,remount /system/ /system/
cp /sdcard/done_app/* /system/app/
rm /system/app/*.odex
[COLOR="red"][B]cp /sdcard/no_deo_app/* /system/app/[/B][/COLOR]
cp /sdcard/done_frame/* /system/framework/
rm /system/framework/*.odex
[COLOR="Red"][B]cp /sdcard/no_deo_frame/* /system/framework/[/B][/COLOR]
mount -o ro,remount /system/ /system/
reboot
Well, that was it for me . This is what I've done to doedex my stock JB 4.2.2 ROM my Galaxy Tab 2 7.0 tablet.
Regards!
Click to expand...
Click to collapse
thanks to @asm-xda
4real*leb
Xeudoxus
and
asm-xda
(for finding the way to deodex rom for Jellybean User)
GALAXY Ace Plus User's : GO HERE http://forum.xda-developers.com/showthread.php?p=43835177#post43835177​

Cool

omarilzz said:
Cool
Click to expand...
Click to collapse
:fingers-crossed: Thanks bro

will this work with any phone?
i have an alcatel OT X'pop. will this work? 4.1.1?

aldnnnn said:
i have an alcatel OT X'pop. will this work? 4.1.1?
Click to expand...
Click to collapse
YES it does work on any device...
first give a try on above 2.3.3 xUltimate version if u face any issue download latest version v2.4 from here ;
follow same steps like above :highfive: ​

nice method but it is easier from dsixda's kitchen(cygwin)

cant recognized device
i think ive done everything but still wont recognize my device.
any suggestions?

ManzzaShahi said:
nice method but it is easier from dsixda's kitchen(cygwin)
Click to expand...
Click to collapse
i know...
but that kitchen doesn't deodex our device's apk files as much this xUltimate do
i don't know why
but i tried every step (I have kitchen & several kind software's too) & found easiest way is this only to deodex ur apk files :fingers-crossed:​
aldnnnn said:
i think ive done everything but still wont recognize my device.
any suggestions?
Click to expand...
Click to collapse
Give a try on newer version v2.4 I gave link above in that pic.
coz it has ICS Razor support.
or you have to check whether your java works fine or not.
go through some youtube video's to find how to setup JAVA or follow guide below;​

JAVA Development KIT
< Guide How to Setup JAVA >
Download JAVA Development Kit & install it first.
go to desktop, right click on
computer > properties >:highfive>Advance system setting> in advance tab environment variables
First : In user variable for ***
click new & type
Code:
variable name : CLASSPATH
variable value : C:\Program Files\Java\jdk1.7.0_21\jre\bin (your java installed path varies on your installed location)
Second : In system variables
click new & type
Code:
variable name : PATHTEXT
variable value : .COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC
also check in path is there above java path present or not if not just add it BUT do not remove old codes from line...!!! ​

j.posarekar70 said:
< Guide How to Setup JAVA >
Download JAVA Development Kit & install it first.
go to desktop, right click on
computer > properties >:highfive>Advance system setting> in advance tab environment variables
First : In user variable for ***
click new & type
Code:
variable name : CLASSPATH
variable value : C:\Program Files\Java\jdk1.7.0_21\jre\bin (your java installed path varies on your installed location)
Second : In system variables
click new & type
Code:
variable name : PATHTEXT
variable value : .COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC
also check in path is there above java path present or not if not just add it BUT do not remove old codes from line...!!! ​
Click to expand...
Click to collapse
missed this part of installing java
thanks!
will try again soon because i dont have my phone right now.
also i i have these folders in the same java folder
C:\Program Files\Java\jre6
C:\Program Files\Java\jre7
do i need these files?

aldnnnn said:
missed this part of installing java
thanks!
will try again soon because i dont have my phone right now.
also i i have these folders in the same java folder
C:\Program Files\Java\jre6
C:\Program Files\Java\jre7
do i need these files?
Click to expand...
Click to collapse
You may keep aside coz u wanna download java development kit which is jdk for that jre doesn't matter...
just for suggestion remove older version of jre from ur pc if u have jre7. ​

can u help every system file i try to deodex gives error and when i move to another it again gives error what to do same is with framework

tejasvi1 said:
can u help every system file i try to deodex gives error and when i move to another it again gives error what to do same is with framework
Click to expand...
Click to collapse
It would be great if u tell me which device u using to deodex files...
& also if possible attach error screen image/attach log file.
sent from Tapatalk 4

thks for replying , i am using my laptop for deodex my stock jellybean firmware on xperia ion

tejasvi1 said:
thks for replying , i am using my laptop for deodex my stock jellybean firmware on xperia ion
Click to expand...
Click to collapse
well you just have to skip those apk's which cause these errors...
close this window, go in Orig_app folder & delete related apk + its .odex file & give another try.
if error appear in another apk do the same.
some apk's wont get deodex through this app you just have to delete those & move forward.
.
.
.
if u get error in each system apk then download older version's of xUltimate app from this POST #5​

Awsm buddy by the way i have a xperia mini(stock ics) . Will this work on it ?

sadab said:
Awsm buddy by the way i have a xperia mini(stock ics) . Will this work on it ?
Click to expand...
Click to collapse
Keep backup
give a try
follow each steps ​

Nice guide! I followed it when I created my ROM! Very useful! tnx

Hope it works on my samsung galaxy pocket
I will try on my samsung galaxy pocket coz i want the s3 status bar so hope it works without any issues if i have some problem i will tell u guys
---------- Post added at 02:16 PM ---------- Previous post was at 02:10 PM ----------
Plzz check and tell me that will it work on my Rooted Samsung Galaxy Pocket plzz thnx in advanced

KumailHyderMirza said:
I will try on my samsung galaxy pocket coz i want the s3 status bar so hope it works without any issues if i have some problem i will tell u guys
---------- Post added at 02:16 PM ---------- Previous post was at 02:10 PM ----------
Plzz check and tell me that will it work on my Rooted Samsung Galaxy Pocket plzz thnx in advanced
Click to expand...
Click to collapse
Give a try my friend...
there is no way to brick your device .
you just have to put system & framework files in the pc & let xUltimate do the work.
if everything goes fine you get pair of folders deodex system apps & that of framework files .
put them to make flashable zip & there you go deodex stock rom.
everything will fine if u follow my steps.
if get any wrong (error) then its been in ur pc only not in ur phone ​
loxdegio said:
Nice guide! I followed it when I created my ROM! Very useful! tnx
Click to expand...
Click to collapse
Happy to help you
​

[Completed] How to Deodex stock Rom for mtk chipset :)

Assalam Alikum (may peace be upon You) People!!
This Tutorial was also done by #Superstone
but that Method Doesn't work now
so here i am for new working Tutorial
Today I’ll be Showing you How To deodex your STOCK ROM
there is only one single signed tool Working with MTK 6592 chipset
Which is Known As UnReal-Deoder
Thanks To Super Stone a Junior member of XDA Fourms Community who found this tool Which is Written by UnReal Mitch and Compiled by Noracle
i-mobile Community Thailand 
So Let’s Get Started 
Requirements :-
1:- downloaded Java SDK 8
2:- Winrar or 7zip
3:-The Unreal-Deodexer
4:- Rooted Device with Root Manager
5:- MTK-Driod Tools 
Step:-
1:- Install the Downloaded java SDK
2:- Fetch The frame work and system apps via Root Explorer. To The sd card
3:- Extract Unreal-Deodexer make Sure there is no space in Directory i.e C:/downloads/Un-Realboxing
4:- now after removing Space paste the system framework folder and system apps in sytem folder in UnReal-Deodexer 
5:- and start Unreal-Deodexer and Wait Till its finished 
6:- after it has been Finished change the Name of Folder like
done_apps and done_framework
7:- post them in internat memory of Phone.
8:- Connect the phone with MTK-Droid Tools
9:- run Abd Terminal 
10:- Enter these Commands 
adb remount
adb shell
stop
cp /sdcard/done_app/* /system/app/
rm /system/app/*.odex
rm /system/app/*.jex
cp /sdcard/done_framework/* /system/framework/
rm /system/framework/*.odex
rm /system/framework/*.jex
echo dalvik.vm.execution-mode=int:fast >> /system/build.prop
reboot recovery
11:-Now phone should be in Recovery mode. Wipe cache + dalvik cache in recovery. (Important to delete both caches! Otherwise phone might be stuck @ reboot...)
12:- reboot the phone (now deodexed rom needs quite a while for the first startup....)
13:- Enjoy Deodexed stock Rom 

Hi there,
There is many threads where is discussed about deodexing ROM's. See bellow:
[Guide] [Tutorial] How to Deodex Stock Rom using Universal Deodexer (Easiest Way)
[GUIDE][UPDATED] How to deodex stock kitkat roms
[GUIDE]【How To DEODEX Stock ROM】[UPDATE 30sept - FIX JELLYBEAN issue]
Ask in one of that thread if you have more querry about that.
Good luck