Develop Bugs

[Q] How can I Remove battery icon from 3.70 or Myns RLS5?

I use Battery Indicator and don't like having two battery gauges at the top. I'm running Myns RLS5. Thanks

Any help would be great, as I need to remove the clock for the same reason. Who has the skills - please?!
Sent through space & time on the wings of 4G

You guys can do this yourself, look HERE

Anseri said:
SteelH said:
7. HOW-TO hide the clock
This reference assumes that you already know how to recompile a framework file using smali/baksmali.
Click to expand...
Click to collapse
This is the gotcha - I am not familiar with the Samali/baksmali tool, and the documentation I was able to find was not helpful.
Suggestions?
Click to expand...
Click to collapse

tgearman said:
Anseri said:
This is the gotcha - I am not familiar with the Samali/baksmali tool, and the documentation I was able to find was not helpful.
Suggestions?
Click to expand...
Click to collapse
Me neither. I was hoping to find a flashable zip file that would take care of this but no luck yet.
Click to expand...
Click to collapse

wirenut110 & tgearman - PM me if you want me to custom,ize your services.jar to remove whatever you would like removed.

For the clock removal (3.70) can't link it from my phone but the paper clip in Myn's Rom thread has it. (3.70 OTA no clock)
Sent from my PC36100 using XDA App

Im making a DIY guide right now. itl include how to use smali/baksmali

Skullmonkey said:
Im making a DIY guide right now. itl include how to use smali/baksmali
Click to expand...
Click to collapse
You could start with this:
1. Connect phone using USB and check that you can see your device using: adb devices
2. in your SDK/tools directory from command line do:
Code:
adb pull /system/framework/services.jar services.jar
3. Make a backup of the services.jar file that just popped in the tools folder just in case!
4. Download smali and baksmali from http://code.google.com/p/smali/ and place them in the tools folder. Rename the files to baksmali.jar and smali.jar to save on typing later
5. Open the services.jar file with something such as winrar or 7zip or whatever you prefer
6. Copy out the classes.dex file to your SKD/tools folder
7. run following from command line:
Code:
java -jar baksmali.jar -o classout/ classes.dex
8. Now browse to your new folders /classout/
9. Open the file you want to edit (i.e. the smali file) in something like notepad or context or any text editor, edit it, then save it
10. Now back to the command line and from your SDK/tools folder run:
Code:
java -Xmx512M -jar smali.jar classout/ -o new-classes.dex
11. If the above finishes without errors you should have a file called new-classes.dex in your SDK/tools folder now that is the same size as your classes.dex file.
12. Rename the old classes.dex file to classes-old.dex and rename the new-classes.dex file to classes.dex
13. Open the services.jar file with your archiving tool again from step 5 and replace the existing classes.dex file with our new classes.dex we just created.
14. From command line run:
Code:
adb remount
15. also from command line:
Code:
adb push services.jar /system/framework/
16. Finally run:
Code:
adb shell reboot

ok... this is what i put together... either way will work
Purpose:
This will let you remove various status bar elements such as the clock and battery icons.
Disclaimer:
I am not responsible for any damage done to your phone. Always do a nandroid backup before doing any changes to your phone.
Requirements:
- (bak)smali
- Text Editor (I use Notepad++)
Instructions:
1. Extract classes.dex from services.jar (best to get a clean copy from your rom found in /system/framework/) and place it in your SDK/Tools folder.
2. Open a command prompt/terminal and change the directory to your SDK/Tools folder
3. Run this command (without quotes)
"java -jar baksmali.jar -o classout/ classes.dex" ~Tells baksmali to take classes.dex and decompile it into a folder called classout/
4. Delete classes.dex file from your SDK/Tools folder (saves confusion later)
5. Remove whatever you would like. SteelH has a post on all of these located here.
6. Now that all your changes are made, we need to recompile classes.dex. To do this, run this command (without quotes and capitalization matters)
"java -Xmx512M -jar smali.jar classout/ -o classes.dex" ~tells smali to take the classout/ folder and recompile it to classes.dex
7. Take classes.dex and add it to your services.jar overwriting the old one.
8. Use your favorite method to flash to your phone. If you need to create an update.zip, you can download a blank one in the attached file and place services.jar in the system/framework/ folder of the zip archive and flash like normal.
Click to expand...
Click to collapse

I see on Myn's thread someone posted a zip to remove the clock that is for the latest framework.
Find out who posted it and send then your mod request directly. I'd run it down for you, but I'm out to dinner my phone is going to get confiscated if I don't put it back in my pocket soon...
Sent through space & time on the wings of 4G

OK guys, have a look HERE. This should solve all your problems.

SteelH - you are THE MAN!!
Sent through space & time on the wings of 4G

Worked like a champ - just had to toggle signature verification.
Thank you very much, kind Sir. It's folks like you that make XDA rock!

SteelH said:
OK guys, have a look HERE. This should solve all your problems.
Click to expand...
Click to collapse
Thanks SteelH. That worked.

[ICS][Deodex] stock system apps and framework [2.007.04_COM_GEN1]

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

