Database Develop

how do you open and edit classes.dex?

I can not open classes.dex for the life of me. I have tried multiple ways with different commands and such and still can not get it to open.
I have found this method to get me the farthest but still no go on opening it. every time I enter the command
java -jar baksmali.jar -o classout/ classes.dex
Click to expand...
Click to collapse
I get "Unable to access jarfile baksmaili.jar"
Thanks to anyone who is willing to help.

Download AvaboxV2 and unzip the folder. Inside there are tools for editing and such, namely the "Smali" folder which is hopefully what you are looking for.

kyouko said:
Download AvaboxV2 and unzip the folder. Inside there are tools for editing and such, namely the "Smali" folder which is hopefully what you are looking for.
Click to expand...
Click to collapse
I tried that. It will only do apks... I need to to do it to a .dex or a .jar
okay now I see the folder C:\Users\Devin\Documents\AvaboxV2\Smali\baksmali
but still I will need the command prompt and I will be in the same trouble i am in now.

Put the classes.dex file in the \smali\baksmali folder. then navigate to that folder in command prompt:
Code:
cd\
cd C:\Users\Devin\Documents\AvaboxV2\Smali\baksmali
java -jar baksmali-1.1.jar -o classout/ classes.dex
*that should create a folder called "classout" in \baksmali with the smali files*
Then make your edits to the .smali files using notepad++ or w/e
To close up the classout folder and put it back into a classes.dex enter this in cmd:
Code:
java -jar smali-1.1.jar classout -o classes.dex
Edit: fixed file name mix-up

kyouko said:
Put the classes.dex file in the \smali\baksmali folder. then navigate to that folder in command prompt:
Then make your edits to the .smali files using notepad++ or w/e
To close up the classout folder and put it back into a classes.dex enter this in cmd:
Code:
java -jar smali-1.2.1.jar classout -o classes.dex
Click to expand...
Click to collapse
dude no matter what I type cmd will NOT go to that folder. "Folder not found" or some ****.
I can NOT wait till iPhone 4 comes out android is total ****.
got it to go to teh folder in cmd but like I said i get the stupid ass unable to access jarfile baksmali.jar
When baksmali.jar is clearly in the freaking folder.
Is there not an easier way to do this?

Ooohhh shii- lol I'm a dumbass
Haha it should be baksmali-1.1.jar and smali-1.1.jar
I just edited my previous post to fix that mixup

I even pasted strait from yours.. it does not work man. I give up android is gay

Never mind thank you so much man.. I was just getting pissed off because I have been trying this for so long. Thanks for the help.

Funny thing is, you think you'll be able to mod I phone easier? Ha!
-------------------------------------
Sent via the XDA Tapatalk App

roflcopter
danaff37 said:
Funny thing is, you think you'll be able to mod I phone easier? Ha!
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
..Thumbs up
Srsly..its not difficult to mod android and its apps/framework(/resources)...at all. Only 2 real vars: setup and level of incompetence
not related->Getting a mac soon, mostly everything is windows compatible (80% of market/business/etc), mac not so much...parallel+windows 7 good idea?
kthxbai

I run a dual boot between ubuntu and windows 7 for work
Sent from my HERO200 using XDA App

Anyone have a clue why i get this error?
Smali\baksmali>java -jar framework.jar
-o classout/ classes.dex
Failed to load Main-Class manifest attribute from
framework.jar
This prog hero specific?
Thanks'

hellmonger said:
Anyone have a clue why i get this error?
Smali\baksmali>java -jar framework.jar
-o classout/ classes.dex
Failed to load Main-Class manifest attribute from
framework.jar
This prog hero specific?
Click to expand...
Click to collapse
it not hero specific > link
framework.jar doesn't have the "Main-class" header which is why you're getting that error.
it should be
Code:
java -jar baksmali.jar -o classout/ classes.dex
NOT
Code:
java -jar [COLOR="red"]framwork[/COLOR].jar -o classout/ classes.dex
java -jar is used to run the baksmali and smali.jar "applications"

