difficulties de-odexing 1 file about smali

[JesusFreke]

Comment #1 originally posted by JesusFreke on 2010-03-16T00:14:53.000Z:

i should have added above. but i have tried adding every .jar from the frameworks
folder to the bootclass path and get that same error. i have no clue what this file
is dependent to.

[JesusFreke]

Comment #2 originally posted by JesusFreke on 2010-03-16T15:21:16.000Z:

Keep in mind that it doesn't have to be a file in /system/framework. It could also be
a file in /system/app. You might try using the axmlprinter2 utility on the manifest
file and see what other libraries it depends on. Also, you can find the base
BOOTCLASSPATH for the rom in the /init.rc file.

If nothing else, just disassemble all the jars and apks from the rom, and do a find
-name "HttpServlet.java"

[JesusFreke]

Comment #3 originally posted by JesusFreke on 2010-03-16T17:36:03.000Z:

Thanks JF. So the depency will lie in one of those 2 folders? Nowhere else possibly?

[JesusFreke]

Comment #4 originally posted by JesusFreke on 2010-03-16T18:29:00.000Z:

i disassembled all the jars and apks and there is nothing named "HttpServlet.java" :/

[JesusFreke]

Comment #5 originally posted by JesusFreke on 2010-03-17T00:13:47.000Z:

sorry, my mistake. should be HttpServlet.smali

[JesusFreke]

Comment #6 originally posted by JesusFreke on 2010-03-17T00:38:01.000Z:

still not finding it. is it possible it could lie somewhere else?

[JesusFreke]

Comment #7 originally posted by JesusFreke on 2010-03-20T00:46:02.000Z:

I've taken a look at a cliq rom, and agree. The HttpServlet class is nowhere to be
found. If anything tried to use the net.oath.signature.Echo class, dalvik would throw
an exception because it couldn't find the superclass javax.servlet.http.HttpServlet

In baksmali, I made the assumption that there wouldn't be any missing classes like
this. Which apparently is an incorrect assumption. I'll need to figure out how to
have baksmali handle this case.

[JesusFreke]

Comment #8 originally posted by JesusFreke on 2010-03-20T00:46:19.000Z:

<empty>

[JesusFreke]

Comment #9 originally posted by JesusFreke on 2010-03-20T00:54:04.000Z:

Thank you sir! I love your status on modmymoto "Itty Bitty Modder" lol.

[JesusFreke]

Comment #10 originally posted by JesusFreke on 2010-04-03T23:26:14.000Z:

I've fixed this in 1.2.2. You need to deodex that file with the -I option
(--ignore-errors). It will still spit out a number of errors, but instead of
stopping, it will continue to disassemble the rest of the classes. The classes that
it couldn't deodex will simply be missing.

This "shouldn't" cause any problems, because if any of those classes were actually
used anywhere, dalvik would likely raise an exception and it wouldn't work. But
you'll obviously want to test it out and make sure there are no problems

[JesusFreke]

Comment #11 originally posted by JesusFreke on 2010-04-04T02:23:41.000Z:

thanks man I am testing now!

[JesusFreke]

Comment #12 originally posted by JesusFreke on 2010-04-04T02:27:30.000Z:

great, let me know if you run into any issues. It should deodex and re-assemble fine.
But if it actually runs or not is the real question! ;)

[JesusFreke]

Comment #13 originally posted by JesusFreke on 2010-04-04T04:52:07.000Z:

and it booted up!! JF thanks once again for your superb work!

[JesusFreke]

Comment #14 originally posted by JesusFreke on 2010-04-04T07:08:27.000Z:

Great! Thanks for the follow up :)