Custom Extended ROM apps don't install - P3600 Software Upgrading

Custom Extended ROM apps don't install - P3600 Software Upgrading

I've got a superCID trinity, mounted the ext rom using fit4cat, changed the Config.txt and added some custom apps and placed the cabs on the extended_rom.
Before hard-reseting I installed the custom apps manually just to be sure the cabs were ok, after that I made a hard-reset and waited for the extrom installation to finish, my custom apps appeared on the lower part of the screen were it displays which cab is being installed and I thought everything was fine.
Problem is, when I opened the program list they weren't there. I unlocked, edited and made a hard-reset, am I missing something? I've tried flagging the new cabs as read-only and archive like the rest but the results were the same. Is it because they're not signed?
Config.txt
Code:
LOCK:Enabled
EXEC:\Windows\SetHSDPA.exe /Enable
CAB: \Extended_ROM\CVC-PPC-WWE-611082-DopodTrinity.CAB
CAB: \Extended_ROM\MP_MMS3.5_Dopod_Asia_Trinity_070206.CAB
CAB: \Extended_ROM\PP_Button1.cab
CAB: \Extended_ROM\TaskManager_IconPatch_20061101.CAB
CAB: \Extended_ROM\Signed_Dpdcert_222.cab
[B]CAB: \Extended_ROM\TrayLaunch.cab
CAB: \Extended_ROM\RescoExplorer.cab
CAB: \Extended_ROM\WMDCIcon.cab
CAB: \Extended_ROM\PT_Customization.cab[/B]
XML: \Extended_ROM\PP_Ecall.xml
EXEC:\Extended_ROM\ChgScutAttri.exe
LOCK:Disabled
RST: Reset
RescoExplorer.cab, the program itself is on a folder in the extended rom(\Extended_ROM\Program Files\Resco Explorer) to save main memory space, the cab installs only a couple of dlls, registry settings and the shortcuts
TrayLaunch.cab is also on the extended rom, the cab installs the shortcuts on start menu\settings & windows\startup plus the registry settings
WMDCIcon.cab places my Sync.ico in the Windows folder to be used by Windows Mobile Device Center
PT_Customization.cab places a couple of dictionary files and makes few registry changes

oops, could one of the mods move this to the upgrading section? sorry.

you need to use a cooked OS.nb that doesn't check application security, or have your cabs signed with a valid certificate, otherwise they won't install.
I would suggest to cook your prefered OS.nb with aChef and modify the boot.hv (registry) to disable application security.

Okay thx a lot!
I'll use the latest official Dopod ROM.

just to be sure
so, I've extracted the nbs from the nbh using dutty's tool, converted the 06_OS.nb to raw using chef's tool, dumped the contents with viewimgfs tool and created and converted the boot.hv to reg using the make_boot_hv.bat & rgucomp.exe.
Now, as a first step and to gain a little confidence I just want to remove application security, for that I'l have to:
1) edit the boot.reg
1.a) as far as I read, I must add REGEDIT4 to the beginning of the file, didn't understand if it is imperative or mandatory, like if I only want to add a few things by hand(notepad), I can edit the file right away, but if I want to do something else like import it to win ce cab manager I must add the REGEDIT4 right?
2) when I finish I must convert it back to hv using rgucomp and use addfile.exe to add it to the raw file.
2.a) don't I have to use delfile to remove the boot.hv and only after addfile the new boot.hv? I think I read the addfile used the space left by delfile to place the new file.
3) convert the raw to nb using achef's tool.
I mean, I'm a little bit confused on the add/remove files subject. Since all the tools already exist, it would be nice if there was some GUI to complement them
A list of all files in the rom would be nice, with add/delete/replace context menus. Integration with the Custom RUU would also be nice, optionally create the nbh and run the Custom RUU( with the SSPL ), or export the nbh for manual flash using an SD Card.
edit: http://forum.xda-developers.com/showthread.php?t=295783 something like that...

Related

Cooking in the Extended Rom Kitichen 1.22

How To: Understand what an Extended Rom is.
The following Post is based on the I-Mate Extended Rom 1.22.162 out of PDA2k_WWE_12200_162_10600_SHIP
Understanding the Extended Rom:
- The Extended Rom is shipped as ms_.ndf and loaded with the BaUpgradeUt.exe
- The ms_.ndf is extracted on the first Hard reset (Power button pressed Stylist press) after upgrade
- The Extended Rom is hidden and read only
- The Extended Rom can un hidden with the following tool
ftp://xda:[email protected]_1_22/Tools/xda-developers _Unlocker.CAB
- The Extended Rom is limited to 16MB in size
- The Extended Rom starts the AutoRun.exe which reads the Config.txt
- The pointer for AutoRun.exe HKEY_LOCAL_MACHINE\Comm\AutoRun to \Extended_ROM\AutoRun
- The pointer for Config.txt HKEY_LOCAL_MACHINE\Comm\AutoRunCFG to \Extended_ROM\AutoRunCFG
- The Touch screen is disabled by the first command in the Config.txt and enabled by 2nd to last.
- The last Command of the config.txt does soft reset.
- The Extended Rom consist of *.CAB installation files
- The installation files fall into the following types
-- A) Applications: Album, Fax, Zip
-- B) Patches for the Hardware: Button9 on the Hardware Keyboard.
-- C) Patches for the software: Blue tooth upgrade.
-- D) Provider customizing: Splash screen, Internet Explore defaults.
- A Hard reset will NOT re-extract the ms_.ndf just do a reload of a clean OS thus also clean the register.
-- Thus what ever you put in that Extended Rom folder will remain.
- The \Storage will not be overwritten on a hard reset
-- Thus you are able to keep CAB files on that for installing after a hard reset.
- The Numbering of the Extended Rom is operator dependent.
-- Thus a Qtec version 1.22.225 might not have higher patches than a I-Mate version 1.22.62
- Extended Roms are built around the major OS release
-- Thus it is Not advisable to install patches from a Extended Rom 1.12.XX into a 1.22.XX
- The Extended Rom can be cooked (Changed to your own liking)
Warnings:
- Cooking you Extended Rom is at your own Risk
- Adding a Cab file to your Extended Rom that requires you to confirm, enter a key or do any input
** Whilst the Touch Screen is disabled ** Will Turn your device into a Paper Weight!!
-- (you will be stuck in the loading of the Extended Rom and will have to flash again)

