Database Info

[MOD] Deodexed XXKB3 with VANILLA Lockscreen for I9003!

Based on I9003XXKB3 firmware, I made this mod also for our phone...
How to install:
- unpack the archive and copy the two folder to sdcard ( you must have /sdcard/done_app and /sdcard/done_frame)
- with you pc get an adb shell and type:
su
mount -o remount rw /system
rm /system/app/*.odex
cp /sdcard/done_app/* /system/app
rm /system/framework/*.odex
cp /sdcard/done_frame/* /system/framework
reboot
Important:The first time the phone maybe won't boot so: unplug the battery and restart...and be patient!
DOWNLOAD HERE
P.S.: for the people that don't like the deodexed app but that have the I9003XXKB3 firmware installed I post also an archive with two files. Simply overwrite the originals in /system/framework/ (also with root explorer)and reboot. The first time the phone maybe won't boot so: unplug the battery and restart...and be patient!
EDIT: The two files contain a mistake so i removed they... sorry.... only apply the first guide!
Let me know what you think.... bye

Ohhh... Basically its a deodexed apk and jar with a different lock screen. I too have deodexed my fw xxkb3. But for Lock screen you can get applications from market. No offence, I respect your work, its a good beginning. Sorry, but I thought initially its with vanilla kernel.
Sent from my GT-I9003 using XDA Premium App

Skin1980 said:
P.S.: for the people that don't like the deodexed app but that have the I9003XXKB3 firmware installed I post also an archive with two files. Simply overwrite the originals in /system/framework/ (also with root explorer)and reboot. The first time the phone maybe won't boot so: unplug the battery and restart...and be patient!
Let me know what you think.... bye
Click to expand...
Click to collapse
I've tried odexed android.policy and now I'm reflashing phone: It became always rebooting during the boot.

falex007 said:
I've tried odexed android.policy and now I'm reflashing phone: It became always rebooting during the boot.
Click to expand...
Click to collapse
You have a risk of boot loop with Framework related files if there is any incompatibility or improper file replacement. Any time you try such items be ready to reflash. What is your Firmware? Is it XXKB3? If yes then it should work as per Skin 1980, but it wont work on other firmware unlike system/app apks.

trip007in said:
You have a risk of boot loop with Framework related files if there is any incompatibility or improper file replacement. Any time you try such items be ready to reflash. What is your Firmware? Is it XXKB3? If yes then it should work as per Skin 1980, but it wont work on other firmware unlike system/app apks.
Click to expand...
Click to collapse
Yes. I have XXKB3. And I am not afraid to reflash I did this several times (first to upgrade from XXKB1, then to remove OCLFv1, and so on ) All my settings/applications are saved to Dropbox with help of Titanium backup

Nice work dude

Thanks a lot. Deodexed applications works well. Also I like standard lock screen
Please fix your instruction:
cp /sdcard/done_frame /system/framework
to
cp /sdcard/done_frame/* /system/framework
BTW After start it showed 318M of free memory, with standard fw I saw ~270M. But I thought that it should use more memory (not lesser). This is strange for me

falex007 said:
Thanks a lot. Deodexed applications works well. Also I like standard lock screen
Please fix your instruction:
cp /sdcard/done_frame /system/framework
to
cp /sdcard/done_frame/* /system/framework
BTW After start it showed 318M of free memory, with standard fw I saw ~270M. But I thought that it should use more memory (not lesser). This is strange for me
Click to expand...
Click to collapse
Thanks.... I have edited the post....

Can you upload to multiupload
megaupload block my area...

Dello i see from the snapshot that you are italian... It istituto true?you have problems with xx b3 deodexed or not ? How is gps working ?
Inviato dal mio GT-I9003 usando Tapatalk

Hi!
I am on ddkb2 and just want the lockscreen! What do i exactly have to do to just get the vanila lockscreen

Thanks dude, used your framework files for the vanilla lock. But why did you remove those framework.apk files? I noticed those missing files during flash and added my own deodexed apks. Worked great.
Sent from my GT-I9003 using XDA Premium App

I don't remove framework-res.apk.... simply it cannot be deodexed cause it doesn't have odex file.... correct me if i'm wrong
trip007in said:
Thanks dude, used your framework files for the vanilla lock. But why did you remove those framework.apk files? I noticed those missing files during flash and added my own deodexed apks. Worked great.
Sent from my GT-I9003 using XDA Premium App
Click to expand...
Click to collapse
Sent from my GT-I9003 using XDA App

Update to kb3, root your device and follow the guide on the first post... pm if you need help..... bye
ritvik93 said:
Hi!
I am on ddkb2 and just want the lockscreen! What do i exactly have to do to just get the vanila lockscreen
Click to expand...
Click to collapse
Sent from my GT-I9003 using XDA App

Who said no odex files dude? just check the stock firmware or ask someone who is running stock firmware to check in the /system/framework. There are 24 files after deodexing the framework folder, before deodexing you have 46 files. Attached screen shot here. I have highlighted the apk and corresponding odex files from framework folder.
Skin1980 said:
I don't remove framework-res.apk.... simply it cannot be deodexed cause it doesn't have odex file.... correct me if i'm wrong
Sent from my GT-I9003 using XDA App
Click to expand...
Click to collapse

Please.... check inside the related jar file on my deodexed file and you will find where the odex is....tell me if i'm wrong
Sent from my GT-I9003 using XDA App

Skin1980 said:
Please.... check inside the related jar file on my deodexed file and you will find where the odex is....tell me if i'm wrong
Sent from my GT-I9003 using XDA App
Click to expand...
Click to collapse
No dear, I am talking about the two apk files in framework folder which are not included in the jar folder. framework-res.apk and twframework-res.apk are the two files. If you are using the application Deodexer_2_3 for deodexing framework files, it creates two folders one for jar files as deodex_jar and another for apk files as framework. Just check in the that folder you will find them.
When I transferred those deodexed files to /system/framework from downloaded files uploaded by you. I used an adb command
Code:
rm /system/framework/*.odex
. This means my system will never reboot without those odex files of above mentioned apks, if did not replace them with deodexed ones. Hope I am clear now. If you guys check in your framework folder you will find two odex files which you have not replaced. Please dont take is as an offense, I love your work.

What i wrote in the first post is what i've done on my phone that works correctly.... sure that the files i attached are not all the files that must be in the system and framework folders.... this because it's simply an "update" to stock rom.
Another thing... no problem with you my friend... we are working all for the same result...
P.s.: framework-res.apk and the other cannot be deodexed i supposed cause the related odex files will be put by the deodex-software into the related .jar files.... check into your framework-res.apk .
Sent from my GT-I9003 using XDA App

No dear, I am sorry to say but you are wrong here. every .apk and jar has their own odex files so the odex resides inside the respective apk or jar file that it belongs to after deodexing them. If you want I can attach those two deodexed framework apk files, which should go into /system/framework folder along with remaining jar files, (without their odex files). Will post tomorrow morning here you may link them to the main post, if you feel so. If I do something, I am never satisfied by incomplete job.
Skin1980 said:
What i wrote in the first post is what i've done on my phone that works correctly.... sure that the files i attached are not all the files that must be in the system and framework folders.... this because it's simply an "update" to stock rom.
Another thing... no problem with you my friend... we are working all for the same result...
P.s.: framework-res.apk and the other cannot be deodexed i supposed cause the related odex files will be put by the deodex-software into the related .jar files.... check into your framework-res.apk .
Sent from my GT-I9003 using XDA App
Click to expand...
Click to collapse

trip007in said:
No dear, I am sorry to say but you are wrong here. every .apk and jar has their own odex files so the odex resides inside the respective apk or jar file that it belongs to after deodexing them. If you want I can attach those two deodexed framework apk files, which should go into /system/framework folder along with remaining jar files, (without their odex files). Will post tomorrow morning here you may link them to the main post, if you feel so. If I do something, I am never satisfied by incomplete job.
Click to expand...
Click to collapse
Maybe i don't explain myself very well... tomorrow i will try to explain better what i'm saying... see you!
Sent from my GT-I9003 using Tapatalk

How to re-odex?

Normally to decompile my dex files I use smali and baksmali, how can I re-odex them?
Id like to get my service.jar re-odexed so I can try and push it to my phone via a zip update.
Sent from my MB865 using xda premium

[mini HOW-TO] Re-Odex (or create a new .odex file)
Fall of Enosis said:
Normally to decompile my dex files I use smali and baksmali, how can I re-odex them?
Id like to get my service.jar re-odexed so I can try and push it to my phone via a zip update.
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
It all needs to be done on your phone, live.. with adb.
Here's how I accomplished it - I will use the services.jar in this example. Just change the file name and path to existing .odex accordingly for other files (not sure if all steps are required exactly, but it has worked for me multiple times with different jars and SysUI apk):
Requirements:
Odexed system
adb
dexopt-wrapper
Put this dexopt-wrapper file (unzip first) in /system/bin with 775 permissions:
X X X
X....X
X....X
Probably a good idea to reboot after pushing that file, if you use root explorer (like I did).
Put the deodexed services.jar (or other jar/apk file you want to make an new odex of) on your sd card.
Go to /system folder (with root explorer or equal) and mount it R/W (not sure if this is necessary - but won't hurt)
Put your USB connection to "Charge only" mode.
Go here (big props and credit to jhotmann for this) and follow steps 8-12 (I've recreated the steps with the A2's bootclasspath below).
The bootclass path is located in the /init.rc file at the root of your phone.
Connect with adb (do a adb devices check to make sure you're all good).
To create the new odex:
Code:
adb shell
su
cd /sdcard/
dexopt-wrapper services.jar new.odex /system/framework/core.jar:/system/framework/bouncycastle.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/android.policy.jar:/system/framework/services.jar:/system/framework/core-junit.jar:/system/framework/com.motorola.android.frameworks.jar:/system/framework/com.motorola.android.widget.jar
I know it's a long entry for those who don't work with command lines often (like me), but double check your entry before hitting enter.
To copy the signature from the existing odex (change path to /system/app/.. if necessary):
Code:
busybox dd if=/system/framework/services.odex of=new.odex bs=1 count=20 skip=52 seek=52 conv=notrunc
Done! Rename new.odex (created on your /sdcard) to services.odex since that is your new signed odex file...
You can then get that on your odexed system by your choice of method (adb push, update.zip, root explorer push, etc.. - note: please know what you are doing before trying to push files with root explorer! - you cannot simply copy and paste!)
Or, if you want to deodex it right away again for some odd reason like I did (personal issues )... Take the services.jar and the new services.odex from your sdcard and put them on your computer - and open the services.jar with 7-zip (maybe winzip) and delete the classes.dex file from the 7-zip window. Now you have a fresh new set of .jar/.odex files ready for deodexing (I did this all with the SystemUI.apk last night, that's why I elaborated and re-typed this whole thing today..).

Frigging brilliant man.
Much appreciated. I'm super sick and my USB cable is at work.
Once i get it back on Wednesday, I'll work all this out. If I could thank you twice I would.
Thanks man!
Sent from my MB865 using xda premium

Fall of Enosis said:
Frigging brilliant man.
Much appreciated. I'm super sick and my USB cable is at work.
Once i get it back on Wednesday, I'll work all this out. If I could thank you twice I would.
Thanks man!
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
Not a prob.
And, I updated the dexopt-wrapper link so it's easier to download - just unzip it first..
Good luck on your quest.. let me know if you catch any snags along the way - and i'll try and help you out.
Sent from my mind using XDA

Ok sooo, I think we (or most likely me) are confused on what I wanted to do. I don't want to make a NEW odex file. I need to recombine my modded classes.dex BACK with the service.jar.
Since I needed to modify some script in the services.jar I had to de-odex it so I had a classes.dex file to use baksmali with so I could modify it. Once I modded it I used smali to create the NEW MODDED classes.dex. And now I need to re-odex(bad terminology?) them to re-combine the services.jar with the classes.dex so the modded services.jar could be used on a odexed ROM.
I'm working on a de-odexed version also, but I'd like to be able to offer both

Fall of Enosis said:
Ok sooo, I think we (or most likely me) are confused on what I wanted to do. I don't want to make a NEW odex file. I need to recombine my modded classes.dex BACK with the service.jar.
Since I needed to modify some script in the services.jar I had to de-odex it so I had a classes.dex file to use baksmali with so I could modify it. Once I modded it I used smali to create the NEW MODDED classes.dex. And now I need to re-odex(bad terminology?) them to re-combine the services.jar with the classes.dex so the modded services.jar could be used on a odexed ROM.
I'm working on a de-odexed version also, but I'd like to be able to offer both
Click to expand...
Click to collapse
So, you have a deodexed services.jar (with an unedited classes.dex inside)? And, you also have an edited classes.dex (the new modded one). Just drag and drop the new modded classes.dex into the services.jar file with 7-zip to overwrite the old one.
Then I would check out the mods on a deodexed system, and provided they work, then go through the re-odexing process (separating that classes.dex from the apk and creating a new odex file) as described above to get it working on odexed systems.
Hope that helps.. Good luck!

Yes sir, you are correct. That was the first thing I tried to do was just drag and drop the modded classes.dex with 7zip, save it, however when i tried to flash the "modded" ROM it can't install the system folder because (according to Jim), when I modded copied the new classes.dex, I changed the size, and so the signature needed to be changed as well. They mismatched.

Fall of Enosis said:
Yes sir, you are correct. That was the first thing I tried to do was just drag and drop the modded classes.dex with 7zip, save it, however when i tried to flash the "modded" ROM it can't install the system folder because (according to Jim), when I modded copied the new classes.dex, I changed the size, and so the signature needed to be changed as well. They mismatched.
Click to expand...
Click to collapse
Not sure about the details of that.. I know the signatures can be tricky, but I've modded a few apks/jars similarly with no problems... when you say "can't install.." is that it wouldn't flash in recovery, or you bootlooped?

Just wouldn't flash at all.
And thanks for all your help man.
Sent from my MB865 using xda premium

I've updated the 2nd post with more detail on creating a new odex file...
Not to be a "rooster" (replace with your word of choice) or anything, but maybe this info has a place somewhere besides the general threads..?:angel: (and what is up with these new Smilies and posting reply layout?) - it just seems so hard to come by good literature on this process (which, I suppose, is a process so rarely needed though...)

So I need to perform the processes above while running in an odexed environment correct? Does this process change the deodexed APK we are running the script on to an odexed one as well as create a new .odex file for that APK? I am just confused about what the result is after running the script. For my situation I want to take 2 deodexed files (systemui and sec settings.apk) and odex them. Then push them into an odexed rom. Once I run the script above what am I left with?

Didact74 said:
So I need to perform the processes above while running in an odexed environment correct?
YES.
Does this process change the deodexed APK we are running the script on to an odexed one as well as create a new .odex file for that APK?
(Yes, it will create a new odex file that you will need to rename, but..)NO. You will need to take the classes.dex out of the deodexed apk/jar - use something like 7-zip. Unless you only edited smali, then you really only need the new odex file.
I am just confused about what the result is after running the script. For my situation I want to take 2 deodexed files (systemui and sec settings.apk) and odex them. Then push them into an odexed rom. Once I run the script above what am I left with?
Click to expand...
Click to collapse
I broke up your quote with my best answers...
As for what your're left with is a new.odex file, properly signed, if all goes well. You are going to need to do it for each of your deodexed files.
Rename them, remove the classes.dex from the deodexed files you used, and get them on your phone however you choose (I prefer zip packages and a restore.zip in case something goes wrong).
Also note that the bootclass path is different from GB to ICS.. and among different devices of course. Check init.rc file if need be. I posted the one to use for A2 ICS (think it may be the same for razr too) here: http://forum.xda-developers.com/showthread.php?t=1753659
I can't garuntee you won't have problems, but good luck... if you do you could try the dexopt-wrapper from here: http://forum.xda-developers.com/showthread.php?t=1645950 - just unzip it first obviously (but I think it's the exact same file though..)
Btw, it's all done with adb, one line at a time.. not really a script, but thank you for the idea - maybe a batch file?
Sent from my phone's mind

Great, thank you for the detailed response. Last question.
What if I have the original SystenUI.odex and SecSettings.odex files that used to be attributed to them before i deodexed them? Can I simply reuse those without having to run through the adb process?
Thanks,

Didact74 said:
Great, thank you for the detailed response. Last question.
What if I have the original SystenUI.odex and SecSettings.odex files that used to be attributed to them before i deodexed them? Can I simply reuse those without having to run through the adb process?
Thanks,
Click to expand...
Click to collapse
But, you deodexed them to edit the smali files in the classes.dex right? So, no, you will need to use the new odex files that are created from the modded deodexed files you used..
If you never edited any of the smali files, then you didn't need to deodex in the first place... you only need to deodex in order to mod the smali files - everything else in the apk can be modded as is on odexed systems.
Sent from my phone's mind

Thank you very much. Can you repost the wrapper file? Its not downloading correctly.

Didact74 said:
Thank you very much. Can you repost the wrapper file? Its not downloading correctly.
Click to expand...
Click to collapse
Updated the link in Post #2 with a zip file - you need to unzip it first then move it.

Thank you.
So I am getting an error trying to re-odex. See the attached image of the error.
Weird thing is that even though I get an error it still creates the new.odex file. I triedto go through the entire process even though I was getting errors and it just got stuck on the boot screen and never loaded. Anything in my error attached raise any flags?
Thanks,

Didact74 said:
Thank you.
So I am getting an error trying to re-odex. See the attached image of the error.
Weird thing is that even though I get an error it still creates the new.odex file. I triedto go through the entire process even though I was getting errors and it just got stuck on the boot screen and never loaded. Anything in my error attached raise any flags?
Thanks,
Click to expand...
Click to collapse
Hmmm... First thing I can think of is: are all of those framework files in the bootclass path that you used actually in your /framework folder? With our A2, in ICS there are a few extra .jar files listed that were not actually on our phone, so I had to remove those from the path...
I will try to make a new odex myself and make sure that's not a standard error message... @Fall of Enosis, you recall what it spits out?
EDIT: Shoot - forgot I'm deodexed right now... will attempt later or hear back from Fall by then..

alteredlikeness said:
Hmmm... First thing I can think of is: are all of those framework files in the bootclass path that you used actually in your /framework folder? With our A2, in ICS there are a few extra .jar files listed that were not actually on our phone, so I had to remove those from the path...
I will try to make a new odex myself and make sure that's not a standard error message... @Fall of Enosis, you recall what it spits out?
EDIT: Shoot - forgot I'm deodexed right now... will attempt later or hear back from Fall by then..
Click to expand...
Click to collapse
Yes, all .jar files listed in my bootclass were located in the framework directory.

Nevermind...my mistake. I had an issue with my files not being deodexed correctly from the start. I went back and deodexed, made the edits to res and smali then odexed using the method above again and all went well!
Thanks!

[Guide]Create Custom ROMs | Modify Apks

Hello xda.
This is a Guide to help anyone who wishes to create custom ROMs. This Guide aims to be as complete as possible, and will give all information related to creating a custom ROM... editing apks, adding or removing apps, de-odexing apps, and so on.
Al suggestions to improve upon this guide are welcome.
0. Pre-requisites
Click to expand...
Click to collapse
Credits to...
1. puppet13th... My mentor, teacher, and a great friend.
2. Wanman... ApkTool for ICS
3. langthang... For a great Guide on Creating Update Script
4. lokeshsaini94... For lots of help
Downloads
You need to Download the following...
1. Apk Tool [link(ICS)|link(GB)]... A tool for De-Compiling apks
2. 7 zip [link]... A tool for un-compressing any sort of compressed file
3. ROM signer [link]... Restores the signing of the ROM zip file, which is messed up while uncompressing
4. Any Image Resizer​
Setting up your PC
You need to do the following...
1. Create a folder (preferably in Desktop, and name it "Android")
2. Create Sub-Folders by the names "Base ROM" and "Custom ROM". Also make Sub Folders by the name...
a. ApkTool... Extract contents of ApkTool Here
b. Signer... Extract Autosigner here​
I. Let's get our Base ROM
Click to expand...
Click to collapse
You need to get the base ROM in the ./Desktop/Base ROM folder. It is also recommended that you flash the Base ROM into your phone, as it will help in testing the mods, as you make them.
The process of getting the base ROM will depend on the scenario your situation fits in, from amongst the following...
1. You want an already made Custom ROM as your Base... Download the ROM [willl come in .zip folder], and extract it in /Desktop/Android/Base ROM folder
2. You want to base your ROM on a stock firmware, which came in an ftf package... Use the following tool to extract the files from the ftf file.
3. You want to base your ROM on a stock firmware, which is instaled on your phone...
Take a back up of the ROM using ClockWork Mod, and copy the back up files (from /sdcard/clockworkmod/backup), somewhere to your computer. Then, using this tool, extract the files to /Destktop/Android/Base ROM
Copy the following folders from /system of your phone using Root Browser
/app
/bin
/etc
/fonts
/framework
/lib
/media
/semc
/usr
/xbin
build.prop​
4. You want to base your ROM on a stock firmware, that comes as a ready to flash .zip file on the internet... Download the ROM, and extract it in /Desktop/Android/Base ROM folder
After completion, the Base ROM will have the following Folder Structure
Desktop
Android
Base ROM
META-INF [only if you got your base from another Custom ROM][/INDENT][/INDENT][/INDENT]
system
apps
bin
etc
.
.
.
data [may be]
Click to expand...
Click to collapse
*ScreenShots*
Copy the contents of Base ROM folder to Custom ROM folder.
We now have the foundation of our ROM laid out in front of us, inviting us to show our creativity.
II. Let's work on the Base ROM... Creation of the Custom ROM
Click to expand...
Click to collapse
A. Apks Make up the Android System...
We will now work, only on the /Desktop/Android/Custom ROM Folder
1. Look into the /system/apps...
You will find apk files which will be raninging frm 100 to 200 in number. Err, half or more are known as "Crapware". You need to remove files which are useless, that's a very important step to enhance performance of your final ROM. Look into your device's forums, to get the list of Safe-To-Remove appks from the respective firmware. In case your base is an already built custom ROM, you will have to remove lesser or none of the files.
2. Here, you can add your desired files as well, keeping compaitability in mind.
3 [Optional]. On a .txt file, keep a record of all the apps your removed or added, as it will help in troubleshooting at a later stage.​
B. Implementing Already-Built-MODs in your ROM...
1. Download any Mod you want to keep in your ROM [Make sure your device, and the Base ROM is compaitable]
2. Extract the zip file and you will get a system folder.
3. Copy the files from the system folder to /Custom ROM/sytem, making sure the files go into the folders they came from.
That is, all apk files from /system/apps folder of the Mod should go to /Custom ROM/system/app folder, and so on...​
C. Changing the Interface... Let's Mess with SystemUI[nterface].apk
Go to /system/app and copy SystemUI.apk to
/Desktop/Android/ApkTool/place-apk-here-for-modding
Working with ApkTool
The link provided in this post is of an easy to use software called ApkTool.
1. Double Click on the Script.bat file to open up the software.
*Screenshot*
2. Decompress the SystemUI.apk using option '9'.
Wait for the process to complete
3. Go to /Projects, and you will find a folder called SystemUI.
Open the /SystemUI.apk/res/drawable folders and you will find lots and lots of .png files
*Screenshot*
4. Look into the files carfully.
Bingo, they correspond to the various system elements of the SystemUI of the Base ROM.
5. Open any file you want to edit, edit it, and save in the original location, replacing the original un-edited file. [On a temporary notepad file, note which all files you edit]
Note: You will notce that there are .png files for, say the Battery Icon. You will find that there are files for each state of the Battery Icon. So if you intend to edit the Battery Icon, you need to edit all the files corresonding to each of the states.
5.A. A common exaple of such editing is making the elements of a Gingerbread SystemUI.apk look like ICS SystemUI.apk. For this get hands on any ICS SystemUI.apk and extract both the files in seprate locations, and then copy the files from the ICS SystemUI folder to GB SystemUI folder. However, here you must make sure that the names of the files coming from ICS SystemUI are changed to corresponding values of the GingerBread SystemUI.apk. Here, also ensure that the new files, which replace the original files, have the same dimensions as the original files. If not use any image resizing tool.
*Screenshot*
6. If you want to edit some values in the .xml files, carry on. Edit the files as you wish, and replace the original files. Once you are done with the editing...
7. Open the Script.bat file and run command 11. [Say NO when it asks if the file is a system file]You will have a new SystemUI.apk file called unsignedSystemUI.apk in /place-apk-here-for-modding folder.
Go and fill your pockets with some cookies from the kitchen. Start having them.
8. Keep the temporary notepad file on one side and open the unsignedSystemUI.apk with 7zip, and open the original SystemUI.apk using 7zip besides it.
*Screenshot*
9. Drag and extract the files you edited to a temporary folder.
10. Drag the extracted files to the SystemUI.apk, replacing the older files, making sure all the edited files go to the proper place. [That's why I asked to keep a note of which all files were edited].
*Screenshot*
11. If you edited some .xml files, then you MIGHT need to copy the resources.acrc file at the root of the unsignedSystemUI.apk file to the root of the original SystemUI.apk file.
Once done, the original SystemUI.apk has now become a modded SystemUI.apk, with your creativity embedded into it. Time to test the SystemUI.apk.
12. Using Quick ADB, push the edited SystemUI.apk to your phone.
*Screenshot*
13. Re-boot your phone and you shoud see the changes you made in the UI. .
In case it gives force close message, you messed up somewhere. So you will have to push the original SystemUI.apk [from /Base ROM/system/apps folder], and try to mod the file from scratch again.
14. Copy the sucessfully modded SystemUI.apk from /Apktool/place-apk-here-for-modding folder to /Custom ROM/system/app folder, replacing the older file.​
D. Changing the Interface... Editing other .apks
1. As earlier, copy the apk you want to edit from /Custom ROM/System/app to /Apktool/**** folder, and perform the modification to optain a new modded .apk file.
2. Test this file if you wish, by pushing it using Qucik ADB.
3. If the modded file wrks, copy this new file to /Custom ROM/System/app and replace the original file​
E. Changing the Interface... Editing the font
1. Take your desired font.ttf file and rename it as DroidSans.ttf..
2. Go to the folder system/fonts/
3. Now, replace the file DroidSans.ttf with your desired DoridSans.ttf...
4. To change the lock screen clock font...replace the Clocktopia.ttf with your desired one (rename first)...​
If you did a good job in the above steps, the /Custom ROM folder should be having the contents of a wonderful ROM in making.
Here, I will like to mention that, if you want to upload your custom ROM on the internet and share it, you must ensure that you did lots of hard work in the above steps. There's no point making a custom ROM without modifying lots of files and adding lots of tweaks.
Just make sure that you do so much of modding that, say, your Gingerbread ROM looks like Jellybean, or say, your ROM made for Galaxy Y works as smooth as an SIII.
III. Compiling the Custom ROM
Click to expand...
Click to collapse
A. If you got your base ROM as in [1 or 4] in step I above
1. Copy the META-INF folder from /Base ROM to /Desktop/Android/Custom ROM
2. Rename the Custom ROM folder to whatever-you-want-your-ROM-to-be-called.
3. Add the Folder to a zip file using 7zip.
4. Take this zip file to /Desktop/Android/Signer folder and run sign.bat.​
X. The new zip file called Update.zip is your ROM.
Copy this file to the SD Card of your phone, format /system, /data, /cache using CWM and flash your .zip file. And enjoy your custom ROM.
B. If you got your base ROM as in [2 or 3] in step I above... Creating your own Update script
Read the following Tutorial. [link]
Once you are done, try the ROM on your phone. Share it if you feel it's great. And hit Thanks Button.

Reserved

Reserved2

nice guide!

thanks for the tutorial.

Nice guide, continue finish it.:good:

Awesome
Adds some more tutorial please:thumbup:
Thanks for your work
Inviato dal mio GT-N7000 con Tapatalk 2

Please also add link to original thread....
Btw .. Nice guide....
In 1. Looking into system apps... you should delete .apk as well as .odex files when you want to remove an app... Like browser.apk and browser.odex... Many peoples won't delete them....
Sent from my GT-S7500 using xda premium

Thanks for this nice guide. :highfive:
Please add the placeholder *Screenshot* s :good:

beautiful
Thanks a lot for this beautiful guide. Loved it

i tried it ............
i followed the guide n tried editin my custom rom technoduos on sgy duos GT-s6102
all i did was extract the rom using CWM and then added removed some apps at /system/apps
no other tweaks just addin n removin apps dats all then compressed it n signed it
then wen i flashed it on my set it worked (yayyyyyyy)
but there were some problems the apps which i del were gone but the ones i added were not there ..........
also wen i flashed the rom again the apps which were del were back how is it possible i made sure i had del em
plz help

thank you very much for your tutorials are very helpful to me

nice guide! thx

Nice Guide...
Thanks for the hard work to track down all this information and publish for us.
Thanks

Thanks... im gonna give this a whirl
Sent from my SGH-T999 using Tapatalk 2

R: [Guide]Create Custom ROMs | Modify Apks
Very useful giude thanks ; )
Inviato dal mio GT-N7100 con Tapatalk 2

:Good:
Sent from my potato oO

thanks

Need some help regarding Odex Files and corresponding apks

Hi guys, I got this problem in my odexed stock rom, I have this problem in sysui, gallery and calculator.
I downloaded 4.2.2 style sysUI, pushed it in the respective folder by replacing with its stock sysUI.
I rebooted my core, the statusbar was gone, so I deleted 'SystemUI.odex" file, then rebooted it worked!
In the same way, I replaced stock gallery with note3 gallery, and stock SecCalculator2
Luckily note3 gallery worked, but it doesn't support Sim2 so I can't change Sim2's wallpaper or make it same as Sim1's.
In the statusbar, I can't see most notification cuz its completely transparent, and also its a bit laggy.
Calculator never worked
So I wanted to replace these with stock, when I pushed it in system>apps> I noticed that there were no .odex files for .apks
I replaced them with their stock odex files, none of 'em worked, I guess cuz of the odex thing, so I again deleted odex files and rebooted, nothing worked..
Now, I need some developer's advice, plz don't tell me to "Flash Stock Rom via Odin" I can't do it...
Is there any other left way to make them work plz I need help..

You are saying 'in my deodexed rom' and then you said 'deleted. Odex file for systemUI'
How could this be possible?
If you have .Odex files in system/apps folder then your ROM is not odexed.
Deodex it first using xUltimate tool
And yup Don't forget to set permissions = rw--r--r--

M_E_G_A_T_R_O_N said:
You are saying 'in my deodexed rom' and then you said 'deleted. Odex file for systemUI'
How could this be possible?
If you have .Odex files in system/apps folder then your ROM is not odexed.
Deodex it first using xUltimate tool
And yup Don't forget to set permissions = rw--r--r--
Click to expand...
Click to collapse
Sorry bro, huge typo. I meant in my odex rom and yes I set the proper permissions...

Well, it seems to me that you have messed up your phone alot.. Flashing stock rom via odin would've been the correct solution to this problem. It's not as difficult as you think, and you're capable of doing it. Follow thecoreguy's tutorial for that.

CoreGuy said:
Sorry bro, huge typo. I meant in my odex rom and yes I set the proper permissions...
Click to expand...
Click to collapse
Then you have done wrong.
Not every apk can be used by just deleting the .odex file.
You need to deodex the apps in system/app and system/framework folder then you can easily replace the apks.
1.First restore back to any working backup.
2.Download xUltimate Tool.
3. Run it.
4. Then just run commands with options 1,2,3,4 (You just need to type 1 and then enter, then 2 and then enter, so on upto option 4.)
5. Exit after executing 4th option.
6. Download ADB tool(don't download the complete package, you will get a 1-2MB ADB.exe from the from itself) - Use it to push the deodexed files made from xultimate.
---------- Post added at 09:47 AM ---------- Previous post was at 09:22 AM ----------
If you find it difficult then Better you upload the apks with their respective odex file. I will deodex those apks

M_E_G_A_T_R_O_N said:
Not every apk can be used by just deleting the .odex file.
Click to expand...
Click to collapse
Not even the stock apks? I want to replace the ported/modded apks with the stock ones..

No you can't because almost all stock apks have their respective odex files and every odex file contains resources that are needed to run those apks. Also there exists dependencies in system/framework folder. So just deleting odex file won't work all time.

Finally got it! Special thanks to megatron
Solution if u r screwed in my situation: don't panic, what I found why I cant do it was bcuz my phone has dat "newest" update of samsung ota. So b4 u take someone's apk and odex file always cross check this(image)
And then you are gud to go!!! U wont even need to restart it'll come automatically(my dad has same phone and same updated version as mine so I copied everything needed frm his phone to mine) @AnsleyC at times, the answer should not be "flash stock rom via ODIN" if u have a crappy pc, u can either repair faulty parts(easier and efficient) or buy a new one(bullcrap)
Have fun everyone!
Sent from my GT-I8262 using XDA Premium 4 mobile app

[SOLVED]deodex zip D6603_Customized US_1288-7827_23.4.A.1.232_R6C

Wondering if anybody around here has some experience on using SVADeodexerForArt?
Trying to deodex D6603_Customized US_1288-7827_23.4.A.1.232_R6C and from what I gathered this is the tool to use, but been bouncing from thread to thread trying to understand how to make use of it and the more I read the more confusing it has become and I'm still at square one...
Anybody willing to shade to light and give direction on how to proceed?
Thanks

-Deodex-
Ok, so after a few days of reading I figured how to deodex my rom, took the long way since I didn't have the rom on my phone, just started from the xperifirm file...
Want to give a big THANKS @serajr for answering my questions and letting me use his zip to add my files for flashing!
This deodex zip is only for the D6603_Customized US_1288-7827_23.4.A.1.232_R6C firmware with root and recovery so be sure you're on that exact firmware before flashing!
-BACK UP before you even think of flashing this-
there is no debloat in the zip , you'll end up with a full stock D6603_Customized US_1288-7827_23.4.A.1.232_R6C deodexed, rooted and dualrecovery firmware
just flash the zip through recovery, wipe cache and dalvik and then boot...
get the deodex zip to flash here

-DM- said:
Ok, so after a few days of reading I figured how to deodex my rom, took the long way since I didn't have the rom on my phone, just started from the xperifirm file...
Want to give a big THANKS @serajr for answering my questions and letting me use his zip to add my files for flashing!
This deodex zip is only for the D6603_Customized US_1288-7827_23.4.A.1.232_R6C firmware with root and recovery so be sure you're on that exact firmware before flashing!
-BACK UP before you even think of flashing this-
there is no debloat in the zip , you'll end up with a full stock D6603_Customized US_1288-7827_23.4.A.1.232_R6C deodexed, rooted and dualrecovery firmware
just flash the zip through recovery, wipe cache and dalvik and then boot...
get the deodex zip to flash here
Click to expand...
Click to collapse
Hello there,
Can you please share how you did that? I am not able to find any way.
I wanna deodex D6653 firmware 23.4.A.1.232 Customized IN
I have .ftf, PRF Creator and SVA Deodexer
Thanks in advance

Mohitash said:
Hello there,
Can you please share how you did that? I am not able to find any way.
I wanna deodex D6653 firmware 23.4.A.1.232 Customized IN
I have .ftf, PRF Creator and SVA Deodexer
Thanks in advance
Click to expand...
Click to collapse
First make sure that you have the firmware you want to deodex, rooted with recovery and installed on your phone already so in your case D6653 firmware 23.4.A.1.232 Customized IN , if not then create a prerooted zip with that ftf file, SuperSu and latest dual recovery with PRFcreator then flash it and boot....Once that exact firmware is on your phone, you can follow those steps below to create a deodex zip.
Here is the process:
-download the zip that I provided in this thread (you'll need it later to swap my files with yours)
-open the ftf with 7-Zip to copy the system.sin file
-then use Flashtool Sin Editor to extract data to get System.ext4
-from there, use ext2explore (download it here) to open the system.ext4
-Once you opened system.ext4, locate those 3 folders (app, framework and priv-app) and build.prop
-create a folder called deodex on your C drive (so C:\deodex) and copy those 3 folders mentioned above and the build.prop file to it
-then move SemcGenericUxpRes folder from framework folder to app folder and take the 2 containing folders from vendor\app and move them to the app folder as well
- then run SVADeoderForArt.exe and selected the path to C:\deodex folder, check deodexing framework, app and private-app, let the tool run (it should tell you if it ran without errors when done)
-now you should have app, dex, framework, odex and priv-app folders (inside the SVADeodexerforart folder) after the tools finished the deodexing process (you can delete the dex and odex as they're not needed anymore)...now move SemcGenericUxpRes folder back to framework folder...also move back the 2 folders that you took from vendor\app, just put them anywhere on your desktop you're going to need them in a minute
-now when you open the deodex zip that you first downloaded, go into the system folder and you'll see 4 folders, app, framework, priv-app and vendor....delete the 3 folders app (but before, move the supersu folder from my app folder to your app folder, otherwise you'll end up without supersu) , framework and priv-app folders and move your 3 corresponding folders in there...now open vendor\app and delete the 2 folders and put yours instead
-your deodex zip should be good to flash now, put it on your sdcard...reboot to recovery, choose your zip to flash , then clear cache and dalvik cache and then boot....now you should have a full stock deodexed D6653 firmware 23.4.A.1.232 Customized IN (if you want to debloat, remove what you don't want from the app and private app folder in the zip before flashing, but you're on your own for that)
And as always make a backup before you start all this
Also, you should thank @serajr, as he's the one that wrote the script to clean and replace the system odexed folders, he nicely let me use it as a base to make my changes

-DM- said:
First make sure that you have the firmware you want to deodex rooted with recovery installed on your phone..............Also, you should thank @serajr, as he's the one that wrote the script to clean and replace the system odexed folders, he nicely let me use it as a base to make my changes
Click to expand...
Click to collapse
Thanks a lot for taking your time to write this and to give me good guide. This will help others too.
Ok i will follow the guide and now i am good to go. In case, any help needed, i will post here
And i think you saying to download your deodexed.zip only for meta inf and SuperSU, so i am not going to download that because i can do it myself so why to download ~800mb zip
And ya, Big thanks to @serajr. I dont know where to post exactly. So i am thanking you @serajr here.
Thanks and Regards
Mohitash

Mohitash said:
And i think you saying to download your deodexed.zip only for meta inf and SuperSU, so i am not going to download that because i can do it myself so why to download ~800mb zip
Thanks and Regards
Mohitash
Click to expand...
Click to collapse
yes, but looks like that you know what you're doing so you should be good to go

-DM- said:
yes, but looks like that you know what you're doing so you should be good to go
Click to expand...
Click to collapse
Ya, you got me right. May be you checked my profile or you can check now my history on XDA
I am just very very new to Sony and lollipop
Sent you pm.....
Regards
Mohitash

-DM- said:
First make sure that you have the firmware you want to deodex, rooted with recovery and installed on your phone already so in your case D6653 firmware 23.4.A.1.232 Customized IN , if not then create a prerooted zip with that ftf file, SuperSu and latest dual recovery with PRFcreator then flash it and boot....Once that exact firmware is on your phone, you can follow those steps below to create a deodex zip.
Here is the process:
-download the zip that I provided in this thread (you'll need it later to swap my files with yours)
-open the ftf with 7-Zip to copy the system.sin file
-then use Flashtool Sin Editor to extract data to get System.ext4
-from there, use ext2explore (download it here) to open the system.ext4
-Once you opened system.ext4, locate those 3 folders (app, framework and priv-app) and build.prop
-create a folder called deodex on your C drive (so C:\deodex) and copy those 3 folders mentioned above and the build.prop file to it
-then move SemcGenericUxpRes folder from framework folder to app folder and take the 2 containing folders from vendor\app and move them to the app folder as well
- then run SVADeoderForArt.exe and selected the path to C:\deodex folder, check deodexing framework, app and private-app, let the tool run (it should tell you if it ran without errors when done)
-now you should have app, dex, framework, odex and priv-app folders (inside the SVADeodexerforart folder) after the tools finished the deodexing process (you can delete the dex and odex as they're not needed anymore)...now move SemcGenericUxpRes folder back to framework folder...also move back the 2 folders that you took from vendor\app, just put them anywhere on your desktop you're going to need them in a minute
-now when you open the deodex zip that you first downloaded, go into the system folder and you'll see 4 folders, app, framework, priv-app and vendor....delete the 3 folders app (but before, move the supersu folder from my app folder to your app folder, otherwise you'll end up without supersu) , framework and priv-app folders and move your 3 corresponding folders in there...now open vendor\app and delete the 2 folders and put yours instead
-your deodex zip should be good to flash now, put it on your sdcard...reboot to recovery, choose your zip to flash , then clear cache and dalvik cache and then boot....now you should have a full stock deodexed D6653 firmware 23.4.A.1.232 Customized IN (if you want to debloat, remove what you don't want from the app and private app folder in the zip before flashing, but you're on your own for that)
And as always make a backup before you start all this
Also, you should thank @serajr, as he's the one that wrote the script to clean and replace the system odexed folders, he nicely let me use it as a base to make my changes
Click to expand...
Click to collapse
I understand the problem but somehow I do follow instructions whose results have been bootloop

đạt gao ô said:
I understand the problem but somehow I do follow instructions whose results have been bootloop
Click to expand...
Click to collapse
Sent you a pm