Develop Bugs

[H] Help in dodexing process

amadeyX said:
Hi
I try dodexing same files and dont successful.
This file I try : "DialerTabActivit" (APK and odex file)
This what i do:
1. put all filse from framework folder, APK and odex files .
2.add the smali and baksmali files
3. run a next Command in CMD :
"java -jar baksmali-1.2.4.jar -x DialerTabActivit.odex"
and get error : http://www.siz.co.il/my/2myiiydmrmxf.jpg
I try this Command :
"java -jar baksmali-1.2.4.jar -l DialerTabActivit.odex"
and this extracts files without deodexing process.
What can ido to successful deodexing?
Thanks!
Click to expand...
Click to collapse
look for xultimate (thanks to xeododus) program, it fully automates the process of deodexing your odex files.
hope this helps.

g00ndu said:
look for xultimate (thanks to xeododus) program, it fully automates the process of deodexing your odex files.
hope this helps.
Click to expand...
Click to collapse
Link to post would be highly appriciated

thechamp007 said:
Link to post would be highly appriciated
Click to expand...
Click to collapse
http://www.xeudoxus.com/android/xUltimate-v2.2.2.zip

Thanks fro this!
How to use ? xUltimate
Writes that java was not installed on my phone
Image : http://www.siz.co.il/my/zzignim1tgzz.png

?........................................