can this be done in window? cygwin? I have tried to call baksmali for a classes.dex also and having no luck. any insight?

thank
thanksssssss

this app, everytime i start it, i have to press OK button (that annoying) but it work. see what can we do with it:
- i try to extract the classes.dex file, (using winrar)
- edit some code (to remove the dialog appear when it start),
- compress the code back .dex file
- put the .dex into .apk file
- install on the phone fail
can anyone give me suggestion or please do something..

khanhj said:
this app, everytime i start it, i have to press OK button (that annoying) but it work. see what can we do with it:
- i try to extract the classes.dex file, (using winrar)
- edit some code (to remove the dialog appear when it start),
- compress the code back .dex file
- put the .dex into .apk file
- install on the phone fail
can anyone give me suggestion or please do something..
Click to expand...
Click to collapse
Why you have attached a warez spy app?

Can anyone tell why I get this error?
UNEXPECTED TOP-LEVEL EXCEPTION:
java.lang.RuntimeException: bad magic value: 64 65 79 0a 30 33 36 00
at org.jf.dexlib.DexFile.<init>(DexFile.java:359)
at org.jf.baksmali.main.main(main.java:176)

Using Win7. I've always just thrown all editing files in Android/SMALI folder.
Hold Shift, Right Click "Open Command Window Here".
Then for compressing/decompressing the commands I use are.
java -jar baksmali.jar -o classout/ classes.dex
java -Xmx512M -jar smali.jar classout -o classes.dex
Haven't run into any issues yet. I noticed no one has put the "-Xmx512M" in their code.
I hope this helps.

[HOW TO] Add Haptic Home Feedback To Any i9000 Theme

This works on JPY/JS3, and ought to work on any other i9000 ROM, with a bit of ingenuity.
Download the Home_Haptic_Editing.zip at the end of this post. Extract the files to somewhere of your choosing.
Now, look at the theme package. The file you'll need is android.policy.jar.
Open android.policy.jar inside a .zip program, such as 7-zip or WinRAR. Extract the file "classes.dex" to the same folder as baksmali.jar and smali.jar.
Open a command prompt and navigate to that folder. (Or, hold Shift and right click inside the folder and hit "Open command window here").
Enter into that command prompt the following:
Code:
java -jar baksmali.jar -o classout/ classes.dex
This will create a folder called "classout" filled with .smali files.
Delete the classes.dex file.
Replace the PhoneWindowManager.smali with the uploaded one.
Back inside the command prompt, enter the following:
Code:
java -Xmx512M -jar smali.jar classout/ -o classes.dex
This will generate a classes.dex file.
Delete the classout folder.
Using 7-zip or similar, replace the classes.dex inside the android.policy.jar.
Put the android.policy.jar back inside your theme, and you're done.

It compiled. Will test tomorrow, as I don't feel like dealing with forces closes if I ****ed up tonight.

x3nhydr4lutr1sx said:
It compiled. Will test tomorrow, as I don't feel like dealing with forces closes if I ****ed up tonight.
Click to expand...
Click to collapse
My first victim tester.

Works on JS3 and JPY.

can u explain more what should this mod does exactly ?? and ought to work on any other i9000 ROM, with a bit of ingenuity?? is that mean if i try to replace ur PhoneWindowManager.smali with mine could break my phone ???

ingvay2009 said:
can u explain more what should this mod does exactly ?? and ought to work on any other i9000 ROM, with a bit of ingenuity?? is that mean if i try to replace ur PhoneWindowManager.smali with mine could break my phone ???
Click to expand...
Click to collapse
It means that it adds haptic
feedback to the home key.
It means that if you try it on non-JPY/JS3, I don't know what will happen.
Sent from my Captivate.

Compilled, now testing... AFAIK it shouldn't **** up.
But it's android - sign for that file is now bad, so it will recompile dalvik-cache (yeah, crazy i know)
Edit: **** up DID not occured, replaced file via recovery and adb. JS3 firmware

So I take it it worked?

Yep, but feedback on home is a bit stronger than other buttons.this is weird

ive tried multiple times but the windows phone 7 theme woll not work

