Hi can somebody guide me how can i delete packages from the OEM folder.I use EVK kitchen,i want to keep new packages in to the EXT folder,and want to delete the packages from OEM folder.
how can i do that?and to prevent from a non booting rom,which r modules/files/folder/ i should keep in the OEM?
help for this will be appreciated.
thx a lot
regards
Why bother with it, they will be overwrite from those one in EXT folder
Nahhh...jk....can you upload your OEM folder so we can have a look in it?
deepankerjha said:
Hi can somebody guide me how can i delete packages from the OEM folder.I use EVK kitchen,i want to keep new packages in to the EXT folder,and want to delete the packages from OEM folder.
how can i do that?and to prevent from a non booting rom,which r modules/files/folder/ i should keep in the OEM?
help for this will be appreciated.
thx a lot
regards
Click to expand...
Click to collapse
af974 said:
Why bother with it, they will be overwrite from those one in EXT folder
Nahhh...jk....can you upload your OEM folder so we can have a look in it?
Click to expand...
Click to collapse
I know that mate,but the problem is there r some packages in the OEM which i dont want to use at all but cant c a way to delete them,fearing it may not boot the rom.I want to make a complete NEW OEM or DELETE those packages completly.
i remember when last i tried this i got a rom with normal boot up and abnormal behaviour ....so just not daring again.will upload my OEM pkg for u to have look.
is there any way to know package specific files/folders in the OEM for EVK ?I doubt.....but then u r my SUNSHINE.... when it comes to problems in cooking
you are my sunshine....my only sunshine....lol nice song
you are to kind say this...im only a noob the real masters here are Shane (TPC),NGR,Leo(??...oh sure Laurentius ) and sorry if i forgot someone
I would make a thread with a list of OEM/EXT packages explanation,
im in the same mod as you ....
...what the hell is " irsir.dll " or " Random_Access_4_1_19173928_0" ??
dunno...lol...i just use the instinct to cook roms
waiting for your OEM.
deepankerjha said:
I know that mate,but the problem is there r some packages in the OEM which i dont want to use at all but cant c a way to delete them,fearing it may not boot the rom.I want to make a complete NEW OEM or DELETE those packages completly.
i remember when last i tried this i got a rom with normal boot up and abnormal behaviour ....so just not daring again.will upload my OEM pkg for u to have look.
is there any way to know package specific files/folders in the OEM for EVK ?I doubt.....but then u r my SUNSHINE.... when it comes to problems in cooking
Click to expand...
Click to collapse
af974 said:
you are my sunshine....my only sunshine....lol nice song
you are to kind say this...im only a noob the real masters here are Shane (TPC),NGR,Leo(??...oh sure Laurentius ) and sorry if i forgot someone
I would make a thread with a list of OEM/EXT packages explanation,
im in the same mod as you ....
...what the hell is " irsir.dll " or " Random_Access_4_1_19173928_0" ??
dunno...lol...i just use the instinct to cook roms
waiting for your OEM.
Click to expand...
Click to collapse
hey bro suddenly something came in my mind.just going to try that out.if it works,will let u know.
and yes SHANE is too good to be a human always supporting and always there....
regards
I haven't messed around much with OEM's myself, but the only thing to keep in mind is that if you shift a package from there to the EXT, you need to convert it to EXT format. Change .rgu's to app.reg files, delete the .dsm's, and get the proper folder structure. Once, I moved NETCF from a Sys to my EXT directory, not thinking about the folder conversion, and I ended up with a rom that didn't have net framework. It booted up ok, but let me tell you, that rom suck hard. It took me a while to figure out what I'd done wrong. Check your dump before flashing just to make sure all the files are included.
Random Access is the alphabet that appears on the right side of your contacts (and other places), and that gives you a quick shortcut to hop down to a specific letter. I'm guessing irsir.dll is some IR based driver? But if it's in your oem, then maybe it's something else. A quick google will definitely tell you what it is.
Edit: yeah irsir.dll is an ir driver:
IrDA Devices
Fast IR Driver nscirda.dll
Serial IR Driver Irsir.dll
Click to expand...
Click to collapse
Here's a thread that says you can remove irsir.dll if you don't have IR on your device. Not sure why they put it in, in that case.
oh dammit...now i cant sleep if you dont say me what came in your mind
Uhmmm.....are you sure that he is an human?? do you have prove?
deepankerjha said:
hey bro suddenly something came in my mind.just going to try that out.if it works,will let u know.
and yes SHANE is too good to be a human always supporting and always there....
regards
Click to expand...
Click to collapse
Farmer Ted said:
I haven't messed around much with OEM's myself, but the only thing to keep in mind is that if you shift a package from there to the EXT, you need to convert it to EXT format. Change .rgu's to app.reg files, delete the .dsm's, and get the proper folder structure. Once, I moved NETCF from a Sys to my EXT directory, not thinking about the folder conversion, and I ended up with a rom that didn't have net framework. It booted up ok, but let me tell you, that rom suck hard. It took me a while to figure out what I'd done wrong. Check your dump before flashing just to make sure all the files are included.
Click to expand...
Click to collapse
thx ted for ur thoughts on that,but how about if i dont want to move the OEM to EXT and use a new EXT?
deepankerjha said:
thx ted for ur thoughts on that,but how about if i dont want to move the OEM to EXT and use a new EXT?
Click to expand...
Click to collapse
Just create a new EXT, and move all the file you want into the \New EXT\Files folder, and if there's an associated .rgu, rename it app.reg and stick it in the \New EXT folder. That's pretty much all you have to do.
af974 said:
oh dammit...now i cant sleep if you dont say me what came in your mind
Uhmmm.....are you sure that he is an human?? do you have prove?
Click to expand...
Click to collapse
nop Shane is more than human... because being HUMAN i know
Farmer Ted said:
Just create a new EXT, and move all the file you want into the \New EXT\Files folder, and if there's an associated .rgu, rename it app.reg and stick it in the \New EXT folder. That's pretty much all you have to do.
Click to expand...
Click to collapse
ted thats exactly i want to know that what if i dont want some packages from the OEM how do i delete it ? because its a jungle out there in the OEM folder
deepankerjha said:
ted thats exactly i want to know that what if i dont want some packages from the OEM how do i delete it ? because its a jungle out there in the OEM folder
Click to expand...
Click to collapse
Not sure I am following correctly, but if you just want to move things to a new OEM folder so that you don't mess up the original OEM folder here is what I do.
Under the OEM folderI have a Rhodium folder. I just rename that to RhodiumOriginal and then make another folder Rhodium. now just copy everything to this folder and you can make changes without messing up the original folder. If soemthing doesn't work out, just delete the new folder and rename the original folder.
Just make sure that the folder you want to use is the first folder in the OEM directory or EVK won;t like it. If you rename the original folder to OriginalRhodium EVK won;t like it because O comes before R. Hope you understand that part. If not, EVK will let you know pretty quick there is a problem.
If i remember right you are using Mega EXT package right?
Well i guess you can delete OEM_app because is plenty of useless files with Mega Pack.
In OEM drivers i would not delete the dll folders and some dll file, but Autorun,commmanager,some ringtones and picture could be deleted without problem.
I suggest you to use an app for comapring folders,in 2nd thread there is one, for check both OEM and EXT and see which files are duplicated.
deepankerjha said:
ted thats exactly i want to know that what if i dont want some packages from the OEM how do i delete it ? because its a jungle out there in the OEM folder
Click to expand...
Click to collapse
- Following are the contents of my OEM folder in EVK for your reference. Everything else is in EXT :
.VM
0409
--ConfigAP
--CONNECTIONSETUPDB
--ExtendedPkg
--ExtraFilesPkg
--OEM_Lang_0409
--OperatorPkg
--OperatorPkg_PT
COMMON
--COLORSKIN
--OEM_DPI_96
--OEMAPPS
--OEMDrivers
--OEMMISC
--OEMOPERATORS
--OEMVersion
- This works fine for Elfin/Elf ROMs.
Hope this helps .
chota_shivaji said:
- Following are the contents of my OEM folder in EVK for your reference. Everything else is in EXT :
.VM
0409
--ConfigAP
--CONNECTIONSETUPDB
--ExtendedPkg
--ExtraFilesPkg
--OEM_Lang_0409
--OperatorPkg
--OperatorPkg_PT
COMMON
--COLORSKIN
--OEM_DPI_96
--OEMAPPS
--OEMDrivers
--OEMMISC
--OEMOPERATORS
--OEMVersion
- This works fine for Elfin/Elf ROMs.
Hope this helps .
Click to expand...
Click to collapse
so what ???
af974 said:
If i remember right you are using Mega EXT package right?
Well i guess you can delete OEM_app because is plenty of useless files with Mega Pack.
In OEM drivers i would not delete the dll folders and some dll file, but Autorun,commmanager,some ringtones and picture could be deleted without problem.
I suggest you to use an app for comapring folders,in 2nd thread there is one, for check both OEM and EXT and see which files are duplicated.
Click to expand...
Click to collapse
hi buddy
my thought didnt work,so dropped that idea.now going to follow what u have suggested
regards
Check this link about what packages are/aren't needed in OEM.
rgb-rgb said:
Not sure I am following correctly, but if you just want to move things to a new OEM folder so that you don't mess up the original OEM folder here is what I do.
Under the OEM folderI have a Rhodium folder. I just rename that to RhodiumOriginal and then make another folder Rhodium. now just copy everything to this folder and you can make changes without messing up the original folder. If soemthing doesn't work out, just delete the new folder and rename the original folder.
Just make sure that the folder you want to use is the first folder in the OEM directory or EVK won;t like it. If you rename the original folder to OriginalRhodium EVK won;t like it because O comes before R. Hope you understand that part. If not, EVK will let you know pretty quick there is a problem.
Click to expand...
Click to collapse
thats not the point mate,,,..but thx for trying to help
regards
Diagrafeas said:
Check this link about what packages are/aren't needed in OEM.
Click to expand...
Click to collapse
boy......that is SOMETHING ....thx a lot Diagrafeas
regards
One thing I've found with the OEM is that if you convert the .provxml's to app.reg files (for the ones with registry operations-don't mess with ones that load certificates and what-not), it will really speed up your first boot-time. There's really no good reason, for instance, to have a provxml load your OEM version. Just put that in a .reg file and delete the .provxml. I get to the welcome screen in 90 s with most of the registry operations loaded into app.reg files, and during screen alignment, the cursor moves quickly. If you use autorun for customization, though, you need to leave alone the autoruncfg reg key that is in the 107 (think that's the one) provxml.
Related
I have followed this tutorial exactly and put the folder it gives me here.
D:\Kitchen\OEM
The program I am trying this with is Advanced_Configuration_Tool_v3_3
The D drive is my second hard drive, however I did all the work to make the folder on my C drive just like the tutorial said. Then copied the folder to D:\Kitchen\OEM
Thus making D:\Kitchen\OEM\Advanced_Configuration_Tool_v3_3
Everytime I cook this ROM it does say Advanced_Configuration_Tool_v3_3 in the CMD however Advanced Configuration does not install when I flash.
What is it that I am doing wrong? I have searched and found nothing about my problem. I have also tried using a pre-made Advanced_Configuration_Tool_v3 from XDA2'S OEM PACK. So I do not think I am making it wrong, instead I am placing it in the wrong location or there is a file I need to edit to include the new folder. Those are just my guesses as this is my first time as a Chef and I have found no information on this particular problem.
Does a file that needs to be edited exist? From what I've gathered, I just turn the cab into a OEM and place that folder inside the folder that I did. Is that correct?
The Kitchen i am using is New Old style kitchen based on Bepe's tools
I have tried to make this as readable as possible, with as many links to what i refer to as possible. If there is anything I can do to explain my problem easier please let me know.
EDIT: I have found Advanced Config in my windows folder, however no shortcut was made in any menu. How do I fix this?
Also can someone tell me what the following means? Most folders in the folder OEM are labeled PACKAGE_Raphael_ then the name of the program. Then theres another folder labeled the same thing except at the end it has _0409
Also theres a folder named 0409
EDIT: I finaly got it to work. I'd like someone to explain why this made it work and explain what I put in my last edit. I got this to work by using package-creator-v2.7.
I dont know about EVK cos i use OsKitchen, anyway give a look here for converting Cab to OEM or EXT http://forum.xda-developers.com/showthread.php?t=525302 its a cool and easy to use.
TheSlimHim said:
I have followed this tutorial exactly and put the folder it gives me here.
D:\Kitchen\OEM
The program I am trying this with is Advanced_Configuration_Tool_v3_3
The D drive is my second hard drive, however I did all the work to make the folder on my C drive just like the tutorial said. Then copied the folder to D:\Kitchen\OEM
Thus making D:\Kitchen\OEM\Advanced_Configuration_Tool_v3_3
Everytime I cook this ROM it does say Advanced_Configuration_Tool_v3_3 in the CMD however Advanced Configuration does not install when I flash.
What is it that I am doing wrong? I have searched and found nothing about my problem. I have also tried using a pre-made Advanced_Configuration_Tool_v3 from XDA2'S OEM PACK. So I do not think I am making it wrong, instead I am placing it in the wrong location or there is a file I need to edit to include the new folder. Those are just my guesses as this is my first time as a Chef and I have found no information on this particular problem.
The Kitchen i am using is New Old style kitchen based on Bepe's tools
I have tried to make this as readable as possible, with as many links to what i refer to as possible. If there is anything I can do to explain my problem easier please let me know.
Click to expand...
Click to collapse
Are you sure that Advanced_Configuration_Tool_v3_3 was not installed?
The default link installation path for this app is the Settings\System folder and not Start menu\Programs.
Goto Start\Settings\System and check if there is an Advanced Config icon there.
dotcompt said:
Are you sure that Advanced_Configuration_Tool_v3_3 was not installed?
The default link installation path for this app is the Settings\System folder and not Start menu\Programs.
Goto Start\Settings\System and check if there is an Advanced Config icon there.
Click to expand...
Click to collapse
I did check in the settings and it is not in any of the tabs, but I did find it in the windows folder. How do I fix this? Like I said I have tried both making my own a pre-made. I'm am going to try what af974 suggested but I do not have high hopes since pre-made OEM did not work. I feel as if I am putting it in the wrong folder.
af974 said:
I dont know about EVK cos i use OsKitchen, anyway give a look here for converting Cab to OEM or EXT http://forum.xda-developers.com/showthread.php?t=525302 its a cool and easy to use.
Click to expand...
Click to collapse
Thank you. I'll give it a try, however it is not the OEM of the Cab that is the problem because I have tried pre-made.
For the EVK based kitchens you NEED an app.dat file in the root of the package you're trying to put in the ROM. That file, gets merged with the rest of the initflashfiles.dat file that can be (usually) found in OEM\0409\OEM_Lang_0409 . If you don't tell the system to copy the shortcut (usually found in the package as a *.lnk) to somewhere on the start menu, then you wont get a shortcut to the app
I hope i can help u learn how to cook rom and makes it more easier!
1.Structure OF THE KITCHEN
ROOT OF THE KITCHEN-------
dump----> This will contan files dumped from ROM,like OFFICIAL ROMS.
OEM---->This folder contans all the OEM DRIVERS and OEM software
ROM\XIP\ ---->contain boot.rgu,don't mod or del it!
SYS -------->SYS of WM build
SYSNEW ------>TH SYS OF NEW version of WM building u will proting
temp ----->temp files,and ROM files u cooked are here
TOOLS --------->All tools that ness for cooking
XIPNEW ------>NEW XIP of WM version.there are two styles:XIP.BIN and MSXIPKernel.u can porting them by choose correct method in my bat command
reg&iniflashfiles_tools ------->Tools to edit reg files and initflashfiles.
HOW TO：
1、IF u don't want to Porting new version of wm and u just want to mod ,u can dump OFFICIAL rom.
TO DO：Place official ROM in root of kitchen，run "dump ROM.bat" and follow the instruction.when finished,u will find OEM AND SYS in DUMP\DUMP.Move them to root of the kitchen.and move xip.bin in dump to root of kitchen and rename it to xip_out.bin.Now,u can edit softwares in OEM and build as u like by run"Build ROM.bat"
2、IF u want to cook new version of WM build,just down load new SYS AND XIP file form somewhere like DFT.usually,u may only need these parts:COMM，COMM_0409,WVGA_COMM,WVGA_COMM_0409 and XIP.
UNZIP COMM，COMM_0409,WVGA_COMM,WVGA_COMM_0409 to SYSNEW folder,UNzip MSXIPKernel form XIP to XIPNEW folder then run"Build ROM.bat" and follow the guid.
sorry for my english...
hope u can understand...
-------------------------------------------------
sorry for my mistake..
i forget something important
just creat ROM\XIP\ folder in root of kitchen and put this boot.rgu in it
View attachment boot.rgu.zip
Download:TG01_ROM_KITCHEN.rar
ffboy2009 said:
I hope i can help u learn how to cook rom and makes it more easier!
1.Structure OF THE KITCHEN
ROOT OF THE KITCHEN-------
dump----> This will contan files dumped from ROM,like OFFICIAL ROMS.
OEM---->This folder contans all the OEM DRIVERS and OEM software
ROM\XIP\ ---->contain boot.rgu,don't mod or del it!
SYS -------->SYS of WM build
SYSNEW ------>TH SYS OF NEW version of WM building u will proting
temp ----->temp files,and ROM files u cooked are here
TOOLS --------->All tools that ness for cooking
XIPNEW ------>NEW XIP of WM version.there are two styles:XIP.BIN and MSXIPKernel.u can porting them by choose correct method in my bat command
reg&iniflashfiles_tools ------->Tools to edit reg files and initflashfiles.
HOW TO：
1、IF u don't want to Porting new version of wm and u just want to mod ,u can dump OFFICIAL rom.
TO DO：Place official ROM in root of kitchen，run "dump ROM.bat" and follow the instruction.when finished,u will find OEM AND SYS in DUMP\DUMP.Move them to root of the kitchen.and move xip.bin in dump to root of kitchen and rename it to xip_out.bin.Now,u can edit softwares in OEM and build as u like by run"Build ROM.bat"
2、IF u want to cook new version of WM build,just down load new SYS AND XIP file form somewhere like DFT.usually,u may only need these parts:COMM，COMM_0409,WVGA_COMM,WVGA_COMM_0409 and XIP.
UNZIP COMM，COMM_0409,WVGA_COMM,WVGA_COMM_0409 to SYSNEW folder,UNzip MSXIPKernel form XIP to XIPNEW folder then run"Build ROM.bat" and follow the guid.
sorry for my english...
hope u can understand...
Download:Uploading
Click to expand...
Click to collapse
U are the MAN!
Thank you.
Very nice
Hope I am now able to mod my favourite rom by myself now
Two worlds about how to integrate Sense in your ROMs maybe a good link if you have ?
Thanks
Edgar
I tested your tool and it is great as it is well guided.
but i can not find OEM folder in dump/dump only many folders containing "....dll" names and one folder called "SYS"
Also when editing OEM`s to the rom i get the error "Creating initialflashfiles.dat"
Looks like i am even not able to build a rom with a auto tool
P.S. Wanted to add cabs to your wm6.1 rom using this tool
eddgarms said:
Two worlds about how to integrate Sense in your ROMs maybe a good link if you have ?
Thanks
Edgar
Click to expand...
Click to collapse
Maybe this http://forum.xda-developers.com/showthread.php?t=633795 can help you.
FFboy: "IF u want to cook new version of WM build, just down load new SYS AND XIP file from somewhere like DFT."
What is DFT?
This is a DFT
Hello ffboy..
Can we use your tool to "modify" your sense rom, for exemple?
Thanks!
ps: moreover, i haven't got this folder "ROM\XIP\"...so i've got an error when i build the rom.
I tried to download your tool 3 times, but nothing....!!
What's wrong?
And I dumped the toshiba 6.5 rom, i did what you say in the first post and then i build the rom...
The original toshiba rom was 253mo and the new one is 244mo...but I didn't remove anything!!! Is this just because of the xip directory error i have during the "buildOs" process?
thanks!
iceeyes91 said:
I tested your tool and it is great as it is well guided.
but i can not find OEM folder in dump/dump only many folders containing "....dll" names and one folder called "SYS"
Also when editing OEM`s to the rom i get the error "Creating initialflashfiles.dat"
Looks like i am even not able to build a rom with a auto tool
P.S. Wanted to add cabs to your wm6.1 rom using this tool
Click to expand...
Click to collapse
Some roms that deleted all dsm and rgu files can't be dumped to OEM&SYS style
i can dump it out without do DM2PKG and copy all files in dump folder to SYS and do some mods.run kitchen maybe it works...
u want ro add cabs autoinstall on first boot?
just dump my rom to files and copy all off them into SYS,then creat a .rgu file and place it into a folder in OEM
add these in .rug file:
Code:
[HKEY_LOCAL_MACHINE\Software\TOSHIBA\AutocabInstall]
"cab1"=""
"cab2"=""
"Reboot"=dword:15
Nokser said:
This is a DFT
Click to expand...
Click to collapse
Yep!
That darkforcesteam。。。
pipolas said:
Hello ffboy..
Can we use your tool to "modify" your sense rom, for exemple?
Thanks!
ps: moreover, i haven't got this folder "ROM\XIP\"...so i've got an error when i build the rom.
I tried to download your tool 3 times, but nothing....!!
What's wrong?
And I dumped the toshiba 6.5 rom, i did what you say in the first post and then i build the rom...
The original toshiba rom was 253mo and the new one is 244mo...but I didn't remove anything!!! Is this just because of the xip directory error i have during the "buildOs" process?
thanks!
Click to expand...
Click to collapse
sorry fo my mistake...
download files in first threat
and it will fix erro..
the diff between ori rom and moded rom maybe because EXTRELOC useing a diff way to reloc moudules..i think
ffboy2009 said:
sorry fo my mistake...
download files in first threat
and it will fix erro..
the diff between ori rom and moded rom maybe because EXTRELOC useing a diff way to reloc moudules..i think
Click to expand...
Click to collapse
Thanks ffboy, i'll try!
pipolas said:
Hello ffboy..
Can we use your tool to "modify" your sense rom, for exemple?
Thanks!
ps: moreover, i haven't got this folder "ROM\XIP\"...so i've got an error when i build the rom.
I tried to download your tool 3 times, but nothing....!!
What's wrong?
And I dumped the toshiba 6.5 rom, i did what you say in the first post and then i build the rom...
The original toshiba rom was 253mo and the new one is 244mo...but I didn't remove anything!!! Is this just because of the xip directory error i have during the "buildOs" process?
thanks!
Click to expand...
Click to collapse
Size difference is mostly because of the IMGFS building, which may well be skipping free space at the end (used for ImageUpdate). It shouldn't matter too much.
I'll stick this, and unstick the other kitchen.
ffboy2009 said:
Some roms that deleted all dsm and rgu files can't be dumped to OEM&SYS style
i can dump it out without do DM2PKG and copy all files in dump folder to SYS and do some mods.run kitchen maybe it works...
u want ro add cabs autoinstall on first boot?
just dump my rom to files and copy all off them into SYS,then creat a .rgu file and place it into a folder in OEM
add these in .rug file:
Code:
[HKEY_LOCAL_MACHINE\Software\TOSHIBA\AutocabInstall]
"cab1"=""
"cab2"=""
"Reboot"=dword:15
Click to expand...
Click to collapse
Sorry i do not really get it
I dumped a official 6.5 Rom and there is like u said a OEM and a SYS Folder in dump/dump.
Using DMP2PKG i get an error on my win7 32bit by choosing "select folder"
Dumping your 6.1 rom it seems that in the dump/dump folder the OEM and his sub folders are not created, so all the data is loose.
will try some stuff and see where it gets me
Edit:
error : \.VM\imageinfo.bin not found, getting this with official and your 6.1
iceeyes91 said:
Dumping your 6.1 rom it seems that in the dump/dump folder the OEM and his sub folders are not created, so all the data is loose.
Click to expand...
Click to collapse
When dumping a cooked rom it is unlikley that you will get an OEM folder, i do not know why but the OEM parts can be found in the sys folder and relocated. Only dumping an original rom gives proper file segregation, ie OEM+SYS
Made my own rom now. Changed a official one and put some oem's in OEM folder.
Have some questions though:
How do you add the information to the rom , that it automatically adds a xxx.lnk file in startmenu for each program you have been put to OEM Folder??
Also how do you insert another input keyboard to the rom??
I wanted to add Neo2007 driverpack to my rom but it tells me that the xxx.dll already exists. how do i bypass this??
And how do I upgrade the netcf??
I now this is a lot of questions and maybe they are stupid, but i am totally new to rom-development. Thanks in advance
Thank you for this great tool
iceeyes91 said:
Made my own rom now. Changed a official one and put some oem's in OEM folder.
Have some questions though:
How do you add the information to the rom , that it automatically adds a xxx.lnk file in startmenu for each program you have been put to OEM Folder??
Also how do you insert another input keyboard to the rom??
I wanted to add Neo2007 driverpack to my rom but it tells me that the xxx.dll already exists. how do i bypass this??
And how do I upgrade the netcf??
I now this is a lot of questions and maybe they are stupid, but i am totally new to rom-development. Thanks in advance
Thank you for this great tool
Click to expand...
Click to collapse
Could you explain: if /OEM doent exit after DUMP, do you fill with your new cab (transform in OEM?) and add a registry entry ?
super_sonic said:
Could you explain: if /OEM doent exit after DUMP, do you fill with your new cab (transform in OEM?) and add a registry entry ?
Click to expand...
Click to collapse
I used this application to made my OEM's http://forum.xda-developers.com/showthread.php?t=525302
I just converted and put them into OEM folder.
Btw 1 thing concerning your 6.1 rom ffboy
Dumping it and putting everything to SYS does not work. I can not rebuild the rom , even if I do not add anything in OEM
iceeyes91 said:
Made my own rom now. Changed a official one and put some oem's in OEM folder.
Have some questions though:
How do you add the information to the rom , that it automatically adds a xxx.lnk file in startmenu for each program you have been put to OEM Folder??
Also how do you insert another input keyboard to the rom??
I wanted to add Neo2007 driverpack to my rom but it tells me that the xxx.dll already exists. how do i bypass this??
And how do I upgrade the netcf??
I now this is a lot of questions and maybe they are stupid, but i am totally new to rom-development. Thanks in advance
Thank you for this great tool
Click to expand...
Click to collapse
1.ALL files in SYS and OEM placed default in WINDOWS folder.check initflashfiles.dat in OEM_LANG_0409 and initflashfiles.txt in ur own oem folder.these files can change the place of file.
if u want add FFBOY.LNK to startmenu,add command like this.
Code:
Directory("\Windows\Start Menu"):-File("FFBOY.lnk","\Windows\FFBOY.lnk")
2.input keyboard can be added by download someone posted,u may search ur self.
3.if buildos tells u that XXX.DLL or some tile already exist,check the name and search in SYS or OEM to see if there exist a file in same name.
if exist,delete them except the newest one.
4.NETCF in wm6.5 already version 3.5
iceeyes91 said:
I used this application to made my OEM's http://forum.xda-developers.com/showthread.php?t=525302
I just converted and put them into OEM folder.
Btw 1 thing concerning your 6.1 rom ffboy
Dumping it and putting everything to SYS does not work. I can not rebuild the rom , even if I do not add anything in OEM
Click to expand...
Click to collapse
what buildos tell info to u?
Ok heres my dilema:
I wan't to cook in loads of manila files, but theres a few different versions of each one, and they aren't going into windows.
its better I explain it, heres an example:
Root Folder
\Folder 1
¬FileX
\Folder 2
¬FileX
\Folder 3
¬FileX
How can I do this? is I cant put the same file (FileX) in the files folder of a package as it has the same file name... The only way I can think of is to have a seperate package for each invidual file, and considering theres over 40 files, its going to take a long time!
Are there anymore efficient ways to do this? Thanks
SOLVED: AIRXTREME HAS MADE A UTILITY FOR CHEFS TO FIX THIS VERY PROBLEM:
[GET IT HERE]
THANKS AIRXTREME!!!
[★] said:
Ok heres my dilema:
I wan't to cook in loads of manila files, but theres a few different versions of each one, and they aren't going into windows.
its better I explain it, heres an example:
Root Folder
\Folder 1
¬FileX
\Folder 2
¬FileX
\Folder 3
¬FileX
How can I do this? is I cant put the same file (FileX) in the files folder of a package as it has the same file name... The only way I can think of is to have a seperate package for each invidual file, and considering theres over 40 files, its going to take a long time!
Are there anymore efficient ways to do this? Thanks
Click to expand...
Click to collapse
If all these files go into "\Windows", there will be only one in the end ... not 40. Meaning the last "FileX" your kitchen finds will have overwritten all the others ...
You can't end up with all these files, without doing a little bit of legwork.
When you cook a ROM, all the files end up in \Windows, and are then moved around as required.
So, you could either cook all the files in with different names (so they don't overwrite) and then move them using a provxml or initflashfiles.dat, or you could cab up all the files, and run the cab after first boot.
The easiest way is to use a cab or to put everything in a zip file and use an 'inzipall' mortscript to unzip the folders wherever you want during customization.
Diegis0n said:
If all these files go into "\Windows", there will be only one in the end ... not 40. Meaning the last "FileX" your kitchen finds will have overwritten all the others ...
Click to expand...
Click to collapse
Yeah thats what I thought , althought I didnt know they went into windows first, thanks.
l3v5y said:
You can't end up with all these files, without doing a little bit of legwork.
When you cook a ROM, all the files end up in \Windows, and are then moved around as required.
So, you could either cook all the files in with different names (so they don't overwrite) and then move them using a provxml or initflashfiles.dat, or you could cab up all the files, and run the cab after first boot.
Click to expand...
Click to collapse
Hmm the cab sounds like a good aproach, although still I wouldn't be able to have more than one manila file with the same name in the cab.
Farmer Ted said:
The easiest way is to use a cab or to put everything in a zip file and use an 'inzipall' mortscript to unzip the folders wherever you want during customization.
Click to expand...
Click to collapse
hmm thats a good idea, could you point me to that script please
[★] said:
Yeah thats what I thought , althought I didnt know they went into windows first, thanks.
Hmm the cab sounds like a good aproach, although still I wouldn't be able to have more than one manila file with the same name in the cab.
Click to expand...
Click to collapse
Cab files do allow you to specify the paths, so they do allow you to have files with the same name. WinCE CAB Manager is a good choice to create cabs. You can then use RunCC / Autorun/ XDA_UC to install it during the first boot.
[★] said:
hmm thats a good idea, could you point me to that script please
Click to expand...
Click to collapse
Just take a look at this package; it has a zip file, a mortscript, and the add2config that you need. Here's a mortscript package that you can use.
You could also rename the files for example "1_FileX", "2_FileX" and have initflashfiles.dat rename it to the filename you want it to be, like so:
Directory("\Folder_1"):-File("FileX","\Windows\1_FileX")
Directory("\Folder_2"):-File("FileX","\Windows\2_FileX")
Click to expand...
Click to collapse
But that would really clog up your ROM, so the mortscript way is better.
ock said:
Cab files do allow you to specify the paths, so they do allow you to have files with the same name. WinCE CAB Manager is a good choice to create cabs. You can then use RunCC / Autorun/ XDA_UC to install it during the first boot.
Click to expand...
Click to collapse
Yes but putting the files in will overwrite eachother, as they have to have the same file name
Farmer Ted said:
Just take a look at this package; it has a zip file, a mortscript, and the add2config that you need. Here's a mortscript package that you can use.
Click to expand...
Click to collapse
Thanks I dont understand what the mortscript for is (the one from 4shared) but Im using the add2config package, I think I get it I will let you know when its finished cooking. Although I am having a problem where none of my add2config packages are working so it might be useless
seeM_ZA said:
You could also rename the files for example "1_FileX", "2_FileX" and have initflashfiles.dat rename it to the filename you want it to be, like so:
But that would really clog up your ROM, so the mortscript way is better.
Click to expand...
Click to collapse
Yeah but the files have to keep the same name
You need mortscript support cooked into your rom one way or another if you're going to use zip files; that's what the 4shared package is for.
l3v5y said:
So, you could either cook all the files in with different names (so they don't overwrite) and then move them using a provxml or initflashfiles.dat
Click to expand...
Click to collapse
+1 for this...
ai6908 said:
+1 for this...
Click to expand...
Click to collapse
That's ok if you're talking a couple of files, but if you're talking a few dozen (or more), then putting together all the initflashes scripts will get tedious.
Farmer Ted said:
That's ok if you're talking a couple of files, but if you're talking a few dozen (or more), then putting together all the initflashes scripts will get tedious.
Click to expand...
Click to collapse
Did you get my message?
and yeah, it seems your mortscript may be easier If I can get add2config to work lol
SOLVED: AIRXTREME HAS MADE A UTILITY FOR CHEFS TO FIX THIS VERY PROBLEM:
[GET IT HERE]
THANKS AIRXTREME!!!
I've been reading up on cooking ROM's and with the help of leeston i managed to create a basic ROM earlier in the week. After searching for guides / tutorials on this stuff im really not that much the wiser, i cant seem to find anything that explains it well enough, there always missing details. The actual cooking process seems fairly straightforward but its those extra bits im missing ie
how do i add my own packages - am i right in just copying them to the SYS folder or is there more to it ?
how do i edit the registry - I know how to edit the registry once the ROM is loaded onto my phone but how do i do it from the ROM without the phone ?
how do i add things to the start menu - When i add packages to the SYS folder and load the ROM into my phone the shortcuts dont seem to be in my start menu
how do i add sense - i've loaded the packages but it never starts and theres no sense option in today settings
im new to this so as you'd imagine the questions i have are endless ...
Im sure most of this info is on XDA already somewhere but i just cant find it, maybe im searching for the wrong term or something.
Any help from the chef's would be great, perhaps you could provide links to tutorials / info you've used when learning to cook. Im sure this stuff would be useful to everyone and may even encourage more to have a go at cooking .
drkdeath5000 said:
1.how do i add my own packages - am i right in just copying them to the SYS folder or is there more to it ?
2.how do i edit the registry - I know how to edit the registry once the ROM is loaded onto my phone but how do i do it from the ROM without the phone ?
3.how do i add things to the start menu - When i add packages to the SYS folder and load the ROM into my phone the shortcuts dont seem to be in my start menu
4.how do i add sense - i've loaded the packages but it never starts and theres no sense option in today settings
.
Click to expand...
Click to collapse
I am still new to cooking but I'll tell you what i believe to be correct.
1.Yes. To add a package to a rom you put the package into the SYS folder.
However be aware that the kitchen used for the TG01 cannot handle EXT (visual) packages, only OEM (old) packages can be used. Use Totalfires package converter to convert between the 2 types.
The above info is not strictly true but is what you need to know when cooking for the TG and i don't have the time or knowledge to write a complete tutorial.
2. Editing the registry is all to do with .RGU files, you can create a package with a new one in or edit the existing ones within the packages in the SYS folder. You can edit them with notepad but i suggest using Notepad2.
Once you open an .RGU file you should recognize the reg key text in the file and edit it accordingly. As far as i am aware the file MUST have REGEDIT4 in the first line and an empty line at the bottom in order to work. Another way is to edit the regkey on your device then export the regkey using resco or something similar, then rename the resulting file from .reg to .rgu then open it in note pad and copy and paste it into another packages .rgu file, or create a custom package for that .rgu file.
The registry can also be modified using cab files during autorun, but this can be a little messy as the cab can be uninstalled by the end user causing problems.
3. To do this you need to edit the initflashs.txt file within the . This can be done manually or with one of the many package tools available on this site. The one i use is below, it does the hardwork for you, you click a few options and it edits the required files as needed.
4. Sense is a funny one. You should just need to add all the required packages to the SYS folder and away it goes. Unfortunately this is rarely the case. It should just a case of making sure all the sense packages are there, including its many dependencies. Sense is one of my weaker areas so maybe some one else has better advice.
Hope this is useful.
do you have a loooong far way, but read the forumposts an try, try and shortPin and try. that was my way, or is my way. i have don´t helping, all found with google and in xda forum.
unfortunately, my English knowledge is terrible. otherwise I would write more.
best to dump a officiels ROM or miROM5 , then you have an example
related post here
http://forum.xda-developers.com/showthread.php?t=750261
PC Software Reg-editor
http://ceregeditor.mdsoft.pl/index.php?id=1〈=en
CAB to OEM
http://forum.xda-developers.com/showpost.php?p=3942000&postcount=1
EXT to OEM
http://www.ppckitchen.org/forums/re...e666.ppckitchen.org/Tools/EXT%20to%20PPCk.exe
All folder to cooking need a .dsm (and/or) .rgu file
RGU name Generator (such as Reg- file) , dsm become automatically
http://www.famkruithof.net/uuid/uuidgen (Fetch UUIDs of another type to Version 4)
do you have a loooong far way!
... Or make a good donation to nokser or ffboy, they teach you
Hi my friend, I have a problem to cook a ROM with cab which required a reboot or witch have a information message ( SWYPE or GPSMOdDriver for example)
Do you know a solution for this please?
Thanks in advance.
Thanks for the info leeston and miro ;-). I havent had time to try it yet but will be over weekend and im almost sure now i know where to find the registry files ill be able to cook something decent up since that was my main problem. Thanks again for the help.
EVEALEX62 said:
Hi my friend, I have a problem to cook a ROM with cab which required a reboot or witch have a information message ( SWYPE or GPSMOdDriver for example)
Do you know a solution for this please?
Thanks in advance.
Click to expand...
Click to collapse
I may be wrong but when the cab files are first installed doesnt it automatically reboot ? If not you can always do a manual reboot ;-).
I've tried everything to get sense working but im just having no luck ... copied the packages to the sys folder, flashes fine, boots fine but no sense and now theres no setting shortcut in the start menu ?
Could i ask for the exact procedure for installing sense please ? Im getting my packages from here but replacing the 2017 home with 2016. Could i perhaps be missing something ?
Thanks again
drkdeath5000 said:
I may be wrong but when the cab files are first installed doesnt it automatically reboot ? If not you can always do a manual reboot ;-).
Click to expand...
Click to collapse
I have try to delete the line "Reboot" after autocabinstall but nothing change the phone always reboot ... I think the only thing is to do OEM package...
I have test with many cabs but nothing works same as you with Sense ...
Have you found solutions ?
EVEALEX62 said:
Hi my friend, I have a problem to cook a ROM with cab which required a reboot or witch have a information message ( SWYPE or GPSMOdDriver for example)
Do you know a solution for this please?
Thanks in advance.
Click to expand...
Click to collapse
The solutoin is to use autorun instead of cabinstl, you can then write a custom script to handle the input required by the cab.
However this is above my head, and i couldn't get autorun to work. FFBOY knows how but i doubt you will get his help as he doesn't seem to check any threads other than his own rom threads, and if he does his responces are few and far between.
drkdeath5000 said:
I've tried everything to get sense working but im just having no luck ... copied the packages to the sys folder, flashes fine, boots fine but no sense and now theres no setting shortcut in the start menu ?
Could i ask for the exact procedure for installing sense please ? Im getting my packages from here but replacing the 2017 home with 2016. Could i perhaps be missing something ?
Thanks again
Click to expand...
Click to collapse
Those are the packages i used and they work so it's not the packages, but i cheated and dumped a sense rom then modified it. I don't have time to try and work out how to do it properly unfortunatley.
leeston2379 said:
Those are the packages i used and they work so it's not the packages, but i cheated and dumped a sense rom then modified it. I don't have time to try and work out how to do it properly unfortunatley.
Click to expand...
Click to collapse
Well atleast i know the packages are fine, i was starting to wonder if that was the problem . Theres some satisfaction in doing it yourself but like miro said i think its just too much for me, ill give it another go later in the week and if that fails ill just dump a sense rom like you did ... if there was just a tutorial on installing sense packages etc id be fine, with sense being so popular you'd think there to be loads of tuts.
Sorry for being dumb once again.
I know how to create an XML and convert reg files to PROVXML etc but :
I flashed my cooked rom and did snapshot with kheb made all my changes and got a difference .reg file.
I converted that to PROVXML cause i believe its the best way of doing it.
What I dont know is what to do with it and where to put it in order to flash it.
Ive put it under custom settings\files but iot needs to be named something specifically according to 0Kitchen . Also i have an xml file that has my exchange settings in that which i want to cook in as well but dont know how.
I do use XDA uc but id prefer to let it be done with runcc or something?
Please advise whats better and whats the difference between the differentx PROVXML file naming.
Thanx
I would preffer using reg instead Provxml because they take a lot of time for 1st boot....anyway you need to name them mxip_xxxx.provxml if im not wrong.
af974 said:
I would preffer using reg instead Provxml because they take a lot of time for 1st boot....anyway you need to name them mxip_xxxx.provxml if im not wrong.
Click to expand...
Click to collapse
Can i renam the exchange.xml to mxip_exchange.provxml as well. does a xml and provxml contain the same information/layout?
Uhmm...it seems that should work, give a look here http://ip208-100-42-21.static.xda-developers.com/showthread.php?p=6995989.
Grumps said:
Can i renam the exchange.xml to mxip_exchange.provxml as well. does a xml and provxml contain the same information/layout?
Click to expand...
Click to collapse
af974 said:
Uhmm...it seems that should work, give a look here http://ip208-100-42-21.static.xda-developers.com/showthread.php?p=6995989.
Click to expand...
Click to collapse
Leme just try quickly we do flash like 30 times a day in any case hey. Will revdert just now
Thanx for your help
There's various file names, mxip, mxipinit and mxipupdate. In my experience I've never needed to add anything to a .dsm file, as long as the extension is .provxml they execute ok.
What I do though, is put my post-boot provxml's into the very last folder that my kitchen picks up so it's named ZZZ_postboot_provxml or something similar and I also name the file to mxipupdate_zzzPostBoot.provxml but I'm not sure if this helps. I do this because:
If you use total commander and search for *.provxml files in your windows folder you might find that none of them have the original name you gave in your packages, but if you step through the files you find there, you can see the execution order.
Hope this helps a bit.
arealityfarbetween said:
There's various file names, mxip, mxipinit and mxipupdate. In my experience I've never needed to add anything to a .dsm file, as long as the extension is .provxml they execute ok.
What I do though, is put my post-boot provxml's into the very last folder that my kitchen picks up so it's named ZZZ_postboot_provxml or something similar and I also name the file to mxipupdate_zzzPostBoot.provxml but I'm not sure if this helps. I do this because:
If you use total commander and search for *.provxml files in your windows folder you might find that none of them have the original name you gave in your packages, but if you step through the files you find there, you can see the execution order.
Hope this helps a bit.
Click to expand...
Click to collapse
ok so postboot is also one of the names like mxipinit and mxipupdate. Why are there so many different ones and which ones are executed in what order?
Grumps said:
ok so postboot is also one of the names like mxipinit and mxipupdate. Why are there so many different ones and which ones are executed in what order?
Click to expand...
Click to collapse
I think the order is all to do with the way the kitchen picks them up. e.g. I use OSKitchen and it seems SYS, then OEM, then EXT packages are picked up, alphabetically-so my provxml's get the same order, which is why I put them in a package of their own with the ZZZ_postboot name. It just makes it the last one to be picked up of the EXT packages-ensuring everything is in place when the script runs
arealityfarbetween said:
I think the order is all to do with the way the kitchen picks them up. e.g. I use OSKitchen and it seems SYS, then OEM, then EXT packages are picked up, alphabetically-so my provxml's get the same order, which is why I put them in a package of their own with the ZZZ_postboot name. It just makes it the last one to be picked up of the EXT packages-ensuring everything is in place when the script runs
Click to expand...
Click to collapse
Ok lemme try
Im trying to change my timezone from dublin -8 to gmt +2. n start kheb take snapshot make the change get i difference .reg file. convert it to xml and the paste it in files folder of lastflash folder?? ill try and see what happens