what is Tuatara_v2a_Custom.zip on FTP? - MDA III, XDA III, PDA2k, 9090 Software Upgrading

There's an odd file in uploads/BlueAngel on the Ftp, "Tuatara_v2a_Custom.zip".
This is definitely not a flashable release - it's not even XORed as the romfile is nk.nba, as opposed to XORed nk.nbf.
Alongside the non-XORed nk rom, the seperate RGU registry databases are included, which sure enough look like TuMa-based files, having browsed through them looking at the COMPACTIONPRIO256, CACHESIZE etc settings.
Lastly there's an EXTROM.zip file which contains the camera_2k5 cab, JMM101257_WWE.cab and a cab of patches for missing files.
My question is - is this a Tuatara work-in-progress? Or just someone toying with us by uploading a half-decrypted TuMa 1.4?
I could of course go XOR the nba file and try flashing it, but that would be daft without some indication of what this file actually is.

it was first tuatara rom i think, it is basicly modified ported from wizard rom

Yep, that was the original = "WM5 ported from Wizard version 2a - beta"

Related

Post Exteneded Rom Links Here.

We have lost the exteneded roms again.
This is the 2nd time that I know of.
I think this has to do with the fact that they were not linked to post thus unkonw files get killed. I read that some were when I first came here.
I have most of them and will start uploading them again, linking them to a post.
Anybody have a better idea or know why they have gone?
Not sure whether they've been deleted or not, unless you have been reposting. They are under BlueAngel_Roms instead of Extended_Roms. Things seem to keep getting moved.
And what are they doing there ?
Sure I have been uploading to ExtenedRoms for over an hour now.
I will move the buggers!
Rename The Folder Exteneded_Roms
Clean up the file names
Gee I love house work thought I was would be cooking in the Rom Kitchen, but no.
We are going to have to post the links as they got killed once before.
Thought you were out.
Can you belive this!
Got a folder name that says "Dont touch MDAIIIUser Uploading" and we have dowloades.
You around need so help.
ok done
cleaned up the Exteneded_Roms
Will post in the morning.
We need to take these apart and find what version they are then rename them.
ftp://xda:[email protected]/BlueAngel/Exteneded_Roms/IIs Asia WWE Ext ROM.zip
ftp://xda:[email protected]/BlueAngel/Exteneded_Roms/Seimens_SX66_Ext_ROM_ENG.zip
ftp://xda:[email protected]_MDAIII_Extended_Rom_Inc_DeviceInfo.zip
Do you need some assistance with the Excel sheet for ROM Versions and contained cab files?
Is there a neater way of structuring the ftp server directories? Is there any way of setting folder permissions on the server for read/write only and not alter/delete?
Bebbo
Do I need help in the Exteneded Rom Kitchen. Does the .... (ok no bad jokes)
Sure do BIG Time!!! Its not my kitchen, I just work there!
The Idea of the Kitchen is not realy to find out what version number Orange Rom A has for an application but to see if Orange's Rom A has application / Patches that are better than our base.
The Sheet just is a list of the files which go:
Base (I-mate) + Rom A + Rom B = Extended Rom Kitchen (ERK) Rom
My end goal is to generate a ERK Rom Version which is as upto date as possible.
And have this info on wiki so we dont need to hunt for it.
How far am I, Well The UK orange rom has been looked at but info not posted in the kitchen.
( I think RTP worked on that but I am not sure as I was haveing PMs with few people about that rom. )
We have the 3 roms above that need to be looked and info posted in the Kitchen and added to the Excel Sheet.
The Excel Sheet needs to be made to look nice so the rest of us can undersatand it.
We need to check against the "List of know Blue angels" to see what rom is missing and see if we can find it.
Oh yes and its friday, I get to pick my kids as its "The 3rd weekend of every month" and as my ex-wife has got a date, thus By 12:00.
Chances of me doing much till monday are ZERO.
So you want a job, pay is s**t, hours are bad, it can get hot in the kitchen when there is a fire and you lose all your stuff.
You need to understand Roms, read cab files, use your brain and most of all admit to the fact that you don't know everything and thus ask.
I am looking for Pastry Chef as well. One that can write applications.
Is there any way of setting folder permissions on the server for read/write only and not alter/delete?
Click to expand...
Click to collapse
Given that at the moment we are all the user XDA, I would say no.
What we need is a "BA_Admin" that revokes the rights of XDA to Read only, then we just get into the next problem, the person that posted (XDA) can't update it, so he needs to be BA_Admin...
The FTP site is a public place and like Toilets some people just can't pee in the Pot like the rest of us and sonebody has to clean up the mess.
Is there a neater way of structuring the ftp server directories?
Click to expand...
Click to collapse
Got some ideas, then share them with us.
Will have a look at dir structure but seems reasonable to me at the moment (Though Extended is the correct spelling ). Will use my WinCE CAB Manager to see what if anything is different on rom's you haven't had chance to view yet and generally assist where I can.
I will have a look at the orange rom as well, time permitting.
Would it be better to extract the .nbf files to sub dirs under the Extended_ROMS dir and have similar structure for radio and CE ROM?
ie ->
BlueAngel/Extended_Roms/Imate_PDA2k_WWE_12200_162_10600_SHIP/ms_.nbf
(With cabs extracted as well under a cabs sub dir?)
BlueAngel/CE_Roms/Imate_PDA2k_WWE_12200_162_10600_SHIP/nk.nbf
BlueAngel/Radio_Roms/Imate_PDA2k_WWE_12200_162_10600_SHIP/radio_.nbf
Or leave as is and use the kitchen with a CAB's dir under it with all known versions of cab files so we can select the most appropriate ones?
I've posted the document on the Orange 1.12.139 ROM into the Kitchen. It's fairly large since there is so much in the Orange ROM.
Here's a link:
ftp://xda:[email protected]_1_22/Docs/Orange_WWE_1.12.139_ExtROM.doc
Unfortunately nothing really new though (Wish I had known you were doing this rom - just wasted 2 hours!).
I haven't looked at the WModem.exe update yet - any ideas what this is for?
Who keeps moving files in the BlueAngel section of the FTP server? Makes life difficult having to keep searching each time. Please let us all know what you are trying to achieve as it keeps breaking links on other web pages!
Running it comes up with this text:
The utility will simulate this device as a wireless modem, and let your PC/Notebook be connected to network wirelessly.
Before you press the 'Start' button, please make sure you have connected the device to your PC/Notebook by serial or IrDA connection and disabled the Activesync.
When the wireless modem is activated you will not be able to receive any voice calls.
Click to expand...
Click to collapse
It then gives options for Serial, IrDA, USB and Bluetooth. Start, Stop and View Log buttons. Plus connection status LEDs - Connection, Send Data and Receive Data.
I've never tried it. I tend to use something more direct for dialup from my laptop.
OK guys!!!
I don't know what your naming system is but I've uploaded the O2 UK EXT ROM and I've called it "O2_UK_XDAIIs_Ext_ROM_112178_WWE.zip". This one is the original from my device.
Regards,
Dom
Ext_ROM password??
MDAIIIUser said:
ok done
cleaned up the Exteneded_Roms
Will post in the morning.
We need to take these apart and find what version they are then rename them.
ftp://xda:[email protected]/BlueAngel/Exteneded_Roms/IIs Asia WWE Ext ROM.zip
ftp://xda:[email protected]/BlueAngel/Exteneded_Roms/Seimens_SX66_Ext_ROM_ENG.zip
ftp://xda:[email protected]_MDAIII_Extended_Rom_Inc_DeviceInfo.zip
Click to expand...
Click to collapse
Any known pw's for those .nbf files? I tried Rom editor but couldn't recognize the pw's
Re: Ext_ROM password??
Cyber-mate said:
Any known pw's for those .nbf files? I tried Rom editor but couldn't recognize the pw's
Click to expand...
Click to collapse
They aren't .nbf files???????? They are zipped up (rar'd up) cab files extracted from the extended roms.
+*+*+*+ FOR INFO +*+*+*+
The xda3nbftool has an extra command line option of -t which attempts to discover the xor key used to encrypt the .nbf files. This seems to work well for all files except the radio_.nbf file which causes it problems. Try it on roms that you are having problems with to see if it is the correct key. You can check the resulting .nba file with a hex editor to ensure the PH20B and other data is shown at the beginning of the .nba file.
+*+*+*+*+*+*+*+*+*+*+*+
I have pulled the above ext roms apart and the version numbers are as follows:
IIs Asia WWE Ext ROM.zip = Version "1.12.925 WWE"
Seimens_SX66_Ext_ROM_ENG.zip = Version "1.20.115 WWE"
T-Mobile_MDAIII_Extended_Rom_Inc_DeviceInfo.zip = Version "1.06.117 WWE"
Files renamed appropriately so any links will now be broken (plus the fact that some kindly person has renamed the Extended ROM directory to its correct spelling!)

