Database Users

[DEV] ROM Extractor for Bepe's Platformrebuilder

Hello People
I have coded a solution for extracting roms automatically and make it ready for Bepe's Kitchen.
How to: V2
- Extract the KitchenV2.rar
- Put the extractRom.exe and the Tools2 Folder wherever you like (but it must me together in a folder)
IMPORTANT: DONT RENAME THE Tools2 Folder
- Put a nbh in the Tools2\NBH or a os.nb in the \Tools2\OS
- start extractRom.exe and chose your file
then Wait. It takes a few minutes and your kitchen is ready.
Be sure that the rom is not protected else it doesnt works
WORKS ONLY WITH THE NEWER GENERATION OF PHONES!!
TESTED WITH: NIKI, DIAMOND, BLACKSTONE, BREEZE
http://rapidshare.com/files/192469913/KITCHENV2.rar

Failure with build ROM
Hi Blackdragon_860,
many thanks for your effort - but unfortunately I must say that I have yet to find a
working dumptool for bepe's kitchen that fits the average user.
Using your toolset (put in the root of my drive) seems to create the structure just
fine but whenever I use build_rom.bat (from your kitchen or from bepes) it just gives
me an errormessage from platformrebuilder.exe:
Collecting standard packages and initializing hives...
ERROR! (errorlevel: -1073740777)
please press any key ...
I tried with the new HTC 1.93 GER ROM btw.
Any thoughts on that ?
/mst
P.S. why does yor tool need another location than platformrebuilder that makes it
even more difficult?

Thx for this, great work! one issue: I have made my Diamond roms with Surface Kitchen so far. I give this a go and I take one of my own roms and dump it and rebuilt it..I made no changes every thing went fine no errors and the new OS.nbh was created. Then I flash it but it dont boot, just the splash screen came up? the txt which allways come up normally where you seen the radio and protocol version didnt shown at all..How come?? What did I miss??

OK now I test a stock .nbh file and now the rom boot, but my finnish xt9 was gone I got just the ordinary keyboard in the rom, and the phone canvas is missing too in the rom, random acsess is gone
I used the 2.03 nbh

i use it for every "OFFICIAL" & "ORIGINAL" Rom
and it works greate..
i am working on a update,but for now it works.
greets

released V2

works awesome! THX

Great job! Perfect THX very much

thx for yours feedbacks..

I met an error like this:
Error: 0x80000009
'boot.rgu' does not exist in th specified paths!
Error! (errorlevel:1)
does this means the rom protected?

yes, when the rom is not protect or original it works 100%

Blackdragon_860 said:
Hello People
I have coded a solution for extracting roms automatically and make it ready for Bepe's Kitchen.
How to: V2
- Extract the KitchenV2.rar
- Put the extractRom.exe and the Tools2 Folder wherever you like (but it must me together in a folder)
IMPORTANT: DONT RENAME THE Tools2 Folder
- Put a nbh in the Tools2\NBH or a os.nb in the \Tools2\OS
- start extractRom.exe and chose your file
then Wait. It takes a few minutes and your kitchen is ready.
Be sure that the rom is not protected else it doesnt works
WORKS ONLY WITH THE NEWER GENERATION OF PHONES!!
TESTED WITH: NIKI, DIAMOND, BLACKSTONE, BREEZE
http://rapidshare.com/files/192469913/KITCHENV2.rar
Click to expand...
Click to collapse
dude i tried to extract wm6.5 rom with this. it did not extract ROM folder so i had to manually copy it. after that when i run the rom builder i get an error that boot.rgu is not placed in right paths. i think its supposed to be in XIP and it is there only. then why this problem?

[ASK] How to port WM6.5 into my M490 WM6.1(T-Omnia)

Hi. Everyone.
At first, I'd like to appreciate all you guys. I've learned so many things from you.
Thank you so much.
This time I wanna ask you for giving me hands.(again~) And I hope someone would help me ^^
I'm trying to port WM6.5(0409) into my SCH-M490(0412, this is the Korean domestic version of the Samsung Omnia phone).
As far as I've searched for the way how to do it,
I found that I have to replace XIP, SYS and MUI with released WM6.5 ROM.
But I'm still confused what exactly I should do.
I'll describe here the process that I will go.
plz correct wrong one or add insufficient information.
# Preparation
1. Download SCH-M490's WM6.1 PDA.BIN Rom file and i900's WM6.5 ROM (PDA.BIN of course)
2. Download all tools I need (osbntools.exe, xipport.exe, dump.exe and so on.)
# XIP Porting (I think I already succeeded this)
1. Dump original WM6.1 ROM and extract XIP.BIN.
2. Dump i900's WM6.5 ROM and extract XIP.BIN, too.
3. With xipport.exe, dump them both and make packages.
4. Replace original XIP.BIN's MSXIPKernel package with new XIP.BIN's one.
(I know I have to do this for both FILES and MODULES folders)
5. Remove some module's which are known as unnecessary. (If I meet the alert saying "not enough space" when realloc. such as hd.dll, osaxst0.dll and so on)
6. Realloc P, write maps, check collisons, correct them (if any), build xip_out.bin.
7. insert new "xip_out.bin" into OS.NB by using osnbtool.exe.
# SYS replacement
1. Remove all files from original WM6.1 dump's sys folder, but .ROM and .VM folder.
2. Copy all files in the sys folder of WM6.5 ROM (except .ROM and .VM folder) to original dump's sys folder.
# MUI Translation
1. Find all files that have string "0412" for their file names (mostly, they will be in the OEM dump folder I guess).
2. Rename them (0412 -> 0409).
3. Open every mui file,which has .mui as their file extention, with reshacker.exe.
4. Translate resources as many as I can and Recompile them.
5. Find all *.rgu files in the OEM dump folder.
6. Open them all and find string "0412" and change them to "0409".
# Flashing
1. Build a rom.
2. Download the Rom to my M490 by using UMDL_GrandPrix_V1.8.1
So.. I wanna change
Language : 0412 -> 0409
OS : WM6.1 -> WM6.5
Are there something wrong? Are there something I missed? (I'm not talking about my grammar. lol)

I wish if someone would answer you!!!
I think in the SYS folder, you can replace the .ROM folder. But, you cannot replace the WinCENLS_WWE folder, I think.
Also, inside the SYS/Shell folder, you shouldn't replace shell32 and shellres.
That's what I've read. I'm pissed that I can't get this working either, though!!!

are you using that phone in the US?
If so which provider are you using and where can i buy one!?

ace10134 said:
I wish if someone would answer you!!!
I think in the SYS folder, you can replace the .ROM folder. But, you cannot replace the WinCENLS_WWE folder, I think.
Also, inside the SYS/Shell folder, you shouldn't replace shell32 and shellres.
That's what I've read. I'm pissed that I can't get this working either, though!!!
Click to expand...
Click to collapse
You are correct about a few things here, but not everything.
You are right about the WINCENLS. This is usually device-specifc and should not be replaced when cooking. The .ROM can be replaced but not the .VM.
Now, as far as I understand rom cooking, the shell is changed from build to build. You may end up with weird, unstable results if you don't match it with the rom you are trying to cook.
@samuel281,
I think you pretty much nailed everything down. What exactly isn't working for you? It isn't flashing, booting, doesn't create the rom (error in the build process)?
One other thing, as far as the SYS, all you need to replace are the Files and Modules. You just need to make sure that you are using what you are supposed to (either Files or Modules).

[GUIDE] Tg01 AUTO COOK&porting ROM kitchen with guid!fix bug!

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?

Learning to cook a rom

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.

Upgrading from 6.1 to 6.5

I have cooked a few roms for my diamond using the HTC WM6.1 1.93 release as a base. But i'd like to try Titanium and I gather i'd need WM6.5.
I have downloaded OEM xip kernel, SYS_23563_192DPI_0409, SYS_23563_Common and SYS_23563_XIP.
Please could someone give me some idea of what to do with these folders.... I use EVK 12.5.8

rikpotts said:
I have cooked a few roms for my diamond using the HTC WM6.1 1.93 release as a base. But i'd like to try Titanium and I gather i'd need WM6.5.
I have downloaded OEM xip kernel, SYS_23563_192DPI_0409, SYS_23563_Common and SYS_23563_XIP.
Please could someone give me some idea of what to do with these folders.... I use EVK 12.5.8
Click to expand...
Click to collapse
first thing is port the SYS (common and DPI 192),unpack this two archives then useing the Packer.jar you will create a new SYS for youre build,next you will need some OEMDrivers(the touch.dll for WM 6.5) and a OEMXIPKernel (the nk.exe for WM 6.5) and last but not least the MSXIPKernel,in ROM/Shared (just create a new folder and copy the content of SYS_23563_XIP.

Thankyou so much for your reply.
I have just built my first wm6.5 rom and will attempt to flash in a minute.
The only thing i'm left slightly confused about is a few bits in the OEM folder.
OEM/DIAMOND/COMMON/OEMVERSION/mxipupdate_OEMVERSION_100.provxml
It reads "ROMVersion" value="1.93.401.2"" Surely I should have a second file for wm6.5?
Also in ROM/DIAMOND there were a load of files in the OEMXIPKernel I downloaded that wanted to overwrite some existing files.... namely info.txt, ROMHdr.bin, xip.bin, os.nb.payload.
I didn't let them overwrite but do I need to keep both sets of files?

rikpotts said:
Thankyou so much for your reply.
I have just built my first wm6.5 rom and will attempt to flash in a minute.
The only thing i'm left slightly confused about is a few bits in the OEM folder.
OEM/DIAMOND/COMMON/OEMVERSION/mxipupdate_OEMVERSION_100.provxml
It reads "ROMVersion" value="1.93.401.2"" Surely I should have a second file for wm6.5?
Also in ROM/DIAMOND there were a load of files in the OEMXIPKernel I downloaded that wanted to overwrite some existing files.... namely info.txt, ROMHdr.bin, xip.bin, os.nb.payload.
I didn't let them overwrite but do I need to keep both sets of files?
Click to expand...
Click to collapse
the part with the rom version, you can modified as you wish ,yo can put you're name in there(PS: dont modify the phones ID or things like that)...then,you don't need the info.txt files anymore,delete them(PS: don't delete them if you are trying to build a new XIP.bin).If it says to overwrite.overwrite them with the new ones.Because the xip.bin,os.nb.payload,and the ROMHdr.bin are the old build files.so you need to replace them with the new ones,but you need to make a backup,just to be shure...or if you dont have the xip.bin and also the os.nb.payload for the new build you have to create the xip.bin with XIPport.exe and then we use again the XIPport app to inplant the new created xip.bin in the OS.nb.payload...that its a little tricky even i can do it properly