amadeyX said:
Writes that java was not installed on my phone
Click to expand...
Click to collapse
You do not need java on the phone but your pc that you running xUltimate on
amadeyX said:
How to use ? xUltimate
Click to expand...
Click to collapse
1. Unzip xUltimate v2.2
2. Plug in phone (USB Debugging)
3 Launch "Main.exe"
4. Run option 1. After option 1 is done, run option 2.
5. Now these well take a while. Run option 3.
6. Now run option 4, and wait.
7. Exit xUltimate, and put the phone in USB mass storage.
8. Go back into the xUltimate folder and copy "done_frame", and "done_app", and move them to the root of the sdcard.
9. Open a command prompt, and do the following:
Code:
busybox mount -o remount,rw /system
cp /sdcard/done_app/* /system/app/
cp /sdcard/done_frame/* /system/framework/
rm /system/app/*.odex
rm /system/framework/*.odex
sync
reboot, Your phone should now be deodexed!

amadeyX said:
Thanks fro this!
How to use ? xUltimate
Writes that java was not installed on my phone
Image : http://www.siz.co.il/my/zzignim1tgzz.png
Click to expand...
Click to collapse
install java in your pc and launch xultimate.

"busybox mount -o remount,rw /system
"
dont work - error "permission denied
I have ROOT.

amadeyX said:
"busybox mount -o remount,rw /system
"
dont work - error "permission denied
I have ROOT.
Click to expand...
Click to collapse
were you in su mode before entering that command?
adb shell
su (..accept permission prompt)
busybox mount -o remount,rw /system

LAG.........................

how to inter to su mode?
adb shell
su
permission denied

amadeyX said:
how to inter to su mode?
adb shell
su
permission denied
Click to expand...
Click to collapse
If you can, do another root process again. Is your recovery 2e or 3e?

recovey 2e + cf root
Sent from my GT-I9000 using XDA App

amadeyX said:
how to inter to su mode?
adb shell
su
permission denied
Click to expand...
Click to collapse
when you enter su on the PC you will be prompted to Approve the Permission Request on the phone. So type su on the PC and click Accept on the phone

[HOW TO][Windows] Manually Deodex and Odex back

The purpose of this thread is to give basics to manually deodex and odexing back framework and apk files​
Credits and Thanks to :
jubeh
Decad3nce
software_samurai
JKay
LeoMar75
and many others I forgot
Click to expand...
Click to collapse
Theory :
WHAT IS AN ODEX FILE?
In Android file system, applications and framework files come in packages with the extension .apk or .jar. These APKs or JARs contain certain .odex files whose supposed function is to save space. These ‘odex’ files are actually collections of parts of an application that are optimized before booting. Doing so speeds up the boot process, as it preloads part of an application. On the other hand, it also makes hacking those applications difficult because a part of the coding has already been extracted to another location before execution.
THEN COMES DEODEX
Deodexing is basically repackaging of these APKs or JARs in a certain way, such that the .odex files are reassembled into classes.dex files directly integrated inside the APKs or JARs. By doing that, all pieces of an application package are put together back in one place.
For now, we need Baksmali.jar and Smali.jar to deodex, it seems these tools are not perfect and it seems to be why deodexed stock browser is laging/freezing.
This is the reason why there is a return to odexed customROMs
Click to expand...
Click to collapse
Prerequisites :
You will need these files :
* backsmali.jar
* smali.jar
* custom java.awt.jar
* dexopt wrapper
* recent version of busybox
Click to expand...
Click to collapse
all included in the attached .zip (end of post)
You will also need :
* your GS2
* with the official odexed firmware you want to mod
* rooted and with root explorer (pay app but really usefull) and with CWM recovery (better )
* ADB installed and working in su (#)
* copy dexopt-wrapper in /system/bin/ and giving it 755 permissions (using root explorer or command: chmod 755 /system/bin/dexopt-wrapper
* optional (if errors during odexing back) overwrite installed busybox with the one included here in /system/xbin/
Click to expand...
Click to collapse
You have to know :
* even on stock firmware (odexed) there are some deodexed .apk (like framework-res.apk in /system/framework/ and like some .apk in system/app/)
Tip on Windows "Vista / 7" : open a CMD prompt in a specified folder
1. Select the folder you want to open in the command prompt
2. Right-click on it while holding the Shift key
3. Select Open command window here
Click to expand...
Click to collapse
Manually Deodexing :
theory :
to decompil an odex file you need Baksmali.jar and you needs the BOOTCLASSPATH
BOOTCLASSPATH is a list in specific order of some framework .jar files
** To decompil and re-odex back .odex from JAR file you need to use the BOOTCLASSPATH specified in the init.rc file located in the root folder of your GS2 : (open init.rc with notepad ++)
Extract of I9100 init.rc :
export BOOTCLASSPATH /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
** To decompil an .odex from APK file, BOOTCLASSPATH is different in fonction of the APKs, so the lazy way is to include all the .JAR files of the framework folder
2 applications : Emails.apk and MobilePrint.apk needs one more custom java.awt.jar
Click to expand...
Click to collapse
1/ put in the same folder :
* apk to deodex
* all system/framework files
add :
* custom java.awt.jar
* baksami.jar
* smali.jar
* zipalign.exe
Click to expand...
Click to collapse
2/ open CMD prompt in this folder (see above for how to)
3/ Deodexing Framework file (I will take android.policy.jar for example) :
* BAKSMALI of the android.policy.odex :
Code:
java -Xmx1024m -jar baksmali.jar -c :core.jar:bouncycastle.jar:ext.jar:framework.jar:android.policy.jar:services.jar:core-junit.jar -x [B]android.policy.odex[/B]
* This create an out folder. You can now modify some files (like adding Advanced power menu)
* SMALI the /out folder in a classes.dex file :
Code:
java -Xmx1024m -jar smali.jar [B]out[/B] -o classes.dex
* finally deodex your android.policy.jar :
open android.policy.jar with 7zip without extracting
push the classes.dex created in the 7zip window in the root folder
close the 7zip windows and here is your deodexed android.policy.jar
Click to expand...
Click to collapse
4/ Deodexing APK in system/app (I will take SystemUI.apk for exemple) :
* BAKSMALI of the SystemUI.odex :
Code:
java -Xmx1024m -jar baksmali.jar -c :am.jar:android.policy.jar:android.test.runner.jar:bmgr.jar:bouncycastle.jar:com.android.location.provider.jar:com.google.android.maps.jar:com.samsung.device.jar:com.yamaha.android.media.jar:core.jar:core-junit.jar:ext.jar:framework.jar:ime.jar:input.jar:[B]java.awt.jar[/B]:javax.obex.jar:libvtmanagerjar.jar:monkey.jar:pm.jar:sec_feature.jar:seccamera.jar:sechardware.jar:secmediarecorder.jar:services.jar:sqlite-jdbc.jar:svc.jar:twframework.jar -x [B]SystemUI.odex[/B]
* an out folder is created. You can modify the files inside if you want.
* SMALI the /out folder in a classes.dex file :
Code:
java -Xmx1024m -jar smali.jar [B]out[/B] -o classes.dex
* finally deodex your SystemUI.apk :
open SystemUI.apk with 7zip without extracting
push the classes.dex created in the 7zip window in the root folder
close the 7zip windows and here is your deodexed SystemUI.apk
Click to expand...
Click to collapse
* extra step for APKs : zipaplign of your new deodexed SystemUI.apk
--> In the same CMD prompt windows, type :
Code:
zipalign -v 4 SystemUI.apk zip_SystemUI.apk
A zip_SystemUI.apk file is created. Delete your deodexed SystemUI.apk and rename zip_SystemUI.apk in SystemUI.apk
ODEXING BACK :
the theory :
*You will need to copy the (custom) deodexed file (.jar or .apk) in the system/framework/ folder of your phone.
*You will use dexopt wrapper (already copied in your phone) to obtain a new .odex file (patched_android.policy.odex for example)
* You will copy the signature of original .odex file to patched.odex file - if not, the phone won't boot ...
Click to expand...
Click to collapse
How To :
1/ backup your original files (apk jar and odex) to /sdcard/Mod/
2/ copy modified deodexed files (.apk and .jar) in /system/framework/ of your GS2
Now we are going to odex back
3/ open a CMD prompt in the folder of adb.exe (usualy /android-sdk-windows/platform-tools/)
4/ type command :
Code:
adb shell
su
## for .JAR file :
dexopt-wrapper /system/framework/XXX.jar /system/framework/patched_XXX.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
response must be :
--- BEGIN '/system/framework/android.policy.jar' (bootstrap=0) ---
--- waiting for verify+opt, pid=7194
--- would reduce privs here
--- END '/system/framework/android.policy.jar' (success) ---
## for .APK file :
dexopt-wrapper /system/framework/XXX.apk /system/framework/patched_XXX.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
--> This will create the patched_XXX.odex file
Now we need to copy signature from original .odex file to patched .odex file cause Dalvik need files signature integrity in order to boot.
5/ always in the same CMD prompt windows :
Code:
# if not already done ...
adb shell
su
# copy the original .odex and .jar in system/framework (not .apk) :
cp /sdcard/MOD/original.XXX.odex /system/framework
cp -f /sdcard/MOD/XXX.jar /system/framework # where XXX.jar is the original odexed .jar
# give all permissions to XXX.odex files :
chmod 777 /system/framework/original.XXX.odex
chmod 777 /system/framework/patched_XXX.odex
# copy signature :
busybox dd if=/system/framework/original.XXX.odex of=/system/framework/patched_XXX.odex bs=1 count=20 skip=52 seek=52 conv=notrunc
response must be :
busybox dd if=/system/framework/original.XXX.odex of=/system/framewor
k/patched_XXX.odex bs=1 count=20 skip=52 seek=52 conv=notrunc
20+0 records in
20+0 records out
20 bytes (20B) copied, 0.002042 seconds, 9.6KB/s
Now the signature is copied over the patched_XXX.odex
Notice :
a - if you don't have response after busybox dd command : busybox is not installed or you have a to old version, use the busybox included in the attached .zip
b - if you don't have the last response line : 20 byt

Awesome! Thank you for your time sir!
Best regards,
aDEO

awesome man!'help me out of questions!

Thanks for the guide, just a quick question.
Can I odex a custom deodexed ROM? Just that will save me time.
If not, I'll unpack an official ROM and made my mods. You've posted some other great guides which has really helped me tonight! Thanks again.

nice tutorial
I've successfully deodex them.
lets try odex them back .

Mekrel said:
Thanks for the guide, just a quick question.
Can I odex a custom deodexed ROM? Just that will save me time.
If not, I'll unpack an official ROM and made my mods. You've posted some other great guides which has really helped me tonight! Thanks again.
Click to expand...
Click to collapse
Yes you can odex back a customROM (in theory) I never try to, but you will need to odex back all the .jar of the framework folder. And you will need the original firmware to copy signature of original .odex files to re-odexed .odex files
Sent from my GT-I9100 using XDA Premium App

abu2x said:
nice tutorial
I've successfully deodex them.
lets try odex them back .
Click to expand...
Click to collapse
Sometimes it will work the first time.
Sometimes it won't cause you forgot to give good permissions to dexopt-wrapper in system/bin
Or to the pached_XXX.odex files (need write permissions for all)
Or Busybox not installed or to old... Then the copy signature step won't work
Sent from my GT-I9100 using XDA Premium App

brilliant! thx a ton!

Great ! I was looking for this, thank you.
One thing was still giving me a hard time and i got that one solved also.
When doing a odex back from a custom theme, the method is different.
Because you need to use the modified framework file in the dependencylist.
So for me it was:
(I put a modified framework.jar in /sdcard)
dexopt-wrapper /sdcard/framework.jar /sdcard/framework.odex /system/framework/core.jar:/system/framework/bouncycastle.jar:/system/framework/ext.jar:/sdcard/framework.jar:/system/framework/android.policy.jar:/system/framework/services.jar:/system/framework/core-junit.jar
Otherwise it does NOT work. Now i have succusfully added overglow to a odex ROM.

Ok a new problem with the framework.jar
In the method to odex on the FP there was mentioned to use the dependency framework stuff.
When doing that trying to odex framework.jar i only get bootloops. aka the created odex file is wrong. The weird part is that the odex file created is 6,8 mb
When using the method i proposed in including the modified framework.jar in the dependencylist a bigger framework.odex is created. This one is about 7,14 mb
And it boots !
But it seems to be messed up because when trying to do some settings i get fc or it just exits. It appears to focus on phone settings. (try adding a apn and it closes)
Does anyone know of a solution for this ?
I did try to add the java.awt.jat in the dependencylist, but it does not seem to matter at all.

Yes you need to use your modded framework.jar in bootclasspath dependencies of dexopt wrapper.
If force close, perhaps you did not erase dalvik cache or made a mistake when modding framework.jar
Did you use the last Smali version out today x.7 to make your mod ? cause smali.jar was buggy with framwork.jar deodexing.
If you just want to odex a theme with more than 1 framework file, you should need to do by step : first you copy 1 file and odex it back then you do the same for second file ... You should only use 1 deodexed jar in your bootclasspath corresponding to the file you try to odex back.
Hope this will help, i cannot help much cause my GS2 doesn't really love the beautifull sand of the mediteraneen sea I am on vacation ...
Sent from my GT-I9100 using XDA Premium App

Thanx for the reply, i did just that.
The framework.jar file works flawlessly on a deodexed system, so i guess this file is ok.
But it does not work correctly when trying to odex back. I keep getting (thesame ) errors. Even doing a binary compare of the odex files when trying different methods to odex back is identical.
But the endresult is always thesame. The phone does boot but there are issues inside the jarfile.

Brotuck said:
Thanx for the reply, i did just that.
The framework.jar file works flawlessly on a deodexed system, so i guess this file is ok.
But it does not work correctly when trying to odex back. I keep getting (thesame ) errors. Even doing a binary compare of the odex files when trying different methods to odex back is identical.
But the endresult is always thesame. The phone does boot but there are issues inside the jarfile.
Click to expand...
Click to collapse
I just remember that original developper of overscroll glow for Galaxy S has stopped to dev odexed owerscroll glow cause of same errors (MMS)
I believe this due to a dexopt wrapper bug on odexing back framework.odex ??

smali / baksmali v1.2.8 is available

Hi Sicopat,
I'm having issues with this.
I'm currently running XXKG6 ROM that I've successfully deodexed and after reading your thread, I've wrote the below shell script that successfully runs.
Code:
#!/system/bin/sh
chmod 755 /system/bin/dexopt-wrapper
chmod 755 /system/bin/zip
coreframework="/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"
echo "Odexing /system/framework/*jar files"
for i in $coreframework
do
filename=$(basename $i .jar)
dexopt-wrapper $i /system/framework/$filename.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
zip -d $i classes.dex
done
for i in /system/framework/*.jar
do
if [ $i == "/system/framework/core.jar" -o $i == "/system/framework/bouncycastle.jar" -o $i == "/system/framework/ext.jar" -o $i == "/system/framework/framework.jar" -o $i == "/system/framework/android.policy.jar" -o $i == "/system/framework/services.jar" -o $i == "/system/framework/core-junit.jar" ]
then
echo "Already odexed in sequence"
else
filename=$(basename $i .jar)
dexopt-wrapper $i /system/framework/$filename.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
zip -d $i classes.dex
fi
done
echo "Giving permissions to all *odex files"
chmod -R 777 /sdcard/original-framework/*.odex
chmod -R 777 /system/framework/*.odex
echo "Copying signatures from original odex files"
for i in /sdcard/original-framework/*.odex
do
filename=$(basename $i .odex)
busybox dd if=$i of=/system/framework/$filename.odex bs=1 count=20 skip=52 seek=52 conv=notrunc
done
rm -r /data/dalvik-cache/*
The script does the following process:
Sets permisions for the dexopt-wrapper and zip binaries.
Odexes the core framework in the same order they're listed in BOOTCLASSPATH in init.rc.
Odexes the other framework files that were not previously odexed
Copies the signatures from the original XXKG6 .odex files, to the ones that have just been created (the origials are stored on the sdcard)
The only difference in the script I wrote is the classes.dex are removed from the .jar files using the zip binary.
I can see the .odex files created when running a ls /system/framework command and pulling the .jar files reveals that the dex file from inside has been removed.
I've also tried copying the original .jar files over, rather than removing the .dex files on the fly.
However, the phone doesn't even boot, i.e. it doesn't even get past the splash image.
Can you see anything wrong with my logic/shell script?
Many thanks
Mark

Mekrel said:
Hi Sicopat,
I'm having issues with this.
I'm currently running XXKG6 ROM that I've successfully deodexed and after reading your thread, I've wrote the below shell script that successfully runs.
Code:
#!/system/bin/sh
chmod 755 /system/bin/dexopt-wrapper
chmod 755 /system/bin/zip
coreframework="/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"
echo "Odexing /system/framework/*jar files"
for i in $coreframework
do
filename=$(basename $i .jar)
dexopt-wrapper $i /system/framework/$filename.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
zip -d $i classes.dex
done
for i in /system/framework/*.jar
do
if [ $i == "/system/framework/core.jar" -o $i == "/system/framework/bouncycastle.jar" -o $i == "/system/framework/ext.jar" -o $i == "/system/framework/framework.jar" -o $i == "/system/framework/android.policy.jar" -o $i == "/system/framework/services.jar" -o $i == "/system/framework/core-junit.jar" ]
then
echo "Already odexed in sequence"
else
filename=$(basename $i .jar)
dexopt-wrapper $i /system/framework/$filename.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
zip -d $i classes.dex
fi
done
echo "Giving permissions to all *odex files"
chmod -R 777 /sdcard/original-framework/*.odex
chmod -R 777 /system/framework/*.odex
echo "Copying signatures from original odex files"
for i in /sdcard/original-framework/*.odex
do
filename=$(basename $i .odex)
busybox dd if=$i of=/system/framework/$filename.odex bs=1 count=20 skip=52 seek=52 conv=notrunc
done
rm -r /data/dalvik-cache/*
The script does the following process:
Sets permisions for the dexopt-wrapper and zip binaries.
Odexes the core framework in the same order they're listed in BOOTCLASSPATH in init.rc.
Odexes the other framework files that were not previously odexed
Copies the signatures from the original XXKG6 .odex files, to the ones that have just been created (the origials are stored on the sdcard)
The only difference in the script I wrote is the classes.dex are removed from the .jar files using the zip binary.
I can see the .odex files created when running a ls /system/framework command and pulling the .jar files reveals that the dex file from inside has been removed.
I've also tried copying the original .jar files over, rather than removing the .dex files on the fly.
However, the phone doesn't even boot, i.e. it doesn't even get past the splash image.
Can you see anything wrong with my logic/shell script?
Many thanks
Mark
Click to expand...
Click to collapse
Okay, I actually got this to work by removing the copying of signatures from the stock .odex files to the new ones.
I find that a little weird seeing as that step is specifically mentioned in your guide and that the phone is supposedly unable to boot without copying the signature.

After deodexing (and not odexing back) my framework and app folder of my custom ROM in my kitchen (before flashing),
is it necessary to sign/resign apks?

ok i have a few questions if you wouldnt mind helping.
i've been using androids since July of this year, only 2 months now, so i'm really new to modding...
i'm trying very hard to catch on and to learn...
unfortunately, i purchased a device with absolutely no development
anyway, assuming that you'll help, i'll proceed...
i'm not on a galaxy s II - i'm doing this on a gravity smart.
our bootclass path is different:
system/framework/core.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/android.policy.jar:/system/framework/services.jar
your bootclass path:
/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
so i removed the difference in your command example to this:
java -Xmx1024m -jar baksmali.jar -c :core.jar:framework.jar:android.policy.jar:services.jar -x android.policy.odex
all is fine, i get an "out" folder created with files in it
i then use your command example:
java -Xmx1024m -jar smali.jar out -o classes.dex
and a classes.dex is created
i then opened the android.policy.jar with 7zip and dropped the classes.dex file in its root
i'm assuming the process is going as its supposed to at this point.
question 1: am i doing this right?
question 2: do i do this to all the .jars in the /system/framework/ directory to have a completely deodexed system (and of course all the /system/app/files)?
question 3: do i also use these methods or the apk methods listed on your 2nd post to do the twframework-res.apk file?
question 4: do i create a new "out" folder for each .jar (run the command line for each .jar) or do i use the first created classes.dex for all the .jar files in /system/framework/ directory?
question 5: after i create the deodexed files i can safely delete the .odex companion files correct? (this may be a dumb question with an obvious answer, but i don't want to screw up)
question 6: can i place the deodexed files on the sdcard and move them with root explorer or do i need to push them thru using ADB?
any help or suggestions would be greatly appreciated!

NitroOnTheRocks said:
After deodexing (and not odexing back) my framework and app folder of my custom ROM in my kitchen (before flashing),
is it necessary to sign/resign apks?
Click to expand...
Click to collapse
Nope
Sent from my GT-I9100 using xda premium

Arhtard said:
ok i have a few questions if you wouldnt mind helping.
i've been using androids since July of this year, only 2 months now, so i'm really new to modding...
i'm trying very hard to catch on and to learn...
unfortunately, i purchased a device with absolutely no development
anyway, assuming that you'll help, i'll proceed...
i'm not on a galaxy s II - i'm doing this on a gravity smart.
our bootclass path is different:
system/framework/core.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/android.policy.jar:/system/framework/services.jar
your bootclass path:
/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
so i removed the difference in your command example to this:
java -Xmx1024m -jar baksmali.jar -c :core.jar:framework.jar:android.policy.jar:services.jar -x android.policy.odex
all is fine, i get an "out" folder created with files in it
i then use your command example:
java -Xmx1024m -jar smali.jar out -o classes.dex
and a classes.dex is created
i then opened the android.policy.jar with 7zip and dropped the classes.dex file in its root
i'm assuming the process is going as its supposed to at this point.
question 1: am i doing this right?
question 2: do i do this to all the .jars in the /system/framework/ directory to have a completely deodexed system (and of course all the /system/app/files)?
question 3: do i also use these methods or the apk methods listed on your 2nd post to do the twframework-res.apk file?
question 4: do i create a new "out" folder for each .jar (run the command line for each .jar) or do i use the first created classes.dex for all the .jar files in /system/framework/ directory?
question 5: after i create the deodexed files i can safely delete the .odex companion files correct? (this may be a dumb question with an obvious answer, but i don't want to screw up)
question 6: can i place the deodexed files on the sdcard and move them with root explorer or do i need to push them thru using ADB?
any help or suggestions would be greatly appreciated!
Click to expand...
Click to collapse
Q1/ yes
Q2/ yes if you want a deodexed Rom
Q3/you don't need to deodex twframework and framework-res ...
Q4/ you need to backsmali every files. You can rename out folders to core, android.policy, ... And replace out with the "name of folder" in smali command. Classes.dex is specific of 1 file
Q5Yes, you can delete odex files. This is the point of deodexing
Q6/ you can do the 2 ways, to try if deodexed files are correct, then correct the permissions and then backup and delete odex file. But for entire rom, the better is to use a non wipe script and to flash the entire deodexed Rom.
Finaly, there are many deodexing auto kit. I made an How to deodex resign and zipalign a customRom, try the kit-Deodexage included.
Or look for more used deodex script cause there are many apks to deodex, doing this manually will be very long ...
Sent from my GT-I9100 using xda premium

[MOD] Remove carrier label from status bar (odex/deodex)

Hi guys,
so, if you have an unlocked bootloader and have root access, you may apply my following mod. I'll guide you step through step as we got no CWM recovery yet, so you must do it manually.
If you have downloaded this mod previously and everything works, you are fine, but as reported by @geminihc he had no bars (navbar, status bar) after install, so you have to CHMOD the file, I added this to the code you have to enter:
- download your preferred version (BHR = back, home, recent, RHB = recent, home, back) and rename it to SystemUI.apk
- move it to your internal SD card with an explorer or via adb:
Code:
adb push SystemUI.apk /sdcard/
- after that type in the following commands (red lines backup the old files), beware that su wants you to grant root access (SuperSU popup)
Code:
adb shell
su
stop
mount -o rw,remount /system/ /system/
[COLOR="Red"]mv /system/app/SystemUI.apk /system/app/SystemUI.apk.bak
mv /system/app/SystemUI.odex /system/app/SystemUI.odex.bak[/COLOR]
cp /sdcard/SystemUI.apk /system/app/
rm /system/app/SystemUI.odex
chmod 644 /system/app/SystemUI.apk
mount -o ro,remount /system/ /system/
reboot
Done! Enjoy this mod
Reminder: Although this mod was tested on my device, I'll take no responsibility if you damage your system, so just do it if you know what you do!
If we have CWM, I will provide flashable .zip's then.

Thanks for this mod, just ordered my Moto G, will install it as soon as I get it
Just one question, does that also change the 3G icon to a more elegant and minimalistic H and H+ icon like on the Nexus? If not, is it hard to make such SystemUI.apk?

Thanks for this.
Just a quick suggestion: It might be a good idea to add a command that backs up the original SystemUI before overwriting it... It would be easier to restore the original if something goes wrong for someone.
EDIT: also, could you tell us how you managed to achieve this please?

flargen said:
It might be a good idea to add a command that backs up the original SystemUI before overwriting it...
[...]
EDIT: also, could you tell us how you managed to achieve this please?
Click to expand...
Click to collapse
I hope that someone who hacks with the adb console knows how to backup and restore as I said, I don't take any responsibility for damaging your system.
You may copy the original files to a temporary directory for sure before overwriting them:
Code:
cp /system/app/SystemUI.* /sdcard/tmp/
Notice that SystemUI.apk is odexed in original stock ROM, so you have to backup 2 files. When you apply my mod, you copy a DEodexed file to the system directory, so you need to remove the corresponding .odex file as you see in my how-to.
But for your convenience, I attached the original SystemUI.apk (14.71.8) to this post. This is already deodexed, so in case you don't like my mod, simply copy the .apk to /system/app and reboot, just as above. No need to deal with .odex-files.
Manage to achieve "what"? Navbar mod or the carrier label remove?
I edited statur_bar.xml for the carrier, and navigation_bar.xml for the navbar. Both are located in res/layout/

Anyone interested in a semi-transparent status bar?
In my case the launcher is Nova Launcher 2.3beta which supports transparent navbar, but status bar remained black, so I modded the SystemUI again.

shaftenberg said:
I hope that someone who hacks with the adb console knows how to backup and restore as I said, I don't take any responsibility for damaging your system.
You may copy the original files to a temporary directory for sure before overwriting them:
Code:
cp /system/app/SystemUI.* /sdcard/tmp/
Notice that SystemUI.apk is odexed in original stock ROM, so you have to backup 2 files. When you apply my mod, you copy a DEodexed file to the system directory, so you need to remove the corresponding .odex file as you see in my how-to.
But for your convenience, I attached the original SystemUI.apk (14.71.8) to this post. This is already deodexed, so in case you don't like my mod, simply copy the .apk to /system/app and reboot, just as above. No need to deal with .odex-files.
Manage to achieve "what"? Navbar mod or the carrier label remove?
I edited statur_bar.xml for the carrier, and navigation_bar.xml for the navbar. Both are located in res/layout/
Click to expand...
Click to collapse
Yep, I did mean "how to achieve removing the carrier label" Thanks for the info. I guess you're right about people who mess around with ADB in the first place!!

Why they aren't like this by default I do not know. Android dev team do realise our thumbs aren't that long?

theoneofgod said:
Android dev team do realise our thumbs aren't that long?
Click to expand...
Click to collapse
Maybe they are all lefties

shaftenberg said:
Hi guys,
- after that type in the following commands, beware that su wants you to grant root access (SuperSU popup)
Code:
adb shell
su
stop
mount -o rw,remount /system/ /system/
cp /sdcard/SystemUI.apk /system/app/
rm /system/app/SystemUI.odex
mount -o ro,remount /system/ /system/
reboot
Done! Enjoy this mod
.
Click to expand...
Click to collapse
sorry for a possibly stupid question, where do i enter these commands? I got terminal emulator on android but it doesn't seem to use these commands. thanks,
NVM: i figured i get to get the android SDK. cheers,

sorry to bump this up again, but i did somehting that screwed up my system. when rebooted, it keeps saying "Unforunately System UI has stopped" . when i first did it, i did screw up in that i accidentally closed my command prompt after i did "rm /system/app/SystemUI.odex"
but anyway, I re-did the whole thing again, reboot and that error showed.
So i tried to revert back to original using your backed up Systemui.apk but it is still saying that error. also when i try to do "rm /system/app/SystemUI.odex", it says file not found.
can someone please help? thanks!
update: i also tried fixing permissions via chmod 755 /system/app but still same error.. getting desperate will this help? this is a ls -l listing of my system/app around the systemui.apk . did i do something i'm not supposed to? note that this is using the OP's deodexed modified systemui.apk thanks,
-rw-r--r-- root root 79474 2013-10-26 11:20 SoundRecorder.apk
-rw-r--r-- root root 25704 2013-10-26 11:20 SoundRecorder.odex
-rw-r--r-- root root 28190 2013-10-26 11:20 Stk.apk
-rw-r--r-- root root 77592 2013-10-26 11:20 Stk.odex
-rw-r--r-- root root 264451 2013-10-26 11:20 Street.apk
--w----r-T root root 1966976 2008-08-01 05:00 Superuser.apk
-rwxr-xr-x root root 3099269 2013-12-01 10:44 SystemUI.apk
-rw-r--r-- root root 245294 2013-10-26 11:20 TagGoogle.apk
-rw-r--r-- root root 59251 2013-10-26 11:20 TelephonyProvider.apk
-rw-r--r-- root root 136496 2013-10-26 11:20 TelephonyProvider.odex
-

geminihc said:
update: i also tried fixing permissions via chmod 755 /system/app but still same error.. getting desperate
Click to expand...
Click to collapse
Which ROM? Country? But that shouldn't be a problem.
I'm trying out in mind where your error occurred...

Well, I don't know what you did, but try the following:
download attachment and put the content(!! - not the archive but the .apk and .odex) to your SD card manually or via adb:
Code:
adb push SystemUI.apk /sdcard/
adb push SystemUI.odex /sdcard/
then one after the other:
Code:
adb shell
su
stop
mount -o rw,remount /system/ /system/
cp /sdcard/SystemUI.apk /system/app/
cp /sdcard/SystemUI.odex /system/app/
rm -r /cache/*
rm /data/dalvik-cache/*
mount -o ro,remount /system/ /system/
reboot
this might help.

shaftenberg said:
Which ROM? Country? But that shouldn't be a problem.
I'm trying out in mind where your error occurred...
Click to expand...
Click to collapse
canada, the stock ROM (rooted and unlocked bootloader)

I advise you to copy the lines with crtl-c and insert it into your console just to avoid typing errors.
[edit]
you set the wrong permissions!!
type
Code:
chmod 644 /system/app/SystemUI.apk
chmod 644 /system/app/SystemUI.odex

shaftenberg said:
Well, I don't know what you did, but try the following:
download attachment and put the content(!! - not the archive but the .apk and .odex) to your SD card manually or via adb:
Code:
adb push SystemUI.apk /sdcard/
adb push SystemUI.odex /sdcard/
then one after the other:
Code:
adb shell
su
stop
mount -o rw,remount /system/ /system/
cp /sdcard/SystemUI.apk /system/app/
cp /sdcard/SystemUI.odex /system/app/
rm -r /cache/*
rm /data/dalvik-cache/*
mount -o ro,remount /system/ /system/
reboot
this might help.
Click to expand...
Click to collapse
thank you! it did not fully fix it but at least now it does not keep showing the error loop so i can use my phone, BUT i'm missing the bottom system bar (the back home recent buttons).. lol.. i'm going SOMEWHERE

geminihc said:
thank you! it did not fully fix it but at least now it does not keep showing the error loop so i can use my phone, BUT i'm missing the bottom system bar (the back home recent buttons).. lol.. i'm going SOMEWHERE
Click to expand...
Click to collapse
read my edit, you set the wrong permissions.

shaftenberg said:
read my edit, you set the wrong permissions.
Click to expand...
Click to collapse
i fixed the permissions back, cleared both the cache but still missing bar after reboot. now the listing is:
-rw-r--r-- root root 28190 2013-10-26 11:20 Stk.apk
-rw-r--r-- root root 77592 2013-10-26 11:20 Stk.odex
-rw-r--r-- root root 264451 2013-10-26 11:20 Street.apk
--w----r-T root root 1966976 2008-08-01 05:00 Superuser.apk
-rw-r--r-- root root 2948805 2013-12-01 11:16 SystemUI.apk
-rw-r--r-- root root 695088 2013-12-01 11:16 SystemUI.odex
-rw-r--r-- root root 245294 2013-10-26 11:20 TagGoogle.apk
-rw-r--r-- root root 59251 2013-10-26 11:20 TelephonyProvider.apk
-rw-r--r-- root root 136496 2013-10-26 11:20 TelephonyProvider.odex
is something preventing the systemUI from loading..?

geminihc said:
is something preventing the systemUI from loading..?
Click to expand...
Click to collapse
The only thing I can guess is that the retail SystemUI.apk is not compatible to the canadian version, but I don't think so.
Pretty weird... Have you backed up your SystemUI.apk? Otherwise you have to flash your ROM again as a last resort :/

shaftenberg said:
The only thing I can guess is that the retail SystemUI.apk is not compatible to the canadian version, but I don't think so.
Pretty weird... Have you backed up your SystemUI.apk? Otherwise you have to flash your ROM again as a last resort :/
Click to expand...
Click to collapse
unfortunately i didnt back it up stupid me. but the version should be the 8GB global version (not the US version). i believe there are only 2 versions of this phone.
i realize that the notification bar is also gone, i guess thats part of the systemui.apk

geminihc said:
i realize that the notification bar is also gone, i guess thats part of the systemui.apk
Click to expand...
Click to collapse
Yes, this is part of SystemUI.apk
So sad, sorry
I added a warning to the opening post. Never thought of an incompatibility, but maybe there are language resources missing between german and canadian version.
However, using RSDlite is quite easy, there is a thread here.

ADB system remount FAIL

hi, quick question .
im trying to remount the system folder to R\W , but seems like no luck .
adb remount
*permission denied
adb shell
Code:
C:\android sdk\sdk\platform-tools>adb shell
[email protected]:/ $ su
su
[email protected]:/ # mount -o rw,remount /system
mount -o rw,remount /system
[email protected]:/ #
[email protected]:/ # exit
exit
[email protected]:/ $ exit
exit
C:\android sdk\sdk\platform-tools>adb push C:\Users\HOME\Desktop\build.prop /sys
tem
failed to copy 'C:\Users\HOME\Desktop\build.prop' to '/system/build.prop': Permi
ssion denied
shell - fail
normal remount -fail
whats next.any suggestions?

cant do that yet, you need kernel with unsecure adb .

Helloworld294 said:
cant do that yet, you need kernel with unsecure adb .
Click to expand...
Click to collapse
Means I can't tweak my phone safely? (1 bootloop and I'm on stock again? )

subwoffer13 said:
Means I can't tweak my phone safely? (1 bootloop and I'm on stock again? )
Click to expand...
Click to collapse
You bootloop you're on stock again, with formatted /data/media of course.
EDIT: So I downloaded adb insecure from playstore by chainfire and it seems to work actually. Its $2 though.
Sent from my LG-D852 using Tapatalk

Helloworld294 said:
You bootloop you're on stock again, with formatted /data/media of course.
EDIT: So I downloaded adb insecure from playstore by chainf
ire and it seems to work actually. Its $2 though.
Sent from my LG-D852 using Tapatalk
Click to expand...
Click to collapse
Well, just bought it too.going to slepp right now, tomorrow hopefully I'll be able to push and pull files with adb.

subwoffer13 said:
Well, just bought it too.going to slepp right now, tomorrow hopefully I'll be able to push and pull files with adb.
Click to expand...
Click to collapse
Before pulling/pushing anything from system
run 'chmod 777 /system'
And before pushing/pulling any file chmod 666 the file and after dont ever forget to chmod 644 any system or data file after pushing or else you gonna end up in bootloop.
Sent from my LG-D852 using Tapatalk

Helloworld294 said:
Before pulling/pushing anything from system
run 'chmod 777 /system'
And before pushing/pulling any file chmod 666 the file and after dont ever forget to chmod 644 any system or data file after pushing or else you gonna end up in bootloop.
Sent from my LG-D852 using Tapatalk
Click to expand...
Click to collapse
.ok , i am a bit confused .i understand that every time im pulling or pushing i should fix the permissions. Bit what is the exact order ?
Shouldn't i just make sure the file im only pushing is 644 (rw-r-r)?
Lets say for example , i want to push stock "build.prop" to system .
What are the steps?

subwoffer13 said:
.ok , i am a bit confused .i understand that every time im pulling or pushing i should fix the permissions. Bit what is the exact order ?
Shouldn't i just make sure the file im only pushing is 644 (rw-r-r)?
Lets say for example , i want to push stock "build.prop" to system .
What are the steps?
Click to expand...
Click to collapse
Mount everything and do su and all that then chmod 777 /system
Then do the push "adb push 'source file location' /system/build.prop
Then do chmod 644 /system/build.prop
All done.
Sent from my LG-D852 using Tapatalk

note 4 sm-n910g how to mount system write only on adb shell

trying lots but ab shell say system is read only ??

Krprem said:
trying lots but ab shell say system is read only ??
Click to expand...
Click to collapse
#1 you need to be rooted, if you're not this won't work
Mount system RW: mount -o rw,remount,rw /system
Mount system RO: mount -o ro,remount,ro /system

dicksteele said:
#1 you need to be rooted, if you're not this won't work
Mount system RW: mount -o rw,remount,rw /system
Mount system RO: mount -o ro,remount,ro /system
Click to expand...
Click to collapse
i try its work but when i reboot modifiy file gone away ...??
any premanet fix bro ??
thank u in advance

Krprem said:
i try its work but when i reboot modifiy file gone away ...??
any premanet fix bro ??
thank u in advance
Click to expand...
Click to collapse
You must not have saved it right or something.
Find a file manager in playstore that can do root privileges.
Or since you know adb. Pull the file, edit it then push it back.
Adb pull /system/build.prop
Edit the file
Adb push /system/build.prop

Bro can u give me step by step instruction about adb push and pull
Can i edit my efs folder because i lost my csc code and sn number
I am trying to add new folder in efs