soga07 / smali

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

error deodexing ics 4.0.4 #120

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What seems to be the problem?
I keep getting an error when i try to deodex an ics file.

What is the exact smali/baksmali command that you ran?

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

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

NOW AT FILE 103 OF 124 IN system/app: SystemUI.odex
Disassembling SystemUI.odex ...
java -Xmx512m -jar baksmali.jar -a 15 -d ../framework -x SystemUI.odex

Error occured while loading boot class path files. Aborting.
org.jf.dexlib.Code.Analysis.ClassPath$ClassNotFoundException: Could not find 
interface 
Lcom/sec/android/app/minimode/manager/MiniModeAppCallback$OnFocusChangedCallback
;
    at org.jf.dexlib.Code.Analysis.ClassPath$ClassDef.loadAllImplementedInterfaces(ClassPath.java:865)
    at org.jf.dexlib.Code.Analysis.ClassPath$ClassDef.<init>(ClassPath.java:690)
    at org.jf.dexlib.Code.Analysis.ClassPath.loadClassDef(ClassPath.java:280)
    at org.jf.dexlib.Code.Analysis.ClassPath.initClassPath(ClassPath.java:163)
    at org.jf.dexlib.Code.Analysis.ClassPath.InitializeClassPathFromOdex(ClassPath.java:110)
    at org.jf.baksmali.baksmali.disassembleDexFile(baksmali.java:104)
    at org.jf.baksmali.main.main(main.java:293)
Error while loading class 
Lcom/android/systemui/statusbar/tablet/MiniModeAppsPanel$1; from file 
SystemUI.odex
Error while loading ClassPath class 
Lcom/android/systemui/statusbar/tablet/MiniModeAppsPanel$1;

-> Using brute-force method (ignore above error if successful):

Disassembling SystemUI.odex ...
java -Xmx512m -jar baksmali.jar -a 15 -d ../framework -c 
:am.jar:android.policy.jar:android.test.runner.jar:apache-xml.jar:bmgr.jar:bounc
ycastle.jar:browsermanagement.jar:bu.jar:cneapiclient.jar:com.android.future.usb
.accessory.jar:com.android.location.provider.jar:com.android.nfc_extras.jar:com.
att.vvm.sharedlib.jar:com.cequint.platform.jar:com.google.android.maps.jar:com.g
oogle.android.media.effects.jar:com.google.widevine.software.drm.jar:com.qualcom
m.location.vzw_library.jar:com.quicinc.cne.jar:com.samsung.device.jar:core.jar:c
ore-junit.jar:ext.jar:filterfw.jar:framework2.jar:framework.jar:ime.jar:input.ja
r:java.awt.jar:javax.obex.jar:libvtmanagerjar.jar:minimode.jar:modemwarmup.jar:m
onkey.jar:pm.jar:seccamera.jar:sec_feature.jar:secframework.jar:sechardware.jar:
secmediarecorder.jar:sec_platform_library.jar:services.jar:svc.jar:twframework.j
ar -x SystemUI.odex

Error occured while loading boot class path files. Aborting.
org.jf.dexlib.Util.ExceptionWithContext: Cannot locate boot class path file 
com.att.vvm.sharedlib.jar
    at org.jf.dexlib.Code.Analysis.ClassPath.loadBootClassPath(ClassPath.java:237)
    at org.jf.dexlib.Code.Analysis.ClassPath.initClassPath(ClassPath.java:151)
    at org.jf.dexlib.Code.Analysis.ClassPath.InitializeClassPathFromOdex(ClassPath.java:110)
    at org.jf.baksmali.baksmali.disassembleDexFile(baksmali.java:104)
    at org.jf.baksmali.main.main(main.java:293)

ERROR: Aborting SystemUI.odex

Original issue reported on code.google.com by spdfr...@gmail.com on 17 May 2012 at 12:58

GoogleCodeExporter commented 9 years ago
There are two "errors" here. The first is "expected", in the sense that these 
errors (and dealing with them) are a normal part of the deodexing process.

The second is fairly simple, it can't find the file com.att.vvm.sharedlib.jar. 
Is it in the "../framework" path you specified with -d?

Original comment by bgruv@google.com on 5 Jun 2012 at 4:45