Related
I have a T-Mobile MDA Vario and to get rid of standard T-Mobile wallpapers aand stuff I have deleted some files from the extended rom, using the program Total Commander. Off course I've made a backup of the extended rom first.
However, I deleted one file that I like to have back. How can I restore that file from my back up?
Cheers
The actaul t mobile stuff is written in to customisation file for the k jam.
I initially di dteh hard reset, then reset again. But my phone still had the tmobile phone pad erghhh.
So hard reset, browse through your back up and play with files till you find the one you need. Run from the sd card.
Hmm, I still do not get it. I have put the file i'd like to have back in my extended rom on my SD. Now, if I run that particular .cab file, I get confirmnation that the file has been installed.
However, if I explore my extended rom with Total Commander, the file has not been put back in the extended rom. Even if I soft reset.
So, can anybody explain how to put a back upped file that is on my SD back into the extended rom?
Another question I can not find a clear answer for: how do I get into bootloader so I can update my TMobile Vario Rom to a I-mate rom. Any step by step how-to?
Thanks
Still learning what I can about this stuff, n00b.....
Hi,
Just copy and past it back to the Extended_ROM, on the Vario the Extended_ROM is only hidden, not locked. It should be named Hidden_RAM
Cheers,
Cacti
Hi all,
Havn't posted for a while but I am still here! My exec seems to be running pretty fast now, using ozVGA
Anyways, just installed 2 patched *.exe files into windows directory (Backlight.exe.0409.mui.exe and Power.exe.0409.mui.exe) but me being stupid, I forgot to make a back up of the ORIGINAL backlight.exe and power.exe (located in the Windows DIR on the phone)...
So could somebody PLEASE upload me them two files, as I really need to restore them because using ozvga is hurting my eyes at the moment!
Thank you!
Not sure if this is what you want, since they are ROM files.
They originally had Read-Only, Hidden & System attributes set, but don't know if those will survive being compressed with WinZIP.
HTH
Exactly what i needed.. but I have no such luck of getting them onto the exec! i remove the attributes and it still doesn't let me copy!! DOH! any ideas? and thank you for such a quick reply
peteypye said:
Exactly what i needed.. but I have no such luck of getting them onto the exec! i remove the attributes and it still doesn't let me copy!! DOH! any ideas? and thank you for such a quick reply
Click to expand...
Click to collapse
Sorry, wait a minute... That's better just got my spare (hopefully working) brain cell out of cold storage. :roll:
Both files are shown as "ROM" files if I look at their properties in the \Windows\ folder using Resco Explorer, so, errr..... won't they already be there if you delete whatever you've currently replaced them with?
Unfortunately, neither ActiveSync Explore, nor the PDA's File Explorer appear to allow you to overwrite an existing system file on the PDA. Resco's Explorer does allow this, although you get a message saying that the world will probably end if you do. I just tried copying another program into Windows as Backlight.exe. Then deleted my program, and the original was available again. But as mentioned, not posible with File Explorer, nor ActiveSync Explore.
Ok, simply by deleting the two files restored the default versions and fixed my problem.
Thanks for your advice, astage.
peteypye said:
Thanks for your advice, astage.
Click to expand...
Click to collapse
Nothing to thank me for ..... since I'm just another fish out of water...
astage said:
Not sure if this is what you want, since they are ROM files.
They originally had Read-Only, Hidden & System attributes set, but don't know if those will survive being compressed with WinZIP.
HTH
Click to expand...
Click to collapse
link not working .
Hello,
I have read that some people have been having a bit of trouble with customising their extended rom on the Universal. So here is my attempt at creating a guide, as a way of saying THANKS to all who helped me in these forums to create my own customised ROM's on the blue angel and my current EXEC.
First thanks mainly to Buzz for the Ext Rom Unlocker and also to BeyondTheTech for the Disable Security Cab.
Also thanks to all other members who contributed their trials and files in the thread.
IMPORTANT - DO A BACKUP BEFORE DOING THIS AS A HARD RESET IS REQUIRED!!!!
Here Goes:
This is how i did it:
1. I created a folder on the desktop called Exec, and inside i created 2 folders called Orig Rom and Cooked Rom
2. I then downloaded the following 3 files and placed them into the Exec folder.
3. i copied the unlock policies and the ext rom unlocker onto sd card and copied them to the phone.
4. i ran the unlock policies cab first then the ext rom unlocker cab
5. under programs i clicked on ext rom unlocker to execute the file
6. it then said succesful and reboot to finsh
7. once rebooted install total commander from below.
8. i then ran total commander and typed in /extended_rom (note underscore) and it displayed the contents of the exteneded rom that originally came with the phone.
9. selected it all and copied the contents to SD card.
10. if you connect your phone directly to pc then you can copy the contents directly to the 'orig rom' folder you created earlier, or use card reader to do same.
11. either way you have the contents of the ext rom on the pc. i then deleted the contents of the Extended_Rom on the phone.
12. the next steps are done on the pc.
13. copy the autorun.exe and the config.txt file from the 'orig rom' folder to the 'cooked rom' folder.
14. copy all the CAB files that you want to be installed upon hard reset into the cooked rom folder aswell.
15. copy the disable security.cab file into the 'cooked rom' folder aswell
16. you will need to rename the cab files that you want installing in the following format:
Default_Unsigned_xxxxxx.cab where xxxxxx is the name of the file
17. if the cab files have long names then just rename them!
18. if you wanted to keep some of the original cabs from your extended rom then copy these into the 'cooked' folder aswell but leave their naming system alone ie:
Signed_UNI_Remove_BatteryIcon.sa.CAB
19. once these have been named as above open the config.txt file
20. it needs to be prepared into the following format :
LOCK:Enabled
CAB: \Extended_ROM\Default_Signed_DisableSecurity.CAB
CAB: \Extended_ROM\Default_Unsigned_tcpmp.arm_ce3.cab
CAB: \Extended_ROM\Signed_SSD_BTUR_Patch_For_BT_Cannot_Initial.sa.CAB
CAB: \Extended_ROM\Default_Unsigned_Porta-Pinball.CAB
RST: RESET
this is an extract from my config.txt file
21. i used the existing file and amended the entries, add/deleted some of the entries.
22. note the space between Cab: \ this is important.
23. also note that the first file that i wanted to install was the disablesecurity.cab file, without this the other 'personal' cabs will not install.
24. so once you have edited and saved your config.txt files making sure all spelling is correct (also an important thing otherwise the files dont install) and no warnings are issued either! you will have in your 'cooked rom' folder:
autorun.exe
config.txt
and several cab files
25. select all the files and then 'right click' on properties.
26. select the 'read-only' option and ok
27. i found that after the first install some of the cab files delete themselves! this prevents that from happening.
28. connect your phone to the pc
29. using active-sync Explore device and navigate to the Extended_Rom folder
30. copy all the contents of your 'cooked rom' folder into the Extended_Rom folder
31. once completed, disconnect the phone and perform a hard reset.
32. after you have aligned screen and done the start-up routine it will start installing your personallised cab files.!!
33. You should now have an Exec, customised with your own extended rom and as a bonus a complete back-up on your pc.
34. if ever you upgrade the phone rom/radio etc, all the software you need and the perosnlaised rom is ready to go.
if i have missed a step plz post back and i will edit my posts and put in there.
I cannot stress how important it is that you make a backup first before doing this as you will lose everything on the phone.
Bye for now!!!
Gr8 Work!!!
hi there this is a perfect guide well done m8
only one question as i have the jasjar and i-mate rom on it
i do not have the config.txt file
how do i tell the device to install my personal/third party cab files
thanx in advance
mail attachments
Thanks for the guide, however when i use total commander, extended rom is shown with the same symbol as storage card and I cannot get the mail programme to save attachments to the real storage card as the universal thinks the extended rom is the storage card.
How can the properties of the extended rom be changed so it does not appear to be a storage card ?
Thanks
Steve
Re: Gr8 Work!!!
krassen said:
hi there this is a perfect guide well done m8
only one question as i have the jasjar and i-mate rom on it
i do not have the config.txt file
how do i tell the device to install my personal/third party cab files
thanx in advance
Click to expand...
Click to collapse
i have the same problem, any solution?
the solution to that can be found here:
http://www.buzzdev.net/index.php?option=com_simpleboard&Itemid=59&func=view&catid=40&id=7869#7869
Re: Gr8 Work!!!
majdi said:
krassen said:
hi there this is a perfect guide well done m8
only one question as i have the jasjar and i-mate rom on it
i do not have the config.txt file
how do i tell the device to install my personal/third party cab files
thanx in advance
Click to expand...
Click to collapse
i have the same problem, any solution?
Click to expand...
Click to collapse
I just renamed the required cab file by adding "Default_" to it. That did it.
Thanks
But I have been through the thread numerous time.
The mail programme thinks the extended rom is the storage card.
The thread has a fix to hide the extended rom so the mail programme now saves attachements onto the real storage card.
It just seems a shame to have gone to all the trouble to unlock and make visisble the extended rom, just to hide it again so the mail programme can save onto the real storage card.
Am I missing something. Simple guidance PLEASE.
Steve
hollytree said:
Thanks
But I have been through the thread numerous time.
The mail programme thinks the extended rom is the storage card.
The thread has a fix to hide the extended rom so the mail programme now saves attachements onto the real storage card.
It just seems a shame to have gone to all the trouble to unlock and make visisble the extended rom, just to hide it again so the mail programme can save onto the real storage card.
Am I missing something. Simple guidance PLEASE.
Steve
Click to expand...
Click to collapse
When the hard reset is done the whole point is for the Extended Rom to be hidden again. This ensures that at any point in the future if a hard-reset is required then the phone is setup agian as you want it.
At the moment the Extended_rom partitrion cannot be used as a storage space , and i believe Buzz is working on that.
So my guide illustrates deleting existing rom, and replacing with personalised rom and then hiding it agian.
Above this thread is a link to Buzz's small tutorial to alllow attachemnts to be saved back to storage card instead of the Extended Rom for those who want to leave it Un-Hid.
Regarding those without a config.txt file then renaming everything to Default_xxxxx.cab does the trick.
thanks
This is a GREAT thread. Hats off to you.
Personally, I think I'm going to add the T-Mobile USA Internet Settings cab to "cooked" stuff (I'm in the US).
Does anyone have a cab that will set up the gmail pop settings (w/ generic un/pass of course)? Lazy, yes, but I'm just trying to make any refresh that I would ever need to do that much simpler
i have another question as we have a lot of good registry tweaks....
is it really that hard to create cab files for those registry settings and just throw those in the extRom
regards
krassen
flippy said:
the solution to that can be found here:
http://www.buzzdev.net/index.php?option=com_simpleboard&Itemid=59&func=view&catid=40&id=7869#7869
Click to expand...
Click to collapse
my problem is that in wm5.0 there is no config.txt file to tell the os what to install from the ext rom, i unlocked the ext rom and moved all contents to pc, i also deleted all the existing files from it, and i have all my cabs ready, but the problem is how to tell the installer to take these cabs instead of the origionals?
does it take it automatically, or should i do something to make it install my personalised ext rom?
majdi said:
flippy said:
the solution to that can be found here:
http://www.buzzdev.net/index.php?option=com_simpleboard&Itemid=59&func=view&catid=40&id=7869#7869
Click to expand...
Click to collapse
my problem is that in wm5.0 there is no config.txt file to tell the os what to install from the ext rom, i unlocked the ext rom and moved all contents to pc, i also deleted all the existing files from it, and i have all my cabs ready, but the problem is how to tell the installer to take these cabs instead of the origionals?
does it take it automatically, or should i do something to make it install my personalised ext rom?
Click to expand...
Click to collapse
If you dont have a config.txt file then you need to rename your cab files in the following format:
Default_xxxxxx.cab where xxxxx is the name of your file. this has been found to work in your phone.
thanks
many thanx to u.
this worked just fine.
cheers
disable security cab
Does anyone know where I can download the DisableSecurity.CAB as the links no longer work.
Thanks
Steve
Re: disable security cab
hollytree said:
Does anyone know where I can download the DisableSecurity.CAB as the links no longer work.
Click to expand...
Click to collapse
Did you try the first post in this thread?
You have to register and be logged in to see the files...
links worked for me
l6cum said:
majdi said:
flippy said:
the solution to that can be found here:
http://www.buzzdev.net/index.php?option=com_simpleboard&Itemid=59&func=view&catid=40&id=7869#7869
Click to expand...
Click to collapse
my problem is that in wm5.0 there is no config.txt file to tell the os what to install from the ext rom, i unlocked the ext rom and moved all contents to pc, i also deleted all the existing files from it, and i have all my cabs ready, but the problem is how to tell the installer to take these cabs instead of the origionals?
does it take it automatically, or should i do something to make it install my personalised ext rom?
Click to expand...
Click to collapse
If you dont have a config.txt file then you need to rename your cab files in the following format:
Default_xxxxxx.cab where xxxxx is the name of your file. this has been found to work in your phone.
thanks
Click to expand...
Click to collapse
It's shuld be Default_xxxxxx.cab or Default_Unsigned_xxxxxx.cab / Default_Signed_xxxxxx.cab, now ?
Hi all,
I need to replace the pim.vol file on my Blackstone with an older copy. I tried a simple copy and rename procedure, but after rebooting my device, cprog.exe crashes and the device remains frozen until I change back to the original pim.vol ( via PC using Activesync).
Any ideas how I can replace my pim.vol without my phone freaking out?
Thanks in advance...
Bumping for the first and last time only... anyone?
danrop said:
Hi all,
I need to replace the pim.vol file on my Blackstone with an older copy. I tried a simple copy and rename procedure, but after rebooting my device, cprog.exe crashes and the device remains frozen until I change back to the original pim.vol ( via PC using Activesync).
Any ideas how I can replace my pim.vol without my phone freaking out?
Thanks in advance...
Click to expand...
Click to collapse
Just simply replacing a file may not work due to which rom it came from. The replace new files with an older version may not be compatible and may also affect registry enties. Always better to use 3rd party apps for backup.
How did you originally backup your PIM data. Did you just copy a file over or did you use 3rd party apps like SPB Backup, Sprite etc?
Thanks for the reply, Fallen... the PIM file is from the same ROM as the one I'm trying to replace for (1.19 that ships with handsets with Orange UK).
I understand what you're saying about using back up software; in fact I had used PIMbackup, but I had stored the backup file generated by this program on the SD card on my phone only, and unfortunately my phone got lost/stolen - a possibility I hadn't taken into account. I've got a replacement handset now.
The pim.vol file I'm trying to replace with was simply copied from my phone's main folder to my PC a long time ago. Although I can view the pim.vol file as a text file and extract contact names and phone numbers amidst the rest of the ASCII junk in there, I was hoping there might be a way to replace it.
Could I get access to the phone internal storage memory without booting up the phone into Windows somehow and then replace the pim.vol file?
Rename the \pim.vol file, to something like pim2.vol, then copy your old replacement into the root of the device.
l3v5y said:
Rename the \pim.vol file, to something like pim2.vol, then copy your old replacement into the root of the device.
Click to expand...
Click to collapse
Don't mean to be rude, but if you read my original post, you'll know that I've tried that and it didn't work for me, hence this post.
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?