Problem with an extracted ROM - Tilt, TyTN II, MDA Vario III Windows Mobile ROM De

Hello,
I extracted Schap's ROM 4.31, no problems until that.
But when I want to reconstruct it with Ervius package tools + Build OS, without adding any package (so no cooking if I can tell that...), there are some problems when it come to the last process, the "Registry file processor and hive builder.". It tell me that : 'InitRegistry FAILED in file ".\Registry\1dc3da02-499f-4547-9fd2-78cddfda9c62.rgu" within a few lines of line 1.'
So, I looked at this RGU file, and indeed, the file is empty ! And there are many other RGU in the same way !
So, what is the problem ? Bad extraction ?
Thanks in advance.

Ok,
Nobody wants to help me ?
Why ?

up!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

It's been posted in the ROM kitchen thread and the reconstructing ROMs thread many MANY times. You can't re-cook certain chef's ROMs, because they don't include .RGU files.
Hope this helps!

Thanks you very much Alex, I read the Kitchen thread, but may me be not wholly...
So, is there a possibility to include the missing rgu's from other rom ?
Just another question,
during the past weeks I reconstructed my factory ROM, there wasn't all the RGU files too, but however, this has worked... Why ?
Thanks a lot for your great patience...

Pascal06 said:
Thanks you very much Alex, I read the Kitchen thread, but may me be not wholly...
So, is there a possibility to include the missing rgu's from other rom ?
Just another question,
during the past weeks I reconstructed my factory ROM, there wasn't all the RGU files too, but however, this has worked... Why ?
Thanks a lot for your great patience...
Click to expand...
Click to collapse
Some directories just won't have RGU files, which is ok. This is what you've encountered with your factory ROM.
RGU files are important because they contain registry information. Taking them from another ROM is going to be a very painful process, and that's also where 75% of the customization takes place, so losing the important registry information from the original ROM will make it less than useful.
For more information about RGU files, read my OEM Primer from my OEM Package Tutorial...
Hope this helps!

Thanks you Alex,
I already read your OEM primer tutorial.
In fact, if I wanted to cook the Schap's ROM, it's because the included Arcsoft MMS program doesn't work. So, I wanted to include yours (the last version 5 cab), and others app, eg. MS voice command and Transcriber.
I'm very ashamed...

Pascal06 said:
Thanks you Alex,
I already read your OEM primer tutorial.
In fact, if I wanted to cook the Schap's ROM, it's because the included Arcsoft MMS program doesn't work. So, I wanted to include yours (the last version 5 cab), and others app, eg. MS voice command and Transcriber.
I'm very ashamed...
Click to expand...
Click to collapse
Why be ashamed? It's good that you tried something new and even if it didn't work as expected, it was a learning experience.

Related

Rom cooking on Vox

