Database Develop

Tweaking rom - begginer question ;)

Hi!
Since xda-univeristy arised i thought it would be nice to learn something about green droid
I am going to learn about tweaking and theming:and here comes dozens of my questions:
1. I have downloaded Official ics repack by N00BY0815
2. I extracted it and i have:
2 folders ( META-INF and System)
2 files boot.ing and system.img
How can i extract this system.img ?
I tried to use 7zip but it says that" it cannot open it as archive"
Thanks in advance and please for leniency

it can be opened with Diskinternals Linux Reader. if not. use "sgs2toext4.jar" to convert it to .img.ext4 and then open it

Nihiliu said:
Hi!
Since xda-univeristy arised i thought it would be nice to learn something about green droid
I am going to learn about tweaking and theming:and here comes dozens of my questions:
1. I have downloaded Official ics repack by N00BY0815
2. I extracted it and i have:
2 folders ( META-INF and System)
2 files boot.ing and system.img
How can i extract this system.img ?
I tried to use 7zip but it says that" it cannot open it as archive"
Thanks in advance and please for leniency
Click to expand...
Click to collapse
Everything for theming is in the System folder. All the APK's(Applications) Boot.img is probably the recovery image it installs. But to theme you would need to decompile the apks in the system folder

Everythink was in system folder in gingerbread, in this system folder i have only app folder with su.apk and bin folder with su file.
So files i need are in system.img
@broodplank1337 thanks for help, program works well, now i can begin
But first only one question, now i can extract files, but can i pack them using same tool ?

Nihiliu said:
Everythink was in system folder in gingerbread, in this system folder i have only app folder with su.apk and bin folder with su file.
So files i need are in system.img
@broodplank1337 thanks for help, program works well, now i can begin
But first only one question, now i can extract files, but can i pack them using same tool ?
Click to expand...
Click to collapse
I don't know much about S2 but can't you just use 7zip to make it an archive and flash it through rrecovery?
"Anger and intolerance are the enemies of correct understanding." -Mahatma Gandhi

Nihiliu said:
How can i extract this system.img ?
Click to expand...
Click to collapse
Hi. You can use dsixda's Android Kitchen for that.

Nihiliu said:
Everythink was in system folder in gingerbread, in this system folder i have only app folder with su.apk and bin folder with su file.
So files i need are in system.img
@broodplank1337 thanks for help, program works well, now i can begin
But first only one question, now i can extract files, but can i pack them using same tool ?
Click to expand...
Click to collapse
You can pack them with the android kitchen, install the zip, then you do this in terminal emulator to make the system.img file:
Code:
su
cat proc/mounts
now look up the system partition, in my case it's mmcblk0p14
Code:
dd if=/dev/block/mmcblk0p14 of=/sdcard/system.img BS=4096
This will dump the system partition to system.img (for example when making an odin image)

[SOLVED]How to convert system.sin to system.img?

Been looking around and I cannot get info(or I may have missed it) on how to convert system.sin to system.img.
The reason I want the system.img is I'd like to try deodexing my own JB(HKversion) stock rom.
how can I manage it in dsixda's kitchen, it says I need a system.img or either one of the following:
The format for each ROM must be one of the following:
- system.img + optional boot.img/lib.img (e.g. stock ROM or Nandroid)
- ZIP file for a custom ROM (e.g. update.zip)
- ZIP file containing *.img (e.g. stock rom.zip)
- ZIP file containing shipped ROM in SYSTEM + BOOT folder format
- Working folder made with this kitchen (e.g. WORKING_old_rom)
What I've already done so far was pulled out the system.sin from an FTF and made it system.ext4 in flashtool. And I also have extracted all the system files but I don't know how to go from here LoL.
Thanks in advance for any inputs guys.

Rycon33 said:
Been looking around and I cannot get info(or I may have missed it) on how to convert system.sin to system.img.
The reason I want the system.img is I'd like to try deodexing my own JB(HKversion) stock rom.
how can I manage it in dsixda's kitchen, it says I need a system.img or either one of the following:
The format for each ROM must be one of the following:
- system.img + optional boot.img/lib.img (e.g. stock ROM or Nandroid)
- ZIP file for a custom ROM (e.g. update.zip)
- ZIP file containing *.img (e.g. stock rom.zip)
- ZIP file containing shipped ROM in SYSTEM + BOOT folder format
- Working folder made with this kitchen (e.g. WORKING_old_rom)
What I've already done so far was pulled out the system.sin from an FTF and made it system.ext4 in flashtool. And I also have extracted all the system files but I don't know how to go from here LoL.
Thanks in advance for any inputs guys.
Click to expand...
Click to collapse
Just rename it.
That works if you want to use system.sin in dsixdas kitchen to make your own rom.
The instructions say to rename system.sin to system.img
PS, in fact you can just use system.sin, check in the first post for supported devices, it tlks about what to do for sony phones

