Related
Ok since alot of people are getting more and more interested in cooking thier own roms I thought I might make a post with my vast knowledge (or lack there of) to help the newbies who dont want to do as much reading as I did. I was a newb too and wish i saw this somewhere, hence why i wrote it. LOL.
Attached are all the files youll need {minus the nk.nbf}
To save myself the headache:
You have to be on IPL/SPL versions 2.xx or better.
20 Steps to Cooking your own ROM
The legal stuff:
This guide comes with no warranty and is based off the fact that you have a G3 wizard CID/SIM unlocked.
I provide no support for phones, ROMs, or pretty much anything else. Im always willing to give advice but
im not the ROM building GOD. If you brick your phone while following this tutorial, I cannot be held responsible.
If you have a lose of limb or life while using this guide, I cannot be held responsible.
Step 1.
Extract nottoosmart_cooking.zip to C:\ROM
Step 2.
Copy nk.nbf to C:\ROM
Step 3.
Open DOS prompt by going to Start>Run>CMD
Once in DOS Prompt simply type in cd
Code:
C:\ROM
Step 4.
This extracts all the seperate parts of the ROM
Code:
typho5.exe -x nk.nbf
Step 5.
This dumps the files to a folder called dump. Made it one batch to minimize on the typing. This batch does 2 commands which prepares the image then dumps it
Code:
Dump.bat
Step 6.
Copy default.hv and user.hv to the C:\ROM folder
<edit: Located in the dump folder created by Step 5. Remember most of these files you will want to edit will be read-only and hidden. So turn show hidden on and modify the properties to turn read only off. Only on these 3 files; initflashfiles.dat, default.hv and user.hv>
Step 7.
Code:
"HV to TXT.bat" default.hv
Edit default.txt in notepad. Save as Unicode {important: make sure its unicode and turn off wordwrap} and make sure the last line is blank.
Step 8.
Rename default.txt to boot.rgu
Step 9.
Code:
make_boot_hv.bat
This changes it back to an hv file.
Step 10.
Rename the newly generated boot.hv to default.hv
Step 11.
Repeat steps 6 through 9 for the user.hv {important: change default.hv to user.hv this time}
Step 12.
Use Notepad to work in the initflashfiles.dat and make sure that the last line is blank as with the default.hv and user.hv
{this file tells where to put files and such during a hard reset or initial instal}
Step 13.
Open initflashfiles.dat with WinHex {or any other hex editor} and delete the first 2 bytes {thats the first 4 characters}
{make sure you change the file properties for initflashfiles.dat to remove the read-only tag or else you wont be able to do this step}
Step 14.
Code:
Build.bat
This will build and package the ROM back into the 8004000-OS.nb
Step 15.
Run nb2nbf_tornado.exe
Fill in with the information below:
Code:
Model id: Wizard
Language: WWE
OEM Version {can be left blank}
Operator Version {can be left blank}
CID: Blank {must be left blank}
Step 16.
Set output file {should default to C:\ROM\nk.nbf}
Step 17. {follow this step exactly or you will brick your phone}
File #1 point to: 80040000-OS.nb
Start address: 80040000
Image Name: OS
{below I will list other known parts of an image that you may have with correct information if needed}
Step 18.
Click the Translate Button
Step 19.
Move the newly created nk.nbf to the C:\ROM\Wiz_Flash_Util folder
Step 20.
Run ROMUpdateUtility_Wizard_NoID.exe and sit back and watch.
During this process the update will stall at some point {differs between ROMs} just be patient and let it finish
Enjoy your hard work!!!
***
As promised, here are the diffrent parts for a ROM and the correct start addresses and Image Names.
{Dont stray from these or you will brick your phone}
Image Name: Extension Rom (aka the Extended ROM)
Start Address: 9b000000
Image Name: HTC (No idea what this is, but Molski uses it so I'm adding it)
Start Address: 9d000000
Image Name: OS (aka the guts of the ROM)
Start Address: 80040000
Image Name: Splash Screen (need I say more???)
Start Address: 92000000
Image Name: GSM (Radio part of the ROM)
Start Address: 96000000
***
All this information was collected from xda-developers.com and molski.biz forums.
I just made it look all pretty
-NotTooSmart
PS as a side note. You can modify the WM start picture by modifying the welcomehead.96.png. This file is typically hidden also
THANKS !!!!!!!!!
Thanks...Always wanted to go to the next level....now I can really get myself in trouble!
Wow... I've avoided cooking as I wasn't ready to try to put all the pieces together... Dang, I may have to try this now... Just what I need, something else to suck even more of my time away...
Looks like sticky material to me...
Step 6.
Copy default.hv and user.hv to the C:\ROM folder
where do I get those from ?
nottoosmart said:
Image Name: HTC (No idea what this is, but Molski uses it so I'm adding it)
Start Address: 9d000000
Click to expand...
Click to collapse
I would suggest that that is the OEM part of the ROM which is in this case named HTC where all OEM files that are integrated into the OS are put such as Commmanager.exe and certain drivers and control panel extensions.
Very nice guide otherwise.
pencilcase said:
Step 6.
Copy default.hv and user.hv to the C:\ROM folder
where do I get those from ?
Click to expand...
Click to collapse
Those files are located in the Dump folder created after Step 5 completes
ok there is no such file in the pdaviet3 release ... this is weird found it in faria's 3.3 though
pencilcase said:
ok there is no such file in the pdaviet3 release ... this is weird found it in faria's 3.3 though
Click to expand...
Click to collapse
Ok, one thing I should have put on there.....
Most files in these roms are read only and hidden.
To see them make sure that you have show hidden files on.
i used a different rom as base now pdaviet really does not have those files for some reason. I have one issue though. I can add a few rom-parts in nb2nbf_wizard.exe - for instance the extended rom ... see screenshot
my question: how can I add my extended rom?????
pencilcase said:
i used a different rom as base now pdaviet really does not have those files for some reason. I have one issue though. I can add a few rom-parts in nb2nbf_wizard.exe - for instance the extended rom ... see screenshot
my question: how can I add my extended rom?????
Click to expand...
Click to collapse
You have to manually type in the Image name for Extended Rom
Type it in exactly like this Extension Rom if not, hello paper weight
Impossible since it stops typing at
Extension R
...
dazed and confused
i wish to use this tool just to delete or add the programs that i wish to have in the rom
do i have to change registry settings to this
what part of it do i change i got to step 10-11 and did know what to change when i got there if there is a quick answer then please let me know if there is a long answer and it sounds like am in way over my head then tell me know and put me out of my misery
cheers
Anyone tried this?
Scoters Kitcken
http://buzzdev.net/index.php?option=com_phorum&Itemid=125&phorum_query=read,64,29513
pencilcase said:
ok there is no such file in the pdaviet3 release ... this is weird found it in faria's 3.3 though
Click to expand...
Click to collapse
Also, save yourself some grief and don't re-cook someone else's ROM. Cook your own "dinner" off of your provider's official release.
If you really want to "re-heat" Faria's or someone else's ROM, ask them first.
--M
easymob said:
i wish to use this tool just to delete or add the programs that i wish to have in the rom
do i have to change registry settings to this
what part of it do i change i got to step 10-11 and did know what to change when i got there if there is a quick answer then please let me know if there is a long answer and it sounds like am in way over my head then tell me know and put me out of my misery
cheers
Click to expand...
Click to collapse
Ok its not too difficult if you pay attention to how the install goes. What you need is something like WinCE Manager to look at the steps that the install does for that application and put in the required files which you can extract for the cab. also the reg entries are there. initflashfiles.dat is the file that the OS reads after a hard reset and what the file does is tells it where to place files. Im going to write a new addition today to this guild to explain how that file works and how to work in the default.hv and user.hv so that you dont have any problems.
Also with adding files or applications you have to be careful as there is a size limit to the ROM. The build.bat will fail out if you exceed the limit. I learned this while messing with the WM6 MB edition which actually pushes the limit on the size.
demontefixo said:
Also, save yourself some grief and don't re-cook someone else's ROM. Cook your own "dinner" off of your provider's official release.
If you really want to "re-heat" Faria's or someone else's ROM, ask them first.
--M
Click to expand...
Click to collapse
I was not meaning to steal someone elses work but in order to learn the process I prefer to compare how things are done so I dont brick my phone completely.. I guess thats understandable? All I am looking for is a Vanilla ROM with all my personalized apps.
pencilcase said:
Step 6.
Copy default.hv and user.hv to the C:\ROM folder
where do I get those from ?
Click to expand...
Click to collapse
they are in the dump folder
pencilcase said:
Impossible since it stops typing at
Extension R
...
Click to expand...
Click to collapse
Ok, even though it looks like it stopped...... it really didnt. Just finish the "om" and it will be fine
nottoosmart said:
Ok, even though it looks like it stopped...... it really didnt. Just finish the "om" and it will be fine
Click to expand...
Click to collapse
Figured it out ... its
"Extension" without the ""
Hello all,
Apart from Part02.raw, which holds the OS, what do the other RAW files do that get extracted when you dump the ROM from the Trinity? Would I be right in guessing one of them holds the extROM?
Hi there
re: HTC Himalaya. how do I change the first bootscreen? Pls can you give links to tools and provide instructions.
Cheers
I think what you are referring to is the welcome screen? Perhaps do a search for welcome.96 and see what comes up.
I had it in mind you just made an image the size of the welcome screen image and named it welcome.96.png and then just dragged it into the Windows folder (it will overwrite the original).
Having said that, Google it and find out how to do it exactly, don't take my word for it. But you should have enough information frfom what I have said to find out more.
I see its your First post..Welcome to xda-developers..sspecially for choosing Himalaya
To Change the Splash Screen..follow these steps :
Open any Image Editor
or Choose any Image that is 240*320 In Size
Its format Must be .PNG
and rename it to " welcomehead.96.png " (note : png is the extension )
connects your device via Active Sync or copy the splash screen to your Devices and replace place it in the \Windows Folder..it will ask to over right..Select Yes and You are done
Soft-Reset and Enjoy
PS. Search the Forum for ALOT of welcomeheads
the screen I want to change is the very first one that is shown when the machine is turned on, i.e. it appears as the device is booting up. Hope this makes sense.
Oh I suspect then you are not talking about Welcomehead/Splashscreen. Does the screen you are talking about feature the logo or name of a phone company/service provider? IE Telstra, Optus, Sprint, AT&T, Verizon, etc
yes, that's the one. On booting up it is replaced by the welcome screen, and then the wallpaper. I'm using Ather's 'Dark Edition'
i would like to change this very first image too. I hope someone know how to do it.
Hrmm, not sure how possible it is. I have both the o2 logo on one phone and Telstra on the other which I wanted to remove. I dare say it is part of the radio rom, not the OS rom. Basically, you can flash the Radio to a different version, just as you can flash the Operating System, though some say it is a bit more difficult.
No matter what rom I flash, those logos are always there, so I suspect they are part of the radio rom. I will investigate.
EDIT: Okay this guy has created a program to do it for the Prophet only, but he may be the person to ask as I would suspect he had the general knowledge of how to do it by hand before he created the program.
http://forum.xda-developers.com/showthread.php?t=333194
Thoses two can be changed by editing the ExtRom file (ms_.nbf) from a 2003 Rom..Search the forum for WM2003 Edit in the Himalaya Wiki...i have also uploaded a Clean extrom..just replace the images init and then place it in the folder where your HimaUpgradeUT_noid.exe is and flash as normal
here is the ExtROM file : http://rapidshare.com/files/82299532/ms_.nbf
I think this way was working in WM5
Install extromunlocker
Soft reset
Start
Program
ExtROMTools
Unhid
Unlock
Folder will appear in the root
Inside this folder is the image need to be change
But I traied this extromunlocker cab file in WM6.1, I could not find the Extrom.
Thanks for the method - however, I'm new to this and would appreciate a bit more hand-holding if you don't mind. Can you give a more detailed stepwise method?
TIA
It wont work if u ahve Partitioned your DOC..because that was the Storage where these files were kept
Well ok..just tell me what u cant understand
See here ..
Hi,
as Ather described, I did it successfully last year this way
(http://forum.xda-developers.com/showthread.php?t=220799&page=12)
as described, I restored my ExtRom with DOC_Restore, took the T-Mobile 1.72 Update (http://xdazone.india372.server4you.d...d.php?id=3373), extracted the ms_.nbf (ExtROM) , changed the splashes with "Windows Mobile 2003 ROM Editor" and updated the ExtROM. Works well.
I'm not sure if the t-mobile extrom could be used for other version of Himalaya than the MDA II.
Click to expand...
Click to collapse
So long
HonkBB
Anyone know how to open RLE files? I extracted logo.rle from mtd2 boot image but can't open it up.
to565 converts a raw image to rle so could to565 also be used to convert back to raw image????
Anyone got the G1 logo image?????
thanks
logo.rle appears to do nothing as far as I can tell. At one point somebody claimed to have changed the startup G1 screen but I never had any luck.
However, you can add initlogo.rle and it will display that after the G1 screen and before the Android screen. I posted about this here:
http://forum.xda-developers.com/showthread.php?t=443431
alansj, you remember who? Was it on this board???? I can do the android logo but not the g1 logo
thanks
I believe it was dream_kill on #android (irc.freenode.net)
Convert back rle to raw and jpg/png
Hi all,
Please allow me to dig this topic out from the dust.
I had the same need as posted, that is convert back a logo.rle to check it out but only rgb2565 is to be found (as seen on wiki.xda-developers.com/index.php?pagename=HTC_Sapphire_Hacking_2#sec08 or on forum.xda-developers.com/showpost.php?p=3064450&postcount=30
So I took some time and made a quick and dirty hack of the code to reverse the process
Note : This is on linux, I don't have motivation nor time to check the code on mswin system, sorry...
How to convert logo.rle back to png
1°) get the code (I called it from565.c)
View attachment from565.c.txt
2°) compile with
Code:
$ gcc -O2 -Wall -Wno-unused-parameter -o 5652rgb from565.c
3°) find a logo.rle (for example in a recovery.img with the unpacking tool found at forum.xda-developers.com/showthread.php?t=443994 )
4°) give it a spin !
Code:
$ ./5652rgb -rle < logo.rle > logo.raw
5°) OK, now what ? You can use imagemagick to convert the raw to some viewable format.
Code:
$ convert -depth 8 -size 320x480 rgb:logo.raw logo.png
All options are important : it's a raw image so the program cannot guess the bpp, size and format by itself.
6°) Take a look at your logo.png with whatever image viewer you fancy
Caveats :
Unfortunately, the code, as its rgb565 parent, does a lossy conversion (you can't stuff 3x8 bits of raw rgb into 16 bits of rgb565 without some cutting one way or another...), so do not hope to retrieve the EXACT image that generated the logo in the beginning, and avoid to convert it back and forth several times. but it's still nice to KNOW how the d*mn file looks like !
Cheers all and many thanks for the forum and community of xda-dev !
zebarbu
Moved as not Android Development.
Thank you zebarbu! Using your code I successfuly convert Samsung Galaxy Ace boot logo to png, edit it and convert back to rle.
dellio said:
Anyone know how to open RLE files? I extracted logo.rle from mtd2 boot image but can't open it up.
to565 converts a raw image to rle so could to565 also be used to convert back to raw image????
Anyone got the G1 logo image?????
thanks
Click to expand...
Click to collapse
Could u say how u extracted the boot.img file to get cooper.rle ???
and i downloaded ur file and tried edittin it worked for me..... but the prob is i hav no idea on how to extract the copper.rle from boot.img
http://android-dls.com/wiki/index.p..._Images#Structure_of_boot_and_recovery_images
This is how you can extract it
Been looking for a way to view them/convert them, anyone got any luck with this?
Oh worked great, stupid me just didn't think about the image being 480x800 sometimes on my O3D =D
Works great
Can someone give me the working download link of to565 ? Please
Here comes compiled version of file
Here comes compiled version of file
Before i get flammed like crazy. I have searched for guides to cooking roms and used all different kinds of kitchens but none seem to work at all. Unless there is something written between the lines that i can't see i just don't think i'm doing anything wrong.
Anyway. When I try an build a rom and create the os-new.nb file imgfsfromdump just crashes and i can't create the file. Sometimes it works but once it fails it doesn't start working for a long time. I'm not sure what i'm doing. I try and dumb a stock rom and rebuild exactly the same but the same thing happens.
If anyone with some xip|sys porting could give me a hand to get past this step i'd appreciate it.
Thanks..
I'm starting to believe it might be a conflict with SP3. Can anyone confirm that they have these kitchens working with SP3?
replace your ImgfsFromDump with the attached version
itje said:
replace your ImgfsFromDump with the attached version
Click to expand...
Click to collapse
Thanks itje. I tried this but it still crashes everytime i try and compile the files. I'm not sure why. Is there something i could be doing wrong? Have you seen this before?
Did ImgfsFromDump ever work for you? (That is, did you try just extract and create the image without modify any content)
For me, I am not following the script in the kitchen completely to create the image. Here is what I execute on the temp directory (w/ dump as sub-directory) and work fine so far. (just make sure you did not remove the imgfs.bin and the payload in extracting the image)
..\TOOLS\ImgfsFromDump imgfs.bin imgfs-new.bin
..\TOOLS\ImgfsToNb imgfs-new.bin os.nb.payload os-new.nb.payload
..\TOOLS\NBMerge -kaiser os-new.nb
Strangly enough it did work a couple of times then i just started getting that error that says "imgfsfromdump needs to close" that basic windows error. I thought it might have been DEP but i made a exception for that program. I'm going to try this and see if i have the same problems.
I'M SUCH AND IDIOT!!! The reason it was crashing is cause i kept building the dump into packages. So i assume it was looking for files in the wrong place which just causes the process to fail. Thanks guys!!!
Can someone help me find this 21109 build to where i can actuallyt port it? I've tried to extract it from various roms and all it does is fail everytime and my phone is stuck at the sony screen.
*******EDIT******
I finally figured out how to get XIP ported but now i'm having a problem with the SYS folder. No matter what SYS folder i use and no matter how many different tutorials i go through i still get the same point. I flash and it sits at the sony ericisson symbol and does nothing. Is there some folders i shouldn't change in the SYS?
run g'reloc on the stock sys folder from x1, note all the values..
then run g'reloc on your new UNTOUCHED sys, where you change NOTHING...no swapping of files (unless you port from vga or qvga, or change locale, but thats another story) then change the values on the new sys with the values from the stock x1 sys, apply changes, and you have ported the sys.
cheers
itje said:
run g'reloc on the stock sys folder from x1, note all the values..
then run g'reloc on your new UNTOUCHED sys, where you change NOTHING...no swapping of files (unless you port from vga or qvga, or change locale, but thats another story) then change the values on the new sys with the values from the stock x1 sys, apply changes, and you have ported the sys.
cheers
Click to expand...
Click to collapse
When i run g reloc i get the same values as i did with the original build. Let me see if i understand the file hierarchy correctly.
1. I run G'reloc where i have my stock ROM's SYS folde. (note those values)
2. then i run G'reloc where my Donor SYS folder with the rest of the crap from the Donor ROM.
3.Then i copy the Donor SYS folder into the location i have my stock ROM SYS folder and overwrite. I run G'reloc again if the information is different from the first time i ran g'reloc i change it and hit do it.
Is this what i should be doing? I do this and i get the same result no matter which ROM i try and port from. I am porting from a touch pro ROM so is there anything i would need to change due to the vga to wvga switch?
swap from the modules marked with red to blue
base_dpi_192_resh_480_resv_640
to
base_dpi_192_resh_480_resv_800
since our device is WVGA you need to have the value set to 800 instead og 640.
So swap the folders with 640 from donor rom to the ones from either blackstone or x1
I can't get anything to work... If i extract the xip from this 21109 build that i have and try an use xipporterex to create the new xip and write it into the os.nb.payload and then merge the files. If i take that os.nb that is created i can build that and it will boot but if i try use the rom build procedure where it makes the os-new.nb file it will never boot. Even if i do nothing but just extract and rebuild the rom will not boot. From this i assume that i'm doing something wrong, 21109 build is corrupted or both. I'm not this inept. This shouldn't be giving me this much trouble with all these tutorials. Can someone please help me out with the exact procedure they use when building an X1 rom with porting over a new build?