Database Info

Mda compact from german to english for dummies?

Can somebody please dump the English Rom version including the first German 416 bytes, in ONE file?
Or just explain how to upgrade, for dummies?
because a German MDA = No MDA!

For not advance user it's not easy managing bootloader and so on...

this works upgrading to 1.03!!!
After some searching and trail by error testing I have sucesfuly upgrade my German T-Mobile MDA with the latest Jam rom from the I-mate website.
ROM version 1.03.00 WWE
Radio version 1.01.00
ExtROM version 1.03.141 WWE
I am not resposible for any damages !!! It should work perfectly !!
First Step:
You need to download the latest ROM (English version!!!).
http://www.clubimate.com/Support/ma_cdlsku2_arb_10300_141_10100_ship.exe
After download run it.
When you see a screen with "welcome to device software update utility", do nothing and go to your TEMP directory of windows. I you don't know where to look do a search for this file name: MaUpgradeUt.exe
When you have located the directory that hold this file copy the complete contents, 8 files. To a directory on your PC eg: c:\jam
Then cancel/close the "welcome to device software update utility"
Second step:
You need to find out the Operator code and language of you device.
If you have a MDA Compact from germany, the Operator code is: T-MOB101
If you have a German language ROM your code is: GER
If you have a UK ROM the Language code is: WWE
Third Step:
Download xda3nbftool.exe, and put it in the same directory as the 8 ROM files.
Fourth Step:
Build a batch file, name it change.bat or whatever you like in the directory where you put ROM files.
Paste the following in it:
------------------------------- paste the data below ------------------------
xda3nbftool -x ms_.nbf ms_.nba 0x20040522
xda3nbftool -x nk.nbf nk.nba 0x20040521
xda3nbftool -x radio_.nbf radio_.nba 0x20040523
xda3nbftool -so T-MOB101 -sl WWE ms_.nba
xda3nbftool -so T-MOB101 -sl WWE nk.nba
xda3nbftool -so T-MOB101 -sl WWE radio_.nba
xda3nbftool -c -u NK.nba
xda3nbftool -c -u ms_.nba
xda3nbftool -c -u Radio_.nba
xda3nbftool -x ms_.nba ms_.nbf 0x20040522
xda3nbftool -x nk.nba nk.nbf 0x20040521
xda3nbftool -x radio_.nba radio_.nbf 0x20040523
del *.nba
--------------------- paste the data above --------------------
This data is for a MDA Compact from T-mobile, with a UK language.
If you have a German Language change the WWE to GER in the file.
Fifth Step:
Go to a Command Promt and change to the directory you have places all the files in. Then run your batch file. It give's some errors maybe about a password but ignore those, it works !
Sixth step:
Run the MaUpgradeUt.exe program in the directory, it should start the UPGRADE. If not then you have not changed the language or operator code sucsesfully.
Last step:
If you have reset your device after the upgrade, be sure to skid the Extended ROM install. Install the apps you need manualy from the EXT-Rom. Or you will end up with some arabic nonsense.
Some tips:
If you want to find out your Operator Code and Language of you device:
In the directory you should have a file called: GetDeviceData.exe copy this file to your device. On the device run it, it looks like it does not work but that is fine! Now go with you PC to your windows directory on your device. You should find a file called DeviceData.txt there. Copy it to your PC and open it with notepad.
You should see something like this:
---------------------------------------------------------------------------------
PM10A 0 A WWE E T-MOB101
1.01.00 0 0 1.03.141 1.00.10 WWE
-----------------------------------------------------------------------------
The PM10A is the Device code
The WWE stands for English language, if you have a different language it hould say so. German would be GER.
The T-MOB101 is the Operator code.
If you have different info there use it for the batch file. Language an operator code.
Good luck everybody !!! And I will try to provide more info if needed !

xda3nbftool -x ms_.nbf ms_.nba 0x20040522
xda3nbftool -x nk.nbf nk.nba 0x20040521
xda3nbftool -x radio_.nbf radio_.nba 0x20040523
0x20040522,0x20040521,0x20040523 depends on what? the rom?
i mean for the other roms upgrade is that nummber same? example chinese rom upgrade.

