can I extract the contents of a mod.zip and take the .jar or .apk and copy and paste them into the framework dir of the working working folder? i tried copying a custom .apk file into the framework dir of the working folder and it went into a boot loop.
alucke
There could be several reasons for a boot loop. If I understand you correctly, you are working on a ROM using dsixda's kitchen, and you want to add an apk before flashing? Could you provide more information like what apk and what folder you are trying to add it to? I suspect it might have something to do with the signature of the apk. I'm not 100% sure but I believe that the system apks all need the same signature when flashing a new ROM.
alucke said:
can I extract the contents of a mod.zip and take the .jar or .apk and copy and paste them into the framework dir of the working working folder? i tried copying a custom .apk file into the framework dir of the working folder and it went into a boot loop.
alucke
Click to expand...
Click to collapse
If you are changing things within the framework you also need to edit the .xml files within the framework. The best way to learn is to take the stock rom and load it into a working folder. then take a custom rom that you can find all the differences to stock on when loaded on your phone and load that into the kitchen. Compare the stock roms working folder with the custom rom working folder and take note of all the differences and figure out how they were achieved. Dont just look at apk files. Look at the update script as well as the xml files in all the folders too. Repeat with another ROM and you will start to see how to change things around yourself.
Hi,
I need to install HTC's Locations app on any custom ROM (ie: MyOneV or CM9/CM10)
So any1 can help me with this ?
(i tried it though, by moving these files (from MyOneV5.0FX Removed apks) htclocation.apk,locationpicker.apk,locatiooninstaller.apk in System/app folder bt it didn't worked)
When you move those files to system app manually, you need to put right permission rw-r--r-- then reboot.
Or the simplest way is, open the Removed_Apks_RC5.x.zip with 7-zip (not extract), delete all apks that you don't need and leave those location files in zip.
Then flash the zip in recovery.
And these files will not work on a CM rom.
ckpv5 said:
When you move those files to system app manually, you need to put right permission rw-r--r-- then reboot.
Or the simplest way is, open the Removed_Apks_RC5.x.zip with 7-zip (not extract), delete all apks that you don't need and leave those location files in zip.
Then flash the zip in recovery.
And these files will not work on a CM rom.
Click to expand...
Click to collapse
:good:
Thankz
I tried that too, by removing all apks from zip keeping the said three files & flash it in recovery, still it doesn't appeared in apps!
Though i'll try again may b missed something or some file..
I just tried it, it works.
Your filename looks different, attached here the files from the Removed_Apks_RC5.x.zip, I named it to location.zip. Flash in recovery.
It Worked: Thanx
Someday I found this:
[HOWTO]Implement Swipe to Remove Notification
I like this function but my phone can't update to 4.1.2 (I8160-TGY don't have JellyBean Firmware...)
So I tried to modify it.
But deodex the whole ROM is a hard work.
So I found this:
[Toturial][Windows] How Editing The ODEX framework files? [Simplified]
I tried to decompile framework.odex ,and compile without modifications ,then my phone can boot normally.
So I'm sure this method is possible.
========================
So now I know how to decompile and compile.
And I find many thread about this but I still have no idea...
Even if I can compile it after modify, I still got bootloop.
Here is my deodexed framework.jar and SystemUI.apk:
https://www.dropbox.com/s/vj5u68g4qfo7zwp/Desktop.rar
Can any devs help me to modify it?
THANKS A LOT!!!
changes umanalm
I found that if I compile and decompile again, some string become different.
So now I don't know how to decompile correctly........
I use baksmali1.4.2 and decompile via command line:
java -jar baksmali-1.4.2.jar -a 10 -x framework.odex
When you compile apk your output is not signed. that is reason why you cant boot
here is what to do
1. Open output apk with 7-zip
2. Open original apk with 7-zip
3. Take meta-inf folder from original and drag to new apk
4. You will have signed apk and you can push it to your device
hope this will help you
btw. for decompiling i use
apktool d path\original.apk path\outputfolder
for compiling
apktool b path\outputfolder path\output.apk
Rox said:
When you compile apk your output is not signed. that is reason why you cant boot
here is what to do
1. Open output apk with 7-zip
2. Open original apk with 7-zip
3. Take meta-inf folder from original and drag to new apk
4. You will have signed apk and you can push it to your device
hope this will help you
btw. for decompiling i use
apktool d path\original.apk path\outputfolder
for compiling
apktool b path\outputfolder path\output.apk
Click to expand...
Click to collapse
I know that.
Because my phone haven't DEODEX, so I Just put classes.dex into framework.jar and odex it.
So it's not my question, but thank you for reply.
Why dont you just deodex rom using android kitchen and do your mods?
Sent from my GT-I8160
Rox said:
Why dont you just deodex rom using android kitchen and do your mods?
Sent from my GT-I8160
Click to expand...
Click to collapse
I tried.
But I can't boot after I deodex my rom.
I use system.tar.md5 to make CWM Flashable ROM.
These is my method: (Android Kitchen version is 0.223, I already download 0.224 but I never use it....)
1.Choose 1 to decompress system.tar.md5 and make Work Folder.
2.Then choose 0 to Advanced option, and choose 11 to de-odex the whole ROM.
3.Repack a CWM Flashabe ROM.
4.Format all partition and flash it.
5.Reboot, and the screen stay in "SAMSUNG GT-I8160".
Is there any wrong? or I have to use Android Kitchen 0.224?
You probably make some mistake.
Can you post updater script to see if problem is there.
Btw. You can try copying system folder to sd card from root directory and than use it as working folder for kitchen
Edit:
Oh, you formatted all partitions? You dont need to format them you possibly lost some device specific files required for boot. Try without formatting
Sent from my GT-I8160
Rox said:
You probably make some mistake.
Can you post updater script to see if problem is there.
Btw. You can try copying system folder to sd card from root directory and than use it as working folder for kitchen
Edit:
Oh, you formatted all partitions? You dont need to format them you possibly lost some device specific files required for boot. Try without formatting
Sent from my GT-I8160
Click to expand...
Click to collapse
Thanks!
This time I make a deodexed ROM via kitchen 0.224, And flash it without formatting.
It still can't boot, and when I enter to CWM, it can't mount any partition.
So I reflash stock ROM via Odin v3.07....
Oh, few days ago I tried to make a CWM flashable zip with only de-odexed /system/app and /system/framework.
It also can't boot.......
Hello Friends..!!!
This guide is for all who wants to deodex their roms for easy customization.
First Lets know some Basic knowledge about DEODEX/ODEX...
What is Odex and Deodex ROM
What is an ODEX file?
In Android file system, applications come in packages with the extension .apk.
These application packages, or APKs contain certain .odex files whose supposed function is to save space.
These ‘odex’ files are actually collections of parts of an application that are optimized before booting.
Doing so speeds up the boot process, as it preloads part of an application.
On the other hand, it also makes hacking those applications difficult because a part of the coding has already been extracted to another location before execution.
What is an DEODEX file?
Deodexing is basically repackaging of these APKs in a certain way, such that they are reassembled into classes.dex files.
By doing that, all pieces of an application package are put together back in one place, thus eliminating the worry of a modified APK conflicting with some separate odexed parts.
So, Deodexed ROMs (or APKs) have all their application packages put back together in one place,
allowing for easy modification such as theming. Since no pieces of code are coming from any external location,
custom ROMs or APKs are always deodexed to ensure integrity.
How this works?
For the majority noobs amongst us, Android OS uses a Java-based virtual machine called the Dalvik Virtual Machine.
A deodexed or .dex file contains the cache used by this virtual machine (referred to as Dalvik-cache) for a program, and it is stored inside the APK.
An .odex file, on the other hand, is an optimized version of this same .
dex file that is stored next to the APK as opposed to inside it.
Android applies this technique by default to all the system applications.
When an Android-based system is booting, the davlik cache for the Davlik VM is built using these .odex files, allowing the OS to learn in advance what applications will be loaded, and thus speeds up the booting process.
By deodexing these APKs, a developer actually puts the .odex files back inside their respective APK packages.
Since all code is now contained within the APK itself, it becomes possible to modify any application package without conflicting with the operating system’s execution environment.
Advanteges & Disadvantages
The advantage of deodexing is in modification possibilities.
This is most widely used in custom ROMs and themes. A developer building a custom ROM would almost always choose to deodex the ROM package first,
since that would not only allow him to modify various APKs, but also leave room for post-install theming.
On the other hand, since the .odex files were supposed to quickly build the dalvik cache, removing them would mean longer initial boot times.
However, this is true only for the first ever boot after deodexing, since the cache would still get built over time as applications are used.
Longer boot times may only be seen again if the dalvik cache is wiped for some reason.
Note: Themes for android come in APKs too, and if you want to modify any of those, you should always choose a dedoexed custom ROM.
Now Lets Start!!!
Requirements:-
1. Java installed on your PC
2. Universal Deodexer (Download from here - http://d-h.st/bMp)
3. Android SDK (for installing deodexed files)
Instructions:-
1. Now first of all you need to copy system/framework and system/apps folders from your phone to your PC. You can do this by simply using the Root Explorer or using ADB commands.
2. Download and extract the zip. You will get a folder called "Universal Deodexer V4"
3. Open the folder and place all your apks or jars from the apps folder in the "apks" folder. No need to manually check if a apk has the corresponding .odex file or not. Apks or Jars which do not have .odex files are automatically deleted.
4. Double click on Universal Deodexer V4.jar. If it does not open then right click--->Properties--->change the Opens With: to "Java(TM) Platform SE Binary". Now double click and it will open. If it still doesn't open then shift+right click anywhere in the folder and open a command prompt window there. Then type - "java -jar Universal Deodexer V4.jar" (no quotes) and see the output.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
5. Select the various options (android version, compression level, debug mode).
6. Then chose the deodex all apks option. Once the deodex is complete, you will get a popup message if it was successful or not.
7. You can find the deodexed apks in the "deodexed" folder. Copy them to some other folder and empty the "apks" and "deodexed" folder.
8. Now for framewok files, you also need to put them in the "apks" folder not in "framework" folder (because there is a bug in this tool).
9. Then you need to choose both the options deodex all apks and deodex all jars one by one.
10. Thats it... Done :good:
Now for installing deoedexed files in your phone:-
1. Put the phone in USB mass storage.
2. Go to folder where you have copied Deodexed apks and framework files and move them to the root of the sdcard.
3. Now get out from USB storage mode.
4. Go to the folder there you android SDK is installed. Go to C:\Program Files\Android\android-sdk\ [Assuming that your SDK is installed in C:\]. Then open a command prompt here. For this press Right Mouse click while holding the Shift key and select the "Open command window here" option.
5.Enter following codes.
(If you are using ADB shell in su for the first time, keep phone screen on. After entering "su" code, super user request prompt in phone. Press allow )
Code:
adb shell
su
stop
mount -o rw,remount /system/ /system/
cp /sdcard/done_app/* /system/app/
rm /system/app/*.odex
cp /sdcard/done_frame/* /system/framework/
rm /system/framework/*.odex
mount -o ro,remount /system/ /system/
reboot
6. Congrats...!!! Now you have deodexed rom :good: :victory:
Does this need unlocked bootloader?
ADB shell not working
divyamg28 said:
Hello Friends..!!!
This guide is for all who wants to deodex their roms for easy customization.
First Lets know some Basic knowledge about DEODEX/ODEX...
What is Odex and Deodex ROM
What is an ODEX file?
In Android file system, applications come in packages with the extension .apk.
These application packages, or APKs contain certain .odex files whose supposed function is to save space.
These ‘odex’ files are actually collections of parts of an application that are optimized before booting.
Doing so speeds up the boot process, as it preloads part of an application.
On the other hand, it also makes hacking those applications difficult because a part of the coding has already been extracted to another location before execution.
What is an DEODEX file?
Deodexing is basically repackaging of these APKs in a certain way, such that they are reassembled into classes.dex files.
By doing that, all pieces of an application package are put together back in one place, thus eliminating the worry of a modified APK conflicting with some separate odexed parts.
So, Deodexed ROMs (or APKs) have all their application packages put back together in one place,
allowing for easy modification such as theming. Since no pieces of code are coming from any external location,
custom ROMs or APKs are always deodexed to ensure integrity.
How this works?
For the majority noobs amongst us, Android OS uses a Java-based virtual machine called the Dalvik Virtual Machine.
A deodexed or .dex file contains the cache used by this virtual machine (referred to as Dalvik-cache) for a program, and it is stored inside the APK.
An .odex file, on the other hand, is an optimized version of this same .
dex file that is stored next to the APK as opposed to inside it.
Android applies this technique by default to all the system applications.
When an Android-based system is booting, the davlik cache for the Davlik VM is built using these .odex files, allowing the OS to learn in advance what applications will be loaded, and thus speeds up the booting process.
By deodexing these APKs, a developer actually puts the .odex files back inside their respective APK packages.
Since all code is now contained within the APK itself, it becomes possible to modify any application package without conflicting with the operating system’s execution environment.
Advanteges & Disadvantages
The advantage of deodexing is in modification possibilities.
This is most widely used in custom ROMs and themes. A developer building a custom ROM would almost always choose to deodex the ROM package first,
since that would not only allow him to modify various APKs, but also leave room for post-install theming.
On the other hand, since the .odex files were supposed to quickly build the dalvik cache, removing them would mean longer initial boot times.
However, this is true only for the first ever boot after deodexing, since the cache would still get built over time as applications are used.
Longer boot times may only be seen again if the dalvik cache is wiped for some reason.
Note: Themes for android come in APKs too, and if you want to modify any of those, you should always choose a dedoexed custom ROM.
Now Lets Start!!!
Requirements:-
1. Java installed on your PC
2. Universal Deodexer (Download from here - http://d-h.st/bMp)
3. Android SDK (for installing deodexed files)
Instructions:-
1. Now first of all you need to copy system/framework and system/apps folders from your phone to your PC. You can do this by simply using the Root Explorer or using ADB commands.
2. Download and extract the zip. You will get a folder called "Universal Deodexer V4"
3. Open the folder and place all your apks or jars from the apps folder in the "apks" folder. No need to manually check if a apk has the corresponding .odex file or not. Apks or Jars which do not have .odex files are automatically deleted.
4. Double click on Universal Deodexer V4.jar. If it does not open then right click--->Properties--->change the Opens With: to "Java(TM) Platform SE Binary". Now double click and it will open. If it still doesn't open then shift+right click anywhere in the folder and open a command prompt window there. Then type - "java -jar Universal Deodexer V4.jar" (no quotes) and see the output.
5. Select the various options (android version, compression level, debug mode).
6. Then chose the deodex all apks option. Once the deodex is complete, you will get a popup message if it was successful or not.
7. You can find the deodexed apks in the "deodexed" folder. Copy them to some other folder and empty the "apks" and "deodexed" folder.
8. Now for framewok files, you also need to put them in the "apks" folder not in "framework" folder (because there is a bug in this tool).
9. Then you need to choose both the options deodex all apks and deodex all jars one by one.
10. Thats it... Done :good:
Now for installing deoedexed files in your phone:-
1. Put the phone in USB mass storage.
2. Go to folder where you have copied Deodexed apks and framework files and move them to the root of the sdcard.
3. Now get out from USB storage mode.
4. Go to the folder there you android SDK is installed. Go to C:\Program Files\Android\android-sdk\ [Assuming that your SDK is installed in C:\]. Then open a command prompt here. For this press Right Mouse click while holding the Shift key and select the "Open command window here" option.
5.Enter following codes.
(If you are using ADB shell in su for the first time, keep phone screen on. After entering "su" code, super user request prompt in phone. Press allow )
Code:
adb shell
su
stop
mount -o rw,remount /system/ /system/
cp /sdcard/done_app/* /system/app/
rm /system/app/*.odex
cp /sdcard/done_frame/* /system/framework/
rm /system/framework/*.odex
mount -o ro,remount /system/ /system/
reboot
6. Congrats...!!! Now you have deodexed rom :good: :victory:
Click to expand...
Click to collapse
As per the above guide, i was able to deodex all system apk/framework. Then i have copied the deodexed apk and framework folder to the root of the sdcard as said above but at the time of running adb shell, all commands were accepted and except "cp /sdcard/done_app/* /system/app/", it says "cp: /sdcard/done_app/*: No such file or directories. By this, what does it mean, i don't know as it is available on sdcard and i can access it through root explorer. I am totally stuck here, kindly help me to get out of this ...
Problem using adb shell
[/INDENT][/INDENT][/INDENT][/INDENT][/INDENT]
gusato said:
As per the above guide, i was able to deodex all system apk/framework. Then i have copied the deodexed apk and framework folder to the root of the sdcard as said above but at the time of running adb shell, all commands were accepted and except "cp /sdcard/done_app/* /system/app/", it says "cp: /sdcard/done_app/*: No such file or directories. By this, what does it mean, i don't know as it is available on sdcard and i can access it through root explorer. I am totally stuck here, kindly help me to get out of this ...
Click to expand...
Click to collapse
Thanks for your advice but i think you didn't get my point, i have done all the process of deodexing apk n jar file successfully. Then i tried to push them bach into my fone with adb shell and it didn't work. Using adb shell when i entered
"cp /sdcard/done_app/* /system/app/" it says No such file or directory but when entered
"cp /sdcard/done_frame/* /system/framework/" it accept. Why this used to happen????????
Thank you so much !! This Worked really well on my Micromax a25:victory:
I tried it bt it doesn't work for me....showing some classpath error...however my java is perfectly install even test result show completely fine n every thing got passed
same here!
deoboy said:
I tried it bt it doesn't work for me....showing some classpath error...however my java is perfectly install even test result show completely fine n every thing got passed
Click to expand...
Click to collapse
Mybe theres somtething is missing in this guide! after deodexing both apks and jars, when i opened in archive still no classes.dex which is needed in decompling the apks. I think the boothclasspath is missing here?
---------- Post added at 10:40 AM ---------- Previous post was at 10:37 AM ----------
Guys can you help me decompiling the apks of huawei which being odexed? I have tried decompiling some apks of huawei and was successfully recompile without error. But my huawei g526 is odexed room which really hard to decompile. Can yopu help me? please?
divyamg28 said:
Hello Friends..!!!
This guide is for all who wants to deodex their roms for easy customization.
First Lets know some Basic knowledge about DEODEX/ODEX...
What is Odex and Deodex ROM
What is an ODEX file?
In Android file system, applications come in packages with the extension .apk.
These application packages, or APKs contain certain .odex files whose supposed function is to save space.
These ‘odex’ files are actually collections of parts of an application that are optimized before booting.
Doing so speeds up the boot process, as it preloads part of an application.
On the other hand, it also makes hacking those applications difficult because a part of the coding has already been extracted to another location before execution.
What is an DEODEX file?
Deodexing is basically repackaging of these APKs in a certain way, such that they are reassembled into classes.dex files.
By doing that, all pieces of an application package are put together back in one place, thus eliminating the worry of a modified APK conflicting with some separate odexed parts.
So, Deodexed ROMs (or APKs) have all their application packages put back together in one place,
allowing for easy modification such as theming. Since no pieces of code are coming from any external location,
custom ROMs or APKs are always deodexed to ensure integrity.
How this works?
For the majority noobs amongst us, Android OS uses a Java-based virtual machine called the Dalvik Virtual Machine.
A deodexed or .dex file contains the cache used by this virtual machine (referred to as Dalvik-cache) for a program, and it is stored inside the APK.
An .odex file, on the other hand, is an optimized version of this same .
dex file that is stored next to the APK as opposed to inside it.
Android applies this technique by default to all the system applications.
When an Android-based system is booting, the davlik cache for the Davlik VM is built using these .odex files, allowing the OS to learn in advance what applications will be loaded, and thus speeds up the booting process.
By deodexing these APKs, a developer actually puts the .odex files back inside their respective APK packages.
Since all code is now contained within the APK itself, it becomes possible to modify any application package without conflicting with the operating system’s execution environment.
Advanteges & Disadvantages
The advantage of deodexing is in modification possibilities.
This is most widely used in custom ROMs and themes. A developer building a custom ROM would almost always choose to deodex the ROM package first,
since that would not only allow him to modify various APKs, but also leave room for post-install theming.
On the other hand, since the .odex files were supposed to quickly build the dalvik cache, removing them would mean longer initial boot times.
However, this is true only for the first ever boot after deodexing, since the cache would still get built over time as applications are used.
Longer boot times may only be seen again if the dalvik cache is wiped for some reason.
Note: Themes for android come in APKs too, and if you want to modify any of those, you should always choose a dedoexed custom ROM.
Now Lets Start!!!
Requirements:-
1. Java installed on your PC
2. Universal Deodexer (Download from here - http://d-h.st/bMp)
3. Android SDK (for installing deodexed files)
Instructions:-
1. Now first of all you need to copy system/framework and system/apps folders from your phone to your PC. You can do this by simply using the Root Explorer or using ADB commands.
2. Download and extract the zip. You will get a folder called "Universal Deodexer V4"
3. Open the folder and place all your apks or jars from the apps folder in the "apks" folder. No need to manually check if a apk has the corresponding .odex file or not. Apks or Jars which do not have .odex files are automatically deleted.
4. Double click on Universal Deodexer V4.jar. If it does not open then right click--->Properties--->change the Opens With: to "Java(TM) Platform SE Binary". Now double click and it will open. If it still doesn't open then shift+right click anywhere in the folder and open a command prompt window there. Then type - "java -jar Universal Deodexer V4.jar" (no quotes) and see the output.
5. Select the various options (android version, compression level, debug mode).
6. Then chose the deodex all apks option. Once the deodex is complete, you will get a popup message if it was successful or not.
7. You can find the deodexed apks in the "deodexed" folder. Copy them to some other folder and empty the "apks" and "deodexed" folder.
8. Now for framewok files, you also need to put them in the "apks" folder not in "framework" folder (because there is a bug in this tool).
9. Then you need to choose both the options deodex all apks and deodex all jars one by one.
10. Thats it... Done :good:
Now for installing deoedexed files in your phone:-
1. Put the phone in USB mass storage.
2. Go to folder where you have copied Deodexed apks and framework files and move them to the root of the sdcard.
3. Now get out from USB storage mode.
4. Go to the folder there you android SDK is installed. Go to C:\Program Files\Android\android-sdk\ [Assuming that your SDK is installed in C:\]. Then open a command prompt here. For this press Right Mouse click while holding the Shift key and select the "Open command window here" option.
5.Enter following codes.
(If you are using ADB shell in su for the first time, keep phone screen on. After entering "su" code, super user request prompt in phone. Press allow )
Code:
adb shell
su
stop
mount -o rw,remount /system/ /system/
cp /sdcard/done_app/* /system/app/
rm /system/app/*.odex
cp /sdcard/done_frame/* /system/framework/
rm /system/framework/*.odex
mount -o ro,remount /system/ /system/
reboot
6. Congrats...!!! Now you have deodexed rom :good: :victory:
Click to expand...
Click to collapse
I had some few questions? After deodexing my apks and frameworks, I was able to check the classes.dex was there but why when I decompiled the apks then smali is empty? I thought that the size of deodexed apks would be bigger but the size of odexed apk still the same with deodexed apks? can you help to solve my problem? I dont why encounter ?
---------- Post added at 05:27 AM ---------- Previous post was at 05:10 AM ----------
deoboy said:
I tried it bt it doesn't work for me....showing some classpath error...however my java is perfectly install even test result show completely fine n every thing got passed
Click to expand...
Click to collapse
yes thats what I think coz after reading the error I thnink the bootclasspath is missing. hope it will be fixed soon...
---------- Post added at 05:34 AM ---------- Previous post was at 05:27 AM ----------
toto2011 said:
I had some few questions? After deodexing my apks and frameworks, I was able to check the classes.dex was there but why when I decompiled the apks then smali is empty? I thought that the size of deodexed apks would be bigger but the size of odexed apk still the same with deodexed apks? can you help to solve my problem? I dont why encounter ?
---------- Post added at 05:27 AM ---------- Previous post was at 05:10 AM ----------
yes thats what I think coz after reading the error I thnink the bootclasspath is missing. hope it will be fixed soon...please see attaeched photos
Click to expand...
Click to collapse
Hello, I have already pulled my .apks and .jars but nothing is appearing in the deodexed file. Here's the debug script of what happens with any one particular .apk:
deodexapk.bat said:
Welcome!
Deodexing apk..
Compression=0
API=17
'xcopy' is not recognized as an internal or external command, operable program or batch file.
Can't find the file AllshareMediaShare.odex
UNEXPECTED TOP-LEVEL EXCEPTION:
java.lang.RuntimeException: Cannot find file or directory "out/" at org.if.smali.main.main(main.java:180)
'xcopy' is not recognized as an internal or external command, operable program or batch file.
Can't find the file AllshareMediaShare.odex
'xcopy' is not recognized as an internal or external command, operable program or batch file.
Can't find the file AllshareMediaShare.odex
'xcopy' is not recognized as an internal or external command, operable program or batch file.
Can't find the file AllshareMediaShare.odex
'7za' is not recognized as an internal or external command, operable program or batch file.
Can't find the file AllshareMediaShare.odex
'7za' is not recognized as an internal or external command, operable program or batch file.
Can't find the file AllshareMediaShare.odex
The system cannot find the file specified.
'xcopy' is not recognized as an internal or external command, operable program or batch file.
The system cannot find the file specified.
Could Not Find C:¥Users¥Teracotta¥Downloads¥Android¥Universal Deodexer V4¥framework¥AllshareMediaShare.odex
Could Not Find C:¥Users¥Teracotta¥Downloads¥Android¥Universal Deodexer V4¥framework¥classes.dex
The system cannot find the file specified.
Could Not Find C:¥Users¥Teracotta¥Downloads¥Android¥Universal Deodexer V4¥framework¥AllshareMediaShare.odex
DEODEXED SUCCESSFULLY.
Press any key to continue...
Click to expand...
Click to collapse
The Path I have set in Advanced Systems: C:\ProgramData\Oracle\Java\javapath;C:\Users\Teracotta\AppData\Local\Android\android-sdk\platform-tools