As always tha.ks for the guide. Think we might need to make a roll up of your guids so they are easy to find.
As far as the windows theme what is the theme built off?

Thanks for posting this info. Keep up all your great work my cappy would be bone stock if not for you

Can you point me in the direction in how to add haptic feedback for jvp or even jvq, I'm trying to port a I9000 to tmobile vibrant.

jrafael said:
Can you point me in the direction in how to add haptic feedback for jvp or even jvq, I'm trying to port a I9000 to tmobile vibrant.
Click to expand...
Click to collapse
It's the same.
Sent from my Infuse 4G

[Q] Deodexing Vivid manually?

Has anyone been able to deodex the vivid yet? I attempted with xUltimate but i got a variety of errors when trying. To my knowledge it was something to do with the phone not the program. Any other alternatives to doing so?

There are numerous deodexed roms out there.
Sent from my aokp_tenderloin using Tapatalk

i know, but currently i'm using RumRaider Beta 4 and i dont want to downgrade just for the deodex

Have you tried the kitchen yet? It does work.
Sent from my Transformer TF101 using xda premium

Jirv311 said:
Have you tried the kitchen yet? It does work.
Sent from my Transformer TF101 using xda premium
Click to expand...
Click to collapse
im installing it right now, it's a bit of a pain since xcode doesn't install GCC anymore so i have to get it manually. but i'll let you know

Only partly works, have to do some changes to it

Wild Child said:
Only partly works, have to do some changes to it
Click to expand...
Click to collapse
This. Sometimes it will get the whole way through. Otherwise you can do it manually with baksmali/smali. I bet someone could write a script, using the kitchen's brute force method (checking all .odex files against all .jar files for dependencies)..
The way I do it when I have to do it manually.. first dump all .apk, .jar, and .odex to the same directory (not necessary, just less changing directories with the following commands), and get baksmali and smali in the same directory, then open a command prompt there..
Decompile odex:
java -jar baksmali.jar -c :dependency:dependency -x <output directory> <.dex file, typically classes.dex>
(This part can be a real pain in the ass. But usually you can find the dependencies from the errors baksmali throws at you)
Compile to classes.dex:
java -Xmx512M -jar smali.jar <output directory from above step> -o classes.dex
Then change .jar to .zip and open with 7zip (or just open .apk with 7zip), add your classes.dex to the .zip (or .apk), change back to .jar, delete to .odex, classes.dex, and output folder, and move on to the next one. Once you're done, put the .jar files and framework-res.apk and com.htc.resources.apk back to /framework/ and the rest of the .apks to /app/

I didn't have to make any changes to the kitchen at all. Per PG's tip, I plucked the ATT VVM.jar temporarily and everything de-odexed just fine. This was using the ATT ICS RUU.

zacgoesrawr said:
i know, but currently i'm using RumRaider Beta 4 and i dont want to downgrade just for the deodex
Click to expand...
Click to collapse
Gotcha. From your wording I thought you were under the impression that there were no deodexed ROMs available. Sorry for the confusion.

[Tool] nhnt11's XML Generator Revived V2+Extended UPDATED!