Cannot get the ROM
I have tried following the link that everyone has for the ROM at:
ClubIMate . . .
ma_cdlsku1_wwe_10300_143_10100_ship.exe
But I get Page Cannot Be Displayed.
My previous experience with I-Mate, having bought a used JAM, was that I now had to buy a membership and get an ID and Password to get anything.
Does anyone have the file OFF SITE from the club, or does anyone have a password, yada yada?
Barring all that, has anyone built a better ROM than that? Is there a kitchen available for it?
And anyone looking for themes I am selling a collection of mine on eBay and offer to sell 6 for the price of 3 to anyone that references xda-developers . . . I hope you like.
http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItem&rd=1&item=190106886535&ssPageName=STRK:MESE:IT&ih=009
Thanks

I AM BACK!!! Just picked up a JAM myself (thanks MMB) and was lucky to find this, even though it was a generic Worldwide English ROM: http://rapidshare.com/files/54981836/JAM_WWE_11200_128_11210_ship.exe.html
I'm sure you can put together the appropriate Operator CAB files on the FTP.

mmc for big storage rom upgrade

can i use mmc for big storage rom upgrade

You can try, but many people are reporting problems with it.
You can optain BS with an usb upgrade as well via this:
All steps:
-get nbfdec from the thread 'upg to 1.13 wwe rom (with 1.13 radio)in 10 easy steps' post from hlt on first page
- get maupgradeut_noid.exe from the ftp
- Download the shipped rom from:
http://www.t-mobile.nl/zakelijk/htdocs/page/service/mda_compact_upgrade.asp
- Download the Hexeditor from:
http://www.hhdsoftware.com/hexeditor.html
1. Unzip NL_11300_131_11200.exe (or any other shipped rom)
2. Put NBFDEC in the same directory as the unzipped shipped rom files
3. Copy the getdevicedata.exe to your Magician and execute to write DeviceData.txt
to \Windows and view with notepad
5. Decode nk.nbf -> nk.nb1:
nbfdec -d nk.nbf nk.nb1
6. Hexedit header to correct ID from DeviceData.txt
(probably only if using a rom from other provider)
7. Replace pattern for bigstorage in hexeditor:
locate the 02 00 00 80 00 20 and change 80 00 to b8 01 in the nk.nb1
(use binary search for this!!)
7. Encode nk.nb1->nk.nbf
nbfdec -e nk.nb1 nk.nbf
8. run maupgradeut_noid.exe to upgrade CE image
Also, this way you will save the contents of increased \Storage folder if previous rom was bigstorage one
Usage sample (must be run from the same folder as nbf files or specify full path):
nbfdec -d nk.nbf nk.nb1
nbfdec -e nk.nb1 nk.nbf

oltp said:
You can try, but many people are reporting problems with it.
You can optain BS with an usb upgrade as well via this:
All steps:
-get nbfdec from the thread 'upg to 1.13 wwe rom (with 1.13 radio)in 10 easy steps' post from hlt on first page
- get maupgradeut_noid.exe from the ftp
- Download the shipped rom from:
http://www.t-mobile.nl/zakelijk/htdocs/page/service/mda_compact_upgrade.asp
- Download the Hexeditor from:
http://www.hhdsoftware.com/hexeditor.html
1. Unzip NL_11300_131_11200.exe (or any other shipped rom)
2. Put NBFDEC in the same directory as the unzipped shipped rom files
3. Copy the getdevicedata.exe to your Magician and execute to write DeviceData.txt
to \Windows and view with notepad
5. Decode nk.nbf -> nk.nb1:
nbfdec -d nk.nbf nk.nb1
6. Hexedit header to correct ID from DeviceData.txt
(probably only if using a rom from other provider)
7. Replace pattern for bigstorage in hexeditor:
locate the . and change 80 00 to b8 01 in the nk.nb1
(use binary search for this!!)
7. Encode nk.nb1->nk.nbf
nbfdec -e nk.nb1 nk.nbf
8. run maupgradeut_noid.exe to upgrade CE image
Also, this way you will save the contents of increased \Storage folder if previous rom was bigstorage one
Usage sample (must be run from the same folder as nbf files or specify full path):
nbfdec -d nk.nbf nk.nb1
nbfdec -e nk.nb1 nk.nbf
Click to expand...
Click to collapse
how to decode step 5??how to do step 6?? i have DeviceData.txt but what 2 do next....using arabic rom imate and i cant locate binar search in hexeditor...how to find02 00 00 80 00 20???? plz some 1 help me im an noob caz iwant bs for real ???????????plz any body thx in advance