How To: Find Info, Tools, Files to cook with ExtRom Kitchen
How To: Find Info, Tools, Files to cook with in The EXTRom Kitchen
Unlock tool:
ftp://xda:[email protected]_1_22/Tools/xda-developers _Unlocker.CAB
Thread on Unlock Tool
Unlocking Imate PDA2K extended rom
http://forum.xda-developers.com/viewtopic.php?p=78370#78370
Splashviewer files:
ftp://xda:[email protected]_1_22/Tools/Splashviewer/comdlg32_901.exe
ftp://xda:[email protected]/Splashviewer/MDA3_bootimage_changer2.CAB
ftp://xda:[email protected]/Splashviewer/nb_image_converter_859_418.exe
Thread on the Splashviewer:
CHANGING MDA III BOOT IMAGES TO YOUR LIKING
http://forum.xda-developers.com/viewtopic.php?p=66133#66133
Splash Screens:
ftp://xda:[email protected]/BlueAngel/Exteneded_ROM_Kitchen_1_22/Splash
Cab Extractor:
WinCE CAB Manager
http://www.ocpsoftware.com/products.php?nm=cecabmgr
Trail version has a limit of being able to be started 15 Times
er2003edit
The er2003edit is a tool to allow us to build custom roms before using the BaUpgradeUt.exe
At the moment IT DOES NOT SUPPORT the Blueangle.Info about this tool:
http://wiki.xda-developers.com/index.php?pagename=ER2003Edit
Extended Roms:
ftp://xda:[email protected]/BlueAngel/BlueAngel_Extended_Roms
Customization Operator Files
ftp://xda:[email protected]/BlueAngel/Exteneded_ROM_Kitchen_1_22/Customization_Operator

How to: Cook in the Extended Rom Kitchen
How to: Cook in the Extended Rom Kitchen
Preparations:
Step 1
Unlock the Extended Rom with the Un Lock Tool.
ftp://xda:[email protected]_1_22/Tools/xda-developers _Unlocker.CAB
Step 2
Edit the config.txt to remove the disable and enable touch screen commands.
Step 3
Edit the config.txt to remove the reset, You need to reset the device when you want.
Step 1
Down Load the ZIP_WWE.CAB extracted out of the T-mobile WWE Extended Rom 1.06.117.
ftp://xda:[email protected]/BlueAngel/Exteneded_ROM_Kitchen_1_22/WWE/ZIP_WWE.CAB
Ingredients:
ZIP_WWE.CAB
Your Device
Instructions:
Place the ZIP_WWE.CAB in your Extended Rom
in the \Extended_ROM\Config.sys add the following line
CAB: \Extended_ROM\ZIP_WWE.CAB
Click to expand...
Click to collapse
Serving the cooked Exteneded Rom
On the next hard reset you will have a COOKED Extended Rom with the added zip application
(and a clean OS with none of your loaded software)
Warnings:
Be aware of what you are installing and test it before hand.
Cabs fall into the following types
1) Un-removable: Cabs that install software however the can not be removed the "Remove programs" application (Fax)
2) Confirm: Cabs that ask for a registration key or need to be confirmed (Resco File Explorer)
Thus you need to be able to use the touch screen.
3) Error: Cabs that come up with the message such as "written for wrong version"
Thus you need to be able to use the touch screen.
4) Confused: Cabs that if executed by hand install fine.
if executed by AutoRun, install fine however then come up with the message that it will re-install itself.
Thus you need to be able to use the touch screen to say cancel.
5) Picky: Cabs that install a directory were they have been executed (splashPhoto).
\Exteneded_ROM\Dirname
6) Vanishing: Cabs that delete then selves after install (Extended Rom Unlock tool)
Thus you need a backup and are not very useful in extended rom.
The Extended Rom is Limited by size to 16MB thus not all your software can be placed in it.
This link goes into more details.
Auto install of applications, folder making & regcodes.
http://forum.xda-developers.com/viewtopic.php?p=83119#83119

How To: Understand the I-Mate Extended Rom 1.22.162
How To: Understand the I-Mate Extended Rom 1.22.162
Config.txt Install order:
EXEC:\Extended_ROM\TPDisable.exe
CAB: \Extended_ROM\BA_Version_122.CAB
CAB: \Extended_ROM\CDL_ECall.CAB
CAB: \Extended_ROM\BA_Album_WWE.CAB
CAB: \Extended_ROM\CallerID_wwe.cab
CAB: \Extended_ROM\Fax_2.09_WWE_Unremovable_0720.CAB
CAB: \Extended_ROM\MIDI561.CAB
CAB: \Extended_ROM\MMS_v2.0.0.13_BA_WWE_12132004.sa.CAB
CAB: \Extended_ROM\JMM101257_WWE_1004.CAB
CAB: \Extended_ROM\Custimization_CDL_090904.CAB
CAB: \Extended_ROM\Default_ImateV112.001.cab
CAB: \Extended_ROM\Button9_PIE.sa.CAB
CAB: \Extended_ROM\OEM_BA_09080401.sa.CAB
CAB: \Extended_ROM\Default_BTsearchTime.sa.CAB
CAB: \Extended_ROM\OEM_ALL_122_04111601.CAB
CAB: \Extended_ROM\OEM_BA_CDL_11230401.sa.CAB
CAB: \Extended_ROM\OEM_WWE_124_008.sa.CAB
CAB: \Extended_ROM\OEM_Patche_12100401.sa.CAB
EXEC:\Extended_ROM\TPEnable.exe
RST: Reset
Click to expand...
Click to collapse
Explanation of Files:
System Files
TPDisable.exe = Disable touch screen
TPEnable.exe = Enable touch screen
AutoRun.exe = Execution application
Config.txt = Config file read by AutoRun to execute the installation of the cab files.
Applications
BA_Album_WWE.CAB = Album Version 2.51 Build 16894
CallerID_wwe.cab = Photo Contacts (Caller ID) Version 1.17 Build 16965
Fax_2.09_WWE_Unremovable_0720.CAB = KSE Truefax Version 2.09
MMS_v2.0.0.13_BA_WWE_12132004.sa.CAB = MMS Composer Part of messaging
JMM101257_WWE_1004.CAB = MIDlet Manager Version 10.1.2.57 Build 20040705
MIDI561.CAB = Ring Tone Plug-in Player: Adds file \Windows\RTPlugIn.dll
Customization General:
BA_Version_122.CAB = Set Extended Rom version number to 1.22.126
[HKEY_LOCAL_MACHINE\SOFTWARE\OEM\3rdversion] "MSYSTEM"="1.22.162 WWE"
CDL_ECall.CAB = Sets
[HKEY_LOCAL_MACHINE\Security\ECall]"List"=hex(7):\ 39,39,39,00,31,31,32,00
Default_BTsearchTime.sa.CAB = sez
[HKEY_LOCAL_MACHINE\SOFTWARE\Widcomm\BtConfig\General] "InquiryDuration"=dword:00000019
Customization Hardware:
Button9_PIE.sa.CAB = Set the buttom9
(Hardware keyboard the red one) to Internet explorer calling the link "I-Mate"
Patches:
OEM_WWE_124_008.sa.CAB = Major Bluetooth upgrade replacing:
BTAudioGW.dll, BTBusinessCard.exe, BtCeBCSPTrans.dll, BtCeIf.dll, BTCeOsif4.dll, btcepan.dll, BTCePimCmdApp.exe,
BtCeProfiles.dll, BtCeSendTo_Poom.dll, BtCeStack.dll, BTChooserLib.dll, BTConfigCE.cpl, BTConnManagerCE.exe,
BtContextMenuPE.dll, BtCoreIf.dll, BTCplCE.exe, BTDialer.dll, BTFileExplorer.exe, BTPanManagerCE.exe, BtPhoneIf.dll,
btrez.dll, BtSdkCE30.dll, BTTrayCE.exe, BTWizardCE.exe, BTWizardHfp.dll, BTWizardProfiles.dll, HFPControlPanel.dll,
HFPUI.exe, SdkCE.dll, wbtapiCE.dll, ace_ddi.dll, acevidcap.dll, ahioem.dll, Serial_Cmd.dll, tiacxwln.dll, AudioGW.dll,
FrontLight.dll, Keybddr.dll, Serial_BTUR.dll, Wavedev.dll, atihwtbl0.txt
OEM_Patche_12100401.sa.CAB = Minor Bluetooth upgrade to date stamp 10.12.04: Replaces files BTConnManagerCE.exe & AudioGW.dll (Final version!!)
OEM_BA_09080401.sa.CAB = Wireless manager to upgrade date stamp 20.08.04: Replace files: WirelessMgr.exe.0409.mui & WLanMgr.exe (date stamp 20.08.04)
OEM_BA_CDL_11230401.sa.CAB = Battery.dll upgrade to date stamp 01.11.04 Replaces files Battery.dll
OEM_ALL_122_04111601.CAB = Upgrades the following files: ace_ddi.dll, acevidcap.dll, ahioem.dll, AudioGW.dll, Serial_BTUR.dll, Serial_Cmd.dll, tiacxwln.dll
[HKEY_LOCAL_MACHINE\SOFTWARE\OEM\Patch]= "Version"="OEM_ALL_122_04111601"
Note that the AudioGW.dll is again replaced however the final version is found in OEM_Patche_12100401.sa.CAB
Customization Operator:
Custimization_CDL_090904.CAB = I feel that this copies the default.htm patches it with I-Mate and Club i-mate then copies it to "\Windows\default.htm"
Two gif files are around (Operator.gif & Clubimate.gif)
Default_ImateV112.001.cab = Set up the default Spalsh1.nb & Splash2.nb and configures links to I-mate
More Detailed view of the Files can be read in:
ftp://xda:[email protected]_1_22/Docs/I-Mate_WWE_1.22.126_ExtROM.doc

