I want to deodex stock firmware (2.36 - XWKTH) and i made the zip file with system folder include 'app' and 'framework' folders.
I can't create update-script for this.
any bady can make me a list of commands For the following? (of course with mount system and what is needed for this)
Code:
deleting .odex files forom app and framework.
copying system folder (in the zip file) to /system
Many thanks!
Related
I'm looking for a deodexed version of the stock Telus/Koodo (Canada) rom for Galaxy Ace. I have the odexed version, but I'm not sure how to deodex. If anyone knows where I can get the deodexed version, or can help me with deodexing, it would be greatly appreciated.
Quietly, THIS IS DEVELOPMENT SECTION and not Q&A or GENERAL, POST IT THERE, here will be posted roms! READ THE XDA RULES BEFORE POSTING -.-
I only know how to deodex on Windows.
First have/download your SG Ace firmware (Canada)
Extract your firmware contents using MagicISO to: firmware_name\system
Download AutoDEOTool1.0.4 (Just a modified version of the tool, including updated binaries)
Unzip it to a directory without spaces e.g: C:\
Move/Copy your firmware's apps and framework files to: _app & _framework
Run AutoDEOToolMain.bat
Hit 2 to be specific.
To find your bootclasspath, just download Terminal Emulator on your Android phone
Run the command: echo $BOOTCLASSPATH
To save it in your sdcard, run: echo $BOOTCLASSPATH>>/sdcard/bootclasspath.txt
Open the bootclasspath.txt, remove any "/system/framework/" codes (without the quotes) then save it
Now copy everything in bootclasspath.txt
Then in the AutoDEOToolMain windows, paste your bootclasspath & hit enter
This will deodex all files in _app & _framework
NOTE: If there are still some odexed files left, then use dsixda's kitchen to deodex the remaining files.
Now copy/move all files in _app to your firmware's /system/app folder
Copy/move all files in _framework to your firmware's /system/framework folder
Now you have a deodexed Canada firmware!
Download these rom_tools and extract it to the root of the extracted firmware (firmware_name)
Now add the boot.img
Zip it and to flash it!
Thanks, I'll try that tonight. What exactly do the rom tools do? I looked at the archive, and I'm pretty sure busybox means root, but what about the rest?
sauron82 said:
Thanks, I'll try that tonight. What exactly do the rom tools do? I looked at the archive, and I'm pretty sure busybox means root, but what about the rest?
Click to expand...
Click to collapse
data folder is optional to include
META-INF folder is to flash the ROM
format.sh formats your Ace/Gio
installbusybox.sh installs busybox
mkfs.ext4 is the tool that format.sh uses
Here are some tools I put together to deopt/deodex a system.img
It's been partially tested and works for me, but needs some more testing
I'll continue working on it to fine tune/clean scripts.
Linux Only For Now!
What does this do exactly?
This de-odexes the app, priv-app and framework folders, adds .dex files and lib folders to the appropriate apks/jars and folders, removes odex files and organizes everything into structured folders ready to flash. This does all the work so you don't have to.
Why would I want to do this?
Doing this helps with customization of apks. You can theme the launcher or even replace the lockscreen photos with your own if you choose
This also shrinks the stock system.img to 700+MB
Warning: contains the command 'sudo' for linux root permissions in unpack/repack scripts. Just an easy workaround for now
Instructions:
extract the zip
chmod 755 -R the extracted folder
Add a stock system.img to the extracted folder
run ./unpack.sh to mount the system.img
copy app, priv-app and framework from the 'fugu' folder to the 'system' folder
run ./oat2dex.sh to deodex the 3 folders
remove the 3 folders from the 'fugu' folder
add the 3 folders from the 'system' folder to the 'fugu' folder
run ./repack.sh to build the system.img
Download - auto-oat2dex-fugu_v1.zip
Um I'm familiar with deodex but what's de-opt?
Sent from my Nexus 6
trvbone said:
Um I'm familiar with deodex but what's de-opt?
Sent from my Nexus 6
Click to expand...
Click to collapse
It's de-optimization, which is a method to undo the oat optimized dex. It's similar to deodexing.
awesome thanks, ill test this out tomorrow.
thanks for sharing,
dfl
negamann303 said:
Here are some tools I put together to deopt/deodex a system.img
It's been partially tested and works for me, but needs some more testing
I'll continue working on it to fine tune/clean scripts.
Linux Only For Now!
What does this do exactly?
This de-odexes the app, priv-app and framework folders, adds .dex files and lib folders to the appropriate apks/jars and folders, removes odex files and organizes everything into structured folders ready to flash. This does all the work so you don't have to.
Why would I want to do this?
Doing this helps with customization of apks. You can theme the launcher or even replace the lockscreen photos with your own if you choose
This also shrinks the stock system.img to 700+MB
Warning: contains the command 'sudo' for linux root permissions in unpack/repack scripts. Just an easy workaround for now
Instructions:
extract the zip
chmod 755 -R the extracted folder
Add a stock system.img to the extracted folder
run ./unpack.sh to mount the system.img
copy app, priv-app and framework from the 'fugu' folder to the 'system' folder
run ./oat2dex.sh to deodex the 3 folders
remove the 3 folders from the 'fugu' folder
add the 3 folders from the 'system' folder to the 'fugu' folder
run ./repack.sh to build the system.img
Download - auto-oat2dex-fugu_v1.zip
Click to expand...
Click to collapse
Can you please deodex Marshmallow stock rom for Nexus Player ?
Thanks a lot
Can u provide deodexed all system apps links.
APK-Patcher Lite
Flashable Zip Template for Modifying System APKs On-Device
Based on APK-Patcher by @osm0sis
Information
This is a modified version of APK-Patcher that will delete / inject files into System APK files instead of using a baksmali / apktool method.
The method used here is a similar method used in my ROMs to patch files, where instead of having to have like for example 4 SystemUI files, I only needed to keep the actual files that were changed.
This method could also be used quite easily to apply OTA updates or addons on already pre-modified APK files.
LINK TO GITHUB (STANDARD): https://github.com/djb77/APK-Patcher-Lite
LINK TO GITHUB (MAGISK): https://github.com/djb77/APK-Patcher-Lite_Magisk
Usage
Copy your pre-compiled resource files (including .dex files) to the patch folder, removing the .apk part of the filename (ie: SystemUI)
Create a file in scripts with the same name (ie: SystemUI.sh) if you want to delete any existing files from the APK
Make edits to envvar.sh, and also to extracmd.sh if needed
Properties / Variables (envvar.sh)
banner="";
apklist="";
apkbak=/data/media/0/APK-Backup;
backup=1;
cleanup=1;
banner is the name of your patch zip, usually suggestive of what it does, to be displayed at the beginning of the zip flash. You should include your name/handle here like "by osm0sis @ xda-developers" for credit purposes.
apklist is a string containing the list of APKs to be patched included in the patch zip, separated by spaces between the quotes. Each APK is automatically found recursively in /system, then copied to the working directory to be decompiled and acted on, then copied back to /system.
apkbak is the location to place backups of the untouched APKs in apklist if backup=1 is set.
backup=1 will store backups of the untouched APKs in the location specified in apkbak.
cleanup=0 will keep the zip from removing it's working directory in /tmp/apkpatcher - this can be useful if trying to debug in adb shell whether the patches worked correctly. cleanup=1 is necessary on multi-APK patching zips, so it's recommended each APK to be patched be tested on their own with cleanup=0 before combining into a single zip.
envvar.sh
Modify the envvar.sh to add your banner, apklist, backup and cleanup options
Multiple files can be patched, put a space between the filenames (ie: apklist="file1.apk file2.apk"
extracmd.sh
Modify the extracmd.sh to add any additional commands to be performed at the end of the patching process that aren't patch-related (/data file changes,
scripts/$apkname.sh
fileremove="";
$apkname is the name of the folder that you put your resources files in. Copy scripts_sample.sh and rename it to your APK (ie: SystemUI.sh)
Multiple files can be deleted, put a space between the paths (ie: fileremove="/res/drawable/file1.png /res/drawable/file1.png"
For me returned error bellow
Code:
local entry crc does not match
I want to use root explorer to copy some file into some system folder,
root explorer can successful mount system as RW. but when I copy files, it failed and show "read-only".
the strange things is: I can rename or modify a file/ folder, for example: I can modify "build.prop" and save it successfully.
so the problem is: I can't create new files or folders, but I can modify existing file an folders?
Dear all, I need help im modifying system.img from Stockrom. I can delete apks (de-bloating) but I do not know how to add new apks!
So far I have done the following steps:
1. Untar AP*.tar.md5
2. Extract with LZ4 system.img.lz4
3. simg2img system.img system-new.raw
4. sudo mount -t ext4 -o loop system-new.raw mnt/
5. delete bloatware apps from system/app and system/priv-app
6. add additional apks to system/app and system/priv-app????
7. umount, img2simg, lz4, tar and flash (e.g. Odin)
I have real issues with step 6, everything I tried so far did not work.
a) add apks to system/app and system/priv-app with user root and 644
b) create directories in system/app and system/priv-app
c) replace apks in system/app and system/priv-app
While the de-bloating works, step 6 is broken! The new apps are not usable. They show up with the generic android "robot icon" and their canonical name (e.g. org.fdroid.fdroid...) and are immediately stopped.
What is the correct approach to add additional apks to an existing stock rom image? Please help.