ExtROM's config.txt commands - MDA II, XDA II, 2060 ROM Development

:?
Hi "wizards",
I've just registered even if I spent last two week looking around the whole forum gathering "precious" information...
I'm cooking my own ExtROM (better, I'm "tuning" it with various .CABs I need).
I'm wondering if there is any solution (or workaround) to the following:
- is there any way to create a directory within the commands available in config.txt ?
- is there maybe the way to move a complete directory from one source to another (thus solving the above problem...) ?
- is there any way to use the CPY1 and CPY2 commands to get some files stored inside a MMC/SD card and move them around the XDA2 ?
I mean I have an Italian version of the device and the MMC/SD is called "Scheda di memoria" with spaces within the name...
I've tried using brackets with no success...
- is there any way (switch, etc.) to install a .CAB in a MMC/SD instead of the main memory ?
I know I could gather only NEGATIVE asnwers to the above questions, nevertheless I thought is was worth asking... :wink:
BTW: I think the registration process should be updated with the newer versions available for the XDA2: actually I'm running v1.72.04ITA dated 04/13/04 with Radio v1.14.00 (ExtROM "was" 1.72.128). Am I the only one with this ? :shock:

These are the commands that I know off:
EXEC:<exe command>
CAB:<cab to install>
CPY1:<source file>
CPY2:<destination>
RST: Reset
Not sure if there are any more.... ??

I have an answer for myself, in the meaningwhile...
The third question is stupid...
I was trying to get the CPY1 & CPY2 commands to copy from the Memory Card ("Scheda di memoria" in Italian) while at the same time I was trying to have the PPC create a non existant directory in the hope the PPC could imagine my desires... :lol:
Indeed SPACES within the command may be present as I'm actually copying files from the MMC/SD called "Scheda di memoria" to the main PPC memory with no troubles at all...
Obviously, the paths must already exist... the batch does not create them...
My first two and the fourth questions are still pending... 8)
Thank you for your efforts...
Ciao

Related

Extended_ROM read-only on Qtek 2020. Why?