Hey guys, I had made a tutorial video on how to edit xml files and using nhnt11's xml generator found here: http://www.youtube.com/watch?v=xObYfIynRlw
In this tutorial I covered a lot of how to edit xml files. I also covered some issues wrong with this xml generator. One viewer of my tutorial, who goes by the name of fcknghst here on xda, was kind enough to listen to problems I explained and is in the process of fixing these issues to have a more complete xml generator. He told me I could post the fixed file here. Originally, nhnt11's xml generator was great except for a few small issues. For 1, it would skip images/lines in the generated xml of # 9s. 2nd the xml line would be set to drawable which would make it a pain to go through and edit all the mipmap images from drawable to mipmap. The way this works, as I understand it, everything is pretty much the same except with a few added Operators. The commands are as follows for the operators:
Code:
[B]Operator Codes:[/B]
Drawable: -d
Mipmap: -m
Complete xml drawable: -df
Complete xml mipmap: -mf
So now new commands should look like this:
Code:
java -jar XMLGenerator2.jar <package names separated by spaces> [operator] <input directory> <output file>
Thank you so much for listening to me and helping us out with this, I do not take credit for this, credit goes to the original xml generator dev nhnt11 and bug fixes by fcknghst.
Download Link​There was a minor update and the download link was updated so you want to get the XMLGenerator2(1).zip, it is more common package name friendly now!!!
Here is the README:
Code:
I claim no ownership for this script.
This script was created by Nihanth (nhnt11 @xda)
Only bug fixed and "extended" by Foster Buster (fcknghst @xda)
---------------------------------------------------------------------
Some basic documentation:
Usage: java -jar XMLGenerator2.jar <package names separated by spaces> [operator] <input directory> <output file>
An example could be that I wanted a ready-made xml of files from the package "com_mycats_areawesome":
And if I wrote java -jar XMLGenerator2.jar -df something something.xml
it would output <item name="drawable/com_mycats_areawesome_something">@drawable/com_mycats_areawesome_something</item>
Which is not correct.
It should be <item name="drawable/something">@drawable/com_mycats_areawesome_something</item>
This is because the package "com_mycats_areawesome" is not included in this script (see included packages at the bottom of this document).
Now if I wrote java -jar XMLGenerator2.jar com_mycats_areawesome -df something something.xml
It would give the correct output.
You can always add more package names in the source (Main.java), or perhaps write yourself a nifty little batch script.
The operators are as follows:
-d = Writes it as "drawable"
-m = Writes it as "mipmap"
-df = Writes it as "drawable", and makes it a complete xml-file.
-mf = Writes it as "drawable", and makes it a complete xml-file.
Not using a operator will result in an empty file.
If you at some point forget this, just type "java -jar XMLGenerator2.jar" into the command prompt and it will list how to use the script.
If you dont feel like typing "XMLGenerator2.jar" every time, you can always rename it to whatever.
Package names already included: (There will properly never be any need for some of them, but it was an automated process :))
app_fastfacebook_com
cn_wps_moffice_eng
com_accuweather_android
com_adobe_flashplayer
com_adobe_psmobile
com_adobe_reader
com_alphonso_pulse
com_amazon_venezia
com_anddoes_launcher
com_andrew_apollo
com_android_bluetooth
com_android_browser
com_android_calculator2
com_android_calendar
com_android_camera
com_android_chrome
com_android_contacts
com_android_deskclock
com_android_development
com_android_dreams
com_android_email
com_android_fm
com_android_gallery3d
com_android_inputmethod_latin
com_android_launcher
com_android_mifileexplorer
com_android_mms
com_android_music
com_android_phone
com_android_providers_calendar
com_android_providers_downloads_ui
com_android_quicksearchbox
com_android_settings
com_android_stk_
com_android_systemui
com_android_vending
com_android_videoeditor
com_android_voicedialer
com_android_wallpaper
com_android_wallpaper_livepicker
com_antivirus
com_anydo
com_apdroid_tabtalk
com_appspot_swisscodemonkeys_apps
com_baked_romcontrol
com_baked_walls
com_bel_android_dspmanager
com_bellmo_selfserve
com_bigeyes0x0_trickstermod
com_bigtincan_android_adfree
com_booking
com_box_android
com_bsplayer_bspandroid_free
com_citc_wallbase
com_citc_weather
com_clov4r_android_nil
com_cooliris_media
com_cyandelta
com_cyanogenmod_filemanager
com_cyanogenmod_settings_device
com_cyanogenmod_trebuchet
com_cyanogenmod_updater
com_dataviz_docstogo
com_derkernel_tkt
com_dropbox_android
com_drx2_bootmanager
com_duduapps_craigslistfree
com_dwdesign_tweetings
com_dynamixsoftware_printershare
com_ebay_mobile
com_endomondo_android
com_espn_score_center
com_estrongs_android_pop
com_evernote
com_facebook_katana
com_facebook_orca
com_farproc_wifi_analyzer
com_fitnesskeeper_runkeeper_pro
com_floriandraschbacher_fastfiletransfer
com_flyersoft_moonreader
com_funtrigger_mp3tag
com_geogrant_bordertimes
com_glympse_android_glympse
com_google_android_apps_books
com_google_android_apps_currents
com_google_android_apps_docs
com_google_android_apps_genie_geniewidget
com_google_android_apps_googlevoice
com_google_android_apps_maps_ic
com_google_android_apps_plus
com_google_android_apps_reader
com_google_android_apps_translate
com_google_android_carhome
com_google_android_ears
com_google_android_gm
com_google_android_gm_com
com_google_android_googlequicksearchbox
com_google_android_marvin_talkback
com_google_android_talk
com_google_android_youtube
com_google_earth
com_google_zxing_client_android
com_gotv_nflgamecenter_us_lite
com_handcent_nextsms
com_handlerexploit_tweedle
com_handmark_friendcaster_chat
com_handmark_tweetcaster
com_happydroid_tweetline
com_hootsuite_droid_full_icon
com_hotfree_iheart
com_imdb_mobile
com_indeed_android_jobsearch
com_instagram_android
com_intonow
com_intsig_camscanner
com_joelapenna_foursquared
com_jrummy_liberty_toolbox
com_jv_cleanwidgets
com_jv_falcon
com_koushikdutta_rommanager
com_levelup_beautifulwidgets
com_levelup_touiteur
com_linkedin_android
com_lookout
com_manor_currentwidget
com_mapquest_android_ace
com_mathpad_mobile_android_wt_unit_
com_metago_astro
com_microsoft_skydrive
com_microsoft_smartglass
com_mobisystems_office
com_mseven_msecure
com_mxtech_videoplayer_ad
com_netflix_mediaclient
com_nimbuzz
com_nixpa_kik_video
com_noinnion_android_greader_reader
com_noshufou_android_su
com_nuance_swype_beta
com_nullsoft_winamp
com_olive_office
com_olivephone_edit
com_onelouder_baconreader
com_onelouder_tweetvision
com_onexuan_battery
com_opera_browser
com_otaupdater
com_pandora_android
com_paranoid_preferences
com_path
com_paypal_android_p2pmobile
com_picsart_studio
com_pinterest
com_platinumapps_facedroid
com_plexapp_android
com_quoord_tapatalkpro_activity
com_quoord_tapatalkrwk_activity
com_quoord_tapatalkxda_activity
com_rdio_android_ui
com_rebelvox_voxer
com_ringdroid
com_roidapp_photogrid
com_s0up_goomanager
com_sand_airdroid
com_seesmic
com_sgiggle_production
com_shazam_android
com_shinycore_picsayfree
com_skype_raider
com_smartandroidapps_audiowidget
com_socialnmobile_dictapps_notepad_color_note
com_songkick
com_spartancoders_gtok
com_speedsoftware_rootexplorer
com_spotify_mobile_android_ui
com_teamviewer_teamviewer_market_mobile
com_tenthbit_juliet
com_texty_sms_app
com_thedeck_android_app
com_threebanana_notes
com_tmobile_themechooser
com_tumblr_app
com_tweetlanes_android
com_twidroid
com_twidroydlegacy
com_twitter_android
com_uberullu_rescansd
com_utorrent_client
com_vevo
com_viber_voip
com_whatsapp
com_yahoo_mobile_client_android_im
com_yahoo_mobile_client_android_mail
de_devmil_minimaltext
de_softxperience_android_noteeverything
eu_chainfire_supersu
ext_recovery_update
flipboard_app
frameworks_res
google_android_youtube
hu_tagsoft_ttorrent_lite_
im_mercury_android
in_vineetsirohi_customwidget
intelgeen_rocketdial_trail
jackpal_androidterm
kik_android
me_sonar_androi
mobi_cyann_nstools
mobi_ifunny
mobi_mgeek_TunnyBrowser
net_cactii_flash2
net_flixster_android
net_rgruet_android_g3watchdog
net_sourceforge_subsonic_androidapp
net_zedge_android_launcher
org_adaway
org_adw_launcher
org_adwfreak_launcher
org_mozilla_firefox
org_openintents_filemanager
org_projectvoodoo_controlapp
org_zwanoo_android_speedtest
pl_solidexplorer
radiotime_player
ru_zdevs_zarchiver
usa_jersey_tvlistings

