Database Develop

[Q] manually deodexed and compressed apk's make bootloop

Hello,
I tried manually deodexing my /system/framework and /system/app with xUltimate according to this:
http://forum.androidcentral.com/mot...cks/30539-how-manually-deodex-your-phone.html
Now this has worked fine and I can also boot my phone fine with the deodexed files. But there is also on option in xUltimate to compress/optimize the apk files. If I do that and flash my phone with the compressed files, I get into a bootloop.
The compression seems to save a total of 20MB of space (from 103MB to 84MB) and I hope this could give the device a small speed improvement, but I just can't seem to get it to work.
I also know that there are ROMs out there that have all the files deodexed, but in 90% of cases these files are also modified (custom themes and whatnot) and I don't like that, I would just want a vanilla deodexed ROM so that I can make changes myself if I want to.
I have also searched the forum for 'xultimate' but couldn't find any hit. What are other people using to deodex/optimize/zipalign their ROMs? Are there any better utilities out there?
I'd be very thankful for any tips/tricks.
Thank you!

without odex

I am using the GT540 with 2.1 rom
i want delete in the system/app-> odex files
but when i delete any odex files
app does not work
examples
delete system/app-> music.odex... music does not work
There are some applications run with odex
some applications run without odex (example lgecamera.apk)
I would like in working without odex every app on 2.1
how do I
please help
Thank you for answers
I'm sorry for my English

