yashsingh1/xdaforums huggingface dataset:
[Touch GSM ROM Development] Noonski:
Your right in both cases.

I just wanted to mention that you don't need to use numbers in those cases.

And to be honost i still have taskmanager cooked, but not running to close windows or on the homescreen. Haven't had the time to change all this.

Giving the whole engine an overhaul, and even polishing up the tiny parts like giving each App an unique Icon (almost unique then):D
[Touch GSM ROM Development] Ameet:
Well I'm going to try to use the bootlauncher package to load the services and the exe at startup :D Lets hope we can let go of the TM completely :D
[Touch GSM ROM Development] sendhiloo7:
Thanks for cook class

Hi,

With your help i able create my own from Shipped Rom.

when try recook from cooked ROM,itz getting error.

Can you help me......
[Touch GSM ROM Development] Ameet:
What is the exact error you getting and when?
[Touch GSM ROM Development] sendhiloo7:
thank for reply.

i am not able create SYS&OEM from Dump
[Touch GSM ROM Development] fcukmayank:
looks like you are dumping a cooked rom

you can't do that
[Touch GSM ROM Development] Ameet:
Hmm.. Which ROM are you trying to dump? If you are dumping a cooked ROM then you need all the dsm & rgu files which you can copy from your existing OEM & SYS dirs into the dump dir and then try to rebuild packages ;)
[Touch GSM ROM Development] sendhiloo7:
ok. i will try and come back

Thanks
[Touch GSM ROM Development] fcukmayank:
can anybody guide me on which folders do i need to replace while sys porting

currently i replace .vm .rom shell os and wincell plus sql ce

wat am i doing wrong

i have ported the xip correctly
[Touch GSM ROM Development] !Aman!:
replacing .VM is enough, if u are using old kitchens... but if u use Bepe's platformrebuilder, u dont need to replace anything (except for dpi's, mui's etc if needed). also make sure wincenls_wwe is there inside the SYS.
[Touch GSM ROM Development] Noonski:
Hey Aman smart Nick change.

Maybe i should change mine to !!Noonski!! :D
[Touch GSM ROM Development] dsixda:
Haha.. I love seeing the nickname when you click on "Members List" at the top ;-)

When using Platform Rebuilder, be careful how you use it for other devices. For example, when cooking for the Diamond, the WinCENLS folder has to go under the ROM/XIP folder and not SYS; otherwise you'll brick. For Elfin you should leave it under SYS.
[Touch GSM ROM Development] Noonski:
Doing my hopefully final flash to test the XDA UC.

If SDConFig.txt exist run at third boot if not run at second boot:D

Ready for Beta testing Whooo Ha!

There used to be a time i could say Rock and Roll *******!

Now i have to watch my language:rolleyes:

CrossPosting is good Confusion is even better.
[Touch GSM ROM Development] !Aman!:
thanks! i changed my nick a long time back, almost 3 months now... i was just not posting here, had some personal problems.

it can go to SYS for diamond also, Ameet knows about this.
[Touch GSM ROM Development] dsixda:
Oh really... after bricking the Diamond, I read a post from Ameet where he said you couldn't ;) Ok I will ask him.

Ah, nevermind.. here is the post:

http://xdaforums.com/showpost.php?p=3611817&postcount=849
[Touch GSM ROM Development] skauk:
SYS and XIP question

I have got myself the ELfink_WWE kitchen which is basically a dump rom and platform rebuidler to build rom. I have dumped a WWE 6.1 Rom base rom that builds again perfectly and I can remove all the junk out of it and still builds fine. I want to use the SYS and XIP for WM6.5 (thanks to dsixda) so that its becomes WM6.5 BUT when I delete my SYS and copy over the WM6.5 SYS the build ROM just errors first with the windows message that windows has encountered an error and the app will be shutdown and then says errorlevel and some really randown numbers that done mean anything to me.

How do I change the XIP and SYS of my 6. base to make it WM6.5 ??? using platform rebuilder I been looking for ages and not found out.
[Touch GSM ROM Development] dsixda:
skauk,

