No given passwords work with those files :x Since they are (PH20B), does relate?
Has anyone got those pw's? I repeat for Blue Angel only.
1) The files you are looking at are simply zipped cab files (See posting in Extended Roms thread)
2) 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.
3) The following are the "passwords" (Really xor values) working for most Blue Angel Roms:
ms_.nbf = 0x20040522
nk.nbf = 0x20040521
radio_.nbf = 0x20040523
Related
:?:
Hi,
I have ordered a new QTEK9090, which the provider here will only supply me in French. I see conversions on this forum for German to English. However, is there one for Frnech to English?
Thanks
Not that i'm aware of, but the process is similar. You will just have to do a few extra steps, like putting Devicedata.exe on your device and retrieving the devicedata.txt file so you know the operator and "country" ID to use with xda3nbftool.exe.
No reason why it shouldn't work.
It should be the same conversion process. You'll need to dump the french ROM from your phone unlock it using the exact same commands, use a hex editor to see what the french ROM has for a carrier code (T-Mobile) and the designation to say that it is in French (i.e. WWE for english).
You will then modify the .bat file in the other posts that were listed for the German update.
********************8
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 GER ms_.nba
xda3nbftool -so T-MOB101 -sl GER nk.nba
xda3nbftool -so T-MOB101 -sl GER 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
*****************
You'll want to modify the "T-MOB101" and "GER" settings to what you find in the first 128 bytes of the French ROM that you pull off the device to your SD card or PC. I have never dumped a ROM off of a device so you have to search this site for instructions, I know they have been posted multiple times. So to sum it up:
1. Dump the ROM from your French phone to your desktop
2. Use the command xda3nbftool -x nk.nbf nk.nba 0x20040521 to unlock the nk ROM
3. Use a hex editor to read the nk.nba file (XVI32.exe, search web)
4. Once you see what they have for the operator code and how they specify French (FRE???) you will then modify the above commands and save in a .bat
5. Run the .bat file you just saved
6. Run BaUpgradeUt.exe in you unzipped ROM directory.
Hope this helps.
I Just noticed that you’re a newbie. If you search the forum for "dumping ROMs to the SD card", "How do I get the ROM off my XDA/XDAII/MDAIII" , etc and forward me the links, I'll then do the processes on my end first so I know what I'm doing before I hold your hand. I can then walk you through the process to get the two unknown pieces of data, provider and the French 3 letter abbreviation. I'll do all the changes and upload a completed set of files for you to use to make it easy.
Deal? If so, start searching and PM with your results.
later,
Wnpublic,
Do you know how to dump from the device to the SD or desktop machine?
I don't know how to dump the "original" ROM. It appears to be possible, I just haven't explored.
BUT
dumping that rom to get country code and operator ID is unnecessary. All you need to do is put Devicedata.exe on your device and run it. That will create a small text file called Devicedata.txt. Open it and it shows the whole header - or at least enough of it to do the upgrade.
Devicedata.exe is part of the standard upgrade package. simply get the imate one, for instance, unzip it twice, and devicedata.exe will be there.
Thanks,
I had just realized this last night as I reading up on dumping the ROM. I had totally forgot about it, thanks for the reminder and making the complex simple!
I tried to upgrade my Tmobile MDA III with the ROM of O2 XDA IIs and it is now stuck in boot load. I was wanting to use the new rom to fix the bluetooth issues, But now I would just be happy if I can get it back to the factory defaults. This was the German flashed to English MDA III. If there is anyone who can help me Pleeeease! Thanks in advance to anyone who can reply or help.
Shaneframe
Mine is also stuck
Yeah this sucks ... i get error 101: connection error
Hi
RELEVANT TOOLS
XDAII USB Cradle
SD card with at least 32 MB memory (All data will be deleted during the process)
Multi-Port/USB TTY
PRE-PREPARATION
Backup all data on your device, because this process involves hard reset.
Kill ActiveSync (wcescomm.exe) by using task manager (Ctrl + Alt + Delete).
HERE WE GO
Go to bootloader mode (hold Power Button + Directional Pad + Reset Button)
Run Muti-Port/USB TTY (romupdate.exe)
bill gate u gave me my needed tip THANK A 100 no A 10000000 times
Billgate
Interesting I must say.
I was hoping that you might "please" spend so time and explain the Boot load for us all.
Unlike the extened rom were I have read enough about it and thus some what understand it, I have no understanding about the boot load on a PPC.
Would be nice of you, thanks
Reviving a dead MDAIII from Bootloader
I hear you brother! Thanks to XDADOM elsewhere on this website, I *finally* managed to revive my dead MDAIII tonight.
You will need this ROM PDA2k_WWE_12200_162_10600_SHIP.exe (lurking somewhere on this website), xda3nbftool.exe and I also had ActiveSync 3.8 which may help.
The process to update is described elsewhere on this website, but as it's easy to get lost, here's how I did it:
Double click on the EXE file. Just before the upgrade starts, hop into Windows Explorer and try to locate the file radio_.nbf which will be in a TEMP folder somewhere on your hard disk (usually c:\Documents and Settings\YOURNAME\Local Settings\Temp)
Copy/Move all of these files into somewhere safe and memorable.
Fire up Notepad and cut and paste the following text and SAVE IT AS A .BAT file (NOT a TXT!!). Then run the attached batch file.
-----------------------------------------------------------------------------
xda3nbftool -x ms_.nbf ms_.nba 0x20040522
xda3nbftool -x nk.nbf nk.nba 0x20040521
xda3nbftool -x radio_.nbf radio_.nba 0x20040523
xda3nbftool -sd PH20B -sl WWE -so T-MOB005 ms_.nba
xda3nbftool -sd PH20B -sl WWE -so T-MOB005 nk.nba
xda3nbftool -sd PH20B -sl WWE -so T-MOB005 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
---------------------------------------------------------------------------------
Now cancel out of the Update, then navigate back to where you just copied those files. Run the file BaUpgradeUt and hopefully your MDAIII should be back to factory settings as an "imate" after about 10-20 minutes.
Once again, THANK YOU to XDADOM for his time, patience and efforts in helping me out.
MB,
No problem buddie!
If anyone else has this problem with their Blue Angel device feel free to PM me and my "Team" (MDAIIIUser and I [and you too MB if you're up for it!]) will endevour to help you! (I think we need a name...like...the Blue Angels?!?!?)
We will also be starting a new thread with a full walkthrough to upgrading/restoring your device...this will hopefully include all the different country and languages codes for all the different types of Blue Angels....
Coming soon!
So, in the meantime, PM me and we'll see if we can help!
Dom
I have posted an Excel sheet on the ftp server describing the Byte Layout for the BlueAngel Extended ROM with a view to creating a file extractor / creator so that we can build our own ms_.nbf files.
Please note that in order to work on ANY of the ROM files for the BlueAngel you must first decode them using the following:
Code:
xda3nbftool -x ms_.nbf ms_.nba 0x20040522
xda3nbftool -x nk.nbf nk.nba 0x20040521
xda3nbftool -x radio_.nbf radio_.nba 0x20040523
This results in producing three files with the same size and name but an nba extension. The ms_.nba file is the one we are concerned with at the moment, however if someone wishes to look at the nk.nba file it would be nice to be able to extract the base rom files directly as well.
The Excel sheet can be found here if you wish to have a play! There are some areas I am unsure of as yet and as such it is still a work in progress.
I have made a start at coding a fat file extractor but:
1) Have not been programming for some years now so it will probably take me until the XDA XVII comes out!
2) Hope that someone else has already written FAT16 file handling code and could help out!
Any help greatly appreciated.....
I have now created this as a Wiki Page which can be found here.
Hi guys,
I have had my XDA IIs for a few weeks now and I have been reading up on how to upgrade it to 1.40 with the latest 1.13 radio. I would appreciate if I could just describe the steps I am going to take to upgrade it and see if anyone can tell me if I have misunderstood some of the wiki/ forum instructions.
My current version is (from DeviceDate.txt) PH20B 0 B WWE E O2___001 1.31.00 0 0 1.31.139 1.06.00 06.00.
1. I have downloaded from the wiki (ftp://xda:[email protected]_11200_Ship/Extracted_Type_I_CE_Rom/nk.nbf) From what I understand, a Type I file is one that can be edited with xda3nbftool.exe- is this correct?
2. I have also downloaded the 1.13 radio ROM from http://forum.xda-developers.com/viewtopic.php?t=23807&highlight= . I understand this is also a type I file as mdaIIIuser converted it.
3. Using the Type I upgrade tools, I use the instructions from the wiki getting started (http://wiki.xda-developers.com/index.php?pagename=BA_GettingStarted) and edit editfix.bat for my Operator ID etc.
4. At this stage I am not upgrading my Extended ROM with anything, so I am not putting any ms_.nbf into my upgrade directory. I am not upgrading my ext rom like this as we cannot edit ms_.nbf for Blue Angel (which is a pig as I am used to my Himalaya!!!!!)
5. I run editfix.bat from command prompt which hopefully will convert my rom and radio files to O2 UK.
6. Now that my files are converted I run BAUpgrade_UT.exe (from what I understand I dont need the MA_upgradeUT.exe since my headers should all be correct) If this doesn't work due to country code error etc, I use the cracked MAUpgrade_UT files and try again (twice).
7. My radio and ROM shoudl now be 1.13 and 1.40 WWE respectively.
8. My extended ROM is still 1.31 though so I unlock and unhide it and remove all files (except for my O2 UK customization cabs for GPRS etc) and replace them with the 1.40 Base. At this stage I get a little confused, from what I gather, i need to pick one of the QTEK base roms. Which one would be the best to add my O2 stuff to? I was thinkng that I-Mate Qtek 1.40.147 WWE (as it uses the config.txt method, which I am used to!) I copy these files into my extended ROM, upadate the config.txt to include my O2 UK and other customizations and then I do a hard reset. And there you go, job done, I hope!
Please, if anyone who has done this before with Blue Angel could check over my steps to see if I have done anything particularly foolish. I am so used to all hte tools used to customise my Himalaya so it is just a case of getting used to a new way of doing things.
Thanks for any help in advance!
Fin
I thought I should include the contents of my editfix.bat:
REM ~DeviceData.txt PH20B 0 B WWE E T-MOB101 1.12.22 2 2 1.12.169 1.02.00 02.00
REM Replace the question marks with the data from ~DeviceData.txt
REM 'sd' stands for device, e.g. PH20B.
REM 'sl' stands for language, e.g. WWE.
REM 'so' stands for operator (Country ID), e.g. T-M0B101.
REM ms_.nbf Password = 0x20040522
REM nk.nbf Password = 0x20040521
REM radio_.nbf PAssword = 0x20040523
xda3nbftool -x nk.nbf nk.nba 0x20040521
xda3nbftool -x radio_.nbf radio_.nba 0x20040523
xda3nbftool -sd PH20B -sl WWE -so O2___001 nk.nba
xda3nbftool -sd PH20B -sl WWE -so O2___001 radio_.nba
xda3nbftool -c -u NK.nba
xda3nbftool -c -u Radio_.nba
xda3nbftool -x nk.nba nk.nbf 0x20040521
xda3nbftool -x radio_.nba radio_.nbf 0x20040523
del *.nba
-Fin
Looks fine (only skiimed it though)
Note the files are type I so you need the type I upgrade files (which you have fixed) the Ma tool is for type 2 files.
Dont mix them up.
Thanks for checking for me. Have just updated my phone and all seems fine, still need to check my GPRS and operator settings are all there!
Thanks again,
Fin
the 1.40 has BT 3900, your EXT Rom might have cabs that install BT 3500, which will be a downgrade.
Check that your Ext rom is clean of patches and add the 1.40 patches off wiki that you need. Browse the kitchen for more info.
I have read through the ERK in wiki and I can't see anything to install bluetooth version 3500. I might be wrong though, the only cabs I have left from my previous extended ROM are as follows:
CAB: \Extended_ROM\BA_cm_rm_map_o2_v3.CAB
CAB: \Extended_ROM\O2UK_AP_09212004_BA_1.sa.CAB
CAB: \Extended_ROM\O2UK_Button9_WWE.sa.CAB
CAB: \Extended_ROM\O2UK_Connection_Setting.sa.CAB
CAB: \Extended_ROM\O2UK_Hide_WLan_message.sa.CAB
CAB: \Extended_ROM\O2UK_PIE_homepage.sa.CAB
CAB: \Extended_ROM\O2UK_Regional_TimeZone.sa.CAB
CAB: \Extended_ROM\install.ARM.CAB
From what I can gather these are just customization cabs for O2 UK, if anyone knows any different please let me know!
Thanks again for your help!
Fin
Looks good, have fun
Update XDA IIs
I have the unlock UK xda IIs, and I have download the new update. I was hopping someone can answer my question. If I install my update will it lock my phone again?
Once you unlock, it's unlocked for good - no need to worry about changing ROMs back and forth.
Hi,
i just downloaded the file BA_DT_GER_14001_154_11200_Ship.exe from the xda-developers ftp-server.
now i try to change the id's for the .nbf files so that the updater-program updates my xdaIII from o2.
xda3nbftool -x ms_.nbf ms_.nba 0x20040522
WARNING: this does not look like a nbf header, possible you provided the wrong password
xda3nbftool -x nk.nbf nk.nba 0x20040521
WARNING: this does not look like a nbf header, possible you provided the wrong password
xda3nbftool -x radio_.nbf radio_.nba 0x20040523
WARNING: this does not look like a nbf header, possible you provided the wrong password
Perhaps someone can tell me what i did wrong?
thanks in advance.
Best wishes from germany
Sascha Schmidt
EditFix.bat ?
I'm new at this myself but I think there's something missing when you're re-doing the ID. I think you need to use GetDeviceData.exe to get your device info and then use EditFix.bat with that info (or run the xda3nbftool directly) with the -so -sl -sd options.
Hello, today I tried upgrading to Mamaich's Wizard, but unfortunately didn't get that far... I was following the WIKI, and got as far as ' Download EditFix.bat and XDA3NbfTool. Patch your ROM with the data in DeviceData.txt -- read EditFix.bat for the how-to. '
This seems rather vague, and when I click on the How-to it doesn't explain it at all, so I simly ran the .bat in the folder and it began processing it, until I got the following message...
WARNING: this does not look like a nbf header, perhaps you entered the wrong password
If what bytemybits is true, can someone explain how one should run editfix.bat properly?
Thanks for your help
Leo
Okay let me be more clear as I found that somewhat vague as well.
Download GetDeviceData.exe to your desktop, then copy it to your phone. Run it on your phone, it won't look like it did anything but there will now be a file called DeviceData.txt in your \Windows\ folder. Copy that file to your desktop and open it with your favorite text editor. It will be one long line with a bunch of non-printing (usually square boxes) characters. Remove the non-printing characters. You should now have something like:
PH20B 0 0 ORANG001 1.40.00 0 0 1.40.00 0 0 1.13.00 00
Now open the EditFix.bat file in that same text editor. There are a bunch of REM statements that tell you what to do. Basically you take the DeviceData information and use it to fill in the question marks in the bat file. So where there is a -so ????? change it to read -so PH20B (or wehatever you have). Do the same for the other question marks replacing them with the appropriate info. Save the EditFix.bat.
Now that's done run the EditFix.bat as instructed.
Ahhhh, thanks for your help! I shall try that later and let you know if I have success.
Thanks again bytemybits!
Leo
saschahb said:
Hi,
i just downloaded the file BA_DT_GER_14001_154_11200_Ship.exe from the xda-developers ftp-server.
now i try to change the id's for the .nbf files so that the updater-program updates my xdaIII from o2.
xda3nbftool -x ms_.nbf ms_.nba 0x20040522
WARNING: this does not look like a nbf header, possible you provided the wrong password
xda3nbftool -x nk.nbf nk.nba 0x20040521
WARNING: this does not look like a nbf header, possible you provided the wrong password
xda3nbftool -x radio_.nbf radio_.nba 0x20040523
WARNING: this does not look like a nbf header, possible you provided the wrong password
Perhaps someone can tell me what i did wrong?
thanks in advance.
Best wishes from germany
Sascha Schmidt
Click to expand...
Click to collapse
it's not gonna work. Any rom newer than 1.22 is Type II, that means that xda3nbftool can not be used for it. You have to use MaUpgradeUt_noID.exe for upgrading.
xda3nbftool For 1.40, 1.42 does not exist?
And to carry out operation nbf-> nba for roms newer than 1.22 it is impossible?
I have correctly understood?
Problem in the password?