Database Develop

SIMPLE QUESTION

I KNOW SOMETIME I HAVE ANYOING QUESTION SO THIS TIME I HAVE A VERY ONE
WHAT THE POINT OF ALL UPGRADE WHEN YOU CANT SOLVE THE COUNTRY ID PROBLEM AND EACH TIME A NEW UPGRADE COMING OUT WE CANT USING IT BECAUSE IS NO TOOL TO SOLVE THIS PROBLEM
I HOPE SOME SERIOUS ANSWER WILL BE GIVEN

I guess i'll try to answer this one. I can imagine some of the big guys here get sick and tired of ansering the same question over and over... and over... and over... and...
So i'll do my bit and with the very little knowledge i have will try to explain how I fixed it after reading wiki. Maybe some people are just not used to forums and how things work, maybe some people aren't skilled enough with the english language to figure it out themself. Of course, some people are just lazy
1: download the ROM file you want to use. Often rar-ed or zip-ed so extract the .exe file from the compressed file.
2: use winrar to extract the files from the .exe file. (so don't just double click the .exe file, but left button and then extract to "folder name"
3: download this file: ftp://xda:[email protected]/BlueAngel/Tools/MaUpgradeUt_noID.zip
4: extract MaUpgradeUt_noID.zip into the same folder you just extracted the files from the .exe file.
5: run MaUpgradeUt_noID.exe and follow instructions.
Good luck.

Abducted said:
3: download this file: ftp://xda:[email protected]/BlueAngel/Tools/MaUpgradeUt_noID.zip
Click to expand...
Click to collapse
It jump/skip the ID check process

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.

Need original audiopara3.csv!!!

i was messing around with this file to try to increase my voume by just a lil bit, and in the process deleted my backup. if anyone has this file please post it, my volume is now really really quiet and i don't remember how to undo waht i did :{

Use the search function!!!

my bad :{ im a lil stressed out.

FatalCharade said:
i was messing around with this file to try to increase my voume by just a lil bit, and in the process deleted my backup. if anyone has this file please post it, my volume is now really really quiet and i don't remember how to undo waht i did :{
Click to expand...
Click to collapse
http://www.mediafire.com/download.php?3jmyiltg2oq

Hi:
I used this file to increase volume on my Fuze. Seemed to work very well for me.
Hope this helps.

Just delete the file you have there, soft reset, and the original will come back by itself

Thanks for posting the files guys! I'm running RRE, and my mic is way out of whack. I've had many complaints of noise while I am on the line. I'm hoping that restoring my audiopara3.csv file will fix the problem. BUT, I am having serious problems extracting the file in order to synch it to my phone. Is there a trick that I'm missing? I can't even get the file to show up on my desktop after I move it. Should I only be replacing the audiopara3.csv file? Do the other audiopara files have any impact here? TIA guys. I really appreciate your responses.

Not sure if the audiopara has hidden/system attributes but to convert back to stock, del in windows dir and soft reset. The system will revert to stock settings.
BTW if you have one to play with just copy it from the SD to the windows dir using TotalCommander and leave AS alone.

Thanks tyguy. I am using total commander. I went and selected audiopara3.csv, but after I tell the phone to delete, it gives me a warning window:
Could not delete 1 file(s)!
Any idea what could be causing this to happen? From what I've been reading, it should be pretty easy to either overwrite / delete this file, so I don't know why I'm having so much trouble.

Most likely it is in use. Check the TC settings that you are permitted to see/access/delete system files.
Try to rename and delete

I'm running Total Commander/CE v2.51
The only TC settings I have are language settings.
I checked the file attributes for audiopara3.csv, and they are set to 'read only' and 'in ROM'. When I uncheck the read only and save, the next time i check the file properties, the check box reverts back to being selected. I might need to revert back to the stock ROM if I can't get this audio stuff to work.

I don't have the original anymore, but this one really helped, it's loud and no distortions. Unzip first.

squirrel, did you try to rename or move it using TC?
Worked for me all the time.

i get the same error when trying to rename, edit, or move.

I'm happy to be able to report some resolution. What I was able to do was copy the entire zip file to my phone with all the audiopara files that herg posted on the last page. Then, using totalcommander, I was able to extract the files one by one to the windows directory and overwrite the files. Thanks for all of your help guys! Everyone who had to put up with the static while talking to me sincerly appreciates it!

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"

I Need Helping Making A Custom update.zip

So I guess my question is, "Can anyone help me?"
I used custom ringtones, and I don't like using them from the SD card, it creates lag, takes longer to load the ringtone, etc, so I keep them on my /system/media folder. Normally to accomplish this, when I install a new ROM update, I edit it and resign it, with my media folder, rather than the ROM's.
My predicament however, is that I don't know how to change the file structure for the update, I know there are files in the update that say, this and this folder exist, where this goes, etc. This is what I don't know how to do.
All I need the update to do is contain the media (/system/media) folder, so I can just add all my ringtones and notifications to this update, and flash it after I flash whatever update/rom, etc, instead of always having to be at my computer to create a custom version of every rom I use.
Could anyone please care to help? I'd be ever grateful.

You can use the attached file.
Just edit the files in the ROM
zip it
put the zipped ROM in the same folder as the attached files
run sign.bat
FLASH

ID# said:
You can use the attached file.
Just edit the files in the ROM
zip it
put the zipped ROM in the same folder as the attached files
run sign.bat
FLASH
Click to expand...
Click to collapse
is this just to be used for signing? i already know how to sign files. i need someone to edit w/e files are inside the rom that tell its structure (this folder exists, and gets flashed here, this folder goes here, etc). i cant just take a cm rom and delete everything i dont need then flash it. it will get errors in recovery.

Make a folder called media in the root of your update, and create the proper descending folders in media (i.e. audio/ringtones, etc). Place your notifications/ringtones/alarms etc in the proper folders. (I am sure you understand this already)
Open your update-script file for the update and add the line
Code:
copy_dir PACKAGE:media SYSTEM:media
That should do it.
Note that if in the update-script you already have an entire system folder being copied over via
Code:
copy_dir PACKAGE:system SYSTEM:
then you need only add the folder media to the folder /system in the update.

cloverdale said:
Make a folder called media in the root of your update, and create the proper descending folders in media (i.e. audio/ringtones, etc). Place your notifications/ringtones/alarms etc in the proper folders. (I am sure you understand this already)
Open your update-script file for the update and add the line
Code:
copy_dir PACKAGE:media SYSTEM:media
That should do it.
Note that if in the update-script you already have an entire system folder being copied over via
Code:
copy_dir PACKAGE:system SYSTEM:
then you need only add the folder media to the folder /system in the update.
Click to expand...
Click to collapse
Thanks man, but my buddy actually just helped me out with this, but yeah thats exactly what I needed to know. Thanks a ton mate