Files need for the Exteneded Rom Kitchen
** Files need for the Exteneded Rom Kitchen **
Please up load some Exteneded Roms version 1.22 from your Operator to:
ftp://xda:[email protected]/BlueAngel/BlueAngel_Extended_Roms
Use the format Operator_Language_Version Number.
This will allow us to extract Splashscreens.
Find the Customization per Operator files
See what new patches are out to update.
We can Thus update our devices.
Thanks

:shock:
Well I don't need it since I managed to make my stuff work thanks to Buzz Lightyear, but WOW Great job !
We should keep this great thread safe

MDA User III:
A piece of very compehensive information. Good work !!!! Hope you can give us some hints on operator ID errors.

Cooked Rom Kitchen Ver 1.22.01 WWE
Thanks for all the new 1.22 Exteneded Roms that you have all uploaded (NOT).
Anyway:
if we take our base as I-Mate_PDA2K_Ext_ROM_122162_WWE
If we add to QTEC_BelDT_Ext_ROM_122557_WWE
We end up with CRK_RomKItchen_Ext_Rom_122001_WWE
Ver 1.22.001 WWE
Have added: Pdf reader
ftp://xda:[email protected]/WWE/ClearVue2.4.381WWE_withoutBP_OzUp.sa.CAB
Have added: Zip
ftp://xda:[email protected]/BlueAngel/Exteneded_ROM_Kitchen_1_22/WWE/ZIP_WWE.CAB
Findings: on QTEC_BelDT_Ext_ROM_122557_WWE = Well its poor!
Check it out for your self:
ftp://xda:[email protected]/BlueAngel/Exteneded_ROM_Kitchen_1_22/Docs/Rom_Kitchen_122.xls
Request:
Would somebody with QTEC_BelDT_Ext_ROM_122557_WWE Please check the Version Build number:
Album
Photo Contact
New Roms would be nice.
Hint:
You can download the 2 cabs and just run them of your device.
They will install without an entry in the "Remove Programs"
Info
Have extracted the spash1/2 of Tmobile / NZ Com / Qtec
Have added the custom files
Off Topic
@ leochan2005:
Read your PM, then I will help.
@ Daimaou:
Thanks for the flowers

