Not able to deodex framework.odex from android 4.2 emulator

[GoogleCodeExporter]

What seems to be the problem?
Not able to deodex framework.odex from android 4.2 emulator. It throws lot of 
exceptions. I have created a log file for all the exceptions and it is attached 
herewith.

What is the exact smali/baksmali command that you ran?
baksmali-2.0.jar -a 17 -x -d /tmp/framework framework.odex

What version of smali/baksmali are you using? What rom are you working
from?
baksmali-2.0.jar Android 4.2.2 emulator

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

Please see the attached log file. there are lot of exceptions 

Original issue reported on code.google.com by ankitmit...@gmail.com on 8 Nov 2013 at 7:30

Attachments:

• log.txt

[GoogleCodeExporter]

The command used is 

java -jar baksmali-2.0.jar -a 17 -x -d /tmp/framework framework.odex > log.txt 
2>&1

Original comment by ankitmit...@gmail.com on 8 Nov 2013 at 7:32

[GoogleCodeExporter]

Weird. I'm assuming your /tmp/framework has the full /system/framework folder?

Original comment by jesusfreke@jesusfreke.com on 8 Nov 2013 at 7:58

• Changed state: Accepted

[GoogleCodeExporter]

Yes I have pulled the complete /system/framework folder from 4.2 emulator to 
/tmp/framework folder on my machine.

FYI: I am able to deodex the framework.odex from API level 14 emulator.

Original comment by ankitmit...@gmail.com on 8 Nov 2013 at 8:57

[GoogleCodeExporter]

I'm unable to reproduce

<start 4.2.2 emulator>
adb pull /system/framework /tmp/framework
baksmali -a 17 -x -d /tmp/framework /tmp/framework/framework.odex -o 
/tmp/framework_out

This successfully deodexes framework.odex, with no errors, using baksmali 2.0.

Are you sure you were passing the right framework folder via -d while 
deodexing? Maybe you were using a framework folder from a different device/avd?

Original comment by jesusfreke@jesusfreke.com on 11 Nov 2013 at 6:04

• Changed state: Pending

[GoogleCodeExporter]

I'll go ahead and close this one. Feel free to ping the issue if you are still 
encountering the problem and can provide more information.

Original comment by jesusfreke@jesusfreke.com on 7 Dec 2013 at 10:55

• Changed state: Done