Rebuilding Dumped Roms - P3600 Software Upgrading

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

Related

aWizard isn't cooperating -- need help!

I just got my 8125 yesterday and tried to CID unlock the phone, but aWizard doesn't want to function. I unzipped the aWizard files to C:\awizard\ and triedseveral times. No matter what command I choose in aWizard, I get "The system cannot find the path specified." (See attached screenie.) I also get the same error if using lokiwiz.
BTW, even though it says the procedure is completed, nothing really happened; the program is just failing at what it's doing and completing its run anyway.
I know that the phone is communicating with the PC because I can do all the usual AS things -- sync, copy files, etc. I've tried using different USB ports and sync cables, too, but nothing helps. Existing OS is build 14410.1.1.3.
Any tips?
Have you tried manually installing the "EnableRapi.cab" the phone and then running aWizard or lokiwiz? the file should be on both apps, in aWizard check to make sure it's in the "lib" folder and in lokiwiz it should be extracted in plain sight.
There is no "lib" folder in my aWizard directory (see below), but the file is there, and it's in the lokiwiz directory, too. And, yes, I did copy and run the file on the 8125 as well.
That's what's so weird; I can't figure out why this works so easily for other folks but not for me. It must be something pretty basic, but I can't get it.
masr1979 said:
Have you tried manually installing the "EnableRapi.cab" the phone and then running aWizard or lokiwiz? the file should be on both apps, in aWizard check to make sure it's in the "lib" folder and in lokiwiz it should be extracted in plain sight.
Click to expand...
Click to collapse
Which version of aWizard are you using? the lib folder should be there. Did you download it from this thread?
http://forum.xda-developers.com/viewtopic.php?t=37386&highlight=awizard
Try redownloading it, because the aWizard.cmd is set up to look for the file in the "lib" folder, so try that it should work. Good luck, let me know what happens.
P.S if you want open up the aWizard.cmd or bat file with notepad, press ctrl and f to bring up a search box, and put in enablerapi. Check to see what's the path to the file. If you find this line "lib\cecopy lib\EnableRapi.cab dev:\ >NUL" then hopefully the file being in the wrong place was the problem.
Yup, that's where I got it from -- 1.2b3. If you download the zip file and open it, you'll see that there's no archived folder structure, and the readme doesn't specify how one should be created. What file(s) should show up in the "lib" folder? Maybe I can change the directories and test. Thanks!
EDIT: Yes, that line is in there. So, should I create a directory \lib and put some of the existing files in it? If so, which ones?
masr1979 said:
Which version of aWizard are you using? the lib folder should be there. Did you download it from this thread?
http://forum.xda-developers.com/viewtopic.php?t=37386&highlight=awizard
Try redownloading it, because the aWizard.cmd is set up to look for the file in the "lib" folder, so try that it should work. Good luck, let me know what happens.
Click to expand...
Click to collapse
Hot damn! I made the directory and put all the .dll and .exe files into it, and it appears to have worked!
masr, you rock! Thanks so much!!
Ok glad to hear it bro. For future reference, everything but the aWizard.cmd file should be in the lib folder, though I hope you won't have to use it again for the time being.

initflashfiles.dat -- Help Needed

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.

Cooking a rom...

Hi, I followed the thread: "How to reconstruct a dumped ROM"... (obviously I had, before, did a rom dump!). Now I have a directory named "dump" with several subdirs.
In the step 3) there is written: "After this step you can optionally edit the OS files with the proper tools"... now the question is: what are these proper tools? I searched in the forum, in the other threads but I didn't find anything... My needs are: to delete some programs that are in the rom (for example Pocket Word, Pocket Excel, other..) in order to obtain more space, but to install other tools at the free space.
Thanks in advance for your help....
Great question ! i can't help you , but i wait for answers ....
I asked the same thing the other day, and got an answer(thx again to him).
Actually, I'm doing it right now, as a test I've successfuly dumped and rebuilt lsvw's rom using enhanced imgfs tools batch files, nbdump.bat nbname.nb & nbbuild nbname.nb, now I'm removing files from the rom and maybe add some other, like that quick gps thingy, latest msn(optimized for trinity, removed vga resources), phone pad, and some other thing on my custom extrom.
I had the same doubt as you, but it seems that we're overcomplicating things, you can simply use the file explorer to remove files from that dir, beware of which files you remove/alter.. initflashfiles.dat has some operations to be done after flashing the device(creating folders,renaming files, moving them to startup/start menu/etc folders), I thought that if the file didn't exist on the windows folder, whatever invoques initflashfiles.dat would crash, but it doesn't seem to be the case, I haven't put this to test, but I've found several missing files on the initflashfiles.dat(and a typo, "floder", go figure what it means - lazy/rushed editing IMO), so there seems to be some tolerance to the operations contained in that file.
I won't edit the wiki until I'm 100% sure that what I know is correct, but to sum it up:
dump the files
add/delete files with explorer
edit the registry using rgucomp
edit initflashfiles.dat using the original windows notepad & use an hexeditor to remove the 1st 2 bytes
run NBBuild.bat to create the *.nb file
OSchecker.exe to validate the *.nb file
nbhtool.exe to create the nbh
flash it(I prefer the sd card method)
Code:
rgucomp needs setting _FLATRELEASEDIR environment variable to current directlry like this:
set _FLATRELEASEDIR=.
Dump default.hv/user.hv file to .reg with:
rgucomp.exe -nologo -o default.hv > default.reg, then add line "REGEDIT4" to the beginning of REG file.
Modify the .reg file to your liking, (save it in UTF-16 with CR+LF terminations and a new line at the end of the file) and convert it back to .hv
And don't forget to flash Olipro's Hard SPL before, it may save your device.
"and convert it back to .hv"
http://forum.xda-developers.com/showpost.php?p=1186635&postcount=1
(no wonder I didn't find this info, forum search is almost useless, googled for rgucomp and voilĂ , first result(above) right answer)

Simple WM6.1 ROM kitchen

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.

how to extract cabs from NBH file

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"

Categories

Resources