Database Users

PPC 2003 and mkrom

Any brave soul try using mkrom in conjucntion with the 2003 ROM? I think I might give it a shot here in a bit but wanted to know if anybody had tried it yet...

I've managed to build a 2003 ROM. It's extremely tricky though. I'm working on customizing a ROM similar to the XDA Developers SER - as soon as I get some free time
I'd like to acknowledge all the help given to me by Developer Itsme in this endeavor.
Let me know any suggestions you may have for the new ROM.

sheran_g,
i didn't know u could use mkrom with 2003 rom image. can u please post how u did it? i created a special version based on SE 1.1 rom but would like to put the same programs into the new rom. any help is appreciated.
thanks
alex

sheran_g said:
I've managed to build a 2003 ROM. It's extremely tricky though. I'm working on customizing a ROM similar to the XDA Developers SER - as soon as I get some free time
I'd like to acknowledge all the help given to me by Developer Itsme in this endeavor.
Let me know any suggestions you may have for the new ROM.
Click to expand...
Click to collapse
What's tricky about it...?

The modified registry file you make does not get picked up at the device startup. You need to manually inject the memory address of the modified registry file into the ROM in order for it to get picked up.

my latest romtools can be found at romtools
now it calls dumprom to find and fix the filedata offsets.
I think they should now build 2003 roms.

sheran_g,
can u post the steps that u take to buid it? i'm trying right now and its not working. i'm having little problems. can u post ur default.reg and initobj.txt? any other help is apreciated.
thanks
alex

Ok. Here they are in a nutshell:
Get the latest romtools.
Make the following dirs: romfiles, cfg, tmp, out, files, files1, files2
Split the ROM into Bootloader, bootimage, OS image, xipchain into the 'cfg' dir.
Dump the files in the OS image into a 'romfiles' dir.
Get the default registry file, initobj & initdb files into your 'cfg' dir.
Make changes to your default.reg and initobj.txt
Place any files you want loaded in the ROM into the 'files' dir.
Run 'mkrom.sh'
You should then have your new ROM. I'm sorry if it's extremely brief; you'll have to make do with this and the README file in the romtools archive file for now. You'll find my default.reg and initobj.txt files on my site: www.zensay.com/qtek/mkrom

sheran_g,
Have you created a decent working custom WM2003 ROM?
If so what Apps have you added?
How much ROM space does it use?

I've not added any apps to my ROM. I have only added a carrier logo file and made some changes to the registry. So I cannot comment on ROM space yet. The ROM works fine.

sheran_g,
what command did u use to extract rom files? did u do it under windows or unix?
I'm having problems trying to dump the rom image. I don't know if its too much to ask, but can u zip ur directory and post it somewhere so i can download it? or if u can post commands that u ran to dump the 2003 rom?
thanks
alex

Hi,
could you include "O2 home zune" to the 2003 image, like in the 2002 3.19 GER. Its for Germany interested only!
AR :?:

home zone depends on specific 3.19 rilgsm features. which are not in 4.*

okay, used dumprom -4 -d files -q nk.nbf and extracted all files. Got could not find pointer for ofs 00000000 ERROR but all the files seem to be there. Trying to figure this out. Saw the above abreviated directions but am fumbling around. Anyone have concise directions?
Val

Anyone? Just give me a good hint then please.

Hi all!
When i overwrite the rilgsm.dll file in the t-mobile 4.0.10 image with the rilgsm.dll from the O2 GER 3.19 image, i could use the "O2 home zone" option with the hz.exe in Starup directory? rilgsm.dll from german image hes 'at+creg=2' string in it. probably the RIL_GetCellTowerInfo call is now implemented. When it can work, how could i write the german rilgsm.dll to the image? I haven't linux, could somebody cook the image for me?
here is the germen rilgsm.dll and the hz.exe for the "home zone" funktion! http://www.nokiaprog.de/XDA/home_zone.zip
THX
PS: Sorry, my english! ;-)
AR

the homezone enabled rilgsm.dll depends on other dll's and exe's.
probably ril.dll, stk.exe, cell*.dll and maybe more, I have not tried
replacing all.
you don't need to build a new rom in order to experiment with this, you
can just copy the desired files to \windows, to override the rom versions.