How To: Understand the Orange 1.22.170 WWE Ext ROM
Orange_SPVM2000_Ext_ROM_122170_WWE_AZERTY_France
Can be found under:
ftp://xda:[email protected]_Ext_ROM_122170_WWE_AZERTY_France.rar
Config.txt reads
EXEC:\Extended_ROM\TPDisable.exe
CAB: \Extended_ROM\BA_Version_122.CAB
CAB: \Extended_ROM\BA_Album_WWE.CAB
CAB: \Extended_ROM\CallerID_wwe.cab
CAB: \Extended_ROM\MIDI561.CAB
CAB: \Extended_ROM\ClearVue2.4.381WWE_withoutBP_OzUp.sa.CAB
CAB: \Extended_ROM\Java_V10.1.2.49_BA_WWE_0901_unremovable.CAB
CAB: \Extended_ROM\KSE_Fax_v2.09_BA_WWE_0720_unremovable.CAB
CAB: \Extended_ROM\MMS_v2.0.0.16_BA_WWE_20041115.CAB
CAB: \Extended_ROM\OEM_BA_04112301_WWE.sa.CAB
CAB: \Extended_ROM\OEM_BA_11230401_WWE.sa.CAB
CAB: \Extended_ROM\Default_BTsearchTime.sa.CAB
CAB: \Extended_ROM\OEM_WWE_124_008.sa.CAB
CAB: \Extended_ROM\OEM_Patche_12100401.sa.CAB
CAB: \Extended_ROM\BroadcomCorp_BTUpdate.CAB
CAB: \Extended_ROM\Orange_WWE_Customize.sa_041203.CAB
CAB: \Extended_ROM\Button9.CAB
EXEC:\Extended_ROM\TPEnable.exe
RST: Reset
Click to expand...
Click to collapse
It is a subset of the base of I-Mate_PDA2K_Ext_ROM_122162_WWE
and by far better than QTEC_BelDT_Ext_ROM_122557_WWE
Upgrades on the rom
Orange MMS_v2.0.0.16_BA_WWE_20041115.CAB
I-Mate MMS_v2.0.0.13_BA_WWE_12132004.sa.CAB
New Update on this rom
BroadcomCorp_BTUpdate.CAB
Adds the following files Date stamped 12.10.2004
BtAvUI.dll, BtCeAvIf.dll, BtHidPlugIn.dll, BTRezAV.dll, BTRezHID.dll, BtWizardAv.dll, BtWizardHID.dll
Sets the following.
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\WaveDev]
"Dll"="btceavif.dll"
[HKEY_LOCAL_MACHINE\SOFTWARE\Widcomm\BtConfig\UserInterface\ServiceIcons\AV]
"Icon"="btwizardav.dll,32015"
"IconConnected"="btwizardav.dll,32014"
"UUID"=dword:0000110B
[HKEY_LOCAL_MACHINE\SOFTWARE\Widcomm\BtConfig\UserInterface\ServiceIcons\Hid]
"Icon"="btwizardhid.dll,25513"
"IconConnected"="btwizardhid.dll,25512"
"UUID"=dword:00001124
[HKEY_LOCAL_MACHINE\SOFTWARE\Widcomm\Connection Wizard\AddIns\AV]
"Description"="btrezav.dll,32002"
"Dll"="btwizardav.dll"
"Icon"="btwizardav.dll,32002"
"Order"=dword:00000005
"Title"="btrezav.dll,32001"
[HKEY_LOCAL_MACHINE\SOFTWARE\Widcomm\Connection Wizard\AddIns\Hid]
"Description"="btrezhid.dll,25501"
"Dll"="btwizardhid.dll"
"Icon"="btwizardhid.dll,25511"
"Order"=dword:000000ff
"Title"="btrezhid.dll,25500"
[HKEY_LOCAL_MACHINE\SOFTWARE\Widcomm\Plugin\AV\AutoLoadOnStackShutdown]
"ActionType"=dword:00000002
"LoadPath"="\windows\btavui.dll"
[HKEY_LOCAL_MACHINE\SOFTWARE\Widcomm\Plugin\AV\AutoLoadOnStackStartup]
"ActionType"=dword:00000003
"LoadPath"="\windows\btavui.dll"
[HKEY_LOCAL_MACHINE\SOFTWARE\Widcomm\Plugin\Hid\AutoLoadOnConnect]
"ActionType"=dword:00000002
"LoadPath"="\windows\bthidplugin.dll"
[HKEY_LOCAL_MACHINE\SOFTWARE\Widcomm\Plugin\Hid\AutoLoadOnStackShutdown]
"ActionType"=dword:00000002
"LoadPath"="\windows\bthidplugin.dll"
[HKEY_LOCAL_MACHINE\SOFTWARE\Widcomm\Plugin\Hid\AutoLoadOnStackStartup]
"ActionType"=dword:00000003
"LoadPath"="\windows\bthidplugin.dll"
Click to expand...
Click to collapse
Splash Info
The Splash sreenes are basic windows logo.
There is a orange logo that is also added I am not sure if this is on the spalsh afterwards.
ERK Ver 1.22.002 WWE:
Have added: MMS_v2.0.0.16_BA_WWE_20041115.CAB
Ftp//xda:[email protected]/BlueAngel/Exteneded_ROM_Kitchen_1_22/WWE/MMS_v2.0.0.16_BA_WWE_20041115.CAB
Have Added BroadcomCorp_BTUpdate.CAB
ftp://xda:[email protected]_Kitchen_1_22/WWE/BroadcomCorp_BTUpdate.CAB
Findings: on Orange_SPVM2000_Ext_ROM_122170_WWE_AZERTY_France = Almost on par with I-mate 162! Even has Clearview .
Check it out for your self:
ftp://xda:[email protected]/BlueAngel/Exteneded_ROM_Kitchen_1_22/Docs/Rom_Kitchen_122.xls
To Whoever uploaded, thanks you can delete the old file of the root if you dont need it for somebody else. and Can you post your version for Album, photo contact and BT.

O2_IIs_Asia_Ext_Rom_11295.WWE Part of the 1.31
O2_IIs_Asia_Ext_Rom_11295.WWE Part of the 1.31
This Extended Rom is to say the least "[bI]nteresting[/b]"
It comes with a grand total of 77 Files
It set up the following Carriers:
Default, 1O1O, 3-DUALBAND, AIS, Celcom, ChungHwa Telecom, DiGi, DTAC, Globe, IM3, M1, Maxis, New World Mobility, One2Free, Optus, ProXL, Satelindo, SingTel, Smart, SmarTone, StarHub, StarHub Prepaid, Sunday, Telkomsel, Telstra, Vodafone Australia,
It does this by first running its
1) normal Autoinstall.
2) Allowing the Touchsceen
3) Changing the satatus of the buttons
4) Loading a daialog moduale
5) Copying a new autoconfig.txt file to the device
6) Running a autoconfig.exe.
This is in fact a feat as the file CAB: \Extended_ROM\6inone.CAB
Which is seen in every carrier of the Autoconfig.sys can't be found.
I also did not find it in the cabs that I looked at and no I dd not look at all 77.
I Have have done a ERK cleaned up of the files and moved them to carrier directories for better viewing
don't install this its just to work with
ftp://xda:[email protected]_Asia_Ext_Rom_112295.WWE_NewDirStructure.rar
The original remains
ftp://xda:[email protected]_Roms/O2_IIs_Asia_Ext_Rom_11295.WWE.zip
Splash Info
To many so did none.
Up / Down Grades
It upgrades the camera
Camera_Patch_10080401.sa.CAB (to Camera.exe 22.09.04)
ftp://xda:[email protected]_1_22/WWE/Camera_Patch_10080401.sa.CAB
It Downgrades the Wireless manager
By replacing STK.exe = 02.09.04
This is a downgrade
Base STK.exe = 22.10.04 after all upgrades.
New Stuff
It adds
CW-Album-Association.CAB
Which are Reg Entries
ftp://xda:[email protected]_Kitchen_1_22/WWE/CW-Album-Association.CAB
It adds
DialerSkin_Portrait_091104.sa.CAB
DialerSkin_Portrait_091104.sa.CAB
Be warned these cabs will create a bad looking background on your phone.
Findings:
O2_IIs_Asia_Ext_Rom_11295.WWE is a pain to work with and should be left to those that feel they need it.
Check it out for your self:
ftp://xda:[email protected]/Docs/ERK_O2_IIs_Asia_Ext_Rom_112295.WWE.Doc
Config.txt
EXEC:\Extended_ROM\TPDisable.exe
CAB: \Extended_ROM\CallerID_wwe.cab
CAB: \Extended_ROM\BA_Album_WWE.CAB
CAB: \Extended_ROM\MIDI561.CAB
CAB: \Extended_ROM\MMS_v2.0.0.13_BA_WWE_O2Asia_0913.CAB
CAB: \Extended_ROM\ClearVue2.4.381WWE_withoutBP_OzUp.sa.CAB
CAB: \Extended_ROM\Java_V10.1.2.49_BA_WWE_0901_unremovable.CAB
CAB: \Extended_ROM\DialerSkin_Portrait_091104.sa.CAB
CAB: \Extended_ROM\DialerSkin_Landscap_091104.sa.CAB
CAB: \Extended_ROM\After_Sales_Service_091304.sa.CAB
CAB: \Extended_ROM\O2ASIA_WWE_Customization_0923.CAB
CAB: \Extended_ROM\default.sa.CAB
CAB: \Extended_ROM\o2_connect_iis.cab
CAB: \Extended_ROM\Camera_Patch_10080401.sa.CAB
CAB: \Extended_ROM\CW-Album-Association.CAB
CAB: \Extended_ROM\DelAddStarMenu_092404.sa.CAB
CAB: \Extended_ROM\O2_Base_09240402.sa.CAB
CAB: \Extended_ROM\O2Auto.sa.CAB
CAB: \Extended_ROM\Version_BA_112.sa.CAB
CAB: \Extended_ROM\OEM_BA_09240401.sa.CAB
CAB: \Extended_ROM\LoadDialogInit_MS_10150402.sa.CAB
EXEC:\Extended_ROM\SetButtonLock.exe
EXEC:\Extended_ROM\TPEnable.exe
CPY1:\Extended_ROM\Autoconfig.txt
CPY2:\Windows\Autoconfig.txt
EXEC:\Windows\Autoconfig.exe
RST: Reset
Click to expand...
Click to collapse
Autoconfig.txt
;Remark
[Default]
CAB: \Extended_ROM\6inone.CAB
CAB: \Extended_ROM\O2ASIA_WWE_Customization_0923.CAB
CAB: \Extended_ROM\O2_Default.sa.CAB
EXEC:\Extended_ROM\UpdateStartMenu.exe
RST: Reset
[1O1O]
CAB: \Extended_ROM\O2ASIA_1010_Customization_0923.CAB
CAB: \Extended_ROM\1O1O_ALL.sa.CAB
RST: Reset
[3-DUALBAND-]
CAB: \Extended_ROM\default.sa.CAB
CAB: \Extended_ROM\6inone.CAB
CAB: \Extended_ROM\O2ASIA_3DualBand_Customization_0923.CAB
CAB: \Extended_ROM\3-DUALBAND_ALL.sa.CAB
RST: Reset
[AIS]
CAB: \Extended_ROM\default.sa.CAB
CAB: \Extended_ROM\O2ASIA_AIS_Customization_0923.CAB
CAB: \Extended_ROM\AIS_ALL_100104.CAB
RST: Reset
[Celcom]
CAB: \Extended_ROM\default.sa.CAB
And on
And on ect bla bla
Click to expand...
Click to collapse

