Related
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.
I downloaded the upgrade from O2 and run it on my QTEK 2020. The process finished without any errors but I am surprised/dissapointed that:
-this upgrade IS NOT the one announced by Microsoft recently i.e. WM2003 second edition
-the applications that are listed in the pdf instructions have not been installed on my QTEK
-the BT remains the same
Am I missing something or was expecting too much from this update?
Well this upgrade is just bug fixes and no new features. The Windows Mobile 2003 Special Edition (SE) is just out of the door. I just with testing and all we would be luck to get this towards the end of second quarter or the third q. Even then I am not sure if it is going to be free or even offered as an paid upgrade.
Regards,
Kueh.
What about the applications that are listed in the pdf, I think something is a miss as I haven't even got the o2 active interface after the upgrade...nor any of the new apps.
check if the ext-rom is proberly installed...
you can even run this manually.
how do I check that it is properly installed?
how do I got about reinstalling it? is it just a case of opening the installer in winzip and then rerunning one of the files?
Enable the hidden extended rom by using the attached cab. Reset it. Use file explorer to view the extended rom in the root directory. if your extended rom has been installed correctly, you should be able to find o2ActiveUIEngl.CAB. run it to get your active O2.
:lol:
When my XDAII rebooted after upgrade there was no O2Active and no links to it - I just did another hard reset and it installed itself correctly the second time around.
extened rom
Thanks all, i used the ext rom viewer and managed to install the missing new applications. i might do a hard reset anyway just to be sure.
thanks again.
Please any one can till me how to etid my ROM W2003SEWWE 2.06 so I can add some programs that I use alote.
I have tried (Windows Mobile 2003 ROM Editor) and I did use passwords (0x20040304/305) bu it did not work.
Thanks
If you want to edit extended ROM (ms_.nbf) then...
1. In "Files of type" , you just select to open file type as WM2003 Extended ROM (ms._nbf) don't use auto detection.
2. Using password 0x20040305 when prompt.
3. Don't forget to save ROM before exit.
Have Fun!
Thanks, it did work.
try the patch
try the patch...don't need to put a password
thread: http://forum.xda-developers.com/viewtopic.php?t=17204&start=75
download: http://forum.xda-developers.com/download.php?id=3208
Hello,
even with the update and not using autodetection I can not open a OS upgrade built from lumpi stefans environment (The T-Mobile upgrade also).
Anyway I do not understand what those different files mentioned contain.
- Is it possible to add some things to the ROM area using a different file than the OS upgrade (no need to loose all changes that were made meanwhile)?
- Once the device is upgraded I would like to remove something from the ROM is this possible (how can I get the current data from my xda back to the ROM Editor)?
(Assuming I get a hint on how to open successfuly the *.nb? ...)
Thanks in advance!
udk
hi ppl,
today I ve made rom with the romkitchen, it was 2003 final and everything went ok, phone was functional until I used to try to install some newer versin of the programs I previously included in the rom. That didnt work (of course) so I decide to put another rom without those programs so I can install newer versions but when I run the romkithen exe computer report
in the dos window
error getconnectiontipe - unspecified error
error getting connectiontype
and the program for the patching report that he is trying to get the data from the device and after that he reports that
"cannot execute the remote communication program, please make sure that the usb/serial cable is properly connectes"
of course cable is connected, device syncing with the active sync and the icon is green, used to try to soft reset pc and pocketpc, to hardware reset pocket pc, to connect it to other pc and patch there, to install active sync 3.7.1, to reinstall active sync 4.2, to reinstall usb drivers on the pc, to put sim card and sd card out and to patch then... nothing helped...
what can I do ? is that due to the windows 2003 instalation on the pocket pc (had same version on other wallaby without the problems) ? can I solve that some way ?
I ve read before that patching can be performed from the SD card so I found the xda tools and osi image tool but couldnt found rom nd1 file anywhere (was stupid and didnt make copy of my previous rom)... which rom can I use just to enable USB connection and after that I ll patch it with the "normal" rom from the rom kitchen...
Ive checked those roms http://wiki.xda-developers.com/index.php?pagename=ROMVersions but didnt find any nd1 file in the files I ve checked, can I use those roms with osi image tool eventually ?
which one ?
Lots of questions ... Sorry people ...
I can use it in this condition too but I d rather have an opportunity to flash it to some other version maybe.
Best regards to the community !
I think it´s just the problem that the ROM prohibits flashing via EXE-file. You have to flash via SD-Card.....
You find the ROm to write on the SD-Card in the EXE-FIle. Just extract the exe using winzip, and then you will find it in a subdirectory (normally english, or dependent on the ROM-Language...)
Stefan
Thanks a lot Stefan, so I can use some ROM from the page http://wiki.xda-developers.com/index.php?pagename=ROMVersions ?
Any advice which one should I take please (Im not using any of the operators noted there, just looking for some rom that will function ok) ?
Thanks m8 !
Yes, you can take any rom of it. Mostly the T-Mobile prohibits flashing via EXE-File, but Flashing via SD-Card is more secure in my opinion. So i´ve done 99,9% of my flashes via SD-Card, and you can believe me, i´ve done it a lot of times.....
By the way, which software has to been updated in my romkitchen?
If you give me the hints, i could try to update them....
Stefan
thanks a lot for your time and advices Stefan !
Its not a huge problem but probably we share same opinion - most of the tech guys like to see that everything work fine, if something doesnt work then we re not satisfied.
Basically problem is that I included spb pocket plus in the rom and therefore I cant install spb weather which demands pocket plus v 2.5+ and version in the rom is 2.0. I cant upgrade it coz its in the ROM, used to try to remove it from the registry but no luck, used to install latest spb diary coz the spb weather also work with the diary but looks like that the first thing weather perform is checking of the pocket plus version and if the version is not 2.5+ it stops the installation...
Probably for the most of the people spb weather is not a reason for loosing couple of hours in trying to change rom in wallaby but as I ve mentioned I like the things that work 100%, if some electronic/computer stuff work at 99% that usually bother me. Stupid - I know but thats the way it is.
Im going to patch it thru the SD, thanks again for the all your efforts now and before.
GL & HF !
Sorry...
Still need help, using the OSI tool I copyed NK.nbf file from 4.02.04_eng rom to "XDA SD Card Slot -unknown size" - coz I dont have card reader/writer at the present moment so I tought that I can put the file via the cradle connection while the card is in the wallaby...
Checked the card from the wallaby file explorer but nothing is on the card, since I had expirience with direct writing to c64 and amiga disks writing I assumed that file could be written directly to the card without OS instructions but after the reset of the wallaby it report that card shoud be formatted to become writable... Is that normal, or I should wait for the card writer reader to put the file properly to the sd card ?
If possible please help me with the link for the OSI tool patching, I cant find it anymore, checked thru the site but no luck, dont know what I have to press so the wallaby read the rom from the sd card.
Thanks Stefan & all others
success !
No help needed, I ve made it...
So dont have any fears as Stefan told unpack the rom from the self extracting archive and run osi tool, in the source field set nbf as a file type and then select extraced rom.
As a target you can set card reader/writer and also you can put the SD card in the wallaby as I did. Set the XDA SD card as a target in that case.
Its normal that after the writing (no message that writing is successfull, when it is finished OSI tool will stop) SD card become unreadable to wallaby.
Then perform actions as noted in SD card patching info
http://wiki.xda-developers.com/index.php?pagename=Wallaby_HT_FlashSD
Hold the power button and soft reset. You'll be taken to the below screen:
SD DOWNLOAD
Card Type:
CE OS & BOOT
Press action to Download
Or
Press REC to Exit
Press action to download and it will start the download/restore from the SD card.
Follow the on screen instructions once its "Completed" which will consist of a " Hard Reset"
Action button mentioned above is middle button - "D PAD"
Works like a charm, now I have o2 win 2002 and later I ll patch it to 2003 SE again but without pocket plus.
Thanks Stefan and community !
This is my first contribution to xda-developers.com, and hope that someone finds it useful.
DevPrep (Device Prep) is intended to be a replacement for user customisation using autorun.exe or runcc.exe. It has more options than these tools, and supports the following commands: -
CAB - CAB file installation
CFG - Include another config file for processing
CPY1 - The first part of the copy command, specifying the source file name
CPY2 - The second part of the copy command, specifying the destination file name
DEBUG - (Enable/Disable) Turns debugging on or off, which creates a .log file in the same path as your config file
DELE - Deletes a specified file
ERR - (Enable/Disable) Turns error reporting on or off, so that errors are either displayed in the interface, or ignored
EXEC - Allows an executable to be run, or a CAB file to be installed interactively when used with the HIDE or LOCK commands
HIDE - (Enable/Disable) Allows other applications to take the focus away from the DevPrep tool, to allow user interaction to take place (e.g. interactive CAB installs)
LOCK - (Enable/Disable) The same as the HIDE command, but in reverse (i.e. LOCK: Enable is the same as HIDE: Disable)
RST - Resets the device (should be the last command specified, as DevPrep will not continue processing after this)
XML - Processes XML configuration and provisioning files
The commands are used in the same way as autorun.exe and runcc.exe, (for example "CAB: \Storage Card\myfile.cab") however the spaces between the command and the parameter aren't important.
Rather than cooking DevPrep directly in to the ROM, there is a DevPrepLauncher utility that can be cooked in and launches DevPrep.exe from the storage card. If DevPrep doesn't exist, it just ignores it.
This way if there are updates to DevPrep, the new version can just be copied to the storage card without needing to re-flash.
Both the OEM package for DevPrepLaunch and the CAB file for DevPrep are attached. Install the CAB file to the Storage Card.
http://rapidshare.com/files/363384988/DevPrep.cab
http://rapidshare.com/files/363385916/DevPrepLaunch.zip
Wow!
I was just looking for something like this. I have never used a tool like this before. But the Imagio (my phone) just got HSPL'd. So I am thinking about using something like this. Do you mind a noob question? So- if I set this up, after I flash a ROM or do a hard reset- I could set this up to auto install all my .cabs? Do I need both "DevPrep.cab" and "DevPrepLaunch.zip" what is the difference?
maisonpulaski said:
I was just looking for something like this. I have never used a tool like this before. But the Imagio (my phone) just got HSPL'd. So I am thinking about using something like this. Do you mind a noob question? So- if I set this up, after I flash a ROM or do a hard reset- I could set this up to auto install all my .cabs? Do I need both "DevPrep.cab" and "DevPrepLaunch.zip" what is the difference?
Click to expand...
Click to collapse
Yep, you can use it to re-install your .cabs. You can also use RunCC.exe or autorun.exe, but I wrote this tool because I had issues with the interactive installations.
You need DevPrepLaunch if you are cooking your own ROM and you want it to start automatically when you do a hard reset.
If you aren't cooking your own ROM, you can just install DevPrep.cab and then run it manually.
Thanks
Thanks for the reply. I am still waiting to flash a ROM. Nothing out yet I am interested in. But when I do I might try this. Is it very complicated to set up? And- what do I do if I set it up on my phone, then flash a new ROM- wouldn't it be wiped off the phone?
maisonpulaski said:
Thanks for the reply. I am still waiting to flash a ROM. Nothing out yet I am interested in. But when I do I might try this. Is it very complicated to set up? And- what do I do if I set it up on my phone, then flash a new ROM- wouldn't it be wiped off the phone?
Click to expand...
Click to collapse
Yeah, that's right, it would get wiped after every new flash so you would need to cook the DevPrepLauncher in to your ROM that way it is kept there.
Another option is to just run it manually off the storage card after you hard reset.
matm said:
Yeah, that's right, it would get wiped after every new flash so you would need to cook the DevPrepLauncher in to your ROM that way it is kept there.
Another option is to just run it manually off the storage card after you hard reset.
Click to expand...
Click to collapse
Duh to me! It will be on the storage card. Not the device memory. So all of the settings are safe? I mean- after I flash- I would just install it again and run it? I wouldn't have to set it all up all over again?
maisonpulaski said:
Duh to me! It will be on the storage card. Not the device memory. So all of the settings are safe? I mean- after I flash- I would just install it again and run it? I wouldn't have to set it all up all over again?
Click to expand...
Click to collapse
Yep, that's right. So, for example, the directory structure might look like this: -
\Storage Card\DevPrep\Application\DevPrep.exe <-- The application
\Storage Card\DevPrep\Config.txt <-- The config file with the commands (installing cabs, settings preferences, etc...)
\Storage Card\DevPrep\Installs\myApplication.cab <-- An application you want to install
\Storage Card\DevPrep\Settings\mySettings.xml <-- Some preferences you want to apply
Awesome!!
I just fell off my chair reading your thread. Just after finishing these threads ;
First read this to understand User Customization and filling SDConfig.txt;
ROM Chefs: SDAutoRun gives customziation to everybody!
While reading, in a way, I replaced 'SDAutoRun' with 'DevPrepLauncher' and 'AutoRun' in \Windows\ with 'DevPrep' on \Storage Card\
[GUIDE] 60 Universal Tutorials for Customizing any Device and Cooking
[App] ROM Flashing Junkies: User Customization is here!
Within this thread there is an application called SDConfig.txt creator which was created by DoeDoe's. Currently it is replaced by;
[Release] UC ROM SDConfig.txt Builder (reborn) [Prikolchik Ed.]
and ofcourse;
SDConfig.txt Builder Mobile by l3v5y
http://forum.xda-developers.com/show....php?p=2114491
I'm adding your application too! What a contribution
Thanks a lot matm,
Senax
Thanks Senax!
tried it...
Hello- I had some time the other day so I sat down to try and figure out the app. I installed on my storage card. Did a soft reset. Ran the app. It went to the "Preparing Device" screen and stayed there for about 30 minutes. Does it take longer than that? I gave up.
I have the HTC Imagio (Whitestone) WinMo 6.5. Custom Rom. But it is very near stock -only removed Sense and Verizon Wireless needless software.
Thanks for any pointers.
Will someone just attach the files to a post here. I hate spending half a day trying to get an 85 kb cab file since rapidshare always thinks I'm downloading another file (probably because of the network I'm on). Thanks.
maisonpulaski said:
Hello- I had some time the other day so I sat down to try and figure out the app. I installed on my storage card. Did a soft reset. Ran the app. It went to the "Preparing Device" screen and stayed there for about 30 minutes. Does it take longer than that? I gave up.
I have the HTC Imagio (Whitestone) WinMo 6.5. Custom Rom. But it is very near stock -only removed Sense and Verizon Wireless needless software.
Thanks for any pointers.
Click to expand...
Click to collapse
Hi maisonpulaski,
Can you please post your config file?
matm said:
Hi maisonpulaski,
Can you please post your config file?
Click to expand...
Click to collapse
So after reading your reply it suddenly dawned on me -I have no idea what I am doing. So it is not your app it is me (pretty sure). I thought I would open it and then it would walk me through setting it all up. Now I am thinking that I need to write up a "Config file". No idea how to do that. So I am probably a lost cause. I am guessing you use notepad or something? Anyways -sorry.