gregbradley said:
Just rename it.
That works if you want to use system.sin in dsixdas kitchen to make your own rom.
The instructions say to rename system.sin to system.img
PS, in fact you can just use system.sin, check in the first post for supported devices, it tlks about what to do for sony phones
Click to expand...
Click to collapse
- If using stock FTF for kitchen:
1) Unzip FTF file, extract the system.sin
2) Dump system image from system.sin w/ Flashtool
(Advanced-> SIN Editor)
3) Rename dumped file to system.img
mate, I tried renaming it and put it on "original_update" folder but still the file cannot be detected I still cannot create a working folder and says
CREATE WORKING FOLDER FOR ROM
==============================
Ensure there is at least one ROM under the 'original_update' folder!
Select an option:
s - Show supported formats
x - Abort, don't create working folder
Or press Enter to continue
?
I also tried renaming the flashtool's dumped data(system.ext4) to system.img but still to no avail.
Any other way aside from system.img thing?

Rycon33 said:
- If using stock FTF for kitchen:
1) Unzip FTF file, extract the system.sin
2) Dump system image from system.sin w/ Flashtool
(Advanced-> SIN Editor)
3) Rename dumped file to system.img
mate, I tried renaming it and put it on "original_update" folder but still the file cannot be detected I still cannot create a working folder and says
CREATE WORKING FOLDER FOR ROM
==============================
Ensure there is at least one ROM under the 'original_update' folder!
Select an option:
s - Show supported formats
x - Abort, don't create working folder
Or press Enter to continue
?
I also tried renaming the flashtool's dumped data(system.ext4) to system.img but still to no avail.
Any other way aside from system.img thing?
Click to expand...
Click to collapse
wait, let me boot into linux and I will check

gregbradley said:
wait, let me boot into linux and I will check
Click to expand...
Click to collapse
mate, btw I'm only using cygwin in win7 if that matters on my issue

Rycon33 said:
mate, btw I'm only using cygwin in win7 if that matters on my issue
Click to expand...
Click to collapse
No, it doesnt matter, I did it with that setup, but its much easier with a ubuntu dual boot.
What you did should work.
Extract system.sin
Dump it with flash tool to get system.ext4, rename to system.img and put in original input folder.
then choose create working folder....
try it again,

gregbradley said:
No, it doesnt matter, I did it with that setup, but its much easier with a ubuntu dual boot.
What you did should work.
Extract system.sin
Dump it with flash tool to get system.ext4, rename to system.img and put in original input folder.
then choose create working folder....
try it again,
Click to expand...
Click to collapse
thanks mate, after I re-do the dump-data in flashtool, now system.img(renamed from system.ext4) can be detected
got another question again, just to confirm what's the API level? is it 16 for Android 4.1.2? coz I only see 4.1.1 for level 16

Rycon33 said:
thanks mate, after I re-do the dump-data in flashtool, now system.img(renamed from system.ext4) can be detected
got another question again, just to confirm what's the API level? is it 16 for Android 4.1.2? coz I only see 4.1.1 for level 16
Click to expand...
Click to collapse
if you have the latest version of everything it should be OK.
Just give it a go and see...
I used the same setup I have for my latest release as I did for my original ICS release, so the api level should be OK
EDIT
I do love your sig pic, where did you get it from? Or did you make it yourself?

gregbradley said:
if you have the latest version of everything it should be OK.
Just give it a go and see...
I used the same setup I have for my latest release as I did for my original ICS release, so the api level should be OK
EDIT
I do love your sig pic, where did you get it from? Or did you make it yourself?
Click to expand...
Click to collapse
with regards to my sig banner, i got it from one of the post from G+ last time, here's a copy of the actual file -> https://dl.dropbox.com/u/28587036/Android/Android_Evolution.jpg
ok I used 16, another question , what will I do to the one file that was never deodexed? it is the playstationcertified.odex
Could not deodex the following (you can try to deodex these files again):
playstationcertified.odex
A summary of the deodexing has been logged in deodex_040813_020606.log
71 *.odex files remain in system/app
1 *.odex files remain in system/framework

