Related
where to download - or doesn't exist ?
If you want to get access to the extended ROM you simply have to do perform the standard debranding procedure on you MDA Compact (or whatever brand you have).
Here is how it works:
1) Do a hard reset.
2) Go through all the initial configuration stuff (calibration of touch screen etc.).
3) At some point you will be asked to tab the screen to continue. Right after that the contents of the extended ROM will begin to install themselves. The trick is to tap the screen and immidiately after perform a soft reset.
Once your MDA Compact is done with the soft reset, you will find yourself being the proud owner of a debranded phone/pda. The external ROM will be visible. If you wish to install some of the things on the external ROM simply execute the respective CAB files.
I chose to install the caller ID application as well as the camera patch.
Have fun,
Lars
Hello,
Ok but if you don't want to make a hard reset you can:
go to your windows directory and launch loadvdisk.exe
just for info total commander see this file but the explorer of file not
yes thanks - but still i can't edit the ex-rom
Right, I forgot to mention that you can unlock the extended ROM without a hard reset. However, this is as I see it not particularly useful since everything on the extended ROM has already been installed if you don't go through the debranding procedure. Also as the name Read Only Memory (ROM) suggests you cannot write to it, so it is fairly useless to unlock it if everything on it has already been installed ... except if you want to extract the content of it to post it
/Lars
I don't need to post - there is a lot already on the web. i need to change some preconfiguration with my own cab files for my company.
But it seams that there is no way to do this like with the 2020
Hello,
I read a lot about the big ROM flashing and did this on my XDA mini. Anything seems to work so I'm quite happy until now. One point of concern is still there... what about the apps from the ExtROM that I copied for backup on my harddisk? Using an XDA on the O2 network, we are talking about apps like Homezone and O2 settings.
If I understood the BigROM thing right, I deleted the ExtROM that was executed on a hard reset before. Therefore, after BigROM,
- no O2 app will be loaded after hard reset
- no autostarter, like in the O2 ExtROM, is necessary any more since nothing is loaded after hard reset
- after hard reset, all apps have to be installed once again
- best way to keep the apps secure and appropriate is install all apps once and frequently backup the whole setup
Is this the right way to look at the changes?
Another question about the O2 files: Besides the homezone control, are there alternative programs for the rest (Java, Today screen) or do I need the special O2 apps due to the settings coming with them?
Any help appreciated!
Yes you got it all right! After the Big Storage ROM the Extended ROM bit was deleted from the ROM. The space consumed by the Extended ROM is now available for you to use under the /Storarge folder.
Now, to install the required extended ROM programs just copy them to any folder on the PPC and click on them from the file explorer.
However I would suggest to install a program called CABINSTL. This allows you to run CAB files and install them in the folder of your choice instead of the default folder that consumes some of your precious RAM. I would install these CAB files in the /Storage folder, thus making benefit of the Big Storage ROM
The same applies to any other program you install. Always install it in /Storage. If you don't, after the Big Storage upgrade the only benefit would be of having some extra storage space. If you have an SD Card you don't need this space so might as well use it to install programs and free up the RAM.
If I use the cabinstl programme to manually install my Orange ExtRom files after a BigStorage install - even when I choose a different install location (eg. /Storage) the utility is still installed into the default location (usually somewhere in /Windows/).
I have the same problem. Also i pushed the option not to delete the cab file, but after install they are deleted I know i can make them read only, but i cannot do this trough explore of activesync.
It appears that some CAB files have their install location 'hard coded' into the file so it cannot or should not be changed.
I guess that this is to ensure that the utility works correctly so I don't suppose that there is much that we can do.
You can edit the CAB on your PC and define your own folder. However this is not recommended as the code for these programs may have some paths that are hard coded as well.
Anyway these couple of CAB files will not impact your overall RAM situation at all. On mine I only installed JAVA, MMS, Bluetooth and Camera patches from the Extended ROM. I don't need the rest.
Thanks for your help! So is it okay to install anything in the storage that goes there without complaining? As I installed PocketPlus there, Windows looked at it like on the memory card and displayed a message that installing apps there could become a problem during startup.
Thanks again and bye!
Hi guys
Ive recently got my jammin and have found that without installing the extended rom the device speed is alot better.
Bu theres 1 prog in the extended rom that i use alot which is the phonepad ...Ive found the cab located in the rom but the problem is the cab also install the voice app / pdf viewer and java app.
Is there a cab available thatll just install the phonepad and nothing else?
Thanks
if you post the cab we can easily extract the parts you don't want, or you can do it yourself with WinCE Cab Manager
Ok brilliant ive attahced the cab
Thanks alot
This cab doesn't install the voice cab or anything like it.
It makes 4 shortlinks and addssome values to the register, that's all it does.
so it just installs the phonepad...is there anyway of deleting all the etxra links .etc .etc and just it installing the phonepad ?
No it doesn't install the phonepad, in fact it doesn't install any software at all, this cab.
However you can delete the shortlinks, located here; /windows/start menu/
But remember you still don't uninstall/delete the actual software.
Ah , ok ....so do you know the phone pad (touchpad thng for texts .etc .etc) ....Not smartdialing program...Is this actually located on the rom itseld or does it install from the extended rom.
As i thought it was installed form the extended rom but now this as got me thinking its hard encoded in the rom itself?
Is this rite on HTC devices?
Thanks
The touchpad itself is included in the rom, however I've seen you can enable/disable some of those input pads with some registry settings.
Unafortunatly I don't know what settings and if it can be done on all htc devices.
On my wizard it's enabled by default.
ok ,Thanks for the help / info
after few days of playing around, then found a solution to WRITE to Ext-ROM which persists after soft-reset.
All praise and thanks are to God the Most High.
Here is the solution; Tested for prophet ROM2.15.13.27 -G4 but should work for over chipsets and even other handsets e.g Wizard
To Unhide Ext-ROM --- (this is already known by most- but include for completeness)
Need following registry changes:
HKEY_LOCAL_MACHINE \System\StorageManager \AutoLoad\TRUEFFS_DOC1
"Bootphase"=dword:2
HKEY_LOCAL_MACHINE \System\StorageManager \Profiles\TRUEFFS_DOC1
"MountHidden"=dword:0
To Rename EXT-ROM
HKEY_LOCAL_MACHINE \System\StorageManager \Profiles\TRUEFFS_DOC1
"Folder"=string:Storage
--- can call it anything you like instead of "Storage"
To Unlock the EXT-ROM
HKEY_LOCAL_MACHINE \Drivers\Builtin\TRUEFFS _DOC1
"SoftwareWriteProtect" =Dword:0
THIS key is the mainchange that will enable write protect, but it keeps reverting after softreset. To get around this, will need to change the following also.
HKEY_LOCAL_MACHINE \Drivers\Builtin\TRUEFFS _DOC1
"AutoDPDMode"=Dword:0
Then Softreset.
Now should be able to write and install to Ext-ROM/Storage
If any problem can return the last key to original value
HKEY_LOCAL_MACHINE \Drivers\Builtin\TRUEFFS _DOC1
"AutoDPDMode"=Dword:1
-----not sure what this key does??
then soft reset again.
this worked for me . try at own risk!!
Enjoy
All praise and thanks are to God the Most High
AbuYAHYA
Ps. let me know if it works or not for you...if anyone wants to make a Cab file then would be helpful
did any1 try this??
Works!!
Yes it works flawlessly....
Thanks
FeiYu
Not On The Wizard
That's a very old and known trick.
But: it does not work on the Wizard !
Prophet, etc. all OK
Cheers
hrb
Does that mean that i can install a dutch rom, by downgrading my G4 device.
Hopefully it does.
Cheers
Hello,
i installed the AKU 2.3 Rom "2006-10-14_Upgrade_Rom_lvsw_edition.exe" and don't habe these entrys in my registry:
AbuYahya said:
HKEY_LOCAL_MACHINE \System\StorageManager \Profiles\TRUEFFS_DOC1
"MountHidden"=dword:0
To Unlock the EXT-ROM
HKEY_LOCAL_MACHINE \Drivers\Builtin\TRUEFFS _DOC1
"SoftwareWriteProtect" =Dword:0
Click to expand...
Click to collapse
AbuYahya said:
THIS key is the mainchange that will enable write protect, but it keeps reverting after softreset. To get around this, will need to change the following also.
HKEY_LOCAL_MACHINE \Drivers\Builtin\TRUEFFS _DOC1
"AutoDPDMode"=Dword:0
Click to expand...
Click to collapse
this key is in my device at:
HKEY_LOCAL_MACHINE \Drivers\Builtin\TRUEFFS1
"AutoDPDMode"=Dword:1
is it the same key?
thanks
John
John-Wu said:
Hello,
i installed the AKU 2.3 Rom "2006-10-14_Upgrade_Rom_lvsw_edition.exe" and don't habe these entrys in my registry:
Click to expand...
Click to collapse
I instaled the same ROM so abit strange you don't have writeprotect key. Possible options maybe perform backup and hard reset and then recheck for the latter key....Or....just make the keys.
I think I added this key also myself but not 100% sure.
HKEY_LOCAL_MACHINE \System\StorageManager \Profiles\TRUEFFS_DOC1
"MountHidden"=dword:0
As for writeprotect key then try adding. if the dword remain at 0 after soft reset then should work. if not try changing the Dword for AutoDPDMode form 1 to 0, aswell as the softwarewriteprotect key as below
To Unlock the EXT-ROM
HKEY_LOCAL_MACHINE \Drivers\Builtin\TRUEFFS _DOC1
"SoftwareWriteProtect" =Dword:0
HKEY_LOCAL_MACHINE \Drivers\Builtin\TRUEFFS _DOC1
"AutoDPDMode"=Dword:0
hopefully should work.
Abu Yahya
add to wiki
hrb said:
That's a very old and known trick.
But: it does not work on the Wizard !
Prophet, etc. all OK
Cheers
hrb
Click to expand...
Click to collapse
sorry to hear it doesn't work on Wizard.
If it was well known then maybe some-one should add it to the WIKI page. As several have asked how on a few threads with no replies both here and BUZZdev.net.
Abu yahya
doesnt work on my Jamin with the 16Mb_AKU2.3_GSM02.30.21_Extrom-4PDA.ru.exe rom
I had to use buzz's unlock tool to let me write to my extended rom.
I have upgraded to the PDAMobiz 16MB ROM. Unhiding the extrom via the registry entries work. But unlocking it doesn't.
I too do not have HKEY_LOCAL_MACHINE \Drivers\Builtin\TRUEFFS _DOC1 key. So, I manually created it with the entries as posted, but it didn't work. (yes I did a soft reset after shutting down for 30s or so).
I then proceeded to go to HKEY_LOCAL_MACHINE \Drivers\Builtin\TRUEFFS1 and change the "AutoDPDMode" to 0, and SoftwareWriteProtect to 0. There are 3 such keys: TrueFFS, TrueFFS1 & TrueFFS2. I changed all 3.
Unfortunately, it still didn't work...
But Buzz's unlocker prog worked. It didn't before when I was using the official Dopod ROM.
To every body !
I've update my rom to RUU-Prophet-G4-AKU2.2-2.20-2.47.21-Jester-r1.exe. when finished, the extended rom can't use. Change reg not work. So when i lock up at the rom "AKU2.3.1_LvsW_Edition_2006-11-28" i find there're 2 files : extunlock.exe and UnlockExtRom.cab. Run 2 files and finally i can use extended rom with no restrict.
My device is O2 Neo. Hope this usefull for some one
Would you please be so kind and upload these two files to the ftp? I'd like to try if it works with the last original QTEK-ROM.
Thank you
hi all.
've been reading some very interesting things in the forum the last few days.
i think you re great.
As far as:
Show extended ROM: [HKEY_LOCAL_MACHINE\System\StorageManager\AutoLoad\ TRUEFFS_DOC1] "Bootphase"=dword:2
[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\ TRUEFFS_DOC1] "MountHidden"=dword:0
Hide extended ROM:
[HKEY_LOCAL_MACHINE\System\StorageManager\AutoLoad\ TRUEFFS_DOC1] "Bootphase"=dword:1
[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\ TRUEFFS_DOC1] "MountHidden"=dword:1
they work ok for me with 2.9.7.24 wwe ROM
2.9.7.8009 extROM
(IPL&SPL 2.09.0001)
after soft reset i can see Extended_ROM2 on my file explorer.
when i check the file properties with resco file explorer all files inside extended_rom folder are read only(which can be changed of course).
so i can easily modify the cab files inside the extended rom along with config.txt entries.
last, changing all files to read only, reverting the registry keys to hide ext_rom
and hard reset.
crazyd said:
Would you please be so kind and upload these two files to the ftp? I'd like to try if it works with the last original QTEK-ROM.
Thank you
Click to expand...
Click to collapse
You can load "AKU2.3.1_LvsW_Edition_2006-11-28.exe", then right click to this file, select "extract to ..." to get these files hope this work on your !!
Great, it works again! Thank you for your help.
could you please to upload just two files ( extunlock.exe and UnlockExtRom.cab.) only, cause my connection is very slow for getting "complete packet rom".thx
Here you are!
Thaks bro, but still can't edit/delete my ext rom,
one more question, is this ROM can work with Simtolkit App?
Have tried the two files but I still can't install to ExtRom. It says ExtRom2 on my Dopod 818 Pro G3. Currently having more problems with syncing. Ay advise?
AbuYahya said:
HKEY_LOCAL_MACHINE \Drivers\Builtin\TRUEFFS _DOC1
"AutoDPDMode"=Dword:0
Click to expand...
Click to collapse
I found the following document about the Trueffs file system.
Download the following document http://www.mobilediskonchip.com/NR/....pdf|Installing_TrueFFS_for_Win_CE_Rev4.7.pdf
The AutoDPDMode parameter is described on page 12 as:
“AutoDPDMode”: This option enables Auto Deep Power-Down mode, which reduces the
average power consumption of DiskOnChip. Auto mode puts DiskOnChip in Deep Power-Down
mode automatically after each driver command, and takes DiskOnChip out of Deep
Power-Down mode automatically when the driver is called again. Using this mode disables the
option of booting from DiskOnChip via software reset, as the IPL cannot be accessed from Deep
Power-Down mode. In order to boot from a DiskOnChip device in Deep Power-Down mode, a
hardware reset or powering off is required. This registry entry has no effect on DiskOnChip
devices that do not support Deep Power-Down mode.
dword:1
Click to expand...
Click to collapse
Looks to me that AutoDPDMode has nothing to do with the write protection of the Extended ROM...
Regards,
--eluth.
Ok, had to wipe my computer and start again (Do it ever couple of months). So I tried to run BuildOS again but i get a message as below :
Code:
BuildOS.exe - Application Error
The application failed to initialize properly (ox0000135). Click OK to terminate the application.
Can anyone shed some light on why this will not work for me anymore!!!
Did you re-install Net Framework 2?
this is .NET framework related indeed
Thnak you both!!! I should not be let to use this!!! That worked for me!!!
I'm so dumb!
Glad I could provide a small assist. I owe you big for the RK PDF docuument (which I've used over and over again this past week) and your tip on removing the setup dll file !
Forums at their best!
saeba said:
Glad I could provide a small assist. I owe you big for the RK PDF docuument (which I've used over and over again this past week) and your tip on removing the setup dll file !
Forums at their best!
Click to expand...
Click to collapse
Well i am working on the setup.dll files, as i have found with some packages this is needed, but you can only have one file like that so!!! am doing testing on different way for doing it!
Me too. After working with the extended ROM, I have this new idea of how to customize a newly installed ROM:
After installing the ROM:
1) Create/Use a cab file that sets the autorun registry pointers to point to my Storage Card (instead of extended ROM)
2) Maintain a library of the 20+ application and customization cab files on my storage card that I need
3) Create a config.txt with pointers to these cab files
4) execute autorun.exe which then automatically runs all these cab files
5) Sit back and wait for the installations/customizations to complete !
This makes it easy to keep a library of these apps on my storage card and as new versions arrive, just toss them in there and update the config.txt install file. If I decide to go with a new ROM, no work to integrate packages into it. And no limits on the number or size of the cab files I can use this way like with the extended ROM (only 9.5 mb space there).
I'm thinking that if I don't enable the LOCK on input, I can even interact with those cabs that have a setup dll requiring input. Haven't tried that yet though.
saeba said:
I'm thinking that if I don't enable the LOCK on input, I can even interact with those cabs that have a setup dll requiring input. Haven't tried that yet though.
Click to expand...
Click to collapse
Wow, let me know if you get this working, as I'd like to do this myself. Its exactly what I do (but manually) after a new flash. I have a Setup Files folder on my SD card, and I just go down through each of the cab's I've stored there to get back up and running as quickly as possible. But my biggest issue is the ones that require manual input.
This seems like it should be doable though, as you can do similar with ActiveSync. After a new flash just go back to ActiveSync and tick off all the stuff you want to reinstall, and it will do them one right after the other. Only ones you have to be careful of are any that require a softreset after install.
saeba said:
Me too. After working with the extended ROM, I have this new idea of how to customize a newly installed ROM:
After installing the ROM:
1) Create/Use a cab file that sets the autorun registry pointers to point to my Storage Card (instead of extended ROM)
2) Maintain a library of the 20+ application and customization cab files on my storage card that I need
3) Create a config.txt with pointers to these cab files
4) execute autorun.exe which then automatically runs all these cab files
5) Sit back and wait for the installations/customizations to complete !
This makes it easy to keep a library of these apps on my storage card and as new versions arrive, just toss them in there and update the config.txt install file. If I decide to go with a new ROM, no work to integrate packages into it. And no limits on the number or size of the cab files I can use this way like with the extended ROM (only 9.5 mb space there).
I'm thinking that if I don't enable the LOCK on input, I can even interact with those cabs that have a setup dll requiring input. Haven't tried that yet though.
Click to expand...
Click to collapse
Why dont you just point the reg to your card, !!! Just like faria point it at the windows folder, you can point it at storeage card!!!
funman said:
Why dont you just point the reg to your card, !!! Just like faria point it at the windows folder, you can point it at storeage card!!!
Click to expand...
Click to collapse
Yes, thought of that. To do it as part of the ROM install though, you need to edit the ROM itself (the OEMOPERATORS registry file in Faria's build) and rebuild the ROM.
But I'm thinking of a mechanism that will work with no changes to the base ROM. That way, can pick up any of these wonderful ROMs that are coming out, just install and do this customization separate.
mfrazzz said:
But my biggest issue is the ones that require manual input.
Click to expand...
Click to collapse
Yep, same here. Funman taught me one trick - the manual input is done via a setup dll file in the cab. On some cabs, you can delete this and work around it (this worked for PocketBreeze and PocketWeather, didn't work for iLauncher). I used this trick and put these two cabs in extended ROM.
I was going to wait for the new Faria WM6 V3 ROM to do some more testing, but since there's interest, I'll try out a test regarding the LOCK tonite. I have verified the other stuff works (the autorun registry changes via a cabinet, running autorun on the storage card after the install), but do need to check that.
And congratulations on the ROM release! Looks like a very nice packaging job !
saeba said:
Yes, thought of that. To do it as part of the ROM install though, you need to edit the ROM itself (the OEMOPERATORS registry file in Faria's build) and rebuild the ROM.
But I'm thinking of a mechanism that will work with no changes to the base ROM. That way, can pick up any of these wonderful ROMs that are coming out, just install and do this customization separate.
Click to expand...
Click to collapse
You are looking at this too much!!!
You could just do as below!
Code:
[HKEY_LOCAL_MACHINE\Comm]
"AutoRun"="\\Storage Card\\cabs\\autorun.exe"
"AutoRunCFG"="\\Storage Card\\cabs\\config.txt"
"AutoRunType"=dword:00000000
"TurnRadioFlag"=dword:00000000
Then in the config :-
Code:
CAB: \Storage Card\cabs\example.cab
But you dod have a problem of it freezing if you take out the card!
OK. We're mostly on the same page then. As you mentioned, I created a small cab file that sets:
[HKEY_LOCAL_MACHINE\Comm]
"AutoRun"="\\Storage Card\\cabs\\autorun.exe"
"AutoRunCFG"="\\Storage Card\\cabs\\config.txt"
I then just manually select/run autorun.exe against my custom config.txt.
When autorun.exe runs as part of the initial rom run, it locks out input so any cabinets that prompt for input breaks the execution. We're just wondering if it could work without the lock so that any cabinet (other than those that restart the system) could be executed in this manner. I have a handful of cabinets that do prompt for input that cause problems !
saeba said:
OK. We're mostly on the same page then. As you mentioned, I created a small cab file that sets:
[HKEY_LOCAL_MACHINE\Comm]
"AutoRun"="\\Storage Card\\cabs\\autorun.exe"
"AutoRunCFG"="\\Storage Card\\cabs\\config.txt"
I then just manually select/run autorun.exe against my custom config.txt.
When autorun.exe runs as part of the initial rom run, it locks out input so any cabinets that prompt for input breaks the execution. We're just wondering if it could work without the lock so that any cabinet (other than those that restart the system) could be executed in this manner. I have a handful of cabinets that do prompt for input that cause problems !
Click to expand...
Click to collapse
Ya if you dont have LOCK in your config, it still will work!
funman said:
Ya if you dont have LOCK in your config, it still will work!
Click to expand...
Click to collapse
Yes it does, but even if you remove the lock, you still can't respond to the prompt from the running cabinet. It just hangs the AutoRun process :-(. I just finished running a test to check this out.
This still goes a long way in helping automate my setup. I currently have about 26 cab files that I use to "customize" my system. 5 of those prompt for input and 2 more restart the system. So, I could automate the execution of 19 of them. I can use your "delete setup dll" trick and get 4 more to automate. So that means 23 of 26 could be automated !
Thanks!
saeba said:
I currently have about 26 cab files that I use to "customize" my system. 5 of those prompt for input and 2 more restart the system. So, I could automate the execution of 19 of them. I can use your "delete setup dll" trick and get 4 more to automate. So that means 23 of 26 could be automated !
Click to expand...
Click to collapse
You don't necessarily have to restart the phone after installing every cab that asks for it. Most just need the restart to work properly, but your not going to use them yet, because you are still installing all of your programs, so the restart can wait. Personally, I just cancel the restart notice and finish installing all of my cab before a singal restart for all of the cabs installed.
Ron
lokmeup said:
You don't necessarily have to restart the phone after installing every cab that asks for it. Most just need the restart to work properly, but your not going to use them yet, because you are still installing all of your programs, so the restart can wait. Personally, I just cancel the restart notice and finish installing all of my cab before a singal restart for all of the cabs installed.
Ron
Click to expand...
Click to collapse
I will have to find it, but there is a reg key that i chnaged that you can set it so you would need a reset after different cabs, but you can turn it off too!!! Cus i always got a prblem when trying to install my GPRS cab as it would say that it needed to restart, but now it does not say it!!! I will have to go back over reg keys i have chnaged and see if i can work it out again!
saeba said:
Yes it does, but even if you remove the lock, you still can't respond to the prompt from the running cabinet. It just hangs the AutoRun process :-(. I just finished running a test to check this out.
This still goes a long way in helping automate my setup. I currently have about 26 cab files that I use to "customize" my system. 5 of those prompt for input and 2 more restart the system. So, I could automate the execution of 19 of them. I can use your "delete setup dll" trick and get 4 more to automate. So that means 23 of 26 could be automated !
Thanks!
Click to expand...
Click to collapse
Just a thought but try taking the line of that says the background, i was thinking that if it does not have that in the process will it let you see the input window that comes up, if it does maybe it lets you press the buttons too!