Database Info

[MOD] Battery Icon Mod for Stock 2.3.6 ROM

Was bored today (read: avoiding doing work), and quickly had the UOT kitchen give a better battery icon. Nothing fancy.
If anyone wants the zip, feel free. Also attached are the necessary files to make your own mods in UOT kitchen (if you're running the stock 2.3.6 rom).
....and now I guess I'd better do work today.

Without CWM (on stock 3e recovery), how's this installed? Can't install non official samsung zip files with 3e. Also, stock ROM is odexed... can i just rename/delete SystemUI.odex and replace my SystemUI.apk with this one? Or does it have to be pushed with ADB?

Good question! Wish I knew how else to install it without CWM. You might be able to change out the files, but I honestly don't know. Anyone out there know better than I?
Sent from my SAMSUNG-SGH-I727

easiest way to install without cwm is to have root explorer extract all the files in there which should be (framework-res.apk) and systemui.apk . once extracted and in your phone sd then you have to drag it with root explorer to system/framework for the framework-res.apk and for systemui.apk to system/app but before u do that you have to fix permissions by bringing them into system folder then fix permission and then move it otherwise you'll see forecloses like no tommorow and you're done. but if your rom is .odexed its not possible because of .odex scripts it'll mess up your phone like whoa ..anyways enjoy
permission to fix in the box are like this..
Read X X
Write X
Other X

This is stock 2.3.6, so it is still odexed...
Sent from my SAMSUNG-SGH-I727

Will this work for Sky ICS? 6.9
Sent from my SAMSUNG-SGH-I727 using XDA App

jslanger said:
This is stock 2.3.6, so it is still odexed...
Sent from my SAMSUNG-SGH-I727
Click to expand...
Click to collapse
I'm on the stock 2.3.6 ROM which is odexed. I see in /system/framework there is framework.jar and framework.odex. And a framework-res.apk with no matching odex. In /system/app there is systemUI.apk and systemUI.odex. So, to avoid a FC shii storm, I should:
1) put the OP systemUI.apk and framework-res.apk in /system and fix permissions...
2) then move systemUI.apk to /system /app folder.
3) move framework-res.apk to /system/framework folder.
Do I need to delete my current SystemUI.odex or leave it? Not sure if OP's systemUI.apk is deodexed or odexed?
Secondly, do I do anything with my current framework. jar and framework.odex files?

Kenneth.Torres said:
Will this work for Sky ICS? 6.9
Sent from my SAMSUNG-SGH-I727 using XDA App
Click to expand...
Click to collapse
Sorry, but it won't. But you can make your own using uot kitchen (online) for themes. Though I have read that some of the personalized ROMs don't play nice with UOT...
Sent from my SAMSUNG-SGH-I727

DoctorQMM said:
I'm on the stock 2.3.6 ROM which is odexed. I see in /system/framework there is framework.jar and framework.odex. And a framework-res.apk with no matching odex. In /system/app there is systemUI.apk and systemUI.odex. So, to avoid a FC shii storm, I should:
1) put the OP systemUI.apk and framework-res.apk in /system and fix permissions...
2) then move systemUI.apk to /system /app folder.
3) move framework-res.apk to /system/framework folder.
Do I need to delete my current SystemUI.odex or leave it? Not sure if OP's systemUI.apk is deodexed or odexed?
Secondly, do I do anything with my current framework. jar and framework.odex files?
Click to expand...
Click to collapse
ive not tried anything with .odex but it doesn't work as far as i know and yah some roms that are personalized have uot problems but just follow up with devs of those roms they can fix it up and all for ya.

I can confirm that it does work with odexed roms (since it does work with stock 2.3.6).
Sent from my SAMSUNG-SGH-I727

jslanger said:
I can confirm that it does work with odexed roms (since it does work with stock 2.3.6).
Sent from my SAMSUNG-SGH-I727
Click to expand...
Click to collapse
Thx for confirming... so back to my questions above.. do i need the systemUI.odex file or does your systemUI.apk combine both? Also, do I do anything with the framework.jar and framework.odex files (or just replace framework-res.apk with yours?)

DoctorQMM said:
Thx for confirming... so back to my questions above.. do i need the systemUI.odex file or does your systemUI.apk combine both? Also, do I do anything with the framework.jar and framework.odex files (or just replace framework-res.apk with yours?)
Click to expand...
Click to collapse
The framework and systemui files posted above are originals (I posted them in case someone else wanted to mod it themselves, so they wouldn't have to extract them themselves). The zip file is the new icon materials from UOT. Not sure how to directly install it (I've only ever installed from the zip file myself)...
Sent from my SAMSUNG-SGH-I727

I am missing something
I tried installing with CWM and following DoctorQMM steps to the letter (even learned all about fix permissions) but no matter what, my phone locks up and just flashes after the install and reboot. What can I try next?
Running stock 2.3.6 ROM on an AT&T i727 that i rooted just now this is my first mod

How to re-odex?

Normally to decompile my dex files I use smali and baksmali, how can I re-odex them?
Id like to get my service.jar re-odexed so I can try and push it to my phone via a zip update.
Sent from my MB865 using xda premium