The Information for the following Extended Roms
I-Mate 1.22.162 WWE
Qtec 1.22.557 WWE
Orange 1.22.170 France WWE
02 Asia 1.22.925 WWE (Part of CE 1.31)
Has Been Ported to Wiki
The following Exteneded Roms Have also been updated
Orange UK 1.22.139 WWE
O2 UK 1.12.178 WWE
T-Mobile UK 1.06.117 WWE
QTEC 1.22.167 WWE
QTEC 1.12.121 WWE
Siemens 1.20.115 WWE
I-Mate Arabic 1.31.112 WWE
Wiki Blue Angel Home Page
http://wiki.xda-developers.com/index.php?pagename=HTC_Blueangel
Wiki Blue Angel Extended Rom Kitchen
http://wiki.xda-developers.com/index.php?pagename=BA_RomKitchen

The Orange UK one should have read 1.12.139, so I've corrected on wiki.
I've also just gone through looking at Orange UK 1.31.124. I'll put the doc and updated XLS on the FTP site when I'm done here.
A thought though.... The ERK is currently based on 1.22 CE, but more people are going to 1.31. I've added my 1.31 info to Rom_Kitchen_122.xls and marked as 1_31.01. But logically it should go in a _131.xls doc.
Also I haven't reported the base versions since I've imediately done a ExtRom install, which I note Orange is still using doengrade versions of WirelessMgr, WLanMgr and WModem.

RTP
Thanks for your help.
I know that the base is based on 1.22.
Alas I can't see what the differnece between 1.22 and 1.31.
Both report the same CE version and Build.
If you look at the I-Mate 1.22.162 WWE ERK_1.22_Base vs the I-Mate Arabic 1.31.112 WWE ERK_1.22.010 you will find that they ship the same files however in the 1.31 version the BT upgrade is missing.
I have asked Bebbo to have a better look into the file dates in the hope of finding out if the shipped MS file is infact an combination of the CE and added patches (in this case BT)
The same is true if you look at Orange UK 1.12.139 WWE ERK_1.22_004 Vs the new Orange 1.31.124 UK (in the Kitchen Entrance) on a short look the only diff I can see is that BA_OEM_PA_STK.sa.CAB is missing in 1.31.
Here to one would need a person who has 1.31 CE installed to check file dates.
Did you notice that I-mate 1.31 is using the setup.exe and orange is back on the config.txt?
Think you would mind also updating wiki with Orange UK 1.31.124 after you have cooked it and thanks for your help.

Yep, not sure what is new apart from the Bluetooth patches. However, at least that means the pataches aren't clogging up the ExtendedRom.
I did notice that is doesn't include the patch to Add the HQ Audio and Keyboard profiles to BT.
Yes, the STK update has gone. Also they have changed the help file from OrangeUK_Help.sa.CAB to OrangeUK_Help_102804.sa.CAB. However, going into downloads on the PDA, there is still a 432K Help update available for download - ContactsWiz and EmailWiz.
Yep, just going off to do WiKi now.
Of course if we could get the .nbf files open, we could check the files from there, rather than by doing an arduous check on the PDA.
By the way, did this latest update by installing ExtRom by hand, then doing just the CE and Radio rom updates. Worked pretty well. Though I didn't need the Radio update.... Cuts down upgrade time.

Just had a PM from Bebbo.
1.31 (I-mate) has the BT patches in the CE Base. I have asked him to check the file dates of the other patches that were missing based on the info I posted on the 1.31 Arabic.
Think you could do the same.
He has dropped his autorun.exe (which calls setup.exe) and gone back to the old version with config.txt
So what we know is 1.31 is not just a name change but a upgrade.
Looks like I will have to open a 1.31 kitchen, create a new base, oh what fun! Every time I check the site a new Ext Rom Pops up.

Looked at the cabs and dates:-
- Includes OEM_WWE_124_008.sa.CAB or at least the date on 1.31 is 10/12/2004 for BTWizardCE and the cab date is 9/12/2004. I would guess the date difference is as a result of repackaging of the files for inclusion in the firmware rather than as a patch. Version is 1.0.0.3500.
- Includes OEM_Patche_12100401.sa.CAB. Again a date discrepancy on AudioGW.dll. 1.31 is 13/12/2004, cab is 10/12/2004
- Don't know if it includes OEM_BA_04112301_WWE.sa.CAB because this seems to be the same as BA_OEM_PA_Remove_WiFi_Logo_WWE.sa.CAB which I have installed from Orange ExtRom 1.31.124
- Doesn't include BroadcomCorp_BTUpdate.CAB which is the HQ Audio and Keyboard profiles (I think).
- Doesn't include Default_BTsearchTime.sa.CAB which does what it says on the tin.
- Doesn't include OEM_BA_11230401_WWE.sa.CAB which is something to do with battery life and has a Microphone registry update.
So it looks like it includes the base BT update, or a very similar version as to make no difference. But doesn't include some other less fundamental patches.

