First let me say that I am not a technical writer and I hated English in school ((#(# years ago That being said, I will try to do the best I can with this.
I also want to thank StrongSteve for teaching me how to Odex files on Gingerbread. I have learned a great deal from him so he deserves a lot of credit.
This is a tutorial on how to Odex your mods.
What you need. You will need the Deodexed files that you want to Odex, custom recovery, ADB (attached if needed), an Odexed rooted Rom that you want to use your mod on, busybox and the attached dexopt-wrapper.
Let me explain a little about why you Odex on specific Roms. The process of Odexing relies on signatures. It builds the signatures from the original Odexed files. In most cases all of the Roms are built from the same original release so they all contain the same signatures. However, sometimes during the development process the signatures get modified. So if you are building your mod for a specific Odexed Rom start with that Rom as your base. Once you are done and you verify that the Mod works on that rom you can test it on other roms to see if it still works. If it doesn't work you would want to build it again using that Rom as the base.
OK so let's get started. I am not positive if this is necessary but I have been doing it this way since I started Odexing. If you have multiple jar files that you are going to Odex follow the bootclass order when Odexing.
The bootclass for ICS is /system/framework/core.jar:/system/framework/core-junit.jar:/system/framework/bouncycastle.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/framework2.jar:/system/framework/android.policy.jar:/system/framework/services.jar:/system/framework/apache-xml.jar:/system/framework/filterfw.jar:/system/framework/sechardware.jar:/system/framework/wimax.jar. So if you are Odexing services.jar and framework.jar you would first Odex framework.jar then services.jar. If you are Odexing jar files that aren't in the bootclass do those after you Odex the bootclass jars.
The below is an example. You will replace the text marked in red with the actual jar that you want to Odex.
This is the process for ICS
What I do is make a folder called Odexed on the root of my internal storage
I keep the dexopt-wrapper file on the root of my internal storage
Copy the Deodexed files that you want to odex into the Odexed folder
Do a nandroid backup of your phone
Flash the Odexed rom that you want to use with your mod
Make sure you are rooted
Make sure your phone has usb debugging enabled
Attach your phone to your computer
Open a command prompt and go to the adb folder
Type adb shell
Type su (check your phone to see if it is asking for permission and allow it if so)
Enter the following commands
mount -oremount,rw /dev/block/mmcblk0p9 /system
cp /sdcard/dexopt-wrapper /system/xbin
cp /sdcard/odexed/core.jar /system/framework
dexopt-wrapper /system/framework/core.jar /system/framework/patched_core.odex /system/framework/core.jar:/system/framework/core-junit.jar:/system/framework/bouncycastle.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/framework2.jar:/system/framework/android.policy.jar:/system/framework/services.jar:/system/framework/apache-xml.jar:/system/framework/filterfw.jar:/system/framework/sechardware.jar:/system/framework/wimax.jar
chmod 777 /system/framework/core.odex
chmod 777 /system/framework/patched_core.odex
busybox dd if=/system/framework/core.odex of=/system/framework/patched_core.odex bs=1 count=20 skip=52 seek=52 conv=notrunc
cp /system/framework/patched_core.odex /sdcard/odexed/core.odex
rm /system/framework/patched_core.odex
If you are odexing other files repeat the process starting from step 16
Once all of the Jar files are done you can Odex any apk files that you have. Note: framework-res.apk was never odexed so you can just skip that file.
For apks you only need to run this command dexopt-wrapper sdcard/odexed/SystemUI.apk sdcard/odexed/SystemUI.odex replacing SystemUI with the apk name that you are Odexing
Now copy all of the files from the Odexed directory on the phone to your computer
Open each of the jar and apk files with a program like winrar and delete the classes.dex file
Create a cwm zip file and put all of the files into the zip (you can use my Odexed Hotspot Mod as a template if you don't know how to do this)
Flash the Odexed rom that you want to use again so that you are starting fresh
Flash your mod and test to see if it works
If it doesn't work verify the steps to make sure you did everything in order
This process has never failed for me before
Once you have this working you can flash other Odexed Roms and test your mod out on them to see if they work
If not you need to repeat the process for that Rom if you want your Mod to work on that Rom
The bootclass for GB is /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
This is the process for Gingerbread
Everything from the ICS process is the same except for step 17
Change that line to dexopt-wrapper /system/framework/core.jar /system/framework/patched_core.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
If you have any questions or issues let me know and I will do my best to help you out. Good Luck!
One thing I have wanted to do, but havn't had a chance to work on, is to turn this process into a script so that this can be done automatically. If anyone would like to help me with this I would greatly appreciate it.
Reserved again just in case
Thanks for doing this!
Sent from my SPH-D710 using Tapatalk 2
Thanks for sharing your knowledge with us. Looking forward to this tutorial.
Pp.
Delivered to you via Mayan technology .
crawrj said:
One thing I have wanted to do, but havn't had a chance to work on, is to turn this process into a script so that this can be done automatically. If anyone would like to help me with this I would greatly appreciate it.
Click to expand...
Click to collapse
there is a script located in this link that worked for gingerbread maybe you could edit it for ics? It was a zip file that runs in recovery. Here is the link,
http://forum.xda-developers.com/showthread.php?t=1476617&page=31
mjohnson4580 said:
there is a script located in this link that worked for gingerbread maybe you could edit it for ics? It was a zip file that runs in recovery. Here is the link,
http://forum.xda-developers.com/showthread.php?t=1476617&page=31
Click to expand...
Click to collapse
Yeah i have one for gingerbread also that does the whole Rom. Haven't been able to get it to work on ics yet.
Sent from my SPH-D710 using xda premium
Related
This will have to be "flashed" through adb and your a100 needs to be on the newest update.
[STOCK ROM] Official Packages It's the first link on that post. We can thank vache for that.
All bloatware is still included, also acer's MusicA.odex did not deodex and is included.
Code:
$ adb shell
$ su
# stop
# mount -wo remount /system
# rm /system/app/*
# rm /system/framework/*
# cd /mnt/external_sd/path_to_tar
# busybox tar xvf A100_2.007.04_COM_GEN1_deodex.tar -C /
Permissions should be fine as it is in tar format otherwise:
Code:
# chmod 644 /system/app/*
# chmod 644 /system/framework/*
dalvik cache will be about 20MB larger and it should be wiped
Code:
# busybox rm /data/dalvik-cache/*
# exit
$ exit
$ adb reboot
It will take a bit longer on the first boot while the cache rebuilds
For anyone that doesn't know deodexing is only useful for creating a ROM/theme.
After any theming of the apps permissions will have to be set and keep the official stock ROM in hand in case of a bootloop.
Code:
# chmod 644 /system/app/apk_package
or
# chmod 644 /system/framework/jar_package
I've been running this for a few days and have had no issues at all.
Using this method we can start building some ROMS. I would suggest using tar and maybe include a small script to flash it.
Let me know if anyone wants a full ROM package as this is only the apps and framework.
A100_2.007.04_COM_GEN1_deodex.tar - 191.05 MB
[edit] As it turns out MusicA does not work at all, it doesn't even show up in the app drawer. Some guy named Jeff Lee compiled some of the framework wrong. com.acer.android.clearfilib_tablet.jar/C:/Users/Jeff_lee/Desktop/_acer/Jeff/clearfilib_tablet.java will not work. It should be a classes.dex file in the jar archive. Oh well it looks like its fixed in ICS.
02/22/12
Here's Deodex ICS, everything deodexed without issues. But without root this will be useless. [edit] We now have root so this will be very useful
A100_0.002.00_WW_GEN1_deodex.tar - 206.06 MB
Pending...
I was meaning to do this for a few days now and I am glad to see it works.
Did you do some more testing to see how it is, performance-wise?
Icewyng said:
I was meaning to do this for a few days now and I am glad to see it works.
Did you do some more testing to see how it is, performance-wise?
Click to expand...
Click to collapse
Nothing more than opening the stock apps and using it as I normally do. Just ran linpack, it got the same result as before deodexing. It really shouldn't run any better or worse. Though odex is supposed to be faster than using the dex format. It's also zipaligned so that can also speed things up a bit to compensate.
eww245 said:
This will have to be "flashed" through adb and your a100 needs to be on the newest update.
[STOCK ROM] Official Packages It's the first link on that post. We can thank vache for that.
All bloatware is still included, also acer's MusicA.odex did not deodex and is included.
Code:
$ adb shell
$ su
# stop
# mount -wo remount /system
# rm /system/app/*
# rm /system/framework/*
# cd /mnt/external_sd/path_to_tar
# busybox tar xvf A100_2.007.04_COM_GEN1_deodex.tar -C /
Permissions should be fine as it is in tar format otherwise:
Code:
# chmod 644 /system/app/*
# chmod 644 /system/framework/*
dalvik cache will be about 20MB larger and it should be wiped
Code:
# busybox rm /data/dalvik-cache/*
# exit
$ exit
$ adb reboot
It will take a bit longer on the first boot while the cache rebuilds
For anyone that doesn't know deodexing is only useful for creating a ROM/theme.
After any theming of the apps permissions will have to be set and keep the official stock ROM in hand in case of a bootloop.
Code:
# chmod 644 /system/app/apk_package
or
# chmod 644 /system/framework/jar_package
I've been running this for a few days and have had no issues at all.
Using this method we can start building some ROMS. I would suggest using tar and maybe include a small script to flash it.
Let me know if anyone wants a full ROM package as this is only the apps and framework.
A100_2.007.04_COM_GEN1_deodex.tar - 191.05 MB
Click to expand...
Click to collapse
Great work eww245! I am definately interested.....just noticed your thread today.
Is there a way to do this on the tablet itself?? Thanks for the work....
Sent from my ADR6400L using xda premium
BrothaJINC said:
Is there a way to do this on the tablet itself?? Thanks for the work....
Sent from my ADR6400L using xda premium
Click to expand...
Click to collapse
Probably but be prepared for a lot of force closings. I suggest you immediately end it with reboot ex: # busybox tar x.... ; reboot
and don't use stop, the screen will go black. Good Luck
So just put in the code above on a terminal then reboot. And have the file on the sdcard
Sent from my ADR6400L using xda premium
BrothaJINC said:
So just put in the code above on a terminal then reboot. And have the file on the sdcard
Sent from my ADR6400L using xda premium
Click to expand...
Click to collapse
Yep, not sure if your on ICS but I haven't tested it yet.
No I'm trying to get to ics... I'm on gen2.... Will post back how it went.... Thanks for the help...
Sent from my ADR6400L using xda premium
Using this method we can start building some ROMS. I would suggest using tar and maybe include a small script to flash it.
Let me know if anyone wants a full ROM package as this is only the apps and framework.
A100_2.007.04_COM_GEN1_deodex.tar - 191.05 MB
hello eww245, i am not familiar with this and at the risk of sounding like a total newb, how would one go about this....what i mean is could you just give the basics to get me started....how would we get past the acer signature and checksums? thanks so much for your hard work
oneovakindoldys2 said:
Using this method we can start building some ROMS. I would suggest using tar and maybe include a small script to flash it.
Let me know if anyone wants a full ROM package as this is only the apps and framework.
A100_2.007.04_COM_GEN1_deodex.tar - 191.05 MB
hello eww245, i am not familiar with this and at the risk of sounding like a total newb, how would one go about this....what i mean is could you just give the basics to get me started....how would we get past the acer signature and checksums? thanks so much for your hard work
Click to expand...
Click to collapse
As far as signatures, all the apks and jars are signed but unless you sign them with all the same keys, files will have to be added / replaced in the archive. They are just zip files.
One tool baksmalli code.google.com/p/smali/ allows the code to be extracted into smalli code, which is quite difficult to read. That's what I used to deodex the files, but something like adding a reboot menu to the long press power button is possible.
Another, ApkTool code.google.com/p/android-apktool/ Will decode all the xml files and extract the images. With that it's possible to change or add string values. Like new translation values or changing text that's already there.
The eaisest edit would be just replacing images. So using 7zip or if you use linux xarchiver works good. As I mentioned above if the apks/jars are unzipped and rezipped the signature changes. So the images will have to be replaced in the archive.
I haven't experiment much yet my self, I tried to change the autobacklight values without any effect, but I did manage to add a CRT power off effect to the framework-res.apk.
Good luck hopefully this helps.
eww245 said:
As far as signatures, all the apks and jars are signed but unless you sign them with all the same keys, files will have to be added / replaced in the archive. They are just zip files.
One tool baksmalli code.google.com/p/smali/ allows the code to be extracted into smalli code, which is quite difficult to read. That's what I used to deodex the files, but something like adding a reboot menu to the long press power button is possible.
Another, ApkTool code.google.com/p/android-apktool/ Will decode all the xml files and extract the images. With that it's possible to change or add string values. Like new translation values or changing text that's already there.
The eaisest edit would be just replacing images. So using 7zip or if you use linux xarchiver works good. As I mentioned above if the apks/jars are unzipped and rezipped the signature changes. So the images will have to be replaced in the archive.
I haven't experiment much yet my self, I tried to change the autobacklight values without any effect, but I did manage to add a CRT power off effect to the framework-res.apk.
Good luck hopefully this helps.
Click to expand...
Click to collapse
Thanks alot Eww, I will do some research on this and see what I can come up with. In the meantime, I have a question [mission actually...lol] for anyone that might have some knowledge. I have been working on cracking fastboot and nvflash on our a100 so we can flash custom roms. I have come to the conclusion that our fastboot/nvflash is locked/disabled in the default prop and init. I have been working on this in my spare time....anyway, this is the progress i have made so far ....i have extracted the leaked ics release, decompressed it, extracted the boot image, unpacked it and used split_boot to seperate the ramdisk from the kernel and made the changes that I thought were necessary. I then used mkboot and finally got it gzipped up without any errors. I now have an edited boot.img for the a100 that should enable fastboot operation, however I have no way to get it back on to the tablet.....tis is the dilemma! Any suggestions with merit will certainly be appreciated. thanks again
How do get cm7 to boot? i flashed it on safestrap 3.05 but all i get is black screen. also check y D3 rom Collection filled the best D3 roms https://www.mediafire.com/folder/b0gq735hrqxx6/Droid_3_ROMS
So, I just deodexed my Defy MB525 and wanted to share this info.
It works on Defy+ too!
************************************************************
DEODEXING ONLY MAKES SENSE IF YOU ARE USING A STOCK ROM.
MOST OF CUSTOM ROMs ARE ALREADY DEODEXED
************************************************************
WHAT IS DEODEXING?
Read here for a complete guide on odexed vs deodexed ROMs. In a few words a deodexed ROM allows users and developers to make easier modifications and theming.
ATTENTION:
I AM NOT RESPONSIBLE FOR WHATEVER HAPPENS TO YOUR PHONE!
If you don't follow the steps correctly you might brick your tablet and/or lose your personal data!
REQUIREMENTS:
xUltimate (download here)
Rooted Motorola Defy/Defy+
ADB set up and basic knowledge of using it
Windows PC
a brain that is able to think (not too much )
Process:
1. Unzip xUltimate to a folder, and launch "Main.exe"
2. Plug in your Defy/Defy+ (USB debugging enabled)
3. If everything is OK, xUltimate should recognize the phone and make a connection. You now should see a list of options.
4. Run option 5. This is going to take a while. Don't panic.
5. When it's finished, exit xUltimate and put the phone in USB mass storage mode.
6. Go back into the xUltimate folder, copy "done_frame", and "done_app" and move them to the root of the sdcard.
7. Turn off the USB mass storage.
8. Open command promt, navigate to your ADB directory, and type in the following:
Code:
adb shell
su
cp /sdcard/done_app/* /system/app/
cp /sdcard/done_frame/* /system/framework/
rm /system/app/*.odex
rm /system/framework/*.odex
reboot
8. Now, let your phone reboot, it is now deodexed!
Thanks for sharing. Although I might have some problem with that last requirement
I'll use the thanks button on this one definitely
thanks. some people think a odexed rom run faster than deodexed rom.if you dont modify your rom , i think a odexed rom works better.
Sent from my MB525 using xda premium
hsrars-d said:
So, I just deodexed my Defy MB525 and wanted to share this info.
It works on Defy+ too!
************************************************************
DEODEXING ONLY MAKES SENSE IF YOU ARE USING A STOCK ROM.
MOST OF CUSTOM ROMs ARE ALREADY DEODEXED
************************************************************
WHAT IS DEODEXING?
Read here for a complete guide on odexed vs deodexed ROMs. In a few words a deodexed ROM allows users and developers to make easier modifications and theming.
ATTENTION:
I AM NOT RESPONSIBLE FOR WHATEVER HAPPENS TO YOUR PHONE!
If you don't follow the steps correctly you might brick your tablet and/or lose your personal data!
REQUIREMENTS:
xUltimate (download here)
Rooted Motorola Defy/Defy+
ADB set up and basic knowledge of using it
Windows PC
a brain that is able to think (not too much )
Process:
1. Unzip xUltimate to a folder, and launch "Main.exe"
2. Plug in your Defy/Defy+ (USB debugging enabled)
3. If everything is OK, xUltimate should recognize the phone and make a connection. You now should see a list of options.
4. Run option 5. This is going to take a while. Don't panic.
5. When it's finished, exit xUltimate and put the phone in USB mass storage mode.
6. Go back into the xUltimate folder, copy "done_frame", and "done_app" and move them to the root of the sdcard.
7. Turn off the USB mass storage.
8. Open command promt, navigate to your ADB directory, and type in the following:
Code:
adb shell
su
cp /sdcard/done_app/* /system/app/
cp /sdcard/done_frame/* /system/framework/
rm /system/app/*.odex
rm /system/framework/*.odex
reboot
8. Now, let your phone reboot, it is now deodexed!
Click to expand...
Click to collapse
Are you know the procedure how extract the stock Rom of Defy by md5 file?.
I would like use to modifiy system, kernel etc
Thanks
Deodexed using DsiXda's Rom kitchen, so credit goes to DsiXda.
Do it at your own risk ! I'm just as NOOB as any on this forum. I just followed few topics and made this up.
I'm not responsible if your Xperia S gets bricked , because mine is working fine.
Follow steps correctly or else you get bootloops and you have to flash your rom again.
Your SXS must be rooted (with Locked Bootloader or Unlocked boot loader) on Stock ICS ROM 6.1.A.2.45 without any mods like toggles or reboot menus.
So i recommend to do this just after you flash & root your Stock ICS ROM 6.1.A.2.45.
Install Latest 'BusyBox' from Andriod Market.
Make complete backup first.
Step1: Downloading & Copying files on to phone's internal storage
These are NOT and i repeat NOT flashable zips through recovery.
Extracting the below zips on your PC you get two folders namely done_app & done_frame.
Copy these two folders on to your Xperia S. (Please Do Not rename the folders)
Deodexed_app .45(146mb)
Deodexed_frame .45(24mb)
Deodexed_app .50(150mb)
Deodexed_frame .50(24mb)
Step2: Pushing them onto your phone. (Adopted from xUltimate method, credits to him )
You should have ADB correctly setup on your PC.
Turn on your Xperia S.
Enable Settings>Security>Unknown Sources.
Enable Settings>Developer Options>Usb Debugging.
Disable Xperia>Connectivity>Install PC Companinon.
Connect phone to your PC . Wait for PC to show up internal storage.
Go to 'platform-tools' folder in your adnroid-sdk folder, hold shift down and right click mouse, select 'Open Command window here' , You'll get a cmd window.
Enter the below code in the cmd window line by line
Code:
adb shell
su
stop
mount -o rw,remount /system/ /system/
cp /sdcard/done_app/* /system/app/
rm /system/app/*.odex
cp /sdcard/done_frame/* /system/framework/
rm /system/framework/*.odex
mount -o ro,remount /system/ /system/
reboot
After the phone reboots you'll have deodexed rom.
I also made 30 steps Volume mod i'll share it once deodexing works perfectly for you guys because it works only on deodexed roms. Have fun !
iamsuperuser said:
Great ! Thanks for your interest. Deodexed using DsiXda's Rom kitchen, so credit goes to DsiXda.
Do it at your own risk ! I'm just as NOOB as any on this forum. I just followed few topics and made this up.
I'm not responsible if your Xperia S gets bricked , because mine is working fine.
Follow steps correctly or else you get bootloops and you have to flash your rom again.
Your SXS must be rooted (with Locked Bootloader or Unlocked boot loader) on Stock ICS ROM 6.1.A.2.45 without any mods like toggles or reboot menus.
So i recommend to do this just after you flash & root your Stock ICS ROM 6.1.A.2.45.
Install Latest 'Busybox' from Andriod Market.
Make complete backup first.
Step1: Downloading & Copying files on to phone's internal storage
These are NOT and i repeat NOT flashable zips through recovery.
Extracting the below zips on your PC you get two folders namely done_app & done_frame.
Copy these two folders on to your Xperia S. (Please Do Not rename the folders)
Deodexed_app(146mb)
Deodexed_frame(24mb)
Step2: Pushing them onto your phone. (Adopted from xUltimate method, credits to him )
You should have ADB correctly setup on your PC.
Turn on your Xperia S.
Enable Settings>Security>Unknown Sources.
Enable Settings>Developer Options>Usb Debugging.
Disable Xperia>Connectivity>Install PC Companinon.
Connect phone to your PC . Wait for PC to show up internal storage.
Go to 'platform-tools' folder in your adnroid-sdk folder, hold shift down and right click mouse, select 'Open Command window here' , You'll get a cmd window.
Enter the below code in the cmd window line by line
Code:
adb shell
su
stop
mount -o rw,remount /system/ /system/
cp /sdcard/done_app/* /system/app/
rm /system/app/*.odex
cp /sdcard/done_frame/* /system/framework/
rm /system/framework/*.odex
mount -o ro,remount /system/ /system/
reboot
After the phone reboots you'll have deodexed rom.
I also made 30 steps Volume mod i'll share it once deodexing works perfectly for you guys because it works only on deodexed roms. Have fun !
Click to expand...
Click to collapse
this should be stickied! Post this in Development mate! :good:
I've been waiting for this. I'll try it with pdroid once I have the time.
blakwhite said:
I've been waiting for this. I'll try it with pdroid once I have the time.
Click to expand...
Click to collapse
Report back I wanna try this too! But I'm kind of busy
iamsuperuser said:
Great ! Thanks for your interest. Deodexed using DsiXda's Rom kitchen, so credit goes to DsiXda.
Do it at your own risk ! I'm just as NOOB as any on this forum. I just followed few topics and made this up.
I'm not responsible if your Xperia S gets bricked , because mine is working fine.
Follow steps correctly or else you get bootloops and you have to flash your rom again.
Your SXS must be rooted (with Locked Bootloader or Unlocked boot loader) on Stock ICS ROM 6.1.A.2.45 without any mods like toggles or reboot menus.
So i recommend to do this just after you flash & root your Stock ICS ROM 6.1.A.2.45.
Install Latest 'Busybox' from Andriod Market.
Make complete backup first.
Step1: Downloading & Copying files on to phone's internal storage
These are NOT and i repeat NOT flashable zips through recovery.
Extracting the below zips on your PC you get two folders namely done_app & done_frame.
Copy these two folders on to your Xperia S. (Please Do Not rename the folders)
Deodexed_app(146mb)
Deodexed_frame(24mb)
Step2: Pushing them onto your phone. (Adopted from xUltimate method, credits to him )
You should have ADB correctly setup on your PC.
Turn on your Xperia S.
Enable Settings>Security>Unknown Sources.
Enable Settings>Developer Options>Usb Debugging.
Disable Xperia>Connectivity>Install PC Companinon.
Connect phone to your PC . Wait for PC to show up internal storage.
Go to 'platform-tools' folder in your adnroid-sdk folder, hold shift down and right click mouse, select 'Open Command window here' , You'll get a cmd window.
Enter the below code in the cmd window line by line
Code:
adb shell
su
stop
mount -o rw,remount /system/ /system/
cp /sdcard/done_app/* /system/app/
rm /system/app/*.odex
cp /sdcard/done_frame/* /system/framework/
rm /system/framework/*.odex
mount -o ro,remount /system/ /system/
reboot
After the phone reboots you'll have deodexed rom.
I also made 30 steps Volume mod i'll share it once deodexing works perfectly for you guys because it works only on deodexed roms. Have fun !
Click to expand...
Click to collapse
Mate you got to share the 3o step volume thing..
Sent from my LT26i using xda premium
Harsh7689 said:
Mate you got to share the 3o step volume thing..
Sent from my LT26i using xda premium
Click to expand...
Click to collapse
No big deal man chill ! Let some of the users confirm this method, I'll share it. It is only for deodex users. If I share it now stock odex users will have bootloops.
Links Updated. Please discard old files and download new ones .
great work buddy...
Has anyone tried this yet ?? Please give feedback so that i can post in development section.
iamsuperuser said:
Has anyone tried this yet ?? Please give feedback so that i can post in development section.
Click to expand...
Click to collapse
I'm trying it... will post as soon as i finished...
I have done it.. all step went without any errors... after reboot showed rebuilding cache (android is updating showed up).. no .odex in app folder..
I hope thats... DeOdexed...voilaa....
s-X-s said:
I'm trying it... will post as soon as i finished...
I have done it.. all step went without any errors... after reboot showed rebuilding cache (android is updating showed up).. no .odex in app folder..
I hope thats... DeOdexed...voilaa....
Click to expand...
Click to collapse
What about framework folder ?
yaaa both are pushed to respective folders... but i donno how to confirm framework is doedexed?
Nice job.... 30 Steps media volume is already there... By krabappel2548
s-X-s said:
yaaa both is pushed to respective folder... but i donno how to confirm framework is doedexed?
Click to expand...
Click to collapse
Check if there is any .odex files on framework folder.
I request the forum mods to move this topic to development section . Thanks s-X-s for testing.
iamsuperuser said:
I request the forum mods to move this topic to development section . Thanks s-X-s for testing.
Click to expand...
Click to collapse
Pm the moderators... E.Cardo or cooleagle
Hi noob question..what this tutorial does?
nemer12 said:
Hi noob question..what this tutorial does?
Click to expand...
Click to collapse
you should give a look here : http://forum.xda-developers.com/showthread.php?t=1363749
Sorry, a wrong post, please del it
Sent from my LT26i using xda app-developers app
milton.bain said:
Nice job.... 30 Steps media volume is already there... By krabappel2548
Click to expand...
Click to collapse
Yes but I need to update it to the latest fw and this method works for more devices then our XS I did it for 2011 line in my starting days there
In fact it will deodex most firmwares for most Android devices on Gingerbread, ICS or even Jellybean with the latest update, so it's not strictly for Xperia S and ICS
Sent from my LT26i using xda app-developers app
I want to have a Deodexed ROM without going and installing a different ROM. Is it possible to Deodex the 4.1.2 stock rom? Im sure it is. Im SGH-1317m on 4.1.2.
Thanks :fingers-crossed::good:
Pirlo#21 said:
I want to have a Deodexed ROM without going and installing a different ROM. Is it possible to Deodex the 4.1.2 stock rom? Im sure it is. Im SGH-1317m on 4.1.2.
Thanks :fingers-crossed::good:
Click to expand...
Click to collapse
u can use any of the deodex tools and kitchens, or just smali/baksmali like I do.
if u have link for this rom, I can do it for you.
Pirlo#21 said:
I want to have a Deodexed ROM without going and installing a different ROM. Is it possible to Deodex the 4.1.2 stock rom? Im sure it is. Im SGH-1317m on 4.1.2.
Thanks :fingers-crossed::good:
Click to expand...
Click to collapse
In titanium back up you can odex o4 deodex in settings
Sent from my GT-N7105 using xda premium
Android The Greek said:
In titanium back up you can odex o4 deodex in settings
Sent from my GT-N7105 using xda premium
Click to expand...
Click to collapse
How do i do that?
Sent from my GT-N7105 using xda premium
Android The Greek said:
Sent from my GT-N7105 using xda premium
Click to expand...
Click to collapse
Oh yeah. I tried that. It didn't work on the stock rom
djodjoni said:
u can use any of the deodex tools and kitchens, or just smali/baksmali like I do.
if u have link for this rom, I can do it for you.
Click to expand...
Click to collapse
How do i use the smali or baksmali? i have android kitchen. I just cant run any of the .Jar files. If thats even what your supposed to do. sorry. im usually not this lost
Pirlo#21 said:
How do i use the smali or baksmali? i have android kitchen. I just cant run any of the .Jar files. If thats even what your supposed to do. sorry. im usually not this lost
Click to expand...
Click to collapse
I havent used any kitchen actually, just do things manually with some small dirty scripts
So smali/baksmali:
1) to run a jar you can just exe "java -jar baksmali.jar" for example
for that of course you need to have java installed and it needs to be in your path
the (bak)smali jars normally come with a script wrapper so you dont need to bother for the java thing. I ll explain later
2) to deodex you need to baksmali, then smali then pack the classes.dex back into the apk/jar, then zipalign (optional but recommended)
3) to backsmali: baksmali -a {API} -x {APP.odex} -d {Dependencies ex: framework} -o {OUT_DIR}
4) to smali: smali -a {API} -o {output.dex} {smali DIR-got from baksmali}
5) to pack: aapt a -v {the package to put it in apk/jar} {the.dex file got from smali}
note u may use any archiving tool i just reuse the tools i get from AOSP
6) to zipalign: zipalign -f 4 r {the package apk/jar} {the out zipaligned package apk/jar}
ur done.
You normally also need to deodex framework and then app folder.
So if this is a bit complicated to do it urself if you have linux environment you can:
1) download:
smali
baksmali
baksmali.jar
smali.jar
aapt
zipalign
deodex.sh
from: http://web.djodjo.org/?a=download:android:tools:x86_linux:alltools
2) put those in your ~/bin and chmod them to 777
3) get your system dir(or just system/app and system/framework) to some place
4) execute deodex.sh {fullpath to the system dir} {API for you it is 16}
and wait ...
In case you've got the ext4 sparsed image i.e. system.img
you can download deodexsystem.sh from the same link and execute:
sudo deodexsystem.sh system.img 16
this one will even pack it back to an ext4 sparsed image file so you can tar it and flash it with odin
enjoy
djodjoni said:
I havent used any kitchen actually, just do things manually with some small dirty scripts
So smali/baksmali:
1) to run a jar you can just exe "java -jar baksmali.jar" for example
for that of course you need to have java installed and it needs to be in your path
the (bak)smali jars normally come with a script wrapper so you dont need to bother for the java thing. I ll explain later
2) to deodex you need to baksmali, then smali then pack the classes.dex back into the apk/jar, then zipalign (optional but recommended)
3) to backsmali: baksmali -a {API} -x {APP.odex} -d {Dependencies ex: framework} -o {OUT_DIR}
4) to smali: smali -a {API} -o {output.dex} {smali DIR-got from baksmali}
5) to pack: aapt a -v {the package to put it in apk/jar} {the.dex file got from smali}
note u may use any archiving tool i just reuse the tools i get from AOSP
6) to zipalign: zipalign -f 4 r {the package apk/jar} {the out zipaligned package apk/jar}
ur done.
You normally also need to deodex framework and then app folder.
So if this is a bit complicated to do it urself if you have linux environment you can:
1) download:
smali
baksmali
baksmali.jar
smali.jar
aapt
zipalign
deodex.sh
from: http://web.djodjo.org/?a=download:android:tools:x86_linux:alltools
2) put those in your ~/bin and chmod them to 777
3) get your system dir(or just system/app and system/framework) to some place
4) execute deodex.sh {fullpath to the system dir} {API for you it is 16}
and wait ...
In case you've got the ext4 sparsed image i.e. system.img
you can download deodexsystem.sh from the same link and execute:
sudo deodexsystem.sh system.img 16
this one will even pack it back to an ext4 sparsed image file so you can tar it and flash it with odin
enjoy
Click to expand...
Click to collapse
thanks but none of the downloads work for me and i tried to do it with Cygwin but i cant keep a terminal open for more than 3 seconds before it crashes sorry. ive been busy. why it took me so long to get back. and i also tried doing the android kitchen in Ubuntu. but every time i try. that terminal also force closes. i don't know what going on!
Pirlo#21 said:
thanks but none of the downloads work for me and i tried to do it with Cygwin but i cant keep a terminal open for more than 3 seconds before it crashes sorry. ive been busy. why it took me so long to get back. and i also tried doing the android kitchen in Ubuntu. but every time i try. that terminal also force closes. i don't know what going on!
Click to expand...
Click to collapse
what do you mean "none of the downloads work for me".
You use those in ubuntu not in cygwin.
What exactly do you do when it crashes? do you see any messages?
djodjoni said:
what do you mean "none of the downloads work for me".
You use those in ubuntu not in cygwin.
What exactly do you do when it crashes? do you see any messages?
Click to expand...
Click to collapse
okay. Well. I cant seem to run the ./menu on ubuntu. ive tried several commands.
Success!
djodjoni said:
what do you mean "none of the downloads work for me".
You use those in ubuntu not in cygwin.
What exactly do you do when it crashes? do you see any messages?
Click to expand...
Click to collapse
Okay! im sorry for the really long wait reply. But i got everything to open well. I extracted the system.img, boot.img, cache.img and modem.bin from a stock rom .tar... I gave it root, gave it busybox. did all that stuff. but before i build it. whats the API level i need to deodex? is it 16?
Guys I need some help.
I am trying to deodex my friend's Acro S using this tool here: http://forum.xda-developers.com/showthread.php?t=2176241
I can make the sytem dump but can't deodex it. I followed the instruction on how to get the bootclasspath and I am sure of the bootclasspath I am inputing but gives me an error saying "The system cannot find the specified path." After pasting the bootclasspath and pressing enter, the tool just returns to the start asking what I want to do. Anyway can someone post their bootclasspath here for verification.
Did anyone here tried using this tool?
My friend's Acro S in on stock .96 rom, rooted, and unlocked bootloader.
Any help will be greatly appreciated.
ronin1728 said:
Guys I need some help.
I am trying to deodex my friend's Acro S using this tool here: http://forum.xda-developers.com/showthread.php?t=2176241
I can make the sytem dump but can't deodex it. I followed the instruction on how to get the bootclasspath and I am sure of the bootclasspath I am inputing but gives me an error saying "The system cannot find the specified path." After pasting the bootclasspath and pressing enter, the tool just returns to the start asking what I want to do. Anyway can someone post their bootclasspath here for verification.
Did anyone here tried using this tool?
My friend's Acro S in on stock .96 rom, rooted, and unlocked bootloader.
Any help will be greatly appreciated.
Click to expand...
Click to collapse
The bootclasspath files generally are the files in /system/framework. So you need the files present in /system/framework.
Or you can use my tool over here - http://forum.xda-developers.com/showthread.php?t=2213235
I am sure that it will work for Acro S.
abcdjdj said:
The bootclasspath files generally are the files in /system/framework. So you need the files present in /system/framework.
Or you can use my tool over here - http://forum.xda-developers.com/showthread.php?t=2213235
I am sure that it will work for Acro S.
Click to expand...
Click to collapse
Oh thank goodness you are here. Yes I saw your tool too. And I have some questions about what to do (^^)d
1st: The apks that need deodexing are inside the /system/app, everything inside???
2nd: What about the jar files, where are they located? I am unsure where I can find these.
3rd: After I successfully deodex the apk & jar files, do I need to manually zipaligned them?
4th: And can I just copy/paste the deodexed files in /system?
Thank you in advance. (^-^)v
ronin1728 said:
Oh thank goodness you are here. Yes I saw your tool too. And I have some questions about what to do (^^)d
1st: The apks that need deodexing are inside the /system/app, everything inside???
2nd: What about the jar files, where are they located? I am unsure where I can find these.
3rd: After I successfully deodex the apk & jar files, do I need to manually zipaligned them?
4th: And can I just copy/paste the deodexed files in /system?
Thank you in advance. (^-^)v
Click to expand...
Click to collapse
1. Yes, the apks in /system/app need to be deodexed, but some of them are already deodexed. Simply pull all the apks from your phone and place them in the "apks" folder of my tool. The already deodexed apks will be automatically deleted
2. Jar files are located in /system/framework. You can use the pull from framework option in my tool. It will pull all the framework files.
3. Yes, you will have to manually zipalign all the apks. Sorry
4. It is better if you make a flashable zip, or try this - first keep the deodexed apks in /sdcard/done_app and the deodexed framework files in /sdcard/done_frame. I would still recommend you to make a flashable zip as it is the safest.
Code:
adb shell
su
stop
mount -o rw,remount /system/ /system/
cp /sdcard/done_app/* /system/app/
rm /system/app/*.odex
cp /sdcard/done_frame/* /system/framework/
rm /system/framework/*.odex
mount -o ro,remount /system/ /system/
reboot
Regards,
abcdjdj