I have recently bought a Qtek 2020 and I have applied the registry hack to make visible the Extended_ROM area.
Now I would like to edit which CABs the system install after an hard reset but, to my surprise :shock:, the area appears as read-only (error code 19).
Do have I to make other registry modifications to make the Extended_ROM writable? I am using ROM 1.03.00 USA.
TIA
ROM == Read only memory
you can write or delete rom
but in many cases you can flash it
if you make your own cooked ROM and
update the ppc2003 os of your xda2
Please, study the stuff you don't know before posting obvious things!
http://www.ppcw.net/index.php?itemid=1642
Byez
but the config.txt is not in rom
so you are not chaning or writing in the rom
you are just chaning which files in the rom
the system access
just got confused about the way you asked the question
RAM/ROM?
Hi I would like to know, is your Qtek 2020 has 128M and 64ROM :?: ??
How much did you buy it and where? :roll:
Best regards,
Paf
Hi, Yes to both questions . You can buy it at :http://www.mobilkompagniet.dk/default.asp?Action=Details&Item=1820
Rudegar said:
but the config.txt is not in rom
so you are not chaning or writing in the rom
you are just chaning which files in the rom
the system access
Click to expand...
Click to collapse
What the hell are you saying??? Config.txt is on Extended_ROM like Autorun.exe and various CABs.
I suggest you to read again the article I have linked (http://www.ppcw.net/index.php?itemid=1642) and leave space for replies to people that really own and know the Qtek 2020.
Byez
I didn't have a config.txt in MY rom.
Luckily another user (props to him) figured out that if you prefix the names of your cab files with Default_ (default underscore) and make a config.txt they will autoload on hard reset.
-arebelspy
arebelspy said:
Luckily another user (props to him) figured out that if you prefix the names of your cab files with Default_ (default underscore) and make a config.txt they will autoload on hard reset.
-arebelspy
Click to expand...
Click to collapse
You miss the key point of my message: Extended_ROM is read-only in the Qtek 2020. Stop. No way to add any prefix, "Default_" or whatever you want.
Any Qtek 2020 owner out ther that could confirm this? Any XDA-Developers team guy that _know_ how storage disk are mounted by Windows CE and could suggest a (registry?) trick?
Thanks, byez
he is right with saying:
I do have the same issue:
"You miss the key point of my message: Extended_ROM is read-only in the Qtek 2020. Stop. No way to add any prefix, "Default_" or whatever you want. "
same here. read only can't delete or add anything.
alex
It seems my XDA2 has this problem too (but some other XDA2 don't have this problem
I have an O2 XDAII and cannot modify anything in Extended_Rom too
HI,
Anyone that have fix same workaround for this problem?
I have Qtek 2020 . I´m unabel to make changes in the Extended_Rom
JoseF
Hi guys; i also would be interested in such a fix for my french rom Qtek2020.
Thanking you all in advance, i remain, Arnaud

Totorial: XDAII Extended-Rom

I had a hard time to upgrade and modify my xda2 so I decided to make a small tutorial for everyone with the information’s I found on the forum. It’s not perfect but it could help.
Thank's to every one who made all this possible!!
Before starting I recommend every one to make a back-up of your rom
http://forum.xda-developers.com/viewtopic.php?t=4608
1- Extended Rom:
Your XDA2 has an Invisible Extended Rom in the device containing the operator’s configuration files and software.
Modifying it will allow you to customize the boot image and to choose the programs you wish to install during the setup of the device.
To show the extended rom on your device your need to apply this small hack and then open your file explorer:
http://www.ppcw.net/index.php?itemid=1638
2- Files contained in the Extend Rom:
Broadcast_WWE.sa.CAB:
Seems to only set the CellBroadcast setting to enabled or disabled. (I guess this refers to the Reception of News via SMS by selecting channels of interested. Quite expensive I think and only interesting for phones that do not have any other capabilities of receiving and displaying information).
T-Mobile NL sets it on, with O2 it's switched off.
CallerIDRC11_WWE_1.5.sa.CAB:
Installs the CallerID application from IA Style and the Photo Contacts extension. There are other programs that are able to provide this functionality but I use it.
CameraRC131_WWE_1.5.sa.CAB:
The camera application for taking pictures and recording videos. AFAIK there is currently no alternative to this one, you should leave it in your ROM.
GPRSMonitor_WWE.sa.CAB:
Includes the GPRS Monitor from SPB Soft. Very useful I would recommend it unless you aren't going to use GPRS anyway.
MIDI56.sa.CAB:
RingTone plugin player. Allow you to play back RingTones in the following formats: mid,3gp,mp4. Also seems to register the audio/midi MIME type for playback of midi files directly from Internet Explorer.
By default the XDA can play back only wav and wma audio files (AFAIK)
MMS1507_WWE.sa.CAB:
Installs the Arcsoft MMS application for composing and sending MMS messages.
VideoMMS.sa.CAB (not contained in Qtek):
Installs the "Video MMS.exe" file into the Windows folder. When you start it you are in camera mode immediately and after you have recorded a picture or video you get into MMS composition mode.
This seems to be just an easier way to compose MMS messages since the main MMS Application (see above) is already able to compose MMS messages.
OEM_AKU1_WWE_4AP.sa.CAB (named OEM_4AP_WWE.CAB in Qtek ROM)
Installs the following files: GPRSAuthentication.exe, BTSetting.exe, STK.exe and WModem.exe
I am not sure if these are customized versions or if the normal ROM doesn't contain them. Well perhaps not because these are specific to the Phone edition so they can't be present in the main ROM, maybe they are contained in the Radio ROM, but probably they are only contained here, meaning you shouldn't remove this cab file.
OEM_WWE_03120301.sa.CAB (named OEM_WWE_03122301.sa.CAB in Qtek ROM)
Installs files for Bluetooth: AudioGW.dll, BthASPlugIn.dll, rilgsm.dll, Serial3.dll and Wavedev.dll. Also contains the new feature of mapping a (dynamic) serial port for BT.
I think you should not remove it.
TM_phone_class10.CAB (not contained in Qtek):
Installs several registry settings regarding phone functionality. (See my other post regarding this topic: http://forum.xda-developers.com/viewtopic.php?t=5539)
TMCOMREG.sa.CAB (not contained in Qtek):
Contains some of the settings contained in the previous one anyway. I'm not sure if it does anything else but I don't think so.
TMD_AP_NL.sa.CAB (not contained in Qtek):
Implements several settings specific to T-Mobile (NL): Restricts video types for MMS. Adds connection and gateway settings for MMS connection via T-Mobile NL. Adds a T-Mobile profile to GPRS Monitor.
I would not install this cab unless you live in NL!
TMD_NL.sa.CAB (not contained in Qtek):
Sets the HKEY_LOCAL_MACHINE\SOFTWARE\OEM\3rdversion\MSYSTEM1 value to the provider name.
Not required!
TMDNLCustomize.sa.CAB (not contained in Qtek):
Adjusts all the "theming" stuff: Changes colors, installs Today-theme, installs T-Mobile Dialpad, sets T-Mobile ringtone.
If you don't like you xda2 look like a pink pig you should leave this out.
(You can extract single items from the cab file if you like)
t-mobile_shortcuts_only(UK).PPC2002_ARM.CAB (not contained in Qtek):
Contains some strange things that seem to me rather useless: "WebDisplayText t-zones", "T-Mobile Resetter.exe", "T-Mobile PIE Launcher.exe", "TMobileWebToday.dll", "T-Mobile Homepage Plugin".
I wouldn't install this one!
Version_AKU1.sa.CAB (Version_AKU1_160.sa.CAB in Qtek):
Seems to only set the version number of the extended ROM in the registry.
3- Modifying and editing your Extended Rom:
Most of the latest XDA2 have a write protected Extended Rom
A) For NOT Write Protected Extended Rom:
If your XDA2 Extended Rom is not write protected just add the new files you want, you can find on the forum many different extend rom files (O2, T_Mobile, Orange) and kitchen your own extended Rom by adding the cab files directly in the Extended_rom directory and soft reset.
B) For Write Protected Extended Rom:
The only way for the moment (until we find a way to make the rom writable) is to use the upgrade programs used by the operators and ER2003Edit program.
1)- Download
http://www.c1au.com/iMatePDAROMS/ruu15283.zip
or
http://www.clubimate.com/Support/ruu113sku1.zip
2) Simply unpack the complete T-Mobile Rom update file (it's a zipped EXE) into a folder.
There you will find these 6 files:
- HimaClearJumpCode.exe
- HimaGetDeviceData.exe
- HimaUpgradeUt.exe
- ms_.nbf <----- this is the file which holds Ext Rom!
- NK.nbf (main rom)
- Radio_.nbf (radio rom)
3) Delete the other *.nbf files to prevent updating the full XDA2/MDA2 rom. You only need "ms_.nbf" and the "*.exe" files!
4) Now modify the ms_.nbf with the tool softworkz kindly provided.
http://wiki.xda-developers.com/wiki/ER2003Edit
5) After this, install the modified ext-rom to your XDA2/MDA2 by starting "HimaUpgradeUt.exe" and follow the instructions!
6) If you get a country code error during the install you will need to modify the country code included in the ms_.nbf file
- Download xda2nbftool
http://forum.xda-developers.com/viewtopic.php?t=5563
- Put xda2nbftool.exe in the same folder as your ms_.nbf file
- Run xda2nbftool.exe from Command Prompt and type the following command
xda2nbftool.exe -so O2 -v ms_.nbf
Replace O2 by your operator’s name (ex: orange, O2 etc)
It should now work!
cheers,
Yann
nice one Yann
Thanks
I had a go at doing the "if your extended rom is protected"
I down loaded the file
1)- Download
http://www.c1au.com/iMatePDAROMS/ruu15283.zip
and accidentally ran it.... I know I was stupid... I now have an I-Mate instead of a XDA - O2. Please help can I get the O2 back is there a programme that does the same as the one I just have used. It has changed every thing the radio stack, the other bits of software, I am just pleased it still works of calls.
I couldn’t find the indivuiual HimaUpgradeUt.exe programme any ware.
Please help I am really stuck at the minute!!
The bit I didn’t understand was the bit about unpack the exe. Which I now understand how to do. Although I have upgraded to Rom 1.52.00wwe, radio version 1.06.01, I can haply say I have the original O2 rom back in place with additional programmes installed in the Ex-Rom. I had a fair bit of space so I popped some music files in as well!!!!
Thanks for all the help!!!!
thanks yann for the perfect summary
as newby i needed something clear like this to dare my first rom changes, and i successfully did!
it would be even more perfect if also somehow the program settings/passwords could be cooked in/restored from the extended rom. i searched the forum but could not find any hints.
Are there methods for this ?
Perhaps a silly question, but I'm fairly conservative when it comes to messing around with my device.
How do you find out or know if your Ext ROM is write protected or not? I know that I can add applications to my Ext ROM and it does not seem like I should be able to do that if it's write protected, but then again I'm not sure if this matters.
Ed
ed, if you can copy files to your ext-rom via activesync, it is per definition not write-protected.
your not that conservative, because you already run a tool or edited the registry to be able to see the ext-rom
ronald,
Well I guess you are right I do like to play around, as I get more comfortable doing so. It is this Forum, guys like you, and some other forums that have made this possible for me to do. For some reason I'm more comfortable in general hacking around a desktop pc than a PPC.
I thought my Ext ROM must not be write protected. When I deleted the TMD files, described here as useless, I got the message that they were read only, but they did go away from the Ext ROM Folder. I do not notice a big difference, however, nor did it free up that much memory. I was thinking that I might need to do more then this. Do I?
So basically, if my Ext ROM is not right protected, and I have been already loading programs into the Ext ROM, I’m pretty much at the place people are trying to get with the Ext ROM Cook ER...Edit. Is that correct or am I missing something here?
Ed
Ed,
I do not like flashing rom (or bios) on either my desktop or PDA (if not absolute sure to fix bugs). However flashing the PDA's ext-rom can basically not screw up the PDA because you don't touch the OS, so I flashed the ext-rom to get familiar with the PDA flashing in general (and also to have a restore of my standard used software after a hard-reset).
About your ext-rom; I do not recognise your situation. I would say if it is read-only the file will not disappear (like with my PDA).
I did notice while editing the ext-rom file for flashing that the file is fixed ~16MB, regardless of which cab's are included or deleted.
Maybe this is the same effect that you see when deleting the file in the ext-rom ???????? (although I can imagine both effects have no relation)
ronald
Camera Programs
Okay,
I made a custom ROM with the following programs:
CAB: \Extended_ROM\CameraRC131_WWE_1.5.sa.CAB
CAB: \Extended_ROM\CallerIDRC11_WWE_1.5.sa.CAB
CAB: \Extended_ROM\MMS1507_WWE.sa.CAB
CAB: \Extended_ROM\GPRSMonitor_WWE.sa.CAB
CAB: \Extended_ROM\Version_AKU1.sa.CAB
CAB: \Extended_ROM\OEM_AKU1_WWE_4AP.sa.CAB
CAB: \Extended_ROM\OEM_WWE_03120301.sa.CAB
CAB: \Extended_ROM\VideoMMS.sa.CAB
Awesome, alot less bloat, but.... Camera doesn't work.. Application says Camera is not a valid Pocket PC application. :: grumble ::
Did I miss something?? Camera.exe is there, but doesn't work
Brandon
My Ext ROM is not write protected, and I'm able to run applications in the EXT ROM Folder. I deleted the 2 TMD and the T-Mobile cab files, but I have not nticed a big difference, nor is my GPRS back to always on, which it should be now.
Perhaps the device requires another hard reset without these cab files in place prior to the changes taking actual effect. Does anyone know if my assumption is accurate about the required hard reset?
Ed
what dictates if the ExtROM is write protected or not? is it the version? or the hardware itself? or a mix of the version with the OS checks?
cuz i believe the ROM version is dictated by the version_AKU1.sa.cab. does that mean we can hack the cab (or use a diff version) to disable the write protection?
i'm using a himalaya btw.
I have a question or two.
I'd also like to know if it is possible to modify CAB files so they install an application and then also put in your purchased key or serial depending on the application so it's already registered to yourself. It seems like it must be possible because the GPRS Monitor on the T-Mobile Extended ROM is already Registered when you try and register it yet I was under the impression it normally has to have a key entered to turn it into the full version with no limits.
This would be great if this was possible, if it's a key file then it's simple to copy it over but how about automatic registry entries? Are these done similar to Windows .reg files? Does anyone have any info if a .reg file can be make and run from the Extended ROM to make changes to the registry? This would also allow me to key in a few other things I'd like presetup.
Is there a way to see what registry changes a CAB file makes other than from purchasing MagicCAB? Is there a free program like this? It seems like a reasonable program from the info but I don't want to spend 10 dollars on a program I might only use once or twice.
Acutally, one more while I'm here. Does anyone have a CAB installation version of CabInstl which puts a shortcut in the Programs or an easy way for me to make that? I've set it up so it will copy the EXE in manually along with a shortcut but I've yet to try it. I think it should work OK I imagine, just might be neater and have an uninstall if it's in a CAB format?
Can you delete files from the extended ROM script? Just so I can clear out a few folders of things I don't want in there when I do a hard reset?
Thanks for all your help. I'm looking forward to making a super kick ass Extended ROM for myself, I'm half way there
Updating the indirect way
Had a few problems with the updating process... and thought i would explain how I got around them!
First I updated to the standard 16007DE ROM
Then I installed the Extended Rom Viewer, and then because it is protected, i copied the contents to my HDD.
Then i tried to open the Rom update from T-mobile with the Extended ROM editor, but kept on getting file access errors The only one i could open was the NL 13006 version. So I changed the splash screen, deleted the origianl contents, and then inserted the contents from my updated original Extended ROM, as well as a few other bits that i could find, IE the extended ROM viewer. It is updating at the moment, So I hope it all works.
I have a few questions though!
Does anyone know a way in which I can automatically install a few themes, and a few ringtones? I have a few MIDI files that i want to be installed into the windows\rings folder, and the themes need to go in a folder called themes in My Documents. I also wanted to ask if there is a way to extract the CAB from another program, for instance Voice Commander. It is an MSI, but only works in windows!!!
Any help would be greatly appreciated...
Greets from Hannover, Germany
Juggs :?
Is this going to work:
- Download ER2003Edit
- Download the O2 XDA2 ROM 1.60.50
- Download the T-Mobile MDA2 ROM 1.60.36
- Remove O2 apps i don't want to use
- Add applications from T-mobile rom which i want to use
- Change ROM provider from O2 rom to to T-Mobile
- Save new O2 ROM and upgrade
But... I want to add custom ring tones to contacts, and if possible also want to add custom picture. Also my camera must be able to work. Which software do i need for this?
Because.. All i want to upgrade is today theme to O2's and also the software to 1.60.50... Does the O2 rom also has an "TMDNLCustomize.sa.CAB" ?
Greek full support language for qtek 2020
Hello,
this is a very intresting site!
Can anyone tell me is exist & where can i dinf an extended rom for qtek 2020 with full support of greek language?
Also there any newer version than the 1.66.00 wwe extended1.66.130 radio 1.10.00 wihich my qtek 2020 has??
best regards
george
A) For NOT Write Protected Extended Rom:
If your XDA2 Extended Rom is not write protected just add the new files you want, you can find on the forum many different extend rom files (O2, T_Mobile, Orange) and kitchen your own extended Rom by adding the cab files directly in the Extended_rom directory and soft reset.
B) For Write Protected Extended Rom:
The only way for the moment (until we find a way to make the rom writable) is to use the upgrade programs used by the operators and ER2003Edit program.
Click to expand...
Click to collapse
2 questions for you,
1. how do i know whether my rom is the editable 1 or the non editable one?
2. I tried option A, just mergly adding the CAB files into the EXTROM but... when the hard reset was perform it did not install the CAB files i added in? what could be the prob i know there is a "autorun.exe" in it but i dunno whether will it affect the process. I also notice a "config.txt" in the extrom, tried editing it but it seems that nothing happen
Reason for adding the cab files is because i was using a 1.72.00 rom with radio stack 1.12 but intend to change it to radio stack 1.14 and also try cooking up my own rom in the ktchen but after doin so its like nothing happen. need some advice for cooking roms in the kitchen been searching the forum... found a few but its all talking about Linux platform.
Hi Kelvin,
1)
The way to know if your rom is not writ protected is if you see a folder called extended_rom in the root of XDAII and if you can add files in it.
If not, there’s a nice tool to make the extended_rom visible and to make it writable.
http://forum.xda-developers.com/viewtopic.php?t=8422&highlight=extended+rom+hide
2) The config.txt is made to lunch the programs in the extended rom when you hard reset the XDA or when it starts for the first time.
You just need to put the cab files in your extended_rom folder and edit the config.txt this way:
Exemple:
I added the cab file vxIPConfig.ppc3_arm.CAB in the folder extended_rom
and added this line in config.txt
CAB: \Extended_ROM\vxIPConfig.ppc3_arm.CAB
Cheers,
Yann
hi yann,
i tried doing that way as i figured out that config is like a startup "prg" to actually start the programs installing when hard reset is performed. But the thing is i cannot make the programs i added in the install after the hard reset is perform. I don't know why but the rest of the cab files can be done. Do adding of all this cab files into the ROM consider cooking ROM??? not really fimilar with the terms of cooking ROM unless that is the way.

