Related
I need to copy a single file using an update-script (update.zip's script)
I know that command to copy a dir is
Code:
copy_dir
But if i want to copy only a single file how can i do?
Exit93 said:
I need to copy a single file using an update-script (update.zip's script)
I know that command to copy a dir is
Code:
copy_dir
But if i want to copy only a single file how can i do?
Click to expand...
Click to collapse
put only a single file in the dir? not sure i get your problem, the script should copy everything from the update.zip to the flash memory, why would there be a need to copy a single file?
Kendon is right. Just
Code:
show_progress 0.1 0
copy_dir PACKAGE:system SYSTEM:
show_progress 0.1 10
is needed to copy a single file into the system directory. That script is from one to install WaveSecure to ROM. All it does is copy the contents of the system folder (which is a folder called app, to that location on the system partition of the phone. As there is only one file in the folder app, that file is added or overwritten. Nothing else is changed.
No, i need to copy only one file form SYSTEM to DATA
Then format SYSTEM and recopy that file from DATA to SYSTEM
How can i do?
Exit93 said:
No, i need to copy only one file form SYSTEM to DATA
Then format SYSTEM and recopy that file from DATA to SYSTEM
How can i do?
Click to expand...
Click to collapse
i don't think this is possible with update-script, as it wasn't made for this purpose. care to elaborate what your main goal is, maybe we can find other ways?
kendong2 said:
i don't think this is possible with update-script, as it wasn't made for this purpose. care to elaborate what your main goal is, maybe we can find other ways?
Click to expand...
Click to collapse
I have to format system partition but i have to preserve /system/init.rc file
Deleting all system's subdirs doesn't work
I am not sure if someone posted something similar or not.
Anyways.
This ZIP file does not have a KERNEL in it, it is just a ZIP with empty boot and system folder. The META-INF contains a script that will copy everything in boot to your \boot in your ROM and everything in system to your \system in your ROM.
NOTE: It will overwrite any files that have the same file name in the same folder. So, yes, you can use it for other than updating kernel, say copying a file to a specific folder in \system partition, or \boot partition.
Just open with 7-zip, drop zImage file into the boot folder, then drop modules in the system\lib\modules folder. Copy the zip file to your SD, then run Clockwork Recovery, and install the zip.
thanks,
will try this ASAP
LiFE1688 said:
I am not sure if someone posted something similar or not.
Anyways.
This ZIP file does not have a KERNEL in it, it is just a ZIP with empty boot and system folder. The META-INF contains a script that will copy everything in boot to your \boot in your ROM and everything in system to your \system in your ROM.
NOTE: It will overwrite any files that have the same file name in the same folder. So, yes, you can use it for other than updating kernel, say copying a file to a specific folder in \system partition, or \boot partition.
Just open with 7-zip, drop zImage file into the boot folder, then drop modules in the system\lib\modules folder. Copy the zip file to your SD, then run Clockwork Recovery, and install the zip.
Click to expand...
Click to collapse
It doesn't have to be signed?
Code:
ui_print("Welcome to MDJ Kernel Updater");
mount("MTD", "boot", "/boot");
mount("MTD", "system", "/system");
ui_print("Copying zImage...");
package_extract_dir("boot", "/boot");
ui_print("Copying modules...");
package_extract_dir("system", "/system");
unmount("/system");
unmount("/boot");
ui_print("All Done...");
I don't see anything in the updater-script that requires signing.
Actually, original idea and script by Shadiku...
He actually made two scripts.
can i create a folder called androidapp and put the apks in it and install them automatically like we do with the SD roms
it's not working for me.. try to change the kernel to hastarin that support Extended battere..
it says "Instalation aborted "... what happened?
any clue?
edit : can push the Zimage and some other files, but it stuck with the gogogo...
I have 4 computers that I use and 2 of them have adb drivers installed, the other 2(work computers that i am not really allowed to install much on) does not. To be able to push files to my htc desire on the computers that i do not have adb drivers installed I need a flashable zip. I only want to push files such as ringtones, /system apps, bootanimation.zip files and such, i have no intention of changing the framework or the theme and so on. So could anyone point me in the direction of where could i find a ready empty zip file like this or a tutorial in how to make one?
P.S. one of the uses for this is when i am out on a business trip i do not have my personal computer with me, so if brut-maps gets updated i want to be able to push it to the phone without adb.
Hello.
I only have basic knowledge on the subject, so i'm just gonna explain what i do when i need to flash something via flashable .zip.
1) Get a simple flashable .zip used to flash files anywhere on the /system partition.
2) Open it with WinRAR or 7zip or whatever. Navigate to META-INF/com/google/android/. There you will find two files: update-binary and updater-script. You need not touch the binary, because it's the same for all flashable .zips. What you need to do is extract then edit the updater-script, as that tells the recovery what to do with the flashable .zip's contents.
3) Editing the updater-script: let's say we need to create a .zip to flash a new Mail.apk to /system/app. The updater-script's content would need to be:
Code:
show_progress(0.1, 0);
mount("MTD", "system", "/system");
delete("/system/app/Mail.apk");
package_extract_dir("system", "/system");
show_progress(0.1, 10);
unmount("/system");
The "show_progress" lines are self-explanatory. The "mount" command tells the system to mount the /system partition. We then delete the old Mail.apk and tell the recovery where we want to extract the contents of the .zip. After everything's done, we unmount /system.
Add the edited updater-script to the archive, overwriting the original one. Be sure to set your archiver to "Normal" compression level.
4) Creating the proper directory structure: again, let's say we need to flash Mail.apk to /system/app and that we have properly configured the updater-script for this task. We now need to create a folder named "system" (anywhere on the PC), place a subfolder named "app" inside it, then place the new Mail.apk inside the "app" subfolder. We then add the whole structure to the flashable .zip (making sure that there are no other folders in it than "META-INF") and that's that! Again, make sure you use "Normal" compression.
5) Copy the .zip to your SD card, reboot into Recovery and flash the .zip.
6) Enjoy!
thank you very much, that was exactly the kind of information i was looking for.
You're welcome.
Here's a simple flashable .zip i used to replace media_profiles.xml in the /system/etc folder when i didn't have a PC handy and my phone wouldn't boot. You can edit it and use it for your own purpose.
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
- I unzipped e.g. T705XXU1ANF from samdownloads.de.rar.
- Then I opened the T705XXU1ANF7.tar.md5 and extracted the *.img files with winrar.
- Then I tried to mount system.img / recovery.img with OSFMount.
Mounting worked but non of the ext2 tools (Ext2Fsd, ext2explore, explore2fs-1.08beta9, Paragon ExtFS for Windows, LinuReader ) would recognice the mounted image or could mount the image itself to view the files.
For ICS/JB I read about ext4_unpacker. Do we have something like that for Kitkat ? Or is it possible under Linux (I am a noob there)
Basically on Linux, it's really easy.
mount -o loop disk1.iso /mnt/disk
Or wherever that you want it to be.
did one of you mount an system.img from Kitkat Stock Rom already ?? Because I dont think ist about W7/8 .... some of the tools listed should be able to read ext4 ... (ext4_unpacker wont work either !!)
pegasus21 said:
Basically on Linux, it's really easy.
mount -o loop disk1.iso /mnt/disk
Or wherever that you want it to be.
Click to expand...
Click to collapse
no it cant be mounted that way... I tried under unbuntu LiveDVD. the System.img can be mounted, but there is no readable filesystem. So it must be processed in some form like ext4unpacker did for ICS/JB ...
gggg said:
no it cant be mounted that way... I tried under unbuntu LiveDVD. the System.img can be mounted, but there is no readable filesystem. So it must be processed in some form like ext4unpacker did for ICS/JB ...
Click to expand...
Click to collapse
You're right... I thought it worked out of the box.
Anyway, I used RKwinTools to extract the system.img contents on Windows.
Place system.img in RKwinTools_v133\unpack\firmware\image\
Run the batch file and select option 6 and you'll find the contents under RKwinTools_v133\unpack\System
pegasus21 said:
You're right... I thought it worked out of the box.
Anyway, I used RKwinTools to extract the system.img contents on Windows. Place system.img in RKwinTools_v133\unpack\firmware\image\
Run the batch file and select option 6 and you'll find the contents under RKwinTools_v133\unpack\System
Click to expand...
Click to collapse
THX unpacking worked like a charm, but is there also a way of just converting the img to one that is a mountable.ext4. This one I could use under Win and Linux as it would keep permissions ... (Simg2img didnt work)
This is the error:
Code:
*** Please wait... ***
Ext4Extractor version 1.5.2 Created by And_PDA Based on sources ext4_unpacker
Extractor for images in EXT2\EXT3\EXT4\SPARSE formats
Open image file Unpack/Firmware/Image/system.img successfull...
Found SPARSE FORMAT
Convert to EXT4 format started...
Convert to EXT4 format finish success
*********************************
*** Error! ***
*********************************
gggg said:
THX unpacking worked like a charm, but is there also a way of just converting the img to one that is a mountable.ext4. This one I could use under Win and Linux as it would keep permissions ... (Simg2img didnt work)
This is the error:
Code:
*** Please wait... ***
Ext4Extractor version 1.5.2 Created by And_PDA Based on sources ext4_unpacker
Extractor for images in EXT2\EXT3\EXT4\SPARSE formats
Open image file Unpack/Firmware/Image/system.img successfull...
Found SPARSE FORMAT
Convert to EXT4 format started...
Convert to EXT4 format finish success
*********************************
*** Error! ***
*********************************
Click to expand...
Click to collapse
Well option 7 will convert the sparse ext4 image to a normal ext4 image. The message shows error but it would seem that it's converted. Find the image in the same location that you placed system.img.
Mount system_ext4.img on linux using
Code:
mount -t ext4 -o loop system_ext4.img /mnt
pegasus21 said:
Well option 7 will convert the sparse ext4 image to a normal ext4 image. The message shows error but it would seem that it's converted. Find the image in the same location that you placed system.img.
Click to expand...
Click to collapse
THX so far, I can mount it on my Linux PC not under Win8
- Linux Rader still cant open it
- I can Mount it with OSFMount, but neither paragon ExtFS nor ext2Mgr recognice the mounted Drive ????
ideas very welcome
gggg said:
ideas very welcome
Click to expand...
Click to collapse
try this windows system to ext4 double click bat file then drag your system.ing,cache.img or data.img to the open window
pegasus21 said:
You're right... I thought it worked out of the box.
Anyway, I used RKwinTools to extract the system.img contents on Windows.
Place system.img in RKwinTools_v133\unpack\firmware\image\
Run the batch file and select option 6 and you'll find the contents under RKwinTools_v133\unpack\System
Click to expand...
Click to collapse
How to decompile the boot and the kernel?
hello... how to repack the unpacked files?
pegasus21 said:
You're right... I thought it worked out of the box.
Anyway, I used RKwinTools to extract the system.img contents on Windows.
Place system.img in RKwinTools_v133\unpack\firmware\image\
Run the batch file and select option 6 and you'll find the contents under RKwinTools_v133\unpack\System
Click to expand...
Click to collapse
bro can you little explain how its work, i have win , after extract i have just this 3 folders
_in
app
cywim
so where i put system.img.ext4 files?
i really don,t care about extracted i need to repack to ext4