Related
Based on I9003XXKB3 firmware, I made this mod also for our phone...
How to install:
- unpack the archive and copy the two folder to sdcard ( you must have /sdcard/done_app and /sdcard/done_frame)
- with you pc get an adb shell and type:
su
mount -o remount rw /system
rm /system/app/*.odex
cp /sdcard/done_app/* /system/app
rm /system/framework/*.odex
cp /sdcard/done_frame/* /system/framework
reboot
Important:The first time the phone maybe won't boot so: unplug the battery and restart...and be patient!
DOWNLOAD HERE
P.S.: for the people that don't like the deodexed app but that have the I9003XXKB3 firmware installed I post also an archive with two files. Simply overwrite the originals in /system/framework/ (also with root explorer)and reboot. The first time the phone maybe won't boot so: unplug the battery and restart...and be patient!
EDIT: The two files contain a mistake so i removed they... sorry.... only apply the first guide!
Let me know what you think.... bye
Ohhh... Basically its a deodexed apk and jar with a different lock screen. I too have deodexed my fw xxkb3. But for Lock screen you can get applications from market. No offence, I respect your work, its a good beginning. Sorry, but I thought initially its with vanilla kernel.
Sent from my GT-I9003 using XDA Premium App
Skin1980 said:
P.S.: for the people that don't like the deodexed app but that have the I9003XXKB3 firmware installed I post also an archive with two files. Simply overwrite the originals in /system/framework/ (also with root explorer)and reboot. The first time the phone maybe won't boot so: unplug the battery and restart...and be patient!
Let me know what you think.... bye
Click to expand...
Click to collapse
I've tried odexed android.policy and now I'm reflashing phone: It became always rebooting during the boot.
falex007 said:
I've tried odexed android.policy and now I'm reflashing phone: It became always rebooting during the boot.
Click to expand...
Click to collapse
You have a risk of boot loop with Framework related files if there is any incompatibility or improper file replacement. Any time you try such items be ready to reflash. What is your Firmware? Is it XXKB3? If yes then it should work as per Skin 1980, but it wont work on other firmware unlike system/app apks.
trip007in said:
You have a risk of boot loop with Framework related files if there is any incompatibility or improper file replacement. Any time you try such items be ready to reflash. What is your Firmware? Is it XXKB3? If yes then it should work as per Skin 1980, but it wont work on other firmware unlike system/app apks.
Click to expand...
Click to collapse
Yes. I have XXKB3. And I am not afraid to reflash I did this several times (first to upgrade from XXKB1, then to remove OCLFv1, and so on ) All my settings/applications are saved to Dropbox with help of Titanium backup
Nice work dude
Thanks a lot. Deodexed applications works well. Also I like standard lock screen
Please fix your instruction:
cp /sdcard/done_frame /system/framework
to
cp /sdcard/done_frame/* /system/framework
BTW After start it showed 318M of free memory, with standard fw I saw ~270M. But I thought that it should use more memory (not lesser). This is strange for me
falex007 said:
Thanks a lot. Deodexed applications works well. Also I like standard lock screen
Please fix your instruction:
cp /sdcard/done_frame /system/framework
to
cp /sdcard/done_frame/* /system/framework
BTW After start it showed 318M of free memory, with standard fw I saw ~270M. But I thought that it should use more memory (not lesser). This is strange for me
Click to expand...
Click to collapse
Thanks.... I have edited the post....
Can you upload to multiupload
megaupload block my area...
Dello i see from the snapshot that you are italian... It istituto true?you have problems with xx b3 deodexed or not ? How is gps working ?
Inviato dal mio GT-I9003 usando Tapatalk
Hi!
I am on ddkb2 and just want the lockscreen! What do i exactly have to do to just get the vanila lockscreen
Thanks dude, used your framework files for the vanilla lock. But why did you remove those framework.apk files? I noticed those missing files during flash and added my own deodexed apks. Worked great.
Sent from my GT-I9003 using XDA Premium App
I don't remove framework-res.apk.... simply it cannot be deodexed cause it doesn't have odex file.... correct me if i'm wrong
trip007in said:
Thanks dude, used your framework files for the vanilla lock. But why did you remove those framework.apk files? I noticed those missing files during flash and added my own deodexed apks. Worked great.
Sent from my GT-I9003 using XDA Premium App
Click to expand...
Click to collapse
Sent from my GT-I9003 using XDA App
Update to kb3, root your device and follow the guide on the first post... pm if you need help..... bye
ritvik93 said:
Hi!
I am on ddkb2 and just want the lockscreen! What do i exactly have to do to just get the vanila lockscreen
Click to expand...
Click to collapse
Sent from my GT-I9003 using XDA App
Who said no odex files dude? just check the stock firmware or ask someone who is running stock firmware to check in the /system/framework. There are 24 files after deodexing the framework folder, before deodexing you have 46 files. Attached screen shot here. I have highlighted the apk and corresponding odex files from framework folder.
Skin1980 said:
I don't remove framework-res.apk.... simply it cannot be deodexed cause it doesn't have odex file.... correct me if i'm wrong
Sent from my GT-I9003 using XDA App
Click to expand...
Click to collapse
Please.... check inside the related jar file on my deodexed file and you will find where the odex is....tell me if i'm wrong
Sent from my GT-I9003 using XDA App
Skin1980 said:
Please.... check inside the related jar file on my deodexed file and you will find where the odex is....tell me if i'm wrong
Sent from my GT-I9003 using XDA App
Click to expand...
Click to collapse
No dear, I am talking about the two apk files in framework folder which are not included in the jar folder. framework-res.apk and twframework-res.apk are the two files. If you are using the application Deodexer_2_3 for deodexing framework files, it creates two folders one for jar files as deodex_jar and another for apk files as framework. Just check in the that folder you will find them.
When I transferred those deodexed files to /system/framework from downloaded files uploaded by you. I used an adb command
Code:
rm /system/framework/*.odex
. This means my system will never reboot without those odex files of above mentioned apks, if did not replace them with deodexed ones. Hope I am clear now. If you guys check in your framework folder you will find two odex files which you have not replaced. Please dont take is as an offense, I love your work.
What i wrote in the first post is what i've done on my phone that works correctly.... sure that the files i attached are not all the files that must be in the system and framework folders.... this because it's simply an "update" to stock rom.
Another thing... no problem with you my friend... we are working all for the same result...
P.s.: framework-res.apk and the other cannot be deodexed i supposed cause the related odex files will be put by the deodex-software into the related .jar files.... check into your framework-res.apk .
Sent from my GT-I9003 using XDA App
No dear, I am sorry to say but you are wrong here. every .apk and jar has their own odex files so the odex resides inside the respective apk or jar file that it belongs to after deodexing them. If you want I can attach those two deodexed framework apk files, which should go into /system/framework folder along with remaining jar files, (without their odex files). Will post tomorrow morning here you may link them to the main post, if you feel so. If I do something, I am never satisfied by incomplete job.
Skin1980 said:
What i wrote in the first post is what i've done on my phone that works correctly.... sure that the files i attached are not all the files that must be in the system and framework folders.... this because it's simply an "update" to stock rom.
Another thing... no problem with you my friend... we are working all for the same result...
P.s.: framework-res.apk and the other cannot be deodexed i supposed cause the related odex files will be put by the deodex-software into the related .jar files.... check into your framework-res.apk .
Sent from my GT-I9003 using XDA App
Click to expand...
Click to collapse
trip007in said:
No dear, I am sorry to say but you are wrong here. every .apk and jar has their own odex files so the odex resides inside the respective apk or jar file that it belongs to after deodexing them. If you want I can attach those two deodexed framework apk files, which should go into /system/framework folder along with remaining jar files, (without their odex files). Will post tomorrow morning here you may link them to the main post, if you feel so. If I do something, I am never satisfied by incomplete job.
Click to expand...
Click to collapse
Maybe i don't explain myself very well... tomorrow i will try to explain better what i'm saying... see you!
Sent from my GT-I9003 using Tapatalk
No one seemed to wanna help me so I had to figure this out myself
Started with the Europe RUU and patched the files from the OTA zip posted earlier today, rooted, the whole 9 yards.
What you get:
1.45.401.2 Android 2.3.4
disabled boot sound (I had to, sorry!)
rooted & busybox installed
odexed
unsecure boot.img
love
Deodexed version comes with all of the above plus:
busybox runparts support (init.d)
/data/app enabled
nano & bash shell
deodexed
extra love
Older kernels do not seem to work (2.3.3 ones), so you will have to stick with this stock kernel for now. I have a TMO US Sensation and everything seems to be working fine on my end (I AM running the new radio, btw).
Flash with CWM.
Note for odexed ROM!! - I mucked up the Settings.apk and included a wrong one. The correct files are in there but need to be renamed before you flash, or flash the file I linked below IMMEDIATELY after you flash the ROM (before rebooting). Deodexed version is unaffected. Sorry for the trouble!
Download Odexed -d40386a3258546ee1bd760588007d2bd
Odex Settings Flashable fix - flash immediately after
Downdload Deodexed - 71aeba2d1ae00813458b78bda5c188a0
Deodex Flashable Settings.apk fix - or just push this Settings.apk
Instructions for those not so sure which to download:
Download deodex version
Download Deodex Settings.apk flashable right below it
Place both on SD
reboot to recovery and make a nandroid backup
wipe dalvik cache (and data if you choose, I recommend doing so)
flash deodex
flash settings.apk fix
reboot
Nice one man, will be helpfull to many
yah now all will make a super mega uber fast .... rom
thanks for release, users who like all stock will be happy
Bug
(Do NOT Flash this ROM!) - FIXED
There is no Settings application!!!!!!!!
And in Menu also!!!
Am I missing something? What's so good about this. o_o
Good things ahead.
Great work. How did you apply the OTA patch "HTC_Europe_1.45.401.2-1.35.401.1" to "HTC_Europe_1.35.401.1" ?? Did you update your phone then backup and used that in the kitchen ?
Thanx
There is no settings app. Attempting to start settings from the status bar crashes the status bar process...
Nice :\
Flashed with CWM.
zmfl said:
There is no settings app. Attempting to start settings from the status bar crashes the status bar process...
Nice :\
Flashed with CWM.
Click to expand...
Click to collapse
+1 Same prob.
It's unanimous. Settings are missing.
Sent from my GT-P1000 using XDA Premium App. Waiting for my phone to restore.
Sorry fellas, was experimenting with one and forgot to get rid of it, you can run the following commands to get it back (it should be on your phone, I just renamed it, look at the zip ).
Open up your zip and delete Settings.apk in /system/app and rename Settings.apk.bak to Settings.apk and then rename Settings.odex.bak to Settings.odex then flash away.
Or the hard way:
Code:
roman$ adb remount
remount succeeded
roman$ adb shell
sh-3.2# cd /system/app
sh-3.2# rm Settings.apk
sh-3.2# mv Settings.apk.bak Settings.apk
sh-3.2# mv Settings.odex.bak Settings.odex
roman$ adb reboot recovery
**wipe dalvik cache in recovery**
reuploading a newer version.
teshxx said:
Great work. How did you apply the OTA patch "HTC_Europe_1.45.401.2-1.35.401.1" to "HTC_Europe_1.35.401.1" ?? Did you update your phone then backup and used that in the kitchen ?
Thanx
Click to expand...
Click to collapse
Ripped the patch zip apart, took out any references to firmware, flashed the patch file upgrade.
In the firmware.zip were the boot.img & radio.imgs i flashed among other things I was way too scared to touch
So any "reviews" on 2.3.4, is battery life better? Anything new?
Also a question.
If I install this, would I be able to extract my backup rom of Anroid Revolution and take the apps out aswell as other things like contacts and just slap em on my SD card or in System/apps and have it all work again?
willhub said:
So any "reviews" on 2.3.4, is battery life better? Anything new?
Also a question.
If I install this, would I be able to extract my backup rom of Anroid Revolution and take the apps out aswell as other things like contacts and just slap em on my SD card or in System/apps and have it all work again?
Click to expand...
Click to collapse
Just do a nandroid backup before, flash over, if you get no issues, great! If you start seeing issues, nandroid back, or do a /data wipe in recovery. But theoretically you should be able to.
Deodexed version is also up. flashed and seems to be working great.
birgertime said:
Just do a nandroid backup before, flash over, if you get no issues, great! If you start seeing issues, nandroid back, or do a /data wipe in recovery. But theoretically you should be able to.
Deodexed version is also up. flashed and seems to be working great.
Click to expand...
Click to collapse
I did it! Just flashed it over my old ROM and it worked like an update. Settings working, probably because old ones weren't overwritten. I'm gonna keep using it and report any problems.
Also I used root explorer to fix settings.
Sent from my GT-P1000 using XDA Premium App. Phone is restored.
You sure it'll work ok?
I've got Android Revolution HD with No Sense (So all HTC Sense is removed)
Still safe to just flash over?
It worked for me. I flashed over training wheels.
Sent from my HTC Sensation Z710e using XDA Premium App
willhub said:
You sure it'll work ok?
I've got Android Revolution HD with No Sense (So all HTC Sense is removed)
Still safe to just flash over?
Click to expand...
Click to collapse
Honestly no, but theoretically it SHOULD work. Do a nandroid, and then you have nothing to be scared of .
birgertime said:
Sorry fellas, was experimenting with one and forgot to get rid of it, you can run the following commands to get it back (it should be on your phone, I just renamed it, look at the zip )
Code:
roman$ adb remount
remount succeeded
roman$ adb shell
sh-3.2# cd /system/app
sh-3.2# rm Settings.apk
sh-3.2# mv Settings.apk.bak Settings.apk
sh-3.2# mv Settings.odex.bak Settings.odex
sh-3.2# reboot
reuploading a newer version.
Click to expand...
Click to collapse
Since I have to re-flash I renamed the files within the zip. Let's see if it works
Also, is it safe to just remove a couple of files from the zip? I'm thinking about bloatware naturally...
It might be a silly question, but I've never messed with roms before
i dont like you and all but thanks.
odex ROM - faster boot, a little snappier and faster, but unthemeable
deodex ROM - customization (tweaks, themes ,fonts, etc.), more space in system, but slower
it will ODEX on fase 1 /system/framework and /system/app
it will ODEX on fase 2 /data/app [optional]
ON WINDOWS (unzip odexVlad_v14.zip on windows)
Instruction: (windows and unix bash script ) (will use adb)
1. Run (run just ONE of this 4 scripts)
......... 1odex.cmd ------- for 2.3.5 roms
......... 1odex-2.cmd ---- for 2.3.5 rom insertcoin
......... 1odex-3.cmd ---- for 2.3.5 rom stock
......... 1odex-234.cmd - for 2.3.4 roms
2. Run 2odex.cmd [optional] [this script will only odex deodex apks, so you can run many times you wanna]
My script will reboot the sensation to recovery
Click to expand...
Click to collapse
ON SENSATION TERMINAL (flash odexVlad-TERM_v14.zip on CWM)
Instruction:
1. Set your screen timeout to "Never turn off"
2. Run /system/odexVlad/ (run just ONE of this 4 scripts)
.................................... odex11.sh ------ for 2.3.5 roms
.................................... odex11-2.sh ---- for 2.3.5 rom insertcoin
.................................... odex11-3.sh ---- for 2.3.5 rom stock
.................................... odex11-234.sh - for 2.3.4 roms
3. Run /system/odexVlad/odexb11.sh [optional] [this script will only odex deodex apks, so you can run many times you wanna]
Click to expand...
Click to collapse
Once done clean your dalvik-cache directory and reboot.
or reboot to recovery and wipe dalvik-cache
APPs THAT DON'T WORK ODEXED
-rootexplorer
-bejeweled 2
Click to expand...
Click to collapse
TESTED ROMs
-Pyramid3D_v8.2.0_XE
-Synergy r93
-InsertCoin
-RCMix_3.5_v09
-HTC Sensation 2.08.401.1 | Stock
Click to expand...
Click to collapse
Hi , So did you create the script or you just share the idea or...?
Edit : its OK , now the OP is completed ,my bad hehe..
so is this an init.d script?
Used something very similar for the Classic Desire "No A2SD" versions, very handy imo, although it does make things a little restrictive
Sent from my LeeDrOiD loaded s-off HTC EVO 3D
you can run this script on terminal or with a script runner app
LeeDroid said:
Used something very similar for the Classic Desire "No A2SD" versions, very handy imo, although it does make things a little restrictive
Sent from my LeeDrOiD loaded s-off HTC EVO 3D
Click to expand...
Click to collapse
Hi Lee , pleasure to see you dude . its been a long time.
vladnosferatu said:
you can run this script on terminal or with a script runner app
Click to expand...
Click to collapse
ahh thankyou
probably a noob question, but is dexopt-wrapper a script in a toolkit or SDK somewhere or is it contained in every Android installation and can this be done from ADB?
dipje said:
probably a noob question, but is dexopt-wrapper a script in a toolkit or SDK somewhere or is it contained in every Android installation and can this be done from ADB?
Click to expand...
Click to collapse
its a bin file located on /system/xbin/
"a little snappier" is incorrect because the /system and /data partitions are on the same chip in our device and use the same filesystem; there is no difference where the odex files are.
the only things affected will be boot time and themability.
jcarrz1 said:
"a little snappier" is incorrect because the /system and /data partitions are on the same chip in our device and use the same filesystem; there is no difference where the odex files are.
the only things affected will be boot time and themability.
Click to expand...
Click to collapse
on my device is faster with odex apks and jar
I'm getting a syntex error while trying to do this and this is for the first line of code
odex=`echo $i | sed -e 's/.apk/.odex/g'`
Am I doing something wrong.
Nevermind I didn't add in "do" I got it. But the Rom I'm running doesn't have dexopt-wrapper can you supply it.
Sent from my HTC Sensation Z710e with Beats Audio using xda premium
vladnosferatu said:
you can run this script on terminal or with a script runner app
Click to expand...
Click to collapse
So do we just copy and paste it in terminal emulator? Sorry if I sound like I don't know what I'm talking about. I don't know but I'd want my device faster.
d3vilskid said:
I'm getting a syntex error while trying to do this and this is for the first line of code
odex=`echo $i | sed -e 's/.apk/.odex/g'`
Am I doing something wrong.
Nevermind I didn't add in "do" I got it. But the Rom I'm running doesn't have dexopt-wrapper can you supply it.
Sent from my HTC Sensation Z710e with Beats Audio using xda premium
Click to expand...
Click to collapse
i'm upgrading the script, i will add the dexopt-wrapper, give me same time
wotking on odexing the java files
I just ran the script on InsertCoin 3.3.9 but I don't see any difference..
can someone guide how it works practically*
Found the solution to ODEX the system/framework,
now i have to make a easy friendly script...
give me some time please ...
vladnosferatu said:
i'm upgrading the script, i will add the dexopt-wrapper, give me same time
wotking on odexing the java files
Click to expand...
Click to collapse
Thanks, I've been a fan of odex roms
Sent from my HTC Sensation Z710e with Beats Audio using xda premium
SCRIPT ON POST #1
Code:
Instruction: (windows and unix bash script ) (will use adb)
1. Run 1dex.cmd ( will odex /system/framework and /system/app )
2. Run 2dex.cmd ( will odex /data/app ) optional rootexplorer will not work odxed
My script will reboot the sensation to recovery
Once done clean your dalvik-cache directory and reboot.
or reboot to recovery and wipe dalvik-cache
add a script to run on phone terminal
Error run is not a command via terminal
Sent from my HTC Sensation Z710e with Beats Audio using xda premium
I made a tutorial for other devices here http://forum.xda-developers.com/showthread.php?t=1500475
Why this tutorial?
I wanted a good odexed rom, but there isn't any here. So I tried to make my own odexed rom, but it wasn't so good. So I read something about re-odexing and tried it out. I modified it a little bit and I don't know all about re-odexing, so if someone know something better, pls post it here in the thread for everyone. Im working also on this thread, so I'll try to make few things like a flashable update.zip who executes the script. English is also not my mother language, but I hope you'll understand me
What is a odexed and a deodexed rom?
When you look at a stock rom in the folder /system/app, you will see files with the ending .odex and the apks doesn't contains classes.dex files. When you look at a deodexed rom, you'll see that there are no .odex files and the apks contains classes.dex files. Basically every apk contains a classes.dex files. Then the dalvik virtual machine generates a dalvik cache based of the classes.dex file. When you load a app, it will be loaded from the the dalvik cache, not from the apk. Samsung built the odexed rom using a tool called dexopt-wrapper. This tool generates .odex files based from the classes.dex, that means it does the same job like the dalvik vm. The .odex files were pushed in the /system. The files are the replacement for the dalvik cache. Like I wrote above, apps are loading from the dalvik cache, not from apk or classes.dex file, so classes.dex are not needed anymore, so they are deleted in odexed roms. Deodexing using xUltimate means regenerating a classes.dex based from the .odex file, merging it into the apk and deleting .odex.
What are the advantages and disadvantages from a deodexed rom?
Advantages:
-All needed things are in one apk, so modding/theming is (better) possible
-Needs less space on /system
Disavantages:
-Needs more space on /data, you have on some roms only 110/170 mb free(because a deodexed rom needs a dalvik cache for system apps and frameworks
-Is not so stable than a odexed rom(because some moves dalvik cache to a low end sdext)
-Slower on first boot(because a odexed rom has already execute ready .odex files, a deodexed rom needs to generate dalvik cache)
Why should I re-odex?
I wanted this, because I use ~100 apps and I have a slow sd card, so moving /data/app and /data/dalvik cache to sdext made my system unstables, which was needed to run ~100 apps on a deodexed rom. But when I tried it on a odexed rom, I had only to move /data/app to sdext. So I used long time Stock rooted JPU. But the system was not so fast than on any other custom rom and I hated the stock theme. So If you want more space on /data and you don't want to try out new themes, you should probably try re-odexing.
What do I need to re-odex?
-A full NANDroid Backup
-More than 30 mb free space on /system
-ADB drivers for Option 1
-Titanium Backup Pro for Option 2
How can I re-odex a Rom?
There are 2 Options to do it, but only the first does a full re-odex.
Before doing anything make sure that you have a full NANDroid Backup because you'll propably get into a bootloop.
Option 1 using dexopt-wrapper:
I used first the script from puppet13th, but I got into a bootloop. So I corrected the $BOOTCLASSPATH and corrected permissions, but I got also into a bootloop. I compared the re-odexed Kyrillos Rom v9.3 framework with the framework from JPU. The difference was that Kyrillos Rom v9.3 Framework files android.policy.jar and services.jar doesnt contained the Meta-Inf.
Step 1: Check jars
Pull all your framework .jars using this adb command to your computer
Code:
adb pull /system/framework
and open them in WinRar or sth and check that they contains the Meta-Inf folder. If some file doesnt contain a Meta-Inf folder, I attached all jars from Stock JPU, so you can add the Meta-Inf folder from them. When you are done with adding Meta-Inf Folder to one file, you can push it to the system using this adb command(services.jar is only for example, use your filename):
Code:
adb push services.jar /system/framework
Some users told me that you can re-odex the rom without being in CWM, so you can may skip Step 2, but you could get into a bootloop without Step 2, but you can try it out, there is no risk with a NANDroid backup
Step 2(optional): Reboot your phone into cwm recovery and get adb access there
I never got adb access in windows, but i got always access with linux. If you also don't get access on Linux, you should try to reboot your phone and to select then recovery in the extended power menu, this gaves me always adb access.
Step 3: run reodex script
I attached a script, which push a script and needed binaries over adb to the phone. Then it executes the pushed script, which creates odex files and removes classes.dex from apks or jars and rezipaligns apks and deletes the dalvik cache.
For windows users: double click on odex.cmd
For linux users: open a terminal and navigate to the folder which contains the unzipped attachment and run
Code:
chmod +x reodex.sh
./reodex.sh
After its finished, simply reboot and enjoy your fully re-odexed rom.
Step 4 (optional) convert /data:
I dont know if there is a better option, but after a re-odex with Option 1, my phone didnt showed the right free space on /data. So I converted /data to a other filesystem and back and then it showed the right free space.
Option 2 using Titanium Backup Pro:
You need to have Titanium Backup pro for re-odexing.
Step 1:
Select Menu -> More -> integrate sys dalvik into rom and wait until its finished. Then you should have more space on /data. I had when I tried it before 105 and after 135 mb free space on /data and 0kb free space after it on /system, so its not all.
You can also undo it. Its good when you want to try out a new theme, so you can undo and redo it using TB Pro.
Simply select Menu -> More -> Undo sys dalvik integration
and you're done.
Option 1 vs. Option 2
-Option 1 does a full re-odex, you have full free space on /data(Option 2 does only re-odex the apps, not the framework)
-Option 1 deletes classes.dex from apks and jars(against Option 2), so you have more space free on /system
-You can undo Option 2 fast, so theming/modding is also possible by undo, theme and redo it(against Option 1)
For other Phones:
If someone has a other phone, theres a chance for getting re-odex working, but I think that you should not hope that it works. You can try to put in the right $BOOTCLASSPATH. You can find the valid $BOOTCLASSPATH in /init.rc. Then replace the following characters with the $BOOTCLASSPATH in the script in the folder odex(beginning from Line 8):
Code:
BOOTCLASSPATH=replace_this_with_your_bootclasspath
cd /system/framework
for filename replace_this_with_your_bootclasspath
In the line
Code:
for filename replace_this_with_your_bootclasspath
you must replace the ":" character between framework files with a space.
For theme developers:
I dont know if it works that you use the re-odexed theme on a stock odexed theme. If it is so, you dont have to re-odex and deodex your phone, you can simply push the dexopt-wrapper binary to a folder, chmod 755 it and use it to make odex files from the needed apks and jars(all apks inside /system/framework has no odex files, so dont odex them) like this:
Code:
dexopt-wrapper /system/app/Phone.apk /mnt/sdcard/Phone.odex /system/framework/core.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/android.policy.jar:/system/framework/services.jar
You can change argument 1-2, but not argument 3(its the BOOTCLASSPATH)Then you could copy all needed main apks or jars to sdcard and remove classes.dex. Then only do Step 1 from Option 1 and you should have a theme for odexed rom.
Download Links
XDA gaves me only 500 Errors when uploading was done, so I uploaded it to min.us
Framework jars from JPU
Re-Odex Script for Windows
Re-Odex Script for Linux
Credits
puppet13th for making orginal script
If I helped you, dont be shy, just press the Thanks Button under this post.
www.kingsrom.com/f8-how-to-theme-guideslinkstutorials
Oh year I didnt see any tutorial before, but his is only for Froyo sense or Gingerbread aosp, so it wont work on galaxy 3 and I also wrote my tutorial so that noobs can understand it(I hope so).
I could also post a system.img of a re-odexed Kyrillos Rom v9.3 and other Roms, but I dont know if Im allowed to do that.
TearsDontFalls said:
Oh year I didnt see any tutorial before, but his is only for Froyo sense or Gingerbread aosp, so it wont work on galaxy 3 and I also wrote my tutorial so that noobs can understand it(I hope so).
I could also post a system.img of a re-odexed Kyrillos Rom v9.3 and other Roms, but I dont know if Im allowed to do that.
Click to expand...
Click to collapse
So the re-odexed kyrillos rom v9.3 is working faster than the original kyrillos rom v9.3??
Its not generally faster, but much faster for me because I have ~100 apps and when I run these apps on kyrillos v9.3 deodexed, i must move app and dalvik-cache to sdext which made my phone laggy. With a odexed kyrillos v9.3, i have much more space free on /data, so i only must move app to sdext which is much.
I wrote also the advantages and disadvantages from a deodexed and odexed rom in my tutorial.
TearsDontFalls said:
Its not generally faster, but much faster for me because I have ~100 apps and when I run these apps on kyrillos v9.3 deodexed, i must move app and dalvik-cache to sdext which made my phone laggy. With a odexed kyrillos v9.3, i have much more space free on /data, so i only must move app to sdext which is much.
I wrote also the advantages and disadvantages from a deodexed and odexed rom in my tutorial.
Click to expand...
Click to collapse
So, in a re-odexed rom the HD2SD is not working ?
You use again froyo data2SD ?
dante_100 said:
So, in a re-odexed rom the HD2SD is not working ?
You use again froyo data2SD ?
Click to expand...
Click to collapse
As far as I understand, it works but only for data/app.
correct me if I'm wrong
Sorry, my english is not the yellow from the egg(you must not understand this).
Im using on my re-odexed rom also Hybrid Data 2 SD, I can move also move /data/dalvik-cache and any other folder to sdext, its only not needed, because I had after the re-odexing much more free space on /data, so I did moved dalvik cache back to the NAND from the sdext, before re-odexing I moved dalvik cache to sdext, becaue it was needed for running ~100 apps.
short form:Only Theming is impossible with a re-odexed rom
Hope you'll understand this now.
Edit: Can someone help me for creating a update.zip for re-odexing. It must only copy the dir odex to /data/local/tmp/odex , chmod 755 them all and execute the shell script /data/local/tmp/odex/odex
Sooo
if i get ADB access using windows i can skip step 2 in option1 right?
chandradithya said:
Sooo
if i get ADB access using windows i can skip step 2 in option1 right?
Click to expand...
Click to collapse
No. You need to reboot in cwm and try to get adb access from there. Windows adb in recovery never worked for me, you need linux to get adb access from cwm mode
Sent from my i9003 powered by Poseidon's Rom + UC kernel
Right, I tried to make a update.zip which execute the script, but i had no success, it would be great if somebody can help me.
bscraze said:
No. You need to reboot in cwm and try to get adb access from there. Windows adb in recovery never worked for me, you need linux to get adb access from cwm mode
Sent from my i9003 powered by Poseidon's Rom + UC kernel
Click to expand...
Click to collapse
ADB actually works for me, just ran cmd.exe using admin privileges and i ran the odex script it worked, odexed ALL my system files, cleared my /data/dalvik-cache/
But like TearsDontFalls said it doesn't show the free memory correctly,
Im running g3mod and im yet to try the option4 that asks you to switch file systems
And the /g3mod.log says,
st17: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY
While the other partitions are all clean,
How did you got adb access in windows? Sure you was in cwm recovery while re-odexing?
Finally, someone post a guide on this. And it works! Though titanium backup never worked for me. And is it necessary to run the script on cmw? Cause I didn't done it on cmw.
Sent from my GT-I5800 using XDA App
I didn't expect that it works on a running system, but it can be so, so I'll update the guide after Christmas.
TearsDontFalls said:
How did you got adb access in windows? Sure you was in cwm recovery while re-odexing?
Click to expand...
Click to collapse
It worked perfectly for me,
I tried going to the G3 kernels recovery, ADB just wouldnt connect,
so i turned it on, Ran the script when it was in standby mode , then it gave an error at first,
Which i rectified by making the /system read or write using root explorer,
I think i ran the script using admin privileges.
Dont remember..
And g3mod.log showed me this
Code:
Checking mmcblk0p2
/dev/block/mmcblk0p2: clean, 11/125488 files, 15840/500173 blocks
Checking stl6
/dev/block/stl6: clean, 1302/13600 files, 46914/54400 blocks
Checking stl7
/dev/block/stl7 contains a file system with errors, check forced.
/dev/block/stl7: Inodes that were part of a corrupted orphan linked list found.
/dev/block/stl7: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
(i.e., without -a or -p options)
Checking stl8
/dev/block/stl8: clean, 12/2176 files, 143/8704 blocks
Data2SD Disabled
Multi-OS Data Disabled
System detected: FROYO
System booted with Samsung Froyo kernel mode
Compcache disabled
No problems right now, But cant stop wondering why it says it is inconsistent.
I don't know why it is so, but it also doesn't show the right free space, so convert it to a other file system and then convert it back.
UNBELIEVABLE!
Finally, the first method worked for me.
Working great on HTC Amaze 4G
Thanks
heyjoe66 said:
UNBELIEVABLE!
Finally, the first method worked for me.
Working great on HTC Amaze 4G
Thanks
Click to expand...
Click to collapse
Thanks for your report. So it seems to be working on other devices, so I'll create a thread in android development.
Thanks works on sense 3.5, but I had to change Bootclasspath from the boot.img and add missing files below in odex script.
great guide
edit: now searching on how to re odex a single file.
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..