For Platform Rebuilder you can just swap out the SYS with the new one (as I told you before). For XIP, just swap out the MSXIPKernel folder. ... the OEMXIPKernel folder stays the same as before.
[Touch GSM ROM Development] skauk:
That didnt work

I tried that and that is when i get the error just deleting the content of my base and replacing it with the content of your SYS doesnt work for me :-(
[Touch GSM ROM Development] skauk:
I get ImgfsFromDump.exe has encountered and error and needs to close so I click dont sent and i get on the DOS screen..

ERROR!(errorlevel:- 1073741819)

I errors quite a way in to the process though at:

Processing "cespell.dll" as a module.
[Touch GSM ROM Development] trueg:
Did you change the kernel mode in platformrebuilder?

'set OLDKERNEL=1' for WM 6.1

'set OLDKERNEL=' for WM 6.5
[Touch GSM ROM Development] dsixda:
I didn't need to change OLDKERNEL for mine, it's the same for 6.1 and 6.5.
[Touch GSM ROM Development] trueg:
Are you using the updated version (2.1)? I ran into an error after updating to 2.1 and not setting the variable appropriately, but now looking back the problem was my ROM would hang, I didn't get an error while building. The variable is not used in the first version.
[Touch GSM ROM Development] skauk:
I dont have those variables in my buildROM batch file. I dont see where i can work out what version it is but if i right click on the platform builder icon it says file version 2.0 ??

I got 2.1 from the dark forces post and copied it to my basic bepe kitchen I just need to edit the buildrom.bat I suppose with thie 2 variables above ?
[Touch GSM ROM Development] dsixda:
Make sure you have 2.1 with that variable set to 1 for both wm6.1 and wm6.5.
[Touch GSM ROM Development] trueg:
This is from darkforcestream.com

Updates:

platformbuilder.zip V 2.1

New Variables:

set OLDKERNEL=1 (in "build_rom.bat")

- This variable MUST be set if you don't have a real AKU5 nk.exe

- If you are using an AKU5+ nk.exe remove this line from the bat file or set it without a value: set OLDKERNEL=

I believe alot of the WM 6.5 ROM dumps are not using a native AKU5 which is why it still works when set to 1. There was leaked copy of WM 6.5 for the Raphael (a.k.a. 21169 autobuilder build) that was released and the kernel from that has been in use for the last few weeks (on the Raphael at least).
[Touch GSM ROM Development] skauk:
2.1 is better

I at least get a decent error message although i dont know why really, I have copied the XIP from wm6.5 into the ROM/XIP folder in the kitchen it even says found 2 XIP when you first start platform rebuilder it completes the whole of the plaform rebuilder bit and then opens a new dos window for IMPLANDXIP and then says in red NO XIP SECTION FOUND. error level 4
[Touch GSM ROM Development] !Aman!:
thats because u have removed the ULDR and implantxip doesnt support ROMs without ULDR. u need to use msflsh50 tool to insert the xip instead of implantxip.
[Touch GSM ROM Development] fcukmayank:
when i build using bepe kitchen

it get an error rom kitchen excuteble has stopped working
[Touch GSM ROM Development] !Aman!:
from where did u get the SYS? did u replace anything inside it? if possible, elaborate the error or post a screenshot.
[Touch GSM ROM Development] fcukmayank:
i got the sys from the nike kitchen

replaced the rom vm and wincell folder

and have ported xip using xipporter ex

currently using hubrid kitchen

sometime my build works something it does not
[Touch GSM ROM Development] skauk:
Me too I downloaded bepe toolset and got an nbh file i ran extract nbh to get an nb file but when i drag to to Dump_800 it tells me that an error was performed and in the DOS window it says it cannot map file IMGFS.BIN

Investigates it says my elf uses 0x200 so I used dump_200 still same error but without the windows illigal operation.
[Touch GSM ROM Development] !Aman!:
u can rely on bepe's kitchen for everything including xip porting. using bepe's kitchen, u dont even need to have .VM and .ROM inside the SYS, u can just delete them.
[Touch GSM ROM Development] dsixda:
If you use the exact same version of Bepe's kitchen found in the Hybrid Kitchen thread, then you shouldn't have problems. It doesn't use ImplantXIP.
[Touch GSM ROM Development] fcukmayank:
@dsixda

can u post the exact link for the kitchen or upload them to rapidshare???

watsay???
[Touch GSM ROM Development] !Aman!:
do u have the following code inside dump_200.bat?

"%path_exe%bin\NBSPLIT" -data 512 -extra 8 "%~1"
del "%~1.extra"

if it is there, delete it and then try.
[Touch GSM ROM Development] skauk:
This is the DOs readout when I have these 2 lines in:

NBSplit 2.1rc2

Using data chunk size = 0x200 and extra chunk size = 0x8

on file C:\Documents and Settings\kevin.squires\Desktop\00_OS.nb

Done.

ImgfsFromNb 2.1rc2

ImgFs partition starts at 0x00000000 and ends at 0x00000000

Dumping IMGFS at offset 0x00646e48 (size 0xff9b91b8)

Done!

ImgfsToDump 2.1rc2

Cannot map file IMGFS.BIN

Could Not Find C:\Documents and Settings\kevin.squires\Desktop\dump_MemoryMap.tx

t

The system cannot find the file specified.

Press any key to continue . . .

This is the DOS readout when I take them out:..

ImgfsFromNb 2.1rc2

Could not open input file 'C:\Documents and Settings\kevin.squires\Desktop\00_OS

.nb.PAYLOAD'. Aborting.

ImgfsToDump 2.1rc2

Cannot map file IMGFS.BIN

Could Not Find C:\Documents and Settings\kevin.squires\Desktop\IMGFS.BIN

Could Not Find C:\Documents and Settings\kevin.squires\Desktop\dump_MemoryMap.tx

t

The system cannot find the file specified.

Press any key to continue . . .

Either way it doesnt work for me bepe's video made it all look seemless.
[Touch GSM ROM Development] !Aman!:
also change the following line

"%path_exe%bin\IMGFSFROMNB" "%~1.PAYLOAD" IMGFS.BIN

to

"%path_exe%bin\IMGFSFROMNB" "%~1" IMGFS.BIN

then try
[Touch GSM ROM Development] skauk:
That did more than before gave me a desktop folder called IMGFS but looking at Bepe's video it doesnt give me the other file so i can get the XIP, I know Bepe in the video uses Dump_800 but i thought that was due to the ROM using 0x800 ??

I edited the Dump_800 as well just changing the

"%path_exe%bin\IMGFSFROMNB" "%~1.PAYLOAD" IMGFS.BIN[/code]

to

"%path_exe%bin\IMGFSFROMNB" "%~1" IMGFS.BIN

That ran fine without a windows error, created me a IMGFS folder that i can build with package builder, it also created an OS.nb.payload file that i tried to use with the DUmp XIP but it doesnt work says again there is no XIP section.
[Touch GSM ROM Development] dsixda:
I just told you where it is... Go to post 2 of that thread.
[Touch GSM ROM Development] sendhiloo7:
Dumped ROM

when i extract ROM, in package folder i get SYS, OEM , some *.dll folder.

inside the SYS folder -> .ROM, MSXIPKernel. OEM folder is empty.

*.dll folder where to move in SYS or OEM:confused:

please help me.....
[Touch GSM ROM Development] Ameet:
My dear friend. You are trying to dump some cooked ROM. To use that ROM you will need all the dsm & rgu files. Dump a nice clean shipped ROM and you will get a much better looking dir structure
[Touch GSM ROM Development] fcukmayank:
can u post the link
[Touch GSM ROM Development] skauk:
What about my ROm its a Shipped

Its the once DSIXDA posted in the the shiped ROM sticky that had the Radio and IPL/SPL removed. I can dump the SYS, OEM and EXT correctly using bepe's toolset but when i try and get an XIP I just get the folders with the names of the DLL's and not anything I can build into packages to get the OEMIPKernal etc.

I can however use the other Demo kitchen for Elfin that posed on the Kitchen Sticky thats based on bepe's platform rebuilder kitchen and it dunps the whole shipped ROM out to SYS, OEM and EXT fine and I can re-build it and flash fine. But when i copy over the SYS and XIP that DSIXDA has posted for WM6.5 I get buid errors.

I have two kitchens that Bepe shows to work fine but they dont for me....

Need some help just port a SYS and XIP into an existing 6.1 ROM Dump am I using the best tools for the job ?
[Touch GSM ROM Development] + Que PPC:
:eek: this is it fcuck

hahaha http://xdaforums.com/showthread.php?t=335631 :rolleyes:

what if i dont erase the dsm missing on customs or in the shipped?

I did it... everything seems to be ok... it finish with no errors, but when the DOS starts moving sys and oem it freezes an cant move the folders so i move it manually... but thats why the missing dsm persist til the finish process i close it and cant clean that three dsm... ;)

