Database Develop

Assembling Dex files

Hello, i want to know how can i assemble the DEX Files after extracting them out? i tried the command :
Code:
java -jar baksmali.jar out
but i get this error
Code:
C:\>java -jar baksmali.jar out
UNEXPECTED TOP-LEVEL EXCEPTION:
java.lang.RuntimeException: out: not a file
at org.jf.dexlib.Util.FileUtils.readFile(FileUtils.java:77)
at org.jf.dexlib.DexFile.<init>(DexFile.java:288)
at org.jf.baksmali.main.main(main.java:161)
i can extract it out using :
Code:
java -jar smali.jar classes.dex
any help will be appreciated

instead out out, put the filename? classes.dex? see if that works. I havent used baksmali/smali but i would imagine thats whats happening as the exception says not a file lol

I think the Command you're Looking for is
run following from command line: java -jar baksmali.jar -o classout/ classes.dex

that just extracts the file ;/ i need to put the extracted files back ;(
I think the Command you're Looking for is
run following from command line: java -jar baksmali.jar -o classout/ classes.dex
Click to expand...
Click to collapse

[Q] Odex before compression

Is it possible to odex a system before I compress it into a androidinstall and send it to my device to install?
If so how?

only way i have found to odex is through the phone

How do people release odex'ed builds then?

2 ways
1. if adb works push the odex script to /data run the scrpit (search odex donut or dzo's instructions on how to use it), then do an adb pull of /system then repack it into a .tar and go
2 adb doesnt work for me so here is how i do it, i load up my build and in the /data folder i have the odex script, i run the script using terminal emulator, then i restart after its finished and put in a blank sd card then i copy the app and framework folders from /system to the SD and replace those folders in the original .tar with the newly odex'd ones

I put the odex script into data and then added it to init

jholtom said:
Is it possible to odex a system before I compress it into a androidinstall and send it to my device to install?
If so how?
Click to expand...
Click to collapse
I asked dzo once and he answered me, in the Fresh Froyo thread. The search function isn't working right now, but when you read this it might be working. Another thread described things in more detail, but I long ago forgot where that thread is. I never got odexing to work outside the phone, but here is the script I have tried. Note that the dexpreopt.py python script has to be edited to mount system as read/write, or it completely fails. I run this after a complete build.
Code:
#! /bin/sh
. build/envsetup.sh
lunch us_vogue-userdebug
rm out/target/product/vogue/obj/PACKAGING/systemimage_unopt_intermediates/system.img
ONE_SHOT_MAKEFILE=/home/devel/android/build/tools/dexpreopt/Android.mk make -C /home/devel/android/ files
make
mkdir /tmp/system-odex
rm -rf /tmp/system-odex/system
cp -ra out/target/product/vogue/system /tmp/system-odex
dexpreopt.py --outsystemdir=/tmp/system-odex/system
for i in /tmp/system-odex/system/app/*.apk; do zipalign -f 4 $i /tmp/zip; mv /tmp/zip $i; done
tar -C /tmp/system-odex -czf odex.tgz system

n2rjt said:
I asked dzo once and he answered me, in the Fresh Froyo thread. The search function isn't working right now, but when you read this it might be working. Another thread described things in more detail, but I long ago forgot where that thread is. I never got odexing to work outside the phone, but here is the script I have tried. Note that the dexpreopt.py python script has to be edited to mount system as read/write, or it completely fails. I run this after a complete build.
Code:
#! /bin/sh
. build/envsetup.sh
lunch us_vogue-userdebug
rm out/target/product/vogue/obj/PACKAGING/systemimage_unopt_intermediates/system.img
ONE_SHOT_MAKEFILE=/home/devel/android/build/tools/dexpreopt/Android.mk make -C /home/devel/android/ files
make
mkdir /tmp/system-odex
rm -rf /tmp/system-odex/system
cp -ra out/target/product/vogue/system /tmp/system-odex
dexpreopt.py --outsystemdir=/tmp/system-odex/system
for i in /tmp/system-odex/system/app/*.apk; do zipalign -f 4 $i /tmp/zip; mv /tmp/zip $i; done
tar -C /tmp/system-odex -czf odex.tgz system
Click to expand...
Click to collapse
ok thanks
I'll work with it

Also there is a script I use to odex files as they are downloaded from the market or installed on the phone. It is inside of my barebones build and if you look inside my userinit from my build you will see the call to the file.
Edit: I do not take credit for it, I just claim to be a source of the file as I already have it.

[TUTORIAL] Self-assembly of Android Firmwares

I just saw a tutorial in 4PDA by R0iz and wanted to share it here!
The link to the original post translated:
http://tinyurl.com/self-assembly-androidOS
Extract the files *. img
To extract system.img, used unyaffs (http://code.google.com/p/unyaffs/)
I have compiled under Ubuntu 64. With Unyaffs can only be extracted system.img.
To extract boot.img use extract-kernel.pl and extract-ramdisk.pl
# extract-kernel.pl boot.img
# extract-ramdisk.pl boot.img
Click to expand...
Click to collapse
Rebuilding boot.img
After extracting boot.img with the enclosed extract-*. pl
In order to collect boot.img with Custom kernel in the same folder run:
# mkbootfs boot.img-ramdisk | gzip > ramdisk-boot
# mkbootimg --kernel boot.img-kernel --ramdisk ramdisk-boot --cmdline "no_console_suspend=1 console=null" -o newBoot.img --base 0x19200000
Click to expand...
Click to collapse
Rebuilding system.img
At first glance it seems that you can simply mount the image and format it with YAFFS, but it's not because, as SPL Hero does not allow flash system.img directly.
You must use the format update.zip packages for this. (читайте ниже) (See below)
Write update.zip quite simple really. For example, to add the package test.apk in your rum:
- Create an empty folder <workdir>
- Create a folder structure for test.apk (<workdir> / system / app) and copy test.apk
- Create a folder structure for the update-script (<workdir> / META-INF/com/google/android)
- Edit <workdir> / META-INF/com/google/android/update-script
- Insert the following:
show_progress 0.1 0 show_progress 0.1 0
copy_dir PACKAGE:system SYSTEM: copy_dir PACKAGE: system SYSTEM:
set_perm_recursive 0 0 0755 0644 SYSTEM:app set_perm_recursive 0 0 0755 0644 SYSTEM: app
show_progress 0.1 10 show_progress 0.1 10
- Pack the contents <workdir> in zip (not the folder itself <workdir>, only its contents)
Now you have to sign a zip file. Testsign.zip download and copy it to your <SDK> / tools.
Unzip it there, thus creating a sub-folder sign with a file testsign. in it.
Then in the folder <workdir>, run this command:
java-classpath "<SDK> / tools / sign / testsign.jar" testsign file.zip file-signed.zip
Everything is now ready for your update.zip pouring into the apparatus by a modified recovery.
Click to expand...
Click to collapse
Change. Apk package
apk can just unpack an archive, change what you need and pack it back. But in the end you have to sign it as well as update.zip packages.
ODEX files
- What is it? Answer
- How to get rid of them?
For deodex ODEX files, use this howto
Then you can create classes.dex file by running smali from your "out". Then rename it to classes.dex and add it to apk.
- How to create them?
Use dexopt-wrapper on the device.
Click to expand...
Click to collapse
Porting ROM with other devices.
Well, this part is simple smile_good.gif
- Extract system.img
- Extract boot.img
- Replace boot.img-kernel of the original Roma HTC Hero.
- Rebuild boot.img
- Collect update.zip (see how it's done in any Custom rum for Hero)
- Sign and flash.
Device should start, and even be able to call, but probably will not work WiFi, BT, trackball.
Androsign script (Linux)
Androsign allows you to quickly sign the zip and apk. Just put it in <SDK> / tools, then CHMOD + X. If the path to the folder \ tools registered in the PATH, then you can run this script by typing:
androsign /dev/folder1/folder2/update.zip
He will Update-signed.zip (or App-signed.apk, etc.) in the same folder where the original file.
THANKS ARE WELCOMED!

Can we actually use this to port Sense or MIUI ?

this explains part of the process, the steps to do fo that purpose extracting and rebuilding but of course not about the code. i've heard MIUI is complex than sense

Most of us know this allready but nice to see it being said instead of learning the hard way
Sent from my GT540 using XDA Premium App

[Q] Reverse engineering framework files

I had a look at LG GearBox for Optimus 4X application source code and saw that it uses functions in com.lge.systemservice.core.jar file which is located in /system/framework folder.
Since this application does not work on JB, I thought I could find similar functions for JB in other jar files of the framework and copied the whole framework folder to my PC and tried to baksmali/smali com.lge.systemservice.core.odex file.
These are the commands I tried: (I have the latest versions of smali and baksmali)
java -jar baksmali.jar -x -o .\out com.lge.systemservice.core.odex
java -jar smali.jar out
The first line works OK and creates the smali files but I need to put them back to an "out.dex" file with the second line so that I can use dex2jar application to turn the smali files to java .class files to read the source code better. (dex2jar works on dex files, not on odex files)
The second line does not work and outputs lots of error messages.
Is there any developer out there who has ever done this operation to reverse engineer framework odex files?
A second question: Do the source files for the framework exist in the source code of v20A which is on LG Open web site?
My questions may be a bit complicated but I'm sure they will mean something to those who have worked with these tools.

As far as I understand, nobody in this forum has had experience with decompiling Android applications.

Have you tried specifying the framework path on the baksmali line?
I've never got errors from running smali before.
Sent from my LG-P880 using Tapatalk 4 Beta

arararagi said:
Have you tried specifying the framework path on the baksmali line?
I've never got errors from running smali before.
Sent from my LG-P880 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Baksmali is ok. I have errors with smali line.
Sent from my LG-P880

google virtous ten studio a nice tool to decompile/compile jars/apks
or java -Xmx512M –jar smali.jar dex –o classes.dex
Sent from my LG-P880 using xda app-developers app

postacik said:
Baksmali is ok. I have errors with smali line.
Sent from my LG-P880
Click to expand...
Click to collapse
Does the error on the smali line go away if you specify the framework path on the baksmali line?

arararagi said:
Does the error on the smali line go away if you specify the framework path on the baksmali line?
Click to expand...
Click to collapse
No, it doesn't.
Can you try to baksmali and then smali the file I specified in the first post?
By the way, thank you all very much for the replies.
Sent from my LG-P880

postacik said:
No, it doesn't.
Can you try to baksmali and then smali the file I specified in the first post?
By the way, thank you all very much for the replies.
Sent from my LG-P880
Click to expand...
Click to collapse
Works fine.
Code:
$ baksmali -x -d eur_open_jb_system/system/framework -o com.lge.systemservice.core eur_open_jb_system/system/framework/com.lge.systemservice.core.odex
$ smali -o com.lge.systemservice.core.dex com.lge.systemservice.core
$ ls -ln com.lge.systemservice.core.dex
-rw-rw-r-- 1 1000 1000 98816 Jun 11 12:46 com.lge.systemservice.core.dex

arararagi said:
Works fine.
Code:
$ baksmali -x -d eur_open_jb_system/system/framework -o com.lge.systemservice.core eur_open_jb_system/system/framework/com.lge.systemservice.core.odex
$ smali -o com.lge.systemservice.core.dex com.lge.systemservice.core
$ ls -ln com.lge.systemservice.core.dex
-rw-rw-r-- 1 1000 1000 98816 Jun 11 12:46 com.lge.systemservice.core.dex
Click to expand...
Click to collapse
So you are awake at this time of the night.(Well, the sun is rising here in Turkey)
I tried it again with your syntax, thinking I might have misspelled some of the options but it's still the same. I get errors like the following:
Code:
java -jar baksmali.jar -x -d ./framework -o com.lge.systemservice.core ./framework/com.lge.systemservice.core.odex
java -jar smali.jar -o com.lge.systemservice.core.dex com.lge.systemservice.core
Code:
com.lge.systemservice.core\com\lge\systemservice\core\nfclgmanager\NfcLgManager.
smali[181,15] no viable alternative at input 'e'
com.lge.systemservice.core\com\lge\systemservice\core\nfclgmanager\NfcLgManager.
smali[181,17] no viable alternative at input 'Landroid/os/RemoteException;'
com.lge.systemservice.core\com\lge\systemservice\core\nfclgmanager\NfcLgManager.
smali[193,4] Error for input '.parameter': Invalid directive
com.lge.systemservice.core\com\lge\systemservice\core\nfclgmanager\NfcLgManager.
smali[194,4] Error for input '.parameter': Invalid directive
com.lge.systemservice.core\com\lge\systemservice\core\nfclgmanager\NfcLgManager.
smali[193,15] mismatched input '"command"' expecting END_METHOD_DIRECTIVE
I am working on Windows. Are you on cygwin or Linux?
Anyway, thank your for the attached file. Now I will try dex2jar on that.

postacik said:
So you are awake at this time of the night.(Well, the sun is rising here in Turkey)
I tried it again with your syntax, thinking I might have misspelled some of the options but it's still the same. I get errors like the following:
Code:
java -jar baksmali.jar -x -d ./framework -o com.lge.systemservice.core ./framework/com.lge.systemservice.core.odex
java -jar smali.jar -o com.lge.systemservice.core.dex com.lge.systemservice.core
Code:
com.lge.systemservice.core\com\lge\systemservice\core\nfclgmanager\NfcLgManager.
smali[181,15] no viable alternative at input 'e'
com.lge.systemservice.core\com\lge\systemservice\core\nfclgmanager\NfcLgManager.
smali[181,17] no viable alternative at input 'Landroid/os/RemoteException;'
com.lge.systemservice.core\com\lge\systemservice\core\nfclgmanager\NfcLgManager.
smali[193,4] Error for input '.parameter': Invalid directive
com.lge.systemservice.core\com\lge\systemservice\core\nfclgmanager\NfcLgManager.
smali[194,4] Error for input '.parameter': Invalid directive
com.lge.systemservice.core\com\lge\systemservice\core\nfclgmanager\NfcLgManager.
smali[193,15] mismatched input '"command"' expecting END_METHOD_DIRECTIVE
I am working on Windows. Are you on cygwin or Linux?
Anyway, thank your for the attached file. Now I will try dex2jar on that.
Click to expand...
Click to collapse
Linux, but it's all Java so it doesn't matter. I'm using 1.4.2.

I used dex2jar on the dex file you provided and unfortunately it does not contain the functions that LG GearBox for Optimus 4X uses so I think I have to look elsewhere.
But the file contains a class which contains functions about bootloader unlocking.
I have not followed the bootloader unlock discussions lately but I think it may help somebody to better understand how it works.
The file is attached to this post.

arararagi said:
Linux, but it's all Java so it doesn't matter. I'm using 1.4.2.
Click to expand...
Click to collapse
I'm also using 1.4.2 version of smali and baksmali.
In theory yes, it should not matter since it's all Java but I tried the same commands on cygwin and it worked without any problems.
On cygwin, I could use the smali and baksmali scripts provided along with tha jar files. I don't have time to investigate why, but with the scripts it worked flawlessly.
Thank you very much for the enlightment.
Code:
./baksmali -x -d ./framework -o com.lge.systemservice.core ./framework/com.lge.systemservice.core.odex
./smali -o com.lge.systemservice.core.dex com.lge.systemservice.core

tobixdev said:
google virtous ten studio a nice tool to decompile/compile jars/apks
or java -Xmx512M –jar smali.jar dex –o classes.dex
Sent from my LG-P880 using xda app-developers app
Click to expand...
Click to collapse
I wasn't aware of Virtous Ten Studio until you wrote here. Thank you very much.
It is a great GUI which uses baksmali, smali, dex2jar, apktool and signapk under cover.
All the things I've learned by reading many documents have been packed into one application.

[Q] Help with deodexing stock XXBMF1

Hi.
Been trying to deodex my favourite stock XXBMF1.
Working on dsixda kitchen and for some reason can`t go any further with deodexing as stuck with 2 files from framework directory.
Have a look below please and let me know what can be done to finish with deodexing.
Thanks a lot in advance.
p.s. Tried deodexing files manually but no luck either..
Code:
Going into system/framework ...
NOW AT FILE 1 OF 2 IN system/framework: framework.odex
Disassembling framework.odex ...
java -Xmx512m -jar baksmali.jar -a 17 -d ../framework -x framework.odex
Error occured while disassembling class Lcom.android.internal.telephony.gsm.GsmCallTracker; - skipping class
java.lang.RuntimeException: regCount does not match the number of arguments of the method
at org.jf.dexlib.Code.Format.Instruction35c.checkItem(Instruction35c.java:160)
at org.jf.dexlib.Code.Format.Instruction35c.<init>(Instruction35c.java:69)
at org.jf.dexlib.Code.Analysis.MethodAnalyzer.analyzeInvokeVirtualQuick(MethodAnalyzer.java:3681)
at org.jf.dexlib.Code.Analysis.MethodAnalyzer.analyzeInstruction(MethodAnalyzer.java:1106)
at org.jf.dexlib.Code.Analysis.MethodAnalyzer.analyze(MethodAnalyzer.java:213)
at org.jf.baksmali.Adaptors.MethodDefinition.addAnalyzedInstructionMethodItems(MethodDefinition.java:389)
at org.jf.baksmali.Adaptors.MethodDefinition.getMethodItems(MethodDefinition.java:311)
at org.jf.baksmali.Adaptors.MethodDefinition.writeTo(MethodDefinition.java:132)
at org.jf.baksmali.Adaptors.ClassDefinition.writeMethods(ClassDefinition.java:338)
at org.jf.baksmali.Adaptors.ClassDefinition.writeVirtualMethods(ClassDefinition.java:310)
at org.jf.baksmali.Adaptors.ClassDefinition.writeTo(ClassDefinition.java:117)
at org.jf.baksmali.baksmali.disassembleDexFile(baksmali.java:186)
at org.jf.baksmali.main.main(main.java:308)
Assembling into classes.dex ...
java -Xmx512m -jar smali.jar -a 17 -o classes.dex out
out\com\android\internal\telephony\gsm\GsmCallTracker.smali[0,-1] no viable alternative at input '<EOF>'
WARNING: Unable to produce classes.dex!
ERROR: Aborting framework.odex
NOW AT FILE 2 OF 2 IN system/framework: framework2.odex
Disassembling framework2.odex ...
java -Xmx512m -jar baksmali.jar -a 17 -d ../framework -x framework2.odex
Error occured while disassembling class Lcom.android.internal.telephony.msim.MSimCDMAPhone; - skipping class
java.lang.RuntimeException: regCount does not match the number of arguments of the method
at org.jf.dexlib.Code.Format.Instruction35c.checkItem(Instruction35c.java:160)
at org.jf.dexlib.Code.Format.Instruction35c.<init>(Instruction35c.java:69)
at org.jf.dexlib.Code.Analysis.MethodAnalyzer.analyzeInvokeVirtualQuick(MethodAnalyzer.java:3681)
at org.jf.dexlib.Code.Analysis.MethodAnalyzer.analyzeInstruction(MethodAnalyzer.java:1106)
at org.jf.dexlib.Code.Analysis.MethodAnalyzer.analyze(MethodAnalyzer.java:213)
at org.jf.baksmali.Adaptors.MethodDefinition.addAnalyzedInstructionMethodItems(MethodDefinition.java:389)
at org.jf.baksmali.Adaptors.MethodDefinition.getMethodItems(MethodDefinition.java:311)
at org.jf.baksmali.Adaptors.MethodDefinition.writeTo(MethodDefinition.java:132)
at org.jf.baksmali.Adaptors.ClassDefinition.writeMethods(ClassDefinition.java:338)
at org.jf.baksmali.Adaptors.ClassDefinition.writeDirectMethods(ClassDefinition.java:294)
at org.jf.baksmali.Adaptors.ClassDefinition.writeTo(ClassDefinition.java:116)
at org.jf.baksmali.baksmali.disassembleDexFile(baksmali.java:186)
at org.jf.baksmali.main.main(main.java:308)
Error while disassembling method Lcom/android/internal/telephony/msim/MSimCdmaDataConnectionTracker;->getUiccCardApplication()Lcom/android/internal/telephony/uicc/IccRecords;. Continuing.
org.jf.dexlib.Code.Analysis.ValidationException: Could not resolve the field in class Ljava/lang/String; at offset 36
at org.jf.dexlib.Code.Analysis.MethodAnalyzer.analyzeIputIgetQuick(MethodAnalyzer.java:3590)
at org.jf.dexlib.Code.Analysis.MethodAnalyzer.analyzeInstruction(MethodAnalyzer.java:1104)
at org.jf.dexlib.Code.Analysis.MethodAnalyzer.analyze(MethodAnalyzer.java:213)
at org.jf.baksmali.Adaptors.MethodDefinition.addAnalyzedInstructionMethodItems(MethodDefinition.java:389)
at org.jf.baksmali.Adaptors.MethodDefinition.getMethodItems(MethodDefinition.java:311)
at org.jf.baksmali.Adaptors.MethodDefinition.writeTo(MethodDefinition.java:132)
at org.jf.baksmali.Adaptors.ClassDefinition.writeMethods(ClassDefinition.java:338)
at org.jf.baksmali.Adaptors.ClassDefinition.writeVirtualMethods(ClassDefinition.java:310)
at org.jf.baksmali.Adaptors.ClassDefinition.writeTo(ClassDefinition.java:117)
at org.jf.baksmali.baksmali.disassembleDexFile(baksmali.java:186)
at org.jf.baksmali.main.main(main.java:308)
opcode: iget-quick
CodeAddress: 10
Method: Lcom/android/internal/telephony/msim/MSimCdmaDataConnectionTracker;->getUiccCardApplication()Lcom/android/internal/telephony/uicc/IccRecords;
Error while disassembling method Lcom/android/internal/telephony/msim/MSimCdmaDataConnectionTracker;->update()V. Continuing.
org.jf.dexlib.Code.Analysis.ValidationException: Could not resolve the method in class Lcom/android/internal/telephony/msim/MSimCDMAPhone; at index 317
at org.jf.dexlib.Code.Analysis.MethodAnalyzer.analyzeInvokeVirtualQuick(MethodAnalyzer.java:3655)
at org.jf.dexlib.Code.Analysis.MethodAnalyzer.analyzeInstruction(MethodAnalyzer.java:1106)
at org.jf.dexlib.Code.Analysis.MethodAnalyzer.analyze(MethodAnalyzer.java:213)
at org.jf.baksmali.Adaptors.MethodDefinition.addAnalyzedInstructionMethodItems(MethodDefinition.java:389)
at org.jf.baksmali.Adaptors.MethodDefinition.getMethodItems(MethodDefinition.java:311)
at org.jf.baksmali.Adaptors.MethodDefinition.writeTo(MethodDefinition.java:132)
at org.jf.baksmali.Adaptors.ClassDefinition.writeMethods(ClassDefinition.java:338)
at org.jf.baksmali.Adaptors.ClassDefinition.writeVirtualMethods(ClassDefinition.java:310)
at org.jf.baksmali.Adaptors.ClassDefinition.writeTo(ClassDefinition.java:117)
at org.jf.baksmali.baksmali.disassembleDexFile(baksmali.java:186)
at org.jf.baksmali.main.main(main.java:308)
opcode: invoke-virtual-quick
CodeAddress: 42
Method: Lcom/android/internal/telephony/msim/MSimCdmaDataConnectionTracker;->update()V
ERROR: Aborting framework2.odex
Finished system/framework
WARNING: Could not deodex the following (you can try to deodex these files again):
framework.odex framework2.odex
A summary of the deodexing has been logged in deodex_100113_204254.log
135 *.odex files remain in system/app
2 *.odex files remain in system/framework
Press Enter to continue