Rycon33 said:
with regards to my sig banner, i got it from one of the post from G+ last time, here's a copy of the actual file -> https://dl.dropbox.com/u/28587036/Android/Android_Evolution.jpg
ok I used 16, another question , what will I do to the one file that was never deodexed? it is the playstationcertified.odex
Could not deodex the following (you can try to deodex these files again):
playstationcertified.odex
A summary of the deodexing has been logged in deodex_040813_020606.log
71 *.odex files remain in system/app
1 *.odex files remain in system/framework
Click to expand...
Click to collapse
I have always just left it in for my releases, but seeing as I dont use it, i have personally deleted both the file and the odex file.
I think its the same for all stock based roms...there will be some aditional sony security on that file as it enables you to download sony play station games so the kitchen is not set up to integrate the odex file into the original one.

gregbradley said:
I have always just left it in for my releases, but seeing as I dont use it, i have personally deleted both the file and the odex file.
I think its the same for all stock based roms...there will be some aditional sony security on that file as it enables you to download sony play station games so the kitchen is not set up to integrate the odex file into the original one.
Click to expand...
Click to collapse
oh ok.
mate, apologies for many questions, this is my first try so I'm still confuse of many things
so after I de-odexed, what's next?
> ADVANCED OPTIONS
11 - De-odex files in your ROM
12 - Tools for boot image (unpack/re-pack/etc.)
13 - Add /data/app functionality
14 - Add /etc/init.d scripts support (busybox run-parts)
15 - Unpack data.img
16 - Sign APK or ZIP file(s)
17 - Convert update-script or updater-script
18 - Plugin scripts
99 - Build ROM from working folder
0 - BACK TO MAIN MENU
basically I only want a deodexed ROM and the CWM and root retained

Rycon33 said:
oh ok.
mate, apologies for many questions, this is my first try so I'm still confuse of many things
so after I de-odexed, what's next?
> ADVANCED OPTIONS
11 - De-odex files in your ROM
12 - Tools for boot image (unpack/re-pack/etc.)
13 - Add /data/app functionality
14 - Add /etc/init.d scripts support (busybox run-parts)
15 - Unpack data.img
16 - Sign APK or ZIP file(s)
17 - Convert update-script or updater-script
18 - Plugin scripts
99 - Build ROM from working folder
0 - BACK TO MAIN MENU
basically I only want a deodexed ROM and the CWM and root retained
Click to expand...
Click to collapse
What do you want to do?
You cant do (12) use championshipswimmers kernel kitchen for that.
But i do suggest adding 14, and rooting it (thats in the main menu)
also, zipalign apks...but it will ask you to do that when you compile it
Other than that its up to you. Just try some different options out and see what you think...thats the best way to learn, if you see my releases, the first two versions were not released because I was learning and playing around with it
Make sure though that you dont use the updater script it produces, its wrong for our phones.
"Borrow" one from a working ROM in our dev section, just ask permission first.

Rycon33 said:
thanks mate, after I re-do the dump-data in flashtool, now system.img(renamed from system.ext4) can be detected
got another question again, just to confirm what's the API level? is it 16 for Android 4.1.2? coz I only see 4.1.1 for level 16
Click to expand...
Click to collapse
For android 4.1.2 api must be set @16 othervise it wont boot
Sent from my LT29i using xda app-developers app

gregbradley said:
What do you want to do?
You cant do (12) use championshipswimmers kernel kitchen for that.
But i do suggest adding 14, and rooting it (thats in the main menu)
also, zipalign apks...but it will ask you to do that when you compile it
Other than that its up to you. Just try some different options out and see what you think...thats the best way to learn, if you see my releases, the first two versions were not released because I was learning and playing around with it
Make sure though that you dont use the updater script it produces, its wrong for our phones.
"Borrow" one from a working ROM in our dev section, just ask permission first.
Click to expand...
Click to collapse
asterix005 said:
For android 4.1.2 api must be set @16 othervise it wont boot
Sent from my LT29i using xda app-developers app
Click to expand...
Click to collapse
ok mates, thank you very much, I managed to de-odexed my stock ROM:good:

