Related
Is there a way to override a rom file?
I found welcomehead.192.png the windows boot screen, not the initial imate one, the blue windows one, ive edited the png, but cant replace the file as it is in rom, any suggestions as how to do this? or is it wait until someone works out how to open the nbf file and then change that way?
Theres nothing in the registry that i can find that points to this file
anyone?
just overwrite the file with the same name. ignore errors
1. As sama says, just use a proper file explorer (Resco/Total) to overwrite the ROM file. If you delete the new file the old one will still be there in ROM.
2. The ROMs can be decoded, you can change the ROM then flash it. This is not a safe thing to do, and is complicated. However, this is a total waste of time (hours) for a 100KB image file unless you really can't afford 100KB in your Programs Memory.
3. If you want, you can also change the "initial imate one" too. Buzz has the tools and instructions on his site (http://buzzdev.net). This will be a flash job, but takes up no space and a hard reset won't wipe it.
Hope this helps.
Any ideas how to change the boot image on the prophet?
changing boot image
Got this info from PPCSG - so all credit goes to them (especially farbird). This changes the 2nd splash screen (the one with the windows logo on the blue background). The HTC/Dopod splash screen which appears after every reset is still there.
1) copy the welcome96.png file to your desktop from ppc. edit it... do not change the dimensions.
2) save that edited file as 'welcomehead.961.png' and copy it into your ppc /windows folder.
3) open total commander in ppc. go to windows folder, tap on hold on the original welcomehead.96.png, click properties, uncheck all the boxes under attributes. select ok.
4) total commander will refresh the directory, rename it now to 'welcomehead.962.png'. After that look for your edited file copied from the pc ie welcomehead.961.png.. rename it to welcomehead.96.png. after that, tap and hold and click on properties. check the box that says " read only, hidden, system "
once that is done, do a soft reboot. u should be able to see your new bootup screen after the rom version is up.
There is another way using activesync, but it didn't work for me as it gives me a write-protect error.
Do a search here @ xda-dev, u shld get the same info...
Hi,
this does not work on GER Vodafone ROM 2.15.3.26 cause welcome.96.png is in the rom part and not deletable.
funnysurf said:
Hi,
this does not work on GER Vodafone ROM 2.15.3.26 cause welcome.96.png is in the rom part and not deletable.
Click to expand...
Click to collapse
Yes, that file is a ROM file and cannot be deleted. BUT if you use TotalCommander, you can rename that file to something else, rename your new splash image file to welcome.96.png, copy it to your windows folder and set its attributes to read only, system, & hidden. AND the changes will be permanent. Try it.
The reason it being a ROM file is why I was unable to copy & paste using the activesync method. But the way I did it works. Make sure you use Total Commander & not resco explorer or the built-in file explorer
krale said:
Any ideas how to change the boot image on the prophet?
Click to expand...
Click to collapse
this feature will also add soon in JAFWM, i think is a very usefull option.
Putra said:
funnysurf said:
Hi,
this does not work on GER Vodafone ROM 2.15.3.26 cause welcome.96.png is in the rom part and not deletable.
Click to expand...
Click to collapse
Yes, that file is a ROM file and cannot be deleted. BUT if you use TotalCommander, you can rename that file to something else, rename your new splash image file to welcome.96.png, copy it to your windows folder and set its attributes to read only, system, & hidden. AND the changes will be permanent. Try it.
The reason it being a ROM file is why I was unable to copy & paste using the activesync method. But the way I did it works. Make sure you use Total Commander & not resco explorer or the built-in file explorer
Click to expand...
Click to collapse
Hi Pruta,
O.K., now I was able to rename welcome.96.png and replaced it with my PNG.
Softreset... Sh*t, the 'old' welcome.96.png was shown. O.K., my device wants war...it gets war .
I was able to DELETE the old (original) welcome.96.png.
Softreset... Aaaaahhhhh nothing changed!
O.K. continued search. I found a file named welcomehead.96.png, that is the same image than the original welcome.96.png.
The only prob is, I'm NOT able to rename or delete/replace it.
Are there anybody that also use the Vodafone rom and can test to change the boot image???
Attached file is welcomehead.96.png
If you can change the attributes to exclude System, and Read-Only, it should be able to change/remove it.
Hi krale,
nope. It's not possible to change the attributes. See attached MPG.
I was able to do it with total commander...
here is the link
http://www.ppcsg.com/index.php?showtopic=71471&st=40#
thanks for the credit, Putra.
Appreciated.
Do not delete, but overwrite
@farbird: Sure, bro - after all it was your post @ PPCSG that helped me change the splash screen.
Important: do no delete the welcomehead file as it is ROM file, and it will automatically be created again. The trick is to overwrite the file with another file but with EXACTLY the same name and attributes (except ROM). So Windows will not try to create the file again.
After you change the attributes of the original welcomehead file, NO NEED to check if it has changed - Total Commander will show it as NOT changed (meaning all the check marks are still present).
Just go ahead and rename that file, then rename your splash image file to welcomehead.96.png, and set the attributes, and it should work.
I used this trick to "delete" a useless movie file: 1-nature_15fps.mp4 (274K, I think). I created an empty txt file called 1-nature_15fps.txt (0B), copied into the windows folder, performed the trick, and now I have a 1-nature_15fps.mp4 file which is 0 bytes! Just a little experiment, which may come in handy if you really need the space.
Hope the above explains things a little.
HELP!! How to change 1st Splash and HTC splash
Hi EveryBody
i've Imate JamIN
batterystatus overclocked to 286MHz
Rom: PDAVIET 4.0.0.4 (totally stable)
i know how to change the 2nd Splash (concerned of Windows)
but i dont know how to change the 1st Splash (that of Imate or Qtek) OR the Splash concerned of white backgrounded HTC Innovation...
Can anybody help me in full details, step by step and straight commands
NB. I still dont know what is CID, IPL , SPL... (please let me understand these terms)
Welcome ksadek
read the xda wiki to find out what CID IPL and SPL are
I tried to copy a bunch of .dll files from \Windows
I encountered a couple of problems doing that:
1. Some files are not shown on the PC in Windows Explorer though I've enabled viewing hidden and system files. However, these files are shown on the device in Resco Explorer, but can't be copied to e.g. \Storage Card
2. Some files are shown on PC in Windows Explorer but are in use and therefore can't be copied
What are the tricks to back up those files?
PS: My device (S710 Vox) is unlocked using M$ Security Manager
No tricks.
If you bothered to learn anything about your device you would know that these files are part of ROM and can not be copied out.
Don't mean to be rude but this was asked and answered many times before. Do a search on "ROM dump"
Yeah stupid me...
Dumped the ROM and got the files I want
(http://wiki.xda-developers.com/index.php?pagename=Vox_HowToDumpRom)
Actually I can't find coredll.dll in my ROM dump.
I used viewimgfs.exe to dump Part02. I can't use viewimgfs.exe on Part00 and Part01.
Is there another tool which can retrieve coredll.dll and perhaps other missing files?
Another question: can the S710 be flashed by using imgfs tools v1.82 to create the image(s) and a generic HTC flash tool?
Hello,
I am trying to copy a file (from my smartphone to SD card), which have a 'ROM' attribute set and... it is impossible - acces denied is showed (even in Resco Explorer, Total Commander). I can't even change that attribute.
Please help me to find any solution
Best greetings,
RA
You should be able to extract files from the ROM file on your PC thanks to the tools provided in one of the sticky about ROMs modifications.
Unfortunatelly...
Cricri said:
You should be able to extract files from the ROM file on your PC thanks to the tools provided in one of the sticky about ROMs modifications.
Click to expand...
Click to collapse
I have extracted an 'nb' file from my ROM file, but WinImage can't open it ("not FAT16, FAT32 file"). It is WM6 image file, what tools to open this 'nb' file?
Best greetings,
RA
I, too, am trying to find a way to copy some ROM attributed files.
Ultimately, I am trying to move/copy some apps from one smartphone (WM5) to another (WM6). Is there a way to copy them to a zip file and move the files that way or maybe even using a backup copy (i.e. using Sprite Backup?) and restoring to a different phone?
Any help or direction would be appreciated. If there is another thread out there, please be sure to point me to it since searching brings up a lot of different threads.
u need to extract the rom.
Funny, but you make it sound so easy... ;-) I've been searching to figure out how to do that and found some instructions I'm hoping I can follow for the one phone, but not sure it it will apply to the old phone (WM5). If I do manage to dump the ROM, where does it go and does it extract the files in cab format for easy upload?
Update: I found a file extractor at http://pdaphonehome.com/forums/ppc-6700-xv6700/56057-6700-rom-dump.html which may have originally come from Buzz... (thanks Buzz!)? so now I have all the files and modules off the old phone, but am running into some issues installing. I can transfer the files indirectly, and can find the specific application file, but when trying to run the app, it tells me that it's still missing files to enable the program. Any ideas on how to determine which files they might be or how to install the files via Activesync?
I tried to keep the title as descriptive and short as possible, I hope it makes sense
I picked up the kitchen of nhathoa (a retired Topaz cook) hoping to get it customized to make it exactly the way I want but I'm running into some issues.
Long story short, I'm using Ervius Visual Kitchen (1.8.2) and I noticed that the EXT packages I added end up leaving two copies of the files, a copy under \windows\ and another one in the places I specified using app.dat using:
Code:
Directory("\Program Files\bla\"):-File("bla.exe","\Windows\bla.exe")
Is there some way to get rid of the copy under \Windows\ ??
I know that I could simply leave everything there and discard the app.dat files but I would really prefer having everything organized properly (I have a bit of an OCD when it comes to organizing everything neatly ).
I'm pretty sure that this is a rather simple and noobish issue but I couldn't find anything relevant by searching and I took a look at some ext packages by various cooks and noticed the same behaviour.
MusikMonk said:
I tried to keep the title as descriptive and short as possible, I hope it makes sense
I picked up the kitchen of nhathoa (a retired Topaz cook) hoping to get it customized to make it exactly the way I want but I'm running into some issues.
Long story short, I'm using Ervius Visual Kitchen (1.8.2) and I noticed that the EXT packages I added end up leaving two copies of the files, a copy under \windows\ and another one in the places I specified using app.dat using:
Code:
Directory("\Program Files\bla\"):-File("bla.exe","\Windows\bla.exe")
Is there some way to get rid of the copy under \Windows\ ??
I know that I could simply leave everything there and discard the app.dat files but I would really prefer having everything organized properly (I have a bit of an OCD when it comes to organizing everything neatly ).
I'm pretty sure that this is a rather simple and noobish issue but I couldn't find anything relevant by searching and I took a look at some ext packages by various cooks and noticed the same behaviour.
Click to expand...
Click to collapse
No, it's call Read-Only-Memory (ROM) and is the reason you can hard-reset your phone. Every file you cook into the ROM is in \windows. Two ways I know of to reduce the amount of files would be to zip them and have a mortscript unzip them to the proper location during customization or cook in a cab containing all of the files and have it run during customization.
That makes a lot of sense, I really feel ashamed that I didn't figure it out earlier
EXT packages seemed easier than bothering to read about customization but I guess it's time to start reading about this kind of stuff.
Thread marked as solved.
Thanks for the quick reply!
Yup, files in rom are in rom forever, or until you flash again, lol. The trick is to just run bla.exe from \windows. I would say that 90% of the time, bla.exe runs just fine out of the windows directory (especially if it's the only file in the package). When people create cabs, they naturally install the app in \program files, but in general apps don't need to be in a specific folder. If there are other files present, usually an .exe will search within its own folder for those files. So, if you just cook everything straight into windows, you'll be good to go. It's easy enough to test: just move all the files from program files to windows after installing a cab, fix the shortcut in the start menu, and then try to run the app. It's always a good idea to do a soft reset and try again (found this out the hard way many times). The one thing you have to watch out for is settings files, like .dat files. These files frequently have to be archived (not read-only). Particularly with apps that use net 3.5, if there's a setting file that is read-only, the app won't boot and you'll get an error message. The fix is to name the file settings-1.txt (or whatever) and have an app.dat rename it to settings.txt (and keep it in \windows).
Also, remember to fix the shortcut path in the start menu, and examine the registry entries to see if there are any paths for files present-you may need to change them to point to \windows (this could also be true in settings files).
mwalt2 said:
No, it's call Read-Only-Memory (ROM) and is the reason you can hard-reset your phone. Every file you cook into the ROM is in \windows. Two ways I know of to reduce the amount of files would be to zip them and have a mortscript unzip them to the proper location during customization or cook in a cab containing all of the files and have it run during customization.
Click to expand...
Click to collapse
This actually made me think a little bit. When you think about read only, I always thing can't delete or overwrite. Obviously I can run a cab and replace a file that is located in the \Windows directory, that leads me to believe there is a way to delete a file or maybe even replaced with an empty file of the same name.
You can over-write a rom file, but the rom file is still there. The file system just flags it somehow or another and tells the device to ignore it and instead use the new file.
TMartin03 said:
This actually made me think a little bit. When you think about read only, I always thing can't delete or overwrite. Obviously I can run a cab and replace a file that is located in the \Windows directory, that leads me to believe there is a way to delete a file or maybe even replaced with an empty file of the same name.
Click to expand...
Click to collapse
The new file you copy over goes into the "user" partition of the file system and windows knows to use that file instead. Once you delete this newly copied file from \windows, the old one from the ROM will take its place back in the filesystem.
Farmer Ted said:
Yup, files in rom are in rom forever, or until you flash again, lol. The trick is to just run bla.exe from \windows. I would say that 90% of the time, bla.exe runs just fine out of the windows directory (especially if it's the only file in the package). When people create cabs, they naturally install the app in \program files, but in general apps don't need to be in a specific folder. If there are other files present, usually an .exe will search within its own folder for those files. So, if you just cook everything straight into windows, you'll be good to go. It's easy enough to test: just move all the files from program files to windows after installing a cab, fix the shortcut in the start menu, and then try to run the app. It's always a good idea to do a soft reset and try again (found this out the hard way many times). The one thing you have to watch out for is settings files, like .dat files. These files frequently have to be archived (not read-only). Particularly with apps that use net 3.5, if there's a setting file that is read-only, the app won't boot and you'll get an error message. The fix is to name the file settings-1.txt (or whatever) and have an app.dat rename it to settings.txt (and keep it in \windows).
Also, remember to fix the shortcut path in the start menu, and examine the registry entries to see if there are any paths for files present-you may need to change them to point to \windows (this could also be true in settings files).
Click to expand...
Click to collapse
First of all, a small question about the underlined part, just to make sure that I got it right: it won't be exactly a rename just a copy with a different name, correct?
Some of the apps I use need a specific directory structure for the resources and files they use, so just dumping them in one big folder won't work.
Another possible issue that I think I'll run into is having two files sharing a generic name (let's say settings.xml) while each belongs to a different app. I didn't personally encounter such a situation just yet but my packages are still a work in progress and I did see a post or two about this while searching.
I was still hoping there would be a simple way to arrange the files in folders while keeping them under \windows\ but I can't find such a method either. Doesn't seem like I have other options than to decided on a firstboot customization method: Runcc, autorun, xda_uc or something that I haven't read about yet...
"Runcc" is currently used in the base kitchen so that gives it an edge right now.
Edit:
Remembered that I had another question, and it's probably not worth a new thread.
I was looking at how to manually create .lnk files and I noticed something that I didn't understand and couldn't find info about.
For example:
Code:
21#"\Windows\MSDict.htm"
What exactly does the "21" refer to?? I tried changing it randomly to other values a couple of times and it didn't effect anything.
NRGZ28 said:
The new file you copy over goes into the "user" partition of the file system and windows knows to use that file instead. Once you delete this newly copied file from \windows, the old one from the ROM will take its place back in the filesystem.
Click to expand...
Click to collapse
Ok now that makes a lot of sense. I guess I'm just use to Android and being able to see that separate partition. Thanks for the explanation.
That sort of leaves me to another question. Can't someone develop a way to overwrite directly to the "system" partition? It would almost be like a root/superuser for WinMo.
Sent from my HTC Evo 4G!
MusikMonk said:
First of all, a small question about the underlined part, just to make sure that I got it right: it won't be exactly a rename just a copy with a different name, correct?
Click to expand...
Click to collapse
Yup, that's correct. Another approach is to take all similar files that go into windows and stick them in a zip file that unzips to the windows directory. I do that in a few cases (power radio comes to mind; it has an ini file). What I do in most cases though is use a backup/restore mortscript. The backup copies all settings files (and similar things) on my device to my sd card. During customization, the restore copies them back. It's convenient for apps where I change the settings a lot and I don't want to have to constantly fuss with the packages.
Some of the apps I use need a specific directory structure for the resources and files they use, so just dumping them in one big folder won't work.
Click to expand...
Click to collapse
What you do in that case is move the sub-folders into windows. In this case, I'll use a zip file to unzip those folders into windows. Using app.dat files to copy large numbers of files blows. It increases the rom file count as well as the storage used. A zip file is a single file, and usually it saves space.
Another possible issue that I think I'll run into is having two files sharing a generic name (let's say settings.xml) while each belongs to a different app. I didn't personally encounter such a situation just yet but my packages are still a work in progress and I did see a post or two about this while searching.
Click to expand...
Click to collapse
In that case, you're screwed unless there's a registry key that lets you change the name. I've run into a few complications; tcpmp and OMarket both use a common.dll. My solution was to buy Core Player, lol.
I was still hoping there would be a simple way to arrange the files in folders while keeping them under \windows\ but I can't find such a method either. Doesn't seem like I have other options than to decided on a firstboot customization method: Runcc, autorun, xda_uc or something that I haven't read about yet...
"Runcc" is currently used in the base kitchen so that gives it an edge right now.
Click to expand...
Click to collapse
Using cabs or zip files is the way to go if you want to copy large folders in one shot (with a mortscript; you can also un-rar rar files, but I don't know how. Yet, lol). Zips are easier to make and edit than cabs, but you need to have mortscript cooked in and know how to write the simple script (aka cut-and-paste).
Edit:
Remembered that I had another question, and it's probably not worth a new thread.
I was looking at how to manually create .lnk files and I noticed something that I didn't understand and couldn't find info about.
For example:
Code:
21#"\Windows\MSDict.htm"
What exactly does the "21" refer to?? I tried changing it randomly to other values a couple of times and it didn't effect anything.
Click to expand...
Click to collapse
The 21 is the number of bytes after the #. It doesn't matter. I usually just change the first number to 1. It works fine. Counting bytes blows.
That was extremely helpful. Too bad these boards don't use a rep system
Farmer Ted said:
Yup, that's correct. Another approach is to take all similar files that go into windows and stick them in a zip file that unzips to the windows directory.
Click to expand...
Click to collapse
Well, if I'm going to follow this method, and it seems like I am, I don't see why I would still have to limit myself to the \windows folder. I can just put everything the way I originally wanted to do. I only looked at arranging files under \windows when I found out that there's no way to get rid of the duplicates.
Farmer Ted said:
Using cabs or zip files is the way to go if you want to copy large folders in one shot (with a mortscript; you can also un-rar rar files, but I don't know how. Yet, lol). Zips are easier to make and edit than cabs, but you need to have mortscript cooked in and know how to write the simple script (aka cut-and-paste).
Click to expand...
Click to collapse
I haven't tried writing mortscripts yet but I've seen enough to figure out the basic and notice how easy it is. I'm gonna check how usable is the WM version of 7zip, as long as it accepts arguments combining it with mortscript will be easy and perfect for me.
7z archives can get smaller in size than half of the zip archives for the same files. And cabs are too annoying to work with and keep updated later on.
Only issue remaining now is checking whether I should put the archived files under \windows or use the sdcard for customization. I'm leaning toward the first but I'll have to wait and see how much memory I would be sacrificing that way.
Farmer Ted said:
The 21 is the number of bytes after the #. It doesn't matter. I usually just change the first number to 1. It works fine. Counting bytes blows.
Click to expand...
Click to collapse
Ah! I thought about counting bytes/characters and noticed that it works sometimes. But I thought it was a coincidence after I experimented in changing the value and noticed that it wasn't always the right count in the .lnk files that I found.
[rant]
Nice, I was messing around with some packages to free up ram and storage and I seem to have ended up with a rather b0rked up xTask. And then there's still convincing Resco Explorer that the registry add-in IS in fact there.
Figuring out the causes should keep me happily busy for a while (and probably heavily pissed for another while afterwards).
[/rant]
Edit:
Just for the record, I ended up using xda_uc it's a lot easier than doing things manually. Although it would help if there was some kind of documentation available, took me a while to understand what .xda, xdai, xdas & .xdaz files are supposed to be.
hi by the way is it possible to convert ext packages of QVGA phones to one another?