Unlock STORAGE on Alpine QTEK 2020i

Is very good day
I speak about QTEK 2020i Alpine and no other
I succeful unlok my STORAGE was as looked after trying to unlok Extended_ROM.
Try this step
1) Go to registry HKEY_LOCAL_MACHINE/System/StorageManager/Profiles/TRUEFFS_DOC
2) Change value in folder "Storage" by other thing example "Toto"
3) Soft Reset your 2020i
4) With Explorer now you must have a folder nammed "Toto" in my example
5) Try to copy or delete inside a file. For me it's working
6) Return in registry, return original value "Storage" in Folder value
7) Soft reset again
In final you must have your original Storage that is now unloked
Let me know if it's correct for you
I'm be happy and to find solution
[/b]
I tried exactly what you said, even that I have tried it before, but it DID NOT work.
that parameter which you changed is just responsible for the name of the folder only, so if you realy could unlock the Storage folder, then it happened with you by chance with another way. if it was just that simple then flashing PPC would solve it also, but it wont, I also tried that.
so please try again to lock and unlock it if u remember the way and tell us in more details. in yours explanations: the name of storage is changed but still I cannot delete or save into it.
on the other hand, if you change the value of MOUNT there to 0 then you will hide your Storage folder, and this is what the LoadvDisk does, it just plays with such a registry parameter, but for unlocking the DLL file is responsible for that, for those who doesn't know what is the DLL, simply I can tell that it is a collection (Library) of functions, now that DLL file has a function that is responsible of unlocking the disk by modifying the non erasable memory ROM. and that is why when you flash the PPC, still your extended rom and Storage is locked, because that data is saved on the ROM that needs a special function and password passed to that function for modifying that data there.
sorry for the long post
Right
In fact i was no certain about "other way" at the moment where i wrote.
Follow exchange about " eNiPlA", i tried modify the tools for SX66 and use it during the test but don't view effect immediatly. It was the same tools that was loocked my storage that today after modification unlock it.
Try this, but i m not certain that to change name of folder in registry is necessary
1) Go to registry HKEY_LOCAL_MACHINE/System/StorageManager/Profiles/TRUEFFS_DOC
2) Change value in folder "Storage" by other thing example "Toto"
3) Soft Reset your 2020i
4) With Explorer now you must have a folder nammed "Toto" in my example
5) USE TOOL ATTACHED HERE and Try to copy or delete inside a file. For me it's working
6) Return in registry, return original value "Storage" in Folder value
7) Soft reset again
IMPORTANT
Don't use this tools (in this state) to lock, but just for UNLOCK Storage . As EMU said, if you try to lock , in fact it lock your STORAGE.
yes, that tool worked alone, just install the tool, run it on your device and try only to unlock (ONLY UNLOCK, DONT TRY ANYTHING ELSE) and it would be ok after a soft reset!
thanks apoujade, can I ask you how did you modify the tool, which tools you used for that, if you had the whole source code can you please send it also, because if you could modify this tool, then we may reach to the Extended Rom easier from it also.
I feel we are very near to the solution....
Hi
This tools came from http://www.myehud.com/xv6600/cabs/ExtTools.exe.
I changed with binary editor string "rEiRaH" with " eNiPlA" wthitout missing 2 space before. It's seems to be made for Audiovox with Extended ROM in target. On Alpine it's work for Storage area.
Hello guys, please help me!
How can I unlock the Extended ROM on my XDA IIi? I've been used the search-function but I haven't found any thing that would heplfull fo rme!
Storage released!
My Alpine's storage was also locked and have been looking for any solution.
Today Asukal informed this thread and I tried ExtTools_modifiedAlpine.exe.
It works quite well and I could unlock my Alpine's Storage area!!
Thanks guys!!
Stop!
Storage is the place where I can install programs and them aren't deleting during a hard reset and a ExtROM is the place for the software that are using by the providers! Are I'm right? :?:
Than it wouldn't be helpfull for me!
animelover said:
Stop!
Storage is the place where I can install programs and them aren't deleting during a hard reset and a ExtROM is the place for the software that are using by the providers! Are I'm right? :?:
Than it wouldn't be helpfull for me!
Click to expand...
Click to collapse
Yes, you are right.
What I thank all friends here is that I could release the lock of Storage which was locked during the operation of finding the way to unlock ExtROM.
So if I try this manual, after that my ExtROM is writeable? That would it be cool!
Hehehehe, space, I want more space for my porgrams! ^^
to clear something out:
everyone is wondering how to unlock the Extended Rom, so as everyone, while we were trying to figure it out, our Storage Folder became also locked (not-writable) so we had another problem, it became our main problem, since the Storage folder should be writable in the normal form, so the ideas in this post are only to unlock the Storage folder and has no relation to the extended rom, so if your Storage folder is already writable, then ignore what is in this form. if you are looking for a solution for your Extended Rom, the answer is: WAIT, we are working on that, and when it is solved most probably you will find the answer in a seperate post..
Good luck to all in the unlocking process..
so Brother EMU, do you already find the way to unlock the Ext Rom of XDA? I upgrade to WM2005, then the tools I used before is mulfucntion.
I am eager to wait for your solutions, tks!
Hi
Without EMEI, i sue two site for french ROM, but other depends what you want (O2, WWE ..)
Mobinaute it's free but you must ask for download DANGAARD ROM
http://www.mobinaute.com/mobinaute/ (search for DANGA)
Brighpoint it's also free, but you must create an account to access download area
http://www.qtekfr.com/modules/news/
Other way, but not the last version is ftp from xda where you search in ALpine folder
ftp://xda:[email protected]/
what do you mean? is there a point to posting the rom download sites???
tia
Works for locked 2i Storage
THANK YOU!
This worked to unlock the Storage folder on my 2i
I didn't even realize that the problem started when I tried to use the extrom unlocking tools, I just found one day that my storage was locked and I could no longer write or delete files from it. That sucked, it took me ages to find this post and now it is fixed. Great!
Re: Storage released!
reveil said:
My Alpine's storage was also locked and have been looking for any solution.
Today Asukal informed this thread and I tried ExtTools_modifiedAlpine.exe.
It works quite well and I could unlock my Alpine's Storage area!!
Thanks guys!!
Click to expand...
Click to collapse
MY XDA2i HAVE THE SAME PROBLEM,CAN YOU SHARE A ExtTools_modifiedAlpine.exe WITH ME?THANK YOU!!!
Re: Storage released!
catcatwh said:
reveil said:
My Alpine's storage was also locked and have been looking for any solution.
Today Asukal informed this thread and I tried ExtTools_modifiedAlpine.exe.
It works quite well and I could unlock my Alpine's Storage area!!
Thanks guys!!
Click to expand...
Click to collapse
MY XDA2i HAVE THE SAME PROBLEM,CAN YOU SHARE A ExtTools_modifiedAlpine.exe WITH ME?THANK YOU!!!
Click to expand...
Click to collapse
Why don't you download from the above link?\
Here is a link again.
http://forum.xda-developers.com/download.php?id=5263&sid=1fb6fbc8c0958abc01e668c52bbb1df3
apoujade said:
I speak about QTEK 2020i Alpine and no other
Click to expand...
Click to collapse
If you are speaking about QTEK 2020i Alpine and no other, WHY ON EARTH YOU OPEN THIS TOPIC AT THE "Himalaya upgrading etc." FORUM?
Thanks
To all the Masters
You're Great
It work's with my Alpine (i-mate PDA2)
i've unlocked my Storage
Thanks