And I don't think it works with the RIL_GetCellTowerInfo call,
but adds some notification events.
to change the CREG setting you need to call RIL_DevSpecific with parameter 25 ( to turn it on ) or 26 ( to turn it off )
even though that does not seem to be how hz.exe does it.

Hi,
I opened the image file in the Hex editor and renamed the file there rilgsm.dll. Then I flashed the image, which was phone probably deactivated, because rilgsm.dll was missing. Then I copied over ActiveSync the German rilgsm.dll into the Windows directory, XDA reset and he not accept the file. I assume because the file was not in the EPROM memory! Therefore I wanted to have rilgsm.dll first times in the image!
AR

XDA developer Itsme said:
my latest romtools can be found at romtools
now it calls dumprom to find and fix the filedata offsets.
I think they should now build 2003 roms.
Click to expand...
Click to collapse
Is there any other way i can access this site or I can download this files, the sites are block here in my country, Please Help
Ronnie

Remove files from ROM

How can I remove from the original ROM some files like T-Mobile, AIM ... etc. ?
I cooked up a 4.00.10 T-Mobile with GPRS monitor and batterypack but i want some more addons.
Can someone tell me what steps are required to remove from the ROM some files ?
Thanks,
Decebal

ROM = Read Only Memory.

But, i've we're able to add Programs to the ROM in the ROMkitchen, i think we're also able to remove programs.
Regards
Stefan

cruisin-thru said:
ROM = Read Only Memory.
Click to expand...
Click to collapse
obviously i do not deserve that
i was talking about the ROM image and since i've already succeded in putting into the ROM two apps i want to try something else.
so if anyone know how to remove at least T-mobile and AIM files from the image i'll be happy.
thanks,
Decebal

I believe they are in an area not able to be modified.

I was just quoting from that site, it does state that it cannot be erased, modified etc, no offence meant here. :roll:

The mkrom tools will allow you to 'unpack' a rom, i.e. extract all the files that are in it.
A rom, to the best of my understanding, has a 'native' or stock part to it, and then a series of XIP chains -- programs that are added into the free spaces of the rom.
I dont know what happens if you try to remove files from a rom that are part of the standard build...
Maybe the TMobile stuff is in a 'removeable' section of the ROM... there is also the 'operator' section... I am assuming that is a location that will give the 'operator' or creator of the rom space to put specialized programs, such as TMobiles phone apps, etc.
So, it seems that your best bet is to get the mkrom tools and read about how to extract/remove files/rebuild a rom.
Hey, it may even work!
J

You can rebuild a rom image from extracted files and leave some files out but Mkrom does not use compression and therefore the rom you end up with will probably be bigger than the rom you started with.
Richard

If I am correct, an eeprom is something else than a flash-rom.
so the article at least states it incorrectly.
if it is flash, you should be able to modify it.

XDA developer Itsme said:
If I am correct, an eeprom is something else than a flash-rom.
so the article at least states it incorrectly.
if it is flash, you should be able to modify it.
Click to expand...
Click to collapse
Now, I do think that the real question is "How do we unlock the 'ROM' so that it can be modified being that it is an eeprom?"
Misterdollymaker

you need backup the ROM to *.nb1 or *.nbf file, than using tools to add/delete file to *.nb1 , write the new file back to XDA ROM. it is fun to add/delete file to your personized ROM!

cgigate said:
you need backup the ROM to *.nb1 or *.nbf file, than using tools to add/delete file to *.nb1 , write the new file back to XDA ROM. it is fun to add/delete file to your personized ROM!
Click to expand...
Click to collapse
this is quite interesting...can you elaborate further?? I wish to learn more...

cgigate said:
you need backup the ROM to *.nb1 or *.nbf file, than using tools to add/delete file to *.nb1 , write the new file back to XDA ROM. it is fun to add/delete file to your personized ROM!
Click to expand...
Click to collapse
Yes, please! I wish to learn more too! I am looking to remove the standard sounds and replace them with my own (using same names) as well as the boot image and desktop.

yea, no kiddin, i'd like to know how too!
im sure its not impossible, 'they' did it the first time arround.
why not hacking it? and since its all at no charge (no profit) are we realy breaking any patents?

