The irish O2 update includes "NK_Wallaby31413wwe_O2_Full.nbf". This is I assume the ce-rom part. Which file is the bootloader ?
If the bootloder is in fact included in the above file, what should be ticked & selected to write this to the SD card ?
delhaze said:
If the bootloder is in fact included in the above file, what should be ticked & selected to write this to the SD card ?
Click to expand...
Click to collapse
Start XDA ROM Image Tool. Select 'Write to SD card'. In the box, check both bootloader and Windows CE, in both boxes select the name of the .nbf file. Select the header type for the bootloader that is currently in the device, and remember that you'll need a little more work if the device has a 5.17. (Downgrade to Bootloader 5.15 or 5.14 if you can).
You can, after doing this, save the bootloader and CE part separately to XDA-developer format, as .nb0 (bootloader) and .nb1 (CE) files. Ofcourse you really shouldn't need to first write it to SD to do this. But hey, nobody's perfect...
Related
after I cooked ROM from Jeff Summer's Kitchen, it has the option to choose whether you want it .nb1 or .nbf
.nb1 is for SD card flashing
while .nbf is for advanced users...
so what is exactly the difference between this 2 extensions??
Good Q - I was finkin that 2
Keen to always b learning more. Would appreciate a response to add 2 d knowledge for which without this site I would be stuffed wit an XDA still stuck on d update screen
an nbf file contains some information about what kind of device the os image
is intended for, and a bootloader and the os image.
a nb1 file contains only an os image.
nbf's can be flashed with Programme A.
see http://www.xs4all.nl/~itsme/projects/xda/wince-flashfile-formats.html
osimagetool understands both nb1 and nbf files.
XDA developer Itsme said:
an nbf file contains some information about what kind of device the os image
is intended for, and a bootloader and the os image.
a nb1 file contains only an os image.
nbf's can be flashed with Programme A.
see http://www.xs4all.nl/~itsme/projects/xda/wince-flashfile-formats.html
osimagetool understands both nb1 and nbf files.
Click to expand...
Click to collapse
Do you mean if I flash the phone with .nbf via osimagetool ( Programme A) , it could be over-write bootloader ?
yes, it could. but osimagetool will not take the bootloader from the nbf,
it always puts the 5.15 bootloader in the file that is flashed with "Programme A"
for a reason I don't yet understand, the bootloader is not always updated.
I am quite sure that "programme a" used to update bootloaders, but I have not seen it do this for some time. - maybe it has to do with the rom version?
I am not able to Flash the original O2 ROm to the SD card.
I have copied the file NK.NB1 using XDAtools to the SC card and did a soft reset.
It does not work. Can someone please help me and give me the exact steps to do the same.
I have WM2003 (tmobile) on the phone memory. Wallaby bootloader ver. 6.22.
Please help me.
Ok here you go, its a little outdated but its what I still use:
Qman's how to use XDArit to write nk.nb1 or nk.nbf to your SD card aka the Bootloader Method!
1. Place XDArit and the nk.nb1 or nk.nbf file in the same folder and start XDArit.
2. Select your SD card (disk drive) from the drop down menu.
3. Select Write to SD
Notice that the Windows CE box is already checked so just click the browse button at the end of that window.
4. Select your (nk.nb1 or nk.nbf) image and then Open
Notice by default XDArit will open looking for a *.nb1 file but if you're going to use a .nbf file you'll have to manually change the "Files of Type" to *.nbf
Notice that nk.nbo / nk.nbo was automatically added as your boot-loader and its check box is unchecked so leave it that way and click OK. XDArit should start writing to the card.
When XDArit has finished writing the image put the SD-card into the XDA and hold the power button and soft reset. You'll be taken to the below screen:
SD DOWNLOAD
Card Type:
CE OS & BOOT
Press action to Download
Or
Press REC to Exit
Press action to download and it will start the download/restore from the SD card.
Follow the on screen instructions once its "Completed" which will consist of a "Soft Boot/Reset".
Click to expand...
Click to collapse
It does not bring me to that screen on the bootloader after the reset.
It just says GSM OK.
please help...
Diki said:
I have WM2003 (tmobile) on the phone memory. Wallaby bootloader ver. 6.22.
Click to expand...
Click to collapse
6.22 doesn't recognize ROMs on SD cards ... you have to downgrade it to 5.15 ... and I doubt you can do it coz tmobile ROMs prevent USB flashing
Anyway, try this ... under \XDAtools\binaries directory run this command while your device is connected
pnewbootloader bootloader_5_15.nb0
I just tried and this is what the cmd window says:
D:\Program Files\XDAtools\binaries>pnewbootloader bootloader_5_15.nb0
ERROR: fopen(bootloader_5_15.nb0) - The system cannot find the file specified.
ERROR reading bootloader
Please help me...............please
Oops ... there is a missing "v"
The file name is bootloader_v5_15.nb0
Or just try bootloaderfix.bat
This will do the same... ;-)
Stefan
This is what I got now:
D:\Program Files\XDAtools\binaries>pnewbootloader bootloader_v5_15.nb0
'D:\Program' is not recognized as an internal or external command,
operable program or batch file.
ERROR: ITReadProcessMemory - Unspecified error
Unable to find flash info offset, cannot disable bootloader writeprotect
D:\Program Files\XDAtools\binaries>
I believe this is a DOS error as it can't read "Program Files" as a full name due to the space character.
Try running this command your self from the DOS command window
same error message. typed the whole command myself.
anything?? any answers???
:idea:
:shock:
might be a silly advice ... copy the 2 files to a different directory with a short name ... ex. C:\Test ... and make sure that the device is connected to ActiveSync and in sync
same problem
i cannot downgrade wallaby 5.17 to 5.15 same as diki... but in 5.17 i can use patch wallaby to flash rom to 2003 successful ly... but i still want to know how to downgrade wallaby....
somebody please tell me
my pc is win xp because win me didn't work for xdarit.......thx
sorry in bad english....
Huray. .. i find the way to downgrade wallby 5.17 to 5.15
may be it's can help u
fist please read this fixbootloader.zip is work for .........
This tool depends on specific memory locations for certain roms.
It does verify that it is talking to a known rom. It also does a very
minimalisitc check if the file presented to it resembles a bootloader.
I tested it with 3.16.52, 4.00.10 and 3.04.00 ( the very old ppc2003 rom ).
It should also work with 3.17.03, 3.19.01, 4.00.01 and 4.00.05.
unpack the archive, from the command prompt, in the 'build' directory
run 'pnewbootloader bl515.nb0'.
it should take about 10 seconds.
output should be something like this:
C:\fix\build>pnewbootloader.exe bl515.nb0
protection found at 8c0d62d8
result: 00000000 00000000
Bingo........u have wallaby 5.15 absolutely
This is my step but i flash from 4.00.11Eng Wallaby 5.17 to 3.17.03Eng cook from http://xda.weblink.net ( may this my method not work for u )
first i must go back to ppc 2002 with ver 3.17.03
1.i burn sd by patch wallyby 5.17 with xdarit ( ver 1.3 M ) check box in 1k
2.insert sd to xda
3.press power+soft reset
4.that show screen ................patch press action to continue
5.press contact button
6.that show new menu is restore from sd ( oh god how u can do that xda-development teams ........thx very much )
7.i burn rom 3.17.03 that cook from http://xda.weblink.net ( thank again ) make sure when u cook this rom u did't check box except only for 3.17.03 that have simunlock already and i download in Nk.zip ( sd method )
8.burn Nk.nb1 with xdarit ( ver 1.3 M ) check box in 3.5k
9.press action to restore
10.that confirm to abort or yes press yes
11.wait.........not over than 5 minutes
12.that show screen check sum ok ....succesfully ........ cold reboot
13.press hard reset button ( near earphone plug )
14.boot screen and u have ..... welcome ppc 2002 ... try next step that show on screen and sync with u pc by Guest
15.find bootloaderfix.zip in this forum u can download somewhere.......
16.copy and paste it to Harddisk and extract to bootloaderfix\
17.go to start menu in ur Pc.... i use winXp
18.choose run and type this cmd it will show ur Dos command
19.in Dos command may be will show C:\Documents and Settings\new> u must type this C:\cd\ to go to C:\>
20.type C:\cd bootloaderfix to go C:\ bootloaderfix>
21.type C:\bootloaderfix>cd build to go C:\bootloaderfix\build>
22.type C:\bootloaderfix\build>pnewbootloader.exe bl515.nb0
23.Enter it and if it's not wrong that show this screen
C:\bootloaderfix\build>pnewbootloader.exe bl515.nb0
protection found at 8c0d62d8
result: 00000000 00000000
24.Congratulation now u have Wallaby 5.15 already u can check by unpluck ur cradle and press soft reset+power to check
25.Now that's free times to Upgrade or Downgrade with no problem
26.in Wallaby 5.15 U must use Xdatool to burn rom in ur sd or mmc no need Xdarit anymore hehehehe ( very fast to write rom ..don't believe me? try with ur self )
27.finish........and up to u to upgrade in wm2003 or ppc2002 any version......... huray.......
May be this i write it's cannot help u so much .....but i trust may be it's useful for dump man like me to downgrade Wallaby since i try to read more than 400 topic in here....... : )
and if u cannot flash 3.17.03 in sd because ur Wallaby block it....try to make rom is Nk.exe file but it's very risk to up/downgrade
by activesync because i broke my xda to dead because my com is Hank......... spare ur UPS to protect accident like me...
and so very Sorry in Very Bad English because it's not my tongue language : )
try to do and reply to me in this forum or my email [email protected] Thx....xda-developers teams again ........
Hi I am New about it but I have an Idea probably i have download the radio_stack_upgrade form My-Xda O2 web site and also i have Cooked a nbf ROM file from http://lumpistefan.dyndns.org/ and i have replaced the nbf ROM file to C:\Program Files\PROGRAMME A\english and try to run the PROGRAMME A.exe to upgrade will i have a success on this think ?
D:\Program Files\XDAtools\binaries>pnewbootloader bootloader_v5_15.nb0
'D:\Program' is not recognized as an internal or external command,
operable program or batch file.
Click to expand...
Click to collapse
yeah it's a long file name issue
i think it needs to be d:\program^1 insted of d:\program files
if you make a dir command in the root of the consol it should display
all the names of the dirs in the root
and that should make it clear how the consol inpert the progra files dir name
i Have been flashing all the while Ok . Last Flash T-Mobile 4.04 16
After that can't flash . It gives
Gives Error 011 : execute remote communication program error
ERROR: GetConnectionType - An existing connection was forcibly closed by the remote host.
error getting connectiontype
My active sync ok
PLEASE HELP.Thanks
once a 4.x.x.x rom is flashed to a device, you may only flash it via sd method, and not Activesync/ProgrammA.
Bootloader 5.17 can't flash
Thanks
I got SD to flash
..& followed the steps
After pressing the contacts button, these are the options i get.
it says
FLASH TOOLS
============
CE ROM TO SD
BOOT TO SD
CE+ BOOT TO SD
GSM ROM TO SD
CE + GSM TO SD
I dont have the options that say...
Restore SD
About
Exit
If i press anything is says "CARD Key Invalid"
Please Help
Thanks
if it dont start to autoupdate then
1 the boot loader is not right
2 there is not a valid rom on the sd card
here is a guide
Ok here you go, its a little outdated but its what I still use:
Qman's how to use XDArit to write nk.nb1 or nk.nbf to your SD card aka the Bootloader Method!
1. Place XDArit and the nk.nb1 or nk.nbf file in the same folder and start XDArit.
2. Select your SD card (disk drive) from the drop down menu.
3. Select Write to SD
Notice that the Windows CE box is already checked so just click the browse button at the end of that window.
4. Select your (nk.nb1 or nk.nbf) image and then Open
Notice by default XDArit will open looking for a *.nb1 file but if you're going to use a .nbf file you'll have to manually change the "Files of Type" to *.nbf
Notice that nk.nbo / nk.nbo was automatically added as your boot-loader and its check box is unchecked so leave it that way and click OK. XDArit should start writing to the card.
When XDArit has finished writing the image put the SD-card into the XDA and hold the power button and soft reset. You'll be taken to the below screen:
SD DOWNLOAD
Card Type:
CE OS & BOOT
Press action to Download
Or
Press REC to Exit
Press action to download and it will start the download/restore from the SD card.
Follow the on screen instructions once its "Completed" which will consist of a "Soft Boot/Reset".
Click to expand...
Click to collapse
xda help!!!!!!!!!
have have flashed my xda with the developers-update but i need a german version. if i try to update with a germnman one, the software said no dilddatei found!should i do? please help me and sent a e-mail to [email protected] thx 4 help
Thanks
I did tried but fail ...
XDArit Can't write into Sd It's Say "fail to open device" . PC Can detect it
OSimagetools does the job but end up bootup menu (refer my message)
Is there any way downgrade or upgrade the bootloader ?
Thanks
http://wiki.xda-developers.com/images/startmenu.gif
try picking the fix broken bootloader ?
I think he is having the same problem I am having.
How can we replace or upgrade the bootloader itself?
Hi, I thought I had a Himalaya untill I realized I had a wallaby (I tried flashing Himalaya images which I am not sure worked - Stcuk in loader screen). Anyway, I am using himaupgradeut_noID.exe to put back the proper OEM images now (hope it works) but I cant seem to get any of the images for the Wallaby to want to upgrade?
Is there somehting I am missing about my device?
Thanks,
Ritmo2k
rom
http://lumpistefan.dyndns.org/
guide
Ok here you go, its a little outdated but its what I still use:
Qman's how to use XDArit to write nk.nb1 or nk.nbf to your SD card aka the Bootloader Method!
1. Place XDArit and the nk.nb1 or nk.nbf file in the same folder and start XDArit.
2. Select your SD card (disk drive) from the drop down menu.
3. Select Write to SD
Notice that the Windows CE box is already checked so just click the browse button at the end of that window.
4. Select your (nk.nb1 or nk.nbf) image and then Open
Notice by default XDArit will open looking for a *.nb1 file but if you're going to use a .nbf file you'll have to manually change the "Files of Type" to *.nbf
Notice that nk.nbo / nk.nbo was automatically added as your boot-loader and its check box is unchecked so leave it that way and click OK. XDArit should start writing to the card.
When XDArit has finished writing the image put the SD-card into the XDA and hold the power button and soft reset. You'll be taken to the below screen:
SD DOWNLOAD
Card Type:
CE OS & BOOT
Press action to Download
Or
Press REC to Exit
Press action to download and it will start the download/restore from the SD card.
Follow the on screen instructions once its "Completed" which will consist of a "Soft Boot/Reset".
Click to expand...
Click to collapse
and you will never get anywhere trying to put a rom from a different device on your wallaby device
Thanks for the help
When I build the rom at that page, nothing happens? It thinks for a while then stops? Any ideas?
Thanks!
OK, was able tog et an image of lumpi's page
But now when I run it, it says "ERROR: GetDeviceData - Unspecified error" in the dos window. This "Programme A" exe has never worked on my pda?
Any ideas?
I know you say to use the flash card, but I dont have an external writer?
Thanks,
Re: OK, was able tog et an image of lumpi's page
Ritmo2k said:
But now when I run it, it says "ERROR: GetDeviceData - Unspecified error" in the dos window. This "Programme A" exe has never worked on my pda?
Any ideas?
I know you say to use the flash card, but I dont have an external writer?
Click to expand...
Click to collapse
Then you have to stay at your current ROM. T-Mobile ROMs prohibit flashing via Exe-file, and you get the Error Message....
So only possibility is to flash via SD-Card. As much as i know, you can alos use the XDA itself as Card Reader. Give it a try with the XDA-Tools...
Stefan
This is just a note on an alternate way of doing the bootloader downgrade
If you have attempted to use pnewbootloader and it hasn't worked (error message usually states something about not finding the protection address in flash - can't recall exact wording) then another option which worked for me is to just install the bootloader_v5_15.nb0 file onto your SD card using XDArit and load it using the wallabypatch-sd.nb2 diagnostic image.
Here are the steps:
1. Grab the file wbt-1.5.zip form http://wiki.xda-developers.com/index.php?pagename=WallabyPatch
2. Extract the wallabypatch-sd.nb2 file from wbt-1.5.zip archive.
2. Grab XDArit from http://wiki.xda-developers.com/index.php?pagename=XDArit (file link at bottom of the page).
3. Read the above page on XDArit - paying particular attention to the section on 'Dealing with 5.17 bootloader'
4. Obviously the wallaby patch tool you have downloaded and the one mentioned in the XDArit page above are one in the same, so write the diagnostic image to SD using the 1k header format etc.
5. Do the bootloader procedure described in the XDArit page to get to the "Restore SD" option.
6. Now after choosing 'Restore SD' you should be getting a prompt to insert the new image. This is your que to take out the SD card and put it back into your desktop card writer.
7. If you havent allready install the updated version of XDAtools the link is at the bottom of http://wiki.xda-developers.com/index.php?pagename=XDAtools
7. Using XDArit again choose to write an image and this time select the bootloader checkbox and find the bootloader_v5_15.nb0 file thats in the "C:\Program Files\XDAtools\binaries" directory.
8. Put your new bootloader image laiden SD card back into your XDA, follow the prompt and Zap.
9. upgrade and downgrade your CE image to your hearts content by just writing to an SD card using XDAtools and booting of it - no more pesky 5.17.
Hope this helps somebody, about the only part you wouldn't allready know from looking at other messages on xda-developer is that it does infact work and doesn't (at least not in my case - your milage may vary) frag your bootloader. All the kudos goes to the XDA-developers for making the tools