Related
Hi all ,
i would really like to know what tools you are using to edit the Rom,
(a short explanation will be excellent)
I've tried some tools from the furom without luck.
Many Thanks
Jimmy
jimmymotek said:
Hi all ,
i would really like to know what tools you are using to edit the Rom,
(a short explanation will be excellent)
I've tried some tools from the furom without luck.
Many Thanks
Jimmy
Click to expand...
Click to collapse
look for imgfs tools,nb2nbf.exe, and typho5.exe.
it was quite easy creating a Ext. ROM (so i know how to use nb2nbf.exe, and typho5.exe it's imgfs tools that is not working for me.
i would really appriciate help with that.
Thanks again
Jimmy
jimmymotek said:
it was quite easy creating a Ext. ROM (so i know how to use nb2nbf.exe, and typho5.exe it's imgfs tools that is not working for me.
i would really appriciate help with that.
Thanks again
Jimmy
Click to expand...
Click to collapse
what part are you having trouble?
This is what I did :
after extracting the OS with typho5.exe
prepare_imgfs.exe 80040000-OS_0.nb -nosplit
viewimgfs.exe imgfs_raw_data.bin
than I wanted to edit the "dump" directory (I don't know how to put different files in diffrent directories) , any how i've replace few files. and than I run :
BuildImgfs.exe
make_imgfs.exe 80040000-OS_0.nb
than nb2nbf.exe and after all that I "burned" it into the device
(RUU) and than the device stucked.
So what I'm doing worng ?
again
many thanks
Jimmy
jimmymotek said:
This is what I did :
after extracting the OS with typho5.exe
prepare_imgfs.exe 80040000-OS_0.nb -nosplit
viewimgfs.exe imgfs_raw_data.bin
than I wanted to edit the "dump" directory (I don't know how to put different files in diffrent directories) , any how i've replace few files. and than I run :
BuildImgfs.exe
make_imgfs.exe 80040000-OS_0.nb
than nb2nbf.exe and after all that I "burned" it into the device
(RUU) and than the device stucked.
So what I'm doing worng ?
again
many thanks
Jimmy
Click to expand...
Click to collapse
your OS address is most problably wrong. it should be; 80040000
faria said:
your OS address is most problably wrong. it should be; 80040000
Click to expand...
Click to collapse
I know this is the OS address (that's what i was typing),
can you think of anything else ?
how do i know where the file is goona be (in which directory)
how can arrange the startmenu ?
sorry for the "tons" of questions
Jimmy
jimmymotek said:
I know this is the OS address (that's what i was typing),
can you think of anything else ?
how do i know where the file is goona be (in which directory)
how can arrange the startmenu ?
sorry for the "tons" of questions
Jimmy
Click to expand...
Click to collapse
look at the initflashes.dat in the dump.take a good look.,thats how.
faria said:
look at the initflashes.dat in the dump.take a good look.,thats how.
Click to expand...
Click to collapse
Found it...
Still not working , i have made a test on the T-Mobile ROm,
just took the os file , prepareifile -nospilt
than i used delfile t-mobile.tsk
afterward i used make_imgfs.exe
afterward i used nb2nbf , just the os (address 80040000) and than bured it.
and..... No luck still stuked on the Startup LOGO , what am i missing ?
(it's almost driving me nuts)
thanks again
Jimmy
faria said:
look at the initflashes.dat in the dump.take a good look.,thats how.
Click to expand...
Click to collapse
I'm not able to find it out the file "initflashes.dat" in dump folders. Where can I find the file?
It must be in the rom, if you cannot find it type in a command line console in the dump directory "attrib -h -s initflashes.dat", that surely would let you see it. But normally you will see it without doing this.
Molski
jimmymotek said:
Still not working , i have made a test on the T-Mobile ROm,
just took the os file , prepareifile -nospilt
than i used delfile t-mobile.tsk
afterward i used make_imgfs.exe
afterward i used nb2nbf , just the os (address 80040000) and than bured it.
and..... No luck still stuked on the Startup LOGO , what am i missing ?
(it's almost driving me nuts)
thanks again
Jimmy
Click to expand...
Click to collapse
Molski , Do you have any suggestion ?
jimmymotek said:
Molski , Do you have any suggestion ?
Click to expand...
Click to collapse
Extract one of my Roms, replace my OS.nb file with yours and cook it again.
Use ALL files including IPL/SPL so you will have to put 7 files in nb2nbf tool, if you need all the correct addresses, PM me.
Regards,
Molski
is it possible that my problem was that i just tried to "burn" OS and Ext. rom only ?
going to tray it again.
(BTW : is there a number of times i can burn my rom , i think i've done a hundred time)
thanks
still not working , stuck at the logo screen (it does write the spl,Ipl etc)
here are the address i used :
i think the problem is with something else ,
what version of imgfs you using (link ?)
can you write down the list of commands you writing
(i've been dealing with it quite few days with no luck)
I would really appriciate any help....
thanks again
Jimmy
molski said:
It must be in the rom, if you cannot find it type in a command line console in the dump directory "attrib -h -s initflashes.dat", that surely would let you see it. But normally you will see it without doing this.
Molski
Click to expand...
Click to collapse
Thanks molski I'm able to find it...
I had posted this to the mamaich's thread. posting here as well since it is wizard specific:
I've been trying to use the tools for building an HTC wizard ROM. Now, before starting out on any modifications, I simply tried to break apart and rebuild it. So, I extracted a ROM using typhoondecode_v5, then followed this:
1. prepare_imgfs.exe OS.nb -nosplit
2. viewimgfs.exe imgfs_raw_data.bin
3. BuildImgfs.exe
But then my imgfs_raw_data.bin is not rebuilt and stays at its original self. The buildimgfs tool does not give me an error, however the last 3 lines of its output reas something like :
total sectors: 0000
used: <some number>
free: <some number>
I searched the forums but couldn't find an answer. Saw a couple of posts having the same prob but no answer. Since I havent done any modifications to the ROM and have tried with both AKU2.3 and AKU 3.3 (and custom ROMs as well as official Qtek ROMs), the ROM that i am using is also not an issue.
Now, since there are so many custom wizard ROMs out there and ppl swear by mamaich's tools so there must be a solution. Please help me out or let me know if there is no way out and I ve to use some other way to make ROMs, i also found bepe's kitchen post but couldn't find how to use it for wizard..
Thanks in advance.
for the wizard, this line:
1. prepare_imgfs.exe OS.nb -nosplit
should be:
prepare_imgfs.exe 80040000-OS.nb –nosplit
see if that helps...
prepare_imgfs.exe 80040000-OS.nb –nosplit
Click to expand...
Click to collapse
I used that one only, and I have no probs with the "prepare" and "view" commands. I correctly get the bin files as well the modules/files are correctly extracted. I have problem with the "build" and "make" commands.
side question. should have thought of this earlier. how do you know its not updating? its been stated that this file will for some reason not change date/time and size.
hopefully that helps.
see this post:
http://forum.xda-developers.com/showpost.php?p=1110892&postcount=13
see this post:
http://forum.xda-developers.com/show...2&postcount=13
Click to expand...
Click to collapse
oopsie I am sure I read that post some time ago when I was collecting all the info for ROM cooking, but somehow forgot abt it when I started. Thnx for reminding
But There's another problem after this. When I run make_imgfs command it gives me some weird characters, however, a couple of posts above the one that you pointed at, there is a comment that I've to give the name of the old file only instead of new one. Will try that tonight when I go home and report back.
Thnx for the help dude
Anyways, another question:
This one is about the "universal id" part (dont remember the name of the app correctly, smthing like genuuid), for which all packages do we have to use this app? I mean if I wanted to add an executable (say a.exe) to the ROM, is it enough to simply add it to the "dump" directory and follow the build/make path or do I have to use the genuuid app path, or is this app used for some special kinda apps?
Thnx in advance. I'm not a newbie by any means in programming, GSM, and programming for GSM etc (I work in a Nokia GSM BTS project ) but am cooking a ROM for the first time.
yupz, worked...I was able to rebuild the rom. (Though the size/date-time stamp of the final 80040000-OS.nb also remains the same as the older one. I take that to be OK like the same thing happening with img_raw_data.bin. Haven't flashed the ROM onto my phone to see...)
Moreover, about the uuidgen program, I found out that it is bepe's way of doing it. We can do it the mamaich way that is simply add the programs that we want to the /dump folder and rebuilding. Correct me if I'm wrong.
Now that I've tested the waters, I'm on to making a custom ROM myself...
Thnx xda-dev...
shantzg001 said:
yupz, worked...I was able to rebuild the rom. (Though the size/date-time stamp of the final 80040000-OS.nb also remains the same as the older one. I take that to be OK like the same thing happening with img_raw_data.bin. Haven't flashed the ROM onto my phone to see...)
Moreover, about the uuidgen program, I found out that it is bepe's way of doing it. We can do it the mamaich way that is simply add the programs that we want to the /dump folder and rebuilding. Correct me if I'm wrong.
Now that I've tested the waters, I'm on to making a custom ROM myself...
Thnx xda-dev...
Click to expand...
Click to collapse
Hi shantzg001
i too am doing similar steps and all gone well ( i.e breaking/rebuilding).
but im surprized why dump dir size is extremaly different in compare to
imgfs_raw_data.bin . I tried some OS.nb and got the size of dumb approx
456kb or 368 kb or some MBs. Also dump dir contains only some modules and
some files.
Am i doing some mistake or u too r getting similar result
reply ASAP
thanx
nandlal
That seems strange, because in my case the dump folder is even bigger than the bin file (more than double the size)..
Can you list out the exact steps that you are following, and which ROM were you breaking apart?
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 ""
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
hi all
i noticed most of us having this problem with imate spjas \ breeze
stuck at bootscreen and can startup the phone
i downloaded the original rom from
ftp://ftp.clubimate.com/
extracted it and took the nbh file renamed it to breeimg.nbh
copied it to SD card and camer+reset button
congratulations
where is every body... can any majestious senior or moderator help...
vodovodo said:
hi all
i noticed most of us having this problem with imate spjas \ breeze
stuck at bootscreen and can startup the phone
i downloaded the original rom from
ftp://ftp.clubimate.com/
extracted it and took the nbh file renamed it to breeimg.nbh
copied it to SD card and camer+reset button
congratulations
Click to expand...
Click to collapse
i"m pleased to know that you fixed your device, and thx that you shared with us your xperience, specially that no one seems to care for the members request in this forum even the moderator....
i dtried what you shared with us, but i couldn't repair my device, still stucked in the DAME windows mobile blue screen
hope i'll find an answer from the majestious members or senoirs or even moderator to repair my device....
i think the problem is there is the hardware diff. between spjas and mteor ! i dont know
do u have the imate ??? the one with the camera infront ?
vodovodo said:
i think the problem is there is the hardware diff. between spjas and mteor ! i dont know
do u have the imate ??? the one with the camera infront ?
Click to expand...
Click to collapse
yep that's it...
when i extracted the rom that i downloded from ftp imate club, and renamed the breeimg.nbh, i copied it to the memory card, i pressed cam+power botton, the device entered into bootloader, then marked checking for 15 to 20 sec
then NOT ALLOWED....
really i'm tired from trying to fix help.... euffffffffffffffffffffffffffff
just relax.... i felt the same and i couldnt think strainght too
lets take it step by step
1- make sure u formated the SD with FAT32
2- make sure to rename the nbh from the exe file "not the exe itself just right click and extract here if u have winace or winrar" to BREEIMG.nbh with cap. letters
try again and tell me what happened
helloooooooooooooooooo no one can help here, where are the professionel in the forum SOS HELPPPPPPPPPPPPpp!!!!!!!!!
vodovodo said:
just relax.... i felt the same and i couldnt think strainght too
lets take it step by step
1- make sure u formated the SD with FAT32
2- make sure to rename the nbh from the exe file "not the exe itself just right click and extract here if u have winace or winrar" to BREEIMG.nbh with cap. letters
try again and tell me what happened
Click to expand...
Click to collapse
nothing better,
when i did these steps, the device didn't even load or even the cheking word.
but when i tried to synchronize my device via active sync and install the rom the device started to install windows 1%... 2% and oupssss failed, the device turned off and restated....
just to let you kow on the 3 color screen (bootloader screen)
BREE100
IPL-0.90
REE100
SPL-1.09.0000
and i installed before this bootloader vrsion that i geted from a link mentionned to be installed before the BREE rus
really i dont know what to do...
but really thx for your help...
it seems you are the one who care in this forum...