Closed GoogleCodeExporter closed 9 years ago
Why are you using -I to deodex framework.jar? Does it contain a reference to
some class that doesn't exist on the device?
-I is an experimental option, as workaround to the above problem. If it is
misused, it is very likely that it will generate an invalid dex file that other
tools might choke on.
What rom specifically are you trying to deodex? (That question is in the
template for a reason :p).
Original comment by jesusfreke@jesusfreke.com
on 26 Nov 2011 at 3:42
I am so sorry for so late to reply you,I think the -I option may be not the
cause,when I dexopt the settings.apk,and do not use the -I option ,it is the
same error; I do not know the name of the rom,I just use adb pull /system
system to pull odex from a not well-known phone;Maybe I should send the rom to
you,but it is too big;
Original comment by wylhistory
on 29 Nov 2011 at 10:50
I make a list of error-open files,then checkout the responding smali file as
attachment,I find most of the error-open files have some inner class;
Original comment by wylhistory
on 29 Nov 2011 at 11:28
Attachments:
also attach the dex2jar file of settings,in which some files can not be open
when using jd-gui ;
Original comment by wylhistory
on 29 Nov 2011 at 11:34
Attachments:
Is there any update to this issue? I am having the same problem
Original comment by mattpmi...@gmail.com
on 25 Jan 2013 at 9:04
This almost certainly isn't an issue with baksmali, but with either dex2jar or
jd-gui.
Original comment by jesusfreke@jesusfreke.com
on 14 Feb 2013 at 11:41
Original issue reported on code.google.com by
wylhistory
on 26 Nov 2011 at 9:48