This is what I did. Using flashtool, I dumped my system.sin file to get a ext4 file. Then I open it with ext4 reader and extracted the contents. I then placed it in a folder called 'system' and proceed with the android kitchen.
Humans have evolved to be smarter, but there's one thing we can't get rid off. It's human stupidity.

If you still want to deodex playstationcertified.odex rename it to com.playstation.playstationcertified.odex.
That did the trick for me in earlier firmware versions.
Sent from my phone using XDA Premium

i try many times but it's all show this
CREATE WORKING FOLDER FOR ROM
==============================
Ensure there is at least one ROM under the 'original_update' folder!
Select an option:
s - Show supported formats
x - Abort, don't create working folder
Or press Enter to continue
any idea or should i press enter to continue?
i try with system.img from xperia TX rom 1.67

lucky92 said:
i try many times but it's all show this
CREATE WORKING FOLDER FOR ROM
==============================
Ensure there is at least one ROM under the 'original_update' folder!
Select an option:
s - Show supported formats
x - Abort, don't create working folder
Or press Enter to continue
any idea or should i press enter to continue?
i try with system.img from xperia TX rom 1.67
Click to expand...
Click to collapse
why don't you press it an see?
anyway, have you used flashtool to extract the system.sin into an ext4 extension yet?

gregbradley said:
why don't you press it an see?
anyway, have you used flashtool to extract the system.sin into an ext4 extension yet?
Click to expand...
Click to collapse
i tried extract thee system.sin into ext4 and rename it to sysmtem.img but no luck
update: after re-dump system.sin and press countinue, it's seem ok, maybe my fault.
Thank you anyway :laugh:

Sorry but I have another question, after i make a flashable zip and flash through CWM, it always stuck at Sony logo, any idea ?

Help ! Need SemcCameraUI.apk for .108

Hey guys , i was trying to flash a camera mod , but i got a problem and every time i lunch it i have force close so please i need anyone to upload "SemcCameraUI.apk" From "system/priv-app" and another frile name is "media_profiles.xml" from System/etc
-Thanks in advance

Before you do that, have you tried clearing the data in
settings/apps
for ALL the camera apps

gregbradley said:
Before you do that, have you tried clearing the data in
settings/apps
for ALL the camera apps
Click to expand...
Click to collapse
yea i did but the same :|

well,
I am sure you can restore the backup you made before flashing something new..
In the mean time, which FW of the SemCamerisUI do you need, you can always download a FTF and extract it from that..by now you will have had it...

gregbradley said:
well,
I am sure you can restore the backup you made before flashing something new..
In the mean time, which FW of the SemCamerisUI do you need, you can always download a FTF and extract it from that..by now you will have had it...
Click to expand...
Click to collapse
i tried to extract from the ftf , but it didn't work the tool i have to extract files from .ext4 only for ICS/JB , i had searched on the internet for the for the KK but i didn't find .

m0urazz said:
i tried to extract from the ftf , but it didn't work the tool i have to extract files from .ext4 only for ICS/JB , i had searched on the internet for the for the KK but i didn't find .
Click to expand...
Click to collapse
If you're looking for that APK, try downloading [NUT]'s .108 flashable zip file from here. In this zip file there is a file called "system.tgz", extract it, then in "system.tgz" there is a file called "system.tar". Extract the "system.tar" file and you'll see the folder structure of your "/system" partition, including the "priv-app" folder which contains the APK you're looking for. Bare in mind that this APK is odexed, so you'll have to copy the .odex file as well.
If you need the de-odexed version of said APK, download the de-odex package instead and grab the APK from there.

thanks guys , fixed

[MOD][Z2] MM 575 Deodex Patch

Hello guys
Today i will be Sharing Deodex Patch for Official Android 6.0.1 (.575 build).
This ZIP Contains Deodex and Zipalign Patch For Stock Rom with Build no 23.5.A.0.575. .
REQUIREMENTS
Prerooted Stock MM Build no .575 With Recovery
INSTALL INSTRUCTIONS
Wipe cache and dalvik cache.
Flash Deodex ZIP followed by Fix zip in Recovery.
Reboot.
DOWNLOADS
Link: http://www.mediafire.com/download/lns07bainl8iaac/Deodex_Patch_575.zip
Fix: https://drive.google.com/file/d/0B_ACsHR2ThfsU1dTd0dpLUhJdWM/view?usp=drivesdk
CREDITS
@lord-ralf-adolf For His Awesome Lordroid One Batch Deodexer
@jitz975 and @Rajeev for Helping.