2 NEW ROMs WM5 (Microsoft BT stack) based on namaich ROM

I have cooked two completely new WM5 ROMs based on namaich ROM.
One in WWE:
ftp://xda:[email protected]_Extracted_Updates/WM5_ArtZ/WM5_ArtZ_WWE.rar
and the second one customized for France:
ftp://xda:[email protected]_Extracted_Updates/WM5_ArtZ/WM5_ArtZ_FRA.rar
I hope you will like them ;-)
EDIT MDAIIIUser (links corrected)
Notes about these releases
__________________________________________________________
This version is based on "BA_5.1.1700_build_14343_Upgrade_V3_by_mamaich" ROM. I have used the original package and rebuild completely this version from that point. It's really a clean version and all modifications have been already tested successfully in TuMa's and Ivan's versions.
In fact, I've been using Ivan's 4 R1 version with Widcomm BT stack, but I find this version "dirty", because many Microsoft BT stack parameters are still in the registry and I found some keys were missing (intentionally?).
Personally, I don't see the interest of using Widcomm BT stack over a version built on Microsoft's... so I decided to go back to the original BT stack. Well, I don't use a headset but I use BT to connect my BA to the audio system in my car and TomTom Navigator 5.21 at the same time. I don't have any problem with this issue.
I find WM5 runs not as fast as WM2k3 on BAs, but I cannot see really an overall difference between Ivan's release and this one.
Do not hesitate to make your comments.
Briefly, I've done the following of changes:
-New Camera 2.3 version,
-New Pocket MSN version,
-SPCS is now disable by default,
-Extended_ROM is on your SD Card and supports AutoStart,
-GPRS disconection settings, WiFi fix, Buttons Fix, Headset Today, CarKit camera patch, Speed Settings (cache and flag values),
-Registry have been cleaned (ordered and double entries deleted) and version numbers have been added
HowTo install this new version
__________________________________________________________
1.- Copy the folders "\Extended_ROM" and "\Tools" in the root of your SD Card
2.- Launch "\Tools\DOC_Tool_1.0.exe" from your SD Card to to get extra storage space under WM2005 (31Mb). This change IS reversible with "DOC_Restore_1.0.exe"
3.- Launch WM5 upgrade
You're done!
When our BA will start, it will automatically install all the CABs located in "\Storage Card\Extended_ROM", though you must validate each CAB.
Some CABS will propose you to "Restart". Click on "Cancel" to continue the Setup. Your BA will automatically restart at the end of the process.
Notes about Extended_ROM
__________________________________________________________
I recommend you to install at least these CABs in the \Extended_ROM directory:
"\Storage Card\Extended_ROM\Album_BA_AKU26_RC23_Midi.cab"
"\Storage Card\Extended_ROM\ArcsoftMMS_3.0.7.6.cab"
"\Storage Card\Extended_ROM\BA_OEM_PA_WModem.sa.cab"
"\Storage Card\Extended_ROM\BA_WW5_ScreenRotate_1.1.cab"
"\Storage Card\Extended_ROM\BA_WW5_SMS_Alert_fix.cab"
"\Storage Card\Extended_ROM\BA_WW5_Wizard2_Tweaks.cab"
"\Storage Card\Extended_ROM\CAB-Cyberon_Voice_Dialer_2.cab"
"\Storage Card\Extended_ROM\CAB-TrueFax-2.09.1-WWE-04Mar05.cab"
"\Storage Card\Extended_ROM\Caller_ID_BA26_Generic_WWE_RC21.cab"
"\Storage Card\Extended_ROM\ClearVue_2.4.386_withoutBP_OzUp.sa.cab"
"\Storage Card\Extended_ROM\Java_10.1.2.76_BA_WWE_unremovable.cab"
"\Storage Card\Extended_ROM\PVPlayer_WWE_AAC.2577.cab"
"\Storage Card\Extended_ROM\Signed_HTC_CameraPatch_2.3.sa.cab"
"\Storage Card\Extended_ROM\ZIP_BlueAngelAKU26_Generic_WWE_RC20.cab"
Description
__________________________________________________________
"Album_BA_AKU26_RC23_Midi.cab" is used by the HTC Camera
"ArcsoftMMS_3.0.7.6.cab", you need this cab for sending MMS
"BA_OEM_PA_WModem.sa.cab" You can use your BA as a modem
"BA_WW5_ScreenRotate_1.1.cab" An icon to rotate your screen will display in "Today"
"BA_WW5_SMS_Alert_fix.cab" will fix a problem receiving SMS alerts.
"BA_WW5_Wizard2_Tweaks.cab" will install a small tool call "Set Security" that will allow you to set ON and OFF SPCS security.
"CAB-Cyberon_Voice_Dialer_2.cab" Voice Speed dialer. Works also with "Bluetooth"
"CAB-TrueFax-2.09.1-WWE-04Mar05.cab" You can use your BA as a Fax
"Caller_ID_BA26_Generic_WWE_RC21.cab" Will show the names in your phonebook instead of the phone numbers
"ClearVue_2.4.386_withoutBP_OzUp.sa.cab" will install clearVue fonts
"Java_10.1.2.76_BA_WWE_unremovable.cab" will install java
"PVPlayer_WWE_AAC.2577.cab" a multimedia player useful to play your MMS files.
"Signed_HTC_CameraPatch_2.3.sa.cab" contains important updates for the camera and camera
CarKit.
"ZIP_BlueAngelAKU26_Generic_WWE_RC20.cab" Zip utility for BA
Downloading... Will try it as soon as downloaded
[deleted]
Was not able to doenload with IE. Used WSFTP. Slow but it worked.
The Upgrade is running ...
YAY! The MP4 recording in Camera works!
The Keyboard lag is still there
Attempting test procedures...
[deleted]
willpower102 said:
i really don't understand what i am doing wrong. I do this stuff all the time so i'm not noob scrambling to learn ftp.
am i connecting to the wrong port?
Click to expand...
Click to collapse
NO : port 21 it's right.
Maybe your personal firewall? If you have installed one, try to disable it before connecting.
Hi,
BT problems are sthe same as in Tuma and Ivan's ROM, still disconnect's when pressing power onn and off.
Hi,
BT problems are still same as in Tuma and Ivan's ROM, still disconnect's when pressing power onn and off.
Hi guys,
According to a few post on xda-developers ( there's a very interesting post at http://forum.xda-developers.com/viewtopic.php?t=45846&highlight=cachesize by TuMa) and wiki.xda-developers, I have used the following parameters to speed up (cache settings) our BA in my ROM:
Registry entry: 0x00001000 (=dword:1000)
Number of sectors: 4096
Cache in kilobytes (KB): 2048
as follows
[HKEY_LOCAL_MACHINE\System\StorageManager\FATFS]
"EnableCache"=dword:1
"CacheSize"=dword:1000
"Flags"=dword:10046
[HKEY_LOCAL_MACHINE\System\StorageManager\Filters\fsreplxfilt]
"ReplStoreCacheSize"=dword:1000
[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\MSFlash\FATFS]
"Flags"=dword:28
"DataCacheSize"=dword:1000
[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\TRUEFFS_DOC\FATFS]
"Flags"=dword:10056
"DataCacheSize"=dword:1000
[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\TRUEFFS_DOC1\FATFS]
"Flags"=dword:14
"DataCacheSize"=dword:1000
but after doing further tests, I have the impression that reducing
CacheSize to 1024KB my BA runs faster and smoothly.
Registry entry: 0x00000800 (=dword:800)
Number of sectors: 2048
Cache in kilobytes (KB): 1024
[HKEY_LOCAL_MACHINE\System\StorageManager\FATFS]
"EnableCache"=dword:1
"CacheSize"=dword:800
"Flags"=dword:10046
[HKEY_LOCAL_MACHINE\System\StorageManager\Filters\fsreplxfilt]
"ReplStoreCacheSize"=dword:800
[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\MSFlash\FATFS]
"Flags"=dword:28
"DataCacheSize"=dword:800
[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\TRUEFFS_DOC\FATFS]
"Flags"=dword:10056
"DataCacheSize"=dword:800
[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\TRUEFFS_DOC1\FATFS]
"Flags"=dword:14
"DataCacheSize"=dword:800
I have also modified some of the default "Flags" values, but I don't recommend you to do that if you don't know exactly what are you doing.
For further information, please check:
http://msdn.microsoft.com/library/d...tml/wce50confatfilesystemregistrysettings.asp
Please, let me know your own experiences.
Regards,
it's very slow the telephone!
FANTASTIC ROM!!
Love the new ROM & extended rom on the SD card. By the way do we have to install all cabs in extended to the device or card?
Simon
You can install the cabs where you want. I installed all the 'system' cabs (such as camera upgrade, MMS tool, etc) to the internal storage, while all the others - to the card.
Is there any method to change the boot logo? Those stripes aren't nice...
Hi guys,
I keep on testing CacheSize and DataCacheSize values and I'm very impressed with the results I get. I show some articles in MSDN which point out that increasing cache size will decrease performance especially using flash memory.
In fact, reducing values (I'm testing =dword:100 (256 in DEC) and =dword:80 (128 in DEC)) my BA works really fast... as fast as WM2k3
I do believe now the fact of increasing values up to =dword:1000 (4096 in DEC), as we were doing, it DOES decrease overall preformance.
There're also other registry key I have modified to add the following values:
[HKEY_LOCAL_MACHINE\System\StorageManager\IMGFS]
"PathCacheEntries"=dword:80
"Flags"=dword:10046
"EnableWriteBack"=dword:1
"EnableDataCacheWarm"=dword:1
"EnableCacheWarm"=dword:1
"EnableCache"=dword:1
"DataCacheSize"=dword:100
"CompactionPrio256"=dword:ff
"CompactionCritPrio256"=dword:ff
"CacheSize"=dword:100
"CacheDll"="diskcache.dll"
"BufferSize"=dword:100
Please, if you can add these values and modify CacheSize and DataCacheSize in this key and all the keys I gave you previously in this thread, I would really appreciate your help.
I will post a new version on Sunday night or monday morning with the optimal values.
Concerning BT disconection at power off, I don't have a solution yet. For me it's not a big deal as I don't have a headset and when I use BT in my car with TomTom, the BA is always turned on but I keep researching.
ArtZ
@simonsalo
Well, install all cabs in the extended rom is not mandatory. But you need the following cabs if you want to use all possibilities of your BA:
Album_BA_AKU26_RC23_Midi.cab (this cab works with your camera)
ArcsoftMMS_3.0.7.6.cab (if you send and receive MMS)
BA_WW5_SMS_Alert_fix.cab (if you want to see the name of the person who is calling you)
Java_10.1.2.76_BA_WWE_unremovable.cab (needed for IE)
PVPlayer_WWE_AAC.2577.cab (used together with ArcsoftMMS)
Signed_HTC_CameraPatch_2.3.sa.cab (camera patch)
@_TB_TB_
This is how I add files (ie: boot splash image) into a nk.nbf file. If you feel confortable with it, you can try.
I use "IMGF tools" and "rgucomp.exe" to modify the ROM.
The process is as follows:
-With xda3nbftool.exe, I convert the original nk.nbf file into nk.nba
-With IMGF tools, I prepare the nk.nba file to antoher format so I can extract, delete, add files (You cannot replace an extinsting file for a new one if you don't delete first the old one) or make a dump of the whole ROM (all directories and files) into a directory (I use the this option). The registry is in two files: default.hv and user.hv
-Then I use "rgucomp.exe" to convert the registry (default.hv and user.hv) into a text (ASCII) file to modify the values.
-Once this is done, I convert the new ASCII files into UNICODE files and I use again "rgucomp.exe" to convert the UNICODE files into default.hv and user.hv
-I copy the new files to the dump directory to replace the old files. I also can add some new files (programs, dll, etc) to the dump directory (This is how I have updated the Camera and Pocket MSN)
-When all this is done, I compile the dump directory to build a nk.nba file.
-Finally, with xda3nbftool.exe I rebuild nk.nbf file
two thumbs up
Promptly, Thanks to Artz Efforts for new cooked WM2K5 ROM, I'm downloading... I do hope your ROM improved and solved some bugs & problems on Others ROM.
I have deleted Cache settings patch from ftp server. This patch is not need anymore with the versions actually on the server. The patch has been already included!
Hi ArtZ
Can i use your cab to setting my device using Ivan v4R1 now??
can you link to IMGF tools please
ArtZ said:
@simonsalo
Well, install all cabs in the extended rom is not mandatory. But you need the following cabs if you want to use all possibilities of your BA:
Album_BA_AKU26_RC23_Midi.cab (this cab works with your camera)
ArcsoftMMS_3.0.7.6.cab (if you send and receive MMS)
BA_WW5_SMS_Alert_fix.cab (if you want to see the name of the person who is calling you)
Java_10.1.2.76_BA_WWE_unremovable.cab (needed for IE)
PVPlayer_WWE_AAC.2577.cab (used together with ArcsoftMMS)
Signed_HTC_CameraPatch_2.3.sa.cab (camera patch)
@_TB_TB_
This is how I add files (ie: boot splash image) into a nk.nbf file. If you feel confortable with it, you can try.
I use "IMGF tools" and "rgucomp.exe" to modify the ROM.
The process is as follows:
-With xda3nbftool.exe, I convert the original nk.nbf file into nk.nba
-With IMGF tools, I prepare the nk.nba file to antoher format so I can extract, delete, add files (You cannot replace an extinsting file for a new one if you don't delete first the old one) or make a dump of the whole ROM (all directories and files) into a directory (I use the this option). The registry is in two files: default.hv and user.hv
-Then I use "rgucomp.exe" to convert the registry (default.hv and user.hv) into a text (ASCII) file to modify the values.
-Once this is done, I convert the new ASCII files into UNICODE files and I use again "rgucomp.exe" to convert the UNICODE files into default.hv and user.hv
-I copy the new files to the dump directory to replace the old files. I also can add some new files (programs, dll, etc) to the dump directory (This is how I have updated the Camera and Pocket MSN)
-When all this is done, I compile the dump directory to build a nk.nba file.
-Finally, with xda3nbftool.exe I rebuild nk.nbf file
Click to expand...
Click to collapse
Artz,
Thanks for this ROM. Seems very stable to me. Is there any way to get the UNLOCK feature as available on TuMA 1.3 and 1.4 on this ROM?
Just tried your cache patch and will report back after some experience.

Extracting CABs from a ROM

Anyone on here know how to Extract a CAB file from a ROM/Extended ROM? ive been trying to find something about this on here and cant seem to find anything that pertains to it. there are several programs that are included in roms and extended roms that i have and i wold like to be able to put them on my 8125 with the ROM i have now. Thanks in Advance!
Corey
If you already have a cabfile that resides in the extended rom the process is quite easy... just use total commander and copy the file from there to a place on your device where you can later use it...
If you don't have a cabfile but just a program, say arcsoft mms composer that's already integrated into the rom, the process gets a little more complicated, but not impossible. You will, however, need to know all the files that the program uses, dll's, imagefiles, exe's and registry posts, copy them from rom to your windows pc and from there use a program like ce cab manager to create a cabfile for it (if you want. you can merely transer all the files and registry posts to your current rom without creating a cab)
_Nomad_ said:
If you already have a cabfile that resides in the extended rom the process is quite easy... just use total commander and copy the file from there to a place on your device where you can later use it...
If you don't have a cabfile but just a program, say arcsoft mms composer that's already integrated into the rom, the process gets a little more complicated, but not impossible. You will, however, need to know all the files that the program uses, dll's, imagefiles, exe's and registry posts, copy them from rom to your windows pc and from there use a program like ce cab manager to create a cabfile for it.
Click to expand...
Click to collapse
cool, thanks for the info, what program do i need to use to unpack the NBF so i can access the files? I tried to use the one in the wiki (typho5) but i cant seem to get it to work.
for dumping rom's read through this thread
You'll probably want to read it all and I'm sure that it wont make that much sense to begin with but it'll come to you
For converting a nbf to nb files use:
Code:
typho5.exe -x nk.nbf
typho5.exe -x nk.nbf does NOT make it a .nba file!
It extracts the contents of the rom (OS, Extended Rom, Radio, Splash Screen, IPL/SPL) into .nb files.
The Extended Rom file can be opened with WinImage.
Molski
Thanks...i just checked out that thread..looks like ive got some studying ahead of me lol thanks for the help.
thanks Molski, you must have posted that just after i read the post above yours lol. thanks for the info i have another question for you here though. http://forum.xda-developers.com/showthread.php?t=291847 As smart as you guys are im sure theres a reason you havent done it though

How to merge multiple .cab files into single .cab file

Hi,
I am looking for a utility to merge multiple small ( free ) utilities into a single .cab file to automate the installation; just to ease the installation process after the hard reset or ROM upgrade.
Though i tried Win CE Cab Manager but unable to achieve that functionality - its look like to me that i am missing something somewhere.
Regards.
I'd like to know this too...
Does this help? Not used it myself
http://forum.xda-developers.com/showthread.php?t=392983
mic_888 said:
Does this help? Not used it myself
http://forum.xda-developers.com/showthread.php?t=392983
Click to expand...
Click to collapse
Thanks mic for the link... But according to that software ... one have to place all the required cab files in a specially designated directory and software start installing the files from there one by one...
But; what i am looking is a software that creat a single .cab file which includes all the required ( individual ) cab files along with the parameters e.g. installation location ( Device or Storage Card )....
sashami is the best solution which was actually inspired by a script called autorun back in the days of win mo but only way to do a auto install of cabs or all one one would be to attempt and cook into you're own rom or see if it's possible to cook all cabs into 1
Maybe extract all cabs with ini or XML file. Merge ini or XML place all extracted components in same folder and use cab building program to build cab from ini/xml...
Maybe.
This is the best thing I have found........not really an app per se.
What is UC? It is a feature contained in UC capable ROMs. A UC capable ROM extends initial customization to your SD card so you can load cabs and install XML files that are located there too. What this means is that once you get your customization scripts right, you can flash any UC capable ROM and all your apps and settings will be restored as part of the initial customization process whenever your SD card is inserted in the slot.
http://forum.xda-developers.com/showthread.php?t=366337
I have been using Slueth's ROM and this UC method for quite a while now and it works fantastically. Takes a little effort but anything worth it's oats will take atleast a little effort.
http://forum.xda-developers.com/showthread.php?t=366284
I just come a across while searching, here is another solution:
http://www.pocketpctoolkit.com/
this should not be a advertisement, because it is not freeware, but a suggestion.
you can add cabs and the program builds an desktop or device installer and merges the cabs (and other files). the device installer is a exe not a cab....
if you look deeper in the internet you find a full time solution...
hope it helps...
chipsxj said:
This is the best thing I have found........not really an app per se.
What is UC? It is a feature contained in UC capable ROMs. A UC capable ROM extends initial customization to your SD card so you can load cabs and install XML files that are located there too. What this means is that once you get your customization scripts right, you can flash any UC capable ROM and all your apps and settings will be restored as part of the initial customization process whenever your SD card is inserted in the slot.
http://forum.xda-developers.com/showthread.php?t=366337
I have been using Slueth's ROM and this UC method for quite a while now and it works fantastically. Takes a little effort but anything worth it's oats will take atleast a little effort.
http://forum.xda-developers.com/showthread.php?t=366284
Click to expand...
Click to collapse
i flash phones like everyday. using that method is for doing a couple of cabs. if you are trying to do like 100 cab files it will take a loooooooooooong time.
wince cab manager
if you just want to make one cab i would use Wince Cab Manager (OCP Software) (google it) to extract all the neccesary information from all the cab files.
then re-import all the information (links, registry, files etc) into a brand new Cab File.
so long as you keep all the extracted cab files separated this should be easy enough, but time taking.
Hope that helps. =D
Dan

[REF|TUT] My first Rhodium ROM - Completed

I’ve started cooking my own ROM’s only a week ago. I wanted to share my experiences here as it’s not as easy as it seems Well, with the right settings, tools, references, etc it makes it easier though. So this is my sharing back to the community, my tutorial/reference guide on how to cook a ROM.
The result of my days of hard work is named DaxyROM and can be found here.
If you want to start cooking, be prepared to read a lot and spent a lot of time trying your home cooked meals. But when it boots and works as expected, you’ll enjoy all the time spent.
There are 3 steps I’d like to discuss in the following 3 posts:
1) Basic ROM extraction and cooking
2) Adding / Removing programs
3) Upgrading your XIP/SYS (aka install new OS version)
First of all get to know what you’re dealing with. Understand what SYS/EXT/OEM/ROM/XIP is ‘cause at the end of the week you can’t think of anything else. Good source here.
1 Basic ROM extraction and cooking
I’ll be using the Ervius Visual Kitchen and the official WM6.5 ROM from HTC to start with.
* Download Ervius Visual Kitchen. Always use the latest version.
* Download WM6.5 ROM’s from HTC
* Download CustomRUU.exe
Preparing the kitchen:
Extract Visual Kitchen (VK) to C:\Kitchen (will be refered to as Kitchen now)
Create a directory in the Kitchen named RomDump
Open the WM6.5 HTC ROM .exe file with Winzip
Extract the file named RUU_signed.nbh to the RomDump directory
Now open the Kitchen (erviuskitchen.exe). Ignore the warning messages
Click on the bottom left button named “Dump nbh/nb/payload”
Open the RUU_signed.nbh file and wait till it’s completed.
Enter the Kitchen\RomDump\dump directory
Move all files to Kitchen directory
There seems to be an issue with kitchen_build_rom.bat while building your ROM.
Modify your kitchen_build_rom.bat file from this:
Code:
set DSM_TEMPLATE=%dsm%
set DSM_INCLUDES=*
REM **************** TOOLS\platformrebuilder.exe
if not "%errorlevel%"=="0" goto error
To this:
Code:
set DSM_TEMPLATE=%dsm%
set DSM_INCLUDES=*
REM **************** TOOLS\platformrebuilder.exe
REM **************** if not "%errorlevel%"=="0" goto error
You’re now ready to go.
Built your first ROM – The Visual Kitchen Basics:
Click on the pull-down menu next to RHODIUM and select RHODIUM
Ignore the messages. You’ll see the screen building now
Fill in the name of your ROM at the ROM ver. Field
Check the “Real WM 6.5 AKU” field
Click on the “Other” button
Change the –PP value from 6 to 18 and click on the Close button
Save the settings: hit the “Save ROM” button. Filename must end with extension .erv.
You’re ready to hit the Create ROM button
Wait till it finishes
Now open the Kitchen\RELEASE_Rhodium directory
Copy the CustomRUU.exe to this directory and run it
You’re now running the HTC WM 6.5 ROM rebuilded by yourself
Right now your kitchen is ready to use and you can modify it as much as you like.
Part 2: Adding / Removing programs
Right now we know that the kitchen works. We have rebuiled the official version and it boots up fine. Make sure to test your extracted ROM works otherwise you will loose a lot of time. Now it's time to make changes. Keep in mind that the following is what I've teached myself and that there might be better methods in adding/removing packages.
The easiest is removing packages. Just double-click on the package and it won't be included. If you want it back, just double-click again and it's back in. Easy as that.
Keep in mind that you can't remove OEM packages and that if you're removing packages from the SYS you have to be carefull as you might run the risk you remove a core application and that Windows won't boot anymore. You can however safely remove packages like LiveSearch, MSTag, OneNote, etc without any problems.
The EXT directory is where all packages reside. This directory is devided in 2 sub-directories. One for Rhodium specific packages and one for Shared platforms. By default all applications are in the Rhodium directory but you might want to change this manually to Shared if you're planning on building for multiple platforms. For now we'll keep them in the Rhodium directory.
You need to either find EXT packages online, or you need to convert CAB files to EXT packages. That is basically it.
I've found a lot of new EXT files here: http://www.everythingdiamond.info/showthread.php?t=94. You can download new EXT folders and copy them into the VK\EXT\Rhodium\<built>\Rhodium_External_Packages directory. Now load VK and Load your previous saved config. Scroll down the list and you will see your new package. This package is not yet included in the Kitchen. This is useful if you're upgrading packages so you'll know which one is new and which one is old.
If you're upgrading packages, keep in mind that some do depend on each other. For example Manila heavily depends on all kinds of other packages. When you're upgrading one, upgrade the others as well unless you're certain there are no dependances. You'll find out when your upgrading. Make sure to safe your work very often so you can always revert back to your previous situation.
As I mentioned you can also convert CAB's to EXT. This can be done using the package-creator from Ervius. TotalFire Package Converter does the job as well, but I haven't used it yet.
Download your application as cab file. Open the package converter, open the cab file and it converts to an EXT directory. This EXT directory can be copied into the kitchen again.
Adding your own EXT is more complicated. For example if you want to create a package which holds all your registry tweaks.
You can either download this file and change the .reg file, or you can take the hard way and learn by using this tutorial: http://www.mediafire.com/file/j15nqfzkwz5/CreatingOEM.zip
Both are written by user kwbr. See here for more info: http://forum.xda-developers.com/showthread.php?t=480714.
I believe this concludes this section. You should be able to add and remove packages right now. Next stop, installing a different Windows build.
Please sent me feedback on how to improve my posts.
Part 3: Upgrading your XIP/SYS (aka install new OS version)
It's time for the last part of my Tutorial. This time I will explain how to upgrade your XIP/SYS.
First you need to find your new XIP/SYS. I get mine WM 6.5.1 at http://forum.xda-developers.com/showthread.php?t=544445 but there are probably more sources.
First you need to know what to get. If I'm taking the above URL as example, there are several files.
The first one you need is the XIP/SYS one. This however is the OS for a screen resolution of 480x600 (The Touch Pro2 has a screen resolution of 480x800). You still need this file as it the the base OS combined with the (wrong) resolution files. That's why you need the 2nd file named "0409 USA English United States (Includes COMMON DPI, required for others)" as well. This is the english version for all resolutions.
The first file you can just extract in your SYS directory. It will create a new directory with the new build number and a directory named Shared.
The Shared directory you need to move to your ROM directory. This means you end up with a new build number in the Shared directory.
Now we just need to make sure the resolution files are copied. This means you need to copy a list of directories. At first create a directory named SYS\<build>\dpi_192_resh_480_resv_800. Just extract the complete 0409 Language file into a temp directory and the create the following directory structure by moving directories:
Code:
SYS\<build>\dpi_192_resh_480_resv_800\0409\Base_Lang_0409_DPI_192_RESH_480_RESV_800
SYS\<build>\dpi_192_resh_480_resv_800\0409\Themes_Lang_0409_DPI_192_RESH_480_RESV_800
SYS\<build>\dpi_192_resh_480_resv_800\COMMON\base_dpi_192_resh_480_resv_800
SYS\<build>\dpi_192_resh_480_resv_800\COMMON\MediaOS_dpi_192_resh_480_resv_800
SYS\<build>\dpi_192_resh_480_resv_800\COMMON\Phone_dpi_192_resh_480_resv_800
SYS\<build>\dpi_192_resh_480_resv_800\COMMON\Redist_dpi_192_resh_480_resv_800
This concludes the SYS, now the XIP.
The zip file you downloaded also contains a directory named "MSXIPKernel".
Extract this directory to your ROM\Shared\<build> directory.
Now go into the directory ROM\Rhodium.
Inside the builds you can find the OEMXipKernel which are basically the device specific drivers.
Usually these drivers don't change, unless you are upgrading the OEMXipKernel using a newly released ROM from HTC.
For now you have to copy the original build directory over to the new directory and you're done.
Right now your OS is ready to cook:
Open your Kitchen
Open your saved configuration file
Change the XIP and SYS versions (top right) to the new build version
Hit the Create ROM button
You're all set
After creating your new SYS, I suggest changing some default values. For example changing Unsigned Themes/CAB Policies:
Open the file named OEM\Rhodium\0409\Operator Pkg\mxipupdate_oemoperators_100.provxml
Find the section <!--337.01_SecurityPolicy-->
Add the following lines:
Code:
<parm name="4101" value="8" />
<parm name="4102" value="1" />
<parm name="4122" value="1" />
<parm name="4103" value="16" />
<parm name="4097" value="1" />
Save the file
Cook your ROM
Basically this means:
ID 4101: Unsigned CABS Policy = 8
ID 4102: Unsigned Applications Policy = 1
ID 4122: Unsigned Prompt Policy = 1
ID 4103: Unsigned CABS Policy = 16
ID 4097: Unsigned Prompt Policy = 1
Now you won't get warnings if you install unsigned applications etc.
One last thing to keep in mind. Don't forget to grab a new version of the OEM directory once it gets released by HTC.
I've ran into a situation where ActiveSync ran out of memory and a new OEM fixed this.
Thanks
Ervius: Big thanks to Ervius for his great Kitchen and Package creator: http://forum.xda-developers.com/showthread.php?t=469420
Da_G: For providing the latest WM builds: http://forum.xda-developers.com/showthread.php?t=544445
hilaireg: For providing his tuturial which was my starting point: http://forum.xda-developers.com/showthread.php?t=521632
kwbr: For his tutorial on creating applications: http://forum.xda-developers.com/showthread.php?t=480714
Everyone I forgot to add. Make yourself known and I'll add you of course!
This concludes my Tutorial. I hope you find it useful. Please feel free to provide feedback so I can adjust the tutorial or provide answers.
Eventually I may try cooking my own ROM.
Not because I can't find any good roms out there.
But just for the simple fact that I want to learn how to do it.
Thanks for taking the time to write this all up.
Just what I was looking for. I have been searching and reading and searching and reading but not getting anywhere. After following your post I've dissasembled a ROM, renamed it, and then reassembled it.
Now I was just following a recipe and didn't understand everything that happened (what is the -PP value and why am I changing it?) but I'm finally making some progress. Looking forward to your upcoming posts.
BTW, I just used the official TMo US 6.1 ROM that CDGuider dumped and made available. It'll do while I'm learning but I'm really waiting for the Official TMo US 6.5 to be released so I can use it as the main ingredient.
S
sleonard said:
Just what I was looking for. I have been searching and reading and searching and reading but not getting anywhere. After following your post I've dissasembled a ROM, renamed it, and then reassembled it.
Now I was just following a recipe and didn't understand everything that happened (what is the -PP value and why am I changing it?) but I'm finally making some progress. Looking forward to your upcoming posts.
BTW, I just used the official TMo US 6.1 ROM that CDGuider dumped and made available. It'll do while I'm learning but I'm really waiting for the Official TMo US 6.5 to be released so I can use it as the main ingredient.
S
Click to expand...
Click to collapse
Let me know if I missed something. I had to do it from the top of my head so if I forgot to add an action, let me know and I'll add it.
PS, the -PP allows you to change the PagePool size (sort of swapfile for WM).
Some people set it to 0, some to 12-18. I found 18 to be working fine. I must admit that I have too little knowledge to truly understand the PP stuff to come to a clear correct value (I believe it's questionable, the values).
If anyone disagrees, let me know
This is a great post.
I've subscribed because I'm really interested in learning and once I've ran through it myself will reference it on my site for all to use.
Well done you, supply and demand.
Daxy, On Tuesday I get my Pro2 and begin to try. Thanks for a great post!!!!!!!!!!!!!
I download the files of 23069, for example, where should I hold?
Xip and sys...
Awesome Information!! Thanks a lot and I appriciate it because rarely people share knowledge!
Thanks for the clear tutorial! Looking forward to future updates!
really excited to start making my own roms...
thank you for taking the time and making this
hopefully in the future ill be able to contribute to the community...
my touch pro2 could use some of my own flavor lol
thanx for the effort ...
gonna read thru it when i am more awake ... lol ... this seem to be what i am looking for ... wanna cook my own rom but proper info is few and far between for the rhodium ... unless i waslooking in the wrong places ... hehehe
I have used this tool to dump official rom, it works. But when i dump others' customized roms, it always says 'lost XIP'. why?
Thanks all for your kind words.
I've updated Post 2: Adding / Removing programs
Hope you like it. Please let me know if anything is missing.
Next post will be regarding using a new version of Windows, where to place files etc. This one should be up in a couple of days.
eddy16112 said:
I have used this tool to dump official rom, it works. But when i dump others' customized roms, it always says 'lost XIP'. why?
Click to expand...
Click to collapse
Customized ROMs are protected. You cant dump them. You can only dump official ROMs.
eddy16112 said:
I have used this tool to dump official rom, it works. But when i dump others' customized roms, it always says 'lost XIP'. why?
Click to expand...
Click to collapse
ai6908 said:
Customized ROMs are protected. You cant dump them. You can only dump official ROMs.
Click to expand...
Click to collapse
Correct! even if the customized rom was unprotected you still would not be able to rebuild a rom off of it because of the loss of rgu's and dsm's in the origional building process. would be very difficult.. best thing to do is ask for the kitchen files from the chef and hope they can share.
edit: one thing you can do is use an app called rom imaged editor and open the nbh with that, you can grab individual files out, even protected roms you can.. then you can add things on your own.
I've changed the topic to My first Rhodium ROM. Though it would sound better.
joshkoss said:
edit: one thing you can do is use an app called rom imaged editor and open the nbh with that, you can grab individual files out, even protected roms you can.. then you can add things on your own.
Click to expand...
Click to collapse
I have extracted files from kooked roms no biggie. saves time from flashing for sure...
I have tried to extract all files from kooked rom too, and it seems to work. but might be able to use some dll files.
Everytime I build the ROM (rebuilding the stock rom, not config changes) towards the end the kitchen gives me a runtime error, I have tried on a 64-bit vista and 32-bit XP.
After reviewing the log it appears that the problem is:
Executing: kitchen_build_rom.bat.....
ERROR! (errorlevel: 1)
ERROR executing: kitchen_build_rom.bat
ERROR!!!
Wait some seconds...
No ''SVN'' folders present...

Categories

Resources