Itjes Guide on how to cook your own rom, fast and dirty J Part 1
First of all, this guide will not tell you everything you need, I cant show you where to find reg entries, where all files are located. It’s a guide that will show you the basics. I will tell you how to extract a official nbh to os.no, how to dump it to respective oem and sys folders where you will do your “cooking”
First of all download Hypercore Kitchen here, then run the install file.
You will now have a folder called hypercore on your desktop, and a folder called core, located on c:\core
After install, download this fixed batch folder: batch or from mirror here: Batch
Delete the batch folder in c:\
Extract it to c:\core, and replace the original one.
The reason for doing this, is that there had to be some changes in the batch files for it to work.
Now you have a functional hypercore kitchen and you can start working.
I am gonna release a OEM, SYS and ROM folder for you, but not yet. I want you to understand how mutch work it takes to build a rom, and you need to go through some of the steps that all the other chefs must when they build roms. Why not just make it simple and give you everything? There is a answer to that, and you might not like it: Because I don’t want to….
Download your official RUU from here
Use winrar or similar to extract the files in the installer, choose extract to a folder.
Open the folder you extracted the files to, and find the RUU_signed.nbh
Copy it to c:\core\tools
Open your command-promt (dos editor)
Go to c:\core\tools
Your command promt should now look something like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
When this is done, you must enter this: nbhextract ruu_signed.nbh
The nbh will now be extracted and in the core\tools folder you now have all the files dumped from the nbh
The screen should now look something like this:
See the second last line Extracting: 06_OS.nb
That is the file you will need.
Rename the 06_OS.nb to OS.nb
Copy the OS.nb, then close the core\tools folder
Move to your desktop, and open the hypercore folder
Then enter the extract folder, and paste your OS.nb there
Go back to hypercore main folder, open the Panel folder, then open the Extract folder.
Inside the extract folder you will find a file/shortcut called Dump .nb and .bin
Now a panel will open and give you 4 options:
Now you are dumping the OS.nb into a xdump folder located in panel\extract
Your answer here is 1 since im doing this guide for heralds
Now a new window is gonna pop up and tell you that in that windows your OS.nb should be placed, and if you did what I told you correctly, then the OS.nb is located there already. So close that window, and then another option in the command promt will ask you to hit enter when ready, witch I now suppose you are.
The OS.nb is now being extracted into the xdump folder located in the extract folder. This takes aprox a minute or so.
When the OS.nb is finished extracting, you will get a option to start pkg.tools. just close that option,its not working for some reason, I never really looked into it, I just did a “workaround”
In panel\extract you will find pkg tool
Start the pkg tool, and you get a command promt window, read it, and then press enter.
Now you should see this:
Choose option 3
Pkg tools will now open.
Go to the file menu in upper left corner, chose open, then browse to hypercore\extract\xdump\
Highlight the dump folder and press ok.
GO TO NEXT POST IN THIS THREAD
You should see something like this:
Forget the missing manifests.
Now choose the Tools meny in pkg tools, and build packages, this will only take max a minute. (you will see nothing, just wait a bit.
When you have done his, browse to you xdump folder, open it, inside you will see the dump folder, rename the dump folder (not the xdump) to packages.
Copy the new packages folder and paste it into the hypercore\extract folder. Then close the pkg tools.
From now on, I will not give you screenshots of everything. You should get the picture on how it works now.
You will see a new commandpromt window, giving you 5 options, you choose option 4: Move oem and sys to hypercore\build.
You will get a question if you wanna backup, type n for no this time.
This takes 2-3 minutes, depending on your computer. The oem and sys is being moved to hypercore/build. Where the building process is gonna happen.
Next step is to go back to hypercore\panel\extract.
Open the dump XIP tool, and you get a new pop up window, just close it and press enter in the command promt. A new commandpromt window show you option 1 and 2, do both options, and when you have done this, the oem, sys and rom folder contains all you need to cook.
But that comes in next lesson.
I have now written this as easy as I can, if you don’t understand this, I cant help you more in this process, because I cant give it to you in a easier fashion.
Have fun
Itje
Part 2 of Itjes cooking lessons
How to add and remove and build your rom
I assume you have followed the instructions in the first part, learned to extract both the .nbh and the os.nb into rom, sys and oem folders.
My way of cooking:
First you need to find out what you want and not want in your rom. I will try to guide you into building a small apps rom.
So first I do, is deciding what I don’t want to have in my rom, and I usually go to the sys folder, and start removing stuff I don’t use:
But before you start removing in sys, highlight the sys folder, right click and choose properties, uncheck the read only box, if you don’t you can’t edit files.
Remove:
Transcriber + Transcriber_lang_04xx (xx is the country code in your rom) + Transcriber_ Lang_04xx_DPI_96
See what you need to do? Remove all the folders with the name transcriber in it
You can also do this with: Office, windowslive. Internetsharing, entertainment (games)
Be careful removing in SYS folder, delete wrong stuff, and you will have a brick when flashing.
That’s a easy “clean up” of the sys, there are also other stuff you can do.
You can make your own startup image, that is located in the Redist_dpi_96_resh_240_resv_320 folder, and is called welcomehead.96.png, edit with either adobe photoshop or corel, or any other picture editors that support png files.
Open the welcomehead.96.png and do your changes, save and your done. How to and all that with photos/pictures im not gonna do, so you need to find a way to do so yourself.
Now, you can go to OEM folder, where you can add and remove a lot off stuff.
I will not show you everything, you must figure some stuff out yourself.
But download OEM packages (This is easy to fin, its all over the xda forum.
Im assuming you have found in some stuff you wanna add, in.ex total commander, htc home, networkwizard, CommManager. Ocourse you can add more or less.
Add the oem packages into the oem folder. Total commander and networkwzard don’t require removal off default files from the oem folder, but comm. Manager do, and so do htc home. The way I use to find duplicate files, is before I add the oem packages, I open in.ex the new package with comm manager, and I highlight the OEM folder and rightclick and choose searchtab. Search for files, type in search “comm.” And all files containing the word “comm.” Will be displayed, dele them (make sure they belong to comm manager, that the names matches the one in your package)
When you have searched for all files in your package, and deleted them from the OEM folder, you can add you package.
Follow same steps for all packages you add, that can have duplicate files, if you don’t you will get error when building the rom, and the build process will terminate, tell you what file is duplicate. You must then find the file, and remove it (don’t remove the one in your new package)
You can also delete stuff from oem folder, I will take as example adobe.
The easy way to remove adobe, is to find a oem package with adobe, so you can see what files needs to be deleted. Use same way as I showed you with comm manager.
You can also delete gif files, png files and wav files to make more space, be carefulll so you don’t delete files that are needed by applications you wanna keep.
Now I hope this was clear enough.
Now you can go to the hypercore/panel/build section where you will find buildOS, run it it follow steps there.
If you get errors with duplicate files, you need to remove the duplicate and start buildOS again. And continue to do so if you get more errors.
But when the buildOS is finished, close it and a new window will pop up, chose your device, and press enter, and your os.nb will be built.
flash it to your device, and test it. If it didnt work, then you have done something wrong, or im just a lousy teacher
This was a very easy guide, I hope you find it usefull. There are lot of things you can do more then I have described now, but all you need is posted all over the forum. And if your dedicated enough, you will find all you need, just be patient. You cant find it all in one day,and you cant understand it all in one day.
Have fun
Happy cooking
cheers
----------------------------
Good work. Hopefully we can get some new roms going around.
itje said:
After install, download this fixed batch folder: batch or from mirror here : batch
Click to expand...
Click to collapse
Where's the link to the batch download?
LordPhong said:
Where's the link to the batch download?
Click to expand...
Click to collapse
right there
lol, was a bit tired yesterday, forgot to add the link
Cool - thank you itje for all the effort and time you are investing...
Can't wait for the next parts
trallala said:
Cool - thank you itje for all the effort and time you are investing...
Can't wait for the next parts
Click to expand...
Click to collapse
thx
has anyone been sucessfull extracting nbh to os.nb to oem, sys and xip (rom folder) following this tutorial?
When is the next part due? I really am eager to cook!!!
oddball1 said:
When is the next part due? I really am eager to cook!!!
Click to expand...
Click to collapse
havnt started on it yet
So I dont know maybe this weekend, but not later then the end of next week
patience, my friend, patience
is the next part just making the extended rom portion? I think there's a tutorial somewhere on this site but I can't seem to remember off the top of my head, right now.
itje said:
Download your official RUU from here
Click to expand...
Click to collapse
I'm being a pain in the arse again. there's no link there and I don't know if it's the same one as the official tmo release. I know I can probably use that one but would rather not.
hey itje the links for the new batch files doesnt seem to be working. i tried them and it just keeps popping up saying it cant DL
edit: nevermind i got it too work. it was blocked on the isp i was using.
itje said:
thx
has anyone been sucessfull extracting nbh to os.nb to oem, sys and xip (rom folder) following this tutorial?
Click to expand...
Click to collapse
itje said:
Rename the 06_OS.nb to OS.nb
Copy the OS.nb, then close the core\tools folder
Click to expand...
Click to collapse
where do we copy the OS.nb to? Since, I didn't know, I, manually, had to do it.
itje said:
Copy the new packages folder and paste it into the hypercore\extract folderThen close the pkg tools.
Click to expand...
Click to collapse
This didn't work for me. I had to manually past it in %systemroot%\Core\Extract\Packages after I closed the pkgtools. For some reason, it didn't find the Packages folder correctly.
After that, I followed everything else and it worked fine. Just as you described. Just waiting for part dos (spanish not MS-DOS).
everything works fine up until the end waiting on farther instructions.
EVERYTHING YOU ASK FOR IS ALLREADY THERE, START READING........
Just as its clear, from now im not gonna answer anyone who ask for something thats allready described in the tutorial.
But the link for ruu was not there, I'll give you that..
i am cooking my chinese rom ,and thanks you working.
ginolin said:
i am cooking my chinese rom ,and thanks you working.
Click to expand...
Click to collapse
Glad I can help
Honestly, if anything you did went wrong, is because you are not reading and reading it again before you do it!
Up to now, everything is well explained
Related
For those of you who want to customize wm6.1, here it a simple ROM kitchen to do so. Beginners, please wait for my GUI release. It is much simpler to use. This isn't that hard, but it takes a little bit of time on your side.
The basics:
All software and regedits are contained in folders called OEM packages. These are in the OEM folder.
All operating system stuff is in the SYS folder. I've also moved the shadow drivers here so you don't have to mess with them.
To make OEM packages:
Download ervius's package creator 5.4 from XDA-developers. Use this to open the cab file to convert into a package.
Copy the OEM package to the OEM folder.
Do NOT delete the OEM packages you don't want. You will choose them later in a different way.
NOTE: You can always download premade OEM packages from XDA-Develoers. There are tons of options.
If you want to make a regedit.
Create a new folder in the OEM folder and convert it into a package using Package Creator 5.4.
Open the RGU file inside with notepad
Edit like following. Note that this isn't the way to comment in regedit files:
Code:
REGEDIT4 <-----Make sure this is always the first line
------Leave one line blank here-------
[HKEY_LOCAL_MACHINE\Software\Example Software\Example Key] <----- Navigate to keys like this
"Example String" = "test" <-------- Write values with quotes. Strings are given with quote after the equal sign.
"Example Directory" = "Windows\\test.jpg" <------ Use \\ to indicate a \ between directories. Otherwise, the ROM build will not work.
"Example Number" = dword: 5000 <----- use dword: to indicate a number or hex value.
<----- You can add more reg entries after the first one. Make sure to specify a different key when needed
-----leave 2 lines at the end of file------
For Sliding Panels:
Leave ROM as it is.
For Neo interface:
Replace Chome folders and bronze folders in SYS folder with the ones attached below.
Select Neo Interface in the buildos step.
Build ROM:
start buildos.bat
when it opens packagetools+buildos, click on the buildos tab.
Click load rom and navigate and select the kitchen folder
Select which oem packages you want and then click Go.
Once it is done, close out.
Sit back and relax for a while so the batch file can build the ROM.
Self-explanatory from here.
Post any questions/problems here.
link: http://www.sendspace.com/file/ap9n8w
NOTES: The inlcuded T-Mobile Edition Package is my beta version. Feel free to build on it. You might also notice the empty placeholder folder for my N33D4SP33D Edition rom that I haven't worked on yet.
To make OEM packages:
Download ervius's package creator 5.4 from XDA-developers. Use this to open the cab file to convert into a package.
Click to expand...
Click to collapse
I found the program but get many errors when I start it up on my computer.. Im currently running Vista Ultimate. I went into control panel and changed the enviroment to emulate WinXP when the program runs and still get many errors..
Is there a vista friendly program out there or alternative available?
I'm running Vista Ultimate too and it works perfectly for me.
Attached is the version I have.
ND4SPD said:
I'm running Vista Ultimate too and it works perfectly for me.
Attached is the version I have.
Click to expand...
Click to collapse
Great! yours works thanks alot now to get my feet wet in all this lol
I got this error
'Error building default.hv and user.hv! (see imto "BuildOsX-log.Txt")
i can't see anything in there. What now. Thanks
Do you mean there's nothing in the BuildOsX-lot.txt? There should be. A few lines from the last, or the last line, there should be the registry file that messed up and on which line it messed up on. The file is given by the GUID, or that long string of numbers and letters that you see.
no, there is nothing what tell me what to do. so what should i do with that error.
i will make stick this thread.Hope next times will see some roms with this kitchen
Thanks tom. I'll make sure to post my GUI kitchen soon to let more people create ROMs a lot easier.
kormanb1123 said:
no, there is nothing what tell me what to do. so what should i do with that error.
Click to expand...
Click to collapse
what kind of things did you modify or add? Maybe I can help based on that.
I get the same error for the following:
InitRegistry FAILED in file ".\Registry\fcbf420c-04fd-478f-bd29-e4ab55973337.rgu" within a few lines of line 359.
ImportFromPackageListStrict: (RGUComp) !ERROR failed importing ".\Registry\fcbf420c-04fd-478f-bd29-e4ab55973337.rgu"
wmain: (RGUComp) !ERROR failed building DEFAULT hives
Looked through each App in the OEM folder until I found the matching rgu number, which in my case is the HTC DirectShow. Took that out of my ROM build, ran again and it states that it completed.
I think there is a problem with the directshow package. I'll check the registry entries. Until then, I think you might need to go without that.
This may sound like a stupid question, but hear me out. I have used BuildOS in the past for an Apache from PPCGeeks\PPCKitchens. Once the ROM is finished creating in that version it auto prompts to update your device.
After the ROM is done in your version, I then selected the Package Tool tab and pointed it to the "temp" directory and it did it's thing. Now I am at a loss for what to do next. I see a .nb file temp\dump\ROM directory but i don't see a .nbh file. Do I use the NBHTool even though PHOEB is not listed?
ND4SPD said:
I think there is a problem with the directshow package. I'll check the registry entries. Until then, I think you might need to go without that.
Click to expand...
Click to collapse
I'm not too worried about the directshow, I just that maybe the other guy was getting the error for the same reason so figured I would pass on my resolution.
Sorry, I guess I didn't completely read you post. For the HTC Rom Tool, use the exacalibur settings. Those are the exact same as the Juno.
all I have is o4_osxip.nb.exe in the temp folder no nbh is this the right nb. file I use with
htc tool I put exacalibur settings but don't no what to put in firmware contents
do I put o4_osxip.nb.exe in system and none in the ipl spl and splash and 0x800 radio
ok i did this
Build ROM:
start buildos.bat
when it opens packagetools+buildos, click on the buildos tab.
Click load rom and navigate and select the kitchen folder
Select which oem packages you want and then click Go.
Once it is done, close out.
Sit back and relax for a while so the batch file can build the ROM.
ok where is the rom all i have is o4_osxip.nb.exe in the temp
i have no file imgfs-new.bin in the temp all i have is 04_OSXIP.nb.exe and cecompr_nt.dll and CECompressv4.dll
and where would i look for the batch file
Thank you for your works, ND4SPD
but i can not download your kitchen, it says reached the 4G limit.
because i want to know is there any wrong method i used.
My issue is :
when buildimgfs, the total sections can not bigger than 1B200.
when i put too many files into the imgfs file, the buildimgfs will quit without any info.
but the 71M imgfs.bin have about 22000 sections.
do you have issue too ?
Is it because my PC have only 1G RAM, not enough to do the building?
@Hikey: I have that same problem too. It's the way t-mobile packaged the rom. I'm going to try using the dopod rom for the base next. It might be the PC too. I only have 1GB of RAM, maybe it isn't enough.
@kron2:
run buildos
download this zip: http://www.sendspace.com/file/xuhlc5
copy the files from the zip archive to the temp directory.
open up the cmd that's now in the temp directory.
type the following:
Code:
ImgfsFromDump imgfs-old.bin imgfs-new.bin
Sit back and relax. If this finishes without crashing like Hikey said, do this:
Code:
ImgfsToNb imgfs-new.bin 04_OSXIPN.nb os.nb -conservative
Now you can run the htccert program in the main directory of the kitchen to build the rom. When you are done making the nbh, copy it to the RUU folder and run the update utility.
In the following 3 manuals, you will be shown/told how too create a theme.
Thank you to the authors. Most of all to Stericson for he is the first to figure out HOW to create a theme for your phones.
Thank You Again
Restore your G1 back to it's original theme and fonts!
To create themes, or to edit themes to your liking, you will need a working knowledge of android, adb, how to resign apk's, knowledge of your own O/S.
Things you will need:
The rom you intent to create a theme for... Now a days there are so many to choose from so none of this will be rom specific.
You will also want to get the latest and greatest bootloader installed on your phone and to HIGHLY suggest everyone trying your theme to install it as well.
You'll find this on Android Development
You will also need the latest SDK and java:
Link to Java: http://java.sun.com/javase/downloads/index.jsp
Downloading SDK: http://code.google.com/android/intro/installing.html
You can also use any zipping archive to extract files from and to the update.zips. I believe there are links below to some of these.
Very Important!
You do not usually need to resign every apk that you change! Usually you only need to resign the update.zip! However there may be times that you may need to resign an apk. So dont sign the apks...if you have problems with the update then try to resign the apks.
JesusFreke was kind enough to build a custom signing tool for me that would allow me to right click on an apk and resign it from there. I am posting it here for others to use as well. Note that this is a courtesy of JF, so thank him for it. I cannot stress how much time this has saved me and will save you.
Automatic version!
Do not use this to sign APK files in Vista or windows 7! It will cause your theme to loop phones when placed on a device. Only use this to sign update files if your using those O/S's
Note, this will not work if your SDK or the path that you place this in has any spaces in the dir name!
An Example of this is c:\users\Nikki and Stephen\sdk\tools
Try to put the SDK and the contents of the zip in a dir where the names are all together and not like the one above.
I have made a batch file that will automate the entire process of setting up to use the signing tool made by JF. This batch file will set the CLASSPATH, set the PATH, install the registries, and will even allow you to sign files manually if you wish. I plan on building onto this batch file to include other things. However, for the moment, it will only include what you see here.
In order to use this you should have downloaded the sdk already. Simply extract all of the files into the tools dir of your sdk, and run autosign.bat follow the instructions and go through the options one by one, starting with 1 working through 4. You can however, put the contents of this zip anywhere on your computer and it will work. It is just better to put them into the tools dir of your SDK. Especially for the consideration of future versions.
Autosign .zip: https://docs.google.com/leaf?id=0B5...MTEyMi00NzI4LWJkMDQtZTUzNjBjMTZlMWNj&hl=en_US
Want to set up the signing tool manually?
Before using this you need to know how to set this up:
Now you will need to add the tools dir of your sdk to the environment variable CLASSPATH.
FOR XP:
Right click on My Computer click properties, then choose the tab that says advanced.
Click the button that says environmental variables.
Go to system variables find the one that says CLASSPATH
double click it
go to the end of variable value.
There should be a semicolon ; at the end, type in the path to the testsign.jar located in the tools directory of your SDK
for example the path to my testsign.jar was c:\sdk\android-sdk-windows-1.0_r1\tools\testsign.jar
If CLASSPATH is not in your system variables then create it.
Secondly, Find the system variable called PATH and add to the end of it, the full path to your sdk directory.
For example, mine was c:\sdk\android-sdk-windows-1.0_r2\tools
FOR VISTA:
Open a cmd prompt.
Replace THEEXACTPATHTO-TESTSIGN with the path to the dir that holds the file testsign.jar.
Type:
echo %CLASSPATH%
If it is returns %CLASSPATH%
Type the following:
set CLASSPATH=THEXACTPATHTO-TESTSIGN\testsign.jar
If it comes back with something else then
Type the following:
set CLASSPATH=%CLASSPATH%;.;THEXACTPATHTO-TESTSIGN\testsign.jar
For Example, when I type this it looks like:
set CLASSPATH=%CLASSPATH%;.;c:\Android\SDK\tools\tests ign.jar
To set the PATH
Replace THEEXACTPATHTO-SDK with the path to the tools dir of your SDK.
Now type:
set PATH=%PATH%;.;THEXACTPATHTO-SDK\tools
For example, when I type this out it looks like this:
path-%PATH%;.;c:\Android\SDK\tools
Now through doing this you have done two things, first off you have made the resigning process extremely easy, secondly you will not have to cd to the tools dir of the sdk to use adb or any other tool in the sdk.
Signing the Files:
Now right click the reg file that you extracted and choose to install it, or merge.
Now, right click an apk, do you see an option that says ResignApk? That's how you will resign your .apks and .zips.
When you choose it a cmd window should open for a few seconds and then close. the file you signed will be overwritten with the new resigned file.
If you find the right click menu not working for some reason you can type the following in cmd to sign your files: java testsign whateverfiletosign
General Info:
You will need to be specific in addressing what version your theme is for, RC8, RC30, or ADP1. Make sure you test the update.zip before you release it.
Every .apk contains the images relating to itself. However, every apk has the ability to use the images in framework-res.apk. The images for every apk is located inside of itself. To find these images open up the apk, you can rename it to .zip or open it with an archiver of your choice, winrar, winace, etc. Then after opening the apk open the folder called res and inside of that there are folders that are named Drawable, drawable-land, drawable-port, etc. This is where the images are stored.
There are some things you cannot edit unless you rebuild the entire apk from source, which we will not go into here.(another tutorial, another time) Just know that at this time you SHOULD NOT edit, or even open images with the extension .9.png doing so will corrupt the .9.png and cause the image to distort. You can however compile the images with eclipse.
Editing .9.png's - http://forum.xda-developers.com/showthread.php?t=487001
Be aware, messing with .9.png's can cause problems if they are not done correctly.
If your going to build your own update.zip from scratch:
To simplify this process for you though, most rom devs provide a theme template with their roms now. You can also download someone elses theme and use their files, since they are resigned already. It may also be easier to see what files do what and go where since they have already been edited and are easy to point out.
Now, your ready to start changing things up.
You will now need to open the apk, which you can do by adding .zip after .apk, effectively changing it to a zip. or you can use your favorite archive opener.
I dont use the archive process because it can lead to very aggravating problems such as things not getting signed correctly and have heard reports of it interfering with the signing tool above. Anyways I just add zip and it works great for me.
For those renaming the .apk's to .zips
Note that if you are using windows you will need to unhide known file extension types. you can also use your favorite archiver such as winrar, winzip, etc.
See here to unhide known file extension types for Xp: http://www.mediacollege.com/microsof...on-change.html
See here to unhide file extension types for Vista: http://maximumpcguides.com/windows-v...ile-extension/
Tips:
After opening the apk copy the folder called res.
Go to your desktop, or wherever, create a new folder called Images, or whatever.
Open the folder, paste the res in there.
Now you can see what the files look like without opening them, by using thumbnails to see what they are.
Btw, you may also want to add -frame, or -launcher, to the end of the res folder you copy over to keep them separated from others.
Almost Done
So now your theme is done and your ready to make an update.zip for others to install your theme.
Update script
The update script is in a Unix format, while you do not need linux you must save it in a Unix format. I suggest using Textpad to edit this script and saving it in the Unix format.
Link to Textpad: ftp://download.textpad.com/pub/textpad5.2/txpeng520.exe
XML Edits
I have provided some additional support for the process of hex editing xml files to change things like text color, size, and more things not easily changeable.
You can find this thread here: http://forum.xda-developers.com/showthread.php?t=479019
Final Notes:
Editing market apps
With market apps, if you make changes you usually need to make sure you dont resign their apk because you will overwrite their signature keys with the test keys.
If anyone has any questions please try asking for help in this thread before emailing me for help Usually I will respond to questions in this forum.
I hope this Tutorial has been helpful. I will add on to it as needed.
Any questions can be directed to me at [email protected]
Stericson
Links of interest:
Using ADB: http://code.google.com/android/reference/adb.html
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
ToDo:
1. Explain about the files that make up themes
a. Explain update.zip and folder structure
b. Explain about pngs and apks
2. Explain the tools
a. WinRaR
b. Auto-sign
c. Java JRE and JDK
d. Draw9patch tool
e. Editing tool
3. Setting up your phone for themes
a. Choosing which JF firmware to use
b. Using the Eng Boot Loader and why
4. Explain the process to get the files
5. Explain which files to edit
6. Explain how to import modified files
7. Explain about auto-sign and how to use it - I am building a program that will making signing files easier. check it out as i build it! here
1. When you download a theme it comes in the form of an update.zip file. Basically the same as the full update looks, but it is a watered down version. All of the operating system, boot loader and radio files have been removed.
a. If you check the file size of JF’s RC30 1.31 and compare it to any of the themes, you will notice that the theme file is about a 3rd the size. JF’s update.zip contains data, META-INF and system folders it also contains a boot.img file. Where as a theme update.zip contains app, framework and META-INF folders. The theme update.zip only contains the folders and files that are necessary for changing the Android theme. If you were to dig deeper into JF’s RC30 1.31 update.zip you will find the folders that are in the theme’s update.zip. For example, double click the system folder and you will see 11 folders and 2 files. The only ones we are concerned about are app and framework. So when you flash a theme it doesn’t bother rewriting all of the OS and boot loader, but only the app and framework folders.
b. Inside the app and framework folders are apk files, apk files are like zip files or containers. There are many folders and files inside the update.zip but we are only going to cover a few for now.
(app folder) - This folder contains all of the apps that will be installed during an update or wipe. You will need to extract only the apks of the apps you wish to change the icon and graphics for.
(Launcher.apk) - This file is in the app folder and contains the menu launcher tab, clock, Google search widget, wallpapers and a few other things.
(framework) - This folder contains framework-res.apk, this is where the bulk of your editing will take place.
When you open a apk you will see:
(assets) - This will contain images, sounds and other content used by the programs. Not always used!
(META-INF) - This contains the encryption data for the update.zip.
(res) - This folder contains all of the png and xml files. The xml files are used to format the UI, these can be used to change the locations of things on the screen. They need to be unencrypted first.
Depending on the apk there can be a bunch of folders under the res folder but we will only concentrate on the drawable ones.
-drawable - The png files in this folder are displayed wheather the keyboard is open or closed. The majority of the files are here.
-drawable-land - These are the files that will show when the keyboard is open. There won't be as many files in these folders. Most of the time the programmer will re-organize the layout with an xml file.
Basically the interface of Android is a bunch of pictures; the programmer links these to certain actions. As someone making themes you do not have to worry about any programming, in the future when people start unlocking the xml files to change the way things look. Then you will have to learn some basic programming, but for now we will only talk about changing the picture files.
2. The tools you use for creating themes are very basic and you might already have 3 out of 4 installed.
a. WinRaR is a must have for everyone, it allows you to create and open compressed files (i.e. Zips, RaRs and about 25 other file types) It would best if you associate WinRaR with zips and apks, the zips can be associated during the install of WinRaR. To associate apks you can right click on an apk and choose “Open With…” make sure to check off the box that says “Always use this program to open this kind of file”
b. Auto-Sign was released by Dave da illest 1, to make signing the apks and update.zip an easier process. Before you can flash an update or theme the phone checks to make sure the update.zip is signed by google or by JesusFreake. I will explain this more in Section 3.
c. Android apps are built on Java, hence the need for JRE and JDK, You will not be working directly with these apps but part of the signing process uses Java. You can get both files here: http://java.sun.com/javase/downloads/index.jsp you will want to grab the first and second downloads.
d. The draw9Patch tool comes with the Android SDK, it is located in the tools folder. This tool is used to edit stretchable images. There is still a lot of research that needs to be done on using this tool. So for now let’s just say do not touch any files with .9.png as an extension. Dave da illest 1 has changed a few of these .9.png files without issue so maybe we can get him to explain them better. I have also edited some of these files but it made some of the images stretch weirdly.
e. I am not sure what other photo editors you can use, but everyone I have spoken to about modding the theme uses Adobe Photoshop. I am sure you can use other programs. But I am not aware of any at the time of this writing.
3. Before changing the theme on your phone you will need to gain root access which is explain here: http://forum.xda-developers.com/showthread.php?t=442480
a. As you look through all of the different themes, you will notice some say they are for RC30, RC8 or ADP1.
i. RC30 – Is the US version
ii. RC8 – is the UK version
iii. ADP1 – Stands for Android Developers Phone and was produced for programmers. This version is completely unlocked and does not have any of T-Mobile’s software or locks.
b. So your phone is rooted and you’re wondering why you should have the engineering boot loader. Well one reason is because of the 3 Androids on skateboards, the other reason is if your phone bricks during a flash you can fully recover your OS with the fastboot option. More about this can be found here: http://forum.xda-developers.com/showthread.php?t=455860
4. You have a few options here, you can either get the files from RC30 update.zip, one of the other theme’s update.zip or you can use the themes template at the bottom of this thread. All 3 methods you will need to open the update.zip go into the framework folder (if you get it from RC30 you will need to go into system\framework) Extract the framework-res.apk to a folder of your choosing. Most of your editing will take place on the files from this apk. When you are looking at these files in Windows explorer it is best to change the view to Thumbnails and look at all of the images and see if you can figure out where they are placed on your phone’s screen.
::TIP1:: Your best bet is to create a Themes folder on your desktop or in My Documents, somewhere simple to find. You will be dealing with a lot of files and it can get very confusing quickly.
The other file you will want to change is Launcher.apk; this file is in the app folder and contains the menu launcher tab, clock, Google search widget, wallpapers and some other things.
::TIP2:: When you open Launcher.apk from inside the update.zip file, WinRaR may default to a temp folder...(i.e. C:\Documents and Settings\bobbyd\Local Settings\Temp\Rar$DI71.579\framework-res) double check the location of where WinRaR wants to extract the files, this is how I ended up flashing the original files after spending a decent amount of time photoshopping.
5. Now the only files you will want to edit are png image files. There are also xml files, they are used to format the UI, you can change the locations of things on the screen but the xmls need to be unencrypted before you can edit them. I have not done this process yet and will update more information later.
6. Importing the files is very simple, as long as you know the layout of the update.zip. Once you have edited all of the files you plan to or just want to test to see how your theme looks. Open the update.zip in WinRaR and go to the location of the files (i.e. Say you changed the 3G icons, you would go to the framework folder and double click on framework-res.apk. This will open another WinRaR window, open Windows Explorer where your edited files are and hold the Ctrl key while clicking the files you want to copy. Now drag them onto the open WinRaR window from the framework-res.apk. When it asks to replace the files choose “Yes” or Yes to All”. Close that WinRaR window and the one from update.zip will tell you “Files have changed would you like to save this file now” click “Yes” again and now your update.zip will contain your modified files.
7. Download and install Stericson's auto-signing tool here.
I have been slacking on this guide, I will update soon again.
[HOW TO] Easy steps for creating a theme
I know there are a million and 1 walkthroughs on here for creating themes but after doing it for a while I have really refined my process and made it as easy as possible. Im just hoping to clear up some of the confusion so after you know how to sign your files you will know how to finish making them into your own custom theme.
First you need to get signing setup properly. This topic is covered in many places and my recommendation is to use the Stericson walkthrough or the Stericson auto-signing setup tool. Once you can click on any zip or apk file and get the option to Resign it you are ready to proceed with making your own theme.
1. Download an archive manager that allows you to open archives inside of archives without creating new windows. My recommendation for this is the application 7-zip. It is tiny, free, easy to use, and on all my computers it has replaced winzip and winrar.
2. Now take a blank theme from Stericson to use as your starting point, in my case I use the ADP1.1h version since I am building for JFv1.43 which uses ADP1.1h this will be the minimum needed to change your theme and will contain all the original artwork.
3. Open the update.zip and inside are typically 3 files, framework, system or app, and META-INF. Leave META-INF alone, you wont be touching that. Inside framework and system/app is where the files are that you can change. In this case we will open update.zip, then double click framework and then double click framework-res.apk (this is where the next archive will open inside the same window, your life just got a little easier).
4. Now you are looking at assets, META-INF, res, and a couple other random files, the resources.arsc can be edited but I will show you that in another tutorial. Now open up the folder res and you will see the treasure we are searching for, folders with the name drawable. All of the folders that start with the name drawable are where we can edit the themes, this includes drawable, drawable-land, drawable-port, and drawable-finger.
5. Now drag and drop the folders drawable and drawable-land onto the desktop. Once they are on the desktop you can edit the .png files in those folders until you are ready to put your theme together.
6. Now in your still open window at \framework\framework-res.apk\res\ you will open the drawable folders one at a time and drag and drop your edited files into the archive, only dragging and dropping the files you edited and not just everything inside the folder.
7. Once you have your new images copied into the archive in the correct place you can just hit the close button or browse up a couple directories and find other files to edit. Any time you edit an apk and browse out of it or close it you will be prompted to update it in the archive by 7-zip (this is my secret shortcut), always press ok.
8. Now you have a freshly created theme ready to install, all you have to do is right click, chose to Resign the file, and once its done you can copy it to your SDcard, make sure its named update.zip, and flash your new theme.
Its literally that easy! And you use this same technique in the system/app folder to edit the apk files for the individual apps on the phone. Explore around in the update.zip and see what you can find, I only told you about the major items but there is plenty more to find and change. You can always copy a folder out of the archive and if you cant edit anything just toss it but if you can find something to edit, do so and throw it back in the archive. You guys now have all the info I had when I started plus all my tricks to making that process 10x easier.
I Just Want To Change My Clock. I want everything else stock. Sorry for asking but when i search so much comes up. I know its really simple to do. If anyone can just point me in the right direction or give me a quick how to that would me AMAZING!
Read:
http://forum.xda-developers.com/showthread.php?t=482205
notifi
jut want to change notification to white on statusbar
Before I tried to setup the autosign tool, when I double clicked on zip files it opened them up, which was how I wanted it. After trying to setup the autosign, when I double click on zip files nothing happens, except a java command prompt window pops up, same happens when I right click and hit resign zip, how can I fix this?
Edit: I reinstalled Java which fixed my issue
i got this tryin to update
E:No digest for framework-res.apk
i edited someone else theme, did not edit no .9 file.. i right click on the update.zip and resigned it. what went wrong?
EDIT: nevermind i got it.. i followed the one for dummies, guess i am dumb lol
What the image file for the tab on the bottom of the screen called? I couldn't find it searchin throguh the framework-res.apk
its in launcher.apk. Check in drawable portrait and drawable landscape.
Stericson
thanks i should of explore more before posting
Hi,
I've got 99% of my theme done although I can't find where the bottom of the notification bar is and the white bit where the notifications would be.
I've done a little picture below to help me explain.
Bottom notification bar is the arrow.
The white bit where the notifications would be is the hatched.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks for help in advance.
Also could someone tell me how to put icons in for well know apps from the market. At the moment I have put the full apk in the update and change the icon. But this increases the theme size. Thanks again!
NO DIGEST? Failed?
what does it mean when I try to flash the new update.zip and it fails because it says NO DIGEST? What does this mean? Any help would be greatly appreciated. Thanks
parmenti said:
what does it mean when I try to flash the new update.zip and it fails because it says NO DIGEST? What does this mean? Any help would be greatly appreciated. Thanks
Click to expand...
Click to collapse
means it hasn't been properly resigned.
thanks, that's what I thought. Can't seem to get it right. Does the image, the apk, and the zip all have to be resigned? Or just one or the other? THanks for your help.
parmenti said:
thanks, that's what I thought. Can't seem to get it right. Does the image, the apk, and the zip all have to be resigned? Or just one or the other? THanks for your help.
Click to expand...
Click to collapse
Just the update.zip needs to be resigned.
**********************************************************************************************************************
IMPORTANT: Use my guide as your own risk. I am not responsible for anything if you device is bricked. Please flash only if you have hardspl installed.
**********************************************************************************************************************
XPERIA ROCKS**********************************************************************************************************************
I have been using Xperia's cooked roms from Jack and ITJE and they are good. However, there are some problems with working that and not working this. and also I found that either the roms are too light or too heavy.
My goal is making Xperia rom as light as possible and only using xperia original stuffs so that I don't have problems with bluetooth and other things.
And I found a way to taking out junks from Xperia X1 and increased X1's storage space to around 360 MB by using Kovsky Kitchen and working everything normal.
I found that X1i_GENERIC_UK_CDF1215-1832_R2AA010 is the best for me and I stripped out SE's junks from the rom using Kovsky Kitchen. You can do to any original rom for your need.
Preperation:
1. Download Kovsky Kitchen here http://forum.xda-developers.com/showthread.php?t=477801 .
2. Download X1i_GENERIC_UK_CDF1215-1832_R2AA010 .
Start Cooking your own rom:
Step 1: Preperation
1. Extract Kovsky Kitchen to any where you want. (Preferrably C:\Kovsky Kitchen)
2. Rename APP_SW_X1i_GENERIC_UK_CDF1215-1832_KOV_R2AA010.image to RUU_Signed.nbh and copy to Kovsky kitchen's BaseRom folder.
Step 2: Extracting
1. Run KovskyKitchen.CMD
2. Type "e" to extract the original X1 R2AA010 rom
3. Type "a" to start extracting. (It will take around 2 or 3 minutes)
4. Wait until you see "Press Any Key to continue...."
5. Leave the CMD windows open...
Now Kovsky Kitchen is ready to cook...
Step 3: Cooking
1. Go to a newly created folder called " OEM" in the kitchen that where you do stripping out SE's Junks.
2. Go to "ConfigAP" folder. You will see config_AP.txt. Make file writable by changing read only attribute. And delete all links to CAB files that you want to delete. I delete them all as I don't want any of them.
CAB: \WINDOWS\bejeweled2SX1.PPC_2577.WM5_signed.CAB
CAB: \WINDOWS\FM-Radio_Panel_MR1_R19_32318_signed.CAB
CAB: \WINDOWS\GoogleMaps-ms-sonyericsson_emb.cab
CAB: \WINDOWS\GooglePanel_UK_MR1_R19_32195_signed.CAB
CAB: \WINDOWS\GoogleSearch_SEMC_1.1.40_RC3_signed.CAB
CAB: \WINDOWS\MxP_R19_MR1_RC2_32367_signed.CAB
CAB: \WINDOWS\WM6.1_PPC_dawn_Opera_2532_signed.cab
CAB: \WINDOWS\sudokuSX1.PPC_2577.WM5.CAB
Leave only "CFG: \WINDOWS\config_end.txt" line . I don't want any junk in the rom. I will install them later by UC config or manually install them.
And put the file back "Read Only"
3. Delete folders that you don't want in the OEM folder whatever start with "PACKAGE_". For example:
PACKAGE_Kovsky_Bejeweled2
PACKAGE_Kovsky_Bejeweled2_0409
PACKAGE_Kovsky_FMRadioPanel
PACKAGE_Kovsky_FMRadioPanel_0409
PACKAGE_Kovsky_GoogleMap
PACKAGE_Kovsky_GoogleMap_0409
PACKAGE_Kovsky_Googlepanel
PACKAGE_Kovsky_Googlepanel_0409
PACKAGE_Kovsky_GoogleSearch
PACKAGE_Kovsky_GoogleSearch_0409
PACKAGE_Kovsky_HandangoInHand
PACKAGE_Kovsky_HandangoInHand_0409
PACKAGE_Kovsky_MxP
PACKAGE_Kovsky_MxP_0409
PACKAGE_Kovsky_Opera_Browser
PACKAGE_Kovsky_Opera_Browser_0409
PACKAGE_Kovsky_Sudoku
PACKAGE_Kovsky_Sudoku_0409
4. Deleting files from ExtendedPkg (Musics and Movies)
Make config.txt writable and delete
"XML: \WINDOWS\fileoperations.xml" line and Make the file read only again.
Delete all files that are larger than 22 KB except "Xperia Black.tsk", because i like Xperia black theme.
You can delete other files if you want to but for me I leave them alone as they are small enough.
5. Deleting files from SYS folder (These are original WM stuffs)
Delete "AUTOUPDATE" folder
Delete "NetCF" folder (You can install NetCF 3.0 later)
Delete "SampleMusic" folder
Delete "WelcomeCenter" folder
Delete "WelcomeCenter_Lang_0409" folder
You can delete OneNote, Office, or WindowsLive if you would like to. But I leave them alone.
Now.. our rom has no more unwanted stuffs..
Step 4: Building OS
1. Go back to CMD window and
2. Type "C" cook a rom.
3. Type "A" if you want to use the old BuildOS.exe (I can't figure out the second one)
4. BuildOS windows will appear.
5. Just click on green "Play" icon and It will start building our rom. Wait until it finishs and closes the "Build OS" window.
6. Go back to CMD windows again and wait until you see "press any key to contine".. press any key..
7. It will do some stuffs and you will see os-new.nb in the kitchen folder.
8. htc rom tool windows will appear.
Go to Rom Builder TAB. Choose Kovsky * in device. It will fill all the infomation in other fields. Just change the version to anything you like.
9. Choose "os-new.nb" in the OS field. and click on "Build" button.
10. Save it as "RUU_Signed.nbh" in the kitchen folder. A new window appear and it will quit itself.
11. Now. you will see "RUU_Signed.nbh" in the kitchen folder.
12. An Hexa Editor windows will appear. Just close it.
13. You can close CMD window now.
Step 5: Flashing
Now you are ready to flash your own cooked rom. You can flash your rom with RUU Update Utility or just change "RUU_Signed.nbh" to "KOVSIMG.nbh" and put is in SD card and flash it.
For information on how to flash using SD card here .
You can get my sample rom here.
*********************************************************************************************************************
FOR THOSE WHO WANT TO PUT CAB FILES IN THE ROM.
*********************************************************************************************************************
Step1:
Put the line in Config_AP.txt the line "CAB: \WINDOWS\FM-Radio_Panel_MR1_R19_32318_signed.CAB" . It has to be exactly as the cab file name that you are going to put in the OEM folder.
Step2:
Make 2 folders "PACKAGE_Kovsky_FMRadioPanel" and "PACKAGE_Kovsky_FMRadioPanel_0409" in the OEM folder. Put your cab file in the first folder.
And now you are good to go.
Step3:
Open KovskyKitchen.CMD and start the procedures "Step 4: Building OS "from my guide.
************************************************** ********
Step 4: Building OS
1. Go back to CMD window and
2. Type "C" cook a rom.
3. Type "A" if you want to use the old BuildOS.exe (I can't figure out the second one)
4. BuildOS windows will appear.
5. Just click on green "Play" icon and It will start building our rom. Wait until it finishs and closes the "Build OS" window.
6. Go back to CMD windows again and wait until you see "press any key to contine".. press any key..
7. It will do some stuffs and you will see os-new.nb in the kitchen folder.
8. htc rom tool windows will appear.
Go to Rom Builder TAB. Choose Kovsky * in device. It will fill all the infomation in other fields. Just change the version to anything you like.
9. Choose "os-new.nb" in the OS field. and click on "Build" button.
10. Save it as "RUU_Signed.nbh" in the kitchen folder. A new window appear and it will quit itself.
11. Now. you will see "RUU_Signed.nbh" in the kitchen folder.
12. An Hexa Editor windows will appear. Just close it.
13. You can close CMD window now.
************************************************** ************************************************** *****************
FOR THOSE WHO WANT TO PUT OTHER HTC DEVICE'S STUFFS IN THE ROM. (For example "Blackstone" HTC Touch HD)
************************************************** ************************************************** *****************
Step 1: Exact other device's ROM the same procedure as X1 rom.
Step 2: Simply copy folders from Blackstone kitchen's OEM folder to X1 kitchen's OEM folder. For example:
PACKAGE_Blackstone_AudioBooster
PACKAGE_Blackstone_AudioBooster_0409
Step 3: Follow the step 4: Building OS from the guide.
Working Stuffs:
Album
AudioBooster
AudioManagerEngine
Enlarge Startmenu
MP3 Trimmer
FMRadio
Manila
JetCet Print
LargeTitalbar
Volume Control
AdvancedNetwork
Not Working Stuffs: (May need shared files from other folders or tweakings)
Camera (I simply use X1 camera application . Copy \Program Files\CameraRunner.exe to \Windows and rename it to "Camera.exe".)
Youtube (You can simply install Youtube program that has been modified)
CyberonVoice Commander
Nice work!! Downloading at the moment, and see what your guide brings me
wow,that's what i'm looking for!
thanks for the work
How to cook rom 101.. This is what i've been looking for.. Thanks TS.
Brilliant, someone should sticky this.
Been wanting to try cooking my own rom for a while but didn't know where to start. Your example is pretty much exactly what i've been looking for in a cooked rom, strip out all the media junk but not mess with anything else.
What do I have to do to get UC working, is it just a case of having SDConfig.txt on my storage card or do I need to add something to the rom?
Any chance of a part 2 for how to add cab's to the rom? I would like to add a few light weight essentials such as blackstone dialer, fm radio & volume control to mine.
Nice Thread...I will try it later after work...
"Make config.txt writable and delete
"XML: \WINDOWS\fileoperations.xml" line and Make the file read only again.
Delete all files that are larger than 22 KB except "Xperia Black.tsk", because i like Xperia black theme."
One question...what do you mean "make config.txt writable?"
MykeChester said:
One question...what do you mean "make config.txt writable?"
Click to expand...
Click to collapse
In file properties, untick "read-only"
Q
a good guide.Thanks!
thank you very much
Actually, I have never tried to use UC yet. I just install whatever I want manually. Using UC should be quicker to install things. Great chefs like ITJE and Jack should know better. Please search their threads for UC stuffs.
For putting the cab files should be relatively easy. We can do reverse exactly how we stripped them out.
For example , you can do the following if you want to put FM Radio panel back or any other cabs you wanted to include in the rom.
But for me, I want the rom as light as possible and to get the largest storage space, I don't bother to put them in the rom. If I want them, I just install them manually.
Step1:
Put the line in Config_AP.txt the line "CAB: \WINDOWS\FM-Radio_Panel_MR1_R19_32318_signed.CAB" . It has to be exactly as the cab file name that you are going to put in the OEM folder.
Step2:
Make 2 folders "PACKAGE_Kovsky_FMRadioPanel" and "PACKAGE_Kovsky_FMRadioPanel_0409" in the OEM folder. Put your cab file in the first folder.
And now you are good to go.
Step3:
Open KovskyKitchen.CMD and start the procedures "Step 4: Building OS "from my guide.
**********************************************************
Step 4: Building OS
1. Go back to CMD window and
2. Type "C" cook a rom.
3. Type "A" if you want to use the old BuildOS.exe (I can't figure out the second one)
4. BuildOS windows will appear.
5. Just click on green "Play" icon and It will start building our rom. Wait until it finishs and closes the "Build OS" window.
6. Go back to CMD windows again and wait until you see "press any key to contine".. press any key..
7. It will do some stuffs and you will see os-new.nb in the kitchen folder.
8. htc rom tool windows will appear.
Go to Rom Builder TAB. Choose Kovsky * in device. It will fill all the infomation in other fields. Just change the version to anything you like.
9. Choose "os-new.nb" in the OS field. and click on "Build" button.
10. Save it as "RUU_Signed.nbh" in the kitchen folder. A new window appear and it will quit itself.
11. Now. you will see "RUU_Signed.nbh" in the kitchen folder.
12. An Hexa Editor windows will appear. Just close it.
13. You can close CMD window now.
**********************************************************
Hope this help.
i_am_jon said:
Brilliant, someone should sticky this.
Been wanting to try cooking my own rom for a while but didn't know where to start. Your example is pretty much exactly what i've been looking for in a cooked rom, strip out all the media junk but not mess with anything else.
What do I have to do to get UC working, is it just a case of having SDConfig.txt on my storage card or do I need to add something to the rom?
Any chance of a part 2 for how to add cab's to the rom? I would like to add a few light weight essentials such as blackstone dialer, fm radio & volume control to mine.
Click to expand...
Click to collapse
@htainlin
Thank you greatly for these posts - they are very clear and concise.
Most of all, they are explicit and very helpful. Trying to obtain a "road map" of ROM cookery is very frustrating - it's all a "big secret", where you are advised to read and read etc, but the multifarious references are truncated, incomplete, chaotic and contradictory. You've helped enormously in cleaning up this mess.
Straightforward now - generic RA3 versions will turn up sometime.
Re UC:
I use this to re-install most apps after a new ROM flash (see Jack Leung's thread for my posts). The only real hassle for UC are those apps that splatter files on installation to both the SD card and Storage. There is a huge thread on UC with most questions answered in one fashion or another, but it takes patience to sort through it. Having done it once, you need only update your sdconfig.txt as you add/remove apps over time.
Nice post!
However if you really want to make a streamlined rom use Ervius Visual Mulitlang Kitchen
http://forum.xda-developers.com/showthread.php?p=3147148#post3147148,
The GUI is pretty neat, and it uses Bepe's new kitchen system to get rid of extra gumpf in the roms (such as dsm files).
this then optimizes it a bit as /windows has less files in it. Ergo it does things faster.
this will also work with the newer format roms coming I think.
ianl8888 said:
@htainlin
Thank you greatly for these posts - they are very clear and concise.
Most of all, they are explicit and very helpful. Trying to obtain a "road map" of ROM cookery is very frustrating - it's all a "big secret", where you are advised to read and read etc, but the multifarious references are truncated, incomplete, chaotic and contradictory. You've helped enormously in cleaning up this mess.
Click to expand...
Click to collapse
There's no "big secret" the reasons you've stated are the reasons people tell you to read. If there was one post to point people to then don't you think people would have done it?
It takes a lot of time to do the work that htainlin did, which is why most people dont get around to doing it all.
htainlin stick it in the WIKI.
Very rom cooking guide for beginner
Nice work. I did something similar for Asus P525 long time back and I know it's takes a lot of effort to bring everything together, and explain the subject clearly for beginner.
This is a very good starter "re-cooking" document for beginner. There is no "big secret" for rom cooking. All you still need to do is research and read a lot more to do some hardcore stuff for the next level. e.g. remove unnecessary driver/service/registry Welcome center / Customer Satisfactory ...etc, replace driver w/ other device to get more functionality. Then XIP/Sys port .....etc
Thanks guys. I am not really into cooking.
My goal is to take the "Unwanted Stuffs" out from the rom so that the storage will be larger and just a small guide to everyone who wants to make their rom lighter. Everyone should be able to do it themselves for their likings to any future rom versions.
There is "NO BIG SECRET" for rom cooking. But for beginners, it is really hard to figure out how to use "Kovsky Kitchen". Once you are experienced, it's quite easy.
But for advanced stuffs as Jack mentioned.. we need more research and skills. I might write a detailed guide later, how to edit registry and replacing better dlls and applications.
Everyone has his/her own preferences and I just want to show them even a beginner could do themselves.
Windows mobile is the best ever mobile os for me so far and you can modify anyway you like. Thanks to many developers who created kitchen and make things easy for us.
how to's...
here are some of the how to's i stumbled on ppc geeks. hope this enlighten some in modding/customizing roms:
1. how to's for developing
2. adding registry entries (rgu method)
twisted said:
here are some of the how to's i stumbled on ppc geeks. hope this enlighten some in modding/customizing roms:
1. how to's for developing
2. adding registry entries (rgu method)
Click to expand...
Click to collapse
Thanks for the links. Very good.
There is no need to do such a hard job - to extract & rebuild all the ROM file.
Just take HTC Rom Editor, open your ROM there, clear all useless stuff and correct files
config.txt
config_AP.txt
config_operatior.txt
config_SP.txt (if exist)
fileoperations.xml
runlua.cc
Then save your rom and flash it. Easy way.
PS: My custom rom with cleared "stuff" (even SE Dialer) and some features is about 65MB, and makes about 360+MB free memory.
Great job! Big help to us new to WM and ROM cooking. Thanks, mate!
+1 to make this thread sticky
great write up. got a couple questions tho.
what effect does deleting the \windows\fileoperations.xml have on:
ringtones? will you have to maually load your ringtone, like for my alarm, notifications (mail, sms)
internet explorer start page?
startup animation?
panels? will i still have the se1 and 2 panels? how about the today panel?
thanks,
claudio
TotalFire's ROM Cooking Guide
I have been requested to write a simplified guide on how to cook ROMs For Xperia, as I have just started please be patient and ignore any empty posts for now.
This guide is for anyone who wants to learn how to cook ROMs for Xperia, you dont need any knowledge other than being able to flash a ROM on your Xperia
If any of the information stated is incorrect please tell me and i'll change it.
Tutorial Layout:
1: Tutorial Layout
2: Setting Up The Kitchen
3: Cooking Your First ROM
4: Customizing Your ROM
5: Customizing Using Autorun
6: Fixing BuildOS Error's
Credits:
Bepe & Gtrab for the kitchen
Anyone else I forgot to mention
Setting Up The Kitchen
The Kitchen is where all the files in the ROM are kept and where there put together into a ROM which is flashed. There are mainly two types of kitchens, an automated kitchen and a visual kitchen, in this tutorial I will be using a automated kitchen which was made by bepe and modified by gtrab. The only modification I did to the kitchen was to make it rename the ROM to RUU_signed.nbh so that it could be flashed from the PC. in this tutorial I will explain the filesystem used in the kitchen.
In the root of the kitchen you will find 4 folders, they are OEM, SYS, ROM and Tools, below I will explain whats in each folder and what it does.
OEM
The OEM folder contains all the customizations made by the OEM or in this case chef. In the folder you will find lots of folders which begin with PACKAGE, these are most often applications, registry changes or both. The name can indicate which phone they come from for example a package which is called "PACKAGE_Kovsky_Camera" comes from the Kovsky (Xperia) and a package called "PACKAGE_Rhodium_PhoneCanvas" comes from the Rhodium (Touch Pro 2). Inside a Package you could find many different filetypes, every package has at least a dsm file inside, this is a identifier file. The dsm files name will have loads of random numbers and letters in such as "d9dd6d62-02d6-48d7-9764-18ac81aff3ad.dsm", this is it's unique identity no other package will have the same ID. Most Packages will also have a rgu file, an rgu file contains registry changes for the device, a package can contain only one rgu file and it must have the same name as the dsm file. Make sure when writing a rgu file to have the first line say "REGEDIT 4" and the last line must be empty, if this is not done the rgu will be ignored. One more filetype to look out for is a provxml file this contains registry changes just like the rgu but can be called anything and you can have as many provxml's as you want in a package, the registry edits are written in xml. The last file to look for is an "option.xml" file, these are used only by the kitchen to tell it if the package should be used, these are not needed but without one the kitchen uses the package without giving you a choice. The "option.xml" files can be made manually or generated with Ervius Package Creator but its easy enough to make it manually so I usually do. OEM Packages can be extracted from official ROMs and unprotected ROMs, you can also convert cab's into oem packages using Ervius Package Creator or doing it manually, later on in the tutorial I will add a guide on how to using Ervius Package Creator (manually doing it is too complicated). CABs can be installed without converting them to OEMs but the more CABs you have the longer it takes for the customization to finish when you first install the ROM, I will also show you how to install CABs without converting them to an OEM in a later tutorial, the use of this is if a CAB doesnt convert properly with Ervius Package Creator and you dont want to convert it manually.
ROM
In the ROM folder you will find the folder XIP and the file "OS.nb.payload", the "OS.nb.payload" file contains things such as the splashscreen, usually this file is not edited and the splashscreen is overwritten by a package in OEM. The "OS.nb.payload" is usually changed when upgrading the SYS folder because "XIP.bin" contains the kernel files which is inbuilt in the "OS.nb.payload" file. In the XIP folder there is boot.rgu file which contains registry entries used by windows mobile and isnt used by the OEM or chef, it is used exactly as an rgu file would in a package in the OEM folder. When upgrading to a new build of windows mobile this folder will be upgraded, it will need to be ported properly to xperia for it to work but i'll add a guide for that in a later tutorial.
SYS
The SYS folder contains all the files used by windows such as themes and applications like office mobile. Inside the SYS folder there are many other folders such as MediaOS (Windows Media Player) and WindowsLiveIM(Windows Live Messenger) These are basically packages made by windows similar to the OEM packages. I dont need to go into as much detail as I did with the OEM because the only time you use this folder is when you either swapping images to change skins or upgrading the windows mobile build. I will show you how to upgrade the SYS folder in a later tutorial because some of the files in SYS are device specific and resolution specific so you cant just take a SYS folder and overwrite your old one.
Tools
The Tools folder contains all of the applications the kitchen uses to build a ROM. I dont need to go into any detail because you never need to touch any of the files in the Tools folder but if you intrested, you can open the cook.bat file in the root of the kitchen which should tell you more about which applications do what.
Other than the 4 folders in the root of the kitchen is 4 files, they are Cook.bat, CustomRUU.exe, SYSVersion.exe and XVI32.exe Shortcut, below I will explain what each file does.
Cook.bat
This files runs all of the tools in the kitchen to build to ROM.
CustomRUU.exe
You should have seen this file before, it is used to flash a ROM
SYSVersion.exe
This application checks the version of each individual SYS folder, useful to check the SYS build
XVI32.exe Shortcut
This application is used to HEX edit files, this can be used to HEX edit the ROM to change the default date, i'll show you how to do this at a later date.
Download the Kitchen Here
Cooking Your First ROM
I feel the best way to learn to cook ROMs is to get familar with the cooking process. In this tutorial you will cook a ROM using Gtrabs/Bepes kitchen and end up with RUU_signed.nbh will can be flashed on your xperia, hopefully this will give you an sense of what cooking is like.
Step 1
Extract the kitchen you downloaded in post 2 to any place on you computer, I have my kitchen on the desktop. Please make sure you have framework 3.5 installed onto your pc as its required.
Step 2
Run the file Cook.bat, a command prompt will open up shortly followed by a application called BuildOS. BuildOS lets you chose which packages to cook in your ROM without having to delete them every time. Only packages with an option.xml file will be shown meaning if its not there it, you will have to make one or else it will be cooked in without giving you a choice. As this is an early tutorial i recommend you like all packages in for now incase you remove required packages accidently. Now press the play button and wait until it says at the bottom left corner "done", once "done" appears close BuildOS.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Step 3
After closing BuildOS, two Command Prompts will open, wait for one to close. Once one has closed you'll have one command prompt asking for you to chose a compression method, like in the picture below. What you do is press enter and an application called XVI32 will open, this is an HEX editor. Now you need to choose which compression method you want LZX or XPR, LZX compresses the ROM much better than XPR but takes longer to cook the ROM, most often I compress with XPR when testing but use LZX when releasing a ROM. All you do to change compression is look at the HEX editor it says either LZX or XPR, if it says LZX and you want XPR, change it to XPR, save and close and vice versa. After closing XVI32 There will be loads of white scrolling text wait for it to stop moving.
Step 4
You will now have a comand prompt, like below just press enter and wait for it to close. Congratulations!, you have just cooked your first ROM, if you would like to test it plug in your xperia and run CustomRUU.exe and just flash the ROM like you normally would.
Now that you've cooked a ROM you can try cooking another while removing some packages and following any customization suggestions in post 4Click Here
Customizing Your ROMThis Tutorial Contains Various Mini Tutorials On How To Customize Your ROM
How to change your ROMs Name
In the kitchens tools folder there is a file called nbhgen.txt, edit the third line (which says "SEX1.R3" by default) to the new name of your ROM
In the kitchens OEM\OEMVersion there is a rgu file, edit the line in the file "ROMVersion"="SEX1-r3.61-XprT" changing "SEX1-r3.61-XprT" to the new name of your ROM
Note: Your ROM name can have a maximum of 16 characters and no more, change both of the above to chnage your ROMs name
How to change your ROMs Boot Screen
In the kitchens SYS\Redist_dpi_192_resh_480_resv_800 folder there is a file welcomehead.192.png which is the phones boot screen
Only the first 480 x 800 pixels are used from the image taking from the left side of the image
Adding Extra OEM Packages
Simply take the package and place it in the OEM folder of the kitchen
Some packages have a language package with must be cooked also for example "PACKAGE_Kovsky_Camera" & "PACKAGE_Kovsky_Camera_0409"
OEMs can be extracted from Stock ROMs and some custom ROMs (if there unprotected), I will show you how to extract ROMs in a later tutorial
Upgrading Windows CE Build (SYS)
Replace packages from your old SYS folder with ones from the new SYS folder
Dont replace the folders ".VM" or "WinCENLS_WWE" because they are unique to that device
Dont replace files with resolution packages with newer resolution packages of a different size, for example "Redist_dpi_192_resh_480_resv_800", this is for a phone with resolution 480 x 800, so dont replace it with something like this "Redist_dpi_192_resh_480_resv_640"
The same goes for DPI, make sure the new package is the same DPI as your old one, for example "Base_DPI_192" this package has a DPI of 192, dont change it to something like this "Base_DPI_96"
Finally packages that contain language files must be replace with files of the same language or else the OS will be in another language, for example "Browsing_Lang_0409" this package is and english package (0409 is english) so dont replace it with something like this "Browsing_Lang_0407"
Changing The ROMs Default Date
After cooking a ROM, open XVI32 in the root of your kitchen
Click File > Open and select the "RUU_signed.nbh" file from the root of your kitchen
Press Ctrl and F, and search for "Jan"
Below the line its selected there should be something like "Apr 23 2009", Change it to something like "Aug 18 2009"
"Apr" stands for April change it to the first 3 letters of the month you want to change it to
Customizing Using AutorunThis Tutorial Is Not Finished, Please Ignore It
In most ROMs, there is a customizing screen which is shown just after the ROM is cold booted (ran first time or ran after hard reset). This is where all the CABs are installed, theme is set and the last registry entries are added. In this tutorial I will show you how to use autorun to customize your ROM.
First in the kitchen go into the OEM\OperatorPkg folder.
Installing CABs With Autorun
First place the CAB you want to install into the OEM\OperatorPkg folder
Open either config.txt or config_operator.txt, I would use config.txt
Add line in between "LOCK:Enabled" and "LOCKisabled", "CAB: \WINDOWS\your_cab_file.cab" replacing "your_cab_file" with the exact name of the CAB.
Remeber the more CABs you have, the longer it will take to customize, so only use it if converting it to a package doesnt work.
Installing TSKs (Theme's) With Autorun
First place the Theme you want to install into the OEM\OperatorPkg folder
Open either config.txt or config_operator.txt, I would use config.txt
Add line in between "LOCK:Enabled" and "LOCKisabled", "TSK: \WINDOWS\your_tsk_file.cab" replacing "your_tsk_file" with the exact name of the TSK, this changes your default theme
Put as many themes as you want in the OperatorPkg folder, they will all be added into the list in today settings
following every word!!
Very nj!
It's all clear and easy to follow: the perfect tutorial!
I was waiting for this for long time, thank you!
well done TotalFire, keep the high spirt
great work...i can finally understand how this works! When will you release another tutorial? I would love to know how to put programs in your rom (or the packages, for that matter) install skins or a connectio nsetup which runs automatically....
love this!
I'll try and release a few tommorow.
Does anyone know if its possible to disable smilies in a post?
yes when u reply click go advanced .then u click disable smilies in text!
rotastrain said:
yes when u reply click go advanced .then u click disable smilies in text!
Click to expand...
Click to collapse
Thank You
--------------
Totalfire , i believe after you finish this tutorial any beginner can cook his own rom with his own recipe
so please continue the same SIMPLE wording
thanks M8
I will, just need a bit more time
Please request tutorials, and i'll make then. Dont know which one to make next.
Nice tutorial I'm using Visual kitchen myself but nice tutorial for old style
killer8nl said:
Nice tutorial I'm using Visual kitchen myself but nice tutorial for old style
Click to expand...
Click to collapse
Ive just started using the visual kitchen, didnt give it much of a try last time. Seems good so far.
Fixing BuildOS Error's
While cooking ROMs you are very likely to come across error's, this post will show how to fix some of them.
Default.hv And User.hv:
Open the file temp\log.txt, and scroll to the bottom of it
Look at the second last line, there should be an error message with the name of a rgu file
Higlight the rgu file and copy the name to clipboard
Search the root of the kitchen with the text you just copied from the last step
Look at the folder it says and open the rgu, there is a problem in there you need to fix
As i have switched to visual kitchen, it would be easier for me to make guides for that, would anyone prefer me to continue making a guide for the old style kitchen. BTW visual kitchen, is easier especially for thing like porting SYS and ROM.
if i need to remove anything from the OEM before cooking (like a panel), just delete the item? or is there another task i must perform as well?
BTW thanks for this tutorial, this is soo damn simple, nuff respect to you dude
im trying to extract some cabs from a NHB file...can anyone guide me in the direction on how to do this
I'd say the best way to do that is to extract the ROM into regular files.
You need to download a bunch of EXE files: NBHextract.exe, NBSplit.exe, ImgfsToDump.exe, and ImgfsFromNB.exe
You need to extract the NBH with NBHextract.exe. This will yield a .nb file
You need to use NBSplit (use the "-kaiser" parameter) to split the .nb into a .nb.payload file and a .nb.extra file
You then need to use ImgfsFromNB on the .nb.payload file, which will create a file called imgfs.bin
Use ImgfsToDump on imgfs.bin, which will create a folder called "Dump". When it finishes, All of the ROM's files will be there. You will probably want to search the folder for .cab files, since there are thousands of files in the average ROM dump.
That should do the job for you.
Or just use Visual Kitchen to Dump the ROM, and then rebuild the OEMs to CABs.
Dave
could u walk me through the visual kitchen program?
Hmmm look for htcRIE_0.4.0.47 and extract what you want.
im trying to extrct the streaming media player cab...the one thats in most of the 6.5 roms that has a look a like HTC ablum look to it, but i cant find a cab using "htcRIE_0.4.0.47"
little help will might ...
You do not search for it at you WM ROM,
Search at the site...
Anyway i have been find it for you !
A newer version of htcRIE, enjoy!
michealmyers said:
im trying to extrct the streaming media player cab...the one thats in most of the 6.5 roms that has a look a like HTC ablum look to it, but i cant find a cab using "htcRIE_0.4.0.47"
Click to expand...
Click to collapse
i have that program, but im unsure on how to properly use it to get the cab files.....can u help me?
michealmyers said:
i have that program, but im unsure on how to properly use it to get the cab files.....can u help me?
Click to expand...
Click to collapse
With Visual Kitchen, just click on the Dump button at the bottom - and then browse to the NBH file .
Dave
i guess all nbh files dont have cabs because in the dump folder it creates...its only a couple of cabs and whole lot of systems files
michealmyers said:
i guess all nbh files dont have cabs because in the dump folder it creates...its only a couple of cabs and whole lot of systems files
Click to expand...
Click to collapse
Yeah, you have to rebuild the EXT packages to CAB's I don't know if there is a tool for that actually. Might be better dumping it the Dave (TyTNII) way, that will give you OEM's. There are tools for OEM 2 CAB.
Jason8 is working on a tool to convert all 3 all ways IIRC.
Dave
the nbh extract file launches for a quick second...it doesnt stay on the screen, as well as a lot of other files such as nbh split....do i need to update something in order to have these programs run properly?
michealmyers said:
the nbh extract file launches for a quick second...it doesnt stay on the screen, as well as a lot of other files such as nbh split....do i need to update something in order to have these programs run properly?
Click to expand...
Click to collapse
You have to run them from the windows command line (CMD.exe). If you really want me to, I'll upload a batch file I made which automates most of this. You just put the NBH and tools in certain folders and run the batch file and it does the rest.
DaveTheTytnIIGuy said:
You have to run them from the windows command line (CMD.exe). If you really want me to, I'll upload a batch file I made which automates most of this. You just put the NBH and tools in certain folders and run the batch file and it does the rest.
Click to expand...
Click to collapse
that would be so helpful
Alright, I fixed all the bugs in it (it was still in progress) and added some new features I had meant to add for a while, such as renaming the processed files by date processed (though you probably won't need them if you're only extracting one ROM). Hit [WINDOWS KEY] and R on your keyboard at the same time to open the Windows Run dialog, and type "%USERPROFILE%" without the quotes. Simply unzip the file and drag the folder called "Flashing" in the user folder (it's vital to have the Flashing folder in the correct spot. Otherwise, the entire script will fail). Place the NBH file you want to extract in the NBHDUMP folder (in the Rhodium folder, which is in the Flashing folder), and go to the IMGFS folder (in the Rhodium folder, which is in the Flashing folder). Now, run RhodiumRomDump.bat and the dump should commence, and a folder with your dump should appear in the same directory.
If anything should go wrong, please tell me so I can try to fix it.
EDIT: Please redownload, all issues I could find are fixed in this version. If you get errors about needing MSVCr71.DLL with this version, google is your friend.
maybe im not doing something right, ive been at it for days now...i put the "flashing folder" in C:\Documents and Settings\Sean (sean's my name..haha), put the nbh file in the NBH folder, ran "DumpRhodiumRom", i got 2 folders named "and" and "Setings"....when i run "dumpRhodiumRom", its just stays on the screen for half a second
ive extracted the rom before using visual kitchen...im trying to get some of the programs into cabs...the problem is that in the dump file, i see the programs i want, but they arent in cabs, so i cant just take its "exe" file and put it into another phone (well at least that didnt work for me)
michealmyers said:
maybe im not doing something right, ive been at it for days now...i put the "flashing folder" in C:\Documents and Settings\Sean (sean's my name..haha), put the nbh file in the NBH folder, ran "DumpRhodiumRom", i got 2 folders named "and" and "Setings"....when i run "dumpRhodiumRom", its just stays on the screen for half a second
Click to expand...
Click to collapse
That's odd. Can you tell me two things?
Where do these folders ("Settings" and "And") show up?
Hit [Windows Key] + R and type "CMD" (without quotes), then hit okay, then type "cd %USERPROFILE%\Flashing\Rhodium\IMGFS" (without quotes). Now, type "DumpRhodiumRom" (without quotes), and tell me exactly what is says (you don't actually have to include all the formatting and everything). Also, if you could tell me what color it's in, that would help.
I'm going to test it in a virtual Windows XP environment and see if it's compatiblity with XP that's the problem.
EDIT: So the problem seems to be the fact that it doesn't like the spaces in the folder name "Documents and Settings", hence the creation of the "and" and "settings" folders. Unfortunately, it's an important folder, so renaming isn't really possible. However, I think I know a simple fix to the original script, so I'll test that and post it shortly.
michealmyers said:
ive extracted the rom before using visual kitchen...im trying to get some of the programs into cabs...the problem is that in the dump file, i see the programs i want, but they arent in cabs, so i cant just take its "exe" file and put it into another phone (well at least that didnt work for me)
Click to expand...
Click to collapse
Try downloading cabtools V 0.3 and use pkg2cab to build the package back into a .cab file. I've never done it myself, but this looks like what you want.
DaveTheTytnIIGuy said:
That's odd. Can you tell me two things?
Where do these folders ("Settings" and "And") show up?
Hit [Windows Key] + R and type "CMD" (without quotes), then hit okay, then type "cd %USERPROFILE%\Flashing\Rhodium\IMGFS" (without quotes). Now, type "DumpRhodiumRom" (without quotes), and tell me exactly what is says (you don't actually have to include all the formatting and everything). Also, if you could tell me what color it's in, that would help.
I'm going to test it in a virtual Windows XP environment and see if it's compatiblity with XP that's the problem.
EDIT: So the problem seems to be the fact that it doesn't like the spaces in the folder name "Documents and Settings", hence the creation of the "and" and "settings" folders. Unfortunately, it's an important folder, so renaming isn't really possible. However, I think I know a simple fix to the original script, so I'll test that and post it shortly.
Click to expand...
Click to collapse
This is What i got....where the "and" and "settings" folder apear is "untitled2.zip"