This is nice, thanks to many people in this thread...

thanks noonski since i have test your custom manilla 2d brushed metal first introduce in wizard device i knew that you could make something like this... thanks to ayuu and many many people involved... i need to learn more... so i need to read more.
[Touch GSM ROM Development] Noonski:
No Thanks, it's a pleasure , and i'm sure it is for everyone that comes back here to help out.

My personal mission has been to get more people into doing something instead flashing their phone.

And in saying that i hope most of you here would want to help testing out my 10kb of code that will hopefully change the way stuff is installed and cooked.

And hopefully also will help XDA be an anwser to Microsofts new App Store.

As i don't see that as being a directly good thing to keep developers doing what they have been doing here.

Make Free Solutions easy and accessible.
[Touch GSM ROM Development] + Que PPC:
Yeah thats the real XDA base purpouse!

Btw... whats the answer to... my last post, the missing dsm that the kitchen told me..?

Oh sorry... does the suscriptions still open on this season? i mean cooking class class 2008/09???

I want to inscribe myself on this class... :p
[Touch GSM ROM Development] Noonski:
I didn't get the Missing DSM part.

It's been a long time i used Hypercore, and it always gave three missing DSM files in package creator.

Can you post the results of package creator?
[Touch GSM ROM Development] + Que PPC:
where it is?