Hi max414,
I changed step 5 & later hope you understand them now. I think you've succeeded in unzipping the shipped-rom, so you have all the .nbf, getdevicedate.exe, enterbl.exe etc files in the same directory. It will be very handy in step 5. that you put all these file together with NBFDEC.exe & MAUPGRADEUT_NOID.EXE in a directory like c:\BIGStorage\
5. Decode nk.nbf -> nk.nb1:
NBFDEC must executed from the commandline. Press the 'Start button' & select 'Run…' & type CMD in the window you get. Now a command window opens & go to the directory where you've put all your files. Then type on the commandline:
nbfdec -d nk.nbf nk.nb1
6. Skip this step you're going to use maupgradeut_noid twice in step 8.:
Hexedit header to correct ID from DeviceData.txt
(probably only if using a rom from other provider)
7. Replace pattern for bigstorage in hexeditor. Open the nk.nb1 in hexedit and locate twice the byte pattern 02 00 00 80 00 20. Don't use the text search!!
Change the 80 00 to b8 01
7. Encode nk.nb1->nk.nbf again with nbfdec on the command line.
nbfdec -e nk.nb1 nk.nbf
8. Connect your magician with usb to your PC & run maupgradeut_noid.exe twice to upgrade CE image. The first run will give you error 120 (country id), just exit and start maupgradeut_noid.exe again now it will proceed.
Succes, M

fi9 workks
i have 1.13 big storage :twisted:

nice to see

How For Extracting Files From Cooked Rom

hi!!
i downloaded llbasha-WM5-AKU35pp16c3 rom
i want extract os.nb file from nk.nbf with typho5 utility (typhoonbftool_v5),i got this error:
unknow header format, and it abort work.
other way:
i want extract os.nb file from nk.nba with prepare_imgfs, and i got this error:
searching for IMGFS start.......Not found!!!
anybody know if it can extract some file from a rom already cooked ???
thank in advance

use xda2nbftool
open command prompt -> xda2nbftool.exe -c nk.nbf nk.nba 0x20040304 press enter.

Find where ROM begins (rommaster)

Hi,
I'm trying to extract XIP part of an orange rose rom here :
http://forum.xda-developers.com/showthread.php?t=450221
I know how to obtain OS.nb with nbhextract, but i don't know how to find "rom begin".
If i use nbsplit to obtain os.nb.payload, i don't know what option i must use.
And after, if i use "kaiser" option with nbsplit, i don't know how to extract xip with rommaster, and what "begin" option i can give.
How i can find it ?
Thanks.

No idea please ?
I always have this problem.
Thanks.

try this:
Code:
RomMaster.exe -x -w 5 -b 0x320000 OS.nb.payload -o xip.bin
good luck

Hi,
I was able to :
nbsplit.exe -kaiser OS.nb
and :
RomMaster.exe -x -w 5 -b 0x320000 OS.nb.payload -o xip.bin
and :
dump xip.bin with XIPPort
I obtained :
OUT and files usually found in xip.bin
BUT, how i can find this start adress 0x320000 ?
This value is for kaiser, but i don't konw if it's ok with others devices.
And how i can know if "kaiser" value is good with nbsplit ?
Thanks.

moved to Q&A section. please post your questions in the Q&A section next time.