This is more or less what I found except I feel that the upgrades in OEM_Patche_12100401.sa.CAB are NOT pre-installed as the dates in this patch are newer than the supplied ones in the CE ROM (Though I need to extract them to find version numbering to be sure).
Mind you, I have at some point installed the OEM_ALL_122_04111601.CAB file which seems to DOWNGRADE the AudioGW.dll so maybe I was looking at this one on the PDA instead of the pre-supplied one!
I need to refresh my PDA as I have installed so many things on there it is difficult to know which dll's and exe's are originals.
If you still have a clean install RTP could you copy the AudioGW.dll and BTConnManagerCE.exe to windows and see if they have a version number inside them so I can compare with the ones in OEM_Patche_12100401.sa.CAB?
On another point, in the kitchen you are stating that you should install:
1) OEM_ALL_122_04111601.CAB
then
2) OEM_WWE_124_008.sa.CAB
However, I'm sure that 124 contains newer versions of the files installed by 122 and therefore 122 is not needed (Some are newer the rest are the same but everything in 122 is covered by 124). In fact, it is probably not wise having it in the install because if you install it POST 124 it will DOWNGRADE some of files!

Bebbo, I'd agree with your thoughts on the 122/124 patches. I think this comes of the 122 being in the 'Base'.
Perhaps the Base should be cut back to being just the nk.nbf contents (and maybe radio.nbf), rather than including a random OEM's ExtRom.
That way you could more easily remove something from the ERK, when replaced by a newer upgrade.

I have not contributed much as yet to the ERK as I have been finding the most STABLE version I can rather than following what is supplied by manufacturers as the "latest and greatest" updates. In addition to this I do not use some of the other "features" supplied as standard (Such as ringtones) so I do not install these items.
I find the ERK fairly useful for finding what is available in each cab file but other than that I pick and chose what cab files to install (Such as leaving out Caller_ID and the OEM_ALL_122 patch).
I would feel that a simple xls file describing ONLY the cab files available, their function and where to locate them along with individual sheets on their file structure such as dates, version numbers etc would be of more use to me in compiling my own ER. In fact, on my next day off I might (If you dont mind) take some of the work you have done and create a new xls doc with information formatted in this way?

Looks like I have been missing out on a chat.
I have set up the ftp site for 1.31
I have set up a 1.31 spreadsheet
I have set up a 1.31 base and cooked page on wiki
I need to move the o2 asian rom over to 1.31
@ Bebbo
I to would like to see a better solution to what the patches / cabs are.
The information about them is in fact on wiki, based on the ERK that they were found in.
The file dates are around in the Cooked Erk and if you go into the details doc you will find screen shots of the Cabs.
This is all fine if you know what you are looking for.
Alas as seen by myself over the last 4 hours I have to hunt for info on OM_some_name.Cab.
The wiki site has the flyover funtion, that I don't understand how it works, or better said I have not found the time to look at it.
I would Think that it would be useful to have:
Name OM_some_name.Cab
Short text = Upgrade of BT to 1.456
Type = Application / Reg Entries only / Patch / System File
Reg Entries = Yes / No (If yes pints to some other page)
Files supplied = BTPatch.exe 12.12.04
Other info: This is a update of OM_XXX_SD.Cab
More info = Points to page if need
For large application like Album just the version number as I would not want to go through 30 odd files.
Now are you realy planning to have a day of ? Add all the Flyover stuff ?

Help on I-Mate Arabic Ext Rom 131112 WWE

Hello I just ungraded to the I mate arabic 1.31 rom with radio 1.06.02. my question is in the extended rom there is no config.txt file? using the instruction under the Cooking in the Extended Rom Kitichen thread
http://forum.xda-developers.com/viewtopic.php?t=16137
I cant seem to find how to edit the config txt file to allow the ZIP_WWW.cab to be installed and the editing config to say the following
Instructions:
Place the ZIP_WWE.CAB in your Extended Rom
in the \Extended_ROM\Config.sys add the following line
Quote:
CAB: \Extended_ROM\ZIP_WWE.CAB
I Would Like to get shot of the arabic stuff
I-Mate PDA2K (PH20B)
Rom 1.31.00 WWE
Radio 1.06.02
Protocol 1337,38
ExtROM 1.31.122 WWE

Ok 2 things,
1 you need the extended rom unlock util which will allow you to see and edit items in the hidden extended rom folder on your pda.
2 dont bother with the ZIP program, get pocket rar, its freeware and works much better. You can install cabs from within rar or zip files without needing to extract them to the file system first etc.
PS: You can copy the config.txt to your pc to edit, or edit with pocket word of similar.

reply to ringman
I have unlocked my extended rom and can extract the contents. In the unlocked extended rom there in no config.txt file?.
Would it be possible to just replace the ms_.nbf file that contains the extended rom with another extrom, just like I replaced the Radio file then use the fix.bat
Many thanks

The newer ROMs do not use a config.txt they run a setup.exe program called from a modified version of autorun.exe instead.
You can use the old config.txt file by replacing the autorun.exe from an older rom and creating your own config.txt (you can also then delete the unneeded setup.exe file).

reply to bebbo
ok so correct me if Im wrong, you unlock your extended rom delete TPEnable.exe, TPDisable and setup then hard reboot. unlock extrom again then replace old for new, new having autorun.exe and config.txt?
Many Thanks

I usually do the upgradein this order:
1) Copy the ext rom unlock tool to PDA - run it and then run unhide + unlock ext rom.
2) Soft reset to unhide ext rom.
3) Make a full backup of current ext rom to PC!
4) Create my own ext rom by adding / removing apps as necessary to ext rom as cab files and modifying config.txt.
5) Hard reset PDA to install new apps and clean copy of Pocket PC.
Note:
As mentioned before, if you do not have a config.txt then you will need to replace autorun.exe with one from a pre v1.31 ext rom, create your own config.txt (Use one from ftp server as a base) and you can delete the setup.exe prog as it will not be used.
I have left the TPEnable and TPDisable on the ext rom but have removed their entries from the config.txt file so that the screen is not disabled.

reply to Bebbo
Thanks Bebbo
Your advice worked. I used config.txt and autorun.exe from extended rom Imate 1.22.162 now I have extrom without arab stuff
Many Thanks
Windows Mobile Version 4.21.1088 (Build 14132)
ROM Version 1.31.00 WWE
ROM Date 12/13/04
Radio Version 1.06.02
Protocol 1337.38
ExtROM Version 1.31.124 WWE (Cooked)

Help cooking my Extended ROM

