I have to test a new 32 MB rom that has been packaged as a nk.bin file.
The special HimaUpgradeUt lets me bypass bootloader 1.06 protection.
So I'd like to transform my nk.bin into a nk.nbf.
Is there some command line tool that allows to to this?
Thanks,
There is such a tool. It is your favorite hex-editor. Take any NBA file, and paste there your BIN just after the header. Then encrypt with xda2nbftool and flash.
nk.nbf generated this way does not boot
sorry but I'm stuck at bootloader level after flashing.
I took the .nba header (17 912 bytes), appended the .bin files (32 500 000 bytes), appended spaces to fill the exact nk.nba file (33 554 496 bytes), re-crypted the .nba into .nk.nbf, flashed with himupgradeut.exe, but no joy. Where may I be wrong?
thanks for your hint,
Related
Hi,
I recently upgraded to WM2003SE, this introduced some errors om my Q-Tek 2020 which is why i want to downgrade to the original image.
I downloaded 'HI_TMNL_17200_190_11700_Ship.exe' from the T-Mobile (NL) site, but when trying to execute it it shows "Country ID error" and stops.
I searched the forum and found a post the said i could use the no_id patch. After reading the instructions i found out that this patch needs the extracted files, but i only have the .exe i downloaded.
Can someone give me some advice?
Cheers,
-peter
Run the .exe file and press next ONCE. (this extracts the files)
open file explorer on your pc and navigate to C:\Documents and Settings\YOUR NAME\Local Settings\Temp
in this directory there should be a temp directory (mine was called pftA4.tmp)
the ROM images are located in this directory.
once you cancel the .exe program the files are deleted, so copy them to a new directory to save them.
Good luck.
Thanks, i managed to get the files!
I've been reading a lot on the forum lately, and in particular this post:
http://forum.xda-developers.com/viewtopic.php?t=12101
When trying to get the xor keys with the command 'xda2nbftool.exe -t' it only shows the xor keys for "ms_.nbf" and "Radio_.nbf".
I'm missing they key for "nk.nbf" while the file does exist and is in the current directory.
I tried this command on two rom's and both did not gave me the nk.nbf xor key.
G:\peter\Officele T-Mobile image>xda2nbftool.exe -t
xda2nbftool -x ms_.nbf ms_.nba 0x20040305
xda2nbftool -x Radio_.nbf Radio_.nba 0x20040306
Another "push" in the right direction would be appriciated
-P
search the ftp
i do beleave that god toenailed has already decompressed that files
check in the ftp
Thanks rictec, but i looked all over the ftp today but didnt find it.
Nevertheless, the xda2nbftool.exe should be able to decompress my files right? Do you know why i'm not getting a xor key for that file (nk.nbf)?
Cheers,
-P
Could anyone please help me out?
I'm still in the dark about why i can't get the key from the nk.nbf file using xda2nfbtool.exe
Help would really be appriciated!
-peter
After looking for some tuts on upgrading my mda II to wm2003se i destroyed my pda, well works pda but still mine and i'm gutted.
i downloaded wm2003se from here. After not being able to get anything to work i transfered the contents of the files to sd card. then i tried booting the files on pda.
I got to 1 of these
HimaClearJumpCode
HimaGetDeviceData
xda2nbftool
then the pda reseted to
a dead screen.
all i see at the top of the screen is seriel and at the bottom is v1.06 and if i plug the cradle in the serial goes to usb?
Can i fix this myself or is my boss gonna be having it in for me?
Regards.
1 thing i know for sure, i'll not do this again
This is file i dl
Himalaya_WM2003SE_Upgrade
Your device is in bootloader mode...
Put the XDa back into the cradle and on the PC start the upgrade program again.
Brgds
Pat
Yes it is stuck in bootloader. The problem i have when running the upgrade is that the upgrade is meant for o2 xda not tmobile mda II.
I know i need to change the id and have read the read me on changing the id but i do not know how to extract nbf files so i can do this
The nbf files are configured for operator ID O2 and language ID WWE. If you need to change these, carry out all the steps below. If they are OK for you, go straight to step 5.
1. Extract the decrypted versions of the nbf files by entering the following commands at the command prompt:
xda2nbftool -x NK.nbf NK.nba 0x20040304
xda2nbftool -x Radio_.nbf Radio_.nba 0x20040306
2. Modify the operator ID in the nbfs to the value you require by entering the following commands at the command prompt substituting <operator> with the required value:
xda2nbftool -sd PH10 -so <operator> -sl WWE NK.nba
xda2nbftool -sd PH10 -so <operator> -sl WWE Radio_.nba
3. Update the crc values for each of the decrypted files by entering the following commands at the command prompt:
xda2nbftool -c -u NK.nba
xda2nbftool -c -u Radio_.nba
4. Encrypt the files back into the nbf files by entering the following commands at the command prompt:
xda2nbftool -x NK.nba NK.nbf 0x20040304
xda2nbftool -x Radio_.nba Radio_.nbf 0x20040306
what am i supposed to do with this lot?
Yes, that's what you have to do.
You can also download the rom editor from here and change the values with the editor. Get the rom editor from here:
http://wiki.xda-developers.com/index.php?pagename=ER2003Edit
Good luck'
Patric
You can also download the rom editor from here and change the values with the editor. Get the rom editor from here:
http://wiki.xda-developers.com/index.php?pagename=ER2003Edit
Good luck'
Patric
Click to expand...
Click to collapse
Thanks dude, the error of my ways has been playing on my mind all day.
The Mda II is now working again and is all cool. I do have and O2 boot up screen on my T-mobile MdaII and thats cool cos my t-mibile sim card works aswell.
BUT!!
1 big problem we have is that 4 or 5 of our mda's have no camera function.
Upgrading the os was only to get the cameras working so that i could get my mates cameras working, now my Mda has no camera function.Lol.
forum.xda-developers.com has many files but there is so much to search through that i find myself going round in circles in the search. Can i please ask for more help in getting my camera working.
Regards
1 thing after another eh! I find myself buzzing with joy at my upgrade but still there is a darkness lurking.
Ps
ER2003Edit is exelent, a true life saver and so simple and easy to use, thanks to the creators on that 1.
Go to the FTP section
ftp://ftp.xda-developers.com
Login as xda and xda (all in small letters)
Go to the Himalaya section. You will find there many extended ROM for 2003SE to download. Download one EXTROM, open in EREDITOR and extract the Camera cab from there.
Install the cab on your XDA.
Cheers
Pat
Go to the FTP section
ftp://ftp.xda-developers.com
Login as xda and xda (all in small letters)
Click to expand...
Click to collapse
Exellant info, thanks. Luckily i know about ftp so i can now finish this post.
Thanks to all peeps who have given me there time!
Regards...Mike
Please help! Being an avid user (I really enjoy the old system environment I was using), but not that much of a "techie". I've managed to create for myself an interesting problem/ concern. I followed a link here in xda-developers and I foolishly tried upgrading my system through the following: Himalaya_WM2003SE_Upgrade and HIMA_WM_2K3_EXTROM. I need to and want to restore back to my old system. Please help me!!!
Note: Not being a consumate techie, but a user, I may have overlooked a something below... But I desperately need to restore.
"I obtained (with many thanks to fychan) a memory image of an English version of WM2003 SE which is an earlier version than the recent Chinese release, but it is genuine English. I managed to create an installable NK.nbf file from this. Also, mamaich has provided the version 1.18 Radio upgrade included here. Many thanks to mamaich for that and also for some advice when I was building the OS nbf file. Also, mamaich has provided some CAB files for Extended ROM which I have also attached here separately.
Attached is an upgrade for Himalaya devices to WM2003 SE WWE, Radio 1.18. Unzip the attachment into a folder of your choice. The nbf files are configured for operator ID O2 and language ID WWE. If you need to change these, carry out all the steps below. If they are OK for you, go straight to step 5.
1. Extract the decrypted versions of the nbf files by entering the following commands at the command prompt:
Code:
xda2nbftool -x NK.nbf NK.nba 0x20040304
xda2nbftool -x Radio_.nbf Radio_.nba 0x20040306
2.
3. Modify the operator ID in the nbfs to the value you require by entering the following commands at the command prompt substituting <operator> with the required value:
Code:
xda2nbftool -sd PH10 -so <operator> -sl WWE NK.nba
xda2nbftool -sd PH10 -so <operator> -sl WWE Radio_.nba
4.
5. Update the crc values for each of the decrypted files by entering the following commands at the command prompt:
Code:
xda2nbftool -c -u NK.nba
xda2nbftool -c -u Radio_.nba
6.
7. Encrypt the files back into the nbf files by entering the following commands at the command prompt:
Code:
xda2nbftool -x NK.nba NK.nbf 0x20040304
xda2nbftool -x Radio_.nba Radio_.nbf 0x20040306
8.
9. Place your device in the cradle, ensuring that the cradle is plugged directly into a USB port on your PC and not to a hub and that the power supply is connected to the cradle. It is also a good idea to disable any screensavers.
10. Run HimaUpgradeUt.exe
11. Sit back and wait for the Congratulations screen to be displayed on your PC. Your device will still be displaying 'Upgrading radio stack, please wait', but as long as the PC says it is done, then its all OK.
Notes:
a. I have installed this upgrade on my XDA II without any problems, and have also been able to revert back to the 1.72 ROM I had installed previously. I have bootloader v1.01, and I don't know whether it would be any different for later versions of bootloader.
b. After upgrading, a hard reset takes places and the Extended ROM is installed. I found that several applications caused a 'Application may not display properly.....' message box to appear which required tapping to dismiss. Therefore, you will need to make sure that TPDisable.exe is not run in the Config.txt script in the Extended ROM, otherwise you will not be able to respond to the messages.
Edit: I've created a .BAT file which can be run from a DOS prompt to replace steps 1-4...
Usage: OperatorUpdate operatorID
where operatorID is O2 or CDL or TMOBILE, etc.
Just unzip the attached zip file.
________________________________________
OperatorUpdate.zip
Description: Update operator ID in .nbf files.
Download
Filename: OperatorUpdate.zip
Filesize: 528 Bytes
Downloaded: 4289 Time(s)
________________________________________
________________________________________
HIMA_WM_2K3_EXTROM.RAR
Description: Extended ROM CABs
Download
Filename: HIMA_WM_2K3_EXTROM.RAR
Filesize: 2.88 MB
Downloaded: 9422 Time(s)
________________________________________
________________________________________
Himalaya_WM2003SE_Upgrade.zip
Description: OS and Radio
Download
Filename: Himalaya_WM2003SE_Upgrade.zip
Filesize: 17.52 MB
Downloaded: 17787 Time(s)
________________________________________"
Hi all,
Can someone tell me how I flash a .bin or a .nb0 file on the Hermes using Mitty?
I have got the new bootloader and its supersid, just wana try a rom I got sent
thanks!
dave
Here's the howto:
http://wiki.xda-developers.com/index.php?pagename=Hermes_BootloaderMFG
Basically, you need to use 'lnb' command for unsigned files, and 'lnbs' for signed files. The syntax is the same for both commands:
Code:
lnb <PathName> [StartAddr] [Length]
If StartAddr is omited it defaults to 0x501a0000, which is the address of OS.nb
If Length is omited it defaults to the legth of the file you provided in PathName.
The addresses for all known ROM parts are here (scroll down to "NAND flash distribution"):
http://wiki.xda-developers.com/index.php?pagename=HermesMemoryMap
Be careful if you flash a cooked or modified OS.nb, as it might produce bad blocks in NAND.
Hi there,
How can i replace a base rom file while cooking my own rom? I want to replace the browser.dll, but not afterwards when the image is on my phone, i want to include it into my rom. My problem is after i build my own rom i got the "patched" browser.dll replaced by the original one.
I understand that i have a imageinfo.txt and imageinfo.bin along with the 5 files s000, s001, s002, s003, s004 and i guess the browser.dll is build from these files. But how can i generate those files or modify them to that my patched browser.dll is included into the cooked rom. Or isn't that possible at all?
regards,
nEUTRon
if browser.dll is a module (it's in a folder in the dump dir whose name is also browser.dll) then just remove the folder and replace it with your own dll.
The actual technique required to do this depends on the kitchen you're using. With Tadzio's tools, I simply remove the folder then move my new dll to the dump directory. Tadzio's tools rebuild imgfs from the dump dir and then merges it back into the XIP section.
Hi....I have the same problem....
What's wrong??
1) I split a .NBH to some .NB
2) Put in the same folder, Tadzio's Tools and OS.nb
3) Make the payload using the string "NBSplit -hermes OS.nb"
4) Make the imgfs.bin using the string "Imgfsfromnb OS.nb.payload imgfs.bin"
5) Extract all files to dumpfolder using the string "ImgfsToDump imgfs.bin"
Ok....now I would want to replace the "MsgStore.dll" and the "cespell.dll"....
Both are MODULEs (in the dump folder I have two folder named as, contain the dll e few other files)
So, I'll delete this two folder from Dump folder, and put in this my two DLL as they are
(note: original MsgStore size: 151 kb / My MsgStore size: 152 kb
note2: original cespell size: 7kb / My cespell size: 8 kb)
6) Make a new imgfs.bin using the string "ImgfsFromDump imgfs.bin imgfs-new.bin"
7) Make the new payload using the string "ImgfsToNb imgfs-new.bin os.nb.payload os-new.nb.payload"
8) Make the new OS.bin using the string "NBMerge -hermes os-new.nb"
What's WRONG ????
Tnks,