I wanted to know if there is an easy :wink: way around, to put our own programs in the rom. xda-developers certainly can't put ezwap2.5, and the total commander appears to be older version, while new version is much better. There are some more freeware application I'd love to put in there

xda-developers already posted some tools to do job, such as MKROM ...

cgigate said:
you need backup the ROM to *.nb1 or *.nbf file, than using tools to add/delete file to *.nb1 , write the new file back to XDA ROM. it is fun to add/delete file to your personized ROM!
Click to expand...
Click to collapse
I'm interested too
How can i add/delete file from nb1 file?
Thanks
Fabio

I've used mkrom suite to do this (even for Smartphone2002). This are great tools.
Unfortunately it's not as easy as you might think. It's nearly impossible to build a ZERO-KNOWLEDGE ROM file explorer which can add or delete files "on the fly".
You will still have to look for valid gap's in the original rom where you can add a new XIP block.
All .exe and .dll files are "fixed up" that means they MUST run at THE fixed ROM position where they have been initially placed (execute in place). If you dump an exe or dll file you can't use it for other than disassembly to see how things work.
Removing files is a very hard task (they are splitted over the whole rom). And the resulting gap's are mostly not more than 10-16 kB. All you can do is to "hide" files (simply patch the directory entry).
So you see compression is not the real problem (see programers corner for a .bib file which can be used with romimage.exe - a Microsoft Tool to build XIP blocks, this tool supports compression)
John Smith

only the kernel actually runs in the virtual memory area mapped to rom,
all the other XIP stuff runs from a virtual memory area mapped somewhere
in the top of each processes memory space.
( look at the 'real=' values in the output of dumprom )
so for all the other modules it should be possible to move them around
in rom a bit, I think you only need to keep the pagealignment the same.

Hi,
The virtual memory address is also fixed in the module. (That's why I've to rebuild all the stuff I want to copy from other roms).
Since all relocation info is gone the module can't run from another memory position. So the only thing you can do is to move it in it's own XIP section...
John

Guide to Cooking Universal Extended Rom with FILES

Hello,
I have read that some people have been having a bit of trouble with customising their extended rom on the Universal. So here is my attempt at creating a guide, as a way of saying THANKS to all who helped me in these forums to create my own customised ROM's on the blue angel and my current EXEC.
First thanks mainly to Buzz for the Ext Rom Unlocker and also to BeyondTheTech for the Disable Security Cab.
Also thanks to all other members who contributed their trials and files in the thread.
IMPORTANT - DO A BACKUP BEFORE DOING THIS AS A HARD RESET IS REQUIRED!!!!
Here Goes:
This is how i did it:
1. I created a folder on the desktop called Exec, and inside i created 2 folders called Orig Rom and Cooked Rom
2. I then downloaded the following 3 files and placed them into the Exec folder.

3. i copied the unlock policies and the ext rom unlocker onto sd card and copied them to the phone.
4. i ran the unlock policies cab first then the ext rom unlocker cab
5. under programs i clicked on ext rom unlocker to execute the file
6. it then said succesful and reboot to finsh
7. once rebooted install total commander from below.

