Related
So I've been playing around for a little while with the intention of creating my own custom ROM. I think I've got everything all figured out - however I'm having a problem that I think is related to the initflashfiles.dat file. Basically, after flashing my new OS ROM, my 8125 hangs at the splash screen with the version numbers on it. As a test, I redid my modified ROM, except I used the original initflashfiles.dat - this worked just fine. Tried it again by building the ROM with my modified initflashfiles.dat - same problem.
Here are the steps I'm going through.
1. Parse out the nk.nbf file using typhoonnbfdecode -x
2. prepare_imgfs 80040000-OS.nb -nosplit
3. viewimgfs imgfs_raw_data.bin
4. Modify contents of dump directory. Basically I've deleted files I don't need and added new ones.
5. Modifiy initflashfiles.dat (which I've attached). After modifying the file I open it in a hex editor and remove the first two bytes - making the first byte 3B (";"). I save it and mark it as read-only.
6. buildimgfs
7. make_imgfs 80040000-OS.nb -nosplit
8. Run nb2nbf_tornado.exe. I do run this correctly, using the correct memory address for the OS .nb file.
9. Put the new nk.nbf into an existing RUU self-extracting archive and run it.
It really seems like it's the initflashfiles.dat file - as I've successfully loaded this ROM with the original file (its really not the original, it's from a summiter ROM that I'm basing mine off).
Any thoughts?
I'm going to bump this once just in case people missed it originally.
I've messed around a bit more, and have pretty much isolated that this is my problem - but for the life of me I can't figure out what I'm doing wrong.
CameronJ said:
I'm going to bump this once just in case people missed it originally.
I've messed around a bit more, and have pretty much isolated that this is my problem - but for the life of me I can't figure out what I'm doing wrong.
Click to expand...
Click to collapse
Hi,
i see that the file you've attached isn't actually a .DAT file. It is a .dat.TXT that's the same that saying it's a TXT file!!!
If the file you're putting inside your ROM is this very same file (.dat.txt) then you've found your problem: you need a .DAT and NOT a .dat.txt file!!!
Try following this procedure on your PC (i suppose you're using XP or 2003 server):
- open a folder (whichever folder you like, it's not important)
- on the Tools menu click Folder Options.
- click the View tab.
- clear the Hide extensions for known file types check box.
- press OK
PS: Here is an illustrated guide on how to show file extensions
Now go to the place where your initflashfiles.dat is. If the file is named 'initflashfiles.dat.TXT' (like the file you uploaded in this forum) then:
- select the file
- press F2 (or right click and choose 'Rename')
- remove the tailing .txt from the name
Finally:
- let us know if it worked
Bye bye
risidoro said:
i see that the file you've attached isn't actually a .DAT file. It is a .dat.TXT that's the same that saying it's a TXT file!!!
Click to expand...
Click to collapse
:lol: Thanks for the reply.
I had to add the .txt extension otherwise the forum wouldn't let me upload the file (.dat files are not on the list of available file types for upload).
When I loaded the file I meant to put that explanation in there but forgot before I finished the post.
Hi. I don't know if you're still working on this, but I'd like to share with you my experience last night. I examined your initflashfiles.dat, and it is perfectly ok.
As I see in your initflashfiles.dat, there are a lot of folder customization like:
Directory("\Program Files\Task Manager"):-File("taskmanager.exe","\Windows\taskmanager.exe")
There is nothing wrong with this as we need the file to be in the right location. BTW, THIS FORMAT WORKED FOR ME. Just a thought, you might be editing the default.hv and user.hv (hives) to put in the registry keys of some applications?
My device (Himalaya) did not start out correctly and did not execute the initflashfiles.dat, BUT when I connected my Hima through active sync, you can actually explore the contents. SO, in this non-working state, I experimented in tracing the culprit, by restoring a couple of the original files I edited. I found out that it has something to do with the way I edited the hives.
Steps I made in experimenting:
1. I sync my Hima to my PC.
2. Copied the original default.hv to \windows directory
3. Hard Reset Hima, BUT answer NO to all three boot options
4. My Hima started normally and executed initflashfiles.dat to the detail.
Discovery from experiment:
1. The files were only copied to the directory were we wanted it, BUT the original file is still in the \windows directory. Therefore, we did not save storage memory.
2. We only benefitted from an already installed app built into the ROM.
Hope this gives you some insight.
Help!
I've followed the instructions on the wiki about dumping a ROM, which I've done and it worked fine.
Then i started to follow everything to rebuild the ROM, which worked until I got to the buildimgfs.exe stage, and all I get is an error message that it cant find the compression dll, even though I know the dll is in the directory with it.
Any help much appreciated as I'm trying to rebuild a Orange UK M700 rom
Cheers
use these batch files to dump/rebuild the rom&hive, nbhtool to create the Signed_RUU.nbh
Make Sure You Have A Valid Imgfs_raw_data.bin In The Folder You Are Issueing The Command From, That Stopped My buildimgfs.exe Working.
Cheers
still not working...
message about missing compression dll still happens, even though viewimgfs works fine.
@apoc - not entirely sure which bat files to run, the dump ones didnt seem to do anything?
hollandg said:
still not working...
message about missing compression dll still happens, even though viewimgfs works fine.
@apoc - not entirely sure which bat files to run, the dump ones didnt seem to do anything?
Click to expand...
Click to collapse
command prompt:
NBDump.bat OS.nb - to dump
NBBuild.bat OS.nb - to rebuild
HVDump.bat user | HVDump.bat default - to dump the user.hv or default.hv,
The HV bat files must be on the same dir as the .hv files.
there are a bunch of hidden files, and I've mistankenly hidden OSChecker.exe, I think it's not exactly necessary to check the created .nb files, but the file is there and you can use it.
@APOC, another bit of help if you dont mind?
I've run the NBBuild.bat and it produced a file but someones tested it and says it doesnt work so I had a look at the .bat and some of the steps seem to pull information from an exisiting NBH file? I downloaded a file as part of the wiki step by step to dump and rebuild a file so the NBH I have is nothing to do with the one I'm trying to rebuild ... is that a problem?
As before I've got as far as running viewimgfs to create the dump directory but buildimgfs refuses to work still!
-----
I've jsut read tadzio's thread about the enhanced imgfs tools so I'm going to try that again and see what I can do
Itjes Guide on how to cook your own rom, fast and dirty J Part 1
First of all, this guide will not tell you everything you need, I cant show you where to find reg entries, where all files are located. It’s a guide that will show you the basics. I will tell you how to extract a official nbh to os.no, how to dump it to respective oem and sys folders where you will do your “cooking”
First of all download Hypercore Kitchen here, then run the install file.
You will now have a folder called hypercore on your desktop, and a folder called core, located on c:\core
After install, download this fixed batch folder: batch or from mirror here: Batch
Delete the batch folder in c:\
Extract it to c:\core, and replace the original one.
The reason for doing this, is that there had to be some changes in the batch files for it to work.
Now you have a functional hypercore kitchen and you can start working.
I am gonna release a OEM, SYS and ROM folder for you, but not yet. I want you to understand how mutch work it takes to build a rom, and you need to go through some of the steps that all the other chefs must when they build roms. Why not just make it simple and give you everything? There is a answer to that, and you might not like it: Because I don’t want to….
Download your official RUU from here
Use winrar or similar to extract the files in the installer, choose extract to a folder.
Open the folder you extracted the files to, and find the RUU_signed.nbh
Copy it to c:\core\tools
Open your command-promt (dos editor)
Go to c:\core\tools
Your command promt should now look something like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
When this is done, you must enter this: nbhextract ruu_signed.nbh
The nbh will now be extracted and in the core\tools folder you now have all the files dumped from the nbh
The screen should now look something like this:
See the second last line Extracting: 06_OS.nb
That is the file you will need.
Rename the 06_OS.nb to OS.nb
Copy the OS.nb, then close the core\tools folder
Move to your desktop, and open the hypercore folder
Then enter the extract folder, and paste your OS.nb there
Go back to hypercore main folder, open the Panel folder, then open the Extract folder.
Inside the extract folder you will find a file/shortcut called Dump .nb and .bin
Now a panel will open and give you 4 options:
Now you are dumping the OS.nb into a xdump folder located in panel\extract
Your answer here is 1 since im doing this guide for heralds
Now a new window is gonna pop up and tell you that in that windows your OS.nb should be placed, and if you did what I told you correctly, then the OS.nb is located there already. So close that window, and then another option in the command promt will ask you to hit enter when ready, witch I now suppose you are.
The OS.nb is now being extracted into the xdump folder located in the extract folder. This takes aprox a minute or so.
When the OS.nb is finished extracting, you will get a option to start pkg.tools. just close that option,its not working for some reason, I never really looked into it, I just did a “workaround”
In panel\extract you will find pkg tool
Start the pkg tool, and you get a command promt window, read it, and then press enter.
Now you should see this:
Choose option 3
Pkg tools will now open.
Go to the file menu in upper left corner, chose open, then browse to hypercore\extract\xdump\
Highlight the dump folder and press ok.
GO TO NEXT POST IN THIS THREAD
You should see something like this:
Forget the missing manifests.
Now choose the Tools meny in pkg tools, and build packages, this will only take max a minute. (you will see nothing, just wait a bit.
When you have done his, browse to you xdump folder, open it, inside you will see the dump folder, rename the dump folder (not the xdump) to packages.
Copy the new packages folder and paste it into the hypercore\extract folder. Then close the pkg tools.
From now on, I will not give you screenshots of everything. You should get the picture on how it works now.
You will see a new commandpromt window, giving you 5 options, you choose option 4: Move oem and sys to hypercore\build.
You will get a question if you wanna backup, type n for no this time.
This takes 2-3 minutes, depending on your computer. The oem and sys is being moved to hypercore/build. Where the building process is gonna happen.
Next step is to go back to hypercore\panel\extract.
Open the dump XIP tool, and you get a new pop up window, just close it and press enter in the command promt. A new commandpromt window show you option 1 and 2, do both options, and when you have done this, the oem, sys and rom folder contains all you need to cook.
But that comes in next lesson.
I have now written this as easy as I can, if you don’t understand this, I cant help you more in this process, because I cant give it to you in a easier fashion.
Have fun
Itje
Part 2 of Itjes cooking lessons
How to add and remove and build your rom
I assume you have followed the instructions in the first part, learned to extract both the .nbh and the os.nb into rom, sys and oem folders.
My way of cooking:
First you need to find out what you want and not want in your rom. I will try to guide you into building a small apps rom.
So first I do, is deciding what I don’t want to have in my rom, and I usually go to the sys folder, and start removing stuff I don’t use:
But before you start removing in sys, highlight the sys folder, right click and choose properties, uncheck the read only box, if you don’t you can’t edit files.
Remove:
Transcriber + Transcriber_lang_04xx (xx is the country code in your rom) + Transcriber_ Lang_04xx_DPI_96
See what you need to do? Remove all the folders with the name transcriber in it
You can also do this with: Office, windowslive. Internetsharing, entertainment (games)
Be careful removing in SYS folder, delete wrong stuff, and you will have a brick when flashing.
That’s a easy “clean up” of the sys, there are also other stuff you can do.
You can make your own startup image, that is located in the Redist_dpi_96_resh_240_resv_320 folder, and is called welcomehead.96.png, edit with either adobe photoshop or corel, or any other picture editors that support png files.
Open the welcomehead.96.png and do your changes, save and your done. How to and all that with photos/pictures im not gonna do, so you need to find a way to do so yourself.
Now, you can go to OEM folder, where you can add and remove a lot off stuff.
I will not show you everything, you must figure some stuff out yourself.
But download OEM packages (This is easy to fin, its all over the xda forum.
Im assuming you have found in some stuff you wanna add, in.ex total commander, htc home, networkwizard, CommManager. Ocourse you can add more or less.
Add the oem packages into the oem folder. Total commander and networkwzard don’t require removal off default files from the oem folder, but comm. Manager do, and so do htc home. The way I use to find duplicate files, is before I add the oem packages, I open in.ex the new package with comm manager, and I highlight the OEM folder and rightclick and choose searchtab. Search for files, type in search “comm.” And all files containing the word “comm.” Will be displayed, dele them (make sure they belong to comm manager, that the names matches the one in your package)
When you have searched for all files in your package, and deleted them from the OEM folder, you can add you package.
Follow same steps for all packages you add, that can have duplicate files, if you don’t you will get error when building the rom, and the build process will terminate, tell you what file is duplicate. You must then find the file, and remove it (don’t remove the one in your new package)
You can also delete stuff from oem folder, I will take as example adobe.
The easy way to remove adobe, is to find a oem package with adobe, so you can see what files needs to be deleted. Use same way as I showed you with comm manager.
You can also delete gif files, png files and wav files to make more space, be carefulll so you don’t delete files that are needed by applications you wanna keep.
Now I hope this was clear enough.
Now you can go to the hypercore/panel/build section where you will find buildOS, run it it follow steps there.
If you get errors with duplicate files, you need to remove the duplicate and start buildOS again. And continue to do so if you get more errors.
But when the buildOS is finished, close it and a new window will pop up, chose your device, and press enter, and your os.nb will be built.
flash it to your device, and test it. If it didnt work, then you have done something wrong, or im just a lousy teacher
This was a very easy guide, I hope you find it usefull. There are lot of things you can do more then I have described now, but all you need is posted all over the forum. And if your dedicated enough, you will find all you need, just be patient. You cant find it all in one day,and you cant understand it all in one day.
Have fun
Happy cooking
cheers
----------------------------
Good work. Hopefully we can get some new roms going around.
itje said:
After install, download this fixed batch folder: batch or from mirror here : batch
Click to expand...
Click to collapse
Where's the link to the batch download?
LordPhong said:
Where's the link to the batch download?
Click to expand...
Click to collapse
right there
lol, was a bit tired yesterday, forgot to add the link
Cool - thank you itje for all the effort and time you are investing...
Can't wait for the next parts
trallala said:
Cool - thank you itje for all the effort and time you are investing...
Can't wait for the next parts
Click to expand...
Click to collapse
thx
has anyone been sucessfull extracting nbh to os.nb to oem, sys and xip (rom folder) following this tutorial?
When is the next part due? I really am eager to cook!!!
oddball1 said:
When is the next part due? I really am eager to cook!!!
Click to expand...
Click to collapse
havnt started on it yet
So I dont know maybe this weekend, but not later then the end of next week
patience, my friend, patience
is the next part just making the extended rom portion? I think there's a tutorial somewhere on this site but I can't seem to remember off the top of my head, right now.
itje said:
Download your official RUU from here
Click to expand...
Click to collapse
I'm being a pain in the arse again. there's no link there and I don't know if it's the same one as the official tmo release. I know I can probably use that one but would rather not.
hey itje the links for the new batch files doesnt seem to be working. i tried them and it just keeps popping up saying it cant DL
edit: nevermind i got it too work. it was blocked on the isp i was using.
itje said:
thx
has anyone been sucessfull extracting nbh to os.nb to oem, sys and xip (rom folder) following this tutorial?
Click to expand...
Click to collapse
itje said:
Rename the 06_OS.nb to OS.nb
Copy the OS.nb, then close the core\tools folder
Click to expand...
Click to collapse
where do we copy the OS.nb to? Since, I didn't know, I, manually, had to do it.
itje said:
Copy the new packages folder and paste it into the hypercore\extract folderThen close the pkg tools.
Click to expand...
Click to collapse
This didn't work for me. I had to manually past it in %systemroot%\Core\Extract\Packages after I closed the pkgtools. For some reason, it didn't find the Packages folder correctly.
After that, I followed everything else and it worked fine. Just as you described. Just waiting for part dos (spanish not MS-DOS).
everything works fine up until the end waiting on farther instructions.
EVERYTHING YOU ASK FOR IS ALLREADY THERE, START READING........
Just as its clear, from now im not gonna answer anyone who ask for something thats allready described in the tutorial.
But the link for ruu was not there, I'll give you that..
i am cooking my chinese rom ,and thanks you working.
ginolin said:
i am cooking my chinese rom ,and thanks you working.
Click to expand...
Click to collapse
Glad I can help
Honestly, if anything you did went wrong, is because you are not reading and reading it again before you do it!
Up to now, everything is well explained
For those of you who want to customize wm6.1, here it a simple ROM kitchen to do so. Beginners, please wait for my GUI release. It is much simpler to use. This isn't that hard, but it takes a little bit of time on your side.
The basics:
All software and regedits are contained in folders called OEM packages. These are in the OEM folder.
All operating system stuff is in the SYS folder. I've also moved the shadow drivers here so you don't have to mess with them.
To make OEM packages:
Download ervius's package creator 5.4 from XDA-developers. Use this to open the cab file to convert into a package.
Copy the OEM package to the OEM folder.
Do NOT delete the OEM packages you don't want. You will choose them later in a different way.
NOTE: You can always download premade OEM packages from XDA-Develoers. There are tons of options.
If you want to make a regedit.
Create a new folder in the OEM folder and convert it into a package using Package Creator 5.4.
Open the RGU file inside with notepad
Edit like following. Note that this isn't the way to comment in regedit files:
Code:
REGEDIT4 <-----Make sure this is always the first line
------Leave one line blank here-------
[HKEY_LOCAL_MACHINE\Software\Example Software\Example Key] <----- Navigate to keys like this
"Example String" = "test" <-------- Write values with quotes. Strings are given with quote after the equal sign.
"Example Directory" = "Windows\\test.jpg" <------ Use \\ to indicate a \ between directories. Otherwise, the ROM build will not work.
"Example Number" = dword: 5000 <----- use dword: to indicate a number or hex value.
<----- You can add more reg entries after the first one. Make sure to specify a different key when needed
-----leave 2 lines at the end of file------
For Sliding Panels:
Leave ROM as it is.
For Neo interface:
Replace Chome folders and bronze folders in SYS folder with the ones attached below.
Select Neo Interface in the buildos step.
Build ROM:
start buildos.bat
when it opens packagetools+buildos, click on the buildos tab.
Click load rom and navigate and select the kitchen folder
Select which oem packages you want and then click Go.
Once it is done, close out.
Sit back and relax for a while so the batch file can build the ROM.
Self-explanatory from here.
Post any questions/problems here.
link: http://www.sendspace.com/file/ap9n8w
NOTES: The inlcuded T-Mobile Edition Package is my beta version. Feel free to build on it. You might also notice the empty placeholder folder for my N33D4SP33D Edition rom that I haven't worked on yet.
To make OEM packages:
Download ervius's package creator 5.4 from XDA-developers. Use this to open the cab file to convert into a package.
Click to expand...
Click to collapse
I found the program but get many errors when I start it up on my computer.. Im currently running Vista Ultimate. I went into control panel and changed the enviroment to emulate WinXP when the program runs and still get many errors..
Is there a vista friendly program out there or alternative available?
I'm running Vista Ultimate too and it works perfectly for me.
Attached is the version I have.
ND4SPD said:
I'm running Vista Ultimate too and it works perfectly for me.
Attached is the version I have.
Click to expand...
Click to collapse
Great! yours works thanks alot now to get my feet wet in all this lol
I got this error
'Error building default.hv and user.hv! (see imto "BuildOsX-log.Txt")
i can't see anything in there. What now. Thanks
Do you mean there's nothing in the BuildOsX-lot.txt? There should be. A few lines from the last, or the last line, there should be the registry file that messed up and on which line it messed up on. The file is given by the GUID, or that long string of numbers and letters that you see.
no, there is nothing what tell me what to do. so what should i do with that error.
i will make stick this thread.Hope next times will see some roms with this kitchen
Thanks tom. I'll make sure to post my GUI kitchen soon to let more people create ROMs a lot easier.
kormanb1123 said:
no, there is nothing what tell me what to do. so what should i do with that error.
Click to expand...
Click to collapse
what kind of things did you modify or add? Maybe I can help based on that.
I get the same error for the following:
InitRegistry FAILED in file ".\Registry\fcbf420c-04fd-478f-bd29-e4ab55973337.rgu" within a few lines of line 359.
ImportFromPackageListStrict: (RGUComp) !ERROR failed importing ".\Registry\fcbf420c-04fd-478f-bd29-e4ab55973337.rgu"
wmain: (RGUComp) !ERROR failed building DEFAULT hives
Looked through each App in the OEM folder until I found the matching rgu number, which in my case is the HTC DirectShow. Took that out of my ROM build, ran again and it states that it completed.
I think there is a problem with the directshow package. I'll check the registry entries. Until then, I think you might need to go without that.
This may sound like a stupid question, but hear me out. I have used BuildOS in the past for an Apache from PPCGeeks\PPCKitchens. Once the ROM is finished creating in that version it auto prompts to update your device.
After the ROM is done in your version, I then selected the Package Tool tab and pointed it to the "temp" directory and it did it's thing. Now I am at a loss for what to do next. I see a .nb file temp\dump\ROM directory but i don't see a .nbh file. Do I use the NBHTool even though PHOEB is not listed?
ND4SPD said:
I think there is a problem with the directshow package. I'll check the registry entries. Until then, I think you might need to go without that.
Click to expand...
Click to collapse
I'm not too worried about the directshow, I just that maybe the other guy was getting the error for the same reason so figured I would pass on my resolution.
Sorry, I guess I didn't completely read you post. For the HTC Rom Tool, use the exacalibur settings. Those are the exact same as the Juno.
all I have is o4_osxip.nb.exe in the temp folder no nbh is this the right nb. file I use with
htc tool I put exacalibur settings but don't no what to put in firmware contents
do I put o4_osxip.nb.exe in system and none in the ipl spl and splash and 0x800 radio
ok i did this
Build ROM:
start buildos.bat
when it opens packagetools+buildos, click on the buildos tab.
Click load rom and navigate and select the kitchen folder
Select which oem packages you want and then click Go.
Once it is done, close out.
Sit back and relax for a while so the batch file can build the ROM.
ok where is the rom all i have is o4_osxip.nb.exe in the temp
i have no file imgfs-new.bin in the temp all i have is 04_OSXIP.nb.exe and cecompr_nt.dll and CECompressv4.dll
and where would i look for the batch file
Thank you for your works, ND4SPD
but i can not download your kitchen, it says reached the 4G limit.
because i want to know is there any wrong method i used.
My issue is :
when buildimgfs, the total sections can not bigger than 1B200.
when i put too many files into the imgfs file, the buildimgfs will quit without any info.
but the 71M imgfs.bin have about 22000 sections.
do you have issue too ?
Is it because my PC have only 1G RAM, not enough to do the building?
@Hikey: I have that same problem too. It's the way t-mobile packaged the rom. I'm going to try using the dopod rom for the base next. It might be the PC too. I only have 1GB of RAM, maybe it isn't enough.
@kron2:
run buildos
download this zip: http://www.sendspace.com/file/xuhlc5
copy the files from the zip archive to the temp directory.
open up the cmd that's now in the temp directory.
type the following:
Code:
ImgfsFromDump imgfs-old.bin imgfs-new.bin
Sit back and relax. If this finishes without crashing like Hikey said, do this:
Code:
ImgfsToNb imgfs-new.bin 04_OSXIPN.nb os.nb -conservative
Now you can run the htccert program in the main directory of the kitchen to build the rom. When you are done making the nbh, copy it to the RUU folder and run the update utility.
im trying to extract some cabs from a NHB file...can anyone guide me in the direction on how to do this
I'd say the best way to do that is to extract the ROM into regular files.
You need to download a bunch of EXE files: NBHextract.exe, NBSplit.exe, ImgfsToDump.exe, and ImgfsFromNB.exe
You need to extract the NBH with NBHextract.exe. This will yield a .nb file
You need to use NBSplit (use the "-kaiser" parameter) to split the .nb into a .nb.payload file and a .nb.extra file
You then need to use ImgfsFromNB on the .nb.payload file, which will create a file called imgfs.bin
Use ImgfsToDump on imgfs.bin, which will create a folder called "Dump". When it finishes, All of the ROM's files will be there. You will probably want to search the folder for .cab files, since there are thousands of files in the average ROM dump.
That should do the job for you.
Or just use Visual Kitchen to Dump the ROM, and then rebuild the OEMs to CABs.
Dave
could u walk me through the visual kitchen program?
Hmmm look for htcRIE_0.4.0.47 and extract what you want.
im trying to extrct the streaming media player cab...the one thats in most of the 6.5 roms that has a look a like HTC ablum look to it, but i cant find a cab using "htcRIE_0.4.0.47"
little help will might ...
You do not search for it at you WM ROM,
Search at the site...
Anyway i have been find it for you !
A newer version of htcRIE, enjoy!
michealmyers said:
im trying to extrct the streaming media player cab...the one thats in most of the 6.5 roms that has a look a like HTC ablum look to it, but i cant find a cab using "htcRIE_0.4.0.47"
Click to expand...
Click to collapse
i have that program, but im unsure on how to properly use it to get the cab files.....can u help me?
michealmyers said:
i have that program, but im unsure on how to properly use it to get the cab files.....can u help me?
Click to expand...
Click to collapse
With Visual Kitchen, just click on the Dump button at the bottom - and then browse to the NBH file .
Dave
i guess all nbh files dont have cabs because in the dump folder it creates...its only a couple of cabs and whole lot of systems files
michealmyers said:
i guess all nbh files dont have cabs because in the dump folder it creates...its only a couple of cabs and whole lot of systems files
Click to expand...
Click to collapse
Yeah, you have to rebuild the EXT packages to CAB's I don't know if there is a tool for that actually. Might be better dumping it the Dave (TyTNII) way, that will give you OEM's. There are tools for OEM 2 CAB.
Jason8 is working on a tool to convert all 3 all ways IIRC.
Dave
the nbh extract file launches for a quick second...it doesnt stay on the screen, as well as a lot of other files such as nbh split....do i need to update something in order to have these programs run properly?
michealmyers said:
the nbh extract file launches for a quick second...it doesnt stay on the screen, as well as a lot of other files such as nbh split....do i need to update something in order to have these programs run properly?
Click to expand...
Click to collapse
You have to run them from the windows command line (CMD.exe). If you really want me to, I'll upload a batch file I made which automates most of this. You just put the NBH and tools in certain folders and run the batch file and it does the rest.
DaveTheTytnIIGuy said:
You have to run them from the windows command line (CMD.exe). If you really want me to, I'll upload a batch file I made which automates most of this. You just put the NBH and tools in certain folders and run the batch file and it does the rest.
Click to expand...
Click to collapse
that would be so helpful
Alright, I fixed all the bugs in it (it was still in progress) and added some new features I had meant to add for a while, such as renaming the processed files by date processed (though you probably won't need them if you're only extracting one ROM). Hit [WINDOWS KEY] and R on your keyboard at the same time to open the Windows Run dialog, and type "%USERPROFILE%" without the quotes. Simply unzip the file and drag the folder called "Flashing" in the user folder (it's vital to have the Flashing folder in the correct spot. Otherwise, the entire script will fail). Place the NBH file you want to extract in the NBHDUMP folder (in the Rhodium folder, which is in the Flashing folder), and go to the IMGFS folder (in the Rhodium folder, which is in the Flashing folder). Now, run RhodiumRomDump.bat and the dump should commence, and a folder with your dump should appear in the same directory.
If anything should go wrong, please tell me so I can try to fix it.
EDIT: Please redownload, all issues I could find are fixed in this version. If you get errors about needing MSVCr71.DLL with this version, google is your friend.
maybe im not doing something right, ive been at it for days now...i put the "flashing folder" in C:\Documents and Settings\Sean (sean's my name..haha), put the nbh file in the NBH folder, ran "DumpRhodiumRom", i got 2 folders named "and" and "Setings"....when i run "dumpRhodiumRom", its just stays on the screen for half a second
ive extracted the rom before using visual kitchen...im trying to get some of the programs into cabs...the problem is that in the dump file, i see the programs i want, but they arent in cabs, so i cant just take its "exe" file and put it into another phone (well at least that didnt work for me)
michealmyers said:
maybe im not doing something right, ive been at it for days now...i put the "flashing folder" in C:\Documents and Settings\Sean (sean's my name..haha), put the nbh file in the NBH folder, ran "DumpRhodiumRom", i got 2 folders named "and" and "Setings"....when i run "dumpRhodiumRom", its just stays on the screen for half a second
Click to expand...
Click to collapse
That's odd. Can you tell me two things?
Where do these folders ("Settings" and "And") show up?
Hit [Windows Key] + R and type "CMD" (without quotes), then hit okay, then type "cd %USERPROFILE%\Flashing\Rhodium\IMGFS" (without quotes). Now, type "DumpRhodiumRom" (without quotes), and tell me exactly what is says (you don't actually have to include all the formatting and everything). Also, if you could tell me what color it's in, that would help.
I'm going to test it in a virtual Windows XP environment and see if it's compatiblity with XP that's the problem.
EDIT: So the problem seems to be the fact that it doesn't like the spaces in the folder name "Documents and Settings", hence the creation of the "and" and "settings" folders. Unfortunately, it's an important folder, so renaming isn't really possible. However, I think I know a simple fix to the original script, so I'll test that and post it shortly.
michealmyers said:
ive extracted the rom before using visual kitchen...im trying to get some of the programs into cabs...the problem is that in the dump file, i see the programs i want, but they arent in cabs, so i cant just take its "exe" file and put it into another phone (well at least that didnt work for me)
Click to expand...
Click to collapse
Try downloading cabtools V 0.3 and use pkg2cab to build the package back into a .cab file. I've never done it myself, but this looks like what you want.
DaveTheTytnIIGuy said:
That's odd. Can you tell me two things?
Where do these folders ("Settings" and "And") show up?
Hit [Windows Key] + R and type "CMD" (without quotes), then hit okay, then type "cd %USERPROFILE%\Flashing\Rhodium\IMGFS" (without quotes). Now, type "DumpRhodiumRom" (without quotes), and tell me exactly what is says (you don't actually have to include all the formatting and everything). Also, if you could tell me what color it's in, that would help.
I'm going to test it in a virtual Windows XP environment and see if it's compatiblity with XP that's the problem.
EDIT: So the problem seems to be the fact that it doesn't like the spaces in the folder name "Documents and Settings", hence the creation of the "and" and "settings" folders. Unfortunately, it's an important folder, so renaming isn't really possible. However, I think I know a simple fix to the original script, so I'll test that and post it shortly.
Click to expand...
Click to collapse
This is What i got....where the "and" and "settings" folder apear is "untitled2.zip"