System files moving not permitted

Hi to everyone.
Before this HTC device I had others and also had a Motorola Mpx220 (WM2003 SE).
I was used to move the files within "\Windows\Start Menu" (mostly .lnk files to installed programs) into newly created subfolders, to be able to use and/or access the function I needed in a faster way.
I've tried doing the same on this WM5 device, but everytime I try I get an error message reporting it is not possible (File Explorer has greyed out options to cut and/or copy, while TotalCommander just reports it's not possible to "overwrite" ???).
Does anyone have an idea of how this can be done (registry ???) ?
Thank you.
Ciao
Here is the solution...
Hi Mix, it's Mix answering (yes, I'm the same person...)...
First of all I would like to thank you ALL the people which knew the solution and were fighting to answer to my doubt...
You were so many, I wonder why the message has been read times and so many answers arrived: 0 (yes, ZERO).
Anyway, I came across the solution myself, by chance...
The problems seems being the smartphone versions of WM5 being protected against file modifications. This protection extends also to some files execution and to certificate installations (hence some problems may arise when connecting to an Exchange Server for syncronization).
Some tools are needed to remove this protection, and some experience of registry modification is required too (I will not help anyone beside what is in this message and I take no responsability for any mistakes and/or troubles you may produce or face).
First of all you need a special version of RegEdit (the tool from PHM): you should find an HTC digitally signed copy of it called RegEditSTG.exe.
Look around for it: there are many forums around which do hold a copy of it.
Place it in your phone's memory, not on the MicroSD card...
With this tool you should change the following values:
HKLM\Security\Policies\Policies\00001001 = 2 => 1 (RAPI)
HKLM\Security\Policies\Policies\00001005 = 16 => 40 (Cert)
HKLM\Security\Policies\Policies\00001017 = 128 => 144 (?)
The first is the value you will find, the second is the value you should enter. The third line has a question mark because someone says it should be made, someone not... It's up to you. I made it.
Then you should find another tool (with the same above method) called SDA_ApplicationUnlock.exe which has to be run on your desktop PC with the phone already connected with USB (and possibly with ActiveSync not in the middle of a sync...).
Once you run this, you will get a message that the unlock took place (if not, it may be the first operations did not complete well).
Disconnect your phone from the USB cable and power cycle it (switch it off and then on again).
Opla'... the phone is not APPLICATION UNLOCKED and you will be able to move file around the directories as I was looking to when I first posted my message.
Now I have a very quick Start Menu, as I wanted.
Please, be aware that this operation hacks the security policies of WM5 and then any other application which may be dangerous can now run on your phone.
If you wish to stay on the safe side, it could be useful to restore the registry settings to their original values, but I do not know if this could cause other problems, since I didn't on my phone.
I actually double check every single file by myself before launching it and I do not run anything which I'm not sure it is safe.
So, pay attention... (you have been warned...).
Hope this helps someone else out there.
Ciao
Thanks for the tips mate! I was searching around for the same problem.
Can a hard reset put all the files back as in the old WM2003? I'm asking that 'cause if you look at the windows directory, many exe and dll files are repeated, with a different code. I guessed they are for the many different languages the phone support and the code is the country code. Maybe when you switch from one language to another those files are renamed so you have the correct exe and dll for the language you need...
If I can erase all the files I don't need (I will never change the language or maybe have only italian and english) I can save lot of space.
Am I wrong? Was that ever tried before?
vbi said:
Thanks for the tips mate! I was searching around for the same problem.
Click to expand...
Click to collapse
;-) I knew...
Can a hard reset put all the files back as in the old WM2003? I'm asking that 'cause if you look at the windows directory, many exe and dll files are repeated, with a different code. I guessed they are for the many different languages the phone support and the code is the country code. Maybe when you switch from one language to another those files are renamed so you have the correct exe and dll for the language you need...
If I can erase all the files I don't need (I will never change the language or maybe have only italian and english) I can save lot of space.
Am I wrong? Was that ever tried before?
Click to expand...
Click to collapse
In order:
- Yes, I suppose a hard reset of the device completely restores the original factory settings, hence, the device will appear as "brand new".
- You're right: all the localized files present there are just to be able to swithc to other languages (maybe following user's settings and maybe also following user's SIM settings too...).
- Erasing the unused files may appear as a "space saving" job. It is not. First of all you will not be able to remove ROM resident files, but provided you could be able to do this, you will not be able to use ROM space as you intend...
Finally then, it's completely unuseful to try to remove them, just a waste of time trying...
Ciao
Thanks Michele.
Are you sure the windows directory is in ROM?
I always tought ROM was only to store the "disk" image when you hard reset the device. I was so for the Qtek S100.
vbi said:
Are you sure the windows directory is in ROM?
Click to expand...
Click to collapse
Yes it is. On the fact that it is then copied into RAM, well, this is a tecnique which was used up to WM2003 SE devices.
Starting from WM5 devices MS somewhat changed the behaviour of the whole system, hence I'm not then so sure.
Indeed, I have never been sure of anything, beside death, so you can imagine...
I'm not really so "expert".
Having used an MPx220 for over one year (with all its limitations, but exploiting it very much), using a WM5 device now is a much more relaxed experience (faster, more realiable and less troubly in terms of memory).
Just MHO
Thanks Mix - i followed your directions and it worked.
Got my QTEK (running i-Mate ROM) Application Unlocked