Where can I found the log text?... yeah that thre dsm missing does make anysense on the final rom... im afraid to flash my first rom with that doubt. :confused:
[Touch GSM ROM Development] Noonski:
in the build package tool you can copy the text inside the tool itself.
[Touch GSM ROM Development] skauk:
I Give up

After about 2 weeks of trying just about everything I can with every Kitchen and even mutiple kitchens I have yet to get anywhere with any kitchens. Dumping ROM fine and rebuild the same ROM again works fine in 1 kitchen but bepe platform builder kitchen just doesnt work for me at all IT even doesnt work just rebuilding a shipped ROM I just dump and transfer to that kitchen. I cannnot port an SYS or XIP sucessfully to save my life I havent even got as far as bricking my ELFIN yet cause I cannot get a cooked build to complete and make the nbh file.

I been trying but im obviously just useless. Thanks to DSIXDA who has tried and tried to help me along the way but its game over cause im out of ideas. :mad:
[Touch GSM ROM Development] dsixda:
Dude.. don't give up, frustration is part of cooking.

Make sure you got the exact same version of Platform Rebuilder that Kokotos posted in the Hybrid Kitchen sticky (post #2). The one in Bepe's thread at Darkforcesteam.com will not work 100%. I have also posted the working Elfin XIP/SYS for 21215 at PPCGeeks.

BTW, ****fuckfuck (or whatever your name is) ;), I have told you many times to look in Kokotas' thread yet you still keep asking me and telling me I am hiding something. Please read the stickies, the authors spent a lot of time on them to help others.