[mini HOW-TO] Re-Odex (or create a new .odex file)
Fall of Enosis said:
Normally to decompile my dex files I use smali and baksmali, how can I re-odex them?
Id like to get my service.jar re-odexed so I can try and push it to my phone via a zip update.
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
It all needs to be done on your phone, live.. with adb.
Here's how I accomplished it - I will use the services.jar in this example. Just change the file name and path to existing .odex accordingly for other files (not sure if all steps are required exactly, but it has worked for me multiple times with different jars and SysUI apk):
Requirements:
Odexed system
adb
dexopt-wrapper
Put this dexopt-wrapper file (unzip first) in /system/bin with 775 permissions:
X X X
X....X
X....X
Probably a good idea to reboot after pushing that file, if you use root explorer (like I did).
Put the deodexed services.jar (or other jar/apk file you want to make an new odex of) on your sd card.
Go to /system folder (with root explorer or equal) and mount it R/W (not sure if this is necessary - but won't hurt)
Put your USB connection to "Charge only" mode.
Go here (big props and credit to jhotmann for this) and follow steps 8-12 (I've recreated the steps with the A2's bootclasspath below).
The bootclass path is located in the /init.rc file at the root of your phone.
Connect with adb (do a adb devices check to make sure you're all good).
To create the new odex:
Code:
adb shell
su
cd /sdcard/
dexopt-wrapper services.jar new.odex /system/framework/core.jar:/system/framework/bouncycastle.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/android.policy.jar:/system/framework/services.jar:/system/framework/core-junit.jar:/system/framework/com.motorola.android.frameworks.jar:/system/framework/com.motorola.android.widget.jar
I know it's a long entry for those who don't work with command lines often (like me), but double check your entry before hitting enter.
To copy the signature from the existing odex (change path to /system/app/.. if necessary):
Code:
busybox dd if=/system/framework/services.odex of=new.odex bs=1 count=20 skip=52 seek=52 conv=notrunc
Done! Rename new.odex (created on your /sdcard) to services.odex since that is your new signed odex file...
You can then get that on your odexed system by your choice of method (adb push, update.zip, root explorer push, etc.. - note: please know what you are doing before trying to push files with root explorer! - you cannot simply copy and paste!)
Or, if you want to deodex it right away again for some odd reason like I did (personal issues )... Take the services.jar and the new services.odex from your sdcard and put them on your computer - and open the services.jar with 7-zip (maybe winzip) and delete the classes.dex file from the 7-zip window. Now you have a fresh new set of .jar/.odex files ready for deodexing (I did this all with the SystemUI.apk last night, that's why I elaborated and re-typed this whole thing today..).

Frigging brilliant man.
Much appreciated. I'm super sick and my USB cable is at work.
Once i get it back on Wednesday, I'll work all this out. If I could thank you twice I would.
Thanks man!
Sent from my MB865 using xda premium

Fall of Enosis said:
Frigging brilliant man.
Much appreciated. I'm super sick and my USB cable is at work.
Once i get it back on Wednesday, I'll work all this out. If I could thank you twice I would.
Thanks man!
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
Not a prob.
And, I updated the dexopt-wrapper link so it's easier to download - just unzip it first..
Good luck on your quest.. let me know if you catch any snags along the way - and i'll try and help you out.
Sent from my mind using XDA

Ok sooo, I think we (or most likely me) are confused on what I wanted to do. I don't want to make a NEW odex file. I need to recombine my modded classes.dex BACK with the service.jar.
Since I needed to modify some script in the services.jar I had to de-odex it so I had a classes.dex file to use baksmali with so I could modify it. Once I modded it I used smali to create the NEW MODDED classes.dex. And now I need to re-odex(bad terminology?) them to re-combine the services.jar with the classes.dex so the modded services.jar could be used on a odexed ROM.
I'm working on a de-odexed version also, but I'd like to be able to offer both

Fall of Enosis said:
Ok sooo, I think we (or most likely me) are confused on what I wanted to do. I don't want to make a NEW odex file. I need to recombine my modded classes.dex BACK with the service.jar.
Since I needed to modify some script in the services.jar I had to de-odex it so I had a classes.dex file to use baksmali with so I could modify it. Once I modded it I used smali to create the NEW MODDED classes.dex. And now I need to re-odex(bad terminology?) them to re-combine the services.jar with the classes.dex so the modded services.jar could be used on a odexed ROM.
I'm working on a de-odexed version also, but I'd like to be able to offer both
Click to expand...
Click to collapse
So, you have a deodexed services.jar (with an unedited classes.dex inside)? And, you also have an edited classes.dex (the new modded one). Just drag and drop the new modded classes.dex into the services.jar file with 7-zip to overwrite the old one.
Then I would check out the mods on a deodexed system, and provided they work, then go through the re-odexing process (separating that classes.dex from the apk and creating a new odex file) as described above to get it working on odexed systems.
Hope that helps.. Good luck!

Yes sir, you are correct. That was the first thing I tried to do was just drag and drop the modded classes.dex with 7zip, save it, however when i tried to flash the "modded" ROM it can't install the system folder because (according to Jim), when I modded copied the new classes.dex, I changed the size, and so the signature needed to be changed as well. They mismatched.

Fall of Enosis said:
Yes sir, you are correct. That was the first thing I tried to do was just drag and drop the modded classes.dex with 7zip, save it, however when i tried to flash the "modded" ROM it can't install the system folder because (according to Jim), when I modded copied the new classes.dex, I changed the size, and so the signature needed to be changed as well. They mismatched.
Click to expand...
Click to collapse
Not sure about the details of that.. I know the signatures can be tricky, but I've modded a few apks/jars similarly with no problems... when you say "can't install.." is that it wouldn't flash in recovery, or you bootlooped?

Just wouldn't flash at all.
And thanks for all your help man.
Sent from my MB865 using xda premium

I've updated the 2nd post with more detail on creating a new odex file...
Not to be a "rooster" (replace with your word of choice) or anything, but maybe this info has a place somewhere besides the general threads..?:angel: (and what is up with these new Smilies and posting reply layout?) - it just seems so hard to come by good literature on this process (which, I suppose, is a process so rarely needed though...)

So I need to perform the processes above while running in an odexed environment correct? Does this process change the deodexed APK we are running the script on to an odexed one as well as create a new .odex file for that APK? I am just confused about what the result is after running the script. For my situation I want to take 2 deodexed files (systemui and sec settings.apk) and odex them. Then push them into an odexed rom. Once I run the script above what am I left with?

Didact74 said:
So I need to perform the processes above while running in an odexed environment correct?
YES.
Does this process change the deodexed APK we are running the script on to an odexed one as well as create a new .odex file for that APK?
(Yes, it will create a new odex file that you will need to rename, but..)NO. You will need to take the classes.dex out of the deodexed apk/jar - use something like 7-zip. Unless you only edited smali, then you really only need the new odex file.
I am just confused about what the result is after running the script. For my situation I want to take 2 deodexed files (systemui and sec settings.apk) and odex them. Then push them into an odexed rom. Once I run the script above what am I left with?
Click to expand...
Click to collapse
I broke up your quote with my best answers...
As for what your're left with is a new.odex file, properly signed, if all goes well. You are going to need to do it for each of your deodexed files.
Rename them, remove the classes.dex from the deodexed files you used, and get them on your phone however you choose (I prefer zip packages and a restore.zip in case something goes wrong).
Also note that the bootclass path is different from GB to ICS.. and among different devices of course. Check init.rc file if need be. I posted the one to use for A2 ICS (think it may be the same for razr too) here: http://forum.xda-developers.com/showthread.php?t=1753659
I can't garuntee you won't have problems, but good luck... if you do you could try the dexopt-wrapper from here: http://forum.xda-developers.com/showthread.php?t=1645950 - just unzip it first obviously (but I think it's the exact same file though..)
Btw, it's all done with adb, one line at a time.. not really a script, but thank you for the idea - maybe a batch file?
Sent from my phone's mind

Great, thank you for the detailed response. Last question.
What if I have the original SystenUI.odex and SecSettings.odex files that used to be attributed to them before i deodexed them? Can I simply reuse those without having to run through the adb process?
Thanks,

Didact74 said:
Great, thank you for the detailed response. Last question.
What if I have the original SystenUI.odex and SecSettings.odex files that used to be attributed to them before i deodexed them? Can I simply reuse those without having to run through the adb process?
Thanks,
Click to expand...
Click to collapse
But, you deodexed them to edit the smali files in the classes.dex right? So, no, you will need to use the new odex files that are created from the modded deodexed files you used..
If you never edited any of the smali files, then you didn't need to deodex in the first place... you only need to deodex in order to mod the smali files - everything else in the apk can be modded as is on odexed systems.
Sent from my phone's mind

Thank you very much. Can you repost the wrapper file? Its not downloading correctly.

Didact74 said:
Thank you very much. Can you repost the wrapper file? Its not downloading correctly.
Click to expand...
Click to collapse
Updated the link in Post #2 with a zip file - you need to unzip it first then move it.

Thank you.
So I am getting an error trying to re-odex. See the attached image of the error.
Weird thing is that even though I get an error it still creates the new.odex file. I triedto go through the entire process even though I was getting errors and it just got stuck on the boot screen and never loaded. Anything in my error attached raise any flags?
Thanks,

Didact74 said:
Thank you.
So I am getting an error trying to re-odex. See the attached image of the error.
Weird thing is that even though I get an error it still creates the new.odex file. I triedto go through the entire process even though I was getting errors and it just got stuck on the boot screen and never loaded. Anything in my error attached raise any flags?
Thanks,
Click to expand...
Click to collapse
Hmmm... First thing I can think of is: are all of those framework files in the bootclass path that you used actually in your /framework folder? With our A2, in ICS there are a few extra .jar files listed that were not actually on our phone, so I had to remove those from the path...
I will try to make a new odex myself and make sure that's not a standard error message... @Fall of Enosis, you recall what it spits out?
EDIT: Shoot - forgot I'm deodexed right now... will attempt later or hear back from Fall by then..

alteredlikeness said:
Hmmm... First thing I can think of is: are all of those framework files in the bootclass path that you used actually in your /framework folder? With our A2, in ICS there are a few extra .jar files listed that were not actually on our phone, so I had to remove those from the path...
I will try to make a new odex myself and make sure that's not a standard error message... @Fall of Enosis, you recall what it spits out?
EDIT: Shoot - forgot I'm deodexed right now... will attempt later or hear back from Fall by then..
Click to expand...
Click to collapse
Yes, all .jar files listed in my bootclass were located in the framework directory.

Nevermind...my mistake. I had an issue with my files not being deodexed correctly from the start. I went back and deodexed, made the edits to res and smali then odexed using the method above again and all went well!
Thanks!

[HowTo] Odex FRAMEWORK, all Android versions may apply.

Here in this tutorial, I will show some facts about Deodex and Odex, then explain how to odex the framework of a ROM(which is pretty annoying, you'll find out). Credits goes to myself
This method should work on all Android devices.
------------------------------------------------------------------------------------------------------------
First of all, what is odex? Something you should know about classes.dex.
Odex stands for Optimized dex. I'm not gonna explain a lot because I'm not sure if I'm right. First of all, in typical apk files, when you open it with WinRAR or something like that, you can find a file called "classes.dex"(this type of apk is deodexed). This file is the key. It contains the core codes of the apk. However the other type of apk comes with an *.odex file and doesn't have classes.dex inside the apk file. This is odexed apk. There are 2 types of ROMs here, odexed and deodexed. Odexed ROMs' classes.dex are already out of the apk files, while deodexed ROMs' classes.dex are still in the apks. When Android executes an apk, it has to extract the classes.dex out and execute it. So when you flash an deodexed ROM, the first boot takes a long long time since the Android system needs to extract all the classes.dex into dalvik-cache(it shows "Optimizing apks" on the screen for 4.0 ROMs, shows boot animation on screen for 2.3 or below ROMs). However for the odexed ROMs, because the classes.dex are already out there, the system just grabs them and use them, without wasting time and storage space extracting classes.dex out.
Why odex framework?
It can boost your device a little by odexing your framework. Your phone can run more efficiently. Although it's a complicated process, but trust me, it's worth it.
What is so special about odexing framework files? What's the difference?
Odexing an app is very easy, and I believe everyone knows how to do it. But odexing framework is really annoying. Why? Because apps and more like stand-alone things, they are not a part of system. You delete it, nothing bad happens, your phone still boots, you just get endless FC if you delete the wrong one, or missing status bar, that's all. But framework files you cannot mess around. They are parts of the system. They have to match the system's codes precisely, without any error, even the order of files(keep this in mind, very important). So for every ROM, the framework initialize codes are different(same RUU or other ROM based ROMs count as its base ROM), and you must modify the odexing binary to make it odex for you properly, or you can sit and watch the beautiful bootloop.
What's the relationship between odexing apps and odexing framework?
Simple, but important. If you odexed apps, you cannot touch the framework. Framework always goes in the first place. If you wanna odex both, you must odex framework first. Or... "The Tragedy of App and Framework"...
So what do we have to keep in mind before we start?
Keep your mind clear, prepare a bag of ice in case you feel dizzy with the codes, and MAKE ENOUGH SPACE FOR FRAMEWORK ODEXING. I would prefer you remove a few useless apks in /system/app first to make more room in system partition. Failing odexing may brick your device forever! Nah just kidding it will only cause you to bootloop. No big deal. Also, it won't odex your framework-res.apk and always will not, so don't feel bad and do it again and again till your phone burn . Make sure your device is ROOTED and enable USB debug. You need Java Runtime Environment.
What tools do you need?
Notepad++ and a magical rar that contains all you need to success.
Let's get started.
------------------------------------------------------------------------------------------------------------
1. Use your file manager to find init.rc at the very root directory of your phone and copy it to SDCard for later code editing, or you simply adb pull it out and skip the coping step. (If you know how to compile boot.img it is even easier, just unpack boot in Android Kitchen, look for line "export BOOTClassPATH". I'm not gonna introduce that method since most people can't. Silly me, didn't I just intoduced that? XD)
2. Connect USB, set mode as disk drive so you can access your SDCard. Copy init.rc into your computer. Open it with notepad, and find where it says "export BOOTClassPATH", create a new file and copy line "export BOOTClassPATH" into the new file. For example:
Code:
export BOOTCLASSPATH/system/framework/core.jar:/system/framework/bouncycastle.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/android.policy.jar:/system/framework/services.jar:/system/framework/core-junit.jar:/system/framework/HTCExtension.jar:/system/framework/com.htc.framework.jar:/system/framework/com.htc.android.pimlib.jar:/system/framework/com.htc.android.easopen.jar:/system/framework/com.scalado.util.ScaladoUtil.jar:/system/framework/com.orange.authentication.simcard.jar:/system/framework/android.supl.jar:/system/framework/com.ecrio.sip.jar
3. Open dexopter in the rar you downloaded with Notepad++. Find the lines that show the similar contents to the things after "export BOOTClassPATH". It is Line 21 to Line 35 on my laptop. Edit them according to the things you just copied out of init.rc. For example, if the first file is "X.jar", then you will have to edit the line into "dexopt-wrapper/system/framework/X.jar /system/framework/X.odex". Then repeat until you finish with all the files that are listed in the long list you copied out of init.rc. File order DOES MATTER. Use the bag of ice I told you to prepare eariler to make you sober if you feel dizzy with the codes. The lines may be more or less after you edited them, doesn't matter.
4. Copy "dexopter" and "dexopt-wrapper" into /system/bin and set the correct permissions. Make sure they have enough permission to change your system files. Restart your phone.
5. Go to CMD and lead it to where adb.exe is(included in the rar). Type these in order:
Code:
adb shell
su
cd system/framework
dexopter fr
Then the codes will run crazy in your cmd window... The odex process has begun!
6. If the odex process completed without error, you are half way there! Well it doesn't mean you have to stare at your screen during the process. It's about time we figure it out! The phone will automatically reboot once it's finished. If it doesn't and you are sure all are done, reboot manually.
7. If you can't boot properly, go back and check everything carefully. If you can, then open your file manager and copy the entire framework directory into your SDCard. You can still adb pull and skip the next coping step.
8. Mount SDCard. Go into framework directory on your computer. Open every file that has an odex file with it, delete the classes.dex inside. WinRAR is okay. The files may seem ridiculously small after you delete the classes.dex, but don't worry since classes.dex are already pulled out and turned into odex files.
9. Copy the whole framework folder into the folder where adb is at. Use adb to push all the files back into /system/framework.
Code:
adb root
adb remount
adb push framework /system/framework
adb shell
su
chmod /system/framework xxx (xxx is a permission code, depends on your ROM. They should be the same as the old deodexed framework files. Use Google to find out how to use the permission codes.)
10. After all the files are pushed in, reboot your phone.
11. If it still boots into the system, congratulations! You've successfully odexed your framework! If it doesn't, then go back and read everything carefully. The most common error occurs when you are editing the dexopter code. You will have to redo everything again.
Done! Everything is ready to go!
You can directly grab the files you've odexed and put it in your custom ROM(must be the same base), just don't forget the odex files.
------------------------------------------------------------------------------------------------------------
Okay, hmm, what to say now? Still, I would be glad if you donated me, but if you don't it's okay, just reply and hit thanks .
Oh almost forgot, the magical rar: http://d-h.st/tYi
------------------------------------------------------------------------------------------------------------
Big thanks to Scott, see him in #3. He explained why some files aren't odexed and provided a easier method(but they all get you dizzy )
Big thanks to JSLEnterprises, see him in #4. He provided a newer busybox for Scott's method.

If you can, send me a PM on how to odex apps.
Sent from my HTC One X using Tapatalk 2

BreatheHT said:
Here in this tutorial, I will show some facts about Deodex and Odex, then explain how to odex the framework of a ROM(which is pretty annoying, you'll find out). Credits goes to myself
Also, it won't odex your framework-res.apk and always will not, so don't feel bad and do it again and again till your phone burn . Make sure your device is ROOTED and enable USB debug. You need Java Runtime Environment.
Click to expand...
Click to collapse
Good write up. Other files that wont "re-odex" are com.htc.resources.apk, com.htc.videowidget.res.apk, com.htc.weather.res.apk and framework-htc-res.apk.
The reason? The files dont have .dex files because there is no code in them. These files just carrier resources like images (for those that didint know).
The .dex files are the actual smali code that devs mod to make the ROM do crazy things
Also, an easier method can be found here: http://themikmik.com/showthread.php?12988-Tool-App-Dexo-the-Universal-Odex-Utility
It does it all and pulls the bootclass for you. And it also does /system/app/ in one simple shot.
Also, one last thing... You can just as easily pull the files back to the PC using the ADB Pull command...
Code:
adb pull /system/app ./app
adb pull /system/framework/ ./framework
EDIT: And another simple method to get your bootclass is do another ADB Pull
Code:
add pull init.rc
I find the adb pull method quicker and more simple...
theking_13 said:
If you can, send me a PM on how to odex apps.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
You can use the method I just explained or if you want to try the framework manually then do apps seperately then you can use this: http://forum.xda-developers.com/showthread.php?t=1514576
I use that app to re-odex updated files in the ROM. For example... If Gmail updates (which it just did) I would remove the old gmail files from system/app/ and put the new one in and run that program then pull the files.
-Scott

If anyone finds this to be too much work... dont worry... it only unpacks the classes.dex once. It will only need to unpack a dex if original file has changed (changed entries need to propogate). That's why all the consecutive boots are back to a 'normal' span of time.
re-odexing your roms IS recommended if either A) you're anal-retentive/have OCD or B) propogation ("Android is Upgrading...") happens every time you reboot your device (it happens sometimes)
If you're going to use the tool scrosler linked to, replace the busybox binary with the one inside the attatched zip (this is busybox 1.20.1). The one that come with the tool is pretty dated.
:good:
Update: Busybox 1.20.2 has been released (though not compiled for android use yet)

Great stuff guys.

scrosler said:
Good write up. Other files that wont "re-odex" are com.htc.resources.apk, com.htc.videowidget.res.apk, com.htc.weather.res.apk and framework-htc-res.apk.
The reason? The files dont have .dex files because there is no code in them. These files just carrier resources like images (for those that didint know).
The .dex files are the actual smali code that devs mod to make the ROM do crazy things
Also, an easier method can be found here: http://themikmik.com/showthread.php?12988-Tool-App-Dexo-the-Universal-Odex-Utility
It does it all and pulls the bootclass for you. And it also does /system/app/ in one simple shot.
Also, one last thing... You can just as easily pull the files back to the PC using the ADB Pull command...
Code:
adb pull /system/app ./app
adb pull /system/framework/ ./framework
EDIT: And another simple method to get your bootclass is do another ADB Pull
Code:
add pull init.rc
I find the adb pull method quicker and more simple...
You can use the method I just explained or if you want to try the framework manually then do apps seperately then you can use this: http://forum.xda-developers.com/showthread.php?t=1514576
I use that app to re-odex updated files in the ROM. For example... If Gmail updates (which it just did) I would remove the old gmail files from system/app/ and put the new one in and run that program then pull the files.
-Scott
Click to expand...
Click to collapse
hehe yep I know the adb pull command, I thought about it and I didn't put it in...

theking_13 said:
If you can, send me a PM on how to odex apps.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
You confused bro?

Thanks. Even though I won't ever be doing this, it's good to know what's going on.

This is awesome. Thanks so much for this. I wanted to know how to odex and deodex roms.
Sent from my HTC One XL using xda app-developers app

scrosler said:
Good write up. Other files that wont "re-odex" are com.htc.resources.apk, com.htc.videowidget.res.apk, com.htc.weather.res.apk and framework-htc-res.apk.
The reason? The files dont have .dex files because there is no code in them. These files just carrier resources like images (for those that didint know).
The .dex files are the actual smali code that devs mod to make the ROM do crazy things
Also, an easier method can be found here: http://themikmik.com/showthread.php?12988-Tool-App-Dexo-the-Universal-Odex-Utility
It does it all and pulls the bootclass for you. And it also does /system/app/ in one simple shot.
Also, one last thing... You can just as easily pull the files back to the PC using the ADB Pull command...
Code:
adb pull /system/app ./app
adb pull /system/framework/ ./framework
EDIT: And another simple method to get your bootclass is do another ADB Pull
Code:
add pull init.rc
I find the adb pull method quicker and more simple...
You can use the method I just explained or if you want to try the framework manually then do apps seperately then you can use this: http://forum.xda-developers.com/showthread.php?t=1514576
I use that app to re-odex updated files in the ROM. For example... If Gmail updates (which it just did) I would remove the old gmail files from system/app/ and put the new one in and run that program then pull the files.
-Scott
Click to expand...
Click to collapse
Is there also a tool to deodex roms?
Sent from my HTC One XL using xda app-developers app

SkizzMcNizz said:
Is there also a tool to deodex roms?
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Like Scott posted?
Basically that is the steps right there..you are doing the apk in the system/app and framework.
That link provides a tool which when done properly will run on the de-odexed stock Rom and odex it...
Good luck with that...it's a nightmare...haha..

SkizzMcNizz said:
Is there also a tool to deodex roms?
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Yep Android Kitchen can do it.

Hopefully this will help to see more odex ROMs

This is the first phone I've had where developers strive to odex their roms
Something to get used to
Sent from my HTC One X using Tapatalk 2

superchilpil said:
This is the first phone I've had where developers strive to odex their roms
Something to get used to
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Most official ROMs are odexed.

BreatheHT said:
Most official ROMs are odexed.
Click to expand...
Click to collapse
Quite the opposite where I come from
Although I came from a different carrier so this side of the forums is different
Sent from my HTC One X using Tapatalk 2

superchilpil said:
Quite the opposite where I come from
Although I came from a different carrier so this side of the forums is different
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Nah carrier doesn't matter.

SkizzMcNizz said:
Is there also a tool to deodex roms?
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1208320
(you'll have to update the versions included in the zip as this thread is dated - 2011)
Note: the API level for 4.0.3/4.0.4 (what our HOX's run) is '15'.
you can also use DSIXDA's kitchen which can be used to batch deodex apk's after you set the api level
(it's defaulted to '10'... which was Gingerbread -> 2.3.3-2.3.7)
Full list of API levels for their specific Android versions

BreatheHT said:
hehe yep I know the adb pull command, I thought about it and I didn't put it in...
Click to expand...
Click to collapse
Yeah, I like to do it better that way. Dont have to move my hands from the keyboard and mouse. Makes you more efficient :good:
BreatheHT said:
Most official ROMs are odexed.
Click to expand...
Click to collapse
I think all?
superchilpil said:
Quite the opposite where I come from
Although I came from a different carrier so this side of the forums is different
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Carrier is irrelevant. Most people dont know how to work with ODEX files so they go with de-odex. Its mroe challanging but provides a better experience.
techlogik said:
Like Scott posted?
Basically that is the steps right there..you are doing the apk in the system/app and framework.
That link provides a tool which when done properly will run on the de-odexed stock Rom and odex it...
Good luck with that...it's a nightmare...haha..
Click to expand...
Click to collapse
No he is asking to go the other way from odex to de-odex.
BreatheHT said:
Yep Android Kitchen can do it.
Click to expand...
Click to collapse
JSLEnterprises said:
http://forum.xda-developers.com/showthread.php?t=1208320
(you'll have to update the versions included in the zip as this thread is dated - 2011)
Note: the API level for 4.0.3/4.0.4 (what our HOX's run) is '15'.
you can also use DSIXDA's kitchen which can be used to batch deodex apk's after you set the api level
(it's defaulted to '10'... which was Gingerbread -> 2.3.3-2.3.7)
Full list of API levels for their specific Android versions
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Yep, I love that script. I was the one that sent him the mnt point file for the HOX :highfive:
I am going to talk to him about bringing in "official" support for the Asus TF300T. I got the boot.img fiugred out this morning! Woot. **** is about to get real with the Asus!

superchilpil said:
This is the first phone I've had where developers strive to odex their roms
Something to get used to
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
its a good final touch when cook done with smali tweaks.
another benefit is sorta kang-protection

<req>Add toggles to stock LSZ

Hi all!
Is there a way to get a mod in order to add toggles (airplane, reboot, power off buttons) for a odex stock rom LSZ Rooted?
TNX a lot

try this!!! http://forum.xda-developers.com/showthread.php?t=2151953

diruengeru said:
try this!!! http://forum.xda-developers.com/showthread.php?t=2151953
Click to expand...
Click to collapse
Won't work because he's using a odexed Rom whereas the Mods only work in a deodexed Rom

Sounds silly but what if he just delete SystemUI.apk and SystemUI.odex, services.jar and services.odex files then flash the mentioned mod, will it be OK???
tbh, I didn't test this method, although it works in some other mods!!!

majdinj said:
Sounds silly but what if he just delete SystemUI.apk and SystemUI.odex, services.jar and services.odex files then flash the mentioned mod, will it be OK???
tbh, I didn't test this method, although it works in some other mods!!!
Click to expand...
Click to collapse
I have Odex firmware, but I put all the fashion, because I can make the necessary files Odex
odexer4_update_external_sd.zip: http://yadi.sk/d/CQSFNoCO2uNMD
odexer_4_update_internal_sd.zip: http://yadi.sk/d/ZLLm-1Qw2uNMF - Who's supposed to, I can write a guide on how to do it, it is elementary

majdinj said:
Sounds silly but what if he just delete SystemUI.apk and SystemUI.odex, services.jar and services.odex files then flash the mentioned mod, will it be OK???
tbh, I didn't test this method, although it works in some other mods!!!
Click to expand...
Click to collapse
I've tried it doesn't work...

ThaiDai said:
Won't work because he's using a odexed Rom whereas the Mods only work in a deodexed Rom
Click to expand...
Click to collapse
Yes it's true...

Klementiy said:
I have Odex firmware, but I put all the fashion, because I can make the necessary files Odex
odexer4_update_external_sd.zip: http://yadi.sk/d/CQSFNoCO2uNMD
odexer_4_update_internal_sd.zip: http://yadi.sk/d/ZLLm-1Qw2uNMF - Who's supposed to, I can write a guide on how to do it, it is elementary
Click to expand...
Click to collapse
Sorry I've not understood. Do you have a way to add toggle on LSZ odex stock rom? If it works, can you write a little guide to do it, please?

updated instructions and changed the translator http://forum.xda-developers.com/showpost.php?p=38715726&postcount=14

Thanks a lot Klementiy. I went through odexer.sh, and it seems so simple now.
I can confirm that this works.. If someone want the CWM package for Odexed LSZ, I can post it here.
Klementiy said:
Instructions on how to make Odex:
1. For First you need to open an archive with modifications and see what sort of files
2. Look on your phone or at this address https://docs.google.com/folder/d/0B...ring&pli=1&docId=0B_tjIX7pV_liQjR3VGhoY0VMSWM which of these files have a second file Odex
3. Install this archiver https://play.google.com/store/apps/details?id=ru.zdevs.zarchiver ZArchiver.apk: http://yadi.sk/d/qhsL2d8n31-w8 and in the settings set compression "uncompressed"
4. From the archive with modifications extract the Deodex files for which you want to create files Odex
5. With an archiver to open our tool odexer_4_update_internal.zip: http://yadi.sk/d/ZLLm-1Qw2uNMF and on the way tmp / MOD add the Deodex file to the appropriate folder for which you want to make a file Odex
6. Exit from the archiver, go to CWM and install the resulting archive
7. After application of the archive in the internal memory card appears folder odexer, in which be necessary apk and odex and which is necessary to put a hands in system, framework and preload, because when they wrote the script, then the preload section has not yet been activated by the system
... shorter than anyone should, he will understand, good luck !
Click to expand...
Click to collapse

R: <req>Add toggles to stock LSZ
Klementiy said:
Instructions on how to make Odex:
1. For First you need to open an archive with modifications and see what sort of files
2. Look on your phone or at this address https://docs.google.com/folder/d/0B...ring&pli=1&docId=0B_tjIX7pV_liQjR3VGhoY0VMSWM which of these files have a second file Odex
3. Install this archiver https://play.google.com/store/apps/details?id=ru.zdevs.zarchiver ZArchiver.apk: http://yadi.sk/d/qhsL2d8n31-w8 and in the settings set compression "uncompressed"
4. From the archive with modifications extract the Deodex files for which you want to create files Odex
5. With an archiver to open our tool odexer_4_update_internal.zip: http://yadi.sk/d/ZLLm-1Qw2uNMF and on the way tmp / MOD add the Deodex file to the appropriate folder for which you want to make a file Odex
6. Exit from the archiver, go to CWM and install the resulting archive
7. After application of the archive in the internal memory card appears folder odexer, in which be necessary apk and odex and which is necessary to put a hands in system, framework and preload, because when they wrote the script, then the preload section has not yet been activated by the system
... shorter than anyone should, he will understand, good luck !
Click to expand...
Click to collapse
Thank you very much
Inviato dal mio GT-N8000 con Tapatalk 2

R: <req>Add toggles to stock LSZ
shardul_seth said:
Thanks a lot Klementiy. I went through odexer.sh, and it seems so simple now.
I can confirm that this works.. If someone want the CWM package for Odexed LSZ, I can post it here.
Click to expand...
Click to collapse
Do I understand right ? Is possible a zip file in order to add toggles by Klementiy way for odex LSZ stock rom ? I'd like it a lot!
Inviato dal mio GT-N8000 con Tapatalk 2

R: <req>Add toggles to stock LSZ
Sorry, I'm trying the klementiy way but I have some problem...For example: why is it necessary to check which files are there in my stock rom and where are they? How many LSZ are there? I thought only one from sammobile site...
Inviato dal mio GT-N8000 con Tapatalk 2

Instructions for installing mods for Odex-firmware:
1. Extract all apk and jar files from the archive for modding
2. Install this archiver ZArchiver: http://yadi.sk/d/gkKGRw3e3_lID and in his settings select the compression method "No compression"
3. With an archiver ZArchiver open archive odexer_4_update_internal.zip: http://yadi.sk/d/lkaVBHxc3_kkG and on the way: tmp/MOD to the appropriate folders to throw the files with modifications, You can throw in any number of
4. Exit from the archiver, go to CWM and install the resulting archive
5. After running the script on the internal memory card appears folder odexer with the new apk and odex files, which must be manually placed in folders on the device, do not forget to set the permissions and ownership are the same as in the original file
CAUTION:
1. This script was created when not yet used section preload, so the script does not know section preload, ready archives use only for sections system/app and system/framework, for working with the section preload/symlink/system/app use only hands
2. If you move any files to the section preload, do not forget to make sure that the system/app to these files have the proper labels symlink, if the symlink is missing, it can easily be created by using Root Explorer: http://yadi.sk/d/dWKFeyRX3_lEh
3. After all the manipulations with the replacement files do not forget to delete the folder: data/dalvik-cache and reboot the device

shardul_seth said:
Thanks a lot Klementiy. I went through odexer.sh, and it seems so simple now.
I can confirm that this works.. If someone want the CWM package for Odexed LSZ, I can post it here.
Click to expand...
Click to collapse
Thank you, can I have Ink Effect for LSB Stock ?

majdinj said:
Sounds silly but what if he just delete SystemUI.apk and SystemUI.odex, services.jar and services.odex files then flash the mentioned mod, will it be OK???
tbh, I didn't test this method, although it works in some other mods!!!
Click to expand...
Click to collapse
this will never work, cause you need the framework jar files completely odexed or deodexed - no mix possible (except some google or third party stuff also working as deodexed in an odexed version)...whereas it is no prob to have a mixture in apps with odexed and deodexed

" odexer_4_update_internal.zip"
Прикольно, у меня такой же есть

finist1 said:
" odexer_4_update_internal.zip"
Прикольно, у меня такой же есть
Click to expand...
Click to collapse
so this is you gave it to me

shardul_seth said:
Thanks a lot Klementiy. I went through odexer.sh, and it seems so simple now.
I can confirm that this works.. If someone want the CWM package for Odexed LSZ, I can post it here.
Click to expand...
Click to collapse
Hello shardul_seth
could you share the mod to add the airplane toggle for a stock rooted rom LSZ?
Thank you very much

ask
hai,.
any one have guide for add stock toggle for samsung 4.1.2 ???
help..

Need some help regarding Odex Files and corresponding apks

Hi guys, I got this problem in my odexed stock rom, I have this problem in sysui, gallery and calculator.
I downloaded 4.2.2 style sysUI, pushed it in the respective folder by replacing with its stock sysUI.
I rebooted my core, the statusbar was gone, so I deleted 'SystemUI.odex" file, then rebooted it worked!
In the same way, I replaced stock gallery with note3 gallery, and stock SecCalculator2
Luckily note3 gallery worked, but it doesn't support Sim2 so I can't change Sim2's wallpaper or make it same as Sim1's.
In the statusbar, I can't see most notification cuz its completely transparent, and also its a bit laggy.
Calculator never worked
So I wanted to replace these with stock, when I pushed it in system>apps> I noticed that there were no .odex files for .apks
I replaced them with their stock odex files, none of 'em worked, I guess cuz of the odex thing, so I again deleted odex files and rebooted, nothing worked..
Now, I need some developer's advice, plz don't tell me to "Flash Stock Rom via Odin" I can't do it...
Is there any other left way to make them work plz I need help..

You are saying 'in my deodexed rom' and then you said 'deleted. Odex file for systemUI'
How could this be possible?
If you have .Odex files in system/apps folder then your ROM is not odexed.
Deodex it first using xUltimate tool
And yup Don't forget to set permissions = rw--r--r--

M_E_G_A_T_R_O_N said:
You are saying 'in my deodexed rom' and then you said 'deleted. Odex file for systemUI'
How could this be possible?
If you have .Odex files in system/apps folder then your ROM is not odexed.
Deodex it first using xUltimate tool
And yup Don't forget to set permissions = rw--r--r--
Click to expand...
Click to collapse
Sorry bro, huge typo. I meant in my odex rom and yes I set the proper permissions...

Well, it seems to me that you have messed up your phone alot.. Flashing stock rom via odin would've been the correct solution to this problem. It's not as difficult as you think, and you're capable of doing it. Follow thecoreguy's tutorial for that.

CoreGuy said:
Sorry bro, huge typo. I meant in my odex rom and yes I set the proper permissions...
Click to expand...
Click to collapse
Then you have done wrong.
Not every apk can be used by just deleting the .odex file.
You need to deodex the apps in system/app and system/framework folder then you can easily replace the apks.
1.First restore back to any working backup.
2.Download xUltimate Tool.
3. Run it.
4. Then just run commands with options 1,2,3,4 (You just need to type 1 and then enter, then 2 and then enter, so on upto option 4.)
5. Exit after executing 4th option.
6. Download ADB tool(don't download the complete package, you will get a 1-2MB ADB.exe from the from itself) - Use it to push the deodexed files made from xultimate.
---------- Post added at 09:47 AM ---------- Previous post was at 09:22 AM ----------
If you find it difficult then Better you upload the apks with their respective odex file. I will deodex those apks

M_E_G_A_T_R_O_N said:
Not every apk can be used by just deleting the .odex file.
Click to expand...
Click to collapse
Not even the stock apks? I want to replace the ported/modded apks with the stock ones..

No you can't because almost all stock apks have their respective odex files and every odex file contains resources that are needed to run those apks. Also there exists dependencies in system/framework folder. So just deleting odex file won't work all time.

Finally got it! Special thanks to megatron
Solution if u r screwed in my situation: don't panic, what I found why I cant do it was bcuz my phone has dat "newest" update of samsung ota. So b4 u take someone's apk and odex file always cross check this(image)
And then you are gud to go!!! U wont even need to restart it'll come automatically(my dad has same phone and same updated version as mine so I copied everything needed frm his phone to mine) @AnsleyC at times, the answer should not be "flash stock rom via ODIN" if u have a crappy pc, u can either repair faulty parts(easier and efficient) or buy a new one(bullcrap)
Have fun everyone!
Sent from my GT-I8262 using XDA Premium 4 mobile app