Hi all, I've been trying for quite some time to cook my first rom. I've now read a lot on the subjects here on these forums but it seems the vox is not the easiest device to start with I've successfully extracted all files from an .nbh rom upgrade. I've then extracted everything to /dump folder using prepare_imgfs.exe and imgfstodump.exe. Here I can delete/change/add files in the directory and rebuild the rom with buildimgfs.exe but it is not a very clean cooking... I'd like to be able to use Package tool. Actually I can use it and get the two folders /OEM and /SYS but then I really don't know how to rebuild the rom using Buildos.exe. Does anyone know how to do this ?
Tell me if my english is not very understandable..
I've finally been able to use these tools after a lot of trials and errors. But there is a lot of fixing to do in the building process. For exemple after running OEM and SYS folders through BuildOs a lot of files are missing in temp\dump
It seems every important file is missing in each of the subfolders. Missing dll's, missing exe's...
For example if I look in the zlib.dll\ directory I can see 5 files : imageinfo.bin, imageinfo.txt, S000, S001, S002, S003 BUT no zlib.dll ?! So I have to manually reimport those files... Is this a known issue with buildos and if so is there any solution to it ?
Thanks for any help
My bad, just realised reimporting the dlls is not at all needed
Still speaking alone ?
Perhaps this thread from the Kaiser forum helps you.
Dr Gonzo.... i would have lied to said something but my knowledge of cooking ROMs is zilch.... but i was hoping someones cooks a ROM for the Vox ... so wanted to ask u how its going?
I've been able to build an awkward "kitchen" for the Vox but I don't know yet if the roms built with it are really stable. Awkward because I don't really know how to write batch files and because I had to add a .dsm taken from Bepe's kitchen for Buildos.exe to work (but I delete it once the dump folder is rebuilt). But I have been able to add/remove packages and it seems to work.
I am currently building my rom from the Arabic one with smarttoolkit included, custom system screens, commanager and homescreen, office and HTC audio manager removed, windows live updated, Jbed instead of Jeodek etc... It seems to be stable but some things don't work yet (I still need to edit the registry)
But what I'd really like would be the possibility to add Bigstorage to the rom as it increases free memory from what I've read.
Maybe I can release this kitchen with some instructions and someone better than me could improve it ?
RE
Yeah that would be awesome to get some Vox Rom cooking happening when can you post your kitchen?
I'm in the process of writing a quick guide to go along my very dirty kitchen to show how to use it. For the moment only with HTC_Vox_ARA_1.27.415.4_4.1.13.47_02.98.90 as a base rom because I haven't tested anything else yet.

Learning to cook. Need a little help

I'm using alex's kitchen and am trying to create a cooked wm6.1 rom from the CE OS 5.2.19170 (BUILD 19170.1.0.0).
I've extracted the rom loads of times and can create a flashable RUU_signed.nbh with additional apps from packages (and some packages i made myself) but if i try to add the new polaris camera or anything that the rom may have a previous version of it errors out and can't create the default hives.
It says for a lot of the added packages they do not contain rgu's.
Anyone fancy trying to mentor me a bit?
read the wiki on how to make oem packages bro im in the midst of making my own custom rom right now based off of dcs1.1
Cheers for the reply.
I've done that and made some working packages but it seems thats not the problem. i think i need to remove all the older stuff from oemapps first but i don't know how to do that and can't find any pointers.
I know i could start deleting stuff but thats probably not wise.
ive been lerning myself the past 3 days non stop just testing n testing new stuff seeing what goes well, trying to take pkgs from roms and merge to other etc takes some time but ull get it if u keep at it, i really recommend the packages creator 5.4 util for making ur pkgs
i just wish i cood find the pkgs for dutties beautiful red phone dialer and call history etc. i tried removing it but its a bit too advanced for me atm
I've been using the package creator in the kitchen (ervius' one).
I'm on nightshifts at work and i think the sleep deprivation is making me miss the obvious.
I'll stick at it for a bit though and then have a proper go when i get a day off.
I'll have a bash with the rom your using as its got the camera in already but i'd still like to know how to do it myself.
Now where'd i put that cup of coffee?
oh and i find with the pkg tool i have to delete the rgu files to avoid the hv registry errors in buildos hope that helps
It says they are missing for most of them anyway.
Please watch this.
to get my pkgs to work i found that i had to uncheck prefix files and leave all others checked, then after creating the pkgs i delete the rgu files
_Alex_ said:
Please watch this.
Click to expand...
Click to collapse
Now that's funny.
Now i know it's the wrong thread and all but i don't want to start a new one just to thank you for your kitchen and tutorials. So ta very much.
xzon said:
to get my pkgs to work i found that i had to uncheck prefix files and leave all others checked, then after creating the pkgs i delete the rgu files
Click to expand...
Click to collapse
Cheers for the advice xzon.
I'm gonna call it a day for now but will definitely check out what you've said.
_Alex_ said:
Please watch this.
Click to expand...
Click to collapse
Thanks Alex

A plea to all ROM Cookers!