8. i then ran total commander and typed in /extended_rom (note underscore) and it displayed the contents of the exteneded rom that originally came with the phone.
9. selected it all and copied the contents to SD card.
10. if you connect your phone directly to pc then you can copy the contents directly to the 'orig rom' folder you created earlier, or use card reader to do same.
11. either way you have the contents of the ext rom on the pc. i then deleted the contents of the Extended_Rom on the phone.
12. the next steps are done on the pc.
13. copy the autorun.exe and the config.txt file from the 'orig rom' folder to the 'cooked rom' folder.
14. copy all the CAB files that you want to be installed upon hard reset into the cooked rom folder aswell.
15. copy the disable security.cab file into the 'cooked rom' folder aswell
16. you will need to rename the cab files that you want installing in the following format:
Default_Unsigned_xxxxxx.cab where xxxxxx is the name of the file
17. if the cab files have long names then just rename them!
18. if you wanted to keep some of the original cabs from your extended rom then copy these into the 'cooked' folder aswell but leave their naming system alone ie:
Signed_UNI_Remove_BatteryIcon.sa.CAB
19. once these have been named as above open the config.txt file
20. it needs to be prepared into the following format :
LOCK:Enabled
CAB: \Extended_ROM\Default_Signed_DisableSecurity.CAB
CAB: \Extended_ROM\Default_Unsigned_tcpmp.arm_ce3.cab
CAB: \Extended_ROM\Signed_SSD_BTUR_Patch_For_BT_Cannot_Initial.sa.CAB
CAB: \Extended_ROM\Default_Unsigned_Porta-Pinball.CAB
RST: RESET
this is an extract from my config.txt file
21. i used the existing file and amended the entries, add/deleted some of the entries.
22. note the space between Cab: \ this is important.
23. also note that the first file that i wanted to install was the disablesecurity.cab file, without this the other 'personal' cabs will not install.
24. so once you have edited and saved your config.txt files making sure all spelling is correct (also an important thing otherwise the files dont install) and no warnings are issued either! you will have in your 'cooked rom' folder:
autorun.exe
config.txt
and several cab files
25. select all the files and then 'right click' on properties.
26. select the 'read-only' option and ok
27. i found that after the first install some of the cab files delete themselves! this prevents that from happening.
28. connect your phone to the pc
29. using active-sync Explore device and navigate to the Extended_Rom folder
30. copy all the contents of your 'cooked rom' folder into the Extended_Rom folder
31. once completed, disconnect the phone and perform a hard reset.
32. after you have aligned screen and done the start-up routine it will start installing your personallised cab files.!!

33. You should now have an Exec, customised with your own extended rom and as a bonus a complete back-up on your pc.
34. if ever you upgrade the phone rom/radio etc, all the software you need and the perosnlaised rom is ready to go.
if i have missed a step plz post back and i will edit my posts and put in there.
I cannot stress how important it is that you make a backup first before doing this as you will lose everything on the phone.
Bye for now!!!

Gr8 Work!!!
hi there this is a perfect guide well done m8
only one question as i have the jasjar and i-mate rom on it
i do not have the config.txt file
how do i tell the device to install my personal/third party cab files
thanx in advance

mail attachments
Thanks for the guide, however when i use total commander, extended rom is shown with the same symbol as storage card and I cannot get the mail programme to save attachments to the real storage card as the universal thinks the extended rom is the storage card.
How can the properties of the extended rom be changed so it does not appear to be a storage card ?
Thanks
Steve

Re: Gr8 Work!!!
krassen said:
hi there this is a perfect guide well done m8
only one question as i have the jasjar and i-mate rom on it
i do not have the config.txt file
how do i tell the device to install my personal/third party cab files
thanx in advance
Click to expand...
Click to collapse
i have the same problem, any solution?

the solution to that can be found here:
http://www.buzzdev.net/index.php?option=com_simpleboard&Itemid=59&func=view&catid=40&id=7869#7869

Re: Gr8 Work!!!
majdi said:
krassen said:
hi there this is a perfect guide well done m8
only one question as i have the jasjar and i-mate rom on it
i do not have the config.txt file
how do i tell the device to install my personal/third party cab files
thanx in advance
Click to expand...
Click to collapse
i have the same problem, any solution?
Click to expand...
Click to collapse
I just renamed the required cab file by adding "Default_" to it. That did it.

Thanks
But I have been through the thread numerous time.
The mail programme thinks the extended rom is the storage card.
The thread has a fix to hide the extended rom so the mail programme now saves attachements onto the real storage card.
It just seems a shame to have gone to all the trouble to unlock and make visisble the extended rom, just to hide it again so the mail programme can save onto the real storage card.
Am I missing something. Simple guidance PLEASE.
Steve

hollytree said:
Thanks
But I have been through the thread numerous time.
The mail programme thinks the extended rom is the storage card.
The thread has a fix to hide the extended rom so the mail programme now saves attachements onto the real storage card.
It just seems a shame to have gone to all the trouble to unlock and make visisble the extended rom, just to hide it again so the mail programme can save onto the real storage card.
Am I missing something. Simple guidance PLEASE.
Steve
Click to expand...
Click to collapse
When the hard reset is done the whole point is for the Extended Rom to be hidden again. This ensures that at any point in the future if a hard-reset is required then the phone is setup agian as you want it.
At the moment the Extended_rom partitrion cannot be used as a storage space , and i believe Buzz is working on that.
So my guide illustrates deleting existing rom, and replacing with personalised rom and then hiding it agian.
Above this thread is a link to Buzz's small tutorial to alllow attachemnts to be saved back to storage card instead of the Extended Rom for those who want to leave it Un-Hid.
Regarding those without a config.txt file then renaming everything to Default_xxxxx.cab does the trick.
thanks

This is a GREAT thread. Hats off to you.
Personally, I think I'm going to add the T-Mobile USA Internet Settings cab to "cooked" stuff (I'm in the US).
Does anyone have a cab that will set up the gmail pop settings (w/ generic un/pass of course)? Lazy, yes, but I'm just trying to make any refresh that I would ever need to do that much simpler

i have another question as we have a lot of good registry tweaks....
is it really that hard to create cab files for those registry settings and just throw those in the extRom
regards
krassen

flippy said:
the solution to that can be found here:
http://www.buzzdev.net/index.php?option=com_simpleboard&Itemid=59&func=view&catid=40&id=7869#7869
Click to expand...
Click to collapse
my problem is that in wm5.0 there is no config.txt file to tell the os what to install from the ext rom, i unlocked the ext rom and moved all contents to pc, i also deleted all the existing files from it, and i have all my cabs ready, but the problem is how to tell the installer to take these cabs instead of the origionals?
does it take it automatically, or should i do something to make it install my personalised ext rom?

majdi said:
flippy said:
the solution to that can be found here:
http://www.buzzdev.net/index.php?option=com_simpleboard&Itemid=59&func=view&catid=40&id=7869#7869
Click to expand...
Click to collapse
my problem is that in wm5.0 there is no config.txt file to tell the os what to install from the ext rom, i unlocked the ext rom and moved all contents to pc, i also deleted all the existing files from it, and i have all my cabs ready, but the problem is how to tell the installer to take these cabs instead of the origionals?
does it take it automatically, or should i do something to make it install my personalised ext rom?
Click to expand...
Click to collapse
If you dont have a config.txt file then you need to rename your cab files in the following format:
Default_xxxxxx.cab where xxxxx is the name of your file. this has been found to work in your phone.
thanks

many thanx to u.
this worked just fine.
cheers

disable security cab
Does anyone know where I can download the DisableSecurity.CAB as the links no longer work.
Thanks
Steve

Re: disable security cab
hollytree said:
Does anyone know where I can download the DisableSecurity.CAB as the links no longer work.
Click to expand...
Click to collapse
Did you try the first post in this thread?
You have to register and be logged in to see the files...

links worked for me

l6cum said:
majdi said:
flippy said:
the solution to that can be found here:
http://www.buzzdev.net/index.php?option=com_simpleboard&Itemid=59&func=view&catid=40&id=7869#7869
Click to expand...
Click to collapse
my problem is that in wm5.0 there is no config.txt file to tell the os what to install from the ext rom, i unlocked the ext rom and moved all contents to pc, i also deleted all the existing files from it, and i have all my cabs ready, but the problem is how to tell the installer to take these cabs instead of the origionals?
does it take it automatically, or should i do something to make it install my personalised ext rom?
Click to expand...
Click to collapse
If you dont have a config.txt file then you need to rename your cab files in the following format:
Default_xxxxxx.cab where xxxxx is the name of your file. this has been found to work in your phone.
thanks
Click to expand...
Click to collapse
It's shuld be Default_xxxxxx.cab or Default_Unsigned_xxxxxx.cab / Default_Signed_xxxxxx.cab, now ?

Is there an autorun.exe that points to..

Howdy.
Does anyone know of an autorun.exe which is coded to look in "extendedROM"? (As opposed to "extended_ROM").
I'm aware of PocketPC Installer and that it probably can create a custom autoexec.exe for me, but I'm looking for a free solution if there's already one hacked up out there.
Thanks
--SUmmiter

I thought that it got that value from the registry:
[HKEY_LOCAL_MACHINE\Comm]
"AutoRun"="\\Extended_ROM\\AUTORUN.EXE"
"AutorunCFG"="\\Extended_ROM\\CONFIG.TXT"
"AutoRunType"=dword:0
"TurnRadioFlag"=dword:0