[REF]Noonski's Little SPC-MORT-COOKING OEM Packages repository

Since i'm not going to cook just yet for the Pro, nor am i helping out any specific crew Over At the Pro (SPC crew will come over to Pro someday anyway).
I have decided to make a OEMMORT Packages Repository.
For those that want to cook with the utmost optimized packages for their Pro.
OEM PACKS
To use these Optimized Packages to Cook (specifically with Touch Pro In Mind), you always need the the MortScript Base.
So if you use more or less packages the RFO.mscr & CLASC.mscr need to be adjusted appropriately to correspond with the correct File Operations.
Mort Script 4.112.b7
AdobePDF_2_5_103401_01
IA_ZIP_1_21_18171328_1
More coming eventually.
Explanations
If you do see the Logic and and improvements this adds to cooking control and performance enhancement, then don't forget to mention the SPC-MORT-COOKING Style, Wax in Wax Out
Any Comments, Opinions, Ideas or Questions welcome.
TNX to the rest of the bengalih for some pointers & SPC crew for testing and helping out.
And thanx of course to MORT.
Don't Know MortScript? Shame on you. (neither do i)
Donny Bahama's easy to carry Mortscript Manual in HTML:
http://forum.xda-developers.com/atta...9&d=1214102654​
excellent stuff
Hi Noonski... Very interesting concept.. Great Works! Cheerz..
would it be possible to put the cab files from UC all into 1 zip file to save space ?
da_jojo said:
would it be possible to put the cab files from UC all into 1 zip file to save space ?
Click to expand...
Click to collapse
ExactMundo.
If you'd make the cab files into OEM packages first.
I have a WNDWS.zip
PRGF.ZIP
and a MYDOCS.zip
But even that would not be needed as one zip file should be able to do it.
As long as the Makedir command is used in a Mortscript before the Zip is extracted for folders that do not exist unless you have the complete folder structure in the zip files.
Unless you mean the Cabs from the UC on your SD card.
But even then you could also only extract just a cab at a time.
So i'm not sure you meant the ROM Autorun Cabs or the SD UC cabs?
Also unzipping the files instead of having them in Rom, or making the links with a script removes that darned ROM Read File Protection.
yes yes yes that is what i mean exactly my friend
i mean both ... it would save space on the storagecard as well as remove this freaking writeprotect on the dirs. dir structure in the zip file would be the best option i think as it copies 1 on 1 without setting userrights.
this writeprotect option is set on a hidden part of the systemflashdrive. in the mft i think. strange thing is that i got acces to my windows folder through activesync and it doesnt work on vista mobile device center.. frankly i have no idea what i did but it seems something in the pc as it works on my xp machine and not on vista. i didnt change anything yet on the phone itself relating to this.
pocketcommander www.totalcommander.com is able to ignore or overwrite the writeprotected files in windows dir so there must be a sollution to this.
i dont have the proper tools to do all this stuff but it would be the fastest way to extract all files from all cabs one need into one zip file and let mortscript handle the unpacking and settings of the registry. this way theres no need for autorun cabs merely the UC SD installer. maybe someone can make an nice logo for the custom uc installer.
da_jojo said:
yes yes yes that is what i mean exactly my friend
i mean both ... it would save space on the storagecard as well as remove this freaking writeprotect on the dirs. dir structure in the zip file would be the best option i think as it copies 1 on 1 without setting userrights.
this writeprotect option is set on a hidden part of the systemflashdrive. in the mft i think. strange thing is that i got acces to my windows folder through activesync and it doesnt work on vista mobile device center.. frankly i have no idea what i did but it seems something in the pc as it works on my xp machine and not on vista. i didnt change anything yet on the phone itself relating to this.
pocketcommander www.totalcommander.com is able to ignore or overwrite the writeprotected files in windows dir so there must be a sollution to this.
i dont have the proper tools to do all this stuff but it would be the fastest way to extract all files from all cabs one need into one zip file and let mortscript handle the unpacking and settings of the registry. this way theres no need for autorun cabs merely the UC SD installer. maybe someone can make an nice logo for the custom uc installer.
Click to expand...
Click to collapse
I think for that for the SD Autorun UC solutions there are already a few good solutions around some even supporting Mortscript.
And they all are pretty user friendly to.
Depending on what a user wants and knows, using mortscript being cooked in just gives them more freedom to play around customizing a cooked rom.
But it would need more hand work using your method, but it is possible of course.
It boils down to, do you like making Mortscripts to change registry settings or do you prefer making PROVXML files?
And not everyone is into decompiling cab files to make them fit their exact requirements.
But there's only one rule, Copy the Script to device memory and a folder name tat does not contain a space in it's path. And then run the script.
As the Exec: command from autorun doesn't like that.
But mostly the main way i use it is for the Cooked Autorun part.
I control when the Welcome wizard is run, Before Autorun or after the boot.
I can remove the extra parts of the Networkwizardauto.exe files and also run the networkwizard when i want during the process.
All i need to ad to my process is to open the Locale Preferences dialog during this process and then finish it of with Syncrotime. (or asking for the choice if you want threaded SMS on or not, the possibilities are plenty)
Put all the Setting up your device options after each other for those users that don't have the know how of how to use UC to setup their personal settings.
I even delete the back up files for the one App that i only get installed correctly through a cab file
DelTree( "\Windows\AppMgr\SRS Labs SRS WOW HD" )
So i hope that those that cook or customize and want even more control and detail into what happens can appreciate this.
I know i'll keep using this, and adjusting all my OEM packages to it. Because i have experienced the overall speed improvements in the Rom because of it.
I'm not a Pro in Mortscript and myself i only use the fairly simple commands.
i see.. thnx for explaning
it would be far simpeler using the xmlprov
unless one requires the extra functionality of mort script
the SRS wow HD is a driver enhancement so it needs the system to detach the driver which is only possible with the installer . hence cab files work good cause the're installed by the windowsinstaller which can temp disable the driver.
Instead of MortScript, there is a Yonsm's CeleCmd that perform roughly the same thing.
Check it out!
http://www.yonsm.net/read.php?329
V
vibranze said:
Instead of MortScript, there is a Yonsm's CeleCmd that perform roughly the same thing.
Check it out!
http://www.yonsm.net/read.php?329
V
Click to expand...
Click to collapse
Hey Vibranze, Long time no See.
Would you mind translating
Mort has a bigger fanbase here on XDA.
Yeah, long time no see How are you?
I really not used to your new avatar, without the cigarette it's not like you at all hehe
Actually you can try to download it and check out the sample, it's very easy to understand. I attached here for you
Anyway, here is the translated page by Google.
V
Noonski said:
Hey Vibranze, Long time no See.
Would you mind translating
Mort has a bigger fanbase here on XDA.
Click to expand...
Click to collapse
Explanations
What Does RFO.mscr do?
What Does CLASC.mscr do?
Which Packages Contain Modules and Why?
There's Files Missing from the Packages?
What Does RFO.mscr Do?
Well this script is copied to the regular Start up Folder in Windows.
I use short file names because as much as possible for anything that goes into Windows folder and have no other use being in the Windows folder then being copied by initflashfiles to another folder.
RFO.mscr basicly is the only file i use an initflasfiles.txt for (goes to \Windows\StartUp\ReplaceFileOperations.mscr)
Because after that it takes over the File Operations of the Default build in initflashfiles method.
Why?
Well You don't need actual shortcut files present in ROM to make them.
Code:
CreateShortcut("\Windows\StartUpDisabled\btdwake.lnk","\Windows\btdwake.exe")
in the RFO i don't put that much actual File Operations.
Only the ones that might be useful.
(Why start up WiFiInit.exe during autorun, if it's only useful after the Autorun reBoot?)
Code:
CreateShortcut("\Windows\StartUp\WiFiInit.lnk","\Windows\WiFiInit.exe")
I basicly set up the Second mortscript that will run after the Autorun reboot.
And i make sure the script is not to short. A script that is to short might actually copy the second script so fast into the autorun folder that it will actually be run immediately at during Autorun.
And i make sure the script deletes itself
Code:
RegDeleteKey( "HKLM" , "Services\SqmUpload" , TRUE , TRUE )
RegDelete( "HKLM" , "init" , "Launch99" )
SetFileAttribute("\Windows\StartUp\ReplaceFileOperations.mscr", "readonly", FALSE)
SetFileAttribute("\Windows\StartUp\ReplaceFileOperations.mscr", "system", FALSE)
CreateShortcut("\Windows\StartUp\WiFiInit.lnk","\Windows\WiFiInit.exe")
Copy( "\Windows\CLASC.mscr", "\Windows\StartUp\Clean AutoShortCutStartUp.mscr" )
Delete( "\Windows\StartUp\ReplaceFileOperations.mscr" )
So you can choose during which Boot you want to do what.
But it's better to do it after the first Reboot in case there is no Autorun installation and the phone reboots before finishing the RFO script.
So the Yummy goes to the CLASC.mscr.
What Does CLASC.mscr Do?
Well this does the actuall JuJu...
It takes over the Job of AutoAttribute.exe, so that can be kicked out of the Rom.
Code:
SetFileAttribute("\Windows\StartUp\Clean AutoShortCutStartUp.mscr", "readonly", FALSE)
SetFileAttribute("\Windows\StartUp\Clean AutoShortCutStartUp.mscr", "system", FALSE)
It Takes over the Job of AutoShortcut.exe and initflashfiles.
(less autoshortcut.provxml files in the final rom for the people to lazy to put these into a .rgu file for correct cleanliness)
Also Autoshortcut.exe is set up to run and check the regsitry at every Boot up, so out with this nonsense.
Code:
MkDir("\Windows\Start Menu\Programs\Office")
CreateShortcut("\Windows\Start Menu\Programs\Office\Adobe Reader.lnk","\Windows\AdobeReaderLE.exe")
And eventually it run some Post Stuff to make setting up the device easier at first boot.
Code:
Run("\Windows\ConnectionSetup.exe")
Delete( "\Windows\StartUp\Clean AutoShortCutStartUp.mscr" )
Message("Thank you for installing A SPC Optimized Rom. ","Installation Finished")
Also sometimes people encounter a registry setting that does not get applied directly because of .rgu or .provxml conflict.
So instead of making a new EXTRA .provxml file to fix this.
The registry setting can be added to a file that is already there.
Code:
RegWriteString ("HKLM", "Software\Microsoft\MediaPlayer\Skins", "DefaultPortraitSkin", "\Storage Card\My Documents\Windows Media Skins\Mono SPC\portrait-htc-touch.skn")
RegWriteString ("HKLM", "Software\Microsoft\MediaPlayer\Skins", "DefaultLandscapeSkin", "\Storage Card\My Documents\Windows Media Skins\Mono SPC\landscape-htc-touch.skn")
Or create a new start up script that runs at every start up when you have these annoying Registry settings that for some reason like to reset to a specific default value.
Code:
WriteFile("\Windows\StartUp\FixRightSFTKey.mscr", 'RegWriteString("HKCU", "Software\Microsoft\Today\Keys\113", "Open", "\Windows\Submenus\Contacts.mbi")^NL^RegWriteString("HKCU", "Software\Microsoft\Today\Keys\113", "Default", "Contacts")')
Less headaches going trough all the files finding the conflicts, as you now have a sure fire hit to get the registry right.
And we all know that eventually you will stumble upon the rgu or provxml file that is causing Havoc. But at least you don't have to stay awake pounding your head to find them.
Which Packages Contain Modules and Why?
Well the ones that do have Modules instead of regular files most propalby..
Work as a Module.
Show improved starting up of the application
Can be made into a module to start with (not all files like this)
Show improved handling speed or usage performance.
So when you do find Modulated files in the packages, these have been tested and found worth modulating.
These days most of the kitchen's have G'Reloc.exe build into the cooking process.
So the chance of Modules overlapping a specific memory allocation/space is fixed.
Some kitchens also offer this functionality to Make Modules of files.
But in some Junior Cheffs cases, that usually will result in (nice term coming) OverModulating.
If the kitchen you are using does not run G'Reloc.exe automatically please do so manually when cooking packages with modules.​

Categories

Resources