Guys,
we love what you do, and we couldn't do it ourselves, *but* most of us could (and would like to) remove/add the odd OEM pkg or so. And be honest, that's probably how you all got started, too.
However, these days, it isn't possible to easily do. Hypercore Kitchen (which is wonderful) doesn't work for either Ranju or PDAViet ROMs, and I've had limited success with other recent ROMs.
I for one (and I know I'm not alone) would love to make my own custom ROM based on some of those out there, but because of problems, can't.
So - PLEASE - as well as your ROM, please post your kitchen somewhere.
Thank you!!
-Paul.
I second this request. I am currently using a custom builtRom I built using hypercore from an earlier Ranju WM6 ROM and although it works well I always want the latest ROMs and the WM6.1 roms I have tried are so much faster.
Any help would be much appretiated.
Would love to see this too.
I Think Ranju's ROMs are great but I would love to be able to remove total commander and a couple of other bits and pieces.
uMP2k said:
Would love to see this too.
I Think Ranju's ROMs are great but I would love to be able to remove total commander and a couple of other bits and pieces.
Click to expand...
Click to collapse
The Ranju 7.7 ROM have the rgu.cab file. Unzip this file in dump directory and use pkgtool for create oem and sys folder. Use a cooker tutorial for changes.
anmendes said:
The Ranju 7.7 ROM have the rgu.cab file. Unzip this file in dump directory and use pkgtool for create oem and sys folder. Use a cooker tutorial for changes.
Click to expand...
Click to collapse
Thanks for the tip, I have taken the rgu.cab file and now have them incorperated into the OEM folder after running pkgtool. However I still get an error that comes up when i use any uild rom tools. It runs through all the files fine but after i have "pressed any button to continue" it comes up with an error about the partition and then says it is safer to abort.
Could you let me know if you have successfully rebuilt a personal rom and exactly what tools you used.
Thanks
Dan

Can anyone help me to debug my first rom

Hey guys,
I am working on my first rom. After going through many readings from other sub-forum (hermes and kaiser) as well as Ivan's cooking class, I made my first rom using the Wing stock rom. After deleting un-used packages and files, I can sucessfully build the os.nb and converted it to .nbh file. But when I tried to flash it back to the wing, I got a error saying my RUU cannot used to flash the device, but I have been using this same RUU for many roms. I attached the screenshot, please take a look and help me debug it. It's my first rom Many thanks
go and try when you buld .nbh to set device "herald" but in section "version" write "test" not the numbers that are there by default.....
hope that helps.
Yep, looks like you didn't set it to Herald when you built it.
Thanks. You guys are right. I can flash my rom now. However, it stuck in the primary splash and does not response to the stylus. Any idea how to fix? Again, really appriciate any help.
live4nothing said:
Thanks. You guys are right. I can flash my rom now. However, it stuck in the primary splash and does not response to the stylus. Any idea how to fix? Again, really appriciate any help.
Click to expand...
Click to collapse
This is part of the fun of being a cook, figuring out what mistakes we made.
There could have been 1 million different things you could have done that made it not boot up. It could have been something you removed or something you added. What kitchen are you cooking with? (It could also be that you didn't relocate all the modules if you're using something like hypercore.)
ivanmmj said:
This is part of the fun of being a cook, figuring out what mistakes we made.
There could have been 1 million different things you could have done that made it not boot up. It could have been something you removed or something you added. What kitchen are you cooking with? (It could also be that you didn't relocate all the modules if you're using something like hypercore.)
Click to expand...
Click to collapse
I am using hypercore. Can you point me to a reference to use hypercore or maybe an better kitchen for new cooks?
Either use G'Reloc for hypercore, or use Bepe's Extended Kitchen for the Herald. The latter option would be the best.
After re-doing the delete packages part, I got the rom flashed into my wing, booted, but nothing working. I mean windows started, top and bottom bars also loaded, but radio not working, nothing reponses. One thing, the screen seem to flicker a little bit. I notice the boot speed is super fast (really really fast) as in none of the hardware drivers is initialized at all. I am clueless as of this point. Any more help?
@Ivan:
Thanks man. Since I started with hypercore and kind of familiar with it already, I would like to stick with it. Can you show me how to use G'Reloc? Thanks
Just drop the file into your build folder and run it. (Assuming you're using a SYS folder that belongs to your phone.) Bepe's kitchen is great because it does a lot of fixing up for you automatically. It's not a competitor's kitchen, it's a MUCH newer kitchen. I use both. I use Hypercore to take Herald ROMs appart and for different tools in it and Bepe's kitchen to put my ROMs together (and a kaiser kitchen to take appart kaiser, diamond and other ROMs) and I also use my own kitchens which are mostly based out of Bepe's kitchens.
The whole boot speed and nothing working means that you deleted things packages you shouldn't have.
I run G'Reloc, but it ask for slot 1, slot 2, ... Do you mind explain them to me? I tried to just click "do it" with the default values, and it showed that it relocated 265 out of 368. I built the rom and flashed it to my wing, but it stuck in the boot splash now. Thank for the help
Those are taken from a folder in your SYS folder. It sounds to me like you deleted a lot of packages that are essential to WM6/6.1. You can't delete everything that SOUNDS like you don't use. Also, the SYS folder HAS to be from a Herald UNLESS you ported it. If you didn't port it, then the values on slot 1 and slot 2 will be wrong.
I followed your guide to take the SYS from the Kaiser's rom. Here's what I did. I run buildOS.exe, then I run G'reloc, then I run createROM.bat. Did I do it right?
live4nothing said:
I followed your guide to take the SYS from the Kaiser's rom. Here's what I did. I run buildOS.exe, then I run G'reloc, then I run createROM.bat. Did I do it right?
Click to expand...
Click to collapse
Which guide? My guide? You run G'Reloc first and THEN buildOS, or else you're building the OS BEFORE fixing the files that you need to BUILD the OS.
The sequence part, I guess on my own. I meant I follow your guide on porting the SYS and XIP on lesson 4 and 5. I did not even try G'Reloc in the first place because I did not know I have to do it. Btw, thank again man, you're such a big help to me.
The reason why the guide was failing and I hadn't mentioned G'Reloc in the walkthrough is because the walkthrough was made for Bepe's Extended Kitchen. No problem with the help. I remember when I was learning, no one answered, so I figured I'd give something back.
working with OEM
Hey Ivan,
thank to your help, I was be able to cook some roms with the newer SYS and XIP build. During the process, just to learn how to port SYS and XIP, I borrowed your OEM folder (I copied the whole OEM folder form your JustMine kitchen). Now I learned how to port SYS and XIP and get them working, I want to play with my own OEM. Otherwise, I would not be cooking if I copied your OEM. Here what I did:
1) Since I can't find any base OEM folder for herald or wing here, I used hypercore to extract the OEM from the official stock Wing stock rom.
2) I copied the whole OEM without deleting junks (because it failed when I deleted stuffs before. So I want to ensure that I got the OEm working before start deleting stuffs) to bepe kitchen
3) build the rom
Here's what happen:
When i used the stock OEM, my wing can boot into WM, but it skip the screen align, setting timezone and setting password section. AFter that, it say my pout.exe (or something like that) and repllog.exe is currupted. The green light indicating the radio is blinking, but the radio doesn't pick up anytihing, said no service.
If I replace your OEM, everything works fine. So I test my OEM by building it with the stock SYS and XIP, it also works fine. Did I missed anything? Thanks for all your help, man.
live4nothing said:
Hey Ivan,
thank to your help, I was be able to cook some roms with the newer SYS and XIP build. During the process, just to learn how to port SYS and XIP, I borrowed your OEM folder (I copied the whole OEM folder form your JustMine kitchen). Now I learned how to port SYS and XIP and get them working, I want to play with my own OEM. Otherwise, I would not be cooking if I copied your OEM. Here what I did:
1) Since I can't find any base OEM folder for herald or wing here, I used hypercore to extract the OEM from the official stock Wing stock rom.
2) I copied the whole OEM without deleting junks (because it failed when I deleted stuffs before. So I want to ensure that I got the OEm working before start deleting stuffs) to bepe kitchen
3) build the rom
Here's what happen:
When i used the stock OEM, my wing can boot into WM, but it skip the screen align, setting timezone and setting password section. AFter that, it say my pout.exe (or something like that) and repllog.exe is currupted. The green light indicating the radio is blinking, but the radio doesn't pick up anytihing, said no service.
If I replace your OEM, everything works fine. So I test my OEM by building it with the stock SYS and XIP, it also works fine. Did I missed anything? Thanks for all your help, man.
Click to expand...
Click to collapse
This is great news, we have a new herald cook on the way.
I'm very glad to see this since I will be not be cooking any more after my current release is done.
Keep it up bro,
live4nothing said:
Hey Ivan,
thank to your help, I was be able to cook some roms with the newer SYS and XIP build. During the process, just to learn how to port SYS and XIP, I borrowed your OEM folder (I copied the whole OEM folder form your JustMine kitchen). Now I learned how to port SYS and XIP and get them working, I want to play with my own OEM. Otherwise, I would not be cooking if I copied your OEM. Here what I did:
1) Since I can't find any base OEM folder for herald or wing here, I used hypercore to extract the OEM from the official stock Wing stock rom.
2) I copied the whole OEM without deleting junks (because it failed when I deleted stuffs before. So I want to ensure that I got the OEm working before start deleting stuffs) to bepe kitchen
3) build the rom
Here's what happen:
When i used the stock OEM, my wing can boot into WM, but it skip the screen align, setting timezone and setting password section. AFter that, it say my pout.exe (or something like that) and repllog.exe is currupted. The green light indicating the radio is blinking, but the radio doesn't pick up anytihing, said no service.
If I replace your OEM, everything works fine. So I test my OEM by building it with the stock SYS and XIP, it also works fine. Did I missed anything? Thanks for all your help, man.
Click to expand...
Click to collapse
Your missing the SQM package (or at the very least the patched file that you use to bypass it.) http://forum.xda-developers.com/showthread.php?t=393997
ivanmmj said:
Your missing the SQM package (or at the very least the patched file that you use to bypass it.) http://forum.xda-developers.com/showthread.php?t=393997
Click to expand...
Click to collapse
Dude Ivan, you are awsome. I sucessfully created a ROM using my ported SYS, XIP and my own OEM. Again, thank you very much for guiding me through the whole process. I am thinking release it as a lite rom so everyone here can enjoy the newest build if they wish to. Before I can do it, I want to do some tweaks to it. So can you so me how to cook registry entries into the ROM? Thanks
live4nothing said:
Dude Ivan, you are awsome. I sucessfully created a ROM using my ported SYS, XIP and my own OEM. Again, thank you very much for guiding me through the whole process. I am thinking release it as a lite rom so everyone here can enjoy the newest build if they wish to. Before I can do it, I want to do some tweaks to it. So can you so me how to cook registry entries into the ROM? Thanks
Click to expand...
Click to collapse
You've got two options. RGU's and PROVXML's. You're better off setting up a package with an RGU that has all your registry keys. RGU's are nothing more than reg files. ^_^ And I'm glad it worked.

