Hi,
After flashing a custom rom I noticed that rom didn't have my language, so I wanted to add it to this custom rom.
After a great and long journey and thx to the info found on this forum I managed to add the language I wanted.
During the journey I started to write a small tool to make the whole process a bit less painful. The tool has been growing from as simple batch decomiple - recompile apk tool to 1 that adds the value folders and do the resources.arsc switch thing.
This is my 1ste release and is still a beta version so still has some errors, stuff to be added and bad code. But still I hope some of you can use it.
If you got any questions just post or pm
Greetings
Installing the tool.
Just extract all files to your root folder and run the ignite script as root. That's it.
There is a help option that guide you step by step.
EDIT: Small adjustment in the language lists and added the Custom_language_list option
EDIT: Like I said tool is still in beta stage, it seems that yesterday in my hurry to get it ready I screwed up big time (like command to make a cp without telling where to copy to) anyway already beta version 1.1 is out now
UPDATE: 1ste real release out now.
Killed some more bugs
Updated the help page
Added some layout editing
Added or updated the log handeling
how can i insert pt language on last jaggyrom for htc explorer ?
I would appreciate if u created a 'How To' for Super Noobs like me ...
a windows version
If there is a windows version,it will be more appreciated.
bascro said:
I would appreciate if u created a 'How To' for Super Noobs like me ...
Click to expand...
Click to collapse
There is a help function in the tool that guide through most of the steps from the moment you got your hands on tha apk files.
So now the question is how to get those apk files.
Well I like to use Android-Kitchen to unpack rom's, and you'll need that tool anyway to add the new apk files to the rom.
1. Decompile the rom containing the language you want. (Can be stock-rom, your original rom, other custom,...)
2. Copy all the apk files from the systeml/app folder to the stock_APK.
3.Copy the framework-res.apk and com.htc.resources.apk from the system/framework folder to flare/framework and the stock_APK folders
The rest of the how you'll find when you start APK-Fire and use option 'h'
Note: Not all of the apk file will decompile without errors, those that give errors (like market, street, superuser,...) you don't realy need to add language so just delete those apk's from the stock_APK and the decompiled_APK folders.
pedrofidalgo said:
how can i insert pt language on last jaggyrom for htc explorer ?
Click to expand...
Click to collapse
To add portugees you can choose to add all the languages from the South_West_Europe list.
or
you put pt and pt-rPT (each on a diff line) to the Custom_language_list.
then follow the steps you'll find in help option.
picodaren said:
If there is a windows version,it will be more appreciated.
Click to expand...
Click to collapse
There is a windows version called APK Edit
Only prob here is that you have to open the apk that has the wanted language, copy those folders, open the apk from the rom where you want to add the language to and repeat this process for all the apk files 1 by 1.
If you take this road plz let me know how long it took yah
i have jaggy rom. and a backup of my stock rom in Portuguese. can i install pt language on jaggy rom ?
Need a little help .. : p
pedrofidalgo said:
i have jaggy rom. and a backup of my stock rom in Portuguese. can i install pt language on jaggy rom ?
Need a little help .. : p
Click to expand...
Click to collapse
sure you can.
Step trough:
1 Set-up Android-kitchen
2 Decompile your stock rom
3 copy the content of the system/apk folder to the APK-Fire/stock_APK
4 copy the 2 apk files from system/framework to APK-Fire/stock_APK AND APK-Fire/flare/framework
5 Start APK-Fire and install the frameworks (option 1)
6 Decompile the apk files (option 2)
7 Add the language code to the Custom_language_list each language code get's it's own line. (you find this file in the APK-Fire/lighter folder) for portugees you add something like this:
pt
pt-rPT
8 Get the value folders containing the portugees language (option 4)
9 Now you can choose to back up the stock_apk and the decompiled_apk folders (option 6 / 1) or delete the content of those 2 folders.
10 Got back to the kitchen and decompile the Jaggyrom and repeat the steps 2 till 6 as before.
11 Now copy the value folders you took from the stock rom to the jaggyrom (option 5)
12 Recompile the apk files (option 3)
(check log for errors, warnings you could ignore but errors need attention, be aware that non stock apps mostly will give errors but those also don't need additional language)
13 Do the resources.arsc switch thing to fool the signature security (option 6)
(for more info what this is all about read the switch_resources script)
14 Copy your upgraded apk files from the APK-Fire/firebox/translated_APK folder to the Android-kitchen/WORKING_****/system/app (don't forget to copy the 2 framework apk files to the Android-kitchen/WORKING_****/system/framework folder and not the app folder)
15 Cook your rom
16 Flash the rom
17 Hold your fingers crossed while booting
18 Hopely enjoy the costum rom in your desired language.
Hope this helps you.
Cosmoon said:
sure you can.
Step trough:
1 Set-up Android-kitchen
2 Decompile your stock rom
3 copy the content of the system/apk folder to the APK-Fire/stock_APK
4 copy the 2 apk files from system/framework to APK-Fire/stock_APK AND APK-Fire/flare/framework
5 Start APK-Fire and install the frameworks (option 1)
6 Decompile the apk files (option 2)
7 Add the language code to the Custom_language_list each language code get's it's own line. (you find this file in the APK-Fire/lighter folder) for portugees you add something like this:
pt
pt-rPT
8 Get the value folders containing the portugees language (option 4)
9 Now you can choose to back up the stock_apk and the decompiled_apk folders (option 6 / 1) or delete the content of those 2 folders.
10 Got back to the kitchen and decompile the Jaggyrom and repeat the steps 2 till 6 as before.
11 Now copy the value folders you took from the stock rom to the jaggyrom (option 5)
12 Recompile the apk files (option 3)
(check log for errors, warnings you could ignore but errors need attention, be aware that non stock apps mostly will give errors but those also don't need additional language)
13 Do the resources.arsc switch thing to fool the signature security (option 6)
(for more info what this is all about read the switch_resources script)
14 Copy your upgraded apk files from the APK-Fire/firebox/translated_APK folder to the Android-kitchen/WORKING_****/system/app (don't forget to copy the 2 framework apk files to the Android-kitchen/WORKING_****/system/framework folder and not the app folder)
15 Cook your rom
16 Flash the rom
17 Hold your fingers crossed while booting
18 Hopely enjoy the costum rom in your desired language.
Hope this helps you.
Click to expand...
Click to collapse
i dont know how to do it :/
if i give you my backup can you add pt language for the last jaggyrom ?
cumps
really??
I've already robbed the experience from you of wandering through the jungle of this mystic entity called Android by making the wandering seem nothing more then a walk through the park.
And now you tell me you don't want to know this mystic entity?
Nah I don't buy that, you almost got me there.
I'm willing to guide you through every step but I refuse to carry you.
If you'r on IRC or msn or I can meet you there to start your journey.
Btw at the current rate Jaggyjags is spitting out rom's I can't keep up adding stuff for everyone so I go by the rule:
You translate 1 version of a rom for a man and you made him happy till the release of the next version. You teach a man how to translate a rom and you made him happy for many versions
pedrofidalgo said:
i dont know how to do it :/
if i give you my backup can you add pt language for the last jaggyrom ?
cumps
Click to expand...
Click to collapse
seriously, I know you like your phone and want get the best out of it but your maximum effort is installing .zip roms or .zip updates?
you've got 2 options.
1. Stick with whatever you have right now: your Portuguese backup or any available custom rom.
2. research, research again, try things out and learn. Try to stop asking people to do things for you. It's difficult, I know, specially when you are used to it, but don´t worry, it always is.
Believe me, it is a really nice feeling when you get things done on your own.
good luck
Would you teach us HOT TO DO IT MANUALLY (without using APK Fire)
pmeler said:
Would you teach us HOT TO DO IT MANUALLY (without using APK Fire)
Click to expand...
Click to collapse
Well.... all right then
I've explained most of how to add language already, k most of it in close relation with the use of APK-Fire. Anyway I'll try to explain the whole process starting from the base rom till the modified one.
Step 1
Check if your (custom) rom really really doesn't have your language. Try also 'morelocal' app. This simple step can save you lot's of time
Step 2
Now that you't sure that the (custom) rom doesn't have your language or you just want to add more languages to the rom you build your self you have to go and look for roms that do have the language(s) your want to add.
Possible finding places:
- different versions of the leaked stock rom
- Others people custom rom's
- Rom's for other devices. ! Won't work for the 2 framework apk files, but has good chances to work with the other apk files !
Step 3
Question now probably is how can I find out what languages a rom contains (specialy those for other devices). Well easy, you just have to dismantle the rom's and to be sure a few apk files.
The easyest way to dismantle a rom is to use Android-Kitchen. This tool doesn't need alot of installing or modification but I do recommend you read the how to etc.
So now you have easy access to all the content files of the rom.
Take a few apk files from the system/app folder and dismantle them with 'Apk Tool' or if you realy want to go hardcore 'aapt'. And check the 'app-name'/res for 'values-*' folders that you need.
Step 4
Now that you've found the folders containing the translation (those values-* folders) you've got to copy them to to 'app-name'/res of the afk file from the rom you want to add language to.
dismantled app from copy value folders dismantled app from
rom with language -----------------> rom without language
Step 5
recompile the dismantled app where you just added the value folders to
Step 6
You thought you where allmost done didn't you??? Now the real fun part just starts.
In order to bypass the security that check for the integity of the apk file we need to cheat abit.
You need the new apk file and the original apk (the one without the language)
*rename the 'app-name'.apk file (from both version) to 'app-name'.zip
*delete the resources.arsc file from the original 'app-name'.apk (now temporaly 'app-name'.zip)
*take that same file from the new apk file and copy it to the original apk
* rename the original back from 'app-name'.zip to 'app-name'.apk
* Copy that apk file back into the rom (Android-Kitchen remember)
Step7
Now you repeat this proces for ALL apk files you find in the rom.
Yup all +100 apk files from 1 rom + the same +100 apk files from the other rom need to get this treatment.
Step 8
Cook rom
So you see 8 simple step is more or less what it takes.
Same tutorial but better here
Even more resources here and here
Updated the tool
Cosmoon said:
Updated the tool
Click to expand...
Click to collapse
It doesn't seem to do the last step for me. The one that is supposed to copy the resources.arsc. It just creates another copy of the stock, without the new resources.arsc.
Any idea of what's going on? Would be a flavor to not have to do this manually!
Hmm I fully tested the latest update with the 2 rframework apk files and everything worked fine.
Are you sure that it's just a copy of the stock apk folder?
The switch_resources script does all the final steps. renaming, delete file from stock, copy from new to stock and rename back.
As I still have to add loggin to this part you should see an output on screen showing what the script is/was doing.
While that part is running you should see a folder called 'temp' (inside firebox or 1 of the subfolders of firebox).
Inside the firebox/recompiled_APK you should find a folder for each app containing the resources.arsc file.
And as last check you can compair the size of the 3 diff apk files. (stock, recompiled and translated). If I'm not mistaken the translated is the smallest (how strange it may sound)
Also make sure the tool is in your root folder.
If possible send me the output you get during this fase.
Cosmoon said:
Hmm I fully tested the latest update with the 2 rframework apk files and everything worked fine.
Are you sure that it's just a copy of the stock apk folder?
The switch_resources script does all the final steps. renaming, delete file from stock, copy from new to stock and rename back.
As I still have to add loggin to this part you should see an output on screen showing what the script is/was doing.
While that part is running you should see a folder called 'temp' (inside firebox or 1 of the subfolders of firebox).
Inside the firebox/recompiled_APK you should find a folder for each app containing the resources.arsc file.
And as last check you can compair the size of the 3 diff apk files. (stock, recompiled and translated). If I'm not mistaken the translated is the smallest (how strange it may sound)
Also make sure the tool is in your root folder.
If possible send me the output you get during this fase.
Click to expand...
Click to collapse
They are identical, not even smaller so Although i was running this in cygwin on windows so it might be that. I'll try to boot it up in ubuntu to see if it's any difference Could be the su that's messing with me in cygwin :S
leolulz said:
They are identical, not even smaller so Although i was running this in cygwin on windows so it might be that. I'll try to boot it up in ubuntu to see if it's any difference Could be the su that's messing with me in cygwin :S
Click to expand...
Click to collapse
Never tried it on windows with cygwin, I'm running a debian linux, so that could be the thing that's messing it up.
Still good to know that only that part doesn't work on windows, I'll see if I can modify the script.
THANK YOU Cosmoon !
I asked because I want to remove unsued language from framework-res.apk to make it slimmer
Cosmoon said:
Never tried it on windows with cygwin, I'm running a debian linux, so that could be the thing that's messing it up.
Still good to know that only that part doesn't work on windows, I'll see if I can modify the script.
Click to expand...
Click to collapse
Ye, but it could work although, i never checked the su/root stuff, kinda rushed it yesterday to see how it worked Anyways it's a nice script and ill love to see this project getting further
pmeler said:
THANK YOU Cosmoon !
I asked because I want to remove unsued language from framework-res.apk to make it slimmer
Click to expand...
Click to collapse
Hmm never thought about that. Only thinking of adding stuff but having a option to remove can be handy to.
I'll add it in the next update.
Thx great idea man
Related
Once again let me preface this by saying that I am a Noob. However, I have been swapping roms for the past couple of months with no major problems. The one annoyance is every time I install a new rom I have to go through the hassle of reloading all my favorite apps.
I wanted to know how to make a update.zip folder that will actually load on my Google Ion for my apps. Any help would be greatly appreciated.
If you know how to sign a ROM its no Problem, if you dont ...
Lol, that would be a big "No."
You would have to be able to sign .zip files for it to work, You could have your favorite apps on the side so you could open your rom on the computer and add them in the apps folder.
Your prolly better off installing them individually because some roms (mostly skins) wont run with some apps although this is VERY rare!
is it not possible to resign i.e. the cyanogen rom after adding a few apps?
frleus said:
is it not possible to resign i.e. the cyanogen rom after adding a few apps?
Click to expand...
Click to collapse
I am new to the signing of roms but from what i can see it is possible and seems to be a little easier than I originally thought. I just started with signing last night and was able to take parts of three different roms put them together and was able to sign it and sucessfully loaded and installed with no problems to my mytouch. Just to give an example I used the bootscreen from Qteks rom along with the transparent lockscreen from evils sense rom and combined them with wikeds rom cause I liked his icon pack. signed it and loaded on first shot with no issues.
Here is what I used posted by Dave Da illest 1 Senior Member
link to op
http://forum.xda-developers.com/showthread.php?t=471586
How To Theme Develop for Windows For Dummies in 10 easy steps (( no your really not a dummy its just an easy name for a how to lol))
well i'm going to give this a shot in the dark on how to create this how to be as easy as possible
1st
download these files if you don't already have them
JAVA
http://java.sun.com/javase/downloads/index.jsp
download the JDK
Winrar
http://rarlabs.com/rar/wrar380.exe
and Auto-sign.zip
http://www.mediafire.com/download.php?uwzjjydnm2r
2nd
Download my included Auto-sign files.
what it contains.
the Test keys file..
and an update.zip file
and a batch file i created called auto-sign to make things easier to sign
3rd
after you have downloaded my Auto-sign
then you extract it to where ever you want.
4th.
use the update.zip included if your a Beginner it includes my windows 7 theme .. i edit so many files that it's easier to tell what does what and whats goiing to go where. now open that zip file DON'T EXTRACT just open it using winrar..
5th
When it is open go to Framework.. and open Framework-res.apk
NOW IF THE APK. POPS UP AND SAYS IT CANT OPEN BLAH BLAH SELECT A PROGRAM AND THEN SELECT WINRAR.
6th
Once you open Framework-res.apk KEEP THIS WINDOW AND UPDATE.ZIP WINDOW OPEN!!
then just extract the whole Res Folder to where ever you like this makes it easier to see what files you wish to edit.. most of the files will be in the folder called Drawable
7th
open up your favorite photo editor .. i use photoshop along with 90% of the people who Graphic Design... Edit your pictures Remember a file with a .9 can mess up your phone so edit those carefully.. and save what ever pictures you have
8th
Now drag the whole Res Folder .. back into the Framework-res.apk
now your update.zip file is going to say files has been changed to framework-res blah blah do you wish to save it . click yes .. now your framework has been updated you can close everything out
9th
go to the Auto-sign folder.. and open Auto-sign this will now sign your update.zip .. and rename it to update_sign.zip .. now just delete your old update.zip.. rename update_signed.zip to update.zip
10th
put it on the root of your memory card.. reset using green call + menu + end
then hold home and end .. until the recovery mode shows up .. then press Alt+S and hope your device isn't bricked
Disclaimers
I'm not responsible if your brick your device.. but i will help to the best of my abilty and if i can't help i'm sure XDA will
i don't sign every file in my update.zip i just sign update.zip .. and hey it works lol..
For ADP or RC 8 versions .. just download your favortie ADP theme or RC 8
put it in the Auto-sign folder.. and rename it to update.zip if it isn't already then just follow my steps
thelastgoodbrother said:
Once again let me preface this by saying that I am a Noob. However, I have been swapping roms for the past couple of months with no major problems. The one annoyance is every time I install a new rom I have to go through the hassle of reloading all my favorite apps.
I wanted to know how to make a update.zip folder that will actually load on my Google Ion for my apps. Any help would be greatly appreciated.
Click to expand...
Click to collapse
the easy way
what i do is a .bat file with my info in it
place all the stuff you want installed into a folder
and create ad .bat file(notepad save as select all files from dropdown the put .bat on end of file name\)
mine is all.bat and inside looks like this
adb remount
adb push D:\android\install\apns-conf.xml /system/etc
adb push D:\android\install\wpa_supplicant.conf /data/misc/wifi
adb install D:\android\install\apps\android.tether.apk
adb install D:\android\install\apps\com.a0soft.gphone.aTrackDog.apk
adb install D:\android\install\apps\org.freecoder.widgets.overclock.apk
adb install D:\android\install\apps\com.metago.astro.apk
adb install D:\android\install\apps\com.qype.radar.apk
adb install D:\android\install\apps\com.arron.taskManager.apk
adb install D:\android\install\apps\com.rerware.android.MyBackupPro.apk
adb install D:\android\install\apps\com.curvefish.widgets.silentmodeonoff.apk
adb install D:\android\install\apps\com.mattwach.trap2.apk
adb install D:\android\install\apps\com.tapjoy.coloroid.apk
adb install D:\android\install\apps\com.schwimmer.android.mmsextract.apk
adb install D:\android\install\apps\com.google.android.stardroid.apk
adb install D:\android\install\apps\de.android_telefonie.appmanager.apk
adb install D:\android\install\apps\MyBackupPro.apk
adb shell
reboot
and i do it when the setup wizard starts so when it reboots my apn and wireless are installed
here is the one twisted made... its simple and eazy... btw when I was getting sick of restoring all my apps every time I flashed a new rom, I searched for it and learned how to do it without posting once... but thats just me
download incremental here
http://twistedumbrella.slackdev.com/Incremental.zip
Back your apps up as an update in case you do a wipe using this:
Use Incremental_original.zip
Back all the apps up you want.
Open the archive and replace the apps in the data/app directory.
Sign the archive like a regular update and place in root of SD card.
Flash the update you want. When finished, flash Incremental.zip
Reboot the phone and both the update and apps will be installed.
to learn how to sign files look at this thread...
http://forum.xda-developers.com/showthread.php?p=4721739
You can avoid the hassle easily by going apps to sd. After that, any rom that enables apps to sd (almost every rom) will automatically have your apps installed upon first boot.
That being said, next time post in "General" first. We don't want this section to get as messed up as it has become in the Dream forum.
Buster3616 said:
That being said, next time post in "General" first. We don't want this section to get as messed up as it has become in the Dream forum.
Click to expand...
Click to collapse
lol have you noticed this forum? i guess better late than never...
as every other post says "this should be in general" or "this should be in Q&A"
but then again I cant say Ive ever seen a clean forum... sad
Also if your gonna say "this should be [where ever]" you shouldn't also provide an answer to the initial question... What does that teach? Post where ever you want because you'll still get an answer? That doesn't help your cause.
This is a very basic guide to beginning themeing. It is not meant to be all-inclusive, just some simple steps that can be taken to make your own custom theme fairly easily. This guide should allow anyone to be able to grab images they like from any ROM and incorporate them into their own.
I SUGGEST YOU ALWAYS MAKE A BACKUP OF ANY FILE BEFORE YOU THEME IT AND NANDROID FIRST BEFORE FLASHING
Here is a basic overview of changing images in an apk:
1. Get your base file to theme – framework-res.apk, com.htc.resources.apk, phone.apk ect.
2. “Open” apk archive with 7-zip (don’t unzip!) and drag and drop the new images into the appropriate folder.
3. Flash new file.
Now some details:
1. The first step is to obtain the file you are going to theme. The file you are themeing ( i.e. going to flash to your phone) must come from the ROM you are currently running. Always use files from your current ROM as a base, however the images you want to change can come from other ROMs, or you can edit existing ones or make your own from scratch. You can obtain your theme base through an ADB pull of the files from your phone, or simply downloading the ROM zip file and extracting the files you need.
2. Now that you have the file to theme, don’t touch it! OK, more specifically, you won’t unzip or do anything to this file except “open” it with 7-zip (unless this is a market app, but more on that later). You are going to drag and drop the new icons into this file by “opening” it and navigating to the appropriate folder. The images you want to change are stored in the apk under /res/drawable-hdpi. Once you have your new icons from other sources, open your base file and navigate to this folder and drop them in.
3. Now you can flash this new file. I have provided empty zip files that you can place your themed files into and flash in recovery. Place your framework-res.apk and/or com.htc.resources.apk into the /system/framework folder located in the zip file provided. Now highlight the META-INF and system folders and zip them up. You can now place this file on the root of your SD card and flash. System apps can be placed under /system/app in the zip file.
Some more info on common themeable files:
Framework-res.apk – this is the meat and potatoes of a theme. On an AOSP ROM it will contain almost everything you want to theme aside from individual apps themselves. Sense ROMs have another file com.htc.resources.apk, as well as framework-res.apk. Both of these files are located in a ROM under /system/framework.
System apps: These apps come packaged in a ROM under /system/apps. They can be themed in the same manner as a framework apk. Some of these apps include Gmail, browser, camera, ect. Place them in your flashable zip under the folder /system/app.
Market apps: These apps are downloaded from the market and are can be pulled from your phone from /data/app. These files require a bit more to theme. They don’t share the same signature as the system apps and you must resign them using a program such as apkmanger. Place them in your flashable zip under /data/app.
If there are any errors, or if anyone has suggestions please let me know. I may have over looked some details, ect.
Thanks to everyone on XDA who has shared their knowledge and made this a great community!
Thanks that will be helpful
Sent from my PC36100 using XDA App
so using this guide we can pull parts and what not from other elements of themes we like and create our own framework to push back? Also, based on what you have, shouldn't it be easy to put this up on bid for hire (?) website to create a program to automate that?
xlGmanlx said:
so using this guide we can pull parts and what not from other elements of themes we like and create our own framework to push back? Also, based on what you have, shouldn't it be easy to put this up on bid for hire (?) website to create a program to automate that?
Click to expand...
Click to collapse
Yes the idea of this guide was to help people pick and choose icons they like in other ROMs and add it to their own. I'm not sure what bid for hire is?
its a website where you can load your requirements and folks can bid to do your work
linky
nukedukem said:
Yes the idea of this guide was to help people pick and choose icons they like in other ROMs and add it to their own. I'm not sure what bid for hire is?
Click to expand...
Click to collapse
xlGmanlx said:
its a website where you can load your requirements and folks can bid to do your work
linky
Click to expand...
Click to collapse
Interesting. Didn't know anything like this existed.
Sent from my EVO (CM6.1) using XDA App
Thank you, thank you!!!! I've been looking for something like this for a while.
evolishesh said:
Thank you, thank you!!!! I've been looking for something like this for a while.
Click to expand...
Click to collapse
No prob. Let me know if it works for you.
I couldn't get the auto signing to work, but the manual way of doing it worked.
Hmm, I got a boot loop on first try and doing this. Does that mean something went wrong with the signing, or that what I created for the theme was wrong? I used the empty .zip folder and re-zipped it, so I don't think that is the issue.
JasonK75 said:
Hmm, I got a boot loop on first try and doing this. Does that mean something went wrong with the signing, or that what I created for the theme was wrong? I used the empty .zip folder and re-zipped it, so I don't think that is the issue.
Click to expand...
Click to collapse
The signing should be ok. If you are using Amon_ra recovery it wont let you flash an unsigned zip I believe. Are you on sense or AOSP? Are you editing images or just copying from other ROMs?
What you might want to do is just create a simple test file. Change just one image and then flash that. That should let you know that your process is correct.
I using Amon Ra and using AOSP. I was moving some items out of a sense ROM so I guess that is where I might have went wrong. I think I'll take your advice and move just a single image and see how that works for me. Thanks!
I tried again this time I ended up stuck at the EVO white screen. I'm guessing it doesn't like the sense part I'm trying to throw in there. I'll have to try again with a AOSP theme instead.
Sent from my EVO (CM6.1.1) using XDA App
A couple things to look out for when swapping sense/CM icons - some file names are slightly different between sense and AOSP. Rename any sense icons to their AOSP counterparts and vice versa. Also, double check the image size of the icon is the same in both, i.e. 70x70 pixels, ect. and make sure you are not adding images that don't exist normally in the framework. For example there wont be any 4G icons in CM framework.
Also, make sure you aren't unzipping the new framework-res.apk you want to theme and flash, or trying to resign it. Only sign the flashable zip, not the individual files inside. The only thing you want to do with the framework-res.apk you will package and flash is open (not unzip) with 7-zip and navigate to the res/drawable-hdpi folder so you can drag and drop the new icons into it, overwriting the old.
I hope that helps!
How important is it to re-sign? I have modified the Framework and Resources apks with 7zip by switching images out. I have also modified the Rosie.apk. I put everything back where it was supposed to go, backed out of 7-zip and flashed. I have never had an issue with it, nor have I re-signed it. Just wondering.
spence341 said:
How important is it to re-sign? I have modified the Framework and Resources apks with 7zip by switching images out. I have also modified the Rosie.apk. I put everything back where it was supposed to go, backed out of 7-zip and flashed. I have never had an issue with it, nor have I re-signed it. Just wondering.
Click to expand...
Click to collapse
AFAIK if you are on clockwork recovery, I don't think it checks for signatures. I think Amon_ra requires a signed file to flash. I think it's just added protection against flashing any old junk. If you can flash in amon_ra without a signature and you don't have problems then I wouldn't worry about it. It's the signature of the framework-res.apk ( or com.htc.resources.apk) that's important. That's why you don't unzip it.
I think that
1.7.0.2 = yes
1.8 = no
nukedukem said:
AFAIK if you are on clockwork recovery, I don't think it checks for signatures. I think Amon_ra requires a signed file to flash. I think it's just added protection against flashing any old junk. If you can flash in amon_ra without a signature and you don't have problems then I wouldn't worry about it. It's the signature of the framework-res.apk ( or com.htc.resources.apk) that's important. That's why you don't unzip it.
Click to expand...
Click to collapse
nukedukem said:
A couple things to look out for when swapping sense/CM icons - some file names are slightly different between sense and AOSP. Rename any sense icons to their AOSP counterparts and vice versa. Also, double check the image size of the icon is the same in both, i.e. 70x70 pixels, ect. and make sure you are not adding images that don't exist normally in the framework. For example there wont be any 4G icons in CM framework.
Also, make sure you aren't unzipping the new framework-res.apk you want to theme and flash, or trying to resign it. Only sign the flashable zip, not the individual files inside. The only thing you want to do with the framework-res.apk you will package and flash is open (not unzip) with 7-zip and navigate to the res/drawable-hdpi folder so you can drag and drop the new icons into it, overwriting the old.
I hope that helps!
Click to expand...
Click to collapse
Thanks, any advice does help.
I did make sure the the icons I was swapping out were named the same thing in the CM ROM, but I didn't check the size of it at all.
I didn't unzip the famework-res.apk but instead just went into it with 7-Zip and dragged the icons into that. Then I backed out of 7-Zip so that it would save and close everything properly - know that does work because that is how I add the Fold transistions to the ROM - and then I put the famework-res.apk into the folder and zip it up per your instructions above. Then I manually sign it (still haven't been able to get the auto-signing to work) and then flash.
I'll have to try again moving a CM theme to the CM framework-res.apk and see if it is working. What I was attempting to do was take, from the Batman Theme for sense, the drop down notification shade with the Bat Icon and put it into the CM ROM. I don't know if you have time to try it yourself to see if it works, or if you get the same issues that I had.
Either way, thanks for the help! I know I'll get this theming down at some point!
nukedukem said:
No prob. Let me know if it works for you.
Click to expand...
Click to collapse
Hey buddy.
I’m stuck. I had to download and install Eclipse with the sdk plus java. I don’t know where to go from there. Every time I open the rom that I want to theme and get the framework.apk and edit the PNG’s , how do I go about saving them? Do I just used the same name as the old ones or I have to save them with a new name.
Or pm Me.
xlGmanlx said:
I think that
1.7.0.2 = yes
1.8 = no
Click to expand...
Click to collapse
So the new amon_ra doesn't require a signed file to flash? I'll make a note off that. Thanks.
JasonK75 said:
Thanks, any advice does help.
I did make sure the the icons I was swapping out were named the same thing in the CM ROM, but I didn't check the size of it at all.
I didn't unzip the famework-res.apk but instead just went into it with 7-Zip and dragged the icons into that. Then I backed out of 7-Zip so that it would save and close everything properly - know that does work because that is how I add the Fold transistions to the ROM - and then I put the famework-res.apk into the folder and zip it up per your instructions above. Then I manually sign it (still haven't been able to get the auto-signing to work) and then flash.
I'll have to try again moving a CM theme to the CM framework-res.apk and see if it is working. What I was attempting to do was take, from the Batman Theme for sense, the drop down notification shade with the Bat Icon and put it into the CM ROM. I don't know if you have time to try it yourself to see if it works, or if you get the same issues that I had.
Either way, thanks for the help! I know I'll get this theming down at some point!
Click to expand...
Click to collapse
OK I'll try and do what you are trying to do and see if it works...
evolishesh said:
Hey buddy.
I’m stuck. I had to download and install Eclipse with the sdk plus java. I don’t know where to go from there. Every time I open the rom that I want to theme and get the framework.apk and edit the PNG’s , how do I go about saving them? Do I just used the same name as the old ones or I have to save them with a new name.
Or pm Me.
Click to expand...
Click to collapse
So now you have an unzipped framewor-res.apk with a bunch of images. This framework should be the one that you want to take icons from. If not, start over with the ROM you want to copy images from. You will want to copy the images you want to put into another ROM so that you can dump them into the new framework-res.apk. After you figure out what icons you want to bring to your new framework, get a clean version of framework/com.htc from the ROM you are actually running - i.e. if you are running myn ROM on your phone, download the myn ROM and pull out the framework-res.apk or com.resources.apk that you are going to theme.
Now with this fresh clean framework you will "open" it with 7-zip to navigate to the /res/drawable-hdpi folder so you can now drag and drop the images you want to copy over into it. Then the close the 7zip window and your framework-res.apk is all set to flash. You don't need to rename if the file names are the same, you can just drag and drop and the files will be overwritten in the new framework.
AutoMod BETA 1.6 by MAD Industries
-----------------------------------------------------------------------------------------------------------------------------------
First off, this is not another APK Manager, this is also not Auto APK Tool. These two tools focus on the decompiling and recompiling of APK and jar files. AutoMod intends to bring a new paradigm to modding. That is, there are mods and there are roms. AutoMod makes them friendly with eachother. APKs are handled internally by the script.
I wrote this tool because as a developer who was using APK Manager, I ran into several obstacles along the way. One of them was that I liked to be able to take requests from users and personalize the mod to their tastes. Unless I was impeccable with my folder organization, it very quickly got out of hand with people asking for personalizations based on other personalizations. I would find myself decompiling a version I made the day before so I could remember what was in it and create yet another version on top of it. All this back and forth and I would end up with a mess of recompiled, decompiled, original, custom, extracted, etc files all over the place taking unnecessary HD space. On top of that, every step of the way required user input in the form of a yes/no prompt or selected a menu option for decompiling/recompiling/keep folders/signing/etc. And then I would manually create a flashable zip file for each version. AutoMod solves many of this issues in it's current BETA state. When it is finished, it will have solved all of them.
Features for End-Users:
Mods are dynamically applied to your ROM (this allows mods to stay up-to-date with the ROM without original developer support)
Mods often work across multiple similar ROMs (easy porting)
Mods are stored in what I call "opensource" format which means it is very easy to dig into the Mod package and change things to your personal preferences with very little knowledge modding
Only the modified files within the apk are stored in a mod package. This greatly reduces filesize
AutoMod encourages backups at every major step in the process
Backups are dynamic, meaning it will only backup the files which are modified
Backups are automatically saved as a flashable zip file so you can have it ready if a mod does not successfully integrate
AutoMod always keeps itself up-to-date with the latest features
Distribution of AutoMod requires only the script itself
AutoMod has the ability to accept a ROM Install file or an actual device as a base for creating a flashable zip file out of any mod package
Supported devices can have mods applied instantly and automatically over adb
Features for Developers
Since mod packages only contain changed files, you no longer have to hunt through hundreds of files to find a single png (such as when creating five different colored versions of a theme)
Easy packaging of mods for redistribution for this tool as well as update.zip format
AutoMod can "install" multiple ROMs into it's system so you can make a mod once, and then distrubute it for several ROMs at the same time
If you run nightly builds of your own ROM, AutoMod will soon include a scriptable feature which will allow you to release nightly themes, mods, etc with no extra effort
Much of the developer features are yet to come (such as quick prototyping of mods and parallel device/ROM support)
---------------------------------------------------------------------------------------------------------------------------------------
Tutorial written by mybook4 on post #16 (be sure to thank him)
---------------------------------------------------------------------------------------------------------------------------------------
1) Download automod.sh script and place it into an appropriate directory (I used one called AutoModTest)
2) Download the ROM Install zips you would like
3) Create your mod package (see below)
4) Run automod by typing “bash automod.sh” in a terminal
5) Select option 5 (Install a new ROM file into AutoMod), and follow the script's directions (copying your ROM zip, to the directory, not moving it or it will be overridden)
6) Select option 4 (Install a new mod package into Automod), and follow the script's directions (copying your mod zip, to the directory, not moving it or it will be overridden)
7) Select option 3 (Use a ROM Install zip + mod to create a flashable zip for another ROM/device), choosing the appropriate ROM and mod package.
8) Out came the zip! This makes things soooooooooooo much easier and more manageable!
Notes about automod mod packages:
1) A mod file is structured as a zip file with the extension .zip replaced with .mod (so as to separate it from flashable zips with the same name)
2) In the mod file is a directory with the name of the mod.
3) In the directory with the name of the mod is a directory tree leading to the files within the specific apk you would like to modify. For example, in the ICSBlueFull.mod file, the directory tree is as follows: ICSBlueFull, system, app, SystemUI (the apk being modified), res, directories with modified files (images, xml files, etc).
4) Just to be safe (and to match the ICSBlueFull mod supplied), I set permissions on all folders in my mod to 755 and all files to 644 (if these numbers don't mean much to you, open a terminal and type “man chmod”)
5) There is a command to package mods you have made into .mod files. This can be found in the developer menu. (option 11)
6) Spaces in file name are currently not handled very well. Try and name your mods accordingly.
---------------------------------------------------
How To Create A Mod
click to enlarge
---------------------------------------------------
Download the script here: http://cl.ly/code/463B1C3B123i
Note: Proper syntax is 'bash automod.sh'
Download an example mod here (for stock GS3 touchwiz based ROMs) [Fixed!]: https://github.com/downloads/MADindustries/automod/ICSBlueFull.mod
Original thread for this mod can be found here: http://forum.xda-developers.com/showthread.php?t=1775235
View the source/branch it here: https://github.com/MADindustries/automod (check this to see if using a 'forceupdate' would add features/functions)
awesome work dude!
invisiblek said:
awesome work dude!
Click to expand...
Click to collapse
Thanks. Btw you are in the credits on the script itself. (even if it was a couple binaries haha)
Wow. Great work. Can't wait to see more!
Ta very much indeed.
ALQI
Sent from my SCH-I535 using xda app-developers app
Nice job buddy..No Windows support?
This is amazing. +100000000000
Sent from my SCH-I535 using xda app-developers app
incubus26jc said:
Nice job buddy..No Windows support?
Click to expand...
Click to collapse
Not just yet. I'm on Mac personally which makes it not too difficult to see some Linux support as well. But Windows would be a completely new write from what i can tell. It will likely happen after this is out of beta unless a Windows dev feels like working with me on it. Obviously everything is open source and i would love to see a port pop up before i get around to it.
Sent from my Galaxy Nexus using Tapatalk 2
Very cool indeed.
Tried to download the example mod but appears it's down/not available.
Definitely want to give this a try.
Thanks for sharing
MAD Industries said:
Not just yet. I'm on Mac personally which makes it not too difficult to see some Linux support as well. But Windows would be a completely new write from what i can tell. It will likely happen after this is out of beta unless a Windows dev feels like working with me on it. Obviously everything is open source and i would love to see a port pop up before i get around to it.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
It might work on windows with the right install of cygwin. I'd have to create a windows VM to test it out and I'm not all that familiar with cygwin anymore, any windows devs out there good with cygwin?
Sent from my SCH-I535 using xda app-developers app
alquimista said:
It might work on windows with the right install of cygwin. I'd have to create a windows VM to test it out and I'm not all that familiar with cygwin anymore, any windows devs out there good with cygwin?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Oh yeah! I totally forgot about cygwin. Yeah that should do it. It has all dependencies packaged with it except java and wget/curl. And only java is really necessary if you kinda know your way around.
Nice! Another great tool for the community!
Just what ive been waiting for
---------- Post added at 08:40 PM ---------- Previous post was at 08:32 PM ----------
Looks like running with cygwin gives unknown operating system. Can't proceed after that.
clark44 said:
Just what ive been waiting for
---------- Post added at 08:40 PM ---------- Previous post was at 08:32 PM ----------
Looks like running with cygwin gives unknown operating system. Can't proceed after that.
Click to expand...
Click to collapse
Oh yeah, that will have to be changed. run the command 'echo $(uname)' in a cygwin terminal and let me know what it outputs. I'm guessing just cygwin. Then i'll update the script to support it.
Any chance anyone has the example mod posted in the first post available on another hosting provider? It's been down for 2 days
myn said:
Any chance anyone has the example mod posted in the first post available on another hosting provider? It's been down for 2 days
Click to expand...
Click to collapse
Fixed it! Sorry about that. I don't know what happened with cloud.
Automod works great! Thanks so much! Here are the steps I took to create a quick little test mod to enable a 40x38px navigation bar and have only the wifi, bluetooth, gps, rotation, sync status bar toggles for Beans R8. I'm on Beans R3.1, so I didn't get a chance to test the zip in CWM.
1) Download automod.sh script and place it into an appropriate directory (I used one called AutoModTest)
2) Download the ROM Install zips you would like
3) Create your mod package (see below)
4) Run automod by typing “bash automod.sh” in a terminal
5) Select option 5 (Install a new ROM file into AutoMod), and follow the script's directions (copying your ROM zip, to the directory, not moving it or it will be overridden)
6) Select option 4 (Install a new mod package into Automod), and follow the script's directions (copying your ROM zip, to the directory, not moving it or it will be overridden)
7) Select option 3 (Use a ROM Install zip + mod to create a flashable zip for another ROM/device), choosing the appropriate ROM and mod package.
8) Out came the zip! This makes things soooooooooooo much easier and more manageable!
Notes about automod mod packages:
1) A mod file appears to be structured as a zip file with the extension .zip replaced with .mod
2) In the mod file is a directory with the name of the mod.
3) In the directory with the name of the mod is a directory tree leading to the files within the specific apk you would like to modify. For example, in the ICSBlueFull.mod file, the directory tree is as follows: ICSBlueFull, system, app, SystemUI (the apk being modified), res, directories with modified files (images, xml files, etc).
4) Just to be safe (and to match the ICSBlueFull mod supplied), I set permissions on all folders in my mod to 755 and all files to 644 (if these numbers don't mean much to you, open a terminal and type “man chmod”)
The 5StatusBarNavBar mod package for Beans R8
The CWM zip for the above mod package
MAD Industries said:
Oh yeah, that will have to be changed. run the command 'echo $(uname)' in a cygwin terminal and let me know what it outputs. I'm guessing just cygwin. Then i'll update the script to support it.
Click to expand...
Click to collapse
CYGWIN_NT-6.1-WOW64 (edit: uname -o will just return Cygwin)
Took a quick look at your script and I don't think it will too much of effort to offer cygwin support. Package manager by default will install bash, and curl/wget is available as well. You would need to install java naively on OS (it is accessible via your bash shell). Also to note don't think it will be required for your script based on my quick look, but you could always use the built in 'cygpath' command to convert windows<->unix paths if necessary.
Unfortunately only have a Windows box at work so can't spend to much time on but if no one gets to it I will take a stab later this week time permitting.
incubus26jc said:
Nice job buddy..No Windows support?
Click to expand...
Click to collapse
Linux is free and easy to dual boot. Nothing stopping you.
Or just run Linux from a VM. You can even forward the USB ports with Vitualbox.
mybook4 said:
Automod works great! Thanks so much! Here are the steps I took to create a quick little test mod to enable a 40x38px navigation bar and have only the wifi, bluetooth, gps, rotation, sync status bar toggles for Beans R8. I'm on Beans R3.1, so I didn't get a chance to test the zip in CWM.
1) Download automod.sh script and place it into an appropriate directory (I used one called AutoModTest)
2) Download the ROM Install zips you would like
3) Create your mod package (see below)
4) Run automod by typing “bash automod.sh” in a terminal
5) Select option 5 (Install a new ROM file into AutoMod), and follow the script's directions (copying your ROM zip, to the directory, not moving it or it will be overridden)
6) Select option 4 (Install a new mod package into Automod), and follow the script's directions (copying your ROM zip, to the directory, not moving it or it will be overridden)
7) Select option 3 (Use a ROM Install zip + mod to create a flashable zip for another ROM/device), choosing the appropriate ROM and mod package.
8) Out came the zip! This makes things soooooooooooo much easier and more manageable!
Notes about automod mod packages:
1) A mod file appears to be structured as a zip file with the extension .zip replaced with .mod
2) In the mod file is a directory with the name of the mod.
3) In the directory with the name of the mod is a directory tree leading to the files within the specific apk you would like to modify. For example, in the ICSBlueFull.mod file, the directory tree is as follows: ICSBlueFull, system, app, SystemUI (the apk being modified), res, directories with modified files (images, xml files, etc).
4) Just to be safe (and to match the ICSBlueFull mod supplied), I set permissions on all folders in my mod to 755 and all files to 644 (if these numbers don't mean much to you, open a terminal and type “man chmod”)
The 5StatusBarNavBar mod package for Beans R8
The CWM zip for the above mod package
Click to expand...
Click to collapse
Thank you so much for writing this! I am adding it to the OP. (let me know if you want me to take it down for some reason though)
Quick note, I think step 6 was supposed to be copy mod file to install directory? Also, a .mod file is exactly that; a zip file renamed to .mod. I did this to differentiate it from flashable zip files because the two would likely have the same name and it would cause confusion yet I still wanted to keep the .mod format easily modifiable/not proprietary. And one last thing, there is a hidden command called "packagemod" which can be used after you create your own mod to zip it up properly for distribution. It is entered at the main menu in place of choosing an option. Syntax: 'packagemod ICSBlueFull'.
lowg said:
CYGWIN_NT-6.1-WOW64 (edit: uname -o will just return Cygwin)
Took a quick look at your script and I don't think it will too much of effort to offer cygwin support. Package manager by default will install bash, and curl/wget is available as well. You would need to install java naively on OS (it is accessible via your bash shell). Also to note don't think it will be required for your script based on my quick look, but you could always use the built in 'cygpath' command to convert windows<->unix paths if necessary.
Unfortunately only have a Windows box at work so can't spend to much time on but if no one gets to it I will take a stab later this week time permitting.
Click to expand...
Click to collapse
Thanks for the tips. I have next to no experience with cygwin so this information is very helpful. I'll look into adding support to the next release.
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
Hi,
everytime I want to flash a new version of a rom I have to modify the zip file contents, i.e. delete some files etc, which is a very tedious process.
Thats why I created a little tool for Windows (requires .NET 3.5) that can do the following with a zip file of a rom:
- Delete files
- Add / Replace files
- extract .apk's, decompile them, modify (regex replace) inside text / xml files within, recompile them and put the updated version back into the rom zip.
The tool is still beta, so there could be many errors if you don't use it correctly... always make a copy of the rom zip before using this tool on it
The included apktool (for decompile/recompile of apk) requires JRE 1.6 and only works for Android Jellybean roms / framework-res.apk's - but I think you could just use another apktool version for different Android versions.
Included in the package is a sample configuration that is basically exactly what I am using. Of course you can change what files to add, delete and modify. Also there is a screenshot attached so you can see what it looks like - as you can see you need to have some basic knowledge of how android rom stuff works, I don't think this is useful to total noobs, sorry.
If you have any problems / suggestions feel free to write here.
I hope this is useful to someone
Regards
Abomb
Changelog:
1.0: Inital release
1.1: Some error checking, not all errors will be caught but at least some basic ones.
1.2: Files to delete and apk's to modify can now be selected from the zip file via file browser
1.3: Log during modify operation and bugfixes
1.4: More bugfixes, plus the settings are now stored in the image of a cat
Thanks I'll try it.
Nice tool mister.
There is any way to add zip paths auto (for example /system/etc/ etc) against to write all the line manual?
I'm using win7 and winrar.
Thanks.
Sent from my GT-I9300 using Tapatalk 2
eliashadow said:
Nice tool mister.
There is any way to add zip paths auto (for example /system/etc/ etc) against to write all the line manual?
I'm using win7 and winrar.
Thanks.
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
I'm not sure what part of the tool you mean, add files, delete files or apk modify? And do you want to add a whole directory to add/remove?
Abomb said:
I'm not sure what part of the tool you mean, add files, delete files or apk modify? And do you want to add a whole directory to add/remove?
Click to expand...
Click to collapse
To remove files i have to write manual the line.I don't know of there is a way to add it without write the path with keyboard.
I hope to understand what i mean...
Sent from my GT-I9300 using Tapatalk 2
Ah now I see what you mean.
I'll try to implement a way to "open" the rom zip file inside the tool to select files from it without having to type in the paths manually.
Edit: 1.2 now has that feature implemented, please try it and tell me if that works for you.
Version 1.3 shows a log during the modify operation and has various bugfixes.
Abomb said:
Ah now I see what you mean.
I'll try to implement a way to "open" the rom zip file inside the tool to select files from it without having to type in the paths manually.
Edit: 1.2 now has that feature implemented, please try it and tell me if that works for you.
Click to expand...
Click to collapse
Everything seems just fine now...
Thank you mister.
Sent from my GT-I9300 using Tapatalk 2
thx im gone try it:fingers-crossed: