firstly, i am trying to flash the rom following the guide from romkitchen.
after using dos command, i want to double check whether i set the operator correctly.
so i use er 2003 edit for fast checking
NK.nbf and radio.nbf have no problem
except that when i open MS_.nbf, with the correct password type in, it just prompt me
error access image.
i checked the setting is correct.
I want to confirm whether this error is normal
please advice
thanks
keith
download he patched ER2003Edit from the thread mentioned in WIKI.
The original had this problem if you have file type = auto detect in the file open dialog. Choose Extended Rom and it will work.
dont use the romkitchen to get roms for xda2 devices it's ONLY xda1 roms which can be made in the romkitchens
if i dont follow romkitchens, then who can give me a brief explanation or can say easy way to upgrade from XDA 2 to WM2003SE
I used to upgrade my ROM before, but due to people giving a lot of ways to do it, i am getting confuse.
need someone to compile the overall documentation
what i did last time
1. unlock all files and change the operator name to O2
2. put or remove cab files into my extROM, including editing the config.txt
3. flash it
after reading so much, i am still thinking with the genuine WM2003SE, do i need to edit a lot?
i believe i need to change the operator name to O2.
as i am from Asian, i also believe i need to put in Asian Cab, so that my phone, will display local telco.
also when u say genuine WM2003SE, does it means is standard package ?
thanks for advice again
@Rudegar : I hope/think he means following the instructions in the WIKI HimalayaRomkitchen. which is maybe a confusing name, but a good starting point to learn about upgrading (At least that is my humble opinion)
the reason why you are getting this message is becaz after you click on file open rom image window pops up over there at the ottom thers an option giving different file names make sure you have WM2003 Extended ROM (ms_.nbf) selected there to open ms_.nbf or accordingly.
regards
jeetz
yeah thanks, i got it done
appreciated.
I can't install xml files
Please tell me? how i can do that
You cannot install xml files Think about it - its just a text inside...
edit: XML stands for http://en.wikipedia.org/wiki/XML
it's related to html as internet pages it's not a bin file which one can install
XML file is an input to another program and that would read the content and install whatever needs to be.
i have the same problem!!
The XML format files opend by document as defult, I cant install any XML format files.
Also in pocket PC the explorer is the defult to open XML files.
ad2master: Are you dumb, or just cannot read? Everything is explained above. I would just add, that XML is TXT, or INI file. It's just text prepared for a program to read.
When you got such a file from and what makes you think, that you can install it?
i think he's meaning is to load info in OMA xml foramat files that wince supports
like registery info ,network setting info,or file operation info etc.
We don't know it. Anyway for future reference: If you have problems with "XML file installation" provide us with example, we will be able to check what it contains.
Good news and Bad
BAD news = (jakubd) is a jack *EDITED*.
GOOD news = I have a fix.
WARNING = using this fix may make you kick yourself. I did.
PROBLEM = When you open the compressed file you see the content, some files and the important SETUP.XML Like years of Windows use has taught us, the SETUP file is the only one we need. It's like magic, we click and the preprogrammed file will do the rest. BUT all you get is TEXT. Thats crap.
CAUSE = You have WinRAR installed on your desktop PC, Don't you??
See WinRAR is telling your desktop computer that your .CAB file is a compressed .RAR file. It is but we will not get in to that. Confusion sucks.
FIX = You don't have to do step 1. but I recommend you do.
1. (on your desktop computer) go to START and to ALL PROGRAMS and open WinRAR. That was easy. Now click on OPTIONS and go down to click on SETTINGS (or just hit (CTRL + S) Click on tab INTEGRATION. On the left UNCHECK the BOX marked CAB. Say my name over and over while dancing on one foot.
2. Take the file you are installing (STILL COMPRESSED) and put it on your device. Use your FILE EXPLORER in your device to EXECUTE the still compressed .CAB (note: if you did not do step 1 the file will LOOK like a .RAR on your PC but a .CAB on your Phone/Device.)
SHORT ANSWER = do NOT uncompress the file on your Desktop PC. Just take the file just as it was when you downloaded it and put it on your Phone/Device. Use your Phone/Device file explorer to locate the file and execute it.
NOW = Kick your own *EDITED*
So going back to the very begining - you never ever install XMLs. Good explanation DJ_SirG - I would never guess that anybody at any occasion would try to decompress a CAB.
But as usual I'm asking myself - how many times people will as on forums "how to install xml file"... At least I have a place to point them to. Thanks!
DJ_SirG
Thank You very much for helping, problems solved now.
jakubd
I am just asking for help, you can help others if you want, or just keep your self away with your huge experience.
ad2master: I'm doing my best to help, but if somebody asks you "how to do X" and the person receives answer "you don't because it makes no sense" and then another one asks the same thing multiple times in multiple places instead of thinking for a while you can get irritated. Also when people ask hundreds of times the same question (like where is reset button) that are clearly explained in Wiki or were answered many times here, you can also get irritated and more over - they get irritated when you point the to the wiki or suggest HR.
And of course sometimes you can miss the point (like here) because of lack of information from the other side. I would never guessed that smb could first decompress a CAB file to install it and you need to know this part to understand the whole story with "xml" installation problem. It's like a person calling Ford support and asking "my car doesn't go" just to find out, that it run out of gas - it's so obvious, that you need fuel, they you don;t even take it into account. Same with CAB - it's so dead obvious to me that you don't decompress it before installation, that I would never take it into account.
So if you want precise and effective answer, check the wiki, search, use google, if nothing comes out and you think your are the first in the world with this specific problem: ask. But because you think you are so special, please try to be specific: give all the details that might be needed. answer all the questions that might help other people solve your problem. There is always somebody that might be able/want to help you, but you also have to help him.
I think The miss communication is when we would click on the .cab file to download it once it showed up on our desktop, it was a .rar. Like the file name was changed. So if you download XDA.CAB once the file was on your desktop it said XDA.RAR. So you click on it to find your .CAB file just to find .XML and let the confusion began.... Thanks for your help guy's and I hope this helps you. If it do, reply back with a quick word so we know the post is getting used and not deleted...
DJ_SirG said:
Good news and Bad
BAD news = (jakubd) is a jack *EDITED*.
GOOD news = I have a fix.
WARNING = using this fix may make you kick yourself. I did.
PROBLEM = When you open the compressed file you see the content, some files and the important SETUP.XML Like years of Windows use has taught us, the SETUP file is the only one we need. It's like magic, we click and the preprogrammed file will do the rest. BUT all you get is TEXT. Thats crap.
CAUSE = You have WinRAR installed on your desktop PC, Don't you??
See WinRAR is telling your desktop computer that your .CAB file is a compressed .RAR file. It is but we will not get in to that. Confusion sucks.
FIX = You don't have to do step 1. but I recommend you do.
1. (on your desktop computer) go to START and to ALL PROGRAMS and open WinRAR. That was easy. Now click on OPTIONS and go down to click on SETTINGS (or just hit (CTRL + S) Click on tab INTEGRATION. On the left UNCHECK the BOX marked CAB. Say my name over and over while dancing on one foot.
2. Take the file you are installing (STILL COMPRESSED) and put it on your device. Use your FILE EXPLORER in your device to EXECUTE the still compressed .CAB (note: if you did not do step 1 the file will LOOK like a .RAR on your PC but a .CAB on your Phone/Device.)
SHORT ANSWER = do NOT uncompress the file on your Desktop PC. Just take the file just as it was when you downloaded it and put it on your Phone/Device. Use your Phone/Device file explorer to locate the file and execute it.
NOW = Kick your own *EDITED*
Click to expand...
Click to collapse
I Must say to all you.."A-Holes" That Spitted on us for asking stupid questions like that you guys bashing us this guy actually knew what we were talking about and helped us why you guy stood back and did nothing Grats buddy you answered my question. and it just goes to show not everyone knows everything about computers.
The only reason I found this fix was because I ran out of hair to pull out.
We are not all rocket scientists
I too had no idea how to install a .cab file with a setup xml file. Once the one gentlemen said to install the file with the file explorer it literally took as long as it took to open that file. I am really disappointed that I had a question and in order to get it answered I have to go through the abuse of being called names and being cursed at. I get enough of that at home. If you are going to run a web site that is a computer forum, you can safely assume that most of us do not have your knowledge; otherwise, we would have the web site. Nonetheless, thank you for your web site. My program is now installed. Merry Christmas, Lindy Wise
THANKYOU thankyou thankyou
A sincere thank you...
DJ_SirG said:
The only reason I found this fix was because I ran out of hair to pull out.
Click to expand...
Click to collapse
You have no idea how much time I saved with guys like you in this forum...
Currently, I am out of pennies; as such , could not give you a donation for now...
( that's why I'm reviving my xdaIIs that runs wm2003 to run wm6.5 ... so that I can give it to my disappointed son as a present... ) cant afford a sonyPSP.
When I'm back on my feet, I shall not forget those who helped me...
Thank you... and may your hair grow back Fast & Furious ...
Honestdad
I have read all the previous messages but cannot get the answer im looking for. I have a folder which contains text files and a xml file. I do not see any setup file for me to click on.
but as all the previous posters, you probably didn't download a folder, but an archive and you extracted it to see the folder and its contents. that was the mistake. the .cab file appears like an archive on the pc, but is the extractable setup for the phone. try it again by extracting nothing and copy the file to the phone and start it there.
While Cooking for LEO, many CABs has a self registering Dlls which runs fine from the cab file but when you try to convert the cab to OEM package, this dll looses it self registering functionality because there wasn't any code grabbed to the OEM package that tells the Kitchen to mark it for self registering.
Is there any solution for such a case?
To Make it clear:
I'm trying to cook "MOBiDIV_PrayerTimes_Diamond2_B15_TSD_Jun1.Cab " but the problem with the included "fileosp.dll" which requires self registration that is been automatic done while installing the .CAB
So, is there any kind of solution to do it while COOKING the ROM?
Use kheb to grab all the registry keys that are installed during the cab install/reset process. Then put them in your package. Or just search for the keys. We're talking the HKCR\clsid keys, aren't we? They're usually easy enough to find, if you dump and search your registry.
Farmer Ted said:
Use kheb to grab all the registry keys that are installed during the cab install/reset process. Then put them in your package. Or just search for the keys. We're talking the HKCR\clsid keys, aren't we? They're usually easy enough to find, if you dump and search your registry.
Click to expand...
Click to collapse
Thanks for your idea.
I did already and got all clsid and inject them in the package but still the same.
It seems emulator is behaving differently than actual device, what you think?
InCities.cdb
After ROM Booting, i re-install the Original Application, it works.
This is normal because the original application is doing something with InCities.cdb file.
I knew that my registry entries is correct because:
1- I checked everything in registry before and after my modification.
2- I checked everything before and after Original Program Change.
changes are identical
BUT
BUT
WHEN I PLAYED WITH (CHANGED) THE REGISTRY ENTRIES:
FROM
[HKEY_LOCAL_MACHINE\Software\Apps\Shared]
"\\Windows\\InCities.cdb"=dword:00000001
TO
[HKEY_LOCAL_MACHINE\Software\Apps\Shared]
"\\Windows\\InCities111111111.cdb"=dword:00000001
then copied another file as the same name
then tried to change it back to original, THE APPLICATION FAILED.......................................
So, Here is the trick but i don't know how to fix.
HTC new drivers Mango Rom will not allow old system apps to get root access, like TouchXplorer does not work on 4.xx above roms.So these days i found a way to make my custom rom based on htc 5.10 rom work perfect with old system apps.
Step 1
get an old htc offical rom, like 1.xx, get a htc offical 4.0x rom.dump them.copy HTCFileUtility.dll and HTCRegUtility.dll from 1.xx rom dump, and HTCProvisionDrv.dll from 4.0x rom dump.(they are both in OEM\HTC_AppDrivers)
Step 2
use the three files(modules) copied above to replace your custom rom, if u are using 4.0x rom as your base skip step 3.
Step 3
replace the ApprovedlistDB.db(in OEM\CSConn_DB) by my uploaded one.
Step 4
use OSBuilder to relloc your modules, or relloc them by yourself(just like me, cause OSBuilder is hard for me to understand how to use it)
Step 5
package your custom rom, and flash it, then you will get a new rom that TouchXplorer and RegistryEditor(this works much faster than before) can work like charm
Step 6
thx DFT bring us HSPL & Julien Schapman bring us magic system tools!
remarkable，thx 4 sharing
Would be awesome if there was a way to restore the old versions in-place without re-flashing the whole phone. CAB maybe? I don't think you can overwrite ROM modules any other way. I've avoided installing the latest HTC updates because I've written a couple apps that rely on the File and Reg DLLs, but that also means I don't have things like the Connected Media app working.
GoodDayToDie said:
Would be awesome if there was a way to restore the old versions in-place without re-flashing the whole phone. CAB maybe? I don't think you can overwrite ROM modules any other way. I've avoided installing the latest HTC updates because I've written a couple apps that rely on the File and Reg DLLs, but that also means I don't have things like the Connected Media app working.
Click to expand...
Click to collapse
if you can put files in \windows folder, and change reg key under HKLM\Drivers\BuiltIn\, you can make it works without flash a rom.
cause we could get drivers from htc orginal update cabs then rename them to put into \windows folder and change reg key to make these drivers load, no need to replace.
Well, if you care about this at all, you're already interop-unlocked.
If you're interop-unlocked, then you can set registry values and move files (using provxml).
So... yes, this sounds pretty exciting. Having the official HTC updates but still being able to use TouchXplorer would be awesome.
So, would it just be a matter of copying the old files under new names to the Windows folder and changing the "Dll" value of "HKLM\Drivers\BuiltIn\HTCFileUtility" and such? Or would something need to be done with the DB as well? I'm not sure if that can be changed on a running device.
Tell me what needs to be done and I'll create a tool to do it.
GoodDayToDie said:
Well, if you care about this at all, you're already interop-unlocked.
If you're interop-unlocked, then you can set registry values and move files (using provxml).
So... yes, this sounds pretty exciting. Having the official HTC updates but still being able to use TouchXplorer would be awesome.
So, would it just be a matter of copying the old files under new names to the Windows folder and changing the "Dll" value of "HKLM\Drivers\BuiltIn\HTCFileUtility" and such? Or would something need to be done with the DB as well? I'm not sure if that can be changed on a running device.
Tell me what needs to be done and I'll create a tool to do it.
Click to expand...
Click to collapse
you are on the way, m8.
get drivers from htc update cab, then u'll get files not modules
Code:
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\HTCFileUtility]
"Dll"="HTCFileUtility_new.dll"
if you make new HTCFileUtility.dll work, you will have enough power to replace files.
then make your new reg drivers work.
Code:
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\HTCRegUtility]
"Dll"="HTCRegUtility_new.dll"
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\HTCProvisionDrv]
"Dll"="HTCProvisionDrv_new.dll"
thanks for sharing, waiting for this method for along time.
Thanks ted. I'll update my backup (so I can roll back to working version if I need to) and go hunt down those files.
I don't think I'll need to overwrite HTCProvisionDrv, the current version seems to work just fine. In fact, if it doesn't, there won't be any way to do the overwrite. It's just the registry and filesystem drivers that were broken.
Now I'm wondering what the other HTC drivers do. There's a specific one for Connection Setup and for HTC YouTube, plus drivers for "HTCBgService" (a way to run tasks in the background, I assume) and "HTCVersionUtility" (probably not useful, but maybe?). It would be interesting to examine the APIs of those.
For that matter, it would be interesting to examine the API of things like the provision driver. It appears to have full permissions, but the DMXMLCOM.DLL library used to interface with it has a fairly limited API (no way to get the result of a provxml query, for example). Talking directly to the driver may work better.
Anyhow, off to find the correct CAB!
Sounds pretty awesome! New drivers in Mango with support for old apps - cool! Really hoping for a tool to do this, i've never cooked my own ROM, I solely rely on the experts for this
Hi Ted (or anybody), do you knwo where I can get the pre-Mango HTC cabs? All the cabs I've been able to find are for the Mango HTC updates, and have the wrong versions of the files.
EDIT: Found some that might work. They aren't labeled but the datestamp is from January.
Pretty sure xboxmod has a thread with all the official cabs linked somewhere on xda.
Sent from my HD7 T9292 using XDA Windows Phone 7 App
Thanks. I'll see if the files I found work. They're old enough, and are supposedly from an official update, but it's hard to be sure. Their file sizes are different from the ones in the latest update, but not by much.
The real trick, of course, is seeing whether I can install my own drivers at all or not. I know I can place files and change registry values, we just have to see if the phone will use them.
ted973 said:
HTC new drivers Mango Rom will not allow old system apps to get root access, like TouchXplorer does not work on 4.xx above roms.So these days i found a way to make my custom rom based on htc 5.10 rom work perfect with old system apps.
...
Click to expand...
Click to collapse
Any chance you would release your custom ROM? Can you make one for Trophy, only one using 5.10 version are Ansar's, your's sounds nicer!
Well, I didn't find Xboxmod's cabs, so I'm using the ones linked in Heathcliff74's thread. Unfortunately all the reliable ones are pretty recent, so I don't think they'll work. Last resort I'll try pulling them off my phone's filesystem, but that gets weird with modules.
I've successfully broken TouchXplorer and Connection Setup, and then fixed them again. I think this constitutes progress. Next step: try some older drivers, and see if I can install them without breaking anything. If so, then I'll try updating my phone with the official HTC update, and see if it's still working. If so, I'll clean up the XAP a little and publish.
EDIT: Additional discovery: Connection Setup relies on HTCFileUtility.dll. Installing the broken FileUtility driver causes Connection Setup to complain that there's no database installed on the phone, and then quit. Now I *really* wonder what HTCConnectionSetUp.dll is used for. Also, I'm not gonna touch the Provision driver unless I have to; this testing takes long enough when every step requires a reboot. If I mess up the provision driver I'll probably need to restore the phone backup.
EDIT2: The new HTCConnectionSetUp.dll driver is several times the size of the old one, but it doesn't seem to change how Connection Setup works when I use it. In particular, it still processes CustClear.provxml.
EDIT3: Still not working, even with very old drivers (January). I have a few possible ideas as to why, but it looks like I may need to run this with drivers from my "working" phone instead of from a CAB.
OK, I haven't been able to get this working with any of the DLLs I've been able to pull from CABs, and the DLL modules on the filesystem can't be moved, renamed, or read (ERROR_ACCESS_DENIED when I try to read one using ComFileRW.dll).
I either need the right CAB, the special sauce to make it work with the wrong CAB, or a way to extract those modules as files. I suspect it's at least partially a "special sauce" situation - the errors I get when I try using different drivers are not the same as the errors I get with the official update that breaks third-party apps trying to use those drivers.
I would *REALLY* appreciate some assistance with this. It has the potential to provide an easier interop-unlock (if the official update doesn't reset the driver DLL paths) and even if that doesn't work, it would be a big step forward for HTC homebrew. However, I know nothing about ROM assembly - not even how to extract a file from a shipped ROM. I'm trying to learn, but if somebody wants to point me in the right direction that would be a big help.
EDIT: I managed to extract the ROM module (took some doing; HTCRIE will crash at the drop of a hat if you aren't careful). I can't rebuild the file though - recmod doesn't seem to like it.
if you can use Provxml i have some way to replace module in \Windows dir
1.
<wap-provisioningdoc>
<characteristic type="Registry">
<characteristic type="HKLM\System\Explorer\Shell Folders">
<parm name="My Ringtones" value="\Windows" datatype="string" />
</characteristic>
</characteristic>
</wap-provisioningdoc>
Click to expand...
Click to collapse
copy this to notepad and save as File.Provxml file
2.Install DiagProvXMLv0.91
3.Use Chevron Ringtone Installer to copy .Provxml to your phone
4.Run DiagProvXML and go to " File Operations" tab , select Copy (to isoStore)
in Source Path use
\My Documents\My Ringtones\
Click to expand...
Click to collapse
and Source File use
File.Provxml
Click to expand...
Click to collapse
,,
Press (+) to save ,,
and now go to provxml tab and Press Publish (disk icon) ,,
go to iso store tab and Hold press at File and select Excute ,,
restart your phone and now you can use Chevron Ringtone installer to Add File you need to \Windows\ (sure as module , and defaultcert.dat for cab sender)
Best Regard
PPJD
@peeks20: Thanks (sort of) but your method is both overly complicated and doesn't solve the actual problem. If you're already interop-unlocked (and you have to be, to use DiagProvXML), then it's trivial to write a small app that just uses DMXMLCOM.dll to process whatever provxml commands you want. That includes copying files to the Windows directory.
The problem is that I'm not sure what file to copy, and I'm not sure it'll work even if I have the right file (I've tried multiple official files from various update CABs, and none of them have worked). There's probably either a version-matching function that's getting in the way, or a database somewhere that needs to register the new drivers (beyind just changing the path in the Dll value in the registry). Heck, maybe it's both. The point is, it doesn't work.
Now, if there's something about deploying the files using the Chevron ringtone installer instead of using pvroxml that will make all the difference, that would be cool. I really doubt it, though. The files copy just fine, and can be accessed and opened. They jut don't actually work. I get the same errors as if I point the Dll path in the registry to completely bogus paths ("Dll"="ThisFileDoesNotExist.dll").
GoodDayToDie said:
@peeks20: Thanks (sort of) but your method is both overly complicated and doesn't solve the actual problem. If you're already interop-unlocked (and you have to be, to use DiagProvXML), then it's trivial to write a small app that just uses DMXMLCOM.dll to process whatever provxml commands you want. That includes copying files to the Windows directory.
The problem is that I'm not sure what file to copy, and I'm not sure it'll work even if I have the right file (I've tried multiple official files from various update CABs, and none of them have worked). There's probably either a version-matching function that's getting in the way, or a database somewhere that needs to register the new drivers (beyind just changing the path in the Dll value in the registry). Heck, maybe it's both. The point is, it doesn't work.
Now, if there's something about deploying the files using the Chevron ringtone installer instead of using pvroxml that will make all the difference, that would be cool. I really doubt it, though. The files copy just fine, and can be accessed and opened. They jut don't actually work. I get the same errors as if I point the Dll path in the registry to completely bogus paths ("Dll"="ThisFileDoesNotExist.dll").
Click to expand...
Click to collapse
i uploaded HTC Appdrivers from Mozart 1.32 & 4.06 update cabs, maybe you can continue your test
Thanks, I'll give them a try. However, I've got to ask - what is Approvedlist.db, and if you have to modify it for a custom ROM, would I also need to modify it for this app? I can't shake the feeling that there's more to installing a driver than just changing a registry value.
GoodDayToDie said:
Thanks, I'll give them a try. However, I've got to ask - what is Approvedlist.db, and if you have to modify it for a custom ROM, would I also need to modify it for this app? I can't shake the feeling that there's more to installing a driver than just changing a registry value.
Click to expand...
Click to collapse
hard for me to explain this in english, this file decides which Registry keys allow apps to change.its format changed in 5.xx rom, so RegistryEditor v1.2.0.0 didn't work on these roms, we need to use old version HTCRegUtility & HTCProvisionDrv and old format ApprovedlistDB.db to make htc apps and 3rd Registry tools works perfect, that's why you need to replace ApprovedlistDB.db.