Extract pure OS from cooked ROM

Hi all,
Perhaps it is a newbie question so please bear with me.
I have an i-mate K-Jam flashed with TNT rom (build 20273). It works perfect and nice, however (frankly speaking) I don't like or want some of the APPs installed with this ROM, but I can't uninstall them.
I've searched this forum to find a way to extract the OS (OS only) from TNT rom so that I can flash my wizard and then install all the APPs I want, with no luck. Perhaps my search skills are a little poor...
So would someone please explain if it is possible or not? and if yes, how?
Thanks in advance.
Regards.
You cannot remove apps from a cooked rom. Search for Vanilla roms if you just want the base rom without any extras and then you can install you own apps.
well you can, but for that u'll have to dump the ROM first, remove the apps you dnt like and recook it
you can not dump the TNT roms. when you try, there are no RGU'S or DSM's.
You can dump my rom if you like, but you will get some missing files you will have to put back into the oem.
the missing files come from me not editing the rgu's when I cook.
try dumping Hornet5. for the most part you will get complete packages, but also some "missing files". just put them back into the oem/sys and recook.
Thanks for info. Saved me a lot of time.
I finally managed to cook my own rom. Everything works perfect except that:
1) I've used XIP, SYS and OEM files/folders of different builds. Am I going to have problem later?
2) "CommManager.exe" was missing. I've searched the files used in kitchen and the only thing I found is "commmanager.htm". Later I managed to download and install HTC CommManager but I can't assign in to its button (button 6). Is there any solution for that?
3) How may I extract the "splash screen" from one build, and upload it to my phone?
4) Bluetooth is not working. It says there is no bluetooth hardware on device. Also WLAN disconnects after a few seconds. How may I extract the drivers from original ROM and upload it?
I know the above questions are too much, but actually I'm so excited that my first attempt to cook a rom was successful (almost). I hope one of you experts be kind enough to help me solve the above issues and have a perfect phone.
Thanks in advance.
you will have some problems with the initflashfiles.dat in the oem, as well as the "oemtranslation.prvxml" or something which controls your icons for programs and control panel.
The best thing to do is use the same build OEM SYS & ROM folders.
If you dumped hornet 5, then your best bet ist to work with everything in it. I was working at this rom after Sleurhut for about a month or two.
mixing builds of those folders makes you start from scratch again fixing up your oem again.. and again.
as far as the missing files, try using the Xdump method; or use the searcher on your PC to find the missing files folder and the contents.
Dear S.V.I
Thank you so much for your ongoing support and help.
As I've mentioned before, I'm a total newbie trying to have a clean WM6.1 on Wizard. I've searched and read lots of tutorials here and there, but there are still lots of questions remained.
I tried to play with HyperCore (multi-device) today and I failed in the first step. I've extracted the "nk.nbf" from official i-mate KJam ROM using WinRAR. HyperCore is installed and I've a "C:\Core" folder as well as a "HyperCore" folder on my desktop.
The "DumpRom" is asking me to make sure the "nk.nbf" is in "HyperCore\Extract\Source" folder. Well it is there. Press Enter and the error message says: "There is no nk.nbf in Core\Extract\Source".
No it is not. First, it asked me to put it in "HyperCore\Extract\Source" not "Core\Extract\Source". Second, there is no "Extract" folder under "C:\Core". Even after creating Extract\Source under C:\Core and copying nk.nbf there, the same error message appears again.
So, what I'm missing here?
Same
I'm also scratching my head on this problem too. I've even tried creating extract\source folders in locations C:\core\ and desktop\hypercore\ but still no luck.
I'm wondering however that the issue could be caused by vista/7's change from Documents and Settings\user\desktop (2000, XP) to Users\user\desktop.
It may change the way the batch files are called but i'm really rusty on batch commands these days
I would start with the sticky "How to cook a ROM" thread, focusing on CRACING's kitchen, then move to Nekid Angel (Post #3)
where you will find a more updated ROM ready to cook. If you want to try WM6.5 a good ROM and kitchen is at [WM Kitchen] Wizard Kitchen or CRACING's RC6. I have been playing around with that.
You might move your discussion to one of the cooking or kitchen threads mentioned above, too, since that is where others will look.
Perfect
That's what i was looking for thanks for the heads up N2rjt!

Categories

Resources