Yes but you have to add this into rom before building if you want it to look for autorun there after flashing

Right. My possibly incorrect assumption was that autorun.exe is hardcoded to look inside "Extended_Rom" for it's config, ignoring what is in the registry. I'll mod my OS rom and try changing AutorunCFG and see what happens.
joemanb said:
I thought that it got that value from the registry:
[HKEY_LOCAL_MACHINE\Comm]
"AutoRun"="\\Extended_ROM\\AUTORUN.EXE"
"AutorunCFG"="\\Extended_ROM\\CONFIG.TXT"
"AutoRunType"=dword:0
"TurnRadioFlag"=dword:0
Click to expand...
Click to collapse

Autorun.exe and config.txt can be anywhere as long as the registry points to them.
(if the registry points to Extended_Rom, then of course the files need to be included in the Extended_Rom.)
My autorun.exe is in windows, and config.txt is in the extended rom, but I've tried it other ways and it's worked.
alot of cooked roms use this feature to do a final modification like loading a theme from the windows directory.
BTW config.txt contains the paths to the files you wish to process, so it doesn't matter where autorun.exe, or config.txt are.
In other words, you could put autorun.exe, and config.txt in windows or anywhere else as long as the registry points to them, and it will process the files on the paths contained in config.txt

Little question, has autoexec any link in startup, or not?
(I make in intiflash registry entry es mentioned before, I have hope corect congig.txt but after HR ... nothing, co customization . Interesting is, that I can launch autoexec in ext rom manualy and it runs ok. I rebuld quite naked WM 6.1 rom)
Thx for help...

[Q] [PROBLEM][HERMES-TYTN]Default.hv cooked ROM

Hi,
I have a really strange problem.
I have two HTC HERMES, one good that I use and a second that I use only fot test purposes because it's not in good conditions.
I cook ROMs with "ROMDonalds Kitchen" and I have neved had any problem.
Since yesterday, every new ROM I cook, I have this problem:
if I don't edit "default.hv" the cooked ROM goes well in both my HERMES, but if I edit it, the ROM can only be loaded on the second HERMES (the one not in good conditions).
In the other HERMES after flashing, when I make the reset or even the hard-reset, the ROM begins to boot but then stops after the first splash-screen and the screen becames white.
I always flash from SD (hermimg.nbh).
What can be the problem?
Can be a problem of the good HERMES of the two I have?
Can be a difference in hardware between the good HERMES, even if they are identical from outside?
Many thanks !

Hi,
I don't understand why you need to edit default.hv but probably you have your reason.
It's better to leave it untouched to my opinion.
To edit the registry you can edit the .rgu in the specific package or create
a new package with the new registry overwriting the first package registry.
The second suggestion you can keep your tweaks in every rom you cook and switch the stock packages more easy.
What you are writing is indeed weird but this way you avoid errors in the .hv files.
Edit; btw, because Hermes is a pretty old device I'm asuming the kitchen you use is still using .rgu instead of .reg in the packages, latest kitchens mostly use .reg
.rgu and .reg files are same and containing the registry.
Grtz,
Laurentius26

yeah its true, what do you change in the d.hv? maybe you can tell us, what about to use another kitchen? or do your changes in app.reg ext pkgs or in oem packages to void edit it

I edit .hv files when I add or remove programs from the ROM.
I've tried also Ervius kitchen but when I try to dump my ROMs It gives me some errors...the only kitchen I was able to use is RomDonald's..
Can You suggest me another good one?
Thanks

Airxtreme's Oskitchen or Barin's OSbuilder, they are both in Chef Central here.
You don't need to edit .hv files as when you remove the package all registry of that package will be gone too.
eryunt said:
I edit .hv files when I add or remove programs from the ROM.
I've tried also Ervius kitchen but when I try to dump my ROMs It gives me some errors...the only kitchen I was able to use is RomDonald's..
Can You suggest me another good one?
Thanks
Click to expand...
Click to collapse

I dont think ROMDonalds processes rgu files. If I remember correct, you have edit the hive files to use that kitchen.

Wow, that's gotta be a huge pain in the butt.

