Related
Hello
With ActiveSync STG files I know that I can use a program to look at the internals of that file and extract items that I want.
I was wondering if there is a way to do this with the ROMs that are on the FTP? I dont want to install the whole ROM, I just want to go in to look around and see if there is anything interesting to install.
Thanks
http://forum.xda-developers.com/viewtopic.php?t=17918
read xda2jojo's post
To disassemble ROM files you'll need to feed a decrypted ROM image to this utility - http://www.xs4all.nl/~itsme/projects/xda/dumprom.html
Example: dumprom.exe nk.nba -4 -d c:\dumped
this would extract all files from nk.nba to c:\dumped directory.
Then you can disassemble files by IDA. In the case of XIP DLLs you'll need to play with it because relocation info is missing.
Hi there,
I'm pretty experienced with rom cooking, but need a bit of direction from the pros here in a project I'm working on.
I have a working WM6 rom that I'm looking to make a kitchen for in order to more efficiently customize the rom.
I've decoded the rom to nba/fat format (my device uses nba/nbf format) and dumped the imgfs to a dump folder without any issues and can edit the rom that way, but I'm looking to make a kitchen.
I've used bepe's package tool to convert my dump into OEM & SYS folders without any problems. I now just need to be pointed in the right direction on how to rebuild these packages back into a working nba/fat file.
I've tried putting the OS & SYS directories in an existing kitchen like the bepe/helmi/scoter kitchens and using the imgfs tools there building the packages back into a rom. The rom builds successfully but then won't boot past the initial splash screen after flashing it.
Is there something else I need to do? Is it possible Bepe's package tool isn't properly building the packages?
Any help is appreciated. Thanks for everything each of you does to help the community
anyone?
I'm no expert, but everytime I've tried to dump a rom then rebuild it and flash it, it freezes at the 2nd splash screen. I never could get it to work, then I read somewhere that if the RGU files are missing then it would fail to boot, and sure enough on every rom I tried to dump, the RGUs were gone
My advice would be to build your rom with an existing kitchen. Collect all the packages you can find, build the ones you can't. Save all your custom graphics, themes, sounds, ringtones. Export all the registry keys for the programs you have on your phone now and use them to tweak your packages. It really won't take you much longer than if you were able to use the one you dumped. Before you know it, the kitchen you put together will be so much better than the ROM you dumped that you'll forget all about it!
My kitchen is a work in progress, but right now it's SO close to the way I want it that I can do Hard Resets without a thought as the only thing that needs to be done afterwards is restore my contacts!
All my connection settings are there, all of the buttons are set the way I like, all the colors, graphics, themes...everything! I've even set up an extrended rom with custom cabs I put together with all my commerical software with the Registration keys built-in.
I can't recommend a kitchen since I haven't used them all, but I started with Octaivio's with a 1437 build rom, now I've replaced that base rom with the 1908 build one from his latest kitchen and it's worked fine. The reason I used Octaivio is because he used Pbar as a taskmanager instead of that awful useless HTC x button (remnants of it still pop up when switching from portrait to landscape and vice versa).
joemanb said:
I'm no expert, but everytime I've tried to dump a rom then rebuild it and flash it, it freezes at the 2nd splash screen. I never could get it to work, then I read somewhere that if the RGU files are missing then it would fail to boot, and sure enough on every rom I tried to dump, the RGUs were gone
Click to expand...
Click to collapse
I can easily dump a rom, change it, rebuild it and use it successfully. That's not my issue. And, by the way, you were given misinformation about the rgu's. The rgu files are supplementary registry files that are merged into the main hives for each specific package, to make the registry entries modular. Even if you were to delete some rgu files, your device would still boot but wouldn't have the desired behavior for the packages you installed as some registry entries would be missing
My advice would be to build your rom with an existing kitchen. Collect all the packages you can find, build the ones you can't. Save all your custom graphics, themes, sounds, ringtones.
Click to expand...
Click to collapse
There are still a number of devices where no kitchen exists--mine is one of them, and honestly I'm not looking to use someone else's--I'd prefer to make my own
I just need someone to tell me what needs to be done to convert the OEM & SYS directories generated by bepe's package tool back to a working rom.
Steps I'm attempting now:
1) Dump original rom to dump folder
2) Run Bepe's package tool to make SYS & OEM folders.
3) Add modules
4) Run G'Reloc to fix overlapping modules.
5) I run BuildOS which makes the dump in the temp folder from the SYS & OEM folders.
6) I copy the original rom's fat(nba) to a temp folder
7) I dump imgfs from fat(nba) to imgfs bin file in temp folder with prepare_imgfs.exe
8) I merge the dump back into imgfs bin file with buildimgfs.exe
9) I put imgfs back into the fat(nba) with make_imgfs.exe
10) I convert nba back to nbf to flash
11) I flash the rom successfully.
12) Doesn't get past splash screen
Can anyone tell me what I'm missing or what could be making this non-bootable?
Thanks.
So its not the RGUs..
Please, if you figure this out, post the solution. When I ran into this, I searched all over the forum for a solution and found at least 2 or 3 other posts with this problem, but never a response.
Good Luck
have you modified the Iniflashfile.txt? thats the step most leave out and then it wont boot past the second splash screen
austinsnyc said:
have you modified the Iniflashfile.txt? thats the step most leave out and then it wont boot past the second splash screen
Click to expand...
Click to collapse
No, at this point I'm not trying to change the initflash so I haven't modified it. I know that when the time comes to change it I'll need to do the hex edit thing for the first 2 bytes, the unicode and the last line empty,. etc.
Also I'm not even getting to the 2nd splash. I'm not getting off the initial splash screen.
I'm thinking at this point the imgfs isn't getting put back together properly.
There have got to be some old pros who can tell me what I'm doing wrong.
I think I found part of the problem. In step 5, CreateOS.exe is doing something wrong with the hives. After running it, default.hv which is 770K+ in sys/metadata goes down to like 42K.
Anyone know why this is happening?
source said:
I can easily dump a rom, change it, rebuild it and use it successfully. That's not my issue. And, by the way, you were given misinformation about the rgu's. The rgu files are supplementary registry files that are merged into the main hives for each specific package, to make the registry entries modular. Even if you were to delete some rgu files, your device would still boot but wouldn't have the desired behavior for the packages you installed as some registry entries would be missing
There are still a number of devices where no kitchen exists--mine is one of them, and honestly I'm not looking to use someone else's--I'd prefer to make my own
I just need someone to tell me what needs to be done to convert the OEM & SYS directories generated by bepe's package tool back to a working rom.
Steps I'm attempting now:
1) Dump original rom to dump folder
2) Run Bepe's package tool to make SYS & OEM folders.
3) Add modules
4) Run G'Reloc to fix overlapping modules.
5) I run BuildOS which makes the dump in the temp folder from the SYS & OEM folders.
Click to expand...
Click to collapse
At this point I think that you have the XIP extracted already, in order to create valid boot.rgu
6) I copy the original rom's fat(nba) to a temp folder
7) I dump imgfs from fat(nba) to imgfs bin file in temp folder with prepare_imgfs.exe
8) I merge the dump back into imgfs bin file with buildimgfs.exe
9) I put imgfs back into the fat(nba) with make_imgfs.exe
10) I convert nba back to nbf to flash
11) I flash the rom successfully.
12) Doesn't get past splash screen
Can anyone tell me what I'm missing or what could be making this non-bootable?
Thanks.
Click to expand...
Click to collapse
It's a suggestion, but i think you're missing the .rgu files.
Of course, those are not needed when flashing, but when BuildOS creates the default.hv and user.hv...these 2 being invalid, the OS can't boot.
Probably Bepe can clear you better on that one.
Cheers !
source said:
And, by the way, you were given misinformation about the rgu's.
Click to expand...
Click to collapse
Apparently not, after reading Anichillus' response (which agreed with mine) I converted the HVs to RGUs and it WORKS finally!
It's probably not a good idea to reject info out of hand like that..You almost had me convinced. Thankfully I always try to verify information before I accept it, or tell someone they're wrong, mistaken, or misinformed.
Thanks Anichillus!
How can we extract a program from a rom and convert it to a Cab for install on another phone
how to know what and where to find the files (like registry for instance)
and how to convert to cab
Thanks
Hi,
currently the most apps available as oem pack or cab file, use google and find this.
What a app search you?
wfg
Starbase64
aalim said:
How can we extract a program from a rom and convert it to a Cab for install on another phone
how to know what and where to find the files (like registry for instance)
and how to convert to cab
Thanks
Click to expand...
Click to collapse
Well, if you have the ROM already, it depends on what phone it comes from. Once you have the files out, you have to look at packages in the OEM and SYS folders, find the corresponding files, and look through the RGU's and HV files for needed registry keys. And of course, you also have to check the initflash.txt and iniflash.dat files.
ivanmmj said:
Well, if you have the ROM already, it depends on what phone it comes from. Once you have the files out, you have to look at packages in the OEM and SYS folders, find the corresponding files, and look through the RGU's and HV files for needed registry keys. And of course, you also have to check the initflash.txt and iniflash.dat files.[/QUOTE
Click to expand...
Click to collapse
then how can we turn OEM into a cab??
Hi All,
I have managed to split XIP.bin and imgfs.bin from the OS ROM of HW6915 G4-v.121UK, but failed to dump the imgfs due to unable to load compression dll, any one know the compression method or how to analyze the compression method of imgfs.bin?
If we have the way to dump and undump imgfs, then we can customize the rom of hw69xx.
I will uplaod tools, XIP.bin and imgfs.bin if anyone would like to give a shot.
you probably missing cecompr_nt.dll
keyx said:
you probably missing cecompr_nt.dll
Click to expand...
Click to collapse
I do have the cecompr_nt.dll file in the rom tool folder, maybe the hw69XX rom has a special compression method so current version of cecompr_nt.dll can't not recognize.
not likely as ther are only XPR/LZX compression for imgfs, may be the rom is encrypted..no idea sorry
Here's a tool to dump hw6900 series ROMs.
Just drag-n-drop CEOS.nbf in DUMP_hw6900_IMGFS.bat
You will get OEM and SYS folders.
PS. hw6900 series problem is that you can't get a working xip.bin from NBF file. As you said you got a xip.bin, but did you tried to dump it? Most likely you will get an error.
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?