I think first you need to understand the concept of ODEXing. In stock LG roms the system applications are Odexed. "ODEX" stands for Optimized DEX - Classes.dex is usually a file that stands inside the apk file of any application. When a program is odexed the file is extracted from the apk, optimized, and saved alongside the application in the odex format. However, since the apk no longer contains its (albeit optimized) classes, deleting the odex file leaves the application broken and unusable, until you reinstall it again. Now, I can think of only one way to deodex right now, but I really don't think it's a good idea(The rom i'm using was deodexed, yet I odexed it intentionally). What you need to do is:
1. Make a backup of your phone using clockworkmod recovery
2. From that backup take system.img and boot.img
3. You will need to download and run Android Kitchen. Since it's a Linux program, you'll need that as well. Look into it.
4. Insert the 'boot' and 'system' img files into the kitchen, and use the deodex option, then export the rom as update.zip
5. Put the file in your sdcard, boot into recovery, and format system
6. Choose 'install update.zip', and install the one you've created
7. From 'Advanced' menu clean Dalvik-Cache, and see if the phone works now.
While this *should* work *in theory*, as far as I know using a backup to modify it in the kitchen doesn't always work. Also, since I imagine some of your system apps are now broken, what I told you to do should be done after first reinstalling the rom in some way, in order to get your apps straight.
Well, I hope I've been helpful. Good luck.

if I'm not wrong there should be a script somewhere i the forum

bs828 said:
if I'm not wrong there should be a script somewhere i the forum
Click to expand...
Click to collapse
For deodexing? There's one for odexing, but I'm not sure about the opposite one. I'll do a search. Besides, some of his system apps are already screwed up, so I doubt that will help.

This kitchen can run on Cygwin (author mentioned it)

nutterbg said:
I think first you need to understand the concept of ODEXing. In stock LG roms the system applications are Odexed. "ODEX" stands for Optimized DEX - Classes.dex is usually a file that stands inside the apk file of any application. When a program is odexed the file is extracted from the apk, optimized, and saved alongside the application in the odex format. However, since the apk no longer contains its (albeit optimized) classes, deleting the odex file leaves the application broken and unusable, until you reinstall it again. Now, I can think of only one way to deodex right now, but I really don't think it's a good idea(The rom i'm using was deodexed, yet I odexed it intentionally). What you need to do is:
1. Make a backup of your phone using clockworkmod recovery
2. From that backup take system.img and boot.img
3. You will need to download and run Android Kitchen. Since it's a Linux program, you'll need that as well. Look into it.
4. Insert the 'boot' and 'system' img files into the kitchen, and use the deodex option, then export the rom as update.zip
5. Put the file in your sdcard, boot into recovery, and format system
6. Choose 'install update.zip', and install the one you've created
7. From 'Advanced' menu clean Dalvik-Cache, and see if the phone works now.
While this *should* work *in theory*, as far as I know using a backup to modify it in the kitchen doesn't always work. Also, since I imagine some of your system apps are now broken, what I told you to do should be done after first reinstalling the rom in some way, in order to get your apps straight.
Well, I hope I've been helpful. Good luck.
Click to expand...
Click to collapse
Thank you for your excellent explanation
definitely going to try them
but where do I find Android kitchen for the GT540
and the running xp or win7?
Can you give the web address?
thanks a lot.

Here you are
http://forum.xda-developers.com/showthread.php?t=633246
You can use kitchen on Windows thanks to Cygwin .
Wystukane z mojego Swifta przy użyciu Tapatalk.

[Q] Odexed o deodexed

I Have read a lot of info about odexed and deodexed ROMS. but still (and maybe cause I don't understand a lot of technicalities) I don't get, WHICH IS BETTER? and WHY?
odexed o deodexed????
If u can explain it in simple in words would be better, and sorry for asking a lot!

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.
THEN COMES DEODEX
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.
Click Below link for Complete Guide.
http://www.addictivetips.com/mobile/what-is-odex-and-deodex-in-android-complete-guide/

[Q] How to make Custom Rom ?

Did anyone has tried the dsixda Android Kitchen to make a custom rom for OB ? Is it working ?
http://forum.xda-developers.com/showthread.php?t=633246
or just give me a link to very helpful site about how to make custom rom for OB

For starters, yes it works. but nothing compares as to compiling and building from source (Linux).
What you need is a mere system dump or backup from CWM.
That backup will be saved in your CWM folder in SD
Grab the boot.img & system.ext3.tar
unpack the .tar with a zip/RAR propgram
grab a base upater script from the many ROMs around here
Now for a start:
your base ROM like Zeus etc.
Delete the system folder and boot.img from that zip.
Replace files.
Use dsixda kitchen via cygwin (windows)
Now do as you please... it can unpack boot.img and add features like init.d etc.
Adding apps:
Apps can be added together with som libs (system/lib). Example: Terminal Emulator. the lib is some "jackpal" or something. .
When you download an app, apk will be saved in data/app in your phone. The lib or added files will be saved in data/data/(app name folder)/lib. Grab the apk and insert in system/app (kitchen's working folder). Grab the lib and insert it in system/lib (kitchen's working folder).

gabwerkz said:
For starters, yes it works. but nothing compares as to compiling and building from source (Linux).
What you need is a mere system dump or backup from CWM.
That backup will be saved in your CWM folder in SD
Grab the boot.img & system.ext3.tar
unpack the .tar with a zip/RAR propgram
grab a base upater script from the many ROMs around here
Now for a start:
your base ROM like Zeus etc.
Delete the system folder and boot.img from that zip.
Replace files.
Use dsixda kitchen via cygwin (windows)
Now do as you please... it can unpack boot.img and add features like init.d etc.
Adding apps:
Apps can be added together with som libs (system/lib). Example: Terminal Emulator. the lib is some "jackpal" or something. .
When you download an app, apk will be saved in data/app in your phone. The lib or added files will be saved in data/data/(app name folder)/lib. Grab the apk and insert in system/app (kitchen's working folder). Grab the lib and insert it in system/lib (kitchen's working folder).
Click to expand...
Click to collapse
many thanks gabwerkz. I had been searching ebook The Complete Idiot's Guides to custom rom, but I think the book has not published yet.

I only once tried to cook with kitchen, but that's waaaaay back and there I simply had no clue, of what I am doing and those days, the cust ROM I made, didnt work, but I simply randomly applied mods/tweaks and also had no clue of how things like updater-script work, but now I do and maybe as soon as I got some time again (in about 2 months ) I'll give it another shot and also read a lot about deving on my own and all the stuff related to it. Then maybe I'll be able to help all the cookers here out in a better way, cause until now, I only got the basics
You can start with simply things, like extracting the files with a packer, remove LG bloatware, add files/patches, you can find in dev section, add apps you like and think others might like as well, change lockscreen, launcher, keyboard,...
Remember to always do this step by step and make a changelog for yourself, so you know, where you might have made a mistake (also important for others to be able to help you). Then repack your ROM, sign and test it, if it works properly, use kitchen, to zipaligne, deodex, change filesystem,... And as soon as you are satisfied, post it/PM the good ones in here, to test it and ask for opinions, what you might change next. Custom kernels are always cool, cause you can change way more, like governors, iosched,... But that will take more time to dev and a lot more time to test for errors
Hope this helps you out a bit

N00BY0815 said:
I only once tried to cook with kitchen, but that's waaaaay back and there I simply had no clue, of what I am doing and those days, the cust ROM I made, didnt work, but I simply randomly applied mods/tweaks and also had no clue of how things like updater-script work, but now I do and maybe as soon as I got some time again (in about 2 months ) I'll give it another shot and also read a lot about deving on my own and all the stuff related to it. Then maybe I'll be able to help all the cookers here out in a better way, cause until now, I only got the basics
You can start with simply things, like extracting the files with a packer, remove LG bloatware, add files/patches, you can find in dev section, add apps you like and think others might like as well, change lockscreen, launcher, keyboard,...
Remember to always do this step by step and make a changelog for yourself, so you know, where you might have made a mistake (also important for others to be able to help you). Then repack your ROM, sign and test it, if it works properly, use kitchen, to zipaligne, deodex, change filesystem,... And as soon as you are satisfied, post it/PM the good ones in here, to test it and ask for opinions, what you might change next. Custom kernels are always cool, cause you can change way more, like governors, iosched,... But that will take more time to dev and a lot more time to test for errors
Hope this helps you out a bit
Click to expand...
Click to collapse
Your post help me a lot... thanks... I will try what you told me todo...
And If your rom need a bootanimation just PM me right...

[Q] How exactly does flashing work?

Hi all,
My question is aimed to head deep into the Android OS and the flashing process itself. I know that if I flash my phone with a new ROM that system files are replaced and also some other files too. My question is how is this done? Is there an exact order in which the files have to be replaced, and are they "just" overwritten or are they deleted first and then the new ones put in place?
Forgive me if this question has already been answered. I really tried my best to find answers on Google and in here.
Thanks in advance for any enlightening comment.

Open up an update-script and your dilemma will be solved
Sent from my GT-I9000 using Tapatalk

Essentially, like the previous reply mentioned the android OS is heavily partitioned, but has a lot of sneaky mount points to hide this fact.
Really all a CWM flashable zip does is follow a script, easily readable in the zip, to copy files throughout the OS partition.
If you look in the zip you'll see a few things, the biggest thing here is the /System folder. It contains the entirety of the system partition that makes your ROM /Your ROM/. Also you'll see boot.img which is the kernel (and CWM). A modem.bin file is also present, but to my understanding is only flashed if one is not currently present.
When looking at CM9's zip, you'll see an updater.sh. This is the shell script that's run on using CWMs install function.
It's process checks a few environment things and installs (copys over /system) based on this.
Check out the script, it's really interesting.

Thanks to all of you
I will have a look inside a script then.