Once you guys have the correct copy of PRB, your life is set.
[Touch GSM ROM Development] skauk:
You mean the Elfink_WWE kitchen says thread title is "Example Kitchen based on bepe's Platformrebuilder"

Thats the one I downloaded first before the Dark Forces one. Its the one that allows me to unpack my 6.1 shipped ROM from the nbh file which i drop into the BaseROM folder. Its also the one that lets me rebuild the 6.1 ROM no problem.

But then its also the one that when I delete the SYS folder and replace it with yours and Delete the XIP folder and replace it with yours it wont let me build it for love nor money. Which is what is frustrating me. I even tried just replacing the 1 folder in the XIP folder and leaving the OEM one from the 6.1 ROM. Nothing seems to work.

I did watch the video on Bepe's dark forces platform builder version and saw him drop the nb file onto the DUMP_800 icon which doesnt work for me without hacking at the createROM batch file and then it doesnt seem to complete 100% and im left with a half extracted ROM.

What could possibly be wrong with what im doing with the Koto example kitchen, is there anything that needs editing in the batch files from the download to make it work.??
[Touch GSM ROM Development] lokura:
im having the same problems including ERROR!(errorlevel:- 1073741819)

i was able to cook a rom till xip-sys 21159, after this one i tried with 21500 and 501 with no succes, im using kokos and bepes kitchens (the one from kokos thread) and dsixda sys-xip from ppcgeeks

i have tried to port sys and xip, with the sys and greloc i havent integrer overflow error but not working, any way i try with wmreloc and with this i get error (i dont remember which one), with the xip less problems, ported succesfully, and working but at about tab on settings shows 21139

I'm going crazy, but well, this is my nick
[Touch GSM ROM Development] skauk:
I only started trying to cook from 21500 so I not had any sucess but you say that Koto's kitchen worked for previous WM6.5 builds ?

Hmmm anyone got any ideas why ?
[Touch GSM ROM Development] lokura:
yes, i´ve roms with 21139 and 21159, i started using bepes when i cant use dsi sys on it due to .vm is not present

i remember now the error on wmreloc, it was "cant open ...\sys\.vm\imageinfo.bin
[Touch GSM ROM Development] dsixda:
Guys, delete your kitchens and burn them to hell. Just use Platform Rebuilder... It's what we have been talking about all this time. I even said in my SYS/XIP post that I used Platform Rebuilder. It doesn't need those stupid .VM .ROM folders and manual relocating. You guys don't listen :D
[Touch GSM ROM Development] lokura:
this is the one im using with your sys-xip
[Touch GSM ROM Development] dsixda:
Hmm..maybe your base ROM is not the correct one.

(Check your PM)
[Touch GSM ROM Development] + Que PPC:
lol i think i did it...

But it doesnt works.... seems that the RUU cant flash it to my dev.. it says invalid comand at 3%... i have tried the RUU overwrited... and the custom... even the original unpack it from the shipped but always the same error INVALID COMMAND.

Maybe we just need to look over other forums to get the newest way to cook isnt it.... lets try what happends with the platform rebuilder at DFT.

Hey noonski sorry im not on my job and the cooking was ther... lets try another one... i red you telling me you dont use hypercore since a long time ago... lets see that platform rebuilder... or what do you use..? ervius visual? im there reding as much as i can... :)
[Touch GSM ROM Development] Noonski:
http://xdaforums.com/showthread.php?t=365664

And then the same version packaged for Diamond and Raphael by Jsceppi.

But my last ELF rom was maybe even more then half a year ago.
[Touch GSM ROM Development] skauk:
I works!!!!

With many many thanks to DSIXDA for plenty of help I finally got my 6.1 ROM to build into WM6.5 21501 and now 21502 I just need to mess about with it all now and get it working how I want. The 6.1 shipped rom has loads of stuff in the EXT folder in the kitchen so I renamed it and starting from scratch with a blank EXT folder.

It is advisable to use this for adding apps ?? there is an app that allows you to turn the screen on and off that must be in the old EXT folder was wondering when I find it is it worth putting it into my new EXT folder or converting it to a SYS ??? If thats possible.
[Touch GSM ROM Development] skauk:
What package is it that