Thank you.
it isn't delete odex files in system/app, priv-app and framwork automatically but I delete them manually, work fine

Thanks brother! I will try and report...

yakuzainlove said:
Thank you.
it isn't delete odex files in system/app, priv-app and framwork automatically but I delete them manually, work fine
Click to expand...
Click to collapse
For me it worked bro, Yesterday i kept few odex files in system/app.... arm folder nd ran the delete.sh using terminal and the odex files got deleted so script was working.

Nice Hey man , this is like slim 570 deodexed but with bloat?

dex87xda said:
Nice Hey man , this is like slim 570 deodexed but with bloat?
Click to expand...
Click to collapse
Ur wlcm.
Its just a deodex patch which is to be flashed after flashing prerooted rom to deodex the system.

Nice

Hey how do i confirm that my System is deodexed after flashing this or not ?

chawlasrijan said:
Hey how do i confirm that my System is deodexed after flashing this or not ?
Click to expand...
Click to collapse
Just delete sqsh files from system and see if u can boot to system

dex87xda said:
Just delete sqsh files from system and see if u can boot to system
Click to expand...
Click to collapse
Umm, i cannot locate sqsh files anywhere in the systen !!
Can you pinpoint the exact location.

chawlasrijan said:
Hey how do i confirm that my System is deodexed after flashing this or not ?
Click to expand...
Click to collapse
Check for odex files in system/app or priv-app or framework. If they are not there then ur system is deodexed.

vikash1994b said:
Check for odex files in system/app or priv-app or framework. If they are not there then ur system is deodexed.
Click to expand...
Click to collapse
There are !!
So basically flashing this didn't help.
How do i proceed now ?

chawlasrijan said:
Umm, i cannot locate sqsh files anywhere in the systen !!
Can you pinpoint the exact location.
Click to expand...
Click to collapse
Sqhs files are present in root of ur system but since u have flashed the deodexed patch sqsh and other odex files r deleted thats why ur not able to locate

vikash1994b said:
Sqhs files are present in root of ur system but since u have flashed the deodexed patch sqsh and other odex files r deleted thats why ur not able to locate
Click to expand...
Click to collapse
Okay, but then i still have odex files present

chawlasrijan said:
Okay, but then i still have odex files present
Click to expand...
Click to collapse
Wait iwl tell how u can delete them manually.

your fw is deodexed

chawlasrijan said:
Okay, but then i still have odex files present
Click to expand...
Click to collapse
Do one thing extact delete.sh from zip nd run it via terminal emulator

vikash1994b said:
Do one thing extact delete.sh from zip nd run it via terminal emulator
Click to expand...
Click to collapse
Okay, extracted !
Now what command do I write in Terminal emulator.
Sorry I'm new to all this

chawlasrijan said:
Okay, extracted !
Now what command do I write in Terminal emulator.
Sorry I'm new to all this
Click to expand...
Click to collapse
No problem bro
First move delete.sh to sdcard Download terminal emulator from playstore then open it nd write following commands
Su
Sh sdcard/delete.sh
U may get some error ignore them and then check for odex files

vikash1994b said:
No problem bro
First move delete.sh to sdcard Download terminal emulator from playstore then open it nd write following commands
Su
Sh sdcard/delete.sh
U may get some error ignore them and then check for odex files
Click to expand...
Click to collapse
Okay, so i figured what i had to do, but using mine & your commands as well, I'm getting this same error
& odex files are still present

Need System Folder of latest firmware

hello! I had a request for anyone running stock odexed firmware (.291)
Can you pull the system folder for that version and upload it for me? Thanks!
Edit: with odex files pls!
P.s. I need the untouched version without root. Thanks!

HERE are stock ftf firmwares. Choose one and download it.
Rename *.ftf to *.zip and extract a file system.sin using 7zip.
Open Flashtool, use function "Sin Editor" to convert system.sin -> system.ext4. Then use this to "save" /system folder.
There are some files *.sqsh that contain .odex files. this sqsh file link to odex file of the app. Use 7zip 16.04 to extract *.sqsh file, you will see odex files
---------- Post added at 04:22 PM ---------- Previous post was at 04:17 PM ----------
Eg: odex.app.sqsh contains all odex of /app folder.
Extract sqsh file and copy odex file to folder (ex: copy AnonymousData.odex to /app/AnonymousData/oat/arm/, then you have stock AnonymousData apk with odex file . )

