Cannot deodex when both jar and odex files are present about smali

[JesusFreke]

Comment #1 originally posted by JesusFreke on 2010-03-03T05:03:43.000Z:

Good catch :). I'll get this fixed in the next version. A temporary work around is to
delete or rename the framework jar files, leaving only the odex files.

[JesusFreke]

Comment #2 originally posted by JesusFreke on 2010-03-03T07:12:05.000Z:

That did the trick!

[JesusFreke]

Comment #3 originally posted by JesusFreke on 2010-03-03T17:14:45.000Z:

YES! This is the EXACT issue I was running into. Im glad im not the only one...My
understanding is renaming core.jar to core.jar.bak and so on...Correct?

[JesusFreke]

Comment #4 originally posted by JesusFreke on 2010-03-03T17:29:32.000Z:

I must be doing something wrong...I tried to rename the files, but it didnt
work...Can someone shed some light on this for me? Thank you!

[JesusFreke]

Comment #5 originally posted by JesusFreke on 2010-03-04T00:17:50.000Z:

This is what I get when I rename, or delete the framework jar files.

java -jar baksmali-1.2.jar -x services.odex

Error occured while loading boot class path files. Aborting.
org.jf.dexlib.Code.Analysis.ValidationException: class
Landroid/content/DialogInterface$OnCancelListener; cannot be resolved.
at
org.jf.dexlib.Code.Analysis.ClassPath$UnresolvedClassDef.unresolvedValidationException(ClassPath.java:391)
at
org.jf.dexlib.Code.Analysis.ClassPath$UnresolvedClassDef.getSuperclass(ClassPath.java:395)
at
org.jf.dexlib.Code.Analysis.ClassPath$ClassDef.loadAllImplementedInterfaces(ClassPath.java:676)
at org.jf.dexlib.Code.Analysis.ClassPath$ClassDef.(ClassPath.java:532)
at org.jf.dexlib.Code.Analysis.ClassPath.loadDexFile(ClassPath.java:127)
at org.jf.dexlib.Code.Analysis.ClassPath.loadBootClassPath(ClassPath.java:118)
at org.jf.dexlib.Code.Analysis.ClassPath.initClassPath(ClassPath.java:64)
at org.jf.dexlib.Code.Analysis.ClassPath.InitializeClassPath(ClassPath.java:54)
at org.jf.baksmali.baksmali.disassembleDexFile(baksmali.java:68)
at org.jf.baksmali.main.main(main.java:263)

[JesusFreke]

Comment #6 originally posted by JesusFreke on 2010-03-04T00:58:20.000Z:

That's not the same error. You've gotten past the jar issue. Please create a new issue.

[JesusFreke]

Comment #7 originally posted by JesusFreke on 2010-03-04T02:18:26.000Z:

<empty>

[JesusFreke]

Comment #8 originally posted by JesusFreke on 2010-03-06T06:28:49.000Z:

This is fixed in 1.2.1