What package is it that allows the power button to be used to turn the screen on and off. I have got a battery power app in my system folder already but when I turn the screen off it wont turn back on.
[Touch GSM ROM Development] Noonski:
I think you mean PsShutXP for the shutdown.

But if your screen doesn't turn on anymore when you press power, i'm not sure PSShut will solve it.
[Touch GSM ROM Development] skauk:
No it cannot be that it wasnt in my base rom and that works a treat I wonder if its the power app I am just going to try cooking it back into my 6.5 ROM via EXT folder and see.
[Touch GSM ROM Development] fcukmayank:
when i use bepe kitchen

i get an error rom kitchen excuteble has stopped working

but i have created my 6.5 rom with xip sys 21215 with hybrid kitchen
[Touch GSM ROM Development] lokura:
this error, at least for me, was due the path of initflashfiles.dat, once corrected is working fine
[Touch GSM ROM Development] dsixda:
You don't need the EXT folder. Just put your Packages under OEM... and all the new Microsoft build files go under SYS/XIP.
[Touch GSM ROM Development] skauk:
Ah right so I need to convert them

Some work to do then lol, the file I was missing from the EXT folder that would let the screen power be turned on and off was the power app although.

Before I added it the battery icon appeared in the system folder after I added the app from the old rom it didn appear and couldnt be run from windows folder on the device.

I reverted back to the latest Onyx 6.5 ROM while I play around for a while otherwise my phone will be out of action while i keep flashing and testing.
[Touch GSM ROM Development] fcukmayank:
i finally got the link to bepe kitchen in hybrid kitchen thread

but can i use it on vista ultimate
[Touch GSM ROM Development] lokura:
its working for me in home basic, may be you have to turn off user acount control
[Touch GSM ROM Development] dsixda:
So Lokura, did the files work? Thank you? ;)
[Touch GSM ROM Development] lokura:
yes working fine, haven´t receive my pm yesterday? a lot of tnx

and a little question, the new initflashfiles path is due to the kitchen?, ive downloaded a lot of sys and no one includes this file
[Touch GSM ROM Development] dsixda:
Oh, my PM box is full, which is probably why I didn't see your response :D

Initflashfiles.dat? That should be in your OEM_LANG_0409 folder.
[Touch GSM ROM Development] fcukmayank:
just got a hold a bepe kitchen

its awesome !!!

no need for relocating sys

and for xip just need to place your original oemxipkernel and add te msipkernel from the new xip

and ur done
[Touch GSM ROM Development] madsurfer1:
Do you care to share a download link?
[Touch GSM ROM Development] fcukmayank:
i will post it as soon as possible in MADE IN INDIA THREAD
[Touch GSM ROM Development] lokura:
yes, this should be the path, but first time i run your files it gime an error about initflashfiles wasnt in his paht, (it was in oem lang 0409) then i begin to try others folders, when i put it in sys base_lang_0409 it works fine, then i try with bepes kitchen from kokos thread and it works too with the new path

verry strange, but it works
[Touch GSM ROM Development] fcukmayank:
on working wid hybrid as well as hybrid kitchen

i found hybrid kitchen to be more useful than bepe kitchen

although all kitchens are based on bepe one

i found porting sys and xip on hybrid more easier

is there anyone who also agrees wid me????
[Touch GSM ROM Development] + Que PPC:
Ok lets see what happends here

In hybrid kitchen

I took the elfin 3.07 nbh form this forum... upper thread... unpack it... place on thje source... all extracted OEM XIP SYS then... move them to build os and load the app... to build it... finaly use the room tool by htc and... convert it as nbh for elfin wwe... and i get the final product but it cant be flashed to my elfin...?

I read the log for the build os... and in sys it says no RGU found in all the modules? is this why it can be flashed to my phone?

I did the xip port using the xip.bin and try again... nothing happends the result is the same...

anybody has an idea what am i skipping? :confused: