Related
Any brave soul try using mkrom in conjucntion with the 2003 ROM? I think I might give it a shot here in a bit but wanted to know if anybody had tried it yet...
I've managed to build a 2003 ROM. It's extremely tricky though. I'm working on customizing a ROM similar to the XDA Developers SER - as soon as I get some free time
I'd like to acknowledge all the help given to me by Developer Itsme in this endeavor.
Let me know any suggestions you may have for the new ROM.
sheran_g,
i didn't know u could use mkrom with 2003 rom image. can u please post how u did it? i created a special version based on SE 1.1 rom but would like to put the same programs into the new rom. any help is appreciated.
thanks
alex
sheran_g said:
I've managed to build a 2003 ROM. It's extremely tricky though. I'm working on customizing a ROM similar to the XDA Developers SER - as soon as I get some free time
I'd like to acknowledge all the help given to me by Developer Itsme in this endeavor.
Let me know any suggestions you may have for the new ROM.
Click to expand...
Click to collapse
What's tricky about it...?
The modified registry file you make does not get picked up at the device startup. You need to manually inject the memory address of the modified registry file into the ROM in order for it to get picked up.
my latest romtools can be found at romtools
now it calls dumprom to find and fix the filedata offsets.
I think they should now build 2003 roms.
sheran_g,
can u post the steps that u take to buid it? i'm trying right now and its not working. i'm having little problems. can u post ur default.reg and initobj.txt? any other help is apreciated.
thanks
alex
Ok. Here they are in a nutshell:
Get the latest romtools.
Make the following dirs: romfiles, cfg, tmp, out, files, files1, files2
Split the ROM into Bootloader, bootimage, OS image, xipchain into the 'cfg' dir.
Dump the files in the OS image into a 'romfiles' dir.
Get the default registry file, initobj & initdb files into your 'cfg' dir.
Make changes to your default.reg and initobj.txt
Place any files you want loaded in the ROM into the 'files' dir.
Run 'mkrom.sh'
You should then have your new ROM. I'm sorry if it's extremely brief; you'll have to make do with this and the README file in the romtools archive file for now. You'll find my default.reg and initobj.txt files on my site: www.zensay.com/qtek/mkrom
sheran_g,
Have you created a decent working custom WM2003 ROM?
If so what Apps have you added?
How much ROM space does it use?
I've not added any apps to my ROM. I have only added a carrier logo file and made some changes to the registry. So I cannot comment on ROM space yet. The ROM works fine.
sheran_g,
what command did u use to extract rom files? did u do it under windows or unix?
I'm having problems trying to dump the rom image. I don't know if its too much to ask, but can u zip ur directory and post it somewhere so i can download it? or if u can post commands that u ran to dump the 2003 rom?
thanks
alex
Hi,
could you include "O2 home zune" to the 2003 image, like in the 2002 3.19 GER. Its for Germany interested only!
AR :?:
home zone depends on specific 3.19 rilgsm features. which are not in 4.*
okay, used dumprom -4 -d files -q nk.nbf and extracted all files. Got could not find pointer for ofs 00000000 ERROR but all the files seem to be there. Trying to figure this out. Saw the above abreviated directions but am fumbling around. Anyone have concise directions?
Val
Anyone? Just give me a good hint then please.
Hi all!
When i overwrite the rilgsm.dll file in the t-mobile 4.0.10 image with the rilgsm.dll from the O2 GER 3.19 image, i could use the "O2 home zone" option with the hz.exe in Starup directory? rilgsm.dll from german image hes 'at+creg=2' string in it. probably the RIL_GetCellTowerInfo call is now implemented. When it can work, how could i write the german rilgsm.dll to the image? I haven't linux, could somebody cook the image for me?
here is the germen rilgsm.dll and the hz.exe for the "home zone" funktion! http://www.nokiaprog.de/XDA/home_zone.zip
THX
PS: Sorry, my english! ;-)
AR
the homezone enabled rilgsm.dll depends on other dll's and exe's.
probably ril.dll, stk.exe, cell*.dll and maybe more, I have not tried
replacing all.
you don't need to build a new rom in order to experiment with this, you
can just copy the desired files to \windows, to override the rom versions.
And I don't think it works with the RIL_GetCellTowerInfo call,
but adds some notification events.
to change the CREG setting you need to call RIL_DevSpecific with parameter 25 ( to turn it on ) or 26 ( to turn it off )
even though that does not seem to be how hz.exe does it.
Hi,
I opened the image file in the Hex editor and renamed the file there rilgsm.dll. Then I flashed the image, which was phone probably deactivated, because rilgsm.dll was missing. Then I copied over ActiveSync the German rilgsm.dll into the Windows directory, XDA reset and he not accept the file. I assume because the file was not in the EPROM memory! Therefore I wanted to have rilgsm.dll first times in the image!
AR
XDA developer Itsme said:
my latest romtools can be found at romtools
now it calls dumprom to find and fix the filedata offsets.
I think they should now build 2003 roms.
Click to expand...
Click to collapse
Is there any other way i can access this site or I can download this files, the sites are block here in my country, Please Help
Ronnie
Can anybody please help me to build a rom? specially to the XDA-developers, thanks in a million...in advance.
My question is:
1. Do i need a base rom(no program included) on the cfg/(rom.nb1)? is it necessary ?
2. what is the maximum files i can put in the files/ directory? that will be splited by mkrom, i know it is depending on the version since 3.17 the maximum for all files is 5 M. how about other version. 4.01,4.05, 4.10 and 4.16
3. when i run the bash setup.sh nk.nb1(4.05), using parameter for 4.05 i get a message "!!! your rom is not known to me: md5:fb9e70c5786f08e4db6db7c184c59704" is this normal or it is not define on the splitrom.pl ?
4. what kind of editor did you use for building a BMP file with 16 bit, I tried to use adobe photoshop 6.0, but i can not seem to save it as 151 k, the option is only 24 bit and 8 bit, if you can give me a site where i can download it , i will really apreciate it.
Thanks for the Help..
More power to the XDA team
and
Welcome TMO 4.16!!! (which i think no diff with 4.10)
1. yes you do need some kind of rom to start with
2. you can check using
Code:
perl splitrom.pl yourrom.nb1 -ob <your bmp offset> | perl calcgaps.pl 0x3ffff
and add the sizes of the holes.
you have to figure out where the bootsplash is for your rom. ( for new roms this is most likely 0x81ec0000 )
3) there is a list of 27 roms I know about in splitrom, if I never saw your rom, the signature will also not be there.
btw, what rom do you have?
4) I think we used photoshop for that. ( Peter Poelman knows more about that )
thanks for the reply XDA developer Itsme,
but how can i build a baserom with the rom i have, I have a ROM 4.05 which i created in jeff's kitchen? or any site where i can download the base rom 4.05?
I have a ROM 4.05, 4.10 which i get from jeff's kitchen and also the original 4.10 TMO. regarding the signature of the ROM, i read your splitrom.pl and i found out you 27 list of roms, but i didn't find that signature "md5:fb9e70c5786f08e4db6db7c184c59704" is it because my ROM is not base ROM?
my param is ;
wincever=4
start1=21740000
size1=0040000
start2=003c0000
startbmp=81ec0000
startop=81b00000
I'll still try to use the photoshop, maybe i miss something there.
Please correct me if i done something wrong with my commands.
I have Perl 5.8 and cygwin, installed in windows 2003
then make the path for perl/bin and cygwin/bin
then i copy all the things i need to build a rom in one directory including nk.nbf(with jeff's 4.05) and mkrom tools(which i got from the demokitchen)
i run "perl setup.sh nk.nbf" to extract the bootimage.bmp and rom.nb1 to cfg/ directory
then i dump "dumprom -4 -d files -q nk.nbf" to extract all files in files directory
then i convert "perl fdf2reg.pl files/default.fdf cfg/default.reg"
"tr -d "\0" <files/initobj.dat >cfg/initobj.txt"
"cp files/initdb.ini cfg/initdb.ini"
then in files/ directory i delete all the windows files i leave only the program with the dll i wanted to add in the rom like total commander, file commander.. etc...
(I compare it with the original files of WM2003)
then i run "bash mkrom.sh out/out.nbf"
but i got an OVERLAP message on the screen
and also the same message like i told you before "Your rom is not know to me"
Please Help me with this because i want to build my own rom according to the program i need.. and many thanks.
split rom does not recognize romkitchen roms, since they vary too much.
you should use an original rom, not one from the romkitchen.
the overlap means that somehow the params file was not correct.
or maybe you just tried to add too much files.
XDA developer Itsme said:
split rom does not recognize romkitchen roms, since they vary too much.
you should use an original rom, not one from the romkitchen.
the overlap means that somehow the params file was not correct.
or maybe you just tried to add too much files.
Click to expand...
Click to collapse
Thanks Itsme, thats why splti rrom can not recognize the ROM I have, I'll try to search for the base ROM in the forum, or can you give me a site where i can download the baseROM, I think that's why I am having a OVERLAP because there is a added program on my ROM, XDA-Developers File1 and File2 is duplicated.
It answer my question regarding the ROM i have, thanks a lot man you really a good help.
Now my only problem is to find all the base rom so i can start cooking some ROM.
FIRST OF ALL I'M NOT RESPONSABLE OF ANY KIND OF DAMAGE OCCURRED DURING THIS PROCEDURE.
DO IT AT YOUR OWN RISK!
Ok, go on now
This guide assumes that you have already dumped your original ROM.
For how to dump your ROM, follow [email protected]'s wiki until obtain imgfs_raw_data.bin
What we need:
Official Pharos WWE ROM
tadzio tool (by tadzio)
XIPPORT tool (by bepe)
bPatch (by suracha)
HTC rom tool (by Dark Simpson) with pharos settings added by me
ROM update utility
I suggest you to create a folder for each tool (eg. C:\tadzio C:\XIPPORT C:\HTCRomTool C:\RomUpdate)
and unzip the tools in the respective folders. bPatch.exe is inside tadzio tool.
Download the official rom, right clic on "RUU_Pharos_HTC_WWE-ME_1.11.456.1_4.1.13.59_03.15.90_BLUE_Ship.exe", select "Open with WinRar" and extract RUU_Signed.nbh in "C:\tadzio"
Open a command prompt, go in "C:\tadzio" and type this command:
Code:
C:\tadzio>nbhextract ruu_signed.nbh
this tool extract the content of the .nbh file, if its all ok you should have these files now:
Code:
00_GSM.nb
01_IPL.nb
02_SPL.nb
03_MainSplash.bmp
03_MainSplash.nb
04_OS.nb
Copy 02_SPL.nb and 03_MainSplash.nb to C:\HTCRomTool and 04_OS.nb to C:\XIPPORT
ok, now we have official SPL and MainSplash ready to use but we need the OS too
To obtain exactly the original OS we need to modify some registry keys inside "boot.hv" according to our language.
This file is located in the XIP section, so we should extract the xip files from 04_OS.nb, modify boot.hv and re-inject the xip in the os.
Don't worry, we have another solution because we already have the original xip obtained from dump process ([email protected]'s wiki)
The XIP section is Part01.raw
Copy Part01.raw to C:\XIPPORT and rename it to "xip_out.bin"
Run xipport.exe, change the offset to "00313800", the filename to "04_OS.nb" (see pic01 at the end of post for detail) and press "write xip_out.bin to:"
This tool write the xip section (xip_out.bin) in the OS (04_OS.nb) at the specified address (00313800).
Now we have 04_OS.nb with our original XIP
Rename 04_OS.nb to OS.nb and copy it to C:\tadzio
Copy imgfs_raw_data.bin obtained from dump process to C:\tadzio
Open a command prompt, go in C:\tadzio and type this command:
Code:
C:\tadzio>imgfstonb imgfs_raw_data.bin os.nb os-new.nb -bigstoragemove
This tool recostructs the OS (os-new.nb) from our dumped image (imgfs_raw_data.bin)
Now we need to patch the size of OS-new.nb, to do this type this command:
Code:
C:\tadzio>bPatch.exe -1 0xFF 0x632D000 OS-new.nb
The size of patched file must be 99.1 MB (103,993,344 bytes)
Ok, our OS is ready to use!
Copy OS-new.nb to C:\HTCRomTool and run "htcrt.exe"
This tool creates and signes a .nbh file from a .nb file. I suggest you to create 2 .nbh, one for OS and Spalsh (eg. OS.nbh)
and one for SPL (eg. SPL.nbh).
Select "ROM builder" tab and fill the fields like screenshots at the end of post:
OS.nbh (see pic02 for detail)
SPL.nbh (see pic03 for detail)
Press "Build!", type the filename without extension and press "Save"
Flash OS.nbh first so if something wrong in the image and the device don't boot you'll be able to flash any other ROM; while, if it boots ok, then flash the SPL.nbh.
Copy OS.nbh to C:\RomUpdate, rename it to ruu_signed.nbh, run "ROMUpdateUtility.exe" and follow the instructions
At this point we have flashed OS and Splash, if its all ok and the device boot right, then you can flash SPL
Delete ruu_signed.nbh, copy SPL.nbh to C:\RomUpdate, rename it to ruu_signed.nbh and run "ROMUpdateUtility.exe"
That's all!! Now you have completely restored your device to its original condition.
I've tested this procedure, worked fine for me and i hope for you too
.
.
.
bye all
.
.
.
isnt there some way to find out if we can enable wifi in the startup of the os? .. then we know if its in the Pharos or not. whadoyathinkhuh? seems in the Artemis wifi is enabled by the os....
avathar behemoth said:
isnt there some way to find out if we can enable wifi in the startup of the os? .. then we know if its in the Pharos or not. whadoyathinkhuh? seems in the Artemis wifi is enabled by the os....
Click to expand...
Click to collapse
i've tried to play around this few time ago with no succes
I've configured wifi interface card throw registry hack, it appears in the network adapter list, but when i turn on wifi nothing happens...
did you use the files i posted in the wifi thread? (posted the tnetw 1251 driver and a file from the extended rom of the artemis... wifinit.exe) but kudos to you for getting a device listed in the pharos (though i looked with task manager i think in a previous rom i flashed and i saw wifi.dll or something loaded at the list of pharos devices)
poldo964 said:
FIRST OF ALL I'M NOT RESPONSABLE OF ANY KIND OF DAMAGE OCCURRED DURING THIS PROCEDURE.
DO IT AT YOUR OWN RISK!
Ok, go on now
This guide assumes that you have already dumped your original ROM.
For how to dump your ROM, follow [email protected]'s wiki until obtain imgfs_raw_data.bin
What we need:
Official Pharos WWE ROM
tadzio tool (by tadzio)
XIPPORT tool (by bepe)
bPatch (by suracha)
HTC rom tool (by Dark Simpson) with pharos settings added by me
ROM update utility
I suggest you to create a folder for each tool (eg. C:\tadzio C:\XIPPORT C:\HTCRomTool C:\RomUpdate)
and unzip the tools in the respective folders. bPatch.exe is inside tadzio tool.
Download the official rom, right clic on "RUU_Pharos_HTC_WWE-ME_1.11.456.1_4.1.13.59_03.15.90_BLUE_Ship.exe", select "Open with WinRar" and extract RUU_Signed.nbh in "C:\tadzio"
Open a command prompt, go in "C:\tadzio" and type this command:
Code:
C:\tadzio>nbhextract ruu_signed.nbh
this tool extract the content of the .nbh file, if its all ok you should have these files now:
Click to expand...
Click to collapse
Failed to pass this step with this message " 'nbhextract' is not recognized as an internal or external command, operable program or batch file"
This command was not included in your attached tadzio tool.
wittanny said:
Failed to pass this step with this message " 'nbhextract' is not recognized as an internal or external command, operable program or batch file"
This command was not included in your attached tadzio tool.
Click to expand...
Click to collapse
oops! sorry
hi
i have not imgfs_raw_data.bin ????
when i run the romupdateutility i get error "invalid vendor id"
please help
lindows said:
when i run the romupdateutility i get error "invalid vendor id"
please help
Click to expand...
Click to collapse
you need HardSPL to flash a NON official ROM
well, actually I went from a Pharos running Poldo v13 (HardSPL Mobiz) to a completely original english Pharos by simply installing Pharos Official English ROM Version 1.11.707.1 (http://forum.xda-developers.com/showthread.php?t=394721).
Now when I boot, everything is original, even the SPL is the original and not the Mobiz anymore.....
Lucky?
fmulinacci said:
well, actually I went from a Pharos running Poldo v13 (HardSPL Mobiz) to a completely original english Pharos by simply installing Pharos Official English ROM Version 1.11.707.1 (http://forum.xda-developers.com/showthread.php?t=394721).
Now when I boot, everything is original, even the SPL is the original and not the Mobiz anymore.....
Lucky?
Click to expand...
Click to collapse
are you italian?
poldo964 said:
are you italian?
Click to expand...
Click to collapse
yes, why? do I write english so bad ?
by the way, I got a question for you: from your signature now you are using your latest rom and the new radio. I now a lot of people likes your new rom very much, but somebody complains about poor battery lasting. Does this new radio improves battery issue?
Cheers
fmulinacci said:
yes, why? do I write english so bad ?
Click to expand...
Click to collapse
no no... i mean that you have a WWE ROM now, not italian... When i've bought my pharos there was an ITA ROM inside and this thread explains "how to completely restore your device to its original condition (warranty coverage)" like the title says
by the way, I got a question for you: from your signature now you are using your latest rom and the new radio. I now a lot of people likes your new rom very much, but somebody complains about poor battery lasting. Does this new radio improves battery issue?
Cheers
Click to expand...
Click to collapse
cannot confirm this, i'm working with kaiser device now... but you can test by yourself, just flash the old radio and see what happens
cu
poldo964 said:
no no... i mean that you have a WWE ROM now, not italian... When i've bought my pharos there was an ITA ROM inside and this thread explains "how to completely restore your device to its original condition (warranty coverage)" like the title says
cannot confirm this, i'm working with kaiser device now... but you can test by yourself, just flash the old radio and see what happens
cu
Click to expand...
Click to collapse
ok, I got it....however my Pharos was French (a great deal, about 150€ at FNAC in Geneva...I could not let it on the shelf), and I did not back it up before upgrading....let us hope in 1 year nothing bad will happen ;-)
Hi all,
I'm looking for the official french version. Could anyone share it or tell me where i could DL it?
Thanks all.
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?
Hello there, im trying to make a 6.1 rom with ESP lang but i can't port the one posted by Da_G be cause the rom maker cab sends me problems with some files.
I hope some of you can help me with the lang porting or any pack I can use.
I'm using Old style kitchen made by aeroflyluby
Since you are speaking about WM 6.1 i suppose that you got the right build from the right Da_G thread....anyway ,here is the link:
http://forum.xda-developers.com/showthread.php?t=547314
Actually I'm using that package that you mentioned but no luck, when i change the files from the SYS folder the program "my build os" sends me an error anywhere and if y solve it (by deleting the problematic file) the rom maker (the .cab that calls the pack of tools) sends me an error while is rebuilding the files so I dont know what I'm doing wrong.
Do I have to use the SYS files with or without the 0409(ENG) files or i have to replace them?
Is there any proble if I cant find any 0C0A(ESP) OEM folder files?
I hope you can help me.
Regards.
If you are cooking for 0c0a then every 0409 folders must be left from your kitchen.
With 0c0a SYS you need 0c0a OEM at least OEM_Lang_0c0a otherwise your rom will not work.
Lokmetro said:
Actually I'm using that package that you mentioned but no luck, when i change the files from the SYS folder the program "my build os" sends me an error anywhere and if y solve it (by deleting the problematic file) the rom maker (the .cab that calls the pack of tools) sends me an error while is rebuilding the files so I dont know what I'm doing wrong.
Do I have to use the SYS files with or without the 0409(ENG) files or i have to replace them?
Is there any proble if I cant find any 0C0A(ESP) OEM folder files?
I hope you can help me.
Regards.
Click to expand...
Click to collapse
Oh i see. So i can extract 0c0a OEM files from any 6.0 dump folder? or I have to find a new oem folder files for 6.1?
BTW i'm cooking for a BenQ-e72 so I can't find any rom in spanish except for the one that came with my phone (WinMo 6.0)
a_GWM 6.0 OEM should be work with WM 6.1 at least you will need a WM 6.1 Initflashfile.dat (it is in OEM_Lang), sometimes Da_G shares his build within the Initflashfiles for every language,check in that thread to see otherwise try to cook it with your 6.0 initflashfile.dat and check if something is missing in StartMenu.
Lokmetro said:
Oh i see. So i can extract 0c0a OEM files from any 6.0 dump folder? or I have to find a new oem folder files for 6.1?
BTW i'm cooking for a BenQ-e72 so I can't find any rom in spanish except for the one that came with my phone (WinMo 6.0)
Click to expand...
Click to collapse
Thanks for the fast answer. I'm going to look for the WM from Da_G but I don't remember if i have seen that thread before, and btw I will take some time after I can post any advance be cause I'm not at home. for now I can only ask things if I have any question.
I have tried what you said but no luck. the phone wont start. it just stay in black screen, i don't know what i'm doing wrong
can you xplain exactly where does your rom stucks? maybe is not a SYS trouble maybe is a XIP trouble due to not pòrting ok or maybe is the wince. nls WWE or any SYS pkg missed
Well the rom wont give me any image, it just shows me a black screen and the normal screen lights for the rest it does nothing.
Once i got lucky but I had problems with the Start menu be cause i wasn't able to see the icons, i think it was caused by the initflashfiles.dat but now I can't do it again