I've tried using SVN multiple times, each time with the same result (failure). Can anybody tell me what I'm doing wrong?
I'm trying to download the Bliss rom. Each time, I use my Mac client and click "export" to a folder on my desktop. Next, I zip the folder up into a file called "bliss.zip" and push it with ADB to the phone. When I try to flash with CWM, I get Installation Aborted shortly after starting the install.
I use a Mac as well. Do this, download the application called SmartSVN (just Google it), set up the repo using that. Download it (the SVN files from http://code.google.com/p/bliss-sense) to a folder in your Macintosh HD (I named mine bliss-sense), then download and install dsixda's kitchen. Just follow his instructions in his thread (here: http://forum.xda-developers.com/showthread.php?t=633246). Drag the fully downloaded boot.img, data, META-INF, and system folders into a folder that you create inside the Disk.img you made for the kitchen, naming the folder WORKING_BlissSense. Open up terminal, cd into the mounted Disk.img you made with your kitchen in, run "./menu" without quotes to load the Kitchen's menu. Select option 99 "Build ROM from Working Folder" and do interactive mode (option 1). Do Y for zipalign, Y for signing the ROM, and rename if you want. Then mount your phone to the computer and drag the new ROM zip from the OUTPUT_ZIP folder in the kitchen where your ROM is after building to your SD Card. Flash in CWM and reboot. There you go. Hope it works.
Oh, you have to use the kitchen?
...
derp
Yes you have to use the Android Kitchen.
Sent from my ADR6300 using XDA App
Has someone already tested this Mod on the Xperia ZL?
http://forum.xda-developers.com/showthread.php?t=2202383
Yes it works !!!!!
Yes I installed it, tested it and can confirm it works on the Sony Xperia ZL.
First I rooted the phone using this method:
http://forum.xda-developers.com/showthread.php?t=2186368
Then I download the files to computer then to my SD Card/external storage on smartphone.
Back up all necessary file from system/app such systemui.apk, systemui.odex, taskswitcher.apk, settings.apk and settings.odex files to my sd card/external storage in case it went wrong.
Deleted the systemui.odex and settings.odex files.
Copy on files at a time for example the systemui.apk file to the system folder then changed the permission to rw-r--r-- then delete and move the the systemui.apk file to the system/app folder. I did the same for teh other files as well.
Finally reboot the smartphone and voila it should work.
Darkfunnyguy said:
Yes I installed it, tested it and can confirm it works on the Sony Xperia ZL.
First I rooted the phone using this method:
http://forum.xda-developers.com/showthread.php?t=2186368
Then I download the files to computer then to my SD Card/external storage on smartphone.
Back up all necessary file from system/app such systemui.apk, systemui.odex, taskswitcher.apk, settings.apk and settings.odex files to my sd card/external storage in case it went wrong.
Deleted the systemui.odex and settings.odex files.
Copy on files at a time for example the systemui.apk file to the system folder then changed the permission to rw-r--r-- then delete and move the the systemui.apk file to the system/app folder. I did the same for teh other files as well.
Finally reboot the smartphone and voila it should work.
Click to expand...
Click to collapse
Thank you for your explanations, because I also have the problem.
I have some questions:
1. I did not use this method to root, which for me is more complicated. Is that my problem may be here?
2. What recovery are you using?
3. can you detail me this because I do not understand:
"Copy on files at a time for example the systemui.apk file to the system folder then changed the permission to rw-r--r-- then delete and move the the systemui.apk file to the system/app folder. I did the same for teh other files as well.
In the topic, asked to remove only two files."
Thank you to you for your help
Compare to other method to rooting I looked this is by far the easiest to root without unlocking the bootloader as well. It only takes a minutes or two.
Sorry I have not used any recovery as of yet apart from android software such as backup pro or backup and restore.
When you downloaded the files from here in Zip or WinRAR format I used I extract the three files systemui.apk, taskswitcher.apk and settings.apk to your computer/laptop then connect up your Xperia ZL to the computer/laptop then copy or move these files to your Xperia ZL on your sd card.
You need to download something like android app like file manager and make sure the settings on file manager is set to root.
Now I used the file manager copy the systemui.apk to the system folder then I press on systemui.apk to press option for permission to change the permission with the with the first column all boxes ticked for read and second column only the top for owner is ticked for write, all other boxes including the third column for execute is left unticked.
Now I move the systemui.apk file to the system/app folder replacing the current systemui.apk. I used the same method for settings.apk and taskswitcher.apk files. Once you done that reboot your smartphone.
Darkfunnyguy said:
Compare to other method to rooting I looked this is by far the easiest to root without unlocking the bootloader as well. It only takes a minutes or two.
Sorry I have not used any recovery as of yet apart from android software such as backup pro or backup and restore.
When you downloaded the files from here in Zip or WinRAR format I used I extract the three files systemui.apk, taskswitcher.apk and settings.apk to your computer/laptop then connect up your Xperia ZL to the computer/laptop then copy or move these files to your Xperia ZL on your sd card.
You need to download something like android app like file manager and make sure the settings on file manager is set to root.
Now I used the file manager copy the systemui.apk to the system folder then I press on systemui.apk to press option for permission to change the permission with the with the first column all boxes ticked for read and second column only the top for owner is ticked for write, all other boxes including the third column for execute is left unticked.
Now I move the systemui.apk file to the system/app folder replacing the current systemui.apk. I used the same method for settings.apk and taskswitcher.apk files. Once you done that reboot your smartphone.
Click to expand...
Click to collapse
Thanks.
Yes, I do that and it's ok.
Look at : http://forum.xda-developers.com/showpost.php?p=40569989&postcount=443
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