[Guide] How to Odex your mod

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

[GUIDE] DEODEX Xperia S Stock Rom (6.1.A.2.45 ~ 6.2.B.1.96) - 27/8

Warning: This is very advanced, if you do not know what it is, dont play play.
I'm not responsible if your device bricked during deodexing process.
This method has been commonly used, I just improved it and included important cautions and precautions.
Requirements:
- Rooted firmware (Search XDA)
- Busybox installed (included when root with Root Many Droid)
- ADB correctly set up on computer *(sdk + environment variables setup)* ? - if u dont know what it is, as long as sdk installed is ok *(only sdk installed)*
- Xperia S with coresponding firmware version.
- In phone, usb debugging enabled, unknown sources enabled
- Downloaded app and framework zips
Downloads:
LT26i - 6.2.B.1.96 deodexed **not tested** by zhuhang
http://www.androidfilehost.com/?fid=23060877490002553​LT26i - 6.2.B.0.200 deodexed **not tested** by @davidbar93
https://www.dropbox.com/s/saog0fip6m8gsyf/done_app.rar
https://www.dropbox.com/s/d8s6rll8esatzny/done_frame.rar​LT26i - 6.1.A.2.55 deodexed **working** by zhuhang
http://www.androidfilehost.com/?fid=9390244042945593433
http://www.androidfilehost.com/?fid=9390244042945593434​LT26i - 6.1.A.2.50 deodexed **working** by zhuhang
http://www.androidfilehost.com/?fid=9390244042945593431
http://www.androidfilehost.com/?fid=9390244042945593432​LT26i - 6.1.A.2.45 deodexed **working** by zhuhang
http://www.androidfilehost.com/?fid=9390244042945593350
http://www.androidfilehost.com/?fid=9390244042945593351​
Instructions:
1. Extract downloaded zips
2. Copy done_app and done_frame to /sdcard/ (via MTP acceptable)
3. Make sure debugging mode connected
4. (i) Open Command Prompt on PC (Ctrl + R > cmd) *(sdk + environment variables setup)*
4. (ii) Go to /android-sdk/platform-tools/ folder, hold Shift button and right click mouse, 'Open Command window here' (Win 7) *(only sdk installed)*
5. Enter lines ony by one:
Code:
adb shell
su
stop
mount -o rw,remount /system/ /system/
busybox cp /sdcard/done_app/* /system/app/
busybox rm /system/app/*.odex
busybox cp /sdcard/done_frame/* /system/framework/
busybox rm /system/framework/*.odex
chmod 644 /system/app/*
chmod 644 /system/framework/*
busybox mount -o ro,remount /system/ /system/
reboot
6. Close Command Prompt
7. Wait for phone to reboot, you'll see "Android Upgrading, Optimizing aplications..."
8. If optimizing aplications succeed, congratulations, ur stock rom is deodexed! Done.
Note: Every time u put apks into /system/app/ and restart, Android Upgrading will appear for once.
Donations:
Its also recommended to make donation using Paypal balance. (lower transaction fee)
My Paypal Account is ready! Malaysian please PM me for local bank account.
I would appreciate if you can donate to me so I can maintain this OP. I'm also making IRS for you guys.
Credits:
Deodexed using dsixda's kitchen
Compressed using Winrar

Is it as simple as that?

eScapeeXc said:
Is it as simple as that?
Click to expand...
Click to collapse
Definitely yes if u know the commands and steps.
Try it yourself then, i've done hundred times on acroS and XS
Link to acroS in my sig.

zhuhang said:
Warning: This is very advanced, if you do not know what it is, dont play play.
I'm not responsible if your device bricked during deodexing process.
This method has been commonly used, I just improved it and included important cautions and precautions.
Requirements:
- Clean Rom (best with data wiped, orelse FCs)
- Rooted firmware (Root with Root Many Droid : here)
- Busybox installed (included when root with Root Many Droid)
- ADB correctly set up on computer *(sdk + environment variables setup)* ? - if u dont know what it is, as long as sdk installed is ok *(only sdk installed)*
- Xperia S with: usb debugging enabled, unknown sources enabled
- Downloaded app and framework zips
Downloads:
LT26i .45 deodexed
http://www.androidfilehost.com/?fid=9390244042945593350
http://www.androidfilehost.com/?fid=9390244042945593351​
Instructions:
1. Extract downloaded done_app and done_frame zips
2. Copy done_app and done_frame to /sdcard/ (via MTP acceptable)
3. Make sure debugging mode connected
4. (i) Open Command Prompt on PC (Ctrl + R > cmd) *(sdk + environment variables setup)*
4. (ii) Go to /android-sdk/platform-tools/ folder, hold Shift button and right click mouse, 'Open Command window here' (Win 7) *(only sdk installed)*
5. Enter lines ony by one:
Code:
adb shell
su
stop
mount -o rw,remount /system/ /system/
busybox cp /sdcard/done_app/* /system/app/
busybox rm /system/app/*.odex
busybox cp /sdcard/done_frame/* /system/framework/
busybox rm /system/framework/*.odex
busybox mount -o ro,remount /system/ /system/
reboot
Note: Do not change permissions of files to 644 or folders to 755! We'll do it later.
6. Leave Command Prompt open
7. Wait for phone to reboot, if optimizing aplications succeed, congratulations, ur stock rom is deodexed!
8. Now let's manually fix some permissions
9. Return to Command Prompt
10. Enter lines ony by one:
Code:
adb shell
su
mount -o rw,remount /system/ /system/
chmod 644 /system/app/*
chmod 644 /system/framework/*
busybox mount -o ro,remount /system/ /system/
reboot
11. After phone reboot, there should be no more "Android Upgrading, Optimizing aplications..."
12. Viola, Done!!
Note: Every time u put apks into /system/app/ and restart, Android Upgrading will appear for once.
Credits:
Deodexed using dsixda's kitchen
Packed using Winrar
Click to expand...
Click to collapse
Is this what u used for AC!D V6? is the internal speaker volume low?

darkace007 said:
Is this what u used for AC!D V6? is the internal speaker volume low?
Click to expand...
Click to collapse
This is deodexing stock ICS rom, nothing to do with any mod or acid v6
Do u know what's deodexing?

I dont exactly know but its about theming possibilties right but I saw one of ur posts that AC!D works for stock .45.
Sent from my LT26i using xda app-developers app

darkace007 said:
I dont exactly know but its about theming possibilties right but I saw one of ur posts that AC!D works for stock .45.
Sent from my LT26i using xda app-developers app
Click to expand...
Click to collapse
Deodex is not for theming. U can understand it somewhere else
I will add advantages of deodexing to 1st post.
Acid v6 not working yet, I haven't really tested. V5 works.
It doesn't matter whether ur Rom is odexed or deodexed, the advantage is no android upgrade loop on deodexed Rom.
Sent from my LT26i using xda app-developers app

You can actually a package, which used here man. Sdk, busybox, etc. It would be better. And one more question. Is it exactly at .55?

eScapeeXc said:
You can actually a package, which used here man. Sdk, busybox, etc. It would be better. And one more question. Is it exactly at .55?
Click to expand...
Click to collapse
Sdk has to be installed (few hundred Mbs) + Java
Root+busybox link given.
I can't make a package for that. Maybe links. I will consider.
Its .45, I'll do .50 and .55, can anyone provide me the app and framework?

There was another Deodexed .45 thread here.... if it was .55 would been better...

s-X-s said:
There was another Deodexed .45 thread here.... if it was .55 would been better...
Click to expand...
Click to collapse
Very soon...
Sent from my LT26i using xda app-developers app

zhuhang said:
Sdk has to be installed (few hundred Mbs) + Java
Root+busybox link given.
I can't make a package for that. Maybe links. I will consider.
Its .45, I'll do .50 and .55, can anyone provide me the app and framework?
Click to expand...
Click to collapse
s-X-s said:
There was another Deodexed .45 thread here.... if it was .55 would been better...
Click to expand...
Click to collapse
Just a thought why don't take .55 deodex both app and framework from the ROM I post long ago. It is in zip format so you could easily extract app and framework then follow instruction in first post to inject to your ROM.

tosa.th said:
Just a thought why don't take .55 deodex both app and framework from the ROM I post long ago. It is in zip format so you could easily extract app and framework then follow instruction in first post to inject to your ROM.
Click to expand...
Click to collapse
Where did u posted it?

zhuhang said:
Where did u posted it?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2005595

tosa.th said:
http://forum.xda-developers.com/showthread.php?t=2005595
Click to expand...
Click to collapse
U modified a little things.

zhuhang said:
U modified a little things.
Click to expand...
Click to collapse
Yes, I delete few app that recognize as bloat ware (this is recommended by rom kitchen) I see that you also use rom kitchen I believe you should see that as well.
The other change is not relate to app and framework.

tosa.th said:
Yes, I delete few app that recognize as bloat ware (this is recommended by rom kitchen) I see that you also use rom kitchen I believe you should see that as well.
The other change is not relate to app and framework.
Click to expand...
Click to collapse
Nope, i didnt saw which is recognized bloatware.
Which one?

zhuhang said:
Nope, i didnt saw which is recognized bloatware.
Which one?
Click to expand...
Click to collapse
Didn't write it down so can not tell you exactly which one.
It said some thing like do you want to remove bloatware ? I just say yes.
May be you could try to deodex .55 ROM then see if it detect any bloatware.

tosa.th said:
Didn't write it down so can not tell you exactly which one.
It said some thing like do you want to remove bloatware ? I just say yes.
May be you could try to deodex .55 ROM then see if it detect any bloatware.
Click to expand...
Click to collapse
I never encounter bloatware detected, anyway i will remove any apps.

Updated 27/12/12
Added:
LT26i - 6.1.A.2.50
LT26i - 6.1.A.2.55
Both not tested, let me know the result.
EDIT: Should be LT26i

「HELP」Deodexing Acro S

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