fireburned said:
Hi,
I was able to :
nbsplit.exe -kaiser OS.nb
and :
RomMaster.exe -x -w 5 -b 0x320000 OS.nb.payload -o xip.bin
and :
dump xip.bin with XIPPort
I obtained :
OUT and files usually found in xip.bin
BUT, how i can find this start adress 0x320000 ?
This value is for kaiser, but i don't konw if it's ok with others devices.
And how i can know if "kaiser" value is good with nbsplit ?
Thanks.
Click to expand...
Click to collapse
Read the last few sentences of my post. It may be the long way to go about it, but it works for me.
http://forum.xda-developers.com/showpost.php?p=2846121&postcount=58

KMFM$ said:
Read the last few sentences of my post. It may be the long way to go about it, but it works for me.
http://forum.xda-developers.com/showpost.php?p=2846121&postcount=58
Click to expand...
Click to collapse
I always have a problem.
I want to extract XIP from this rom :
http://forum.xda-developers.com/showthread.php?t=450221
I tried this :
Code:
nbhextract.exe *.nbh
I obtain :
03_OS.nb => renamed to OS.nb
I tried :
Code:
ImgfsFromNb.exe OS.nb imgfs.bin
ImgfsFromNb 2.1rc2
ImgFs partition starts at 0x00000000 and ends at 0x00000000
Dumping IMGFS at offset 0x006c6c00 (size 0xff939400)
Done!
How i can use nbsplit ?
How i can extract XIP ?
I don't know how i can use nbsplit to obtain OS.nb.payload and OS.nb.extra
I tried rommaster to extract XIP (but it doesn't works because i don't use OS.nb.payload i think) :
Code:
RomMaster.exe -x -w 5 -b 0x006c6c00 OS.nb -o xip.bin
[Info] It is a common ROM.
[Error] File is damaged, end address small than start address.
[Error] File is damaged, end address small than start address.
Could you help me please ?
Bye.

No idea, please ?

How to dump TP2 ROM from Phone

I have successfully dumped the ROM from my Brand New VZW Touch Pro 2 ... Here is how I did it. You will need itsutils to dump the ROM, and imgfstools to extract it.
Dump:
1) List partitions - Should show Part00 to Part03 - pdocread -l
2) Get Part00 address - pdocread -w -d FLASHDR -p Part00 -t -b 0x800 - Find the partition address (displayed as 0x######)
3) Dump Part00 - Use address from step 2 - pdocread -w -d FLASHDR -p Part00 -b 0x800 0 0x###### Part00.raw
4) Repeat steps 2 & 3 for Part01, Part02 and Part03 ... MAKE SURE YOU USE THE CORRECT ADDRESSES
Partitions:
Part00 - Core XIP? (May have something to do with AutoUpdate)
Part01 - XIP
Part02 - OS IMGFS
Part03 - User Storage (TFAT)
Extract XIP (Part00 and Part01 ... You will need bepe's dumpxip.exe from ervius visual kitchen):
1) Make sure there is not an XIP folder (if so, rename it) and run dumpxip Part00.raw
2) Rename XIP folder to XIP_00 (ren XIP XIP_00)
3) Make sure there is not an XIP folder (if so, rename it) and run dumpxip Part01.raw
4) Rename XIP folder to XIP_01 (ren XIP XIP_01)
Extract IMGFS (Part02):
1) imgfstodump Part02.raw - This will create a folder called dump, and extract the contents to it.
View User Storage (Part03):
1) Mount Image using DaemonTools Lite
To rebuild flashable ROM from DUMP (Currently OS Only, No radio or SPL):
1) You need a base_os.nb.payload for your device ... See below for details
2) Convert OS IMGFS (Part02.raw) to nb.payload (new-os.nb.payload) imgfstonb Part02.raw base_os.nb.payload new-os.nb.payload
3) Insert XIP (Part01.raw) into new-os.nb.payload implantxip Part01.raw new-os.nb.payload
4) Merge os-new.nb.payload into os-new.nb nbmerge -kaiser new-os.nb
5) Create os-new.nbh nbhutil, Select "Touch_Pro2" under "Target Device", change RHOD*** to RHOD500, click the ... box next to OS, and select new-os.nb, click Build NBH and select where to save NBH file.
How to get a base os.nb.payload:
1) Download a stock ROM and extract RUU_Signed.nbh
2) Extract RUU_Signed.nbh nbhextract RUU_Signed.nbh - This will list the files extracted ... The one you need is ##_OS.nb ... Copy as os.nb copy ##_OS.nb OS.nb
3) Split OS.nb to OS.nb.payload nbsplit -kaiser OS.nb
4) Create OS.imgfs.bin imgfsfromnb OS.nb.payload OS.imgfs.bin
5) Create empty directory called 'DUMP' (If a DUMP folder exists, rename it) mkdir DUMP
6) Create a blank IMGFS file imgfsfromdump OS.imgfs.bin blank_imgfs.bin
7) Create base_os.nb.payload imgfstonb blank_imgfs.bin OS.nb.payload base_os.nb.payload