Hello, I have successfully updated my ROM to the Mamaich posted 1.33.51 and all seems well apart form the occasional two GPRS Icon bug. However, I have a few questions as I now want to cook my ExtendedROM to updade some CAB files and remove some I don't need or use. The contents of my ExtendedROM currently looks like this
AutoRun.exe
BA_Album_WWE.CAB
BA_Version_122.CAB
Button9_PIE.sa.CAB
CallerID_wwe.cab
CDL_ECall.CAB
Config.txt
Custimization_CDL_090904.CAB
Default_BTsearchTime.sa.CAB
Default_ImateV112.001.cab
Fax_2.09_WWE_Unremovable_0720.CAB
JMM101257_WWE_1004.CAB
MIDI561.CAB
MMS_v2.0.0.13_BA_WWE_12132004.sa.CAB
OEM_ALL_122_04111601.CAB
OEM_BA_09080401.sa.CAB
OEM_BA_CDL_11230401.sa.CAB
OEM_Patche_12100401.sa.CAB
OEM_WWE_124_008.sa.CAB
TPDisable.exe
TPEnable.exe
I have installed the BT3900 cab file and this seems to work O.K, so my question is I would like to add the BT3900 cab file to my extended rom in addition to the camera can file.
Q1:Can anyone tell me which of the cab files in the list above are Bluetooth related, so that I can remove them.
Q2: By just adding the BT3900 cab file bring me up to date without requiring any Patches.
Q3: Would I need the audiogw.dll that a lot of people refer to
Q4: Are there other things I should consider.
I want to add the camera, phonedialler, smartdialler and BT3900 to my ExtendedROM. I would appreciate any help.
Oh! One final question - Having upgraded to 1.33.51 do I need the wave.dll file.
Thanks for all your help.
rgds

"Q2: By just adding the BT3900 cab file bring me up to date without requiring any Patches."
You must add the BT 3900.cab and also RestartRadio.exe to the config.txt as follows:
EXEC:\Extended_ROM\RestartRadio.exe
CAB: \Extended_ROM\[put filename of bt3900 upgrade here].cab
I dont know, if you have to place RestartRadio again after the upgrade.cab, as Wiki says, because after running Autorun, the device softresets itself automatically - wich restarts your radio... - So that is what causes my oppinion, that you wont need another restart before this.
But this is for sure: If you want to add a file to your ext Rom you must edit config.txt too.[/url]

Thanks Bubisch. Yeah I knew I had to update the config.txt.
Can anybody else help with the questions?

An ExtROM trick

Hi there!
Today I've got an idea. If I unlock the extrom, install all my programs and totally config my wizard, the backup my system with SPB Backup for WM5.0, then put the backup file into the ExtROM and write a config.txt, and make a HardReset, the backup file should be installed automatically.
Or ExtROM only works with .CAB files?
EDIT:
NOW Testing.....Will post the result

How are you going to unlock the ext-rom?

risidoro said:
How are you going to unlock the ext-rom?
Click to expand...
Click to collapse
ftp://xda:[email protected]/Wizard/Unlock/Unlock Ext Rom Wizard.cab

faria said:
risidoro said:
How are you going to unlock the ext-rom?
Click to expand...
Click to collapse
ftp://xda:[email protected]/Wizard/Unlock/Unlock Ext Rom Wizard.cab
Click to expand...
Click to collapse
And what about the post AKU2 roms?

There's a fix for that, too. Don't recall where off-hand.

SuperRob said:
There's a fix for that, too. Don't recall where off-hand.
Click to expand...
Click to collapse
It doesn't work!!!

Ok. NowI have time for testing this idea. But I have some problems.
When you open the EXTRom you can see a config.txt which contains the cab configuration datas.
Like this:
CAB: \Extended_ROM\T-Mobile_Network_Customizations.cab
I'm using SPB Backup what is creates backup files in .exe format. So if I want to do a full backup and I want it to autorun after a hard reset, I must do edit this config file right?
Maybe the config file should be like this:
EXE: \Extended_ROM\Full_Backup.exe
All I mentioned here is right, or I'm wrong with something?

HyperMalac said:
Ok. NowI have time for testing this idea. But I have some problems.
When you open the EXTRom you can see a config.txt which contains the cab configuration datas.
Like this:
CAB: \Extended_ROM\T-Mobile_Network_Customizations.cab
I'm using SPB Backup what is creates backup files in .exe format. So if I want to do a full backup and I want it to autorun after a hard reset, I must do edit this config file right?
Maybe the config file should be like this:
EXE: \Extended_ROM\Full_Backup.exe
All I mentioned here is right, or I'm wrong with something?
Click to expand...
Click to collapse
youare correct,but it wont work because the spb .exe has an input dialog before starting to restore ,therefore it will crash the extended-rom when trying to install the .exe,the solucion is to hack the .exe file and remove the dialog input so it can install witout any user help.

faria said:
youare correct,but it wont work because the spb .exe has an input dialog before starting to restore ,therefore it will crash the extended-rom when trying to install the .exe,the solucion is to hack the .exe file and remove the dialog input so it can install witout any user help.
Click to expand...
Click to collapse
Not 100% sure on this as I have not tested it but could you not unlock the LCD while running the EXE then lock it afterwards if needed?
Something like.
Code:
LOCK:Enabled
CAB: \Extended_ROM\1.cab
CAB: \Extended_ROM\2.cab
LOCK:Disabled
EXEC:\Extended_ROM\backup.exe
RST: Reset
or may be copying it to the MiniSD or internal storage would work better?
Code:
LOCK:Enabled
CAB: \Extended_ROM\1.cab
CAB: \Extended_ROM\2.cab
CPY1:\Extended_ROM\backup.exe
CPY2:\Somewhere_On_Device\backup.exe
LOCK:Disabled
EXEC:\Somewhere_On_Device\backup.exe
RST: Reset
Not tested any of this as I just use OMA and CAB's to do all I need but it's just an idea.

djwillis said:
faria said:
youare correct,but it wont work because the spb .exe has an input dialog before starting to restore ,therefore it will crash the extended-rom when trying to install the .exe,the solucion is to hack the .exe file and remove the dialog input so it can install witout any user help.
Click to expand...
Click to collapse
Not 100% sure on this as I have not tested it but could you not unlock the LCD while running the EXE then lock it afterwards if needed?
Something like.
Code:
LOCK:Enabled
CAB: \Extended_ROM\1.cab
CAB: \Extended_ROM\2.cab
LOCK:Disabled
EXEC:\Extended_ROM\backup.exe
RST: Reset
or may be copying it to the MiniSD or internal storage would work better?
Code:
LOCK:Enabled
CAB: \Extended_ROM\1.cab
CAB: \Extended_ROM\2.cab
CPY1:\Extended_ROM\backup.exe
CPY2:\Somewhere_On_Device\backup.exe
LOCK:Disabled
EXEC:\Somewhere_On_Device\backup.exe
RST: Reset
Not tested any of this as I just use OMA and CAB's to do all I need but it's just an idea.
Click to expand...
Click to collapse
yes change to LOCK to [Disabled] or put 2 spaces betwin lock and enable in the config file] and it works ,but the there is a a screen stoping you from accessing the dialog even if you press start it will not go away thats was my experience with the program called wm5torage so i hacked it with an hex editor a now installs great.
maybe your extended rom is diferent [since there is many versions] and will let you input ,i know it use to work in the pda2k extended-rom,let me know the results.