ai6908 said:
I dont think ROMDonalds processes rgu files. If I remember correct, you have edit the hive files to use that kitchen.
Click to expand...
Click to collapse
Yes, It is correct.
But the strange thing is that only one of the two Hermes I have, accepts the ROM after I edit the .hv files...
The question is:
Is there a separate memory where the hive is stored, and can this memory be faulty in one of my Hermes?

eryunt said:
...Is there a separate memory where the hive is stored, and can this memory be faulty in one of my Hermes?...
Click to expand...
Click to collapse
If you mean the fixed address - the answer is No. *.hv are files and files do not have the fixed address.

I've tried also Ervius Visual Kichen, but when I dump my ROM It gives me these two errors:
1- "Xipkernel's DSM not found! I'll create new...Maybe protected XIP (not portable !!!)"
2- "Boo.rgu in xip not found!Create new...But maybe ROM will be NON BOOTABLE !!!)"
What's wrong?
Thanks for all the answers You provide !
XDA, really a great Community !!!

Hi,
I don't know what you are doing to setup Ervius?
Are you importing a new stock rom into the kitchen?
The errors you can check:
Ervius kitchen/Rom/Shared/'Sys build'/MSXipkernel/
boot.rgu and the .dsm should be there.
Without boot.rgu and the dsm the rom won't boot.
Are all your desktop system files unhidden and vissible?
eryunt said:
I've tried also Ervius Visual Kichen, but when I dump my ROM It gives me these two errors:
1- "Xipkernel's DSM not found! I'll create new...Maybe protected XIP (not portable !!!)"
2- "Boo.rgu in xip not found!Create new...But maybe ROM will be NON BOOTABLE !!!)"
What's wrong?
Thanks for all the answers You provide !
XDA, really a great Community !!!
Click to expand...
Click to collapse

The visualization of hidden files is active in my PC, and I am trying to import a NON STOCK ROM to add or remove packages.
Ervius kithchen gives me the errors I described, and also OSKitchen gives me errors..
Can these kitchens import only STOCK ROMs?
I used ROMDonald's kitchen because It was able to edit a ROM that was already cooked...but the editing of .hv files is wrong...

I advise you to use a stock rom as you can test if everything is working ok.
After this you can do your modifications.
I know it's a bit of work but the advantage is to use a new kitchen which is much more configurable.
Editing .hv files isn't that good, but we talked about that already.
Another tip, I always zip my kitchen after I know a configuration is working and I flashed the rom succsesvol, before I continue to the next step.
eryunt said:
The visualization of hidden files is active in my PC, and I am trying to import a NON STOCK ROM to add or remove packages.
Ervius kithchen gives me the errors I described, and also OSKitchen gives me errors..
Can these kitchens import only STOCK ROMs?
I used ROMDonald's kitchen because It was able to edit a ROM that was already cooked...but the editing of .hv files is wrong...
Click to expand...
Click to collapse

eryunt said:
Yes, It is correct.
But the strange thing is that only one of the two Hermes I have, accepts the ROM after I edit the .hv files...
The question is:
Is there a separate memory where the hive is stored, and can this memory be faulty in one of my Hermes?
Click to expand...
Click to collapse
It doesnt make sense why one device would run it, and the other one dont! Are you sure the hive files do not have any errors?
Try to flash a stock ROM first, then flash the cooked one. I know hermes has ext storage, and that can through errors...

ai6908 said:
It doesnt make sense why one device would run it, and the other one dont! Are you sure the hive files do not have any errors?
Try to flash a stock ROM first, then flash the cooked one. I know hermes has ext storage, and that can through errors...
Click to expand...
Click to collapse
That's the point...It's a nonsense..
I've already tried to flash stock ROM on both devices before flashing the cooked ROM, but It's always the same nonsense, one loads the ROM, the other doesn't...
At this point only a malfunction or a difference in hardware between my two devices could explain this strange behaviour
Don't know how to solve...

are you trying to recook my roms? hahaha just kiddin
everybody knows that we don thave bootable and full dumped roms from customized ones, due to DSMsif you want to make a roms looks like or be something like a... i recommend to ask for the kitchen many retired chefs on Legacy devices can share it to you or just dump the rom and xtract the things you want
but make your own Stock OEM an set good your Native Kernel