Dump SPL and Radio
Does anyone know how to do this?

Oh my god I found the answer on "how to dump a rom from the TP2"!
Could someone rename the topic in something like "official guide" or stick it?
I think it could be useful for a lot of people..

dj13241 said:
How to get a base os.nb.payload:
1) Download a stock ROM and extract RUU_Signed.nbh
2) Extract RUU_Signed.nbh nbhextract RUU_Signed.nbh - This will list the files extracted ... The one you need is ##_OS.nb ... Copy as os.nb copy ##_OS.nb OS.nb
3) Split OS.nb to OS.nb.payload nbsplit -kaiser OS.nb
4) Create OS.imgfs.bin imgfsfromnb OS.nb.payload OS.imgfs.bin
5) Create empty directory called 'DUMP' (If a DUMP folder exists, rename it) mkdir DUMP
6) Create a blank IMGFS file imgfsfromdump OS.imgfs.bin blank_imgfs.bin
7) Create base_os.nb.payload imgfstonb blank_imgfs.bin ##_OS.nb.payload base_os.nb.payload
Click to expand...
Click to collapse
Aloha Man,
- i'm trying to use your tutorial to Dump and Rebuild an HTC ROSE (S740) ROM
- i'm at the point where i've downloaded the RUU_Signed, and folowed the above procedure until step 7
- in step 2, i've replaced ## in ##_OS.nb with 03, witch is the number of the file after nbhextract
- i can't find 03_OS.nb.payload and at step 7, the command spits out and error :
" ImgfsTools 2.1rc2>imgfstonb blank_imgfs.bin 03_OS.nb.payload base_os.nb.payload
ImgfsToNb 2.1rc2
Using bigstorage mode
Input file 03_OS.nb.payload cannot be opened. Exiting "
Should i rename
OS.nb.payload to 03_OS.nb.payload or change the syntax on the command input file accordingly ?
tks again alot for your help !

UrbanWarrior said:
Aloha Man,
- i'm trying to use your tutorial to Dump and Rebuild an HTC ROSE (S740) ROM
- i'm at the point where i've downloaded the RUU_Signed, and folowed the above procedure until step 7
- in step 2, i've replaced ## in ##_OS.nb with 03, witch is the number of the file after nbhextract
- i can't find 03_OS.nb.payload and at step 7, the command spits out and error :
" ImgfsTools 2.1rc2>imgfstonb blank_imgfs.bin 03_OS.nb.payload base_os.nb.payload
ImgfsToNb 2.1rc2
Using bigstorage mode
Input file 03_OS.nb.payload cannot be opened. Exiting "
Should i rename
OS.nb.payload to 03_OS.nb.payload or change the syntax on the command input file accordingly ?
tks again alot for your help !
Click to expand...
Click to collapse
You are correct ... Step 7 should should not have the ##_ ... I have corrected the instructions above in my previous post. The command should be:
Code:
imgfstonb blank_imgfs.bin OS.nb.payload base_os.nb.payload