xtbtvd12399 said:
HERE are stock ftf firmwares. Choose one and download it.
Rename *.ftf to *.zip and extract a file system.sin using 7zip.
Open Flashtool, use function "Sin Editor" to convert system.sin -> system.ext4. Then use this to "save" /system folder.
There are some files *.sqsh that contain .odex files. this sqsh file link to odex file of the app. Use 7zip 16.04 to extract *.sqsh file, you will see odex files
---------- Post added at 04:22 PM ---------- Previous post was at 04:17 PM ---------
Eg: odex.app.sqsh contains all odex of /app folder.
Extract sqsh file and copy odex file to folder (ex: copy AnonymousData.odex to /app/AnonymousData/oat/, then you have stock AnonymousData apk with odex file . )
Click to expand...
Click to collapse
Thank you so much! I am learning to deodex my ROM myself.
I will try it this weekend.
But aren't the odex files generated when you run android the first time?
This is wierd
EDIT: I downloaded the ftf from flash
tool and expanded it. I do not see any files *.sqsh files in any folders . Just empty

panzerox123 said:
Thank you so much! I am learning to deodex my ROM myself.
I will try it this weekend.
But aren't the odex files generated when you run android the first time?
This is wierd
Click to expand...
Click to collapse
I dont know this much. But odex files arent generated in system partition. They create odex file in system partition for faster first time bootup maybe.
---------- Post added at 06:14 AM ---------- Previous post was at 06:12 AM ----------
panzerox123 said:
EDIT: I downloaded the ftf from flash
tool and expanded it. I do not see any files *.sqsh files in any folders . Just empty
Click to expand...
Click to collapse
You need to extract system.sin and convert to system.ext4 first . the sqsh file must be in system partition.

xtbtvd12399 said:
I dont know this much. But odex files arent generated in system partition. They create odex file in system partition for faster first time bootup maybe.
---------- Post added at 06:14 AM ---------- Previous post was at 06:12 AM ----------
You need to extract system.sin and convert to system.ext4 first . the sqsh file must be in system partition.
Click to expand...
Click to collapse
I've done that. The folders are empty...

panzerox123 said:
I've done that. The folders are empty...
Click to expand...
Click to collapse
ohh. something wrong here. i ll check it tonight.
normally, the odex.app.sqsh, odex.framework.sqsh, odex.priv-app.sqsh must be in system partition.

xtbtvd12399 said:
ohh. something wrong here. i ll check it tonight.
normally, the odex.app.sqsh, odex.framework.sqsh, odex.priv-app.sqsh must be in system partition.
Click to expand...
Click to collapse
There are efolders in the system partions with those names. But they are empty

panzerox123 said:
There are efolders in the system partions with those names. But they are empty
Click to expand...
Click to collapse
Yes. Those folders are empty, but those are sqsh files near those folders . Check it

xtbtvd12399 said:
Yes. Those folders are empty, but those are sqsh files near those folders . Check it
Click to expand...
Click to collapse
Ill check. But is there a *.sqsh for every apk?
And if not, if I extract the .sqsh file, will it give me the odex for every apk?
Thanks

panzerox123 said:
Ill check. But is there a *.sqsh for every apk?
And if not, if I extract the .sqsh file, will it give me the odex for every apk?
Thanks
Click to expand...
Click to collapse
Yes, they contain all odex files

xtbtvd12399 said:
Yes, they contain all odex files
Click to expand...
Click to collapse
Ok thanks. I'll try once i get home

I checked it already.
Hope this can help you .
If you want to fully deodex your system, there are 2 more sqsh files. /system/etc/product/ and /system/etc/customizations/.
and there are 2 more odexed app with odex file: /system/vendor/app/ims/ & /system/vendor/app/ChromeCustomizations/
-----------------
There are symlinks between /system/$app/*app_name*/oat/arm/ and odex.$apk.sqsh/arm/*app_name*.odex
So the odex file show in folder is a shortcut from sqsh file. Sony made this

xtbtvd12399 said:
I checked it already.
Hope this can help you .
If you want to fully deodex your system, there are 2 more sqsh files. /system/etc/product/ and /system/etc/customizations/.
and there are 2 more odexed app with odex file: /system/vendor/app/ims/ & /system/vendor/app/ChromeCustomizations/
Click to expand...
Click to collapse
Thanks:good: