search

berkus / smali

Automatically exported from code.google.com/p/smali
0 stars 0 forks source link

1.3.0 not working with ICS 4.0.3 #99

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What seems to be the problem?
Can't deodex the new 4.0.3 SGS2 build.

What is the exact smali/baksmali command that you ran?
java -Xmx1024m -jar baksmali.jar -d %bootclasspath% -c 
core.jar:core-junit.jar:bouncycastle.jar:ext.jar:framework.jar:android.policy.ja
r:services.jar:apache-xml.jar:filterfw.jar -x am.odex

What version of smali/baksmali are you using? What rom are you working
from?
1.3.0

What is the airspeed velocity of an unladen swallow?
African or European?

Please provide any additional information below: error messages, symptoms,
etc.

UNEXPECTED TOP-LEVEL EXCEPTION:
org.jf.dexlib.Util.ExceptionWithContext: The magic value is not the expected 
value
        at org.jf.dexlib.Util.ExceptionWithContext.withContext(ExceptionWithCont
ext.java:54)
        at org.jf.dexlib.Item.addExceptionContext(Item.java:176)
        at org.jf.dexlib.Item.readFrom(Item.java:78)
        at org.jf.dexlib.DexFile.<init>(DexFile.java:390)
        at org.jf.baksmali.main.main(main.java:265)
Caused by: java.lang.RuntimeException: The magic value is not the expected value

        at org.jf.dexlib.HeaderItem.readItem(HeaderItem.java:64)
        at org.jf.dexlib.Item.readFrom(Item.java:76)
        ... 2 more
header_item

happens on every odex file I try to deodex.

Original issue reported on code.google.com by shauli.b...@gmail.com on 1 Jan 2012 at 7:04

GoogleCodeExporter commented 9 years ago 
I have also this problem

Original comment by stratos....@gmail.com on 1 Jan 2012 at 8:00

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
Can you print out the odex and dex magic values for that odex file?

hd -n 8 am.odex

and 

hd -s 40 -n 8 am.odex

Original comment by jesusfreke@jesusfreke.com on 2 Jan 2012 at 4:59

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
http://manpages.ubuntu.com/manpages/hardy/man1/hexdump.1.html

Original comment by jesusfreke@jesusfreke.com on 2 Jan 2012 at 6:27

GoogleCodeExporter commented 9 years ago 
Here is the requested info for am.odex:

Gary@eeePC /cygdrive/d/GalaxyS2/kitch
$ hexdump  -n 8 am.odex
0000000 6564 0a79 3330 0036
0000008

Gary@eeePC /cygdrive/d/GalaxyS2/kitch
$ hexdump -s 40 -n 8 am.odex
0000028 6564 0a78 3330 0036
0000030

Regards,
Gary

Original comment by gcrut...@gmail.com on 2 Jan 2012 at 6:37

GoogleCodeExporter commented 9 years ago 
http://pastebin.com/HvUuifCw

there you go
I get the same values with the others odex files as well

Original comment by shauli.b...@gmail.com on 2 Jan 2012 at 6:45

GoogleCodeExporter commented 9 years ago 
Thanks. Looks like the version number for the dex header changed to 36 at some 
point. I'll look into it and get it fixed up.

Original comment by jesusfreke@jesusfreke.com on 2 Jan 2012 at 6:51

GoogleCodeExporter commented 9 years ago 
How soon will fix this bug?
Thanks.

Original comment by mythtran...@gmail.com on 4 Jan 2012 at 11:09

GoogleCodeExporter commented 9 years ago 
Any ETA's on 1.3.1?

Original comment by faryaabs...@gmail.com on 5 Jan 2012 at 10:15

GoogleCodeExporter commented 9 years ago 
Actually, not sure if the version number has been changed.
Below is from DXKL3 which works ok with v1.3.0. First hexdump is same as XXKP8, 
but not the second hexdump

Administrator@Daddy2 /cygdrive/d/GalaxyS2/ROMs/DXKL3/sy
$ hexdump  -n 8 am.odex
0000000 6564 0a79 3330 0036
0000008

Administrator@Daddy2 /cygdrive/d/GalaxyS2/ROMs/DXKL3/sy
$ hexdump -s 40 -n 8 am.odex
0000028 6564 0a78 3330 0035
0000030

Original comment by gcrut...@gmail.com on 11 Jan 2012 at 5:18

GoogleCodeExporter commented 9 years ago 
yea, but DXKL3 is 2.3.6 and XXKP8 is 4.0.3

Original comment by shauli.b...@gmail.com on 11 Jan 2012 at 1:01

GoogleCodeExporter commented 9 years ago 
This should be fixed in 1.3.1

Original comment by jesusfreke@jesusfreke.com on 12 Jan 2012 at 6:51

GoogleCodeExporter commented 9 years ago 
Unless I am doing something wrong, baksmali is hanging while deodexing am.odex.
Am using dsixda kitchen, but did try it manually with same results. Same 
problem on all framework files. I hope I am doing something wrong. :)

Original comment by gcrut...@gmail.com on 12 Jan 2012 at 7:45

GoogleCodeExporter commented 9 years ago 
I have the same problem

Original comment by shauli.b...@gmail.com on 12 Jan 2012 at 7:50

GoogleCodeExporter commented 9 years ago 
Fixed in 1.3.2. *sigh*

Original comment by jesusfreke@jesusfreke.com on 12 Jan 2012 at 8:54

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
v1.3.2 -> It's working. Thank You very much.
Will post any issues IF they occur.

Original comment by gcrut...@gmail.com on 12 Jan 2012 at 9:08

GoogleCodeExporter commented 9 years ago 
Thanks 1.3.2 is working (with api level 15).

Original comment by karami...@gmail.com on 12 Jan 2012 at 10:35