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
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!
Hi!
I want to mod my SystemUI.apk!! Other Bat-Icon, other Softkeys and so...
I can decombile .... then i can mod the SystemUI.apk and i combile without any Error Message in the APK Manager (5_0)
Then i pull the SystemUI to my tablet and give the right permission
xxx
xxo
xxx
Then i Reboot the device.... i see the changes (other bat-icons) but then the System stopps the UI and the Navibar is gone... then she comes again and the System stop it again
The ROM is odex .... is this the reason?
So far I have modified only deodexed ROMs... This is my first odexed ROM....
Darkman_RS said:
The ROM is odex .... is this the reason?
Click to expand...
Click to collapse
Bingo!
Roms need to be deodexed to theme them in that way.
Darkman_RS said:
Hi!
I want to mod my SystemUI.apk!! Other Bat-Icon, other Softkeys and so...
I can decombile .... then i can mod the SystemUI.apk and i combile without any Error Message in the APK Manager (5_0)
Then i pull the SystemUI to my tablet and give the right permission
xxx
xxo
xxx
Then i Reboot the device.... i see the changes (other bat-icons) but then the System stopps the UI and the Navibar is gone... then she comes again and the System stop it again
The ROM is odex .... is this the reason?
So far I have modified only deodexed ROMs... This is my first odexed ROM....
Click to expand...
Click to collapse
Instead of using APK Manager, you can treat SystemUI.apk as a zip archive, extract it on your device, make your changes, re-zip it, change the zip extension to apk, replace your SystemUI.apk with the modded one, and reboot. Don't touch the SystemUI.odex file at all. Leave it. And if anything goes wrong, push your old SystemUI.apk back to the device. This method works (sometimes) on odexed ROMs. Because SystemUI.apk is a system app, it doesn't need to be re-signed or anything; just zipped.
Sent from my GT-I9300 using XDA Premium HD app
Thank you .... but im must decombile because i modding a few of xmls files.
gesendet von Unterwegs......
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..
Wondering if anybody around here has some experience on using SVADeodexerForArt?
Trying to deodex D6603_Customized US_1288-7827_23.4.A.1.232_R6C and from what I gathered this is the tool to use, but been bouncing from thread to thread trying to understand how to make use of it and the more I read the more confusing it has become and I'm still at square one...
Anybody willing to shade to light and give direction on how to proceed?
Thanks
-Deodex-
Ok, so after a few days of reading I figured how to deodex my rom, took the long way since I didn't have the rom on my phone, just started from the xperifirm file...
Want to give a big THANKS @serajr for answering my questions and letting me use his zip to add my files for flashing!
This deodex zip is only for the D6603_Customized US_1288-7827_23.4.A.1.232_R6C firmware with root and recovery so be sure you're on that exact firmware before flashing!
-BACK UP before you even think of flashing this-
there is no debloat in the zip , you'll end up with a full stock D6603_Customized US_1288-7827_23.4.A.1.232_R6C deodexed, rooted and dualrecovery firmware
just flash the zip through recovery, wipe cache and dalvik and then boot...
get the deodex zip to flash here
-DM- said:
Ok, so after a few days of reading I figured how to deodex my rom, took the long way since I didn't have the rom on my phone, just started from the xperifirm file...
Want to give a big THANKS @serajr for answering my questions and letting me use his zip to add my files for flashing!
This deodex zip is only for the D6603_Customized US_1288-7827_23.4.A.1.232_R6C firmware with root and recovery so be sure you're on that exact firmware before flashing!
-BACK UP before you even think of flashing this-
there is no debloat in the zip , you'll end up with a full stock D6603_Customized US_1288-7827_23.4.A.1.232_R6C deodexed, rooted and dualrecovery firmware
just flash the zip through recovery, wipe cache and dalvik and then boot...
get the deodex zip to flash here
Click to expand...
Click to collapse
Hello there,
Can you please share how you did that? I am not able to find any way.
I wanna deodex D6653 firmware 23.4.A.1.232 Customized IN
I have .ftf, PRF Creator and SVA Deodexer
Thanks in advance
Mohitash said:
Hello there,
Can you please share how you did that? I am not able to find any way.
I wanna deodex D6653 firmware 23.4.A.1.232 Customized IN
I have .ftf, PRF Creator and SVA Deodexer
Thanks in advance
Click to expand...
Click to collapse
First make sure that you have the firmware you want to deodex, rooted with recovery and installed on your phone already so in your case D6653 firmware 23.4.A.1.232 Customized IN , if not then create a prerooted zip with that ftf file, SuperSu and latest dual recovery with PRFcreator then flash it and boot....Once that exact firmware is on your phone, you can follow those steps below to create a deodex zip.
Here is the process:
-download the zip that I provided in this thread (you'll need it later to swap my files with yours)
-open the ftf with 7-Zip to copy the system.sin file
-then use Flashtool Sin Editor to extract data to get System.ext4
-from there, use ext2explore (download it here) to open the system.ext4
-Once you opened system.ext4, locate those 3 folders (app, framework and priv-app) and build.prop
-create a folder called deodex on your C drive (so C:\deodex) and copy those 3 folders mentioned above and the build.prop file to it
-then move SemcGenericUxpRes folder from framework folder to app folder and take the 2 containing folders from vendor\app and move them to the app folder as well
- then run SVADeoderForArt.exe and selected the path to C:\deodex folder, check deodexing framework, app and private-app, let the tool run (it should tell you if it ran without errors when done)
-now you should have app, dex, framework, odex and priv-app folders (inside the SVADeodexerforart folder) after the tools finished the deodexing process (you can delete the dex and odex as they're not needed anymore)...now move SemcGenericUxpRes folder back to framework folder...also move back the 2 folders that you took from vendor\app, just put them anywhere on your desktop you're going to need them in a minute
-now when you open the deodex zip that you first downloaded, go into the system folder and you'll see 4 folders, app, framework, priv-app and vendor....delete the 3 folders app (but before, move the supersu folder from my app folder to your app folder, otherwise you'll end up without supersu) , framework and priv-app folders and move your 3 corresponding folders in there...now open vendor\app and delete the 2 folders and put yours instead
-your deodex zip should be good to flash now, put it on your sdcard...reboot to recovery, choose your zip to flash , then clear cache and dalvik cache and then boot....now you should have a full stock deodexed D6653 firmware 23.4.A.1.232 Customized IN (if you want to debloat, remove what you don't want from the app and private app folder in the zip before flashing, but you're on your own for that)
And as always make a backup before you start all this
Also, you should thank @serajr, as he's the one that wrote the script to clean and replace the system odexed folders, he nicely let me use it as a base to make my changes
-DM- said:
First make sure that you have the firmware you want to deodex rooted with recovery installed on your phone..............Also, you should thank @serajr, as he's the one that wrote the script to clean and replace the system odexed folders, he nicely let me use it as a base to make my changes
Click to expand...
Click to collapse
Thanks a lot for taking your time to write this and to give me good guide. This will help others too.
Ok i will follow the guide and now i am good to go. In case, any help needed, i will post here
And i think you saying to download your deodexed.zip only for meta inf and SuperSU, so i am not going to download that because i can do it myself so why to download ~800mb zip
And ya, Big thanks to @serajr. I dont know where to post exactly. So i am thanking you @serajr here.
Thanks and Regards
Mohitash
Mohitash said:
And i think you saying to download your deodexed.zip only for meta inf and SuperSU, so i am not going to download that because i can do it myself so why to download ~800mb zip
Thanks and Regards
Mohitash
Click to expand...
Click to collapse
yes, but looks like that you know what you're doing so you should be good to go
-DM- said:
yes, but looks like that you know what you're doing so you should be good to go
Click to expand...
Click to collapse
Ya, you got me right. May be you checked my profile or you can check now my history on XDA
I am just very very new to Sony and lollipop
Sent you pm.....
Regards
Mohitash
-DM- said:
First make sure that you have the firmware you want to deodex, rooted with recovery and installed on your phone already so in your case D6653 firmware 23.4.A.1.232 Customized IN , if not then create a prerooted zip with that ftf file, SuperSu and latest dual recovery with PRFcreator then flash it and boot....Once that exact firmware is on your phone, you can follow those steps below to create a deodex zip.
Here is the process:
-download the zip that I provided in this thread (you'll need it later to swap my files with yours)
-open the ftf with 7-Zip to copy the system.sin file
-then use Flashtool Sin Editor to extract data to get System.ext4
-from there, use ext2explore (download it here) to open the system.ext4
-Once you opened system.ext4, locate those 3 folders (app, framework and priv-app) and build.prop
-create a folder called deodex on your C drive (so C:\deodex) and copy those 3 folders mentioned above and the build.prop file to it
-then move SemcGenericUxpRes folder from framework folder to app folder and take the 2 containing folders from vendor\app and move them to the app folder as well
- then run SVADeoderForArt.exe and selected the path to C:\deodex folder, check deodexing framework, app and private-app, let the tool run (it should tell you if it ran without errors when done)
-now you should have app, dex, framework, odex and priv-app folders (inside the SVADeodexerforart folder) after the tools finished the deodexing process (you can delete the dex and odex as they're not needed anymore)...now move SemcGenericUxpRes folder back to framework folder...also move back the 2 folders that you took from vendor\app, just put them anywhere on your desktop you're going to need them in a minute
-now when you open the deodex zip that you first downloaded, go into the system folder and you'll see 4 folders, app, framework, priv-app and vendor....delete the 3 folders app (but before, move the supersu folder from my app folder to your app folder, otherwise you'll end up without supersu) , framework and priv-app folders and move your 3 corresponding folders in there...now open vendor\app and delete the 2 folders and put yours instead
-your deodex zip should be good to flash now, put it on your sdcard...reboot to recovery, choose your zip to flash , then clear cache and dalvik cache and then boot....now you should have a full stock deodexed D6653 firmware 23.4.A.1.232 Customized IN (if you want to debloat, remove what you don't want from the app and private app folder in the zip before flashing, but you're on your own for that)
And as always make a backup before you start all this
Also, you should thank @serajr, as he's the one that wrote the script to clean and replace the system odexed folders, he nicely let me use it as a base to make my changes
Click to expand...
Click to collapse
I understand the problem but somehow I do follow instructions whose results have been bootloop
đạt gao ô said:
I understand the problem but somehow I do follow instructions whose results have been bootloop
Click to expand...
Click to collapse
Sent you a pm