This seems like it might come in handy for some of those little issues that can arise. Thanks for the heads up!

OP Updated

great info!

Nice. Very useful tool. One has to batch rename the PNGs though first.
On Windows, if you want to batch rename, open command prompt (type cmd in search/run) and then go into the folder where all the PNGs that have to batch renamed are. Then just type this,
for %a in (*.*) do ren "%a" "prefix%a"
Click to expand...
Click to collapse
Replace the word prefix with the word you want to prefix all the PNGs with.
You can also add a postfix. Just place the postfix after %a.

dhirend_6d said:
On Windows, if you want to batch rename, open command prompt (type cmd in search/run) and then go into the folder where all the PNGs that have to batch renamed are. Then just type this
Click to expand...
Click to collapse
I just use Faststone Photo Resizer for bulk renaming.

XperienceD said:
I just use Faststone Photo Resizer for bulk renaming.
Click to expand...
Click to collapse
I use it for batch converting from Indexed and Greyscale to RGB mode.
I never tried batch renaming using Faststone.
Can it add a prefix/postfix??

combine SystemUI.apk with SystemUI.odex

I am facing issues in compiling systemui.apk and systemUI.odex files. I was porting Pixel Navigation bar for AOSP ROM of @Santhosh M. There is any to combine both the files?

If i remember right i made the Pixel navbar for Santhosh M ROM. Doesn't it work anymore? If you don't like the home button just decompile the apk and go to drawable-xxhdpi-v4 and change the ic_sysbar_home icon.
Anyway in order to combine them
1. Download baksmali. Make new folder and put the baksmali.jar and SystemUI.odex there.
2. Open command prompt in the folder where baksmali is located. Type in command prompt "adb pull /system/framework/arm" to extract the required files from the phone.
3. Type "java -jar baksmali.jar deodex SystemUI.odex -l" in the command prompt and if it successful there should be an output folder called "out". Copy it and paste it to the decompiled SystemUI.apk then rename it "smali"
4. Get the required odex files from Pixel's SystemUI(tho' i would recommend you to get them from the already modified systemUI as it usually generates the same number IDs so you wont have to deal with odex file changes).
5. Paste them to smali/com/google/android/systemui(if i remember right you had to create google/android/systemui folders so no worries if they are missing)
6.Recompile
I'd advise you to use this tutorial as it is way more detailed.

