Related
Obligatory Warning Label:
Use this at your own RISK. I cannot be held liable for any damage caused to your device by your own mistakes or by my mistakes in the instructions.
How to port a XIP:
Extract xip.bin from the build you want to port from
Download Bepe's XIPPort
Extract XIPPort to any folder
The folder should contain XIPPort.exe, pkgcommon.dll, and xip.bin you want to port.
Run XIPProt.exe
Press "Dump xip.bin" - This will create an OUT folder
Press "Make Pkgs"
Open the OUT folder and you will find two folders: Files and Modules
Copy the contents of MSXIPKernel and MSXIPKernelLTK with each folder (Files and Modules) and paste them to /ROM/XIP folder and replace. (Note: Don't worry about copying the .txt files, they are not needed.)
Source
How to port a SYS folder
Open your old SYS folder and copy the .VM and WinCENLS_WWE folders into your new SYS folder
Go to your old SYS\Shell and copy shell32.exe and shellres.dll into your new SYS\Shell
Source
Q&A
Q: What is the XIP?
A: It's the kernel of the ROM.
Q: What is the SYS folder?
A: It's where all the new apps included in each Windows Mobile release are stored.
Q: I did all this and I bricked my phone, help!!!
A: First, rest assured. Your phone is not bricked. See THIS thread on how to unbrick your phone. Secondly, refer to Q&A #4.
Q: This is too complicated... but I still want to port my own ROM. What should I do?
A: Easy. Use my EasyPortOven and the process will be automated.
Q: Where do I get the latest SYS folders? XIP's?
A: I don't know... Your guess is as good as mine. I just download Kaiser ROM's that have them since they tend to have the latest and greatest first. Do NOT PM me asking me where to find them.
well done ,thanks.
ivan i love you...lol just kidding silly goose but thanks a million
Ivan:
Can XIP or SYS folders be ported over different language ROMS?
Say... I have my spanish HTC WM6 ROM, can I port an english WM6.1 over it to obtain an unofficial spanish WM6.1?
I assume the XIP folder could be ported but porting the SYS folder would end with a spanish ROM and multiple applications in WWE (without even starting to think about localization codes troubles)
Thanks.
le_hades said:
Ivan:
Can XIP or SYS folders be ported over different language ROMS?
Say... I have my spanish HTC WM6 ROM, can I port an english WM6.1 over it to obtain an unofficial spanish WM6.1?
I assume the XIP folder could be ported but porting the SYS folder would end with a spanish ROM and multiple applications in WWE (without even starting to think about localization codes troubles)
Thanks.
Click to expand...
Click to collapse
You'd have to go through every file in the OEM folder and find every misdirected link (because of the different language) as well as replace every MUI. So in short, no it's not possible unless you have a LOT of time and want to work really hard. What I would do is just use any of the readily available Spanish Herald ROMs to obtain your OEM files.
mm this is a "fast" and dirty way:
If you use in.ex a 19199 build (0409 wwe)
you need to extract all mui files from 04xx (your langauge from another build, if you use wm6.1 you need to use mui from another wm6.1 build)
rename them from 04xx to 0409, replace all in you 19199 build with the new renamed ones
this can be done both in OEM and SYS
The thing is that i'd like to make a herald spanish 6.1 ROM but I can't find none to port on kaiser forums etc, so i was thinkong about alternatives
ivanmmj said:
Obligatory Warning Label:
Use this at your own RISK. I cannot be held liable for any damage caused to your device by your own mistakes or by my mistakes in the instructions.
How to port a XIP:
Extract xip.bin from the build you want to port from
Download Bepe's XIPPort
Extract XIPPort to any folder
The folder should contain XIPPort.exe, pkgcommon.dll, and xip.bin you want to port.
Run XIPProt.exe
Press "Dump xip.bin" - This will create an OUT folder
Press "Make Pkgs"
Open the OUT folder and you will find two folders: Files and Modules
Copy the contents of MSXIPKernel and MSXIPKernelLTK with each folder (Files and Modules) and paste them to /ROM/XIP folder and replace. (Note: Don't worry about copying the .txt files, they are not needed.)
Source
How to port a SYS folder
Open your old SYS folder and copy the .VM and WinCENLS_WWE folders into your new SYS folder
Go to your old SYS\Shell and copy shell32.exe and shellres.dll into your new SYS\Shell
Source
Q&A
Q: What is the XIP?
A: It's the kernel of the ROM.
Q: What is the SYS folder?
A: It's where all the new apps included in each Windows Mobile release are stored.
Q: I did all this and I bricked my phone, help!!!
A: First, rest assured. Your phone is not bricked. See THIS thread on how to unbrick your phone. Secondly, refer to Q&A #4.
Q: This is too complicated... but I still want to port my own ROM. What should I do?
A: Easy. Use my EasyPortOven and the process will be automated.
Q: Where do I get the latest SYS folders? XIP's?
A: I don't know... Your guess is as good as mine. I just download Kaiser ROM's that have them since they tend to have the latest and greatest first. Do NOT PM me asking me where to find them.
Click to expand...
Click to collapse
Great job bro,
ivan you rock!!
I learn so much from reading your threads.
I think im almost ready to cook a rom.
I was wondering if you could be my mentor??
It works and works very well, however, I have ported from Hermes XIP CE OS 19949 & build 19949.1.1.1
to Atom from orginal XIP and I have CE OS 5.2.1921 & build 19949.1.1.1 (WM6.1) how to gain CE of 19949? thank you very much for sharing.
homer285 said:
It works and works very well, however, I have ported from Hermes XIP CE OS 19949 & build 19949.1.1.1
to Atom from orginal XIP and I have CE OS 1921 & build 19949.1.1.1 (WM6.1) how to gain CE of 19949? thank you very much for sharing.
Click to expand...
Click to collapse
You ported the XIP AND the SYS folder?
Thanks for your reply, yes I did.
homer285 said:
Thanks for your reply, yes I did.
Click to expand...
Click to collapse
Are you using the imgfs.bin/os.nb from the Atom? The only time I've seen that is when you're using the imgfs.bin/os.nb from another device. It "lines up" enough for the ROM to work but somethings like the version numbers don't "line up." I'd need more information to find out what happened. Also, did you change the DPI of the ROM for any reason? or the DPI files?
ivanmmj said:
Are you using the imgfs.bin/os.nb from the Atom? The only time I've seen that is when you're using the imgfs.bin/os.nb from another device. It "lines up" enough for the ROM to work but somethings like the version numbers don't "line up." I'd need more information to find out what happened. Also, did you change the DPI of the ROM for any reason? or the DPI files?
Click to expand...
Click to collapse
yes Im using the Diskimage_Ver.nb0 from Atom in Rom folder, tried by hand and EasyPortOven same result, only build is porting not CE OS info. Perhaps I need a new XIP to try, anyway thanks for this great tool it really makes porting easy, seriously.
Edit: So the trick for me was the Atom needed porting directly, all modules must have address changed and then ported to diskimage_Ver via XIPPORT, drop into Kitchen/ROM folder along with everything mentioned here .
can anyone confirm if this works for the kaiser, and if it doesn't, what to use for the kaiser?
thanks in advance
I've heard that Keeping your original Device MetaData hive files isn't that important as the Hive Files get created.
But just to be on the Sure side.
When you put the Hive files from MetaData folder into the New Build from the Ported Sys.
Won't that make hive files with unneeded Reg entries?
instead of sticking with your original device Hive Files?
€dit: Wrong thread, sorry!
Drivers?
What about the drivers and files specific to the device?
Is it included in the .VM folder? Is it not necessary to copy the .ROM folder too?
So, in essence, I have to just copy the folders you have specified to the new SYS and XIP folders and use BuildOS. To cook a light and clean ROM, only these two folders are enough, right?
BTW, what is the OEM folder for? In the kitchens, I have used, they contain a few folders like OEMAPPS, OEMDRIVERS, etc, which in some kitchens are placed in the SYS folder instead.
I don't know where to place those folders. Is the location of those folders irrelevant? I am kinda noob to cooking. I've played with it a lot of times with mixed results. I am building it for Tornado btw.
rajathvsm said:
What about the drivers and files specific to the device?
Is it included in the .VM folder? Is it not necessary to copy the .ROM folder too?
So, in essence, I have to just copy the folders you have specified to the new SYS and XIP folders and use BuildOS. To cook a light and clean ROM, only these two folders are enough, right?
BTW, what is the OEM folder for? In the kitchens, I have used, they contain a few folders like OEMAPPS, OEMDRIVERS, etc, which in some kitchens are placed in the SYS folder instead.
I don't know where to place those folders. Is the location of those folders irrelevant? I am kinda noob to cooking. I've played with it a lot of times with mixed results. I am building it for Tornado btw.
Click to expand...
Click to collapse
Things have changed a lot since I wrote this... but:
The drivers are in the OEM folder (as well as most of the device specific stuff.)
You need the OEM, SYS and XIP in order to make ANY ROM.
You can move your OEM into your SYS but it makes it harder to port newer builds to your ROM later on.
You only need the .VM folder, not the .ROM folder. The kitchen will autoadjust itself.
Yep its been a long time... but is useful on old kitchens
I gues i have an hybrid
cause the process i use is like EXT packages + OEM packages + SYS + XIP
Something about a platform rebuilder + oldschool buildOS hahaha
Maybe you can help me Ivan using your process to port the xip i DID it! it works the sys too but....
I port the SYS from xbeta.cn hermes WWE, changing the .VM and shellres you know... and the xip usin xipport everything goes fine I port the Xip from Kaiser... but
But now everything i install says certificates untrested... i instal sdkcerts and nothing happends
do you think i port the sys or xip wrong?
thanks in advance I dont have an Herald, I had an hermes... but i think the process is the same...
wm6.5 build 21812
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.
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.
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.
Sorry for my English ...
I'm trying to learn how to build a kitchen and I followed the BEPE's guides perfectly but I have a problem:
When I use "NBHextract.exe" on "RUU_signed.nbh" the file that I get is "00_OS.nb" and not "OS.nb" as in BEPE's guide, same for the file "00_OS.nb.playload" has the same characteristics, and I know not explain why.
Also, I can not use in any way the "packagebuilder" tool to rebuild the "xip" folder because after having dumped "00_OS.nb.playload" the xip folder that I know, does not contain within it the file "*. dsm " essential to the operation of the tool.
can someone help me? (sorry but I translate before answering for now)
Thank you!
PS: other problem..
When I use "Dump_800" on "00_OS.nb" the files that I get are "00_OS.nb.playload", the IMGFS folder and the IMGFS.BIN.
This IMGFS.BIN was to be automatically erased at the end of the process of dumping, but strangely still active and has a size of about 63 MB, and in the prompt window, at the end of the process of dumping, i read this:
C:\xxxxxxxxxx\IMGFS.BIN
Access denied.
Where I wrong?
Thanx 4 all..
Any idea?...
Anything?...
That relief, then I am not the only one who does not understand anything!
ciko84xp said:
Any idea?...
Anything?...
That relief, then I am not the only one who does not understand anything!
Click to expand...
Click to collapse
I can't help you either ... try to PM one of the Chef you knew from the forum.
ciko84xp said:
Sorry for my English ...
I'm trying to learn how to build a kitchen and I followed the BEPE's guides perfectly but I have a problem:
When I use "NBHextract.exe" on "RUU_signed.nbh" the file that I get is "00_OS.nb" and not "OS.nb" as in BEPE's guide, same for the file "00_OS.nb.playload" has the same characteristics, and I know not explain why.
Also, I can not use in any way the "packagebuilder" tool to rebuild the "xip" folder because after having dumped "00_OS.nb.playload" the xip folder that I know, does not contain within it the file "*. dsm " essential to the operation of the tool.
can someone help me? (sorry but I translate before answering for now)
Thank you!
PS: other problem..
When I use "Dump_800" on "00_OS.nb" the files that I get are "00_OS.nb.playload", the IMGFS folder and the IMGFS.BIN.
This IMGFS.BIN was to be automatically erased at the end of the process of dumping, but strangely still active and has a size of about 63 MB, and in the prompt window, at the end of the process of dumping, i read this:
C:\xxxxxxxxxx\IMGFS.BIN
Access denied.
Where I wrong?
Thanx 4 all..
Click to expand...
Click to collapse
What rom are you trying to dump? if it is a custom rom....built by the new kitchen, it won't be dumpable. You will have to get a base from a chef or dump a factory rom.
parleyp said:
What rom are you trying to dump? if it is a custom rom....built by the new kitchen, it won't be dumpable. You will have to get a base from a chef or dump a factory rom.
Click to expand...
Click to collapse
I downloaded this "RUU_Kaiser_HTC_WWE_1.56.405.5_radio_sign_22.45.88.07_1.27.12.11_Ship", which should be the Official HTC ROM for TYTN II (my device), but I have the same errors described in the first post using the BEPE's kitchen!
What do you mean by "You will have to get a base from a chef?
I do not believe that any chef would give me his base, should give me the entire folder containing the kitchen built! Or not?
sorry for my english...
I try to dump the various types of ROM, but I always make the same mistakes! I do not know how ... believe me I tried all possible solutions!
But I do not surrender ... sooner or later arrive at a solution! Even at the cost of start over with another kitchen!
How many kitchens are there? tell me if you know there are others beyond that of bepe?
I am having the same issue with Bepes kitchen - I have the official signed rom from Sprint for the Mogul and every time I try to use dump_800.bat on the OS.nb file, it fails and says access is denied...
ciko84xp said:
sorry for my english...
I try to dump the various types of ROM, but I always make the same mistakes! I do not know how ... believe me I tried all possible solutions!
But I do not surrender ... sooner or later arrive at a solution! Even at the cost of start over with another kitchen!
How many kitchens are there? tell me if you know there are others beyond that of bepe?
Click to expand...
Click to collapse
There is KaiserKitchen by _Alex_ or KaiserChef by mbarvian and a few others - They both exist on the Wiki.
If the IMGFS.bin won't delete it's not that bad, just try and delete it afterwards.
If you are getting 00_OS.nb it might not be the orginal nbh you are dumping. I get 03_OS.nb when I dump the 3.34 HTC Kaiser ROM (which I rename to OS.nb before dumping). I also get 00_Unknown.nb, 01_SPL.nb 02_MainSplash.bmp (and .nb). Do you get any other nb files?
What the link for the ROM, and why are you using that one for the base? There are newer builds (like the 3.34).
Ta
Dave
DaveShaw said:
There is KaiserKitchen by _Alex_ or KaiserChef by mbarvian and a few others - They both exist on the Wiki.
If the IMGFS.bin won't delete it's not that bad, just try and delete it afterwards.
If you are getting 00_OS.nb it might not be the orginal nbh you are dumping. I get 03_OS.nb when I dump the 3.34 HTC Kaiser ROM (which I rename to OS.nb before dumping). I also get 00_Unknown.nb, 01_SPL.nb 02_MainSplash.bmp (and .nb). Do you get any other nb files?
What the link for the ROM, and why are you using that one for the base? There are newer builds (like the 3.34).
Ta
Dave
Click to expand...
Click to collapse
Sorry for my english.. i try to write wath i want tell you....
Problem solved... with "KaiserKitchen" by _Alex_ I have solved all problem with one file called "KaiserKitchen.batch"... this little application, extract .nbh file, dump IMGFS.BIN and create a SYS and OEM folders, dump OS.nb.payload and create a XIP folder... ALL IN ONE STEP!!! IT'S FANTASTIC...!
Yesterday I have cooked and flashed my 1st ROM... really ruins... but the feel thrill don't have comparisons!!!
Now i don't understand wath should i do to take the SYS folder by one ROM and build inside another ROM.. ex. i want to take the SYS folder by your ROM and build in my own ROM...! to do this, i need to copy also your XIP folder?
Sorry for the english and for the ignorance... but I'm beginners for now...!
ciko84xp said:
Sorry for my english.. i try to write wath i want tell you....
Problem solved... with "KaiserKitchen" by _Alex_ I have solved all problem with one file called "KaiserKitchen.batch"... this little application, extract .nbh file, dump IMGFS.BIN and create a SYS and OEM folders, dump OS.nb.payload and create a XIP folder... ALL IN ONE STEP!!! IT'S FANTASTIC...!
Yesterday I have cooked and flashed my 1st ROM... really ruins... but the feel thrill don't have comparisons!!!
Now i don't understand wath should i do to take the SYS folder by one ROM and build inside another ROM.. ex. i want to take the SYS folder by your ROM and build in my own ROM...! to do this, i need to copy also your XIP folder?
Sorry for the english and for the ignorance... but I'm beginners for now...!
Click to expand...
Click to collapse
There are a few tutorials on porting the SYS and XIP. The concept in bepe's kitchen videos is the same for the SYS in most kitchens (be aware of resolution and language specific files).
For the XIP, have a read around, there are many threads and tutorials on how to do it. But normally the XIP and SYS versions should match (or be very close).
Dave
DaveShaw said:
There are a few tutorials on porting the SYS and XIP. The concept in bepe's kitchen videos is the same for the SYS in most kitchens (be aware of resolution and language specific files).
For the XIP, have a read around, there are many threads and tutorials on how to do it. But normally the XIP and SYS versions should match (or be very close).
Dave
Click to expand...
Click to collapse
ok Dave.. I follow your advice! then you story if I have made progress ...! thanks!