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.
Related
As promised, here are Just2Clean's kitchen files. You will need to use either JustClean's EasyBakeOven or Bepe's kitchen in order to use them. Just download either of the kitchens, delete the OEM and SYS folders and replace them with these.
This does NOT include my micro Extended ROM, but if you've flashed my ROM, you already have it installed.
Linky It's the Working_Folder
sorry still kinda new to all this ROM cooking...
So this is a newer build of the OS?
I the just2clean kitchen you released I want to keep all those packages I have in there so all i have to do is add the files from this OEM folder to that one and replace the sys folder... am I right?
Thanks. I will try to cast some magic with this
(for personal use, of course )
macaraballojr said:
sorry still kinda new to all this ROM cooking...
So this is a newer build of the OS?
I the just2clean kitchen you released I want to keep all those packages I have in there so all i have to do is add the files from this OEM folder to that one and replace the sys folder... am I right?
Click to expand...
Click to collapse
This is not my newest build, this is the Just2Clean that I had already released. If you want to get a newer build, search for EasyPortOven 2.2 and use that to port over the ROM. It will change the ROM, though, as the SYS folder has been optimized. You'll learn more about this in one of my upcoming cooking lessons.
awsome!.... Do you know more or less when you will be comming out with this lesson?
Again Thank you for all ur help and work... You Rock dude!
macaraballojr said:
awsome!.... Do you know more or less when you will be comming out with this lesson?
Again Thank you for all ur help and work... You Rock dude!
Click to expand...
Click to collapse
Well, you have to follow all my lessons first, in order to understand the whole process, so keep studying my lessons as they come and the ones I have already released and you'll be ok.
ivanmmj said:
Well, you have to follow all my lessons first, in order to understand the whole process, so keep studying my lessons as they come and the ones I have already released and you'll be ok.
Click to expand...
Click to collapse
What would we do without u bro but many thanks for the info
hmm well old kitchen still works but when i replace files with that attached ive got problem with running buildos (its building temp but after a while its giving up and show problem with buildos (windows dialog) and then with buildxip...)
old kitchen works. i also tried to use a fresh upacked version. its just not working for me...
ive reinstalled all frameworks, c+ and its not helping.. even if i not mod anything its just dont work ;/
(i have unpacked to good folder and old configuration (5.2.19199) still works fine. i'm having badsectors but this cannot be the problem right now..)
i need some help.. or there is some newer version of easybakeoven? (using still beta2...)
slimag said:
hmm well old kitchen still works but when i replace files with that attached ive got problem with running buildos (its building temp but after a while its giving up and show problem with buildos (windows dialog) and then with buildxip...)
old kitchen works. i also tried to use a fresh upacked version. its just not working for me...
ive reinstalled all frameworks, c+ and its not helping.. even if i not mod anything its just dont work ;/
(i have unpacked to good folder and old configuration (5.2.19199) still works fine. i'm having badsectors but this cannot be the problem right now..)
i need some help.. or there is some newer version of easybakeoven? (using still beta2...)
Click to expand...
Click to collapse
One of the packages you chose is probably not compatible with Just2Clean. To make it compatible, read the error and it will tell you. If a duplicate file is found, delete the extra file from the OEM folder or the SYS folder.
when i put the OEM and SYS folder from the Just2Clean in the working folder of the Kitchen, the Kitchen won't even start up.
- reinstall of VC -> no start up.
- mixing of old and new OEM and SYS -> no start up.
- using the old oem and sys -> all works great
Ghostrider
i cant choose any package and i'm using ONLY oem and sys from working folder.7z!
old kitchen works great but i cant use these files. same as GhostRider.
need help..
Ghostrider said:
when i put the OEM and SYS folder from the Just2Clean in the working folder of the Kitchen, the Kitchen won't even start up.
- reinstall of VC -> no start up.
- mixing of old and new OEM and SYS -> no start up.
- using the old oem and sys -> all works great
Ghostrider
Click to expand...
Click to collapse
What do you mean by not start up. There are MANY files and batch files and programs that work together as a kitchen. You'll have to be more specific. Perhaps a screenshot of what happens.
slimag said:
i cant choose any package and i'm using ONLY oem and sys from working folder.7z!
old kitchen works great but i cant use these files. same as GhostRider.
need help..
Click to expand...
Click to collapse
You can't choose packages because the packages are all stored in the OEM folder. I forgot to mention that. Don't delete the OEM folder, just the folders in the OEM folder have the same name as the files in the other new OEM folder...
when I put the new files in the OEM and SYS Folder it say's BuildOS.exe don't work anymore, The Program has an Problem, and must be Closed.
Then the same with Buildxip.exe don't work anymore.
Ghostrider
That means that there's a conflicting name on an RGU, DSM, or inside an option.xml. If you do not go through BuildOS, Buildxip will crash because it will not have something to build in the first place, as it's BuildOS's job to get the files where they need to be.
i'm sorry but you are treating us (me and Ghostrider) like an idiots.. i'm quite sure that problem is with the package.
you write clearly "delete oem and sys and replace them" when i do this - same thing as on Ghostriders screenshots happens.
slimag said:
i'm sorry but you are treating us (me and Ghostrider) like an idiots.. i'm quite sure that problem is with the package.
you write clearly "delete oem and sys and replace them" when i do this - same thing as on Ghostriders screenshots happens.
Click to expand...
Click to collapse
I'm sorry if I insulted you, but I don't see how I treated you like idiots.
All I've done is ask you questions to get a better idea of what's going on. It works on my end, but it doesn't on your end. I can't magically know what's going on without asking questions. I'm sorry if you felt insulted by my questions. It was never my intent. I just wanted to ask questions to find out why it wasn't working on your end so I could help fix it. I just rememebered something, too. Just before I packed it up I was messing around with something... look for the OEM packages that have both an UPX version and a non-UPX version. I THINK that one I uploaded may have one. If it does, one of the packages may have duplicate RGU's and DSM's. If it does, keep the one that starts with A and delete the pair that starts with Z. Also you can delete the UPX version of that package altogether. Tell me if that works.
ivanmmj said:
I'm sorry if I insulted you, but I don't see how I treated you like idiots.
All I've done is ask you questions to get a better idea of what's going on. It works on my end, but it doesn't on your end. I can't magically know what's going on without asking questions. I'm sorry if you felt insulted by my questions. It was never my intent. I just wanted to ask questions to find out why it wasn't working on your end so I could help fix it. I just rememebered something, too. Just before I packed it up I was messing around with something... look for the OEM packages that have both an UPX version and a non-UPX version. I THINK that one I uploaded may have one. If it does, one of the packages may have duplicate RGU's and DSM's. If it does, keep the one that starts with A and delete the pair that starts with Z. Also you can delete the UPX version of that package altogether. Tell me if that works.
Click to expand...
Click to collapse
I don't felt me insulted
I'm testing this now.
Ghostrider
Edit:
I have Just2Clean and MMS 3.5.1.24.R2 as UPX and non UPX deleting the UPX version did't do it. I deleted both the UPX and non UPX version in the Kitchen files for Just2Clean, and now it is working.
I don't have the Just2Clean Customization
Ghostrider
Great to hear!
There should be a Just2Clean customization there also. It's labeled "Customization - Just2Clean."
I think what he meant is that Just2Clean customization packages don't work.
I did as you suggested by deleting the .rgu and .dsm starting with Z, but that still didn't work.
The option XML file needed to be edited because it pointed to those Z files not the A files.
Not sure if just deleting the .dsm and .rgu starting with A would've worked because I didn't try that.
After deleting the UPXed packages everything works for me now.
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
OK, so burn me if you'd like but for the past year or so everyone has been porting the Kaiser SYS and XIP to their devices... but with the recent release of the Diamond, Xperia and TouchPro builds it seems like us Kaiser users want to Port too!!!! So here is my problem
I am having issues right now for some reason as I am \porting the SYS from the Touch DIamond ROm. OS,OSFiles, Shell, .VM, changing the .VM with G'Reloc but for some reason the build # is not changing....WHY I HAVE NO IDEA
In a nutshell I am taking the Touch ROM SYS and replacing only the OS, OSFIles, SHell, .VM folders. THen I am running G'Reloc and entering the proper values. When I cook the rom for some reason it is not changing the build any idea.
I also have used BuildOS+packageTools4.b3 in order to do a XIP port??? I am clueless. I used to do this no problem but for some reason it is not working now???
bayfoco said:
do drop by to www.ebayfoco.com look through the articles there. With information on anything from getting the you like products,
Click to expand...
Click to collapse
enough of this bot already, he was in the development and hacking section as well
mbarvian said:
enough of this bot already, he was in the development and hacking section as well
Click to expand...
Click to collapse
Not anymore. Banned for spam.
P1Tater said:
Not anymore. Banned for spam.
Click to expand...
Click to collapse
thanks, I guess you need a reason to ban
ryncppr said:
In a nutshell I am taking the Touch ROM SYS and replacing only the OS, OSFIles, SHell, .VM folders. THen I am running G'Reloc and entering the proper values. When I cook the rom for some reason it is not changing the build any idea.
Click to expand...
Click to collapse
why are you only bringing over those parts of SYS? take it all.
oh, and replace *DPI_192* from new source with *DPI_96* from kaiser original.
I did that but then the phone wouldn't work???? I dont know whats wrong, I have port other builds no problem but for some reason the new Xperia ROM and TOuch Pro are killing me....
I'll try once more before I whip my computer across the room
ryncppr said:
I did that but then the phone wouldn't work???? I dont know whats wrong, I have port other builds no problem but for some reason the new Xperia ROM and TOuch Pro are killing me....
I'll try once more before I whip my computer across the room
Click to expand...
Click to collapse
if you do what i said above, then g'reloc with original kaiser values, it should boot.
dont use .vm and .rom from kaiser original, use the new ones from new source but g'reloc will change values.
use original kaiser xip until you get sys working then do your xip.
also if you are using original kaiser xip then wincenls_wwe is in xip and doesnt have to be in imgfs. if you are using a cooked xip it may be missing and would be reason for no boot.
oh and on my device htc switched slot values around at a certain ver, i dont know if this is the case on kaiser. i have to match my new xip with new slot values for g'reloc.
in other words if youre using a kaiser wm61 xip from ROM version 3.00 then feed g'reloc the slot values you found in kaiser ROM version 3.00.
i am speaking from experience with your issue, i ported tons of builds then tried new diamond/xperia/etc and suddenly those didnt work with the method i was using previously
WEll all seems to be working now since I ported the whole SYS over... the device is booting fine and the phone is working too!!!
The only problem I have with the port is when the screen boots and gets to the green WM6.1 screen the start icon is in the middle of the screen and the top is blue???
Otherwise it all works fine after the green screen clears the icons are all where they are supposed to be. I didn't mess with this OEM folder where the welcomehead.96.bmp is so thats now confusing?
dcd1182 said:
if you do what i said above, then g'reloc with original kaiser values, it should boot.
dont use .vm and .rom from kaiser original, use the new ones from new source but g'reloc will change values.
use original kaiser xip until you get sys working then do your xip.
also if you are using original kaiser xip then wincenls_wwe is in xip and doesnt have to be in imgfs. if you are using a cooked xip it may be missing and would be reason for no boot.
oh and on my device htc switched slot values around at a certain ver, i dont know if this is the case on kaiser. i have to match my new xip with new slot values for g'reloc.
in other words if youre using a kaiser wm61 xip from ROM version 3.00 then feed g'reloc the slot values you found in kaiser ROM version 3.00.
i am speaking from experience with your issue, i ported tons of builds then tried new diamond/xperia/etc and suddenly those didnt work with the method i was using previously
Click to expand...
Click to collapse
I've ported every new XIP build (Diamond, Raphael, and Xperia) to the Kaiser with "0" problems. All the way up to the newest 20270. Only replacing .VM in SYS.
ryncppr said:
WEll all seems to be working now since I ported the whole SYS over... the device is booting fine and the phone is working too!!!
The only problem I have with the port is when the screen boots and gets to the green WM6.1 screen the start icon is in the middle of the screen and the top is blue???
Otherwise it all works fine after the green screen clears the icons are all where they are supposed to be. I didn't mess with this OEM folder where the welcomehead.96.bmp is so thats now confusing?
Click to expand...
Click to collapse
welcomehead.96 is in sys.
lennysh said:
I've ported every new XIP build (Diamond, Raphael, and Xperia) to the Kaiser with "0" problems. All the way up to the newest 20270. Only replacing .VM in SYS.
Click to expand...
Click to collapse
SO you only ported the .VM? That isn't really a SYS port then is it?
ryncppr said:
SO you only ported the .VM? That isn't really a SYS port then is it?
Click to expand...
Click to collapse
Lol...
I think you took my statement backwards... Ported the entire SYS, all except the .VM. I have four devices all running Build 20270.
Let me rephrase so it's not twisted, they are all four running CE OS 5.2.20270 (Build 20270.1.3.1)
QUESTION since you all are having no issues here, every time I try and dump a diamond rom using the Diamond kitchen RecMode.exe stops working while its dumping the rom so I can't dump it Any hints or do I need to set attributes or anything like that? I am using Windows Vista maybe thats the issue here.
Also your just taking the .VM folder from the kaiser and putting it in the diamond and thats it it works fine? or put it in run G'rec?
I am using the KaiserKitchen to dump my rom. THough I had to rebuild my XIP and separate OEM and SYS for some reason...
I am dying for someone to update the Kitchen for the Kaiser. I am not familar with writting .bat files or I would try.
There is alot of newer programs that need to be implemented into the Kitchen
BuildOS+PackageTool is now 4.b3
HTCTool is newer
PackageTools is newer
I sent a PM to several master chefs but have not heard anything back....
The way that I ported the SYS is as follows....
1st, I dumped both ROMS I want to use. I name the folders accordingly on my C:/ Drive.... KaiserKitchen_BUILD and KaiserKitchen_TOUCHPRO (example)
After dumping both ROMS I make a folder on my desktop and name it NEWSYS. I copy all the files to my NEWSYS folder from the Dumped ROM Folders that I want. PRetty much everything except the .92 files (like stated earlier) after making my NEWSYS the way I want it, I cut my SYS from my KaiserKitchen_BUILD rom to my desktop and replace it with NEWSYS (remember to rename to SYS after copying)
Then I put G'Reloc in the Kitchen folder (same folder as the OEM,XIP,SYS,TOOLS,PACKAGE---main folder) and run it. Since I change the .VM I have to place my numbers back into and press "do it".
The SYS should be fine now.
Thanks buddy, Maybe dutty and his new crew did something to lock the rom down as his was the one i was trying to dump. I find what the other guy said about just changing out the .VM folder if thats the case porting roms couldn't be an easier!
I know it seems simple after I flashed my device like 20 times in the last two days.... now I want to figure out another issue about the blue bar with the start icon in the middle on the top of the green WM6.1 screen...
austinsnyc said:
QUESTION since you all are having no issues here, every time I try and dump a diamond rom using the Diamond kitchen RecMode.exe stops working while its dumping the rom so I can't dump it Any hints or do I need to set attributes or anything like that? I am using Windows Vista maybe thats the issue here.
Also your just taking the .VM folder from the kaiser and putting it in the diamond and thats it it works fine? or put it in run G'rec?
Click to expand...
Click to collapse
That depends on what rom your dumping... If it's a stock rom, you should not have this issue...
ryncppr said:
I know it seems simple after I flashed my device like 20 times in the last two days.... now I want to figure out another issue about the blue bar with the start icon in the middle on the top of the green WM6.1 screen...
Click to expand...
Click to collapse
Same happened to me. I've ported SYS from Diamond, replaced all VGA *.192.* package folders with kaiser's QVGA*.96.*, build rom and flash. The result: it boots everything fine except it doesn't execute any .provxml so no shortcuts no activesync no execute .cabs.
Now the same ROM + OEM and switch back to older SYS: everything OK.
Tried to change .vm values and replacing shell.dll+shellres.dll: the same result. Any idea?
g77 said:
Same happened to me. I've ported SYS from Diamond, replaced all VGA *.192.* package folders with kaiser's QVGA*.96.*, build rom and flash. The result: it boots everything fine except it doesn't execute any .provxml so no shortcuts no activesync no execute .cabs.
Now the same ROM + OEM and switch back to older SYS: everything OK.
Tried to change .vm values and replacing shell.dll+shellres.dll: the same result. Any idea?
Click to expand...
Click to collapse
RUU_Diamond_HTC_Europe_1.35.401.3_Radio_Signed_Diamond_52.26.25.09_0.93.25.26_Ship
+
RUU_Kaiser_HTC_WWE_3.28.405.0_radio_sign_25.83.40.02_1.65.16.25_Ship
Copy .VM from WWE to Diamond
Use G'Reloc
Cook it up!
Boots just fine, no problems whit provxml, shortcuts, activesync, execute or.cabs here.
I've started trying my hand at cooking some of my own ROMs over the past couple of days and have gotten confused on some stuff. I've been following the both the Wiki's and the threads on cooking but none of them seem to point it out so here goes.
1) I'm trying to use a base ROM such as this one or this one and have been successful in both dumping them and cooking them using Alex's latest revision of KaiserKitchen and his apps. When I am including the os.nbh file during the cooking process, should it be the one that comes up in the main KaiserKitchen folder or the one that is located in the BASEROM folder? Is either of those files just the OS part of the ROM without all the applications and such?
2) After cooking and successfully flashing either of the two before mentioned ROMs I will always get the auto-installer which occurs on a default ROM. The problem is is that none of the defined packages that I've chosen in the cooking process will be installed when the ROM is flashed. Why is this? Is there something that I should be doing that I'm not doing now that will allow this?
I would greatly appreciate any help in this as I want to become an avid chef but want to learn the ropes first. I've been toying around with it and wanted to get a decent collection of base ROMs and understand them before I start customizing them and such. Again, any help would be thoroughly appreciative and love what you guys are doing here.
HEdwards2008 said:
I've started trying my hand at cooking some of my own ROMs over the past couple of days and have gotten confused on some stuff. I've been following the both the Wiki's and the threads on cooking but none of them seem to point it out so here goes.
1) I'm trying to use a base ROM such as this one or this one and have been successful in both dumping them and cooking them using Alex's latest revision of KaiserKitchen and his apps. When I am including the os.nbh file during the cooking process, should it be the one that comes up in the main KaiserKitchen folder or the one that is located in the BASEROM folder? Is either of those files just the OS part of the ROM without all the applications and such?
2) After cooking and successfully flashing either of the two before mentioned ROMs I will always get the auto-installer which occurs on a default ROM. The problem is is that none of the defined packages that I've chosen in the cooking process will be installed when the ROM is flashed. Why is this? Is there something that I should be doing that I'm not doing now that will allow this?
I would greatly appreciate any help in this as I want to become an avid chef but want to learn the ropes first. I've been toying around with it and wanted to get a decent collection of base ROMs and understand them before I start customizing them and such. Again, any help would be thoroughly appreciative and love what you guys are doing here.
Click to expand...
Click to collapse
os.nb should be in base rom with RUU_signed.nbh(once youve extracted) The File that is generated during ervius package tools is OS-new.nb-this is your new os. Kaiser Wiki has all info.
yardie.spike said:
os.nb should be in base rom with RUU_signed.nbh(once youve extracted) The File that is generated during ervius package tools is OS-new.nb-this is your new os. Kaiser Wiki has all info.
Click to expand...
Click to collapse
I've been searching the Wiki like crazy and I guess I am just confused on it. So OS-new.nb is the OS ROM with all of the packages, Which one would be just the OS itself? The os.nb file in the BASEROM folder?
HEdwards2008 said:
I've been searching the Wiki like crazy and I guess I am just confused on it. So OS-new.nb is the OS ROM with all of the packages, Which one would be just the OS itself? The os.nb file in the BASEROM folder?
Click to expand...
Click to collapse
Yeah, but dont worry about os.nb in base rom folder, unless you dont want to mod the rom and just add your fave radio/splash/spl. If thats all you want to do then recomplile using htcrt.exe in tools folder. OS .nb is what is extracted into OEM SYS and ROM folders in the kaiserkitchen. To add Packages put a folder called Packages in your kaiserkitchen and put your OEM Packages in it, then run KAISERKITCHEN.CMD chose option c then b. When Ervius build os +package tool opens,click the right tab and add rom(Add your kaiserkitchen folder,but make sure its on your desktop). You will then get a list of packages in the premade folder, just tick the ones you want to add to your rom. Once happy click build rom. Once done exit and KAISERKITCHEN.CMD should crack on by itself....then bring up a couple more apps(Rom Tool and Pagepool)just do what they say . every time you exit these apps KAISERKITCHEN.CMD will take you to the next step.
yardie.spike said:
Yeah, but dont worry about os.nb in base rom folder, unless you dont want to mod the rom and just add your fave radio/splash/spl. If thats all you want to do then recomplile using htcrt.exe in tools folder.
Click to expand...
Click to collapse
speaking of the htc rom tool, does anyone have a mirror for the latest version (1.1.1). it's not working on his site, and I 'm really interested in the command line support
mbarvian said:
speaking of the htc rom tool, does anyone have a mirror for the latest version (1.1.1). it's not working on his site, and I 'm really interested in the command line support
Click to expand...
Click to collapse
Theres a new ROM tool????Anyone tried??
NEW IS GOOD!!!
Thank you so much for the clarification. I've also been trying to find a decent kitchen setup and the one made by Alex is the best one I've encountered so far but haven't really steered too far from his build. I have to agree that a new version of the HTC Rom Tool would be cool.
HEdwards2008 said:
Thank you so much for the clarification. I've also been trying to find a decent kitchen setup and the one made by Alex is the best one I've encountered so far but haven't really steered too far from his build.
Click to expand...
Click to collapse
I just put up a Kaiser 20270 kitchen from PPCKitchen.org and AstainHellbring. Try it, let me know what you think. Feedback thread is here.
yardie.spike said:
Yeah, but dont worry about os.nb in base rom folder, unless you dont want to mod the rom and just add your fave radio/splash/spl. If thats all you want to do then recomplile using htcrt.exe in tools folder. OS .nb is what is extracted into OEM SYS and ROM folders in the kaiserkitchen. To add Packages put a folder called Packages in your kaiserkitchen and put your OEM Packages in it, then run KAISERKITCHEN.CMD chose option c then b. When Ervius build os +package tool opens,click the right tab and add rom(Add your kaiserkitchen folder,but make sure its on your desktop). You will then get a list of packages in the premade folder, just tick the ones you want to add to your rom. Once happy click build rom. Once done exit and KAISERKITCHEN.CMD should crack on by itself....then bring up a couple more apps(Rom Tool and Pagepool)just do what they say . every time you exit these apps KAISERKITCHEN.CMD will take you to the next step.
Click to expand...
Click to collapse
So if I'm understanding this correctly....in order to achieve a completely clean ROM without all the extra fixings I would simply need to use the os.nb file and not the os-new.nb file when cooking correct?
No, the only way to get a completely clean base is to use one someone made, or to manually remove extra oems from an uncorrupted rom (which usually means stock). os.nb is the donor imgfs, os-new.nb is the donor imgfs with your added pkgs.
The PPCkitchen.org kaiser kitchen is clean, and is way simpler to use. If you're trying to get to a clean base, do yourself a favor and just use it.
so... does this mean that if I use for say OEM HTC ROM, and put the os.nb in the base folder, when I build it using the tool, whatever packages I selected are simply added to whatever is on the OS.NB? I thought it would use the baserom as base and whatever apps installed on it are ignored. I guess I totally got it wrong then... So how do you strip out all the programs that have been installed in the baserom? Does this mean you have to dump the image?
maximumbs said:
so... does this mean that if I use for say OEM HTC ROM, and put the os.nb in the base folder, when I build it using the tool, whatever packages I selected are simply added to whatever is on the OS.NB? I thought it would use the baserom as base and whatever apps installed on it are ignored. I guess I totally got it wrong then... So how do you strip out all the programs that have been installed in the baserom? Does this mean you have to dump the image?
Click to expand...
Click to collapse
I do know that in order to get the base OEM packages out of the main build you have to go through and remove and edit certain files to get it done right, which there is information in the Wiki about but haven't really had time to focus on it much. As for the PPCKitchen.org version of the Kitchen, I'm going to try it when I get home tonight because I'm at work currently. Gguruusa, you have to understand that some of us are new to the cooking community and want to be able to get our feet wet slowly and make sure we do stuff right instead of damaging our device. I've only got one Tilt and I don't want to completely destroy it. I would love to cook but need to be able to start off with a simple clean base rom with no extra ingredients and then go from there.
maximumbs said:
so... does this mean that if I use for say OEM HTC ROM, and put the os.nb in the base folder, when I build it using the tool, whatever packages I selected are simply added to whatever is on the OS.NB? I thought it would use the baserom as base and whatever apps installed on it are ignored. I guess I totally got it wrong then... So how do you strip out all the programs that have been installed in the baserom? Does this mean you have to dump the image?
Click to expand...
Click to collapse
No dont put os.nb in the base rom put the RUU_unsigned and extract using KAISERKITCHEN.cmd.....read my previous posts.
gguruusa said:
No, the only way to get a completely clean base is to use one someone made, or to manually remove extra oems from an uncorrupted rom (which usually means stock). os.nb is the donor imgfs, os-new.nb is the donor imgfs with your added pkgs.
The PPCkitchen.org kaiser kitchen is clean, and is way simpler to use. If you're trying to get to a clean base, do yourself a favor and just use it.
Click to expand...
Click to collapse
This looks very promising, downloading it now. Thanks for this! Hope they update it 20273 soon
HEdwards2008 said:
As for the PPCKitchen.org version of the Kitchen, I'm going to try it when I get home tonight because I'm at work currently. Gguruusa, you have to understand that some of us are new to the cooking community and want to be able to get our feet wet slowly and make sure we do stuff right instead of damaging our device. I've only got one Tilt and I don't want to completely destroy it. I would love to cook but need to be able to start off with a simple clean base rom with no extra ingredients and then go from there.
Click to expand...
Click to collapse
That's why ppckitchen.org was born. With ppckitchen.org, it's a point and click thing to build a rom. The mysterious part (making a kitchen base) is done for you. All you have to focus on is what packages you want to add.
You still have to unlock your device and install radios outside the kitchen, which is where people generaly brick their devices.
gguruusa said:
That's why ppckitchen.org was born. With ppckitchen.org, it's a point and click thing to build a rom. The mysterious part (making a kitchen base) is done for you. All you have to focus on is what packages you want to add.
You still have to unlock your device and install radios outside the kitchen, which is where people generaly brick their devices.
Click to expand...
Click to collapse
I shouldn't have any problems then seeing as to how I know that you need to have HardSPL installed and also to be sure to flash the radio AFTER the ROM in order to prevent bricking.
But that takes the whole fun out of cooking a rom when the base is already made for you...!!!
I will have to say my most challenging part is trying to get the base rom the way I like it in order to add whatever I want.
For example....
In my current kitchen I have deleted all of the OEMAPPS folders except the dsm file. I have then rebuilt all of my programs like the way a Diamond and Raphael ROM is....
In essence, If I was to just build my ROM without any packages it would be a clean rom without any software like camera, mms, phoneskins ect....
Its taken awhile thats why I have not published my newest rom yet...
ryncppr said:
But that takes the whole fun out of cooking a rom when the base is already made for you...!!!
I will have to say my most challenging part is trying to get the base rom the way I like it in order to add whatever I want.
For example....
In my current kitchen I have deleted all of the OEMAPPS folders except the dsm file. I have then rebuilt all of my programs like the way a Diamond and Raphael ROM is....
In essence, If I was to just build my ROM without any packages it would be a clean rom without any software like camera, mms, phoneskins ect....
Its taken awhile thats why I have not published my newest rom yet...
Click to expand...
Click to collapse
I totally agree my favourite build was one that went wrong and nearly bricked my phone....sounds sick, but it was going back over what i had done and fixing that was the fun part. That ROM turned out to be possibly my most stable (Yardie 2.1.240) Ha ha i love cooking!!!
ryncppr said:
But that takes the whole fun out of cooking a rom when the base is already made for you...!!!
Click to expand...
Click to collapse
Bah. The fun of cooking is getting a ROM to look and feel like you want. Making a kitchen is entertaining when you haven't done it before, but it's really 99% repetition and 1% art.
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!