Sashko98 said:
If i remember right i made the Pixel navbar for Santhosh M ROM. Doesn't it work anymore? If you don't like the home button just decompile the apk and go to drawable-xxhdpi-v4 and change the ic_sysbar_home icon.
Anyway in order to combine them
1. Download baksmali. Make new folder and put the baksmali.jar and SystemUI.odex there.
2. Open command prompt in the folder where baksmali is located. Type in command prompt "adb pull /system/framework/arm" to extract the required files from the phone.
3. Type "java -jar baksmali.jar deodex SystemUI.odex -l" in the command prompt and if it successful there should be an output folder called "out". Copy it and paste it to the decompiled SystemUI.apk then rename it "smali"
4. Get the required odex files from Pixel's SystemUI(tho' i would recommend you to get them from the already modified systemUI as it usually generates the same number IDs so you wont have to deal with odex file changes).
5. Paste them to smali/com/google/android/systemui(if i remember right you had to create google/android/systemui folders so no worries if they are missing)
6.Recompile
I'd advise you to use this tutorial as it is way more detailed.
Click to expand...
Click to collapse
Thanks! I will be trying this out today. You developed Pixel Nav bars and the thing is you made it for January build. This is April so I have seen that it doesn't works. We need to decompile the systemui.apk again and again Change the ID and other things.
I have ported pixel Navbars for LineageOS. It was easy and today, I stuck in this steps.