Interesting result with AKU3.2 and custom Ext ROM

OK, so I finally got curious enough to cook my own ROM then added it to Ell82's AKU3.2 ROM and stumbled across something pretty cool...I followed Faria's instructions (turns out not very well...) and added a cab with spaces (I know, I know, freakin noob...). Anyway, it apparently just skipped over that cab and kept going. Now here's the cool part, the total cabs I added to my ROM was only 2.6 MB so I thought I was OK. Didn't pay close enough attention until later and realized the nk.nbf file was about 10.5 MB. When faria says the Ext Rom shoudl be less than 9.5 MB, is he talking the total of all the cabs, or the nk.nbf file???
Bottom line is even though the nk.nbf file was 10.5 MB it installed and ran fine on AKU3.2 (except for the cab with spaces). I then tried to load this into Molski's 2.26 ROM and the ExtROM wouldn't take. Went back and fixed the cabs with spaces and it still won't take.
This leads me to the initial conclusion that the AKU3.2 ROM allows you to exceed the 9.5MB limit. Can anyone else confirm this?

total n00b for sure... (not flaming)
when you make an extended rom it defaults to a size of around 10meg, no matter whats in there.. you could have 1 [email protected] 10k or 500 [email protected] 10.5meg (just cant go over the 10 meg limit).. so if you have 1 cab then no matter what the size is automatically 10meg.. everything in the rom is addressed my memory locations, everything has a set start and end address
and you can prevent cabs from being installed by removing them from the config.txt

OK, then help a ROM-cooking n00b out. Faria's tutorial mentions the instructions were tested up to the 2.24 ROMs--anything that would cause a problem with his ext-rom-base on a 2.26 ROM? I just can't get it to install. The ExtROM is not corrupt because I can manually install each cab in the ExtROM using total commander, but can't get them to install from hard-reset...

jorge_culv said:
OK, then help a ROM-cooking n00b out. Faria's tutorial mentions the instructions were tested up to the 2.24 ROMs--anything that would cause a problem with his ext-rom-base on a 2.26 ROM? I just can't get it to install. The ExtROM is not corrupt because I can manually install each cab in the ExtROM using total commander, but can't get them to install from hard-reset...
Click to expand...
Click to collapse
well actually the ext rom could be corrupt.. i have had that problem before(actually with my latest UWC beta, which caused almost a week long delay).. all cabs would install manually but the ones listed in the config.txt wouldnt install at all... what cabs are you trying to install that arent? and what does the contents of your config.txt look like?

Thanks for the help ShogunMark--is it possible for an ExtRom to install fine for AKU3.2, then same extact ExtROM (no rebuild, no changes, didn't even look at it funny!) not install on 2.26 (installed it twice on 2.26 in case it might have been corrupt the first time)? That's the situation I'm looking at. Originally the extROM (the one that worked for AKU3.2 but not on 2.26) had a few cabs with spaces in their names. When I started having problems on 2.26 I started looking closer and rebuilt the ExtROM with new file names, but it still wouldn't install on 2.26. Just to make sure I'm not crazy, I'm about to down-grade to AKU2.3 OS version 2.24 to fully comply with the ROM building tutorial that says its tested to at least OS version 2.25. I'll let you know how that goes in a few hours. In the meantime, here's the Config.txt I'm using now that won't go in auto, but allows me to install the cabs by hand in 2.26:
LOCK:Enabled
CAB: \Extended_ROM\cLaunch.arm.CAB
CAB: \Extended_ROM\Molski.Biz_VoiceDial_Button_Customizer.cab
CAB: \Extended_ROM\Molski.Biz_Customizing_Tweaks.cab
CAB: \Extended_ROM\Molski.Biz_Performance_Registry_Tweaks.cab
CAB: \Extended_ROM\nullkb.ARM4.CAB
CAB: \Extended_ROM\rar360.ppc_arm.cab
CAB: \Extended_ROM\SmartDial+EtenSkinPortretD_v2.cab
CAB: \Extended_ROM\fileaslf.arm.cab
LOCKisabled
RST: Reset

jorge_culv said:
Thanks for the help ShogunMark--is it possible for an ExtRom to install fine for AKU3.2, then same extact ExtROM (no rebuild, no changes, didn't even look at it funny!) not install on 2.26 (installed it twice on 2.26 in case it might have been corrupt the first time)? That's the situation I'm looking at. Originally the extROM (the one that worked for AKU3.2 but not on 2.26) had a few cabs with spaces in their names. When I started having problems on 2.26 I started looking closer and rebuilt the ExtROM with new file names, but it still wouldn't install on 2.26. Just to make sure I'm not crazy, I'm about to down-grade to AKU2.3 OS version 2.24 to fully comply with the ROM building tutorial that says its tested to at least OS version 2.25. I'll let you know how that goes in a few hours. In the meantime, here's the Config.txt I'm using now that won't go in auto, but allows me to install the cabs by hand in 2.26:
LOCK:Enabled
CAB: \Extended_ROM\cLaunch.arm.CAB
CAB: \Extended_ROM\Molski.Biz_VoiceDial_Button_Customizer.cab
CAB: \Extended_ROM\Molski.Biz_Customizing_Tweaks.cab
CAB: \Extended_ROM\Molski.Biz_Performance_Registry_Tweaks.cab
CAB: \Extended_ROM\nullkb.ARM4.CAB
CAB: \Extended_ROM\rar360.ppc_arm.cab
CAB: \Extended_ROM\SmartDial+EtenSkinPortretD_v2.cab
CAB: \Extended_ROM\fileaslf.arm.cab
LOCKisabled
RST: Reset
Click to expand...
Click to collapse
the problem is that you are missing the disable security cab, i have attached in case you need it.. I would also bet those spaces arent suppose to be there... you should have this:
LOCK:Enabled
CAB: \Extended_ROM\Default_Signed_DisableSecurity.CAB
CAB: \Extended_ROM\cLaunch.arm.CAB
CAB: \Extended_ROM\Molski.Biz_VoiceDial_Button_Customizer.cab
CAB: \Extended_ROM\Molski.Biz_Customizing_Tweaks.cab
CAB: \Extended_ROM\Molski.Biz_Performance_Registry_Tweaks.cab
CAB: \Extended_ROM\nullkb.ARM4.CAB
CAB: \Extended_ROM\rar360.ppc_arm.cab
CAB: \Extended_ROM\SmartDial+EtenSkinPortretD_v2.cab
CAB: \Extended_ROM\fileaslf.arm.cab
LOCKisabled
RST: Reset

Ahh, so even though one of Molski's cabs does this, I need to disable security first to allow the other cabs to install? I think I get it! Thanks again,
Geo

jorge_culv said:
Ahh, so even though one of Molski's cabs does this, I need to disable security first to allow the other cabs to install? I think I get it! Thanks again,
Geo
Click to expand...
Click to collapse
yes, you need that or the other cabs wont install, most importantly it needs to be first, or else anything else that isnt signed wont install

Database Develop

welcome