HyperCore
PUBLIC BETA
The most complex KITCHEN a begginer cook may ever need.
Easy to use but also very complex, it can be usefull to anyone.
Why ask and wait for others to make the perfect ROM for you when you got the power to do it yourself ?
~. Base ROM .~* NO BASE ROM ! but ANY ROM !
~. Best part .~* IT USES TADZIO TOOLS
* YOU CAN OPTIMISE EXE's and DLL's, SO IF YOU WANT EVEN MORE SPACE, YOU'LL GET IT
* IT CAN BE USED ON ANY DEVICE WITH VERY LITTLE MODIFICATIONS !!!!!
* NO LONGER LIMITED BY ANYONE OR ANYTHING.
* YOU CAN COOK ANY ROM YOU LAY YOUR EYES ON VERY EASY
* IT HAS ADVANCED ERROR CHECK
~. It will install .~Core folder on the system drive. Some tools and settings required.
HyperCore folder on the Desktop. There is your kitchen. You can move it wherever you want.
The place where you actually use it is HyperCore\Panel.
~. How To .~- First of all edit the file named "Device.txt" located on the "Core\ACK\" folder located on systemdrive (mostly drive C:\)
Edit as following.
If you have a :
HTC Wizard : " set device=Wizard "
HTC Hermes : " set device=Hermes "
HTC Artemis : " set device=Artemis "
HTC Herald : " set device=Herald "
HTC Universal : " set device=Universal "
HTC Trinity : " set device=Trinity "
HTC Prophet : " set device=Prophet "
Click to expand...
Click to collapse
Save it and then you're good to go.
It's much similar to the old Core kitchen...so those of you who used it ...will feel comfortable with it. Regenerated batch scripts, better, and i hope bug free.
~. Guides .~* Hermes Cookbook - THANKS to sambartle
* My Way of cooking
* How to ADD/REMOVE programs -THANKS to mfrazzz
~. Notes .~Since this is still a public BETA, I await your problems/ideas/concepts.
If you spot a bug, i suggest to send me a PM as well as a post on the thread.
I suggest having a ROM to make a backup in case you do something wrong
I created and tested this tool for WindowsMobile 6 , but WM5 should work OK too.
~. Download .~
RapidShare
Special thanks :
* Papamopps - for real support
* nandlal_mk - for answering questions and DSM editor
* mUn - for finding the time to answer some of my questions
* molski - for i started working on his tools and still used some of them
* Tadzio - for his tools and patience
* bepe - for his tools
* the-equinoxe - for his splash-screen tools
* naboleo - for his initflashfiles generator
* dutty - for his NBH Tool
few others that surely i forgot to mention Sorry..
A very very very big THANK YOU anichillus! Your hard work and contribution is appreciated.
Great works anichillus....!
Thanks a lot
Very nice! Can't wait for a custom rom
It seems really good
Good work man!! will give it a try, post back results later!
Tell me guys if anyone tried it and if any problems.
A feedback would be nice.
anichillus,
thanks for the great stuff. BTW, can you advise how i can repackage the OEM and SYS folder back to *.nb file.
Thanks...
anichillus said:
Tell me guys if anyone tried it and if any problems.
A feedback would be nice.
Click to expand...
Click to collapse
simontee said:
anichillus,
thanks for the great stuff. BTW, can you advise how i can repackage the OEM and SYS folder back to *.nb file.
Thanks...
Click to expand...
Click to collapse
Once you run the BuildOS program in Build menu, if you follow those stepps you'll have the OS.nb in the temp folder. After that, you will be asked if you want to convert it into Signed .nbh and it will be moved into the HTools in the Tools folder. Just follow the tutorial in Help folder, you will figure it out.
Cheers
It works !!!
anichillus,
thanks for the guide and it works for me. I have re-cooked BEPE WM6 WWE OS.nb and it works smoothly for me.
removed some files :-
- transcriber
- redundant ringing tone
- redundant pic and image file
- redundant help files
BEPE WM6 WWE
Storage In Use : 5.17 MB
Program In Use : 22.4 MB
and now my self-cooked ...
Storage In Use : 2.79 MB
Program In Use : 25.7 MB
Thanks again !!
simontee said:
anichillus,
thanks for the guide and it works for me. I have re-cooked BEPE WM6 WWE OS.nb and it works smoothly for me.
removed some files :-
- transcriber
- redundant ringing tone
- redundant pic and image file
- redundant help files
BEPE WM6 WWE
Storage In Use : 5.17 MB
Program In Use : 22.4 MB
and now my self-cooked ...
Storage In Use : 2.79 MB
Program In Use : 25.7 MB
Thanks again !!
Click to expand...
Click to collapse
can u tell me the steps of cooking?
I want translate BEBE WM6 WWE to French. But i don't know the method. I can extract mui files from emulator but next ? I misses files into emulator. Do you have a tutorial ?
can this tool be used to change to vendor / country id of a rom - ie change the official htc wm5 rom so that it may install from bootloader on a locked o2 orbit?
thanks.
chickyd said:
can this tool be used to change to vendor / country id of a rom - ie change the official htc wm5 rom so that it may install from bootloader on a locked o2 orbit?
thanks.
Click to expand...
Click to collapse
No! It can create nb/nba file to flash on a live devices. But created nbh files are invalid. So you cannot flash at Bootloader!
first time using kitchen stuck
I just have one question completely new to this stuff how do i take the missing files that are on the package tool and put the back to the sys folder that they need to be in sorry if question is stupid
Hi!
Thanks for an awesome toolkit!! I have some questions regarding home brew
1) Could I cook a ROM containing some of the applications I usually installs on my device, for instance tomtom, pocket plus, resco explorer and so on?
2) How do I change language on the ROM I cooks? I know I have to extract the resource from the emulator ROM's, but then...
3) Can I mix and match resources in different languages? I want a WWE ROM, but with the Norwegian onscreen keyboard?
Thanks for this good tutorial, I'm still trying to find out all options that there are. I'm looking forward to see a complete tutorial about all the functions, e.g. how do I integrate my own apps into the ROM or EXT Rom, signing files.....
My first ROM didn't work but I'd really build a ROM that increases my program memory as already mentioned and all my standard apps preinstalled, own splash screen,.... But that will take some time.
I translated the tutorial into German, send me a PM to tell me where to send it.
Web
Is there a problem with the website? I can ping it but I can't read it.
Thank you so much anichillus for your great posts and releases. I'm using your Kitchen, and I have nothing but all the good to say.
Though, i have a few questions. I understand that making the Rom by using the CreateROM.bat file makes it so much easier. But, I would like to know what exactly hapens when we execute CreateROM.bat.
why do we have many seprate folders like SYS, ROM, flashrom, Tools?
i know that we can use the OEM folder for adding packages.
i also know that the Tools folder has all the programs ndded to make the rom.
What is the SYS folder? what does it do?
What is the ROM folder? what does it do? Can we change the file Flash.nbo? if we can, how is the final ROM affected?
Thanks again for all your support.
majdi_alkurd: click right mouse button on createROM.bat, then Edit and you'll see what exactly does it do.
Related
Can anybody please help me to build a rom? specially to the XDA-developers, thanks in a million...in advance.
My question is:
1. Do i need a base rom(no program included) on the cfg/(rom.nb1)? is it necessary ?
2. what is the maximum files i can put in the files/ directory? that will be splited by mkrom, i know it is depending on the version since 3.17 the maximum for all files is 5 M. how about other version. 4.01,4.05, 4.10 and 4.16
3. when i run the bash setup.sh nk.nb1(4.05), using parameter for 4.05 i get a message "!!! your rom is not known to me: md5:fb9e70c5786f08e4db6db7c184c59704" is this normal or it is not define on the splitrom.pl ?
4. what kind of editor did you use for building a BMP file with 16 bit, I tried to use adobe photoshop 6.0, but i can not seem to save it as 151 k, the option is only 24 bit and 8 bit, if you can give me a site where i can download it , i will really apreciate it.
Thanks for the Help..
More power to the XDA team
and
Welcome TMO 4.16!!! (which i think no diff with 4.10)
1. yes you do need some kind of rom to start with
2. you can check using
Code:
perl splitrom.pl yourrom.nb1 -ob <your bmp offset> | perl calcgaps.pl 0x3ffff
and add the sizes of the holes.
you have to figure out where the bootsplash is for your rom. ( for new roms this is most likely 0x81ec0000 )
3) there is a list of 27 roms I know about in splitrom, if I never saw your rom, the signature will also not be there.
btw, what rom do you have?
4) I think we used photoshop for that. ( Peter Poelman knows more about that )
thanks for the reply XDA developer Itsme,
but how can i build a baserom with the rom i have, I have a ROM 4.05 which i created in jeff's kitchen? or any site where i can download the base rom 4.05?
I have a ROM 4.05, 4.10 which i get from jeff's kitchen and also the original 4.10 TMO. regarding the signature of the ROM, i read your splitrom.pl and i found out you 27 list of roms, but i didn't find that signature "md5:fb9e70c5786f08e4db6db7c184c59704" is it because my ROM is not base ROM?
my param is ;
wincever=4
start1=21740000
size1=0040000
start2=003c0000
startbmp=81ec0000
startop=81b00000
I'll still try to use the photoshop, maybe i miss something there.
Please correct me if i done something wrong with my commands.
I have Perl 5.8 and cygwin, installed in windows 2003
then make the path for perl/bin and cygwin/bin
then i copy all the things i need to build a rom in one directory including nk.nbf(with jeff's 4.05) and mkrom tools(which i got from the demokitchen)
i run "perl setup.sh nk.nbf" to extract the bootimage.bmp and rom.nb1 to cfg/ directory
then i dump "dumprom -4 -d files -q nk.nbf" to extract all files in files directory
then i convert "perl fdf2reg.pl files/default.fdf cfg/default.reg"
"tr -d "\0" <files/initobj.dat >cfg/initobj.txt"
"cp files/initdb.ini cfg/initdb.ini"
then in files/ directory i delete all the windows files i leave only the program with the dll i wanted to add in the rom like total commander, file commander.. etc...
(I compare it with the original files of WM2003)
then i run "bash mkrom.sh out/out.nbf"
but i got an OVERLAP message on the screen
and also the same message like i told you before "Your rom is not know to me"
Please Help me with this because i want to build my own rom according to the program i need.. and many thanks.
split rom does not recognize romkitchen roms, since they vary too much.
you should use an original rom, not one from the romkitchen.
the overlap means that somehow the params file was not correct.
or maybe you just tried to add too much files.
XDA developer Itsme said:
split rom does not recognize romkitchen roms, since they vary too much.
you should use an original rom, not one from the romkitchen.
the overlap means that somehow the params file was not correct.
or maybe you just tried to add too much files.
Click to expand...
Click to collapse
Thanks Itsme, thats why splti rrom can not recognize the ROM I have, I'll try to search for the base ROM in the forum, or can you give me a site where i can download the baseROM, I think that's why I am having a OVERLAP because there is a added program on my ROM, XDA-Developers File1 and File2 is duplicated.
It answer my question regarding the ROM i have, thanks a lot man you really a good help.
Now my only problem is to find all the base rom so i can start cooking some ROM.
Hi!
If I cook my own ROM using the core pro kitchen for Artemis, what is the necessary steps I have to do to repack the rom into i nbh file and be able to flash it with the RUU utilities? I guess this is be possible now that we have the USPL, thanks to Pof and all the other geniuses in this forum.
Regards,
PK
All existing tools for making NBH work fine with hermes / trinity, but not with artemis as signature positions differ. To create artemis NBH you have to use this method, until a better tool to automate this is done.
1) Use nbhgen.exe to create NBH (edit sample.txt)
2) nbh2dbh.pl RUU_signed.nbh file_unsigned.dbh
3) imaghash.exe -raw file_unsigned.dbh file_signed.nbh 1024
I'm making a tool for this at the moment, it is almost finished, but I can't test the generated .nbh's because T-mobile still has my Artemis in repair!!!
today Mr.Dark simpson release HTC rom tool Repack *.nb ---> Nbh
work in HTC Artemis and ....
Link here :
http://forum.xda-developers.com/showthread.php?t=311909
Cheers..!
tom_codon said:
today Mr.Dark simpson release HTC rom tool Repack *.nb ---> Nbh
work in HTC Artemis and ....
Link here :
http://forum.xda-developers.com/showthread.php?t=311909
Cheers..!
Click to expand...
Click to collapse
Tom,
I tried Dark Simpson's utility with your OS.nb but failed. Could you please tell how to do? Thanks.
Khuanchai said:
Tom,
I tried Dark Simpson's utility with your OS.nb but failed. Could you please tell how to do? Thanks.
Click to expand...
Click to collapse
Khuanchai my friend..!
Copy it in Disk C
And try agian.
This worked verry good.
tom_codon said:
Khuanchai my friend..!
Copy it in Disk C
And try agian.
This worked verry good.
Click to expand...
Click to collapse
Thanks, Tom. The new version 1.01 now works beautifully.
pof said:
All existing tools for making NBH work fine with hermes / trinity, but not with artemis as signature positions differ. To create artemis NBH you have to use this method, until a better tool to automate this is done.
1) Use nbhgen.exe to create NBH (edit sample.txt)
2) nbh2dbh.pl RUU_signed.nbh file_unsigned.dbh
3) imaghash.exe -raw file_unsigned.dbh file_signed.nbh 1024
Click to expand...
Click to collapse
Where can I get imaghash.exe please?
Hi!
Thanks a lot for these great advice. I relay start thinking of cooking my own ROM, it seems like all the tool is quite mature now, both the core pro kitchen and the Mr. Dark Simpson's authoring tool.
One thing I could need some more advice about though, is how to make an OEM package, or where do download already created packages.
Regards,
PK
paalkr said:
Hi!
Thanks a lot for these great advice. I relay start thinking of cooking my own ROM, it seems like all the tool is quite mature now, both the core pro kitchen and the Mr. Dark Simpson's authoring tool.
One thing I could need some more advice about though, is how to make an OEM package, or where do download already created packages.
Regards,
PK
Click to expand...
Click to collapse
If you want do some OEM package...!
May be OEM Storage 1.75.
Extract All File in Storage 1.75 cab
Copy to Folder Storage 1.75
All reg in Storage 1.75 cab copy to Notepad and see link :
http://www.famkruithof.net/uuid/uuidgen
That it ID.Maybe : 6b44e778-1c4d-11dc-8314-0800200c9a66
Save all reg Storage 1.75 name 6b44e778-1c4d-11dc-8314-0800200c9a66.rgu ( Save to Unicode Format)
And Create file empty 6b44e778-1c4d-11dc-8314-0800200c9a66.dsm in Folder Storage 1.75
Now you have OEM Storage 1.75
Cheers..!
Quick question
Is there a way to replicate 1 xda orbit onto another? The reason I am asking this is because I have killed my xda orbit to the point where it hangs on the "O2 Welcome Screen". It does however boot up into bootloader mode and I can connect to it using mtty.exe. My mate has an xda orbit which was bought at the same time as mine... is there anyway to mirror that device onto mine so that it starts working again?
Updated and added new version of tools.
1. G'Reloc - updated
Tool for boost rom cooking by autofixing and relocating ALL modules in IMGFS.
HOWTO:
1) Put it in to kitchen folder (one place with BuildOS)
2) StartUp, fill right values for slots 00 and 01 endings
3) Push - DoIt button and feel free
The tool have coomand line, use "G'Reloc -doit -dump".
-dump folder must be in /temp/dump
2. M'Reloc
Tool for relocating one module.
3. M'Reloc for nk
Tool for relocating a nk.exe Dont use it if dont know what is it.
and last new tool
4. reversmode
Simple tool for file-to-module conversion with .reloc section compression.
Many thanks to my friend freepk
Big thanks to: mamaich, bepe
u a the best one thanx a lot!
Great, I was too lasy to make such a tool myself
To clarify why it is needed.
When DLL in ROM is stored as a module, it occupies a fixed address space. So it starts faster, and can be loaded in slot 1, saving the virtual memory in a 32-mb virtual address space of all processes. There are some other benefits described in MSDN.
When you cook ROMs you may find that DLL from one ROM uses the same addresses as DLL from another. Previously to fix this you had to convert DLL to a file losing VM space. And not all DLLs worked after such conversion. Now we have an automated tool that can automatically fix all overlaps.
P.S. I have not tested this tool myself - too busy now
Thank you so much!!!
This makes the ROM Kitchen perfect
You can use any SYS folder from any device now!
- Put it together with the OEM folder for your device into the ROM Kitchen
- Run this tool
And build the ROM... that’s it! ... no module overlappings... perfect ROM
already tried it and it works just perfect!
Great Misar..!
Best regards from Russia
Lo All
We test this tool on hp 4700, loox n560, dell x51, x51v, and all five roms works fine
Misar, u great man, great idea and great roms as result of your great work
P.S. Thank u all guys for help, support and fun
No more recmod! Thanks very much misar for this incredibly useful contribution. And already praised by mamaich and bepe? Can't get a higher endorsement than that
Great stuff!
I may have a go at cooking myself now
nice release
you know it`s great, the betas were also great... it should work perfect with all roms. i personally tested with typhoon, tornado, asus p525, loox 520 - everything is cool)
Wow,
That is a great tool
Thanks
Hey,
Thanks for all the hard work!
Saves doing it all by hand with M'Reloc now!
Cheers,
-Whiterat
Great work! THX!
GREAT WORK!THX!
But there's something confused me, while I put all the things under OEM to SYS, the program cant recognize new added module, it still report as only with SYS like "Total 419".
Then I put only OEMDrivers folder to SYS, it report "Total 437", while I add another folder Drivers to it, report back to "Total 419"
brilliant author + brilliant application = perfect!!..
Thanks!..
WOW , maybe in the future MS will use ROM KITCHEN make rom
misar said:
Tools for boost rom cooking by autofixing and relocating ALL modules in IMGFS.
HOWTO:
1) Put it in to kitchen folder (one place with BuildOS)
2) StartUp, fill right values for slots 00 and 01 endings
3) Push - DoIt button and feel free
The tool have coomand line, use "G'Reloc -doit"
Many thanks to my friend freepk
Big thanks to: mamaich, bepe
Click to expand...
Click to collapse
how do I find the right value for slots 00 and 01 for Prophet ?
many thanks
WOW~Cool misar
Thanks for ur efforts
But I got "Cannot open C:\...\SYS\SYS\.VM\imageinfo.bin" either place it in SYS directory or OEM
hma4 said:
how do I find the right value for slots 00 and 01 for Prophet ?
many thanks
Click to expand...
Click to collapse
If you dont know wich value must be, then use .VM folder from your original rom.
misar said:
If you dont know wich value must be, then use .VM folder from your original rom.
Click to expand...
Click to collapse
many many thanks
i would like to edit nk.nbf files (of course just for personal use).
have searched hours for an editor, but i cant find anything useful.
plz help me !
AFAIR you should only generate nbf file using "kitchen", not edit them.
jakubd said:
AFAIR you should only generate nbf file using "kitchen", not edit them.
Click to expand...
Click to collapse
are you sure ?
i found this app that allows you to edit WM 2003 nbf files (sadly it doesn´t work for 6.1 rom nbf):
http://wiki.xda-developers.com/index.php?pagename=ER2003Edit
is there an other way to edit WM 6.1 images ?
(maybe i can drop them from the device in a format that can be open)
editing nbf files
try this it works a treat and will help you understand thing a little more, Then you could read up on how to port it up a bit higher once you'v learnt how it works hope this helps be carefull when you CreatROM read the text in the dos window the "free sectors" !!!! 0??? To 0001 is good, 0001 been the full to the brim ! ( ffff???? ) is bad ! if bad do NOT flash to your device start buildOS again and unckeck something ealse read the readme or guide file carefully also explode has a kitchen out that's good search for kitchen on this site there's a assortment out there have fun REMEMBER be CAREFULL or you could brick your device however you edit a rom Most time if you screew up you can flash a 2003 shipped rom and alls well agian but if you flash a rom that's fare to big you will over wright your boot sector and that's NOT GOOD
http://forum.xda-developers.com/showthread.php?t=331636
how can i dump a ROM ?
have read xplode´s kitchen how to, but i have still some questions:
witch tool i have to use to dump a rom ?
must the device be in boot loader mode ?
must i perform a hard reset before putting the device in boot loader mode ?
thank you for you help
dump rom
wmvfan said:
how can i dump a ROM ?
have read xplode´s kitchen how to, but i have still some questions:
witch tool i have to use to dump a rom ?
must the device be in boot loader mode ?
must i perform a hard reset before putting the device in boot loader mode ?
thank you for you help
Click to expand...
Click to collapse
I think I read some thing about dumping from the device ! But it's very complicated to do and if you get it wroung then it could damage your device Buzz-dev has a program called grabit see his site it copys the rom from the device to The SD CARD as a *.bin file then you dump that instructions are there, I have attached a zip i found on this site moded a bit for myown use it will dump BA or Hima put it in C:\ and right click it select extract here PS (you need winrar it's free just search xda site for it) My decompilers not complete but should give you some idear or how it works, You say u got explodes kitchen follow his instructions and build his rom when It says put your device in boot loader DON'T. Wait untill the build is finnished Press ctrl + C then look in upgrade folder and you should find an nk.nbf copy this to Swamp395Decompiler folder so you see it with PKGTool then double click BA_Disasemble.bat when that's finnished double click PKGTool.exe then "File" "open" from menu navegate to swampy395decompiler\dump click OK read screen then When that's finnished meun "tools""build packages" you should have some missing files if you look at the one called sys it should look simaler to explodes kitchen!! Then spend some time reading xda site good luck Remember the risk is all your bla bla no responcerbility ETC
I'm learning myself ! But if i can help i will, I'v been Building My own kitchen It's getting close but not got a booting rom yet but soon I HOPE
PPS pda viet rom Don't bump so well
swampy395
It works !
i easily put the nk.nbf file in C:\Swampy395Decompiler\ and start BA Disassemble.bat
a dos window opened and dump the rom in C:\Swampy395Decompiler\dump
all files of the rom are now in this folder and i can edit them.
but i have still some questions:
-how can i make a rom out of the files in \dump ?
-how can i edit registry files ?
-is there a way to change the rom language ?
greetings from germany
editing rom
wmvfan said:
It works !
i easily put the nk.nbf file in C:\Swampy395Decompiler\ and start BA Disassemble.bat
a dos window opened and dump the rom in C:\Swampy395Decompiler\dump
all files of the rom are now in this folder and i can edit them.
but i have still some questions:
-how can i make a rom out of the files in \dump ?
-how can i edit registry files ?
-is there a way to change the rom language ?
greetings from germany
Click to expand...
Click to collapse
read these links and you'll find thing you'll have to do a lot of searches *.reg files open in notepad then save as unicode turn wordwrap off these a lot to read too much fro me to explane here these links should get you in the right area
Ps if you find any good tutorials please send me a link and as i find them i'll send to you good luck I'v been reading some 4 weeks now it's not so easy building a rom so i'v found
PPS the tools i send you copys and converts the default/user.HV files and initflashfiles.dat to swampy395decompiler folder i also posted a tool to edit initflashfiles see
http://forum.xda-developers.com/showthread.php?t=394680
search for kitchen building roms ETC you'll find thing like these
http://www.anichillus.net/index.php?topic=29.0
http://wiki.xda-developers.com/index.php?pagename=OEM Package Tutorial
good luck let me know how get on
swampy395
swampy395 said:
read these links and you'll find thing you'll have to do a lot of searches *.reg files open in notepad then save as unicode turn wordwrap off these a lot to read too much fro me to explane here these links should get you in the right area
Ps if you find any good tutorials please send me a link and as i find them i'll send to you good luck I'v been reading some 4 weeks now it's not so easy building a rom so i'v found
PPS the tools i send you copys and converts the default/user.HV files and initflashfiles.dat to swampy395decompiler folder i also posted a tool to edit initflashfiles see
http://forum.xda-developers.com/showthread.php?t=394680
search for kitchen building roms ETC you'll find thing like these
http://www.anichillus.net/index.php?topic=29.0
http://wiki.xda-developers.com/index.php?pagename=OEM Package Tutorial
good luck let me know how get on
swampy395
Click to expand...
Click to collapse
Just a quick thought you'v got a kitchen and a rom built in that kitchen put the rom back together as it is in the kitchen IE copy the layout you'll find some *.rug files missing download athers himalaya kitchens and read the help and guid files on how to build a kitchen and use explodes kitchen as a referance see if you can put it back together without copying files out of explodes kitchen If you manage that then you should be able to make a higher build kitchen of your own good luck
I hope i can help u learn how to cook rom and makes it more easier!
1.Structure OF THE KITCHEN
ROOT OF THE KITCHEN-------
dump----> This will contan files dumped from ROM,like OFFICIAL ROMS.
OEM---->This folder contans all the OEM DRIVERS and OEM software
ROM\XIP\ ---->contain boot.rgu,don't mod or del it!
SYS -------->SYS of WM build
SYSNEW ------>TH SYS OF NEW version of WM building u will proting
temp ----->temp files,and ROM files u cooked are here
TOOLS --------->All tools that ness for cooking
XIPNEW ------>NEW XIP of WM version.there are two styles:XIP.BIN and MSXIPKernel.u can porting them by choose correct method in my bat command
reg&iniflashfiles_tools ------->Tools to edit reg files and initflashfiles.
HOW TO:
1、IF u don't want to Porting new version of wm and u just want to mod ,u can dump OFFICIAL rom.
TO DO:Place official ROM in root of kitchen,run "dump ROM.bat" and follow the instruction.when finished,u will find OEM AND SYS in DUMP\DUMP.Move them to root of the kitchen.and move xip.bin in dump to root of kitchen and rename it to xip_out.bin.Now,u can edit softwares in OEM and build as u like by run"Build ROM.bat"
2、IF u want to cook new version of WM build,just down load new SYS AND XIP file form somewhere like DFT.usually,u may only need these parts:COMM,COMM_0409,WVGA_COMM,WVGA_COMM_0409 and XIP.
UNZIP COMM,COMM_0409,WVGA_COMM,WVGA_COMM_0409 to SYSNEW folder,UNzip MSXIPKernel form XIP to XIPNEW folder then run"Build ROM.bat" and follow the guid.
sorry for my english...
hope u can understand...
-------------------------------------------------
sorry for my mistake..
i forget something important
just creat ROM\XIP\ folder in root of kitchen and put this boot.rgu in it
View attachment boot.rgu.zip
Download:TG01_ROM_KITCHEN.rar
ffboy2009 said:
I hope i can help u learn how to cook rom and makes it more easier!
1.Structure OF THE KITCHEN
ROOT OF THE KITCHEN-------
dump----> This will contan files dumped from ROM,like OFFICIAL ROMS.
OEM---->This folder contans all the OEM DRIVERS and OEM software
ROM\XIP\ ---->contain boot.rgu,don't mod or del it!
SYS -------->SYS of WM build
SYSNEW ------>TH SYS OF NEW version of WM building u will proting
temp ----->temp files,and ROM files u cooked are here
TOOLS --------->All tools that ness for cooking
XIPNEW ------>NEW XIP of WM version.there are two styles:XIP.BIN and MSXIPKernel.u can porting them by choose correct method in my bat command
reg&iniflashfiles_tools ------->Tools to edit reg files and initflashfiles.
HOW TO:
1、IF u don't want to Porting new version of wm and u just want to mod ,u can dump OFFICIAL rom.
TO DO:Place official ROM in root of kitchen,run "dump ROM.bat" and follow the instruction.when finished,u will find OEM AND SYS in DUMP\DUMP.Move them to root of the kitchen.and move xip.bin in dump to root of kitchen and rename it to xip_out.bin.Now,u can edit softwares in OEM and build as u like by run"Build ROM.bat"
2、IF u want to cook new version of WM build,just down load new SYS AND XIP file form somewhere like DFT.usually,u may only need these parts:COMM,COMM_0409,WVGA_COMM,WVGA_COMM_0409 and XIP.
UNZIP COMM,COMM_0409,WVGA_COMM,WVGA_COMM_0409 to SYSNEW folder,UNzip MSXIPKernel form XIP to XIPNEW folder then run"Build ROM.bat" and follow the guid.
sorry for my english...
hope u can understand...
Download:Uploading
Click to expand...
Click to collapse
U are the MAN!
Thank you.
Very nice
Hope I am now able to mod my favourite rom by myself now
Two worlds about how to integrate Sense in your ROMs maybe a good link if you have ?
Thanks
Edgar
I tested your tool and it is great as it is well guided.
but i can not find OEM folder in dump/dump only many folders containing "....dll" names and one folder called "SYS"
Also when editing OEM`s to the rom i get the error "Creating initialflashfiles.dat"
Looks like i am even not able to build a rom with a auto tool
P.S. Wanted to add cabs to your wm6.1 rom using this tool
eddgarms said:
Two worlds about how to integrate Sense in your ROMs maybe a good link if you have ?
Thanks
Edgar
Click to expand...
Click to collapse
Maybe this http://forum.xda-developers.com/showthread.php?t=633795 can help you.
FFboy: "IF u want to cook new version of WM build, just down load new SYS AND XIP file from somewhere like DFT."
What is DFT?
This is a DFT
Hello ffboy..
Can we use your tool to "modify" your sense rom, for exemple?
Thanks!
ps: moreover, i haven't got this folder "ROM\XIP\"...so i've got an error when i build the rom.
I tried to download your tool 3 times, but nothing....!!
What's wrong?
And I dumped the toshiba 6.5 rom, i did what you say in the first post and then i build the rom...
The original toshiba rom was 253mo and the new one is 244mo...but I didn't remove anything!!! Is this just because of the xip directory error i have during the "buildOs" process?
thanks!
iceeyes91 said:
I tested your tool and it is great as it is well guided.
but i can not find OEM folder in dump/dump only many folders containing "....dll" names and one folder called "SYS"
Also when editing OEM`s to the rom i get the error "Creating initialflashfiles.dat"
Looks like i am even not able to build a rom with a auto tool
P.S. Wanted to add cabs to your wm6.1 rom using this tool
Click to expand...
Click to collapse
Some roms that deleted all dsm and rgu files can't be dumped to OEM&SYS style
i can dump it out without do DM2PKG and copy all files in dump folder to SYS and do some mods.run kitchen maybe it works...
u want ro add cabs autoinstall on first boot?
just dump my rom to files and copy all off them into SYS,then creat a .rgu file and place it into a folder in OEM
add these in .rug file:
Code:
[HKEY_LOCAL_MACHINE\Software\TOSHIBA\AutocabInstall]
"cab1"=""
"cab2"=""
"Reboot"=dword:15
Nokser said:
This is a DFT
Click to expand...
Click to collapse
Yep!
That darkforcesteam。。。
pipolas said:
Hello ffboy..
Can we use your tool to "modify" your sense rom, for exemple?
Thanks!
ps: moreover, i haven't got this folder "ROM\XIP\"...so i've got an error when i build the rom.
I tried to download your tool 3 times, but nothing....!!
What's wrong?
And I dumped the toshiba 6.5 rom, i did what you say in the first post and then i build the rom...
The original toshiba rom was 253mo and the new one is 244mo...but I didn't remove anything!!! Is this just because of the xip directory error i have during the "buildOs" process?
thanks!
Click to expand...
Click to collapse
sorry fo my mistake...
download files in first threat
and it will fix erro..
the diff between ori rom and moded rom maybe because EXTRELOC useing a diff way to reloc moudules..i think
ffboy2009 said:
sorry fo my mistake...
download files in first threat
and it will fix erro..
the diff between ori rom and moded rom maybe because EXTRELOC useing a diff way to reloc moudules..i think
Click to expand...
Click to collapse
Thanks ffboy, i'll try!
pipolas said:
Hello ffboy..
Can we use your tool to "modify" your sense rom, for exemple?
Thanks!
ps: moreover, i haven't got this folder "ROM\XIP\"...so i've got an error when i build the rom.
I tried to download your tool 3 times, but nothing....!!
What's wrong?
And I dumped the toshiba 6.5 rom, i did what you say in the first post and then i build the rom...
The original toshiba rom was 253mo and the new one is 244mo...but I didn't remove anything!!! Is this just because of the xip directory error i have during the "buildOs" process?
thanks!
Click to expand...
Click to collapse
Size difference is mostly because of the IMGFS building, which may well be skipping free space at the end (used for ImageUpdate). It shouldn't matter too much.
I'll stick this, and unstick the other kitchen.
ffboy2009 said:
Some roms that deleted all dsm and rgu files can't be dumped to OEM&SYS style
i can dump it out without do DM2PKG and copy all files in dump folder to SYS and do some mods.run kitchen maybe it works...
u want ro add cabs autoinstall on first boot?
just dump my rom to files and copy all off them into SYS,then creat a .rgu file and place it into a folder in OEM
add these in .rug file:
Code:
[HKEY_LOCAL_MACHINE\Software\TOSHIBA\AutocabInstall]
"cab1"=""
"cab2"=""
"Reboot"=dword:15
Click to expand...
Click to collapse
Sorry i do not really get it
I dumped a official 6.5 Rom and there is like u said a OEM and a SYS Folder in dump/dump.
Using DMP2PKG i get an error on my win7 32bit by choosing "select folder"
Dumping your 6.1 rom it seems that in the dump/dump folder the OEM and his sub folders are not created, so all the data is loose.
will try some stuff and see where it gets me
Edit:
error : \.VM\imageinfo.bin not found, getting this with official and your 6.1
iceeyes91 said:
Dumping your 6.1 rom it seems that in the dump/dump folder the OEM and his sub folders are not created, so all the data is loose.
Click to expand...
Click to collapse
When dumping a cooked rom it is unlikley that you will get an OEM folder, i do not know why but the OEM parts can be found in the sys folder and relocated. Only dumping an original rom gives proper file segregation, ie OEM+SYS
Made my own rom now. Changed a official one and put some oem's in OEM folder.
Have some questions though:
How do you add the information to the rom , that it automatically adds a xxx.lnk file in startmenu for each program you have been put to OEM Folder??
Also how do you insert another input keyboard to the rom??
I wanted to add Neo2007 driverpack to my rom but it tells me that the xxx.dll already exists. how do i bypass this??
And how do I upgrade the netcf??
I now this is a lot of questions and maybe they are stupid, but i am totally new to rom-development. Thanks in advance
Thank you for this great tool
iceeyes91 said:
Made my own rom now. Changed a official one and put some oem's in OEM folder.
Have some questions though:
How do you add the information to the rom , that it automatically adds a xxx.lnk file in startmenu for each program you have been put to OEM Folder??
Also how do you insert another input keyboard to the rom??
I wanted to add Neo2007 driverpack to my rom but it tells me that the xxx.dll already exists. how do i bypass this??
And how do I upgrade the netcf??
I now this is a lot of questions and maybe they are stupid, but i am totally new to rom-development. Thanks in advance
Thank you for this great tool
Click to expand...
Click to collapse
Could you explain: if /OEM doent exit after DUMP, do you fill with your new cab (transform in OEM?) and add a registry entry ?
super_sonic said:
Could you explain: if /OEM doent exit after DUMP, do you fill with your new cab (transform in OEM?) and add a registry entry ?
Click to expand...
Click to collapse
I used this application to made my OEM's http://forum.xda-developers.com/showthread.php?t=525302
I just converted and put them into OEM folder.
Btw 1 thing concerning your 6.1 rom ffboy
Dumping it and putting everything to SYS does not work. I can not rebuild the rom , even if I do not add anything in OEM
iceeyes91 said:
Made my own rom now. Changed a official one and put some oem's in OEM folder.
Have some questions though:
How do you add the information to the rom , that it automatically adds a xxx.lnk file in startmenu for each program you have been put to OEM Folder??
Also how do you insert another input keyboard to the rom??
I wanted to add Neo2007 driverpack to my rom but it tells me that the xxx.dll already exists. how do i bypass this??
And how do I upgrade the netcf??
I now this is a lot of questions and maybe they are stupid, but i am totally new to rom-development. Thanks in advance
Thank you for this great tool
Click to expand...
Click to collapse
1.ALL files in SYS and OEM placed default in WINDOWS folder.check initflashfiles.dat in OEM_LANG_0409 and initflashfiles.txt in ur own oem folder.these files can change the place of file.
if u want add FFBOY.LNK to startmenu,add command like this.
Code:
Directory("\Windows\Start Menu"):-File("FFBOY.lnk","\Windows\FFBOY.lnk")
2.input keyboard can be added by download someone posted,u may search ur self.
3.if buildos tells u that XXX.DLL or some tile already exist,check the name and search in SYS or OEM to see if there exist a file in same name.
if exist,delete them except the newest one.
4.NETCF in wm6.5 already version 3.5
iceeyes91 said:
I used this application to made my OEM's http://forum.xda-developers.com/showthread.php?t=525302
I just converted and put them into OEM folder.
Btw 1 thing concerning your 6.1 rom ffboy
Dumping it and putting everything to SYS does not work. I can not rebuild the rom , even if I do not add anything in OEM
Click to expand...
Click to collapse
what buildos tell info to u?