I just followed your tutorial and I got this error
C:\Users\Xaif\Desktop\Baksmali\framework>java -jar baksmali.jar deodex SystemUI.
odex -x
usage: java -jar baksmali.jar [options] <dex-file>
disassembles and/or dumps a dex file
-?,--help prints the help message then exits.
Specify twice for debug options
-a,--api-level <API_LEVEL> The numeric api-level of the file
being disassembled. If not
specified, it defaults to 15 (ICS).
-b,--no-debug-info don't write out debug info (.local,
.param, .line, etc.)
-c,--bootclasspath <BOOTCLASSPATH> A colon-separated list of
bootclasspath jar/oat files to use
for analysis. Add an initial colon
to specify that the jars/oats should
be appended to the default
bootclasspath instead of replacing
it
-d,--bootclasspath-dir <DIR> the base folder to look for the
bootclasspath files in. Defaults to
the current directory
-e,--dex-file <DEX_FILE> looks for dex file named DEX_FILE,
defaults to classes.dex
-f,--code-offsets add comments to the disassembly
containing the code offset for each
address
-i,--resource-id-files <FILES> the resource ID files to use, for
analysis. A colon-separated list of
prefix=file pairs. For example
R=res/values/public.xml:android.R=$A
NDROID_HOME/platforms/android-19/dat
a/res/values/public.xml
-j,--jobs <NUM_THREADS> The number of threads to use.
Defaults to the number of cores
available, up to a maximum of 6
-k,--check-package-private-access When deodexing, use the
package-private access check when
calculating vtable indexes. It
should only be needed for 4.2.0
odexes. The functionality was
reverted for 4.2.1.
-l,--use-locals output the .locals directive with
the number of non-parameter
registers, rather than the .register
directive with the total number of
register
-m,--no-accessor-comments don't output helper comments for
synthetic accessors
-n,--normalize-virtual-methods Normalize virtual method references
to the reference the base method.
-o,--output <DIR> the directory where the disassembled
files will be placed. The default is
out
-p,--no-parameter-registers use the v<n> syntax instead of the
p<n> syntax for registers mapped to
method parameters
-r,--register-info <REGISTER_INFO_TYPES> print the specificed type(s) of
register information for each
instruction. "ARGS,DEST" is the
default if no types are specified.
Valid values are:
ALL: all pre- and post-instruction
registers.
ALLPRE: all pre-instruction
registers
ALLPOST: all post-instruction
registers
ARGS: any pre-instruction registers
used as arguments to the instruction
DEST: the post-instruction
destination register, if any
MERGE: Any pre-instruction register
has been merged from more than 1
different post-instruction register
from its predecessors
FULLMERGE: For each register that
would be printed by MERGE, also show
the incoming register types that
were merged
-s,--sequential-labels create label names using a
sequential numbering scheme per
label type, rather than using the
bytecode addressQA
-t,--implicit-references Use implicit (type-less) method and
field references
-v,--version prints the version then exits
-X,--experimental enable experimental opcodes to be
disassembled, even if they aren't
necessarily supported in the Android
runtime yet
-x,--deodex deodex the given odex file. This
option is ignored if the input file
is not an odex file
Click to expand...
Click to collapse
I also tried doing like the above given command so I followed this steps:
C:\Users\Xaif\Desktop\Baksmali\framework>java -jar baksmali.jar --deodex SystemU
I.odex -l
Error occurred while loading boot class path files. Aborting.
org.jf.util.ExceptionWithContext: Cannot locate boot class path file /system/fra
mework/core.jar
at org.jf.dexlib2.analysis.ClassPath.loadClassPathEntry(ClassPath.java:2
96)
at org.jf.dexlib2.analysis.ClassPath.fromClassPath(ClassPath.java:207)
at org.jf.baksmali.baksmali.disassembleDexFile(baksmali.java:67)
at org.jf.baksmali.main.main(main.java:305)
C:\Users\Xaif\Desktop\Baksmali\framework>
Click to expand...
Click to collapse

I have used ApkTool for Android to deodex that file and it did it successfully. Now, I am porting again