Related
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.
I think _Alex_ was the last to offer a kitchen and I think it's about time we had a new one. Everyone has their own needs and I know no ROM is perfect so here's my attempt to satisfy everyone.
I don't know if I'm going to have the time to answer everyone's questions and to help resolve all issues so I have to ask the community to please help out when you guys can.
Next, on with the thanks and I know I'm going to leave some people out so I apologize in advance. So thanks to these users for the tools and support we use to customize our phones:
-- kyphur, bepe, jerplea, jscepi, cmonex, alltheway, p1tater...
And to these people for helping me test and support my roms:
-- hang.tuah, dani31, -888-, idj1975, ecltech, kmfm$, rkrasny...
Here's what's included in the link:
OEM-3.29: my cleaned up OEM folder based off of 3.29 Dopod ROM
OEM-Packages: my packages created with help from XDA (see attachment for list)
ROM-20748: ported XIP from jerplea, OS.NB edited to show 20748
SYS-20748: ported SYS from jerplea, has 20212 components
SYS-Extras: entertainment (solitaire, bubble breaker), office, onenote, windowslive
And without further ado here's what you need to do:
1. Extract Kitchen.rar to the root of your drive (i.e. c:\ or d:\)
2. Extract OEM-3.29, ROM-20755, SYS-20755 to where you extracted Kitchen.rar
3. Copy packages you want from OEM-Packages to OEM folder
4. Copy packages you want from SYS-Extras to SYS folder
5. Cook and flash, see attached DK's Instructions doc if you need more help
NOTE: The contents of "OEM\OEMXIPKernel" are REQUIRED for cooking if you want your rom to boot
To get 2DManila working you will want to include from OEM-Packages the following:
-- 2DManila, Album, AudioBooster, AudioManager, CommManager, ConcurrenceMgr, VerionInfo, YouTube, Camera, Dshow, (me thinks that's everything)...You also need GoogleMaps.cab and OperaMobile (not included, search Dev&Hack for current version)
My Supa-Clean ROM always have the following:
-- ConcurrenceMgr, OutlookEnhancement, PictureEnhancement, RingtonePlugin, VersionInfo, StartupAnimationEngine, SymbolPad, DShow and mHub
click me if wanna give me a little somethin'
http://rapidshare.com/files/146363122/DK_s_Kitchen_v1.zip <-- 99MB
http://rapidshare.com/files/146441384/OEMandPackages.zip <-- OEM and Packages Only
http://rapidshare.com/files/146425292/ROM_SYS-20748.zip <-- CE OS 5.2.20748, ROM and SYS only
http://rapidshare.com/files/148174032/ROM_SYS-20755.rar <-- CE OS 5.2.20755, ROM and SYS only
http://www.4shared.com/file/65703329/83b15f7c/SYS_XIP_20755_FIXED.html <-- SYS fixed by KMFM$
TODO:
- Find and Squash bugs
- Get new Jade PhoneCanvas: Sakajati and uDK seem to have this working, but I'm stumped (HELP!!)
- Jade_VolumeControl: didn't include this because when installed you can't change the in call volume with the scroll wheel
- I got the Jade Camera working, but it doesn't seem to have autofocus so I didn't include it. Anyone have a the files for the camera floating around?
OEM Version Numbers:
RandomAccess - 4_0_18174127_0
OutlookEnhancement - 1_0_33540_4
Album - 2_5_18191330_0
BootLauncher - 1_0_34322_2
AdvancedPowerManagement - 1_5_18162126_1
RingtonePlugin - 1_00_080416_1
CommManager - 2_7_1_8
2DManila - 1_00_18183719_00
TaskManager - 2_1_34563_3
AudioBooster - 2_1_18181827_1
LargeTitleBar - 4_40_0_0
PictureEnhancement - 1_50_18141822_c2
YouTube - 1_5_1818_3522
AdobePDF - 2_5_103401_01R1
ArcsoftMMS - 5_0_31_45
HTCGesture - 1_0_30346_1
mHub - 6_54_080529_E0
SymbolPad - 1_0_29364_0
AudioManager - 2_0_18191228_0
VersionInfo - 1_0_18182525_0
ConcurrenceMgr - 1_1_18143521_0000
StartupAnimationEngine - 1_0_626715_0
DShow - 2_00_080730_0
CAMERA - 4_08_30665_00
EnlargeStartMenu - 1_2_34828_4
reserved for me again!!
Great. Really appreciate your gift.
Thank you very much indeed.
yay! Beautiful gift to our community
I will add it to my public share in few minutes...
I aim to please!
akadonny,
Thanks for sharing. Haven't done this in a very long time so maybe I'll give it go.
I downloaded your full 99mb Kitchen, and everything extracts fine. I've cooked up several ROMs so far, so I have a decent understanding of the process.
I apologize if this question has a simple answer, but I am having no luck, so here goes:
I want to use your 20748 build (you mentioned that 20753 has issues with SMS Threading) to update my NATF ROM series. Due to extensive customization I have done to my OEM folder, I would like to keep it as it, and so I extracted your ROM and SYS archives into my existing Kitchen folder. Now this is where it gets complicated...
I have tried using you Kitchen and Alex's Kitchen, both produce different results, and neither seem to work.
Using your Kitchen, the ROM appears to build fine, but OS.nb is nowhere to be found when HTC ROM Tool launches.
If I use Alex's Kitchen with BuildOS 2.7, then I get an error that it cannot find the ROM folder, but after clicking OK, everything builds as normal. However, after flashing the new ROM, my Tilt sits at the initial splash with R G D and will not go any further.
If I update the BuildOS in Alex's Kitchen to 4.3, everything builds correct and the ROM flashes OK, but UC does not run, File Explorer has an AT&T icon for some reason, and Manilla does not work.
--Ultimately, here is my question--
I want to keep the customizations that I have made to both AT&T Official 6.1 ROM (3.57) and HTC's Official WWE (3.28), but I want to use a newer OS build.
Is there a very special/exact combination of things I need to do in order to achieve this?
Thank you for absolutely any insight you can provide.
@NATF- have you tried mbarvian's Kitchen? I have been using his for awhile now trying to get a decent fully stripped rom....It's pretty decent.
@akadonny- sorry for me to tell him it. I will try yours out too...thanks again for your kitchen. Great if added to Wiki...
Knumb said:
@NATF- have you tried mbarvian's Kitchen? I have been using his for awhile now trying to get a decent fully stripped rom....It's pretty decent.
@akadonny- sorry for me to tell him it. I will try yours out too...thanks again for your kitchen. Great if added to Wiki...
Click to expand...
Click to collapse
I tried this one also...
I must be doing something wrong since these kitchen's can't all be incompatible with the 20xxx builds (can they?), but I can't seem to figure it out.
notatreofan,
You should be able to combine your OEM with any ROM and/or SYS. If you run through the kitchen I provided you will need to look for os-new.nb as that is the file that is created. I may be wrong, but I think you need Windows Script 5.6 or something like that. Also, the kitchen needs to be run from the root of a drive so the folder structure looks something like:
C:\Kitchen\OEM
C:\Kitchen\ROM
C:\Kitchen\SYS
After you run !COOK.cmd and it finishes you will have a os-new.nb in your C:\Kitchen folder. Sorry if I'm not understanding correctly. I hope this solves your issue.
All - I removed the 20753 ROM and SYS and added 20755 ROM and SYS
akadonny said:
notatreofan,
You should be able to combine your OEM with any ROM and/or SYS. If you run through the kitchen I provided you will need to look for os-new.nb as that is the file that is created. I may be wrong, but I think you need Windows Script 5.6 or something like that. Also, the kitchen needs to be run from the root of a drive so the folder structure looks something like:
C:\Kitchen\OEM
C:\Kitchen\ROM
C:\Kitchen\SYS
After you run !COOK.cmd and it finishes you will have a os-new.nb in your C:\Kitchen folder. Sorry if I'm not understanding correctly. I hope this solves your issue.
All - I removed the 20753 ROM and SYS and added 20755 ROM and SYS
Click to expand...
Click to collapse
Thank you for your answer. I could swear this is what I was doing, but I've tried so many things that I cannot remember... I'm going to try this method (again?) now, and I'll report back.
i have the same problem
i put your kitchen d:\Kitchen
after inside there the FOLDER sys and rom from 20755 and oem from 3.29
i push the cook
flash the new rom
and after splash screen with R,G,D no respond
My problem continues also.
I can cook successfully if I use the included OEM folders, but mine still causes a freeze at boot.
Plus my packages don't cook in properly using your Kitchen either. I put all of my packages in the OEM folder like your instructions say, and I can see BuildOS processing them, but I know that they're not being integrated because the resulting RUU_signed.nbh file is 28MB too small.
I try now the older 20748
and all working grate
in ABOUT screen have the new number of OS and Build
ACADONY you must test the 20755 again
something going wrong with it
also i can inclunding package with you rom
and your package don't working with alex kitchen
NotATreoFan said:
My problem continues also.
I can cook successfully if I use the included OEM folders, but mine still causes a freeze at boot.
Plus my packages don't cook in properly using your Kitchen either. I put all of my packages in the OEM folder like your instructions say, and I can see BuildOS processing them, but I know that they're not being integrated because the resulting RUU_signed.nbh file is 28MB too small.
Click to expand...
Click to collapse
I am having the same problem at NATF....any ideas????
No preblems at all with 20748... about cooking...
The one big problem at this moment is that I don't get connection trough my provider/operator.
Through ActiveSync and wifi, programs like PIE and RSS Hub works but not via G, E, 3G or H.
It has connection, I mean G, E, 3G or H are visible (depends area wich one) and there is coming an another smaller icon of the four icons but no connection with an error... ;(
Black-Rose said:
No preblems at all with 20748... about cooking...
The one big problem at this moment is that I don't get connection trough my provider/operator.
Through ActiveSync and wifi, programs like PIE and RSS Hub works but not via G, E, 3G or H.
It has connection, I mean G, E, 3G or H are visible (depends area wich one) and there is coming an another smaller icon of the four icons but no connection with an error... ;(
Click to expand...
Click to collapse
the 20748 is only one who working.. but activesync running on backround
20755 stack on splash screen
20753 when flash it start the boot loader screen and say something for error in core try again
For those getting stuck at the bootloader with 20755. Check to make sure that wince.nls is either in the ROM\XIP folder or as a package in SYS. This is a known problem with ROM's that hang at the splash screen. This may not be the case here, but it wouldn't hurt to check. I'm downloading 20755 now. I'll see what I can do.
KMFM$ said:
For those getting stuck at the bootloader with 20755. Check to make sure that wince.nls is either in the ROM\XIP folder or as a package in SYS. This is a known problem with ROM's that hang at the splash screen. This may not be the case here, but it wouldn't hurt to check. I'm downloading 20755 now. I'll see what I can do.
Click to expand...
Click to collapse
you found any solution?
i try to night your tip!!
tell us if you found something
-EDIT-
this tip not working
Hi folks,
After messing around for a while, I finally created my own ROM and sucessfully flashed to my wing. It all works, but it has out dated build. I am using Ivan's guide and Hypercore to cook my room. Here my question. In hypercore, when I extracted the XIP, all the files in the XIP folder are binary. However, from the Hermes forum, they posted the base SYS and XIP for the newest build, but they are in package format. Can I use this new SYS and XIP in Hypercore? If so, how? Thanks
As long as you port the XIP and SYS as per my XIP porting guide, then yes. But you can't port the XIP using Hypercore alone. You'd have to use Bepe's extended kitchen. This kitchen will automatically fix the memory addressing for you. The memory addressing of the the SYS you can easily fix by running G'Reloc after following my walkthrough for XIP porting.
Hi,
Here's what I did:
port xip and sys using ivan's guide
replace sys and xip into bepe's kitchen
replace my oem folder (mine is from the stock rom, not sure if it works with 6.1, so I borrow ivan's justclean oem)
build the rom
After the flash, it stuck in the second splash screen, the blinking light for radio is blinking. There is also a "beep" sound right after it passed the first splash and entering the second splash. Then it stopped here. What's wrong with my procedure? Is this symptom indicate the xip or the sys part gone wrong? Any help is appriciated.
live4nothing said:
Hi,
Here's what I did:
port xip and sys using ivan's guide
replace sys and xip into bepe's kitchen
replace my oem folder (mine is from the stock rom, not sure if it works with 6.1, so I borrow ivan's justclean oem)
build the rom
After the flash, it stuck in the second splash screen, the blinking light for radio is blinking. There is also a "beep" sound right after it passed the first splash and entering the second splash. Then it stopped here. What's wrong with my procedure? Is this symptom indicate the xip or the sys part gone wrong? Any help is appriciated.
Click to expand...
Click to collapse
That's because the SYS and the OEM folders were G'Reloc'ed sperately. In other words, place both Bepe's kitchen. Or just drop and run G'Reloc into your Build folder in Hypercore and run it before you start cooking. (You have modules coming from different places. You have to adjust the memory addresses to not conflict with each other.)
ivanmmj said:
That's because the SYS and the OEM folders were G'Reloc'ed sperately. In other words, place both Bepe's kitchen. Or just drop and run G'Reloc into your Build folder in Hypercore and run it before you start cooking. (You have modules coming from different places. You have to adjust the memory addresses to not conflict with each other.)
Click to expand...
Click to collapse
Sorry, I did not type it correctly. I actually ran g'reloc after I put both both SYS and XIP in bepe's kitchen. One thing is that in the status bar of g'reloc, it show total of 488 modules and relocated 288 modules. Is this bad? If so how do I fix it? Here what I did to port the XIP and SYS:
1) use masterrom from hypercore to extract xip.bin from the newest pdaviet rom (the 20753 build)
2) use bepe's xipport to dump and create packages as your guide showed
3) copy and replace the folders inside MSXIPKernel and MSXIPKernelLTK from Files and Modules into Bepe's kitchen's old XIP
4) get the new SYS from hermes' forum, replace with my old .vm, wincenls_wwe, shell/shell32 shell/shellres
5) replace the old SYS folder with my new ported SYS folder
6) borrow OEM folder from your justclean kitchen
7) run g'reloc
8) run buildOS and try to delete duplicate files (I kept the ones from SYS, deleted the ones in OEM)
9) build new new nbh from nb and flash
what did I do wrong? my goal is to have the most update build and software. I tried pdaviet's 20753 build, it is incredibly fast. Thanks for your help
Another question, would is be bad or could anything bad happen to my wing if I flashed it too much? I flashed to test my rom more than 20 times this week.
live4nothing said:
Sorry, I did not type it correctly. I actually ran g'reloc after I put both both SYS and XIP in bepe's kitchen. One thing is that in the status bar of g'reloc, it show total of 488 modules and relocated 288 modules. Is this bad? If so how do I fix it? Here what I did to port the XIP and SYS:
1) use masterrom from hypercore to extract xip.bin from the newest pdaviet rom (the 20753 build)
2) use bepe's xipport to dump and create packages as your guide showed
3) copy and replace the folders inside MSXIPKernel and MSXIPKernelLTK from Files and Modules into Bepe's kitchen's old XIP
4) get the new SYS from hermes' forum, replace with my old .vm, wincenls_wwe, shell/shell32 shell/shellres
5) replace the old SYS folder with my new ported SYS folder
6) borrow OEM folder from your justclean kitchen
7) run g'reloc
8) run buildOS and try to delete duplicate files (I kept the ones from SYS, deleted the ones in OEM)
9) build new new nbh from nb and flash
what did I do wrong? my goal is to have the most update build and software. I tried pdaviet's 20753 build, it is incredibly fast. Thanks for your help
Another question, would is be bad or could anything bad happen to my wing if I flashed it too much? I flashed to test my rom more than 20 times this week.
Click to expand...
Click to collapse
I tired that build as well and it had issues, thats why I went with 20748 instead.
Also, if you compare the size of the sys folder for build 20753 and another version, you will know why it's faster.
Just and FYI,
Good tips. Also, you have to build the ROM from within Bepe's kitchen. That way, it runs G'reloc on the XIP as well. Or, run the G'reloc with the following AFTER running BuildOS but before actually building the ROM. "G'Reloc.exe -doit -dump"
Ivan and Tony, Thanks. One will try the 20748 build later this week if I have time. However, I have one more question. I look around the forum, I saw there are two type of xip like this:
XIP: (bigstorage)
20753_XIP 09/19/2008
20755-XIP 09/23/2008
To Make XIP/ROM Non-BigStorage or Real BigStorage:
Copy this over existing rom folder
What the different between bigstorage and non-bigstorage or real bigstorage? Which one should I use for our wing/herald? Again thanks for your your help.
Those bigstorage do not apply to our ROM's. Our devices do not store data in the same way as BigStorage compatible ROMs. Our BigStorage comes from stripping the extra crap out of our ROMs.
Could this be the reason I could never got my rom working. I first used there sys and xip. Can I use their SYS? Since we cann't recook already cooked rom and I can't find any new base rom in our forum.
live4nothing said:
Could this be the reason I could never got my rom working. I first used there sys and xip. Can I use their SYS? Since we cann't recook already cooked rom and I can't find any new base rom in our forum.
Click to expand...
Click to collapse
You can use any SYS and XIP that isn't a ROM that has been made with certain kitchens... The issue is that you have to G'reloc the OEM, SYS and XIP within the same kitchen while they're in the same directory. G'reloc will only relocate the modules it sees and if it relocates them seperately, it might set the modules to the same memory address as the other G'reloc did with the OEM package.
Say I downloaded "frauhottelmann"'s GUI kitchen and I grabbed the original, unmodified S740 SYS and OEM folders from a thread here.
What would I need to replace in order to build a ROM that will bootup on an Excalibur ? I have the "dump" of the original 6.1 ROM from the Excalibur. Some drivers maybe ? Any help ? Thanks
Oh, so you got it already. You should start with the OEM folder of the Excalibur. Then you might have to add some of the *.cpl.xml from OEMMISC to get all settings to work. The new packages are a bit trickier to use. You need more files from the new OEM. And don't use the new Connection Setup, it doesn't work. You should be able to use the whole SYS folder though.
This is going to be difficult then. The only kitchen that exists for the Excalibur, dumps the contents of the ROM in one folder and doesn't seperate the foldes out to OEM, SYS, etc...
So is the SYS folder where all the drivers are then ?
No. There are two main folder. SYS is for the general Windows Mobile OS part. OEM is what the manufacturer or you add. The folder for drivers is on OEM and is called OEMDrivers. If you have a dump, you can make "packages" with PKGTools. There is no official 6.1 ROM right? So I guess this will be a problem, because then it doesn't sort the packages right. You'll have to try. Maybe send me a screen shot of the files or the result!
Well the original 6.1 ROM for the Excalibur (the ONLY one) was made by this guy Kavana. I'm pretty sure it was based on the files from the MS emulator and drivers from the OEM WM6. IS PkgTools included in your kitchen ? Should I try to dissassemble the ROM with your kitchen ?
yes pkgtools included.
give it a try and post if it worked!
good luck mate... i saw your prog for the weather! really nice!!
htc sliding plugin also rocks! anyway keep it up!
Well I managed to make an excalibur ROM that works (partially) with the VOX GUI kitchen, and replacing the OEMDrivers with the drivers from my official WM6 ROM. Problem is, the center button on the keypad doesn't work. Everything else is fine... although WI-FI and BT don't turn on. Any ideas what I'm doing wrong ? Oh and the startup screen is all skewed and in 4 pieces, right after the splash screen, bu before the usual winmo 6.1 splash screen.
Well I'm over that road bump now, and I'm trying to port the S740 XIP and SYS over to take advantage of the new CHOME
So far, so good...
Thanks guys for the support. I was able to make a new ROM based on the 20279 core from the S740 ALL by myself. Reading these forums for a few days is what did the trick... heh. THe ROM runs great and I have to say that BuildOS+package tools is my best ROM cooking friend right now...
NRGZ28 said:
Well the original 6.1 ROM for the Excalibur (the ONLY one) was made by this guy Kavana. I'm pretty sure it was based on the files from the MS emulator and drivers from the OEM WM6. IS PkgTools included in your kitchen ? Should I try to dissassemble the ROM with your kitchen ?
Click to expand...
Click to collapse
There is no rgu file in the rom you dumped.
and the one is not official 6.1.
You can dump the
moto q8 WM6.1 rom
s740 official rom
C810 official rom for your resource.
I know.. that was my original problem. No worries though, as I used the SYS folder from the S740 and all is well now