dj13241 said:
To rebuild flashable ROM from DUMP (Currently OS Only, No radio or SPL):
1) You need a base os.nb.payload for your device ... See below for details
2) Convert OS IMGFS (Part02.raw) to nb.payload (new-os.nb.payload) imgfstonb Part02.raw os.nb.payload new-os.nb.payload
3) Insert XIP (Part01.raw) into new-os.nb.payload implantxip Part01.raw new-os.nb.payload
4) Merge os-new.nb.payload into os-new.nb nbmerge -kaiser os-new.nb
5) Create os-new.nbh nbhutil, Select "Touch_Pro2" under "Target Device", change RHOD*** to RHOD500, click the ... box next to OS, and select new-os.nb, click Build NBH and select where to save NBH file.
How to get a base os.nb.payload:
1) Download a stock ROM and extract RUU_Signed.nbh
2) Extract RUU_Signed.nbh nbhextract RUU_Signed.nbh - This will list the files extracted ... The one you need is ##_OS.nb ... Copy as os.nb copy ##_OS.nb OS.nb
3) Split OS.nb to OS.nb.payload nbsplit -kaiser OS.nb
4) Create OS.imgfs.bin imgfsfromnb OS.nb.payload OS.imgfs.bin
5) Create empty directory called 'DUMP' (If a DUMP folder exists, rename it) mkdir DUMP
6) Create a blank IMGFS file imgfsfromdump OS.imgfs.bin blank_imgfs.bin
7) Create base_os.nb.payload imgfstonb blank_imgfs.bin OS.nb.payload base_os.nb.payload
Click to expand...
Click to collapse
Aloha again,
i need some further clarifications if u are so kind :
- i've properly finished the "How to get a base os.nb.payload" section, so now i have a "base_os.nb.payload" file
- going back to point 2 of the section "To rebuild flashable ROM from DUMP (Currently OS Only, No radio or SPL)", i've succesfully executed points 2 and 3 , but when i go to try point 4 nbmerge spits out the following error :
"NBMerge 2.1rc2
Could not open input file os-new.nb.payload"
My Questions :
- where do u use the "base_os.nb.payload" file that's created at the "How to get a base os.nb.payload" step ? since the file is called "base_os.nb.payload" and in the command syntax description u call it : "base os.nb.payload"
- until point 4 of the "To rebuild flashable ROM from DUMP (Currently OS Only, No radio or SPL)" section in the syntax u use the name "new-os.nb.payload" for the file,
- from point 4 on u use the term "Merge os-new.nb.payload into os-new.nb" -> so os-new.nb.payload , and NBmerge is expecting "Could not open input file os-new.nb.payload" but until point for we've created a file called "new-os.nb.payload"
- shouldn't the syntax for the commands from point 2 thru 4 be what NBMerge is expecting ? meaning "os-new.nb.payload"
thanks again for your help!

When I get home from work today, I will run through the steps and eliminate any errors I find.

UrbanWarrior, I have updated the 'Build a Flashable ROM' section step 2 ... I changed the reference to 'os.nb.payload' to 'base_os.nb.payload' ... Let me know if you run into any other issues.

I was trying the steps for my HTCJade to dump my stock ROM. Things were going smoothly however, the step
"Insert XIP (Part01.raw) into new-os.nb.payload implantxip Part01.raw new-os.nb.payload"
fails with an error "XIP File not Specified!"
I noticed that the mentioned step is not following tha syntax of the command:
Usage: implantxip -XIP <xip.bin> -PAYLOAD <.nb.payload> [-ImgStart <hexvalue>] [
-uldr [tryremove] ] [-PP <MbValue>] [-NoCert]
The command expects "xip.bin" but i am giving the argument as Part01.raw as per the step.
What to do? Can anybody help.

svaym said:
I was trying the steps for my HTCJade to dump my stock ROM. Things were going smoothly however, the step
"Insert XIP (Part01.raw) into new-os.nb.payload implantxip Part01.raw new-os.nb.payload"
fails with an error "XIP File not Specified!"
I noticed that the mentioned step is not following tha syntax of the command:
Usage: implantxip -XIP <xip.bin> -PAYLOAD <.nb.payload> [-ImgStart <hexvalue>] [
-uldr [tryremove] ] [-PP <MbValue>] [-NoCert]
The command expects "xip.bin" but i am giving the argument as Part01.raw as per the step.
What to do? Can anybody help.
Click to expand...
Click to collapse
i had the same problem. i just did "implantxip -XIP Part01.raw -PAYLOAD new-os.nb.payload"