Related
Hey Guys,
Do you know if anyone has defined what each of the files are in the Extended ROM for the T-Mo Vario? And if so could you point me in the direction.
Thanks,
Alex
You can extract cab files by yourself and look what each of them contains. For extracting cabinet you can use for exapmle Wince cab manager app.
I think the poster means not just file names but what they can do... I can access the ROM but only guess what each one does.
The read me just gives the file names and thats it.
Terran
PS I'm intrested too
i didn't mean to guess what cab does according to its name, but to extract files from each cabinet and look on them.
Most of them includes only some settings to the device's registries.
For example, CAB-Customization-TMCZ-Wizard-01-04-03Oct05 includes 4 files:
CeSettup.dll
CheckFiles.exe
Customize.lst
Platformxxx.reg
By looking into the Platformxxx.reg you can easily see this cab sets MMS and GPRS..
Thanks for the input. Although I believe there is probably some uneeded files in there, my device has been running smoothly, so I will probably just let it be until I hear otherwise.
Cheers
I have followed this tutorial exactly and put the folder it gives me here.
D:\Kitchen\OEM
The program I am trying this with is Advanced_Configuration_Tool_v3_3
The D drive is my second hard drive, however I did all the work to make the folder on my C drive just like the tutorial said. Then copied the folder to D:\Kitchen\OEM
Thus making D:\Kitchen\OEM\Advanced_Configuration_Tool_v3_3
Everytime I cook this ROM it does say Advanced_Configuration_Tool_v3_3 in the CMD however Advanced Configuration does not install when I flash.
What is it that I am doing wrong? I have searched and found nothing about my problem. I have also tried using a pre-made Advanced_Configuration_Tool_v3 from XDA2'S OEM PACK. So I do not think I am making it wrong, instead I am placing it in the wrong location or there is a file I need to edit to include the new folder. Those are just my guesses as this is my first time as a Chef and I have found no information on this particular problem.
Does a file that needs to be edited exist? From what I've gathered, I just turn the cab into a OEM and place that folder inside the folder that I did. Is that correct?
The Kitchen i am using is New Old style kitchen based on Bepe's tools
I have tried to make this as readable as possible, with as many links to what i refer to as possible. If there is anything I can do to explain my problem easier please let me know.
EDIT: I have found Advanced Config in my windows folder, however no shortcut was made in any menu. How do I fix this?
Also can someone tell me what the following means? Most folders in the folder OEM are labeled PACKAGE_Raphael_ then the name of the program. Then theres another folder labeled the same thing except at the end it has _0409
Also theres a folder named 0409
EDIT: I finaly got it to work. I'd like someone to explain why this made it work and explain what I put in my last edit. I got this to work by using package-creator-v2.7.
I dont know about EVK cos i use OsKitchen, anyway give a look here for converting Cab to OEM or EXT http://forum.xda-developers.com/showthread.php?t=525302 its a cool and easy to use.
TheSlimHim said:
I have followed this tutorial exactly and put the folder it gives me here.
D:\Kitchen\OEM
The program I am trying this with is Advanced_Configuration_Tool_v3_3
The D drive is my second hard drive, however I did all the work to make the folder on my C drive just like the tutorial said. Then copied the folder to D:\Kitchen\OEM
Thus making D:\Kitchen\OEM\Advanced_Configuration_Tool_v3_3
Everytime I cook this ROM it does say Advanced_Configuration_Tool_v3_3 in the CMD however Advanced Configuration does not install when I flash.
What is it that I am doing wrong? I have searched and found nothing about my problem. I have also tried using a pre-made Advanced_Configuration_Tool_v3 from XDA2'S OEM PACK. So I do not think I am making it wrong, instead I am placing it in the wrong location or there is a file I need to edit to include the new folder. Those are just my guesses as this is my first time as a Chef and I have found no information on this particular problem.
The Kitchen i am using is New Old style kitchen based on Bepe's tools
I have tried to make this as readable as possible, with as many links to what i refer to as possible. If there is anything I can do to explain my problem easier please let me know.
Click to expand...
Click to collapse
Are you sure that Advanced_Configuration_Tool_v3_3 was not installed?
The default link installation path for this app is the Settings\System folder and not Start menu\Programs.
Goto Start\Settings\System and check if there is an Advanced Config icon there.
dotcompt said:
Are you sure that Advanced_Configuration_Tool_v3_3 was not installed?
The default link installation path for this app is the Settings\System folder and not Start menu\Programs.
Goto Start\Settings\System and check if there is an Advanced Config icon there.
Click to expand...
Click to collapse
I did check in the settings and it is not in any of the tabs, but I did find it in the windows folder. How do I fix this? Like I said I have tried both making my own a pre-made. I'm am going to try what af974 suggested but I do not have high hopes since pre-made OEM did not work. I feel as if I am putting it in the wrong folder.
af974 said:
I dont know about EVK cos i use OsKitchen, anyway give a look here for converting Cab to OEM or EXT http://forum.xda-developers.com/showthread.php?t=525302 its a cool and easy to use.
Click to expand...
Click to collapse
Thank you. I'll give it a try, however it is not the OEM of the Cab that is the problem because I have tried pre-made.
For the EVK based kitchens you NEED an app.dat file in the root of the package you're trying to put in the ROM. That file, gets merged with the rest of the initflashfiles.dat file that can be (usually) found in OEM\0409\OEM_Lang_0409 . If you don't tell the system to copy the shortcut (usually found in the package as a *.lnk) to somewhere on the start menu, then you wont get a shortcut to the app
This is little matter, I know, but its bugging the heck out of me. I have the Telstra T9193, running a custom ROM (Dutty HG V1.8). The problem is that under Phone Identity, it reads the model number as “HTC HD2 T8585.” I know that custom ROMs can do this. I ran through the registry and found 7 keys related to “T8585.” I changed every one of them to “T9193.” However, the last key must be volatile or something, because it resets to “T8585" after each reboot. That key is HKLM\System\Platform\OEMString. Is there anyway around this?
Thanks
I tried the exact same thing a few weeks back, with no luck. I'd just about given up.
It irritates the crap out of me though, I spend too much damned money on this thing to have it slap me in the face and give the model number of a cheaper device...
not sure if anyone still cares, but you can change this by editing the text file in your windows directory called "ModelName.txt"
That'll make that registry change persist. In fact, you don't even need to touch the registry after that since it appears to just update from that file on bootup...
dlphnkiller said:
not sure if anyone still cares, but you can change this by editing the text file in your windows directory called "ModelName.txt"
That'll make that registry change persist. In fact, you don't even need to touch the registry after that since it appears to just update from that file on bootup...
Click to expand...
Click to collapse
Thanks. I found the file, but I can't seem to save any revisions. How do you get around that?
same here... but I know is rom's fault.... so i got used to it....
willwwa said:
Thanks. I found the file, but I can't seem to save any revisions. How do you get around that?
Click to expand...
Click to collapse
Copy the file to another directory. Make your change. Copy (and replace) the file back.
You cannot edit ROM fiiles, but you can hide them with another file by the same name (RAM file).
harolds said:
Copy the file to another directory. Make your change. Copy (and replace) the file back.
You cannot edit ROM fiiles, but you can hide them with another file by the same name (RAM file).
Click to expand...
Click to collapse
Still won't let me do it. Are you doing this on the device or on the computer through activesync or device center?
Thanks.
if your still having trouble getting this file to overwrite, use totalcommander
c_legaspi said:
if your still having trouble getting this file to overwrite, use totalcommander
Click to expand...
Click to collapse
That did it.
Thanks.
ATT ships at least some of their Windows Mobile phones with a pre-populated contact list to a bunch of their services.
It is probably pim.vol which is not in the pda.bin, but is found in the root of the storage system after startup.
The goal is to have a blank contact list after hard reset or burning.
Is this something that can be accomplished in one of the control files during cooking or is it possibly a case of overwriting a default pim.vol that is copied from the extended rom during hard reset? The data does not appear to be in any of the *.rgu, *.xml, initflashfiles.dat, *.provxml files.
This is the last trace of ATT customisation in the current custom rom and it would be nice to get rid of it.
AT&T stores them in the file default_contacts.xml
I don't remember which OEM folder it is in, but you should be able to find it. I just create a blank file with the same name and store it in my personal EXT folder. That way it overwrite the AT&T file.
Thanks for your quick reply.
There is no file named default_contacts.xml in the dump here.
The dump is of the pda.bin only because that is all that is available for that version in vanilla factory form.
When you say "OEM folder" is that in some other area of the rom?
Are you cooking a ROM or what exactly are you trying to do?
In the kitchen, the file is in the OEM\<Device Name>\OEM\409\OperatorPkg folder.
If you can't see the file in your kitchen, make sure you have your file explorer set to show all hidden files as well.
I can assure you that the file is there in my kitchen and I just dumped it from the new Tlit2 ROM. Was also there in the original stock ROM for the Tilt2
I'm cooking a pda.bin which is loaded using USDL Grandprix.
The source is a dump from a Samsung Epix device, not the update file.
This is because it is an Omnia kitchen which does not seem to know everything about the file structure, but is able to cope with the pda.bin in both directions when supplied with an OS.NB from a rom dump.
Exploder is showing all files with hidden and system attributes. attrib.exe was also used to double check for the existence of the file in the entire tree.
There is no OEM directory.
If the OEM directory actually represents another partition on the flash, then which one?
All WinMo devices are similar. Find where all the pplication packages are (EXT) and there shoud be one with all the AT&T customization.
DJGonzo said:
All WinMo devices are similar. Find where all the pplication packages are (EXT) and there shoud be one with all the AT&T customization.
Click to expand...
Click to collapse
Well of course they are. They all start with the same code base from Microsoft.
The point of the question is to find out whether the files are in a partiition that the software has not managed to dump.
Post your stock rom and/or dump please.
plumsauce said:
Well of course they are. They all start with the same code base from Microsoft.
The point of the question is to find out whether the files are in a partiition that the software has not managed to dump.
Click to expand...
Click to collapse
Post a dump then buddy.
What you should do is just look in the \windows folder (you can flash the rom, right?) and then just copy out all of the provxml's and xml's. Look through them, and you'll probably find the one that's buggering up pim.vol. My guess is that it will have a name suggestive of its purpose.
If you have mortscript, then you can just do it automatically with this script:
Code:
XCopy("\Windows\*.provxml","\Temp\",TRUE,TRUE)
XCopy("\Windows\*.xml","\Temp\",TRUE,TRUE)
They'll end up in the temp folder; you can copy them to a pc and then open all of them up and search for the contact names.
Farmer Ted said:
What you should do is just look in the \windows folder (you can flash the rom, right?) and then just copy out all of the provxml's and xml's. Look through them, and you'll probably find the one that's buggering up pim.vol. My guess is that it will have a name suggestive of its purpose.
If you have mortscript, then you can just do it automatically with this script:
Code:
XCopy("\Windows\*.provxml","\Temp\",TRUE,TRUE)
XCopy("\Windows\*.xml","\Temp\",TRUE,TRUE)
They'll end up in the temp folder; you can copy them to a pc and then open all of them up and search for the contact names.
Click to expand...
Click to collapse
Yes, flashed it 20+ times yesterday while debugging
The latest is that there are a couple of mxip*.xml files that appear in the root of the pda storage area. The content has not been looked at yet because it was discovered at the end of the session. But, one of them is mxip_initdb.xml. As you said, "highly suggestive". These files are not part of the dump. So, they must be getting copied or written by a process instead of being static.
update
actually, they are in the dump, just not *.xml, they are *.vol.
binary format, so I guess I'll have to troll around in there using a hex editor.
/update
The device already has a tricky piece of code. It runs a process on cold restarts that rewrites imei* files. The trick is to disable the process. Then, modified imei* files will work properly without being overwritten.
There are also some registry entries that cannot be touched on a flash/restart because there are insufficent permissions at the time. Entries that are known to work after reg unlocking will fail to work at that stage. Touching any one of the restricted entries with a mxip* file will fail everything in the whole file.
DJGonzo said:
Post a dump then buddy.
Click to expand...
Click to collapse
And what would you look for in the dump?
plumsauce said:
And what would you look for in the dump?
Click to expand...
Click to collapse
The stuff you've missed.
indagroove said:
The stuff you've missed.
Click to expand...
Click to collapse
wouldn't it be more productive to at least describe what area to look in?
plumsauce said:
wouldn't it be more productive to at least describe what area to look in?
Click to expand...
Click to collapse
You are saying that your stock device rom is different than most. Other chefs have already described what to look for. You have been offered help to look through the rom and the dump, but you seem to be declining the offers, so never mind.
indagroove said:
You are saying that your stock device rom is different than most. Other chefs have already described what to look for. You have been offered help to look through the rom and the dump, but you seem to be declining the offers, so never mind.
Click to expand...
Click to collapse
I have said that there are differences between devices. That would hardly be surprising. When someone says look for file "x" and it is not there, that would be a difference. It is then fair game to ask if whether it might be stored in one of the other partitions which has not been dumped.
If someone has said that they have checked from the root of the dump and double checked using a second tool, then that assertion is likely valid.
If you have no specific file or files to look for, then so be it.
Hello everybody, I've tried numerous times using the method of trying to get mms to work on my samsung focus with straighttalk. Everytime I go into diagnosis it never has the straighttalk option even though I have the xml saved and placed in the provxml folder like the directions state. Right now I'm currently using Dynamics 2.0 and I really could use someone's help. Please can someone tell me what I'm doing wrong or is there another method I could use to get mms working? Thanks so much in advance.
I have the same issue. I even went to the windowbreak site and it put the windowbreak xml file in the provxml folder that I created, then when I went to the GPRS Manager, neither one of them show up. There is some change that has been made in the way the GPRS Manager finds the XML files, it sure isn't looking in the provxml folder like it did in previous versions of WP7 ROMs.
I tried searching for "Gumi Test Bed, Suwon2G, etc. I think that if I could find the location of those files, I could put the straighttalk xml file in the same location, and then get the MMS to work.
I looked around on the internet for clues on where the Gumi, etc files are located, and all I could find were the instructions for doing what you and I are trying to do. They all say that if we can't find the provxml folder to create it. They also suggest looking for the Gumi, etc. files but I found no posts that showed that anyone has ever found that location.
I posted about this already in the Windows Phone 7 development section of this Focus website.
http://forum.xda-developers.com/showpost.php?p=34809916&postcount=30
wildbilll said:
I have the same issue. I even went to the windowbreak site and it put the windowbreak xml file in the provxml folder that I created, then when I went to the GPRS Manager, neither one of them show up. There is some change that has been made in the way the GPRS Manager finds the XML files, it sure isn't looking in the provxml folder like it did in previous versions of WP7 ROMs.
I tried searching for "Gumi Test Bed, Suwon2G, etc. I think that if I could find the location of those files, I could put the straighttalk xml file in the same location, and then get the MMS to work.
I looked around on the internet for clues on where the Gumi, etc files are located, and all I could find were the instructions for doing what you and I are trying to do. They all say that if we can't find the provxml folder to create it. They also suggest looking for the Gumi, etc. files but I found no posts that showed that anyone has ever found that location.
I posted about this already in the Windows Phone 7 development section of this Focus website.
http://forum.xda-developers.com/showpost.php?p=34809916&postcount=30[/QUOTE
Why is this so difficult to figure out? I wish someone could help us
Click to expand...
Click to collapse
wildbilll said:
I have the same issue. I even went to the windowbreak site and it put the windowbreak xml file in the provxml folder that I created, then when I went to the GPRS Manager, neither one of them show up. There is some change that has been made in the way the GPRS Manager finds the XML files, it sure isn't looking in the provxml folder like it did in previous versions of WP7 ROMs.
I tried searching for "Gumi Test Bed, Suwon2G, etc. I think that if I could find the location of those files, I could put the straighttalk xml file in the same location, and then get the MMS to work.
I looked around on the internet for clues on where the Gumi, etc files are located, and all I could find were the instructions for doing what you and I are trying to do. They all say that if we can't find the provxml folder to create it. They also suggest looking for the Gumi, etc. files but I found no posts that showed that anyone has ever found that location.
I posted about this already in the Windows Phone 7 development section of this Focus website.
http://forum.xda-developers.com/showpost.php?p=34809916&postcount=30
Click to expand...
Click to collapse
Same exact issue, its almost like 7.8 does not see the provxml folder and that the test bed files have been moved. I had the same issue as will in strawmaplez 7.8 rom. To be honest, I am at a lost as to why dropping the straight talk.xml file in to the provxml folder doesn't work because if I am not mistaken most of the 7.8 ROMs out there are forked 7.5 refresh ROMs with the 7.8 leaked ROMs. Unless this is one of the elements from 7.8.
I had the xml working in the strawmaplez rom. I created the provxml folder in the main directory, them I placed the xml file in there. It found it no problem.
wildbilll said:
I had the xml working in the strawmaplez rom. I created the provxml folder in the main directory, them I placed the xml file in there. It found it no problem.
Click to expand...
Click to collapse
Now that I think about it, I am going to revise my statement about strawmaplez I got the ROM to see the provxml folder and the straighttalk.xml, however it didn't work, it still would not allow me to send or download MMS.
flyingdreamz said:
Now that I think about it, I am going to revise my statement about strawmaplez I got the ROM to see the provxml folder and the straighttalk.xml, however it didn't work, it still would not allow me to send or download MMS.
Click to expand...
Click to collapse
a shot in the dark, but have you tried activating autosimsetting in diagnostics? you can toggle it with either 40*047#3 or *#94765#
we don't have straight talk around here, so i don't know if the mms settings are also stored in the sim card or not
Saiyaku said:
a shot in the dark, but have you tried activating autosimsetting in diagnostics? you can toggle it with either 40*047#3 or *#94765#
we don't have straight talk around here, so i don't know if the mms settings are also stored in the sim card or not
Click to expand...
Click to collapse
I can give it a shot, and I don't believe the MMS settings are in the SIM because straight talk requires you to put in a APN and other information.
wildbilll said:
I had the xml working in the strawmaplez rom. I created the provxml folder in the main directory, them I placed the xml file in there. It found it no problem.
Click to expand...
Click to collapse
I have a Focus 1.4 and I flashed the vt2912 W7.8 rom yesterday. So far no major problem besides the MMS for StraightTalk. I downloaded the xml, made a provxml folder in the root directory and put the xml in there. In the GPRS menu I can see StraightTalk and load it. However, MMS still doesn't work after loading it. There was one time I got it to work by rebooting after loading the xml, but since then I haven't been able to reproduce it. Do you have any other tip that may help make it work?