Closed GoogleCodeExporter closed 9 years ago
Hmm. That one is definitely strange.
Can you disassemble the odex without -x, and pastebin one of the classes that
it is erroring on.
Original comment by jesusfreke@jesusfreke.com
on 4 Sep 2012 at 1:57
I disassemble the odex without -x. There is no error occurred.
d:\apktool_tech\comp>java -jar baksmali-1.3.3.jar -T inline.txt -d framework_TL1
3 -c :core.jar:bouncycastle.jar:ext.jar:framework.jar:android.policy.jar:service
s.jar:core-junit.jar -a 10 framework_TL13.odex
Warning: You are disassembling an odex file without deodexing it. You
won't be able to re-assemble the results unless you deodex it with the -x
option
Original comment by dgcst...@gmail.com
on 4 Sep 2012 at 2:49
Right. please pastebin one of the classes that was erroring before
Original comment by jesusfreke@jesusfreke.com
on 4 Sep 2012 at 3:11
I am unable to reproduce this issue. I am able to deodex the framework odex
from that rom without any problem. Is it possible the odex file is corrupt? The
md5sum I have for framework.odex from that rom is
2c1e18b83929068769917d43daadd9a0
Original comment by jesusfreke@jesusfreke.com
on 4 Sep 2012 at 3:50
[deleted comment]
yes, you are right. The md5sum of framework.odex is
270140EC126DC102172E70E22E0418B5
that is different from the original version. So, I re-get the framework.odex
from original Rom.
Thank you very much.
smali and baksmali are work successfully.
Original comment by dgcst...@gmail.com
on 4 Sep 2012 at 8:15
Original comment by jesusfreke@jesusfreke.com
on 16 Sep 2012 at 6:57
Original issue reported on code.google.com by
dgcst...@gmail.com
on 4 Sep 2012 at 1:10Attachments: