Related
on my qtek9100 there are a couple of sounds that i would like te change, ie. the click sound when opening start in the Today screen. These sounds however are sytemfiles. I tried changing the names, deleting, moving. Everything. But it's not possible for me to change the sounds. Does anyone have a good tip on how it is possible to change /delete/ update the systemfiles of the Qtek9100?
bazzdaciple said:
on my qtek9100 there are a couple of sounds that i would like te change, ie. the click sound when opening start in the Today screen. These sounds however are sytemfiles. I tried changing the names, deleting, moving. Everything. But it's not possible for me to change the sounds. Does anyone have a good tip on how it is possible to change /delete/ update the systemfiles of the Qtek9100?
Click to expand...
Click to collapse
Any files in the rom cannot be deleted but they can be overwritten (the file is still there in the rom under the file you just placed on it). It cannot be done with the stock file explorer, use gsfinder (my personal fav) http://www.pocketpcfreewares.com/en/index.php?soft=1203 or total commander 2
I tried it with TC and tested it by trying to delete a file called Aloutte.mid in the windows dir.
This is a file that's anoying me from the go since it's a music file that I would like removed from my phone. But even TC responded with a message that 1 file could not be removed. As it's a system file. If I want to change the clicksound from start, are you saying I should rename the files first and then copy the desired sound (using the name that the original soundfile uses) to the windows directory? Is that the way to overwrite the systemsounds?
bazzdaciple said:
I tried it with TC and tested it by trying to delete a file called Aloutte.mid in the windows dir.
This is a file that's anoying me from the go since it's a music file that I would like removed from my phone. But even TC responded with a message that 1 file could not be removed. As it's a system file. If I want to change the clicksound from start, are you saying I should rename the files first and then copy the desired sound (using the name that the original soundfile uses) to the windows directory? Is that the way to overwrite the systemsounds?
Click to expand...
Click to collapse
Yes that is the correct way. The only way to silence aloutte.mid is to overwrite it with a silent mid file.
I find that the original phone dial pad is rather dull, so I modified it (see attached) and would like to share with other users. If you like the new dial pad do the followings for installation.
How to install?
A) Find the 5 files below in \windows directory and copy to a another directory (just in case) using Total Commander (or others)
a) Assets_Dialer_Normal.bmp
b) Assets_Dialer_pressed.bmp
c) Dialer_Bkgnd_Port.bmp
d) Dialer_back_key_press.bmp
e) Dialer_back_key_normal.bmp
1) Unzip the attached file -> gives you 5 files as above
2) Ensure that the 5 files is a system file (attributes system - checked)
3) Copy the 5 files above into your \windows directory
4) Soft rest
*** In case it does not work in your set (very unlikely), just copy the original files in step A) above to \windows directory.
this is a great mod - but, the bmp files are set in rom according to the file properties when viewed in total comander. So i cant rename or delete them nor can i overwrite them with your new files. I have jade 110 with hard spl rom flashed with HTC oem rom.
any ideas how to overcome this or am i doing something wrong
TIA
ukmapleleaf said:
this is a great mod - but, the bmp files are set in rom according to the file properties when viewed in total comander. So i cant rename or delete them nor can i overwrite them with your new files. I have jade 110 with hard spl rom flashed with HTC oem rom.
any idea how to overcome this or am i doing something wrong
TIA
Click to expand...
Click to collapse
I am not sure why. I've copied the files to a few different sets (stock rom, though) and they work fine. The files are not in rom. It could be due to your rom.
however, if want to change back to the original keypad how ah?
xtremez said:
however, if want to change back to the original keypad how ah?
Click to expand...
Click to collapse
As far as I understand it you have to copy back your saved original files.
By the way: I can not find these files on my Jade (with TotalCommander).
Owh..ic ic...thanks for clearing that up. Does anyone has those files? Just wanna keep incase.
I changed to a new skin, and the original one kinda looks better with the skin. But i think i accidentally replaced them. Can someone assist me please?
xtremez said:
I changed to a new skin, and the original one kinda looks better with the skin. But i think i accidentally replaced them. Can someone assist me please?
Click to expand...
Click to collapse
I'll post the original files later.. on the move right now. the files are in my notebook at home.
Thanks dude ...PM when u do so then..
Just alittle note about the condition in my Touch3G, i tried installing a various Iphone dialpads...and the software can't be removed even though i deleted it in the registry, plus when i don't use the default windows dialpad..all i get is a white screen with blank [email protected]@ (freaking me out)
Hey guys,
I was wondering if there is a way to put back the original jade notification tones. I'm currently using one of Ironeagle's featherlite roms and it removed a lot of the original sounds.
The main one I need is the notice sound after the other party hands up or the call disconnects. Currently when the call disconnects or other party hangs up, it just has a "static" type of sound and I'm assuming it is suppose to be the short notification clip.
If any of you have the file and know where to replace it in the phone, please help me
Thanks!
For the call disconnection sound, I think you're looking for the file CALLDROP.MID found in the Windows folder...
Try downloading the Jade_Kitchen... It will have all the files of a stock ROM in the OEM or SYS folder... Just copy them over to your phone...
HTH!
thank you! I downloaded the file, but don't even know where to find it or how to insert it back into the phone
wildfxp said:
thank you! I downloaded the file, but don't even know where to find it or how to insert it back into the phone
Click to expand...
Click to collapse
easy way.. download the file again. This time remember, write down the file name. Copy the file to \windows folder in your phone. I assume you know how to sync your phone to your PC.
azahidi said:
easy way.. download the file again. This time remember, write down the file name. Copy the file to \windows folder in your phone. I assume you know how to sync your phone to your PC.
Click to expand...
Click to collapse
Thanks, but I'm really having trouble finding the sound file in the "KITCHEN" files There are so many different folders
Try searching your PC for calldrop.mid...
Here is my Delete Bing .wav files mortscript is there any faster way to delete them? It just takes longer on the startup. I'm not all that good with mortscript so if anyone knows a better or faster way let me know.
PS the reason for Deleting them as they are moved to Program files anyway and are not needed in Windows. Plus they show up as ring tones.
Code:
#Delete Bing Files from Windows
Delete(\Windows\3634cd4e11b1bd74559577b49ed6efae.wav)
Delete(\Windows\ac4096266370f40883a54d090611defb.wav)
Delete(\Windows\bdbb15d2cb8df80d56b32a6d2515ba30.wav)
Delete(\Windows\26277b86d65f70a7ddde3c984e9bf883.wav)
Delete(\Windows\e18f0e15bf9849d036e05a0545eb873e.wav)
Delete(\Windows\bf8c1b233c5da916fe1f075034b7fda4.wav)
Delete(\Windows\743a7b1329ca41f4ec86aa06fb0a3f48.wav)
Delete(\Windows\4a3c7320d03ed16e9834e5cd1824ee03.wav)
Delete(\Windows\5c8f7c51c109c6ade9673ac83deb63c1.wav)
Delete(\Windows\29f1c5be35ede9ff218d805f8995e14e.wav)
Delete(\Windows\66b6cf4d0dc06868a483f8326c27cf97.wav)
Delete(\Windows\005484cc01f1d3e0c5ef0b3f7712e6a3.wav)
Delete(\Windows\2a9ece2598bc70211b7daa2fa2f68c72.wav)
Delete(\Windows\1c25062ce7e0a0494e02752e19288cbe.wav)
Delete(\Windows\f2ff7825a31b57a76454ed7f9ccdb51c.wav)
Delete(\Windows\37002b0a93da55aec001ad6e61050a12.wav)
Delete(\Windows\cb20fd602e53d1e8bbb3ec48deb387a8.wav)
Delete(\Windows\31f890ec125c75dcebbd847085fb7645.wav)
Delete(\Windows\eb75fe209d563eead95b6bc7c1b11486.wav)
Delete(\Windows\d8f11f140bcec702e99e550868657088.wav)
Delete(\Windows\d5e44bfb19fd0b549702074d341410ba.wav)
Delete(\Windows\eec9b002f517cda7dd12b255dc23f7f9.wav)
Delete(\Windows\414be8cb314fc13a20b9fcc46cb7a787.wav)
Delete(\Windows\6a95c3567a42655c77176f66e81d27e9.wav)
Selete(\Windows\9bbb849363c4daa06148ceb671941e4c.wav)
Delete(\Windows\5203a50d4fce11c2978e78e6c402edf7.wav)
Delete(\Windows\76618100dba5235fe6a8c0b87e474e24.wav)
Delete(\Windows\c604c23062ae53b273bad488b5e0798c.wav)
Delete(\Windows\fc1f9f62ccf5e85a12de64bd569ef11e.wav)
Delete(\Windows\8df3b244b6a5a3cc0f2557bc60de4244.wav)
Delete(\Windows\6e7ad19b445243bd5e9cfd18a18177cf.wav)
Delete(\Windows\fe47e09f594a210d51c8829b2df5aa63.wav)
Delete(\Windows\898cbb4e9aeb8d81b20102e52e7eca1c.wav)
Delete(\Windows\77bd63a26cfbf8c259def1a381ab35dd.wav)
Delete(\Windows\5a54b2c14f8003e83310977f1d67e143.wav)
Delete(\Windows\3cd22593dfb9d6c4bba73269ac1fc87a.wav)
Instead of deleting them with mortscript, why not add them with a cab or mortscript rar install during customizations.
I dont know why you're wasting your time with that anyway... Not like you can delete files that are cooked in anyway !!
And to offer a better solution... either do what indagroove suggested, or put rename all your wav to wa_ when you cook them in, then with a mortscript or a simple app.dat move to them program files and rename them back *.wav
I think I will try indagroves method. Anything using app.dat will still leave the original files in windows just like the original External package does.
Thanks for the help guys.
indagroove said:
Instead of deleting them with mortscript, why not add them with a cab or mortscript rar install during customizations.
Click to expand...
Click to collapse
Thanks, I ended up using a zip and mortscript to install them, problem solved.
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?